Automatic translation from German. View original text
Airspace warning in the app: proximity alert in flight
In short: An airspace warning alerts you when your aircraft approaches controlled or restricted airspace, and tells you the estimated remaining time until the boundary. It is only useful if it comes early enough: a warning exactly at the boundary is not a warning, but a notification. Therefore, set a buffer and check before takeoff which data status and altitude filter the app uses.
The flight information service can point out an airspace to you. The map on your knee can. And the app can. Nevertheless, according to the AOPA Safety Letter, Germany records several hundred airspace infringements by VFR pilots every year. Modern cockpit aids have done little to change this magnitude.
EuroPilot Connect originated from the Sport- und Segelfliegerclub Bad Waldsee-Reute , based at EDMZ, 660 meters of grass, runway 14/32, not on the drawing board of a software company. Many in the team hold a pilot's license, and flights and tests are conducted on Bristell LSA, Comco Ikarus C42 C, and Robin DR400, i.e., across ultralight and Echo class. I built the app myself, so I am not neutral. Therefore, I don't speak in adjectives, but in numbers: The airspace data for 36 European countries comes from the daily sync, the warning thresholds are set by default to 2 NM ahead and 200 ft vertical, i.e., exactly to the Take-2 values, and the data primarily comes from KEYVAN Aviation, one of the eight companies with EASA-DAT certification. What this article gives you is the mechanics behind it and verification questions that you can answer yourself in any app on the ground.

