Route manager: Difference between revisions

Jump to navigation Jump to search

Route manager (view source)

Revision as of 11:14, 14 March 2010

1,589 bytes removed ,  14 March 2010
no edit summary
No edit summary
Line 52: Line 52:


In particular, the GPS drives some properties of the generic autopilot, so 'true heading hold' mode can be used to fly the route manager route (or any other GPS course).
In particular, the GPS drives some properties of the generic autopilot, so 'true heading hold' mode can be used to fly the route manager route (or any other GPS course).
The default [[HUD]] (activated by pressing 'h') shows information about the active waypoint and leg, in the top-left corner. Notably, it includes the identifier, time and distance to the current waypoint, the magnetic bearing to the waypoint, and the current ground track, and finally the deviation (in nautical miles) from the leg course.


In aircraft with realistic navigation systems, or customised autopilots, the default behaviours above may not work; hopefully the aircraft author has provided alternative methods, such as panel instruments, to control the interaction with that aircraft's autopilot and panel.
In aircraft with realistic navigation systems, or customised autopilots, the default behaviours above may not work; hopefully the aircraft author has provided alternative methods, such as panel instruments, to control the interaction with that aircraft's autopilot and panel.


==Finding an Airport==
===Lining up with Runways===
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.
The route-manager only provides guidance to a particular location - to arrive on a particular heading, such as lined up with a runway or ILS localizer, it is necessary to use multiple waypoints. Virtually all ILS approaches define multiple fixes that can be used for this purpose, usually including altitude restrictions. For example, for the [http://flightaware.com/resources/airport/KPHX/IAP/ILS+OR+LOC+RWY+08 KPHX 08 approach], waypoints ALLIS, SARTE, HIKID, ILIKE, JAMIL and WAZUP are defined, extending 20nm from the threshold. Typically you enter the initial approach fix (IAF), ALLIS in this example, and as many of the intermediate waypoints as necessary, depending on required descent profile. It is helpful to include the glidepath capture waypoint (WAZUP), to provide an easy altitude reference and cross-check that your ILS receiver is working.
==Lining up with Runways==
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 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.
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 waypoint- basically, any mispelled name, like NATHN, WAKER, etc. and in all caps. 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
 
You can use airnav.com to find charts- input the airport code into airports, then scroll down to the bottom to ILS approaches, and click on the runway you want.
I know a lot of people want to go to KLAX, so I've saved you the trouble of getting the chart:
[http://204.108.4.16/d-tpp/0912/00237IL6L.PDF]
So the waypoints in this case could be anything on the chart.
The 3 ones I use are: (input these into route manager, in order):
WAKER,
NATHN,
KOYEV
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.
Zakalawe
580

edits

Retrieved from "https://wiki.flightgear.org/Special:MobileDiff/19988"

Navigation menu