# Free Route Airspace (FRA) support

**URL:** <https://forum.navigraph.com/t/free-route-airspace-fra-support/24276>\
**Category:** Wishlist\
**Created:** [September 11, 2026, 11:57am UTC](https://forum.navigraph.com/t/free-route-airspace-fra-support/24276 "2026-09-11T11:57:17Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![Nahcep](https://avatars.discourse-cdn.com/v4/letter/n/f0a364/32.png) [@Nahcep](https://forum.navigraph.com/u/Nahcep)\
**Post date:** [September 11, 2026, 11:57am UTC](https://forum.navigraph.com/t/free-route-airspace-fra-support/24276/1 "2026-09-11T11:57:17Z")

</div>

tl;dr Please include at the least the waypoint relevance for FRAs ( **E** ntry/e **X** it, **I** ntermediate, **D** ep/ **A** rr), with possibly the airspace exclusions in the future; this will aid in both manual and Simbrief planning in the areas included

One of the more and more important parts of flying over Europe (though not only) are the Free Route Airspaces, in which the planes crossing them are excluded from following required lateral paths, instead using direct-to legs. However, this does not mean no restrictions exist: most crucially, there are certain waypoints which can be used as intermediates, or through which the FRA can be entered/exited. See example:

 ![image](https://europe1.discourse-cdn.com/flex013/uploads/navigraph1/original/3X/8/0/80fc76280d0e665712a2671703f64eb3ba3ae086.jpeg)

([ENR\_6\_1-5.pdf](https://forum.navigraph.com/uploads/short-url/k5YmNelldl62IPdDW3hdnlCko75.pdf) (3.3 MB) for full version)

Note that, for instance, the PESEL waypoint in the southwest corner can only be used one way, as an e(X)it from Poland into Germany. Note also that many existing waypoints over Poland cannot be used as (I)intermediates.

This functionality is completely missing from Navigraph as I’m writing this, making planning in FRAs difficult, if not impossible. These definitions are nowhere to be seen in the data, both in the Charts app and the navdata (as accessed via LittleNavMap):

 ![image](https://europe1.discourse-cdn.com/flex013/uploads/navigraph1/original/3X/0/7/07d9d3faa7cce32f34065daaf0f3d03f397a398c.png)

 ![image](https://europe1.discourse-cdn.com/flex013/uploads/navigraph1/original/3X/5/2/52bf87d456c018298e85400db4be863c538eddcc.png)

This information is accessible only through the ENR part of the AIPs: 2.2 for definitions, 4.4 for waypoint relevance, somewhere 6 as a chart/series of charts. These are not available through the Charts app, but other data from them does exist - after all, we see airspaces, not just FIRs but also CTAs, RTAs and all other acronyms, which are defined in the ENR parts.

On that note, there is another element of FRAs that’s a bit more complex: the 3D limitations. As you can see in the chart up top, the airspace itself begins at FL095 and nominally goes up to FL660; however, various terminal control areas are excluded in their figures, meaning that the FRA scheme cannot be used there. These excluded airspaces are already in the data, they simply aren’t substracted from the FRA (which are presented as an uniform class C airspace).

This change wouldn’t just aid manual planning; it would also be a boon for Simbrief, which still does not do great with DCT segments. It also may improve the “Real World” functionality, which does still fixate on airways when not necessary:

 ![image](https://europe1.discourse-cdn.com/flex013/uploads/navigraph1/original/3X/b/c/bcc40603ab7d403f6e998108219ab8477653c54d.jpeg)

(the track is offset compared to how it’s shown on FR24, but you get the idea)

---

<div class="post-metadata">

**Author:** ![GordonNG](https://dub1.discourse-cdn.com/flex013/user_avatar/forum.navigraph.com/gordonng/32/27797_2.png) [@GordonNG](https://forum.navigraph.com/u/GordonNG)\
**Post date:** [September 14, 2026, 1:55pm UTC](https://forum.navigraph.com/t/free-route-airspace-fra-support/24276/2 "2026-09-14T13:55:35Z")

</div>

Hello,

Firstly, thank you very much for this context. It is one of the more well researched requests we’ve had. The fact that you verified the data yourself and backed it up with AIP references and proven examples is the kind of input that makes decision making very simple. Its very much so appreciated and we would love more feedback like this.

Our GIS are aware of this and are very interested in implement and are checking this request.

Of course, there is no timeline, however we will definitely want to work with this information.

Thank you very much again!

---

<div class="post-metadata">

**Author:** ![Nahcep](https://avatars.discourse-cdn.com/v4/letter/n/f0a364/32.png) [@Nahcep](https://forum.navigraph.com/u/Nahcep)\
**Post date:** [September 14, 2026, 7:25pm UTC](https://forum.navigraph.com/t/free-route-airspace-fra-support/24276/3 "2026-09-14T19:25:33Z")

</div>

Hi, thanks a lot for the response; since it’s confirmed to be under consideration, I’ve marked this as a solution.

---

<div class="post-metadata">

**Author:** ![system](https://europe1.discourse-cdn.com/flex013/uploads/navigraph1/original/1X/4cc83e90d70ab312b1bd2d7527bddad309607265.png) [@system](https://forum.navigraph.com/u/system)\
**Post date:** [September 16, 2026, 7:26pm UTC](https://forum.navigraph.com/t/free-route-airspace-fra-support/24276/4 "2026-09-16T19:26:24Z")

</div>

This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.
