# OFP wrong MSA **URL:** \ **Category:** Dispatch for MSFS\ **Created:** [February 28, 2026, 9:44am UTC](https://forum.navigraph.com/t/ofp-wrong-msa/22775 "2026-02-28T09:44:28Z")\ **Posts on this page:** 8\ **Page:** 1
**Author:** ![akenan8](https://avatars.discourse-cdn.com/v4/letter/a/87869e/32.png) [@akenan8](https://forum.navigraph.com/u/akenan8)\ **Post date:** [February 28, 2026, 9:44am UTC](https://forum.navigraph.com/t/ofp-wrong-msa/22775/1 "2026-02-28T09:44:28Z")
Hello. Noticed wrong MSA is indicated in OFPs. In this example KUMOM 131 vs 150, NIPEL 089 vs 109. Both are lower that the grid MORA. ![image](https://europe1.discourse-cdn.com/flex013/uploads/navigraph1/original/3X/3/1/31442b9d7a3d3cdb6cb3b97a914756ee36dc4cd1.png) ![image](https://europe1.discourse-cdn.com/flex013/uploads/navigraph1/original/3X/6/e/6e4d1f2258d1e251897fbda1acba184747ed56bc.png) ---
**Author:** ![Rodeo314](https://dub1.discourse-cdn.com/flex013/user_avatar/forum.navigraph.com/rodeo314/32/103_2.png) [@Rodeo314](https://forum.navigraph.com/u/Rodeo314)\ **Post date:** [February 28, 2026, 10:26am UTC](https://forum.navigraph.com/t/ofp-wrong-msa/22775/2 "2026-02-28T10:26:47Z")
If I am not mistaken, those figures in the OFP are meant to be the airway’s MOCA, not the area’s MSA. Regards, Tim ---
**Author:** ![akenan8](https://avatars.discourse-cdn.com/v4/letter/a/87869e/32.png) [@akenan8](https://forum.navigraph.com/u/akenan8)\ **Post date:** [February 28, 2026, 10:33am UTC](https://forum.navigraph.com/t/ofp-wrong-msa/22775/3 "2026-02-28T10:33:23Z")
There is no airway, its DCT ---
**Author:** ![Rodeo314](https://dub1.discourse-cdn.com/flex013/user_avatar/forum.navigraph.com/rodeo314/32/103_2.png) [@Rodeo314](https://forum.navigraph.com/u/Rodeo314)\ **Post date:** [February 28, 2026, 10:41am UTC](https://forum.navigraph.com/t/ofp-wrong-msa/22775/4 "2026-02-28T10:41:44Z")
Oh, duh 😆 My bad, sorry. Regards, Tim ---
**Author:** ![akenan8](https://avatars.discourse-cdn.com/v4/letter/a/87869e/32.png) [@akenan8](https://forum.navigraph.com/u/akenan8)\ **Post date:** [February 28, 2026, 12:10pm UTC](https://forum.navigraph.com/t/ofp-wrong-msa/22775/5 "2026-02-28T12:10:05Z")
In any case the more restrictive altitude is accounted as minimum safety altitude. ---
**Author:** ![jsokoloff](https://dub1.discourse-cdn.com/flex013/user_avatar/forum.navigraph.com/jsokoloff/32/5259_2.png) [@jsokoloff](https://forum.navigraph.com/u/jsokoloff)\ **Post date:** [February 28, 2026, 4:35pm UTC](https://forum.navigraph.com/t/ofp-wrong-msa/22775/6 "2026-02-28T16:35:44Z")
I will send to our team. ---
**Author:** ![SimBrief](https://dub1.discourse-cdn.com/flex013/user_avatar/forum.navigraph.com/simbrief/32/4850_2.png) [@SimBrief](https://forum.navigraph.com/u/SimBrief)\ **Post date:** [February 28, 2026, 8:04pm UTC](https://forum.navigraph.com/t/ofp-wrong-msa/22775/7 "2026-02-28T20:04:25Z")
Hi, the altitudes in the navlog are not grid MORAs. They are the minimum safe altitude along the planned route (within 5 nm either side of the track between the current and next waypoint). It’s normal for them not to match the grid MORA, since the terrain responsible for the grid MORA in a given sector is often not directly beneath your route. Almost all real-world OFPs display the MORA this way, so we have simply done the same. For the grid MORA and/or airway MOCA/MEA, you can continue to reference these in the Charts app. And you definitely should, especially if you are deviating from the planned route for any reason. Best regards, ---
**Author:** ![system](https://europe1.discourse-cdn.com/flex013/uploads/navigraph1/original/1X/4cc83e90d70ab312b1bd2d7527bddad309607265.png) [@system](https://forum.navigraph.com/u/system)\ **Post date:** [March 4, 2026, 1:46pm UTC](https://forum.navigraph.com/t/ofp-wrong-msa/22775/8 "2026-03-04T13:46:24Z")
This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.