Original view from EuroPilot Connect on iPad. Discover all 14 app views →
What is an airspace warning in the app?
An airspace warning is a geometric calculation, not a sensor. The app knows the base area of each airspace and its lower and upper limits from its database. It knows your position, altitude, and ground track from GPS. From both, it estimates when your current course will intersect the boundary and alerts you beforehand.
The distinction from a collision warning is important. An airspace warning says nothing about other traffic. It only says: This volume is ahead of you, and you will be in it within this time.
Equally important is the distinction from mere display. A map that draws airspace requires you to look. A warning comes to you. In flight, these are two completely different things, because the moment you are not looking is exactly the moment it happens.
Why do airspace infringements happen despite moving maps?
The AOPA Safety Letter “Airspace Infringement” cites, among other suspected reasons, inadequate navigational skills, route changes due to bad weather without regard for airspace structure, lack of understanding for obtaining clearance, inexperience, and explicitly the exclusive reliance on GPS.
This last point is not coincidentally at the forefront of an article about airspace warnings. The Safety Letter states that one should not simply continue flying and rely solely on the GPS and moving map display if a planned waypoint cannot be found. As a VFR pilot, you determine your position by visual reference. The app is the second opinion, not the first.
In addition, three effects interact in the cockpit:
- The boundary is invisible. Outside, nothing marks a control zone. What you see is landscape.
- The vertical error is the quieter one. Laterally, you notice a deviation by towns and rivers. Vertically, you don't.
- Re-planning consumes attention. Precisely when weather forces you to change course, the airspace structure is the part that falls by the wayside in your mind.
- Controlled does not mean requiring clearance. Airspace E is controlled airspace and usually begins at 2,500 ft above ground in Germany; there, as a VFR pilot, you can fly without clearance. You need clearance in C and D. Anyone who equates both terms is looking for the warning in the wrong place.
How much distance should you maintain from the airspace boundary?
Maintain distance instead of pushing the boundary. The British Take-2 Initiative recommends as a rule of thumb 2 NM laterally and 200 ft vertically distance from controlled airspace. Take 2 comes from the British Airspace & Safety Initiative, a joint body of air traffic control, authorities, military, and GA associations. It is a recommendation, not a regulation, and formally aimed at Great Britain. As a rule of thumb for the mind, it applies everywhere.
For Germany, the DFS, according to the same AOPA Safety Letter, recommends a vertical distance of 200 to 500 ftwhen flying below airspace C, especially in the approach areas of large commercial airports and particularly in Frankfurt (EDDF). The reason is twofold, and the first part concerns yourself. Wake turbulence from large commercial aircraft can sink up to 1,000 ft, according to the DFS, and poses a particular danger to small, light aircraft; the danger exists even if you don't see the commercial aircraft. The second part concerns others: a VFR aircraft flying too close below, if it transmits a transponder with altitude reporting, can trigger an avoidance recommendation in the TCAS of an approaching commercial aircraft and abort its approach. The same DFS recommendation therefore also applies upwards: do not push the upper limit of airspace E.
The practical point for the app setting follows directly from this:
| Warning at the boundary | Warning with Take-2 buffer | |
|---|---|---|
| Trigger | Boundary is intersected | 2 NM before, 200 ft below |
| Lead time at 100 kt | 0 seconds | approx. 72 seconds |
| Lead time in climb at 500 ft/min | 0 seconds | approx. 24 seconds |
| What you get | Observation | Time to act |
| Reaction possible | Course correction under time pressure | calm avoidance or request clearance |
If your app allows you to set a warning distance, that is the most important switch in the entire menu. If it is fixed, you must know what it is set to, otherwise you are planning against a number you don't know. If it is set to zero, the app warns you at the moment it has already happened.
How do you set up the airspace warning before takeoff?
As a quick guide, on the ground, before engine start:
- Check data status. Aeronautical data follows the 28-day AIRAC cycle. If the app doesn't show you what status it has loaded, you don't know.
- Load offline data. Get airspaces, map, and terrain for the route onto the device. A warning that waits for network reloading won't come at all in a dead zone.
- Set or look up buffer. Choose lateral and vertical warning distance so that you can act before the boundary, not at it. If the app doesn't allow this setting, check the documentation for the values it uses.
- Consciously choose altitude filter. More on this shortly, here lies the trap.
- Pull NOTAMs. Restricted areas and temporary closures do not follow the AIRAC cycle, but are in the NOTAM.
- Do a dry run once. Test the route through a known airspace and see if the warning appears and what it looks like. A warning you see for the first time in flight costs seconds you don't have.
- Altimeter and app do not measure the same thing. Airspace boundaries are defined against the altimeter, i.e., against QNH. An app that gets its altitude from GPS measures geometrically. Set the altimeter to the current QNH and take the altitude in the app as a second opinion, not as proof.
Why is the altitude filter the real trap?
An altitude filter hides airspaces that do not touch your set altitude. This cleans up the screen and is very pleasant in dense German airspace. However, it hides exactly what begins above your set altitude.
In practice, this means: If you set the filter to your cruising altitude and then climb, the lower limit you are currently climbing through disappears from your perception before you reach it.
The rule against it is simple. Set the filter to the highest altitude of your flight, not the current one. Anyone who uses the filter as a cleanup tool should review it after every altitude change.
The same applies to the altitude reference. The Safety Letter describes the case where a pilot believes to be numerically just below a boundary, but in reality is already in the airspace by 100 or 200 ft. In addition: airspace boundaries are defined against QNH, GPS provides a geometric altitude. These are two different quantities, and on cold days with low air pressure, they diverge by a three-digit foot amount. Anyone who pushes the lower limit to the last foot is pushing two numbers that do not measure the same thing.
When does the warning remain silent, even though there is airspace?
This question is the most honest you can ask an app. There are at least five cases:
- Time-activated areas. Many restricted areas are only valid at certain times or after activation. Whether an app treats such an area as currently active depends on the data it has about it.
- Short-term changes. Data loaded the day before will not know about this morning's NOTAM.
- GPS inaccuracy. Position and especially GPS altitude have a tolerance. A seemingly exact flight along the boundary can already be a flight within.
- No GPS altitude. If the GPS altitude fails, the vertical check lacks its input. You should know what an app does then, whether it remains silent or continues calculating with a substitute value, before it happens.
- Device off, screen dark, battery dead. Sounds trivial, but in practice, it fails more often than any data logic.
Therefore, the statement also made by the AOPA Safety Letter applies: Flight information service is no substitute for good flight preparation, and an app is certainly not. The responsibility for complying with the rules remains with the pilot.
What happens after an airspace infringement in Germany?
Unauthorized incursions into Class C and D airspaces must be reported by DFS to the Federal Supervisory Authority for Air Navigation Services (BAF); they are penalized as administrative offenses and are subject to fines. This is stated in the AOPA Safety Letter under the air traffic control advisories. According to the same source, an incursion into a restricted area can even lead to criminal proceedings. I deliberately do not mention specific fine amounts here, as this depends on the individual case and I do not have a reliable source for it.
The reporting itself is not an exception, but a system. The reporting system for safety-related occurrences of the BAF is based on EU Regulation 376/2014 and Implementing Regulation 2015/1018; BAF and the Federal Aviation Office are the competent authorities in Germany. Reports can also be made voluntarily and anonymously.
And if you notice your own mistake: Leave the airspace by the shortest route and call flight information service. Anyone who "calls in" at the first doubt usually defuses the situation.
How it works in EuroPilot Connect
So you know what I'm talking about, here's an honest walkthrough of the app itself.
- Airspace proximity warning. Alerts before controlled or restricted airspace and states the estimated time until the boundary crossing. The thresholds are adjustable, separately for obstacles, airspace, and terrain, each laterally in NM and vertically in feet. For airspace, they are set by default to 2 NM ahead and 200 ft vertically, exactly at the Take-2 values. Changes take effect immediately, without restarting.
- Airspace display. CTR, TMA/CTA, FIR/UIR, restricted, prohibited, and danger areas, TMZ, RMZ, gliding areas, and ATZ with classification, upper and lower limits, and colored filling. An altitude filter reduces the display to the selected altitude.
- 3D airspace and cross-section. Airspaces as volumes with ceiling and floor, tappable for details, plus a vertical route cross-section with terrain and airspace layers. When approaching Innsbruck (LOWI), you can see that the control zone, as Class D, extends from the ground to 7,000 ft MSL and completely fills the Inn Valley at this altitude. There is no 'below' here, and a spatial representation shows this more clearly than a line on a flat map.
- Airspace avoidance in planning. The route optimizer detects controlled and restricted airspace along the route and, by default, routes around it, taking into account activation times so that inactive areas are not unnecessarily circumnavigated.
- NOTAM on the map. NOTAM appear in geographical context along the route; they are collected server-side so that the app does not have to retrieve them from external services during the flight.
- Offline country packages. A tap on the country downloads map, terrain, airfields, airspaces, navaids, runways, reporting points, traffic patterns, and airfield charts to the device.
- AIRAC update. Aeronautical data follows the 28-day cycle and updates from the server with a new cycle, without an app update.
What I do not promise you: that this will prevent an airspace infringement. That depends on who looks, when they look, and how much buffer they allowed themselves beforehand. The app can show you the boundary early enough. It does not replace looking outside and making a radio call.
The app is natively built for iOS and has been in the App Store since August 5, 2026, click here to download; an Android version is under development and not yet usable today. The license costs 99 Euros per year for up to three devices, is concluded on the website, and the first 30 days are free.
Frequently Asked Questions
What is an airspace warning in a flight app? An airspace warning reports that your current course is approaching controlled or restricted airspace. The app calculates your GPS position, altitude, and ground track against the stored airspace geometries. Good implementations also state the estimated remaining time to the boundary.
How much distance should I maintain from an airspace boundary? The British Take-2 recommendation suggests 2 NM laterally and 200 ft vertically as a rule of thumb; it is Airmanship guidance, not a regulation. For flying below Class C airspace in Germany, the DFS recommends, according to the AOPA Safety Letter, 200 to 500 ft vertical distance, especially in the approach areas of large commercial airports.
Does an app prevent airspace infringements? No, it can only make them less likely. The AOPA Safety Letter even names exclusive reliance on GPS as one of the causes of airspace infringements. The responsibility for complying with the rules remains with the pilot.
Why doesn't my app display an airspace? The most obvious reason is an altitude filter set to the current rather than the highest planned flight altitude. Other reasons include outdated data, a missing NOTAM, or an area that is only temporarily active.
Does the airspace warning work without internet? Only to the extent that the airspace data was previously loaded onto the device. The geometry is available offline, NOTAMs and other live data show the status of the last retrieval in a radio dead zone.
What happens if I accidentally fly into Class C airspace? Leave the airspace by the shortest route and establish radio contact. Unauthorized incursions into Class C and D airspace are reported by the DFS to the Federal Supervisory Authority for Air Navigation Services; they are punished as a regulatory offense. According to the AOPA Safety Letter, an infringement of a flight restriction area can result in criminal proceedings.
How often do I need to update the airspace data? Aeronautical data follows the 28-day AIRAC cycle. NOTAMs and weather must be obtained fresh before each flight, as they change continuously and do not follow the AIRAC rhythm.
Conclusion
An airspace warning is not a safety net, it's a clock. It tells you how much time you have left. Whether that time is enough is decided on the ground, when you set the buffer, apply the altitude filter to your flight's highest altitude, and get the latest data onto your device.
The most honest sentence on the subject is in a pilot's own paper, not an app brochure: Do not rely unreservedly on satellite-based navigation displays. A good app does not make this sentence superfluous. It just gives you enough lead time so you don't need it.
How the map should be oriented in flight is explained in Moving Map in the Cockpit; what must be stored offline on the device, in the Offline Flight Navigation. The broader overview of the toolchain is provided by the flight navigation apps.