You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The layout of the flight plan, when created, is confusing to many / most, see "MoveUp.jpg", i.e. same above flight plan will display SNA(Base), next row: 0nm 00:02 191 deg. and below that we have: >LGB(Base), next row: 17nm, --:-- 289 which is the actual distance from SNA to LGB. Most people get confused thinking that there is something wrong, being familiar with the typical convention have having Start, Dist, Hdg, Next Way point. I know what your original thinking was, to get rwy heading? and have no real problem with it but many people are confused by it. They think they have to fly that Hdg to the next waypoint. A solution may be to list / display the 0nm 00:02 191 in parenthesis, or in the same row as SNA, and have the 17nm, --:-- 289 in the next line. Basically move the Dist. Time, Hdg up one row, above the next waypoint / destination. See "MoveUp.jpg"
The text was updated successfully, but these errors were encountered:
The layout of the flight plan, when created, is confusing to many / most, see "MoveUp.jpg", i.e. same above flight plan will display SNA(Base), next row: 0nm 00:02 191 deg. and below that we have: >LGB(Base), next row: 17nm, --:-- 289 which is the actual distance from SNA to LGB. Most people get confused thinking that there is something wrong, being familiar with the typical convention have having Start, Dist, Hdg, Next Way point. I know what your original thinking was, to get rwy heading? and have no real problem with it but many people are confused by it. They think they have to fly that Hdg to the next waypoint. A solution may be to list / display the 0nm 00:02 191 in parenthesis, or in the same row as SNA, and have the 17nm, --:-- 289 in the next line. Basically move the Dist. Time, Hdg up one row, above the next waypoint / destination. See "MoveUp.jpg"
The text was updated successfully, but these errors were encountered: