There is no way this can be garanteed. But AIR³ provides solutions to reach that goal. Look at this video regarding AIRSPACE management
Airspaces information are usually provided to the instrument through an Openair file. The AIRSPACE is continuously evolving through updates of the AIP (Aeronautical Information Publication). This means that Openair files should be regularly updated based on these updates.
In an Openair file, there are prohibited zones 7 days a week, H24, but there are also a certain number of temporary prohibited zones that are announced by Notam (notification to air man). Unfortunatelly, a Notam regarding the same zone can be written differently depending on the person that is producing it. This means that a robot that has the objective to decode notam may not be always 100% correct.
There are different ways to let XCTrack use an Openair file: XCtrack/Airspaces/Web or Custom/Air³ Manager.
Openair files should ideally be produced based on a daily analysis of the Notam in order to humanly determine which airspaces are activated or not.
A group of pilots focusing on a given region should organise themselves to validate Openair files corresponding to their region and publish them on a Google Drive folder. Sharing that folder with the pilots that are interested, AIR³ manager can automatically download the latest Openair file published.
Air³ Manager will copy the airspace files in OpenAir format to ‘’XCTrack/Airspaces’’ directory as “Most_recent_OA.txt” and make a second copy in the directory. By choosing that individual airspace file”Most_recent_OA.txt” once for all, Air³ will automatically use the latest Openair file published on that shared folder without any difficuty.
XCTrack can use airspaces from http://airspace.xcontest.org automatically.
Choose countries in Preferences -> Airspaces -> Web Tap ‘’Refresh’’
Airspace activations are automatically checked upon XCTrack restart
Airspaces are computed automatically through a robot.
There are 2 types of airspaces in XCTrack that are relevant:
Restricted – red. You are supposed to evade the airspace, is shown in red and it appears in the proximity widget.
Warning – orange. This airspace appears only on the map and does not appear in the proximity widget. In custom OpenAir files this corresponds to the class Q airspace.