Skip to content
View in the app

A better way to browse. Learn more.

The AVSIM Community

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

LNM reports airway altitude error incorrectly

Featured Replies

Hi

A very small bug in the scheme of things: I created a flight plan in Simbrief from GCLP to EGGW, cruise altitude FL320. Part of the route is via DIKRO UM185 ADLOG M185 TELTU. Note the step-down to M185 at ADLOG- this airway has a max. altitude restriction of 24,500 ft. 

LNM shows a flight plan error at DESNA, the next wp on (U)M185 after ADLOG because the cruise altitude is 32000, however LNM *also* knows that my altitude at that point in the flight will be 21,750 ft, within the 24,500 restriction, because the aircraft (Zibo 737 800) will be past TOD at that point.

Just a small thing.

Can you post the whole flight plan? Menu "Flight Plan" -> "Copy flight plan route description to clipboard" or simply insert the contents of the LNMPLN into a reply here.

Note that LNM does not do step downs. It starts descent at TOD and adheres to procedure restrictions.

Alex

1 hour ago, HexWizard said:

LNM shows a flight plan error at DESNA, the next wp on (U)M185 after ADLOG because the cruise altitude is 32000, however LNM *also* knows that my altitude at that point in the flight will be 21,750 ft, within the 24,500 restriction, because the aircraft (Zibo 737 800) will be past TOD at that point.


IMHO, it seems LNM doesn't check limits against desc altitude (that is calculated from aircraft performance file) only against enroute altitude.
Try change flight plan to: "... DIKRO UM185 TELTU"" and it should be ok, as UM185 upper limit is FL430
 

 

1 hour ago, albar965 said:

Can you post the whole flight plan? Menu "Flight Plan" -> "Copy flight plan route description to clipboard" or simply insert the contents of the LNMPLN into a reply here.

Alex, try something similar:  "GCLP DIKRO UM185 ADLOG M185 TELTU EGGW", and at DESNA and TELTU are always reported** upper limit violations as they've got Fl245 upper limit.
Even when I've changed performance file such the aircraft TOD is 100NM before DESNA and at DESNA the aircraft is far under FL200 (lower limit for M185 at this point), LNM still reports upper limit violations FL245, but IMHO it should be reported lower limit violation as calculated aircraft's altitude in descent is at 7000' or below there (calculations from changed perf file) - I've such prepared perf parameters to be below lower limit at DESNA, but still upper limit violation is reported under LNM.

Regards,
Piotr

**for flight plans enroute alts above FL245, for example FL320 as @HexWizard wrote

Edited by ppgas

Never give up ...  - here are details of the whip-round: https://zrzutka.pl/en/pewr2d  -> to help my younger son fights against Acute Lymphoblastic Leukemia (blood cancer).

2 hours ago, ppgas said:

Alex, try something similar:  "GCLP DIKRO UM185 ADLOG M185 TELTU EGGW", and at DESNA and TELTU are always reported** upper limit violations as they've got Fl245 upper limit.

I see. The airway restrictions are conflicting. This will not happen if you calculate the plan in LNM. Sorry, stepdown is not supported. This would be a nightmare to implement in the elevation profile.

image.png

Alex

Edited by albar965

9 minutes ago, albar965 said:

I see. The airway restrictions are conflicting. This will not happen if you calculate the plan in LNM. Sorry, stepdown is not supported. This would be a nightmare to implement in the elevation profile.


That's why I personally use LNM to create flight plans 😄
BTW I don't like use SIMBRIEF as for me it's too many automatic calculations there, that I cant control.

Regards,
Piotr

Never give up ...  - here are details of the whip-round: https://zrzutka.pl/en/pewr2d  -> to help my younger son fights against Acute Lymphoblastic Leukemia (blood cancer).

  • Author

Thanks for all the replies. No worries if it's not feasible to fix!

Archived

This topic is now archived and is closed to further replies.

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.