john9002

OK, I think I've solved it. If, in a sort hop for example, you set a cruise altitude higher than can be attained, LittleNavMap sets all items in the Flight Plan Elevation Profile to the cruise altitude. This includes departure and arrival airports (LGKK and EGBB at 25,000 ft!) and all intermediate waypoints nav aids etc at the cruise altitude. This seems odd behaviour.

I have some screenshots of the proble, but don't see a way to upload them here.

Tell me what informatin would help. The problem is that the when I use the flight plan in X-plane (Toliss A320), the FMA shows 'TOC Reached' all the time, even directly after takeoff. The NAV ignores the flight profileand climbs directly to the cruising altitude. All waypoints are circled in orange (unattainable).

When I create a flight plan everything in the Flight Plan Elevation Profile is at cruise altitude (including departure and destination runways. Obviously these flight plans don't work well in X-Plane