51
edits
Route manager: Difference between revisions
Jump to navigation
Jump to search
→Lining up with Runways
| Line 49: | Line 49: | ||
[http://204.108.4.16/d-tpp/0912/00237IL6L.PDF] | [http://204.108.4.16/d-tpp/0912/00237IL6L.PDF] | ||
So the waypoints in this case could be anything on the chart. | So the waypoints in this case could be anything on the chart. | ||
The ones I use are: (input these into route manager, in order): | The 3 ones I use are: (input these into route manager, in order): | ||
WAKER, | |||
NATHN, | |||
KOYEV | |||
and then follow the localizer, 108.5 | and then follow the localizer, 108.5 | ||
==Properties== | ==Properties== | ||
When a route is active, the route-manage provides various pieces of information based upon current aircraft position / speed, and the route progress. These values would be calculated by the navigation computer in a real system, but are handled by route-manage in FG for convenience. Values logged include the takeoff time, estimated time enroute (ETE), distance remaining enroute, and so on - browse the property tree to see what's available. | When a route is active, the route-manage provides various pieces of information based upon current aircraft position / speed, and the route progress. These values would be calculated by the navigation computer in a real system, but are handled by route-manage in FG for convenience. Values logged include the takeoff time, estimated time enroute (ETE), distance remaining enroute, and so on - browse the property tree to see what's available. | ||