51
edits
Route manager: Difference between revisions
Jump to navigation
Jump to search
no edit summary
No edit summary |
No edit summary |
||
| Line 40: | Line 40: | ||
Route Manager is so simple to use that a player can simply input an airport code (e.g. KSFO) and select "true heading" under the autopilot heading control, and end up at the airport. Doing so will NOT line the pilot up with the runway, and will simply fly the plane over the airport. However, every waypoint name is unique; a player could be on the other side of the world, 5,000 miles away, and Route Manager would still lock onto the desired airport. | Route Manager is so simple to use that a player can simply input an airport code (e.g. KSFO) and select "true heading" under the autopilot heading control, and end up at the airport. Doing so will NOT line the pilot up with the runway, and will simply fly the plane over the airport. However, every waypoint name is unique; a player could be on the other side of the world, 5,000 miles away, and Route Manager would still lock onto the desired airport. | ||
Those who wish to end up lined with the runway must considerably more work. | Those who wish to end up lined with the runway must considerably more work. | ||
They must find out a waypoint that is directly in front of a runway, and then find out the runway's localizer. Since a localizer will not extend more than 20 miles, it is imperative to reach the waypoint first. When the player inputs the localizer frequency into their NAV1, it will direct them to the runway. For example, a waypoint near 28R of KSFO is | They must find out a waypoint that is directly in front of a runway, and then find out the runway's localizer. Since a localizer will not extend more than 20 miles, it is imperative to reach the waypoint first. When the player inputs the localizer frequency into their NAV1, it will direct them to the runway. For example, a waypoint near and in front of 28R of KSFO is AXMUL (see the chart HERE[http://204.108.4.16/d-tpp/0912/00375IL28R.PDF]). On the chart, it appears as "AXMUL INT", which stands for AXMUL intercept. A player is "intercepting" the runway course when they reach AXMUL. When a player reached AXMUL via Route Manager, they would follow the NAV1 Localizer. In this case, 28R's frequency is 111.7, as seen on the chart above. AXMUL is not far enough from 28R to keep turning. It's the closest waypoint to 28R, so you may want to use the waypoint before it. In this case, one of the waypoints before AXMUL is CEDES INT, or CEDES. A player can input CEDES into Route Manager, and then AXMUL, so they would reach AXMUL from CEDES. The course from CEDES to AXMUL, as seen on the chart, is straight to the runway, so a player would reach AXMUL lined up well. | ||
In essence, a player can follow route manager until within range of navaids- first the general airport frequency (KSFO, its 115.8), and then the localizer. | In essence, a player can follow route manager until within range of navaids- first the general airport frequency (KSFO, its 115.8), and then the localizer. | ||
Remember, the most effective waypoints are those that are on course for the runway. Any code with a triangle next to it or that says "INT", or is attached to an approach course is probably a runway. Check your waypoints before you fly, though! Go to mpmap01.flightgear.org, click on the nav section, and input the waypoint you want to check | |||
==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. | ||