4
edits
Route manager: Difference between revisions
Jump to navigation
Jump to search
Added "Flying Approaches" section & tutorial
m (+cat: Autoflight, with cat sort) |
(Added "Flying Approaches" section & tutorial) |
||
| Line 50: | Line 50: | ||
=== SID and STAR === | === SID and STAR === | ||
As of FlightGear 2.4.0, the route manager has basic [[SID]]/[[STAR]] support. Download the '''Level-D 767''' formatted files from http://www.navdata.at, then save it under <tt>[[$FG_SCENERY]]/Airports/I/C/A/ICAO.procedures.xml</tt> (use the correct ICAO codes!). Next time you start FlightGear, you can load them through the route manager interface. | As of FlightGear 2.4.0, the route manager has basic [[SID]]/[[STAR]] support. Download the '''Level-D 767''' formatted files from http://www.navdata.at, then save it under <tt>[[$FG_SCENERY]]/Airports/I/C/A/ICAO.procedures.xml</tt> (use the correct ICAO codes!). Next time you start FlightGear, you can load them through the route manager interface. | ||
=== Flying Approaches === | |||
The route manager can also be used to fly from airport to airport without using navaids or waypoints. The following is a step-by-step tutorial on how to plan a flight from KSFO-KLAX without using navaids or waypoints. | |||
In the route manager, you will see two rows at the top: departure and arrival. They are almost the same, except departure has SID and the arrival airport has STAR (see below, SID/STAR). | |||
1. In the departure airport row, fill in the ICAO of the airport you are departing from (KSFO) as well as the runway you are taking off from. (10R) If you are not familiar with the airport, choose your departure runway carefully, as your taxi time will depend on the distance of this runway. The SID dropdown can remain as it is. | |||
2. In the arrival airport row, fill in the ICAO of the airport you are arriving at (KLAX) as well as the runway you will be landing on. (06L) Again, if you are not familiar with this airport, choose your arrival runway carefully, as this may significantly extend flight time. Next, select "Default" in the approach dropdown box. STAR can remain as it is. | |||
3. There should now be a list of waypoints below the information fields. The first waypoint (outside of the airport) is a ways from the departure airport (in this example, 283.9 NM). However, the waypoints following that continue the approach, so they are only a few nautical miles away from the previous. The list should be populated with at least 4 waypoints, excluding the airports. When this is true, proceed to the next step. | |||
4. There is a row of buttons at the bottom of the route manager. Press the button that says "Activate". This will enable the route that you have created (in this case, KSFO-KLAX). However, we don't want to fly to the airport we're already at. We want to fly to the first waypoint, which should be APP-4. To do this, click on APP-4 and click the "Jump To" button at the bottom. APP-4 should now be highlighted in orange. This means that autopilot is ready to fly to that waypoint. | |||
5. Once you get above 500ft, after takeoff, enable autopilot. Click LNAV for lateral navigation to that first waypoint. Your plane will make a slight turn (in this case) towards Los Angeles. Altitude works separately, so you will have to set your own altitude and vertical speed. (If pressing the LNAV button only produces this error: "Captain, we forgot to program or activate the route manager!", you forgot to click the activate button! Repeat step 4 and 5, then proceed to step 6. You should pause the simulation while doing this.) | |||
6. Your planes will make all the turns for you to get on approach. Remember that you, the pilot, are responsible for altitude, which deserves a whole different tutorial in itself. | |||
== Activating a Route == | == Activating a Route == | ||