FlightGear wiki - User contributions [en]

Suggested Flights

2024-08-23T02:59:21Z

Circumn: /* The Paro Challenge */

[[FlightGear]] has accurate and realistic terrain. Here are some interesting places where you can do virtual sight seeing.

If you are starting with [[FGRun]] - the FlightGear launcher - you can enter the [[airport]] id and select the runway on the appropriate screen in the startup wizard.
If you are starting from the command line you can use the options: <tt>--airport=ABCD</tt> and <tt>--runway=12L</tt>.

*Remember to give a look at the [[Suggested Airports]] page, where you can find a comprehensive list of high quality airports in FlightGear.
*If you enjoy these flights, please consider recording a flight and posting a link to it at the [[Suggested Prerecorded Flights]] page.

'''Remove before flight!''' 

Before you start flying into one of the suggested flights, you should add both the terrain and the Objects to you FlightGear installation; This is well explained on the [[Howto: Install scenery|installing scenery]] page.

p.s. charts are generated using FlightGear data only.

This page includes the flights described on the [http://www.flightgear.org/places.html main website] and the suggested flights from the newsletters. It can serve as an archive for suggested flights from future [[FlightGear Newsletter|newsletters]] or can give a flight if creativity is low that month.

{{TOC limit|3}}

=Cross Continentals or World Tour=

* [[Breitling DC-3 World Tour]][[File:Rect17.png|thumbnail]]
* [[Flying the Hump]]

=North America=
==Round Valley Airport==
[[Image:O09-002.png|thumb|left|right after take off]]
[[Image:O09-003.png|thumb|right|Valley]]
Covalis, CA. The airport is at the West edge of a 7 mile across valley.<BR/>
The predominant wind is a cross wind. Take-offs to the west (if they use the full runway length) often have to fly between 2 small hills and over another valley while gaining altitude. Most pilots take off to the west.<BR/>
It is a paved runway and quite long. It was designated as an emergency recovery field during the Cold War and was used twice that I know of by military aircraft that could not take off again from the field.
<div style="clear:both;"></div>

===Airports and coordinates===
{{Location map | USA
| caption = Latitude: 39.790156 Longitude: -123.266403
| lat_deg = 39.790156
| lon_deg = -123.266403
}}

* [[O09|O09 - Round valley]] - [http://assistenza.larasrl.net/brisa/fgfs/suggested_flights/O09.pdf chart]

required scenery tile: ftp://ftp.sunsite.org.uk/sites/ftp.flightgear.org/flightgear-ftp/Scenery/w120n40.tar.gz
<div style="clear:both;"></div>

===Suggested aircraft===
I have tried this trip using a p38, quite powerful airplane
* [[Lockheed-P38|P38]]
<div style="clear:both;"></div>

===FlightGear launching===
fgfs --airport=O09 --runway=28 --aircraft=p38
<div style="clear:both;"></div>

==Half Moon Bay==
[[Image:KHAF-001.png|thumb|left|right after take off]]
[[Image:KHAF-002.png|thumb|right|Bridge]]
Start at [[KHAF|Half Moon Bay]], Runway 30, with 32km visibility; Takeoff in the C172 and climb to 1000 feet, then continue north over the water, near the shoreline. Look out the right window frequently. Fly up the coast, overfly the Golden Gate Bridge, continue around the top of the peninsula past downtown SF, then fly on to [[KSFO]] for a landing. We now have lots to see.

If you cannot see the runway in the default 172, you must be flying too high or too slowly. You can start by practicing a bit with a good setup:

'''fgfs --offset-distance=1.5 --altitude=500 --vc=70'''

As soon as FlightGear starts, cut the power to 1500 rpm and drop two notches of flap. Maintain 70 kt. Now, pick your landing spot (a bit down the runway) and try to hold it in the same spot on your windshield. If your landing spot starts moving down, you are too high, and should cut another 100 rpm; if it starts moving up, you are too low, and should add another 100 rpm. Adjust the nose to keep your speed at 70 kt all the way down until you're right above the numbers, then cut power to idle, drop the last notch of flaps, flare, and land.
<div style="clear:both;"></div>

===Airports and coordinates===
[[Image:KHAF-003.png|thumb|left|surroundings]]
[[Image:World-KHAF.png|thumb|right|Latitude: 37.513333 Longitude: -122.501111]]
* [[KHAF|KHAF - Half Moon Bay]] - [http://assistenza.larasrl.net/brisa/fgfs/suggested_flights/KHAF.pdf chart]

no required scenery tile.
<div style="clear:both;"></div>

===Suggested aircraft===
[[Image:KSFO-001.png|thumb|left|Before landing]]
Use the default c172 airplane
* [[Cessna C172P]]
<div style="clear:both;"></div>

===FlightGear launching===
fgfs --airport=KHAF --runway=30 --visibility=32000 --aircraft=c172
<div style="clear:both;"></div>
===Author===
April 2006 [[User:Hellosimon|Hellosimon]], format and extended by [[User:Francescobrisa|Francescobrisa]]

==Hell's Canyon==
[[Image:25U-001.png|thumb|left|right after take off]]
[[Image:25U-004.png|thumb|right|Valley]]
Hell's Canyon, Imnaha, OR. This airport is located just west of "Hell's Canyon National Park" which has the Snake River running through it.<br/>
Supposedly it's a 5500 foot drop from the top of the canyon to the river.<BR/>
The airport is located on the brink of this canyon.

See the remarks on the airport page (click on the airport id) ... DOWNDRAFTS, SHEER DROP IN TERRAIN, LIVESTOCK, etc. Don't go here on your first solo x-country. :-)
<div style="clear:both;"></div>

===Airports and coordinates===
[[Image:25U-005.png|thumb|left|Landing]]
[[Image:World-25U.png|thumb|right|Latitude: 45.427861 Longitude: -116.693889]]
* [[25U|25U - Round valley]] - [http://assistenza.larasrl.net/brisa/fgfs/suggested_flights/25U.pdf chart]

required scenery tile: ftp://ftp.sunsite.org.uk/sites/ftp.flightgear.org/flightgear-ftp/Scenery/w120n40.tar.gz
<div style="clear:both;"></div>

===Suggested aircraft===
[[Image:25U-006.png|thumb|left|Landing 2]]
I have tried this trip using a pilatus PC-9M, powerful airplane
* [[PC-9M|PC-9M]]
<div style="clear:both;"></div>

===FlightGear launching===
fgfs --airport=25U --aircraft=PC-9M
<div style="clear:both;"></div>

==Crater Lake National Park Tour==
[[Image:64s-003.png|thumb|left|Approaching the lake]]
[[Image:64s-002.png|thumb|right|Direction 40 degrees]]
Prospect, OR.<br/>

Take off and fly at a heading of about 40 degrees until you cross the first distinct ridge in front of you. (several minutes of flight in the navion ... just climb as fast as you can, it will be a close squeek to get over :-)<br/>

Once you clear the ridge and can see beyond it, turn right and fly a heading of about 70 degrees. You should see two shallow peaks off in the distance. Head right between these -- they are the two sides of the crater. As you get closer the shape of the crater will come into view. There's a lake there in real life, hopefully it will be there in flight gear too before long.
<div style="clear:both;"></div>

===Airports and coordinates===
[[Image:64s-001.png|thumb|left|Leaving the 64S airfield]]
[[Image:World-64S.png|thumb|right|Latitude: 42.743183 Longitude: -122.488092]]
* [[64S|64S - Prospect State]] - [http://assistenza.larasrl.net/brisa/fgfs/suggested_flights/64S.pdf chart]

required scenery tile: ftp://ftp.sunsite.org.uk/sites/ftp.flightgear.org/flightgear-ftp/Scenery/w130n40.tgz
<div style="clear:both;"></div>

===Suggested aircraft===
[[Image:64s-004.png|thumb|left|Lake view 1]]
[[Image:64s-005.png|thumb|right|Lake view 2]]

* [[Ryan_Navion|Navion]]
<div style="clear:both;"></div>

===FlightGear launching===
fgfs --airport=64S --runway=02 --aircraft=navion
<div style="clear:both;"></div>

==Grand Canyon Tour==
[[Image:Grand_Canyon_Tour_4.jpg|700px|frameless|center]]
Being a special place, there are also special flight rules for VFR traffic around the Grand Canyon. There are multiple no-fly-zones set up and VFR traffic is only allowed to fly via the designated corridors. If you want to fly realistically, avoid these zones in FlightGear as well, following for example the [https://skyvector.com/?ll=36.18649251415492,-112.52223157994264&chart=230&zoom=5&fpl=%20KGCN%20VPGCF%20VPGCG%20VPGCD%20VPGCC%20VPGCA%203608N11252W%203609N11309W%201Z1%201G4%203AZ5 route shown here. (skyvector link)]

This flight takes you from KGCN, the Grand Canyon National Park airport, to 3AZ5, a small airfield called Hualapai located south of the Grand Canyon. Departing from KGCN, fly north-west bound to reach the canyon. From there, either follow the route shown on skyvector above, or fly visually through the canyon westbound towards 1Z1, Grand Canyon Bar Ten Airstrip. From there on, continue flying westward to 1G4. Called Grand Canyon West, 1G4 also marks about the western end of the canyon. To get to your destination 3AZ5, continue along the southern rim, flying eastward now. Shortly after leaving the breathtaking valley behind you, you will already reach your destination. Land and let your engine and your mind cool down from the special views :)

===Gallery===
<gallery>
Grand_Canyon_Tour_2.jpg
Grand_Canyon_Tour_3.jpg
Grand_Canyon_Tour_1.jpg
</gallery>

===Airports===
* KGCN - Grand Canyon National Park Airport - [https://www.aopa.org/destinations/airports/KGCN/details aopa.org]
* 1Z1 - Grand Canyon Bar Ten Airstrip - [https://www.airnav.com/airport/1Z1 airnav.com]
* 1G4 - Grand Canyon West - [https://www.airnav.com/airport/1G4 airnav.com]
* 3AZ5 - Hualapai - [https://www.airnav.com/airport/3AZ5 airnav.com]

===Suggested aircraft===
Most VFR aircraft with sufficiently big windows will serve the purpose, for example:
*[[Cessna C172P]]
*[[Optica]]
*[[Ryan_Navion]]
If you are more interested in flying helicopters, the [[Eurocopter EC130 B4]] with the Grand Canyon Helicopters livery might be for you.

===Links===
*[https://www.nps.gov/grca/learn/nature/upload/sfra.pdf Chart of the Grand Canyon special airspace, published by the National Park Service]
*[http://www.swaviator.com/html/issueJJ99/canyon.html An article about flying close to the Grand Canyon]
*[https://www.aopa.org/news-and-media/all-news/2017/april/flight-training-magazine/road-trip-grand-canyon AOPA Flight suggestion]

==Ranger Creek Airport==
[[File:21w-1.jpg|500px|center|Waiting for departure at Ranger Creek]]
Ranger Creek Airport is located in Greenwater, Washington, USA. Being wedged into the bottom of a steep canyon, you'll definitely need to be on your toes to get in and out of there. Switch on Advanced Weather and Live Data to experience what the winds can do to you in real life!
===Airports and coordinates===
* [[21W|21W - Ranger Creek]] - [http://www.airnav.com/airport/21W airnav.com]
===Gallery===
<gallery>
Ranger_Creek1.jpg|Departing between the mountains
Ranger_Creek_2.jpg|Looking back towards the airfield
Ranger_Creek_3.jpg|Downwind for approach back to Ranger Creek
</gallery>
===Suggested aircraft===
For this flight, the Piper PA-18 SuperCub is suggested, this is included in the [[Piper J3 Cub]] package

==Mount Rainier Tour==
[[Image:WA20-002.png|thumb|left|The mountain from far away]]
[[Image:WA20-006.png|thumb|right|external view]]
Eatonville, WA. Start out at Swanson Airport in Eatonville, WA. Take off and fly a heading of about 90 degrees. You will need to fly for 5-10 minutes before the mountain comes into view. Be patient if you don't see it right away, it will dwarf everything in it's vicinity.
<div style="clear:both;"></div>
===Airports and coordinates===
[[Image:World-WA20.png|thumb|right|Latitude: 46.87588502 Longitude: -122.25733500]]

* [[WA20|WA20 - Swanson]] - [http://assistenza.larasrl.net/brisa/fgfs/suggested_flights/WA20.pdf chart]

required scenery tile: ftp://ftp.sunsite.org.uk/sites/ftp.flightgear.org/flightgear-ftp/Scenery/w130n40.tgz
<div style="clear:both;"></div>

===Suggested aircraft===
[[Image:WA20-007.png|thumb|left|external near view]]
[[Image:WA20-009.png|thumb|right|external near view]]
* [[mosquito]]

<div style="clear:both;"></div>

===FlightGear launching===
fgfs --airport=WA20 --aircraft=mosquito
<div style="clear:both;"></div>

==Death Valley Tour==
[[Image:L06-001.png|thumb|left|in the air]]
[[Image:Furnace-creek.jpg|thumb|left|real life view of Furnace Creek Airfield]]
[[Image:L06-002.png|thumb|right|in the air]]
Furnace Creek, CA. This starts you right in the middle of Death Valley which runs north & south. If you head south about 15 miles you'll hit the lowest point in the USA, 282 feet (86 meters) below sea level.
<div style="clear:both;"></div>
===Airports and coordinates===
[[Image:World-L06.png|thumb|right|Latitude: 36.46451100 Longitude: -116.88139422]]
* [[L06|L06 - Furnace Creek]] - [http://assistenza.larasrl.net/brisa/fgfs/suggested_flights/L06.pdf chart]

required scenery tile: ftp://ftp.sunsite.org.uk/sites/ftp.flightgear.org/flightgear-ftp/Scenery/w120n30.tgz
<div style="clear:both;"></div>

===Suggested aircraft===
[[Image:L06-003.png|thumb|left|in the air]]
[[Image:L06-004.png|thumb|right|in the air]]
* [[rallye-MS893]]
<div style="clear:both;"></div>

===FlightGear launching===
fgfs --airport=L06 --aircraft=rallye-MS893
<div style="clear:both;"></div>

==Utah==
!!! Work in progress !!!<BR/>

Escalante Muni Airport, Escalante, UT. This airport is east and a bit north of Bryce Canyon National park. If you head mostly south and a bit east you'll eventually hit the Grand Canyon. It is sandwiched between the Dixie National forest to the north and the Grand Staircase-Escalante National Monument to the south. There should be interesting stuff to see no matter which direction you head.
<div style="clear:both;"></div>
===Airports and coordinates===
[[Image:World-1L7.png|thumb|right|Latitude: 37.75054400 Longitude: -111.57578300]]
* [[1L7|1L7 - Escalante Muni]] - [http://assistenza.larasrl.net/brisa/fgfs/suggested_flights/1L7.pdf chart]

required scenery tile: ftp://ftp.sunsite.org.uk/sites/ftp.flightgear.org/flightgear-ftp/Scenery/w120n30.tgz
<div style="clear:both;"></div>

===Suggested aircraft===

<div style="clear:both;"></div>

===FlightGear launching===
fgfs --airport=1L7 --aircraft=pa18
<div style="clear:both;"></div>

==Lake County Airport (CO)==
[[Image:KLXV-001.png|thumb|left|Adjust mixture !]]
[[Image:KLXV-002.png|thumb|right|The terrain will be covered by snow]]
Lake County Airport, Leadville, CO. This airport is at an elevation of 9927 making it a bit of a challenge to get into and out of with a standard C172.<BR/>
Make sure you lean out your engine before taking off and read up on density altitude before you try this one in real life.
<div style="clear:both;"></div>
===Airports and coordinates===
[[Image:KLXV-003.png|thumb|left|The airport]]
[[Image:World-KLXV.png|thumb|right|Latitude: 39.22812500 Longitude: -106.31835600]]
* [[KLXV|KLXV - Lake Co]] - [http://assistenza.larasrl.net/brisa/fgfs/suggested_flights/KLXV.pdf chart]

required scenery tile: ftp://ftp.sunsite.org.uk/sites/ftp.flightgear.org/flightgear-ftp/Scenery/w110n30.tgz
<div style="clear:both;"></div>

===Suggested aircraft===
[[Image:KLXV-004.png|thumb|left|I like this panorama]]
[[Image:KLXV-005.png|thumb|right|The nearby lake]]
* [[Cessna C172P]]

<div style="clear:both;"></div>

===FlightGear launching===
[[Image:KLXV-006.png|thumb|left|Landing...]]
fgfs --airport=KLXV --aircraft=c172p
<div style="clear:both;"></div>

==Caribbean - Saint Martin and St. Kitts==
[[Image:TNCM-003.png|thumb|left|just after the take off]]
[[Image:TNCM-004.png|thumb|right|some nearby island]]
Pilots of the Caribbeans is an informal FlightGear community of users who fly around the small Caribbean islands, many of which have custom scenery and improved landclass data. (For details see [[Pilots of the Caribbean]])<BR/>

[[TNCM|Princess Juliana International Airport (TNCM)]] at the isle of Saint Martin, is one of the most popular airports in FlightGear. In large part due to the custom objects and land cover. However, St. Marten is only one of several detailed airports in the region - and, while the approach for TNCM is one of the most memorable in the whole world, the land cover for St. Kitts and Nevis makes it a lovely place to fly.

British Airways, US Airways and American Airlines, among others, all fly into St. Kitts' [[TKPK|Robert L. Bradshaw International Airport (TKPK)]] in real life.

Take off from TKPK in a [[Piper_J3_Cub|Piper Cub]] and make a northward, clockwise circle of the island. Start your descent on the east side of the island, and focus on the small hill which separates the north from the south. Start hugging the coast near the beach and look to the west - as soon as the railroad heads to the southwest, you're about ready to turn for final. Make your right hand turn for final and taxi to the terminal.

If you want to fully explore this whole country, take off in a Beaver, which has a little more speed, and fly a figure eight. Take off from TKPK and circle the airport to the north like in the Cub. Then instead of landing, perform a touch-and-go and turn left over the boat terminal and make for the west coast of Nevis. Enjoy the beauty of the south coast of St. Kitts before circling Nevis. Over Nevis, you have several options - cut your flight short and land at [[TKPN]] on the island of Nevis, complete the "figure eight" by heading back to TKPK, or check your fuel and head east across the Caribbean to Antigua (which does not have custom land cover).<BR/>
<BR/>
Check out the [[Pilots of the Caribbean]] page, for further informations.
<div style="clear:both;"></div>
===Airports and coordinates===
[[Image:World-TNCM.png|thumb|right|Latitude: 18.040953 Longitude: -63.108900]]

* [[TNCM|TNCM - Princess Juliana International Airport]] - [http://assistenza.larasrl.net/brisa/fgfs/suggested_flights/TNCM.pdf chart]
* [[TKPK|TKPK - Robert L. Bradshaw International Airport]] - [http://assistenza.larasrl.net/brisa/fgfs/suggested_flights/TKPK.pdf chart]
* [[TKPN|TKPN - Vance Winkworth Amory Intl]] - [http://assistenza.larasrl.net/brisa/fgfs/suggested_flights/TKPN.pdf chart]
others interesting airports in the area:
* [[TFFF|TFFF - Le Lamentin]] - [http://assistenza.larasrl.net/brisa/fgfs/suggested_flights/TFFF.pdf chart]
* [[MDPP|MDPP - Gregorio Luperon Intl]] - [http://assistenza.larasrl.net/brisa/fgfs/suggested_flights/MDPP.pdf chart]
* [[TJSJ|TJSJ - Luis Munoz Marin Intl]] - [http://assistenza.larasrl.net/brisa/fgfs/suggested_flights/TJSJ.pdf chart]
* [[FMEE|FMEE - St Denis Gillot]] - [http://assistenza.larasrl.net/brisa/fgfs/suggested_flights/FMEE.pdf chart]
* [[TFFG|TFFG - Grand Case]] - [http://assistenza.larasrl.net/brisa/fgfs/suggested_flights/TFFG.pdf chart]

required scenery tile:
* ftp://ftp.sunsite.org.uk/sites/ftp.flightgear.org/flightgear-ftp/Scenery/w070n10.tgz
* ftp://ftp.sunsite.org.uk/sites/ftp.flightgear.org/flightgear-ftp/Scenery/w080n10.tgz
* ftp://ftp.sunsite.org.uk/sites/ftp.flightgear.org/flightgear-ftp/Scenery/w080n20.tgz
* ftp://ftp.sunsite.org.uk/sites/ftp.flightgear.org/flightgear-ftp/Scenery/w090n20.tgz
<div style="clear:both;"></div>

===Suggested aircraft===
[[Image:TNCM-005.png|thumb|left|amazing]]
[[Image:TNCM-006.png|thumb|right|landing]]
* [[Piper_J3_Cub|Piper Cub]]
<div style="clear:both;"></div>

===FlightGear launching===
fgfs --airport=TKPK --aircraft=Cub
<div style="clear:both;"></div>
===Author===
[[FlightGear Newsletter January 2011]] by [[User:Statto|Statto]], format and extended by [[User:Francescobrisa|Francescobrisa]].

==Friedman Memorial Airport (Idaho)==
[[Image:KSUN-001.png|thumb|left|take off]]
[[Image:KSUN-002.png|thumb|right|nearby]]
Friedman Memorial Airport, Hailey, Idaho. This airport is nestled in a valley surrounded by significant terrain. It's one that shows up quite often in accident investigations.
<div style="clear:both;"></div>
===Airports and coordinates===
[[Image:World-KSUN.png|thumb|right|Latitude: 43.51223900 Longitude: -114.30376100]]
* [[KSUN|KSUN - Friedman Mem]] - [http://assistenza.larasrl.net/brisa/fgfs/suggested_flights/KSUN.pdf chart]

required scenery tile: ftp://ftp.sunsite.org.uk/sites/ftp.flightgear.org/flightgear-ftp/Scenery/w120n40.tgz
<div style="clear:both;"></div>

===Suggested aircraft===
[[Image:KSUN-003.png|thumb|left|landing]]
[[Image:KSUN-004.png|thumb|right|landing]]
* [[FK9MK2]]
<div style="clear:both;"></div>

===FlightGear launching===
fgfs --airport=KSUN --aircraft=fk9mk2
<div style="clear:both;"></div>

== Wyoming - Grand Teton ==
Jackson Hole (KJAC) airport is located at around 6,400ft right next to the Teton range of mountains. The Tetons rise straight out of the plains, gaining over 5,000ft in 2 miles.

You will need the w120n40 scenery.

Tower frequency at KJAC is 118.07. Due to the high altitude, you will need to lean non-turbocharged piston aircraft before take-off. Don't forget that take-off distances will also be longer.

After take-off head to the North East. Grand Teton is the highest of the three peaks that rise straight from the flat-lands. Follow the line of mountains to the East, passing over Jenny Lake. After a couple of miles you will reach a huge lake. The large bulk of a mountain to the East is Mount Moran.

The Teton Mountain range is surprisingly thin - really just a string of mountains running SW-NE. Flying fast jets down the steep valleys is recommended.
* September 2006 by [[User:Stuart|Stuart]].

== Virginia Eastern Shore, Chesapeake Bay-Bridge Tunnel Sightseeing ==
[[Image:KTGI-001.png|thumb|left|before take off]]
[[Image:KTGI-002.png|thumb|right|right after take off]]

Take a short VFR trip from Tangier Island to view the famous Chesapeake Bay Bridge-Tunnel connecting Cape Charles to Cape Henry. Depart historic Tangier Island (KTGI) situated in the Chesapeake Bay and land at Norfolk International Airport (KORF), Norfolk, Virginia. The scenic character of the flight is enhanced by leaving the island at dusk. The flight is both scenic and challenging. Frequently, when flying with real weather, you will have a steady wind blowing across the bay. Starting out quiet Tangier and arriving at busy, glittering Norfolk International (KORF) gives the flight some contrast.

'''fgfs --airport=KTGI --runway=20 --timeofday=dusk'''

Before leaving Tangier: Set your altimeter to the prevailing barometric temperature. Set your communications radio to the Norfolk Intl. (KORF) ATIS frequency of 127.150 MHz to listen for weather reports in the destination area. Set your navigation radio to 112.20 MHz to pick up the Cape Charles (CCV) VOR. Set your heading bug to the runway heading, 200.

Takeoff straight, flying the runway heading. Climb to 2000ft and maintain.

Shortly, you should see the VOR assigned to NAV1 display receive a steady signal (the OFF flag will disappear). The DME should also settle down and display the distance to the Cape Charles VOR station. The flight to CCV will be about 26 nautical miles. As you fly, it will show your airspeed and time to arrival. It should take about ten minutes.

Turn the OBS knob until the VOR displays the TO flag and 190 degrees, the heading you should now turn to.

Fly south from Tangier, crossing an expanse of water, about ten miles until you see the Virginia Eastern Shore. You'll come upon the grass airstrip of Chance (VA89) a few minutes out from Tangier. Beyond are two flashing tower beacons. You may catch a glimpse of Weirwood/Kellam (W08) on the ocean shore, recognizable by two crossing dirt strips.

If you look carefully, you may see the little white building that is the Cape Charles VOR station. As you fly over VOR the flag will change from TO to FROM and the needle will deflect. Do not try to follow the needle. Wait until you are past the VOR. As you cross the VOR station, you should see a highway slanting across your path toward the south west. Turn to follow this highway. You'll come across a lone tower with beacon along the roadside. You'll see an access road stretching from the tower complex to the main road.

If the sky conditions permit, you may try your hand at wayfinding by following the road. If visiblity is poor, set the VOR to 180 degrees to parallel the road to the end of the peninsula. Or you can continue to fly outbound from the VOR on 190 by maintaining the same heading. The VOR needle should return to center with the FROM flag displaying. This will put you west of the bridge with a good view and the option to turn towards KORF near the initial approach fix. If you follow the highway you will need to overfly the airport, but if you stay on the 190 heading, you will be in a position to make a straight in landing.

As you fly down the peninsula you'll pass Cherrystone, Eagle's Nest, Scott and Bull Farm grass airstrips. Bull Farm is the last strip before the mouth of the Chesapeake. Just past Scott Farm you should see the first glimmer of the northern leg of the bridge. The grass strips can be very difficult to see.

As you reach the end of the peninsula, be careful to avoid the tower on Fisherman's Island at the north end of the north leg of the bridge (Note the bridge is not modeled by FlightGear...but I hope to work up one eventually). Next comes the north middle leg. Turn right a few degrees to follow the south middle leg. Watch as the deck plunges beneath the waves to allow ships to navigate the north and south channels.

As Cape Henry approaches, you'll see the Norfolk International airport to the right and the southern leg of the bridge touching the shore.

If you intend to land at KORF, you will want to start your approach soon. Otherwise, you may continue to follow the bridge to the end. Make the approach to KORF by contacting the tower for vectors. Or use the ILS.

This is a good flight to practice VOR flying on. It is a very straight flight path to the VOR requiring little adjustment and there are no other VORs in the area to confuse you.
*June 2006 by [[User:Sek|Sek]].

===Airports and coordinates===
[[Image:World-KTGI.png|thumb|right|Latitude: 37.8250835 Longitude: -75.9976665]]
* [[KTGI|KTGI - Tangier Island]] - [http://assistenza.larasrl.net/brisa/fgfs/suggested_flights/KTGI.pdf chart]
* [[KORF|KORF - Norfolk International]] - [http://assistenza.larasrl.net/brisa/fgfs/suggested_flights/KORF.pdf chart]

required scenery tile: ftp://ftp.sunsite.org.uk/sites/ftp.flightgear.org/flightgear-ftp/Scenery/w80n30.tgz

===Suggested aircraft===
[[Image:KTGI-003.png|thumb|left|surroundings]]
[[Image:KORF-001.png|thumb|right|landing to KORF]]
I have tried this trip using a Seneca II
* [[Piper PA34-200T Seneca II]]
<div style="clear:both;"></div>

===FlightGear launching===
fgfs --airport=KTGI --runway=20 --timeofday=dusk --aircraft=SenecaII
<div style="clear:both;"></div>

==Prince George to Calgary Springbank==
A beautiful flight is from Prince George (CYXS), to Calgary Springbank (CYBW). Route created by reed, which can be seen at {{forum link|t=9772|text=the forums}}
*Published in [[FlightGear Newsletter November 2010]] By [[User:Cael|Cael]].
==Ketchikan to Juneau==
It's cold where we will go so dress up warm and if we are lucky we might see whales during our flight. Don't fly too high to enjoy the amazing views, and there is a small challenge at the end. The runways we will use are long enough for bigger aircraft (7000+). Total length of the trip will be around 245 NM. So, hop in the cockpit of your favourite airliner.

Alaska, here we come! Enjoy!
#Park your aircraft on PAKT, [http://www.borough.ketchikan.ak.us/airport/airport_history.htm Ketchikan International], runway 11. The wind is coming from '''South''', change the weather if needed (SE is ok too).
#Fly North towards [[NDB]] Fredericks Point on 372.0 for 94 NM.
#Fly towards [[NDB]] Five Fingers on 295.0 for 39 NM.
#Fly towards [[NDB]] Gustavus on 219.0 for 77 NM.
#Fly towards [[NDB]] Coghlan Island on 212.0 for 32 NM.
#Set the [[ILS]] on 109.9 and land your aircraft (after 4 NM) on PAJN, [http://www.juneau.org/airport/ Juneau International], runway 08.
If you feel warm after this landing, you just crossed a NORAD microwave site, so that is why.
*October 2011 by [[User:PH-JBO|PH-JBO]] [[FlightGear Newsletter November 2011]]
==Searching Wizard Island==
*USA, Oregon, Klamath County
With one [[VORTAC]] behind our back we do an [[IFR]]/[[VFR]] search of Wizard Island, a mysterious place, a sacred place for native Americans. You might even find the <tt>Old Man of the Lake</tt>.

Don't pull up the map, that would spoil the surprise but I promise '''unique views'''. We will land on a short lawn runway. Terrain [[altitude]] will range from 4,000 to a max of 8,930 feet and down again. Total length of the trip will be about 50 NM. Select your aircraft with care. It must have one working navigational radio (VOR-DME), a strong engine, a strong undercarriage, must be capable of a good climb and a steep descend. I suggest to use Fair weather (Environment=>Global Weather). If needed remove some clouds (View=>Rendering Options=>Slider 3d Clouds to the left).
[[File:Mount Scott.jpg|thumb|250 px|Mount Scott (8,929 feet) just after depart from 2S7 (Two Sierra Seven). Wizard Island is just to the North-West of it.]]
*Park your aircraft on 2S7 (Two Sierra Seven), Chiloguin-State.
*Set [[NAV1]] on 115.9 (Klamath Falls VORTAC) and on radial 323<sup>o</sup> (Magnetic). We are at an [[elevation]] of 4,217 feet. Set QNH. Set heading bug at 275<sup>o</sup> (Magn).
*Take off an fly the course set with the heading bug.
*Intercept the radial.
*Monitor distance and you will find Wizard Island at 50 NM from Klamath Falls. The island has an elevation of 6,673 feet. I suggest a full 360<sup>o</sup> turn, take pictures.
*Set radial 318<sup>o</sup>, keep the same frequency. Do a new radial intercept.
*Try and find the airstrip (3S6, Three Sierra Six, Toketee-State) at 71 NM from Klamath Falls with an elevation of 3,361 feet, runway heading 275<sup>o</sup> (Magn). There are bumps around you should avoid.
*If you are capable of finding the island, finding the airstrip and landing without a crash, in one go..., you are a wizard.

Click [http://en.wikipedia.org/wiki/Crater_Lake this link] '''after''' you have landed so you know what amazing landscape you have seen.

*December 2011 by [[User:PH-JBO|PH-JBO]]. Published [[FlightGear_Newsletter_March_2012|Newsletter March 2012]].

=South America=
==Southern Tip of Chile==
[[Image:Scgz-001.png|thumb|left|right after take off]]
[[Image:Scgz-004.png|thumb|right|Some part of the scenery]]
Gary Carvell: Here is a suggestion for the FlightGear Places to Fly page. I don't have any particular routes, just fly around and enjoy the gorgeous scenery.<BR/>
These three airports are in the same region of the very southern tip of Argentina. This area is a scenic wonderland - a maze of islands, mountains, and ocean channels. Hours of entertainment.<BR/>
SCGZ - Puerto Williams Guardiamarina Zanartu Airport, Chile Located on the north coast of Isla Navarino facing the Beagle Channel. At 55 deg S. longitude, Puerto Williams is considered the southernmost town in the world.<BR/>
SAWH - Ushuaia Islas Malvinas Airport
SAWO - Ushuaia Est Aeronaval Airport
Ushuaia, on the south coast of Isla Grande de Tierra del Fuego, on the the Beagle Channel.
<div style="clear:both;"></div>
===Airports and coordinates===
[[Image:Sawh-004.png|thumb|left|Approaching Ushumaia Malvinas Argentinas]]
[[Image:World-scgz.png|thumb|right|Latitude: -54.931072 Longitude: -67.626261]]

* [[SCGZ|SCGZ - Guardiamarina Zanartu]] - [http://assistenza.larasrl.net/brisa/fgfs/suggested_flights/SCGZ.pdf chart]
* [[SAWH|SAWH - Ushuaia Malvinas Argentinas]] - [http://assistenza.larasrl.net/brisa/fgfs/suggested_flights/SAWH.pdf chart]
* [[SAWO|SAWO - Ushuaia Est Aeronaval]] - [http://assistenza.larasrl.net/brisa/fgfs/suggested_flights/SAWO.pdf chart]
<div style="clear:both;"></div>

===Suggested aircraft===
[[Image:Scgz-002.png|thumb|left|Just left the scgz airport]]
I personally like to fly this area in the [[Consolidated_Aircraft_PBY_Catalina|Catalina]], it's a great sightseeing plane with the advantage that you can take off and land just about anywhere.
* [[Consolidated_Aircraft_PBY_Catalina|Catalina]]
<div style="clear:both;"></div>

===FlightGear launching===
fgfs --airport=SCGZ --aircraft=Catalina
<div style="clear:both;"></div>

==Copacabana to San Rafael over Lake Titicaca==
Bolivia to Peru. This trip will lead you over one of the highest and deepest lakes in the world towards the highest airfield in the world. It a demonstration of a [[IFR]] flight towards a fix and a demonstration how accurate FlightGear simulates air density and the effects it has on aircraft.
[[File:Slcc-sprf.jpg|thumb|200px|left|Flight and fix SLCC to SPRF]]
Place your aircraft on the airfield [http://en.wikipedia.org/wiki/Copacabana,_Bolivia SLCC, Copacabana], with an [[elevation]] of 12,592 feet. FlightGear will show snow all around you but that is not very realistic so let's clean up. View=> Rendering Options=> Snow line=> Set to max. (5,000M).

We will fly towards and land at SPRF. If you would enter SLCC and SPRF in [[Kelpie]] planner you probably would not be able to find SPRF. To find SPRF I am adding an additional VOR-DME station and for a good fix give you another VOR-DME. Try Kelpie planner to plan this route and compare with this suggestion.

Equipment preparation. Set [[NAV1]] to [http://en.wikipedia.org/wiki/Juliaca Juliaca] VOR-DME on 155.55 with a radial of 311° (magnetic). Set [[NAV2]] to Arequipa VOR-DME on 113.7 with a radial of 212°. During our flight we will fly with [[true altitude]] as set with [[QNH]], keep QNH updated. Arm the autopilot with the [[heading bug]] at 311° and an initial altitude of 13,500 feet.

Take off and if you took the wrong RW pull up hard. Take a small tour over [http://en.wikipedia.org/wiki/Titicaca lake Titicaca], see the floating islands and try to find the lost golden treasure. Intercept the nearest radial on NAV1 towards Juliaca (about 311°).

Just before Juliaca is a hill so while on lake Titicaca increase altitude to 14,200 feet, the [[VFR]] part of this trip is over. After passing Juliaca set the radial of NAV1 to 352° and set the altitude to 17,422 feet. We will fly from NAV1 and slowly increase altitude.

At a distance of about 60 NM set the heading bug on the current course. Monitor the distance to NAV1, the radial of NAV2 and the distance to NAV2. At a distance of 74.5 NM to NAV1, a distance of 140.7 NM and at the '''radial''' intercept of NAV2 should be the runway. So, from 60 NM onwards, look outside the window, then at NAV1 and then NAV2 etc.

If you are at 80NM to NAV1 you have missed the airfield but you still won't hit any hills (unless you bank left). Bank right and set the heading bug to 172°. Fly back towards NAV1 and intercept the radial 352° at about 50NM again to repeat the search.

The runway SPRF, San Rafael, has a elevation of 14,422 feet and a heading of 297°/ 117°. Our initial altitude has been set 3,000NM above the RW elevation. That should give sufficient room for navigation.

After you have seen the airfield set the radial of NAV1 to 297°, the heading of the runway (not the course to the runway) as a visual aid. Land on RW 30 (and not on RW 12 unless you are a show-off). Oh, there is a small hill in front of RW 30, just so you know.

Decreasing speed at this altitude can be a bit tricky. The air is thin and does not give much resistance. Next to that, the difference between [[indicated airspeed]] and [[ground speed]] is very noticeable. The ground speed is much higher as the indicated airspeed.

After a successful landing, try to discover the origin of the Amazon river since we are now at the starting point of that trip.
* October 2011 by [[User:PH-JBO|PH-JBO]], published in [[FlightGear_Newsletter_February_2012#Suggested_flights| Newsletter February 2012]].

==Origin of the Amazon River==
[[Image:SPRF-001.png|thumb|left|high altitude]]
[[Image:SPRF-002.png|thumb|right|high altitude]]
Peru. For this [[IFR]] tour (with [[VFR]] parts) we take off from the highest airfield in the world to discover the origin of the [http://en.wikipedia.org/wiki/Amazon_River Amazon river] in South America. I promise spectacular mountains and valleys. The total length of this trip is about 175 NM.

Place your aircraft on the airfield SPRF, San Rafael. FlightGear will show snow all around you but that is not very realistic so let's clean up. View=> Rendering Options=> Snow line=> Set to max. (5,000M).

Equipment preparation: Set [[NAV1]] to [http://en.wikipedia.org/wiki/Arequipa Arequipa] VOR-DME at 113.7 with a radial of 176° (magnetic). Set [[NAV2]] to [http://en.wikipedia.org/wiki/Cusco Cusco] VOR-DME at 114.9 also with a radial of 176°.
Set [[QNH]] and during flight keep correcting it, it's a bad idea to use [[Pressure altitude]] during this flight. Set the [[heading bug]] to 250°. Arm the [[autopilot]] and set the initial [[altitude]] to 16,000 feet.

The airfield SPRF, San Rafael has an [[elevation]] of 14,422 feet. That altitude will cause problems during take-off. It takes a lot longer for the aircraft to gain sufficient speed for take-off, also the take-off speed that is needed is higher as you would expect. Perhaps an additional notch of flaps is needed.

Take-off, avoid the bumps (there are plenty) and fly a course of 250°. After about 80 NM you will fly over the radial of NAV1. Intercept the radial towards Arequipa. At a distance of 75 NM towards NAV1 you will have to increase altitude to 19,000 feet.

At a distance of 50 NM towards NAV1 and 118 NM from NAV2 you will see and cross over the mountain [http://en.wikipedia.org/wiki/Nevado_Mismi Nevado Mismi] with an altitude of 18,362 ft. The rains and water on the area to the right until Nevado Mismi will leave towards the Atlantic ocean through the Amazon river. Anything to the left and after Nevado Mismi will leave towards the Pacific ocean.

After Nevado Mismi you are tempted to descend. Don't. Just before the airfield is [http://en.wikipedia.org/wiki/Chachani Mt.Chachani] with an altitude of 19,872 feet and to the East is the active volcano [http://en.wikipedia.org/wiki/El_Misti El Misti] with an altitude of 19,101 feet. You can either increase the altitude and fly over the airfield or keep the altitude, even descend and fly between the mountains, your choice depends on the visibility.

Fly using the heading bug and set NAV1 to [[ILS]] 109.7 with a radial of 93.2°. We will land at airfield [http://en.wikipedia.org/wiki/Rodr%C3%ADguez_Ball%C3%B3n_International_Airport SPQU, Rodriguez ballon], that has an elevation of 8,405 feet. There is a reason this airfield has just one ILS. The area South-West of the airfield is below 11,405 feet and is safe to navigate.

Position the aircraft in front of the runway at an altitude of 11,405 feet, catch the [[glidescope]] at a distance of 9.5 NM and land your aircraft. After landing and parking your aircraft crawl into the tower to look around.

Happy flying!

* October 2011 by [[User:PH-JBO|PH-JBO]]. Published [[FlightGear_Newsletter_March_2012|Newsletter May 2012]].

===Airports and coordinates===
[[Image:SPQU-001.png|thumb|left|pre - landing]]
[[Image:World-SPRF.png|thumb|right|Latitude: -14.267 Longitude: -70.467]]
* [[SPRF|SPRF - San Rafael]] - [http://assistenza.larasrl.net/brisa/fgfs/suggested_flights/SPRF.pdf chart]
* [[SPQU|SPQU - Rodriguez Ballon]] - [http://assistenza.larasrl.net/brisa/fgfs/suggested_flights/SPQU.pdf chart]

required scenery tile: ftp://ftp.sunsite.org.uk/sites/ftp.flightgear.org/flightgear-ftp/Scenery/w020s80.tar.gz
<div style="clear:both;"></div>

===Suggested aircraft===
[[Image:SPQU-002.png|thumb|right|landed]]
I recomend a powerful jet angine airplane, but not too heavy !
* [[Cessna 550 Citation II]]

<div style="clear:both;"></div>

===FlightGear launching===
fgfs --airport=SPRF --aircraft=Citation-II
<div style="clear:both;"></div>

=Middle East=
==Israel to Jordan over the Dead Sea==
[[Image:LLBS-001.png|thumb|left|take off]]
[[Image:LLBS-002.png|thumb|right|flat land]]
Dead Sea is the lowest water elevation on the Earth. Take off from the Beer-Sheva Teyman airport and head East-North-East. About half way there, after the southern Hebron mountains ridge, there'll be a sharp drop-off down to the Dead Sea --- the lowest exposed point on the Earth.<br/>
<br/>
It's really fun to descend and explore the beautiful coastline. In the real life, you wouldn't like to fly low over this water there of your own will --- while you don't need a life vest in the Dead Sea, the water is pretty caustic there for one's eyes. Once you're done marvelling the sights, continue on to the Queen Alia airport.
<div style="clear:both;"></div>
===Airports and coordinates===
[[Image:LLBS-006.png|thumb|left|landing in the dead sea, notice the altitude !]]
[[Image:OJAI-007.png|thumb|right|landing at Queen Alia Intl.]]
[[Image:World-LLBS.png|thumb|right|Latitude: 31.29037800 Longitude: 34.71922500]]
* [[LLBS|LLBS - Teyman]] - [http://assistenza.larasrl.net/brisa/fgfs/suggested_flights/LLBS.pdf chart]
* [[OJAI|OJAI - Queen Alia Intl]] - [http://assistenza.larasrl.net/brisa/fgfs/suggested_flights/OJAI.pdf chart]

required scenery tile: ftp://ftp.sunsite.org.uk/sites/ftp.flightgear.org/flightgear-ftp/Scenery/e030n30.tar.gz
<div style="clear:both;"></div>

===Suggested aircraft===
[[Image:LLBS-003.png|thumb|left|approaching the dead sea]]
[[Image:LLBS-004.png|thumb|right|there is also a minor airport]]
* [[Albatross]]

<div style="clear:both;"></div>

===FlightGear launching===
fgfs --airport=LLBS --aircraft=Albatross
<div style="clear:both;"></div>

=Europe=
==Edinburgh to Oban==
See article: [[Edinburgh to Oban]].

==Oban to Prestwick==
The west coast of Scotland offers some stunning scenery and a number of small airfields and airports to land at on both the mainland and the small islands the dot the coast. The distances between the various airfields are quite small, and some of the runways are on the short side, so STOL or GA aircraft are ideal. The tour suggested here follows part of a microlight trip I made this month, photos of which can be found [http://www.nanjika.co.uk/photos/gigha/ here].

Oban airport (EGEO) lies on the west coast of Scotland, and offers fuel (both AVGAS and AVTUR) and a North/South tarmac runway.

From Oban it is just a 10 minute flight west to the grass airfield of Glenforsa (EG45), on the north-east coast of the island of Mull. Due to the hills and water channel, this airfield often gets quite strange wind patterns - the weather can be perfect in Oban, but much gustier and windier at Glenforsa. At times the windsocks at either end of the runway can blow in completely opposite directions!

Some distance north of Oban lie the airfields of the Isle of Skye (EG57) and Plockton (EG81). This is an excellent place from which to explore the mountains of the Isle of Skye, known as the Cuilins.

Heading south from Oban, one can follow the coast to the island of Jura, with it's distinctive hills (The Paps of Jura). From Jura one can head south to the island of Islay with its numarous malt whisky distilleries (many of which are modelled in FG). Islay Airport (EGPI) has extensive runways. From Islay head north east to the tiny island of Gigha. Despite it's small size, it too has an airfield (EG44), though the FG version is tarmac rather than grass.

From Gigha head east over the Mull of Kintyre, to the hilly isle of Arran, then north east to the Isle of Bute. Both islands have very small grass airstrips, which are sadly not present in FG. From Bute you can head south east to Prestwick International (EGPK), famous for being the only place Elvis touched down in the UK, and a fine place to end our tour.
*Published in [[FlightGear Newsletter July 2011]] by [[User:Stuart|Stuart]]

== Edinburgh to Dundee ==
Edinburgh Airport (EGPH) is located to the West of the city of Edinburgh and south of the Forth rail and road bridges. You'll need the w010n50 scenery and the latest set of objects from the scenery DB which include a number of models for the Edinburgh area.

From Edinburgh Airport, head north and circle the bridges, then follow the coast on the south eastwards past Edinburgh (watch out for the Castle!) and to East Lothian and Bass Rock - a volcanic plug in the sea that is host to thousands of sea-birds.

There are a number of sights in East Lothian, include a distillery.

If you wish to continue your tour, head back North, crossing the Firth of Forth to the Kingdom of Fife. Head approximated North West, tracking towards the Perth VOR (110.4). There is an airport here (Perth Scone, EGPT), but instead we will now track out on the 090 radial and pick up the ILS to Dundee Airport (108.10) landing beside the sea.
* September 2006 by [[User:Stuart|Stuart]].

==Austrian alps soaring==
Discover the Austrian alps with a glider. [[Pinzgauer Spaziergang]]

== Sightseeing the Alps in a C172 ==
This tour will guide you to many of the most famous mountains, valleys, glaciers, snowfields, winter and summer vacation areas, etc. in the European Alps. In addition there are several hints to visit nearby areas of interest. On the tour you will visit Switzerland, Italy and France.
See the detailed description in: http://www.emmerich-j.de/FGFS/Alp-flying.pdf (mirrored to https://beni.hallinger.org/fgfs.nobackup/Alp-Tour-Jomo/)
*February 2011 by [[User:Jomo|Jomo &dagger;]].;

* The scenic trip does take about 2 hours.
* Skyvector route: https://skyvector.com/?ll=46.464097146192884,7.159790050777061&chart=301&zoom=6&fpl=%20LSZC%204700N00836E%204647N00840E%204642N00836E%204637N00835E%204634N00823E%204634N00812E%204633N00809E%204634N00805E%204634N00801E%204631N00803E%204624N00746E%204619N00745E%204618N00753E%204614N00752E%204612N00749E%204609N00747E%204603N00746E%204601N00745E%204600N00738E%204555N00724E%204555N00712E%204553N00703E%204547N00652E%204549N00649E%204604N00634E%20LSGG

== Salzburg to Zell am See via Hallstatt ==
[[File:LOWS-LOGO-LOWZ.jpg|thumb|The route for Salzburg to Zell am See via Hallstatt]]
This flight will bring you around a very scenic region of the austrian alps.
* [https://skyvector.com/?ll=47.5666119817603,13.107925427128999&chart=301&zoom=3&fpl=N0100A040%20LOWS%204735N01311E%204736N01339E%204733N01340E%204733N01343E%204735N01343E%204738N01355E%204727N01357E%20LOWZ SkyVector route]
* Suggested plane: C172 or C182
* This is VFR only, so pick suitable weather. There are no usable navaids for this trip.
* Trip takes around 1 hr. air time at 120 KTAS.
* Fly at an altitude of about 4000ft or so (the entire trip can be done at that altitude safely).

* Start ''Salzburg (LOWS)''; follow the Autobahn in the valley to the southeast until you reach the fork at ''Golling''. To the south you see the Mountains of the ''Tennengebirge''.
* Alternatively (and I recommned that), you can also deviate sothwest around ''Mt. Untersberg'' (1972m, hosting germanys longest and deepest cave, the ''Riesending'') to visit lake ''Königsee'' and watch the peaks of the ''Steinernes Meer'' (the dominant and very famous ''Mt. Watzmann'', 2713m!) and north side of the ''Mt. Hochkönig''. You need to climb to at least 6200ft to cross the final ridge at the end of the lake valley. After crossing, descend to 4000ft, follow the valley and fly north at the next valley to rejoin the route.
* Turn east and follow the valley and hills, aim for a prominent V-shaped incision at the end. Fly through there and you suddenly break out at the lake ''Hallstätter See'', a fjord-like lake 125m deep.
* Follow the ''Hallstätter See'' to the south, on its western shore is the famous town of ''Hallstatt''. At the mountain to your right (north of Hallstatt) is a very old settlement dating back to the late bronce age (Hallstattzeit, c. 800–450 BC) and there was a very important Salt mine dating back to that time and important archeological grave findings.
Looking south you can see the ''Dachstein'' (2995 m), a high peak hosting the ''Hirlatzhöhle'', with 120km the twentiest longest and with 1560m sixth deepest cave of planet earth.
* Follow the valley east bend to ''Obertraun'', and then north over the ''Koppenpass'' and the town of ''Bad Aussee''.
* From ''Bad Aussee'', fly straight to the lakes ''Grundlsee'' and ''Toplitzsee'' (you can't see the latter yet).
* Between the two, turn southwards and aim for the reservoir lake ''Salza'' which is in the sharp incision you can see to the south.
* After passing the reservoir, you may try to get down to ''Niederoblarn'' (LOGO) to the southeast, it's a short airfield.
* From there, follow the railway in the valley of Enns westwards, LOWZ is about 20 minutes away. On your right side watch out for the other side of the ''Dachstein'' and the town of ''Schladming'', which lies down in the valley next the rocky hills with the river flowing trough. Look for the railway and the river Enns.
* Behind ''Schladming'' (south of Mt. ''Dachstein'', approximately halfway of the distance LOGO/LOWZ) the valley will widen a bit again, featuring a rocky mountain in the middle of the valley. Continue to follow the railway and river bending nortwest arond the small mountain.
* Near the bigger town of ''Radstadt'' the valley will open significantly. Follow west, heading for the next town ''Altenmark'' at the end of the opening.
* The railway will bend north at ''Altenmark'' and soon join the Autobahn A10/E55. This is the point we need to go southwest and follow the next valley.
* The valley leads us westward to the Town of ''St. Johann/Pongau''. probably around the middle of the valley you can spot the prominent ''Mt. Hochkönig'' (2941m) northwest of ''St. Johann'' and the ''Tennengebirge'' to its right.
* Once reaching ''St. Johann'', continue to follow the next big valley west-southwest.
* After about 16 miles you will reach ''Zell am See'' (LOWZ) where we will land after around one hour flight time in total. Beware this is a short field.

== Zell am See to Innsbruck via Mt. Venediger ==
[[File:LOWZ-LOWI.jpg|thumb|The route for Zell am See to Innsbruck]]
This flight will bring you to two of the core peaks of the Alpenhauptkamm.
* [https://skyvector.com/?ll=47.201656734623775,12.160079968084839&chart=301&zoom=3&fpl=N0100A120%20LOWZ%20LOWZ%204708N01241E%204708N01221E%204706N01214E%204710N01152E%204724N01150E%20LOWI SkyVector route]
* Suggested plane: C172 or C182
* This is VFR only, so pick suitable weather. There are no usable navaids for this trip.
* Trip takes around 45 minutes air time at 110 KTAS.
* Climb to at an altitude of about 10000ft or so after starting from [[:File:Lowz-parking.jpg|Zell am See]].

* After starting fly into the valley southwest over the town of ''Kaprun''. Maybe you need to circle a bit to gain altitude, near the mountains we need at least about 10000ft!
* Follow the valley until you overfly two lakes (''Stausee Wasserfallboden'' and ''Moorboden''). To your left you can see ''Mt. Großes Wiesbachhorn'' (3564m).
* The end of the valley goes over into a flank of the ''Großglockner'' which is near to the south. Follow the west bend of the valley end and fly over the lakes ''Tauernmoossee'' and ''Weißsee''. After you climb out of the valley, you already should see the peak of ''Mt. Venediger'' on the front left. Aim to the saddle right of its peak.
* You then fly that direction over several valleys that go from south to north, until you hit the very big valley that bend from south to west. The ridgeline right of that valley is the border between the Austrian states Tirol and Salzburg. Follow the valley up to the ''Venediger'', passing the ''Mt. Sandebentörl'' (2751m), still aiming for the saddle.
* Shortly after you reach the end of the valley and need to overfly the saddle with the glacier ''Venedigerkees'' behind it. The ridgeline is again the border between Tirol and Salzburg. Directly south of the ''Venedigerkees'' is the pyramid of ''Mt. Venediger''.
* Follow ''Venedigers'' ridge to the southwest, skip the first valley and overfly the next ridge.
* From here you can deviate into the valley north and visit the ''Krimmler Wasserfälle'', and from there west trough the main valley.
* If you instead follow the planned route westwards, aim to the peak of ''Mt. Zillerplattenspitze'' (3148m) with the small lake ''Eissee'' to its south flank which you should already see. This is a little hard to get right, but don't fly directly into the big valley but aim right to the second row mountain peaks at about 280 heading.
* Overfly the ridge with ''Eissee'' and follow the valley from there nothwest with the reservoir ''Zillergründl'' and ''Mt. Reichenspitze'' (3303m) to its right; until you reach the town ''Mayrhofen'' where the current valley meets the ''Zillertal'' valley. You also should start to descend now to about 3500ft with a rate of roughly -1000fpm.
* From ''Mayrhofen'' follow the ''Zillertal'' valley north and when reaching the ''Inntal'' valley near the town ''Jenbach'', Innsbruck Airport is a few minutes to the west. If you like, you can divert north at ''Jenbach'' to visit ''Achensee'', and even continue further north to land at Munich via lake ''Tegernsee'' or via the Isartal over ''Bad Tölz''.

== Crossing the alps ==
[[File:ED02-LIPB.jpg|thumb|The route for Fuessen to Bolzano]]
This trip brings us from germany via austria to italy, crossing the alps, visiting the famous castle Neuschwanstein and Mt. Zugspitze, germanys highest peak.
* [https://skyvector.com/?ll=47.068251080980836,10.959411633048108&chart=301&zoom=5&fpl=N01204735N01041E%204734N01045E%204729N01042E%204726N01046E%204724N01054E%204712N01054E%204704N01058E%204656N01103E%204655N01106E%204653N01109E%204650N01110E%204648N01113E%204638N01110E%20LIPB SkyVector route]
* Suggested plane: C172 or C182
* This is VFR only, so pick suitable weather and time (I suggest to start with the first light/sunrise).
* There are no helpful navaids for this trip, but Bolzano NDB: 362 BZO may serve as a final guidance.
* Trip takes around 45 minutes air time at 120 KTAS.

* Start at ED02 Fuessen, climb to about 3000 and head southeast to visit castle Neuschwanstein, south of the Forgensee.
* After looking at the castle (challenge: fly close around behind it), we start climbing to 3500 and aim southwestish and cross over from germany to austria.
* Fly into the big valley directing south. East of Reutte start climbing 500fpm to 6000 and follow the railway in the valley to the southeast.
* Once the valley opens significantly, you can see the famous mountain Zugspitze (germanys highest peak, 2962 m) to the front.
* Head southwards around the Mt. Gartnerwand over town Ehrwald and fly between the two small peaks over the Marienbergjoch mountain pass, 1789m/5870ft (between Mt. Wanning and Mt. Marienberg; challenge: who can make it with the least altitude?).

* After overflying the second mountain, to the south comes a new valley called Ötzal where you fly into.
* Follow that valley all the way to the south and slowly climb to at least 8600 now (300fpm or so). Note overflying Längenfelden, where the dominant valley joins from the east with the river Fischbach, halfaway the leg; this looks similar to the end, but isn't.
* Follow the valley until it starts to branch in all different directions at the end (over the town of Sölden and Zwieselstein).
* We follow the Southeast main branch and then turn quickly to a smaller valley branching off directly eastwards (look for the mountain pass road).
* That brings us to the mountain pass of the Timmelsjoch and is the place where we cross over to Italy.

* After passing, we can descend to 2500 or so, following the terrain. Follow the valley and its river "Passer" southeast, and follow its bend to the south.
* Follow the valley and make a nice turn around Mt. Kolbenspitze's east ridge, over San Leonardo, still following the Passer river now southwards.
* Where the valley hits the next big valley "Etschtal", is a bigger famous city called Merano. From there we follow the River Etsch and the Autobahn (highway) to the south and are soon approaching the somewhat hidden airport of Bolzano (LIPB) after an estimated time of somewhat under one hour at 120 knots.

From here you can also continue more to the south to Trento (LIDT, total FT ~1:00) or Verona (LIPX, total FT ~1:20) - just follow the river Etsch to the south! Venezia is also not far away, just ~30 minutes/62nm to the east of Verona.

==Grenoble Le-Versoud==

[[Image:LFLG.jpg|800px]]

France : '''LFLG''' ( Grenoble Le-Versoud ) airport : border of Alps
*P.A.F. home base [http://equipe-flightgear.forumactif.com/ link]
*Scenery : http://clemaez.fr/flightgear/flightgearfrance_05062011.tar.gz
*Texture : http://clemaez.fr/flightgear/pattentextures_maj24082011.tar.gz

* Take-off from Grenoble le Versoud (LFLG). Head south following the general direction of the Alps. Bearing left (East) will take you into high alpine territory, while towards the West lie the plains of the Rhône valley. Once you reach the Mediterranean coast, follow it to land in Marseilles (LFML), Nice (LFMN), or another smaller airport serving the French Riviera.
*Published in [[Custom France Scenery]].

==Gulf of Finland sightseeing tour==
Take a VFR sightseeing tour over the Gulf of Finland from Helsinki to Tallinn! Estonia's landmarks are all recent additions, while Helsinki was one of the first cities to have original models in the scenery model database.

Take off from the smaller EFHF airfield in Helsinki, or try your luck fighting the virtual traffic at Vantaa, and head toward the port of Helsinki. Look for the Hartwall Arena, the Pasila tower, the railway station and the Olympic Stadium along the way. Make your way out over the Gulf flying just west of south - a heading of 190 should set you up nicely for a sightseeing tour of Tallinn. Try to come in from the west and do a sweeping left turn over the capital of Estonia, looking out for the Swissotel, Olympic Hotel, the Television tower, and other important landmarks in the capital city of Estonia. Make sure you look out for St. Olaf's Church, the tallest building in the capital city. Make your way over the Ulemiste Jarv (lake) to land on runway 09 at Tallinn's main airport.

If you desire, you can do a touch-and-go at Tallinn and set your course southeastward, landing at Tartu Airport, which is also modelled in FlightGear.

The distance between Helsinki and Tallinn is about 50 miles or 80 kilometres, while Tartu is twice the distance from Tallinn at 100 miles/160 kilometres. Fly a heading of 135 to get to Tartu from Tallinn.
*Published in [[FlightGear Newsletter October 2010]] by [[User:Statto|Statto]].

==Azores==
[[Image:LPLA-001.png|thumb|left|take off]]
[[Image:LPLA-002.png|thumb|right|approaching island]]
The [http://en.wikipedia.org/wiki/Azores Azores], set in the middle of the Atlantic ocean, has had many names. Fortunate Isles, the Blue Islands, the Islands of Tin and Silver, the Islands of the Seven Cities. We can add, the Islands of Amazing Sights and Flights.

Our flight is to celebrate the amazing views FlightGear can give us.

Start your plane at [[Lajes Field]] (LPLA). This once was an emergency landing site for the [[Space Shuttle]] so you will have plenty of room to take off.
We will have to fly an odd pattern. The reason for that: if you don't fly too high (stick around 3000 while you can) you will have some amazing views.

Next, fly towards and over LPPD. Look out the window and enjoy the view. Then head out towards LPHR. If you feel LPHR coming near, look out the window good, you might have to pull your plane up.

Happy flying!
*Published in [[FlightGear Newsletter August 2011]] by [[User:PH-JBO|PH-JBO]]

===Airports and coordinates===
[[Image:LPPD-001.png|thumb|left|over the island]]
[[Image:LPPD-002.png|thumb|right|landing]]

* [[LPLA|LPLA - Lajes Field]] - [http://assistenza.larasrl.net/brisa/fgfs/suggested_flights/LPLA.pdf chart]
* [[LPPD|LPPD - Ponta del gada]] - [http://assistenza.larasrl.net/brisa/fgfs/suggested_flights/LPPD.pdf chart]

required scenery tile: http://mirrors.ibiblio.org/pub/mirrors/flightgear/ftp/Scenery-v2.4.0/w020n30.tgz
<div style="clear:both;"></div>

===Suggested aircraft===
* [[Cessna 550 Citation II]]

===FlightGear launching===
fgfs --airport=LPLA --aircraft=Citation-II
<div style="clear:both;"></div>

== Canary Islands Trip ==

An archipelago in the middle of the Atlantic sea, stunning beauty where you won't expect it. Seven islands, seven continents, thats what the canarian people say. And it's true, you will face seven totally different islands and nine different airports.
Take off from the largest one, GCLP, at the main island Gran Canaria. Leave the beautiful island heading to the west, and land at GCTS, the southern airport at Tenerife. Enjoy the view on Spains highest mountain, the glaciered Teide, when flying to La Gomera (GCGM), one of the greenest islands there. Master the short runway, and enjoy the view, before taking the challenge and approach El Hierro (GCHI). A short runway, with cliffs and rocks on both ends will cause you to sweat. From this island, which was claimed to be the western end of the world in medieval times, you'll turn to the beautiful and wild island of La Palma (GCLA). The next approach will be historical, because you are approaching the notorious Tenerife North (GCXO). Yes, I am serious, you will face that airport, where the worst civil plane crash ever took place. But you needn't worry, if you got that far, you will do this approach as easy as any other. The longest flight on your trip will take you to the eastern island, Lanzarote (GCRR). Take a look at the volcanic-red mountains, the vineyards, and the beaches. You want more beaches?? Depart to the south-west, fly over the small island of Los Lobos, and land in the holiday-paradise Fuerteventura. Enjoy dunes, bays, and very nice long beaches, before you finally touch down in Fuerteventura (GCFV). You want to stay? Okay, let's taxi to a parking position, and cut off the engines. If you still want more, fly back to Gran Canaria's GCLP, where we started our trip.

Custom scenery: [[Canary Islands Custom Scenery]] / direct source: https://github.com/D-ECHO/Canarys

=== Suggested Aircraft ===

* small civil aircraft, such as the Cessna Skylane, Skyhawk, or Citation
* small airliners, like the Q400, the ATR72, the CRJ200, or similar

Route by Flycanarias

<gallery>

</gallery>

==Gibraltar==
[[Image:LEMG-010.png|thumb|left|take off]]
[[Image:LEMG-011.png|thumb|right|just after take off]]
Traffic lights turn red, gates are closed. The only busy main road to the peninsula is closed and all the cars and trucks are waiting patiently. Waiting for a train to pass? No. Waiting for a plane to pass since the main road crosses a busy runway.

On both sides water and being crossed by a busy main road can only be one runway: [http://en.wikipedia.org/wiki/Gibraltar_Airport Gibraltar airport]!

One would expect an ILS installed on such a tricky runway but no, you will have to guess where it is and how far away it is. Not even an ADF points to it.

Take off from LEMG (Malaga). Go South-West and find the runway of LXGB somewhere to the right of the rock. Happy guessing!
*Published in [[FlightGear Newsletter September 2011]] by [[User:PH-JBO|PH-JBO]]
<div style="clear:both;"></div>

===Airports and coordinates===
[[Image:LEMG-013.png|thumb|left|search for this]]
[[Image:LEMG-015.png|thumb|right|landing]]

* [[LEMG|LEMG - Malaga]] - [http://assistenza.larasrl.net/brisa/fgfs/suggested_flights/LEMG.pdf chart]
* [[LXGB|LXGB - Gibraltar]] - [http://assistenza.larasrl.net/brisa/fgfs/suggested_flights/LXGB.pdf chart]

required scenery tile: http://mirrors.ibiblio.org/pub/mirrors/flightgear/ftp/Scenery-v2.4.0/w010n30.tgz
<div style="clear:both;"></div>

===Suggested aircraft===
* [[Piper Aerostar]]

===FlightGear launching===
fgfs --airport=LEMG --aircraft=aerostar700 --adf1=300 --nav1=300:117.80
<div style="clear:both;"></div>

=Asia=
==Khorog, Tajikistan==
[[File:Fw190HinduKush.jpeg|left|thumb|Approaching a bank of snow-covered mountains in the south of the Hindu Kush]]
Surrounded by spectacular mountains and nestled in the end of a valley, Khorog Airfield (UT1C) makes an interesting place to land. It can only be approached by flying down the curved valley that snakes in from the North. Flying from here to OPCH (Chitral, Pakistan) at around 500ft AGL all the way is a wonderful way to explore the Hindu Kush mountains.

If you bring a piston engined aircraft, be prepared to adjust the mixture as you climb - at the highest point in the flight, you will be at around 22000ft. Also, don't forget to carry plenty of fuel - there are very few airfields in the Hindu Kush that exist in FlightGear. This is a scenery bug that will hopefully be fixed in the future.

*October 2011 by [[User:Armchair Ace| Armchair Ace]], published in [[FlightGear_Newsletter_January_2012#Suggested_flights| Newsletter January 2012]].
<br>
<br>
<br>
== Central Karakoram range ==
Let's explore one of the highest regions of the planet - the central Karakoram with the densest concentration of mountains of 8000 m and above. We're going to need a good climbing performance for the trip - even the frozen plateau of Baltoro glacier, above which K2 and Gasherbrum V and VI loom, is more than 13,000 ft high.

[[File:Karakoram1.jpg|300px|thumb|left|Circling Gasherbrum I]]

Take off from Skardu airport in Pakistan (OPSD). Skardu has a reasonably long (11,944 ft) runway at just 7,316 ft elevation, so you can take a jet, but for instance the [[De Havilland Canada DHC-6 Twin Otter|Twin Otter]] is more stylish.

South of Skardu lies Deosai park, a famous high plateau, but we turn initially east. There's a chain of lakes which is the Indus river. After about five miles, the Shigar river merges with the Indus. Turn slightly left and follow the Shigar, then follow it into a long and broad lake-filled valley stretching into north-western direction.

Towards the end of the lake, a small tributary river, the Braldu, turns eastward out of the main valley. Follow the Braldu and start climbing (if you haven't done so yet). About 15 miles after turning into the Braldu river valley, two glacier-filled valleys stretch to the north - admire the view!

[[File:Karakoram2.jpg|300px|thumb|right|Heading back into Skardu, Nanga Parbat on the horizon]]

Passing a few lakes, you reach finally Baltoro glacier continuing the river valley stretching eastward. Ever climbing, follow the glacier till you reach some kind of T-junction. The glacier arm reaching north leads to K2 (which sadly isn't really there in Flightgear), but just ahead of you are the still rather impressive peaks of Gasherbrum V, VI and I - circle the range and make some pictures!

A good way back to Skardu is to go about 10 miles sourth from the Gasherbrum peaks, then head due west. To your west, you can see the long valleys fall away from the high ranges, to your right is the still glacier-covered high Karakoram. On a clear day (really good visibility selected) you can see the distinctive peak of Nanga Parbat appearing straight ahead on the horizon. The valley of Skardu is quite a distinctive feature and finding back VFR should not be a problem.

Published in [[FlightGear_Newsletter_April_2012#Suggested_flights| Newsletter April 2012]] by [[User:Thosten|Thosten]].

== The Paro Challenge ==
[[File:The Paro Challenge route.png|thumb|The route to follow in the maze of valleys between Hashimara Air Base (VE44) and Paro airport (VQPR). Created using OpenStreetMap and the Open Topo layer.]]
The challenge consists in flying as fast and as low as possible from Hashimara (VE44) to Paro (VQPR) while navigating a maze of valleys, steep climbs and sharp turns with only one VOR-DME beacon to guide you (it sits on a mountaintop south of Paro airport). You cannot fly on instruments; this is a 100% visual flight.

Spawn at VE44 (Hashimara Air Force Station). Take off in any direction then turn immediately to heading 013 while staying low. You will see the Himalayas appear on the horizon. Follow the valley as it turns 90° left then make a sharp U-turn (180°) to the right. Fly over the bridge, then U-turn left again (160°). Follow the valley and do another U-turn to the right. Take a deep breath for a couple of nautical miles. Climb to 8500ft while heading 080 to pass over the mountain range. Turn slightly to your right (heading 100) and do a steep dive to 4000ft into the valley. Turn left into the second valley (heading 010), which you will need to follow all the way to Paro airport (VQPR), while climbing slowly to the airport elevation of 7500ft. On the way to Paro, you will pass a monastery on your left. If you don't see this monastery, you've lost yourself in the maze; good luck! After this monastery, follow the valley to the left (heading 290), which will force you to turn right after a few nautical miles. The runway will be hidden behind a hill. You can pass over the hill (steep dive on the other side) or fly to the right of it (steep S-turns), your choice.

=== Suggested aircraft ===
The Paro Challenge is a challenge for most aircraft and most pilots. You will probably not succeed on your first attempt; and successive attempts with various aircraft will renew the challenge.

===== Easy =====
[[Cessna 550 Citation II]], [[Pilatus PC-6 Porter|Pilatus PC-6]], [[De Havilland Canada DHC-6 Twin Otter|De Havilland Canada DHC-6]], [[Zivko Edge 540]].

[[De Havilland Mosquito]], Messerschmitt Bf109G, [[Lockheed P-38 Lightning]].

==== Challenging ====
[[Piper PA34-200T Seneca II|Piper Seneca II]], [[Cessna 337G Skymaster|Cessna 337]], [[Antonov An-2]]: keep an eye on your Exhaust Gas Temperature and Cylinder Head Temperature. If you can't lean your mixture, you lose.

Cessna 172, PA-28 or DR-400 with 180hp engines and a light load; [[Cessna 182S]]; Cap 10b. Slower than the above and will require just as much concentration from you, for a longer time.

[[Mikoyan-Gurevich MiG-15|MiG-15]], [[North American F-86 Sabre|F-86F Sabre]], [[Fairchild Republic A-10 Thunderbolt II|A-10 Warthog]]: make high-speed, steep turns while finding your way. Don't black out!

==== Difficult ====
[[JT-5B|JT-5B autogyro]], [[Piper J3 Cub|Piper Super Cub 150hp]]: the Paro challenge takes well over an hour of intense concentration in these unstable aircraft.

Cessna 172, PA-28 or DR-400 with low-power (160hp) engines. You will need to circle several times in the valley during the climb. If you can't lean your mixture, you lose.

[[Boeing 707]], [[Boeing 757-200|757]], [[Tupolev Tu-154B|Tupolev 154]], [[Lockheed Constellation]] if lightly loaded; [[Cessna Citation X]]: Finding your way in these faster aircraft is a challenge. The U-turns before the steep climb are almost impossible without taking shortcuts. The final approach without seeing the runway requires you to control your speed, flaps and landing gear well in advance.

==== Impossible (but you might try to beat them anyway) ====
[[Piper J3 Cub|Piper Cub 65hp]] (cannot climb over 7000ft when fully loaded).

[[Boeing 737-300]] (poor low-speed handling), [[Boeing 787-8 Dreamliner|787]] (bank limiter).

[[Dassault Mirage 2000-5|Mirage 2000]], [[Grumman F-14 Tomcat|F-14B]], [[McDonnell Douglas F-15 Eagle|F-15C]], [[General Dynamics F-16 Fighting Falcon|F-16]]: will either stall or black you out during the sharp turns.

=Africa=
==Ngorngoro==
For this [[VFR]] trip we need a strong machine since we will go up from 4000 to about 10,000 feet and since we are in Africa, Tanzania , what better choice is there as the Cessna 208 Caravan, on wheels. We will take off from HTLM, [http://en.wikipedia.org/wiki/Lake_Manyara Lake Manyara], runway 12 (124.5 deg), that has an elevation of 4150 feet. Hit Shift-B so we don't drop off the runway.
[[File:Map Ngorngoro Crater.jpg|thumb|200px|left|Heightmap with visual reference points]]
We will have to change some settings before we take off. There is no snow where we are so: View=> Rendering Options=> Snow line=> Set to max. (5000M). We need a reasonable clear sky since there are quite a few bumps we could hit: Environment=> Global weather=> METAR source=> Fair weather.

Give full throttle and take off. Bank left and make a full circle so we gain some altitude and make a mental note of the airstrip, since this is the only one nearby. Look at the road West towards the airfield.
You will notice that the airstrip is at the edge of a mountain ridge, the lake to the East is quite a lot lower.

We pass over the airstrip towards lake Manyara and turn left keeping the mountains close to our left side, on an initial course of about 30 deg. We keep the mountains to our left and follow our path, our heading will slowly go from 30 to North and takes about 15 mins. During our path we should slowly gain altitude.
[[File:Ol Doinyo Lengai.jpg|thumb|250px|Mt.Kerimasi (left), Mt.Ol Doinyo Lengai (ahead)]]
On the '''image''' we see two distinct mountains. The nearest is Mt.Kerimasi, a fun place for hang-gliders, and North Mt.Ol Doinyo Lengai, an active volcano. We are heading straight towards [http://en.wikipedia.org/wiki/Ol_Doinyo_Lengai Mt.Ol Doinyo Lengai]. Just before we would collide we take a sharp left turn heading 225. You will see why we need the altitude now.

The mountain ahead, [http://www.ntz.info/gen/n00161.html#id03702 Mt.Embagai], we see does not appear to be anything spectacular. Aim towards it since we have to go over it.
Coming nearer, if you are high enough, 9000 feet, you will see why this mountain is well worth a visit. It is a crater with a lake inside, lake Embagai (Empakaai). Enter the crater and look around, careful not to loose any height since we'll have to get out again, we need about 10 000 feet. Mesmerized we grab our compass and take a course of 225 again. To get out we might skim against a cloud, be careful. If you don't see a way out take a turn again to wait for the clouds to move out of sight.

After you managed to get out of the crater keep on the course of 225 while descending slowly for about 9 mins. There are some bumps to avoid, like Mt.Olmoti we keep to the right and Mt.Losirua on the left.

After a small hill we enter one of the most amazing places in Africa, the [http://en.wikipedia.org/wiki/Ngorongoro_Conservation_Area Ngorngoro Crater], the second biggest crater in the world. A micro climate and amazing wildlife.
Examine the crater and you will notice two lakes, head towards the biggest lake, lake Magadi. When you are above it take a course of 123 to get out of the crater.

After leaving the crater it takes some time before we are near the airstrip again. After about 5 mins we will see a river (left) and a road (right). Follow the road since it will lead us to the airstrip again.

Don't scare the wildebeast!

Notecard:
<tt>
#Fair weather, no snow
#HTLM RW 12 4150 feet
#Course 30 to 0 deg 15 mins, mountains close left
#Head towards /\volcano
#Sharp left turn course 225 deg altitude 9000 feet
#Volcano, lake, 10 000 feet
#Course 225 deg, slow descend 9 min
#Large lake, course 123 deg 5 mins
#River left, road right. Follow road
#Landing 124.5 deg 4150 feet.</tt>

*October 2011 by [[User:PH-JBO|PH-JBO]]. Published in [[FlightGear_Newsletter_December_2011#Suggested_flights | Newsletter December 2011]].
==Kisimayu to Kilimanjaro==
We have to take a big airliner for this trip. The runways are long enough but for this trip we need some altitude and a slow descend.

We park our Big Bird at HCMK, [http://en.wikipedia.org/wiki/Kismayo_Airport Kisimayu], Somalia, near the East coast of Africa. It's unsure what this airfield is used for but it's a long piece of tarmac. I could not find regular flights to and from this airfield, not so strange, there is no lighting, no radio beacons and... no fuel. What you can find is Global Air Rescue that has an air ambulance service based here (with a [http://www.globalairrescue.com/learjet-35.php Learjet 35]).

Our route will be around 425 nm in length. You know your aircraft and know what altitude you will need to fly.

Our destination, HTKJ, [http://en.wikipedia.org/wiki/Kilimanjaro_International_Airport Kilimanjaro], Tanzania, has only one ILS and I have learned, if an airfield has only one ILS there is probably a reason.

Flight Plan (short version):
#HCMK Kisimayu, length 12,177 ft, no navaids near.
#GAR Garissa [[VOR-DME]] freq 115.7 heading 268° dist 169 nm.
#KB Kilimanjaro [[NDB]] freq 393.0 heading 224° dist 258 nm, here is the holding pattern for the Kilimanjaro runway (and there is a [http://en.wikipedia.org/wiki/Mount_Kilimanjaro 19,000 ft] reason for this detour).
#KV Kilimanjaro VOR-DME freq 115.3 heading 70° dist 26 nm.
#HTKJ Kilimanjaro [[ILS]] freq 110.9 runway heading 88° elev 2,900 ft [[AMSL]] length 11,807 ft.

Prepare your flight well to receive amazing views of the landscape during the final steps of the route, if you don't you will discover why some pilots call Kilimanjaro Kill-You-Manjaro.

{{#ev:youtube | KCJi_ZaR8ec}}
Youtube video: Kilimanjaro approach in real, in FG not much different.

*February 2012 by [[User:PH-JBO|PH-JBO]].

=Australia and Oceania=

==Hawai'i==
[[Image:Maui03.jpg|thumb|250px]]
Do you use [[TerraSync]]? If so, try a flight around Hawaii! Take off from PHNL in a light aircraft and head west until you hit Pearl Harbor; a right turn north will take you post the USS Arizona Memorial, and the Punchbowl Crater will be to your right. Or, fly east from PHNL past volcanic craters Diamond Head and Koko Head. If you follow the O'ahu coastline north from Koko Head, you can land at either old World War II airbase Bellows Field (now a wildlife reserve in real life) or at Keahole MCAS.

For a potentially more scenic route, fly east toward Molokai, and stay to the north (left) of the island. The northern part of Molokai features huge sea cliffs and a tiny airstrip on the Kalaupapa peninsula - the peninsula being the only respite from the cliffs. A former leper colony existed near the airstrip!

Also of interest are the volcanoes on Maui and the 'Big Island' of Hawai'i - flying VFR in a small plane from PHTO to PHKO over the plateau between Mauna Kea and Mauna Loa can be a challenge, as you have to take off from sea level, fly through a pass of 6500 feet, and then drop back down to sea level to land! The Hana coast of northern Maui is also a nice flight - a circumnavigation of Haleakala, starting and ending at PHOG, is quite a nice flight.

The islands will be available through the download center with the next major scenery release, but for now, fire up [[TerraSync]] and your favorite VFR aircraft and have a blast.
*Published in [[FlightGear Newsletter September 2010]] by [[User:Statto|Statto]].

== Hawai'i waterfalls tour ==
This flight will let you discover some of the famous Hawai'ian waterfalls, visiting the Islands of Kauai and Oahu.
{{note| Despite the scenery is very nice, the waterfalls are mostly not modeled (as of 5/2024)}}

* [https://skyvector.com/?ll=21.82733715471215,-158.96200561400335&chart=301&zoom=5&fpl=%20PHBK%202211N15938W%202206N15930W%202204N15925W%20LIH%202135N15817W%202138N15802W%202120N15746W%202116N15748W%20PHNL SkyVector route]
* Suggested plane: C172 or C182
* This is VFR only, so pick suitable weather. There are no usable navaids for this trip except the VORTAC LIH 113.500 to cross the sea.
* Trip takes around 90 minutes air time at 110 KTAS.

First part of the trip:
* Start at Parking sands (PHBK), runway 34
* Takeoff, climb to 5000ft and follow the northern coast at about a heading of 030° until you reach Crawlers Ledge (about 8 minutes flight time).
* Turn southeast into the very dominant embayment and watch out for Hanakoa Falls, our first waterfall to visit.
* To your left should be a very dominant valley behind the ridge, featuring a river. Now climb to 6000ft and follow that valley southeastish and visit the famous Weeping wall waterfalls behind the ridge at the end of the valley.
* Bank left slightly (~100° heading), descend to 3000 ft and aim for Wailua waterfalls at the south side of the small hill near the coast (between the two towns).

This concludes the islands waterfalls after about 20 minutes flight.

Now either land at Lihue Airport (PHLI) to your right for a break, or continue the trip and intercept VORTAC LIH 113.500 radial 99/TO. Follow the radial to cross the Kauai Channel until you reach the tip of Oahu Island (the crossing of 63NM takes about 30 minutes at 120 knots. You may also opt to skip and start at PHDH).

* Follow overfly Kawaihapai Airfield (PHDH) and follow the northern coast.
* Shortly you will ovefly a prominent bend from east to nothertheast in the coast, still follow the coast. Note the windfarm appearing to your right ahead.
* Over Waimea (just before the very visible sand beach), turn right and fly to the inland behind (north of) the windfarm. Shortly after passing the wind turbines, look out for Waimea waterfalls.
* Follow the mountains to the southeast of the island and slowly climb to 4000ft (the left side is more rough and scenic).
* North of Diamond Head (a big crater at the south tip of the island) there are several waterfalls (roughly in the middle between Diamond head in the south and Kaneohe in the north), as well as very nice streams coming down the ridge. Also the north side of the ridge is very nice, so consider doing a circle over there.
* Continue south over Diamond head and proceed to land at Honolulu airport (PHNL).

This concludes the trip after about 1:30 hours.

==Brisbane International Airport to Sydney International Airport==
Going from Brisbane International Airport to Sydney International Airport. You should have a heading of about 203. Might take sometime to arrive to this section. Maybe 10-30 mins into the flight. Can't really say but don't give up, you will eventually reach this section of the flight. '''''Your eyes will be rewarded!''''' .

[[Image:Fgfs-screen-020.png|200px]]
[[Image:Fgfs-screen-016.png|200px]]
[[Image:Fgfs-screen-012.png|200px]]
*Published in [[FlightGear Newsletter April 2011]] by [[User:Vin|Vin]]

=Antarctica=

{{Suggested}}

[[Category:Lists]]

Suggested Flights

2024-08-23T02:35:40Z

Circumn: /* The Paro Challenge */ Added a beautiful map which I created myself.

[[FlightGear]] has accurate and realistic terrain. Here are some interesting places where you can do virtual sight seeing.

If you are starting with [[FGRun]] - the FlightGear launcher - you can enter the [[airport]] id and select the runway on the appropriate screen in the startup wizard.
If you are starting from the command line you can use the options: <tt>--airport=ABCD</tt> and <tt>--runway=12L</tt>.

*Remember to give a look at the [[Suggested Airports]] page, where you can find a comprehensive list of high quality airports in FlightGear.
*If you enjoy these flights, please consider recording a flight and posting a link to it at the [[Suggested Prerecorded Flights]] page.

'''Remove before flight!''' 

Before you start flying into one of the suggested flights, you should add both the terrain and the Objects to you FlightGear installation; This is well explained on the [[Howto: Install scenery|installing scenery]] page.

p.s. charts are generated using FlightGear data only.

This page includes the flights described on the [http://www.flightgear.org/places.html main website] and the suggested flights from the newsletters. It can serve as an archive for suggested flights from future [[FlightGear Newsletter|newsletters]] or can give a flight if creativity is low that month.

{{TOC limit|3}}

=Cross Continentals or World Tour=

* [[Breitling DC-3 World Tour]][[File:Rect17.png|thumbnail]]
* [[Flying the Hump]]

=North America=
==Round Valley Airport==
[[Image:O09-002.png|thumb|left|right after take off]]
[[Image:O09-003.png|thumb|right|Valley]]
Covalis, CA. The airport is at the West edge of a 7 mile across valley.<BR/>
The predominant wind is a cross wind. Take-offs to the west (if they use the full runway length) often have to fly between 2 small hills and over another valley while gaining altitude. Most pilots take off to the west.<BR/>
It is a paved runway and quite long. It was designated as an emergency recovery field during the Cold War and was used twice that I know of by military aircraft that could not take off again from the field.
<div style="clear:both;"></div>

===Airports and coordinates===
{{Location map | USA
| caption = Latitude: 39.790156 Longitude: -123.266403
| lat_deg = 39.790156
| lon_deg = -123.266403
}}

* [[O09|O09 - Round valley]] - [http://assistenza.larasrl.net/brisa/fgfs/suggested_flights/O09.pdf chart]

required scenery tile: ftp://ftp.sunsite.org.uk/sites/ftp.flightgear.org/flightgear-ftp/Scenery/w120n40.tar.gz
<div style="clear:both;"></div>

===Suggested aircraft===
I have tried this trip using a p38, quite powerful airplane
* [[Lockheed-P38|P38]]
<div style="clear:both;"></div>

===FlightGear launching===
fgfs --airport=O09 --runway=28 --aircraft=p38
<div style="clear:both;"></div>

==Half Moon Bay==
[[Image:KHAF-001.png|thumb|left|right after take off]]
[[Image:KHAF-002.png|thumb|right|Bridge]]
Start at [[KHAF|Half Moon Bay]], Runway 30, with 32km visibility; Takeoff in the C172 and climb to 1000 feet, then continue north over the water, near the shoreline. Look out the right window frequently. Fly up the coast, overfly the Golden Gate Bridge, continue around the top of the peninsula past downtown SF, then fly on to [[KSFO]] for a landing. We now have lots to see.

If you cannot see the runway in the default 172, you must be flying too high or too slowly. You can start by practicing a bit with a good setup:

'''fgfs --offset-distance=1.5 --altitude=500 --vc=70'''

As soon as FlightGear starts, cut the power to 1500 rpm and drop two notches of flap. Maintain 70 kt. Now, pick your landing spot (a bit down the runway) and try to hold it in the same spot on your windshield. If your landing spot starts moving down, you are too high, and should cut another 100 rpm; if it starts moving up, you are too low, and should add another 100 rpm. Adjust the nose to keep your speed at 70 kt all the way down until you're right above the numbers, then cut power to idle, drop the last notch of flaps, flare, and land.
<div style="clear:both;"></div>

===Airports and coordinates===
[[Image:KHAF-003.png|thumb|left|surroundings]]
[[Image:World-KHAF.png|thumb|right|Latitude: 37.513333 Longitude: -122.501111]]
* [[KHAF|KHAF - Half Moon Bay]] - [http://assistenza.larasrl.net/brisa/fgfs/suggested_flights/KHAF.pdf chart]

no required scenery tile.
<div style="clear:both;"></div>

===Suggested aircraft===
[[Image:KSFO-001.png|thumb|left|Before landing]]
Use the default c172 airplane
* [[Cessna C172P]]
<div style="clear:both;"></div>

===FlightGear launching===
fgfs --airport=KHAF --runway=30 --visibility=32000 --aircraft=c172
<div style="clear:both;"></div>
===Author===
April 2006 [[User:Hellosimon|Hellosimon]], format and extended by [[User:Francescobrisa|Francescobrisa]]

==Hell's Canyon==
[[Image:25U-001.png|thumb|left|right after take off]]
[[Image:25U-004.png|thumb|right|Valley]]
Hell's Canyon, Imnaha, OR. This airport is located just west of "Hell's Canyon National Park" which has the Snake River running through it.<br/>
Supposedly it's a 5500 foot drop from the top of the canyon to the river.<BR/>
The airport is located on the brink of this canyon.

See the remarks on the airport page (click on the airport id) ... DOWNDRAFTS, SHEER DROP IN TERRAIN, LIVESTOCK, etc. Don't go here on your first solo x-country. :-)
<div style="clear:both;"></div>

===Airports and coordinates===
[[Image:25U-005.png|thumb|left|Landing]]
[[Image:World-25U.png|thumb|right|Latitude: 45.427861 Longitude: -116.693889]]
* [[25U|25U - Round valley]] - [http://assistenza.larasrl.net/brisa/fgfs/suggested_flights/25U.pdf chart]

required scenery tile: ftp://ftp.sunsite.org.uk/sites/ftp.flightgear.org/flightgear-ftp/Scenery/w120n40.tar.gz
<div style="clear:both;"></div>

===Suggested aircraft===
[[Image:25U-006.png|thumb|left|Landing 2]]
I have tried this trip using a pilatus PC-9M, powerful airplane
* [[PC-9M|PC-9M]]
<div style="clear:both;"></div>

===FlightGear launching===
fgfs --airport=25U --aircraft=PC-9M
<div style="clear:both;"></div>

==Crater Lake National Park Tour==
[[Image:64s-003.png|thumb|left|Approaching the lake]]
[[Image:64s-002.png|thumb|right|Direction 40 degrees]]
Prospect, OR.<br/>

Take off and fly at a heading of about 40 degrees until you cross the first distinct ridge in front of you. (several minutes of flight in the navion ... just climb as fast as you can, it will be a close squeek to get over :-)<br/>

Once you clear the ridge and can see beyond it, turn right and fly a heading of about 70 degrees. You should see two shallow peaks off in the distance. Head right between these -- they are the two sides of the crater. As you get closer the shape of the crater will come into view. There's a lake there in real life, hopefully it will be there in flight gear too before long.
<div style="clear:both;"></div>

===Airports and coordinates===
[[Image:64s-001.png|thumb|left|Leaving the 64S airfield]]
[[Image:World-64S.png|thumb|right|Latitude: 42.743183 Longitude: -122.488092]]
* [[64S|64S - Prospect State]] - [http://assistenza.larasrl.net/brisa/fgfs/suggested_flights/64S.pdf chart]

required scenery tile: ftp://ftp.sunsite.org.uk/sites/ftp.flightgear.org/flightgear-ftp/Scenery/w130n40.tgz
<div style="clear:both;"></div>

===Suggested aircraft===
[[Image:64s-004.png|thumb|left|Lake view 1]]
[[Image:64s-005.png|thumb|right|Lake view 2]]

* [[Ryan_Navion|Navion]]
<div style="clear:both;"></div>

===FlightGear launching===
fgfs --airport=64S --runway=02 --aircraft=navion
<div style="clear:both;"></div>

==Grand Canyon Tour==
[[Image:Grand_Canyon_Tour_4.jpg|700px|frameless|center]]
Being a special place, there are also special flight rules for VFR traffic around the Grand Canyon. There are multiple no-fly-zones set up and VFR traffic is only allowed to fly via the designated corridors. If you want to fly realistically, avoid these zones in FlightGear as well, following for example the [https://skyvector.com/?ll=36.18649251415492,-112.52223157994264&chart=230&zoom=5&fpl=%20KGCN%20VPGCF%20VPGCG%20VPGCD%20VPGCC%20VPGCA%203608N11252W%203609N11309W%201Z1%201G4%203AZ5 route shown here. (skyvector link)]

This flight takes you from KGCN, the Grand Canyon National Park airport, to 3AZ5, a small airfield called Hualapai located south of the Grand Canyon. Departing from KGCN, fly north-west bound to reach the canyon. From there, either follow the route shown on skyvector above, or fly visually through the canyon westbound towards 1Z1, Grand Canyon Bar Ten Airstrip. From there on, continue flying westward to 1G4. Called Grand Canyon West, 1G4 also marks about the western end of the canyon. To get to your destination 3AZ5, continue along the southern rim, flying eastward now. Shortly after leaving the breathtaking valley behind you, you will already reach your destination. Land and let your engine and your mind cool down from the special views :)

===Gallery===
<gallery>
Grand_Canyon_Tour_2.jpg
Grand_Canyon_Tour_3.jpg
Grand_Canyon_Tour_1.jpg
</gallery>

===Airports===
* KGCN - Grand Canyon National Park Airport - [https://www.aopa.org/destinations/airports/KGCN/details aopa.org]
* 1Z1 - Grand Canyon Bar Ten Airstrip - [https://www.airnav.com/airport/1Z1 airnav.com]
* 1G4 - Grand Canyon West - [https://www.airnav.com/airport/1G4 airnav.com]
* 3AZ5 - Hualapai - [https://www.airnav.com/airport/3AZ5 airnav.com]

===Suggested aircraft===
Most VFR aircraft with sufficiently big windows will serve the purpose, for example:
*[[Cessna C172P]]
*[[Optica]]
*[[Ryan_Navion]]
If you are more interested in flying helicopters, the [[Eurocopter EC130 B4]] with the Grand Canyon Helicopters livery might be for you.

===Links===
*[https://www.nps.gov/grca/learn/nature/upload/sfra.pdf Chart of the Grand Canyon special airspace, published by the National Park Service]
*[http://www.swaviator.com/html/issueJJ99/canyon.html An article about flying close to the Grand Canyon]
*[https://www.aopa.org/news-and-media/all-news/2017/april/flight-training-magazine/road-trip-grand-canyon AOPA Flight suggestion]

==Ranger Creek Airport==
[[File:21w-1.jpg|500px|center|Waiting for departure at Ranger Creek]]
Ranger Creek Airport is located in Greenwater, Washington, USA. Being wedged into the bottom of a steep canyon, you'll definitely need to be on your toes to get in and out of there. Switch on Advanced Weather and Live Data to experience what the winds can do to you in real life!
===Airports and coordinates===
* [[21W|21W - Ranger Creek]] - [http://www.airnav.com/airport/21W airnav.com]
===Gallery===
<gallery>
Ranger_Creek1.jpg|Departing between the mountains
Ranger_Creek_2.jpg|Looking back towards the airfield
Ranger_Creek_3.jpg|Downwind for approach back to Ranger Creek
</gallery>
===Suggested aircraft===
For this flight, the Piper PA-18 SuperCub is suggested, this is included in the [[Piper J3 Cub]] package

==Mount Rainier Tour==
[[Image:WA20-002.png|thumb|left|The mountain from far away]]
[[Image:WA20-006.png|thumb|right|external view]]
Eatonville, WA. Start out at Swanson Airport in Eatonville, WA. Take off and fly a heading of about 90 degrees. You will need to fly for 5-10 minutes before the mountain comes into view. Be patient if you don't see it right away, it will dwarf everything in it's vicinity.
<div style="clear:both;"></div>
===Airports and coordinates===
[[Image:World-WA20.png|thumb|right|Latitude: 46.87588502 Longitude: -122.25733500]]

* [[WA20|WA20 - Swanson]] - [http://assistenza.larasrl.net/brisa/fgfs/suggested_flights/WA20.pdf chart]

required scenery tile: ftp://ftp.sunsite.org.uk/sites/ftp.flightgear.org/flightgear-ftp/Scenery/w130n40.tgz
<div style="clear:both;"></div>

===Suggested aircraft===
[[Image:WA20-007.png|thumb|left|external near view]]
[[Image:WA20-009.png|thumb|right|external near view]]
* [[mosquito]]

<div style="clear:both;"></div>

===FlightGear launching===
fgfs --airport=WA20 --aircraft=mosquito
<div style="clear:both;"></div>

==Death Valley Tour==
[[Image:L06-001.png|thumb|left|in the air]]
[[Image:Furnace-creek.jpg|thumb|left|real life view of Furnace Creek Airfield]]
[[Image:L06-002.png|thumb|right|in the air]]
Furnace Creek, CA. This starts you right in the middle of Death Valley which runs north & south. If you head south about 15 miles you'll hit the lowest point in the USA, 282 feet (86 meters) below sea level.
<div style="clear:both;"></div>
===Airports and coordinates===
[[Image:World-L06.png|thumb|right|Latitude: 36.46451100 Longitude: -116.88139422]]
* [[L06|L06 - Furnace Creek]] - [http://assistenza.larasrl.net/brisa/fgfs/suggested_flights/L06.pdf chart]

required scenery tile: ftp://ftp.sunsite.org.uk/sites/ftp.flightgear.org/flightgear-ftp/Scenery/w120n30.tgz
<div style="clear:both;"></div>

===Suggested aircraft===
[[Image:L06-003.png|thumb|left|in the air]]
[[Image:L06-004.png|thumb|right|in the air]]
* [[rallye-MS893]]
<div style="clear:both;"></div>

===FlightGear launching===
fgfs --airport=L06 --aircraft=rallye-MS893
<div style="clear:both;"></div>

==Utah==
!!! Work in progress !!!<BR/>

Escalante Muni Airport, Escalante, UT. This airport is east and a bit north of Bryce Canyon National park. If you head mostly south and a bit east you'll eventually hit the Grand Canyon. It is sandwiched between the Dixie National forest to the north and the Grand Staircase-Escalante National Monument to the south. There should be interesting stuff to see no matter which direction you head.
<div style="clear:both;"></div>
===Airports and coordinates===
[[Image:World-1L7.png|thumb|right|Latitude: 37.75054400 Longitude: -111.57578300]]
* [[1L7|1L7 - Escalante Muni]] - [http://assistenza.larasrl.net/brisa/fgfs/suggested_flights/1L7.pdf chart]

required scenery tile: ftp://ftp.sunsite.org.uk/sites/ftp.flightgear.org/flightgear-ftp/Scenery/w120n30.tgz
<div style="clear:both;"></div>

===Suggested aircraft===

<div style="clear:both;"></div>

===FlightGear launching===
fgfs --airport=1L7 --aircraft=pa18
<div style="clear:both;"></div>

==Lake County Airport (CO)==
[[Image:KLXV-001.png|thumb|left|Adjust mixture !]]
[[Image:KLXV-002.png|thumb|right|The terrain will be covered by snow]]
Lake County Airport, Leadville, CO. This airport is at an elevation of 9927 making it a bit of a challenge to get into and out of with a standard C172.<BR/>
Make sure you lean out your engine before taking off and read up on density altitude before you try this one in real life.
<div style="clear:both;"></div>
===Airports and coordinates===
[[Image:KLXV-003.png|thumb|left|The airport]]
[[Image:World-KLXV.png|thumb|right|Latitude: 39.22812500 Longitude: -106.31835600]]
* [[KLXV|KLXV - Lake Co]] - [http://assistenza.larasrl.net/brisa/fgfs/suggested_flights/KLXV.pdf chart]

required scenery tile: ftp://ftp.sunsite.org.uk/sites/ftp.flightgear.org/flightgear-ftp/Scenery/w110n30.tgz
<div style="clear:both;"></div>

===Suggested aircraft===
[[Image:KLXV-004.png|thumb|left|I like this panorama]]
[[Image:KLXV-005.png|thumb|right|The nearby lake]]
* [[Cessna C172P]]

<div style="clear:both;"></div>

===FlightGear launching===
[[Image:KLXV-006.png|thumb|left|Landing...]]
fgfs --airport=KLXV --aircraft=c172p
<div style="clear:both;"></div>

==Caribbean - Saint Martin and St. Kitts==
[[Image:TNCM-003.png|thumb|left|just after the take off]]
[[Image:TNCM-004.png|thumb|right|some nearby island]]
Pilots of the Caribbeans is an informal FlightGear community of users who fly around the small Caribbean islands, many of which have custom scenery and improved landclass data. (For details see [[Pilots of the Caribbean]])<BR/>

[[TNCM|Princess Juliana International Airport (TNCM)]] at the isle of Saint Martin, is one of the most popular airports in FlightGear. In large part due to the custom objects and land cover. However, St. Marten is only one of several detailed airports in the region - and, while the approach for TNCM is one of the most memorable in the whole world, the land cover for St. Kitts and Nevis makes it a lovely place to fly.

British Airways, US Airways and American Airlines, among others, all fly into St. Kitts' [[TKPK|Robert L. Bradshaw International Airport (TKPK)]] in real life.

Take off from TKPK in a [[Piper_J3_Cub|Piper Cub]] and make a northward, clockwise circle of the island. Start your descent on the east side of the island, and focus on the small hill which separates the north from the south. Start hugging the coast near the beach and look to the west - as soon as the railroad heads to the southwest, you're about ready to turn for final. Make your right hand turn for final and taxi to the terminal.

If you want to fully explore this whole country, take off in a Beaver, which has a little more speed, and fly a figure eight. Take off from TKPK and circle the airport to the north like in the Cub. Then instead of landing, perform a touch-and-go and turn left over the boat terminal and make for the west coast of Nevis. Enjoy the beauty of the south coast of St. Kitts before circling Nevis. Over Nevis, you have several options - cut your flight short and land at [[TKPN]] on the island of Nevis, complete the "figure eight" by heading back to TKPK, or check your fuel and head east across the Caribbean to Antigua (which does not have custom land cover).<BR/>
<BR/>
Check out the [[Pilots of the Caribbean]] page, for further informations.
<div style="clear:both;"></div>
===Airports and coordinates===
[[Image:World-TNCM.png|thumb|right|Latitude: 18.040953 Longitude: -63.108900]]

* [[TNCM|TNCM - Princess Juliana International Airport]] - [http://assistenza.larasrl.net/brisa/fgfs/suggested_flights/TNCM.pdf chart]
* [[TKPK|TKPK - Robert L. Bradshaw International Airport]] - [http://assistenza.larasrl.net/brisa/fgfs/suggested_flights/TKPK.pdf chart]
* [[TKPN|TKPN - Vance Winkworth Amory Intl]] - [http://assistenza.larasrl.net/brisa/fgfs/suggested_flights/TKPN.pdf chart]
others interesting airports in the area:
* [[TFFF|TFFF - Le Lamentin]] - [http://assistenza.larasrl.net/brisa/fgfs/suggested_flights/TFFF.pdf chart]
* [[MDPP|MDPP - Gregorio Luperon Intl]] - [http://assistenza.larasrl.net/brisa/fgfs/suggested_flights/MDPP.pdf chart]
* [[TJSJ|TJSJ - Luis Munoz Marin Intl]] - [http://assistenza.larasrl.net/brisa/fgfs/suggested_flights/TJSJ.pdf chart]
* [[FMEE|FMEE - St Denis Gillot]] - [http://assistenza.larasrl.net/brisa/fgfs/suggested_flights/FMEE.pdf chart]
* [[TFFG|TFFG - Grand Case]] - [http://assistenza.larasrl.net/brisa/fgfs/suggested_flights/TFFG.pdf chart]

required scenery tile:
* ftp://ftp.sunsite.org.uk/sites/ftp.flightgear.org/flightgear-ftp/Scenery/w070n10.tgz
* ftp://ftp.sunsite.org.uk/sites/ftp.flightgear.org/flightgear-ftp/Scenery/w080n10.tgz
* ftp://ftp.sunsite.org.uk/sites/ftp.flightgear.org/flightgear-ftp/Scenery/w080n20.tgz
* ftp://ftp.sunsite.org.uk/sites/ftp.flightgear.org/flightgear-ftp/Scenery/w090n20.tgz
<div style="clear:both;"></div>

===Suggested aircraft===
[[Image:TNCM-005.png|thumb|left|amazing]]
[[Image:TNCM-006.png|thumb|right|landing]]
* [[Piper_J3_Cub|Piper Cub]]
<div style="clear:both;"></div>

===FlightGear launching===
fgfs --airport=TKPK --aircraft=Cub
<div style="clear:both;"></div>
===Author===
[[FlightGear Newsletter January 2011]] by [[User:Statto|Statto]], format and extended by [[User:Francescobrisa|Francescobrisa]].

==Friedman Memorial Airport (Idaho)==
[[Image:KSUN-001.png|thumb|left|take off]]
[[Image:KSUN-002.png|thumb|right|nearby]]
Friedman Memorial Airport, Hailey, Idaho. This airport is nestled in a valley surrounded by significant terrain. It's one that shows up quite often in accident investigations.
<div style="clear:both;"></div>
===Airports and coordinates===
[[Image:World-KSUN.png|thumb|right|Latitude: 43.51223900 Longitude: -114.30376100]]
* [[KSUN|KSUN - Friedman Mem]] - [http://assistenza.larasrl.net/brisa/fgfs/suggested_flights/KSUN.pdf chart]

required scenery tile: ftp://ftp.sunsite.org.uk/sites/ftp.flightgear.org/flightgear-ftp/Scenery/w120n40.tgz
<div style="clear:both;"></div>

===Suggested aircraft===
[[Image:KSUN-003.png|thumb|left|landing]]
[[Image:KSUN-004.png|thumb|right|landing]]
* [[FK9MK2]]
<div style="clear:both;"></div>

===FlightGear launching===
fgfs --airport=KSUN --aircraft=fk9mk2
<div style="clear:both;"></div>

== Wyoming - Grand Teton ==
Jackson Hole (KJAC) airport is located at around 6,400ft right next to the Teton range of mountains. The Tetons rise straight out of the plains, gaining over 5,000ft in 2 miles.

You will need the w120n40 scenery.

Tower frequency at KJAC is 118.07. Due to the high altitude, you will need to lean non-turbocharged piston aircraft before take-off. Don't forget that take-off distances will also be longer.

After take-off head to the North East. Grand Teton is the highest of the three peaks that rise straight from the flat-lands. Follow the line of mountains to the East, passing over Jenny Lake. After a couple of miles you will reach a huge lake. The large bulk of a mountain to the East is Mount Moran.

The Teton Mountain range is surprisingly thin - really just a string of mountains running SW-NE. Flying fast jets down the steep valleys is recommended.
* September 2006 by [[User:Stuart|Stuart]].

== Virginia Eastern Shore, Chesapeake Bay-Bridge Tunnel Sightseeing ==
[[Image:KTGI-001.png|thumb|left|before take off]]
[[Image:KTGI-002.png|thumb|right|right after take off]]

Take a short VFR trip from Tangier Island to view the famous Chesapeake Bay Bridge-Tunnel connecting Cape Charles to Cape Henry. Depart historic Tangier Island (KTGI) situated in the Chesapeake Bay and land at Norfolk International Airport (KORF), Norfolk, Virginia. The scenic character of the flight is enhanced by leaving the island at dusk. The flight is both scenic and challenging. Frequently, when flying with real weather, you will have a steady wind blowing across the bay. Starting out quiet Tangier and arriving at busy, glittering Norfolk International (KORF) gives the flight some contrast.

'''fgfs --airport=KTGI --runway=20 --timeofday=dusk'''

Before leaving Tangier: Set your altimeter to the prevailing barometric temperature. Set your communications radio to the Norfolk Intl. (KORF) ATIS frequency of 127.150 MHz to listen for weather reports in the destination area. Set your navigation radio to 112.20 MHz to pick up the Cape Charles (CCV) VOR. Set your heading bug to the runway heading, 200.

Takeoff straight, flying the runway heading. Climb to 2000ft and maintain.

Shortly, you should see the VOR assigned to NAV1 display receive a steady signal (the OFF flag will disappear). The DME should also settle down and display the distance to the Cape Charles VOR station. The flight to CCV will be about 26 nautical miles. As you fly, it will show your airspeed and time to arrival. It should take about ten minutes.

Turn the OBS knob until the VOR displays the TO flag and 190 degrees, the heading you should now turn to.

Fly south from Tangier, crossing an expanse of water, about ten miles until you see the Virginia Eastern Shore. You'll come upon the grass airstrip of Chance (VA89) a few minutes out from Tangier. Beyond are two flashing tower beacons. You may catch a glimpse of Weirwood/Kellam (W08) on the ocean shore, recognizable by two crossing dirt strips.

If you look carefully, you may see the little white building that is the Cape Charles VOR station. As you fly over VOR the flag will change from TO to FROM and the needle will deflect. Do not try to follow the needle. Wait until you are past the VOR. As you cross the VOR station, you should see a highway slanting across your path toward the south west. Turn to follow this highway. You'll come across a lone tower with beacon along the roadside. You'll see an access road stretching from the tower complex to the main road.

If the sky conditions permit, you may try your hand at wayfinding by following the road. If visiblity is poor, set the VOR to 180 degrees to parallel the road to the end of the peninsula. Or you can continue to fly outbound from the VOR on 190 by maintaining the same heading. The VOR needle should return to center with the FROM flag displaying. This will put you west of the bridge with a good view and the option to turn towards KORF near the initial approach fix. If you follow the highway you will need to overfly the airport, but if you stay on the 190 heading, you will be in a position to make a straight in landing.

As you fly down the peninsula you'll pass Cherrystone, Eagle's Nest, Scott and Bull Farm grass airstrips. Bull Farm is the last strip before the mouth of the Chesapeake. Just past Scott Farm you should see the first glimmer of the northern leg of the bridge. The grass strips can be very difficult to see.

As you reach the end of the peninsula, be careful to avoid the tower on Fisherman's Island at the north end of the north leg of the bridge (Note the bridge is not modeled by FlightGear...but I hope to work up one eventually). Next comes the north middle leg. Turn right a few degrees to follow the south middle leg. Watch as the deck plunges beneath the waves to allow ships to navigate the north and south channels.

As Cape Henry approaches, you'll see the Norfolk International airport to the right and the southern leg of the bridge touching the shore.

If you intend to land at KORF, you will want to start your approach soon. Otherwise, you may continue to follow the bridge to the end. Make the approach to KORF by contacting the tower for vectors. Or use the ILS.

This is a good flight to practice VOR flying on. It is a very straight flight path to the VOR requiring little adjustment and there are no other VORs in the area to confuse you.
*June 2006 by [[User:Sek|Sek]].

===Airports and coordinates===
[[Image:World-KTGI.png|thumb|right|Latitude: 37.8250835 Longitude: -75.9976665]]
* [[KTGI|KTGI - Tangier Island]] - [http://assistenza.larasrl.net/brisa/fgfs/suggested_flights/KTGI.pdf chart]
* [[KORF|KORF - Norfolk International]] - [http://assistenza.larasrl.net/brisa/fgfs/suggested_flights/KORF.pdf chart]

required scenery tile: ftp://ftp.sunsite.org.uk/sites/ftp.flightgear.org/flightgear-ftp/Scenery/w80n30.tgz

===Suggested aircraft===
[[Image:KTGI-003.png|thumb|left|surroundings]]
[[Image:KORF-001.png|thumb|right|landing to KORF]]
I have tried this trip using a Seneca II
* [[Piper PA34-200T Seneca II]]
<div style="clear:both;"></div>

===FlightGear launching===
fgfs --airport=KTGI --runway=20 --timeofday=dusk --aircraft=SenecaII
<div style="clear:both;"></div>

==Prince George to Calgary Springbank==
A beautiful flight is from Prince George (CYXS), to Calgary Springbank (CYBW). Route created by reed, which can be seen at {{forum link|t=9772|text=the forums}}
*Published in [[FlightGear Newsletter November 2010]] By [[User:Cael|Cael]].
==Ketchikan to Juneau==
It's cold where we will go so dress up warm and if we are lucky we might see whales during our flight. Don't fly too high to enjoy the amazing views, and there is a small challenge at the end. The runways we will use are long enough for bigger aircraft (7000+). Total length of the trip will be around 245 NM. So, hop in the cockpit of your favourite airliner.

Alaska, here we come! Enjoy!
#Park your aircraft on PAKT, [http://www.borough.ketchikan.ak.us/airport/airport_history.htm Ketchikan International], runway 11. The wind is coming from '''South''', change the weather if needed (SE is ok too).
#Fly North towards [[NDB]] Fredericks Point on 372.0 for 94 NM.
#Fly towards [[NDB]] Five Fingers on 295.0 for 39 NM.
#Fly towards [[NDB]] Gustavus on 219.0 for 77 NM.
#Fly towards [[NDB]] Coghlan Island on 212.0 for 32 NM.
#Set the [[ILS]] on 109.9 and land your aircraft (after 4 NM) on PAJN, [http://www.juneau.org/airport/ Juneau International], runway 08.
If you feel warm after this landing, you just crossed a NORAD microwave site, so that is why.
*October 2011 by [[User:PH-JBO|PH-JBO]] [[FlightGear Newsletter November 2011]]
==Searching Wizard Island==
*USA, Oregon, Klamath County
With one [[VORTAC]] behind our back we do an [[IFR]]/[[VFR]] search of Wizard Island, a mysterious place, a sacred place for native Americans. You might even find the <tt>Old Man of the Lake</tt>.

Don't pull up the map, that would spoil the surprise but I promise '''unique views'''. We will land on a short lawn runway. Terrain [[altitude]] will range from 4,000 to a max of 8,930 feet and down again. Total length of the trip will be about 50 NM. Select your aircraft with care. It must have one working navigational radio (VOR-DME), a strong engine, a strong undercarriage, must be capable of a good climb and a steep descend. I suggest to use Fair weather (Environment=>Global Weather). If needed remove some clouds (View=>Rendering Options=>Slider 3d Clouds to the left).
[[File:Mount Scott.jpg|thumb|250 px|Mount Scott (8,929 feet) just after depart from 2S7 (Two Sierra Seven). Wizard Island is just to the North-West of it.]]
*Park your aircraft on 2S7 (Two Sierra Seven), Chiloguin-State.
*Set [[NAV1]] on 115.9 (Klamath Falls VORTAC) and on radial 323<sup>o</sup> (Magnetic). We are at an [[elevation]] of 4,217 feet. Set QNH. Set heading bug at 275<sup>o</sup> (Magn).
*Take off an fly the course set with the heading bug.
*Intercept the radial.
*Monitor distance and you will find Wizard Island at 50 NM from Klamath Falls. The island has an elevation of 6,673 feet. I suggest a full 360<sup>o</sup> turn, take pictures.
*Set radial 318<sup>o</sup>, keep the same frequency. Do a new radial intercept.
*Try and find the airstrip (3S6, Three Sierra Six, Toketee-State) at 71 NM from Klamath Falls with an elevation of 3,361 feet, runway heading 275<sup>o</sup> (Magn). There are bumps around you should avoid.
*If you are capable of finding the island, finding the airstrip and landing without a crash, in one go..., you are a wizard.

Click [http://en.wikipedia.org/wiki/Crater_Lake this link] '''after''' you have landed so you know what amazing landscape you have seen.

*December 2011 by [[User:PH-JBO|PH-JBO]]. Published [[FlightGear_Newsletter_March_2012|Newsletter March 2012]].

=South America=
==Southern Tip of Chile==
[[Image:Scgz-001.png|thumb|left|right after take off]]
[[Image:Scgz-004.png|thumb|right|Some part of the scenery]]
Gary Carvell: Here is a suggestion for the FlightGear Places to Fly page. I don't have any particular routes, just fly around and enjoy the gorgeous scenery.<BR/>
These three airports are in the same region of the very southern tip of Argentina. This area is a scenic wonderland - a maze of islands, mountains, and ocean channels. Hours of entertainment.<BR/>
SCGZ - Puerto Williams Guardiamarina Zanartu Airport, Chile Located on the north coast of Isla Navarino facing the Beagle Channel. At 55 deg S. longitude, Puerto Williams is considered the southernmost town in the world.<BR/>
SAWH - Ushuaia Islas Malvinas Airport
SAWO - Ushuaia Est Aeronaval Airport
Ushuaia, on the south coast of Isla Grande de Tierra del Fuego, on the the Beagle Channel.
<div style="clear:both;"></div>
===Airports and coordinates===
[[Image:Sawh-004.png|thumb|left|Approaching Ushumaia Malvinas Argentinas]]
[[Image:World-scgz.png|thumb|right|Latitude: -54.931072 Longitude: -67.626261]]

* [[SCGZ|SCGZ - Guardiamarina Zanartu]] - [http://assistenza.larasrl.net/brisa/fgfs/suggested_flights/SCGZ.pdf chart]
* [[SAWH|SAWH - Ushuaia Malvinas Argentinas]] - [http://assistenza.larasrl.net/brisa/fgfs/suggested_flights/SAWH.pdf chart]
* [[SAWO|SAWO - Ushuaia Est Aeronaval]] - [http://assistenza.larasrl.net/brisa/fgfs/suggested_flights/SAWO.pdf chart]
<div style="clear:both;"></div>

===Suggested aircraft===
[[Image:Scgz-002.png|thumb|left|Just left the scgz airport]]
I personally like to fly this area in the [[Consolidated_Aircraft_PBY_Catalina|Catalina]], it's a great sightseeing plane with the advantage that you can take off and land just about anywhere.
* [[Consolidated_Aircraft_PBY_Catalina|Catalina]]
<div style="clear:both;"></div>

===FlightGear launching===
fgfs --airport=SCGZ --aircraft=Catalina
<div style="clear:both;"></div>

==Copacabana to San Rafael over Lake Titicaca==
Bolivia to Peru. This trip will lead you over one of the highest and deepest lakes in the world towards the highest airfield in the world. It a demonstration of a [[IFR]] flight towards a fix and a demonstration how accurate FlightGear simulates air density and the effects it has on aircraft.
[[File:Slcc-sprf.jpg|thumb|200px|left|Flight and fix SLCC to SPRF]]
Place your aircraft on the airfield [http://en.wikipedia.org/wiki/Copacabana,_Bolivia SLCC, Copacabana], with an [[elevation]] of 12,592 feet. FlightGear will show snow all around you but that is not very realistic so let's clean up. View=> Rendering Options=> Snow line=> Set to max. (5,000M).

We will fly towards and land at SPRF. If you would enter SLCC and SPRF in [[Kelpie]] planner you probably would not be able to find SPRF. To find SPRF I am adding an additional VOR-DME station and for a good fix give you another VOR-DME. Try Kelpie planner to plan this route and compare with this suggestion.

Equipment preparation. Set [[NAV1]] to [http://en.wikipedia.org/wiki/Juliaca Juliaca] VOR-DME on 155.55 with a radial of 311° (magnetic). Set [[NAV2]] to Arequipa VOR-DME on 113.7 with a radial of 212°. During our flight we will fly with [[true altitude]] as set with [[QNH]], keep QNH updated. Arm the autopilot with the [[heading bug]] at 311° and an initial altitude of 13,500 feet.

Take off and if you took the wrong RW pull up hard. Take a small tour over [http://en.wikipedia.org/wiki/Titicaca lake Titicaca], see the floating islands and try to find the lost golden treasure. Intercept the nearest radial on NAV1 towards Juliaca (about 311°).

Just before Juliaca is a hill so while on lake Titicaca increase altitude to 14,200 feet, the [[VFR]] part of this trip is over. After passing Juliaca set the radial of NAV1 to 352° and set the altitude to 17,422 feet. We will fly from NAV1 and slowly increase altitude.

At a distance of about 60 NM set the heading bug on the current course. Monitor the distance to NAV1, the radial of NAV2 and the distance to NAV2. At a distance of 74.5 NM to NAV1, a distance of 140.7 NM and at the '''radial''' intercept of NAV2 should be the runway. So, from 60 NM onwards, look outside the window, then at NAV1 and then NAV2 etc.

If you are at 80NM to NAV1 you have missed the airfield but you still won't hit any hills (unless you bank left). Bank right and set the heading bug to 172°. Fly back towards NAV1 and intercept the radial 352° at about 50NM again to repeat the search.

The runway SPRF, San Rafael, has a elevation of 14,422 feet and a heading of 297°/ 117°. Our initial altitude has been set 3,000NM above the RW elevation. That should give sufficient room for navigation.

After you have seen the airfield set the radial of NAV1 to 297°, the heading of the runway (not the course to the runway) as a visual aid. Land on RW 30 (and not on RW 12 unless you are a show-off). Oh, there is a small hill in front of RW 30, just so you know.

Decreasing speed at this altitude can be a bit tricky. The air is thin and does not give much resistance. Next to that, the difference between [[indicated airspeed]] and [[ground speed]] is very noticeable. The ground speed is much higher as the indicated airspeed.

After a successful landing, try to discover the origin of the Amazon river since we are now at the starting point of that trip.
* October 2011 by [[User:PH-JBO|PH-JBO]], published in [[FlightGear_Newsletter_February_2012#Suggested_flights| Newsletter February 2012]].

==Origin of the Amazon River==
[[Image:SPRF-001.png|thumb|left|high altitude]]
[[Image:SPRF-002.png|thumb|right|high altitude]]
Peru. For this [[IFR]] tour (with [[VFR]] parts) we take off from the highest airfield in the world to discover the origin of the [http://en.wikipedia.org/wiki/Amazon_River Amazon river] in South America. I promise spectacular mountains and valleys. The total length of this trip is about 175 NM.

Place your aircraft on the airfield SPRF, San Rafael. FlightGear will show snow all around you but that is not very realistic so let's clean up. View=> Rendering Options=> Snow line=> Set to max. (5,000M).

Equipment preparation: Set [[NAV1]] to [http://en.wikipedia.org/wiki/Arequipa Arequipa] VOR-DME at 113.7 with a radial of 176° (magnetic). Set [[NAV2]] to [http://en.wikipedia.org/wiki/Cusco Cusco] VOR-DME at 114.9 also with a radial of 176°.
Set [[QNH]] and during flight keep correcting it, it's a bad idea to use [[Pressure altitude]] during this flight. Set the [[heading bug]] to 250°. Arm the [[autopilot]] and set the initial [[altitude]] to 16,000 feet.

The airfield SPRF, San Rafael has an [[elevation]] of 14,422 feet. That altitude will cause problems during take-off. It takes a lot longer for the aircraft to gain sufficient speed for take-off, also the take-off speed that is needed is higher as you would expect. Perhaps an additional notch of flaps is needed.

Take-off, avoid the bumps (there are plenty) and fly a course of 250°. After about 80 NM you will fly over the radial of NAV1. Intercept the radial towards Arequipa. At a distance of 75 NM towards NAV1 you will have to increase altitude to 19,000 feet.

At a distance of 50 NM towards NAV1 and 118 NM from NAV2 you will see and cross over the mountain [http://en.wikipedia.org/wiki/Nevado_Mismi Nevado Mismi] with an altitude of 18,362 ft. The rains and water on the area to the right until Nevado Mismi will leave towards the Atlantic ocean through the Amazon river. Anything to the left and after Nevado Mismi will leave towards the Pacific ocean.

After Nevado Mismi you are tempted to descend. Don't. Just before the airfield is [http://en.wikipedia.org/wiki/Chachani Mt.Chachani] with an altitude of 19,872 feet and to the East is the active volcano [http://en.wikipedia.org/wiki/El_Misti El Misti] with an altitude of 19,101 feet. You can either increase the altitude and fly over the airfield or keep the altitude, even descend and fly between the mountains, your choice depends on the visibility.

Fly using the heading bug and set NAV1 to [[ILS]] 109.7 with a radial of 93.2°. We will land at airfield [http://en.wikipedia.org/wiki/Rodr%C3%ADguez_Ball%C3%B3n_International_Airport SPQU, Rodriguez ballon], that has an elevation of 8,405 feet. There is a reason this airfield has just one ILS. The area South-West of the airfield is below 11,405 feet and is safe to navigate.

Position the aircraft in front of the runway at an altitude of 11,405 feet, catch the [[glidescope]] at a distance of 9.5 NM and land your aircraft. After landing and parking your aircraft crawl into the tower to look around.

Happy flying!

* October 2011 by [[User:PH-JBO|PH-JBO]]. Published [[FlightGear_Newsletter_March_2012|Newsletter May 2012]].

===Airports and coordinates===
[[Image:SPQU-001.png|thumb|left|pre - landing]]
[[Image:World-SPRF.png|thumb|right|Latitude: -14.267 Longitude: -70.467]]
* [[SPRF|SPRF - San Rafael]] - [http://assistenza.larasrl.net/brisa/fgfs/suggested_flights/SPRF.pdf chart]
* [[SPQU|SPQU - Rodriguez Ballon]] - [http://assistenza.larasrl.net/brisa/fgfs/suggested_flights/SPQU.pdf chart]

required scenery tile: ftp://ftp.sunsite.org.uk/sites/ftp.flightgear.org/flightgear-ftp/Scenery/w020s80.tar.gz
<div style="clear:both;"></div>

===Suggested aircraft===
[[Image:SPQU-002.png|thumb|right|landed]]
I recomend a powerful jet angine airplane, but not too heavy !
* [[Cessna 550 Citation II]]

<div style="clear:both;"></div>

===FlightGear launching===
fgfs --airport=SPRF --aircraft=Citation-II
<div style="clear:both;"></div>

=Middle East=
==Israel to Jordan over the Dead Sea==
[[Image:LLBS-001.png|thumb|left|take off]]
[[Image:LLBS-002.png|thumb|right|flat land]]
Dead Sea is the lowest water elevation on the Earth. Take off from the Beer-Sheva Teyman airport and head East-North-East. About half way there, after the southern Hebron mountains ridge, there'll be a sharp drop-off down to the Dead Sea --- the lowest exposed point on the Earth.<br/>
<br/>
It's really fun to descend and explore the beautiful coastline. In the real life, you wouldn't like to fly low over this water there of your own will --- while you don't need a life vest in the Dead Sea, the water is pretty caustic there for one's eyes. Once you're done marvelling the sights, continue on to the Queen Alia airport.
<div style="clear:both;"></div>
===Airports and coordinates===
[[Image:LLBS-006.png|thumb|left|landing in the dead sea, notice the altitude !]]
[[Image:OJAI-007.png|thumb|right|landing at Queen Alia Intl.]]
[[Image:World-LLBS.png|thumb|right|Latitude: 31.29037800 Longitude: 34.71922500]]
* [[LLBS|LLBS - Teyman]] - [http://assistenza.larasrl.net/brisa/fgfs/suggested_flights/LLBS.pdf chart]
* [[OJAI|OJAI - Queen Alia Intl]] - [http://assistenza.larasrl.net/brisa/fgfs/suggested_flights/OJAI.pdf chart]

required scenery tile: ftp://ftp.sunsite.org.uk/sites/ftp.flightgear.org/flightgear-ftp/Scenery/e030n30.tar.gz
<div style="clear:both;"></div>

===Suggested aircraft===
[[Image:LLBS-003.png|thumb|left|approaching the dead sea]]
[[Image:LLBS-004.png|thumb|right|there is also a minor airport]]
* [[Albatross]]

<div style="clear:both;"></div>

===FlightGear launching===
fgfs --airport=LLBS --aircraft=Albatross
<div style="clear:both;"></div>

=Europe=
==Edinburgh to Oban==
See article: [[Edinburgh to Oban]].

==Oban to Prestwick==
The west coast of Scotland offers some stunning scenery and a number of small airfields and airports to land at on both the mainland and the small islands the dot the coast. The distances between the various airfields are quite small, and some of the runways are on the short side, so STOL or GA aircraft are ideal. The tour suggested here follows part of a microlight trip I made this month, photos of which can be found [http://www.nanjika.co.uk/photos/gigha/ here].

Oban airport (EGEO) lies on the west coast of Scotland, and offers fuel (both AVGAS and AVTUR) and a North/South tarmac runway.

From Oban it is just a 10 minute flight west to the grass airfield of Glenforsa (EG45), on the north-east coast of the island of Mull. Due to the hills and water channel, this airfield often gets quite strange wind patterns - the weather can be perfect in Oban, but much gustier and windier at Glenforsa. At times the windsocks at either end of the runway can blow in completely opposite directions!

Some distance north of Oban lie the airfields of the Isle of Skye (EG57) and Plockton (EG81). This is an excellent place from which to explore the mountains of the Isle of Skye, known as the Cuilins.

Heading south from Oban, one can follow the coast to the island of Jura, with it's distinctive hills (The Paps of Jura). From Jura one can head south to the island of Islay with its numarous malt whisky distilleries (many of which are modelled in FG). Islay Airport (EGPI) has extensive runways. From Islay head north east to the tiny island of Gigha. Despite it's small size, it too has an airfield (EG44), though the FG version is tarmac rather than grass.

From Gigha head east over the Mull of Kintyre, to the hilly isle of Arran, then north east to the Isle of Bute. Both islands have very small grass airstrips, which are sadly not present in FG. From Bute you can head south east to Prestwick International (EGPK), famous for being the only place Elvis touched down in the UK, and a fine place to end our tour.
*Published in [[FlightGear Newsletter July 2011]] by [[User:Stuart|Stuart]]

== Edinburgh to Dundee ==
Edinburgh Airport (EGPH) is located to the West of the city of Edinburgh and south of the Forth rail and road bridges. You'll need the w010n50 scenery and the latest set of objects from the scenery DB which include a number of models for the Edinburgh area.

From Edinburgh Airport, head north and circle the bridges, then follow the coast on the south eastwards past Edinburgh (watch out for the Castle!) and to East Lothian and Bass Rock - a volcanic plug in the sea that is host to thousands of sea-birds.

There are a number of sights in East Lothian, include a distillery.

If you wish to continue your tour, head back North, crossing the Firth of Forth to the Kingdom of Fife. Head approximated North West, tracking towards the Perth VOR (110.4). There is an airport here (Perth Scone, EGPT), but instead we will now track out on the 090 radial and pick up the ILS to Dundee Airport (108.10) landing beside the sea.
* September 2006 by [[User:Stuart|Stuart]].

==Austrian alps soaring==
Discover the Austrian alps with a glider. [[Pinzgauer Spaziergang]]

== Sightseeing the Alps in a C172 ==
This tour will guide you to many of the most famous mountains, valleys, glaciers, snowfields, winter and summer vacation areas, etc. in the European Alps. In addition there are several hints to visit nearby areas of interest. On the tour you will visit Switzerland, Italy and France.
See the detailed description in: http://www.emmerich-j.de/FGFS/Alp-flying.pdf (mirrored to https://beni.hallinger.org/fgfs.nobackup/Alp-Tour-Jomo/)
*February 2011 by [[User:Jomo|Jomo &dagger;]].;

* The scenic trip does take about 2 hours.
* Skyvector route: https://skyvector.com/?ll=46.464097146192884,7.159790050777061&chart=301&zoom=6&fpl=%20LSZC%204700N00836E%204647N00840E%204642N00836E%204637N00835E%204634N00823E%204634N00812E%204633N00809E%204634N00805E%204634N00801E%204631N00803E%204624N00746E%204619N00745E%204618N00753E%204614N00752E%204612N00749E%204609N00747E%204603N00746E%204601N00745E%204600N00738E%204555N00724E%204555N00712E%204553N00703E%204547N00652E%204549N00649E%204604N00634E%20LSGG

== Salzburg to Zell am See via Hallstatt ==
[[File:LOWS-LOGO-LOWZ.jpg|thumb|The route for Salzburg to Zell am See via Hallstatt]]
This flight will bring you around a very scenic region of the austrian alps.
* [https://skyvector.com/?ll=47.5666119817603,13.107925427128999&chart=301&zoom=3&fpl=N0100A040%20LOWS%204735N01311E%204736N01339E%204733N01340E%204733N01343E%204735N01343E%204738N01355E%204727N01357E%20LOWZ SkyVector route]
* Suggested plane: C172 or C182
* This is VFR only, so pick suitable weather. There are no usable navaids for this trip.
* Trip takes around 1 hr. air time at 120 KTAS.
* Fly at an altitude of about 4000ft or so (the entire trip can be done at that altitude safely).

* Start ''Salzburg (LOWS)''; follow the Autobahn in the valley to the southeast until you reach the fork at ''Golling''. To the south you see the Mountains of the ''Tennengebirge''.
* Alternatively (and I recommned that), you can also deviate sothwest around ''Mt. Untersberg'' (1972m, hosting germanys longest and deepest cave, the ''Riesending'') to visit lake ''Königsee'' and watch the peaks of the ''Steinernes Meer'' (the dominant and very famous ''Mt. Watzmann'', 2713m!) and north side of the ''Mt. Hochkönig''. You need to climb to at least 6200ft to cross the final ridge at the end of the lake valley. After crossing, descend to 4000ft, follow the valley and fly north at the next valley to rejoin the route.
* Turn east and follow the valley and hills, aim for a prominent V-shaped incision at the end. Fly through there and you suddenly break out at the lake ''Hallstätter See'', a fjord-like lake 125m deep.
* Follow the ''Hallstätter See'' to the south, on its western shore is the famous town of ''Hallstatt''. At the mountain to your right (north of Hallstatt) is a very old settlement dating back to the late bronce age (Hallstattzeit, c. 800–450 BC) and there was a very important Salt mine dating back to that time and important archeological grave findings.
Looking south you can see the ''Dachstein'' (2995 m), a high peak hosting the ''Hirlatzhöhle'', with 120km the twentiest longest and with 1560m sixth deepest cave of planet earth.
* Follow the valley east bend to ''Obertraun'', and then north over the ''Koppenpass'' and the town of ''Bad Aussee''.
* From ''Bad Aussee'', fly straight to the lakes ''Grundlsee'' and ''Toplitzsee'' (you can't see the latter yet).
* Between the two, turn southwards and aim for the reservoir lake ''Salza'' which is in the sharp incision you can see to the south.
* After passing the reservoir, you may try to get down to ''Niederoblarn'' (LOGO) to the southeast, it's a short airfield.
* From there, follow the railway in the valley of Enns westwards, LOWZ is about 20 minutes away. On your right side watch out for the other side of the ''Dachstein'' and the town of ''Schladming'', which lies down in the valley next the rocky hills with the river flowing trough. Look for the railway and the river Enns.
* Behind ''Schladming'' (south of Mt. ''Dachstein'', approximately halfway of the distance LOGO/LOWZ) the valley will widen a bit again, featuring a rocky mountain in the middle of the valley. Continue to follow the railway and river bending nortwest arond the small mountain.
* Near the bigger town of ''Radstadt'' the valley will open significantly. Follow west, heading for the next town ''Altenmark'' at the end of the opening.
* The railway will bend north at ''Altenmark'' and soon join the Autobahn A10/E55. This is the point we need to go southwest and follow the next valley.
* The valley leads us westward to the Town of ''St. Johann/Pongau''. probably around the middle of the valley you can spot the prominent ''Mt. Hochkönig'' (2941m) northwest of ''St. Johann'' and the ''Tennengebirge'' to its right.
* Once reaching ''St. Johann'', continue to follow the next big valley west-southwest.
* After about 16 miles you will reach ''Zell am See'' (LOWZ) where we will land after around one hour flight time in total. Beware this is a short field.

== Zell am See to Innsbruck via Mt. Venediger ==
[[File:LOWZ-LOWI.jpg|thumb|The route for Zell am See to Innsbruck]]
This flight will bring you to two of the core peaks of the Alpenhauptkamm.
* [https://skyvector.com/?ll=47.201656734623775,12.160079968084839&chart=301&zoom=3&fpl=N0100A120%20LOWZ%20LOWZ%204708N01241E%204708N01221E%204706N01214E%204710N01152E%204724N01150E%20LOWI SkyVector route]
* Suggested plane: C172 or C182
* This is VFR only, so pick suitable weather. There are no usable navaids for this trip.
* Trip takes around 45 minutes air time at 110 KTAS.
* Climb to at an altitude of about 10000ft or so after starting from [[:File:Lowz-parking.jpg|Zell am See]].

* After starting fly into the valley southwest over the town of ''Kaprun''. Maybe you need to circle a bit to gain altitude, near the mountains we need at least about 10000ft!
* Follow the valley until you overfly two lakes (''Stausee Wasserfallboden'' and ''Moorboden''). To your left you can see ''Mt. Großes Wiesbachhorn'' (3564m).
* The end of the valley goes over into a flank of the ''Großglockner'' which is near to the south. Follow the west bend of the valley end and fly over the lakes ''Tauernmoossee'' and ''Weißsee''. After you climb out of the valley, you already should see the peak of ''Mt. Venediger'' on the front left. Aim to the saddle right of its peak.
* You then fly that direction over several valleys that go from south to north, until you hit the very big valley that bend from south to west. The ridgeline right of that valley is the border between the Austrian states Tirol and Salzburg. Follow the valley up to the ''Venediger'', passing the ''Mt. Sandebentörl'' (2751m), still aiming for the saddle.
* Shortly after you reach the end of the valley and need to overfly the saddle with the glacier ''Venedigerkees'' behind it. The ridgeline is again the border between Tirol and Salzburg. Directly south of the ''Venedigerkees'' is the pyramid of ''Mt. Venediger''.
* Follow ''Venedigers'' ridge to the southwest, skip the first valley and overfly the next ridge.
* From here you can deviate into the valley north and visit the ''Krimmler Wasserfälle'', and from there west trough the main valley.
* If you instead follow the planned route westwards, aim to the peak of ''Mt. Zillerplattenspitze'' (3148m) with the small lake ''Eissee'' to its south flank which you should already see. This is a little hard to get right, but don't fly directly into the big valley but aim right to the second row mountain peaks at about 280 heading.
* Overfly the ridge with ''Eissee'' and follow the valley from there nothwest with the reservoir ''Zillergründl'' and ''Mt. Reichenspitze'' (3303m) to its right; until you reach the town ''Mayrhofen'' where the current valley meets the ''Zillertal'' valley. You also should start to descend now to about 3500ft with a rate of roughly -1000fpm.
* From ''Mayrhofen'' follow the ''Zillertal'' valley north and when reaching the ''Inntal'' valley near the town ''Jenbach'', Innsbruck Airport is a few minutes to the west. If you like, you can divert north at ''Jenbach'' to visit ''Achensee'', and even continue further north to land at Munich via lake ''Tegernsee'' or via the Isartal over ''Bad Tölz''.

== Crossing the alps ==
[[File:ED02-LIPB.jpg|thumb|The route for Fuessen to Bolzano]]
This trip brings us from germany via austria to italy, crossing the alps, visiting the famous castle Neuschwanstein and Mt. Zugspitze, germanys highest peak.
* [https://skyvector.com/?ll=47.068251080980836,10.959411633048108&chart=301&zoom=5&fpl=N01204735N01041E%204734N01045E%204729N01042E%204726N01046E%204724N01054E%204712N01054E%204704N01058E%204656N01103E%204655N01106E%204653N01109E%204650N01110E%204648N01113E%204638N01110E%20LIPB SkyVector route]
* Suggested plane: C172 or C182
* This is VFR only, so pick suitable weather and time (I suggest to start with the first light/sunrise).
* There are no helpful navaids for this trip, but Bolzano NDB: 362 BZO may serve as a final guidance.
* Trip takes around 45 minutes air time at 120 KTAS.

* Start at ED02 Fuessen, climb to about 3000 and head southeast to visit castle Neuschwanstein, south of the Forgensee.
* After looking at the castle (challenge: fly close around behind it), we start climbing to 3500 and aim southwestish and cross over from germany to austria.
* Fly into the big valley directing south. East of Reutte start climbing 500fpm to 6000 and follow the railway in the valley to the southeast.
* Once the valley opens significantly, you can see the famous mountain Zugspitze (germanys highest peak, 2962 m) to the front.
* Head southwards around the Mt. Gartnerwand over town Ehrwald and fly between the two small peaks over the Marienbergjoch mountain pass, 1789m/5870ft (between Mt. Wanning and Mt. Marienberg; challenge: who can make it with the least altitude?).

* After overflying the second mountain, to the south comes a new valley called Ötzal where you fly into.
* Follow that valley all the way to the south and slowly climb to at least 8600 now (300fpm or so). Note overflying Längenfelden, where the dominant valley joins from the east with the river Fischbach, halfaway the leg; this looks similar to the end, but isn't.
* Follow the valley until it starts to branch in all different directions at the end (over the town of Sölden and Zwieselstein).
* We follow the Southeast main branch and then turn quickly to a smaller valley branching off directly eastwards (look for the mountain pass road).
* That brings us to the mountain pass of the Timmelsjoch and is the place where we cross over to Italy.

* After passing, we can descend to 2500 or so, following the terrain. Follow the valley and its river "Passer" southeast, and follow its bend to the south.
* Follow the valley and make a nice turn around Mt. Kolbenspitze's east ridge, over San Leonardo, still following the Passer river now southwards.
* Where the valley hits the next big valley "Etschtal", is a bigger famous city called Merano. From there we follow the River Etsch and the Autobahn (highway) to the south and are soon approaching the somewhat hidden airport of Bolzano (LIPB) after an estimated time of somewhat under one hour at 120 knots.

From here you can also continue more to the south to Trento (LIDT, total FT ~1:00) or Verona (LIPX, total FT ~1:20) - just follow the river Etsch to the south! Venezia is also not far away, just ~30 minutes/62nm to the east of Verona.

==Grenoble Le-Versoud==

[[Image:LFLG.jpg|800px]]

France : '''LFLG''' ( Grenoble Le-Versoud ) airport : border of Alps
*P.A.F. home base [http://equipe-flightgear.forumactif.com/ link]
*Scenery : http://clemaez.fr/flightgear/flightgearfrance_05062011.tar.gz
*Texture : http://clemaez.fr/flightgear/pattentextures_maj24082011.tar.gz

* Take-off from Grenoble le Versoud (LFLG). Head south following the general direction of the Alps. Bearing left (East) will take you into high alpine territory, while towards the West lie the plains of the Rhône valley. Once you reach the Mediterranean coast, follow it to land in Marseilles (LFML), Nice (LFMN), or another smaller airport serving the French Riviera.
*Published in [[Custom France Scenery]].

==Gulf of Finland sightseeing tour==
Take a VFR sightseeing tour over the Gulf of Finland from Helsinki to Tallinn! Estonia's landmarks are all recent additions, while Helsinki was one of the first cities to have original models in the scenery model database.

Take off from the smaller EFHF airfield in Helsinki, or try your luck fighting the virtual traffic at Vantaa, and head toward the port of Helsinki. Look for the Hartwall Arena, the Pasila tower, the railway station and the Olympic Stadium along the way. Make your way out over the Gulf flying just west of south - a heading of 190 should set you up nicely for a sightseeing tour of Tallinn. Try to come in from the west and do a sweeping left turn over the capital of Estonia, looking out for the Swissotel, Olympic Hotel, the Television tower, and other important landmarks in the capital city of Estonia. Make sure you look out for St. Olaf's Church, the tallest building in the capital city. Make your way over the Ulemiste Jarv (lake) to land on runway 09 at Tallinn's main airport.

If you desire, you can do a touch-and-go at Tallinn and set your course southeastward, landing at Tartu Airport, which is also modelled in FlightGear.

The distance between Helsinki and Tallinn is about 50 miles or 80 kilometres, while Tartu is twice the distance from Tallinn at 100 miles/160 kilometres. Fly a heading of 135 to get to Tartu from Tallinn.
*Published in [[FlightGear Newsletter October 2010]] by [[User:Statto|Statto]].

==Azores==
[[Image:LPLA-001.png|thumb|left|take off]]
[[Image:LPLA-002.png|thumb|right|approaching island]]
The [http://en.wikipedia.org/wiki/Azores Azores], set in the middle of the Atlantic ocean, has had many names. Fortunate Isles, the Blue Islands, the Islands of Tin and Silver, the Islands of the Seven Cities. We can add, the Islands of Amazing Sights and Flights.

Our flight is to celebrate the amazing views FlightGear can give us.

Start your plane at [[Lajes Field]] (LPLA). This once was an emergency landing site for the [[Space Shuttle]] so you will have plenty of room to take off.
We will have to fly an odd pattern. The reason for that: if you don't fly too high (stick around 3000 while you can) you will have some amazing views.

Next, fly towards and over LPPD. Look out the window and enjoy the view. Then head out towards LPHR. If you feel LPHR coming near, look out the window good, you might have to pull your plane up.

Happy flying!
*Published in [[FlightGear Newsletter August 2011]] by [[User:PH-JBO|PH-JBO]]

===Airports and coordinates===
[[Image:LPPD-001.png|thumb|left|over the island]]
[[Image:LPPD-002.png|thumb|right|landing]]

* [[LPLA|LPLA - Lajes Field]] - [http://assistenza.larasrl.net/brisa/fgfs/suggested_flights/LPLA.pdf chart]
* [[LPPD|LPPD - Ponta del gada]] - [http://assistenza.larasrl.net/brisa/fgfs/suggested_flights/LPPD.pdf chart]

required scenery tile: http://mirrors.ibiblio.org/pub/mirrors/flightgear/ftp/Scenery-v2.4.0/w020n30.tgz
<div style="clear:both;"></div>

===Suggested aircraft===
* [[Cessna 550 Citation II]]

===FlightGear launching===
fgfs --airport=LPLA --aircraft=Citation-II
<div style="clear:both;"></div>

== Canary Islands Trip ==

An archipelago in the middle of the Atlantic sea, stunning beauty where you won't expect it. Seven islands, seven continents, thats what the canarian people say. And it's true, you will face seven totally different islands and nine different airports.
Take off from the largest one, GCLP, at the main island Gran Canaria. Leave the beautiful island heading to the west, and land at GCTS, the southern airport at Tenerife. Enjoy the view on Spains highest mountain, the glaciered Teide, when flying to La Gomera (GCGM), one of the greenest islands there. Master the short runway, and enjoy the view, before taking the challenge and approach El Hierro (GCHI). A short runway, with cliffs and rocks on both ends will cause you to sweat. From this island, which was claimed to be the western end of the world in medieval times, you'll turn to the beautiful and wild island of La Palma (GCLA). The next approach will be historical, because you are approaching the notorious Tenerife North (GCXO). Yes, I am serious, you will face that airport, where the worst civil plane crash ever took place. But you needn't worry, if you got that far, you will do this approach as easy as any other. The longest flight on your trip will take you to the eastern island, Lanzarote (GCRR). Take a look at the volcanic-red mountains, the vineyards, and the beaches. You want more beaches?? Depart to the south-west, fly over the small island of Los Lobos, and land in the holiday-paradise Fuerteventura. Enjoy dunes, bays, and very nice long beaches, before you finally touch down in Fuerteventura (GCFV). You want to stay? Okay, let's taxi to a parking position, and cut off the engines. If you still want more, fly back to Gran Canaria's GCLP, where we started our trip.

Custom scenery: [[Canary Islands Custom Scenery]] / direct source: https://github.com/D-ECHO/Canarys

=== Suggested Aircraft ===

* small civil aircraft, such as the Cessna Skylane, Skyhawk, or Citation
* small airliners, like the Q400, the ATR72, the CRJ200, or similar

Route by Flycanarias

<gallery>

</gallery>

==Gibraltar==
[[Image:LEMG-010.png|thumb|left|take off]]
[[Image:LEMG-011.png|thumb|right|just after take off]]
Traffic lights turn red, gates are closed. The only busy main road to the peninsula is closed and all the cars and trucks are waiting patiently. Waiting for a train to pass? No. Waiting for a plane to pass since the main road crosses a busy runway.

On both sides water and being crossed by a busy main road can only be one runway: [http://en.wikipedia.org/wiki/Gibraltar_Airport Gibraltar airport]!

One would expect an ILS installed on such a tricky runway but no, you will have to guess where it is and how far away it is. Not even an ADF points to it.

Take off from LEMG (Malaga). Go South-West and find the runway of LXGB somewhere to the right of the rock. Happy guessing!
*Published in [[FlightGear Newsletter September 2011]] by [[User:PH-JBO|PH-JBO]]
<div style="clear:both;"></div>

===Airports and coordinates===
[[Image:LEMG-013.png|thumb|left|search for this]]
[[Image:LEMG-015.png|thumb|right|landing]]

* [[LEMG|LEMG - Malaga]] - [http://assistenza.larasrl.net/brisa/fgfs/suggested_flights/LEMG.pdf chart]
* [[LXGB|LXGB - Gibraltar]] - [http://assistenza.larasrl.net/brisa/fgfs/suggested_flights/LXGB.pdf chart]

required scenery tile: http://mirrors.ibiblio.org/pub/mirrors/flightgear/ftp/Scenery-v2.4.0/w010n30.tgz
<div style="clear:both;"></div>

===Suggested aircraft===
* [[Piper Aerostar]]

===FlightGear launching===
fgfs --airport=LEMG --aircraft=aerostar700 --adf1=300 --nav1=300:117.80
<div style="clear:both;"></div>

=Asia=
==Khorog, Tajikistan==
[[File:Fw190HinduKush.jpeg|left|thumb|Approaching a bank of snow-covered mountains in the south of the Hindu Kush]]
Surrounded by spectacular mountains and nestled in the end of a valley, Khorog Airfield (UT1C) makes an interesting place to land. It can only be approached by flying down the curved valley that snakes in from the North. Flying from here to OPCH (Chitral, Pakistan) at around 500ft AGL all the way is a wonderful way to explore the Hindu Kush mountains.

If you bring a piston engined aircraft, be prepared to adjust the mixture as you climb - at the highest point in the flight, you will be at around 22000ft. Also, don't forget to carry plenty of fuel - there are very few airfields in the Hindu Kush that exist in FlightGear. This is a scenery bug that will hopefully be fixed in the future.

*October 2011 by [[User:Armchair Ace| Armchair Ace]], published in [[FlightGear_Newsletter_January_2012#Suggested_flights| Newsletter January 2012]].
<br>
<br>
<br>
== Central Karakoram range ==
Let's explore one of the highest regions of the planet - the central Karakoram with the densest concentration of mountains of 8000 m and above. We're going to need a good climbing performance for the trip - even the frozen plateau of Baltoro glacier, above which K2 and Gasherbrum V and VI loom, is more than 13,000 ft high.

[[File:Karakoram1.jpg|300px|thumb|left|Circling Gasherbrum I]]

Take off from Skardu airport in Pakistan (OPSD). Skardu has a reasonably long (11,944 ft) runway at just 7,316 ft elevation, so you can take a jet, but for instance the [[De Havilland Canada DHC-6 Twin Otter|Twin Otter]] is more stylish.

South of Skardu lies Deosai park, a famous high plateau, but we turn initially east. There's a chain of lakes which is the Indus river. After about five miles, the Shigar river merges with the Indus. Turn slightly left and follow the Shigar, then follow it into a long and broad lake-filled valley stretching into north-western direction.

Towards the end of the lake, a small tributary river, the Braldu, turns eastward out of the main valley. Follow the Braldu and start climbing (if you haven't done so yet). About 15 miles after turning into the Braldu river valley, two glacier-filled valleys stretch to the north - admire the view!

[[File:Karakoram2.jpg|300px|thumb|right|Heading back into Skardu, Nanga Parbat on the horizon]]

Passing a few lakes, you reach finally Baltoro glacier continuing the river valley stretching eastward. Ever climbing, follow the glacier till you reach some kind of T-junction. The glacier arm reaching north leads to K2 (which sadly isn't really there in Flightgear), but just ahead of you are the still rather impressive peaks of Gasherbrum V, VI and I - circle the range and make some pictures!

A good way back to Skardu is to go about 10 miles sourth from the Gasherbrum peaks, then head due west. To your west, you can see the long valleys fall away from the high ranges, to your right is the still glacier-covered high Karakoram. On a clear day (really good visibility selected) you can see the distinctive peak of Nanga Parbat appearing straight ahead on the horizon. The valley of Skardu is quite a distinctive feature and finding back VFR should not be a problem.

Published in [[FlightGear_Newsletter_April_2012#Suggested_flights| Newsletter April 2012]] by [[User:Thosten|Thosten]].

== The Paro Challenge ==
[[File:The Paro Challenge route.png|thumb|The route to follow in the maze of valleys between Hashimara Air Base (VE44) and Paro airport (VQPR). Created using OpenStreetMap and the Open Topo layer.]]
The challenge consists in flying as fast and as low as possible from Hashimara (VE44) to Paro (VQPR) while navigating a maze of valleys, steep climbs and sharp turns with only one VOR-DME beacon to guide you (it sits on a mountaintop south of Paro airport). You cannot fly on instruments; this is a 100% visual flight.

Spawn at VE44 (Hashimara Air Force Station). Take off in any direction then turn immediately to heading 013 while staying low. You will see the Himalayas appear on the horizon. Follow the valley as it turns 90° left then make a sharp U-turn (180°) to the right. Fly over the bridge, then U-turn left again (160°). Follow the valley and do another U-turn to the right. Take a deep breath for a couple of nautical miles. Climb to 8500ft while heading 080 to pass over the mountain range. Turn slightly to your right (heading 100) and do a steep dive to 4000ft into the valley. Turn left into the second valley (heading 000), which you will need to follow all the way to Paro airport (VQPR), while climbing slowly to the airport elevation of 7500ft. On the way to Paro, you will pass a monastery on your left. If you don't see this monastery, you've lost yourself in the maze; good luck! After this monastery, follow the valley to the left (heading 270), which will force you to turn right after a few nautical miles. The runway will be hidden behind a hill. You can pass over the hill (steep dive on the other side) or fly to the right of it (steep S-turns), your choice.

=== Suggested aircraft ===
The Paro Challenge is a challenge for most aircraft and most pilots. You will probably not succeed on your first attempt; and successive attempts with various aircraft will renew the challenge.

===== Easy =====
[[Cessna 550 Citation II]], [[Pilatus PC-6 Porter|Pilatus PC-6]], [[De Havilland Canada DHC-6 Twin Otter|De Havilland Canada DHC-6]], [[Zivko Edge 540]].

[[De Havilland Mosquito]], Messerschmitt Bf109G, [[Lockheed P-38 Lightning]].

==== Challenging ====
[[Piper PA34-200T Seneca II|Piper Seneca II]], [[Cessna 337G Skymaster|Cessna 337]], [[Antonov An-2]]: keep an eye on your Exhaust Gas Temperature and Cylinder Head Temperature. If you can't lean your mixture, you lose.

Cessna 172, PA-28 or DR-400 with 180hp engines and a light load; [[Cessna 182S]]; Cap 10b. Slower than the above and will require just as much concentration from you, for a longer time.

[[Mikoyan-Gurevich MiG-15|MiG-15]], [[North American F-86 Sabre|F-86F Sabre]], [[Fairchild Republic A-10 Thunderbolt II|A-10 Warthog]]: make high-speed, steep turns while finding your way. Don't black out!

==== Difficult ====
[[JT-5B|JT-5B autogyro]], [[Piper J3 Cub|Piper Super Cub 150hp]]: the Paro challenge takes well over an hour of intense concentration in these unstable aircraft.

Cessna 172, PA-28 or DR-400 with low-power (160hp) engines. You will need to circle several times in the valley during the climb. If you can't lean your mixture, you lose.

[[Boeing 707]], [[Boeing 757-200|757]], [[Tupolev Tu-154B|Tupolev 154]], [[Lockheed Constellation]] if lightly loaded; [[Cessna Citation X]]: Finding your way in these faster aircraft is a challenge. The U-turns before the steep climb are almost impossible without taking shortcuts. The final approach without seeing the runway requires you to control your speed, flaps and landing gear well in advance.

==== Impossible (but you might try to beat them anyway) ====
[[Piper J3 Cub|Piper Cub 65hp]] (cannot climb over 7000ft when fully loaded).

[[Boeing 737-300]] (poor low-speed handling), [[Boeing 787-8 Dreamliner|787]] (bank limiter).

[[Dassault Mirage 2000-5|Mirage 2000]], [[Grumman F-14 Tomcat|F-14B]], [[McDonnell Douglas F-15 Eagle|F-15C]], [[General Dynamics F-16 Fighting Falcon|F-16]]: will either stall or black you out during the sharp turns.

=Africa=
==Ngorngoro==
For this [[VFR]] trip we need a strong machine since we will go up from 4000 to about 10,000 feet and since we are in Africa, Tanzania , what better choice is there as the Cessna 208 Caravan, on wheels. We will take off from HTLM, [http://en.wikipedia.org/wiki/Lake_Manyara Lake Manyara], runway 12 (124.5 deg), that has an elevation of 4150 feet. Hit Shift-B so we don't drop off the runway.
[[File:Map Ngorngoro Crater.jpg|thumb|200px|left|Heightmap with visual reference points]]
We will have to change some settings before we take off. There is no snow where we are so: View=> Rendering Options=> Snow line=> Set to max. (5000M). We need a reasonable clear sky since there are quite a few bumps we could hit: Environment=> Global weather=> METAR source=> Fair weather.

Give full throttle and take off. Bank left and make a full circle so we gain some altitude and make a mental note of the airstrip, since this is the only one nearby. Look at the road West towards the airfield.
You will notice that the airstrip is at the edge of a mountain ridge, the lake to the East is quite a lot lower.

We pass over the airstrip towards lake Manyara and turn left keeping the mountains close to our left side, on an initial course of about 30 deg. We keep the mountains to our left and follow our path, our heading will slowly go from 30 to North and takes about 15 mins. During our path we should slowly gain altitude.
[[File:Ol Doinyo Lengai.jpg|thumb|250px|Mt.Kerimasi (left), Mt.Ol Doinyo Lengai (ahead)]]
On the '''image''' we see two distinct mountains. The nearest is Mt.Kerimasi, a fun place for hang-gliders, and North Mt.Ol Doinyo Lengai, an active volcano. We are heading straight towards [http://en.wikipedia.org/wiki/Ol_Doinyo_Lengai Mt.Ol Doinyo Lengai]. Just before we would collide we take a sharp left turn heading 225. You will see why we need the altitude now.

The mountain ahead, [http://www.ntz.info/gen/n00161.html#id03702 Mt.Embagai], we see does not appear to be anything spectacular. Aim towards it since we have to go over it.
Coming nearer, if you are high enough, 9000 feet, you will see why this mountain is well worth a visit. It is a crater with a lake inside, lake Embagai (Empakaai). Enter the crater and look around, careful not to loose any height since we'll have to get out again, we need about 10 000 feet. Mesmerized we grab our compass and take a course of 225 again. To get out we might skim against a cloud, be careful. If you don't see a way out take a turn again to wait for the clouds to move out of sight.

After you managed to get out of the crater keep on the course of 225 while descending slowly for about 9 mins. There are some bumps to avoid, like Mt.Olmoti we keep to the right and Mt.Losirua on the left.

After a small hill we enter one of the most amazing places in Africa, the [http://en.wikipedia.org/wiki/Ngorongoro_Conservation_Area Ngorngoro Crater], the second biggest crater in the world. A micro climate and amazing wildlife.
Examine the crater and you will notice two lakes, head towards the biggest lake, lake Magadi. When you are above it take a course of 123 to get out of the crater.

After leaving the crater it takes some time before we are near the airstrip again. After about 5 mins we will see a river (left) and a road (right). Follow the road since it will lead us to the airstrip again.

Don't scare the wildebeast!

Notecard:
<tt>
#Fair weather, no snow
#HTLM RW 12 4150 feet
#Course 30 to 0 deg 15 mins, mountains close left
#Head towards /\volcano
#Sharp left turn course 225 deg altitude 9000 feet
#Volcano, lake, 10 000 feet
#Course 225 deg, slow descend 9 min
#Large lake, course 123 deg 5 mins
#River left, road right. Follow road
#Landing 124.5 deg 4150 feet.</tt>

*October 2011 by [[User:PH-JBO|PH-JBO]]. Published in [[FlightGear_Newsletter_December_2011#Suggested_flights | Newsletter December 2011]].
==Kisimayu to Kilimanjaro==
We have to take a big airliner for this trip. The runways are long enough but for this trip we need some altitude and a slow descend.

We park our Big Bird at HCMK, [http://en.wikipedia.org/wiki/Kismayo_Airport Kisimayu], Somalia, near the East coast of Africa. It's unsure what this airfield is used for but it's a long piece of tarmac. I could not find regular flights to and from this airfield, not so strange, there is no lighting, no radio beacons and... no fuel. What you can find is Global Air Rescue that has an air ambulance service based here (with a [http://www.globalairrescue.com/learjet-35.php Learjet 35]).

Our route will be around 425 nm in length. You know your aircraft and know what altitude you will need to fly.

Our destination, HTKJ, [http://en.wikipedia.org/wiki/Kilimanjaro_International_Airport Kilimanjaro], Tanzania, has only one ILS and I have learned, if an airfield has only one ILS there is probably a reason.

Flight Plan (short version):
#HCMK Kisimayu, length 12,177 ft, no navaids near.
#GAR Garissa [[VOR-DME]] freq 115.7 heading 268° dist 169 nm.
#KB Kilimanjaro [[NDB]] freq 393.0 heading 224° dist 258 nm, here is the holding pattern for the Kilimanjaro runway (and there is a [http://en.wikipedia.org/wiki/Mount_Kilimanjaro 19,000 ft] reason for this detour).
#KV Kilimanjaro VOR-DME freq 115.3 heading 70° dist 26 nm.
#HTKJ Kilimanjaro [[ILS]] freq 110.9 runway heading 88° elev 2,900 ft [[AMSL]] length 11,807 ft.

Prepare your flight well to receive amazing views of the landscape during the final steps of the route, if you don't you will discover why some pilots call Kilimanjaro Kill-You-Manjaro.

{{#ev:youtube | KCJi_ZaR8ec}}
Youtube video: Kilimanjaro approach in real, in FG not much different.

*February 2012 by [[User:PH-JBO|PH-JBO]].

=Australia and Oceania=

==Hawai'i==
[[Image:Maui03.jpg|thumb|250px]]
Do you use [[TerraSync]]? If so, try a flight around Hawaii! Take off from PHNL in a light aircraft and head west until you hit Pearl Harbor; a right turn north will take you post the USS Arizona Memorial, and the Punchbowl Crater will be to your right. Or, fly east from PHNL past volcanic craters Diamond Head and Koko Head. If you follow the O'ahu coastline north from Koko Head, you can land at either old World War II airbase Bellows Field (now a wildlife reserve in real life) or at Keahole MCAS.

For a potentially more scenic route, fly east toward Molokai, and stay to the north (left) of the island. The northern part of Molokai features huge sea cliffs and a tiny airstrip on the Kalaupapa peninsula - the peninsula being the only respite from the cliffs. A former leper colony existed near the airstrip!

Also of interest are the volcanoes on Maui and the 'Big Island' of Hawai'i - flying VFR in a small plane from PHTO to PHKO over the plateau between Mauna Kea and Mauna Loa can be a challenge, as you have to take off from sea level, fly through a pass of 6500 feet, and then drop back down to sea level to land! The Hana coast of northern Maui is also a nice flight - a circumnavigation of Haleakala, starting and ending at PHOG, is quite a nice flight.

The islands will be available through the download center with the next major scenery release, but for now, fire up [[TerraSync]] and your favorite VFR aircraft and have a blast.
*Published in [[FlightGear Newsletter September 2010]] by [[User:Statto|Statto]].

== Hawai'i waterfalls tour ==
This flight will let you discover some of the famous Hawai'ian waterfalls, visiting the Islands of Kauai and Oahu.
{{note| Despite the scenery is very nice, the waterfalls are mostly not modeled (as of 5/2024)}}

* [https://skyvector.com/?ll=21.82733715471215,-158.96200561400335&chart=301&zoom=5&fpl=%20PHBK%202211N15938W%202206N15930W%202204N15925W%20LIH%202135N15817W%202138N15802W%202120N15746W%202116N15748W%20PHNL SkyVector route]
* Suggested plane: C172 or C182
* This is VFR only, so pick suitable weather. There are no usable navaids for this trip except the VORTAC LIH 113.500 to cross the sea.
* Trip takes around 90 minutes air time at 110 KTAS.

First part of the trip:
* Start at Parking sands (PHBK), runway 34
* Takeoff, climb to 5000ft and follow the northern coast at about a heading of 030° until you reach Crawlers Ledge (about 8 minutes flight time).
* Turn southeast into the very dominant embayment and watch out for Hanakoa Falls, our first waterfall to visit.
* To your left should be a very dominant valley behind the ridge, featuring a river. Now climb to 6000ft and follow that valley southeastish and visit the famous Weeping wall waterfalls behind the ridge at the end of the valley.
* Bank left slightly (~100° heading), descend to 3000 ft and aim for Wailua waterfalls at the south side of the small hill near the coast (between the two towns).

This concludes the islands waterfalls after about 20 minutes flight.

Now either land at Lihue Airport (PHLI) to your right for a break, or continue the trip and intercept VORTAC LIH 113.500 radial 99/TO. Follow the radial to cross the Kauai Channel until you reach the tip of Oahu Island (the crossing of 63NM takes about 30 minutes at 120 knots. You may also opt to skip and start at PHDH).

* Follow overfly Kawaihapai Airfield (PHDH) and follow the northern coast.
* Shortly you will ovefly a prominent bend from east to nothertheast in the coast, still follow the coast. Note the windfarm appearing to your right ahead.
* Over Waimea (just before the very visible sand beach), turn right and fly to the inland behind (north of) the windfarm. Shortly after passing the wind turbines, look out for Waimea waterfalls.
* Follow the mountains to the southeast of the island and slowly climb to 4000ft (the left side is more rough and scenic).
* North of Diamond Head (a big crater at the south tip of the island) there are several waterfalls (roughly in the middle between Diamond head in the south and Kaneohe in the north), as well as very nice streams coming down the ridge. Also the north side of the ridge is very nice, so consider doing a circle over there.
* Continue south over Diamond head and proceed to land at Honolulu airport (PHNL).

This concludes the trip after about 1:30 hours.

==Brisbane International Airport to Sydney International Airport==
Going from Brisbane International Airport to Sydney International Airport. You should have a heading of about 203. Might take sometime to arrive to this section. Maybe 10-30 mins into the flight. Can't really say but don't give up, you will eventually reach this section of the flight. '''''Your eyes will be rewarded!''''' .

[[Image:Fgfs-screen-020.png|200px]]
[[Image:Fgfs-screen-016.png|200px]]
[[Image:Fgfs-screen-012.png|200px]]
*Published in [[FlightGear Newsletter April 2011]] by [[User:Vin|Vin]]

=Antarctica=

{{Suggested}}

[[Category:Lists]]

File:The Paro Challenge route.png

2024-08-23T02:33:37Z

Circumn: Uploaded own work with UploadWizard

=={{int:filedesc}}==
{{Information
|description={{en|1=The route to follow in the maze of valleys between Hashimara Air Base (VE44) and Paro airport (VQPR). Created using OpenStreetMap and the Open Topo layer.}}
|date=2024-08-23
|source={{own}}
|author=[[User:Circumn|Ludovic Brenta]]
|permission=
|other versions=
}}

=={{int:license-header}}==
{{self|cc-by-sa-4.0}}

[[Category:Maps]]

Suggested Flights

2024-08-22T21:44:33Z

Circumn: /* Easy */

[[FlightGear]] has accurate and realistic terrain. Here are some interesting places where you can do virtual sight seeing.

If you are starting with [[FGRun]] - the FlightGear launcher - you can enter the [[airport]] id and select the runway on the appropriate screen in the startup wizard.
If you are starting from the command line you can use the options: <tt>--airport=ABCD</tt> and <tt>--runway=12L</tt>.

*Remember to give a look at the [[Suggested Airports]] page, where you can find a comprehensive list of high quality airports in FlightGear.
*If you enjoy these flights, please consider recording a flight and posting a link to it at the [[Suggested Prerecorded Flights]] page.

'''Remove before flight!''' 

Before you start flying into one of the suggested flights, you should add both the terrain and the Objects to you FlightGear installation; This is well explained on the [[Howto: Install scenery|installing scenery]] page.

p.s. charts are generated using FlightGear data only.

This page includes the flights described on the [http://www.flightgear.org/places.html main website] and the suggested flights from the newsletters. It can serve as an archive for suggested flights from future [[FlightGear Newsletter|newsletters]] or can give a flight if creativity is low that month.

{{TOC limit|3}}

=Cross Continentals or World Tour=

* [[Breitling DC-3 World Tour]][[File:Rect17.png|thumbnail]]
* [[Flying the Hump]]

=North America=
==Round Valley Airport==
[[Image:O09-002.png|thumb|left|right after take off]]
[[Image:O09-003.png|thumb|right|Valley]]
Covalis, CA. The airport is at the West edge of a 7 mile across valley.<BR/>
The predominant wind is a cross wind. Take-offs to the west (if they use the full runway length) often have to fly between 2 small hills and over another valley while gaining altitude. Most pilots take off to the west.<BR/>
It is a paved runway and quite long. It was designated as an emergency recovery field during the Cold War and was used twice that I know of by military aircraft that could not take off again from the field.
<div style="clear:both;"></div>

===Airports and coordinates===
{{Location map | USA
| caption = Latitude: 39.790156 Longitude: -123.266403
| lat_deg = 39.790156
| lon_deg = -123.266403
}}

* [[O09|O09 - Round valley]] - [http://assistenza.larasrl.net/brisa/fgfs/suggested_flights/O09.pdf chart]

required scenery tile: ftp://ftp.sunsite.org.uk/sites/ftp.flightgear.org/flightgear-ftp/Scenery/w120n40.tar.gz
<div style="clear:both;"></div>

===Suggested aircraft===
I have tried this trip using a p38, quite powerful airplane
* [[Lockheed-P38|P38]]
<div style="clear:both;"></div>

===FlightGear launching===
fgfs --airport=O09 --runway=28 --aircraft=p38
<div style="clear:both;"></div>

==Half Moon Bay==
[[Image:KHAF-001.png|thumb|left|right after take off]]
[[Image:KHAF-002.png|thumb|right|Bridge]]
Start at [[KHAF|Half Moon Bay]], Runway 30, with 32km visibility; Takeoff in the C172 and climb to 1000 feet, then continue north over the water, near the shoreline. Look out the right window frequently. Fly up the coast, overfly the Golden Gate Bridge, continue around the top of the peninsula past downtown SF, then fly on to [[KSFO]] for a landing. We now have lots to see.

If you cannot see the runway in the default 172, you must be flying too high or too slowly. You can start by practicing a bit with a good setup:

'''fgfs --offset-distance=1.5 --altitude=500 --vc=70'''

As soon as FlightGear starts, cut the power to 1500 rpm and drop two notches of flap. Maintain 70 kt. Now, pick your landing spot (a bit down the runway) and try to hold it in the same spot on your windshield. If your landing spot starts moving down, you are too high, and should cut another 100 rpm; if it starts moving up, you are too low, and should add another 100 rpm. Adjust the nose to keep your speed at 70 kt all the way down until you're right above the numbers, then cut power to idle, drop the last notch of flaps, flare, and land.
<div style="clear:both;"></div>

===Airports and coordinates===
[[Image:KHAF-003.png|thumb|left|surroundings]]
[[Image:World-KHAF.png|thumb|right|Latitude: 37.513333 Longitude: -122.501111]]
* [[KHAF|KHAF - Half Moon Bay]] - [http://assistenza.larasrl.net/brisa/fgfs/suggested_flights/KHAF.pdf chart]

no required scenery tile.
<div style="clear:both;"></div>

===Suggested aircraft===
[[Image:KSFO-001.png|thumb|left|Before landing]]
Use the default c172 airplane
* [[Cessna C172P]]
<div style="clear:both;"></div>

===FlightGear launching===
fgfs --airport=KHAF --runway=30 --visibility=32000 --aircraft=c172
<div style="clear:both;"></div>
===Author===
April 2006 [[User:Hellosimon|Hellosimon]], format and extended by [[User:Francescobrisa|Francescobrisa]]

==Hell's Canyon==
[[Image:25U-001.png|thumb|left|right after take off]]
[[Image:25U-004.png|thumb|right|Valley]]
Hell's Canyon, Imnaha, OR. This airport is located just west of "Hell's Canyon National Park" which has the Snake River running through it.<br/>
Supposedly it's a 5500 foot drop from the top of the canyon to the river.<BR/>
The airport is located on the brink of this canyon.

See the remarks on the airport page (click on the airport id) ... DOWNDRAFTS, SHEER DROP IN TERRAIN, LIVESTOCK, etc. Don't go here on your first solo x-country. :-)
<div style="clear:both;"></div>

===Airports and coordinates===
[[Image:25U-005.png|thumb|left|Landing]]
[[Image:World-25U.png|thumb|right|Latitude: 45.427861 Longitude: -116.693889]]
* [[25U|25U - Round valley]] - [http://assistenza.larasrl.net/brisa/fgfs/suggested_flights/25U.pdf chart]

required scenery tile: ftp://ftp.sunsite.org.uk/sites/ftp.flightgear.org/flightgear-ftp/Scenery/w120n40.tar.gz
<div style="clear:both;"></div>

===Suggested aircraft===
[[Image:25U-006.png|thumb|left|Landing 2]]
I have tried this trip using a pilatus PC-9M, powerful airplane
* [[PC-9M|PC-9M]]
<div style="clear:both;"></div>

===FlightGear launching===
fgfs --airport=25U --aircraft=PC-9M
<div style="clear:both;"></div>

==Crater Lake National Park Tour==
[[Image:64s-003.png|thumb|left|Approaching the lake]]
[[Image:64s-002.png|thumb|right|Direction 40 degrees]]
Prospect, OR.<br/>

Take off and fly at a heading of about 40 degrees until you cross the first distinct ridge in front of you. (several minutes of flight in the navion ... just climb as fast as you can, it will be a close squeek to get over :-)<br/>

Once you clear the ridge and can see beyond it, turn right and fly a heading of about 70 degrees. You should see two shallow peaks off in the distance. Head right between these -- they are the two sides of the crater. As you get closer the shape of the crater will come into view. There's a lake there in real life, hopefully it will be there in flight gear too before long.
<div style="clear:both;"></div>

===Airports and coordinates===
[[Image:64s-001.png|thumb|left|Leaving the 64S airfield]]
[[Image:World-64S.png|thumb|right|Latitude: 42.743183 Longitude: -122.488092]]
* [[64S|64S - Prospect State]] - [http://assistenza.larasrl.net/brisa/fgfs/suggested_flights/64S.pdf chart]

required scenery tile: ftp://ftp.sunsite.org.uk/sites/ftp.flightgear.org/flightgear-ftp/Scenery/w130n40.tgz
<div style="clear:both;"></div>

===Suggested aircraft===
[[Image:64s-004.png|thumb|left|Lake view 1]]
[[Image:64s-005.png|thumb|right|Lake view 2]]

* [[Ryan_Navion|Navion]]
<div style="clear:both;"></div>

===FlightGear launching===
fgfs --airport=64S --runway=02 --aircraft=navion
<div style="clear:both;"></div>

==Grand Canyon Tour==
[[Image:Grand_Canyon_Tour_4.jpg|700px|frameless|center]]
Being a special place, there are also special flight rules for VFR traffic around the Grand Canyon. There are multiple no-fly-zones set up and VFR traffic is only allowed to fly via the designated corridors. If you want to fly realistically, avoid these zones in FlightGear as well, following for example the [https://skyvector.com/?ll=36.18649251415492,-112.52223157994264&chart=230&zoom=5&fpl=%20KGCN%20VPGCF%20VPGCG%20VPGCD%20VPGCC%20VPGCA%203608N11252W%203609N11309W%201Z1%201G4%203AZ5 route shown here. (skyvector link)]

This flight takes you from KGCN, the Grand Canyon National Park airport, to 3AZ5, a small airfield called Hualapai located south of the Grand Canyon. Departing from KGCN, fly north-west bound to reach the canyon. From there, either follow the route shown on skyvector above, or fly visually through the canyon westbound towards 1Z1, Grand Canyon Bar Ten Airstrip. From there on, continue flying westward to 1G4. Called Grand Canyon West, 1G4 also marks about the western end of the canyon. To get to your destination 3AZ5, continue along the southern rim, flying eastward now. Shortly after leaving the breathtaking valley behind you, you will already reach your destination. Land and let your engine and your mind cool down from the special views :)

===Gallery===
<gallery>
Grand_Canyon_Tour_2.jpg
Grand_Canyon_Tour_3.jpg
Grand_Canyon_Tour_1.jpg
</gallery>

===Airports===
* KGCN - Grand Canyon National Park Airport - [https://www.aopa.org/destinations/airports/KGCN/details aopa.org]
* 1Z1 - Grand Canyon Bar Ten Airstrip - [https://www.airnav.com/airport/1Z1 airnav.com]
* 1G4 - Grand Canyon West - [https://www.airnav.com/airport/1G4 airnav.com]
* 3AZ5 - Hualapai - [https://www.airnav.com/airport/3AZ5 airnav.com]

===Suggested aircraft===
Most VFR aircraft with sufficiently big windows will serve the purpose, for example:
*[[Cessna C172P]]
*[[Optica]]
*[[Ryan_Navion]]
If you are more interested in flying helicopters, the [[Eurocopter EC130 B4]] with the Grand Canyon Helicopters livery might be for you.

===Links===
*[https://www.nps.gov/grca/learn/nature/upload/sfra.pdf Chart of the Grand Canyon special airspace, published by the National Park Service]
*[http://www.swaviator.com/html/issueJJ99/canyon.html An article about flying close to the Grand Canyon]
*[https://www.aopa.org/news-and-media/all-news/2017/april/flight-training-magazine/road-trip-grand-canyon AOPA Flight suggestion]

==Ranger Creek Airport==
[[File:21w-1.jpg|500px|center|Waiting for departure at Ranger Creek]]
Ranger Creek Airport is located in Greenwater, Washington, USA. Being wedged into the bottom of a steep canyon, you'll definitely need to be on your toes to get in and out of there. Switch on Advanced Weather and Live Data to experience what the winds can do to you in real life!
===Airports and coordinates===
* [[21W|21W - Ranger Creek]] - [http://www.airnav.com/airport/21W airnav.com]
===Gallery===
<gallery>
Ranger_Creek1.jpg|Departing between the mountains
Ranger_Creek_2.jpg|Looking back towards the airfield
Ranger_Creek_3.jpg|Downwind for approach back to Ranger Creek
</gallery>
===Suggested aircraft===
For this flight, the Piper PA-18 SuperCub is suggested, this is included in the [[Piper J3 Cub]] package

==Mount Rainier Tour==
[[Image:WA20-002.png|thumb|left|The mountain from far away]]
[[Image:WA20-006.png|thumb|right|external view]]
Eatonville, WA. Start out at Swanson Airport in Eatonville, WA. Take off and fly a heading of about 90 degrees. You will need to fly for 5-10 minutes before the mountain comes into view. Be patient if you don't see it right away, it will dwarf everything in it's vicinity.
<div style="clear:both;"></div>
===Airports and coordinates===
[[Image:World-WA20.png|thumb|right|Latitude: 46.87588502 Longitude: -122.25733500]]

* [[WA20|WA20 - Swanson]] - [http://assistenza.larasrl.net/brisa/fgfs/suggested_flights/WA20.pdf chart]

required scenery tile: ftp://ftp.sunsite.org.uk/sites/ftp.flightgear.org/flightgear-ftp/Scenery/w130n40.tgz
<div style="clear:both;"></div>

===Suggested aircraft===
[[Image:WA20-007.png|thumb|left|external near view]]
[[Image:WA20-009.png|thumb|right|external near view]]
* [[mosquito]]

<div style="clear:both;"></div>

===FlightGear launching===
fgfs --airport=WA20 --aircraft=mosquito
<div style="clear:both;"></div>

==Death Valley Tour==
[[Image:L06-001.png|thumb|left|in the air]]
[[Image:Furnace-creek.jpg|thumb|left|real life view of Furnace Creek Airfield]]
[[Image:L06-002.png|thumb|right|in the air]]
Furnace Creek, CA. This starts you right in the middle of Death Valley which runs north & south. If you head south about 15 miles you'll hit the lowest point in the USA, 282 feet (86 meters) below sea level.
<div style="clear:both;"></div>
===Airports and coordinates===
[[Image:World-L06.png|thumb|right|Latitude: 36.46451100 Longitude: -116.88139422]]
* [[L06|L06 - Furnace Creek]] - [http://assistenza.larasrl.net/brisa/fgfs/suggested_flights/L06.pdf chart]

required scenery tile: ftp://ftp.sunsite.org.uk/sites/ftp.flightgear.org/flightgear-ftp/Scenery/w120n30.tgz
<div style="clear:both;"></div>

===Suggested aircraft===
[[Image:L06-003.png|thumb|left|in the air]]
[[Image:L06-004.png|thumb|right|in the air]]
* [[rallye-MS893]]
<div style="clear:both;"></div>

===FlightGear launching===
fgfs --airport=L06 --aircraft=rallye-MS893
<div style="clear:both;"></div>

==Utah==
!!! Work in progress !!!<BR/>

Escalante Muni Airport, Escalante, UT. This airport is east and a bit north of Bryce Canyon National park. If you head mostly south and a bit east you'll eventually hit the Grand Canyon. It is sandwiched between the Dixie National forest to the north and the Grand Staircase-Escalante National Monument to the south. There should be interesting stuff to see no matter which direction you head.
<div style="clear:both;"></div>
===Airports and coordinates===
[[Image:World-1L7.png|thumb|right|Latitude: 37.75054400 Longitude: -111.57578300]]
* [[1L7|1L7 - Escalante Muni]] - [http://assistenza.larasrl.net/brisa/fgfs/suggested_flights/1L7.pdf chart]

required scenery tile: ftp://ftp.sunsite.org.uk/sites/ftp.flightgear.org/flightgear-ftp/Scenery/w120n30.tgz
<div style="clear:both;"></div>

===Suggested aircraft===

<div style="clear:both;"></div>

===FlightGear launching===
fgfs --airport=1L7 --aircraft=pa18
<div style="clear:both;"></div>

==Lake County Airport (CO)==
[[Image:KLXV-001.png|thumb|left|Adjust mixture !]]
[[Image:KLXV-002.png|thumb|right|The terrain will be covered by snow]]
Lake County Airport, Leadville, CO. This airport is at an elevation of 9927 making it a bit of a challenge to get into and out of with a standard C172.<BR/>
Make sure you lean out your engine before taking off and read up on density altitude before you try this one in real life.
<div style="clear:both;"></div>
===Airports and coordinates===
[[Image:KLXV-003.png|thumb|left|The airport]]
[[Image:World-KLXV.png|thumb|right|Latitude: 39.22812500 Longitude: -106.31835600]]
* [[KLXV|KLXV - Lake Co]] - [http://assistenza.larasrl.net/brisa/fgfs/suggested_flights/KLXV.pdf chart]

required scenery tile: ftp://ftp.sunsite.org.uk/sites/ftp.flightgear.org/flightgear-ftp/Scenery/w110n30.tgz
<div style="clear:both;"></div>

===Suggested aircraft===
[[Image:KLXV-004.png|thumb|left|I like this panorama]]
[[Image:KLXV-005.png|thumb|right|The nearby lake]]
* [[Cessna C172P]]

<div style="clear:both;"></div>

===FlightGear launching===
[[Image:KLXV-006.png|thumb|left|Landing...]]
fgfs --airport=KLXV --aircraft=c172p
<div style="clear:both;"></div>

==Caribbean - Saint Martin and St. Kitts==
[[Image:TNCM-003.png|thumb|left|just after the take off]]
[[Image:TNCM-004.png|thumb|right|some nearby island]]
Pilots of the Caribbeans is an informal FlightGear community of users who fly around the small Caribbean islands, many of which have custom scenery and improved landclass data. (For details see [[Pilots of the Caribbean]])<BR/>

[[TNCM|Princess Juliana International Airport (TNCM)]] at the isle of Saint Martin, is one of the most popular airports in FlightGear. In large part due to the custom objects and land cover. However, St. Marten is only one of several detailed airports in the region - and, while the approach for TNCM is one of the most memorable in the whole world, the land cover for St. Kitts and Nevis makes it a lovely place to fly.

British Airways, US Airways and American Airlines, among others, all fly into St. Kitts' [[TKPK|Robert L. Bradshaw International Airport (TKPK)]] in real life.

Take off from TKPK in a [[Piper_J3_Cub|Piper Cub]] and make a northward, clockwise circle of the island. Start your descent on the east side of the island, and focus on the small hill which separates the north from the south. Start hugging the coast near the beach and look to the west - as soon as the railroad heads to the southwest, you're about ready to turn for final. Make your right hand turn for final and taxi to the terminal.

If you want to fully explore this whole country, take off in a Beaver, which has a little more speed, and fly a figure eight. Take off from TKPK and circle the airport to the north like in the Cub. Then instead of landing, perform a touch-and-go and turn left over the boat terminal and make for the west coast of Nevis. Enjoy the beauty of the south coast of St. Kitts before circling Nevis. Over Nevis, you have several options - cut your flight short and land at [[TKPN]] on the island of Nevis, complete the "figure eight" by heading back to TKPK, or check your fuel and head east across the Caribbean to Antigua (which does not have custom land cover).<BR/>
<BR/>
Check out the [[Pilots of the Caribbean]] page, for further informations.
<div style="clear:both;"></div>
===Airports and coordinates===
[[Image:World-TNCM.png|thumb|right|Latitude: 18.040953 Longitude: -63.108900]]

* [[TNCM|TNCM - Princess Juliana International Airport]] - [http://assistenza.larasrl.net/brisa/fgfs/suggested_flights/TNCM.pdf chart]
* [[TKPK|TKPK - Robert L. Bradshaw International Airport]] - [http://assistenza.larasrl.net/brisa/fgfs/suggested_flights/TKPK.pdf chart]
* [[TKPN|TKPN - Vance Winkworth Amory Intl]] - [http://assistenza.larasrl.net/brisa/fgfs/suggested_flights/TKPN.pdf chart]
others interesting airports in the area:
* [[TFFF|TFFF - Le Lamentin]] - [http://assistenza.larasrl.net/brisa/fgfs/suggested_flights/TFFF.pdf chart]
* [[MDPP|MDPP - Gregorio Luperon Intl]] - [http://assistenza.larasrl.net/brisa/fgfs/suggested_flights/MDPP.pdf chart]
* [[TJSJ|TJSJ - Luis Munoz Marin Intl]] - [http://assistenza.larasrl.net/brisa/fgfs/suggested_flights/TJSJ.pdf chart]
* [[FMEE|FMEE - St Denis Gillot]] - [http://assistenza.larasrl.net/brisa/fgfs/suggested_flights/FMEE.pdf chart]
* [[TFFG|TFFG - Grand Case]] - [http://assistenza.larasrl.net/brisa/fgfs/suggested_flights/TFFG.pdf chart]

required scenery tile:
* ftp://ftp.sunsite.org.uk/sites/ftp.flightgear.org/flightgear-ftp/Scenery/w070n10.tgz
* ftp://ftp.sunsite.org.uk/sites/ftp.flightgear.org/flightgear-ftp/Scenery/w080n10.tgz
* ftp://ftp.sunsite.org.uk/sites/ftp.flightgear.org/flightgear-ftp/Scenery/w080n20.tgz
* ftp://ftp.sunsite.org.uk/sites/ftp.flightgear.org/flightgear-ftp/Scenery/w090n20.tgz
<div style="clear:both;"></div>

===Suggested aircraft===
[[Image:TNCM-005.png|thumb|left|amazing]]
[[Image:TNCM-006.png|thumb|right|landing]]
* [[Piper_J3_Cub|Piper Cub]]
<div style="clear:both;"></div>

===FlightGear launching===
fgfs --airport=TKPK --aircraft=Cub
<div style="clear:both;"></div>
===Author===
[[FlightGear Newsletter January 2011]] by [[User:Statto|Statto]], format and extended by [[User:Francescobrisa|Francescobrisa]].

==Friedman Memorial Airport (Idaho)==
[[Image:KSUN-001.png|thumb|left|take off]]
[[Image:KSUN-002.png|thumb|right|nearby]]
Friedman Memorial Airport, Hailey, Idaho. This airport is nestled in a valley surrounded by significant terrain. It's one that shows up quite often in accident investigations.
<div style="clear:both;"></div>
===Airports and coordinates===
[[Image:World-KSUN.png|thumb|right|Latitude: 43.51223900 Longitude: -114.30376100]]
* [[KSUN|KSUN - Friedman Mem]] - [http://assistenza.larasrl.net/brisa/fgfs/suggested_flights/KSUN.pdf chart]

required scenery tile: ftp://ftp.sunsite.org.uk/sites/ftp.flightgear.org/flightgear-ftp/Scenery/w120n40.tgz
<div style="clear:both;"></div>

===Suggested aircraft===
[[Image:KSUN-003.png|thumb|left|landing]]
[[Image:KSUN-004.png|thumb|right|landing]]
* [[FK9MK2]]
<div style="clear:both;"></div>

===FlightGear launching===
fgfs --airport=KSUN --aircraft=fk9mk2
<div style="clear:both;"></div>

== Wyoming - Grand Teton ==
Jackson Hole (KJAC) airport is located at around 6,400ft right next to the Teton range of mountains. The Tetons rise straight out of the plains, gaining over 5,000ft in 2 miles.

You will need the w120n40 scenery.

Tower frequency at KJAC is 118.07. Due to the high altitude, you will need to lean non-turbocharged piston aircraft before take-off. Don't forget that take-off distances will also be longer.

After take-off head to the North East. Grand Teton is the highest of the three peaks that rise straight from the flat-lands. Follow the line of mountains to the East, passing over Jenny Lake. After a couple of miles you will reach a huge lake. The large bulk of a mountain to the East is Mount Moran.

The Teton Mountain range is surprisingly thin - really just a string of mountains running SW-NE. Flying fast jets down the steep valleys is recommended.
* September 2006 by [[User:Stuart|Stuart]].

== Virginia Eastern Shore, Chesapeake Bay-Bridge Tunnel Sightseeing ==
[[Image:KTGI-001.png|thumb|left|before take off]]
[[Image:KTGI-002.png|thumb|right|right after take off]]

Take a short VFR trip from Tangier Island to view the famous Chesapeake Bay Bridge-Tunnel connecting Cape Charles to Cape Henry. Depart historic Tangier Island (KTGI) situated in the Chesapeake Bay and land at Norfolk International Airport (KORF), Norfolk, Virginia. The scenic character of the flight is enhanced by leaving the island at dusk. The flight is both scenic and challenging. Frequently, when flying with real weather, you will have a steady wind blowing across the bay. Starting out quiet Tangier and arriving at busy, glittering Norfolk International (KORF) gives the flight some contrast.

'''fgfs --airport=KTGI --runway=20 --timeofday=dusk'''

Before leaving Tangier: Set your altimeter to the prevailing barometric temperature. Set your communications radio to the Norfolk Intl. (KORF) ATIS frequency of 127.150 MHz to listen for weather reports in the destination area. Set your navigation radio to 112.20 MHz to pick up the Cape Charles (CCV) VOR. Set your heading bug to the runway heading, 200.

Takeoff straight, flying the runway heading. Climb to 2000ft and maintain.

Shortly, you should see the VOR assigned to NAV1 display receive a steady signal (the OFF flag will disappear). The DME should also settle down and display the distance to the Cape Charles VOR station. The flight to CCV will be about 26 nautical miles. As you fly, it will show your airspeed and time to arrival. It should take about ten minutes.

Turn the OBS knob until the VOR displays the TO flag and 190 degrees, the heading you should now turn to.

Fly south from Tangier, crossing an expanse of water, about ten miles until you see the Virginia Eastern Shore. You'll come upon the grass airstrip of Chance (VA89) a few minutes out from Tangier. Beyond are two flashing tower beacons. You may catch a glimpse of Weirwood/Kellam (W08) on the ocean shore, recognizable by two crossing dirt strips.

If you look carefully, you may see the little white building that is the Cape Charles VOR station. As you fly over VOR the flag will change from TO to FROM and the needle will deflect. Do not try to follow the needle. Wait until you are past the VOR. As you cross the VOR station, you should see a highway slanting across your path toward the south west. Turn to follow this highway. You'll come across a lone tower with beacon along the roadside. You'll see an access road stretching from the tower complex to the main road.

If the sky conditions permit, you may try your hand at wayfinding by following the road. If visiblity is poor, set the VOR to 180 degrees to parallel the road to the end of the peninsula. Or you can continue to fly outbound from the VOR on 190 by maintaining the same heading. The VOR needle should return to center with the FROM flag displaying. This will put you west of the bridge with a good view and the option to turn towards KORF near the initial approach fix. If you follow the highway you will need to overfly the airport, but if you stay on the 190 heading, you will be in a position to make a straight in landing.

As you fly down the peninsula you'll pass Cherrystone, Eagle's Nest, Scott and Bull Farm grass airstrips. Bull Farm is the last strip before the mouth of the Chesapeake. Just past Scott Farm you should see the first glimmer of the northern leg of the bridge. The grass strips can be very difficult to see.

As you reach the end of the peninsula, be careful to avoid the tower on Fisherman's Island at the north end of the north leg of the bridge (Note the bridge is not modeled by FlightGear...but I hope to work up one eventually). Next comes the north middle leg. Turn right a few degrees to follow the south middle leg. Watch as the deck plunges beneath the waves to allow ships to navigate the north and south channels.

As Cape Henry approaches, you'll see the Norfolk International airport to the right and the southern leg of the bridge touching the shore.

If you intend to land at KORF, you will want to start your approach soon. Otherwise, you may continue to follow the bridge to the end. Make the approach to KORF by contacting the tower for vectors. Or use the ILS.

This is a good flight to practice VOR flying on. It is a very straight flight path to the VOR requiring little adjustment and there are no other VORs in the area to confuse you.
*June 2006 by [[User:Sek|Sek]].

===Airports and coordinates===
[[Image:World-KTGI.png|thumb|right|Latitude: 37.8250835 Longitude: -75.9976665]]
* [[KTGI|KTGI - Tangier Island]] - [http://assistenza.larasrl.net/brisa/fgfs/suggested_flights/KTGI.pdf chart]
* [[KORF|KORF - Norfolk International]] - [http://assistenza.larasrl.net/brisa/fgfs/suggested_flights/KORF.pdf chart]

required scenery tile: ftp://ftp.sunsite.org.uk/sites/ftp.flightgear.org/flightgear-ftp/Scenery/w80n30.tgz

===Suggested aircraft===
[[Image:KTGI-003.png|thumb|left|surroundings]]
[[Image:KORF-001.png|thumb|right|landing to KORF]]
I have tried this trip using a Seneca II
* [[Piper PA34-200T Seneca II]]
<div style="clear:both;"></div>

===FlightGear launching===
fgfs --airport=KTGI --runway=20 --timeofday=dusk --aircraft=SenecaII
<div style="clear:both;"></div>

==Prince George to Calgary Springbank==
A beautiful flight is from Prince George (CYXS), to Calgary Springbank (CYBW). Route created by reed, which can be seen at {{forum link|t=9772|text=the forums}}
*Published in [[FlightGear Newsletter November 2010]] By [[User:Cael|Cael]].
==Ketchikan to Juneau==
It's cold where we will go so dress up warm and if we are lucky we might see whales during our flight. Don't fly too high to enjoy the amazing views, and there is a small challenge at the end. The runways we will use are long enough for bigger aircraft (7000+). Total length of the trip will be around 245 NM. So, hop in the cockpit of your favourite airliner.

Alaska, here we come! Enjoy!
#Park your aircraft on PAKT, [http://www.borough.ketchikan.ak.us/airport/airport_history.htm Ketchikan International], runway 11. The wind is coming from '''South''', change the weather if needed (SE is ok too).
#Fly North towards [[NDB]] Fredericks Point on 372.0 for 94 NM.
#Fly towards [[NDB]] Five Fingers on 295.0 for 39 NM.
#Fly towards [[NDB]] Gustavus on 219.0 for 77 NM.
#Fly towards [[NDB]] Coghlan Island on 212.0 for 32 NM.
#Set the [[ILS]] on 109.9 and land your aircraft (after 4 NM) on PAJN, [http://www.juneau.org/airport/ Juneau International], runway 08.
If you feel warm after this landing, you just crossed a NORAD microwave site, so that is why.
*October 2011 by [[User:PH-JBO|PH-JBO]] [[FlightGear Newsletter November 2011]]
==Searching Wizard Island==
*USA, Oregon, Klamath County
With one [[VORTAC]] behind our back we do an [[IFR]]/[[VFR]] search of Wizard Island, a mysterious place, a sacred place for native Americans. You might even find the <tt>Old Man of the Lake</tt>.

Don't pull up the map, that would spoil the surprise but I promise '''unique views'''. We will land on a short lawn runway. Terrain [[altitude]] will range from 4,000 to a max of 8,930 feet and down again. Total length of the trip will be about 50 NM. Select your aircraft with care. It must have one working navigational radio (VOR-DME), a strong engine, a strong undercarriage, must be capable of a good climb and a steep descend. I suggest to use Fair weather (Environment=>Global Weather). If needed remove some clouds (View=>Rendering Options=>Slider 3d Clouds to the left).
[[File:Mount Scott.jpg|thumb|250 px|Mount Scott (8,929 feet) just after depart from 2S7 (Two Sierra Seven). Wizard Island is just to the North-West of it.]]
*Park your aircraft on 2S7 (Two Sierra Seven), Chiloguin-State.
*Set [[NAV1]] on 115.9 (Klamath Falls VORTAC) and on radial 323<sup>o</sup> (Magnetic). We are at an [[elevation]] of 4,217 feet. Set QNH. Set heading bug at 275<sup>o</sup> (Magn).
*Take off an fly the course set with the heading bug.
*Intercept the radial.
*Monitor distance and you will find Wizard Island at 50 NM from Klamath Falls. The island has an elevation of 6,673 feet. I suggest a full 360<sup>o</sup> turn, take pictures.
*Set radial 318<sup>o</sup>, keep the same frequency. Do a new radial intercept.
*Try and find the airstrip (3S6, Three Sierra Six, Toketee-State) at 71 NM from Klamath Falls with an elevation of 3,361 feet, runway heading 275<sup>o</sup> (Magn). There are bumps around you should avoid.
*If you are capable of finding the island, finding the airstrip and landing without a crash, in one go..., you are a wizard.

Click [http://en.wikipedia.org/wiki/Crater_Lake this link] '''after''' you have landed so you know what amazing landscape you have seen.

*December 2011 by [[User:PH-JBO|PH-JBO]]. Published [[FlightGear_Newsletter_March_2012|Newsletter March 2012]].

=South America=
==Southern Tip of Chile==
[[Image:Scgz-001.png|thumb|left|right after take off]]
[[Image:Scgz-004.png|thumb|right|Some part of the scenery]]
Gary Carvell: Here is a suggestion for the FlightGear Places to Fly page. I don't have any particular routes, just fly around and enjoy the gorgeous scenery.<BR/>
These three airports are in the same region of the very southern tip of Argentina. This area is a scenic wonderland - a maze of islands, mountains, and ocean channels. Hours of entertainment.<BR/>
SCGZ - Puerto Williams Guardiamarina Zanartu Airport, Chile Located on the north coast of Isla Navarino facing the Beagle Channel. At 55 deg S. longitude, Puerto Williams is considered the southernmost town in the world.<BR/>
SAWH - Ushuaia Islas Malvinas Airport
SAWO - Ushuaia Est Aeronaval Airport
Ushuaia, on the south coast of Isla Grande de Tierra del Fuego, on the the Beagle Channel.
<div style="clear:both;"></div>
===Airports and coordinates===
[[Image:Sawh-004.png|thumb|left|Approaching Ushumaia Malvinas Argentinas]]
[[Image:World-scgz.png|thumb|right|Latitude: -54.931072 Longitude: -67.626261]]

* [[SCGZ|SCGZ - Guardiamarina Zanartu]] - [http://assistenza.larasrl.net/brisa/fgfs/suggested_flights/SCGZ.pdf chart]
* [[SAWH|SAWH - Ushuaia Malvinas Argentinas]] - [http://assistenza.larasrl.net/brisa/fgfs/suggested_flights/SAWH.pdf chart]
* [[SAWO|SAWO - Ushuaia Est Aeronaval]] - [http://assistenza.larasrl.net/brisa/fgfs/suggested_flights/SAWO.pdf chart]
<div style="clear:both;"></div>

===Suggested aircraft===
[[Image:Scgz-002.png|thumb|left|Just left the scgz airport]]
I personally like to fly this area in the [[Consolidated_Aircraft_PBY_Catalina|Catalina]], it's a great sightseeing plane with the advantage that you can take off and land just about anywhere.
* [[Consolidated_Aircraft_PBY_Catalina|Catalina]]
<div style="clear:both;"></div>

===FlightGear launching===
fgfs --airport=SCGZ --aircraft=Catalina
<div style="clear:both;"></div>

==Copacabana to San Rafael over Lake Titicaca==
Bolivia to Peru. This trip will lead you over one of the highest and deepest lakes in the world towards the highest airfield in the world. It a demonstration of a [[IFR]] flight towards a fix and a demonstration how accurate FlightGear simulates air density and the effects it has on aircraft.
[[File:Slcc-sprf.jpg|thumb|200px|left|Flight and fix SLCC to SPRF]]
Place your aircraft on the airfield [http://en.wikipedia.org/wiki/Copacabana,_Bolivia SLCC, Copacabana], with an [[elevation]] of 12,592 feet. FlightGear will show snow all around you but that is not very realistic so let's clean up. View=> Rendering Options=> Snow line=> Set to max. (5,000M).

We will fly towards and land at SPRF. If you would enter SLCC and SPRF in [[Kelpie]] planner you probably would not be able to find SPRF. To find SPRF I am adding an additional VOR-DME station and for a good fix give you another VOR-DME. Try Kelpie planner to plan this route and compare with this suggestion.

Equipment preparation. Set [[NAV1]] to [http://en.wikipedia.org/wiki/Juliaca Juliaca] VOR-DME on 155.55 with a radial of 311° (magnetic). Set [[NAV2]] to Arequipa VOR-DME on 113.7 with a radial of 212°. During our flight we will fly with [[true altitude]] as set with [[QNH]], keep QNH updated. Arm the autopilot with the [[heading bug]] at 311° and an initial altitude of 13,500 feet.

Take off and if you took the wrong RW pull up hard. Take a small tour over [http://en.wikipedia.org/wiki/Titicaca lake Titicaca], see the floating islands and try to find the lost golden treasure. Intercept the nearest radial on NAV1 towards Juliaca (about 311°).

Just before Juliaca is a hill so while on lake Titicaca increase altitude to 14,200 feet, the [[VFR]] part of this trip is over. After passing Juliaca set the radial of NAV1 to 352° and set the altitude to 17,422 feet. We will fly from NAV1 and slowly increase altitude.

At a distance of about 60 NM set the heading bug on the current course. Monitor the distance to NAV1, the radial of NAV2 and the distance to NAV2. At a distance of 74.5 NM to NAV1, a distance of 140.7 NM and at the '''radial''' intercept of NAV2 should be the runway. So, from 60 NM onwards, look outside the window, then at NAV1 and then NAV2 etc.

If you are at 80NM to NAV1 you have missed the airfield but you still won't hit any hills (unless you bank left). Bank right and set the heading bug to 172°. Fly back towards NAV1 and intercept the radial 352° at about 50NM again to repeat the search.

The runway SPRF, San Rafael, has a elevation of 14,422 feet and a heading of 297°/ 117°. Our initial altitude has been set 3,000NM above the RW elevation. That should give sufficient room for navigation.

After you have seen the airfield set the radial of NAV1 to 297°, the heading of the runway (not the course to the runway) as a visual aid. Land on RW 30 (and not on RW 12 unless you are a show-off). Oh, there is a small hill in front of RW 30, just so you know.

Decreasing speed at this altitude can be a bit tricky. The air is thin and does not give much resistance. Next to that, the difference between [[indicated airspeed]] and [[ground speed]] is very noticeable. The ground speed is much higher as the indicated airspeed.

After a successful landing, try to discover the origin of the Amazon river since we are now at the starting point of that trip.
* October 2011 by [[User:PH-JBO|PH-JBO]], published in [[FlightGear_Newsletter_February_2012#Suggested_flights| Newsletter February 2012]].

==Origin of the Amazon River==
[[Image:SPRF-001.png|thumb|left|high altitude]]
[[Image:SPRF-002.png|thumb|right|high altitude]]
Peru. For this [[IFR]] tour (with [[VFR]] parts) we take off from the highest airfield in the world to discover the origin of the [http://en.wikipedia.org/wiki/Amazon_River Amazon river] in South America. I promise spectacular mountains and valleys. The total length of this trip is about 175 NM.

Place your aircraft on the airfield SPRF, San Rafael. FlightGear will show snow all around you but that is not very realistic so let's clean up. View=> Rendering Options=> Snow line=> Set to max. (5,000M).

Equipment preparation: Set [[NAV1]] to [http://en.wikipedia.org/wiki/Arequipa Arequipa] VOR-DME at 113.7 with a radial of 176° (magnetic). Set [[NAV2]] to [http://en.wikipedia.org/wiki/Cusco Cusco] VOR-DME at 114.9 also with a radial of 176°.
Set [[QNH]] and during flight keep correcting it, it's a bad idea to use [[Pressure altitude]] during this flight. Set the [[heading bug]] to 250°. Arm the [[autopilot]] and set the initial [[altitude]] to 16,000 feet.

The airfield SPRF, San Rafael has an [[elevation]] of 14,422 feet. That altitude will cause problems during take-off. It takes a lot longer for the aircraft to gain sufficient speed for take-off, also the take-off speed that is needed is higher as you would expect. Perhaps an additional notch of flaps is needed.

Take-off, avoid the bumps (there are plenty) and fly a course of 250°. After about 80 NM you will fly over the radial of NAV1. Intercept the radial towards Arequipa. At a distance of 75 NM towards NAV1 you will have to increase altitude to 19,000 feet.

At a distance of 50 NM towards NAV1 and 118 NM from NAV2 you will see and cross over the mountain [http://en.wikipedia.org/wiki/Nevado_Mismi Nevado Mismi] with an altitude of 18,362 ft. The rains and water on the area to the right until Nevado Mismi will leave towards the Atlantic ocean through the Amazon river. Anything to the left and after Nevado Mismi will leave towards the Pacific ocean.

After Nevado Mismi you are tempted to descend. Don't. Just before the airfield is [http://en.wikipedia.org/wiki/Chachani Mt.Chachani] with an altitude of 19,872 feet and to the East is the active volcano [http://en.wikipedia.org/wiki/El_Misti El Misti] with an altitude of 19,101 feet. You can either increase the altitude and fly over the airfield or keep the altitude, even descend and fly between the mountains, your choice depends on the visibility.

Fly using the heading bug and set NAV1 to [[ILS]] 109.7 with a radial of 93.2°. We will land at airfield [http://en.wikipedia.org/wiki/Rodr%C3%ADguez_Ball%C3%B3n_International_Airport SPQU, Rodriguez ballon], that has an elevation of 8,405 feet. There is a reason this airfield has just one ILS. The area South-West of the airfield is below 11,405 feet and is safe to navigate.

Position the aircraft in front of the runway at an altitude of 11,405 feet, catch the [[glidescope]] at a distance of 9.5 NM and land your aircraft. After landing and parking your aircraft crawl into the tower to look around.

Happy flying!

* October 2011 by [[User:PH-JBO|PH-JBO]]. Published [[FlightGear_Newsletter_March_2012|Newsletter May 2012]].

===Airports and coordinates===
[[Image:SPQU-001.png|thumb|left|pre - landing]]
[[Image:World-SPRF.png|thumb|right|Latitude: -14.267 Longitude: -70.467]]
* [[SPRF|SPRF - San Rafael]] - [http://assistenza.larasrl.net/brisa/fgfs/suggested_flights/SPRF.pdf chart]
* [[SPQU|SPQU - Rodriguez Ballon]] - [http://assistenza.larasrl.net/brisa/fgfs/suggested_flights/SPQU.pdf chart]

required scenery tile: ftp://ftp.sunsite.org.uk/sites/ftp.flightgear.org/flightgear-ftp/Scenery/w020s80.tar.gz
<div style="clear:both;"></div>

===Suggested aircraft===
[[Image:SPQU-002.png|thumb|right|landed]]
I recomend a powerful jet angine airplane, but not too heavy !
* [[Cessna 550 Citation II]]

<div style="clear:both;"></div>

===FlightGear launching===
fgfs --airport=SPRF --aircraft=Citation-II
<div style="clear:both;"></div>

=Middle East=
==Israel to Jordan over the Dead Sea==
[[Image:LLBS-001.png|thumb|left|take off]]
[[Image:LLBS-002.png|thumb|right|flat land]]
Dead Sea is the lowest water elevation on the Earth. Take off from the Beer-Sheva Teyman airport and head East-North-East. About half way there, after the southern Hebron mountains ridge, there'll be a sharp drop-off down to the Dead Sea --- the lowest exposed point on the Earth.<br/>
<br/>
It's really fun to descend and explore the beautiful coastline. In the real life, you wouldn't like to fly low over this water there of your own will --- while you don't need a life vest in the Dead Sea, the water is pretty caustic there for one's eyes. Once you're done marvelling the sights, continue on to the Queen Alia airport.
<div style="clear:both;"></div>
===Airports and coordinates===
[[Image:LLBS-006.png|thumb|left|landing in the dead sea, notice the altitude !]]
[[Image:OJAI-007.png|thumb|right|landing at Queen Alia Intl.]]
[[Image:World-LLBS.png|thumb|right|Latitude: 31.29037800 Longitude: 34.71922500]]
* [[LLBS|LLBS - Teyman]] - [http://assistenza.larasrl.net/brisa/fgfs/suggested_flights/LLBS.pdf chart]
* [[OJAI|OJAI - Queen Alia Intl]] - [http://assistenza.larasrl.net/brisa/fgfs/suggested_flights/OJAI.pdf chart]

required scenery tile: ftp://ftp.sunsite.org.uk/sites/ftp.flightgear.org/flightgear-ftp/Scenery/e030n30.tar.gz
<div style="clear:both;"></div>

===Suggested aircraft===
[[Image:LLBS-003.png|thumb|left|approaching the dead sea]]
[[Image:LLBS-004.png|thumb|right|there is also a minor airport]]
* [[Albatross]]

<div style="clear:both;"></div>

===FlightGear launching===
fgfs --airport=LLBS --aircraft=Albatross
<div style="clear:both;"></div>

=Europe=
==Edinburgh to Oban==
See article: [[Edinburgh to Oban]].

==Oban to Prestwick==
The west coast of Scotland offers some stunning scenery and a number of small airfields and airports to land at on both the mainland and the small islands the dot the coast. The distances between the various airfields are quite small, and some of the runways are on the short side, so STOL or GA aircraft are ideal. The tour suggested here follows part of a microlight trip I made this month, photos of which can be found [http://www.nanjika.co.uk/photos/gigha/ here].

Oban airport (EGEO) lies on the west coast of Scotland, and offers fuel (both AVGAS and AVTUR) and a North/South tarmac runway.

From Oban it is just a 10 minute flight west to the grass airfield of Glenforsa (EG45), on the north-east coast of the island of Mull. Due to the hills and water channel, this airfield often gets quite strange wind patterns - the weather can be perfect in Oban, but much gustier and windier at Glenforsa. At times the windsocks at either end of the runway can blow in completely opposite directions!

Some distance north of Oban lie the airfields of the Isle of Skye (EG57) and Plockton (EG81). This is an excellent place from which to explore the mountains of the Isle of Skye, known as the Cuilins.

Heading south from Oban, one can follow the coast to the island of Jura, with it's distinctive hills (The Paps of Jura). From Jura one can head south to the island of Islay with its numarous malt whisky distilleries (many of which are modelled in FG). Islay Airport (EGPI) has extensive runways. From Islay head north east to the tiny island of Gigha. Despite it's small size, it too has an airfield (EG44), though the FG version is tarmac rather than grass.

From Gigha head east over the Mull of Kintyre, to the hilly isle of Arran, then north east to the Isle of Bute. Both islands have very small grass airstrips, which are sadly not present in FG. From Bute you can head south east to Prestwick International (EGPK), famous for being the only place Elvis touched down in the UK, and a fine place to end our tour.
*Published in [[FlightGear Newsletter July 2011]] by [[User:Stuart|Stuart]]

== Edinburgh to Dundee ==
Edinburgh Airport (EGPH) is located to the West of the city of Edinburgh and south of the Forth rail and road bridges. You'll need the w010n50 scenery and the latest set of objects from the scenery DB which include a number of models for the Edinburgh area.

From Edinburgh Airport, head north and circle the bridges, then follow the coast on the south eastwards past Edinburgh (watch out for the Castle!) and to East Lothian and Bass Rock - a volcanic plug in the sea that is host to thousands of sea-birds.

There are a number of sights in East Lothian, include a distillery.

If you wish to continue your tour, head back North, crossing the Firth of Forth to the Kingdom of Fife. Head approximated North West, tracking towards the Perth VOR (110.4). There is an airport here (Perth Scone, EGPT), but instead we will now track out on the 090 radial and pick up the ILS to Dundee Airport (108.10) landing beside the sea.
* September 2006 by [[User:Stuart|Stuart]].

==Austrian alps soaring==
Discover the Austrian alps with a glider. [[Pinzgauer Spaziergang]]

== Sightseeing the Alps in a C172 ==
This tour will guide you to many of the most famous mountains, valleys, glaciers, snowfields, winter and summer vacation areas, etc. in the European Alps. In addition there are several hints to visit nearby areas of interest. On the tour you will visit Switzerland, Italy and France.
See the detailed description in: http://www.emmerich-j.de/FGFS/Alp-flying.pdf (mirrored to https://beni.hallinger.org/fgfs.nobackup/Alp-Tour-Jomo/)
*February 2011 by [[User:Jomo|Jomo &dagger;]].;

* The scenic trip does take about 2 hours.
* Skyvector route: https://skyvector.com/?ll=46.464097146192884,7.159790050777061&chart=301&zoom=6&fpl=%20LSZC%204700N00836E%204647N00840E%204642N00836E%204637N00835E%204634N00823E%204634N00812E%204633N00809E%204634N00805E%204634N00801E%204631N00803E%204624N00746E%204619N00745E%204618N00753E%204614N00752E%204612N00749E%204609N00747E%204603N00746E%204601N00745E%204600N00738E%204555N00724E%204555N00712E%204553N00703E%204547N00652E%204549N00649E%204604N00634E%20LSGG

== Salzburg to Zell am See via Hallstatt ==
[[File:LOWS-LOGO-LOWZ.jpg|thumb|The route for Salzburg to Zell am See via Hallstatt]]
This flight will bring you around a very scenic region of the austrian alps.
* [https://skyvector.com/?ll=47.5666119817603,13.107925427128999&chart=301&zoom=3&fpl=N0100A040%20LOWS%204735N01311E%204736N01339E%204733N01340E%204733N01343E%204735N01343E%204738N01355E%204727N01357E%20LOWZ SkyVector route]
* Suggested plane: C172 or C182
* This is VFR only, so pick suitable weather. There are no usable navaids for this trip.
* Trip takes around 1 hr. air time at 120 KTAS.
* Fly at an altitude of about 4000ft or so (the entire trip can be done at that altitude safely).

* Start ''Salzburg (LOWS)''; follow the Autobahn in the valley to the southeast until you reach the fork at ''Golling''. To the south you see the Mountains of the ''Tennengebirge''.
* Alternatively (and I recommned that), you can also deviate sothwest around ''Mt. Untersberg'' (1972m, hosting germanys longest and deepest cave, the ''Riesending'') to visit lake ''Königsee'' and watch the peaks of the ''Steinernes Meer'' (the dominant and very famous ''Mt. Watzmann'', 2713m!) and north side of the ''Mt. Hochkönig''. You need to climb to at least 6200ft to cross the final ridge at the end of the lake valley. After crossing, descend to 4000ft, follow the valley and fly north at the next valley to rejoin the route.
* Turn east and follow the valley and hills, aim for a prominent V-shaped incision at the end. Fly through there and you suddenly break out at the lake ''Hallstätter See'', a fjord-like lake 125m deep.
* Follow the ''Hallstätter See'' to the south, on its western shore is the famous town of ''Hallstatt''. At the mountain to your right (north of Hallstatt) is a very old settlement dating back to the late bronce age (Hallstattzeit, c. 800–450 BC) and there was a very important Salt mine dating back to that time and important archeological grave findings.
Looking south you can see the ''Dachstein'' (2995 m), a high peak hosting the ''Hirlatzhöhle'', with 120km the twentiest longest and with 1560m sixth deepest cave of planet earth.
* Follow the valley east bend to ''Obertraun'', and then north over the ''Koppenpass'' and the town of ''Bad Aussee''.
* From ''Bad Aussee'', fly straight to the lakes ''Grundlsee'' and ''Toplitzsee'' (you can't see the latter yet).
* Between the two, turn southwards and aim for the reservoir lake ''Salza'' which is in the sharp incision you can see to the south.
* After passing the reservoir, you may try to get down to ''Niederoblarn'' (LOGO) to the southeast, it's a short airfield.
* From there, follow the railway in the valley of Enns westwards, LOWZ is about 20 minutes away. On your right side watch out for the other side of the ''Dachstein'' and the town of ''Schladming'', which lies down in the valley next the rocky hills with the river flowing trough. Look for the railway and the river Enns.
* Behind ''Schladming'' (south of Mt. ''Dachstein'', approximately halfway of the distance LOGO/LOWZ) the valley will widen a bit again, featuring a rocky mountain in the middle of the valley. Continue to follow the railway and river bending nortwest arond the small mountain.
* Near the bigger town of ''Radstadt'' the valley will open significantly. Follow west, heading for the next town ''Altenmark'' at the end of the opening.
* The railway will bend north at ''Altenmark'' and soon join the Autobahn A10/E55. This is the point we need to go southwest and follow the next valley.
* The valley leads us westward to the Town of ''St. Johann/Pongau''. probably around the middle of the valley you can spot the prominent ''Mt. Hochkönig'' (2941m) northwest of ''St. Johann'' and the ''Tennengebirge'' to its right.
* Once reaching ''St. Johann'', continue to follow the next big valley west-southwest.
* After about 16 miles you will reach ''Zell am See'' (LOWZ) where we will land after around one hour flight time in total. Beware this is a short field.

== Zell am See to Innsbruck via Mt. Venediger ==
[[File:LOWZ-LOWI.jpg|thumb|The route for Zell am See to Innsbruck]]
This flight will bring you to two of the core peaks of the Alpenhauptkamm.
* [https://skyvector.com/?ll=47.201656734623775,12.160079968084839&chart=301&zoom=3&fpl=N0100A120%20LOWZ%20LOWZ%204708N01241E%204708N01221E%204706N01214E%204710N01152E%204724N01150E%20LOWI SkyVector route]
* Suggested plane: C172 or C182
* This is VFR only, so pick suitable weather. There are no usable navaids for this trip.
* Trip takes around 45 minutes air time at 110 KTAS.
* Climb to at an altitude of about 10000ft or so after starting from [[:File:Lowz-parking.jpg|Zell am See]].

* After starting fly into the valley southwest over the town of ''Kaprun''. Maybe you need to circle a bit to gain altitude, near the mountains we need at least about 10000ft!
* Follow the valley until you overfly two lakes (''Stausee Wasserfallboden'' and ''Moorboden''). To your left you can see ''Mt. Großes Wiesbachhorn'' (3564m).
* The end of the valley goes over into a flank of the ''Großglockner'' which is near to the south. Follow the west bend of the valley end and fly over the lakes ''Tauernmoossee'' and ''Weißsee''. After you climb out of the valley, you already should see the peak of ''Mt. Venediger'' on the front left. Aim to the saddle right of its peak.
* You then fly that direction over several valleys that go from south to north, until you hit the very big valley that bend from south to west. The ridgeline right of that valley is the border between the Austrian states Tirol and Salzburg. Follow the valley up to the ''Venediger'', passing the ''Mt. Sandebentörl'' (2751m), still aiming for the saddle.
* Shortly after you reach the end of the valley and need to overfly the saddle with the glacier ''Venedigerkees'' behind it. The ridgeline is again the border between Tirol and Salzburg. Directly south of the ''Venedigerkees'' is the pyramid of ''Mt. Venediger''.
* Follow ''Venedigers'' ridge to the southwest, skip the first valley and overfly the next ridge.
* From here you can deviate into the valley north and visit the ''Krimmler Wasserfälle'', and from there west trough the main valley.
* If you instead follow the planned route westwards, aim to the peak of ''Mt. Zillerplattenspitze'' (3148m) with the small lake ''Eissee'' to its south flank which you should already see. This is a little hard to get right, but don't fly directly into the big valley but aim right to the second row mountain peaks at about 280 heading.
* Overfly the ridge with ''Eissee'' and follow the valley from there nothwest with the reservoir ''Zillergründl'' and ''Mt. Reichenspitze'' (3303m) to its right; until you reach the town ''Mayrhofen'' where the current valley meets the ''Zillertal'' valley. You also should start to descend now to about 3500ft with a rate of roughly -1000fpm.
* From ''Mayrhofen'' follow the ''Zillertal'' valley north and when reaching the ''Inntal'' valley near the town ''Jenbach'', Innsbruck Airport is a few minutes to the west. If you like, you can divert north at ''Jenbach'' to visit ''Achensee'', and even continue further north to land at Munich via lake ''Tegernsee'' or via the Isartal over ''Bad Tölz''.

== Crossing the alps ==
[[File:ED02-LIPB.jpg|thumb|The route for Fuessen to Bolzano]]
This trip brings us from germany via austria to italy, crossing the alps, visiting the famous castle Neuschwanstein and Mt. Zugspitze, germanys highest peak.
* [https://skyvector.com/?ll=47.068251080980836,10.959411633048108&chart=301&zoom=5&fpl=N01204735N01041E%204734N01045E%204729N01042E%204726N01046E%204724N01054E%204712N01054E%204704N01058E%204656N01103E%204655N01106E%204653N01109E%204650N01110E%204648N01113E%204638N01110E%20LIPB SkyVector route]
* Suggested plane: C172 or C182
* This is VFR only, so pick suitable weather and time (I suggest to start with the first light/sunrise).
* There are no helpful navaids for this trip, but Bolzano NDB: 362 BZO may serve as a final guidance.
* Trip takes around 45 minutes air time at 120 KTAS.

* Start at ED02 Fuessen, climb to about 3000 and head southeast to visit castle Neuschwanstein, south of the Forgensee.
* After looking at the castle (challenge: fly close around behind it), we start climbing to 3500 and aim southwestish and cross over from germany to austria.
* Fly into the big valley directing south. East of Reutte start climbing 500fpm to 6000 and follow the railway in the valley to the southeast.
* Once the valley opens significantly, you can see the famous mountain Zugspitze (germanys highest peak, 2962 m) to the front.
* Head southwards around the Mt. Gartnerwand over town Ehrwald and fly between the two small peaks over the Marienbergjoch mountain pass, 1789m/5870ft (between Mt. Wanning and Mt. Marienberg; challenge: who can make it with the least altitude?).

* After overflying the second mountain, to the south comes a new valley called Ötzal where you fly into.
* Follow that valley all the way to the south and slowly climb to at least 8600 now (300fpm or so). Note overflying Längenfelden, where the dominant valley joins from the east with the river Fischbach, halfaway the leg; this looks similar to the end, but isn't.
* Follow the valley until it starts to branch in all different directions at the end (over the town of Sölden and Zwieselstein).
* We follow the Southeast main branch and then turn quickly to a smaller valley branching off directly eastwards (look for the mountain pass road).
* That brings us to the mountain pass of the Timmelsjoch and is the place where we cross over to Italy.

* After passing, we can descend to 2500 or so, following the terrain. Follow the valley and its river "Passer" southeast, and follow its bend to the south.
* Follow the valley and make a nice turn around Mt. Kolbenspitze's east ridge, over San Leonardo, still following the Passer river now southwards.
* Where the valley hits the next big valley "Etschtal", is a bigger famous city called Merano. From there we follow the River Etsch and the Autobahn (highway) to the south and are soon approaching the somewhat hidden airport of Bolzano (LIPB) after an estimated time of somewhat under one hour at 120 knots.

From here you can also continue more to the south to Trento (LIDT, total FT ~1:00) or Verona (LIPX, total FT ~1:20) - just follow the river Etsch to the south! Venezia is also not far away, just ~30 minutes/62nm to the east of Verona.

==Grenoble Le-Versoud==

[[Image:LFLG.jpg|800px]]

France : '''LFLG''' ( Grenoble Le-Versoud ) airport : border of Alps
*P.A.F. home base [http://equipe-flightgear.forumactif.com/ link]
*Scenery : http://clemaez.fr/flightgear/flightgearfrance_05062011.tar.gz
*Texture : http://clemaez.fr/flightgear/pattentextures_maj24082011.tar.gz

* Take-off from Grenoble le Versoud (LFLG). Head south following the general direction of the Alps. Bearing left (East) will take you into high alpine territory, while towards the West lie the plains of the Rhône valley. Once you reach the Mediterranean coast, follow it to land in Marseilles (LFML), Nice (LFMN), or another smaller airport serving the French Riviera.
*Published in [[Custom France Scenery]].

==Gulf of Finland sightseeing tour==
Take a VFR sightseeing tour over the Gulf of Finland from Helsinki to Tallinn! Estonia's landmarks are all recent additions, while Helsinki was one of the first cities to have original models in the scenery model database.

Take off from the smaller EFHF airfield in Helsinki, or try your luck fighting the virtual traffic at Vantaa, and head toward the port of Helsinki. Look for the Hartwall Arena, the Pasila tower, the railway station and the Olympic Stadium along the way. Make your way out over the Gulf flying just west of south - a heading of 190 should set you up nicely for a sightseeing tour of Tallinn. Try to come in from the west and do a sweeping left turn over the capital of Estonia, looking out for the Swissotel, Olympic Hotel, the Television tower, and other important landmarks in the capital city of Estonia. Make sure you look out for St. Olaf's Church, the tallest building in the capital city. Make your way over the Ulemiste Jarv (lake) to land on runway 09 at Tallinn's main airport.

If you desire, you can do a touch-and-go at Tallinn and set your course southeastward, landing at Tartu Airport, which is also modelled in FlightGear.

The distance between Helsinki and Tallinn is about 50 miles or 80 kilometres, while Tartu is twice the distance from Tallinn at 100 miles/160 kilometres. Fly a heading of 135 to get to Tartu from Tallinn.
*Published in [[FlightGear Newsletter October 2010]] by [[User:Statto|Statto]].

==Azores==
[[Image:LPLA-001.png|thumb|left|take off]]
[[Image:LPLA-002.png|thumb|right|approaching island]]
The [http://en.wikipedia.org/wiki/Azores Azores], set in the middle of the Atlantic ocean, has had many names. Fortunate Isles, the Blue Islands, the Islands of Tin and Silver, the Islands of the Seven Cities. We can add, the Islands of Amazing Sights and Flights.

Our flight is to celebrate the amazing views FlightGear can give us.

Start your plane at [[Lajes Field]] (LPLA). This once was an emergency landing site for the [[Space Shuttle]] so you will have plenty of room to take off.
We will have to fly an odd pattern. The reason for that: if you don't fly too high (stick around 3000 while you can) you will have some amazing views.

Next, fly towards and over LPPD. Look out the window and enjoy the view. Then head out towards LPHR. If you feel LPHR coming near, look out the window good, you might have to pull your plane up.

Happy flying!
*Published in [[FlightGear Newsletter August 2011]] by [[User:PH-JBO|PH-JBO]]

===Airports and coordinates===
[[Image:LPPD-001.png|thumb|left|over the island]]
[[Image:LPPD-002.png|thumb|right|landing]]

* [[LPLA|LPLA - Lajes Field]] - [http://assistenza.larasrl.net/brisa/fgfs/suggested_flights/LPLA.pdf chart]
* [[LPPD|LPPD - Ponta del gada]] - [http://assistenza.larasrl.net/brisa/fgfs/suggested_flights/LPPD.pdf chart]

required scenery tile: http://mirrors.ibiblio.org/pub/mirrors/flightgear/ftp/Scenery-v2.4.0/w020n30.tgz
<div style="clear:both;"></div>

===Suggested aircraft===
* [[Cessna 550 Citation II]]

===FlightGear launching===
fgfs --airport=LPLA --aircraft=Citation-II
<div style="clear:both;"></div>

== Canary Islands Trip ==

An archipelago in the middle of the Atlantic sea, stunning beauty where you won't expect it. Seven islands, seven continents, thats what the canarian people say. And it's true, you will face seven totally different islands and nine different airports.
Take off from the largest one, GCLP, at the main island Gran Canaria. Leave the beautiful island heading to the west, and land at GCTS, the southern airport at Tenerife. Enjoy the view on Spains highest mountain, the glaciered Teide, when flying to La Gomera (GCGM), one of the greenest islands there. Master the short runway, and enjoy the view, before taking the challenge and approach El Hierro (GCHI). A short runway, with cliffs and rocks on both ends will cause you to sweat. From this island, which was claimed to be the western end of the world in medieval times, you'll turn to the beautiful and wild island of La Palma (GCLA). The next approach will be historical, because you are approaching the notorious Tenerife North (GCXO). Yes, I am serious, you will face that airport, where the worst civil plane crash ever took place. But you needn't worry, if you got that far, you will do this approach as easy as any other. The longest flight on your trip will take you to the eastern island, Lanzarote (GCRR). Take a look at the volcanic-red mountains, the vineyards, and the beaches. You want more beaches?? Depart to the south-west, fly over the small island of Los Lobos, and land in the holiday-paradise Fuerteventura. Enjoy dunes, bays, and very nice long beaches, before you finally touch down in Fuerteventura (GCFV). You want to stay? Okay, let's taxi to a parking position, and cut off the engines. If you still want more, fly back to Gran Canaria's GCLP, where we started our trip.

Custom scenery: [[Canary Islands Custom Scenery]] / direct source: https://github.com/D-ECHO/Canarys

=== Suggested Aircraft ===

* small civil aircraft, such as the Cessna Skylane, Skyhawk, or Citation
* small airliners, like the Q400, the ATR72, the CRJ200, or similar

Route by Flycanarias

<gallery>

</gallery>

==Gibraltar==
[[Image:LEMG-010.png|thumb|left|take off]]
[[Image:LEMG-011.png|thumb|right|just after take off]]
Traffic lights turn red, gates are closed. The only busy main road to the peninsula is closed and all the cars and trucks are waiting patiently. Waiting for a train to pass? No. Waiting for a plane to pass since the main road crosses a busy runway.

On both sides water and being crossed by a busy main road can only be one runway: [http://en.wikipedia.org/wiki/Gibraltar_Airport Gibraltar airport]!

One would expect an ILS installed on such a tricky runway but no, you will have to guess where it is and how far away it is. Not even an ADF points to it.

Take off from LEMG (Malaga). Go South-West and find the runway of LXGB somewhere to the right of the rock. Happy guessing!
*Published in [[FlightGear Newsletter September 2011]] by [[User:PH-JBO|PH-JBO]]
<div style="clear:both;"></div>

===Airports and coordinates===
[[Image:LEMG-013.png|thumb|left|search for this]]
[[Image:LEMG-015.png|thumb|right|landing]]

* [[LEMG|LEMG - Malaga]] - [http://assistenza.larasrl.net/brisa/fgfs/suggested_flights/LEMG.pdf chart]
* [[LXGB|LXGB - Gibraltar]] - [http://assistenza.larasrl.net/brisa/fgfs/suggested_flights/LXGB.pdf chart]

required scenery tile: http://mirrors.ibiblio.org/pub/mirrors/flightgear/ftp/Scenery-v2.4.0/w010n30.tgz
<div style="clear:both;"></div>

===Suggested aircraft===
* [[Piper Aerostar]]

===FlightGear launching===
fgfs --airport=LEMG --aircraft=aerostar700 --adf1=300 --nav1=300:117.80
<div style="clear:both;"></div>

=Asia=
==Khorog, Tajikistan==
[[File:Fw190HinduKush.jpeg|left|thumb|Approaching a bank of snow-covered mountains in the south of the Hindu Kush]]
Surrounded by spectacular mountains and nestled in the end of a valley, Khorog Airfield (UT1C) makes an interesting place to land. It can only be approached by flying down the curved valley that snakes in from the North. Flying from here to OPCH (Chitral, Pakistan) at around 500ft AGL all the way is a wonderful way to explore the Hindu Kush mountains.

If you bring a piston engined aircraft, be prepared to adjust the mixture as you climb - at the highest point in the flight, you will be at around 22000ft. Also, don't forget to carry plenty of fuel - there are very few airfields in the Hindu Kush that exist in FlightGear. This is a scenery bug that will hopefully be fixed in the future.

*October 2011 by [[User:Armchair Ace| Armchair Ace]], published in [[FlightGear_Newsletter_January_2012#Suggested_flights| Newsletter January 2012]].
<br>
<br>
<br>
== Central Karakoram range ==
Let's explore one of the highest regions of the planet - the central Karakoram with the densest concentration of mountains of 8000 m and above. We're going to need a good climbing performance for the trip - even the frozen plateau of Baltoro glacier, above which K2 and Gasherbrum V and VI loom, is more than 13,000 ft high.

[[File:Karakoram1.jpg|300px|thumb|left|Circling Gasherbrum I]]

Take off from Skardu airport in Pakistan (OPSD). Skardu has a reasonably long (11,944 ft) runway at just 7,316 ft elevation, so you can take a jet, but for instance the [[De Havilland Canada DHC-6 Twin Otter|Twin Otter]] is more stylish.

South of Skardu lies Deosai park, a famous high plateau, but we turn initially east. There's a chain of lakes which is the Indus river. After about five miles, the Shigar river merges with the Indus. Turn slightly left and follow the Shigar, then follow it into a long and broad lake-filled valley stretching into north-western direction.

Towards the end of the lake, a small tributary river, the Braldu, turns eastward out of the main valley. Follow the Braldu and start climbing (if you haven't done so yet). About 15 miles after turning into the Braldu river valley, two glacier-filled valleys stretch to the north - admire the view!

[[File:Karakoram2.jpg|300px|thumb|right|Heading back into Skardu, Nanga Parbat on the horizon]]

Passing a few lakes, you reach finally Baltoro glacier continuing the river valley stretching eastward. Ever climbing, follow the glacier till you reach some kind of T-junction. The glacier arm reaching north leads to K2 (which sadly isn't really there in Flightgear), but just ahead of you are the still rather impressive peaks of Gasherbrum V, VI and I - circle the range and make some pictures!

A good way back to Skardu is to go about 10 miles sourth from the Gasherbrum peaks, then head due west. To your west, you can see the long valleys fall away from the high ranges, to your right is the still glacier-covered high Karakoram. On a clear day (really good visibility selected) you can see the distinctive peak of Nanga Parbat appearing straight ahead on the horizon. The valley of Skardu is quite a distinctive feature and finding back VFR should not be a problem.

Published in [[FlightGear_Newsletter_April_2012#Suggested_flights| Newsletter April 2012]] by [[User:Thosten|Thosten]].

== The Paro Challenge ==
The challenge consists in flying as fast and as low as possible from Hashimara (VE44) to Paro (VQPR) while navigating a maze of valleys, steep climbs and sharp turns with only one VOR-DME beacon to guide you (it sits on a mountaintop south of Paro airport). You cannot fly on instruments; this is a 100% visual flight.

Spawn at VE44 (Hashimara Air Force Station). Take off in any direction then turn immediately to heading 013 while staying low. You will see the Himalayas appear on the horizon. Follow the valley as it turns 90° left then make a sharp U-turn (180°) to the right. Fly over the bridge, then U-turn left again (160°). Follow the valley and do another U-turn to the right. Take a deep breath for a couple of nautical miles. Climb to 8500ft while heading 080 to pass over the mountain range. Turn slightly to your right (heading 100) and do a steep dive to 4000ft into the valley. Turn left into the second valley (heading 000), which you will need to follow all the way to Paro airport (VQPR), while climbing slowly to the airport elevation of 7500ft. On the way to Paro, you will pass a monastery on your left. If you don't see this monastery, you've lost yourself in the maze; good luck! After this monastery, follow the valley to the left (heading 270), which will force you to turn right after a few nautical miles. The runway will be hidden behind a hill. You can pass over the hill (steep dive on the other side) or fly to the right of it (steep S-turns), your choice.

=== Suggested aircraft ===
The Paro Challenge is a challenge for most aircraft and most pilots. You will probably not succeed on your first attempt; and successive attempts with various aircraft will renew the challenge.

===== Easy =====
[[Cessna 550 Citation II]], [[Pilatus PC-6 Porter|Pilatus PC-6]], [[De Havilland Canada DHC-6 Twin Otter|De Havilland Canada DHC-6]], [[Zivko Edge 540]].

[[De Havilland Mosquito]], Messerschmitt Bf109G, [[Lockheed P-38 Lightning]].

==== Challenging ====
[[Piper PA34-200T Seneca II|Piper Seneca II]], [[Cessna 337G Skymaster|Cessna 337]], [[Antonov An-2]]: keep an eye on your Exhaust Gas Temperature and Cylinder Head Temperature. If you can't lean your mixture, you lose.

Cessna 172, PA-28 or DR-400 with 180hp engines and a light load; [[Cessna 182S]]; Cap 10b. Slower than the above and will require just as much concentration from you, for a longer time.

[[Mikoyan-Gurevich MiG-15|MiG-15]], [[North American F-86 Sabre|F-86F Sabre]], [[Fairchild Republic A-10 Thunderbolt II|A-10 Warthog]]: make high-speed, steep turns while finding your way. Don't black out!

==== Difficult ====
[[JT-5B|JT-5B autogyro]], [[Piper J3 Cub|Piper Super Cub 150hp]]: the Paro challenge takes well over an hour of intense concentration in these unstable aircraft.

Cessna 172, PA-28 or DR-400 with low-power (160hp) engines. You will need to circle several times in the valley during the climb. If you can't lean your mixture, you lose.

[[Boeing 707]], [[Boeing 757-200|757]], [[Tupolev Tu-154B|Tupolev 154]], [[Lockheed Constellation]] if lightly loaded; [[Cessna Citation X]]: Finding your way in these faster aircraft is a challenge. The U-turns before the steep climb are almost impossible without taking shortcuts. The final approach without seeing the runway requires you to control your speed, flaps and landing gear well in advance.

==== Impossible (but you might try to beat them anyway) ====
[[Piper J3 Cub|Piper Cub 65hp]] (cannot climb over 7000ft when fully loaded).

[[Boeing 737-300]] (poor low-speed handling), [[Boeing 787-8 Dreamliner|787]] (bank limiter).

[[Dassault Mirage 2000-5|Mirage 2000]], [[Grumman F-14 Tomcat|F-14B]], [[McDonnell Douglas F-15 Eagle|F-15C]], [[General Dynamics F-16 Fighting Falcon|F-16]]: will either stall or black you out during the sharp turns.

=Africa=
==Ngorngoro==
For this [[VFR]] trip we need a strong machine since we will go up from 4000 to about 10,000 feet and since we are in Africa, Tanzania , what better choice is there as the Cessna 208 Caravan, on wheels. We will take off from HTLM, [http://en.wikipedia.org/wiki/Lake_Manyara Lake Manyara], runway 12 (124.5 deg), that has an elevation of 4150 feet. Hit Shift-B so we don't drop off the runway.
[[File:Map Ngorngoro Crater.jpg|thumb|200px|left|Heightmap with visual reference points]]
We will have to change some settings before we take off. There is no snow where we are so: View=> Rendering Options=> Snow line=> Set to max. (5000M). We need a reasonable clear sky since there are quite a few bumps we could hit: Environment=> Global weather=> METAR source=> Fair weather.

Give full throttle and take off. Bank left and make a full circle so we gain some altitude and make a mental note of the airstrip, since this is the only one nearby. Look at the road West towards the airfield.
You will notice that the airstrip is at the edge of a mountain ridge, the lake to the East is quite a lot lower.

We pass over the airstrip towards lake Manyara and turn left keeping the mountains close to our left side, on an initial course of about 30 deg. We keep the mountains to our left and follow our path, our heading will slowly go from 30 to North and takes about 15 mins. During our path we should slowly gain altitude.
[[File:Ol Doinyo Lengai.jpg|thumb|250px|Mt.Kerimasi (left), Mt.Ol Doinyo Lengai (ahead)]]
On the '''image''' we see two distinct mountains. The nearest is Mt.Kerimasi, a fun place for hang-gliders, and North Mt.Ol Doinyo Lengai, an active volcano. We are heading straight towards [http://en.wikipedia.org/wiki/Ol_Doinyo_Lengai Mt.Ol Doinyo Lengai]. Just before we would collide we take a sharp left turn heading 225. You will see why we need the altitude now.

The mountain ahead, [http://www.ntz.info/gen/n00161.html#id03702 Mt.Embagai], we see does not appear to be anything spectacular. Aim towards it since we have to go over it.
Coming nearer, if you are high enough, 9000 feet, you will see why this mountain is well worth a visit. It is a crater with a lake inside, lake Embagai (Empakaai). Enter the crater and look around, careful not to loose any height since we'll have to get out again, we need about 10 000 feet. Mesmerized we grab our compass and take a course of 225 again. To get out we might skim against a cloud, be careful. If you don't see a way out take a turn again to wait for the clouds to move out of sight.

After you managed to get out of the crater keep on the course of 225 while descending slowly for about 9 mins. There are some bumps to avoid, like Mt.Olmoti we keep to the right and Mt.Losirua on the left.

After a small hill we enter one of the most amazing places in Africa, the [http://en.wikipedia.org/wiki/Ngorongoro_Conservation_Area Ngorngoro Crater], the second biggest crater in the world. A micro climate and amazing wildlife.
Examine the crater and you will notice two lakes, head towards the biggest lake, lake Magadi. When you are above it take a course of 123 to get out of the crater.

After leaving the crater it takes some time before we are near the airstrip again. After about 5 mins we will see a river (left) and a road (right). Follow the road since it will lead us to the airstrip again.

Don't scare the wildebeast!

Notecard:
<tt>
#Fair weather, no snow
#HTLM RW 12 4150 feet
#Course 30 to 0 deg 15 mins, mountains close left
#Head towards /\volcano
#Sharp left turn course 225 deg altitude 9000 feet
#Volcano, lake, 10 000 feet
#Course 225 deg, slow descend 9 min
#Large lake, course 123 deg 5 mins
#River left, road right. Follow road
#Landing 124.5 deg 4150 feet.</tt>

*October 2011 by [[User:PH-JBO|PH-JBO]]. Published in [[FlightGear_Newsletter_December_2011#Suggested_flights | Newsletter December 2011]].
==Kisimayu to Kilimanjaro==
We have to take a big airliner for this trip. The runways are long enough but for this trip we need some altitude and a slow descend.

We park our Big Bird at HCMK, [http://en.wikipedia.org/wiki/Kismayo_Airport Kisimayu], Somalia, near the East coast of Africa. It's unsure what this airfield is used for but it's a long piece of tarmac. I could not find regular flights to and from this airfield, not so strange, there is no lighting, no radio beacons and... no fuel. What you can find is Global Air Rescue that has an air ambulance service based here (with a [http://www.globalairrescue.com/learjet-35.php Learjet 35]).

Our route will be around 425 nm in length. You know your aircraft and know what altitude you will need to fly.

Our destination, HTKJ, [http://en.wikipedia.org/wiki/Kilimanjaro_International_Airport Kilimanjaro], Tanzania, has only one ILS and I have learned, if an airfield has only one ILS there is probably a reason.

Flight Plan (short version):
#HCMK Kisimayu, length 12,177 ft, no navaids near.
#GAR Garissa [[VOR-DME]] freq 115.7 heading 268° dist 169 nm.
#KB Kilimanjaro [[NDB]] freq 393.0 heading 224° dist 258 nm, here is the holding pattern for the Kilimanjaro runway (and there is a [http://en.wikipedia.org/wiki/Mount_Kilimanjaro 19,000 ft] reason for this detour).
#KV Kilimanjaro VOR-DME freq 115.3 heading 70° dist 26 nm.
#HTKJ Kilimanjaro [[ILS]] freq 110.9 runway heading 88° elev 2,900 ft [[AMSL]] length 11,807 ft.

Prepare your flight well to receive amazing views of the landscape during the final steps of the route, if you don't you will discover why some pilots call Kilimanjaro Kill-You-Manjaro.

{{#ev:youtube | KCJi_ZaR8ec}}
Youtube video: Kilimanjaro approach in real, in FG not much different.

*February 2012 by [[User:PH-JBO|PH-JBO]].

=Australia and Oceania=

==Hawai'i==
[[Image:Maui03.jpg|thumb|250px]]
Do you use [[TerraSync]]? If so, try a flight around Hawaii! Take off from PHNL in a light aircraft and head west until you hit Pearl Harbor; a right turn north will take you post the USS Arizona Memorial, and the Punchbowl Crater will be to your right. Or, fly east from PHNL past volcanic craters Diamond Head and Koko Head. If you follow the O'ahu coastline north from Koko Head, you can land at either old World War II airbase Bellows Field (now a wildlife reserve in real life) or at Keahole MCAS.

For a potentially more scenic route, fly east toward Molokai, and stay to the north (left) of the island. The northern part of Molokai features huge sea cliffs and a tiny airstrip on the Kalaupapa peninsula - the peninsula being the only respite from the cliffs. A former leper colony existed near the airstrip!

Also of interest are the volcanoes on Maui and the 'Big Island' of Hawai'i - flying VFR in a small plane from PHTO to PHKO over the plateau between Mauna Kea and Mauna Loa can be a challenge, as you have to take off from sea level, fly through a pass of 6500 feet, and then drop back down to sea level to land! The Hana coast of northern Maui is also a nice flight - a circumnavigation of Haleakala, starting and ending at PHOG, is quite a nice flight.

The islands will be available through the download center with the next major scenery release, but for now, fire up [[TerraSync]] and your favorite VFR aircraft and have a blast.
*Published in [[FlightGear Newsletter September 2010]] by [[User:Statto|Statto]].

== Hawai'i waterfalls tour ==
This flight will let you discover some of the famous Hawai'ian waterfalls, visiting the Islands of Kauai and Oahu.
{{note| Despite the scenery is very nice, the waterfalls are mostly not modeled (as of 5/2024)}}

* [https://skyvector.com/?ll=21.82733715471215,-158.96200561400335&chart=301&zoom=5&fpl=%20PHBK%202211N15938W%202206N15930W%202204N15925W%20LIH%202135N15817W%202138N15802W%202120N15746W%202116N15748W%20PHNL SkyVector route]
* Suggested plane: C172 or C182
* This is VFR only, so pick suitable weather. There are no usable navaids for this trip except the VORTAC LIH 113.500 to cross the sea.
* Trip takes around 90 minutes air time at 110 KTAS.

First part of the trip:
* Start at Parking sands (PHBK), runway 34
* Takeoff, climb to 5000ft and follow the northern coast at about a heading of 030° until you reach Crawlers Ledge (about 8 minutes flight time).
* Turn southeast into the very dominant embayment and watch out for Hanakoa Falls, our first waterfall to visit.
* To your left should be a very dominant valley behind the ridge, featuring a river. Now climb to 6000ft and follow that valley southeastish and visit the famous Weeping wall waterfalls behind the ridge at the end of the valley.
* Bank left slightly (~100° heading), descend to 3000 ft and aim for Wailua waterfalls at the south side of the small hill near the coast (between the two towns).

This concludes the islands waterfalls after about 20 minutes flight.

Now either land at Lihue Airport (PHLI) to your right for a break, or continue the trip and intercept VORTAC LIH 113.500 radial 99/TO. Follow the radial to cross the Kauai Channel until you reach the tip of Oahu Island (the crossing of 63NM takes about 30 minutes at 120 knots. You may also opt to skip and start at PHDH).

* Follow overfly Kawaihapai Airfield (PHDH) and follow the northern coast.
* Shortly you will ovefly a prominent bend from east to nothertheast in the coast, still follow the coast. Note the windfarm appearing to your right ahead.
* Over Waimea (just before the very visible sand beach), turn right and fly to the inland behind (north of) the windfarm. Shortly after passing the wind turbines, look out for Waimea waterfalls.
* Follow the mountains to the southeast of the island and slowly climb to 4000ft (the left side is more rough and scenic).
* North of Diamond Head (a big crater at the south tip of the island) there are several waterfalls (roughly in the middle between Diamond head in the south and Kaneohe in the north), as well as very nice streams coming down the ridge. Also the north side of the ridge is very nice, so consider doing a circle over there.
* Continue south over Diamond head and proceed to land at Honolulu airport (PHNL).

This concludes the trip after about 1:30 hours.

==Brisbane International Airport to Sydney International Airport==
Going from Brisbane International Airport to Sydney International Airport. You should have a heading of about 203. Might take sometime to arrive to this section. Maybe 10-30 mins into the flight. Can't really say but don't give up, you will eventually reach this section of the flight. '''''Your eyes will be rewarded!''''' .

[[Image:Fgfs-screen-020.png|200px]]
[[Image:Fgfs-screen-016.png|200px]]
[[Image:Fgfs-screen-012.png|200px]]
*Published in [[FlightGear Newsletter April 2011]] by [[User:Vin|Vin]]

=Antarctica=

{{Suggested}}

[[Category:Lists]]

Suggested Flights

2024-08-22T21:27:50Z

Circumn: /* Difficult */

[[FlightGear]] has accurate and realistic terrain. Here are some interesting places where you can do virtual sight seeing.

If you are starting with [[FGRun]] - the FlightGear launcher - you can enter the [[airport]] id and select the runway on the appropriate screen in the startup wizard.
If you are starting from the command line you can use the options: <tt>--airport=ABCD</tt> and <tt>--runway=12L</tt>.

*Remember to give a look at the [[Suggested Airports]] page, where you can find a comprehensive list of high quality airports in FlightGear.
*If you enjoy these flights, please consider recording a flight and posting a link to it at the [[Suggested Prerecorded Flights]] page.

'''Remove before flight!''' 

Before you start flying into one of the suggested flights, you should add both the terrain and the Objects to you FlightGear installation; This is well explained on the [[Howto: Install scenery|installing scenery]] page.

p.s. charts are generated using FlightGear data only.

This page includes the flights described on the [http://www.flightgear.org/places.html main website] and the suggested flights from the newsletters. It can serve as an archive for suggested flights from future [[FlightGear Newsletter|newsletters]] or can give a flight if creativity is low that month.

{{TOC limit|3}}

=Cross Continentals or World Tour=

* [[Breitling DC-3 World Tour]][[File:Rect17.png|thumbnail]]
* [[Flying the Hump]]

=North America=
==Round Valley Airport==
[[Image:O09-002.png|thumb|left|right after take off]]
[[Image:O09-003.png|thumb|right|Valley]]
Covalis, CA. The airport is at the West edge of a 7 mile across valley.<BR/>
The predominant wind is a cross wind. Take-offs to the west (if they use the full runway length) often have to fly between 2 small hills and over another valley while gaining altitude. Most pilots take off to the west.<BR/>
It is a paved runway and quite long. It was designated as an emergency recovery field during the Cold War and was used twice that I know of by military aircraft that could not take off again from the field.
<div style="clear:both;"></div>

===Airports and coordinates===
{{Location map | USA
| caption = Latitude: 39.790156 Longitude: -123.266403
| lat_deg = 39.790156
| lon_deg = -123.266403
}}

* [[O09|O09 - Round valley]] - [http://assistenza.larasrl.net/brisa/fgfs/suggested_flights/O09.pdf chart]

required scenery tile: ftp://ftp.sunsite.org.uk/sites/ftp.flightgear.org/flightgear-ftp/Scenery/w120n40.tar.gz
<div style="clear:both;"></div>

===Suggested aircraft===
I have tried this trip using a p38, quite powerful airplane
* [[Lockheed-P38|P38]]
<div style="clear:both;"></div>

===FlightGear launching===
fgfs --airport=O09 --runway=28 --aircraft=p38
<div style="clear:both;"></div>

==Half Moon Bay==
[[Image:KHAF-001.png|thumb|left|right after take off]]
[[Image:KHAF-002.png|thumb|right|Bridge]]
Start at [[KHAF|Half Moon Bay]], Runway 30, with 32km visibility; Takeoff in the C172 and climb to 1000 feet, then continue north over the water, near the shoreline. Look out the right window frequently. Fly up the coast, overfly the Golden Gate Bridge, continue around the top of the peninsula past downtown SF, then fly on to [[KSFO]] for a landing. We now have lots to see.

If you cannot see the runway in the default 172, you must be flying too high or too slowly. You can start by practicing a bit with a good setup:

'''fgfs --offset-distance=1.5 --altitude=500 --vc=70'''

As soon as FlightGear starts, cut the power to 1500 rpm and drop two notches of flap. Maintain 70 kt. Now, pick your landing spot (a bit down the runway) and try to hold it in the same spot on your windshield. If your landing spot starts moving down, you are too high, and should cut another 100 rpm; if it starts moving up, you are too low, and should add another 100 rpm. Adjust the nose to keep your speed at 70 kt all the way down until you're right above the numbers, then cut power to idle, drop the last notch of flaps, flare, and land.
<div style="clear:both;"></div>

===Airports and coordinates===
[[Image:KHAF-003.png|thumb|left|surroundings]]
[[Image:World-KHAF.png|thumb|right|Latitude: 37.513333 Longitude: -122.501111]]
* [[KHAF|KHAF - Half Moon Bay]] - [http://assistenza.larasrl.net/brisa/fgfs/suggested_flights/KHAF.pdf chart]

no required scenery tile.
<div style="clear:both;"></div>

===Suggested aircraft===
[[Image:KSFO-001.png|thumb|left|Before landing]]
Use the default c172 airplane
* [[Cessna C172P]]
<div style="clear:both;"></div>

===FlightGear launching===
fgfs --airport=KHAF --runway=30 --visibility=32000 --aircraft=c172
<div style="clear:both;"></div>
===Author===
April 2006 [[User:Hellosimon|Hellosimon]], format and extended by [[User:Francescobrisa|Francescobrisa]]

==Hell's Canyon==
[[Image:25U-001.png|thumb|left|right after take off]]
[[Image:25U-004.png|thumb|right|Valley]]
Hell's Canyon, Imnaha, OR. This airport is located just west of "Hell's Canyon National Park" which has the Snake River running through it.<br/>
Supposedly it's a 5500 foot drop from the top of the canyon to the river.<BR/>
The airport is located on the brink of this canyon.

See the remarks on the airport page (click on the airport id) ... DOWNDRAFTS, SHEER DROP IN TERRAIN, LIVESTOCK, etc. Don't go here on your first solo x-country. :-)
<div style="clear:both;"></div>

===Airports and coordinates===
[[Image:25U-005.png|thumb|left|Landing]]
[[Image:World-25U.png|thumb|right|Latitude: 45.427861 Longitude: -116.693889]]
* [[25U|25U - Round valley]] - [http://assistenza.larasrl.net/brisa/fgfs/suggested_flights/25U.pdf chart]

required scenery tile: ftp://ftp.sunsite.org.uk/sites/ftp.flightgear.org/flightgear-ftp/Scenery/w120n40.tar.gz
<div style="clear:both;"></div>

===Suggested aircraft===
[[Image:25U-006.png|thumb|left|Landing 2]]
I have tried this trip using a pilatus PC-9M, powerful airplane
* [[PC-9M|PC-9M]]
<div style="clear:both;"></div>

===FlightGear launching===
fgfs --airport=25U --aircraft=PC-9M
<div style="clear:both;"></div>

==Crater Lake National Park Tour==
[[Image:64s-003.png|thumb|left|Approaching the lake]]
[[Image:64s-002.png|thumb|right|Direction 40 degrees]]
Prospect, OR.<br/>

Take off and fly at a heading of about 40 degrees until you cross the first distinct ridge in front of you. (several minutes of flight in the navion ... just climb as fast as you can, it will be a close squeek to get over :-)<br/>

Once you clear the ridge and can see beyond it, turn right and fly a heading of about 70 degrees. You should see two shallow peaks off in the distance. Head right between these -- they are the two sides of the crater. As you get closer the shape of the crater will come into view. There's a lake there in real life, hopefully it will be there in flight gear too before long.
<div style="clear:both;"></div>

===Airports and coordinates===
[[Image:64s-001.png|thumb|left|Leaving the 64S airfield]]
[[Image:World-64S.png|thumb|right|Latitude: 42.743183 Longitude: -122.488092]]
* [[64S|64S - Prospect State]] - [http://assistenza.larasrl.net/brisa/fgfs/suggested_flights/64S.pdf chart]

required scenery tile: ftp://ftp.sunsite.org.uk/sites/ftp.flightgear.org/flightgear-ftp/Scenery/w130n40.tgz
<div style="clear:both;"></div>

===Suggested aircraft===
[[Image:64s-004.png|thumb|left|Lake view 1]]
[[Image:64s-005.png|thumb|right|Lake view 2]]

* [[Ryan_Navion|Navion]]
<div style="clear:both;"></div>

===FlightGear launching===
fgfs --airport=64S --runway=02 --aircraft=navion
<div style="clear:both;"></div>

==Grand Canyon Tour==
[[Image:Grand_Canyon_Tour_4.jpg|700px|frameless|center]]
Being a special place, there are also special flight rules for VFR traffic around the Grand Canyon. There are multiple no-fly-zones set up and VFR traffic is only allowed to fly via the designated corridors. If you want to fly realistically, avoid these zones in FlightGear as well, following for example the [https://skyvector.com/?ll=36.18649251415492,-112.52223157994264&chart=230&zoom=5&fpl=%20KGCN%20VPGCF%20VPGCG%20VPGCD%20VPGCC%20VPGCA%203608N11252W%203609N11309W%201Z1%201G4%203AZ5 route shown here. (skyvector link)]

This flight takes you from KGCN, the Grand Canyon National Park airport, to 3AZ5, a small airfield called Hualapai located south of the Grand Canyon. Departing from KGCN, fly north-west bound to reach the canyon. From there, either follow the route shown on skyvector above, or fly visually through the canyon westbound towards 1Z1, Grand Canyon Bar Ten Airstrip. From there on, continue flying westward to 1G4. Called Grand Canyon West, 1G4 also marks about the western end of the canyon. To get to your destination 3AZ5, continue along the southern rim, flying eastward now. Shortly after leaving the breathtaking valley behind you, you will already reach your destination. Land and let your engine and your mind cool down from the special views :)

===Gallery===
<gallery>
Grand_Canyon_Tour_2.jpg
Grand_Canyon_Tour_3.jpg
Grand_Canyon_Tour_1.jpg
</gallery>

===Airports===
* KGCN - Grand Canyon National Park Airport - [https://www.aopa.org/destinations/airports/KGCN/details aopa.org]
* 1Z1 - Grand Canyon Bar Ten Airstrip - [https://www.airnav.com/airport/1Z1 airnav.com]
* 1G4 - Grand Canyon West - [https://www.airnav.com/airport/1G4 airnav.com]
* 3AZ5 - Hualapai - [https://www.airnav.com/airport/3AZ5 airnav.com]

===Suggested aircraft===
Most VFR aircraft with sufficiently big windows will serve the purpose, for example:
*[[Cessna C172P]]
*[[Optica]]
*[[Ryan_Navion]]
If you are more interested in flying helicopters, the [[Eurocopter EC130 B4]] with the Grand Canyon Helicopters livery might be for you.

===Links===
*[https://www.nps.gov/grca/learn/nature/upload/sfra.pdf Chart of the Grand Canyon special airspace, published by the National Park Service]
*[http://www.swaviator.com/html/issueJJ99/canyon.html An article about flying close to the Grand Canyon]
*[https://www.aopa.org/news-and-media/all-news/2017/april/flight-training-magazine/road-trip-grand-canyon AOPA Flight suggestion]

==Ranger Creek Airport==
[[File:21w-1.jpg|500px|center|Waiting for departure at Ranger Creek]]
Ranger Creek Airport is located in Greenwater, Washington, USA. Being wedged into the bottom of a steep canyon, you'll definitely need to be on your toes to get in and out of there. Switch on Advanced Weather and Live Data to experience what the winds can do to you in real life!
===Airports and coordinates===
* [[21W|21W - Ranger Creek]] - [http://www.airnav.com/airport/21W airnav.com]
===Gallery===
<gallery>
Ranger_Creek1.jpg|Departing between the mountains
Ranger_Creek_2.jpg|Looking back towards the airfield
Ranger_Creek_3.jpg|Downwind for approach back to Ranger Creek
</gallery>
===Suggested aircraft===
For this flight, the Piper PA-18 SuperCub is suggested, this is included in the [[Piper J3 Cub]] package

==Mount Rainier Tour==
[[Image:WA20-002.png|thumb|left|The mountain from far away]]
[[Image:WA20-006.png|thumb|right|external view]]
Eatonville, WA. Start out at Swanson Airport in Eatonville, WA. Take off and fly a heading of about 90 degrees. You will need to fly for 5-10 minutes before the mountain comes into view. Be patient if you don't see it right away, it will dwarf everything in it's vicinity.
<div style="clear:both;"></div>
===Airports and coordinates===
[[Image:World-WA20.png|thumb|right|Latitude: 46.87588502 Longitude: -122.25733500]]

* [[WA20|WA20 - Swanson]] - [http://assistenza.larasrl.net/brisa/fgfs/suggested_flights/WA20.pdf chart]

required scenery tile: ftp://ftp.sunsite.org.uk/sites/ftp.flightgear.org/flightgear-ftp/Scenery/w130n40.tgz
<div style="clear:both;"></div>

===Suggested aircraft===
[[Image:WA20-007.png|thumb|left|external near view]]
[[Image:WA20-009.png|thumb|right|external near view]]
* [[mosquito]]

<div style="clear:both;"></div>

===FlightGear launching===
fgfs --airport=WA20 --aircraft=mosquito
<div style="clear:both;"></div>

==Death Valley Tour==
[[Image:L06-001.png|thumb|left|in the air]]
[[Image:Furnace-creek.jpg|thumb|left|real life view of Furnace Creek Airfield]]
[[Image:L06-002.png|thumb|right|in the air]]
Furnace Creek, CA. This starts you right in the middle of Death Valley which runs north & south. If you head south about 15 miles you'll hit the lowest point in the USA, 282 feet (86 meters) below sea level.
<div style="clear:both;"></div>
===Airports and coordinates===
[[Image:World-L06.png|thumb|right|Latitude: 36.46451100 Longitude: -116.88139422]]
* [[L06|L06 - Furnace Creek]] - [http://assistenza.larasrl.net/brisa/fgfs/suggested_flights/L06.pdf chart]

required scenery tile: ftp://ftp.sunsite.org.uk/sites/ftp.flightgear.org/flightgear-ftp/Scenery/w120n30.tgz
<div style="clear:both;"></div>

===Suggested aircraft===
[[Image:L06-003.png|thumb|left|in the air]]
[[Image:L06-004.png|thumb|right|in the air]]
* [[rallye-MS893]]
<div style="clear:both;"></div>

===FlightGear launching===
fgfs --airport=L06 --aircraft=rallye-MS893
<div style="clear:both;"></div>

==Utah==
!!! Work in progress !!!<BR/>

Escalante Muni Airport, Escalante, UT. This airport is east and a bit north of Bryce Canyon National park. If you head mostly south and a bit east you'll eventually hit the Grand Canyon. It is sandwiched between the Dixie National forest to the north and the Grand Staircase-Escalante National Monument to the south. There should be interesting stuff to see no matter which direction you head.
<div style="clear:both;"></div>
===Airports and coordinates===
[[Image:World-1L7.png|thumb|right|Latitude: 37.75054400 Longitude: -111.57578300]]
* [[1L7|1L7 - Escalante Muni]] - [http://assistenza.larasrl.net/brisa/fgfs/suggested_flights/1L7.pdf chart]

required scenery tile: ftp://ftp.sunsite.org.uk/sites/ftp.flightgear.org/flightgear-ftp/Scenery/w120n30.tgz
<div style="clear:both;"></div>

===Suggested aircraft===

<div style="clear:both;"></div>

===FlightGear launching===
fgfs --airport=1L7 --aircraft=pa18
<div style="clear:both;"></div>

==Lake County Airport (CO)==
[[Image:KLXV-001.png|thumb|left|Adjust mixture !]]
[[Image:KLXV-002.png|thumb|right|The terrain will be covered by snow]]
Lake County Airport, Leadville, CO. This airport is at an elevation of 9927 making it a bit of a challenge to get into and out of with a standard C172.<BR/>
Make sure you lean out your engine before taking off and read up on density altitude before you try this one in real life.
<div style="clear:both;"></div>
===Airports and coordinates===
[[Image:KLXV-003.png|thumb|left|The airport]]
[[Image:World-KLXV.png|thumb|right|Latitude: 39.22812500 Longitude: -106.31835600]]
* [[KLXV|KLXV - Lake Co]] - [http://assistenza.larasrl.net/brisa/fgfs/suggested_flights/KLXV.pdf chart]

required scenery tile: ftp://ftp.sunsite.org.uk/sites/ftp.flightgear.org/flightgear-ftp/Scenery/w110n30.tgz
<div style="clear:both;"></div>

===Suggested aircraft===
[[Image:KLXV-004.png|thumb|left|I like this panorama]]
[[Image:KLXV-005.png|thumb|right|The nearby lake]]
* [[Cessna C172P]]

<div style="clear:both;"></div>

===FlightGear launching===
[[Image:KLXV-006.png|thumb|left|Landing...]]
fgfs --airport=KLXV --aircraft=c172p
<div style="clear:both;"></div>

==Caribbean - Saint Martin and St. Kitts==
[[Image:TNCM-003.png|thumb|left|just after the take off]]
[[Image:TNCM-004.png|thumb|right|some nearby island]]
Pilots of the Caribbeans is an informal FlightGear community of users who fly around the small Caribbean islands, many of which have custom scenery and improved landclass data. (For details see [[Pilots of the Caribbean]])<BR/>

[[TNCM|Princess Juliana International Airport (TNCM)]] at the isle of Saint Martin, is one of the most popular airports in FlightGear. In large part due to the custom objects and land cover. However, St. Marten is only one of several detailed airports in the region - and, while the approach for TNCM is one of the most memorable in the whole world, the land cover for St. Kitts and Nevis makes it a lovely place to fly.

British Airways, US Airways and American Airlines, among others, all fly into St. Kitts' [[TKPK|Robert L. Bradshaw International Airport (TKPK)]] in real life.

Take off from TKPK in a [[Piper_J3_Cub|Piper Cub]] and make a northward, clockwise circle of the island. Start your descent on the east side of the island, and focus on the small hill which separates the north from the south. Start hugging the coast near the beach and look to the west - as soon as the railroad heads to the southwest, you're about ready to turn for final. Make your right hand turn for final and taxi to the terminal.

If you want to fully explore this whole country, take off in a Beaver, which has a little more speed, and fly a figure eight. Take off from TKPK and circle the airport to the north like in the Cub. Then instead of landing, perform a touch-and-go and turn left over the boat terminal and make for the west coast of Nevis. Enjoy the beauty of the south coast of St. Kitts before circling Nevis. Over Nevis, you have several options - cut your flight short and land at [[TKPN]] on the island of Nevis, complete the "figure eight" by heading back to TKPK, or check your fuel and head east across the Caribbean to Antigua (which does not have custom land cover).<BR/>
<BR/>
Check out the [[Pilots of the Caribbean]] page, for further informations.
<div style="clear:both;"></div>
===Airports and coordinates===
[[Image:World-TNCM.png|thumb|right|Latitude: 18.040953 Longitude: -63.108900]]

* [[TNCM|TNCM - Princess Juliana International Airport]] - [http://assistenza.larasrl.net/brisa/fgfs/suggested_flights/TNCM.pdf chart]
* [[TKPK|TKPK - Robert L. Bradshaw International Airport]] - [http://assistenza.larasrl.net/brisa/fgfs/suggested_flights/TKPK.pdf chart]
* [[TKPN|TKPN - Vance Winkworth Amory Intl]] - [http://assistenza.larasrl.net/brisa/fgfs/suggested_flights/TKPN.pdf chart]
others interesting airports in the area:
* [[TFFF|TFFF - Le Lamentin]] - [http://assistenza.larasrl.net/brisa/fgfs/suggested_flights/TFFF.pdf chart]
* [[MDPP|MDPP - Gregorio Luperon Intl]] - [http://assistenza.larasrl.net/brisa/fgfs/suggested_flights/MDPP.pdf chart]
* [[TJSJ|TJSJ - Luis Munoz Marin Intl]] - [http://assistenza.larasrl.net/brisa/fgfs/suggested_flights/TJSJ.pdf chart]
* [[FMEE|FMEE - St Denis Gillot]] - [http://assistenza.larasrl.net/brisa/fgfs/suggested_flights/FMEE.pdf chart]
* [[TFFG|TFFG - Grand Case]] - [http://assistenza.larasrl.net/brisa/fgfs/suggested_flights/TFFG.pdf chart]

required scenery tile:
* ftp://ftp.sunsite.org.uk/sites/ftp.flightgear.org/flightgear-ftp/Scenery/w070n10.tgz
* ftp://ftp.sunsite.org.uk/sites/ftp.flightgear.org/flightgear-ftp/Scenery/w080n10.tgz
* ftp://ftp.sunsite.org.uk/sites/ftp.flightgear.org/flightgear-ftp/Scenery/w080n20.tgz
* ftp://ftp.sunsite.org.uk/sites/ftp.flightgear.org/flightgear-ftp/Scenery/w090n20.tgz
<div style="clear:both;"></div>

===Suggested aircraft===
[[Image:TNCM-005.png|thumb|left|amazing]]
[[Image:TNCM-006.png|thumb|right|landing]]
* [[Piper_J3_Cub|Piper Cub]]
<div style="clear:both;"></div>

===FlightGear launching===
fgfs --airport=TKPK --aircraft=Cub
<div style="clear:both;"></div>
===Author===
[[FlightGear Newsletter January 2011]] by [[User:Statto|Statto]], format and extended by [[User:Francescobrisa|Francescobrisa]].

==Friedman Memorial Airport (Idaho)==
[[Image:KSUN-001.png|thumb|left|take off]]
[[Image:KSUN-002.png|thumb|right|nearby]]
Friedman Memorial Airport, Hailey, Idaho. This airport is nestled in a valley surrounded by significant terrain. It's one that shows up quite often in accident investigations.
<div style="clear:both;"></div>
===Airports and coordinates===
[[Image:World-KSUN.png|thumb|right|Latitude: 43.51223900 Longitude: -114.30376100]]
* [[KSUN|KSUN - Friedman Mem]] - [http://assistenza.larasrl.net/brisa/fgfs/suggested_flights/KSUN.pdf chart]

required scenery tile: ftp://ftp.sunsite.org.uk/sites/ftp.flightgear.org/flightgear-ftp/Scenery/w120n40.tgz
<div style="clear:both;"></div>

===Suggested aircraft===
[[Image:KSUN-003.png|thumb|left|landing]]
[[Image:KSUN-004.png|thumb|right|landing]]
* [[FK9MK2]]
<div style="clear:both;"></div>

===FlightGear launching===
fgfs --airport=KSUN --aircraft=fk9mk2
<div style="clear:both;"></div>

== Wyoming - Grand Teton ==
Jackson Hole (KJAC) airport is located at around 6,400ft right next to the Teton range of mountains. The Tetons rise straight out of the plains, gaining over 5,000ft in 2 miles.

You will need the w120n40 scenery.

Tower frequency at KJAC is 118.07. Due to the high altitude, you will need to lean non-turbocharged piston aircraft before take-off. Don't forget that take-off distances will also be longer.

After take-off head to the North East. Grand Teton is the highest of the three peaks that rise straight from the flat-lands. Follow the line of mountains to the East, passing over Jenny Lake. After a couple of miles you will reach a huge lake. The large bulk of a mountain to the East is Mount Moran.

The Teton Mountain range is surprisingly thin - really just a string of mountains running SW-NE. Flying fast jets down the steep valleys is recommended.
* September 2006 by [[User:Stuart|Stuart]].

== Virginia Eastern Shore, Chesapeake Bay-Bridge Tunnel Sightseeing ==
[[Image:KTGI-001.png|thumb|left|before take off]]
[[Image:KTGI-002.png|thumb|right|right after take off]]

Take a short VFR trip from Tangier Island to view the famous Chesapeake Bay Bridge-Tunnel connecting Cape Charles to Cape Henry. Depart historic Tangier Island (KTGI) situated in the Chesapeake Bay and land at Norfolk International Airport (KORF), Norfolk, Virginia. The scenic character of the flight is enhanced by leaving the island at dusk. The flight is both scenic and challenging. Frequently, when flying with real weather, you will have a steady wind blowing across the bay. Starting out quiet Tangier and arriving at busy, glittering Norfolk International (KORF) gives the flight some contrast.

'''fgfs --airport=KTGI --runway=20 --timeofday=dusk'''

Before leaving Tangier: Set your altimeter to the prevailing barometric temperature. Set your communications radio to the Norfolk Intl. (KORF) ATIS frequency of 127.150 MHz to listen for weather reports in the destination area. Set your navigation radio to 112.20 MHz to pick up the Cape Charles (CCV) VOR. Set your heading bug to the runway heading, 200.

Takeoff straight, flying the runway heading. Climb to 2000ft and maintain.

Shortly, you should see the VOR assigned to NAV1 display receive a steady signal (the OFF flag will disappear). The DME should also settle down and display the distance to the Cape Charles VOR station. The flight to CCV will be about 26 nautical miles. As you fly, it will show your airspeed and time to arrival. It should take about ten minutes.

Turn the OBS knob until the VOR displays the TO flag and 190 degrees, the heading you should now turn to.

Fly south from Tangier, crossing an expanse of water, about ten miles until you see the Virginia Eastern Shore. You'll come upon the grass airstrip of Chance (VA89) a few minutes out from Tangier. Beyond are two flashing tower beacons. You may catch a glimpse of Weirwood/Kellam (W08) on the ocean shore, recognizable by two crossing dirt strips.

If you look carefully, you may see the little white building that is the Cape Charles VOR station. As you fly over VOR the flag will change from TO to FROM and the needle will deflect. Do not try to follow the needle. Wait until you are past the VOR. As you cross the VOR station, you should see a highway slanting across your path toward the south west. Turn to follow this highway. You'll come across a lone tower with beacon along the roadside. You'll see an access road stretching from the tower complex to the main road.

If the sky conditions permit, you may try your hand at wayfinding by following the road. If visiblity is poor, set the VOR to 180 degrees to parallel the road to the end of the peninsula. Or you can continue to fly outbound from the VOR on 190 by maintaining the same heading. The VOR needle should return to center with the FROM flag displaying. This will put you west of the bridge with a good view and the option to turn towards KORF near the initial approach fix. If you follow the highway you will need to overfly the airport, but if you stay on the 190 heading, you will be in a position to make a straight in landing.

As you fly down the peninsula you'll pass Cherrystone, Eagle's Nest, Scott and Bull Farm grass airstrips. Bull Farm is the last strip before the mouth of the Chesapeake. Just past Scott Farm you should see the first glimmer of the northern leg of the bridge. The grass strips can be very difficult to see.

As you reach the end of the peninsula, be careful to avoid the tower on Fisherman's Island at the north end of the north leg of the bridge (Note the bridge is not modeled by FlightGear...but I hope to work up one eventually). Next comes the north middle leg. Turn right a few degrees to follow the south middle leg. Watch as the deck plunges beneath the waves to allow ships to navigate the north and south channels.

As Cape Henry approaches, you'll see the Norfolk International airport to the right and the southern leg of the bridge touching the shore.

If you intend to land at KORF, you will want to start your approach soon. Otherwise, you may continue to follow the bridge to the end. Make the approach to KORF by contacting the tower for vectors. Or use the ILS.

This is a good flight to practice VOR flying on. It is a very straight flight path to the VOR requiring little adjustment and there are no other VORs in the area to confuse you.
*June 2006 by [[User:Sek|Sek]].

===Airports and coordinates===
[[Image:World-KTGI.png|thumb|right|Latitude: 37.8250835 Longitude: -75.9976665]]
* [[KTGI|KTGI - Tangier Island]] - [http://assistenza.larasrl.net/brisa/fgfs/suggested_flights/KTGI.pdf chart]
* [[KORF|KORF - Norfolk International]] - [http://assistenza.larasrl.net/brisa/fgfs/suggested_flights/KORF.pdf chart]

required scenery tile: ftp://ftp.sunsite.org.uk/sites/ftp.flightgear.org/flightgear-ftp/Scenery/w80n30.tgz

===Suggested aircraft===
[[Image:KTGI-003.png|thumb|left|surroundings]]
[[Image:KORF-001.png|thumb|right|landing to KORF]]
I have tried this trip using a Seneca II
* [[Piper PA34-200T Seneca II]]
<div style="clear:both;"></div>

===FlightGear launching===
fgfs --airport=KTGI --runway=20 --timeofday=dusk --aircraft=SenecaII
<div style="clear:both;"></div>

==Prince George to Calgary Springbank==
A beautiful flight is from Prince George (CYXS), to Calgary Springbank (CYBW). Route created by reed, which can be seen at {{forum link|t=9772|text=the forums}}
*Published in [[FlightGear Newsletter November 2010]] By [[User:Cael|Cael]].
==Ketchikan to Juneau==
It's cold where we will go so dress up warm and if we are lucky we might see whales during our flight. Don't fly too high to enjoy the amazing views, and there is a small challenge at the end. The runways we will use are long enough for bigger aircraft (7000+). Total length of the trip will be around 245 NM. So, hop in the cockpit of your favourite airliner.

Alaska, here we come! Enjoy!
#Park your aircraft on PAKT, [http://www.borough.ketchikan.ak.us/airport/airport_history.htm Ketchikan International], runway 11. The wind is coming from '''South''', change the weather if needed (SE is ok too).
#Fly North towards [[NDB]] Fredericks Point on 372.0 for 94 NM.
#Fly towards [[NDB]] Five Fingers on 295.0 for 39 NM.
#Fly towards [[NDB]] Gustavus on 219.0 for 77 NM.
#Fly towards [[NDB]] Coghlan Island on 212.0 for 32 NM.
#Set the [[ILS]] on 109.9 and land your aircraft (after 4 NM) on PAJN, [http://www.juneau.org/airport/ Juneau International], runway 08.
If you feel warm after this landing, you just crossed a NORAD microwave site, so that is why.
*October 2011 by [[User:PH-JBO|PH-JBO]] [[FlightGear Newsletter November 2011]]
==Searching Wizard Island==
*USA, Oregon, Klamath County
With one [[VORTAC]] behind our back we do an [[IFR]]/[[VFR]] search of Wizard Island, a mysterious place, a sacred place for native Americans. You might even find the <tt>Old Man of the Lake</tt>.

Don't pull up the map, that would spoil the surprise but I promise '''unique views'''. We will land on a short lawn runway. Terrain [[altitude]] will range from 4,000 to a max of 8,930 feet and down again. Total length of the trip will be about 50 NM. Select your aircraft with care. It must have one working navigational radio (VOR-DME), a strong engine, a strong undercarriage, must be capable of a good climb and a steep descend. I suggest to use Fair weather (Environment=>Global Weather). If needed remove some clouds (View=>Rendering Options=>Slider 3d Clouds to the left).
[[File:Mount Scott.jpg|thumb|250 px|Mount Scott (8,929 feet) just after depart from 2S7 (Two Sierra Seven). Wizard Island is just to the North-West of it.]]
*Park your aircraft on 2S7 (Two Sierra Seven), Chiloguin-State.
*Set [[NAV1]] on 115.9 (Klamath Falls VORTAC) and on radial 323<sup>o</sup> (Magnetic). We are at an [[elevation]] of 4,217 feet. Set QNH. Set heading bug at 275<sup>o</sup> (Magn).
*Take off an fly the course set with the heading bug.
*Intercept the radial.
*Monitor distance and you will find Wizard Island at 50 NM from Klamath Falls. The island has an elevation of 6,673 feet. I suggest a full 360<sup>o</sup> turn, take pictures.
*Set radial 318<sup>o</sup>, keep the same frequency. Do a new radial intercept.
*Try and find the airstrip (3S6, Three Sierra Six, Toketee-State) at 71 NM from Klamath Falls with an elevation of 3,361 feet, runway heading 275<sup>o</sup> (Magn). There are bumps around you should avoid.
*If you are capable of finding the island, finding the airstrip and landing without a crash, in one go..., you are a wizard.

Click [http://en.wikipedia.org/wiki/Crater_Lake this link] '''after''' you have landed so you know what amazing landscape you have seen.

*December 2011 by [[User:PH-JBO|PH-JBO]]. Published [[FlightGear_Newsletter_March_2012|Newsletter March 2012]].

=South America=
==Southern Tip of Chile==
[[Image:Scgz-001.png|thumb|left|right after take off]]
[[Image:Scgz-004.png|thumb|right|Some part of the scenery]]
Gary Carvell: Here is a suggestion for the FlightGear Places to Fly page. I don't have any particular routes, just fly around and enjoy the gorgeous scenery.<BR/>
These three airports are in the same region of the very southern tip of Argentina. This area is a scenic wonderland - a maze of islands, mountains, and ocean channels. Hours of entertainment.<BR/>
SCGZ - Puerto Williams Guardiamarina Zanartu Airport, Chile Located on the north coast of Isla Navarino facing the Beagle Channel. At 55 deg S. longitude, Puerto Williams is considered the southernmost town in the world.<BR/>
SAWH - Ushuaia Islas Malvinas Airport
SAWO - Ushuaia Est Aeronaval Airport
Ushuaia, on the south coast of Isla Grande de Tierra del Fuego, on the the Beagle Channel.
<div style="clear:both;"></div>
===Airports and coordinates===
[[Image:Sawh-004.png|thumb|left|Approaching Ushumaia Malvinas Argentinas]]
[[Image:World-scgz.png|thumb|right|Latitude: -54.931072 Longitude: -67.626261]]

* [[SCGZ|SCGZ - Guardiamarina Zanartu]] - [http://assistenza.larasrl.net/brisa/fgfs/suggested_flights/SCGZ.pdf chart]
* [[SAWH|SAWH - Ushuaia Malvinas Argentinas]] - [http://assistenza.larasrl.net/brisa/fgfs/suggested_flights/SAWH.pdf chart]
* [[SAWO|SAWO - Ushuaia Est Aeronaval]] - [http://assistenza.larasrl.net/brisa/fgfs/suggested_flights/SAWO.pdf chart]
<div style="clear:both;"></div>

===Suggested aircraft===
[[Image:Scgz-002.png|thumb|left|Just left the scgz airport]]
I personally like to fly this area in the [[Consolidated_Aircraft_PBY_Catalina|Catalina]], it's a great sightseeing plane with the advantage that you can take off and land just about anywhere.
* [[Consolidated_Aircraft_PBY_Catalina|Catalina]]
<div style="clear:both;"></div>

===FlightGear launching===
fgfs --airport=SCGZ --aircraft=Catalina
<div style="clear:both;"></div>

==Copacabana to San Rafael over Lake Titicaca==
Bolivia to Peru. This trip will lead you over one of the highest and deepest lakes in the world towards the highest airfield in the world. It a demonstration of a [[IFR]] flight towards a fix and a demonstration how accurate FlightGear simulates air density and the effects it has on aircraft.
[[File:Slcc-sprf.jpg|thumb|200px|left|Flight and fix SLCC to SPRF]]
Place your aircraft on the airfield [http://en.wikipedia.org/wiki/Copacabana,_Bolivia SLCC, Copacabana], with an [[elevation]] of 12,592 feet. FlightGear will show snow all around you but that is not very realistic so let's clean up. View=> Rendering Options=> Snow line=> Set to max. (5,000M).

We will fly towards and land at SPRF. If you would enter SLCC and SPRF in [[Kelpie]] planner you probably would not be able to find SPRF. To find SPRF I am adding an additional VOR-DME station and for a good fix give you another VOR-DME. Try Kelpie planner to plan this route and compare with this suggestion.

Equipment preparation. Set [[NAV1]] to [http://en.wikipedia.org/wiki/Juliaca Juliaca] VOR-DME on 155.55 with a radial of 311° (magnetic). Set [[NAV2]] to Arequipa VOR-DME on 113.7 with a radial of 212°. During our flight we will fly with [[true altitude]] as set with [[QNH]], keep QNH updated. Arm the autopilot with the [[heading bug]] at 311° and an initial altitude of 13,500 feet.

Take off and if you took the wrong RW pull up hard. Take a small tour over [http://en.wikipedia.org/wiki/Titicaca lake Titicaca], see the floating islands and try to find the lost golden treasure. Intercept the nearest radial on NAV1 towards Juliaca (about 311°).

Just before Juliaca is a hill so while on lake Titicaca increase altitude to 14,200 feet, the [[VFR]] part of this trip is over. After passing Juliaca set the radial of NAV1 to 352° and set the altitude to 17,422 feet. We will fly from NAV1 and slowly increase altitude.

At a distance of about 60 NM set the heading bug on the current course. Monitor the distance to NAV1, the radial of NAV2 and the distance to NAV2. At a distance of 74.5 NM to NAV1, a distance of 140.7 NM and at the '''radial''' intercept of NAV2 should be the runway. So, from 60 NM onwards, look outside the window, then at NAV1 and then NAV2 etc.

If you are at 80NM to NAV1 you have missed the airfield but you still won't hit any hills (unless you bank left). Bank right and set the heading bug to 172°. Fly back towards NAV1 and intercept the radial 352° at about 50NM again to repeat the search.

The runway SPRF, San Rafael, has a elevation of 14,422 feet and a heading of 297°/ 117°. Our initial altitude has been set 3,000NM above the RW elevation. That should give sufficient room for navigation.

After you have seen the airfield set the radial of NAV1 to 297°, the heading of the runway (not the course to the runway) as a visual aid. Land on RW 30 (and not on RW 12 unless you are a show-off). Oh, there is a small hill in front of RW 30, just so you know.

Decreasing speed at this altitude can be a bit tricky. The air is thin and does not give much resistance. Next to that, the difference between [[indicated airspeed]] and [[ground speed]] is very noticeable. The ground speed is much higher as the indicated airspeed.

After a successful landing, try to discover the origin of the Amazon river since we are now at the starting point of that trip.
* October 2011 by [[User:PH-JBO|PH-JBO]], published in [[FlightGear_Newsletter_February_2012#Suggested_flights| Newsletter February 2012]].

==Origin of the Amazon River==
[[Image:SPRF-001.png|thumb|left|high altitude]]
[[Image:SPRF-002.png|thumb|right|high altitude]]
Peru. For this [[IFR]] tour (with [[VFR]] parts) we take off from the highest airfield in the world to discover the origin of the [http://en.wikipedia.org/wiki/Amazon_River Amazon river] in South America. I promise spectacular mountains and valleys. The total length of this trip is about 175 NM.

Place your aircraft on the airfield SPRF, San Rafael. FlightGear will show snow all around you but that is not very realistic so let's clean up. View=> Rendering Options=> Snow line=> Set to max. (5,000M).

Equipment preparation: Set [[NAV1]] to [http://en.wikipedia.org/wiki/Arequipa Arequipa] VOR-DME at 113.7 with a radial of 176° (magnetic). Set [[NAV2]] to [http://en.wikipedia.org/wiki/Cusco Cusco] VOR-DME at 114.9 also with a radial of 176°.
Set [[QNH]] and during flight keep correcting it, it's a bad idea to use [[Pressure altitude]] during this flight. Set the [[heading bug]] to 250°. Arm the [[autopilot]] and set the initial [[altitude]] to 16,000 feet.

The airfield SPRF, San Rafael has an [[elevation]] of 14,422 feet. That altitude will cause problems during take-off. It takes a lot longer for the aircraft to gain sufficient speed for take-off, also the take-off speed that is needed is higher as you would expect. Perhaps an additional notch of flaps is needed.

Take-off, avoid the bumps (there are plenty) and fly a course of 250°. After about 80 NM you will fly over the radial of NAV1. Intercept the radial towards Arequipa. At a distance of 75 NM towards NAV1 you will have to increase altitude to 19,000 feet.

At a distance of 50 NM towards NAV1 and 118 NM from NAV2 you will see and cross over the mountain [http://en.wikipedia.org/wiki/Nevado_Mismi Nevado Mismi] with an altitude of 18,362 ft. The rains and water on the area to the right until Nevado Mismi will leave towards the Atlantic ocean through the Amazon river. Anything to the left and after Nevado Mismi will leave towards the Pacific ocean.

After Nevado Mismi you are tempted to descend. Don't. Just before the airfield is [http://en.wikipedia.org/wiki/Chachani Mt.Chachani] with an altitude of 19,872 feet and to the East is the active volcano [http://en.wikipedia.org/wiki/El_Misti El Misti] with an altitude of 19,101 feet. You can either increase the altitude and fly over the airfield or keep the altitude, even descend and fly between the mountains, your choice depends on the visibility.

Fly using the heading bug and set NAV1 to [[ILS]] 109.7 with a radial of 93.2°. We will land at airfield [http://en.wikipedia.org/wiki/Rodr%C3%ADguez_Ball%C3%B3n_International_Airport SPQU, Rodriguez ballon], that has an elevation of 8,405 feet. There is a reason this airfield has just one ILS. The area South-West of the airfield is below 11,405 feet and is safe to navigate.

Position the aircraft in front of the runway at an altitude of 11,405 feet, catch the [[glidescope]] at a distance of 9.5 NM and land your aircraft. After landing and parking your aircraft crawl into the tower to look around.

Happy flying!

* October 2011 by [[User:PH-JBO|PH-JBO]]. Published [[FlightGear_Newsletter_March_2012|Newsletter May 2012]].

===Airports and coordinates===
[[Image:SPQU-001.png|thumb|left|pre - landing]]
[[Image:World-SPRF.png|thumb|right|Latitude: -14.267 Longitude: -70.467]]
* [[SPRF|SPRF - San Rafael]] - [http://assistenza.larasrl.net/brisa/fgfs/suggested_flights/SPRF.pdf chart]
* [[SPQU|SPQU - Rodriguez Ballon]] - [http://assistenza.larasrl.net/brisa/fgfs/suggested_flights/SPQU.pdf chart]

required scenery tile: ftp://ftp.sunsite.org.uk/sites/ftp.flightgear.org/flightgear-ftp/Scenery/w020s80.tar.gz
<div style="clear:both;"></div>

===Suggested aircraft===
[[Image:SPQU-002.png|thumb|right|landed]]
I recomend a powerful jet angine airplane, but not too heavy !
* [[Cessna 550 Citation II]]

<div style="clear:both;"></div>

===FlightGear launching===
fgfs --airport=SPRF --aircraft=Citation-II
<div style="clear:both;"></div>

=Middle East=
==Israel to Jordan over the Dead Sea==
[[Image:LLBS-001.png|thumb|left|take off]]
[[Image:LLBS-002.png|thumb|right|flat land]]
Dead Sea is the lowest water elevation on the Earth. Take off from the Beer-Sheva Teyman airport and head East-North-East. About half way there, after the southern Hebron mountains ridge, there'll be a sharp drop-off down to the Dead Sea --- the lowest exposed point on the Earth.<br/>
<br/>
It's really fun to descend and explore the beautiful coastline. In the real life, you wouldn't like to fly low over this water there of your own will --- while you don't need a life vest in the Dead Sea, the water is pretty caustic there for one's eyes. Once you're done marvelling the sights, continue on to the Queen Alia airport.
<div style="clear:both;"></div>
===Airports and coordinates===
[[Image:LLBS-006.png|thumb|left|landing in the dead sea, notice the altitude !]]
[[Image:OJAI-007.png|thumb|right|landing at Queen Alia Intl.]]
[[Image:World-LLBS.png|thumb|right|Latitude: 31.29037800 Longitude: 34.71922500]]
* [[LLBS|LLBS - Teyman]] - [http://assistenza.larasrl.net/brisa/fgfs/suggested_flights/LLBS.pdf chart]
* [[OJAI|OJAI - Queen Alia Intl]] - [http://assistenza.larasrl.net/brisa/fgfs/suggested_flights/OJAI.pdf chart]

required scenery tile: ftp://ftp.sunsite.org.uk/sites/ftp.flightgear.org/flightgear-ftp/Scenery/e030n30.tar.gz
<div style="clear:both;"></div>

===Suggested aircraft===
[[Image:LLBS-003.png|thumb|left|approaching the dead sea]]
[[Image:LLBS-004.png|thumb|right|there is also a minor airport]]
* [[Albatross]]

<div style="clear:both;"></div>

===FlightGear launching===
fgfs --airport=LLBS --aircraft=Albatross
<div style="clear:both;"></div>

=Europe=
==Edinburgh to Oban==
See article: [[Edinburgh to Oban]].

==Oban to Prestwick==
The west coast of Scotland offers some stunning scenery and a number of small airfields and airports to land at on both the mainland and the small islands the dot the coast. The distances between the various airfields are quite small, and some of the runways are on the short side, so STOL or GA aircraft are ideal. The tour suggested here follows part of a microlight trip I made this month, photos of which can be found [http://www.nanjika.co.uk/photos/gigha/ here].

Oban airport (EGEO) lies on the west coast of Scotland, and offers fuel (both AVGAS and AVTUR) and a North/South tarmac runway.

From Oban it is just a 10 minute flight west to the grass airfield of Glenforsa (EG45), on the north-east coast of the island of Mull. Due to the hills and water channel, this airfield often gets quite strange wind patterns - the weather can be perfect in Oban, but much gustier and windier at Glenforsa. At times the windsocks at either end of the runway can blow in completely opposite directions!

Some distance north of Oban lie the airfields of the Isle of Skye (EG57) and Plockton (EG81). This is an excellent place from which to explore the mountains of the Isle of Skye, known as the Cuilins.

Heading south from Oban, one can follow the coast to the island of Jura, with it's distinctive hills (The Paps of Jura). From Jura one can head south to the island of Islay with its numarous malt whisky distilleries (many of which are modelled in FG). Islay Airport (EGPI) has extensive runways. From Islay head north east to the tiny island of Gigha. Despite it's small size, it too has an airfield (EG44), though the FG version is tarmac rather than grass.

From Gigha head east over the Mull of Kintyre, to the hilly isle of Arran, then north east to the Isle of Bute. Both islands have very small grass airstrips, which are sadly not present in FG. From Bute you can head south east to Prestwick International (EGPK), famous for being the only place Elvis touched down in the UK, and a fine place to end our tour.
*Published in [[FlightGear Newsletter July 2011]] by [[User:Stuart|Stuart]]

== Edinburgh to Dundee ==
Edinburgh Airport (EGPH) is located to the West of the city of Edinburgh and south of the Forth rail and road bridges. You'll need the w010n50 scenery and the latest set of objects from the scenery DB which include a number of models for the Edinburgh area.

From Edinburgh Airport, head north and circle the bridges, then follow the coast on the south eastwards past Edinburgh (watch out for the Castle!) and to East Lothian and Bass Rock - a volcanic plug in the sea that is host to thousands of sea-birds.

There are a number of sights in East Lothian, include a distillery.

If you wish to continue your tour, head back North, crossing the Firth of Forth to the Kingdom of Fife. Head approximated North West, tracking towards the Perth VOR (110.4). There is an airport here (Perth Scone, EGPT), but instead we will now track out on the 090 radial and pick up the ILS to Dundee Airport (108.10) landing beside the sea.
* September 2006 by [[User:Stuart|Stuart]].

==Austrian alps soaring==
Discover the Austrian alps with a glider. [[Pinzgauer Spaziergang]]

== Sightseeing the Alps in a C172 ==
This tour will guide you to many of the most famous mountains, valleys, glaciers, snowfields, winter and summer vacation areas, etc. in the European Alps. In addition there are several hints to visit nearby areas of interest. On the tour you will visit Switzerland, Italy and France.
See the detailed description in: http://www.emmerich-j.de/FGFS/Alp-flying.pdf (mirrored to https://beni.hallinger.org/fgfs.nobackup/Alp-Tour-Jomo/)
*February 2011 by [[User:Jomo|Jomo &dagger;]].;

* The scenic trip does take about 2 hours.
* Skyvector route: https://skyvector.com/?ll=46.464097146192884,7.159790050777061&chart=301&zoom=6&fpl=%20LSZC%204700N00836E%204647N00840E%204642N00836E%204637N00835E%204634N00823E%204634N00812E%204633N00809E%204634N00805E%204634N00801E%204631N00803E%204624N00746E%204619N00745E%204618N00753E%204614N00752E%204612N00749E%204609N00747E%204603N00746E%204601N00745E%204600N00738E%204555N00724E%204555N00712E%204553N00703E%204547N00652E%204549N00649E%204604N00634E%20LSGG

== Salzburg to Zell am See via Hallstatt ==
[[File:LOWS-LOGO-LOWZ.jpg|thumb|The route for Salzburg to Zell am See via Hallstatt]]
This flight will bring you around a very scenic region of the austrian alps.
* [https://skyvector.com/?ll=47.5666119817603,13.107925427128999&chart=301&zoom=3&fpl=N0100A040%20LOWS%204735N01311E%204736N01339E%204733N01340E%204733N01343E%204735N01343E%204738N01355E%204727N01357E%20LOWZ SkyVector route]
* Suggested plane: C172 or C182
* This is VFR only, so pick suitable weather. There are no usable navaids for this trip.
* Trip takes around 1 hr. air time at 120 KTAS.
* Fly at an altitude of about 4000ft or so (the entire trip can be done at that altitude safely).

* Start ''Salzburg (LOWS)''; follow the Autobahn in the valley to the southeast until you reach the fork at ''Golling''. To the south you see the Mountains of the ''Tennengebirge''.
* Alternatively (and I recommned that), you can also deviate sothwest around ''Mt. Untersberg'' (1972m, hosting germanys longest and deepest cave, the ''Riesending'') to visit lake ''Königsee'' and watch the peaks of the ''Steinernes Meer'' (the dominant and very famous ''Mt. Watzmann'', 2713m!) and north side of the ''Mt. Hochkönig''. You need to climb to at least 6200ft to cross the final ridge at the end of the lake valley. After crossing, descend to 4000ft, follow the valley and fly north at the next valley to rejoin the route.
* Turn east and follow the valley and hills, aim for a prominent V-shaped incision at the end. Fly through there and you suddenly break out at the lake ''Hallstätter See'', a fjord-like lake 125m deep.
* Follow the ''Hallstätter See'' to the south, on its western shore is the famous town of ''Hallstatt''. At the mountain to your right (north of Hallstatt) is a very old settlement dating back to the late bronce age (Hallstattzeit, c. 800–450 BC) and there was a very important Salt mine dating back to that time and important archeological grave findings.
Looking south you can see the ''Dachstein'' (2995 m), a high peak hosting the ''Hirlatzhöhle'', with 120km the twentiest longest and with 1560m sixth deepest cave of planet earth.
* Follow the valley east bend to ''Obertraun'', and then north over the ''Koppenpass'' and the town of ''Bad Aussee''.
* From ''Bad Aussee'', fly straight to the lakes ''Grundlsee'' and ''Toplitzsee'' (you can't see the latter yet).
* Between the two, turn southwards and aim for the reservoir lake ''Salza'' which is in the sharp incision you can see to the south.
* After passing the reservoir, you may try to get down to ''Niederoblarn'' (LOGO) to the southeast, it's a short airfield.
* From there, follow the railway in the valley of Enns westwards, LOWZ is about 20 minutes away. On your right side watch out for the other side of the ''Dachstein'' and the town of ''Schladming'', which lies down in the valley next the rocky hills with the river flowing trough. Look for the railway and the river Enns.
* Behind ''Schladming'' (south of Mt. ''Dachstein'', approximately halfway of the distance LOGO/LOWZ) the valley will widen a bit again, featuring a rocky mountain in the middle of the valley. Continue to follow the railway and river bending nortwest arond the small mountain.
* Near the bigger town of ''Radstadt'' the valley will open significantly. Follow west, heading for the next town ''Altenmark'' at the end of the opening.
* The railway will bend north at ''Altenmark'' and soon join the Autobahn A10/E55. This is the point we need to go southwest and follow the next valley.
* The valley leads us westward to the Town of ''St. Johann/Pongau''. probably around the middle of the valley you can spot the prominent ''Mt. Hochkönig'' (2941m) northwest of ''St. Johann'' and the ''Tennengebirge'' to its right.
* Once reaching ''St. Johann'', continue to follow the next big valley west-southwest.
* After about 16 miles you will reach ''Zell am See'' (LOWZ) where we will land after around one hour flight time in total. Beware this is a short field.

== Zell am See to Innsbruck via Mt. Venediger ==
[[File:LOWZ-LOWI.jpg|thumb|The route for Zell am See to Innsbruck]]
This flight will bring you to two of the core peaks of the Alpenhauptkamm.
* [https://skyvector.com/?ll=47.201656734623775,12.160079968084839&chart=301&zoom=3&fpl=N0100A120%20LOWZ%20LOWZ%204708N01241E%204708N01221E%204706N01214E%204710N01152E%204724N01150E%20LOWI SkyVector route]
* Suggested plane: C172 or C182
* This is VFR only, so pick suitable weather. There are no usable navaids for this trip.
* Trip takes around 45 minutes air time at 110 KTAS.
* Climb to at an altitude of about 10000ft or so after starting from [[:File:Lowz-parking.jpg|Zell am See]].

* After starting fly into the valley southwest over the town of ''Kaprun''. Maybe you need to circle a bit to gain altitude, near the mountains we need at least about 10000ft!
* Follow the valley until you overfly two lakes (''Stausee Wasserfallboden'' and ''Moorboden''). To your left you can see ''Mt. Großes Wiesbachhorn'' (3564m).
* The end of the valley goes over into a flank of the ''Großglockner'' which is near to the south. Follow the west bend of the valley end and fly over the lakes ''Tauernmoossee'' and ''Weißsee''. After you climb out of the valley, you already should see the peak of ''Mt. Venediger'' on the front left. Aim to the saddle right of its peak.
* You then fly that direction over several valleys that go from south to north, until you hit the very big valley that bend from south to west. The ridgeline right of that valley is the border between the Austrian states Tirol and Salzburg. Follow the valley up to the ''Venediger'', passing the ''Mt. Sandebentörl'' (2751m), still aiming for the saddle.
* Shortly after you reach the end of the valley and need to overfly the saddle with the glacier ''Venedigerkees'' behind it. The ridgeline is again the border between Tirol and Salzburg. Directly south of the ''Venedigerkees'' is the pyramid of ''Mt. Venediger''.
* Follow ''Venedigers'' ridge to the southwest, skip the first valley and overfly the next ridge.
* From here you can deviate into the valley north and visit the ''Krimmler Wasserfälle'', and from there west trough the main valley.
* If you instead follow the planned route westwards, aim to the peak of ''Mt. Zillerplattenspitze'' (3148m) with the small lake ''Eissee'' to its south flank which you should already see. This is a little hard to get right, but don't fly directly into the big valley but aim right to the second row mountain peaks at about 280 heading.
* Overfly the ridge with ''Eissee'' and follow the valley from there nothwest with the reservoir ''Zillergründl'' and ''Mt. Reichenspitze'' (3303m) to its right; until you reach the town ''Mayrhofen'' where the current valley meets the ''Zillertal'' valley. You also should start to descend now to about 3500ft with a rate of roughly -1000fpm.
* From ''Mayrhofen'' follow the ''Zillertal'' valley north and when reaching the ''Inntal'' valley near the town ''Jenbach'', Innsbruck Airport is a few minutes to the west. If you like, you can divert north at ''Jenbach'' to visit ''Achensee'', and even continue further north to land at Munich via lake ''Tegernsee'' or via the Isartal over ''Bad Tölz''.

== Crossing the alps ==
[[File:ED02-LIPB.jpg|thumb|The route for Fuessen to Bolzano]]
This trip brings us from germany via austria to italy, crossing the alps, visiting the famous castle Neuschwanstein and Mt. Zugspitze, germanys highest peak.
* [https://skyvector.com/?ll=47.068251080980836,10.959411633048108&chart=301&zoom=5&fpl=N01204735N01041E%204734N01045E%204729N01042E%204726N01046E%204724N01054E%204712N01054E%204704N01058E%204656N01103E%204655N01106E%204653N01109E%204650N01110E%204648N01113E%204638N01110E%20LIPB SkyVector route]
* Suggested plane: C172 or C182
* This is VFR only, so pick suitable weather and time (I suggest to start with the first light/sunrise).
* There are no helpful navaids for this trip, but Bolzano NDB: 362 BZO may serve as a final guidance.
* Trip takes around 45 minutes air time at 120 KTAS.

* Start at ED02 Fuessen, climb to about 3000 and head southeast to visit castle Neuschwanstein, south of the Forgensee.
* After looking at the castle (challenge: fly close around behind it), we start climbing to 3500 and aim southwestish and cross over from germany to austria.
* Fly into the big valley directing south. East of Reutte start climbing 500fpm to 6000 and follow the railway in the valley to the southeast.
* Once the valley opens significantly, you can see the famous mountain Zugspitze (germanys highest peak, 2962 m) to the front.
* Head southwards around the Mt. Gartnerwand over town Ehrwald and fly between the two small peaks over the Marienbergjoch mountain pass, 1789m/5870ft (between Mt. Wanning and Mt. Marienberg; challenge: who can make it with the least altitude?).

* After overflying the second mountain, to the south comes a new valley called Ötzal where you fly into.
* Follow that valley all the way to the south and slowly climb to at least 8600 now (300fpm or so). Note overflying Längenfelden, where the dominant valley joins from the east with the river Fischbach, halfaway the leg; this looks similar to the end, but isn't.
* Follow the valley until it starts to branch in all different directions at the end (over the town of Sölden and Zwieselstein).
* We follow the Southeast main branch and then turn quickly to a smaller valley branching off directly eastwards (look for the mountain pass road).
* That brings us to the mountain pass of the Timmelsjoch and is the place where we cross over to Italy.

* After passing, we can descend to 2500 or so, following the terrain. Follow the valley and its river "Passer" southeast, and follow its bend to the south.
* Follow the valley and make a nice turn around Mt. Kolbenspitze's east ridge, over San Leonardo, still following the Passer river now southwards.
* Where the valley hits the next big valley "Etschtal", is a bigger famous city called Merano. From there we follow the River Etsch and the Autobahn (highway) to the south and are soon approaching the somewhat hidden airport of Bolzano (LIPB) after an estimated time of somewhat under one hour at 120 knots.

From here you can also continue more to the south to Trento (LIDT, total FT ~1:00) or Verona (LIPX, total FT ~1:20) - just follow the river Etsch to the south! Venezia is also not far away, just ~30 minutes/62nm to the east of Verona.

==Grenoble Le-Versoud==

[[Image:LFLG.jpg|800px]]

France : '''LFLG''' ( Grenoble Le-Versoud ) airport : border of Alps
*P.A.F. home base [http://equipe-flightgear.forumactif.com/ link]
*Scenery : http://clemaez.fr/flightgear/flightgearfrance_05062011.tar.gz
*Texture : http://clemaez.fr/flightgear/pattentextures_maj24082011.tar.gz

* Take-off from Grenoble le Versoud (LFLG). Head south following the general direction of the Alps. Bearing left (East) will take you into high alpine territory, while towards the West lie the plains of the Rhône valley. Once you reach the Mediterranean coast, follow it to land in Marseilles (LFML), Nice (LFMN), or another smaller airport serving the French Riviera.
*Published in [[Custom France Scenery]].

==Gulf of Finland sightseeing tour==
Take a VFR sightseeing tour over the Gulf of Finland from Helsinki to Tallinn! Estonia's landmarks are all recent additions, while Helsinki was one of the first cities to have original models in the scenery model database.

Take off from the smaller EFHF airfield in Helsinki, or try your luck fighting the virtual traffic at Vantaa, and head toward the port of Helsinki. Look for the Hartwall Arena, the Pasila tower, the railway station and the Olympic Stadium along the way. Make your way out over the Gulf flying just west of south - a heading of 190 should set you up nicely for a sightseeing tour of Tallinn. Try to come in from the west and do a sweeping left turn over the capital of Estonia, looking out for the Swissotel, Olympic Hotel, the Television tower, and other important landmarks in the capital city of Estonia. Make sure you look out for St. Olaf's Church, the tallest building in the capital city. Make your way over the Ulemiste Jarv (lake) to land on runway 09 at Tallinn's main airport.

If you desire, you can do a touch-and-go at Tallinn and set your course southeastward, landing at Tartu Airport, which is also modelled in FlightGear.

The distance between Helsinki and Tallinn is about 50 miles or 80 kilometres, while Tartu is twice the distance from Tallinn at 100 miles/160 kilometres. Fly a heading of 135 to get to Tartu from Tallinn.
*Published in [[FlightGear Newsletter October 2010]] by [[User:Statto|Statto]].

==Azores==
[[Image:LPLA-001.png|thumb|left|take off]]
[[Image:LPLA-002.png|thumb|right|approaching island]]
The [http://en.wikipedia.org/wiki/Azores Azores], set in the middle of the Atlantic ocean, has had many names. Fortunate Isles, the Blue Islands, the Islands of Tin and Silver, the Islands of the Seven Cities. We can add, the Islands of Amazing Sights and Flights.

Our flight is to celebrate the amazing views FlightGear can give us.

Start your plane at [[Lajes Field]] (LPLA). This once was an emergency landing site for the [[Space Shuttle]] so you will have plenty of room to take off.
We will have to fly an odd pattern. The reason for that: if you don't fly too high (stick around 3000 while you can) you will have some amazing views.

Next, fly towards and over LPPD. Look out the window and enjoy the view. Then head out towards LPHR. If you feel LPHR coming near, look out the window good, you might have to pull your plane up.

Happy flying!
*Published in [[FlightGear Newsletter August 2011]] by [[User:PH-JBO|PH-JBO]]

===Airports and coordinates===
[[Image:LPPD-001.png|thumb|left|over the island]]
[[Image:LPPD-002.png|thumb|right|landing]]

* [[LPLA|LPLA - Lajes Field]] - [http://assistenza.larasrl.net/brisa/fgfs/suggested_flights/LPLA.pdf chart]
* [[LPPD|LPPD - Ponta del gada]] - [http://assistenza.larasrl.net/brisa/fgfs/suggested_flights/LPPD.pdf chart]

required scenery tile: http://mirrors.ibiblio.org/pub/mirrors/flightgear/ftp/Scenery-v2.4.0/w020n30.tgz
<div style="clear:both;"></div>

===Suggested aircraft===
* [[Cessna 550 Citation II]]

===FlightGear launching===
fgfs --airport=LPLA --aircraft=Citation-II
<div style="clear:both;"></div>

== Canary Islands Trip ==

An archipelago in the middle of the Atlantic sea, stunning beauty where you won't expect it. Seven islands, seven continents, thats what the canarian people say. And it's true, you will face seven totally different islands and nine different airports.
Take off from the largest one, GCLP, at the main island Gran Canaria. Leave the beautiful island heading to the west, and land at GCTS, the southern airport at Tenerife. Enjoy the view on Spains highest mountain, the glaciered Teide, when flying to La Gomera (GCGM), one of the greenest islands there. Master the short runway, and enjoy the view, before taking the challenge and approach El Hierro (GCHI). A short runway, with cliffs and rocks on both ends will cause you to sweat. From this island, which was claimed to be the western end of the world in medieval times, you'll turn to the beautiful and wild island of La Palma (GCLA). The next approach will be historical, because you are approaching the notorious Tenerife North (GCXO). Yes, I am serious, you will face that airport, where the worst civil plane crash ever took place. But you needn't worry, if you got that far, you will do this approach as easy as any other. The longest flight on your trip will take you to the eastern island, Lanzarote (GCRR). Take a look at the volcanic-red mountains, the vineyards, and the beaches. You want more beaches?? Depart to the south-west, fly over the small island of Los Lobos, and land in the holiday-paradise Fuerteventura. Enjoy dunes, bays, and very nice long beaches, before you finally touch down in Fuerteventura (GCFV). You want to stay? Okay, let's taxi to a parking position, and cut off the engines. If you still want more, fly back to Gran Canaria's GCLP, where we started our trip.

Custom scenery: [[Canary Islands Custom Scenery]] / direct source: https://github.com/D-ECHO/Canarys

=== Suggested Aircraft ===

* small civil aircraft, such as the Cessna Skylane, Skyhawk, or Citation
* small airliners, like the Q400, the ATR72, the CRJ200, or similar

Route by Flycanarias

<gallery>

</gallery>

==Gibraltar==
[[Image:LEMG-010.png|thumb|left|take off]]
[[Image:LEMG-011.png|thumb|right|just after take off]]
Traffic lights turn red, gates are closed. The only busy main road to the peninsula is closed and all the cars and trucks are waiting patiently. Waiting for a train to pass? No. Waiting for a plane to pass since the main road crosses a busy runway.

On both sides water and being crossed by a busy main road can only be one runway: [http://en.wikipedia.org/wiki/Gibraltar_Airport Gibraltar airport]!

One would expect an ILS installed on such a tricky runway but no, you will have to guess where it is and how far away it is. Not even an ADF points to it.

Take off from LEMG (Malaga). Go South-West and find the runway of LXGB somewhere to the right of the rock. Happy guessing!
*Published in [[FlightGear Newsletter September 2011]] by [[User:PH-JBO|PH-JBO]]
<div style="clear:both;"></div>

===Airports and coordinates===
[[Image:LEMG-013.png|thumb|left|search for this]]
[[Image:LEMG-015.png|thumb|right|landing]]

* [[LEMG|LEMG - Malaga]] - [http://assistenza.larasrl.net/brisa/fgfs/suggested_flights/LEMG.pdf chart]
* [[LXGB|LXGB - Gibraltar]] - [http://assistenza.larasrl.net/brisa/fgfs/suggested_flights/LXGB.pdf chart]

required scenery tile: http://mirrors.ibiblio.org/pub/mirrors/flightgear/ftp/Scenery-v2.4.0/w010n30.tgz
<div style="clear:both;"></div>

===Suggested aircraft===
* [[Piper Aerostar]]

===FlightGear launching===
fgfs --airport=LEMG --aircraft=aerostar700 --adf1=300 --nav1=300:117.80
<div style="clear:both;"></div>

=Asia=
==Khorog, Tajikistan==
[[File:Fw190HinduKush.jpeg|left|thumb|Approaching a bank of snow-covered mountains in the south of the Hindu Kush]]
Surrounded by spectacular mountains and nestled in the end of a valley, Khorog Airfield (UT1C) makes an interesting place to land. It can only be approached by flying down the curved valley that snakes in from the North. Flying from here to OPCH (Chitral, Pakistan) at around 500ft AGL all the way is a wonderful way to explore the Hindu Kush mountains.

If you bring a piston engined aircraft, be prepared to adjust the mixture as you climb - at the highest point in the flight, you will be at around 22000ft. Also, don't forget to carry plenty of fuel - there are very few airfields in the Hindu Kush that exist in FlightGear. This is a scenery bug that will hopefully be fixed in the future.

*October 2011 by [[User:Armchair Ace| Armchair Ace]], published in [[FlightGear_Newsletter_January_2012#Suggested_flights| Newsletter January 2012]].
<br>
<br>
<br>
== Central Karakoram range ==
Let's explore one of the highest regions of the planet - the central Karakoram with the densest concentration of mountains of 8000 m and above. We're going to need a good climbing performance for the trip - even the frozen plateau of Baltoro glacier, above which K2 and Gasherbrum V and VI loom, is more than 13,000 ft high.

[[File:Karakoram1.jpg|300px|thumb|left|Circling Gasherbrum I]]

Take off from Skardu airport in Pakistan (OPSD). Skardu has a reasonably long (11,944 ft) runway at just 7,316 ft elevation, so you can take a jet, but for instance the [[De Havilland Canada DHC-6 Twin Otter|Twin Otter]] is more stylish.

South of Skardu lies Deosai park, a famous high plateau, but we turn initially east. There's a chain of lakes which is the Indus river. After about five miles, the Shigar river merges with the Indus. Turn slightly left and follow the Shigar, then follow it into a long and broad lake-filled valley stretching into north-western direction.

Towards the end of the lake, a small tributary river, the Braldu, turns eastward out of the main valley. Follow the Braldu and start climbing (if you haven't done so yet). About 15 miles after turning into the Braldu river valley, two glacier-filled valleys stretch to the north - admire the view!

[[File:Karakoram2.jpg|300px|thumb|right|Heading back into Skardu, Nanga Parbat on the horizon]]

Passing a few lakes, you reach finally Baltoro glacier continuing the river valley stretching eastward. Ever climbing, follow the glacier till you reach some kind of T-junction. The glacier arm reaching north leads to K2 (which sadly isn't really there in Flightgear), but just ahead of you are the still rather impressive peaks of Gasherbrum V, VI and I - circle the range and make some pictures!

A good way back to Skardu is to go about 10 miles sourth from the Gasherbrum peaks, then head due west. To your west, you can see the long valleys fall away from the high ranges, to your right is the still glacier-covered high Karakoram. On a clear day (really good visibility selected) you can see the distinctive peak of Nanga Parbat appearing straight ahead on the horizon. The valley of Skardu is quite a distinctive feature and finding back VFR should not be a problem.

Published in [[FlightGear_Newsletter_April_2012#Suggested_flights| Newsletter April 2012]] by [[User:Thosten|Thosten]].

== The Paro Challenge ==
The challenge consists in flying as fast and as low as possible from Hashimara (VE44) to Paro (VQPR) while navigating a maze of valleys, steep climbs and sharp turns with only one VOR-DME beacon to guide you (it sits on a mountaintop south of Paro airport). You cannot fly on instruments; this is a 100% visual flight.

Spawn at VE44 (Hashimara Air Force Station). Take off in any direction then turn immediately to heading 013 while staying low. You will see the Himalayas appear on the horizon. Follow the valley as it turns 90° left then make a sharp U-turn (180°) to the right. Fly over the bridge, then U-turn left again (160°). Follow the valley and do another U-turn to the right. Take a deep breath for a couple of nautical miles. Climb to 8500ft while heading 080 to pass over the mountain range. Turn slightly to your right (heading 100) and do a steep dive to 4000ft into the valley. Turn left into the second valley (heading 000), which you will need to follow all the way to Paro airport (VQPR), while climbing slowly to the airport elevation of 7500ft. On the way to Paro, you will pass a monastery on your left. If you don't see this monastery, you've lost yourself in the maze; good luck! After this monastery, follow the valley to the left (heading 270), which will force you to turn right after a few nautical miles. The runway will be hidden behind a hill. You can pass over the hill (steep dive on the other side) or fly to the right of it (steep S-turns), your choice.

=== Suggested aircraft ===
The Paro Challenge is a challenge for most aircraft and most pilots. You will probably not succeed on your first attempt; and successive attempts with various aircraft will renew the challenge.

===== Easy =====
[[Cessna 550 Citation II]], [[Pilatus PC-6 Porter|Pilatus PC-6]], [[De Havilland Canada DHC-6 Twin Otter|De Havilland Canada DHC-6]], [[Zivko Edge 540]].

[[De Havilland Mosquito]], Messerschmitt Bf109G, [[Lockheed P-38 Lightning]].

==== Challenging ====
[[Piper PA34-200T Seneca II|Piper Seneca II]], [[Cessna 337G Skymaster|Cessna 337]], [[Antonov An-2]]: keep an eye on your Exhaust Gas Temperature and Cylinder Head Temperature. If you can't lean your mixture, you lose.

Cessna 172, PA-28 or DR-400 with 180hp engines and a light load; [[Cessna 182S]]; Cap 10b. Slower than the above and will require just as much concentration from you, for a longer time.

[[Mikoyan-Gurevich MiG-15|MiG-15]], [[North American F-86 Sabre|F-86F Sabre]], [[Fairchild Republic A-10 Thunderbolt II|A-10 Warthog]]: make high-speed, steep turns while finding your way. Don't black out!

==== Difficult ====
[[JT-5B|JT-5B autogyro]], Piper Super Cub 150hp: the Paro challenge takes well over an hour of intense concentration in these unstable aircraft.

Cessna 172, PA-28 or DR-400 with low-power (160hp) engines. You will need to circle several times in the valley during the climb. If you can't lean your mixture, you lose.

[[Boeing 707]], [[Boeing 757-200|757]], [[Tupolev Tu-154B|Tupolev 154]], [[Lockheed Constellation]] if lightly loaded; [[Cessna Citation X]]: Finding your way in these faster aircraft is a challenge. The U-turns before the steep climb are almost impossible without taking shortcuts. The final approach without seeing the runway requires you to control your speed, flaps and landing gear well in advance.

==== Impossible (but you might try to beat them anyway) ====
Piper Cub 65hp (cannot climb over 7000ft when fully loaded).

[[Boeing 737-300]] (poor low-speed handling), [[Boeing 787-8 Dreamliner|787]] (bank limiter).

[[Dassault Mirage 2000-5|Mirage 2000]], [[Grumman F-14 Tomcat|F-14B]], [[McDonnell Douglas F-15 Eagle|F-15C]], [[General Dynamics F-16 Fighting Falcon|F-16]]: will either stall or black you out during the sharp turns.

=Africa=
==Ngorngoro==
For this [[VFR]] trip we need a strong machine since we will go up from 4000 to about 10,000 feet and since we are in Africa, Tanzania , what better choice is there as the Cessna 208 Caravan, on wheels. We will take off from HTLM, [http://en.wikipedia.org/wiki/Lake_Manyara Lake Manyara], runway 12 (124.5 deg), that has an elevation of 4150 feet. Hit Shift-B so we don't drop off the runway.
[[File:Map Ngorngoro Crater.jpg|thumb|200px|left|Heightmap with visual reference points]]
We will have to change some settings before we take off. There is no snow where we are so: View=> Rendering Options=> Snow line=> Set to max. (5000M). We need a reasonable clear sky since there are quite a few bumps we could hit: Environment=> Global weather=> METAR source=> Fair weather.

Give full throttle and take off. Bank left and make a full circle so we gain some altitude and make a mental note of the airstrip, since this is the only one nearby. Look at the road West towards the airfield.
You will notice that the airstrip is at the edge of a mountain ridge, the lake to the East is quite a lot lower.

We pass over the airstrip towards lake Manyara and turn left keeping the mountains close to our left side, on an initial course of about 30 deg. We keep the mountains to our left and follow our path, our heading will slowly go from 30 to North and takes about 15 mins. During our path we should slowly gain altitude.
[[File:Ol Doinyo Lengai.jpg|thumb|250px|Mt.Kerimasi (left), Mt.Ol Doinyo Lengai (ahead)]]
On the '''image''' we see two distinct mountains. The nearest is Mt.Kerimasi, a fun place for hang-gliders, and North Mt.Ol Doinyo Lengai, an active volcano. We are heading straight towards [http://en.wikipedia.org/wiki/Ol_Doinyo_Lengai Mt.Ol Doinyo Lengai]. Just before we would collide we take a sharp left turn heading 225. You will see why we need the altitude now.

The mountain ahead, [http://www.ntz.info/gen/n00161.html#id03702 Mt.Embagai], we see does not appear to be anything spectacular. Aim towards it since we have to go over it.
Coming nearer, if you are high enough, 9000 feet, you will see why this mountain is well worth a visit. It is a crater with a lake inside, lake Embagai (Empakaai). Enter the crater and look around, careful not to loose any height since we'll have to get out again, we need about 10 000 feet. Mesmerized we grab our compass and take a course of 225 again. To get out we might skim against a cloud, be careful. If you don't see a way out take a turn again to wait for the clouds to move out of sight.

After you managed to get out of the crater keep on the course of 225 while descending slowly for about 9 mins. There are some bumps to avoid, like Mt.Olmoti we keep to the right and Mt.Losirua on the left.

After a small hill we enter one of the most amazing places in Africa, the [http://en.wikipedia.org/wiki/Ngorongoro_Conservation_Area Ngorngoro Crater], the second biggest crater in the world. A micro climate and amazing wildlife.
Examine the crater and you will notice two lakes, head towards the biggest lake, lake Magadi. When you are above it take a course of 123 to get out of the crater.

After leaving the crater it takes some time before we are near the airstrip again. After about 5 mins we will see a river (left) and a road (right). Follow the road since it will lead us to the airstrip again.

Don't scare the wildebeast!

Notecard:
<tt>
#Fair weather, no snow
#HTLM RW 12 4150 feet
#Course 30 to 0 deg 15 mins, mountains close left
#Head towards /\volcano
#Sharp left turn course 225 deg altitude 9000 feet
#Volcano, lake, 10 000 feet
#Course 225 deg, slow descend 9 min
#Large lake, course 123 deg 5 mins
#River left, road right. Follow road
#Landing 124.5 deg 4150 feet.</tt>

*October 2011 by [[User:PH-JBO|PH-JBO]]. Published in [[FlightGear_Newsletter_December_2011#Suggested_flights | Newsletter December 2011]].
==Kisimayu to Kilimanjaro==
We have to take a big airliner for this trip. The runways are long enough but for this trip we need some altitude and a slow descend.

We park our Big Bird at HCMK, [http://en.wikipedia.org/wiki/Kismayo_Airport Kisimayu], Somalia, near the East coast of Africa. It's unsure what this airfield is used for but it's a long piece of tarmac. I could not find regular flights to and from this airfield, not so strange, there is no lighting, no radio beacons and... no fuel. What you can find is Global Air Rescue that has an air ambulance service based here (with a [http://www.globalairrescue.com/learjet-35.php Learjet 35]).

Our route will be around 425 nm in length. You know your aircraft and know what altitude you will need to fly.

Our destination, HTKJ, [http://en.wikipedia.org/wiki/Kilimanjaro_International_Airport Kilimanjaro], Tanzania, has only one ILS and I have learned, if an airfield has only one ILS there is probably a reason.

Flight Plan (short version):
#HCMK Kisimayu, length 12,177 ft, no navaids near.
#GAR Garissa [[VOR-DME]] freq 115.7 heading 268° dist 169 nm.
#KB Kilimanjaro [[NDB]] freq 393.0 heading 224° dist 258 nm, here is the holding pattern for the Kilimanjaro runway (and there is a [http://en.wikipedia.org/wiki/Mount_Kilimanjaro 19,000 ft] reason for this detour).
#KV Kilimanjaro VOR-DME freq 115.3 heading 70° dist 26 nm.
#HTKJ Kilimanjaro [[ILS]] freq 110.9 runway heading 88° elev 2,900 ft [[AMSL]] length 11,807 ft.

Prepare your flight well to receive amazing views of the landscape during the final steps of the route, if you don't you will discover why some pilots call Kilimanjaro Kill-You-Manjaro.

{{#ev:youtube | KCJi_ZaR8ec}}
Youtube video: Kilimanjaro approach in real, in FG not much different.

*February 2012 by [[User:PH-JBO|PH-JBO]].

=Australia and Oceania=

==Hawai'i==
[[Image:Maui03.jpg|thumb|250px]]
Do you use [[TerraSync]]? If so, try a flight around Hawaii! Take off from PHNL in a light aircraft and head west until you hit Pearl Harbor; a right turn north will take you post the USS Arizona Memorial, and the Punchbowl Crater will be to your right. Or, fly east from PHNL past volcanic craters Diamond Head and Koko Head. If you follow the O'ahu coastline north from Koko Head, you can land at either old World War II airbase Bellows Field (now a wildlife reserve in real life) or at Keahole MCAS.

For a potentially more scenic route, fly east toward Molokai, and stay to the north (left) of the island. The northern part of Molokai features huge sea cliffs and a tiny airstrip on the Kalaupapa peninsula - the peninsula being the only respite from the cliffs. A former leper colony existed near the airstrip!

Also of interest are the volcanoes on Maui and the 'Big Island' of Hawai'i - flying VFR in a small plane from PHTO to PHKO over the plateau between Mauna Kea and Mauna Loa can be a challenge, as you have to take off from sea level, fly through a pass of 6500 feet, and then drop back down to sea level to land! The Hana coast of northern Maui is also a nice flight - a circumnavigation of Haleakala, starting and ending at PHOG, is quite a nice flight.

The islands will be available through the download center with the next major scenery release, but for now, fire up [[TerraSync]] and your favorite VFR aircraft and have a blast.
*Published in [[FlightGear Newsletter September 2010]] by [[User:Statto|Statto]].

== Hawai'i waterfalls tour ==
This flight will let you discover some of the famous Hawai'ian waterfalls, visiting the Islands of Kauai and Oahu.
{{note| Despite the scenery is very nice, the waterfalls are mostly not modeled (as of 5/2024)}}

* [https://skyvector.com/?ll=21.82733715471215,-158.96200561400335&chart=301&zoom=5&fpl=%20PHBK%202211N15938W%202206N15930W%202204N15925W%20LIH%202135N15817W%202138N15802W%202120N15746W%202116N15748W%20PHNL SkyVector route]
* Suggested plane: C172 or C182
* This is VFR only, so pick suitable weather. There are no usable navaids for this trip except the VORTAC LIH 113.500 to cross the sea.
* Trip takes around 90 minutes air time at 110 KTAS.

First part of the trip:
* Start at Parking sands (PHBK), runway 34
* Takeoff, climb to 5000ft and follow the northern coast at about a heading of 030° until you reach Crawlers Ledge (about 8 minutes flight time).
* Turn southeast into the very dominant embayment and watch out for Hanakoa Falls, our first waterfall to visit.
* To your left should be a very dominant valley behind the ridge, featuring a river. Now climb to 6000ft and follow that valley southeastish and visit the famous Weeping wall waterfalls behind the ridge at the end of the valley.
* Bank left slightly (~100° heading), descend to 3000 ft and aim for Wailua waterfalls at the south side of the small hill near the coast (between the two towns).

This concludes the islands waterfalls after about 20 minutes flight.

Now either land at Lihue Airport (PHLI) to your right for a break, or continue the trip and intercept VORTAC LIH 113.500 radial 99/TO. Follow the radial to cross the Kauai Channel until you reach the tip of Oahu Island (the crossing of 63NM takes about 30 minutes at 120 knots. You may also opt to skip and start at PHDH).

* Follow overfly Kawaihapai Airfield (PHDH) and follow the northern coast.
* Shortly you will ovefly a prominent bend from east to nothertheast in the coast, still follow the coast. Note the windfarm appearing to your right ahead.
* Over Waimea (just before the very visible sand beach), turn right and fly to the inland behind (north of) the windfarm. Shortly after passing the wind turbines, look out for Waimea waterfalls.
* Follow the mountains to the southeast of the island and slowly climb to 4000ft (the left side is more rough and scenic).
* North of Diamond Head (a big crater at the south tip of the island) there are several waterfalls (roughly in the middle between Diamond head in the south and Kaneohe in the north), as well as very nice streams coming down the ridge. Also the north side of the ridge is very nice, so consider doing a circle over there.
* Continue south over Diamond head and proceed to land at Honolulu airport (PHNL).

This concludes the trip after about 1:30 hours.

==Brisbane International Airport to Sydney International Airport==
Going from Brisbane International Airport to Sydney International Airport. You should have a heading of about 203. Might take sometime to arrive to this section. Maybe 10-30 mins into the flight. Can't really say but don't give up, you will eventually reach this section of the flight. '''''Your eyes will be rewarded!''''' .

[[Image:Fgfs-screen-020.png|200px]]
[[Image:Fgfs-screen-016.png|200px]]
[[Image:Fgfs-screen-012.png|200px]]
*Published in [[FlightGear Newsletter April 2011]] by [[User:Vin|Vin]]

=Antarctica=

{{Suggested}}

[[Category:Lists]]

Suggested Flights

2024-08-22T21:19:50Z

Circumn: /* Asia */ The Paro Challenge!

[[FlightGear]] has accurate and realistic terrain. Here are some interesting places where you can do virtual sight seeing.

If you are starting with [[FGRun]] - the FlightGear launcher - you can enter the [[airport]] id and select the runway on the appropriate screen in the startup wizard.
If you are starting from the command line you can use the options: <tt>--airport=ABCD</tt> and <tt>--runway=12L</tt>.

*Remember to give a look at the [[Suggested Airports]] page, where you can find a comprehensive list of high quality airports in FlightGear.
*If you enjoy these flights, please consider recording a flight and posting a link to it at the [[Suggested Prerecorded Flights]] page.

'''Remove before flight!''' 

Before you start flying into one of the suggested flights, you should add both the terrain and the Objects to you FlightGear installation; This is well explained on the [[Howto: Install scenery|installing scenery]] page.

p.s. charts are generated using FlightGear data only.

This page includes the flights described on the [http://www.flightgear.org/places.html main website] and the suggested flights from the newsletters. It can serve as an archive for suggested flights from future [[FlightGear Newsletter|newsletters]] or can give a flight if creativity is low that month.

{{TOC limit|3}}

=Cross Continentals or World Tour=

* [[Breitling DC-3 World Tour]][[File:Rect17.png|thumbnail]]
* [[Flying the Hump]]

=North America=
==Round Valley Airport==
[[Image:O09-002.png|thumb|left|right after take off]]
[[Image:O09-003.png|thumb|right|Valley]]
Covalis, CA. The airport is at the West edge of a 7 mile across valley.<BR/>
The predominant wind is a cross wind. Take-offs to the west (if they use the full runway length) often have to fly between 2 small hills and over another valley while gaining altitude. Most pilots take off to the west.<BR/>
It is a paved runway and quite long. It was designated as an emergency recovery field during the Cold War and was used twice that I know of by military aircraft that could not take off again from the field.
<div style="clear:both;"></div>

===Airports and coordinates===
{{Location map | USA
| caption = Latitude: 39.790156 Longitude: -123.266403
| lat_deg = 39.790156
| lon_deg = -123.266403
}}

* [[O09|O09 - Round valley]] - [http://assistenza.larasrl.net/brisa/fgfs/suggested_flights/O09.pdf chart]

required scenery tile: ftp://ftp.sunsite.org.uk/sites/ftp.flightgear.org/flightgear-ftp/Scenery/w120n40.tar.gz
<div style="clear:both;"></div>

===Suggested aircraft===
I have tried this trip using a p38, quite powerful airplane
* [[Lockheed-P38|P38]]
<div style="clear:both;"></div>

===FlightGear launching===
fgfs --airport=O09 --runway=28 --aircraft=p38
<div style="clear:both;"></div>

==Half Moon Bay==
[[Image:KHAF-001.png|thumb|left|right after take off]]
[[Image:KHAF-002.png|thumb|right|Bridge]]
Start at [[KHAF|Half Moon Bay]], Runway 30, with 32km visibility; Takeoff in the C172 and climb to 1000 feet, then continue north over the water, near the shoreline. Look out the right window frequently. Fly up the coast, overfly the Golden Gate Bridge, continue around the top of the peninsula past downtown SF, then fly on to [[KSFO]] for a landing. We now have lots to see.

If you cannot see the runway in the default 172, you must be flying too high or too slowly. You can start by practicing a bit with a good setup:

'''fgfs --offset-distance=1.5 --altitude=500 --vc=70'''

As soon as FlightGear starts, cut the power to 1500 rpm and drop two notches of flap. Maintain 70 kt. Now, pick your landing spot (a bit down the runway) and try to hold it in the same spot on your windshield. If your landing spot starts moving down, you are too high, and should cut another 100 rpm; if it starts moving up, you are too low, and should add another 100 rpm. Adjust the nose to keep your speed at 70 kt all the way down until you're right above the numbers, then cut power to idle, drop the last notch of flaps, flare, and land.
<div style="clear:both;"></div>

===Airports and coordinates===
[[Image:KHAF-003.png|thumb|left|surroundings]]
[[Image:World-KHAF.png|thumb|right|Latitude: 37.513333 Longitude: -122.501111]]
* [[KHAF|KHAF - Half Moon Bay]] - [http://assistenza.larasrl.net/brisa/fgfs/suggested_flights/KHAF.pdf chart]

no required scenery tile.
<div style="clear:both;"></div>

===Suggested aircraft===
[[Image:KSFO-001.png|thumb|left|Before landing]]
Use the default c172 airplane
* [[Cessna C172P]]
<div style="clear:both;"></div>

===FlightGear launching===
fgfs --airport=KHAF --runway=30 --visibility=32000 --aircraft=c172
<div style="clear:both;"></div>
===Author===
April 2006 [[User:Hellosimon|Hellosimon]], format and extended by [[User:Francescobrisa|Francescobrisa]]

==Hell's Canyon==
[[Image:25U-001.png|thumb|left|right after take off]]
[[Image:25U-004.png|thumb|right|Valley]]
Hell's Canyon, Imnaha, OR. This airport is located just west of "Hell's Canyon National Park" which has the Snake River running through it.<br/>
Supposedly it's a 5500 foot drop from the top of the canyon to the river.<BR/>
The airport is located on the brink of this canyon.

See the remarks on the airport page (click on the airport id) ... DOWNDRAFTS, SHEER DROP IN TERRAIN, LIVESTOCK, etc. Don't go here on your first solo x-country. :-)
<div style="clear:both;"></div>

===Airports and coordinates===
[[Image:25U-005.png|thumb|left|Landing]]
[[Image:World-25U.png|thumb|right|Latitude: 45.427861 Longitude: -116.693889]]
* [[25U|25U - Round valley]] - [http://assistenza.larasrl.net/brisa/fgfs/suggested_flights/25U.pdf chart]

required scenery tile: ftp://ftp.sunsite.org.uk/sites/ftp.flightgear.org/flightgear-ftp/Scenery/w120n40.tar.gz
<div style="clear:both;"></div>

===Suggested aircraft===
[[Image:25U-006.png|thumb|left|Landing 2]]
I have tried this trip using a pilatus PC-9M, powerful airplane
* [[PC-9M|PC-9M]]
<div style="clear:both;"></div>

===FlightGear launching===
fgfs --airport=25U --aircraft=PC-9M
<div style="clear:both;"></div>

==Crater Lake National Park Tour==
[[Image:64s-003.png|thumb|left|Approaching the lake]]
[[Image:64s-002.png|thumb|right|Direction 40 degrees]]
Prospect, OR.<br/>

Take off and fly at a heading of about 40 degrees until you cross the first distinct ridge in front of you. (several minutes of flight in the navion ... just climb as fast as you can, it will be a close squeek to get over :-)<br/>

Once you clear the ridge and can see beyond it, turn right and fly a heading of about 70 degrees. You should see two shallow peaks off in the distance. Head right between these -- they are the two sides of the crater. As you get closer the shape of the crater will come into view. There's a lake there in real life, hopefully it will be there in flight gear too before long.
<div style="clear:both;"></div>

===Airports and coordinates===
[[Image:64s-001.png|thumb|left|Leaving the 64S airfield]]
[[Image:World-64S.png|thumb|right|Latitude: 42.743183 Longitude: -122.488092]]
* [[64S|64S - Prospect State]] - [http://assistenza.larasrl.net/brisa/fgfs/suggested_flights/64S.pdf chart]

required scenery tile: ftp://ftp.sunsite.org.uk/sites/ftp.flightgear.org/flightgear-ftp/Scenery/w130n40.tgz
<div style="clear:both;"></div>

===Suggested aircraft===
[[Image:64s-004.png|thumb|left|Lake view 1]]
[[Image:64s-005.png|thumb|right|Lake view 2]]

* [[Ryan_Navion|Navion]]
<div style="clear:both;"></div>

===FlightGear launching===
fgfs --airport=64S --runway=02 --aircraft=navion
<div style="clear:both;"></div>

==Grand Canyon Tour==
[[Image:Grand_Canyon_Tour_4.jpg|700px|frameless|center]]
Being a special place, there are also special flight rules for VFR traffic around the Grand Canyon. There are multiple no-fly-zones set up and VFR traffic is only allowed to fly via the designated corridors. If you want to fly realistically, avoid these zones in FlightGear as well, following for example the [https://skyvector.com/?ll=36.18649251415492,-112.52223157994264&chart=230&zoom=5&fpl=%20KGCN%20VPGCF%20VPGCG%20VPGCD%20VPGCC%20VPGCA%203608N11252W%203609N11309W%201Z1%201G4%203AZ5 route shown here. (skyvector link)]

This flight takes you from KGCN, the Grand Canyon National Park airport, to 3AZ5, a small airfield called Hualapai located south of the Grand Canyon. Departing from KGCN, fly north-west bound to reach the canyon. From there, either follow the route shown on skyvector above, or fly visually through the canyon westbound towards 1Z1, Grand Canyon Bar Ten Airstrip. From there on, continue flying westward to 1G4. Called Grand Canyon West, 1G4 also marks about the western end of the canyon. To get to your destination 3AZ5, continue along the southern rim, flying eastward now. Shortly after leaving the breathtaking valley behind you, you will already reach your destination. Land and let your engine and your mind cool down from the special views :)

===Gallery===
<gallery>
Grand_Canyon_Tour_2.jpg
Grand_Canyon_Tour_3.jpg
Grand_Canyon_Tour_1.jpg
</gallery>

===Airports===
* KGCN - Grand Canyon National Park Airport - [https://www.aopa.org/destinations/airports/KGCN/details aopa.org]
* 1Z1 - Grand Canyon Bar Ten Airstrip - [https://www.airnav.com/airport/1Z1 airnav.com]
* 1G4 - Grand Canyon West - [https://www.airnav.com/airport/1G4 airnav.com]
* 3AZ5 - Hualapai - [https://www.airnav.com/airport/3AZ5 airnav.com]

===Suggested aircraft===
Most VFR aircraft with sufficiently big windows will serve the purpose, for example:
*[[Cessna C172P]]
*[[Optica]]
*[[Ryan_Navion]]
If you are more interested in flying helicopters, the [[Eurocopter EC130 B4]] with the Grand Canyon Helicopters livery might be for you.

===Links===
*[https://www.nps.gov/grca/learn/nature/upload/sfra.pdf Chart of the Grand Canyon special airspace, published by the National Park Service]
*[http://www.swaviator.com/html/issueJJ99/canyon.html An article about flying close to the Grand Canyon]
*[https://www.aopa.org/news-and-media/all-news/2017/april/flight-training-magazine/road-trip-grand-canyon AOPA Flight suggestion]

==Ranger Creek Airport==
[[File:21w-1.jpg|500px|center|Waiting for departure at Ranger Creek]]
Ranger Creek Airport is located in Greenwater, Washington, USA. Being wedged into the bottom of a steep canyon, you'll definitely need to be on your toes to get in and out of there. Switch on Advanced Weather and Live Data to experience what the winds can do to you in real life!
===Airports and coordinates===
* [[21W|21W - Ranger Creek]] - [http://www.airnav.com/airport/21W airnav.com]
===Gallery===
<gallery>
Ranger_Creek1.jpg|Departing between the mountains
Ranger_Creek_2.jpg|Looking back towards the airfield
Ranger_Creek_3.jpg|Downwind for approach back to Ranger Creek
</gallery>
===Suggested aircraft===
For this flight, the Piper PA-18 SuperCub is suggested, this is included in the [[Piper J3 Cub]] package

==Mount Rainier Tour==
[[Image:WA20-002.png|thumb|left|The mountain from far away]]
[[Image:WA20-006.png|thumb|right|external view]]
Eatonville, WA. Start out at Swanson Airport in Eatonville, WA. Take off and fly a heading of about 90 degrees. You will need to fly for 5-10 minutes before the mountain comes into view. Be patient if you don't see it right away, it will dwarf everything in it's vicinity.
<div style="clear:both;"></div>
===Airports and coordinates===
[[Image:World-WA20.png|thumb|right|Latitude: 46.87588502 Longitude: -122.25733500]]

* [[WA20|WA20 - Swanson]] - [http://assistenza.larasrl.net/brisa/fgfs/suggested_flights/WA20.pdf chart]

required scenery tile: ftp://ftp.sunsite.org.uk/sites/ftp.flightgear.org/flightgear-ftp/Scenery/w130n40.tgz
<div style="clear:both;"></div>

===Suggested aircraft===
[[Image:WA20-007.png|thumb|left|external near view]]
[[Image:WA20-009.png|thumb|right|external near view]]
* [[mosquito]]

<div style="clear:both;"></div>

===FlightGear launching===
fgfs --airport=WA20 --aircraft=mosquito
<div style="clear:both;"></div>

==Death Valley Tour==
[[Image:L06-001.png|thumb|left|in the air]]
[[Image:Furnace-creek.jpg|thumb|left|real life view of Furnace Creek Airfield]]
[[Image:L06-002.png|thumb|right|in the air]]
Furnace Creek, CA. This starts you right in the middle of Death Valley which runs north & south. If you head south about 15 miles you'll hit the lowest point in the USA, 282 feet (86 meters) below sea level.
<div style="clear:both;"></div>
===Airports and coordinates===
[[Image:World-L06.png|thumb|right|Latitude: 36.46451100 Longitude: -116.88139422]]
* [[L06|L06 - Furnace Creek]] - [http://assistenza.larasrl.net/brisa/fgfs/suggested_flights/L06.pdf chart]

required scenery tile: ftp://ftp.sunsite.org.uk/sites/ftp.flightgear.org/flightgear-ftp/Scenery/w120n30.tgz
<div style="clear:both;"></div>

===Suggested aircraft===
[[Image:L06-003.png|thumb|left|in the air]]
[[Image:L06-004.png|thumb|right|in the air]]
* [[rallye-MS893]]
<div style="clear:both;"></div>

===FlightGear launching===
fgfs --airport=L06 --aircraft=rallye-MS893
<div style="clear:both;"></div>

==Utah==
!!! Work in progress !!!<BR/>

Escalante Muni Airport, Escalante, UT. This airport is east and a bit north of Bryce Canyon National park. If you head mostly south and a bit east you'll eventually hit the Grand Canyon. It is sandwiched between the Dixie National forest to the north and the Grand Staircase-Escalante National Monument to the south. There should be interesting stuff to see no matter which direction you head.
<div style="clear:both;"></div>
===Airports and coordinates===
[[Image:World-1L7.png|thumb|right|Latitude: 37.75054400 Longitude: -111.57578300]]
* [[1L7|1L7 - Escalante Muni]] - [http://assistenza.larasrl.net/brisa/fgfs/suggested_flights/1L7.pdf chart]

required scenery tile: ftp://ftp.sunsite.org.uk/sites/ftp.flightgear.org/flightgear-ftp/Scenery/w120n30.tgz
<div style="clear:both;"></div>

===Suggested aircraft===

<div style="clear:both;"></div>

===FlightGear launching===
fgfs --airport=1L7 --aircraft=pa18
<div style="clear:both;"></div>

==Lake County Airport (CO)==
[[Image:KLXV-001.png|thumb|left|Adjust mixture !]]
[[Image:KLXV-002.png|thumb|right|The terrain will be covered by snow]]
Lake County Airport, Leadville, CO. This airport is at an elevation of 9927 making it a bit of a challenge to get into and out of with a standard C172.<BR/>
Make sure you lean out your engine before taking off and read up on density altitude before you try this one in real life.
<div style="clear:both;"></div>
===Airports and coordinates===
[[Image:KLXV-003.png|thumb|left|The airport]]
[[Image:World-KLXV.png|thumb|right|Latitude: 39.22812500 Longitude: -106.31835600]]
* [[KLXV|KLXV - Lake Co]] - [http://assistenza.larasrl.net/brisa/fgfs/suggested_flights/KLXV.pdf chart]

required scenery tile: ftp://ftp.sunsite.org.uk/sites/ftp.flightgear.org/flightgear-ftp/Scenery/w110n30.tgz
<div style="clear:both;"></div>

===Suggested aircraft===
[[Image:KLXV-004.png|thumb|left|I like this panorama]]
[[Image:KLXV-005.png|thumb|right|The nearby lake]]
* [[Cessna C172P]]

<div style="clear:both;"></div>

===FlightGear launching===
[[Image:KLXV-006.png|thumb|left|Landing...]]
fgfs --airport=KLXV --aircraft=c172p
<div style="clear:both;"></div>

==Caribbean - Saint Martin and St. Kitts==
[[Image:TNCM-003.png|thumb|left|just after the take off]]
[[Image:TNCM-004.png|thumb|right|some nearby island]]
Pilots of the Caribbeans is an informal FlightGear community of users who fly around the small Caribbean islands, many of which have custom scenery and improved landclass data. (For details see [[Pilots of the Caribbean]])<BR/>

[[TNCM|Princess Juliana International Airport (TNCM)]] at the isle of Saint Martin, is one of the most popular airports in FlightGear. In large part due to the custom objects and land cover. However, St. Marten is only one of several detailed airports in the region - and, while the approach for TNCM is one of the most memorable in the whole world, the land cover for St. Kitts and Nevis makes it a lovely place to fly.

British Airways, US Airways and American Airlines, among others, all fly into St. Kitts' [[TKPK|Robert L. Bradshaw International Airport (TKPK)]] in real life.

Take off from TKPK in a [[Piper_J3_Cub|Piper Cub]] and make a northward, clockwise circle of the island. Start your descent on the east side of the island, and focus on the small hill which separates the north from the south. Start hugging the coast near the beach and look to the west - as soon as the railroad heads to the southwest, you're about ready to turn for final. Make your right hand turn for final and taxi to the terminal.

If you want to fully explore this whole country, take off in a Beaver, which has a little more speed, and fly a figure eight. Take off from TKPK and circle the airport to the north like in the Cub. Then instead of landing, perform a touch-and-go and turn left over the boat terminal and make for the west coast of Nevis. Enjoy the beauty of the south coast of St. Kitts before circling Nevis. Over Nevis, you have several options - cut your flight short and land at [[TKPN]] on the island of Nevis, complete the "figure eight" by heading back to TKPK, or check your fuel and head east across the Caribbean to Antigua (which does not have custom land cover).<BR/>
<BR/>
Check out the [[Pilots of the Caribbean]] page, for further informations.
<div style="clear:both;"></div>
===Airports and coordinates===
[[Image:World-TNCM.png|thumb|right|Latitude: 18.040953 Longitude: -63.108900]]

* [[TNCM|TNCM - Princess Juliana International Airport]] - [http://assistenza.larasrl.net/brisa/fgfs/suggested_flights/TNCM.pdf chart]
* [[TKPK|TKPK - Robert L. Bradshaw International Airport]] - [http://assistenza.larasrl.net/brisa/fgfs/suggested_flights/TKPK.pdf chart]
* [[TKPN|TKPN - Vance Winkworth Amory Intl]] - [http://assistenza.larasrl.net/brisa/fgfs/suggested_flights/TKPN.pdf chart]
others interesting airports in the area:
* [[TFFF|TFFF - Le Lamentin]] - [http://assistenza.larasrl.net/brisa/fgfs/suggested_flights/TFFF.pdf chart]
* [[MDPP|MDPP - Gregorio Luperon Intl]] - [http://assistenza.larasrl.net/brisa/fgfs/suggested_flights/MDPP.pdf chart]
* [[TJSJ|TJSJ - Luis Munoz Marin Intl]] - [http://assistenza.larasrl.net/brisa/fgfs/suggested_flights/TJSJ.pdf chart]
* [[FMEE|FMEE - St Denis Gillot]] - [http://assistenza.larasrl.net/brisa/fgfs/suggested_flights/FMEE.pdf chart]
* [[TFFG|TFFG - Grand Case]] - [http://assistenza.larasrl.net/brisa/fgfs/suggested_flights/TFFG.pdf chart]

required scenery tile:
* ftp://ftp.sunsite.org.uk/sites/ftp.flightgear.org/flightgear-ftp/Scenery/w070n10.tgz
* ftp://ftp.sunsite.org.uk/sites/ftp.flightgear.org/flightgear-ftp/Scenery/w080n10.tgz
* ftp://ftp.sunsite.org.uk/sites/ftp.flightgear.org/flightgear-ftp/Scenery/w080n20.tgz
* ftp://ftp.sunsite.org.uk/sites/ftp.flightgear.org/flightgear-ftp/Scenery/w090n20.tgz
<div style="clear:both;"></div>

===Suggested aircraft===
[[Image:TNCM-005.png|thumb|left|amazing]]
[[Image:TNCM-006.png|thumb|right|landing]]
* [[Piper_J3_Cub|Piper Cub]]
<div style="clear:both;"></div>

===FlightGear launching===
fgfs --airport=TKPK --aircraft=Cub
<div style="clear:both;"></div>
===Author===
[[FlightGear Newsletter January 2011]] by [[User:Statto|Statto]], format and extended by [[User:Francescobrisa|Francescobrisa]].

==Friedman Memorial Airport (Idaho)==
[[Image:KSUN-001.png|thumb|left|take off]]
[[Image:KSUN-002.png|thumb|right|nearby]]
Friedman Memorial Airport, Hailey, Idaho. This airport is nestled in a valley surrounded by significant terrain. It's one that shows up quite often in accident investigations.
<div style="clear:both;"></div>
===Airports and coordinates===
[[Image:World-KSUN.png|thumb|right|Latitude: 43.51223900 Longitude: -114.30376100]]
* [[KSUN|KSUN - Friedman Mem]] - [http://assistenza.larasrl.net/brisa/fgfs/suggested_flights/KSUN.pdf chart]

required scenery tile: ftp://ftp.sunsite.org.uk/sites/ftp.flightgear.org/flightgear-ftp/Scenery/w120n40.tgz
<div style="clear:both;"></div>

===Suggested aircraft===
[[Image:KSUN-003.png|thumb|left|landing]]
[[Image:KSUN-004.png|thumb|right|landing]]
* [[FK9MK2]]
<div style="clear:both;"></div>

===FlightGear launching===
fgfs --airport=KSUN --aircraft=fk9mk2
<div style="clear:both;"></div>

== Wyoming - Grand Teton ==
Jackson Hole (KJAC) airport is located at around 6,400ft right next to the Teton range of mountains. The Tetons rise straight out of the plains, gaining over 5,000ft in 2 miles.

You will need the w120n40 scenery.

Tower frequency at KJAC is 118.07. Due to the high altitude, you will need to lean non-turbocharged piston aircraft before take-off. Don't forget that take-off distances will also be longer.

After take-off head to the North East. Grand Teton is the highest of the three peaks that rise straight from the flat-lands. Follow the line of mountains to the East, passing over Jenny Lake. After a couple of miles you will reach a huge lake. The large bulk of a mountain to the East is Mount Moran.

The Teton Mountain range is surprisingly thin - really just a string of mountains running SW-NE. Flying fast jets down the steep valleys is recommended.
* September 2006 by [[User:Stuart|Stuart]].

== Virginia Eastern Shore, Chesapeake Bay-Bridge Tunnel Sightseeing ==
[[Image:KTGI-001.png|thumb|left|before take off]]
[[Image:KTGI-002.png|thumb|right|right after take off]]

Take a short VFR trip from Tangier Island to view the famous Chesapeake Bay Bridge-Tunnel connecting Cape Charles to Cape Henry. Depart historic Tangier Island (KTGI) situated in the Chesapeake Bay and land at Norfolk International Airport (KORF), Norfolk, Virginia. The scenic character of the flight is enhanced by leaving the island at dusk. The flight is both scenic and challenging. Frequently, when flying with real weather, you will have a steady wind blowing across the bay. Starting out quiet Tangier and arriving at busy, glittering Norfolk International (KORF) gives the flight some contrast.

'''fgfs --airport=KTGI --runway=20 --timeofday=dusk'''

Before leaving Tangier: Set your altimeter to the prevailing barometric temperature. Set your communications radio to the Norfolk Intl. (KORF) ATIS frequency of 127.150 MHz to listen for weather reports in the destination area. Set your navigation radio to 112.20 MHz to pick up the Cape Charles (CCV) VOR. Set your heading bug to the runway heading, 200.

Takeoff straight, flying the runway heading. Climb to 2000ft and maintain.

Shortly, you should see the VOR assigned to NAV1 display receive a steady signal (the OFF flag will disappear). The DME should also settle down and display the distance to the Cape Charles VOR station. The flight to CCV will be about 26 nautical miles. As you fly, it will show your airspeed and time to arrival. It should take about ten minutes.

Turn the OBS knob until the VOR displays the TO flag and 190 degrees, the heading you should now turn to.

Fly south from Tangier, crossing an expanse of water, about ten miles until you see the Virginia Eastern Shore. You'll come upon the grass airstrip of Chance (VA89) a few minutes out from Tangier. Beyond are two flashing tower beacons. You may catch a glimpse of Weirwood/Kellam (W08) on the ocean shore, recognizable by two crossing dirt strips.

If you look carefully, you may see the little white building that is the Cape Charles VOR station. As you fly over VOR the flag will change from TO to FROM and the needle will deflect. Do not try to follow the needle. Wait until you are past the VOR. As you cross the VOR station, you should see a highway slanting across your path toward the south west. Turn to follow this highway. You'll come across a lone tower with beacon along the roadside. You'll see an access road stretching from the tower complex to the main road.

If the sky conditions permit, you may try your hand at wayfinding by following the road. If visiblity is poor, set the VOR to 180 degrees to parallel the road to the end of the peninsula. Or you can continue to fly outbound from the VOR on 190 by maintaining the same heading. The VOR needle should return to center with the FROM flag displaying. This will put you west of the bridge with a good view and the option to turn towards KORF near the initial approach fix. If you follow the highway you will need to overfly the airport, but if you stay on the 190 heading, you will be in a position to make a straight in landing.

As you fly down the peninsula you'll pass Cherrystone, Eagle's Nest, Scott and Bull Farm grass airstrips. Bull Farm is the last strip before the mouth of the Chesapeake. Just past Scott Farm you should see the first glimmer of the northern leg of the bridge. The grass strips can be very difficult to see.

As you reach the end of the peninsula, be careful to avoid the tower on Fisherman's Island at the north end of the north leg of the bridge (Note the bridge is not modeled by FlightGear...but I hope to work up one eventually). Next comes the north middle leg. Turn right a few degrees to follow the south middle leg. Watch as the deck plunges beneath the waves to allow ships to navigate the north and south channels.

As Cape Henry approaches, you'll see the Norfolk International airport to the right and the southern leg of the bridge touching the shore.

If you intend to land at KORF, you will want to start your approach soon. Otherwise, you may continue to follow the bridge to the end. Make the approach to KORF by contacting the tower for vectors. Or use the ILS.

This is a good flight to practice VOR flying on. It is a very straight flight path to the VOR requiring little adjustment and there are no other VORs in the area to confuse you.
*June 2006 by [[User:Sek|Sek]].

===Airports and coordinates===
[[Image:World-KTGI.png|thumb|right|Latitude: 37.8250835 Longitude: -75.9976665]]
* [[KTGI|KTGI - Tangier Island]] - [http://assistenza.larasrl.net/brisa/fgfs/suggested_flights/KTGI.pdf chart]
* [[KORF|KORF - Norfolk International]] - [http://assistenza.larasrl.net/brisa/fgfs/suggested_flights/KORF.pdf chart]

required scenery tile: ftp://ftp.sunsite.org.uk/sites/ftp.flightgear.org/flightgear-ftp/Scenery/w80n30.tgz

===Suggested aircraft===
[[Image:KTGI-003.png|thumb|left|surroundings]]
[[Image:KORF-001.png|thumb|right|landing to KORF]]
I have tried this trip using a Seneca II
* [[Piper PA34-200T Seneca II]]
<div style="clear:both;"></div>

===FlightGear launching===
fgfs --airport=KTGI --runway=20 --timeofday=dusk --aircraft=SenecaII
<div style="clear:both;"></div>

==Prince George to Calgary Springbank==
A beautiful flight is from Prince George (CYXS), to Calgary Springbank (CYBW). Route created by reed, which can be seen at {{forum link|t=9772|text=the forums}}
*Published in [[FlightGear Newsletter November 2010]] By [[User:Cael|Cael]].
==Ketchikan to Juneau==
It's cold where we will go so dress up warm and if we are lucky we might see whales during our flight. Don't fly too high to enjoy the amazing views, and there is a small challenge at the end. The runways we will use are long enough for bigger aircraft (7000+). Total length of the trip will be around 245 NM. So, hop in the cockpit of your favourite airliner.

Alaska, here we come! Enjoy!
#Park your aircraft on PAKT, [http://www.borough.ketchikan.ak.us/airport/airport_history.htm Ketchikan International], runway 11. The wind is coming from '''South''', change the weather if needed (SE is ok too).
#Fly North towards [[NDB]] Fredericks Point on 372.0 for 94 NM.
#Fly towards [[NDB]] Five Fingers on 295.0 for 39 NM.
#Fly towards [[NDB]] Gustavus on 219.0 for 77 NM.
#Fly towards [[NDB]] Coghlan Island on 212.0 for 32 NM.
#Set the [[ILS]] on 109.9 and land your aircraft (after 4 NM) on PAJN, [http://www.juneau.org/airport/ Juneau International], runway 08.
If you feel warm after this landing, you just crossed a NORAD microwave site, so that is why.
*October 2011 by [[User:PH-JBO|PH-JBO]] [[FlightGear Newsletter November 2011]]
==Searching Wizard Island==
*USA, Oregon, Klamath County
With one [[VORTAC]] behind our back we do an [[IFR]]/[[VFR]] search of Wizard Island, a mysterious place, a sacred place for native Americans. You might even find the <tt>Old Man of the Lake</tt>.

Don't pull up the map, that would spoil the surprise but I promise '''unique views'''. We will land on a short lawn runway. Terrain [[altitude]] will range from 4,000 to a max of 8,930 feet and down again. Total length of the trip will be about 50 NM. Select your aircraft with care. It must have one working navigational radio (VOR-DME), a strong engine, a strong undercarriage, must be capable of a good climb and a steep descend. I suggest to use Fair weather (Environment=>Global Weather). If needed remove some clouds (View=>Rendering Options=>Slider 3d Clouds to the left).
[[File:Mount Scott.jpg|thumb|250 px|Mount Scott (8,929 feet) just after depart from 2S7 (Two Sierra Seven). Wizard Island is just to the North-West of it.]]
*Park your aircraft on 2S7 (Two Sierra Seven), Chiloguin-State.
*Set [[NAV1]] on 115.9 (Klamath Falls VORTAC) and on radial 323<sup>o</sup> (Magnetic). We are at an [[elevation]] of 4,217 feet. Set QNH. Set heading bug at 275<sup>o</sup> (Magn).
*Take off an fly the course set with the heading bug.
*Intercept the radial.
*Monitor distance and you will find Wizard Island at 50 NM from Klamath Falls. The island has an elevation of 6,673 feet. I suggest a full 360<sup>o</sup> turn, take pictures.
*Set radial 318<sup>o</sup>, keep the same frequency. Do a new radial intercept.
*Try and find the airstrip (3S6, Three Sierra Six, Toketee-State) at 71 NM from Klamath Falls with an elevation of 3,361 feet, runway heading 275<sup>o</sup> (Magn). There are bumps around you should avoid.
*If you are capable of finding the island, finding the airstrip and landing without a crash, in one go..., you are a wizard.

Click [http://en.wikipedia.org/wiki/Crater_Lake this link] '''after''' you have landed so you know what amazing landscape you have seen.

*December 2011 by [[User:PH-JBO|PH-JBO]]. Published [[FlightGear_Newsletter_March_2012|Newsletter March 2012]].

=South America=
==Southern Tip of Chile==
[[Image:Scgz-001.png|thumb|left|right after take off]]
[[Image:Scgz-004.png|thumb|right|Some part of the scenery]]
Gary Carvell: Here is a suggestion for the FlightGear Places to Fly page. I don't have any particular routes, just fly around and enjoy the gorgeous scenery.<BR/>
These three airports are in the same region of the very southern tip of Argentina. This area is a scenic wonderland - a maze of islands, mountains, and ocean channels. Hours of entertainment.<BR/>
SCGZ - Puerto Williams Guardiamarina Zanartu Airport, Chile Located on the north coast of Isla Navarino facing the Beagle Channel. At 55 deg S. longitude, Puerto Williams is considered the southernmost town in the world.<BR/>
SAWH - Ushuaia Islas Malvinas Airport
SAWO - Ushuaia Est Aeronaval Airport
Ushuaia, on the south coast of Isla Grande de Tierra del Fuego, on the the Beagle Channel.
<div style="clear:both;"></div>
===Airports and coordinates===
[[Image:Sawh-004.png|thumb|left|Approaching Ushumaia Malvinas Argentinas]]
[[Image:World-scgz.png|thumb|right|Latitude: -54.931072 Longitude: -67.626261]]

* [[SCGZ|SCGZ - Guardiamarina Zanartu]] - [http://assistenza.larasrl.net/brisa/fgfs/suggested_flights/SCGZ.pdf chart]
* [[SAWH|SAWH - Ushuaia Malvinas Argentinas]] - [http://assistenza.larasrl.net/brisa/fgfs/suggested_flights/SAWH.pdf chart]
* [[SAWO|SAWO - Ushuaia Est Aeronaval]] - [http://assistenza.larasrl.net/brisa/fgfs/suggested_flights/SAWO.pdf chart]
<div style="clear:both;"></div>

===Suggested aircraft===
[[Image:Scgz-002.png|thumb|left|Just left the scgz airport]]
I personally like to fly this area in the [[Consolidated_Aircraft_PBY_Catalina|Catalina]], it's a great sightseeing plane with the advantage that you can take off and land just about anywhere.
* [[Consolidated_Aircraft_PBY_Catalina|Catalina]]
<div style="clear:both;"></div>

===FlightGear launching===
fgfs --airport=SCGZ --aircraft=Catalina
<div style="clear:both;"></div>

==Copacabana to San Rafael over Lake Titicaca==
Bolivia to Peru. This trip will lead you over one of the highest and deepest lakes in the world towards the highest airfield in the world. It a demonstration of a [[IFR]] flight towards a fix and a demonstration how accurate FlightGear simulates air density and the effects it has on aircraft.
[[File:Slcc-sprf.jpg|thumb|200px|left|Flight and fix SLCC to SPRF]]
Place your aircraft on the airfield [http://en.wikipedia.org/wiki/Copacabana,_Bolivia SLCC, Copacabana], with an [[elevation]] of 12,592 feet. FlightGear will show snow all around you but that is not very realistic so let's clean up. View=> Rendering Options=> Snow line=> Set to max. (5,000M).

We will fly towards and land at SPRF. If you would enter SLCC and SPRF in [[Kelpie]] planner you probably would not be able to find SPRF. To find SPRF I am adding an additional VOR-DME station and for a good fix give you another VOR-DME. Try Kelpie planner to plan this route and compare with this suggestion.

Equipment preparation. Set [[NAV1]] to [http://en.wikipedia.org/wiki/Juliaca Juliaca] VOR-DME on 155.55 with a radial of 311° (magnetic). Set [[NAV2]] to Arequipa VOR-DME on 113.7 with a radial of 212°. During our flight we will fly with [[true altitude]] as set with [[QNH]], keep QNH updated. Arm the autopilot with the [[heading bug]] at 311° and an initial altitude of 13,500 feet.

Take off and if you took the wrong RW pull up hard. Take a small tour over [http://en.wikipedia.org/wiki/Titicaca lake Titicaca], see the floating islands and try to find the lost golden treasure. Intercept the nearest radial on NAV1 towards Juliaca (about 311°).

Just before Juliaca is a hill so while on lake Titicaca increase altitude to 14,200 feet, the [[VFR]] part of this trip is over. After passing Juliaca set the radial of NAV1 to 352° and set the altitude to 17,422 feet. We will fly from NAV1 and slowly increase altitude.

At a distance of about 60 NM set the heading bug on the current course. Monitor the distance to NAV1, the radial of NAV2 and the distance to NAV2. At a distance of 74.5 NM to NAV1, a distance of 140.7 NM and at the '''radial''' intercept of NAV2 should be the runway. So, from 60 NM onwards, look outside the window, then at NAV1 and then NAV2 etc.

If you are at 80NM to NAV1 you have missed the airfield but you still won't hit any hills (unless you bank left). Bank right and set the heading bug to 172°. Fly back towards NAV1 and intercept the radial 352° at about 50NM again to repeat the search.

The runway SPRF, San Rafael, has a elevation of 14,422 feet and a heading of 297°/ 117°. Our initial altitude has been set 3,000NM above the RW elevation. That should give sufficient room for navigation.

After you have seen the airfield set the radial of NAV1 to 297°, the heading of the runway (not the course to the runway) as a visual aid. Land on RW 30 (and not on RW 12 unless you are a show-off). Oh, there is a small hill in front of RW 30, just so you know.

Decreasing speed at this altitude can be a bit tricky. The air is thin and does not give much resistance. Next to that, the difference between [[indicated airspeed]] and [[ground speed]] is very noticeable. The ground speed is much higher as the indicated airspeed.

After a successful landing, try to discover the origin of the Amazon river since we are now at the starting point of that trip.
* October 2011 by [[User:PH-JBO|PH-JBO]], published in [[FlightGear_Newsletter_February_2012#Suggested_flights| Newsletter February 2012]].

==Origin of the Amazon River==
[[Image:SPRF-001.png|thumb|left|high altitude]]
[[Image:SPRF-002.png|thumb|right|high altitude]]
Peru. For this [[IFR]] tour (with [[VFR]] parts) we take off from the highest airfield in the world to discover the origin of the [http://en.wikipedia.org/wiki/Amazon_River Amazon river] in South America. I promise spectacular mountains and valleys. The total length of this trip is about 175 NM.

Place your aircraft on the airfield SPRF, San Rafael. FlightGear will show snow all around you but that is not very realistic so let's clean up. View=> Rendering Options=> Snow line=> Set to max. (5,000M).

Equipment preparation: Set [[NAV1]] to [http://en.wikipedia.org/wiki/Arequipa Arequipa] VOR-DME at 113.7 with a radial of 176° (magnetic). Set [[NAV2]] to [http://en.wikipedia.org/wiki/Cusco Cusco] VOR-DME at 114.9 also with a radial of 176°.
Set [[QNH]] and during flight keep correcting it, it's a bad idea to use [[Pressure altitude]] during this flight. Set the [[heading bug]] to 250°. Arm the [[autopilot]] and set the initial [[altitude]] to 16,000 feet.

The airfield SPRF, San Rafael has an [[elevation]] of 14,422 feet. That altitude will cause problems during take-off. It takes a lot longer for the aircraft to gain sufficient speed for take-off, also the take-off speed that is needed is higher as you would expect. Perhaps an additional notch of flaps is needed.

Take-off, avoid the bumps (there are plenty) and fly a course of 250°. After about 80 NM you will fly over the radial of NAV1. Intercept the radial towards Arequipa. At a distance of 75 NM towards NAV1 you will have to increase altitude to 19,000 feet.

At a distance of 50 NM towards NAV1 and 118 NM from NAV2 you will see and cross over the mountain [http://en.wikipedia.org/wiki/Nevado_Mismi Nevado Mismi] with an altitude of 18,362 ft. The rains and water on the area to the right until Nevado Mismi will leave towards the Atlantic ocean through the Amazon river. Anything to the left and after Nevado Mismi will leave towards the Pacific ocean.

After Nevado Mismi you are tempted to descend. Don't. Just before the airfield is [http://en.wikipedia.org/wiki/Chachani Mt.Chachani] with an altitude of 19,872 feet and to the East is the active volcano [http://en.wikipedia.org/wiki/El_Misti El Misti] with an altitude of 19,101 feet. You can either increase the altitude and fly over the airfield or keep the altitude, even descend and fly between the mountains, your choice depends on the visibility.

Fly using the heading bug and set NAV1 to [[ILS]] 109.7 with a radial of 93.2°. We will land at airfield [http://en.wikipedia.org/wiki/Rodr%C3%ADguez_Ball%C3%B3n_International_Airport SPQU, Rodriguez ballon], that has an elevation of 8,405 feet. There is a reason this airfield has just one ILS. The area South-West of the airfield is below 11,405 feet and is safe to navigate.

Position the aircraft in front of the runway at an altitude of 11,405 feet, catch the [[glidescope]] at a distance of 9.5 NM and land your aircraft. After landing and parking your aircraft crawl into the tower to look around.

Happy flying!

* October 2011 by [[User:PH-JBO|PH-JBO]]. Published [[FlightGear_Newsletter_March_2012|Newsletter May 2012]].

===Airports and coordinates===
[[Image:SPQU-001.png|thumb|left|pre - landing]]
[[Image:World-SPRF.png|thumb|right|Latitude: -14.267 Longitude: -70.467]]
* [[SPRF|SPRF - San Rafael]] - [http://assistenza.larasrl.net/brisa/fgfs/suggested_flights/SPRF.pdf chart]
* [[SPQU|SPQU - Rodriguez Ballon]] - [http://assistenza.larasrl.net/brisa/fgfs/suggested_flights/SPQU.pdf chart]

required scenery tile: ftp://ftp.sunsite.org.uk/sites/ftp.flightgear.org/flightgear-ftp/Scenery/w020s80.tar.gz
<div style="clear:both;"></div>

===Suggested aircraft===
[[Image:SPQU-002.png|thumb|right|landed]]
I recomend a powerful jet angine airplane, but not too heavy !
* [[Cessna 550 Citation II]]

<div style="clear:both;"></div>

===FlightGear launching===
fgfs --airport=SPRF --aircraft=Citation-II
<div style="clear:both;"></div>

=Middle East=
==Israel to Jordan over the Dead Sea==
[[Image:LLBS-001.png|thumb|left|take off]]
[[Image:LLBS-002.png|thumb|right|flat land]]
Dead Sea is the lowest water elevation on the Earth. Take off from the Beer-Sheva Teyman airport and head East-North-East. About half way there, after the southern Hebron mountains ridge, there'll be a sharp drop-off down to the Dead Sea --- the lowest exposed point on the Earth.<br/>
<br/>
It's really fun to descend and explore the beautiful coastline. In the real life, you wouldn't like to fly low over this water there of your own will --- while you don't need a life vest in the Dead Sea, the water is pretty caustic there for one's eyes. Once you're done marvelling the sights, continue on to the Queen Alia airport.
<div style="clear:both;"></div>
===Airports and coordinates===
[[Image:LLBS-006.png|thumb|left|landing in the dead sea, notice the altitude !]]
[[Image:OJAI-007.png|thumb|right|landing at Queen Alia Intl.]]
[[Image:World-LLBS.png|thumb|right|Latitude: 31.29037800 Longitude: 34.71922500]]
* [[LLBS|LLBS - Teyman]] - [http://assistenza.larasrl.net/brisa/fgfs/suggested_flights/LLBS.pdf chart]
* [[OJAI|OJAI - Queen Alia Intl]] - [http://assistenza.larasrl.net/brisa/fgfs/suggested_flights/OJAI.pdf chart]

required scenery tile: ftp://ftp.sunsite.org.uk/sites/ftp.flightgear.org/flightgear-ftp/Scenery/e030n30.tar.gz
<div style="clear:both;"></div>

===Suggested aircraft===
[[Image:LLBS-003.png|thumb|left|approaching the dead sea]]
[[Image:LLBS-004.png|thumb|right|there is also a minor airport]]
* [[Albatross]]

<div style="clear:both;"></div>

===FlightGear launching===
fgfs --airport=LLBS --aircraft=Albatross
<div style="clear:both;"></div>

=Europe=
==Edinburgh to Oban==
See article: [[Edinburgh to Oban]].

==Oban to Prestwick==
The west coast of Scotland offers some stunning scenery and a number of small airfields and airports to land at on both the mainland and the small islands the dot the coast. The distances between the various airfields are quite small, and some of the runways are on the short side, so STOL or GA aircraft are ideal. The tour suggested here follows part of a microlight trip I made this month, photos of which can be found [http://www.nanjika.co.uk/photos/gigha/ here].

Oban airport (EGEO) lies on the west coast of Scotland, and offers fuel (both AVGAS and AVTUR) and a North/South tarmac runway.

From Oban it is just a 10 minute flight west to the grass airfield of Glenforsa (EG45), on the north-east coast of the island of Mull. Due to the hills and water channel, this airfield often gets quite strange wind patterns - the weather can be perfect in Oban, but much gustier and windier at Glenforsa. At times the windsocks at either end of the runway can blow in completely opposite directions!

Some distance north of Oban lie the airfields of the Isle of Skye (EG57) and Plockton (EG81). This is an excellent place from which to explore the mountains of the Isle of Skye, known as the Cuilins.

Heading south from Oban, one can follow the coast to the island of Jura, with it's distinctive hills (The Paps of Jura). From Jura one can head south to the island of Islay with its numarous malt whisky distilleries (many of which are modelled in FG). Islay Airport (EGPI) has extensive runways. From Islay head north east to the tiny island of Gigha. Despite it's small size, it too has an airfield (EG44), though the FG version is tarmac rather than grass.

From Gigha head east over the Mull of Kintyre, to the hilly isle of Arran, then north east to the Isle of Bute. Both islands have very small grass airstrips, which are sadly not present in FG. From Bute you can head south east to Prestwick International (EGPK), famous for being the only place Elvis touched down in the UK, and a fine place to end our tour.
*Published in [[FlightGear Newsletter July 2011]] by [[User:Stuart|Stuart]]

== Edinburgh to Dundee ==
Edinburgh Airport (EGPH) is located to the West of the city of Edinburgh and south of the Forth rail and road bridges. You'll need the w010n50 scenery and the latest set of objects from the scenery DB which include a number of models for the Edinburgh area.

From Edinburgh Airport, head north and circle the bridges, then follow the coast on the south eastwards past Edinburgh (watch out for the Castle!) and to East Lothian and Bass Rock - a volcanic plug in the sea that is host to thousands of sea-birds.

There are a number of sights in East Lothian, include a distillery.

If you wish to continue your tour, head back North, crossing the Firth of Forth to the Kingdom of Fife. Head approximated North West, tracking towards the Perth VOR (110.4). There is an airport here (Perth Scone, EGPT), but instead we will now track out on the 090 radial and pick up the ILS to Dundee Airport (108.10) landing beside the sea.
* September 2006 by [[User:Stuart|Stuart]].

==Austrian alps soaring==
Discover the Austrian alps with a glider. [[Pinzgauer Spaziergang]]

== Sightseeing the Alps in a C172 ==
This tour will guide you to many of the most famous mountains, valleys, glaciers, snowfields, winter and summer vacation areas, etc. in the European Alps. In addition there are several hints to visit nearby areas of interest. On the tour you will visit Switzerland, Italy and France.
See the detailed description in: http://www.emmerich-j.de/FGFS/Alp-flying.pdf (mirrored to https://beni.hallinger.org/fgfs.nobackup/Alp-Tour-Jomo/)
*February 2011 by [[User:Jomo|Jomo &dagger;]].;

* The scenic trip does take about 2 hours.
* Skyvector route: https://skyvector.com/?ll=46.464097146192884,7.159790050777061&chart=301&zoom=6&fpl=%20LSZC%204700N00836E%204647N00840E%204642N00836E%204637N00835E%204634N00823E%204634N00812E%204633N00809E%204634N00805E%204634N00801E%204631N00803E%204624N00746E%204619N00745E%204618N00753E%204614N00752E%204612N00749E%204609N00747E%204603N00746E%204601N00745E%204600N00738E%204555N00724E%204555N00712E%204553N00703E%204547N00652E%204549N00649E%204604N00634E%20LSGG

== Salzburg to Zell am See via Hallstatt ==
[[File:LOWS-LOGO-LOWZ.jpg|thumb|The route for Salzburg to Zell am See via Hallstatt]]
This flight will bring you around a very scenic region of the austrian alps.
* [https://skyvector.com/?ll=47.5666119817603,13.107925427128999&chart=301&zoom=3&fpl=N0100A040%20LOWS%204735N01311E%204736N01339E%204733N01340E%204733N01343E%204735N01343E%204738N01355E%204727N01357E%20LOWZ SkyVector route]
* Suggested plane: C172 or C182
* This is VFR only, so pick suitable weather. There are no usable navaids for this trip.
* Trip takes around 1 hr. air time at 120 KTAS.
* Fly at an altitude of about 4000ft or so (the entire trip can be done at that altitude safely).

* Start ''Salzburg (LOWS)''; follow the Autobahn in the valley to the southeast until you reach the fork at ''Golling''. To the south you see the Mountains of the ''Tennengebirge''.
* Alternatively (and I recommned that), you can also deviate sothwest around ''Mt. Untersberg'' (1972m, hosting germanys longest and deepest cave, the ''Riesending'') to visit lake ''Königsee'' and watch the peaks of the ''Steinernes Meer'' (the dominant and very famous ''Mt. Watzmann'', 2713m!) and north side of the ''Mt. Hochkönig''. You need to climb to at least 6200ft to cross the final ridge at the end of the lake valley. After crossing, descend to 4000ft, follow the valley and fly north at the next valley to rejoin the route.
* Turn east and follow the valley and hills, aim for a prominent V-shaped incision at the end. Fly through there and you suddenly break out at the lake ''Hallstätter See'', a fjord-like lake 125m deep.
* Follow the ''Hallstätter See'' to the south, on its western shore is the famous town of ''Hallstatt''. At the mountain to your right (north of Hallstatt) is a very old settlement dating back to the late bronce age (Hallstattzeit, c. 800–450 BC) and there was a very important Salt mine dating back to that time and important archeological grave findings.
Looking south you can see the ''Dachstein'' (2995 m), a high peak hosting the ''Hirlatzhöhle'', with 120km the twentiest longest and with 1560m sixth deepest cave of planet earth.
* Follow the valley east bend to ''Obertraun'', and then north over the ''Koppenpass'' and the town of ''Bad Aussee''.
* From ''Bad Aussee'', fly straight to the lakes ''Grundlsee'' and ''Toplitzsee'' (you can't see the latter yet).
* Between the two, turn southwards and aim for the reservoir lake ''Salza'' which is in the sharp incision you can see to the south.
* After passing the reservoir, you may try to get down to ''Niederoblarn'' (LOGO) to the southeast, it's a short airfield.
* From there, follow the railway in the valley of Enns westwards, LOWZ is about 20 minutes away. On your right side watch out for the other side of the ''Dachstein'' and the town of ''Schladming'', which lies down in the valley next the rocky hills with the river flowing trough. Look for the railway and the river Enns.
* Behind ''Schladming'' (south of Mt. ''Dachstein'', approximately halfway of the distance LOGO/LOWZ) the valley will widen a bit again, featuring a rocky mountain in the middle of the valley. Continue to follow the railway and river bending nortwest arond the small mountain.
* Near the bigger town of ''Radstadt'' the valley will open significantly. Follow west, heading for the next town ''Altenmark'' at the end of the opening.
* The railway will bend north at ''Altenmark'' and soon join the Autobahn A10/E55. This is the point we need to go southwest and follow the next valley.
* The valley leads us westward to the Town of ''St. Johann/Pongau''. probably around the middle of the valley you can spot the prominent ''Mt. Hochkönig'' (2941m) northwest of ''St. Johann'' and the ''Tennengebirge'' to its right.
* Once reaching ''St. Johann'', continue to follow the next big valley west-southwest.
* After about 16 miles you will reach ''Zell am See'' (LOWZ) where we will land after around one hour flight time in total. Beware this is a short field.

== Zell am See to Innsbruck via Mt. Venediger ==
[[File:LOWZ-LOWI.jpg|thumb|The route for Zell am See to Innsbruck]]
This flight will bring you to two of the core peaks of the Alpenhauptkamm.
* [https://skyvector.com/?ll=47.201656734623775,12.160079968084839&chart=301&zoom=3&fpl=N0100A120%20LOWZ%20LOWZ%204708N01241E%204708N01221E%204706N01214E%204710N01152E%204724N01150E%20LOWI SkyVector route]
* Suggested plane: C172 or C182
* This is VFR only, so pick suitable weather. There are no usable navaids for this trip.
* Trip takes around 45 minutes air time at 110 KTAS.
* Climb to at an altitude of about 10000ft or so after starting from [[:File:Lowz-parking.jpg|Zell am See]].

* After starting fly into the valley southwest over the town of ''Kaprun''. Maybe you need to circle a bit to gain altitude, near the mountains we need at least about 10000ft!
* Follow the valley until you overfly two lakes (''Stausee Wasserfallboden'' and ''Moorboden''). To your left you can see ''Mt. Großes Wiesbachhorn'' (3564m).
* The end of the valley goes over into a flank of the ''Großglockner'' which is near to the south. Follow the west bend of the valley end and fly over the lakes ''Tauernmoossee'' and ''Weißsee''. After you climb out of the valley, you already should see the peak of ''Mt. Venediger'' on the front left. Aim to the saddle right of its peak.
* You then fly that direction over several valleys that go from south to north, until you hit the very big valley that bend from south to west. The ridgeline right of that valley is the border between the Austrian states Tirol and Salzburg. Follow the valley up to the ''Venediger'', passing the ''Mt. Sandebentörl'' (2751m), still aiming for the saddle.
* Shortly after you reach the end of the valley and need to overfly the saddle with the glacier ''Venedigerkees'' behind it. The ridgeline is again the border between Tirol and Salzburg. Directly south of the ''Venedigerkees'' is the pyramid of ''Mt. Venediger''.
* Follow ''Venedigers'' ridge to the southwest, skip the first valley and overfly the next ridge.
* From here you can deviate into the valley north and visit the ''Krimmler Wasserfälle'', and from there west trough the main valley.
* If you instead follow the planned route westwards, aim to the peak of ''Mt. Zillerplattenspitze'' (3148m) with the small lake ''Eissee'' to its south flank which you should already see. This is a little hard to get right, but don't fly directly into the big valley but aim right to the second row mountain peaks at about 280 heading.
* Overfly the ridge with ''Eissee'' and follow the valley from there nothwest with the reservoir ''Zillergründl'' and ''Mt. Reichenspitze'' (3303m) to its right; until you reach the town ''Mayrhofen'' where the current valley meets the ''Zillertal'' valley. You also should start to descend now to about 3500ft with a rate of roughly -1000fpm.
* From ''Mayrhofen'' follow the ''Zillertal'' valley north and when reaching the ''Inntal'' valley near the town ''Jenbach'', Innsbruck Airport is a few minutes to the west. If you like, you can divert north at ''Jenbach'' to visit ''Achensee'', and even continue further north to land at Munich via lake ''Tegernsee'' or via the Isartal over ''Bad Tölz''.

== Crossing the alps ==
[[File:ED02-LIPB.jpg|thumb|The route for Fuessen to Bolzano]]
This trip brings us from germany via austria to italy, crossing the alps, visiting the famous castle Neuschwanstein and Mt. Zugspitze, germanys highest peak.
* [https://skyvector.com/?ll=47.068251080980836,10.959411633048108&chart=301&zoom=5&fpl=N01204735N01041E%204734N01045E%204729N01042E%204726N01046E%204724N01054E%204712N01054E%204704N01058E%204656N01103E%204655N01106E%204653N01109E%204650N01110E%204648N01113E%204638N01110E%20LIPB SkyVector route]
* Suggested plane: C172 or C182
* This is VFR only, so pick suitable weather and time (I suggest to start with the first light/sunrise).
* There are no helpful navaids for this trip, but Bolzano NDB: 362 BZO may serve as a final guidance.
* Trip takes around 45 minutes air time at 120 KTAS.

* Start at ED02 Fuessen, climb to about 3000 and head southeast to visit castle Neuschwanstein, south of the Forgensee.
* After looking at the castle (challenge: fly close around behind it), we start climbing to 3500 and aim southwestish and cross over from germany to austria.
* Fly into the big valley directing south. East of Reutte start climbing 500fpm to 6000 and follow the railway in the valley to the southeast.
* Once the valley opens significantly, you can see the famous mountain Zugspitze (germanys highest peak, 2962 m) to the front.
* Head southwards around the Mt. Gartnerwand over town Ehrwald and fly between the two small peaks over the Marienbergjoch mountain pass, 1789m/5870ft (between Mt. Wanning and Mt. Marienberg; challenge: who can make it with the least altitude?).

* After overflying the second mountain, to the south comes a new valley called Ötzal where you fly into.
* Follow that valley all the way to the south and slowly climb to at least 8600 now (300fpm or so). Note overflying Längenfelden, where the dominant valley joins from the east with the river Fischbach, halfaway the leg; this looks similar to the end, but isn't.
* Follow the valley until it starts to branch in all different directions at the end (over the town of Sölden and Zwieselstein).
* We follow the Southeast main branch and then turn quickly to a smaller valley branching off directly eastwards (look for the mountain pass road).
* That brings us to the mountain pass of the Timmelsjoch and is the place where we cross over to Italy.

* After passing, we can descend to 2500 or so, following the terrain. Follow the valley and its river "Passer" southeast, and follow its bend to the south.
* Follow the valley and make a nice turn around Mt. Kolbenspitze's east ridge, over San Leonardo, still following the Passer river now southwards.
* Where the valley hits the next big valley "Etschtal", is a bigger famous city called Merano. From there we follow the River Etsch and the Autobahn (highway) to the south and are soon approaching the somewhat hidden airport of Bolzano (LIPB) after an estimated time of somewhat under one hour at 120 knots.

From here you can also continue more to the south to Trento (LIDT, total FT ~1:00) or Verona (LIPX, total FT ~1:20) - just follow the river Etsch to the south! Venezia is also not far away, just ~30 minutes/62nm to the east of Verona.

==Grenoble Le-Versoud==

[[Image:LFLG.jpg|800px]]

France : '''LFLG''' ( Grenoble Le-Versoud ) airport : border of Alps
*P.A.F. home base [http://equipe-flightgear.forumactif.com/ link]
*Scenery : http://clemaez.fr/flightgear/flightgearfrance_05062011.tar.gz
*Texture : http://clemaez.fr/flightgear/pattentextures_maj24082011.tar.gz

* Take-off from Grenoble le Versoud (LFLG). Head south following the general direction of the Alps. Bearing left (East) will take you into high alpine territory, while towards the West lie the plains of the Rhône valley. Once you reach the Mediterranean coast, follow it to land in Marseilles (LFML), Nice (LFMN), or another smaller airport serving the French Riviera.
*Published in [[Custom France Scenery]].

==Gulf of Finland sightseeing tour==
Take a VFR sightseeing tour over the Gulf of Finland from Helsinki to Tallinn! Estonia's landmarks are all recent additions, while Helsinki was one of the first cities to have original models in the scenery model database.

Take off from the smaller EFHF airfield in Helsinki, or try your luck fighting the virtual traffic at Vantaa, and head toward the port of Helsinki. Look for the Hartwall Arena, the Pasila tower, the railway station and the Olympic Stadium along the way. Make your way out over the Gulf flying just west of south - a heading of 190 should set you up nicely for a sightseeing tour of Tallinn. Try to come in from the west and do a sweeping left turn over the capital of Estonia, looking out for the Swissotel, Olympic Hotel, the Television tower, and other important landmarks in the capital city of Estonia. Make sure you look out for St. Olaf's Church, the tallest building in the capital city. Make your way over the Ulemiste Jarv (lake) to land on runway 09 at Tallinn's main airport.

If you desire, you can do a touch-and-go at Tallinn and set your course southeastward, landing at Tartu Airport, which is also modelled in FlightGear.

The distance between Helsinki and Tallinn is about 50 miles or 80 kilometres, while Tartu is twice the distance from Tallinn at 100 miles/160 kilometres. Fly a heading of 135 to get to Tartu from Tallinn.
*Published in [[FlightGear Newsletter October 2010]] by [[User:Statto|Statto]].

==Azores==
[[Image:LPLA-001.png|thumb|left|take off]]
[[Image:LPLA-002.png|thumb|right|approaching island]]
The [http://en.wikipedia.org/wiki/Azores Azores], set in the middle of the Atlantic ocean, has had many names. Fortunate Isles, the Blue Islands, the Islands of Tin and Silver, the Islands of the Seven Cities. We can add, the Islands of Amazing Sights and Flights.

Our flight is to celebrate the amazing views FlightGear can give us.

Start your plane at [[Lajes Field]] (LPLA). This once was an emergency landing site for the [[Space Shuttle]] so you will have plenty of room to take off.
We will have to fly an odd pattern. The reason for that: if you don't fly too high (stick around 3000 while you can) you will have some amazing views.

Next, fly towards and over LPPD. Look out the window and enjoy the view. Then head out towards LPHR. If you feel LPHR coming near, look out the window good, you might have to pull your plane up.

Happy flying!
*Published in [[FlightGear Newsletter August 2011]] by [[User:PH-JBO|PH-JBO]]

===Airports and coordinates===
[[Image:LPPD-001.png|thumb|left|over the island]]
[[Image:LPPD-002.png|thumb|right|landing]]

* [[LPLA|LPLA - Lajes Field]] - [http://assistenza.larasrl.net/brisa/fgfs/suggested_flights/LPLA.pdf chart]
* [[LPPD|LPPD - Ponta del gada]] - [http://assistenza.larasrl.net/brisa/fgfs/suggested_flights/LPPD.pdf chart]

required scenery tile: http://mirrors.ibiblio.org/pub/mirrors/flightgear/ftp/Scenery-v2.4.0/w020n30.tgz
<div style="clear:both;"></div>

===Suggested aircraft===
* [[Cessna 550 Citation II]]

===FlightGear launching===
fgfs --airport=LPLA --aircraft=Citation-II
<div style="clear:both;"></div>

== Canary Islands Trip ==

An archipelago in the middle of the Atlantic sea, stunning beauty where you won't expect it. Seven islands, seven continents, thats what the canarian people say. And it's true, you will face seven totally different islands and nine different airports.
Take off from the largest one, GCLP, at the main island Gran Canaria. Leave the beautiful island heading to the west, and land at GCTS, the southern airport at Tenerife. Enjoy the view on Spains highest mountain, the glaciered Teide, when flying to La Gomera (GCGM), one of the greenest islands there. Master the short runway, and enjoy the view, before taking the challenge and approach El Hierro (GCHI). A short runway, with cliffs and rocks on both ends will cause you to sweat. From this island, which was claimed to be the western end of the world in medieval times, you'll turn to the beautiful and wild island of La Palma (GCLA). The next approach will be historical, because you are approaching the notorious Tenerife North (GCXO). Yes, I am serious, you will face that airport, where the worst civil plane crash ever took place. But you needn't worry, if you got that far, you will do this approach as easy as any other. The longest flight on your trip will take you to the eastern island, Lanzarote (GCRR). Take a look at the volcanic-red mountains, the vineyards, and the beaches. You want more beaches?? Depart to the south-west, fly over the small island of Los Lobos, and land in the holiday-paradise Fuerteventura. Enjoy dunes, bays, and very nice long beaches, before you finally touch down in Fuerteventura (GCFV). You want to stay? Okay, let's taxi to a parking position, and cut off the engines. If you still want more, fly back to Gran Canaria's GCLP, where we started our trip.

Custom scenery: [[Canary Islands Custom Scenery]] / direct source: https://github.com/D-ECHO/Canarys

=== Suggested Aircraft ===

* small civil aircraft, such as the Cessna Skylane, Skyhawk, or Citation
* small airliners, like the Q400, the ATR72, the CRJ200, or similar

Route by Flycanarias

<gallery>

</gallery>

==Gibraltar==
[[Image:LEMG-010.png|thumb|left|take off]]
[[Image:LEMG-011.png|thumb|right|just after take off]]
Traffic lights turn red, gates are closed. The only busy main road to the peninsula is closed and all the cars and trucks are waiting patiently. Waiting for a train to pass? No. Waiting for a plane to pass since the main road crosses a busy runway.

On both sides water and being crossed by a busy main road can only be one runway: [http://en.wikipedia.org/wiki/Gibraltar_Airport Gibraltar airport]!

One would expect an ILS installed on such a tricky runway but no, you will have to guess where it is and how far away it is. Not even an ADF points to it.

Take off from LEMG (Malaga). Go South-West and find the runway of LXGB somewhere to the right of the rock. Happy guessing!
*Published in [[FlightGear Newsletter September 2011]] by [[User:PH-JBO|PH-JBO]]
<div style="clear:both;"></div>

===Airports and coordinates===
[[Image:LEMG-013.png|thumb|left|search for this]]
[[Image:LEMG-015.png|thumb|right|landing]]

* [[LEMG|LEMG - Malaga]] - [http://assistenza.larasrl.net/brisa/fgfs/suggested_flights/LEMG.pdf chart]
* [[LXGB|LXGB - Gibraltar]] - [http://assistenza.larasrl.net/brisa/fgfs/suggested_flights/LXGB.pdf chart]

required scenery tile: http://mirrors.ibiblio.org/pub/mirrors/flightgear/ftp/Scenery-v2.4.0/w010n30.tgz
<div style="clear:both;"></div>

===Suggested aircraft===
* [[Piper Aerostar]]

===FlightGear launching===
fgfs --airport=LEMG --aircraft=aerostar700 --adf1=300 --nav1=300:117.80
<div style="clear:both;"></div>

=Asia=
==Khorog, Tajikistan==
[[File:Fw190HinduKush.jpeg|left|thumb|Approaching a bank of snow-covered mountains in the south of the Hindu Kush]]
Surrounded by spectacular mountains and nestled in the end of a valley, Khorog Airfield (UT1C) makes an interesting place to land. It can only be approached by flying down the curved valley that snakes in from the North. Flying from here to OPCH (Chitral, Pakistan) at around 500ft AGL all the way is a wonderful way to explore the Hindu Kush mountains.

If you bring a piston engined aircraft, be prepared to adjust the mixture as you climb - at the highest point in the flight, you will be at around 22000ft. Also, don't forget to carry plenty of fuel - there are very few airfields in the Hindu Kush that exist in FlightGear. This is a scenery bug that will hopefully be fixed in the future.

*October 2011 by [[User:Armchair Ace| Armchair Ace]], published in [[FlightGear_Newsletter_January_2012#Suggested_flights| Newsletter January 2012]].
<br>
<br>
<br>
== Central Karakoram range ==
Let's explore one of the highest regions of the planet - the central Karakoram with the densest concentration of mountains of 8000 m and above. We're going to need a good climbing performance for the trip - even the frozen plateau of Baltoro glacier, above which K2 and Gasherbrum V and VI loom, is more than 13,000 ft high.

[[File:Karakoram1.jpg|300px|thumb|left|Circling Gasherbrum I]]

Take off from Skardu airport in Pakistan (OPSD). Skardu has a reasonably long (11,944 ft) runway at just 7,316 ft elevation, so you can take a jet, but for instance the [[De Havilland Canada DHC-6 Twin Otter|Twin Otter]] is more stylish.

South of Skardu lies Deosai park, a famous high plateau, but we turn initially east. There's a chain of lakes which is the Indus river. After about five miles, the Shigar river merges with the Indus. Turn slightly left and follow the Shigar, then follow it into a long and broad lake-filled valley stretching into north-western direction.

Towards the end of the lake, a small tributary river, the Braldu, turns eastward out of the main valley. Follow the Braldu and start climbing (if you haven't done so yet). About 15 miles after turning into the Braldu river valley, two glacier-filled valleys stretch to the north - admire the view!

[[File:Karakoram2.jpg|300px|thumb|right|Heading back into Skardu, Nanga Parbat on the horizon]]

Passing a few lakes, you reach finally Baltoro glacier continuing the river valley stretching eastward. Ever climbing, follow the glacier till you reach some kind of T-junction. The glacier arm reaching north leads to K2 (which sadly isn't really there in Flightgear), but just ahead of you are the still rather impressive peaks of Gasherbrum V, VI and I - circle the range and make some pictures!

A good way back to Skardu is to go about 10 miles sourth from the Gasherbrum peaks, then head due west. To your west, you can see the long valleys fall away from the high ranges, to your right is the still glacier-covered high Karakoram. On a clear day (really good visibility selected) you can see the distinctive peak of Nanga Parbat appearing straight ahead on the horizon. The valley of Skardu is quite a distinctive feature and finding back VFR should not be a problem.

Published in [[FlightGear_Newsletter_April_2012#Suggested_flights| Newsletter April 2012]] by [[User:Thosten|Thosten]].

== The Paro Challenge ==
The challenge consists in flying as fast and as low as possible from Hashimara (VE44) to Paro (VQPR) while navigating a maze of valleys, steep climbs and sharp turns with only one VOR-DME beacon to guide you (it sits on a mountaintop south of Paro airport). You cannot fly on instruments; this is a 100% visual flight.

Spawn at VE44 (Hashimara Air Force Station). Take off in any direction then turn immediately to heading 013 while staying low. You will see the Himalayas appear on the horizon. Follow the valley as it turns 90° left then make a sharp U-turn (180°) to the right. Fly over the bridge, then U-turn left again (160°). Follow the valley and do another U-turn to the right. Take a deep breath for a couple of nautical miles. Climb to 8500ft while heading 080 to pass over the mountain range. Turn slightly to your right (heading 100) and do a steep dive to 4000ft into the valley. Turn left into the second valley (heading 000), which you will need to follow all the way to Paro airport (VQPR), while climbing slowly to the airport elevation of 7500ft. On the way to Paro, you will pass a monastery on your left. If you don't see this monastery, you've lost yourself in the maze; good luck! After this monastery, follow the valley to the left (heading 270), which will force you to turn right after a few nautical miles. The runway will be hidden behind a hill. You can pass over the hill (steep dive on the other side) or fly to the right of it (steep S-turns), your choice.

=== Suggested aircraft ===
The Paro Challenge is a challenge for most aircraft and most pilots. You will probably not succeed on your first attempt; and successive attempts with various aircraft will renew the challenge.

===== Easy =====
[[Cessna 550 Citation II]], [[Pilatus PC-6 Porter|Pilatus PC-6]], [[De Havilland Canada DHC-6 Twin Otter|De Havilland Canada DHC-6]], [[Zivko Edge 540]].

[[De Havilland Mosquito]], Messerschmitt Bf109G, [[Lockheed P-38 Lightning]].

==== Challenging ====
[[Piper PA34-200T Seneca II|Piper Seneca II]], [[Cessna 337G Skymaster|Cessna 337]], [[Antonov An-2]]: keep an eye on your Exhaust Gas Temperature and Cylinder Head Temperature. If you can't lean your mixture, you lose.

Cessna 172, PA-28 or DR-400 with 180hp engines and a light load; [[Cessna 182S]]; Cap 10b. Slower than the above and will require just as much concentration from you, for a longer time.

[[Mikoyan-Gurevich MiG-15|MiG-15]], [[North American F-86 Sabre|F-86F Sabre]], [[Fairchild Republic A-10 Thunderbolt II|A-10 Warthog]]: make high-speed, steep turns while finding your way. Don't black out!

==== Difficult ====
[[JT-5B|JT-5B autogyro]], Piper Super Cub 150hp: the Paro challenge takes well over an hour of intense concentration in these unstable aircraft.

Cessna 172, PA-28 or DR-400 with low-power (160hp) engines. You will need to circle several times in the valley during the climb. If you can't lean your mixture, you lose.

[[Boeing 707]], [[Boeing 757-200|757]], [[Tupolev Tu-154B|Tupolev 154]], [[Lockheed Constellation]] if lightly loaded; [[Cessna Citation X|Cessna 650 Citation X]]: Finding your way in these faster aircraft is a challenge. The U-turns before the steep climb are almost impossible without taking shortcuts. The final approach without seeing the runway requires you to control your speed, flaps and landing gear well in advance.

==== Impossible (but you might try to beat them anyway) ====
Piper Cub 65hp (cannot climb over 7000ft when fully loaded).

[[Boeing 737-300]] (poor low-speed handling), [[Boeing 787-8 Dreamliner|787]] (bank limiter).

[[Dassault Mirage 2000-5|Mirage 2000]], [[Grumman F-14 Tomcat|F-14B]], [[McDonnell Douglas F-15 Eagle|F-15C]], [[General Dynamics F-16 Fighting Falcon|F-16]]: will either stall or black you out during the sharp turns.

=Africa=
==Ngorngoro==
For this [[VFR]] trip we need a strong machine since we will go up from 4000 to about 10,000 feet and since we are in Africa, Tanzania , what better choice is there as the Cessna 208 Caravan, on wheels. We will take off from HTLM, [http://en.wikipedia.org/wiki/Lake_Manyara Lake Manyara], runway 12 (124.5 deg), that has an elevation of 4150 feet. Hit Shift-B so we don't drop off the runway.
[[File:Map Ngorngoro Crater.jpg|thumb|200px|left|Heightmap with visual reference points]]
We will have to change some settings before we take off. There is no snow where we are so: View=> Rendering Options=> Snow line=> Set to max. (5000M). We need a reasonable clear sky since there are quite a few bumps we could hit: Environment=> Global weather=> METAR source=> Fair weather.

Give full throttle and take off. Bank left and make a full circle so we gain some altitude and make a mental note of the airstrip, since this is the only one nearby. Look at the road West towards the airfield.
You will notice that the airstrip is at the edge of a mountain ridge, the lake to the East is quite a lot lower.

We pass over the airstrip towards lake Manyara and turn left keeping the mountains close to our left side, on an initial course of about 30 deg. We keep the mountains to our left and follow our path, our heading will slowly go from 30 to North and takes about 15 mins. During our path we should slowly gain altitude.
[[File:Ol Doinyo Lengai.jpg|thumb|250px|Mt.Kerimasi (left), Mt.Ol Doinyo Lengai (ahead)]]
On the '''image''' we see two distinct mountains. The nearest is Mt.Kerimasi, a fun place for hang-gliders, and North Mt.Ol Doinyo Lengai, an active volcano. We are heading straight towards [http://en.wikipedia.org/wiki/Ol_Doinyo_Lengai Mt.Ol Doinyo Lengai]. Just before we would collide we take a sharp left turn heading 225. You will see why we need the altitude now.

The mountain ahead, [http://www.ntz.info/gen/n00161.html#id03702 Mt.Embagai], we see does not appear to be anything spectacular. Aim towards it since we have to go over it.
Coming nearer, if you are high enough, 9000 feet, you will see why this mountain is well worth a visit. It is a crater with a lake inside, lake Embagai (Empakaai). Enter the crater and look around, careful not to loose any height since we'll have to get out again, we need about 10 000 feet. Mesmerized we grab our compass and take a course of 225 again. To get out we might skim against a cloud, be careful. If you don't see a way out take a turn again to wait for the clouds to move out of sight.

After you managed to get out of the crater keep on the course of 225 while descending slowly for about 9 mins. There are some bumps to avoid, like Mt.Olmoti we keep to the right and Mt.Losirua on the left.

After a small hill we enter one of the most amazing places in Africa, the [http://en.wikipedia.org/wiki/Ngorongoro_Conservation_Area Ngorngoro Crater], the second biggest crater in the world. A micro climate and amazing wildlife.
Examine the crater and you will notice two lakes, head towards the biggest lake, lake Magadi. When you are above it take a course of 123 to get out of the crater.

After leaving the crater it takes some time before we are near the airstrip again. After about 5 mins we will see a river (left) and a road (right). Follow the road since it will lead us to the airstrip again.

Don't scare the wildebeast!

Notecard:
<tt>
#Fair weather, no snow
#HTLM RW 12 4150 feet
#Course 30 to 0 deg 15 mins, mountains close left
#Head towards /\volcano
#Sharp left turn course 225 deg altitude 9000 feet
#Volcano, lake, 10 000 feet
#Course 225 deg, slow descend 9 min
#Large lake, course 123 deg 5 mins
#River left, road right. Follow road
#Landing 124.5 deg 4150 feet.</tt>

*October 2011 by [[User:PH-JBO|PH-JBO]]. Published in [[FlightGear_Newsletter_December_2011#Suggested_flights | Newsletter December 2011]].
==Kisimayu to Kilimanjaro==
We have to take a big airliner for this trip. The runways are long enough but for this trip we need some altitude and a slow descend.

We park our Big Bird at HCMK, [http://en.wikipedia.org/wiki/Kismayo_Airport Kisimayu], Somalia, near the East coast of Africa. It's unsure what this airfield is used for but it's a long piece of tarmac. I could not find regular flights to and from this airfield, not so strange, there is no lighting, no radio beacons and... no fuel. What you can find is Global Air Rescue that has an air ambulance service based here (with a [http://www.globalairrescue.com/learjet-35.php Learjet 35]).

Our route will be around 425 nm in length. You know your aircraft and know what altitude you will need to fly.

Our destination, HTKJ, [http://en.wikipedia.org/wiki/Kilimanjaro_International_Airport Kilimanjaro], Tanzania, has only one ILS and I have learned, if an airfield has only one ILS there is probably a reason.

Flight Plan (short version):
#HCMK Kisimayu, length 12,177 ft, no navaids near.
#GAR Garissa [[VOR-DME]] freq 115.7 heading 268° dist 169 nm.
#KB Kilimanjaro [[NDB]] freq 393.0 heading 224° dist 258 nm, here is the holding pattern for the Kilimanjaro runway (and there is a [http://en.wikipedia.org/wiki/Mount_Kilimanjaro 19,000 ft] reason for this detour).
#KV Kilimanjaro VOR-DME freq 115.3 heading 70° dist 26 nm.
#HTKJ Kilimanjaro [[ILS]] freq 110.9 runway heading 88° elev 2,900 ft [[AMSL]] length 11,807 ft.

Prepare your flight well to receive amazing views of the landscape during the final steps of the route, if you don't you will discover why some pilots call Kilimanjaro Kill-You-Manjaro.

{{#ev:youtube | KCJi_ZaR8ec}}
Youtube video: Kilimanjaro approach in real, in FG not much different.

*February 2012 by [[User:PH-JBO|PH-JBO]].

=Australia and Oceania=

==Hawai'i==
[[Image:Maui03.jpg|thumb|250px]]
Do you use [[TerraSync]]? If so, try a flight around Hawaii! Take off from PHNL in a light aircraft and head west until you hit Pearl Harbor; a right turn north will take you post the USS Arizona Memorial, and the Punchbowl Crater will be to your right. Or, fly east from PHNL past volcanic craters Diamond Head and Koko Head. If you follow the O'ahu coastline north from Koko Head, you can land at either old World War II airbase Bellows Field (now a wildlife reserve in real life) or at Keahole MCAS.

For a potentially more scenic route, fly east toward Molokai, and stay to the north (left) of the island. The northern part of Molokai features huge sea cliffs and a tiny airstrip on the Kalaupapa peninsula - the peninsula being the only respite from the cliffs. A former leper colony existed near the airstrip!

Also of interest are the volcanoes on Maui and the 'Big Island' of Hawai'i - flying VFR in a small plane from PHTO to PHKO over the plateau between Mauna Kea and Mauna Loa can be a challenge, as you have to take off from sea level, fly through a pass of 6500 feet, and then drop back down to sea level to land! The Hana coast of northern Maui is also a nice flight - a circumnavigation of Haleakala, starting and ending at PHOG, is quite a nice flight.

The islands will be available through the download center with the next major scenery release, but for now, fire up [[TerraSync]] and your favorite VFR aircraft and have a blast.
*Published in [[FlightGear Newsletter September 2010]] by [[User:Statto|Statto]].

== Hawai'i waterfalls tour ==
This flight will let you discover some of the famous Hawai'ian waterfalls, visiting the Islands of Kauai and Oahu.
{{note| Despite the scenery is very nice, the waterfalls are mostly not modeled (as of 5/2024)}}

* [https://skyvector.com/?ll=21.82733715471215,-158.96200561400335&chart=301&zoom=5&fpl=%20PHBK%202211N15938W%202206N15930W%202204N15925W%20LIH%202135N15817W%202138N15802W%202120N15746W%202116N15748W%20PHNL SkyVector route]
* Suggested plane: C172 or C182
* This is VFR only, so pick suitable weather. There are no usable navaids for this trip except the VORTAC LIH 113.500 to cross the sea.
* Trip takes around 90 minutes air time at 110 KTAS.

First part of the trip:
* Start at Parking sands (PHBK), runway 34
* Takeoff, climb to 5000ft and follow the northern coast at about a heading of 030° until you reach Crawlers Ledge (about 8 minutes flight time).
* Turn southeast into the very dominant embayment and watch out for Hanakoa Falls, our first waterfall to visit.
* To your left should be a very dominant valley behind the ridge, featuring a river. Now climb to 6000ft and follow that valley southeastish and visit the famous Weeping wall waterfalls behind the ridge at the end of the valley.
* Bank left slightly (~100° heading), descend to 3000 ft and aim for Wailua waterfalls at the south side of the small hill near the coast (between the two towns).

This concludes the islands waterfalls after about 20 minutes flight.

Now either land at Lihue Airport (PHLI) to your right for a break, or continue the trip and intercept VORTAC LIH 113.500 radial 99/TO. Follow the radial to cross the Kauai Channel until you reach the tip of Oahu Island (the crossing of 63NM takes about 30 minutes at 120 knots. You may also opt to skip and start at PHDH).

* Follow overfly Kawaihapai Airfield (PHDH) and follow the northern coast.
* Shortly you will ovefly a prominent bend from east to nothertheast in the coast, still follow the coast. Note the windfarm appearing to your right ahead.
* Over Waimea (just before the very visible sand beach), turn right and fly to the inland behind (north of) the windfarm. Shortly after passing the wind turbines, look out for Waimea waterfalls.
* Follow the mountains to the southeast of the island and slowly climb to 4000ft (the left side is more rough and scenic).
* North of Diamond Head (a big crater at the south tip of the island) there are several waterfalls (roughly in the middle between Diamond head in the south and Kaneohe in the north), as well as very nice streams coming down the ridge. Also the north side of the ridge is very nice, so consider doing a circle over there.
* Continue south over Diamond head and proceed to land at Honolulu airport (PHNL).

This concludes the trip after about 1:30 hours.

==Brisbane International Airport to Sydney International Airport==
Going from Brisbane International Airport to Sydney International Airport. You should have a heading of about 203. Might take sometime to arrive to this section. Maybe 10-30 mins into the flight. Can't really say but don't give up, you will eventually reach this section of the flight. '''''Your eyes will be rewarded!''''' .

[[Image:Fgfs-screen-020.png|200px]]
[[Image:Fgfs-screen-016.png|200px]]
[[Image:Fgfs-screen-012.png|200px]]
*Published in [[FlightGear Newsletter April 2011]] by [[User:Vin|Vin]]

=Antarctica=

{{Suggested}}

[[Category:Lists]]

Talk:Main Page

2024-08-22T20:04:05Z

Circumn: Suggest the suggested flights :)

{{Archives|[[/Archive/2006-2011|2006-2011]]}}

:''Please sign your comments with using tildes (<nowiki>~~~~</nowiki>) or the signature button (second from right above the text edit box). Add new sections to the bottom or by using the "+" tab. You are also encouraged to add a summary of your comment to the edit summary (below the text edit box).''

= 2012 =
== Issues and regressions ==

== Planned changes ==
== Extension requests ==
how can I add the slovenian flag to the others on the top right corner ?
[[User:Laserman|Laserman]] ([[User talk:Laserman|talk]]) 04:51, 27 December 2015 (EST)

: {{done}}
: [[:File:Sl.gif]] was uploaded and added to [[:Category:Flag icons]] and the {{tl|Main page/Languages}} template where the flag icons are added to the main page.
: —[[User:Johan G|Johan G]] ([[User_talk:Johan_G|Talk]] | [[Special:Contributions/Johan_G|contribs]]) 10:07, 27 December 2015 (EST)

Thank you! [[User:Laserman|Laserman]] ([[User talk:Laserman|talk]]) 12:40, 27 December 2015 (EST)

== Deleting versus archiving ==

I have archived an earlier version of this page [http://wiki.flightgear.org/index.php?title=Talk:Main_Page/Archive/2006-2011&oldid=40427 here].

I believe that for the sake transparency and keeping a accessible record of the progressing history of the wiki and what is done to it, and I am not talking about the page history, it would be better if comments instead of being deleted get marked off as completed, obsoleted or what seems appropriate. When the page once in a while gets uncomfortably long it should be archived.

I noted when I went through the entire history of the now archived page that a lot of the comments was unsigned and many of the longer ones later on was cut into pieces by headings, later on to be partially deleted. That makes it very difficult and time consuming to follow what is done and what people laid forth what ideas etc. I am a bit frustrated, although not angry, about that. Luckily there was only a few hundred edits, making it possible to attribute the surviving parts of the comments to an individual author and edit.

As for now I have not used any "fancy" templates when archiving the page, but if needed that can be added later.
[[User:Johan G|Johan G]] 11:21, 9 February 2012 (EST)

: I am sorry, you are probably right: it's the better solution. It just didn't occur to me that people might still be interested in stuff that's no longer an issue, i.e. because it was solved. Also, some of the comments were from people who haven't done any wiki editing in years. My next step would have been to go trough the list of "open" issues and suggestions and migrate them over to 2012. What do you think?--[[User:Hooray|Hooray]] 11:42, 9 February 2012 (EST)

::There is no need to be sorry. :-) My frustrations are more related to the entangled edit history than specifically what you deleted, even though it add to it. As for the open issues I agree, it is probably a good idea to copy them over here. [[User:Johan G|Johan G]] 12:22, 9 February 2012 (EST)

= 2024 =

2024-08-22 I suggest a direct link to the [[Suggested_Flights|Suggested Flights]] page, in the side bar under "Using/New to Flightgear".

Cessna 550 Citation II

2018-06-01T16:35:00Z

Circumn: Manual Landing Procedure: new.

{{:{{PAGENAME}}/info}}
The '''Cessna 550 Citation II''' debuted in [[FlightGear]] 0.9.8 in January 2005. It has four "special views": copilot, center-console, passenger 1 and passenger 2.

== Overview ==
The Cessna 550/551 Citation II is a light corporate jet built between 1978 and 2006. The FlightGear model is a luxury corporate jet for two pilots and seven passengers. However you should not view the original Citation II as a real jet; with a cruising speed of only 330 KTAS, it was really intended as a competitor for high-end twin turboprops.

The Cessna 550 requires two pilots; the 551 is the same aircraft certified for single-pilot use.

Later variants of this aircraft include the [[Cessna_Citation_Bravo|Cessna Citation Bravo]], which has newer avionics (available separately in FlightGear), the Cessna Citation S/II with improved wings (not currently available in FlightGear), and the Sierra Super II, available together with this aircraft in FlightGear.

The Sierra Super II is an aftermarket modification of the Cessna 550/551 which replaces the engines with Williams International FJ44-3 turbofans introduced in 2004. They
provide more thrust and less fuel consumption. Climb performance in particular is dramatically improved.

The new engines lack thrust reversers; they are not needed because their idle thrust is only 40 lbf, as opposed to 400 lbf on the old engines.

[[File:CitationII Cockpit Dusk 2015-03-29.jpg|thumb|Cockpit Cessna 550 Citation II at dusk]]
Features available in FlightGear include:

* Choice of two variants: the basic Citation II or the re-engined Sierra Super II
* Several liveries
* Several checklists and tutorials
* Autostart
* Weight and speed limitations
* Tuned autopilot with built-in climb schedule
* Working speedbrakes (engage with {{key press|k}}, retract with {{key press|j}} - alternatively {{key press|Ctrl|b}} toggles the s/b's)
* Working thrust reversers (engage with {{key press|Del}}) on the Citation II only
* Support for the [[Walk_view|Walk View]]

At low altitude, this aeroplane is light and slow enough for sightseeing in the canyons. At high altitude, it is fast enough for medium-haul, multiple-hour flights and GPS navigation. You can fly VFR or IFR, with or without GPS.

== Download ==

=== For FlightGear 3.4 and earlier ===

[https://sourceforge.net/p/flightgear/fgaddon/460/tarball?path=/trunk/Aircraft/Citation Citation rev 460]

=== For FlightGear 3.5 and higher ===

* Since FlightGear 2016.3 you can use the built-in Aircraft Center to download the Citation II from FGAddon.

* Subversion:
{{#tag:syntaxhighlight |
$ {{fgaddon co|Citation|post=Citation}}
$ svn up
| lang="bash"
}}

== Startup ==
Use the aircraft checklist for startup instructions; alternatively, use the menu for autostart.

== Performance ==
{| class="wikitable"
|-
! !! Citation II !! Sierra Super II
|-
! Never exceed speed
| 263 KIAS || 263 KIAS
|-
! Typical cruise speed at FL410
| 330 KTAS || 380 KTAS
|-
! Range at MTOW and full fuel, FL410, full throttle
| 1900 nmi || 2500 nmi
|-
! Endurance (hours) at full throttle
| 5:45 || 6:33
|-
! Climb rate at sea level
| 3000 fpm || 6000 fpm
|-
! Climb to FL410
| 45 min (stepped) || 22 min (direct)
|-
! Thrust reversers
| yes || no
|}

== Manual landing procedure ==

As with most aeroplanes, you maintain a constant pitch and speed using the yoke and control descent rate (vertical speed) using throttle. The Citation II has an Angle of Attack indicator, left of the airspeed indicator, to help with this. This instrument uses an arbitrary unit going from 0.0 to 1.0 (these are not degrees; 1.0 corresponds to 14 degrees). The needle should be in the green zone for climb and cruise and in the white zone for landing. The red zone indicates a stall.

* Reduce speed to 170 knots indicated.
* Deploy flaps 3 steps (i.e. approach configuration).
* When the runway is in sight, increase throttle to n2=58% then deploy flaps 5 more steps (full flaps).
* Watch the angle of attack indicator.
* Push or pull the yoke to keep the angle of attack in the white zone. Do not let the needle into the red zone, or you will stall.
* At this point your throttle should be approximately n2=58%, AoA=0.6, airspeed=120 knots, descent rate=-500 feet/min.
* Extend gear.
* Look at the [[Precision_Approach_Path_Indicator|Precision Approach Path Indicator]] lights next to the runway.
* Reduce throttle a litte bit to descend faster; increase throttle to descend slower. Avoid rapid or large changes to throttle.
* The ideal vertical speed on touchdown is -500 feet per minute.
* When the rear wheels touch the ground, cut throttle and deploy speedbrakes (press {{key press|k}}).
* Wait for the nose wheel to touch the ground by itself.
* On the Citation II, deploy thrust reversers (press {{key press|Del}}) then open full throttle. The Sierra Super II lacks thrust reversers.
* Apply brakes as necessary.

== Autopilot ==
The autopilot will disengage 500 feet above ground level or below the decision height selected on the radio altimeter, whichever is highest. This implies that you must climb at least to 500 ft above ground before you engage the autopilot. In addition, you should never engage autopilot while manoeuvering; always stabilize the aeroplane before you engage autopilot.

When the FD OFF button is illuminated, the autopilot is OFF. Clicking this button will engage the autopilot in wing leveler (horizontal) and pitch hold (vertical) modes. You can also engage autopilot, with the same effects, with the AP ENGAGE button between the seats. The following lateral, vertical and speed modes are available:

=== Lateral modes ===
; Wing Leveler: All lights are off
; HDG: Follow the magnetic heading bug selected on the pilot's HSI.
; NAV: Follow the radial selected on either NAV1 or NAV2. Switch between NAV1 and NAV2 using the NAV/HSI button.
; GPS: Follow the course selected by GPS. To engage, click on the NAV button a second time.
; APR: Click this button to engage both NAV1 and glideslope for an ILS approach. Note that, since the autopilot will disengage at least 500 ft above ground, this aeroplane is certified only for CAT I ILS approaches; it has no autoland capability.

=== Vertical modes ===
; Pitch hold: All lights are off. Adjust pitch (in increments of 1 degree) with the PITCH wheel between the seats.
; ALT: Climb or descend to, then maintain the altitude selected with the ALT knob left of the ADF radio. You can adjust the selected altitude with this knob or with the PITCH wheel between the seats.
; V/S: Hold current vertical speed. Adjust the selected vertical speed with the PITCH wheel between the seats.

You should engage ALT mode in more or less level flight with an angle of attack no greater than 0.2 and airspeed at least 220 KIAS. The autopilot includes a climb schedule and will climb at a speed appropriate for your engines; it will automatically decrease the rate of climb as you gain altitude.

On the base Citation II, you need a stepped climb and 45 minutes to reach FL410. The first step should be at FL330 or thereabouts.

On the re-engined Super II, you can climb all the way to FL430 in one step, even at MTOW, provided you respect the prerequisites listed above before engaging ALT mode.

=== Speed modes ===
; Autothrottle: Engage and disengage with Ctrl+S to hold current indicated airspeed. Note that the real Citation II does not have this, so you may consider using autothrottle cheating.

== Radio navigation ==
Tune the two NAV and COM radios and the sole ADF radio on the cockpit.

=== Horizontal Situation Indicators ===
On startup, the captain's [[HSI|horizontal situation indicator]] uses NAV1 and the copilot's HSI uses NAV2. The NAV/HSI button under each HSI switches between NAV1 and NAV2; you can switch the HSIs independently. If the autopilot is engaged in NAV mode, then the autopilot will also switch between NAV1 and NAV2, always following the radio selected on the captain's HSI. The best usage of this feature is as follows:

# Tune the NAV1 radio to a VOR beacon.
# Select the NAV1 radial on the captain's HSI.
# Fly the selected radial.
# Tune the NAV2 radio to another VOR beacon.
# Select the NAV2 radial on the copilot's HSI.
# When you intercept the radial selected on NAV2, click on the NAV/HSI button on the captain's side. The autopilot will now follow the NAV2 radial.
# Switch the copilot's HSI to NAV1.
# Tune NAV1 to a third VOR beacon.
# Select the NAV1 radial on the copilot's HSI.
# Repeat as necessary.

The two HSIs feature an integrated Radio Magnetic Indicator: the thin red arrow points to the selected VOR beacon (either NAV1 or NAV2). They also have a built-in Distance Measuring Equipment showing the distance between you and the selected beacon, in nautical miles.

=== Radio Magnetic Indicators ===
The cockpit has additional Radio Magnetic Indicators on both the pilot and copilot side. This indicator has two arrows and two buttons:

* The ''left'' button switches the single-stemmed arrow to point either to the NAV1 VOR beacon or to the NDB.
* The ''right'' button switches the double-stemmed arrow to point either to the NAV2 VOR beacon or to the NDB.

Combined with the HSI you can have arrows pointing simultaneously to all three beacons. By default:

* The ''single-stemmed'' arrow points to the NDB selected on the ADF radio
* The ''double-stemmed'' arrow points to the VOR beacon selected on the NAV2 radio
* The ''thin red needle'' of the HSI points to the VOR beacon selected on the NAV1 radio

=== Glideslope NAV1 indicator ===
To the left of the pilot's HSI is an additional NAV1 indicator with two needles; this merely repeats localizer and glideslope information from the HSI and from the attitude indicator.
Thus you have triple redundancy :) This instrument is hardwired to NAV1, so you can fly an ILS approach by hand while simultaneously pointing your HSI at the NAV2 beacon.

=== Distance Measuring Equipment ===
The DME shows the distance in nautical miles to the selected beacon. You can use it either to repeat the information on the HSI or to show the distance to the other beacon.
This instrument also shows your speed towards or from the beacon (''not'' your groundspeed: Only the component of your groundspeed that is on the line between you and the beacon), or
the time to go to the beacon in minutes at your current speed.

=== Control Display Unit ===
The CDU on the central console allows you to create a simple route from one airport to another.

To create a route:

# Click on the DEP ARR button.
# Type the ICAO code of your departure airport.
# Click on the ORIGIN (top left) button.
# Type the ICAO code of your destination airport.
# Click on the DEST (top right) button.
# Optionally type the departure runway number then click the RWY button.
# Click ACTIVATE.

This activates the Route Manager, which you can of course still control with the generic Route Manager dialog.

== Development ==
=== Recently updated ===
==== will be released with 2017.2 ====
* Tutorials have been added.
* A new menu item is in place. The '''Citation II config''' dialog is available under menu -> Citation II -> Citation II config. It contains options for saving through sessions, some display options and several shortcuts for easy access to tutorials, help and more.
* New support for [[State_Overlay_System|state overlays]]. Activate state overlay by adding <code>--state=$state</code> to your command-line.
$state can be:
* '''parking''' ( cold and dark, all systems off) (same as without <code>--state=$state</code> )
* '''taxi''' ( engines and all systems running - ready to taxi )
* '''take-off''' ( flaps and AP set - just throttle up and go )
* '''cruise''' ( flying at FL360 on AP )
* '''approach''' ( !experimental! use with:
''--glideslope=degrees'' ( usually 3 ) '''or'''
''--altitude=ft-above-msl'' ( alt above sea level ) '''or'''
''--offset-distance=nm'' ( 10 seems like a good start )
Never use all 3 options at once! Only 2 of them. Triangle calculation - remember?
''--in-air'' ( well, just do it... )
if you want, you can add options like this:
''--nav1=rad:freq'' ( Going into [https://skyvector.com/airport/LPAZ/Santa-Maria-Airport LPAZ] 18 enter --nav1=179:110.300 meaning NAV1 is set to 110.300 MHz with a radial of 179°, which is the G/S of LPAZ-18 )
)

==== Systems ====
* Several checklists have been added.
* A realistic startup procedure.
* A major overhaul of the Autopilot-systems.
* The FDM got upgraded and several bugs got fixed in the process.
* All knobs can now be turned with the mouse-wheel.
* Some circuit breakers have been made functional, mainly on pilots side cb-panel.

==== Instruments ====
* Added a new Lighting Panel to the pilots panel. All knobs and switches, which actually have a function are animated.
* Instrument Panel got new textures. Looks a bit more used now.
* RMI now is switchable on Nav1/ADF and Nav2/ADF.
* HSI can be switched between Nav1/Nav2/GPS with the AP control panel's NAV-button.
* A CDU was added on the center pedestal.

==== Model ====
* All lights are now Rembrandt-capable.
* ALS flame / heat blur effect was added.
* ALS glass shader was added.
* The missing door-ladder was added and animated.
* Baggage compartments were added and doors animated.
* The speedbrakes got a major overhaul and are now much closer to the real thing, also the lower speedbrakes are added and animated.
* Small details like pitot tubes and antennas were added.
* Several small additions to the cockpit and cabin, including an accurate circuit breaker panel, with some functionality for now.
* Wing-flex has been added

=== Todo ===
* Create different liveries for Citation II and Sierra Super II.
* CDU needs more functions and bug fixes.
* Add some baggage.
* Add new GPS unit.
See [http://sourceforge.net/p/flightgear/fgaddon/HEAD/tree/trunk/Aircraft/Citation/ToDo.txt ToDo.txt @ sourceforge]

== External links ==
* {{wikipedia|Cessna Citation II}} Wikipedia article
* [http://www.sijet.com/page727822 Corporate site for the Sierra Super II aftermarket modification]

{{Cessna}}

Airliner development status

2017-08-24T23:56:27Z

Circumn: Add Tupolev, the Tu-134 and the mighty Tu-154b

The Airliner Development Statuses were previously managed by Skyop in the forum but due to no response there, I created this page. Here, you don't have to go asking someone to change an airliner's status, you can do this yourself.

== Airbus Industries ==
=== Airbus A300 ===
* Airbus A300-B2 - {{alds|stalled}}
* Airbus A300-B4 - {{alds|stalled}}
* [[Airbus A300-600]] - {{alds|active}}
* [[Airbus A300-600ST]] - {{alds|abandoned}}

=== Airbus A310 ===
* Airbus A310-200 - {{alds|not started}}
* [[Airbus A310-300]] - {{alds|active}}

=== Airbus A320 ===
* [[A320-family]]
** Airbus A318-100 - {{alds|abandoned}}
** Airbus A318-200 - {{alds|abandoned}}
** Airbus A319-100 - {{alds|abandoned}}
** Airbus A319-200 - {{alds|abandoned}}
** Airbus A320-100 - {{alds|abandoned}}
** Airbus A320-200 - {{alds|abandoned}}
** Airbus A321-100 - {{alds|abandoned}}
** Airbus A321-200 - {{alds|abandoned}}

* [[A320Family|A320Family by it0uchpods]]
** Airbus A319-100 - {{alds|stable}}, {{alds|active}} by {{usr|it0uchpods|it0uchpods}} Design Group
** Airbus A319neo - {{alds|not started}}
** Airbus A320-100 - {{alds|stable}}, {{alds|active}} by {{usr|it0uchpods|it0uchpods}} Design Group
** Airbus A320-200 - {{alds|stable}}, {{alds|active}} by {{usr|it0uchpods|it0uchpods}} Design Group
** Airbus A320neo - {{alds|stable}}, {{alds|active}} by {{usr|it0uchpods|it0uchpods}} Design Group
** Airbus A321-100 - {{alds|not started}}
** Airbus A321-200 - {{alds|stable}}, {{alds|active}} by {{usr|it0uchpods|it0uchpods}} Design Group
** Airbus A321neo - {{alds|stable}}, {{alds|active}} by {{usr|it0uchpods|it0uchpods}} Design Group

* [[Airbus A320neo|A320neo]]
** Airbus A319neo - {{alds|abandoned}}
** Airbus A320neo - {{alds|abandoned}}
** Airbus A321neo - {{alds|abandoned}}

=== Airbus A330 ===
* [[Airbus A330-200]] - {{alds|stable}}, continued by Artix and the Project 300 Dev Team
* Airbus A330-200F - {{alds|not started}}
* [[Airbus A330-300]] - {{alds|stable}}

=== Airbus A340 ===
* Airbus A340-200 - {{alds|stable}}, {{alds|abandoned}}
* Airbus A340-300 - {{alds|stable}}, {{alds|abandoned}}
* Airbus A340-500 - {{alds|not started}}
* Airbus A340-600 - {{alds|stable}}, {{alds|abandoned}}

=== Airbus A350 ===
* Airbus A350-800 -{{alds|not started}}
* Airbus A350-900 - {{alds|stalled}}
* Airbus A350-1000 -{{alds|not started}}

=== Airbus A380 ===
* [[Airbus A380|Airbus A380-800]] - {{alds|stable}}
* Airbus A380-900 - {{alds|not started}}

== Avions Transportation Regional ==
=== ATR-42 ===
* ATR-42-200 - {{alds|not started}}
* ATR-42-300 - {{alds|not started}}
* ATR-42-500 - {{alds|stalled}}
* ATR-42-600 - {{alds|stalled}}

=== ATR-72 ===
* [[ATR 72-500|ATR-72-500]] - {{alds|stalled}}
* ATR-72-600 - {{alds|stalled}}

== Boeing Commercial Airplanes ==
=== Boeing 707 ===
* [[Boeing_707-420|Boeing 707]]-320C, -420, 707-TT, EC-137D - {{alds|stable}} (official FGAddon version, using JSBSim)
* [[Boeing_707-320|Boeing 707-320C, 3J9C]] - {{alds|stable}} (using YAsim)
* Boeing 720 - {{alds|not started}}
* Boeing KC-137R {{alds|stable}}, {{alds|active}} by {{usr|it0uchpods}} and {{usr|J Maverick 16}}. {{github url|user=JMaverick16|repo=KC-137R}}

=== Boeing 717 ===
* [[Boeing_717/it0uchpods|Boeing 717-200]] - {{alds|stable}}, {{alds|abandoned}}

=== Boeing 727 ===
* Boeing 727-100 - {{alds|not started}}
* [[727-200|Boeing 727-200]] - {{alds|stable}}, {{alds|active}} by {{usr|it0uchpods|it0uchpods}}

=== Boeing 737 ===
* Boeing 737-100 - {{alds|abandoned}}
* Boeing 737-200 - {{alds|abandoned}}
* [[Boeing 737-300]] - {{alds|active}} by {{usr|Michael Soitanen}} {{fgaddon aircraft url|737-300}}
* [[Boeing 737-400]] - {{alds|stalled}}
* [[Boeing 737-500]] - {{alds|stalled}}
* Boeing 737NG models - {{alds|active}} by {{usr|Michael Soitanen}}
* Boeing 737-8 - {{alds|stable}}, {{alds|active}}
* [[Boeing 737-7 MAX]] - {{alds|not started}}
* [[Boeing 737-8 MAX]] - {{alds|not started}}
* [[Boeing 737-9 MAX]] - {{alds|not started}}
* Boeing 737-700, E-7A AEW&C, P-8A, NG JSTARS, C-40A/B - {{alds|not started}} by {{usr|J Maverick 16}}

=== Boeing 747 ===
* [[Boeing 747-100]] - {{alds|abandoned}}
* [[Boeing 747-200]] - {{alds|abandoned}}
* Boeing 747-300 - {{alds|not started}}
* [[Boeing 747-400]] - {{alds|stable}}
* [[Boeing 747-8i]] - {{alds|active}}
* Boeing 747-8F - {{alds|active}}
* Boeing 747SP - {{alds|stalled}}

=== Boeing 757 ===
* [[Boeing 757-200]], -300, C-32A, C-32B - {{alds|stable}}
* Boeing C-32J - {{alds|stable}}, {{alds|active}} by {{usr|J Maverick 16}} and {{usr|it0uchpods}}

=== Boeing 767 ===
* Boeing 767-200 - {{alds|not started}}
* [[Boeing 767-300]] - {{alds|active}}
* [[Boeing 767-300F]] - {{alds|active}}
* Boeing 767-400 - {{alds|not started}}
* Boeing KC-46, E-767, KC-767 - {{alds|not started}} by {{usr|J Maverick 16}}

=== Boeing 777 ===
* [[Boeing 777-200]] - {{alds|stable}}
* [[Boeing 777-300]] - {{alds|stable}}
* Boeing 777-8X - {{alds|not started}}
* Boeing 777-9X - {{alds|not started}}

=== Boeing 787 ===
* [[Boeing 787-8]] - {{alds|stable}}
* Boeing 787-9 - {{alds|stable}}, {{alds|active}}

== Bombardier Aerospace ==
=== Dash 7 ===
* Dash 7-100 - {{alds|abandoned}}

=== Dash 8 ===
* Dash 8-300 - {{alds|abandoned}}
* Dash 8-Q400 - {{alds|active}}

=== Canadair Regional Jets ===
* [[CRJ-200|CRJ200]] - {{alds|active}}
* CRJ700 - {{alds|stable}}
* [[CRJ-900|CRJ900]] - {{alds|stable}}
* CRJ1000 - {{alds|stable}}

=== CSeries ===
* CS100 - {{alds|stalled}}
* CS300 - {{alds|stalled}}

== Dornier Luftfahrt GmbH (Fairchild-Dornier) ==
=== Dornier 328-100 ===
* Dornier 328-100 - {{alds|active}} by {{usr|HHS}}
=== Dornier 328-110 ===
* Dornier 328-110 - {{alds|active}} by {{usr|HHS}}
=== Dornier 328-120 ===
* Dornier 328-120 - {{alds|active}} by {{usr|HHS}}
=== Dornier 328-130 ===
* Dornier 328-130 - {{alds|active}} by {{usr|HHS}}
=== Dornier 328-300 ===
* Dornier 328-300 - {{alds|active}} by {{usr|HHS}}

== Douglas Aircraft Company ==
=== DC-1 ===
* DC-1 - {{alds|not started}}

=== DC-2 ===
* DC-2 - {{alds|abandoned}}

=== DC-3 ===
* DC-3 - {{alds|stable}}

=== DC-4 ===
* DC-4 - {{alds|not started}}

=== DC-5 ===
* DC-5 - {{alds|not started}}

=== DC-6 ===
* DC-6 - {{alds|stable}}

=== DC-7 ===
* DC-1 - {{alds|not started}}

=== DC-8 ===
* DC-8-10 - {{alds|not started}}
* DC-8-20 - {{alds|not started}}
* DC-8-30 - {{alds|not started}}
* DC-8-40 - {{alds|not started}}
* DC-8-50 - {{alds|not started}}
* DC-8-60 - {{alds|stable}}
* DC-8-70 - {{alds|stable}}

=== DC-9 ===
* DC-9-10 - {{alds|not started}}
* DC-9-20 - {{alds|not started}}
* DC-9-30 - {{alds|abandoned}}
* DC-9-40 - {{alds|not started}}

=== DC-10 ===
* DC-10-10 - {{alds|not started}}
* DC-10-20 - {{alds|not started}}
* DC-10-30 - {{alds|stable}}
* DC-10-40 - {{alds|not started}}

== Embraer Manufacturers ==
=== Embraer 120 Series ===
* EMB120 - {{alds|not started}}
* EMB125 - {{alds|not started}}
* EMB140 - {{alds|not started}}
* EMB145 - {{alds|abandoned}}

=== Embraer E-jet Series ===
* ERJ170 - {{alds|stable}}
* ERJ175 - {{alds|stable}}
* ERJ190 - {{alds|stable}}
* ERJ195 - {{alds|stable}}
* Legacy - {{alds|not started}}

== Fokker Aero-structures ==
=== Fokker F27 ===
* Fokker F27 - {{alds|not started}}

=== Fokker 50 ===
* [[Fokker 50]] - {{alds|active}} by {{usr|Erik Hofman}} {{fgaddon aircraft url|fokker50}}

=== Fokker 60 ===
* Fokker 60 - {{alds|not started}}

=== Fokker 70 ===
* [[Fokker 70]] - {{alds|active}} by {{usr|Erik Hofman}} {{fgaddon aircraft url|fokker100}}

=== Fokker 100 ===
* [[Fokker 100]] - {{alds|active}} by {{usr|Erik Hofman}} {{fgaddon aircraft url|fokker100}}

=== Fokker 130 ===
* [[Fokker 100]] - {{alds|active}} by {{usr|Erik Hofman}} {{fgaddon aircraft url|fokker100}}

== Lockheed Corporation ==
=== Lockheed 1049H ===
* [[Lockheed_Constellation|L1049H Super Constellation]] - {{alds|stable}}

=== Lockheed L1011 ===
* L1011-1 - {{alds|not started}}
* L1011-100 - {{alds|not started}}
* L1011-200 - {{alds|not started}}
* L1011-500 - {{alds|abandoned}}

== McDonnell Douglas ==

=== MD-11 ===
* MD-10 - {{alds|stable}}, {{alds|abandoned}}
* [[MD-11]] - {{alds|stable}}, {{alds|stalled}}
* MD-11Family (McDonnell Dawn Project)
** MD-10/F/ERX - {{alds|stable}}, {{alds|active}} by {{usr|it0uchpods|it0uchpods}} Design Group
** MD-11/F/ER - {{alds|stable}}, {{alds|active}} by {{usr|it0uchpods|it0uchpods}} Design Group

=== MD-80 ===
* MD-81 - {{alds|abandoned}}
* MD-82 - {{alds|stable}}, {{alds|abandoned}} Included in MD-88 package
* MD-83 - {{alds|abandoned}}
* MD-87 - {{alds|stable}}, {{alds|abandoned}} Included in MD-88 package
* MD-88 - {{alds|stable}}, {{alds|abandoned}}

=== MD-90 ===
* MD-90 - {{alds|stable}}, {{alds|abandoned}}

== Tupolev Design Bureau ==

=== Tu-134 ===
* [[Tupolev Tu-134]] - {{alds|stalled}}

=== Tu-154 ===
* [[Tupolev Tu-154B]] - {{alds|stable}}

[[Category:Aircraft enhancement]]

Airliner development status

2017-08-24T14:10:58Z

Circumn: /* Boeing 757 */ Coalesce all variants that are shipped together in FGAddon. Add C-32A, C-32B.

Airliner development status

2017-08-24T14:08:33Z

Circumn: /* Airbus A380 */ stable, not abandoned.

The Airliner Development Statuses were previously managed by Skyop in the forum but due to no response there, I created this page. Here, you don't have to go asking someone to change an airliner's status, you can do this yourself.

== Airbus Industries ==
=== Airbus A300 ===
* Airbus A300-B2 - {{alds|stalled}}
* Airbus A300-B4 - {{alds|stalled}}
* [[Airbus A300-600]] - {{alds|active}}
* [[Airbus A300-600ST]] - {{alds|abandoned}}

=== Airbus A310 ===
* Airbus A310-200 - {{alds|not started}}
* [[Airbus A310-300]] - {{alds|active}}

=== Airbus A320 ===
* [[A320-family]]
** Airbus A318-100 - {{alds|abandoned}}
** Airbus A318-200 - {{alds|abandoned}}
** Airbus A319-100 - {{alds|abandoned}}
** Airbus A319-200 - {{alds|abandoned}}
** Airbus A320-100 - {{alds|abandoned}}
** Airbus A320-200 - {{alds|abandoned}}
** Airbus A321-100 - {{alds|abandoned}}
** Airbus A321-200 - {{alds|abandoned}}

* [[A320Family|A320Family by it0uchpods]]
** Airbus A319-100 - {{alds|stable}}, {{alds|active}} by {{usr|it0uchpods|it0uchpods}} Design Group
** Airbus A319neo - {{alds|not started}}
** Airbus A320-100 - {{alds|stable}}, {{alds|active}} by {{usr|it0uchpods|it0uchpods}} Design Group
** Airbus A320-200 - {{alds|stable}}, {{alds|active}} by {{usr|it0uchpods|it0uchpods}} Design Group
** Airbus A320neo - {{alds|stable}}, {{alds|active}} by {{usr|it0uchpods|it0uchpods}} Design Group
** Airbus A321-100 - {{alds|not started}}
** Airbus A321-200 - {{alds|stable}}, {{alds|active}} by {{usr|it0uchpods|it0uchpods}} Design Group
** Airbus A321neo - {{alds|stable}}, {{alds|active}} by {{usr|it0uchpods|it0uchpods}} Design Group

* [[Airbus A320neo|A320neo]]
** Airbus A319neo - {{alds|abandoned}}
** Airbus A320neo - {{alds|abandoned}}
** Airbus A321neo - {{alds|abandoned}}

=== Airbus A330 ===
* [[Airbus A330-200]] - {{alds|stable}}, continued by Artix and the Project 300 Dev Team
* Airbus A330-200F - {{alds|not started}}
* [[Airbus A330-300]] - {{alds|stable}}

=== Airbus A340 ===
* Airbus A340-200 - {{alds|stable}}, {{alds|abandoned}}
* Airbus A340-300 - {{alds|stable}}, {{alds|abandoned}}
* Airbus A340-500 - {{alds|not started}}
* Airbus A340-600 - {{alds|stable}}, {{alds|abandoned}}

=== Airbus A350 ===
* Airbus A350-800 -{{alds|not started}}
* Airbus A350-900 - {{alds|stalled}}
* Airbus A350-1000 -{{alds|not started}}

=== Airbus A380 ===
* [[Airbus A380|Airbus A380-800]] - {{alds|stable}}
* Airbus A380-900 - {{alds|not started}}

== Avions Transportation Regional ==
=== ATR-42 ===
* ATR-42-200 - {{alds|not started}}
* ATR-42-300 - {{alds|not started}}
* ATR-42-500 - {{alds|stalled}}
* ATR-42-600 - {{alds|stalled}}

=== ATR-72 ===
* [[ATR 72-500|ATR-72-500]] - {{alds|stalled}}
* ATR-72-600 - {{alds|stalled}}

== Boeing Commercial Airplanes ==
=== Boeing 707 ===
* [[Boeing_707-420|Boeing 707]]-320C, -420, 707-TT, EC-137D - {{alds|stable}} (official FGAddon version, using JSBSim)
* [[Boeing_707-320|Boeing 707-320C, 3J9C]] - {{alds|stable}} (using YAsim)
* Boeing 720 - {{alds|not started}}
* Boeing KC-137R {{alds|stable}}, {{alds|active}} by {{usr|it0uchpods}} and {{usr|J Maverick 16}}. {{github url|user=JMaverick16|repo=KC-137R}}

=== Boeing 717 ===
* [[Boeing_717/it0uchpods|Boeing 717-200]] - {{alds|stable}}, {{alds|abandoned}}

=== Boeing 727 ===
* Boeing 727-100 - {{alds|not started}}
* [[727-200|Boeing 727-200]] - {{alds|stable}}, {{alds|active}} by {{usr|it0uchpods|it0uchpods}}

=== Boeing 737 ===
* Boeing 737-100 - {{alds|abandoned}}
* Boeing 737-200 - {{alds|abandoned}}
* [[Boeing 737-300]] - {{alds|active}} by {{usr|Michael Soitanen}} {{fgaddon aircraft url|737-300}}
* [[Boeing 737-400]] - {{alds|stalled}}
* [[Boeing 737-500]] - {{alds|stalled}}
* Boeing 737NG models - {{alds|active}} by {{usr|Michael Soitanen}}
* Boeing 737-8 - {{alds|stable}}, {{alds|active}}
* [[Boeing 737-7 MAX]] - {{alds|not started}}
* [[Boeing 737-8 MAX]] - {{alds|not started}}
* [[Boeing 737-9 MAX]] - {{alds|not started}}
* Boeing 737-700, E-7A AEW&C, P-8A, NG JSTARS, C-40A/B - {{alds|not started}} by {{usr|J Maverick 16}}

=== Boeing 747 ===
* [[Boeing 747-100]] - {{alds|abandoned}}
* [[Boeing 747-200]] - {{alds|abandoned}}
* Boeing 747-300 - {{alds|not started}}
* [[Boeing 747-400]] - {{alds|stable}}
* [[Boeing 747-8i]] - {{alds|active}}
* Boeing 747-8F - {{alds|active}}
* Boeing 747SP - {{alds|stalled}}

=== Boeing 757 ===
* [[Boeing 757-200]] - {{alds|stable}}
* Boeing 757-300 - {{alds|stable}}
* Boeing C-32J - {{alds|stable}}, {{alds|active}} by {{usr|J Maverick 16}} and {{usr|it0uchpods}}

=== Boeing 767 ===
* Boeing 767-200 - {{alds|not started}}
* [[Boeing 767-300]] - {{alds|active}}
* [[Boeing 767-300F]] - {{alds|active}}
* Boeing 767-400 - {{alds|not started}}
* Boeing KC-46, E-767, KC-767 - {{alds|not started}} by {{usr|J Maverick 16}}

=== Boeing 777 ===
* [[Boeing 777-200]] - {{alds|stable}}
* [[Boeing 777-300]] - {{alds|stable}}
* Boeing 777-8X - {{alds|not started}}
* Boeing 777-9X - {{alds|not started}}

=== Boeing 787 ===
* [[Boeing 787-8]] - {{alds|stable}}
* Boeing 787-9 - {{alds|stable}}, {{alds|active}}

== Bombardier Aerospace ==
=== Dash 7 ===
* Dash 7-100 - {{alds|abandoned}}

=== Dash 8 ===
* Dash 8-300 - {{alds|abandoned}}
* Dash 8-Q400 - {{alds|active}}

=== Canadair Regional Jets ===
* [[CRJ-200|CRJ200]] - {{alds|active}}
* CRJ700 - {{alds|stable}}
* [[CRJ-900|CRJ900]] - {{alds|stable}}
* CRJ1000 - {{alds|stable}}

=== CSeries ===
* CS100 - {{alds|stalled}}
* CS300 - {{alds|stalled}}

== Dornier Luftfahrt GmbH (Fairchild-Dornier) ==
=== Dornier 328-100 ===
* Dornier 328-100 - {{alds|active}} by {{usr|HHS}}
=== Dornier 328-110 ===
* Dornier 328-110 - {{alds|active}} by {{usr|HHS}}
=== Dornier 328-120 ===
* Dornier 328-120 - {{alds|active}} by {{usr|HHS}}
=== Dornier 328-130 ===
* Dornier 328-130 - {{alds|active}} by {{usr|HHS}}
=== Dornier 328-300 ===
* Dornier 328-300 - {{alds|active}} by {{usr|HHS}}

== Douglas Aircraft Company ==
=== DC-1 ===
* DC-1 - {{alds|not started}}

=== DC-2 ===
* DC-2 - {{alds|abandoned}}

=== DC-3 ===
* DC-3 - {{alds|stable}}

=== DC-4 ===
* DC-4 - {{alds|not started}}

=== DC-5 ===
* DC-5 - {{alds|not started}}

=== DC-6 ===
* DC-6 - {{alds|stable}}

=== DC-7 ===
* DC-1 - {{alds|not started}}

=== DC-8 ===
* DC-8-10 - {{alds|not started}}
* DC-8-20 - {{alds|not started}}
* DC-8-30 - {{alds|not started}}
* DC-8-40 - {{alds|not started}}
* DC-8-50 - {{alds|not started}}
* DC-8-60 - {{alds|stable}}
* DC-8-70 - {{alds|stable}}

=== DC-9 ===
* DC-9-10 - {{alds|not started}}
* DC-9-20 - {{alds|not started}}
* DC-9-30 - {{alds|abandoned}}
* DC-9-40 - {{alds|not started}}

=== DC-10 ===
* DC-10-10 - {{alds|not started}}
* DC-10-20 - {{alds|not started}}
* DC-10-30 - {{alds|stable}}
* DC-10-40 - {{alds|not started}}

== Embraer Manufacturers ==
=== Embraer 120 Series ===
* EMB120 - {{alds|not started}}
* EMB125 - {{alds|not started}}
* EMB140 - {{alds|not started}}
* EMB145 - {{alds|abandoned}}

=== Embraer E-jet Series ===
* ERJ170 - {{alds|stable}}
* ERJ175 - {{alds|stable}}
* ERJ190 - {{alds|stable}}
* ERJ195 - {{alds|stable}}
* Legacy - {{alds|not started}}

== Fokker Aero-structures ==
=== Fokker F27 ===
* Fokker F27 - {{alds|not started}}

=== Fokker 50 ===
* [[Fokker 50]] - {{alds|active}} by {{usr|Erik Hofman}} {{fgaddon aircraft url|fokker50}}

=== Fokker 60 ===
* Fokker 60 - {{alds|not started}}

=== Fokker 70 ===
* [[Fokker 70]] - {{alds|active}} by {{usr|Erik Hofman}} {{fgaddon aircraft url|fokker100}}

=== Fokker 100 ===
* [[Fokker 100]] - {{alds|active}} by {{usr|Erik Hofman}} {{fgaddon aircraft url|fokker100}}

=== Fokker 130 ===
* [[Fokker 100]] - {{alds|active}} by {{usr|Erik Hofman}} {{fgaddon aircraft url|fokker100}}

== Lockheed Corporation ==
=== Lockheed 1049H ===
* [[Lockheed_Constellation|L1049H Super Constellation]] - {{alds|stable}}

=== Lockheed L1011 ===
* L1011-1 - {{alds|not started}}
* L1011-100 - {{alds|not started}}
* L1011-200 - {{alds|not started}}
* L1011-500 - {{alds|abandoned}}

== McDonnell Douglas ==

=== MD-11 ===
* MD-10 - {{alds|stable}}, {{alds|abandoned}}
* [[MD-11]] - {{alds|stable}}, {{alds|stalled}}
* MD-11Family (McDonnell Dawn Project)
** MD-10/F/ERX - {{alds|stable}}, {{alds|active}} by {{usr|it0uchpods|it0uchpods}} Design Group
** MD-11/F/ER - {{alds|stable}}, {{alds|active}} by {{usr|it0uchpods|it0uchpods}} Design Group

=== MD-80 ===
* MD-81 - {{alds|abandoned}}
* MD-82 - {{alds|stable}}, {{alds|abandoned}} Included in MD-88 package
* MD-83 - {{alds|abandoned}}
* MD-87 - {{alds|stable}}, {{alds|abandoned}} Included in MD-88 package
* MD-88 - {{alds|stable}}, {{alds|abandoned}}

=== MD-90 ===
* MD-90 - {{alds|stable}}, {{alds|abandoned}}

[[Category:Aircraft enhancement]]

Airliner development status

2017-08-24T14:05:47Z

Circumn: /* Lockheed Corporation */ link to the Lockheed Super Constellation

The Airliner Development Statuses were previously managed by Skyop in the forum but due to no response there, I created this page. Here, you don't have to go asking someone to change an airliner's status, you can do this yourself.

== Airbus Industries ==
=== Airbus A300 ===
* Airbus A300-B2 - {{alds|stalled}}
* Airbus A300-B4 - {{alds|stalled}}
* [[Airbus A300-600]] - {{alds|active}}
* [[Airbus A300-600ST]] - {{alds|abandoned}}

=== Airbus A310 ===
* Airbus A310-200 - {{alds|not started}}
* [[Airbus A310-300]] - {{alds|active}}

=== Airbus A320 ===
* [[A320-family]]
** Airbus A318-100 - {{alds|abandoned}}
** Airbus A318-200 - {{alds|abandoned}}
** Airbus A319-100 - {{alds|abandoned}}
** Airbus A319-200 - {{alds|abandoned}}
** Airbus A320-100 - {{alds|abandoned}}
** Airbus A320-200 - {{alds|abandoned}}
** Airbus A321-100 - {{alds|abandoned}}
** Airbus A321-200 - {{alds|abandoned}}

* [[A320Family|A320Family by it0uchpods]]
** Airbus A319-100 - {{alds|stable}}, {{alds|active}} by {{usr|it0uchpods|it0uchpods}} Design Group
** Airbus A319neo - {{alds|not started}}
** Airbus A320-100 - {{alds|stable}}, {{alds|active}} by {{usr|it0uchpods|it0uchpods}} Design Group
** Airbus A320-200 - {{alds|stable}}, {{alds|active}} by {{usr|it0uchpods|it0uchpods}} Design Group
** Airbus A320neo - {{alds|stable}}, {{alds|active}} by {{usr|it0uchpods|it0uchpods}} Design Group
** Airbus A321-100 - {{alds|not started}}
** Airbus A321-200 - {{alds|stable}}, {{alds|active}} by {{usr|it0uchpods|it0uchpods}} Design Group
** Airbus A321neo - {{alds|stable}}, {{alds|active}} by {{usr|it0uchpods|it0uchpods}} Design Group

* [[Airbus A320neo|A320neo]]
** Airbus A319neo - {{alds|abandoned}}
** Airbus A320neo - {{alds|abandoned}}
** Airbus A321neo - {{alds|abandoned}}

=== Airbus A330 ===
* [[Airbus A330-200]] - {{alds|stable}}, continued by Artix and the Project 300 Dev Team
* Airbus A330-200F - {{alds|not started}}
* [[Airbus A330-300]] - {{alds|stable}}

=== Airbus A340 ===
* Airbus A340-200 - {{alds|stable}}, {{alds|abandoned}}
* Airbus A340-300 - {{alds|stable}}, {{alds|abandoned}}
* Airbus A340-500 - {{alds|not started}}
* Airbus A340-600 - {{alds|stable}}, {{alds|abandoned}}

=== Airbus A350 ===
* Airbus A350-800 -{{alds|not started}}
* Airbus A350-900 - {{alds|stalled}}
* Airbus A350-1000 -{{alds|not started}}

=== Airbus A380 ===
* [[Airbus A380|Airbus A380-800]] - {{alds|abandoned}}
* Airbus A380-900 - {{alds|not started}}

== Avions Transportation Regional ==
=== ATR-42 ===
* ATR-42-200 - {{alds|not started}}
* ATR-42-300 - {{alds|not started}}
* ATR-42-500 - {{alds|stalled}}
* ATR-42-600 - {{alds|stalled}}

=== ATR-72 ===
* [[ATR 72-500|ATR-72-500]] - {{alds|stalled}}
* ATR-72-600 - {{alds|stalled}}

== Boeing Commercial Airplanes ==
=== Boeing 707 ===
* [[Boeing_707-420|Boeing 707]]-320C, -420, 707-TT, EC-137D - {{alds|stable}} (official FGAddon version, using JSBSim)
* [[Boeing_707-320|Boeing 707-320C, 3J9C]] - {{alds|stable}} (using YAsim)
* Boeing 720 - {{alds|not started}}
* Boeing KC-137R {{alds|stable}}, {{alds|active}} by {{usr|it0uchpods}} and {{usr|J Maverick 16}}. {{github url|user=JMaverick16|repo=KC-137R}}

=== Boeing 717 ===
* [[Boeing_717/it0uchpods|Boeing 717-200]] - {{alds|stable}}, {{alds|abandoned}}

=== Boeing 727 ===
* Boeing 727-100 - {{alds|not started}}
* [[727-200|Boeing 727-200]] - {{alds|stable}}, {{alds|active}} by {{usr|it0uchpods|it0uchpods}}

=== Boeing 737 ===
* Boeing 737-100 - {{alds|abandoned}}
* Boeing 737-200 - {{alds|abandoned}}
* [[Boeing 737-300]] - {{alds|active}} by {{usr|Michael Soitanen}} {{fgaddon aircraft url|737-300}}
* [[Boeing 737-400]] - {{alds|stalled}}
* [[Boeing 737-500]] - {{alds|stalled}}
* Boeing 737NG models - {{alds|active}} by {{usr|Michael Soitanen}}
* Boeing 737-8 - {{alds|stable}}, {{alds|active}}
* [[Boeing 737-7 MAX]] - {{alds|not started}}
* [[Boeing 737-8 MAX]] - {{alds|not started}}
* [[Boeing 737-9 MAX]] - {{alds|not started}}
* Boeing 737-700, E-7A AEW&C, P-8A, NG JSTARS, C-40A/B - {{alds|not started}} by {{usr|J Maverick 16}}

=== Boeing 747 ===
* [[Boeing 747-100]] - {{alds|abandoned}}
* [[Boeing 747-200]] - {{alds|abandoned}}
* Boeing 747-300 - {{alds|not started}}
* [[Boeing 747-400]] - {{alds|stable}}
* [[Boeing 747-8i]] - {{alds|active}}
* Boeing 747-8F - {{alds|active}}
* Boeing 747SP - {{alds|stalled}}

=== Boeing 757 ===
* [[Boeing 757-200]] - {{alds|stable}}
* Boeing 757-300 - {{alds|stable}}
* Boeing C-32J - {{alds|stable}}, {{alds|active}} by {{usr|J Maverick 16}} and {{usr|it0uchpods}}

=== Boeing 767 ===
* Boeing 767-200 - {{alds|not started}}
* [[Boeing 767-300]] - {{alds|active}}
* [[Boeing 767-300F]] - {{alds|active}}
* Boeing 767-400 - {{alds|not started}}
* Boeing KC-46, E-767, KC-767 - {{alds|not started}} by {{usr|J Maverick 16}}

=== Boeing 777 ===
* [[Boeing 777-200]] - {{alds|stable}}
* [[Boeing 777-300]] - {{alds|stable}}
* Boeing 777-8X - {{alds|not started}}
* Boeing 777-9X - {{alds|not started}}

=== Boeing 787 ===
* [[Boeing 787-8]] - {{alds|stable}}
* Boeing 787-9 - {{alds|stable}}, {{alds|active}}

== Bombardier Aerospace ==
=== Dash 7 ===
* Dash 7-100 - {{alds|abandoned}}

=== Dash 8 ===
* Dash 8-300 - {{alds|abandoned}}
* Dash 8-Q400 - {{alds|active}}

=== Canadair Regional Jets ===
* [[CRJ-200|CRJ200]] - {{alds|active}}
* CRJ700 - {{alds|stable}}
* [[CRJ-900|CRJ900]] - {{alds|stable}}
* CRJ1000 - {{alds|stable}}

=== CSeries ===
* CS100 - {{alds|stalled}}
* CS300 - {{alds|stalled}}

== Dornier Luftfahrt GmbH (Fairchild-Dornier) ==
=== Dornier 328-100 ===
* Dornier 328-100 - {{alds|active}} by {{usr|HHS}}
=== Dornier 328-110 ===
* Dornier 328-110 - {{alds|active}} by {{usr|HHS}}
=== Dornier 328-120 ===
* Dornier 328-120 - {{alds|active}} by {{usr|HHS}}
=== Dornier 328-130 ===
* Dornier 328-130 - {{alds|active}} by {{usr|HHS}}
=== Dornier 328-300 ===
* Dornier 328-300 - {{alds|active}} by {{usr|HHS}}

== Douglas Aircraft Company ==
=== DC-1 ===
* DC-1 - {{alds|not started}}

=== DC-2 ===
* DC-2 - {{alds|abandoned}}

=== DC-3 ===
* DC-3 - {{alds|stable}}

=== DC-4 ===
* DC-4 - {{alds|not started}}

=== DC-5 ===
* DC-5 - {{alds|not started}}

=== DC-6 ===
* DC-6 - {{alds|stable}}

=== DC-7 ===
* DC-1 - {{alds|not started}}

=== DC-8 ===
* DC-8-10 - {{alds|not started}}
* DC-8-20 - {{alds|not started}}
* DC-8-30 - {{alds|not started}}
* DC-8-40 - {{alds|not started}}
* DC-8-50 - {{alds|not started}}
* DC-8-60 - {{alds|stable}}
* DC-8-70 - {{alds|stable}}

=== DC-9 ===
* DC-9-10 - {{alds|not started}}
* DC-9-20 - {{alds|not started}}
* DC-9-30 - {{alds|abandoned}}
* DC-9-40 - {{alds|not started}}

=== DC-10 ===
* DC-10-10 - {{alds|not started}}
* DC-10-20 - {{alds|not started}}
* DC-10-30 - {{alds|stable}}
* DC-10-40 - {{alds|not started}}

== Embraer Manufacturers ==
=== Embraer 120 Series ===
* EMB120 - {{alds|not started}}
* EMB125 - {{alds|not started}}
* EMB140 - {{alds|not started}}
* EMB145 - {{alds|abandoned}}

=== Embraer E-jet Series ===
* ERJ170 - {{alds|stable}}
* ERJ175 - {{alds|stable}}
* ERJ190 - {{alds|stable}}
* ERJ195 - {{alds|stable}}
* Legacy - {{alds|not started}}

== Fokker Aero-structures ==
=== Fokker F27 ===
* Fokker F27 - {{alds|not started}}

=== Fokker 50 ===
* [[Fokker 50]] - {{alds|active}} by {{usr|Erik Hofman}} {{fgaddon aircraft url|fokker50}}

=== Fokker 60 ===
* Fokker 60 - {{alds|not started}}

=== Fokker 70 ===
* [[Fokker 70]] - {{alds|active}} by {{usr|Erik Hofman}} {{fgaddon aircraft url|fokker100}}

=== Fokker 100 ===
* [[Fokker 100]] - {{alds|active}} by {{usr|Erik Hofman}} {{fgaddon aircraft url|fokker100}}

=== Fokker 130 ===
* [[Fokker 100]] - {{alds|active}} by {{usr|Erik Hofman}} {{fgaddon aircraft url|fokker100}}

== Lockheed Corporation ==
=== Lockheed 1049H ===
* [[Lockheed_Constellation|L1049H Super Constellation]] - {{alds|stable}}

=== Lockheed L1011 ===
* L1011-1 - {{alds|not started}}
* L1011-100 - {{alds|not started}}
* L1011-200 - {{alds|not started}}
* L1011-500 - {{alds|abandoned}}

== McDonnell Douglas ==

=== MD-11 ===
* MD-10 - {{alds|stable}}, {{alds|abandoned}}
* [[MD-11]] - {{alds|stable}}, {{alds|stalled}}
* MD-11Family (McDonnell Dawn Project)
** MD-10/F/ERX - {{alds|stable}}, {{alds|active}} by {{usr|it0uchpods|it0uchpods}} Design Group
** MD-11/F/ER - {{alds|stable}}, {{alds|active}} by {{usr|it0uchpods|it0uchpods}} Design Group

=== MD-80 ===
* MD-81 - {{alds|abandoned}}
* MD-82 - {{alds|stable}}, {{alds|abandoned}} Included in MD-88 package
* MD-83 - {{alds|abandoned}}
* MD-87 - {{alds|stable}}, {{alds|abandoned}} Included in MD-88 package
* MD-88 - {{alds|stable}}, {{alds|abandoned}}

=== MD-90 ===
* MD-90 - {{alds|stable}}, {{alds|abandoned}}

[[Category:Aircraft enhancement]]

Airliner development status

2017-08-24T14:04:07Z

Circumn: /* Boeing 707 */ stable, very stable.

The Airliner Development Statuses were previously managed by Skyop in the forum but due to no response there, I created this page. Here, you don't have to go asking someone to change an airliner's status, you can do this yourself.

== Airbus Industries ==
=== Airbus A300 ===
* Airbus A300-B2 - {{alds|stalled}}
* Airbus A300-B4 - {{alds|stalled}}
* [[Airbus A300-600]] - {{alds|active}}
* [[Airbus A300-600ST]] - {{alds|abandoned}}

=== Airbus A310 ===
* Airbus A310-200 - {{alds|not started}}
* [[Airbus A310-300]] - {{alds|active}}

=== Airbus A320 ===
* [[A320-family]]
** Airbus A318-100 - {{alds|abandoned}}
** Airbus A318-200 - {{alds|abandoned}}
** Airbus A319-100 - {{alds|abandoned}}
** Airbus A319-200 - {{alds|abandoned}}
** Airbus A320-100 - {{alds|abandoned}}
** Airbus A320-200 - {{alds|abandoned}}
** Airbus A321-100 - {{alds|abandoned}}
** Airbus A321-200 - {{alds|abandoned}}

* [[A320Family|A320Family by it0uchpods]]
** Airbus A319-100 - {{alds|stable}}, {{alds|active}} by {{usr|it0uchpods|it0uchpods}} Design Group
** Airbus A319neo - {{alds|not started}}
** Airbus A320-100 - {{alds|stable}}, {{alds|active}} by {{usr|it0uchpods|it0uchpods}} Design Group
** Airbus A320-200 - {{alds|stable}}, {{alds|active}} by {{usr|it0uchpods|it0uchpods}} Design Group
** Airbus A320neo - {{alds|stable}}, {{alds|active}} by {{usr|it0uchpods|it0uchpods}} Design Group
** Airbus A321-100 - {{alds|not started}}
** Airbus A321-200 - {{alds|stable}}, {{alds|active}} by {{usr|it0uchpods|it0uchpods}} Design Group
** Airbus A321neo - {{alds|stable}}, {{alds|active}} by {{usr|it0uchpods|it0uchpods}} Design Group

* [[Airbus A320neo|A320neo]]
** Airbus A319neo - {{alds|abandoned}}
** Airbus A320neo - {{alds|abandoned}}
** Airbus A321neo - {{alds|abandoned}}

=== Airbus A330 ===
* [[Airbus A330-200]] - {{alds|stable}}, continued by Artix and the Project 300 Dev Team
* Airbus A330-200F - {{alds|not started}}
* [[Airbus A330-300]] - {{alds|stable}}

=== Airbus A340 ===
* Airbus A340-200 - {{alds|stable}}, {{alds|abandoned}}
* Airbus A340-300 - {{alds|stable}}, {{alds|abandoned}}
* Airbus A340-500 - {{alds|not started}}
* Airbus A340-600 - {{alds|stable}}, {{alds|abandoned}}

=== Airbus A350 ===
* Airbus A350-800 -{{alds|not started}}
* Airbus A350-900 - {{alds|stalled}}
* Airbus A350-1000 -{{alds|not started}}

=== Airbus A380 ===
* [[Airbus A380|Airbus A380-800]] - {{alds|abandoned}}
* Airbus A380-900 - {{alds|not started}}

== Avions Transportation Regional ==
=== ATR-42 ===
* ATR-42-200 - {{alds|not started}}
* ATR-42-300 - {{alds|not started}}
* ATR-42-500 - {{alds|stalled}}
* ATR-42-600 - {{alds|stalled}}

=== ATR-72 ===
* [[ATR 72-500|ATR-72-500]] - {{alds|stalled}}
* ATR-72-600 - {{alds|stalled}}

== Boeing Commercial Airplanes ==
=== Boeing 707 ===
* [[Boeing_707-420|Boeing 707]]-320C, -420, 707-TT, EC-137D - {{alds|stable}} (official FGAddon version, using JSBSim)
* [[Boeing_707-320|Boeing 707-320C, 3J9C]] - {{alds|stable}} (using YAsim)
* Boeing 720 - {{alds|not started}}
* Boeing KC-137R {{alds|stable}}, {{alds|active}} by {{usr|it0uchpods}} and {{usr|J Maverick 16}}. {{github url|user=JMaverick16|repo=KC-137R}}

=== Boeing 717 ===
* [[Boeing_717/it0uchpods|Boeing 717-200]] - {{alds|stable}}, {{alds|abandoned}}

=== Boeing 727 ===
* Boeing 727-100 - {{alds|not started}}
* [[727-200|Boeing 727-200]] - {{alds|stable}}, {{alds|active}} by {{usr|it0uchpods|it0uchpods}}

=== Boeing 737 ===
* Boeing 737-100 - {{alds|abandoned}}
* Boeing 737-200 - {{alds|abandoned}}
* [[Boeing 737-300]] - {{alds|active}} by {{usr|Michael Soitanen}} {{fgaddon aircraft url|737-300}}
* [[Boeing 737-400]] - {{alds|stalled}}
* [[Boeing 737-500]] - {{alds|stalled}}
* Boeing 737NG models - {{alds|active}} by {{usr|Michael Soitanen}}
* Boeing 737-8 - {{alds|stable}}, {{alds|active}}
* [[Boeing 737-7 MAX]] - {{alds|not started}}
* [[Boeing 737-8 MAX]] - {{alds|not started}}
* [[Boeing 737-9 MAX]] - {{alds|not started}}
* Boeing 737-700, E-7A AEW&C, P-8A, NG JSTARS, C-40A/B - {{alds|not started}} by {{usr|J Maverick 16}}

=== Boeing 747 ===
* [[Boeing 747-100]] - {{alds|abandoned}}
* [[Boeing 747-200]] - {{alds|abandoned}}
* Boeing 747-300 - {{alds|not started}}
* [[Boeing 747-400]] - {{alds|stable}}
* [[Boeing 747-8i]] - {{alds|active}}
* Boeing 747-8F - {{alds|active}}
* Boeing 747SP - {{alds|stalled}}

=== Boeing 757 ===
* [[Boeing 757-200]] - {{alds|stable}}
* Boeing 757-300 - {{alds|stable}}
* Boeing C-32J - {{alds|stable}}, {{alds|active}} by {{usr|J Maverick 16}} and {{usr|it0uchpods}}

=== Boeing 767 ===
* Boeing 767-200 - {{alds|not started}}
* [[Boeing 767-300]] - {{alds|active}}
* [[Boeing 767-300F]] - {{alds|active}}
* Boeing 767-400 - {{alds|not started}}
* Boeing KC-46, E-767, KC-767 - {{alds|not started}} by {{usr|J Maverick 16}}

=== Boeing 777 ===
* [[Boeing 777-200]] - {{alds|stable}}
* [[Boeing 777-300]] - {{alds|stable}}
* Boeing 777-8X - {{alds|not started}}
* Boeing 777-9X - {{alds|not started}}

=== Boeing 787 ===
* [[Boeing 787-8]] - {{alds|stable}}
* Boeing 787-9 - {{alds|stable}}, {{alds|active}}

== Bombardier Aerospace ==
=== Dash 7 ===
* Dash 7-100 - {{alds|abandoned}}

=== Dash 8 ===
* Dash 8-300 - {{alds|abandoned}}
* Dash 8-Q400 - {{alds|active}}

=== Canadair Regional Jets ===
* [[CRJ-200|CRJ200]] - {{alds|active}}
* CRJ700 - {{alds|stable}}
* [[CRJ-900|CRJ900]] - {{alds|stable}}
* CRJ1000 - {{alds|stable}}

=== CSeries ===
* CS100 - {{alds|stalled}}
* CS300 - {{alds|stalled}}

== Dornier Luftfahrt GmbH (Fairchild-Dornier) ==
=== Dornier 328-100 ===
* Dornier 328-100 - {{alds|active}} by {{usr|HHS}}
=== Dornier 328-110 ===
* Dornier 328-110 - {{alds|active}} by {{usr|HHS}}
=== Dornier 328-120 ===
* Dornier 328-120 - {{alds|active}} by {{usr|HHS}}
=== Dornier 328-130 ===
* Dornier 328-130 - {{alds|active}} by {{usr|HHS}}
=== Dornier 328-300 ===
* Dornier 328-300 - {{alds|active}} by {{usr|HHS}}

== Douglas Aircraft Company ==
=== DC-1 ===
* DC-1 - {{alds|not started}}

=== DC-2 ===
* DC-2 - {{alds|abandoned}}

=== DC-3 ===
* DC-3 - {{alds|stable}}

=== DC-4 ===
* DC-4 - {{alds|not started}}

=== DC-5 ===
* DC-5 - {{alds|not started}}

=== DC-6 ===
* DC-6 - {{alds|stable}}

=== DC-7 ===
* DC-1 - {{alds|not started}}

=== DC-8 ===
* DC-8-10 - {{alds|not started}}
* DC-8-20 - {{alds|not started}}
* DC-8-30 - {{alds|not started}}
* DC-8-40 - {{alds|not started}}
* DC-8-50 - {{alds|not started}}
* DC-8-60 - {{alds|stable}}
* DC-8-70 - {{alds|stable}}

=== DC-9 ===
* DC-9-10 - {{alds|not started}}
* DC-9-20 - {{alds|not started}}
* DC-9-30 - {{alds|abandoned}}
* DC-9-40 - {{alds|not started}}

=== DC-10 ===
* DC-10-10 - {{alds|not started}}
* DC-10-20 - {{alds|not started}}
* DC-10-30 - {{alds|stable}}
* DC-10-40 - {{alds|not started}}

== Embraer Manufacturers ==
=== Embraer 120 Series ===
* EMB120 - {{alds|not started}}
* EMB125 - {{alds|not started}}
* EMB140 - {{alds|not started}}
* EMB145 - {{alds|abandoned}}

=== Embraer E-jet Series ===
* ERJ170 - {{alds|stable}}
* ERJ175 - {{alds|stable}}
* ERJ190 - {{alds|stable}}
* ERJ195 - {{alds|stable}}
* Legacy - {{alds|not started}}

== Fokker Aero-structures ==
=== Fokker F27 ===
* Fokker F27 - {{alds|not started}}

=== Fokker 50 ===
* [[Fokker 50]] - {{alds|active}} by {{usr|Erik Hofman}} {{fgaddon aircraft url|fokker50}}

=== Fokker 60 ===
* Fokker 60 - {{alds|not started}}

=== Fokker 70 ===
* [[Fokker 70]] - {{alds|active}} by {{usr|Erik Hofman}} {{fgaddon aircraft url|fokker100}}

=== Fokker 100 ===
* [[Fokker 100]] - {{alds|active}} by {{usr|Erik Hofman}} {{fgaddon aircraft url|fokker100}}

=== Fokker 130 ===
* [[Fokker 100]] - {{alds|active}} by {{usr|Erik Hofman}} {{fgaddon aircraft url|fokker100}}

== Lockheed Corporation ==
=== Lockheed 1049H ===
* L1049H - {{alds|stable}}

=== Lockheed L1011 ===
* L1011-1 - {{alds|not started}}
* L1011-100 - {{alds|not started}}
* L1011-200 - {{alds|not started}}
* L1011-500 - {{alds|abandoned}}

== McDonnell Douglas ==

=== MD-11 ===
* MD-10 - {{alds|stable}}, {{alds|abandoned}}
* [[MD-11]] - {{alds|stable}}, {{alds|stalled}}
* MD-11Family (McDonnell Dawn Project)
** MD-10/F/ERX - {{alds|stable}}, {{alds|active}} by {{usr|it0uchpods|it0uchpods}} Design Group
** MD-11/F/ER - {{alds|stable}}, {{alds|active}} by {{usr|it0uchpods|it0uchpods}} Design Group

=== MD-80 ===
* MD-81 - {{alds|abandoned}}
* MD-82 - {{alds|stable}}, {{alds|abandoned}} Included in MD-88 package
* MD-83 - {{alds|abandoned}}
* MD-87 - {{alds|stable}}, {{alds|abandoned}} Included in MD-88 package
* MD-88 - {{alds|stable}}, {{alds|abandoned}}

=== MD-90 ===
* MD-90 - {{alds|stable}}, {{alds|abandoned}}

[[Category:Aircraft enhancement]]

Dual control

2017-08-19T19:42:12Z

Circumn: Add Lockheed Constellation

{{Affected by HLA}}
[[File:Dualcontrolready.png]]

'''Dual Control''' is a system for [[FlightGear]] that adds basic support for shared control of an [[aircraft]] over the FlightGear [[Multiplayer Howto|multiplayer network]].

'''Note:''' [[FlightGear 1.9.0]] or later is needed to use Dual Control.

== Aircraft ==

Currently there are a small number of aircraft with dual control support:
* [[Airbus A320 Family]], pilot and co-pilot (<tt>A3xx-xx1</tt>, <tt>A320-copilot</tt>). Available from {{gitorious source|proj=airbus-aircraft|repo=a320|text=Gitorious project page}}. Be sure to rename the aircraft directory to "A320-family" after checking out/downloading.
* [[Airbus A340-600]], pilot and co-pilot (<tt>A340-600</tt>, <tt>A346-copilot</tt>). Available in FlightGear 2.0 or later, Latest beta versions available on the forum.
* [[Blackburn Buccaneer]], pilot and systems officer (<tt>buccaneer</tt>, <tt>buccaneer-obs</tt>). Available in FlightGear 1.9.0 or later.
* [[Boeing 747-400]], pilot flying and pilot monitoring (<tt>747-400</tt>, <tt>747-400-fo</tt>). Available in FlightGear/Git.
* c172p Skyhawk, pilot and copilot (<tt>c172p-pilot</tt> and <tt>c172p-copilot</tt>). Based on David Megginson's [[Cessna C172|c172p]] single control aircraft. Available from [http://www.gidenstam.org/FlightGear/DualControl/Aircraft the dual-control aircraft hangar]. The tar.gz archive for the aircraft should be extracted in [[$FG_ROOT]]/Aircraft/.
* [[Bombardier CRJ700]] (all variants), pilot and first officer (<tt>CRJ700</tt>, et al and <tt>CRJ700-firstofficer</tt>). Copilot can control aircraft using joystick and keyboard shortcuts but not toggle any switches. Available in FlightGear 2.0.0 or later.
* [[Dornier_Do_X|Dornier Do X]], phenomenal experience, pilot and radio operator working on interactive dual coordination for navigation. Available from [http://marc-kraus.de The Lake of Constance]
* [[fr/Douglas DC-3-C47]], pilot and copilot <u>can control aircraft</u>, and passenger 1 to 4 (<tt>dc-3</tt>, <tt>dc-3-copilot</tt>, <tt>dc-3-psg1</tt>, <tt>dc-3-psg2</tt>, <tt>dc-3-psg3</tt>, <tt>dc-3-psg4</tt>). Available in GIT.
* [[Embraer E-jets Family]], pilot and co-pilot (<tt>Embraer-17X</tt>, <tt>Embraer-17X-Copilot</tt>), Avaliable from http://theomegahangar.flymerlion.org
* [[Grumman F-14 Tomcat]], pilot and RIO (<tt>f-14b</tt>, <tt>f-14b-bs</tt>). Available in FlightGear 2.0.0 or later.
* [[Lockheed Constellation]], pilot and flight engineer, available in FGAddon since May 2017, compatible with FlightGear 3.0 and later.
* [[Hughes OH-6 Cayuse]], pilot and co-pilot (<tt>OH-6</tt>, <tt>OH-6-cp</tt>). Available on [[Hughes OH-6 Cayuse|the wiki page]].
* [[ASK-13 sailplane|Schleicher ASK-13 glider]], pilot and passenger (<tt>ask13</tt>, <tt>ask13-passenger</tt>). Available in FlightGear/Git.
* [[Submarine Scout]], pilot and observer (<tt>Submarine_Scout</tt>, <tt>Submarine_Scout-observer</tt>). Available in FlightGear 1.9.0 or later.
* [[Storch|Fieseler Fi 156 Storch]], pilot and passenger (<tt>Fi-156-de</tt>, <tt>Fi-156-passenger</tt>). Available in FlightGear 2.0.0 or later.
* [[Zeppelin NT]], pilot and copilot (<tt>ZLT-NT</tt>, <tt>ZLT-NT-copilot</tt>). Available in FlightGear 1.9.0 or later.

To connect the pilot and copilot selects each other in the Copilot dialog (FlightGear 2.0.0 or later) or set properties as explained in the usage instructions below.

Dual control enables a pilot and copilot to jointly fly the aircraft over the FlightGear multiplayer network. Depending on the aircraft the pilot and copilot have shared control over primary flight controls, throttle, mixture and so on. Exactly which controls are shared varies between the aircraft but usually include elevator trim, flaps, brakes, cockpit switches, the radio stack and some instrument settings. The copilot usually has a subset of the full instrumentation (also depending on the aircraft), usually including airspeed, altimeter, VSI, HSI, turn coordinator, engine RPM and the radio stack. Typically Nav/Comm 1 and the first VOR indicator is best controlled by the pilot, while Nav/Comm 2 and the corresponding VOR indicator is faster for the copilot.

<center>
[[File:ZLT-NT-dual.jpg]]
</center>
<center>
''Side-by-side presentation of the Zeppelin NT pilot's (left) and copilot's (right) views.''
</center>

== Usage instruction ==
The system consists of two "aircraft":

The pilot uses a special variant of the c172p, <tt>c172p-pilot</tt>. The pilot needs to specify the callsign of the copilot (other copilots will be ignored).
For the Zeppelin NT the aircraft names are <tt>ZLT-NT</tt> and <tt>ZLT-NT-copilot</tt>, respectively.

In the current version the pilot and copilot can select each other in their Co/Pilot selection dialogs available from the "Zeppelin NT/c172p-dual-control"->"MP-(Co)Pilot" menus.

Alternatively the relevant properties can be set from the command line or via the property browser.

'''Pilot usage example:'''
fgfs --aircraft=c172p-pilot --prop:/sim/remote/pilot-callsign="someone"

The copilot uses a special "aircraft", c172p-copilot, which piggybacks on the designated pilot and captures the local control inputs. A current limitation is that only the cockpit views are jitter free. There is also a noticeable delay between control inputs and effect, since they are passed via the the multiplayer protocol. The severity of this delay depend on round trip time and some other factors - the delay seems significantly longer than the round trip time itself which is due to buffering in the MP protocol receiver. That said, I have flown successfully as copilot in a setup with 100-120ms round trip time between both pilot and server and copilot and server (total delay >500ms). Landing is a bit exciting in that case, however.

'''Copilot usage example:'''
fgfs --aircraft=c172p-copilot --prop:/sim/remote/pilot-callsign="anybody"
Note: External views are jitter prone for the copilot.

== Developer information ==
{{Caution|
{{FGCquote
|1= Normally the only Nasal available will be loaded from the model xml. The -set is effectively a placeholder for an invisible craft as you'll be sitting inside someone else's MP aircraft. The normal -set file isn't loaded at all. All properties need to be transmitted over MP, so if /instrumentation/cdu/serviceable is missing it'll need to be sent. It's a really strange concept that all of the normal stuff isn't where it usually is. It took me a while to figure out this for the F-14 RIO which I think is done in the same way
|2= {{cite web
| url = http://forum.flightgear.org/viewtopic.php?p=282765#p282765
| title = <nowiki>Re: Dual control for Boeing 777</nowiki>
| author = <nowiki>Richard</nowiki>
| date = Apr 17th, 2016
| added = Apr 17th, 2016
| script_version = 0.25
}}
}}

{{FGCquote
|1= it's roughly like this.
The nasal modules in f-14b-bs-set.xml are loaded and do the work of connecting the RIO to the pilot's aircraft. However the mp-network cannot be loaded until the model is loaded (can't remember exactly why, but it has to be done this way).
So the approach to take is to ensure that you use /sim/multiplay/generic/float or /sim/multiplay/generic/int (0..19 of each) to share the important properties over mp. This is the easiest way. If you look at the F-14 you'll see that a whole heap of animations and gauges are connected to the multiplay properties, because these will work either when flying or as an MP aircraft. If you don't want to change the animations then a nasal module inside the co-pilot to copy the multiplay/generic into the right place will work. See backseat instruments for an example of how this is done.
It gets more difficult if you need to transmit more than the permitted amount of parameters (40). Then you either have to start packing using bits, or use one of the string parameters to share the rest. Using the string parameters (as in the F-14 and the F-15) is quite inefficient and it is something that I'm working on fixing so that we have much better interaction between the front and back seats - but the first thing I'll do is to get the key properties transmitted using ints or floats, and then do the rest probably using the Emesary multiplayer bridge that I'm working on.
|2= {{cite web
| url = http://forum.flightgear.org/viewtopic.php?p=282793#p282793
| title = <nowiki>Re: Dual control for Boeing 777</nowiki>
| author = <nowiki>Richard</nowiki>
| date = Apr 17th, 2016
| added = Apr 17th, 2016
| script_version = 0.25
}}
}}

}}

The main part of the Dual Control system is a set of generic [[Nasal scripting language|Nasal]] modules and modified instrument files that form the core of the networked shared control functionality. See the link below for some more information.

== External links ==

* [http://www.gidenstam.org/FlightGear/DualControl The main page for the Dual Control system.] Check here for the latest information.

[[es:Control dual]]
[[pt:Controle duplo]]
[[Category:Dual control aircraft| ]]
[[Category:FlightGear feature]]
[[Category:Multiplayer]]

Pilatus PC-6 Porter/info

2017-06-16T16:50:44Z

Circumn: Rating.

<includeonly>{{infobox aircraft
| name = Pilatus PC-6 Turbo Porter B2H4
| hangar = fgaddon
| aircraft = PC-6
| image = Pilatus_PC-6.jpg
| image2 = pc-6-3.png
| alt2 = 3D Cockpit
| type = Civil utility aircraft/STOL aircraft
| config = High wing aircraft
| propulsion = Piston aircraft/Single-engine aircraft
| manufacturer = Pilatus aircraft
| authors = Detlef Faber/JeeP Cheney
| fdm = YASim
| fgname = PC6-B2H4
| status-fdm = 3
| status-systems = 4
| status-cockpit = 4
| status-model = 3
| navbar = 1
}}</includeonly><noinclude>
This is the aircraft infobox subpage of the [[Pilatus PC-6 Porter]].
[[Category:Aircraft infobox documentation]]
</noinclude>

Lockheed Constellation/info

2017-06-16T16:50:33Z

Circumn: Undo. Meant to change the rating of the PC-6 instead.

<includeonly>{{infobox aircraft
| name = Lockheed 1049H Super Constellation
| hangar = fgaddon
| aircraft = Lockheed1049h
| image = Lockheed 1049H Super Constellation.png
| image2 = Lockheed 1049H Super Constellation landing.png
| alt2 = {{LangSwitch
| de = Das [[Cockpit]]
| en = The [[cockpit]]
}}
| manufacturer = Lockheed
| type = Airliner/Cargo aircraft/Historical aircraft
| config = Twin boom aircraft
| propulsion = Propeller aircraft/Four-engine aircraft
| ready = dualcontrol/checklist
| authors = Gary R. Neely/Marc Kraus/Ludovic Brenta/Richard Senior
| fdm = JSBSim
| fgname = Lockheed1049h/L1049h-engineer
| status-fdm = 4
| status-systems = 3
| status-cockpit = 4
| status-model = 4
| liverydbid = 54
| forumtid = 4709
| navbar = 1
}}</includeonly><noinclude>
This is the aircraft infobox subpage of the [[Lockheed Constellation]].
[[Category:Aircraft infobox documentation]]

</noinclude>

Lockheed Constellation/info

2017-06-16T16:49:11Z

Circumn:

<includeonly>{{infobox aircraft
| name = Lockheed 1049H Super Constellation
| hangar = fgaddon
| aircraft = Lockheed1049h
| image = Lockheed 1049H Super Constellation.png
| image2 = Lockheed 1049H Super Constellation landing.png
| alt2 = {{LangSwitch
| de = Das [[Cockpit]]
| en = The [[cockpit]]
}}
| manufacturer = Lockheed
| type = Airliner/Cargo aircraft/Historical aircraft
| config = Twin boom aircraft
| propulsion = Propeller aircraft/Four-engine aircraft
| ready = dualcontrol/checklist
| authors = Gary R. Neely/Marc Kraus/Ludovic Brenta/Richard Senior
| fdm = JSBSim
| fgname = Lockheed1049h/L1049h-engineer
| status-fdm = 3
| status-systems = 4
| status-cockpit = 4
| status-model = 3
| liverydbid = 54
| forumtid = 4709
| navbar = 1
}}</includeonly><noinclude>
This is the aircraft infobox subpage of the [[Lockheed Constellation]].
[[Category:Aircraft infobox documentation]]

</noinclude>

Lockheed Constellation

2017-06-12T17:53:45Z

Circumn: /* Current features */

''This includes the following models: Lockheed 1049H Super Constellation''
{{:{{PAGENAME}}/info}}

[[Image:Checklistready.png|link=Aircraft Checklists]]

The '''Lockheed Constellation''', affectionately known as the “Connie”, was a four-engine propeller-driven airliner built by [[Category:Lockheed|Lockheed]] between 1943 and 1958 at its Burbank, California, USA, facility. A total of 856 aircraft were produced in four models, all distinguished by a distinctive triple-tail design and graceful, dolphin-shaped fuselage. It was used as both a civilian airliner and U.S. military air transport plane, seeing service in the Berlin Airlift and as the presidential aircraft for U.S. President Dwight D. Eisenhower.

The Lockheed L-1049 Super Constellation was a member of the Lockheed Constellation aircraft line, and was Lockheed's response to the successful [[Douglas DC-6|Douglas DC-6]] airliner, first flying in 1950. The L-1049H variant flew on November 20, 1956. Called "Super H" and "Husky", the L-1049H was a convertible passenger/freight aircraft, mating a C-121C-based fuselage with L-1049G components. The cargo hold had a volume of 565 ft³ (16 m³) when including the lower hold. The aircraft could carry up to 120 people with seats, luggage lockers and toilets all available along with the option of decorating the walls of the aircraft. When not in use, the luggage lockers and seats could be stowed in the lower hold.

The aircraft entered service with QANTAS a month later. Some L-1049G and H aircraft in later production were fitted with the TC-18EA series engines used on the L-1649 Starliner. A final variant was planned in 1957, known as the L-1049J. Powered by four R-3350-988-TC-18EA-6 engines, the L-1049J was based on the L-1049H with the wings of the R7V-2 Constellation and an extra fuselage-mounted fuel tank.

==Compatibility==

FlightGear 2.x: Loads and runs<br />
FlightGear 3.0: Loads and runs<br />
FlightGear 2016.4:Loads and runs<br />

== External links ==
* {{wikipedia|Lockheed Constellation}}

== Current features ==

As of version 3.0 (May 2017), advanced features of the Lockheed1049h include:

* [http://liveries.flightgear.org/aircraft.php?id=54&display=2 Livery support].
* Realistic and tuned FDM.
* Realistic and tuned, 1956-vintage autopilot (but the generic autopilot dialog also works, for beginners).
* Realistic and complex fuel system with several presets, from no fuel management for beginners to full manual fuel management.
* Detailed checklists.
* Engine fire.
* Engine fire extinguishing.
* Fuel jettison.
* Realistic Fuel and Payload system.
* Dynamic load factor and speed limits (they depend on flight conditions).
* Windshield wipers.
* Autostart via the checklists.
* Dual control with a pilot and a flight engineer, using an all-new multiplayer protocol (not compatible with earlier versions of the Lockheed1049h).

== Future (planned) features ==

* Realistic electrical system to power lights, engine starter, instruments, autopilot, auxiliary fuel pumps.
* Realistic hydraulic system to power control surfaces, main fuel pumps, brakes.
* Pressurization?
* Radar?

{{Lockheed}}

[[de:Lockheed Constellation]]

[[Category:Airliners]]
[[Category:Propeller aircraft]]
[[Category:Aircraft with Checklists]]

Lockheed Constellation/info

2017-06-12T17:52:23Z

Circumn: Add the engineer aircraft name

Lockheed Constellation/info

2017-06-12T17:50:40Z

Circumn: Dual control

<includeonly>{{infobox aircraft
| name = Lockheed 1049H Super Constellation
| hangar = fgaddon
| aircraft = Lockheed1049h
| image = Lockheed 1049H Super Constellation.png
| image2 = Lockheed 1049H Super Constellation landing.png
| alt2 = {{LangSwitch
| de = Das [[Cockpit]]
| en = The [[cockpit]]
}}
| manufacturer = Lockheed
| type = Airliner/Cargo aircraft/Historical aircraft
| config = Twin boom aircraft
| propulsion = Propeller aircraft/Four-engine aircraft
| ready = checklist/dualcontrol
| authors = Gary R. Neely/Marc Kraus/Ludovic Brenta/Richard Senior
| fdm = JSBSim
| fgname = Lockheed1049h
| status-fdm = 4
| status-systems = 3
| status-cockpit = 4
| status-model = 4
| liverydbid = 54
| forumtid = 4709
| navbar = 1
}}</includeonly><noinclude>
This is the aircraft infobox subpage of the [[Lockheed Constellation]].
[[Category:Aircraft infobox documentation]]

</noinclude>

Changelog 2017.2

2017-06-12T17:48:33Z

Circumn: /* Highlighted new and improved aircraft */ Lockheed1049h dual control with a flight engineer

{{changelogs|prev=2017.1|next=2017.3}}
{{-}}
{{draft|changelog|This changelog is currently being written for the FlightGear v2017.2 release. Feel free to help! If you are aware of any FlightGear related changes, please add them to the changelog.}}



== Major enhancements in this release ==
=== Core ===

=== Aircraft Modeling ===
* Added support to allow a geometry object (a line segment with two vertices) that is used to define both the centre and the axis for an animation. This will work with rotate, translate and the knob animations.

=== YASim ===
* The YASim code is under heavy development and will continue to get improvements in the future.

=== Multiplayer ===
* Optional new protocol that improves efficiency (35% reduction in bandwidth). Older clients (pre 2017.1) will only see basic aircraft motion when new protocol selected.
* New debugging options, local loopback, transmitted packet size, packet dump
* Extra generic properties, float[20..39], short[0..79], bool[0..90]
* Connect dialog will use configured ports rather than always using 5000,5000

=== Atmospheric Light Scattering ===

* G-force effect with greyout and tunnel vision
* HUD effect simulating more realistically the appearance of light projected onto glass
* Improved Aurora shader

=== Environment Rendering ===
* Added a normalmap to the Earthview clouds and landscape
* Added a lightmap to Earthview at night, including thunderstorm visuals
* Earthview atmosphere Rayleigh scattering added

=== Performance ===

=== Misc/Uncategorized ===
* A '''new, modern splash screen''' together with start-up tips.
* The --launcher's design '''is reworked'''.

=== Usability ===
* '''Improved aircraft discovery''': Search tags and large screenshots in the launcher.

=== Internationalization ===

=== Scenery ===
* Enhancements for the integration of [[Osm2city.py|osm2city]] generated sceneries:
** Textures and effects are now part of [[FGData]] and therefore do not need to be distributed separately.
** Traffic shader visualising cars on streets based on street type, time of day etc.
** Shader for lit streets
* Custom sceneries can add and correct fixes and navaids.
** This is the logical extension to what was already possible for airports using the NavData/apt folder inside a scenery folder.
** FlightGear now looks for *.dat and *.dat.gz files in NavData/fix and NavData/nav in addition to NavData/apt (optional subfolders of each scenery folder).
** See [https://sourceforge.net/p/flightgear/mailman/message/35716882/ this message] for details.

=== Canvas System ===
* additional APIs to update text elements more performance-friendly

=== Nasal Scripting ===
* <code>get_cart_ground_intersection()</code> and <code>aircraftToCart()</code> {{flightgear commit|b80b9a|t=added}}.

=== Documentation ===

=== Highlighted new and improved aircraft ===
* [[Space Shuttle]] milestone 8 with complete 3d cockpit
* [[Saab 35 Draken|Saab Draken]]
* [[Dassault Mirage 2000-5|Mirage 2000]]
* [[Saab 37 Viggen|Saab Viggen]]
* [[Ercoupe 415-C|Ercoupe]] with completely re-worked 3d model and effects
* [[Lockheed Constellation]] has a new dual-control protocol for a pilot and a flight engineer.
* Improvements to many AI aircraft

=== Other ===
Parameter <code>--log-file</code> renamed to <code>--log-dir</code> ({{flightgear commit|dab685}}).

=== Bug fixes ===
* See [https://sourceforge.net/p/flightgear/codetickets/search/?q=status%3AFixed+AND+created_date%3A%5B2017-02-22T18%3A48%3A48Z+TO+*%5D our bugtracker] for a list, albeit incomplete, of the bugs fixed in this release.

[[Category:FlightGear changelogs]]
[[Category:New Versioning Scheme]]

Lockheed Constellation

2017-06-12T17:46:26Z

Circumn: Dual control with flight engineer is implemented

''This includes the following models: Lockheed 1049H Super Constellation''
{{:{{PAGENAME}}/info}}

[[Image:Checklistready.png|link=Aircraft Checklists]]

The '''Lockheed Constellation''', affectionately known as the “Connie”, was a four-engine propeller-driven airliner built by [[Category:Lockheed|Lockheed]] between 1943 and 1958 at its Burbank, California, USA, facility. A total of 856 aircraft were produced in four models, all distinguished by a distinctive triple-tail design and graceful, dolphin-shaped fuselage. It was used as both a civilian airliner and U.S. military air transport plane, seeing service in the Berlin Airlift and as the presidential aircraft for U.S. President Dwight D. Eisenhower.

The Lockheed L-1049 Super Constellation was a member of the Lockheed Constellation aircraft line, and was Lockheed's response to the successful [[Douglas DC-6|Douglas DC-6]] airliner, first flying in 1950. The L-1049H variant flew on November 20, 1956. Called "Super H" and "Husky", the L-1049H was a convertible passenger/freight aircraft, mating a C-121C-based fuselage with L-1049G components. The cargo hold had a volume of 565 ft³ (16 m³) when including the lower hold. The aircraft could carry up to 120 people with seats, luggage lockers and toilets all available along with the option of decorating the walls of the aircraft. When not in use, the luggage lockers and seats could be stowed in the lower hold.

The aircraft entered service with QANTAS a month later. Some L-1049G and H aircraft in later production were fitted with the TC-18EA series engines used on the L-1649 Starliner. A final variant was planned in 1957, known as the L-1049J. Powered by four R-3350-988-TC-18EA-6 engines, the L-1049J was based on the L-1049H with the wings of the R7V-2 Constellation and an extra fuselage-mounted fuel tank.

==Compatibility==

FlightGear 2.x: Loads and runs<br />
FlightGear 3.0: Loads and runs<br />
FlightGear 2016.4:Loads and runs<br />

== External links ==
* {{wikipedia|Lockheed Constellation}}

== Current features ==

As of version 3.0 (May 2017), advanced features of the Lockheed1049h include:

* [http://liveries.flightgear.org/aircraft.php?id=54&display=2 Livery support].
* Realistic and tuned FDM.
* Realistic and tuned, 1956-vintage autopilot (but the generic autopilot dialog also works, for beginners).
* Realistic and complex fuel system with several presets, from no fuel management for beginners to full manual fuel management.
* Detailed checklists.
* Engine fire.
* Engine fire extinguishing.
* Fuel jettison.
* Realistic Fuel and Payload system.
* Dynamic load factor and speed limits (they depend on flight conditions).
* Windshield wipers.
* Autostart via the checklists.
* Dual control with a pilot and a flight engineer, using an all-new multiplayer protocol. This multiplayer protocol is
not compatible with earlier versions of the Lockheed1049h.

== Future (planned) features ==

* Realistic electrical system to power lights, engine starter, instruments, autopilot, auxiliary fuel pumps.
* Realistic hydraulic system to power control surfaces, main fuel pumps, brakes.
* Pressurization?
* Radar?

{{Lockheed}}

[[de:Lockheed Constellation]]

[[Category:Airliners]]
[[Category:Propeller aircraft]]
[[Category:Aircraft with Checklists]]

Landmark Wish List

2017-06-07T12:52:17Z

Circumn: /* Europe */ Three new massive landmarks requested on the canals of Belgium

This page provides a list of landmarks which are not currently in the FlightGear scenery that the community consider important and would like to see modeled.

If you are a FlightGear modeler and are looking for something to model, please consider something on this list.

Feel free to add to this list.

__TOC__

{{note|
If you are modelling a landmark, please change the "Completed" column from {{tl|no}} to <nowiki>{{</nowiki>[[:Template:n/a|n/a|Claimed]]<nowiki>}}</nowiki>, and when done change to {{tl|yes}}.}}

== Africa ==
{| class="wikitable sortable"
! Landmark !! City !! Country !! Completed
|-
| {{wikipedia|Basilica of Our Lady of Peace of Yamoussoukro}} || Yamoussoukro || Côte d'Ivoire || {{no}}
|-
| Pyramids || Cairo || Egypt || {{yes}}
|-
| Victoria Falls || Victoria Falls || Zimbabwe || {{no}}
|}

== America ==
{| class="wikitable sortable"
! Landmark !! City !! Country !! Completed
|-
| Adler Planetarium || Chicago || USA || {{no}}
|-
| Bank of America Tower || New York || USA || {{yes}}
|-
| Brooklyn Bridge || New York || USA || {{yes}}
|-
| Christ the Redeemer || Rio de Janeiro || Brazil || {{yes}}
|-
| Chrysler Building || New York || USA || {{yes}}
|-
| Empire State Building || New York || USA || {{yes}}
|-
| {{wikipedia|Hoover Dam}} || Boulder|| USA || {{no}}
|-
| {{wikipedia|Machu Picchu}} || Aguas Calientes || Peru || {{no}}
|-
| Marina City || Chicago || USA || {{no}}
|-
| McCormick Place || Chicago || USA || {{no}}
|-
| Millenium Park || Chicago || USA || {{no}}
|-
| Milwaukee Art Museum || Milwaukee || USA || {{no}}
|-
| National Congress || Brasilia || Brazil || {{yes}}
|-
| Navy Pier || Chicago || USA || {{no}}
|-
| {{wikipedia|Nazca Lines}} || Estudiantes || Peru || {{no}}
|-
| Oglivie Transportation Center || Chicago || USA || {{no}}
|-
| {{wikipedia|Panama canal}} and some boats pls|| Panama city - Colòn || Panama || {{yes}}
|-
| Shedd Aquarium || Chicago || USA || {{no}}
|-
| {{wikipedia|Skunk Works|Skunkworks aircraft] hidden in the mountain of KXTA || Area 51 || USA || {{no}}
|-
| Smurfit-Stone Building || Chicago || USA || {{no}}
|-
| Soldier Field || Chicago || USA || {{no}}
|-
| Space Needle || Seattle || USA || {{yes}}
|-
| Union Station || Chicago || USA || {{no}}
|-
| United Center || Chicago || USA || {{no}}
|-
| United Nations Headquarters || New York || USA || {{yes}}
|-
| U.S. Cellular Field || Chicago || USA || {{no}}
|-
| Verizon Center || Washington, D.C. || USA || {{no}}
|-
| {{wikipedia|Windsor Atlantica Hotel}} || Rio de Janeiro || Brazil || {{n/a|Claimed}}
|-
| White House || Washington, D.C. || USA || {{no}}
|-
| Wrigley Field || Chicago || USA || {{no}}
|}

== Asia ==
{| class="wikitable sortable"
! Landmark !! City !! Country !! Completed
|-
| Akashi Kaikyo bridge || Kobe || Japan || {{yes}}
|-
| Azadi Square || Tehran || Iran || {{no}}
|-
| Bank of China Tower || Hong Kong || China || {{yes}}
|-
| Bitexco Financial Tower || Ho Chi Minh City || Vietnam || {{yes}}
|-
| Burj al Arab || Dubai || UAE || {{yes}}
|-
| Burj Khalifa || Dubai || UAE || {{yes}}
|-
| CCTV Tower || Beijing || China || {{yes}}
|-
| {{wikipedia|Kai Tak Airport|"Checkerboard Hill" (VHHX approach)}} || Hong Kong || China || {{no|No, see [[Talk:Landmark_Wish_List#VHHX request| talk page]]}}
|-
| Great Wall of China || Huairou, Peking / Jiuduhezhen, Huairou, Peking || China || {{no}}
|-
| [[Talk:Landmark_Wish_List#Singapore| Marina Bay Sands]] || Singapore ||Singapore || {{yes}}
|-
| Milad Tower || Tehran || Iran || {{no}}
|-
| [[Talk:Landmark_Wish_List#Singapore| One George Street]] || Singapore ||Singapore || {{no}}
|-
| [[Talk:Landmark_Wish_List#Singapore| One Raffles Place]] || Singapore ||Singapore || {{yes}}
|-
| [[Talk:Landmark_Wish_List#Singapore| One Shenton Way]] || Singapore ||Singapore || {{no}}
|-
| Petronas Towers || Kuala Lumpur || Malaysia || {{yes}}
|-
| [[Talk:Landmark_Wish_List#Singapore| The Pinnacle@Duxton]] || Singapore ||Singapore || {{no}}
|-
| Ryugyong Hotel || Pyongyang || North Korea || {{yes}}
|-
| Sigiriya || Matale District || Sri Lanka || {{no}}
|-
| Taj Mahal || Agra || India || {{yes}}
|}

== Europe ==
{| class="wikitable sortable"
! Landmark !! City !! Country !! Completed
|-
| Big Ben || London || UK || {{yes}}
|-
| St. Peter's Basilica & square || Vatican City || Vatican City || {{no}}
|-
| Colosseum || Rome || Italy || {{yes}}
|-
| Lapan || Oldenburg, Niedersachsen || Germany || {{no}}
|-
| North Pole (flag and light) || North Pole || World || {{no}}
|-
| Oeresund Bridge || Copenhagen-Malmo || Scandinavia || {{yes}}
|-
| {{wikipedia|Oslo Plaza}} || Oslo || Norway || {{n/a|Claimed}}
|-
| Porta Westfalica/Hermans-Denkmal || Bückeburg (ETHB), Minden || Germany || {{no}}
|-
| Schloss || Oldenburg || Germany || {{no}}
|-
| Schloss || Neuschwanstein || Germany || {{yes}}
|-
| Stade de France || Saint-Denis || France || {{no}}
|-
| Westminster Abbey || London || UK || {{yes}}
|-
| {{wikipedia|Stuttgart TV Tower}} || Stuttgart, Baden-Württemberg || Germany || {{yes}}
|-
| {{wikipedia|Strépy-Thieu boat lift}} || La Louviere || Belgium || {{no}}
|-
| {{wikipedia|Boat Lifts on the Canal du Centre}} || La Louviere || Belgium || {{no}}
|-
| {{wikipedia|Ronquières inclined plane}} || Braine-le-Comte || Belgium || {{no}}
|}

== Australia and Oceania ==
{| class="wikitable sortable"
! Landmark !! City !! Country !! Completed
|-
| Ayers rock || Uluru || Australia || {{no}}
|-
| Sky Tower || Auckland || New Zealand || {{n/a|Claimed}}
|-
| Sydney Opera House || Sydney || Australia || {{yes}}
|}

== Related content ==
* [[FlightGear Scenery Designer]]
* [[FlightGear Scenery Database]]
* [[UK Scenery Wish List]]

== External links ==
* [http://forum.flightgear.org/viewtopic.php?f=5&t=2390 The forum topic]
* See [http://scenemodels.flightgear.org/ FGFS Scenery Object Database], for more on models for [[Scenery]]

[[Category:Scenery]]
[[Category:Community]]
[[Category:Contribution requests]]

FGAddon

2016-06-27T20:51:08Z

Circumn: /* Deficiencies of git-svn */ Mandate svn+ssh for git-svn clones, explain why.

[[File:FGAddon logo.png|270px|right]]

The official '''FGAddon''' aircraft hangar is a version control repository, hosted on [[FlightGear|FlightGear's]] [https://sourceforge.net/projects/flightgear/ SourceForge infrastructure], and used for the day-to-day development of FlightGear aircraft. FGAddon is an {{wikipedia|Apache Subversion|noicon=1}} version control repository. These are aircraft that are not part of the base package (the aircraft that are included in the base package — the [[Cessna 172P]] and the [[UFO]] — are kept in the [http://sourceforge.net/p/flightgear/fgdata FGData] repository), but are tagged with each stable release for the [http://www.flightgear.org/download/ FlightGear download pages].

The FGAddon aircraft development repository should be considered unstable. When using a stable FlightGear release, it is best to obtain aircraft with a matching version number from the [http://www.flightgear.org/download/ FlightGear download pages]. However, as stable releases from FlightGear version 3.4 onwards are tagged and present within the FGAddon repository, the Subversion tools can be a convenient way to obtain individual aircraft or the entire official hangar of approximately 500 aircraft. Also, if using the [[FlightGear build server|lastest nightly releases]] or a [[Building FlightGear|self-compiled version of FlightGear]] from FlightGear's [http://sourceforge.net/p/flightgear/_list/git Git version control repositories], using FGAddon allows the aircraft to be updated to the latest development versions.

== History ==
{{WIP|The accuracy of the facts in this section are in the process of being verified.}}
[[File:Image103.gif|thumb|Original Win95 icon]]
The FlightGear project was conceived on April 8, 1996 by David Murr who proposed a new flight simulator to be developed by volunteers<ref>David Murr (Apr 9, 1996). FlightGear proposal 1.0: [https://groups.google.com/forum/#!msg/rec.aviation.simulators/ny8HFBE5_T8/OdtIiGNGJc8J "A PROPOSAL FOR A NEW FLIGHT SIMULATOR - home built!@"]. Published on the rec.aviation.simulators newsgroup.</ref><ref>David Murr (1996). FlightGear proposal 2.0: [http://www.flightgear.org/proposal-2.0 FLIGHT GEAR "This truly is as real as it gets!" - a proposal for a new flight simulator - REVISION 2.0].</ref><ref>David Murr (Oct 29, 1996). FlightGear proposal 3.0: [http://www.flightgear.org/proposal-3.0 FLIGHT GEAR FLIGHT SIMULATOR, revision 3.0 - Wednesday, 10.30.96, "The future of flight simulation is here"]. Published on the [http://ftp.igh.cnrs.fr/pub/flightgear/www/old-stuff/flight-gear.9610 flight-gear@infoplane.com mailing list].</ref><ref>David Murr (Sep 11, 1998). FlightGear proposal 3.0.1: [http://www.flightgear.org/proposal-3.0.1 FLIGHT GEAR FLIGHT SIMULATOR, revision 3.0.1 - Friday, Sep.11.98, "The future of flight simulation is here"].</ref>. Part of the initial goals were to develop 2D and 3D graphics routines for the simulator. However this was a huge task that came to an unfinished halt at the start of 1997 as the main developer, Eric Korpela, was finishing his thesis. Therefore starting on May 16, 1997, Curtis Olson relaunched development with a new project based on the OpenGL libraries, allowing a functional flight simulator to be put together in a short period of time<ref>Curtis Olson (Sep 28, 2015). [http://forum.flightgear.org/viewtopic.php?f=42&t=27558&p=259048#p259021 Re: A PROPOSAL FOR A NEW FLIGHT SIMULATOR - home built!@]. Published on the FlightGear forum.</ref>. The first commits were to the original [[FlightGear CVS|flightgear and simgear CVS version control repositories]].

As the project grew, so did the size, quantity, and quality of the FlightGear assets. These assets were not organised and were scattered across different parts of the internet. Therefore it was decided that much of this FlightGear content would be assembled and stored together in a new centralised CVS repository called fgdata, which was created on October 22, 2000. To allow for the legal redistribution of these assets as part of the FlightGear distribution, a GPLv2 only policy was adopted.

In May 2010, development was interrupted by the infamous ''"coffee incident"'' which resulted in the loss of Curtis' home server hosting all of the FlightGear repositories<ref>James Turner (May 20, 2010). [http://thread.gmane.org/gmane.games.flightgear.devel/60340/focus=60341 <nowiki>[Flightgear-devel]</nowiki> Re: Flightgear git repositories (was Re: GIT or CVS - Confusion)] Published on the flightgear-devel mailing list.</ref>. These events resulted in a [[FlightGear CVS|mass migration of all the CVS repositories to Git repositories]]. Due to bandwidth issues, it was decided that the new repositories would be hosted on the Gitorious open source infrastructure.

With time as the project grew, the size and scope of the fgdata repository mushroomed, mainly due to the growing number of aircraft stored in [[$FG_ROOT]]/Aircraft, so that a split was inevitable. A first splitting attempt was organised by Gijs de Rooy and announced on October 18, 2011<ref>Cedric Sodhi (Oct 18, 2011) [http://thread.gmane.org/gmane.games.flightgear.devel/66846 <nowiki>[Flightgear-devel]</nowiki> FGData Split Completed - a.k.a Life after the Split] Published on the flightgear-devel mailing list.</ref>. Each aircraft was placed in its own Git repository and all aircraft linked back to fgdata using a Git submodule approach. However this attempt failed and was abandoned. From this date until the end of 2014, the design of the fgdata split was discussed on the development mailing list and summarised in the [[FlightGear Git: splitting fgdata]] wiki article. In the planning stages, the repositories were known as fgdata-old splitting into [[FGData]] (a.k.a. fgdata-new) and FGAddon (a.k.a. flightgear-aircraft and fgaircraft). After half a decade of planning, it was decided that the best solution for FlightGear aircraft development would be a single centralized Subversion repository. This would facilitate community management and maintenance of the aircraft while at the same time providing modularity and smaller downloads and smaller local repository sizes.

In late 2014, Gitorious, the provider of the open source infrastructure for the FlightGear source code and data repositories announced that it would shut its services down by May 2015 due to its acquisition by GitLab. This catalysed the split of fgdata-old and a switch to the SourceForge open source infrastructure for the hosting of the VC repositories. Other parts of the FlightGear infrastructure were already hosted by SourceForge, making the move a natural one. Sealing the deal, SourceForge agreed in writing to host the huge FlightGear aircraft collection, the size of which is unrivaled in open source circles. Today, the FGAddon SVN repository, together with most of the FlightGear project infrastructure, is hosted on SourceForge.

In August 2015, a new FlightGear policy document was written to codify the unwritten standards of the project<ref>[http://www.flightgear.org/flightgear-policy-document/ FlightGear Policy Document and Roadmap], draft document.</ref>. With this document, the licensing policy for the FlightGear aircraft has been updated from being GPLv2-only to now being a GPLv2+ or GPL-compatible<ref>[http://www.gnu.org/licenses/license-list.en.html GNU license compatibility list].</ref> stance. However, to combat licence proliferation complications for the integrity and good of the FlightGear project, it is strongly recommended that original content be GPLv2+ licensed.



== Obtaining aircraft ==

{{tip|If you are interested in obtaining aircraft for stable FlightGear releases and you are unaware of what version control is, you should visit the [[FlightGear_hangars|FlightGear hangars]] for downloading aircraft.}}
{{caution|If the FlightGear and FGAddon aircraft versions do not match, strange bugs should be expected and the version-mismatch combination will not be supported by the FlightGear community.}}

With access to the Subversion (SVN) tools, the FGAddon version control repository can be a convenient way for obtaining aircraft for using within a specific FlightGear version directly from the official source. When using the [[FlightGear Build Server|nightly builds]] or a [[Building FlightGear|version controlled copy of FlightGear]], the most up to date in-development versions of the aircraft should be used so the versions match. The following describes how to use the official repository to obtain aircraft from the perspective of a FlightGear user.

=== Preparation ===
To use the FGAddon repository, the Subversion tools need to be installed:
* '''MS Windows''': Install one of the [https://subversion.apache.org/packages.html#windows many Subversion clients]. For example [https://sliksvn.com/download/ SlikSVN] is one of the best command line versions and the best for aircraft development, and [http://tortoisesvn.net/ TortoiseSVN] provides a user friendly graphical user interface (GUI) by integrating into Windows Explorer.
* '''Mac OS X''': Install the [https://subversion.apache.org/packages.html#osx official Subversion client].
* '''GNU/Linux''': Install the Subversion client via the package manager. This will usually be in a package called <code>subversion-*.{rpm,deb}</code>.

=== FGAddon directory layout ===
To know how to use the FGAddon repository, an understanding of the repository directory layout is essential.
* <code>/trunk</code>: This base directory is where the in-development versions of the aircraft are located.
* <code>/branches/release-x.y.z/</code>: These directories correspond to the specific stable FlightGear releases.

The [https://sourceforge.net/p/flightgear/fgaddon/HEAD/tree/ web interface for the FGAddon repository] allows all of the aircraft to be browsed.

=== Download ===
[[File:V22Osprey.jpg|thumb|200px|Aircraft to be downloaded]]
Firstly, choose an aircraft to download. The [[Bell Boeing V-22 Osprey]] will be used in this example.

==== Command line ====

To download the aircraft for FlightGear 3.4, simply type:
{{#tag:syntaxhighlight|
{{fgaddon co|branch=branches/release-3.4.0|path=Aircraft/V22-Osprey|post=}}
| lang = "sh"
}}

To obtain the in-development version, type:
{{#tag:syntaxhighlight|
{{fgaddon co|path=Aircraft/V22-Osprey|post=}}
| lang = "sh"
}}

If all of the ~500 aircraft from the repository are desired - beware that this will be a huge download of over 6 GB - use the following command:
{{#tag:syntaxhighlight|
{{fgaddon co|post=flightgear-fgaddon}}
| lang = "sh"
}}

When using a stable FlightGear release, for example FlightGear 2016.1, to obtain all of the FGAddon aircraft to match the installed FlightGear version, use:
{{#tag:syntaxhighlight|
{{fgaddon co|branch=branches/release-2016.1|post=flightgear-fgaddon}}
| lang = "sh"
}}

==== GUI clients and TortoiseSVN ====

When using one of the Subversion GUIs (graphical user interfaces), simply copy one of the above <code>https://</code> URLs and use that in the GUI (each GUI is different, so see the relevant documentation for help). For the unique TortoiseSVN tool, simply:

* In Windows Explorer, create a new empty folder for the aircraft (or aircraft collection).
* In the new folder, right click and select <code>SVN Checkout...</code>.
* Copy and paste the URL, for example {{fgaddon source|path=Aircraft/V22-Osprey|type=svn|full=1}}, leave all other settings as they are, and import by clicking on <code>OK</code>.

For more details, see the [http://tortoisesvn.net/support.html TortoiseSVN documentation]. Note that there is an option to install the command line tools when installing TortoiseSVN.

=== Flying ===

To use the newly downloaded aircraft, please see the [[Howto:Install aircraft]] article, skipping the instructions for downloading and unzipping the aircraft.

=== Updates ===
With a checked out copy of the <code>/trunk</code> in-development version, the aircraft can be updated to the latest version using the command:
<syntaxhighlight lang="bash">
svn up
</syntaxhighlight>

== Aircraft development ==

{{tip|The FlightGear community encourages aircraft development directly within FGAddon.}}

=== Contact the original aircraft authors ===

The first step for developing and advancing the aircraft of the official FlightGear hangar, or from one of the [[Flightgear_hangars#Aircraft_hangars|private hangars]] for that matter, is to make contact with the original aircraft author(s). Their names can be found within the <code>*-set.xml</code> file, within the <code><authors></code> XML tag. Often the contact email address will be listed in a README file or some other text file in the base aircraft directory. If not, contact can sometimes be established via the [https://lists.sourceforge.net/lists/listinfo/flightgear-devel FlightGear development mailing list]. Contacting the original authors is important to see if the aircraft is currently being actively developed, and if you can join in as part of the development team.

=== SourceForge account ===

To work on the official aircraft collection, a [https://sourceforge.net/user/registration/ SourceForge account] should first be set up. This will allow to either directly commit to the FGAddon repository, if commit access has been been granted, or to work in as part of a SourceForge development team. The registration process is lightning quick and the SourceForge developer infrastructure and developer services will be accessible in under a minute.

=== Commit access ===

Before obtaining commit access, an all-out effort to contact the original author(s) should be made to determine if the aircraft is actively being developed. If this is unsuccessful, sign up for the [https://lists.sourceforge.net/lists/listinfo/flightgear-devel FlightGear development mailing list] and ask for help there. If the aircraft has a current maintainer, you will be directed as to how to proceed with development. Otherwise ask if someone could volunteer to mentor you in the process of becoming an aircraft developer with full commit access.

To obtain commit access, you will first need:
# To demonstrate your capabilities and development skills.
# To show that you understand the [http://article.gmane.org/gmane.games.flightgear.devel/78713 FlightGear policy document]. 
# To show an understanding of the GPL licensing issues, and that you can be trusted not to use copyrighted, non-GPL material.
# To earn the trust of the FlightGear community.

These easy to jump over hurdles are simply designed to protect against repository corruption or pollution of the repository with illegal content.

To have your changes committed into the FGAddon repository, you should discuss and coordinate with the original aircraft author, or your mentor, for the best way to proceed. Depending on the [[#Development_scenarios|development scenario]], this maybe by merge request, file transfer, the primitive patch system, or any other convenient way. Once you believe you have proven your capabilities and you are knowledgeable about GPL licensing issues, you should write a mail to the development mailing list asking if you can be granted commit access, providing your SourceForge username.

=== FGAddon commitlog mailing list ===

To follow all changes which occur in the FGAddon repository, subscribe to the dedicated [https://lists.sourceforge.net/lists/listinfo/flightgear-fgaddon-commitlogs Flightgear FGAddon commitlogs mailing list]. One email is sent per commit, as the commit is made.

== Version control tools ==

To access FGAddon and use it for aircraft development, the Subversion or SVN version control tools are needed. Alternatively git-svn provides an interface for those who prefer the git version control tools.

=== Subversion ===

==== Set up ====
The FGAddon aircraft hangar is stored in a remote Subversion repository located on the SourceForge infrastructure, and therefore it is simplest to use the SVN tools for aircraft development and will cause the least problems. See the [[#Preparation|Subversion installation section]] for setting up the tool chain.

==== Repository checkout ====
The first step is to 'checkout' a copy of either the repository trunk or one of the aircraft in the trunk:
<syntaxhighlight lang="bash">
svn co <url> <dir>
</syntaxhighlight>

For the relevant URL to use, you must chose one of the [[#Development_scenarios|development scenarios]] and find the URL in that section. This command will create a local subversion repository copy in the given <code><dir></code> directory. Note that this will only contain the part of the FGAddon repository specified in the URL. This means that Subversion allows you to checkout either a single file all the way to the entire remote repository.

==== Information and history ====
At any point to see information about the local repository, type:
<syntaxhighlight lang="bash">
svn info
</syntaxhighlight>

To see the history of the checked out copy of the repository, type one of:
<syntaxhighlight lang="bash">
svn log
svn log | less
svn log -v | less
</syntaxhighlight>

==== Daily usage ====
The main Subversion command you will be using is:
<syntaxhighlight lang="bash">
svn add <path>
</syntaxhighlight>

This will register the file or directory <code><path></code> within the local repository to allow it to later be 'committed' and sent to the remote repository. To move or rename a file or directory, use:
<syntaxhighlight lang="bash">
svn mv <path1> <path2>
</syntaxhighlight>

This should be used rather than normal file moving/renaming so that the change is tracked in the local repository. To remove a file from the local repository, type:
<syntaxhighlight lang="bash">
svn rm <path>
</syntaxhighlight>

To see the current status of the local repository, type:
<syntaxhighlight lang="bash">
svn st
</syntaxhighlight>

==== Committing changes ====
All of the above operations only occur on the local repository copy - the remote FGAddon repository at SourceForge will know nothing of these changes. To send all your changes to FGAddon, you need to commit the changes:
<syntaxhighlight lang="bash">
svn ci
</syntaxhighlight>

This will open up an editor to allow you to write an informative commit log message. When committing, it is best to make small modular commits so that each commit corresponds to a single purpose. Note that you can only commit to FGAddon if you have [[#Commit access|commit access]].

==== Branching ====
The concept of Subversion branching is currently only used in the FlightGear project for tagging the stable releases. However if you are curious about branching, see the [http://svnbook.red-bean.com/en/1.7/svn.branchmerge.html Branching and Merging chapter of the Subversion manual], and the [https://www.orcaware.com/svn/wiki/Svnmerge.py svnmerge.py script] which can greatly simplify the process.

=== Git-svn ===

The git-svn tool is useful for those who are already familiar with using git repositories, or those who wish to have their own private aircraft development playground. Git-svn provides a bridge between the remote FGAddon Subversion repository and a local git repository. For those unfamiliar with git, the git-svn bridge together with the git repository is far more complicated to use than the native [[#Subversion|Subversion tools]]. For more information on using git, see [[Howto:Start using git]]. The following will assume that only a single aircraft will be stored in the local git repository.

==== Set up ====
The git distributed version control system needs to first be [https://git-scm.com/downloads installed].

==== Cloning a single aircraft ====
The first step is to 'clone' a copy of one of the aircraft in the remote Subversion trunk:
<syntaxhighlight lang="bash">
git svn clone <aircraft_url>
</syntaxhighlight>

For the relevant aircraft URL to use, you must chose one of the [[#Development_scenarios|development scenarios]] and find the URL in that section. The URL depends on your [[#Commit access|FGAddon commit access status]]. The clone command will create a local git repository containing solely the aircraft of interest, and initialise the git-svn bridge.

==== Information and history ====
At any point to see information about the local repository, type:
<syntaxhighlight lang="bash">
git svn info
git branch -vva
git remote -v
</syntaxhighlight>

To see the history of the checked out copy of the repository, type:
<syntaxhighlight lang="bash">
git log
</syntaxhighlight>

==== Daily usage ====
The main git command you will be using is:
<syntaxhighlight lang="bash">
git add <path>
</syntaxhighlight>

This will register the file or directory <code><path></code> within the local repository to allow it to later be 'committed' to the local git repository. To move or rename a file or directory, use:
<syntaxhighlight lang="bash">
git mv <path1> <path2>
</syntaxhighlight>

However note that git history is not as robust as svn history. See the [[#Moving_or_renaming_files|git-svn file moving/renaming deficiency section]] for how to better perform this operation. To remove a file from the local repository, type:
<syntaxhighlight lang="bash">
git rm <path>
</syntaxhighlight>

To see the current status of the local repository, type:
<syntaxhighlight lang="bash">
git status
</syntaxhighlight>

==== Committing changes ====
As git is a distributed version control system, changes are committed to the local git repository.
<syntaxhighlight lang="bash">
git commit
</syntaxhighlight>

This will open up an editor to allow you to write an informative commit log message. The commit is local and will not be sent to FGAddon.

==== Dedicated FGAddon branch ====
In the examples above, only a single branch was assumed in the repository. If interaction with a remote git repository or branching within the local git repository is desired, then a different strategy is required. The reason being that the branch that synchronises with FGAddon must [https://git-scm.com/book/en/v1/Git-and-Other-Systems-Git-and-Subversion#git-svn preserve a linear history]. This means only cherry-picking of the desired changes into that branch is allowed.

In this example, two branches will be set up in the local git repository:
* <code>fgaddon</code>: This branch will be dedicated for FGAddon synchronisation and will preserve a linear history.
* <code>master</code>: A master branch for aircraft development, allowing for mergers and other non-linear history operations.

Assuming a [[#Cloning_a_single_aircraft|newly cloned repository]], create the <code>fgaddon</code> branch with:
<syntaxhighlight lang="bash">
git branch fgaddon
</syntaxhighlight>

And switch to that branch:
<syntaxhighlight lang="bash">
git checkout fgaddon
</syntaxhighlight>

The FGAddon synchronisation can then be performed on this branch. To pull in the developments from the master branch, use cherry-picking to apply a sequentially ordered list of commit hashes:
<syntaxhighlight lang="bash">
git cherry-pick <commit hash 1>
git cherry-pick <commit hash 2>
git cherry-pick <commit hash 3>
...
</syntaxhighlight>

To see the list of commits to be sent to FGAddon prior to dcommitting, type:
<syntaxhighlight lang="bash">
git log git-svn..HEAD
</syntaxhighlight>

And to see the changes as a single diff:
<syntaxhighlight lang="bash">
git diff git-svn..HEAD
</syntaxhighlight>

==== Synchronising ====
To send the changes to the remote FGAddon repository, firstly change to the dedicated <code>fgaddon</code> branch:
<syntaxhighlight lang="bash">
git checkout fgaddon
</syntaxhighlight>

Make sure the local git-svn repository is up to date with all changes that have occurred in FGAddon:
<syntaxhighlight lang="bash">
git svn rebase
</syntaxhighlight>

Then push or dcommit the changes to FGAddon with:
<syntaxhighlight lang="bash">
git svn dcommit
</syntaxhighlight>

=== Deficiencies of git-svn ===

{{warning|Performing a <code>git-svn clone</code> of the <code>/trunk/</code> or entire repository is not recommended, as the entire repository history will be downloaded, resulting in a huge local repository, as well as putting a large strain on the FlightGear open source infrastructure.}}

There are a number of operations in which git-svn is deficient and the svn tools should be used instead. Other deficiencies do not require the use of Subversion but contain gotchas.

==== Copying files between aircraft ====

{{caution|Git-svn does not maintain the file copying history normally present in a Subversion repository.}}

The most important of these is the copying of content from other FGAddon aircraft. In this case you will need FGAddon commit access and a local svn copy of the repository. Firstly synchronise the repositories by dcommitting all changes back to FGAddon:
<syntaxhighlight lang="bash">
git svn dcommit
</syntaxhighlight>

Then in the local svn repository, copy the file:
<syntaxhighlight lang="bash">
svn cp Aircraft/<aircraft1>/<file_path1> Aircraft/<aircraft2>/<file_path2>
</syntaxhighlight>

And commit the change:
<syntaxhighlight lang="bash">
svn ci
</syntaxhighlight>

Back in the local git-svn repository, pull in the new files:
<syntaxhighlight lang="bash">
git svn rebase
</syntaxhighlight>

Using the subversion tools avoids the FGAddon repository backend from significantly increasing in size, as [http://svnbook.red-bean.com/en/1.7/svn.branchmerge.using.html#svn.branchmerge.using.create svn copies are cheap].

==== Moving or renaming files ====

{{caution|Git-svn does not always maintain the file moving or renaming history normally present in a Subversion repository.}}

This problem stems from the fact that svn history is more robust than that of git. The <code>svn mv</code> and <code>git mv</code> commands are not equivalent. The subversion command stores the move history directly in the repository whereas git does not (git instead uses heuristic methods to try to detect history, after the commit). The result of using git-svn is that often the move will not be detected and the FGAddon history will show one file or directory being deleted and another added. This also causes the repository backend to increase in size, whereas <code>svn mv</code> will not cause any significant size increase. If you wish to have a better historical record in the FGAddon repository and be considerate to the repository backend, it is recommended that you temporarily switch to the subversion tools. Firstly, synchronise the repositories:
<syntaxhighlight lang="bash">
git svn dcommit
</syntaxhighlight>

Then in the local svn repository, move or rename the file:
<syntaxhighlight lang="bash">
svn mv Aircraft/<aircraft>/<file_path1> Aircraft/<aircraft>/<file_path2>
</syntaxhighlight>

And commit the change:
<syntaxhighlight lang="bash">
svn ci
</syntaxhighlight>

Back in the local git-svn repository, pull in the changes with:
<syntaxhighlight lang="bash">
git svn rebase
</syntaxhighlight>

==== Copying files within one aircraft ====

Just as the <code>svn mv</code> command stores the move information directly within the repository, so does <code>svn cp</code> store the copy information. Therefore if you would like to duplicate a text file and modify it, using the native Subversion tools instead of git-svn for this operation allows for the file history to be permanently preserved in the FGAddon repository.

==== Subversion properties ====

{{caution|Git-svn currently only supports the <code>svn:executable</code> property, all other properties are ignored and cannot be added, changed, or removed in a git-svn clone of the aircraft.}}

Internally, Subversion identifies binary files using the <code>svn:mime-type</code> repository property. However as git-svn cannot set this property when using the <code>git add</code> command, the result is that binary files will be treated as text. Binary diffs will be seen when using <code>svn diff</code> or <code>git diff</code>, and a binary diff will be shown in the [[#FGAddon commitlog mailing list|FGAddon commitlog mailing list]] messages. As this issue is not unique to git-svn, to work around this issue please see the [[#Binary diffs|binary diffs]] section.

==== Protocols other than svn+ssh ====

<code>git svn init</code> replicates the entire history of an aircraft into a local repository; as part of this process, it constructs a git commit id for every Subversion revision. The problem is that the git commit id depends on the protocol used to read from the Subversion repository; therefore:

{{#tag:syntaxhighlight|
{{fgaddon source|cmd=git svn init|protocol=svn+ssh|login=<username>|type=svn|path=Aircraft/<aircraft>|full=1}}
| lang = "sh"
}}

and

{{#tag:syntaxhighlight|
{{fgaddon source|cmd=git svn init|protocol=https|type=svn|path=Aircraft/<aircraft>|full=1}}
| lang = "sh"
}}

will result in two different and incompatible git repositories, even though they contain the same data. The incompatibility is not immediately apparent but it will bite later. Suppose someone with read-only access to FGAddon uses the https method, then asks a FGAddon gatekeeper to commit their changes. The gatekeeper, naturally, uses svn+ssh, as this is the only protocol granting write permissions. When the gatekeeper tries to merge the contributor's https clone into their own svn+ssh clone, git will complain that the two repositories have no history in common, and flag every change as a conflict.

Therefore, if you are planning to make any changes to an aircraft, be sure to use svn+ssh even if you do not yet have commit permissions on FGAddon. svn+ssh does not require write permissions; it only requires a SourceForge user id.

== FGAddon development concepts ==

=== New aircraft ===

To add a new aircraft to the FGAddon repository, the SVN tools are required. If you encounter <code>svn:mime-type</code> property problems when adding a new aircraft, see the [[#Mime-type problems|mime-type problems section]] for how to resolve the issue. Or if you have a <code>svn:executable</code> property problem, see the [[#Executable flag|executable flag problem section]].

==== svn import ====

{{warning|The <code>svn import</code> command described herein will send all contents of the specified directory directly into FGAddon without warning and without a way to cancel the operation. Therefore special care must be taken when specifying the directory to upload into FGAddon, as well as the target FGAddon directory. See the [[#svn add|svn add]] section below for a safer way to add a new aircraft.}}

The [http://svnbook.red-bean.com/en/1.7/svn.tour.importing.html#svn.tour.importing.import svn import] command is the easiest method to use and does not require a local copy of the repository to be checked out. To start:

# Create an empty local aircraft directory.
# Copy the aircraft files into this directory.
# Carefully check all files to make sure there are no hidden or temporary files that should not be uploaded to FGAddon.

Assuming the Dead Simple Human Powered Airplane (DaSH PA or "DaSH") aircraft as an example, located in the <code>DaSH/</code> directory, on the command line run:
{{#tag:syntaxhighlight|
{{fgaddon source
| cmd = svn import DaSH/
| protocol = svn+ssh
| login = <username>
| type = svn
| path = Aircraft/
| post = -m \
| full = 1
}}
"Initial import of the DaSH human powered aircraft.\n\nFor details see the forum thread at http://forum.flightgear.org/viewtopic.php?f=4&t=24495 ."
| lang = "sh"
}}

Where <code><username></code> is the SourceForge user name. This will add all the files into FGAddon with commit log message with the summary line <code>Initial import of the DaSH human powered aircraft.</code>, followed by a blank line, and then a detailed description pointing to the original location or discussion of the aircraft. To see if the aircraft has been successfully added to the repository:
{{#tag:syntaxhighlight|
{{fgaddon source
| cmd = svn list
| protocol = svn+ssh
| login = <username>
| type = svn
| path = Aircraft/DaSH/
| full = 1
}}
| lang = "sh"
}}

Or visit the {{fgaddon source|path=Aircraft|text=FGAddon web interface}}. The aircraft can then be checked out as described in the [[#Development scenarios|Development scenarios section]].

==== svn add ====

If a local copy of the FGAddon trunk is present, then the <code>svn add</code> command can be used instead. This is far safer than the <code>svn import</code> command, as the change can be double checked before committing. In the <code>Aircraft/</code> directory of the local repository, create the <code>DaSH/</code> directory. This can either be empty or contain all files of the initial aircraft. Then on the command line, add the aircraft to the local repository:
<syntaxhighlight lang="bash">
svn add DaSH/
</syntaxhighlight>

Then double check the changes prior to committing:
<syntaxhighlight lang="bash">
svn st
</syntaxhighlight>

And send the changes to FGAddon with:
<syntaxhighlight lang="bash">
svn ci
</syntaxhighlight>

An editor, often vi<ref>[http://www.vim.org/docs.php Vim documentation]</ref>, will open and the commit message can be composed. Alternatively the commit log message can be specified on the command line with:
<syntaxhighlight lang="bash">
svn ci -m "<subject_line>\n\n<detailed_description>"
</syntaxhighlight>

=== Commit blocking by pre-commit hooks ===

Sometimes when committing to FGAddon, the commit will be blocked the following will be printed out:
<pre>
svn: E165001: Commit failed (details follow):
svn: E165001: Commit blocked by pre-commit hook (exit code 1) with output:
</pre>

This is due to the presence of two repository pre-commit hook scripts which check the quality of the commit, blocking it if a text file is set to a binary file mime-type or if the executable flag is set. These scripts are simply to protect the repository and to keep it clean.

==== Mime-type problems ====

Sometimes when attempting to commit files to FGAddon using the SVN tools, the commit will be blocked with the following message:
<pre>
Sending dash-set.xml
svn: E165001: Commit failed (details follow):
svn: E165001: Commit blocked by pre-commit hook (exit code 1) with output:

Aborting the commit, the svn:mime-type property is labelling the following text
files as binary:

dash-set.xml: svn:mime-type=application/xml

Before committing, please remove this property by typing 'svn propdel svn:mime-
type file_name' for all affected files. This will allow the text files to be
treated as text within the FGAddon repository.

To avoid the svn:mime-type property being incorrectly set by your subversion
client, the subversion configuration file at $HOME/.subversion/config or
%appdata%\roaming\subversion\config should be edited and a new entry added to
[auto-props] for each affected file type. In most cases, the problem is with
XML files being labelled as "application/xml" by a library called libmagic. To
override this, add the following to the svn config file:

*.xml = svn:mime-type=text/xml

svn: E165001: Your commit message was left in a temporary file:
svn: E165001: '/flightgear/repo_testing/svn-commit.tmp'
</pre>

Despite messages about adding or sending files, no change will have occurred in the FGAddon repository. This message is created by a repository pre-commit hook script which checks if the Subversion <code>svn:mime-type</code> property is set on a list of known text files and, if the mime-type is set to a binary format, the commit is blocked. The reason for this block is to protect the repository. Newer SVN clients rely on a 3rd party library known as libmagic which will detect the aircraft XML files as the binary mime-type of <code>application/xml</code>. The result is that the XML files are treated as binary files in the repository. This behaviour is completely undesirable, as changes cannot be followed on the [[#FGAddon commitlog mailing list|flightgear-fgaddon-commitlogs mailing list]] or in the repository history, and the size of the commits become orders of magnitude larger. Therefore this buggy behaviour has been blocked for the protection of the FlightGear project. To remove the problem, follow the instructions in the message and, using the command line tools, type:
<syntaxhighlight lang="bash">
svn propdel svn:mime-type <file_name>
</syntaxhighlight>

Repeat this for each text file listed in the error message. Then commit again, using the commit message saved in the <code>svn-commit.tmp</code> file. The message file name will be reported in the commit failure message, but check its contents first:
<syntaxhighlight lang="bash">
cat svn-commit.tmp
</syntaxhighlight>

And reperform the commit:
<syntaxhighlight lang="bash">
svn ci -F svn-commit.tmp
</syntaxhighlight>

===== Subversion config file =====

The automatic property setting of <code>svn:mime-type</code> can be controlled by modifying the Subversion <code>config</code> file. Firstly in the <code>[miscellany]</code> section, make sure that the auto-properties are turned on:
<syntaxhighlight>
enable-auto-props = yes
</syntaxhighlight>

Then in the <code>[auto-props]</code> section, add:
<syntaxhighlight>
*.ac = svn:mime-type=text/plain
*.eff = svn:mime-type=text/xml
*.frag = svn:mime-type=text/plain
*.nas = svn:mime-type=text/plain
*.osgx = svn:mime-type=text/xml
*.svg = svn:mime-type=text/svg+xml
*.txt = svn:mime-type=text/plain
*.vert = svn:mime-type=text/plain
*.xhtml = svn:mime-type=text/xml
*.xml = svn:mime-type=text/xml
*.xsl = svn:mime-type=text/xml
</syntaxhighlight>

These are all the text files that the hook script will check that the mime-type is set to a text format, though new text files will likely be added in the future. These additions can either be to the user configuration file located at <code>~/.subversion/config</code> (or <code>%USERPROFILE%\AppData\Roaming\Subversion\config</code> in Windows) or, if a user configuration file is not set, to the global configuration file at <code>/etc/subversion/config</code> (or <code>%APPDATA%\Subversion\config</code> in Windows).

==== Executable flag ====

Another blocking message when attempting to commit files to FGAddon using the SVN tools is:
<pre>
Adding dash-set.xml
Transmitting file data .svn: E165001: Commit failed (details follow):
svn: E165001: Commit blocked by pre-commit hook (exit code 1) with output:

The svn:executable property is set on the files ['dash-set.xml'], aborting the
commit.

The current policy is that no executable files are allowed in FGAddon. Before
committing, please remove this property by typing 'svn propdel svn:executable
file_name' for all affected files. Or to remove it recursively from all files
to be committed, in your aircraft directory type 'svn propdel svn:executable
-R'.

To avoid the svn:executable property being set by your subversion client, on
GNU/Linux and Mac OS X systems simply make sure that the file's execute bit is
not set before adding the file to be committed.

svn: E165001: Your commit message was left in a temporary file:
svn: E165001: '/flightgear/repo_testing/svn-commit.tmp'
</pre>

This will probably only be seen on Mac OS X and GNU/Linux systems. This message is printed by a pre-commit repository hook script that checks if the Subversion <code>svn:executable</code> property is set and, if so, the commit is blocked. This is a security measure, as no aircraft files should be executable. To remove the problem, follow the instructions in the message and, using the command line tools, type:
<syntaxhighlight lang="bash">
svn propdel svn:executable -R
</syntaxhighlight>

Then commit again, using the commit message saved in the <code>svn-commit.tmp</code> file. The message file name will be reported in the commit failure message, but check its contents first:
<syntaxhighlight lang="bash">
cat svn-commit.tmp
</syntaxhighlight>

And the reperform the commit:
<syntaxhighlight lang="bash">
svn ci -F svn-commit.tmp
</syntaxhighlight>

=== Binary diffs ===

{{warning|The incorrect setting or absence of the mime-type property on a binary file will result in a binary diff.}}

When looking at the output of <code>svn diff</code> (or <code>git diff</code> if you are using git-svn) as well as when reading messages from the [[#FGAddon commitlog mailing list|FGAddon commitlog mailing list]], you may see a large number of unrecognisable characters. This is the result of what is known as a binary diff, showing the binary file differences as if it were text. Although this is not a issue for the operation of the repository, the situation is an aesthetic problem which makes it more difficult to perform a review of the changes.

To fix the problem, firstly the binary files with the <code>svn:mime-type</code> property missing need to be identified. The following subversion command can be used:
<syntaxhighlight lang="bash">
svn propget svn:mime-type <file_name>
</syntaxhighlight>

As it can be tedious checking each file individually, the following Python script simplifies and automates the process to identify all binary files with a mime-type issue:

{{collapsible script
| type = Python 2/3 script
| title = Find binary files with no <code>svn:mime-type</code> property set.
| intro = The following script is based on blacklisting text files. Hence false positives are to be expected, and the blacklists can be expanded as needed.
| lang = python
| script =
#! /usr/bin/env python

from os import getcwd, walk
from os.path import join, splitext
from re import search
from subprocess import PIPE, Popen

skip_txt_file_seg = [
'authors',
'copying',
'licen',
'readme'
]

skip_txt_ext = [
'ac',
'css',
'dat',
'eff',
'frag',
'html',
'json',
'log',
'nas',
'osgx',
'svg',
'tex',
'txt',
'vert',
'xhtml',
'xml',
'xsl'
]

skip_bin_prop = [
'application/octet-stream',
'application/pdf',
'application/postscript',
'application/x-dosexec',
'application/x-gzip',
'application/zip',
'audio/x-wav',
'image/gif',
'image/jpeg',
'image/png',
'image/vnd.adobe.photoshop',
'image/tiff',
'image/x-ms-bmp',
'image/x-xcf',
]

# Walk through the directories.
for root, dirs, files in walk(getcwd()):
# Loop over the files in the current directory.
for file in files:
# Skip known text files.
skip = False
for i in range(len(skip_txt_file_seg)):
if search(skip_txt_file_seg[i], file.lower()):
skip = True
if skip:
continue

# The file extension.
file_path, ext = splitext(file)
ext = ext[1:].lower()

# Skip known text file extensions.
if ext in skip_txt_ext:
continue

# The full file path.
path = join(root, file)

# Query the file for svn:mime-type.
cmd = 'svn propget svn:mime-type \"%s\"' % path
pipe = Popen(cmd, shell=True, stdin=PIPE, stdout=PIPE, stderr=PIPE, close_fds=False)
props = []
for line in pipe.stdout.readlines():
props.append(line.strip())

# Byte array conversion (Python3).
for i in range(len(props)):
if hasattr(props[i], 'decode'):
props[i] = props[i].decode()

# Skip binary svn:mime-type values.
if len(props) and props[0] in skip_bin_prop:
continue

# Printout.
if not len(props):
print("%s" % path)
else:
print("%s svn:mime-type=%s" % (path, props[0]))
}}

==== Fixing the problem ====

As [[#Subversion_properties|git-svn cannot set or change]] the <code>svn:mime-type</code> property, a [[#Repository_checkout|svn checkout copy]] of the aircraft is required. The property can then be set to the default Subversion binary mime-type with:
<syntaxhighlight lang="bash">
svn propset svn:mime-type "application/octet-stream" <file_name>
</syntaxhighlight>

Alternatively, the following set of shell commands can be used to automate the process:
{{collapsible script
| type = Shell commands
| title = Set specific <code>svn:mime-type</code> values on a set of known binary files.
| intro = These shell commands will work on GNU/Linux or Mac OS X systems (or on Windows if using cygwin, or if a find command line tool is installed). The list of file types here are those most commonly found in FGAddon. To set the property on a list of binary files, type (or copy and paste):
| lang = bash
| script =
find -iname "*.wav" -exec svn propset svn:mime-type "audio/x-wav" {} \;
find -iname "*.bmp*" -exec svn propset svn:mime-type "image/x-ms-bmp" {} \;
find -iname "*.gif" -exec svn propset svn:mime-type "image/gif" {} \;
find -iname "*.jpg" -exec svn propset svn:mime-type "image/jpeg" {} \;
find -iname "*.png*" -exec svn propset svn:mime-type "image/png" {} \;
find -iname "*.psd" -exec svn propset svn:mime-type "image/vnd.adobe.photoshop" {} \;
find -iname "*.tif" -exec svn propset svn:mime-type "image/tiff" {} \;
find -iname "*.xcf" -exec svn propset svn:mime-type "image/x-xcf" {} \;
find -iname "*.rgb*" -exec svn propset svn:mime-type "application/octet-stream" {} \;
find -iname "*.au" -exec svn propset svn:mime-type "application/octet-stream" {} \;
find -iname "*.*af" -exec svn propset svn:mime-type "application/octet-stream" {} \;
find -iname "*.3ds" -exec svn propset svn:mime-type "application/octet-stream" {} \;
find -iname "*.blend*" -exec svn propset svn:mime-type "application/octet-stream" {} \;
find -iname "*.dds" -exec svn propset svn:mime-type "application/octet-stream" {} \;
find -iname "*.od[gst]" -exec svn propset svn:mime-type "application/octet-stream" {} \;
find -iname "*.onetoc2" -exec svn propset svn:mime-type "application/octet-stream" {} \;
find -iname "*.xlsx" -exec svn propset svn:mime-type "application/octet-stream" {} \;
find -iname "*.pdf" -exec svn propset svn:mime-type "application/pdf" {} \;
find -iname "*.ps" -exec svn propset svn:mime-type "application/postscript" {} \;
find -iname "*.gz" -exec svn propset svn:mime-type "application/x-gzip" {} \;
find -iname "*.mdl" -exec svn propset svn:mime-type "application/x-dosexec" {} \;
find -iname "*.zip" -exec svn propset svn:mime-type "application/zip" {} \;
| conc = Other binary files can safely be set to <code>"application/octet-stream"</code>, the Subversion default for binary files.
}}

== SourceForge developer services ==

The FlightGear project is hosted on the SourceForge open source infrastructure. This developer services section will highlight some of the useful tools you can take advantage of. SourceForge consists of two categories of services:
; Project infrastructure : The FlightGear project uses the project services of SourceForge. These services are for standalone software projects.
; Developer infrastructure : These are services available to anyone with a SourceForge account, and are available via your SourceForge homepage and accessible to all. This includes being able to create multiple version control repositories (svn, git, hg), wikis, forums, development teams, blogs, and ticket trackers (for bugs, support requests, tasks, etc.).

Rather than creating a new project, any development for the FlightGear project should be based on the developer infrastructure.

=== Developer git repository ===

To set up your own remote git repository, here for developing the FGAddon fkdr1 aircraft:
* On your profile page at <span style="color: blue"><tt><nowiki>https://sourceforge.net/u/<username>/profile/</nowiki></tt></span>, go to <code>Admin</code> -> <code>Add New</code> -> <code>Git</code>.
* Set label to <code>fkdr1 FGAddon git-svn repository</code>.
* Set the code path to <code>code-fkdr1</code>. The <code>code-*</code> prefix is to differentiate this from the <code>forum-*</code>, <code>wiki-*</code>, and other directories.

The repository will be located at <span style="color: blue"><tt><nowiki>https://sourceforge.net/u/<username>/code-fkdr1/ci/master/tree/</nowiki></tt></span>.

=== Development teams ===

If you and a group of friends would like to privately develop one of the FGAddon aircraft as a team, assuming that the you have contacted the original aircraft authors and the aircraft is not actively being developed, then you should create a SourceForge development team. A team leader should be appointed to set this up under their SourceForge account. Assuming you wish to develop the "ornithopter" aircraft, the steps are:

* Go to <code>Personal tools</code> -> <code>Admin</code>.
* Click on <code>User Permissions</code>.
* Click on <code>Add a new group</code> at the bottom.
* Set the name to <code>ornithopter</code>, and save.
* Click on <code>Add</code> in the <code>ornithopter</code> group and add the SourceForge names of all your team members.

After setting up a private repository in the team leader's account, as described below, then the development team should be set up for the repository.

* Go to the repository under your SourceForge account.
* Click on <code>Admin - <repository name></code>, then select <code>Permissions</code>.
* In the <code>Write</code> section, remove <code>Developer</code> and add <code>ornithopter</code>.
* Click on <code>Save</code>.

The development team will then have commit access to the private repository.

=== Team communications ===

To help with team development, the SourceForge infrastructure allows for multiple [https://sourceforge.net/p/forge/documentation/Discussion/ dedicated discussion forums] to be created. This can either be within a SourceForge project or under a SourceForge users homepage. This allows the team leader to create a forum dedicated solely to the development of the aircraft of interest. Continuing with the <code>ornithopter</code> example, the steps for the team leader are simple:

* On your profile page at <span style="color: blue"><tt><nowiki>https://sourceforge.net/u/<username>/profile/</nowiki></tt></span>, go to <code>Personal tools</code> -> <code>Admin</code>.
* Click on the <code>Tools</code> option in the left hand menu.
* Click on <code>Discussion</code> in the <code>Click to install</code> section.
* Change the label to <code>Ornithopter forum</code>, and the path to <code>forum-ornithopter</code>, for example. The <code>forum-*</code> prefix is to differentiate this from the <code>code-*</code>, <code>wiki-*</code>, and other directories.
* Click on <code>Save</code>.

More details are given on the [https://sourceforge.net/p/forge/documentation/Discussion/ SourceForge Discussion documentation].

== Development scenarios ==

=== Individual developer ===

{{Note|Development scenario: You are an individual developer and will use the native Subversion tools.}}

This is by far the simplest development scenario and should be used in most cases. If you are using the command line Subversion client, you can checkout an individual aircraft with:
{{#tag:syntaxhighlight|
{{fgaddon co
| login = <username>
| path = Aircraft/wrightFlyer1903
| post =
}}
| lang = "sh"
}}

Where <code><username></code> is your SourceForge user name. Alternatively you can checkout all aircraft with:
{{#tag:syntaxhighlight|
{{fgaddon co
| login = <username>
| post = flightgear-fgaddon
}}
| lang = "sh"
}}

If you do not have commit access, type one of:
{{#tag:syntaxhighlight|
{{fgaddon co
| path = Aircraft/wrightFlyer1903
| post =
}}
{{fgaddon co
| post = flightgear-fgaddon
}}
| lang = "sh"
}}

To use the new local svn repository, see the [[#Subversion|subversion instructions]].

=== Individual developer (git-svn) ===

{{Note|Development scenario: You are an individual developer and will use the git-svn tools.}}

This is more complicated than using the native SVN tools, but can be useful without having FGAddon commit access, as multiple local commits can be made to be sent to the original aircraft authors or to the development mailing list/forum. To clone the aircraft of choice into a new git repository, type:
{{#tag:syntaxhighlight|
{{fgaddon source|cmd=git svn clone|protocol=svn+ssh|login=<username>|type=svn|path=Aircraft/<aircraft>|full=1}}
| lang = "sh"
}}

Where <code><username></code> is your infrastructure user name and <code><aircraft></code> is the directory name in the FGAddon repository. This is valid whether or not you have commit permissions.

To use the new local git repository, see the [[#Git-svn|git-svn instructions]] and [[#Deficiencies_of_git-svn|its deficiencies]].

==== Upload to Sourceforge ====

To share the local developments, the changes can be uploaded to a remote git repository on the SourceForge infrastructure. For this, a [[#Developer_git_repository|developer git repository]] should first be set up under your SourceForge profile. Then add this as a remote:
{{#tag:syntaxhighlight|
{{sourceforge url|cmd=git remote add|opt=origin|protocol=ssh|login=<username>|user=<username>|type=git|repo=code-<aircraft>}}
| lang = "sh"
}}

And send the master branch where developments are located with:
<syntaxhighlight lang="bash">
git push --set-upstream origin master
</syntaxhighlight>

The changes in the new repository will be visible via the web interface at {{#tag:span|{{#tag:tt|{{#tag:nowiki|{{sourceforge url|user=<username>|repo=code-<aircraft>|branch=master}}}}}}| style="color: blue"}}.

=== Sending external git repository changes into FGAddon ===

{{Note|Development scenario: You are an individual developer with FGAddon commit access and wish to transfer the commits in a remote git repository into FGAddon using a temporary local git repository.}}

Firstly clone the FGAddon aircraft into a local git-svn repository with:
{{#tag:syntaxhighlight|
{{fgaddon source|cmd=git svn clone|protocol=svn+ssh|login=<username>|type=svn|path=Aircraft/<aircraft>|full=1}}
| lang = "sh"
}}

This will create a new local git repository linked to FGAddon via git-svn. If the aircraft is new and not present in FGAddon, see the [[#New_aircraft|instructions for adding a new aircraft to FGAddon]]. Next, set up the remote git repository as a remote, and fetch it:
<syntaxhighlight lang="bash">
git remote add <name> <url>
git fetch
</syntaxhighlight>

Where <code><url></code> is the URL of the remote git repository. Finally make an ordered list of all hashes of the commits to be sent into FGAddon, from earliest to latest, and cherry-pick them into the git-svn master branch:
<syntaxhighlight lang="bash">
git cherry-pick <commit hash 1>
git cherry-pick <commit hash 2>
git cherry-pick <commit hash 3>
...
</syntaxhighlight>

Note that the git-svn local repository should only have a single <code>master</code> branch and only consist of cherry-picking. To see the changes queued for sending to FGAddon:
<syntaxhighlight lang="bash">
git log git-svn..HEAD
git diff git-svn..HEAD
</syntaxhighlight>

Then to send the changes to FGAddon, firstly pull in any remote changes, and send the commits:
<syntaxhighlight lang="bash">
git svn rebase
git svn dcommit
</syntaxhighlight>

The temporary local repository can then be deleted.

=== Connecting an existing git repository to FGAddon ===

{{Note|Development scenario: You are an individual developer or team leader with FGAddon commit access and wish to connect a pre-existing remote git repository with FGAddon to send all changes back to FGAddon.}}

If a remote git repository containing a developed aircraft already exists, it is possible to connect it to the remote FGAddon repository using the git-svn tools. The following uses the [[#Dedicated_FGAddon_branch|dedicated FGAddon branch technique]]. Firstly, set up the bridge to FGAddon using git-svn in the per-aircraft repository:
{{#tag:syntaxhighlight|
{{fgaddon source|cmd=git svn init|protocol=svn+ssh|login=<username>|type=svn|path=Aircraft/<aircraft>|full=1}}
| lang = "sh"
}}

Where <code><aircraft></code> is the aircraft directory name in FGAddon. Note that this step can be performed without commit access to FGAddon by using a read-only SVN URL instead, but then changes cannot be pushed back to FGAddon ([[#Synchronising|dcommitting]], as it is known in the git-svn terminology). However, this allows upstream FGAddon changes to be integrated into the remote git repository, thus making it easy to prepare changes for submission for FGAddon inclusion using patches sent to the mailing list or sent via other channels.

Now fetch the current state from the remote FGAddon repository:
<syntaxhighlight lang="bash">
git svn fetch
</syntaxhighlight>

The downloaded SVN history is in the remote branch <code>remotes/git-svn</code>. To commit changes to SVN you need a local branch that tracks this remote branch. Create a local <code>fgaddon</code> branch that you will use to commit updates:
<syntaxhighlight lang="bash">
git branch fgaddon remotes/git-svn
</syntaxhighlight>

After committing new stuff to the <code>master</code> branch, to push to FGAddon checkout the <code>fgaddon</code> branch and update it from SVN in case someone else has touched the aircraft in the remote FGAddon repository:
<syntaxhighlight lang="bash">
git checkout fgaddon
git svn rebase
</syntaxhighlight>

Cherry-pick the new commits from <code>master</code> to <code>fgaddon</code> to preserve a linear history:
<syntaxhighlight lang="bash">
git cherry-pick <commit hash 1>
git cherry-pick <commit hash 2>
git cherry-pick <commit hash 3>
...
</syntaxhighlight>

To see the changes queued for sending to FGAddon as either commits or a diff, type:
<syntaxhighlight lang="bash">
git log git-svn..HEAD
git diff git-svn..HEAD
</syntaxhighlight>

If everything looks ok, dcommit the local commits on the <code>fgaddon</code> branch to send them to the remote FGAddon SVN repository:
<syntaxhighlight lang="bash">
git svn dcommit
</syntaxhighlight>

Switch back to the master branch for local development:
<syntaxhighlight lang="bash">
git checkout master
</syntaxhighlight>

To get changes from upstream you can either just download them with
<syntaxhighlight lang="bash">
git svn fetch
</syntaxhighlight>

or download them and rebase your <code>fgaddon</code> branch onto them:
<syntaxhighlight lang="bash">
git checkout fgaddon
git svn rebase
</syntaxhighlight>

=== Team development ===

{{Note|Development scenario: All members of the team are acting as gatekeepers, and all commits are made directly to FGAddon, either using svn or git-svn.}}

The simplest way to work as a team is for each developer to either have a [[#Individual developer|svn copy of FGAddon]] or a [[#Individual developer (git-svn)|git-svn copy of FGAddon]], and everyone commits directly to FGAddon. Communication and coordination between the team members can be performed using a [[#Team_communications|team leader organised SourceForge forum]] or using the [http://forum.flightgear.org/ FlightGear forum]. In this scenario, the team needs to take the initiative and everyone apply for FGAddon commit access.

=== Private team development (git-svn) ===

{{Note|Development scenario: One team leader is acting as the gatekeeper on a private git repository hosted on the in-house SourceForge infrastructure, using git-svn to push a fgaddon branch to FGAddon, with team members committing directly to the private git repository or making merge requests from their fork of the private repository.}}

To keep everything in-house, the entire operation will be based on the official infrastructure and remote repositories under each user's SourceForge (SF) profile. Note to the team leader - you must [https://git-scm.com/book/en/v1/Git-and-Other-Systems-Git-and-Subversion#git-svn keep your git-svn history linear] (meaning that a [[#Dedicated_FGAddon_branch|dedicated FGAddon branch]] should be created and changes manually cherry-picked into this branch). In the following, the <code>ornithopter</code> aircraft will be used as an example.

==== The team ====

Firstly, the entire team should sign up for [[#SourceForge account|SourceForge accounts]].

==== Team leader ====

===== Private repository set up =====

These steps are to be taken by the team leader. In your SourceForge user profile, set up a [[#Developer_git_repository| git repository]] with the label <code>Ornithopter FGAddon git-svn repository</code> and code path <code>code-ornithopter</code>. Then create a empty local git repository:
<syntaxhighlight lang="bash">
$ mkdir ornithopter
$ cd ornithopter
$ git init
</syntaxhighlight>

Link the empty repository to the <code>ornithopter</code> aircraft directory in the remote FGAddon repository and pull it in with:
{{#tag:syntaxhighlight|
$ {{fgaddon source|cmd=git svn init|protocol=svn+ssh|login=<username>|type=svn|path=Aircraft/ornithopter|full=1}}
$ git svn fetch
| lang = "sh"
}}

Replace <code><username></code> with your SF user name. Set up a special git-svn branch for FGAddon gatekeeping and dcommitting changes back to the repository:
<syntaxhighlight lang="bash">
$ git branch fgaddon remotes/git-svn
$ git checkout fgaddon
</syntaxhighlight>

And pull in the <code>ornithopter</code> from FGAddon:
<syntaxhighlight lang="bash">
$ git svn rebase
</syntaxhighlight>

To see the current local git-svn repository setup, type:
<syntaxhighlight lang="bash">
$ git branch -vva
$ git remote -v
$ git svn info
</syntaxhighlight>

Then return to the master branch:
<syntaxhighlight lang="bash">
$ git checkout master
</syntaxhighlight>

Finally, set up the remote git repository as a remote:
{{#tag:syntaxhighlight|
$ {{sourceforge url|cmd=git remote add|opt=origin|protocol=ssh|login=<username>|user=<username>|type=git|repo=code-ornithopter}}
| lang = "sh"
}}

And send the master branch to the remote git repository:
<syntaxhighlight lang="bash">
$ git push -u origin master
</syntaxhighlight>

To see the new set up:
<syntaxhighlight lang="bash">
$ git branch -vva
$ git remote -v
</syntaxhighlight>

The repository will be located at {{#tag:span|{{#tag:tt|{{#tag:nowiki|{{sourceforge url|user=<username>|repo=code-ornithopter|branch=master}}}}}}| style="color: blue"}}. Note that the git-svn information stored in the <code>.git/svn</code> directory will not be pushed to remote SoureForge repository, and therefore the link back to FGAddon will only be present in the local copy of the team leader. The git-svn link can be re-established at a later point if necessary.

===== Team setup =====

Set up a [[#Development teams|dedicated development team and grant them access to the git-svn repository]].

===== Pushing to FGAddon =====

Committing to FGAddon is for the local git repository of the team leader. History must be linear in the fgaddon branch, so cherry-picking is the way to go. This is from the [[#Individual developer (git-svn)|Individual developer (git-svn)]] section. In the local git repository, switch to the <code>fgaddon</code> branch:
<syntaxhighlight lang="bash">
git checkout fgaddon
</syntaxhighlight>

Pull in any changes which have occurred in FGAddon:
<syntaxhighlight lang="bash">
git svn rebase
</syntaxhighlight>

To see the commits in the <code>master</code> branch which are not in the <code>fgaddon</code> branch, type one of:
<syntaxhighlight lang="bash">
git log HEAD..master
git log HEAD..master --pretty=oneline
</syntaxhighlight>

Manually select the commits to be sent to FGAddon and cherry-pick them:
<syntaxhighlight lang="bash">
git cherry-pick <commit hash 1>
git cherry-pick <commit hash 2>
git cherry-pick <commit hash 3>
...
</syntaxhighlight>

Or to cherry-pick a range of commits:
<syntaxhighlight lang="bash">
git cherry-pick <commit hash 1>^..<commit hash 8>
</syntaxhighlight>

Then check what is to be sent:
<syntaxhighlight lang="bash">
git log git-svn..HEAD
git diff git-svn..HEAD
</syntaxhighlight>

Send the changes to FGAddon, send the git <code>fgaddon</code> branch changes to the remote git repository, and switch back to the master branch:
<syntaxhighlight lang="bash">
git svn dcommit
git push
git checkout master
</syntaxhighlight>

Finally merge in the git svn commits with their new hashes from the <code>fgaddon</code> branch, and send it to the remote git repository:
<syntaxhighlight lang="bash">
git merge fgaddon
git push
</syntaxhighlight>

==== Team members ====

===== Working with the repository =====

Each team member should make a clone of the private git repository:
{{#tag:syntaxhighlight|
$ {{sourceforge source|cmd=git clone|protocol=ssh|login=<username>|user=<username_leader>|type=git|repo=code-ornithopter|post=ornithopter|full=1}}
| lang = "sh"
}}

Replace <code><username></code> with your SourceForge user name, and <code><username_leader></code> is the SourceForge user name of the team leader.

===== Forking and merge requests =====

Alternatively, each team member can fork the git repository under your SourceForge account:
* Go to {{#tag:span|{{#tag:tt|{{#tag:nowiki|{{sourceforge source|user=<username>|repo=code-ornithopter|branch=master|full=1}}}}}}| style="color: blue"}}, where <code><username></code> is the SourceForge user name of the team leader.
* Click on <code>Fork</code>.
* Set the mount point to <code>code-ornithopter</code> and change the label as you wish.

Develop and push to your fork, then make merge requests by clicking on the <code>Request Merge</code> button.

== References ==
<references/>

[[Category:FlightGear]]

[[de:FGAddon]]
[[fr:FGAddon]]

FGAddon

2016-06-27T20:38:12Z

Circumn: /* Individual developer (git-svn) */ Always use svn+ssh, never https.

[[File:FGAddon logo.png|270px|right]]

The official '''FGAddon''' aircraft hangar is a version control repository, hosted on [[FlightGear|FlightGear's]] [https://sourceforge.net/projects/flightgear/ SourceForge infrastructure], and used for the day-to-day development of FlightGear aircraft. FGAddon is an {{wikipedia|Apache Subversion|noicon=1}} version control repository. These are aircraft that are not part of the base package (the aircraft that are included in the base package — the [[Cessna 172P]] and the [[UFO]] — are kept in the [http://sourceforge.net/p/flightgear/fgdata FGData] repository), but are tagged with each stable release for the [http://www.flightgear.org/download/ FlightGear download pages].

The FGAddon aircraft development repository should be considered unstable. When using a stable FlightGear release, it is best to obtain aircraft with a matching version number from the [http://www.flightgear.org/download/ FlightGear download pages]. However, as stable releases from FlightGear version 3.4 onwards are tagged and present within the FGAddon repository, the Subversion tools can be a convenient way to obtain individual aircraft or the entire official hangar of approximately 500 aircraft. Also, if using the [[FlightGear build server|lastest nightly releases]] or a [[Building FlightGear|self-compiled version of FlightGear]] from FlightGear's [http://sourceforge.net/p/flightgear/_list/git Git version control repositories], using FGAddon allows the aircraft to be updated to the latest development versions.

== History ==
{{WIP|The accuracy of the facts in this section are in the process of being verified.}}
[[File:Image103.gif|thumb|Original Win95 icon]]
The FlightGear project was conceived on April 8, 1996 by David Murr who proposed a new flight simulator to be developed by volunteers<ref>David Murr (Apr 9, 1996). FlightGear proposal 1.0: [https://groups.google.com/forum/#!msg/rec.aviation.simulators/ny8HFBE5_T8/OdtIiGNGJc8J "A PROPOSAL FOR A NEW FLIGHT SIMULATOR - home built!@"]. Published on the rec.aviation.simulators newsgroup.</ref><ref>David Murr (1996). FlightGear proposal 2.0: [http://www.flightgear.org/proposal-2.0 FLIGHT GEAR "This truly is as real as it gets!" - a proposal for a new flight simulator - REVISION 2.0].</ref><ref>David Murr (Oct 29, 1996). FlightGear proposal 3.0: [http://www.flightgear.org/proposal-3.0 FLIGHT GEAR FLIGHT SIMULATOR, revision 3.0 - Wednesday, 10.30.96, "The future of flight simulation is here"]. Published on the [http://ftp.igh.cnrs.fr/pub/flightgear/www/old-stuff/flight-gear.9610 flight-gear@infoplane.com mailing list].</ref><ref>David Murr (Sep 11, 1998). FlightGear proposal 3.0.1: [http://www.flightgear.org/proposal-3.0.1 FLIGHT GEAR FLIGHT SIMULATOR, revision 3.0.1 - Friday, Sep.11.98, "The future of flight simulation is here"].</ref>. Part of the initial goals were to develop 2D and 3D graphics routines for the simulator. However this was a huge task that came to an unfinished halt at the start of 1997 as the main developer, Eric Korpela, was finishing his thesis. Therefore starting on May 16, 1997, Curtis Olson relaunched development with a new project based on the OpenGL libraries, allowing a functional flight simulator to be put together in a short period of time<ref>Curtis Olson (Sep 28, 2015). [http://forum.flightgear.org/viewtopic.php?f=42&t=27558&p=259048#p259021 Re: A PROPOSAL FOR A NEW FLIGHT SIMULATOR - home built!@]. Published on the FlightGear forum.</ref>. The first commits were to the original [[FlightGear CVS|flightgear and simgear CVS version control repositories]].

As the project grew, so did the size, quantity, and quality of the FlightGear assets. These assets were not organised and were scattered across different parts of the internet. Therefore it was decided that much of this FlightGear content would be assembled and stored together in a new centralised CVS repository called fgdata, which was created on October 22, 2000. To allow for the legal redistribution of these assets as part of the FlightGear distribution, a GPLv2 only policy was adopted.

In May 2010, development was interrupted by the infamous ''"coffee incident"'' which resulted in the loss of Curtis' home server hosting all of the FlightGear repositories<ref>James Turner (May 20, 2010). [http://thread.gmane.org/gmane.games.flightgear.devel/60340/focus=60341 <nowiki>[Flightgear-devel]</nowiki> Re: Flightgear git repositories (was Re: GIT or CVS - Confusion)] Published on the flightgear-devel mailing list.</ref>. These events resulted in a [[FlightGear CVS|mass migration of all the CVS repositories to Git repositories]]. Due to bandwidth issues, it was decided that the new repositories would be hosted on the Gitorious open source infrastructure.

With time as the project grew, the size and scope of the fgdata repository mushroomed, mainly due to the growing number of aircraft stored in [[$FG_ROOT]]/Aircraft, so that a split was inevitable. A first splitting attempt was organised by Gijs de Rooy and announced on October 18, 2011<ref>Cedric Sodhi (Oct 18, 2011) [http://thread.gmane.org/gmane.games.flightgear.devel/66846 <nowiki>[Flightgear-devel]</nowiki> FGData Split Completed - a.k.a Life after the Split] Published on the flightgear-devel mailing list.</ref>. Each aircraft was placed in its own Git repository and all aircraft linked back to fgdata using a Git submodule approach. However this attempt failed and was abandoned. From this date until the end of 2014, the design of the fgdata split was discussed on the development mailing list and summarised in the [[FlightGear Git: splitting fgdata]] wiki article. In the planning stages, the repositories were known as fgdata-old splitting into [[FGData]] (a.k.a. fgdata-new) and FGAddon (a.k.a. flightgear-aircraft and fgaircraft). After half a decade of planning, it was decided that the best solution for FlightGear aircraft development would be a single centralized Subversion repository. This would facilitate community management and maintenance of the aircraft while at the same time providing modularity and smaller downloads and smaller local repository sizes.

In late 2014, Gitorious, the provider of the open source infrastructure for the FlightGear source code and data repositories announced that it would shut its services down by May 2015 due to its acquisition by GitLab. This catalysed the split of fgdata-old and a switch to the SourceForge open source infrastructure for the hosting of the VC repositories. Other parts of the FlightGear infrastructure were already hosted by SourceForge, making the move a natural one. Sealing the deal, SourceForge agreed in writing to host the huge FlightGear aircraft collection, the size of which is unrivaled in open source circles. Today, the FGAddon SVN repository, together with most of the FlightGear project infrastructure, is hosted on SourceForge.

In August 2015, a new FlightGear policy document was written to codify the unwritten standards of the project<ref>[http://www.flightgear.org/flightgear-policy-document/ FlightGear Policy Document and Roadmap], draft document.</ref>. With this document, the licensing policy for the FlightGear aircraft has been updated from being GPLv2-only to now being a GPLv2+ or GPL-compatible<ref>[http://www.gnu.org/licenses/license-list.en.html GNU license compatibility list].</ref> stance. However, to combat licence proliferation complications for the integrity and good of the FlightGear project, it is strongly recommended that original content be GPLv2+ licensed.



== Obtaining aircraft ==

{{tip|If you are interested in obtaining aircraft for stable FlightGear releases and you are unaware of what version control is, you should visit the [[FlightGear_hangars|FlightGear hangars]] for downloading aircraft.}}
{{caution|If the FlightGear and FGAddon aircraft versions do not match, strange bugs should be expected and the version-mismatch combination will not be supported by the FlightGear community.}}

With access to the Subversion (SVN) tools, the FGAddon version control repository can be a convenient way for obtaining aircraft for using within a specific FlightGear version directly from the official source. When using the [[FlightGear Build Server|nightly builds]] or a [[Building FlightGear|version controlled copy of FlightGear]], the most up to date in-development versions of the aircraft should be used so the versions match. The following describes how to use the official repository to obtain aircraft from the perspective of a FlightGear user.

=== Preparation ===
To use the FGAddon repository, the Subversion tools need to be installed:
* '''MS Windows''': Install one of the [https://subversion.apache.org/packages.html#windows many Subversion clients]. For example [https://sliksvn.com/download/ SlikSVN] is one of the best command line versions and the best for aircraft development, and [http://tortoisesvn.net/ TortoiseSVN] provides a user friendly graphical user interface (GUI) by integrating into Windows Explorer.
* '''Mac OS X''': Install the [https://subversion.apache.org/packages.html#osx official Subversion client].
* '''GNU/Linux''': Install the Subversion client via the package manager. This will usually be in a package called <code>subversion-*.{rpm,deb}</code>.

=== FGAddon directory layout ===
To know how to use the FGAddon repository, an understanding of the repository directory layout is essential.
* <code>/trunk</code>: This base directory is where the in-development versions of the aircraft are located.
* <code>/branches/release-x.y.z/</code>: These directories correspond to the specific stable FlightGear releases.

The [https://sourceforge.net/p/flightgear/fgaddon/HEAD/tree/ web interface for the FGAddon repository] allows all of the aircraft to be browsed.

=== Download ===
[[File:V22Osprey.jpg|thumb|200px|Aircraft to be downloaded]]
Firstly, choose an aircraft to download. The [[Bell Boeing V-22 Osprey]] will be used in this example.

==== Command line ====

To download the aircraft for FlightGear 3.4, simply type:
{{#tag:syntaxhighlight|
{{fgaddon co|branch=branches/release-3.4.0|path=Aircraft/V22-Osprey|post=}}
| lang = "sh"
}}

To obtain the in-development version, type:
{{#tag:syntaxhighlight|
{{fgaddon co|path=Aircraft/V22-Osprey|post=}}
| lang = "sh"
}}

If all of the ~500 aircraft from the repository are desired - beware that this will be a huge download of over 6 GB - use the following command:
{{#tag:syntaxhighlight|
{{fgaddon co|post=flightgear-fgaddon}}
| lang = "sh"
}}

When using a stable FlightGear release, for example FlightGear 2016.1, to obtain all of the FGAddon aircraft to match the installed FlightGear version, use:
{{#tag:syntaxhighlight|
{{fgaddon co|branch=branches/release-2016.1|post=flightgear-fgaddon}}
| lang = "sh"
}}

==== GUI clients and TortoiseSVN ====

When using one of the Subversion GUIs (graphical user interfaces), simply copy one of the above <code>https://</code> URLs and use that in the GUI (each GUI is different, so see the relevant documentation for help). For the unique TortoiseSVN tool, simply:

* In Windows Explorer, create a new empty folder for the aircraft (or aircraft collection).
* In the new folder, right click and select <code>SVN Checkout...</code>.
* Copy and paste the URL, for example {{fgaddon source|path=Aircraft/V22-Osprey|type=svn|full=1}}, leave all other settings as they are, and import by clicking on <code>OK</code>.

For more details, see the [http://tortoisesvn.net/support.html TortoiseSVN documentation]. Note that there is an option to install the command line tools when installing TortoiseSVN.

=== Flying ===

To use the newly downloaded aircraft, please see the [[Howto:Install aircraft]] article, skipping the instructions for downloading and unzipping the aircraft.

=== Updates ===
With a checked out copy of the <code>/trunk</code> in-development version, the aircraft can be updated to the latest version using the command:
<syntaxhighlight lang="bash">
svn up
</syntaxhighlight>

== Aircraft development ==

{{tip|The FlightGear community encourages aircraft development directly within FGAddon.}}

=== Contact the original aircraft authors ===

The first step for developing and advancing the aircraft of the official FlightGear hangar, or from one of the [[Flightgear_hangars#Aircraft_hangars|private hangars]] for that matter, is to make contact with the original aircraft author(s). Their names can be found within the <code>*-set.xml</code> file, within the <code><authors></code> XML tag. Often the contact email address will be listed in a README file or some other text file in the base aircraft directory. If not, contact can sometimes be established via the [https://lists.sourceforge.net/lists/listinfo/flightgear-devel FlightGear development mailing list]. Contacting the original authors is important to see if the aircraft is currently being actively developed, and if you can join in as part of the development team.

=== SourceForge account ===

To work on the official aircraft collection, a [https://sourceforge.net/user/registration/ SourceForge account] should first be set up. This will allow to either directly commit to the FGAddon repository, if commit access has been been granted, or to work in as part of a SourceForge development team. The registration process is lightning quick and the SourceForge developer infrastructure and developer services will be accessible in under a minute.

=== Commit access ===

Before obtaining commit access, an all-out effort to contact the original author(s) should be made to determine if the aircraft is actively being developed. If this is unsuccessful, sign up for the [https://lists.sourceforge.net/lists/listinfo/flightgear-devel FlightGear development mailing list] and ask for help there. If the aircraft has a current maintainer, you will be directed as to how to proceed with development. Otherwise ask if someone could volunteer to mentor you in the process of becoming an aircraft developer with full commit access.

To obtain commit access, you will first need:
# To demonstrate your capabilities and development skills.
# To show that you understand the [http://article.gmane.org/gmane.games.flightgear.devel/78713 FlightGear policy document]. 
# To show an understanding of the GPL licensing issues, and that you can be trusted not to use copyrighted, non-GPL material.
# To earn the trust of the FlightGear community.

These easy to jump over hurdles are simply designed to protect against repository corruption or pollution of the repository with illegal content.

To have your changes committed into the FGAddon repository, you should discuss and coordinate with the original aircraft author, or your mentor, for the best way to proceed. Depending on the [[#Development_scenarios|development scenario]], this maybe by merge request, file transfer, the primitive patch system, or any other convenient way. Once you believe you have proven your capabilities and you are knowledgeable about GPL licensing issues, you should write a mail to the development mailing list asking if you can be granted commit access, providing your SourceForge username.

=== FGAddon commitlog mailing list ===

To follow all changes which occur in the FGAddon repository, subscribe to the dedicated [https://lists.sourceforge.net/lists/listinfo/flightgear-fgaddon-commitlogs Flightgear FGAddon commitlogs mailing list]. One email is sent per commit, as the commit is made.

== Version control tools ==

To access FGAddon and use it for aircraft development, the Subversion or SVN version control tools are needed. Alternatively git-svn provides an interface for those who prefer the git version control tools.

=== Subversion ===

==== Set up ====
The FGAddon aircraft hangar is stored in a remote Subversion repository located on the SourceForge infrastructure, and therefore it is simplest to use the SVN tools for aircraft development and will cause the least problems. See the [[#Preparation|Subversion installation section]] for setting up the tool chain.

==== Repository checkout ====
The first step is to 'checkout' a copy of either the repository trunk or one of the aircraft in the trunk:
<syntaxhighlight lang="bash">
svn co <url> <dir>
</syntaxhighlight>

For the relevant URL to use, you must chose one of the [[#Development_scenarios|development scenarios]] and find the URL in that section. This command will create a local subversion repository copy in the given <code><dir></code> directory. Note that this will only contain the part of the FGAddon repository specified in the URL. This means that Subversion allows you to checkout either a single file all the way to the entire remote repository.

==== Information and history ====
At any point to see information about the local repository, type:
<syntaxhighlight lang="bash">
svn info
</syntaxhighlight>

To see the history of the checked out copy of the repository, type one of:
<syntaxhighlight lang="bash">
svn log
svn log | less
svn log -v | less
</syntaxhighlight>

==== Daily usage ====
The main Subversion command you will be using is:
<syntaxhighlight lang="bash">
svn add <path>
</syntaxhighlight>

This will register the file or directory <code><path></code> within the local repository to allow it to later be 'committed' and sent to the remote repository. To move or rename a file or directory, use:
<syntaxhighlight lang="bash">
svn mv <path1> <path2>
</syntaxhighlight>

This should be used rather than normal file moving/renaming so that the change is tracked in the local repository. To remove a file from the local repository, type:
<syntaxhighlight lang="bash">
svn rm <path>
</syntaxhighlight>

To see the current status of the local repository, type:
<syntaxhighlight lang="bash">
svn st
</syntaxhighlight>

==== Committing changes ====
All of the above operations only occur on the local repository copy - the remote FGAddon repository at SourceForge will know nothing of these changes. To send all your changes to FGAddon, you need to commit the changes:
<syntaxhighlight lang="bash">
svn ci
</syntaxhighlight>

This will open up an editor to allow you to write an informative commit log message. When committing, it is best to make small modular commits so that each commit corresponds to a single purpose. Note that you can only commit to FGAddon if you have [[#Commit access|commit access]].

==== Branching ====
The concept of Subversion branching is currently only used in the FlightGear project for tagging the stable releases. However if you are curious about branching, see the [http://svnbook.red-bean.com/en/1.7/svn.branchmerge.html Branching and Merging chapter of the Subversion manual], and the [https://www.orcaware.com/svn/wiki/Svnmerge.py svnmerge.py script] which can greatly simplify the process.

=== Git-svn ===

The git-svn tool is useful for those who are already familiar with using git repositories, or those who wish to have their own private aircraft development playground. Git-svn provides a bridge between the remote FGAddon Subversion repository and a local git repository. For those unfamiliar with git, the git-svn bridge together with the git repository is far more complicated to use than the native [[#Subversion|Subversion tools]]. For more information on using git, see [[Howto:Start using git]]. The following will assume that only a single aircraft will be stored in the local git repository.

==== Set up ====
The git distributed version control system needs to first be [https://git-scm.com/downloads installed].

==== Cloning a single aircraft ====
The first step is to 'clone' a copy of one of the aircraft in the remote Subversion trunk:
<syntaxhighlight lang="bash">
git svn clone <aircraft_url>
</syntaxhighlight>

For the relevant aircraft URL to use, you must chose one of the [[#Development_scenarios|development scenarios]] and find the URL in that section. The URL depends on your [[#Commit access|FGAddon commit access status]]. The clone command will create a local git repository containing solely the aircraft of interest, and initialise the git-svn bridge.

==== Information and history ====
At any point to see information about the local repository, type:
<syntaxhighlight lang="bash">
git svn info
git branch -vva
git remote -v
</syntaxhighlight>

To see the history of the checked out copy of the repository, type:
<syntaxhighlight lang="bash">
git log
</syntaxhighlight>

==== Daily usage ====
The main git command you will be using is:
<syntaxhighlight lang="bash">
git add <path>
</syntaxhighlight>

This will register the file or directory <code><path></code> within the local repository to allow it to later be 'committed' to the local git repository. To move or rename a file or directory, use:
<syntaxhighlight lang="bash">
git mv <path1> <path2>
</syntaxhighlight>

However note that git history is not as robust as svn history. See the [[#Moving_or_renaming_files|git-svn file moving/renaming deficiency section]] for how to better perform this operation. To remove a file from the local repository, type:
<syntaxhighlight lang="bash">
git rm <path>
</syntaxhighlight>

To see the current status of the local repository, type:
<syntaxhighlight lang="bash">
git status
</syntaxhighlight>

==== Committing changes ====
As git is a distributed version control system, changes are committed to the local git repository.
<syntaxhighlight lang="bash">
git commit
</syntaxhighlight>

This will open up an editor to allow you to write an informative commit log message. The commit is local and will not be sent to FGAddon.

==== Dedicated FGAddon branch ====
In the examples above, only a single branch was assumed in the repository. If interaction with a remote git repository or branching within the local git repository is desired, then a different strategy is required. The reason being that the branch that synchronises with FGAddon must [https://git-scm.com/book/en/v1/Git-and-Other-Systems-Git-and-Subversion#git-svn preserve a linear history]. This means only cherry-picking of the desired changes into that branch is allowed.

In this example, two branches will be set up in the local git repository:
* <code>fgaddon</code>: This branch will be dedicated for FGAddon synchronisation and will preserve a linear history.
* <code>master</code>: A master branch for aircraft development, allowing for mergers and other non-linear history operations.

Assuming a [[#Cloning_a_single_aircraft|newly cloned repository]], create the <code>fgaddon</code> branch with:
<syntaxhighlight lang="bash">
git branch fgaddon
</syntaxhighlight>

And switch to that branch:
<syntaxhighlight lang="bash">
git checkout fgaddon
</syntaxhighlight>

The FGAddon synchronisation can then be performed on this branch. To pull in the developments from the master branch, use cherry-picking to apply a sequentially ordered list of commit hashes:
<syntaxhighlight lang="bash">
git cherry-pick <commit hash 1>
git cherry-pick <commit hash 2>
git cherry-pick <commit hash 3>
...
</syntaxhighlight>

To see the list of commits to be sent to FGAddon prior to dcommitting, type:
<syntaxhighlight lang="bash">
git log git-svn..HEAD
</syntaxhighlight>

And to see the changes as a single diff:
<syntaxhighlight lang="bash">
git diff git-svn..HEAD
</syntaxhighlight>

==== Synchronising ====
To send the changes to the remote FGAddon repository, firstly change to the dedicated <code>fgaddon</code> branch:
<syntaxhighlight lang="bash">
git checkout fgaddon
</syntaxhighlight>

Make sure the local git-svn repository is up to date with all changes that have occurred in FGAddon:
<syntaxhighlight lang="bash">
git svn rebase
</syntaxhighlight>

Then push or dcommit the changes to FGAddon with:
<syntaxhighlight lang="bash">
git svn dcommit
</syntaxhighlight>

=== Deficiencies of git-svn ===

{{warning|Performing a <code>git-svn clone</code> of the <code>/trunk/</code> or entire repository is not recommended, as the entire repository history will be downloaded, resulting in a huge local repository, as well as putting a large strain on the FlightGear open source infrastructure.}}

There are a number of operations in which git-svn is deficient and the svn tools should be used instead.

==== Copying files between aircraft ====

{{caution|Git-svn does not maintain the file copying history normally present in a Subversion repository.}}

The most important of these is the copying of content from other FGAddon aircraft. In this case you will need FGAddon commit access and a local svn copy of the repository. Firstly synchronise the repositories by dcommitting all changes back to FGAddon:
<syntaxhighlight lang="bash">
git svn dcommit
</syntaxhighlight>

Then in the local svn repository, copy the file:
<syntaxhighlight lang="bash">
svn cp Aircraft/<aircraft1>/<file_path1> Aircraft/<aircraft2>/<file_path2>
</syntaxhighlight>

And commit the change:
<syntaxhighlight lang="bash">
svn ci
</syntaxhighlight>

Back in the local git-svn repository, pull in the new files:
<syntaxhighlight lang="bash">
git svn rebase
</syntaxhighlight>

Using the subversion tools avoids the FGAddon repository backend from significantly increasing in size, as [http://svnbook.red-bean.com/en/1.7/svn.branchmerge.using.html#svn.branchmerge.using.create svn copies are cheap].

==== Moving or renaming files ====

{{caution|Git-svn does not always maintain the file moving or renaming history normally present in a Subversion repository.}}

This problem stems from the fact that svn history is more robust than that of git. The <code>svn mv</code> and <code>git mv</code> commands are not equivalent. The subversion command stores the move history directly in the repository whereas git does not (git instead uses heuristic methods to try to detect history, after the commit). The result of using git-svn is that often the move will not be detected and the FGAddon history will show one file or directory being deleted and another added. This also causes the repository backend to increase in size, whereas <code>svn mv</code> will not cause any significant size increase. If you wish to have a better historical record in the FGAddon repository and be considerate to the repository backend, it is recommended that you temporarily switch to the subversion tools. Firstly, synchronise the repositories:
<syntaxhighlight lang="bash">
git svn dcommit
</syntaxhighlight>

Then in the local svn repository, move or rename the file:
<syntaxhighlight lang="bash">
svn mv Aircraft/<aircraft>/<file_path1> Aircraft/<aircraft>/<file_path2>
</syntaxhighlight>

And commit the change:
<syntaxhighlight lang="bash">
svn ci
</syntaxhighlight>

Back in the local git-svn repository, pull in the changes with:
<syntaxhighlight lang="bash">
git svn rebase
</syntaxhighlight>

==== Copying files within one aircraft ====

Just as the <code>svn mv</code> command stores the move information directly within the repository, so does <code>svn cp</code> store the copy information. Therefore if you would like to duplicate a text file and modify it, using the native Subversion tools instead of git-svn for this operation allows for the file history to be permanently preserved in the FGAddon repository.

==== Subversion properties ====

{{caution|Git-svn currently only supports the <code>svn:executable</code> property, all other properties are ignored and cannot be added, changed, or removed in a git-svn clone of the aircraft.}}

Internally, Subversion identifies binary files using the <code>svn:mime-type</code> repository property. However as git-svn cannot set this property when using the <code>git add</code> command, the result is that binary files will be treated as text. Binary diffs will be seen when using <code>svn diff</code> or <code>git diff</code>, and a binary diff will be shown in the [[#FGAddon commitlog mailing list|FGAddon commitlog mailing list]] messages. As this issue is not unique to git-svn, to work around this issue please see the [[#Binary diffs|binary diffs]] section.

== FGAddon development concepts ==

=== New aircraft ===

To add a new aircraft to the FGAddon repository, the SVN tools are required. If you encounter <code>svn:mime-type</code> property problems when adding a new aircraft, see the [[#Mime-type problems|mime-type problems section]] for how to resolve the issue. Or if you have a <code>svn:executable</code> property problem, see the [[#Executable flag|executable flag problem section]].

==== svn import ====

{{warning|The <code>svn import</code> command described herein will send all contents of the specified directory directly into FGAddon without warning and without a way to cancel the operation. Therefore special care must be taken when specifying the directory to upload into FGAddon, as well as the target FGAddon directory. See the [[#svn add|svn add]] section below for a safer way to add a new aircraft.}}

The [http://svnbook.red-bean.com/en/1.7/svn.tour.importing.html#svn.tour.importing.import svn import] command is the easiest method to use and does not require a local copy of the repository to be checked out. To start:

# Create an empty local aircraft directory.
# Copy the aircraft files into this directory.
# Carefully check all files to make sure there are no hidden or temporary files that should not be uploaded to FGAddon.

Assuming the Dead Simple Human Powered Airplane (DaSH PA or "DaSH") aircraft as an example, located in the <code>DaSH/</code> directory, on the command line run:
{{#tag:syntaxhighlight|
{{fgaddon source
| cmd = svn import DaSH/
| protocol = svn+ssh
| login = <username>
| type = svn
| path = Aircraft/
| post = -m \
| full = 1
}}
"Initial import of the DaSH human powered aircraft.\n\nFor details see the forum thread at http://forum.flightgear.org/viewtopic.php?f=4&t=24495 ."
| lang = "sh"
}}

Where <code><username></code> is the SourceForge user name. This will add all the files into FGAddon with commit log message with the summary line <code>Initial import of the DaSH human powered aircraft.</code>, followed by a blank line, and then a detailed description pointing to the original location or discussion of the aircraft. To see if the aircraft has been successfully added to the repository:
{{#tag:syntaxhighlight|
{{fgaddon source
| cmd = svn list
| protocol = svn+ssh
| login = <username>
| type = svn
| path = Aircraft/DaSH/
| full = 1
}}
| lang = "sh"
}}

Or visit the {{fgaddon source|path=Aircraft|text=FGAddon web interface}}. The aircraft can then be checked out as described in the [[#Development scenarios|Development scenarios section]].

==== svn add ====

If a local copy of the FGAddon trunk is present, then the <code>svn add</code> command can be used instead. This is far safer than the <code>svn import</code> command, as the change can be double checked before committing. In the <code>Aircraft/</code> directory of the local repository, create the <code>DaSH/</code> directory. This can either be empty or contain all files of the initial aircraft. Then on the command line, add the aircraft to the local repository:
<syntaxhighlight lang="bash">
svn add DaSH/
</syntaxhighlight>

Then double check the changes prior to committing:
<syntaxhighlight lang="bash">
svn st
</syntaxhighlight>

And send the changes to FGAddon with:
<syntaxhighlight lang="bash">
svn ci
</syntaxhighlight>

An editor, often vi<ref>[http://www.vim.org/docs.php Vim documentation]</ref>, will open and the commit message can be composed. Alternatively the commit log message can be specified on the command line with:
<syntaxhighlight lang="bash">
svn ci -m "<subject_line>\n\n<detailed_description>"
</syntaxhighlight>

=== Commit blocking by pre-commit hooks ===

Sometimes when committing to FGAddon, the commit will be blocked the following will be printed out:
<pre>
svn: E165001: Commit failed (details follow):
svn: E165001: Commit blocked by pre-commit hook (exit code 1) with output:
</pre>

This is due to the presence of two repository pre-commit hook scripts which check the quality of the commit, blocking it if a text file is set to a binary file mime-type or if the executable flag is set. These scripts are simply to protect the repository and to keep it clean.

==== Mime-type problems ====

Sometimes when attempting to commit files to FGAddon using the SVN tools, the commit will be blocked with the following message:
<pre>
Sending dash-set.xml
svn: E165001: Commit failed (details follow):
svn: E165001: Commit blocked by pre-commit hook (exit code 1) with output:

Aborting the commit, the svn:mime-type property is labelling the following text
files as binary:

dash-set.xml: svn:mime-type=application/xml

Before committing, please remove this property by typing 'svn propdel svn:mime-
type file_name' for all affected files. This will allow the text files to be
treated as text within the FGAddon repository.

To avoid the svn:mime-type property being incorrectly set by your subversion
client, the subversion configuration file at $HOME/.subversion/config or
%appdata%\roaming\subversion\config should be edited and a new entry added to
[auto-props] for each affected file type. In most cases, the problem is with
XML files being labelled as "application/xml" by a library called libmagic. To
override this, add the following to the svn config file:

*.xml = svn:mime-type=text/xml

svn: E165001: Your commit message was left in a temporary file:
svn: E165001: '/flightgear/repo_testing/svn-commit.tmp'
</pre>

Despite messages about adding or sending files, no change will have occurred in the FGAddon repository. This message is created by a repository pre-commit hook script which checks if the Subversion <code>svn:mime-type</code> property is set on a list of known text files and, if the mime-type is set to a binary format, the commit is blocked. The reason for this block is to protect the repository. Newer SVN clients rely on a 3rd party library known as libmagic which will detect the aircraft XML files as the binary mime-type of <code>application/xml</code>. The result is that the XML files are treated as binary files in the repository. This behaviour is completely undesirable, as changes cannot be followed on the [[#FGAddon commitlog mailing list|flightgear-fgaddon-commitlogs mailing list]] or in the repository history, and the size of the commits become orders of magnitude larger. Therefore this buggy behaviour has been blocked for the protection of the FlightGear project. To remove the problem, follow the instructions in the message and, using the command line tools, type:
<syntaxhighlight lang="bash">
svn propdel svn:mime-type <file_name>
</syntaxhighlight>

Repeat this for each text file listed in the error message. Then commit again, using the commit message saved in the <code>svn-commit.tmp</code> file. The message file name will be reported in the commit failure message, but check its contents first:
<syntaxhighlight lang="bash">
cat svn-commit.tmp
</syntaxhighlight>

And reperform the commit:
<syntaxhighlight lang="bash">
svn ci -F svn-commit.tmp
</syntaxhighlight>

===== Subversion config file =====

The automatic property setting of <code>svn:mime-type</code> can be controlled by modifying the Subversion <code>config</code> file. Firstly in the <code>[miscellany]</code> section, make sure that the auto-properties are turned on:
<syntaxhighlight>
enable-auto-props = yes
</syntaxhighlight>

Then in the <code>[auto-props]</code> section, add:
<syntaxhighlight>
*.ac = svn:mime-type=text/plain
*.eff = svn:mime-type=text/xml
*.frag = svn:mime-type=text/plain
*.nas = svn:mime-type=text/plain
*.osgx = svn:mime-type=text/xml
*.svg = svn:mime-type=text/svg+xml
*.txt = svn:mime-type=text/plain
*.vert = svn:mime-type=text/plain
*.xhtml = svn:mime-type=text/xml
*.xml = svn:mime-type=text/xml
*.xsl = svn:mime-type=text/xml
</syntaxhighlight>

These are all the text files that the hook script will check that the mime-type is set to a text format, though new text files will likely be added in the future. These additions can either be to the user configuration file located at <code>~/.subversion/config</code> (or <code>%USERPROFILE%\AppData\Roaming\Subversion\config</code> in Windows) or, if a user configuration file is not set, to the global configuration file at <code>/etc/subversion/config</code> (or <code>%APPDATA%\Subversion\config</code> in Windows).

==== Executable flag ====

Another blocking message when attempting to commit files to FGAddon using the SVN tools is:
<pre>
Adding dash-set.xml
Transmitting file data .svn: E165001: Commit failed (details follow):
svn: E165001: Commit blocked by pre-commit hook (exit code 1) with output:

The svn:executable property is set on the files ['dash-set.xml'], aborting the
commit.

The current policy is that no executable files are allowed in FGAddon. Before
committing, please remove this property by typing 'svn propdel svn:executable
file_name' for all affected files. Or to remove it recursively from all files
to be committed, in your aircraft directory type 'svn propdel svn:executable
-R'.

To avoid the svn:executable property being set by your subversion client, on
GNU/Linux and Mac OS X systems simply make sure that the file's execute bit is
not set before adding the file to be committed.

svn: E165001: Your commit message was left in a temporary file:
svn: E165001: '/flightgear/repo_testing/svn-commit.tmp'
</pre>

This will probably only be seen on Mac OS X and GNU/Linux systems. This message is printed by a pre-commit repository hook script that checks if the Subversion <code>svn:executable</code> property is set and, if so, the commit is blocked. This is a security measure, as no aircraft files should be executable. To remove the problem, follow the instructions in the message and, using the command line tools, type:
<syntaxhighlight lang="bash">
svn propdel svn:executable -R
</syntaxhighlight>

Then commit again, using the commit message saved in the <code>svn-commit.tmp</code> file. The message file name will be reported in the commit failure message, but check its contents first:
<syntaxhighlight lang="bash">
cat svn-commit.tmp
</syntaxhighlight>

And the reperform the commit:
<syntaxhighlight lang="bash">
svn ci -F svn-commit.tmp
</syntaxhighlight>

=== Binary diffs ===

{{warning|The incorrect setting or absence of the mime-type property on a binary file will result in a binary diff.}}

When looking at the output of <code>svn diff</code> (or <code>git diff</code> if you are using git-svn) as well as when reading messages from the [[#FGAddon commitlog mailing list|FGAddon commitlog mailing list]], you may see a large number of unrecognisable characters. This is the result of what is known as a binary diff, showing the binary file differences as if it were text. Although this is not a issue for the operation of the repository, the situation is an aesthetic problem which makes it more difficult to perform a review of the changes.

To fix the problem, firstly the binary files with the <code>svn:mime-type</code> property missing need to be identified. The following subversion command can be used:
<syntaxhighlight lang="bash">
svn propget svn:mime-type <file_name>
</syntaxhighlight>

As it can be tedious checking each file individually, the following Python script simplifies and automates the process to identify all binary files with a mime-type issue:

{{collapsible script
| type = Python 2/3 script
| title = Find binary files with no <code>svn:mime-type</code> property set.
| intro = The following script is based on blacklisting text files. Hence false positives are to be expected, and the blacklists can be expanded as needed.
| lang = python
| script =
#! /usr/bin/env python

from os import getcwd, walk
from os.path import join, splitext
from re import search
from subprocess import PIPE, Popen

skip_txt_file_seg = [
'authors',
'copying',
'licen',
'readme'
]

skip_txt_ext = [
'ac',
'css',
'dat',
'eff',
'frag',
'html',
'json',
'log',
'nas',
'osgx',
'svg',
'tex',
'txt',
'vert',
'xhtml',
'xml',
'xsl'
]

skip_bin_prop = [
'application/octet-stream',
'application/pdf',
'application/postscript',
'application/x-dosexec',
'application/x-gzip',
'application/zip',
'audio/x-wav',
'image/gif',
'image/jpeg',
'image/png',
'image/vnd.adobe.photoshop',
'image/tiff',
'image/x-ms-bmp',
'image/x-xcf',
]

# Walk through the directories.
for root, dirs, files in walk(getcwd()):
# Loop over the files in the current directory.
for file in files:
# Skip known text files.
skip = False
for i in range(len(skip_txt_file_seg)):
if search(skip_txt_file_seg[i], file.lower()):
skip = True
if skip:
continue

# The file extension.
file_path, ext = splitext(file)
ext = ext[1:].lower()

# Skip known text file extensions.
if ext in skip_txt_ext:
continue

# The full file path.
path = join(root, file)

# Query the file for svn:mime-type.
cmd = 'svn propget svn:mime-type \"%s\"' % path
pipe = Popen(cmd, shell=True, stdin=PIPE, stdout=PIPE, stderr=PIPE, close_fds=False)
props = []
for line in pipe.stdout.readlines():
props.append(line.strip())

# Byte array conversion (Python3).
for i in range(len(props)):
if hasattr(props[i], 'decode'):
props[i] = props[i].decode()

# Skip binary svn:mime-type values.
if len(props) and props[0] in skip_bin_prop:
continue

# Printout.
if not len(props):
print("%s" % path)
else:
print("%s svn:mime-type=%s" % (path, props[0]))
}}

==== Fixing the problem ====

As [[#Subversion_properties|git-svn cannot set or change]] the <code>svn:mime-type</code> property, a [[#Repository_checkout|svn checkout copy]] of the aircraft is required. The property can then be set to the default Subversion binary mime-type with:
<syntaxhighlight lang="bash">
svn propset svn:mime-type "application/octet-stream" <file_name>
</syntaxhighlight>

Alternatively, the following set of shell commands can be used to automate the process:
{{collapsible script
| type = Shell commands
| title = Set specific <code>svn:mime-type</code> values on a set of known binary files.
| intro = These shell commands will work on GNU/Linux or Mac OS X systems (or on Windows if using cygwin, or if a find command line tool is installed). The list of file types here are those most commonly found in FGAddon. To set the property on a list of binary files, type (or copy and paste):
| lang = bash
| script =
find -iname "*.wav" -exec svn propset svn:mime-type "audio/x-wav" {} \;
find -iname "*.bmp*" -exec svn propset svn:mime-type "image/x-ms-bmp" {} \;
find -iname "*.gif" -exec svn propset svn:mime-type "image/gif" {} \;
find -iname "*.jpg" -exec svn propset svn:mime-type "image/jpeg" {} \;
find -iname "*.png*" -exec svn propset svn:mime-type "image/png" {} \;
find -iname "*.psd" -exec svn propset svn:mime-type "image/vnd.adobe.photoshop" {} \;
find -iname "*.tif" -exec svn propset svn:mime-type "image/tiff" {} \;
find -iname "*.xcf" -exec svn propset svn:mime-type "image/x-xcf" {} \;
find -iname "*.rgb*" -exec svn propset svn:mime-type "application/octet-stream" {} \;
find -iname "*.au" -exec svn propset svn:mime-type "application/octet-stream" {} \;
find -iname "*.*af" -exec svn propset svn:mime-type "application/octet-stream" {} \;
find -iname "*.3ds" -exec svn propset svn:mime-type "application/octet-stream" {} \;
find -iname "*.blend*" -exec svn propset svn:mime-type "application/octet-stream" {} \;
find -iname "*.dds" -exec svn propset svn:mime-type "application/octet-stream" {} \;
find -iname "*.od[gst]" -exec svn propset svn:mime-type "application/octet-stream" {} \;
find -iname "*.onetoc2" -exec svn propset svn:mime-type "application/octet-stream" {} \;
find -iname "*.xlsx" -exec svn propset svn:mime-type "application/octet-stream" {} \;
find -iname "*.pdf" -exec svn propset svn:mime-type "application/pdf" {} \;
find -iname "*.ps" -exec svn propset svn:mime-type "application/postscript" {} \;
find -iname "*.gz" -exec svn propset svn:mime-type "application/x-gzip" {} \;
find -iname "*.mdl" -exec svn propset svn:mime-type "application/x-dosexec" {} \;
find -iname "*.zip" -exec svn propset svn:mime-type "application/zip" {} \;
| conc = Other binary files can safely be set to <code>"application/octet-stream"</code>, the Subversion default for binary files.
}}

== SourceForge developer services ==

The FlightGear project is hosted on the SourceForge open source infrastructure. This developer services section will highlight some of the useful tools you can take advantage of. SourceForge consists of two categories of services:
; Project infrastructure : The FlightGear project uses the project services of SourceForge. These services are for standalone software projects.
; Developer infrastructure : These are services available to anyone with a SourceForge account, and are available via your SourceForge homepage and accessible to all. This includes being able to create multiple version control repositories (svn, git, hg), wikis, forums, development teams, blogs, and ticket trackers (for bugs, support requests, tasks, etc.).

Rather than creating a new project, any development for the FlightGear project should be based on the developer infrastructure.

=== Developer git repository ===

To set up your own remote git repository, here for developing the FGAddon fkdr1 aircraft:
* On your profile page at <span style="color: blue"><tt><nowiki>https://sourceforge.net/u/<username>/profile/</nowiki></tt></span>, go to <code>Admin</code> -> <code>Add New</code> -> <code>Git</code>.
* Set label to <code>fkdr1 FGAddon git-svn repository</code>.
* Set the code path to <code>code-fkdr1</code>. The <code>code-*</code> prefix is to differentiate this from the <code>forum-*</code>, <code>wiki-*</code>, and other directories.

The repository will be located at <span style="color: blue"><tt><nowiki>https://sourceforge.net/u/<username>/code-fkdr1/ci/master/tree/</nowiki></tt></span>.

=== Development teams ===

If you and a group of friends would like to privately develop one of the FGAddon aircraft as a team, assuming that the you have contacted the original aircraft authors and the aircraft is not actively being developed, then you should create a SourceForge development team. A team leader should be appointed to set this up under their SourceForge account. Assuming you wish to develop the "ornithopter" aircraft, the steps are:

* Go to <code>Personal tools</code> -> <code>Admin</code>.
* Click on <code>User Permissions</code>.
* Click on <code>Add a new group</code> at the bottom.
* Set the name to <code>ornithopter</code>, and save.
* Click on <code>Add</code> in the <code>ornithopter</code> group and add the SourceForge names of all your team members.

After setting up a private repository in the team leader's account, as described below, then the development team should be set up for the repository.

* Go to the repository under your SourceForge account.
* Click on <code>Admin - <repository name></code>, then select <code>Permissions</code>.
* In the <code>Write</code> section, remove <code>Developer</code> and add <code>ornithopter</code>.
* Click on <code>Save</code>.

The development team will then have commit access to the private repository.

=== Team communications ===

To help with team development, the SourceForge infrastructure allows for multiple [https://sourceforge.net/p/forge/documentation/Discussion/ dedicated discussion forums] to be created. This can either be within a SourceForge project or under a SourceForge users homepage. This allows the team leader to create a forum dedicated solely to the development of the aircraft of interest. Continuing with the <code>ornithopter</code> example, the steps for the team leader are simple:

* On your profile page at <span style="color: blue"><tt><nowiki>https://sourceforge.net/u/<username>/profile/</nowiki></tt></span>, go to <code>Personal tools</code> -> <code>Admin</code>.
* Click on the <code>Tools</code> option in the left hand menu.
* Click on <code>Discussion</code> in the <code>Click to install</code> section.
* Change the label to <code>Ornithopter forum</code>, and the path to <code>forum-ornithopter</code>, for example. The <code>forum-*</code> prefix is to differentiate this from the <code>code-*</code>, <code>wiki-*</code>, and other directories.
* Click on <code>Save</code>.

More details are given on the [https://sourceforge.net/p/forge/documentation/Discussion/ SourceForge Discussion documentation].

== Development scenarios ==

=== Individual developer ===

{{Note|Development scenario: You are an individual developer and will use the native Subversion tools.}}

This is by far the simplest development scenario and should be used in most cases. If you are using the command line Subversion client, you can checkout an individual aircraft with:
{{#tag:syntaxhighlight|
{{fgaddon co
| login = <username>
| path = Aircraft/wrightFlyer1903
| post =
}}
| lang = "sh"
}}

Where <code><username></code> is your SourceForge user name. Alternatively you can checkout all aircraft with:
{{#tag:syntaxhighlight|
{{fgaddon co
| login = <username>
| post = flightgear-fgaddon
}}
| lang = "sh"
}}

If you do not have commit access, type one of:
{{#tag:syntaxhighlight|
{{fgaddon co
| path = Aircraft/wrightFlyer1903
| post =
}}
{{fgaddon co
| post = flightgear-fgaddon
}}
| lang = "sh"
}}

To use the new local svn repository, see the [[#Subversion|subversion instructions]].

=== Individual developer (git-svn) ===

{{Note|Development scenario: You are an individual developer and will use the git-svn tools.}}

This is more complicated than using the native SVN tools, but can be useful without having FGAddon commit access, as multiple local commits can be made to be sent to the original aircraft authors or to the development mailing list/forum. To clone the aircraft of choice into a new git repository, type:
{{#tag:syntaxhighlight|
{{fgaddon source|cmd=git svn clone|protocol=svn+ssh|login=<username>|type=svn|path=Aircraft/<aircraft>|full=1}}
| lang = "sh"
}}

Where <code><username></code> is your infrastructure user name and <code><aircraft></code> is the directory name in the FGAddon repository. This is valid whether or not you have commit permissions.

To use the new local git repository, see the [[#Git-svn|git-svn instructions]] and [[#Deficiencies_of_git-svn|its deficiencies]].

==== Upload to Sourceforge ====

To share the local developments, the changes can be uploaded to a remote git repository on the SourceForge infrastructure. For this, a [[#Developer_git_repository|developer git repository]] should first be set up under your SourceForge profile. Then add this as a remote:
{{#tag:syntaxhighlight|
{{sourceforge url|cmd=git remote add|opt=origin|protocol=ssh|login=<username>|user=<username>|type=git|repo=code-<aircraft>}}
| lang = "sh"
}}

And send the master branch where developments are located with:
<syntaxhighlight lang="bash">
git push --set-upstream origin master
</syntaxhighlight>

The changes in the new repository will be visible via the web interface at {{#tag:span|{{#tag:tt|{{#tag:nowiki|{{sourceforge url|user=<username>|repo=code-<aircraft>|branch=master}}}}}}| style="color: blue"}}.

=== Sending external git repository changes into FGAddon ===

{{Note|Development scenario: You are an individual developer with FGAddon commit access and wish to transfer the commits in a remote git repository into FGAddon using a temporary local git repository.}}

Firstly clone the FGAddon aircraft into a local git-svn repository with:
{{#tag:syntaxhighlight|
{{fgaddon source|cmd=git svn clone|protocol=svn+ssh|login=<username>|type=svn|path=Aircraft/<aircraft>|full=1}}
| lang = "sh"
}}

This will create a new local git repository linked to FGAddon via git-svn. If the aircraft is new and not present in FGAddon, see the [[#New_aircraft|instructions for adding a new aircraft to FGAddon]]. Next, set up the remote git repository as a remote, and fetch it:
<syntaxhighlight lang="bash">
git remote add <name> <url>
git fetch
</syntaxhighlight>

Where <code><url></code> is the URL of the remote git repository. Finally make an ordered list of all hashes of the commits to be sent into FGAddon, from earliest to latest, and cherry-pick them into the git-svn master branch:
<syntaxhighlight lang="bash">
git cherry-pick <commit hash 1>
git cherry-pick <commit hash 2>
git cherry-pick <commit hash 3>
...
</syntaxhighlight>

Note that the git-svn local repository should only have a single <code>master</code> branch and only consist of cherry-picking. To see the changes queued for sending to FGAddon:
<syntaxhighlight lang="bash">
git log git-svn..HEAD
git diff git-svn..HEAD
</syntaxhighlight>

Then to send the changes to FGAddon, firstly pull in any remote changes, and send the commits:
<syntaxhighlight lang="bash">
git svn rebase
git svn dcommit
</syntaxhighlight>

The temporary local repository can then be deleted.

=== Connecting an existing git repository to FGAddon ===

{{Note|Development scenario: You are an individual developer or team leader with FGAddon commit access and wish to connect a pre-existing remote git repository with FGAddon to send all changes back to FGAddon.}}

If a remote git repository containing a developed aircraft already exists, it is possible to connect it to the remote FGAddon repository using the git-svn tools. The following uses the [[#Dedicated_FGAddon_branch|dedicated FGAddon branch technique]]. Firstly, set up the bridge to FGAddon using git-svn in the per-aircraft repository:
{{#tag:syntaxhighlight|
{{fgaddon source|cmd=git svn init|protocol=svn+ssh|login=<username>|type=svn|path=Aircraft/<aircraft>|full=1}}
| lang = "sh"
}}

Where <code><aircraft></code> is the aircraft directory name in FGAddon. Note that this step can be performed without commit access to FGAddon by using a read-only SVN URL instead, but then changes cannot be pushed back to FGAddon ([[#Synchronising|dcommitting]], as it is known in the git-svn terminology). However, this allows upstream FGAddon changes to be integrated into the remote git repository, thus making it easy to prepare changes for submission for FGAddon inclusion using patches sent to the mailing list or sent via other channels.

Now fetch the current state from the remote FGAddon repository:
<syntaxhighlight lang="bash">
git svn fetch
</syntaxhighlight>

The downloaded SVN history is in the remote branch <code>remotes/git-svn</code>. To commit changes to SVN you need a local branch that tracks this remote branch. Create a local <code>fgaddon</code> branch that you will use to commit updates:
<syntaxhighlight lang="bash">
git branch fgaddon remotes/git-svn
</syntaxhighlight>

After committing new stuff to the <code>master</code> branch, to push to FGAddon checkout the <code>fgaddon</code> branch and update it from SVN in case someone else has touched the aircraft in the remote FGAddon repository:
<syntaxhighlight lang="bash">
git checkout fgaddon
git svn rebase
</syntaxhighlight>

Cherry-pick the new commits from <code>master</code> to <code>fgaddon</code> to preserve a linear history:
<syntaxhighlight lang="bash">
git cherry-pick <commit hash 1>
git cherry-pick <commit hash 2>
git cherry-pick <commit hash 3>
...
</syntaxhighlight>

To see the changes queued for sending to FGAddon as either commits or a diff, type:
<syntaxhighlight lang="bash">
git log git-svn..HEAD
git diff git-svn..HEAD
</syntaxhighlight>

If everything looks ok, dcommit the local commits on the <code>fgaddon</code> branch to send them to the remote FGAddon SVN repository:
<syntaxhighlight lang="bash">
git svn dcommit
</syntaxhighlight>

Switch back to the master branch for local development:
<syntaxhighlight lang="bash">
git checkout master
</syntaxhighlight>

To get changes from upstream you can either just download them with
<syntaxhighlight lang="bash">
git svn fetch
</syntaxhighlight>

or download them and rebase your <code>fgaddon</code> branch onto them:
<syntaxhighlight lang="bash">
git checkout fgaddon
git svn rebase
</syntaxhighlight>

=== Team development ===

{{Note|Development scenario: All members of the team are acting as gatekeepers, and all commits are made directly to FGAddon, either using svn or git-svn.}}

The simplest way to work as a team is for each developer to either have a [[#Individual developer|svn copy of FGAddon]] or a [[#Individual developer (git-svn)|git-svn copy of FGAddon]], and everyone commits directly to FGAddon. Communication and coordination between the team members can be performed using a [[#Team_communications|team leader organised SourceForge forum]] or using the [http://forum.flightgear.org/ FlightGear forum]. In this scenario, the team needs to take the initiative and everyone apply for FGAddon commit access.

=== Private team development (git-svn) ===

{{Note|Development scenario: One team leader is acting as the gatekeeper on a private git repository hosted on the in-house SourceForge infrastructure, using git-svn to push a fgaddon branch to FGAddon, with team members committing directly to the private git repository or making merge requests from their fork of the private repository.}}

To keep everything in-house, the entire operation will be based on the official infrastructure and remote repositories under each user's SourceForge (SF) profile. Note to the team leader - you must [https://git-scm.com/book/en/v1/Git-and-Other-Systems-Git-and-Subversion#git-svn keep your git-svn history linear] (meaning that a [[#Dedicated_FGAddon_branch|dedicated FGAddon branch]] should be created and changes manually cherry-picked into this branch). In the following, the <code>ornithopter</code> aircraft will be used as an example.

==== The team ====

Firstly, the entire team should sign up for [[#SourceForge account|SourceForge accounts]].

==== Team leader ====

===== Private repository set up =====

These steps are to be taken by the team leader. In your SourceForge user profile, set up a [[#Developer_git_repository| git repository]] with the label <code>Ornithopter FGAddon git-svn repository</code> and code path <code>code-ornithopter</code>. Then create a empty local git repository:
<syntaxhighlight lang="bash">
$ mkdir ornithopter
$ cd ornithopter
$ git init
</syntaxhighlight>

Link the empty repository to the <code>ornithopter</code> aircraft directory in the remote FGAddon repository and pull it in with:
{{#tag:syntaxhighlight|
$ {{fgaddon source|cmd=git svn init|protocol=svn+ssh|login=<username>|type=svn|path=Aircraft/ornithopter|full=1}}
$ git svn fetch
| lang = "sh"
}}

Replace <code><username></code> with your SF user name. Set up a special git-svn branch for FGAddon gatekeeping and dcommitting changes back to the repository:
<syntaxhighlight lang="bash">
$ git branch fgaddon remotes/git-svn
$ git checkout fgaddon
</syntaxhighlight>

And pull in the <code>ornithopter</code> from FGAddon:
<syntaxhighlight lang="bash">
$ git svn rebase
</syntaxhighlight>

To see the current local git-svn repository setup, type:
<syntaxhighlight lang="bash">
$ git branch -vva
$ git remote -v
$ git svn info
</syntaxhighlight>

Then return to the master branch:
<syntaxhighlight lang="bash">
$ git checkout master
</syntaxhighlight>

Finally, set up the remote git repository as a remote:
{{#tag:syntaxhighlight|
$ {{sourceforge url|cmd=git remote add|opt=origin|protocol=ssh|login=<username>|user=<username>|type=git|repo=code-ornithopter}}
| lang = "sh"
}}

And send the master branch to the remote git repository:
<syntaxhighlight lang="bash">
$ git push -u origin master
</syntaxhighlight>

To see the new set up:
<syntaxhighlight lang="bash">
$ git branch -vva
$ git remote -v
</syntaxhighlight>

The repository will be located at {{#tag:span|{{#tag:tt|{{#tag:nowiki|{{sourceforge url|user=<username>|repo=code-ornithopter|branch=master}}}}}}| style="color: blue"}}. Note that the git-svn information stored in the <code>.git/svn</code> directory will not be pushed to remote SoureForge repository, and therefore the link back to FGAddon will only be present in the local copy of the team leader. The git-svn link can be re-established at a later point if necessary.

===== Team setup =====

Set up a [[#Development teams|dedicated development team and grant them access to the git-svn repository]].

===== Pushing to FGAddon =====

Committing to FGAddon is for the local git repository of the team leader. History must be linear in the fgaddon branch, so cherry-picking is the way to go. This is from the [[#Individual developer (git-svn)|Individual developer (git-svn)]] section. In the local git repository, switch to the <code>fgaddon</code> branch:
<syntaxhighlight lang="bash">
git checkout fgaddon
</syntaxhighlight>

Pull in any changes which have occurred in FGAddon:
<syntaxhighlight lang="bash">
git svn rebase
</syntaxhighlight>

To see the commits in the <code>master</code> branch which are not in the <code>fgaddon</code> branch, type one of:
<syntaxhighlight lang="bash">
git log HEAD..master
git log HEAD..master --pretty=oneline
</syntaxhighlight>

Manually select the commits to be sent to FGAddon and cherry-pick them:
<syntaxhighlight lang="bash">
git cherry-pick <commit hash 1>
git cherry-pick <commit hash 2>
git cherry-pick <commit hash 3>
...
</syntaxhighlight>

Or to cherry-pick a range of commits:
<syntaxhighlight lang="bash">
git cherry-pick <commit hash 1>^..<commit hash 8>
</syntaxhighlight>

Then check what is to be sent:
<syntaxhighlight lang="bash">
git log git-svn..HEAD
git diff git-svn..HEAD
</syntaxhighlight>

Send the changes to FGAddon, send the git <code>fgaddon</code> branch changes to the remote git repository, and switch back to the master branch:
<syntaxhighlight lang="bash">
git svn dcommit
git push
git checkout master
</syntaxhighlight>

Finally merge in the git svn commits with their new hashes from the <code>fgaddon</code> branch, and send it to the remote git repository:
<syntaxhighlight lang="bash">
git merge fgaddon
git push
</syntaxhighlight>

==== Team members ====

===== Working with the repository =====

Each team member should make a clone of the private git repository:
{{#tag:syntaxhighlight|
$ {{sourceforge source|cmd=git clone|protocol=ssh|login=<username>|user=<username_leader>|type=git|repo=code-ornithopter|post=ornithopter|full=1}}
| lang = "sh"
}}

Replace <code><username></code> with your SourceForge user name, and <code><username_leader></code> is the SourceForge user name of the team leader.

===== Forking and merge requests =====

Alternatively, each team member can fork the git repository under your SourceForge account:
* Go to {{#tag:span|{{#tag:tt|{{#tag:nowiki|{{sourceforge source|user=<username>|repo=code-ornithopter|branch=master|full=1}}}}}}| style="color: blue"}}, where <code><username></code> is the SourceForge user name of the team leader.
* Click on <code>Fork</code>.
* Set the mount point to <code>code-ornithopter</code> and change the label as you wish.

Develop and push to your fork, then make merge requests by clicking on the <code>Request Merge</code> button.

== References ==
<references/>

[[Category:FlightGear]]

[[de:FGAddon]]
[[fr:FGAddon]]

Mikoyan-Gurevich MiG-15

2016-02-20T12:25:08Z

Circumn: FDM rating = 4

{{infobox Aircraft
|name = MiG-15bis
|image = MiG-15bis-Interior.jpg
|type = subsonic jet fighter
|livery = USSR 60x standart
|fdm = JSBsim
|status = beta (v20102909)
|authors = Lee Elliott: initial 3d model,
Victor Slavutinsky : Everything else,
Ludovic Brenta, Andreas Zenner: version 3 and beyond
|fgname = MiG-15bis
|status-fdm=4
|status-systems=4
|status-cockpit=4
|status-model=4
}}
The real [http://en.wikipedia.org/wiki/Mig-15 '''MiG-15bis'''] is the most produced aircraft of its type, and it made a great impact in its time. It must have been the most known Russian fighter in the West.

Aim of MiG-15bis FG project is to reproduce the real aircraft restrictions, habits, and features, exactly in that sequence.

Firstly, this mid-50's fighter doesn't have many switches, but without switching them correctly you cannot take off. If forgotten, gears will stick or be sheared off at high speeds (which this aircraft is capable of reaching).Much like the real craft, the engines can be overheated, and can be turned off by bringing the throttle all the way down.

Secondly, it is a jet, but not a modern supersonic fighter with reheated engine. At subsonic speeds it starts to act oddly in reality as well as in simulation.

Thirdly, if you can deploy the landing gear of the real MiG by an emergency procedure which includes lever, handles, and valve. The same goes for this jet. Again, there aren't as many switches as in a modern airliner. But every switch behaves as it does in reality.

The rest of what you need to know to fly this FG model is in included in its documentation. Read it carefully before takeoff.

I hope that this will make you want to learn more about the real MiG-15.

I wish you a good flight!

Victor Slavutinsky, vitosnet@mail.ru.

== Airplane of the Week/Month ==

The MiG-15bis was reviewed as 'Airplane of the Week/Month' on June 9, 2011 as follows:

<b>Model</b>

In my opinion, the MiG-15bis has one of the best 3d cockpits of all Flightgear aircraft. Not only are all gauges specially designed with cyrillic letters for this plane, but also details like the low throttle safer are done in full 3d beauty. In addition to the main panel, there are also two fully functional side panels in the cockpit.

[[File: Mig15bis-cockpit.jpg]]

The exterior model is not done quite with the same impressive level of detail, visible from the interior e.g. in the somewhat rough lines of the canopy, but also shows a lot of detail, e.g. surface bumps, nice animations for canopy, gear, flaps and brakes, or the glow and smoke of the running engine.

[[File: Mig15bis-model.jpg]]

The MiG-15bis is one of the planes where reading the (very detailed) manual is necessary even to start the engine - the startup procedure is fairly complicated. But it doesn't stop here - there are also procedures simulated for engine restart in mid-air, for emergency gear and for emergency flaps extraction.

In addition, the plane comes with a full set of functioning weapons and a photo-camera, so both 'real' and mock dogfighting is quite possible, and the two droptanks can be used for bombing practice if so desired.

<b>Flight characteristics</b>

The JSBSim FDM of the MiG-15bis is quite smooth, and all in all the plane is not difficult to fly. It is very agile and has a mild stall characteristics (I couldn't get it to do anything ugly with me). In high-g turns, it loses energy rapidly, illustrating nicely that the MiG-15bis is not really a match for more modern jet fighters such as the F-16, but its climb rate and velocity also demonstrate well why jet fighters quickly won the Korean skies.

What is perhaps most interesting about the MiG-15bis is that the model simulates quite a lot of restrictions - flaps and gear break when the airspeed is too high, the plane itself breaks for too high g-loads and the engine can overheat and shut off. The latter point actually spoils the fun taking off after having finally mastered the engine startup - if you climb out full throttle, you may need to look up on the mid-air engine restart procedure more quickly than you thought...

Also the gear load limits are fairly restrictive - it requires some work to bring the plane down in one piece, one can't simply smash it onto the runway. In difficult winds, that can be a real problem, but since the plane handles usually well, it's worth practicing.

<b>My personal wishlist</b>

A bit more tolerant gear would be nice... and some texture details on the canopy itself.

<b>Things to experience</b>

There's lots of details to experience. The MiG has an arrestor lever for the throttle to prevent it from moving on its own at high-g. That's not just for fun - the throttle does move on its own when the lever isn't used! Also, try flying into the transonic regime and experience how the flight dynamics changes.

== Changelog summary ==

=== Version 2.0 by Victor Slavutinsky ===

* [http://users.flightgear.ru/vitos/MiG-15.zip MiG-15bis]
* [http://users.flightgear.ru/vitos/MiG-15_Skin.zip MiG-15bis livery .xcf source files ]

=== Version 3.x by Ludovic Brenta and Andreas Zenner ===

* [https://sourceforge.net/p/flightgear/fgaddon/HEAD/tree/trunk/Aircraft/MiG-15 Development version in FGAddon]

* Livery support: Soviet Air Force (original) and Czech aerobatic team
* [[Bombable]] support: take those B-17s down with a single shell of your 37 mm cannon but beware of their M2 machine guns! Also suitable for dogfighting with other Bombable-enabled aircraft over multiplayer
* The FDM is now even more realistic
* Improved, seamless exterior model
* Explain failures with on-screen messages so you can learn from your mistakes
* Show the vertical speed of each wheel on touch down
* Option to disable realistic failures, for beginners
* True airspeed indicator
* Assorted bug fixes: replay support, fgrun preview, cannon shell ballistics, etc.

== External links ==
* [http://en.wikipedia.org/wiki/Mig-15 Wikipedia]
* [http://www.airwar.ru/enc/fighter/mig15bis.html Airwar.ru]

{{Mikoyan-Gurevich}}

[[Category:Military aircraft]]

Changelog 2016.1

2016-02-19T19:09:39Z

Circumn: Use titles instead of bold: this introduces a table of contents. Add 757, 767, P130UL and a few words about the major changes in some aircraft

{{draft|changelog|Please feel free adding screenshots and/or videos that are suitable to highlight some of the developments mentioned in this changelog, thank you!}}

The FlightGear development team is delighted to announce the v2016.1 "San Francisco" release of FlightGear, the free, open-source flight simulator. This new version contains many exciting new features, enhancements and bugfixes. Highlights in this release include an integrated launcher that includes the ability to download aircraft, a reduction in the installation package size, performance improvements and many rendering improvements.

Founded in 1997, FlightGear is developed by a worldwide group of volunteers, brought together by a shared ambition to create the most realistic flight simulator possible that is free to use, modify and distribute. FlightGear is used all over the world by desktop flight simulator enthusiasts, for research in universities and for interactive exhibits in museums.

FlightGear features more than 500 aircraft, a worldwide scenery database, a multiplayer environment, detailed sky and weather modelling, a flexible and open aircraft modelling system, varied networking options, multiple display support, a powerful scripting language and an open architecture. Best of all, being open-source, the simulator is owned by the community and everyone is encouraged to contribute.

Download FlightGear v2016.1 for free from [http://www.flightgear.org/ FlightGear.org].

FlightGear – Fly Free!

[[File:Qt launcher for FlightGear 3.5 on Windows 7.jpg|thumb|The aircraft page of the Qt launcher for FlightGear 3.5 as rendered on Windows 7.]]

= Project Organization =

* The base package has been reduced in size to 1.3 GB and moved to http://sourceforge.net/p/flightgear/fgdata/. All aircraft except the [[Cessna 172P]] and [[UFO]] have been removed.
* All core repositories have been moved to SourceForge. They can be found at https://sourceforge.net/projects/flightgear/.
* Release are now planned to be quarterly (instead of biannually). The new release number (2016.1) reflects this change: the release numbering format is changed to <code><nowiki>[Year].[Release within year].[Fix Release]</nowiki></code>. We also plan to change the default airport and the scenery that is included with the install image with each release. 2016.1 uses the [[KSFO]] default as we have done for many years, and so has the codename "San Francisco."

= Major enhancements =
== Core ==
* Interactive traffic system re-enabled, having been disabled by mistake some releases previously.
* Various security improvements, including the disabling of <tt>system.fgfsrc</tt>.
* Reduction in the memory footprint due to scenery.
* Improved performance when displaying large numbers of scenery objects.

== Aircraft Modeling ==
* [[Tooltips]] can now be positioned at a specific place on-screen.
* [[Wingflexer|Wing flex]] module added, controllable via [[Nasal]] or [[Property rules]].
* Bug-fixes and improvements to the [[Failure Manager]].
* <code><variant-of></code> tag in the [[aircraft-set.xml]] file has been added (see [[FlightGear Newsletter March 2015]]).
* Automatic checklist execution, which can, for example, be used for autostart.
* 8.33 kHz spacing is now supported on comms radios.

== JSBSim ==
* Sync with the latest version of [[JSBSim]].
* The pitot angle can now be tweaked with the <code><pitot_angle></code> tag in the <code><metrics></code> block.
* The refuel rate is now configurable with the <code><refuel-rate></code> tag in the <code><propulsion></code> block.

== Rendering ==
* Improved vegetation including 3D grass and shadows for trees
* Better cockpit rendering:
** Interior shadows
** Glass reflections, dynamical raindrops, fogging and frosting
** Panel backlighting
** Irradiance mapping for more realistic distribution of indirect light
** Diffuse illumination of the interior by instrument lighting
* New thruster effect (can be used for afterburners flames, rockets, etc.).
* Lightning strikes illuminating the surrounding clouds during thunderstorms
* Rainbows
* Improved airport rendering, including runway skid marks and better effects for the runways and surrounding grass.
* Optical phenomena in icy hazes:halos, sundogs, parhelic ring and light pillar.
* Aurora Borealis at night
* More realistic rendering of generic lights (runway, PAPI, taxiway, etc.)
* Detailed procedurally generated lights for aircraft
* A dynamical wingflex shader suitable for wing beats (see the [[Dragon]])

== Usability ==
* Many improvements to [[Phi]], the built-in web interface.
* GUI cleanup to improve support for multiple GUI styles.
* The [[Integrated Qt5 Launcher|built-in Qt launcher]] is available for all of FlightGear's supported operating systems.
* Additional latitude and longitude formats are now supported in the HUD.

== Scenery ==
* Regional texture definitions for Florida, Brazil, Latin America, Africa, the Middle East and Southeastern Asia.
* <tt>stgmerge</tt> tool added to merge objects in a scenery tile into a smaller number of meshes.

= In the hangar =
== Aircraft with major enhancements ==
* Complete refresh of the default [[Cessna 172P]], including engine options, various tire sizes and floats.
* Major enhancements to the [[Space Shuttle]]. The Shuttle can be flown as per the Crew Operations Manual from launch to touchdown.

The following aircraft have also received significant updates:

* [[McDonnell Douglas F-15 Eagle]]
* [[Rockwell B-1B Lancer]]
* [[Saab JA-37 Viggen]]
* [[Cessna 550 Citation II]]
* [[Lockheed Constellation]]
* [[Boeing 737-300]]
* [[Mirage 2000-5]]
* [[De Havilland Canada DHC-6 Twin Otter]]
* [[Mikoyan-Gurevich_MiG-15|MiG-15]] (now supports [[Bombable]], ultra-realistic FDM)
* [[Bombardier CRJ700 series]]
* [[Boeing 757]]: new variants 757-300 and C-32B, complementing the existing 757-200 and C-32A

== New aircraft ==

* A [[dragon]] has been added, complete with fire breath.
* [[Beagle Pup]]
* [[Pottier_P130_UltraLight|Pottier 130 Utra Light]]
* [[Boeing 767]]

= Misc/uncategorized =
* Improved support for KDI572-574 [[DME]] equipment.
* Update to the [http://www.ngdc.noaa.gov/geomag/WMM/DoDWMM.shtml World Magnetic Model] 2015.

= Nasal Scripting =
* Global functions <code>createViaTo()</code> and <code>createDiscontinuity()</code> {{flightgear commit|caead6|t=added}}
* <code>activate()</code> method {{flightgear commit|caead6|t=added}} to the <code>flightplan</code> ghost object

= Documentation =
* The [[FlightGear Manual]] is now available in Chinese.

= Bug fixes =
* See [http://sourceforge.net/p/flightgear/codetickets/search/?q=status%3AFixed+AND+created_date%3A%5B2015-09-23T23%3A11%3A56Z+TO+*%5D our bugtracker] for a list, albeit incomplete, of the bugs fixed in this release.

[[Category:FlightGear changelogs]]
[[Category:New Versioning Scheme]]

Mikoyan-Gurevich MiG-15

2016-02-18T23:28:12Z

Circumn: Update for version 3.x, provide download link to FGAddon, keep the old link intact

{{infobox Aircraft
|name = MiG-15bis
|image = MiG-15bis-Interior.jpg
|type = subsonic jet fighter
|livery = USSR 60x standart
|fdm = JSBsim
|status = beta (v20102909)
|authors = Lee Elliott: initial 3d model,
Victor Slavutinsky : Everything else,
Ludovic Brenta, Andreas Zenner: version 3 and beyond
|fgname = MiG-15bis
|status-fdm=3
|status-systems=4
|status-cockpit=4
|status-model=4
}}
The real [http://en.wikipedia.org/wiki/Mig-15 '''MiG-15bis'''] is the most produced aircraft of its type, and it made a great impact in its time. It must have been the most known Russian fighter in the West.

Aim of MiG-15bis FG project is to reproduce the real aircraft restrictions, habits, and features, exactly in that sequence.

Firstly, this mid-50's fighter doesn't have many switches, but without switching them correctly you cannot take off. If forgotten, gears will stick or be sheared off at high speeds (which this aircraft is capable of reaching).Much like the real craft, the engines can be overheated, and can be turned off by bringing the throttle all the way down.

Secondly, it is a jet, but not a modern supersonic fighter with reheated engine. At subsonic speeds it starts to act oddly in reality as well as in simulation.

Thirdly, if you can deploy the landing gear of the real MiG by an emergency procedure which includes lever, handles, and valve. The same goes for this jet. Again, there aren't as many switches as in a modern airliner. But every switch behaves as it does in reality.

The rest of what you need to know to fly this FG model is in included in its documentation. Read it carefully before takeoff.

I hope that this will make you want to learn more about the real MiG-15.

I wish you a good flight!

Victor Slavutinsky, vitosnet@mail.ru.

== Airplane of the Week/Month ==

The MiG-15bis was reviewed as 'Airplane of the Week/Month' on June 9, 2011 as follows:

<b>Model</b>

In my opinion, the MiG-15bis has one of the best 3d cockpits of all Flightgear aircraft. Not only are all gauges specially designed with cyrillic letters for this plane, but also details like the low throttle safer are done in full 3d beauty. In addition to the main panel, there are also two fully functional side panels in the cockpit.

[[File: Mig15bis-cockpit.jpg]]

The exterior model is not done quite with the same impressive level of detail, visible from the interior e.g. in the somewhat rough lines of the canopy, but also shows a lot of detail, e.g. surface bumps, nice animations for canopy, gear, flaps and brakes, or the glow and smoke of the running engine.

[[File: Mig15bis-model.jpg]]

The MiG-15bis is one of the planes where reading the (very detailed) manual is necessary even to start the engine - the startup procedure is fairly complicated. But it doesn't stop here - there are also procedures simulated for engine restart in mid-air, for emergency gear and for emergency flaps extraction.

In addition, the plane comes with a full set of functioning weapons and a photo-camera, so both 'real' and mock dogfighting is quite possible, and the two droptanks can be used for bombing practice if so desired.

<b>Flight characteristics</b>

The JSBSim FDM of the MiG-15bis is quite smooth, and all in all the plane is not difficult to fly. It is very agile and has a mild stall characteristics (I couldn't get it to do anything ugly with me). In high-g turns, it loses energy rapidly, illustrating nicely that the MiG-15bis is not really a match for more modern jet fighters such as the F-16, but its climb rate and velocity also demonstrate well why jet fighters quickly won the Korean skies.

What is perhaps most interesting about the MiG-15bis is that the model simulates quite a lot of restrictions - flaps and gear break when the airspeed is too high, the plane itself breaks for too high g-loads and the engine can overheat and shut off. The latter point actually spoils the fun taking off after having finally mastered the engine startup - if you climb out full throttle, you may need to look up on the mid-air engine restart procedure more quickly than you thought...

Also the gear load limits are fairly restrictive - it requires some work to bring the plane down in one piece, one can't simply smash it onto the runway. In difficult winds, that can be a real problem, but since the plane handles usually well, it's worth practicing.

<b>My personal wishlist</b>

A bit more tolerant gear would be nice... and some texture details on the canopy itself.

<b>Things to experience</b>

There's lots of details to experience. The MiG has an arrestor lever for the throttle to prevent it from moving on its own at high-g. That's not just for fun - the throttle does move on its own when the lever isn't used! Also, try flying into the transonic regime and experience how the flight dynamics changes.

== Changelog summary ==

=== Version 2.0 by Victor Slavutinsky ===

* [http://users.flightgear.ru/vitos/MiG-15.zip MiG-15bis]
* [http://users.flightgear.ru/vitos/MiG-15_Skin.zip MiG-15bis livery .xcf source files ]

=== Version 3.x by Ludovic Brenta and Andreas Zenner ===

* [https://sourceforge.net/p/flightgear/fgaddon/HEAD/tree/trunk/Aircraft/MiG-15 Development version in FGAddon]

* Livery support: Soviet Air Force (original) and Czech aerobatic team
* [[Bombable]] support: take those B-17s down with a single shell of your 37 mm cannon but beware of their M2 machine guns! Also suitable for dogfighting with other Bombable-enabled aircraft over multiplayer
* The FDM is now even more realistic
* Improved, seamless exterior model
* Explain failures with on-screen messages so you can learn from your mistakes
* Show the vertical speed of each wheel on touch down
* Option to disable realistic failures, for beginners
* True airspeed indicator
* Assorted bug fixes: replay support, fgrun preview, cannon shell ballistics, etc.

== External links ==
* [http://en.wikipedia.org/wiki/Mig-15 Wikipedia]
* [http://www.airwar.ru/enc/fighter/mig15bis.html Airwar.ru]

{{Mikoyan-Gurevich}}

[[Category:Military aircraft]]

Changelog 2016.1

2016-02-18T22:43:26Z

Circumn: Add the MiG-15 to the list of aircraft with significan improvements

{{draft|changelog|}}

The FlightGear development team is delighted to announce the v2016.1 "San Francisco" release of FlightGear, the free, open-source flight simulator. This new version contains many exciting new features, enhancements and bugfixes. Highlights in this release include an integrated launcher that includes the ability to download aircraft, a reduction in the installation package size, performance improvements and many rendering improvements.

Founded in 1997, FlightGear is developed by a worldwide group of volunteers, brought together by a shared ambition to create the most realistic flight simulator possible that is free to use, modify and distribute. FlightGear is used all over the world by desktop flight simulator enthusiasts, for research in universities and for interactive exhibits in museums.

FlightGear features more than 400 aircraft, a worldwide scenery database, a multiplayer environment, detailed sky modelling, a flexible and open aircraft modelling system, varied networking options, multiple display support, a powerful scripting language and an open architecture. Best of all, being open-source, the simulator is owned by the community and everyone is encouraged to contribute.

Download FlightGear v2016.1 for free from [http://www.flightgear.org/ FlightGear.org].

FlightGear - Fly Free!

[[File:Qt launcher for FlightGear 3.5 on Windows 7.jpg|thumb|The aircraft page of the Qt launcher for FlightGear 3.5 as rendered on Windows 7.]]

=== Major enhancements in this release ===
'''Project Organization'''
* The base package has been reduced in size to 1.3 GB and moved to http://sourceforge.net/p/flightgear/fgdata/. All aircraft except the [[Cessna 172P]] and [[UFO]] have been removed.
* All core repositories have been moved to SourceForge. They can be found at https://sourceforge.net/projects/flightgear/.
* Release are now planned to be quarterly (from the previous 6 month cycle). The new release number(2016.1) reflects this change: the release numbering format is changed to <code><nowiki>[Year].[Release within year].[Fix Release]</nowiki></code>. We also plan to change the default airport and the scenery that is included with the install image with each release. 2016.1 uses the KSFO default as we have done for many years, and so has the codename "San Francisco".

'''Core'''
* Interactive traffic system re-enabled, having been disabled by mistake some releases previously.
* Various security improvements, including the disabling of <tt>system.fgfsrc</tt>.
* Reduction in the memory footprint due to scenery
* Improved performance when displaying large numbers of scenery objects

'''Aircraft Modeling'''
* [[Tooltips]] can now be positioned at a specific place on-screen.
* [[Wingflexer|wing flex]] module added, controllable via [[Nasal]] or [[Property rules|Property Rules]].
* Bug-fixes and improvements to the [[Failure Manager]].
* <code><nowiki><variant-of></nowiki></code> tag in the [[Aircraft-set.xml|*-set.xml]] file has been added. See [[FlightGear Newsletter March 2015]].
* Automatic checklist execution, which can, for example, be used for autostart.
* 8.33 kHz spacing is now supported on comms radios.

'''JSBSim'''
* Sync with the latest version of [[JSBSim]].
* The pitot angle can now be tweaked with the <code><nowiki><pitot_angle></nowiki></code> tag in the <code><nowiki><metrics></nowiki></code> block.
* The refuel rate is now configurable with the <code><nowiki><refuel-rate></nowiki></code> tag in the <code><nowiki><propulsion></nowiki></code> block.

'''Rendering'''
* Improved vegetation including 3D grass and shadows for trees
* Better cockpit rendering:
** interior shadows
** glass reflections, fogging and frosting
** panel backlighting.
* New thruster effect (can be used for afterburners flames, rockets, etc.).
* Lightning effects
* Improved airport rendering, including runway skid marks and better effects for the runways and surrounding grass.
* Improved sky rendering, including sun halo, Aurora Borealis.

'''Usability'''
* Many improvements to [[Phi]], the built-in web interface.
* GUI cleanup to improve support for multiple GUI styles.
* The [[Integrated Qt5 Launcher|built-in Qt launcher]] is available for all of FlightGear's supported operating systems.
* Additional latitude and longitude formats are now supported in the HUD.

'''Scenery'''
* Regional texture definitions for Florida, Brazil, Latin America, Africa, the Middle East and Southeastern Asia.
* <tt>stgmerge</tt> tool added to merge objects in a scenery tile into a smaller number of meshes.

'''Highlighted new and improved aircraft'''
* Complete refresh of the default [[Cessna 172P]], including engine options, various tire sizes and floats.
* Major enhancements to the [[Space Shuttle]]. The Shuttle can be flown as per the Crew Operations Manual from launch to touchdown.
* The following aircraft have also received significant updates:
** [[McDonnell Douglas F-15 Eagle]]
** [[Rockwell B-1B Lancer]]
** [[Saab JA-37 Viggen]]
** [[Cessna 550 Citation II]]
** [[Lockheed Constellation]]
** [[Boeing 737-300]]
** [[Mirage 2000-5]]
** [[De Havilland Canada DHC-6 Twin Otter]]
** [[Dragon]]
** [[Beagle Pup]]
** [[Mikoyan-Gurevich_MiG-15|MiG-15]]

'''Misc/uncategorized'''
* Improved support for KDI572-574 [[DME]] equipment
* Update the [http://www.ngdc.noaa.gov/geomag/WMM/DoDWMM.shtml World Magnetic Model] to version 2015.0.

'''Nasal Scripting'''
* <code>createViaTo()</code> {{flightgear commit|caead6|t=added}}
* <code>createDiscontinuity()</code> {{flightgear commit|caead6|t=added}}
* <code>activate()</code> method {{flightgear commit|caead6|t=added}} to <code>flightplan</code> ghost object

'''Documentation'''
* The FlightGear Manual is now available in Chinese

'''Bug fixes'''
* See [http://sourceforge.net/p/flightgear/codetickets/search/?q=status%3AFixed+AND+created_date%3A%5B2015-09-23T23%3A11%3A56Z+TO+*%5D our bugtracker] for a list, albeit incomplete, of the bugs fixed in this release.

[[Category:FlightGear changelogs]]
[[Category:New Versioning Scheme]]

Cessna 550 Citation II

2016-02-18T21:12:29Z

Circumn: Remove the keybinding for autostart from the doc; it has been removed from the aircraft. Mention Walk View.

{{infobox Aircraft
|image =CitationII 2015-03-29.jpg
|name =Cessna 550 Citation II
|type =Business jet
|authors = Curtis Olson, Syd Adams, Ludovic Brenta, chris_blues
|fdm =[[YASim]]
|status-fdm=5
|status-systems=4
|status-cockpit=5
|status-model=5
|fgname = Citation-II<br/>Sierra-Super-II
|ready = rembrandt
|development = http://sourceforge.net/p/flightgear/fgaddon/HEAD/tree/trunk/Aircraft/Citation/
|download = http://sourceforge.net/p/flightgear/fgaddon/HEAD/tarball?path=/trunk/Aircraft/Citation
}}

[[File:CitationII Cockpit.png|thumb|270px|The cockpit of a Cessna 550]]

The '''Cessna 550 Citation II''' debuted in [[FlightGear]] 0.9.8 in January 2005. It has four "special views": copilot, center-console, passenger 1 and passenger 2.

== Overview ==
The Cessna 550/551 Citation II is a light corporate jet built between 1978 and 2006. The FlightGear model is a luxury corporate jet for two pilots and seven passengers. However you should not view the original Citation II as a real jet; with a cruising speed of only 330 KTAS, it was really intended as a competitor for high-end twin turboprops.

The Cessna 550 requires two pilots; the 551 is the same aircraft certified for single-pilot use.

Later variants of this aircraft include the [[Cessna_Citation_Bravo|Cessna Citation Bravo]], which has newer avionics (available separately in FlightGear), the Cessna Citation S/II with improved wings (not currently available in FlightGear), and the Sierra Super II, available together with this aircraft in FlightGear.

The Sierra Super II is an aftermarket modification of the Cessna 550/551 which replaces the engines with Williams International FJ44-3 turbofans introduced in 2004. They
provide more thrust and less fuel consumption. Climb performance in particular is dramatically improved.

The new engines lack thrust reversers; they are not needed because their idle thrust is only 40 lbf, as opposed to 400 lbf on the old engines.

[[File:CitationII Cockpit Dusk 2015-03-29.jpg|thumb|Cockpit Cessna 550 Citation II at dusk]]
Features available in FlightGear include:

* Choice of two variants: the basic Citation II or the re-engined Sierra Super II
* Several liveries
* Several checklists
* Autostart
* Weight and speed limitations
* Tuned autopilot with built-in climb schedule
* Working speedbrakes (engage with {{key press|k}}, retract with {{key press|j}} - alternatively {{key press|Ctrl|b}} toggles the s/b's)
* Working thrust reversers (engage with {{key press|Del}}) on the Citation II only
* Support for the [[Walk_view|Walk View]]

At low altitude, this aeroplane is light and slow enough for sightseeing in the canyons. At high altitude, it is fast enough for medium-haul, multiple-hour flights and GPS navigation. You can fly VFR or IFR, with or without GPS.

== Download ==

=== For FlightGear 3.4 and earlier ===

[https://sourceforge.net/p/flightgear/fgaddon/460/tarball?path=/trunk/Aircraft/Citation Citation rev 460]

=== For FlightGear 3.5 and higher ===

* Subversion:
<syntaxhighlight lang="bash">
$ svn checkout http://svn.code.sf.net/p/flightgear/fgaddon/trunk/Aircraft/Citation Citation
$ svn up
</syntaxhighlight>

* Tarball:

[http://sourceforge.net/p/flightgear/fgaddon/HEAD/tarball?path=/trunk/Aircraft/Citation Citation HEAD]

== Startup ==
Use the aircraft checklist for startup instructions; alternatively, use the menu for autostart.

== Performance ==
{| class="wikitable"
|-
! !! Citation II !! Sierra Super II
|-
! Never exceed speed
| 263 KIAS || 263 KIAS
|-
! Typical cruise speed at FL410
| 330 KTAS || 380 KTAS
|-
! Range at MTOW and full fuel, FL410, full throttle
| 1900 nmi || 2500 nmi
|-
! Endurance (hours) at full throttle
| 5:45 || 6:33
|-
! Climb rate at sea level
| 3000 fpm || 6000 fpm
|-
! Climb to FL410
| 45 min (stepped) || 22 min (direct)
|-
! Thrust reversers
| yes || no
|}

== Autopilot ==
The autopilot will disengage 500 feet above ground level or below the decision height selected on the radio altimeter, whichever is highest. This implies that you must climb at least to 500 ft above ground before you engage the autopilot. In addition, you should never engage autopilot while manoeuvering; always stabilize the aeroplane before you engage autopilot.

When the FD OFF button is illuminated, the autopilot is OFF. Clicking this button will engage the autopilot in wing leveler (horizontal) and pitch hold (vertical) modes. You can also engage autopilot, with the same effects, with the AP ENGAGE button between the seats. The following lateral, vertical and speed modes are available:

=== Lateral modes ===
; Wing Leveler: All lights are off
; HDG: Follow the magnetic heading bug selected on the pilot's HSI.
; NAV: Follow the radial selected on either NAV1 or NAV2. Switch between NAV1 and NAV2 using the NAV/HSI button.
; GPS: Follow the course selected by GPS. To engage, click on the NAV button a second time.
; APR: Click this button to engage both NAV1 and glideslope for an ILS approach. Note that, since the autopilot will disengage at least 500 ft above ground, this aeroplane is certified only for CAT I ILS approaches; it has no autoland capability.

=== Vertical modes ===
; Pitch hold: All lights are off. Adjust pitch (in increments of 1 degree) with the PITCH wheel between the seats.
; ALT: Climb or descend to, then maintain the altitude selected with the ALT knob left of the ADF radio. You can adjust the selected altitude with this knob or with the PITCH wheel between the seats.
; V/S: Hold current vertical speed. Adjust the selected vertical speed with the PITCH wheel between the seats.

You should engage ALT mode in more or less level flight with an angle of attack no greater than 0.2 and airspeed at least 220 KIAS. The autopilot includes a climb schedule and will climb at a speed appropriate for your engines; it will automatically decrease the rate of climb as you gain altitude.

On the base Citation II, you need a stepped climb and 45 minutes to reach FL410. The first step should be at FL330 or thereabouts.

On the re-engined Super II, you can climb all the way to FL430 in one step, even at MTOW, provided you respect the prerequisites listed above before engaging ALT mode.

=== Speed modes ===
; Autothrottle: Engage and disengage with Ctrl+S to hold current indicated airspeed. Note that the real Citation II does not have this, so you may consider using autothrottle cheating.

== Radio navigation ==
Tune the two NAV and COM radios and the sole ADF radio on the cockpit.

=== Horizontal Situation Indicators ===
On startup, the captain's [[HSI|horizontal situation indicator]] uses NAV1 and the copilot's HSI uses NAV2. The NAV/HSI button under each HSI switches between NAV1 and NAV2; you can switch the HSIs independently. If the autopilot is engaged in NAV mode, then the autopilot will also switch between NAV1 and NAV2, always following the radio selected on the captain's HSI. The best usage of this feature is as follows:

# Tune the NAV1 radio to a VOR beacon.
# Select the NAV1 radial on the captain's HSI.
# Fly the selected radial.
# Tune the NAV2 radio to another VOR beacon.
# Select the NAV2 radial on the copilot's HSI.
# When you intercept the radial selected on NAV2, click on the NAV/HSI button on the captain's side. The autopilot will now follow the NAV2 radial.
# Switch the copilot's HSI to NAV1.
# Tune NAV1 to a third VOR beacon.
# Select the NAV1 radial on the copilot's HSI.
# Repeat as necessary.

The two HSIs feature an integrated Radio Magnetic Indicator: the thin red arrow points to the selected VOR beacon (either NAV1 or NAV2). They also have a built-in Distance Measuring Equipment showing the distance between you and the selected beacon, in nautical miles.

=== Radio Magnetic Indicators ===
The cockpit has additional Radio Magnetic Indicators on both the pilot and copilot side. This indicator has two arrows and two buttons:

* The ''left'' button switches the single-stemmed arrow to point either to the NAV1 VOR beacon or to the NDB.
* The ''right'' button switches the double-stemmed arrow to point either to the NAV2 VOR beacon or to the NDB.

Combined with the HSI you can have arrows pointing simultaneously to all three beacons. By default:

* The ''single-stemmed'' arrow points to the NDB selected on the ADF radio
* The ''double-stemmed'' arrow points to the VOR beacon selected on the NAV2 radio
* The ''thin red needle'' of the HSI points to the VOR beacon selected on the NAV1 radio

=== Glideslope NAV1 indicator ===
To the left of the pilot's HSI is an additional NAV1 indicator with two needles; this merely repeats localizer and glideslope information from the HSI and from the attitude indicator.
Thus you have triple redundancy :) This instrument is hardwired to NAV1, so you can fly an ILS approach by hand while simultaneously pointing your HSI at the NAV2 beacon.

=== Distance Measuring Equipment ===
The DME shows the distance in nautical miles to the selected beacon. You can use it either to repeat the information on the HSI or to show the distance to the other beacon.
This instrument also shows your speed towards or from the beacon (''not'' your groundspeed: Only the component of your groundspeed that is on the line between you and the beacon), or
the time to go to the beacon in minutes at your current speed.

=== Control Display Unit ===
The CDU on the central console allows you to create a simple route from one airport to another.

To create a route:

# Click on the DEP ARR button.
# Type the ICAO code of your departure airport.
# Click on the ORIGIN (top left) button.
# Type the ICAO code of your destination airport.
# Click on the DEST (top right) button.
# Optionally type the departure runway number then click the RWY button.
# Click ACTIVATE.

This activates the Route Manager, which you can of course still control with the generic Route Manager dialog.

== Development ==
=== Recently updated ===
==== Systems ====
* Several checklists have been added.
* A realistic startup procedure.
* A major overhaul of the Autopilot-systems.
* The FDM got upgraded and several bugs got fixed in the process.
* All knobs can now be turned with the mouse-wheel.
* Some circuit breakers have been made functional, mainly on pilots side cb-panel.

==== Instruments ====
* Added a new Lighting Panel to the pilots panel. All knobs and switches, which actually have a function are animated.
* Instrument Panel got new textures. Looks a bit more used now.
* RMI now is switchable on Nav1/ADF and Nav2/ADF.
* HSI can be switched between Nav1/Nav2/GPS with the AP control panel's NAV-button.
* A CDU was added on the center pedestal.

==== Model ====
* All lights are now Rembrandt-capable.
* ALS flame / heat blur effect was added.
* ALS glass shader was added.
* The missing door-ladder was added and animated.
* Baggage compartments were added and doors animated.
* The speedbrakes got a major overhaul and are now much closer to the real thing, also the lower speedbrakes are added and animated.
* Small details like pitot tubes and antennas were added.
* Several small additions to the cockpit and cabin, including an accurate circuit breaker panel, with some functionality for now.

=== Todo ===
* Create different liveries for Citation II and Sierra Super II.
* CDU needs more functions and bug fixes.
* Add some baggage.
* Add new GPS unit.
See [http://sourceforge.net/p/flightgear/fgaddon/HEAD/tree/trunk/Aircraft/Citation/ToDo.txt ToDo.txt @ sourceforge]

== External links ==
* {{wikipedia|Cessna Citation II}} Wikipedia article
* [http://www.sijet.com/page727822 Corporate site for the Sierra Super II aftermarket modification]

{{Cessna}}

[[Category:Business aircraft]]

Cessna 550 Citation II

2015-12-07T21:27:25Z

Circumn: /* Performance */ 380 KTAS, not 370

{{infobox Aircraft
|image =Cessna550.jpg
|name =Cessna 550 Citation II
|type =Business jet
|authors = Curtis Olson, Syd Adams, Ludovic Brenta, chris_blues
|fdm =[[YASim]]
|status-fdm=5
|status-systems=4
|status-cockpit=5
|status-model=5
|fgname = Citation-II<br/>Sierra-Super-II
|ready = rembrandt
|development = http://sourceforge.net/p/flightgear/fgaddon/HEAD/tree/trunk/Aircraft/Citation/
|download = http://sourceforge.net/p/flightgear/fgaddon/HEAD/tarball?path=/trunk/Aircraft/Citation
}}

[[File:CitationII Cockpit.png|thumb|270px|The cockpit of a Cessna 550]]

The '''Cessna 550 Citation II''' debuted in [[FlightGear]] 0.9.8 in January 2005. It has four "special views": copilot, center-console, passenger 1 and passenger 2.

== Overview ==
The Cessna 550/551 Citation II is a light corporate jet built between 1978 and 2006. The FlightGear model is a luxury corporate jet for two pilots and seven passengers. However you should not view the original Citation II as a real jet; with a cruising speed of only 330 KTAS, it was really intended as a competitor for high-end twin turboprops.

The Cessna 550 requires two pilots; the 551 is the same aircraft certified for single-pilot use.

Later variants of this aircraft include the [[Cessna_Citation_Bravo|Cessna Citation Bravo]], which has newer avionics (available separately in FlightGear), the Cessna Citation S/II with improved wings (not currently available in FlightGear), and the Sierra Super II, available together with this aircraft in FlightGear.

The Sierra Super II is an aftermarket modification of the Cessna 550/551 which replaces the engines with Williams International FJ44-3 turbofans introduced in 2004. They
provide more thrust and less fuel consumption. Climb performance in particular is dramatically improved.

The new engines lack thrust reversers; they are not needed because their idle thrust is only 40 lbf, as opposed to 400 lbf on the old engines.

Features available in FlightGear include:

* Choice of two variants: the basic Citation II or the re-engined Sierra Super II
* Several liveries
* Several checklists
* Autostart ( {{key press|s}} )
* Weight and speed limitations
* Tuned autopilot with built-in climb schedule
* Working speedbrakes (engage with {{key press|k}}, retract with {{key press|j}} - alternatively {{key press|Ctrl|b}} toggles the s/b's)
* Working thrust reversers (engage with {{key press|Del}}) on the Citation II only

At low altitude, this aeroplane is light and slow enough for sightseeing in the canyons. At high altitude, it is fast enough for medium-haul, multiple-hour flights and GPS navigation. You can fly VFR or IFR, with or without GPS.

== Download ==

=== For FlightGear 3.4 and earlier ===

[https://sourceforge.net/p/flightgear/fgaddon/460/tarball?path=/trunk/Aircraft/Citation Citation rev 460]

=== For FlightGear 3.5 and higher ===

* Subversion:
<syntaxhighlight lang="bash">
$ svn checkout http://svn.code.sf.net/p/flightgear/fgaddon/trunk/Aircraft/Citation Citation
$ svn up
</syntaxhighlight>

* Tarball:

[http://sourceforge.net/p/flightgear/fgaddon/HEAD/tarball?path=/trunk/Aircraft/Citation Citation HEAD]

== Startup ==
Use the aircraft checklist for startup instructions; alternatively, press {{key press|s}} for autostart.

== Performance ==
{| class="wikitable"
|-
! !! Citation II !! Sierra Super II
|-
! Never exceed speed
| 263 KIAS || 263 KIAS
|-
! Typical cruise speed at FL410
| 330 KTAS || 380 KTAS
|-
! Range at MTOW and full fuel, FL410, full throttle
| 1900 nmi || 2500 nmi
|-
! Endurance (hours) at full throttle
| 5:45 || 6:33
|-
! Climb rate at sea level
| 3000 fpm || 6000 fpm
|-
! Climb to FL410
| 45 min (stepped) || 22 min (direct)
|-
! Thrust reversers
| yes || no
|}

== Autopilot ==
The autopilot will disengage 500 feet above ground level or below the decision height selected on the radio altimeter, whichever is highest. This implies that you must climb at least to 500 ft above ground before you engage the autopilot. In addition, you should never engage autopilot while manoeuvering; always stabilize the aeroplane before you engage autopilot.

When the FD OFF button is illuminated, the autopilot is OFF. Clicking this button will engage the autopilot in wing leveler (horizontal) and pitch hold (vertical) modes. You can also engage autopilot, with the same effects, with the AP ENGAGE button between the seats. The following lateral, vertical and speed modes are available:

=== Lateral modes ===
; Wing Leveler: All lights are off
; HDG: Follow the magnetic heading bug selected on the pilot's HSI.
; NAV: Follow the radial selected on either NAV1 or NAV2. Switch between NAV1 and NAV2 using the NAV/HSI button.
; GPS: Follow the course selected by GPS. To engage, click on the NAV button a second time.
; APR: Click this button to engage both NAV1 and glideslope for an ILS approach. Note that, since the autopilot will disengage at least 500 ft above ground, this aeroplane is certified only for CAT I ILS approaches; it has no autoland capability.

=== Vertical modes ===
; Pitch hold: All lights are off. Adjust pitch (in increments of 1 degree) with the PITCH wheel between the seats.
; ALT: Climb or descend to, then maintain the altitude selected with the ALT knob left of the ADF radio. You can adjust the selected altitude with this knob or with the PITCH wheel between the seats.
; V/S: Hold current vertical speed. Adjust the selected vertical speed with the PITCH wheel between the seats.

You should engage ALT mode in more or less level flight with an angle of attack no greater than 0.2 and airspeed at least 220 KIAS. The autopilot includes a climb schedule and will climb at a speed appropriate for your engines; it will automatically decrease the rate of climb as you gain altitude.

On the base Citation II, you need a stepped climb and 45 minutes to reach FL410. The first step should be at FL330 or thereabouts.

On the re-engined Super II, you can climb all the way to FL430 in one step, even at MTOW, provided you respect the prerequisites listed above before engaging ALT mode.

=== Speed modes ===
; Autothrottle: Engage and disengage with Ctrl+S to hold current indicated airspeed. Note that the real Citation II does not have this, so you may consider using autothrottle cheating.

== Radio navigation ==
Tune the two NAV and COM radios and the sole ADF radio on the cockpit.

=== Horizontal Situation Indicators ===
On startup, the captain's [[HSI|horizontal situation indicator]] uses NAV1 and the copilot's HSI uses NAV2. The NAV/HSI button under each HSI switches between NAV1 and NAV2; you can switch the HSIs independently. If the autopilot is engaged in NAV mode, then the autopilot will also switch between NAV1 and NAV2, always following the radio selected on the captain's HSI. The best usage of this feature is as follows:

# Tune the NAV1 radio to a VOR beacon.
# Select the NAV1 radial on the captain's HSI.
# Fly the selected radial.
# Tune the NAV2 radio to another VOR beacon.
# Select the NAV2 radial on the copilot's HSI.
# When you intercept the radial selected on NAV2, click on the NAV/HSI button on the captain's side. The autopilot will now follow the NAV2 radial.
# Switch the copilot's HSI to NAV1.
# Tune NAV1 to a third VOR beacon.
# Select the NAV1 radial on the copilot's HSI.
# Repeat as necessary.

The two HSIs feature an integrated Radio Magnetic Indicator: the thin red arrow points to the selected VOR beacon (either NAV1 or NAV2). They also have a built-in Distance Measuring Equipment showing the distance between you and the selected beacon, in nautical miles.

=== Radio Magnetic Indicators ===
The cockpit has additional Radio Magnetic Indicators on both the pilot and copilot side. This indicator has two arrows and two buttons:

* The ''left'' button switches the single-stemmed arrow to point either to the NAV1 VOR beacon or to the NDB.
* The ''right'' button switches the double-stemmed arrow to point either to the NAV2 VOR beacon or to the NDB.

Combined with the HSI you can have arrows pointing simultaneously to all three beacons. By default:

* The ''single-stemmed'' arrow points to the NDB selected on the ADF radio
* The ''double-stemmed'' arrow points to the VOR beacon selected on the NAV2 radio
* The ''thin red needle'' of the HSI points to the VOR beacon selected on the NAV1 radio

=== Glideslope NAV1 indicator ===
To the left of the pilot's HSI is an additional NAV1 indicator with two needles; this merely repeats localizer and glideslope information from the HSI and from the attitude indicator.
Thus you have triple redundancy :) This instrument is hardwired to NAV1, so you can fly an ILS approach by hand while simultaneously pointing your HSI at the NAV2 beacon.

=== Distance Measuring Equipment ===
The DME shows the distance in nautical miles to the selected beacon. You can use it either to repeat the information on the HSI or to show the distance to the other beacon.
This instrument also shows your speed towards or from the beacon (''not'' your groundspeed: Only the component of your groundspeed that is on the line between you and the beacon), or
the time to go to the beacon in minutes at your current speed.

=== Control Display Unit ===
The CDU on the central console allows you to create a simple route from one airport to another.

To create a route:

# Click on the DEP ARR button.
# Type the ICAO code of your departure airport.
# Click on the ORIGIN (top left) button.
# Type the ICAO code of your destination airport.
# Click on the DEST (top right) button.
# Optionally type the departure runway number then click the RWY button.
# Click ACTIVATE.

This activates the Route Manager, which you can of course still control with the generic Route Manager dialog.

== Development ==
=== Recently updated ===
==== Systems ====
* Several checklists have been added.
* A realistic startup procedure.
* A major overhaul of the Autopilot-systems.
* The FDM got upgraded and several bugs got fixed in the process.
* All knobs can now be turned with the mouse-wheel.
* Some circuit breakers have been made functional, mainly on pilots side cb-panel.

==== Instruments ====
* Added a new Lighting Panel to the pilots panel. All knobs and switches, which actually have a function are animated.
* Instrument Panel got new textures. Looks a bit more used now.
* RMI now is switchable on Nav1/ADF and Nav2/ADF.
* HSI can be switched between Nav1/Nav2/GPS with the AP control panel's NAV-button.
* A CDU was added on the center pedestal.

==== Model ====
* All lights are now Rembrandt-capable.
* ALS flame / heat blur effect was added.
* ALS glass shader was added.
* The missing door-ladder was added and animated.
* Baggage compartments were added and doors animated.
* The speedbrakes got a major overhaul and are now much closer to the real thing, also the lower speedbrakes are added and animated.
* Small details like pitot tubes and antennas were added.
* Several small additions to the cockpit and cabin, including an accurate circuit breaker panel, with some functionality for now.

=== Todo ===
* Create different liveries for Citation II and Sierra Super II.
* CDU needs more functions and bug fixes.
* Add some baggage.
* Add new GPS unit.
See [http://sourceforge.net/p/flightgear/fgaddon/HEAD/tree/trunk/Aircraft/Citation/ToDo.txt ToDo.txt @ sourceforge]

== External links ==
* {{wikipedia|Cessna Citation II}} Wikipedia article
* [http://www.sijet.com/page727822 Corporate site for the Sierra Super II aftermarket modification]

{{Cessna}}

[[Category:Business aircraft]]

Tactical Air Navigation

2015-09-16T15:46:37Z

Circumn: Add the B-1B as a TACAN-equipped aircraft

[[File:Pictogram TACAN.png|frame|TACAN symbol]]
'''TACtical Air Navigation''', or '''[http://en.wikipedia.org/wiki/Tactical_Air_Navigation TACAN]''', is a navigation system used by [[:Category:Military aircraft|military aircraft]]. It provides the user with a distance and bearing from a ground station. It is a more accurate version of the [http://en.wikipedia.org/wiki/Vhf VHF] omnidirectional range / Distance Measuring Equipment ([[VOR-DME]]) system that provides range and bearing information for civil aviation. At VORTAC facilities, the [[DME]] portion of the TACAN system is available for civil use.

== Operation ==
TACAN in general can be described as the military version of the [[VOR-DME]] system. It operates in the frequency band 960-1215 MHz. The bearing unit of TACAN is more accurate than a standard [[VOR]] since it makes use of a two frequency principle, with 15 Hz and 135 Hz components.

The distance measurement component of TACAN operates with the same specifications as do civil [[DME]]'s. Therefore to reduce the number of required stations, TACAN stations are frequently co-located with [[VOR]] facilities. These co-located stations are known as [[VORTAC]]'s. This is a station composed of a [[VOR]] for civil bearing information and a TACAN for military bearing information and military/civil distance measuring information. The TACAN transponder performs the function of a [[DME]] without the need for a separate, collocated [[DME]]. Because the rotation of the antenna creates a large portion of the azimuth signal, if the antenna fails, the azimuth component is no longer available and the TACAN downgrades to a [[DME]] only mode.

=== FlightGear ===
A few planes in FlightGear are equipped with TACAN. Here's a list of known aircraft with TACAN:

* [[Grumman A-6E|A-6E]]
* [[Fairchild A-10|A-10]]
* [[Douglas A4 Skyhawk|A4F]]
* [[Rockwell B-1B Lancer|B-1B]]
* [[Blackburn Buccaneer]]
* [[Grumman F-14 Tomcat]]
* [[English Electric Lightning|Lightning]]
* [[Northrop T-38|T38]]

To set TACAN, go to the <tt>Equipment > Radio Settings</tt> dialog. When using in-air refuel, first read [[Howto: Air-Air Refueling]].

===Related===
*[[Radio beacons]]
*[[Radio navigation]]

[[Category:Aviation]]

Cessna 550 Citation II

2015-04-07T19:10:08Z

Circumn: /* Download */ Add a link to a version of the Citation II that works with FlightGear 3.4

{{infobox Aircraft
|image =Cessna550.jpg
|name =Cessna 550 Citation II
|type =Business jet
|authors = Curtis Olson, Syd Adams, Ludovic Brenta, chris_blues
|fdm =[[YASim]]
|status-fdm=5
|status-systems=4
|status-cockpit=5
|status-model=5
|fgname = Citation-II<br/>Sierra-Super-II
|ready = rembrandt
|development = http://sourceforge.net/p/flightgear/fgaddon/HEAD/tree/trunk/Aircraft/Citation/
|download = http://sourceforge.net/p/flightgear/fgaddon/HEAD/tarball?path=/trunk/Aircraft/Citation
}}

[[File:CitationII Cockpit.png|thumb|270px|The cockpit of a Cessna 550]]

The '''Cessna 550 Citation II''' debuted in [[FlightGear]] 0.9.8 in January 2005. It has two "special views": passenger 1 and passenger 2.

== Overview ==
The Cessna 550/551 Citation II is a light corporate jet built between 1978 and 2006. The FlightGear model is a luxury corporate jet for two pilots and seven passengers. However you should not view the original Citation II as a real jet; with a cruising speed of only 330 KTAS, it was really intended as a competitor for high-end twin turboprops.

The Cessna 550 requires two pilots; the 551 is the same aircraft certified for single-pilot use.

Later variants of this aircraft include the [[Cessna_Citation_Bravo|Cessna Citation Bravo]], which has newer avionics (available separately in FlightGear), the Cessna Citation S/II with improved wings (not currently available in FlightGear), and the Sierra Super II, available together with this aircraft in FlightGear.

The Sierra Super II is an aftermarket modification of the Cessna 550/551 which replaces the engines with Williams International FJ44-3 turbofans introduced in 2004. They
provide more thrust and less fuel consumption. Climb performance in particular is dramatically improved.

The new engines lack thrust reversers; they are not needed because their idle thrust is only 40 lbf, as opposed to 400 lbf on the old engines.

Features available in FlightGear include:

* Choice of two variants: the basic Citation II or the re-engined Sierra Super II
* Several liveries
* Several checklists
* Autostart ( {{key press|s}} )
* Weight and speed limitations
* Tuned autopilot with built-in climb schedule
* Working speedbrakes (engage with {{key press|k}}, retract with {{key press|j}} - alternatively {{key press|Ctrl|b}} toggles the s/b's)
* Working thrust reversers (engage with {{key press|Del}}) on the Citation II only
* GPS navigation as an aftermarket modification

At low altitude, this aeroplane is light and slow enough for sightseeing in the canyons. At high altitude, it is fast enough for medium-haul, multiple-hour flights and GPS navigation. You can fly VFR or IFR, with or without GPS.

== Download ==

=== For FlightGear 3.4 and earlier ===

[https://sourceforge.net/p/flightgear/fgaddon/460/tarball?path=/trunk/Aircraft/Citation Citation rev 460]

=== For FlightGear 3.5 ===

* Subversion:
<syntaxhighlight lang="bash">
$ svn checkout http://svn.code.sf.net/p/flightgear/fgaddon/trunk/Aircraft/Citation Citation
$ svn up
</syntaxhighlight>

* Tarball:

[http://sourceforge.net/p/flightgear/fgaddon/HEAD/tarball?path=/trunk/Aircraft/Citation Citation HEAD]

== Startup ==
Use the aircraft checklist for startup instructions; alternatively, press {{key press|s}} for autostart.

== Performance ==
{| class="wikitable"
|-
! !! Citation II !! Sierra Super II
|-
! Never exceed speed
| 263 KIAS || 263 KIAS
|-
! Typical cruise speed at FL410
| 330 KTAS || 370 KTAS
|-
! Range at MTOW and full fuel, FL410, full throttle
| 1900 nmi || 2500 nmi
|-
! Endurance (hours) at full throttle
| 5:45 || 6:33
|-
! Climb rate at sea level
| 3000 fpm || 6000 fpm
|-
! Climb to FL410
| 45 min (stepped) || 22 min (direct)
|-
! Thrust reversers
| yes || no
|}

== Autopilot ==
The autopilot will disengage 500 feet above ground level or below the decision height selected on the radio altimeter, whichever is highest. This implies that you must climb at least to 500 ft above ground before you engage the autopilot. In addition, you should never engage autopilot while manoeuvering; always stabilize the aeroplane before you engage autopilot.

When the FD OFF button is illuminated, the autopilot is OFF. Clicking this button will engage the autopilot in wing leveler (horizontal) and pitch hold (vertical) modes. You can also engage autopilot, with the same effects, with the AP ENGAGE button between the seats. The following lateral, vertical and speed modes are available:

=== Lateral modes ===
; Wing Leveler: All lights are off
; HDG: Follow the magnetic heading bug selected on the pilot's HSI.
; NAV: Follow the radial selected on either NAV1 or NAV2. Switch between NAV1 and NAV2 using the NAV/HSI button.
; GPS: Follow the course selected by GPS. To engage, click on the NAV button a second time.
; APR: Click this button to engage both NAV1 and glideslope for an ILS approach. Note that, since the autopilot will disengage at least 500 ft above ground, this aeroplane is certified only for CAT I ILS approaches; it has no autoland capability.

=== Vertical modes ===
; Pitch hold: All lights are off. Adjust pitch (in increments of 1 degree) with the PITCH wheel between the seats.
; ALT: Climb or descend to, then maintain the altitude selected with the ALT knob left of the ADF radio. You can adjust the selected altitude with this knob or with the PITCH wheel between the seats.
; V/S: Hold current vertical speed. Adjust the selected vertical speed with the PITCH wheel between the seats.

You should engage ALT mode in more or less level flight with an angle of attack no greater than 0.2 and airspeed at least 220 KIAS. The autopilot includes a climb schedule and will climb at a speed appropriate for your engines; it will automatically decrease the rate of climb as you gain altitude.

On the base Citation II, you need a stepped climb and 45 minutes to reach FL410. The first step should be at FL330 or thereabouts.

On the re-engined Super II, you can climb all the way to FL430 in one step, even at MTOW, provided you respect the prerequisites listed above before engaging ALT mode.

=== Speed modes ===
; Autothrottle: Engage and disengage with Ctrl+S to hold current indicated airspeed. Note that the real Citation II does not have this, so you may consider using autothrottle cheating.

== Radio navigation ==
Tune the two NAV and COM radios and the sole ADF radio on the cockpit.

=== Horizontal Situation Indicators ===
On startup, the captain's [[HSI|horizontal situation indicator]] uses NAV1 and the copilot's HSI uses NAV2. The NAV/HSI button under each HSI switches between NAV1 and NAV2; you can switch the HSIs independently. If the autopilot is engaged in NAV mode, then the autopilot will also switch between NAV1 and NAV2, always following the radio selected on the captain's HSI. The best usage of this feature is as follows:

# Tune the NAV1 radio to a VOR beacon.
# Select the NAV1 radial on the captain's HSI.
# Fly the selected radial.
# Tune the NAV2 radio to another VOR beacon.
# Select the NAV2 radial on the copilot's HSI.
# When you intercept the radial selected on NAV2, click on the NAV/HSI button on the captain's side. The autopilot will now follow the NAV2 radial.
# Switch the copilot's HSI to NAV1.
# Tune NAV1 to a third VOR beacon.
# Select the NAV1 radial on the copilot's HSI.
# Repeat as necessary.

The two HSIs feature an integrated Radio Magnetic Indicator: the thin red arrow points to the selected VOR beacon (either NAV1 or NAV2). They also have a built-in Distance Measuring Equipment showing the distance between you and the selected beacon, in nautical miles.

=== Radio Magnetic Indicators ===
The cockpit has additional Radio Magnetic Indicators on both the pilot and copilot side. This indicator has two arrows and two buttons:

* The ''left'' button switches the single-stemmed arrow to point either to the NAV1 VOR beacon or to the NDB.
* The ''right'' button switches the double-stemmed arrow to point either to the NAV2 VOR beacon or to the NDB.

Combined with the HSI you can have arrows pointing simultaneously to all three beacons. By default:

* The ''single-stemmed'' arrow points to the NDB selected on the ADF radio
* The ''double-stemmed'' arrow points to the VOR beacon selected on the NAV2 radio
* The ''thin red needle'' of the HSI points to the VOR beacon selected on the NAV1 radio

=== Glideslope NAV1 indicator ===
To the left of the pilot's HSI is an additional NAV1 indicator with two needles; this merely repeats localizer and glideslope information from the HSI and from the attitude indicator.
Thus you have triple redundancy :) This instrument is hardwired to NAV1, so you can fly an ILS approach by hand while simultaneously pointing your HSI at the NAV2 beacon.

=== Distance Measuring Equipment ===
The DME shows the distance in nautical miles to the selected beacon. You can use it either to repeat the information on the HSI or to show the distance to the other beacon.
This instrument also shows your speed towards or from the beacon (''not'' your groundspeed: Only the component of your groundspeed that is on the line between you and the beacon), or
the time to go to the beacon in minutes at your current speed.

== GPS navigation ==
The original Citation II did not have a GPS but both it and the re-engined Sierra Super II have two aftermarket additions that enable basic GPS navigation.

=== ZVK500 GPS instrument ===
This instrument is available as part of the base FlightGear package and is shared with the [[Lionceau]] light propeller aircraft. It features a very basic display of current position,
next waypoint, time to waypoint, direct route (DTO) mode, etc. For more details, see [http://sourceforge.net/p/flightgear/fgdata/ci/next/tree/Aircraft/Instruments-3d/zkv500/manual.txt its documentation].

=== Control Display Unit ===
The CDU on the central console allows you to create a simple route from one airport to another.

To create a route:

# Click on the DEP ARR button.
# Type the ICAO code of your departure airport.
# Click on the ORIGIN (top left) button.
# Type the ICAO code of your destination airport.
# Click on the DEST (top right) button.
# Optionally type the departure runway number then click the RWY button.
# Click ACTIVATE.

This activates the Route Manager, which you can of course still control with the generic Route Manager dialog. The ZVK500 unit in POSITION mode will then display where you stand on the selected route.

== Development ==
=== Recently updated ===
==== Systems ====
* Several checklists have been added.
* A realistic startup procedure.
* A major overhaul of the Autopilot-systems.
* The FDM got upgraded and several bugs got fixed in the process.
* All knobs can now be turned with the mouse-wheel.

==== Instruments ====
* Added a new Lighting Panel to the pilots panel. All knobs and switches, which actually have a function are animated.
* Instrument Panel got new textures. Looks a bit more used now.
* RMI now is switchable on Nav1/ADF and Nav2/ADF.
* HSI can be switched between Nav1/Nav2/GPS with the AP control panel's NAV-button.
* A ZVK500 GPS instrument was added on the pilots instrument panel.
* A CDU was added on the center pedestal.

==== Model ====
* All exterior lights are now Rembrandt-capable.
* The missing door-ladder was added and animated.
* The speedbrakes got a major overhaul and are now much closer to the real thing, also the lower speedbrakes are added and animated.
* Several small additions to the cockpit and cabin, including an accurate circuit breaker panel, sadly without functionality for now.

=== Todo ===
* Interior Rembrandt lighting
* Fine-tuning of speedbrake's animations and add LOD
* More interior model details (e.g. better textures, overhead lights, air conditioning outlets etc.)
* Create different liveries for Citation II and Sierra Super II.
* CDU needs more functions and bug fixes

== External links ==
* {{wikipedia|Cessna Citation II}} Wikipedia article
* [http://www.sijet.com/page727822 Corporate site for the Sierra Super II aftermarket modification]

{{Cessna}}

[[Category:Business aircraft]]

Lockheed Constellation

2015-04-07T19:01:17Z

Circumn: Reduce Systems rating to 3. Add present and future features and a Checklist Ready logo.

''This includes the following models: Lockheed 1049H Super Constellation''

{{infobox Aircraft
|image = Lockheed 1049H Super Constellation.png
|name = Lockheed 1049H Super Constellation
|type = 4-engine (radial) airliner and air transport
|livery = Lufthansa, Eastern Great Silver Fleet, KLM, TWA
|authors = Gary R. Neely, Marc Kraus, Ludovic Brenta, Richard Senior
|fdm = JSBSim
|status-fdm=4
|status-systems=3
|status-cockpit=4
|status-model=4
|fgname = Lockheed1049h
|development = http://sourceforge.net/p/flightgear/fgaddon/HEAD/tree/trunk/Aircraft/Lockheed1049h/
|download=http://sourceforge.net/p/flightgear/fgaddon/HEAD/tarball?path=/trunk/Aircraft/Lockheed1049h
}}

[[Image:Checklistready.png|link=Aircraft Checklists]]

The '''Lockheed Constellation''', affectionately known as the “Connie”, was a four-engine propeller-driven airliner built by Lockheed between 1943 and 1958 at its Burbank, California, USA, facility. A total of 856 aircraft were produced in four models, all distinguished by a distinctive triple-tail design and graceful, dolphin-shaped fuselage. It was used as both a civilian airliner and U.S. military air transport plane, seeing service in the Berlin Airlift and as the presidential aircraft for U.S. President Dwight D. Eisenhower.

The Lockheed L-1049 Super Constellation was a member of the Lockheed Constellation aircraft line, and was Lockheed's response to the successful Douglas DC-6 airliner, first flying in 1950. The L-1049H variant flew on November 20, 1956. Called "Super H" and "Husky", the L-1049H was a convertible passenger/freight aircraft, mating a C-121C-based fuselage with L-1049G components. The cargo hold had a volume of 565 ft³ (16 m³) when including the lower hold. The aircraft could carry up to 120 people with seats, luggage lockers and toilets all available along with the option of decorating the walls of the aircraft. When not in use, the luggage lockers and seats could be stowed in the lower hold.

The aircraft entered service with QANTAS a month later. Some L-1049G and H aircraft in later production were fitted with the TC-18EA series engines used on the L-1649 Starliner. A final variant was planned in 1957, known as the L-1049J. Powered by four R-3350-988-TC-18EA-6 engines, the L-1049J was based on the L-1049H with the wings of the R7V-2 Constellation and an extra fuselage-mounted fuel tank.

==Compatibility==

FlightGear 2.x: Loads and runs<br />
FlightGear 3.0: Loads and runs<br />

[[File:Lockheed_1049H_Super_Constellation_landing.png|thumb|270px|The [[cockpit]]]]

== External links ==
* [http://en.wikipedia.org/wiki/Lockheed_Constellation Wikipedia: Lockheed Constellation]

== Current features ==

As of April 2015, advanced features of the Lockheed1049h include:

* Livery support.
* Realistic and tuned FDM.
* Realistic and tuned, 1956-vintage autopilot (but the generic autopilot dialog also works, for beginners).
* Realistic and complex fuel system with several presets, from no fuel management for beginners to full manual fuel management.
* Detailed checklists.
* Engine fire.
* Engine fire extinguishing.
* Fuel jettison.
* Realistic Fuel and Payload system.
* Dynamic load factor and speed limits (they depend on flight conditions).
* Windshield wipers.

== Future (planned) features ==

* Dual-control. Currently, two players can be in the same aircraft: the pilot and the copilot; but the copilit cannot take control of anything, only watch.
* Realistic electrical system to power lights, engine starter, instruments, autopilot, auxiliary fuel pumps.
* Realistic hydraulic system to power control surfaces, main fuel pumps, brakes.
* Autostart following the checklists.
* Pressurization?
* Radar?

{{Lockheed}}

[[Category:Airliners]]
[[Category:Propeller_aircraft]]

Lockheed Constellation

2015-03-20T18:23:32Z

Circumn: Add a link to the development repository, too.

''This includes the following models: Lockheed 1049H Super Constellation''

{{infobox Aircraft
|image = Lockheed 1049H Super Constellation.png
|name = Lockheed 1049H Super Constellation
|type = 4-engine (radial) airliner and air transport
|livery = Lufthansa, Eastern Great Silver Fleet, KLM, TWA
|authors = Unknown author, Gary R. Neely et al.
|fdm = JSBSim
|status-fdm=4
|status-systems=5
|status-cockpit=4
|status-model=4
|fgname = Lockheed1049h
|development = http://sourceforge.net/p/flightgear/fgaddon/HEAD/tree/trunk/Aircraft/Lockheed1049h/
|download=http://sourceforge.net/p/flightgear/fgaddon/HEAD/tarball?path=/trunk/Aircraft/Lockheed1049h
}}

The '''Lockheed Constellation''', affectionately known as the “Connie”, was a four-engine propeller-driven airliner built by Lockheed between 1943 and 1958 at its Burbank, California, USA, facility. A total of 856 aircraft were produced in four models, all distinguished by a distinctive triple-tail design and graceful, dolphin-shaped fuselage. It was used as both a civilian airliner and U.S. military air transport plane, seeing service in the Berlin Airlift and as the presidential aircraft for U.S. President Dwight D. Eisenhower.

The Lockheed L-1049 Super Constellation was a member of the Lockheed Constellation aircraft line, and was Lockheed's response to the successful Douglas DC-6 airliner, first flying in 1950. The L-1049H variant flew on November 20, 1956. Called "Super H" and "Husky", the L-1049H was a convertible passenger/freight aircraft, mating a C-121C-based fuselage with L-1049G components. The cargo hold had a volume of 565 ft³ (16 m³) when including the lower hold. The aircraft could carry up to 120 people with seats, luggage lockers and toilets all available along with the option of decorating the walls of the aircraft. When not in use, the luggage lockers and seats could be stowed in the lower hold.

The aircraft entered service with QANTAS a month later. Some L-1049G and H aircraft in later production were fitted with the TC-18EA series engines used on the L-1649 Starliner. A final variant was planned in 1957, known as the L-1049J. Powered by four R-3350-988-TC-18EA-6 engines, the L-1049J was based on the L-1049H with the wings of the R7V-2 Constellation and an extra fuselage-mounted fuel tank.

==Compatibility==

FlightGear 2.x: Loads and runs<br />
FlightGear 3.0: Loads and runs<br />

[[File:Lockheed_1049H_Super_Constellation_landing.png|thumb|270px|The [[cockpit]]]]

== External links ==
* [http://en.wikipedia.org/wiki/Lockheed_Constellation Wikipedia: Lockheed Constellation]

{{Lockheed}}

[[Category:Airliners]]
[[Category:Propeller_aircraft]]

Lockheed Constellation

2015-03-20T18:17:33Z

Circumn: Update rating and download link to the latest version in Subversion

Cessna 550 Citation II

2015-03-19T21:42:49Z

Circumn: Increase rating of cockpit and model for version 2.0.1.

{{infobox Aircraft
|image =Cessna550.jpg
|name =Cessna 550 Citation II
|type =Business jet
|authors = Curtis Olson, Syd Adams, Ludovic Brenta, chris_blues
|fdm =[[YASim]]
|status-fdm=5
|status-systems=4
|status-cockpit=5
|status-model=5
|fgname = Citation-II<br/>Sierra-Super-II
|ready = rembrandt
|development = http://sourceforge.net/p/flightgear/fgaddon/HEAD/tree/trunk/Aircraft/Citation/
|download = http://sourceforge.net/p/flightgear/fgaddon/HEAD/tarball?path=/trunk/Aircraft/Citation
}}

[[File:CitationII Cockpit.png|thumb|270px|The cockpit of a Cessna 550]]

The '''Cessna 550 Citation II''' debuted in [[FlightGear]] 0.9.8 in January 2005. It has two "special views": passenger 1 and passenger 2.

== Overview ==
The Cessna 550/551 Citation II is a light corporate jet built between 1978 and 2006. The FlightGear model is a luxury corporate jet for two pilots and seven passengers. However you should not view the original Citation II as a real jet; with a cruising speed of only 330 KTAS, it was really intended as a competitor for high-end twin turboprops.

The Cessna 550 requires two pilots; the 551 is the same aircraft certified for single-pilot use.

Later variants of this aircraft include the [[Cessna_Citation_Bravo|Cessna Citation Bravo]], which has newer avionics (available separately in FlightGear), the Cessna Citation S/II with improved wings (not currently available in FlightGear), and the Sierra Super II, available together with this aircraft in FlightGear.

The Sierra Super II is an aftermarket modification of the Cessna 550/551 which replaces the engines with Williams International FJ44-3 turbofans introduced in 2004. They
provide more thrust and less fuel consumption. Climb performance in particular is dramatically improved.

The new engines lack thrust reversers; they are not needed because their idle thrust is only 40 lbf, as opposed to 400 lbf on the old engines.

Features available in FlightGear include:

* Choice of two variants: the basic Citation II or the re-engined Sierra Super II
* Several liveries
* Several checklists
* Autostart ( {{key press|s}} )
* Weight and speed limitations
* Tuned autopilot with built-in climb schedule
* Working speedbrakes (engage with {{key press|k}}, retract with {{key press|j}} - alternatively {{key press|Ctrl|b}} toggles the s/b's)
* Working thrust reversers (engage with {{key press|Del}}) on the Citation II only
* GPS navigation as an aftermarket modification

At low altitude, this aeroplane is light and slow enough for sightseeing in the canyons. At high altitude, it is fast enough for medium-haul, multiple-hour flights and GPS navigation. You can fly VFR or IFR, with or without GPS.

== Download ==
=== Option 1: SVN ===
<syntaxhighlight lang="bash">
$ svn checkout http://svn.code.sf.net/p/flightgear/fgaddon/trunk/Aircraft/Citation Citation
$ svn up
</syntaxhighlight>

=== Option 2: Tarball ===
The other way is to download a tarball from Sourceforge.

[http://sourceforge.net/p/flightgear/fgaddon/HEAD/tarball?path=/trunk/Aircraft/Citation Link]

== Startup ==
Use the aircraft checklist for startup instructions; alternatively, press {{key press|s}} for autostart.

== Performance ==
{| class="wikitable"
|-
! !! Citation II !! Sierra Super II
|-
! Never exceed speed
| 263 KIAS || 263 KIAS
|-
! Typical cruise speed at FL410
| 330 KTAS || 370 KTAS
|-
! Range at MTOW and full fuel, FL410, full throttle
| 1900 nmi || 2500 nmi
|-
! Endurance (hours) at full throttle
| 5:45 || 6:33
|-
! Climb rate at sea level
| 3000 fpm || 6000 fpm
|-
! Climb to FL410
| 45 min (stepped) || 22 min (direct)
|-
! Thrust reversers
| yes || no
|}

== Autopilot ==
The autopilot will disengage 500 feet above ground level or below the decision height selected on the radio altimeter, whichever is highest. This implies that you must climb at least to 500 ft above ground before you engage the autopilot. In addition, you should never engage autopilot while manoeuvering; always stabilize the aeroplane before you engage autopilot.

When the FD OFF button is illuminated, the autopilot is OFF. Clicking this button will engage the autopilot in wing leveler (horizontal) and pitch hold (vertical) modes. You can also engage autopilot, with the same effects, with the AP ENGAGE button between the seats. The following lateral, vertical and speed modes are available:

=== Lateral modes ===
; Wing Leveler: All lights are off
; HDG: Follow the magnetic heading bug selected on the pilot's HSI.
; NAV: Follow the radial selected on either NAV1 or NAV2. Switch between NAV1 and NAV2 using the NAV/HSI button.
; GPS: Follow the course selected by GPS. To engage, click on the NAV button a second time.
; APR: Click this button to engage both NAV1 and glideslope for an ILS approach. Note that, since the autopilot will disengage at least 500 ft above ground, this aeroplane is certified only for CAT I ILS approaches; it has no autoland capability.

=== Vertical modes ===
; Pitch hold: All lights are off. Adjust pitch (in increments of 1 degree) with the PITCH wheel between the seats.
; ALT: Climb or descend to, then maintain the altitude selected with the ALT knob left of the ADF radio. You can adjust the selected altitude with this knob or with the PITCH wheel between the seats.
; V/S: Hold current vertical speed. Adjust the selected vertical speed with the PITCH wheel between the seats.

You should engage ALT mode in more or less level flight with an angle of attack no greater than 0.2 and airspeed at least 220 KIAS. The autopilot includes a climb schedule and will climb at a speed appropriate for your engines; it will automatically decrease the rate of climb as you gain altitude.

On the base Citation II, you need a stepped climb and 45 minutes to reach FL410. The first step should be at FL330 or thereabouts.

On the re-engined Super II, you can climb all the way to FL430 in one step, even at MTOW, provided you respect the prerequisites listed above before engaging ALT mode.

=== Speed modes ===
; Autothrottle: Engage and disengage with Ctrl+S to hold current indicated airspeed. Note that the real Citation II does not have this, so you may consider using autothrottle cheating.

== Radio navigation ==
Tune the two NAV and COM radios and the sole ADF radio on the cockpit.

=== Horizontal Situation Indicators ===
On startup, the captain's [[HSI|horizontal situation indicator]] uses NAV1 and the copilot's HSI uses NAV2. The NAV/HSI button under each HSI switches between NAV1 and NAV2; you can switch the HSIs independently. If the autopilot is engaged in NAV mode, then the autopilot will also switch between NAV1 and NAV2, always following the radio selected on the captain's HSI. The best usage of this feature is as follows:

# Tune the NAV1 radio to a VOR beacon.
# Select the NAV1 radial on the captain's HSI.
# Fly the selected radial.
# Tune the NAV2 radio to another VOR beacon.
# Select the NAV2 radial on the copilot's HSI.
# When you intercept the radial selected on NAV2, click on the NAV/HSI button on the captain's side. The autopilot will now follow the NAV2 radial.
# Switch the copilot's HSI to NAV1.
# Tune NAV1 to a third VOR beacon.
# Select the NAV1 radial on the copilot's HSI.
# Repeat as necessary.

The two HSIs feature an integrated Radio Magnetic Indicator: the thin red arrow points to the selected VOR beacon (either NAV1 or NAV2). They also have a built-in Distance Measuring Equipment showing the distance between you and the selected beacon, in nautical miles.

=== Radio Magnetic Indicators ===
The cockpit has additional Radio Magnetic Indicators on both the pilot and copilot side. This indicator has two arrows and two buttons:

* The ''left'' button switches the single-stemmed arrow to point either to the NAV1 VOR beacon or to the NDB.
* The ''right'' button switches the double-stemmed arrow to point either to the NAV2 VOR beacon or to the NDB.

Combined with the HSI you can have arrows pointing simultaneously to all three beacons. By default:

* The ''single-stemmed'' arrow points to the NDB selected on the ADF radio
* The ''double-stemmed'' arrow points to the VOR beacon selected on the NAV2 radio
* The ''thin red needle'' of the HSI points to the VOR beacon selected on the NAV1 radio

=== Glideslope NAV1 indicator ===
To the left of the pilot's HSI is an additional NAV1 indicator with two needles; this merely repeats localizer and glideslope information from the HSI and from the attitude indicator.
Thus you have triple redundancy :) This instrument is hardwired to NAV1, so you can fly an ILS approach by hand while simultaneously pointing your HSI at the NAV2 beacon.

=== Distance Measuring Equipment ===
The DME shows the distance in nautical miles to the selected beacon. You can use it either to repeat the information on the HSI or to show the distance to the other beacon.
This instrument also shows your speed towards or from the beacon (''not'' your groundspeed: Only the component of your groundspeed that is on the line between you and the beacon), or
the time to go to the beacon in minutes at your current speed.

== GPS navigation ==
The original Citation II did not have a GPS but both it and the re-engined Sierra Super II have two aftermarket additions that enable basic GPS navigation.

=== ZVK500 GPS instrument ===
This instrument is available as part of the base FlightGear package and is shared with the [[Lionceau]] light propeller aircraft. It features a very basic display of current position,
next waypoint, time to waypoint, direct route (DTO) mode, etc. For more details, see [http://sourceforge.net/p/flightgear/fgdata/ci/next/tree/Aircraft/Instruments-3d/zkv500/manual.txt its documentation].

=== Control Display Unit ===
The CDU on the central console allows you to create a simple route from one airport to another.

To create a route:

# Click on the DEP ARR button.
# Type the ICAO code of your departure airport.
# Click on the ORIGIN (top left) button.
# Type the ICAO code of your destination airport.
# Click on the DEST (top right) button.
# Optionally type the departure runway number then click the RWY button.
# Click ACTIVATE.

This activates the Route Manager, which you can of course still control with the generic Route Manager dialog. The ZVK500 unit in POSITION mode will then display where you stand on the selected route.

== Development ==
=== Recently updated ===
==== Systems ====
* Several checklists have been added.
* A realistic startup procedure.
* A major overhaul of the Autopilot-systems.
* The FDM got upgraded and several bugs got fixed in the process.
* All knobs can now be turned with the mouse-wheel.

==== Instruments ====
* Added a new Lighting Panel to the pilots panel. All knobs and switches, which actually have a function are animated.
* Instrument Panel got new textures. Looks a bit more used now.
* RMI now is switchable on Nav1/ADF and Nav2/ADF.
* HSI can be switched between Nav1/Nav2/GPS with the AP control panel's NAV-button.
* A ZVK500 GPS instrument was added on the pilots instrument panel.
* A CDU was added on the center pedestal.

==== Model ====
* All exterior lights are now Rembrandt-capable.
* The missing door-ladder was added and animated.
* The speedbrakes got a major overhaul and are now much closer to the real thing, also the lower speedbrakes are added and animated.
* Several small additions to the cockpit and cabin, including an accurate circuit breaker panel, sadly without functionality for now.

=== Todo ===
* Interior Rembrandt lighting
* Fine-tuning of speedbrake's animations and add LOD
* More interior model details (e.g. better textures, overhead lights, air conditioning outlets etc.)
* Create different liveries for Citation II and Sierra Super II.
* CDU needs more functions and bug fixes

== External links ==
* {{wikipedia|Cessna Citation II}} Wikipedia article
* [http://www.sijet.com/page727822 Corporate site for the Sierra Super II aftermarket modification]

{{Cessna}}

[[Category:Business aircraft]]

Cessna 550 Citation II

2015-03-11T23:36:29Z

Circumn: /* ZVK500 GPS instrument */ Point to the git repository on SourceForge instead of gitorious which is disappearing.

{{infobox Aircraft
|image =Cessna550.jpg
|name =Cessna 550 Citation II
|type =Business jet
|authors = Curtis Olson, Syd Adams, Ludovic Brenta, chris_blues
|fdm =[[YASim]]
|status-fdm=5
|status-systems=4
|status-cockpit=4
|status-model=4
|fgname = Citation-II<br/>Sierra-Super-II
|ready = rembrandt
|development = http://sourceforge.net/p/flightgear/fgaddon/HEAD/tree/trunk/Aircraft/Citation/
|download = http://sourceforge.net/p/flightgear/fgaddon/HEAD/tarball?path=/trunk/Aircraft/Citation
}}

[[File:CitationII Cockpit.png|thumb|270px|The cockpit of a Cessna 550]]

The '''Cessna 550 Citation II''' debuted in [[FlightGear]] 0.9.8 in January 2005. It has two "special views": passenger 1 and passenger 2.

== Overview ==
The Cessna 550/551 Citation II is a light corporate jet built between 1978 and 2006. The FlightGear model is a luxury corporate jet for two pilots and seven passengers. However you should not view the original Citation II as a real jet; with a cruising speed of only 330 KTAS, it was really intended as a competitor for high-end twin turboprops.

The Cessna 550 requires two pilots; the 551 is the same aircraft certified for single-pilot use.

Later variants of this aircraft include the [[Cessna_Citation_Bravo|Cessna Citation Bravo]], which has newer avionics (available separately in FlightGear), the Cessna Citation S/II with improved wings (not currently available in FlightGear), and the Sierra Super II, available together with this aircraft in FlightGear.

The Sierra Super II is an aftermarket modification of the Cessna 550/551 which replaces the engines with Williams International FJ44-3 turbofans introduced in 2004. They
provide more thrust and less fuel consumption. Climb performance in particular is dramatically improved.

The new engines lack thrust reversers; they are not needed because their idle thrust is only 40 lbf, as opposed to 400 lbf on the old engines.

Features available in FlightGear include:

* Choice of two variants: the basic Citation II or the re-engined Sierra Super II
* Several liveries
* Several checklists
* Autostart ( {{key press|s}} )
* Weight and speed limitations
* Tuned autopilot with built-in climb schedule
* Working speedbrakes (engage with {{key press|k}}, retract with {{key press|j}} - alternatively {{key press|Ctrl|b}} toggles the s/b's)
* Working thrust reversers (engage with {{key press|Del}}) on the Citation II only
* GPS navigation as an aftermarket modification

At low altitude, this aeroplane is light and slow enough for sightseeing in the canyons. At high altitude, it is fast enough for medium-haul, multiple-hour flights and GPS navigation. You can fly VFR or IFR, with or without GPS.

== Download ==
=== Option 1: SVN ===
<syntaxhighlight lang="bash">
$ svn checkout http://svn.code.sf.net/p/flightgear/fgaddon/trunk/Aircraft/Citation Citation
$ svn up
</syntaxhighlight>

=== Option 2: Tarball ===
The other way is to download a tarball from Sourceforge.

[http://sourceforge.net/p/flightgear/fgaddon/HEAD/tarball?path=/trunk/Aircraft/Citation Link]

== Startup ==
Use the aircraft checklist for startup instructions; alternatively, press {{key press|s}} for autostart.

== Performance ==
{| class="wikitable"
|-
! !! Citation II !! Sierra Super II
|-
! Never exceed speed
| 263 KIAS || 263 KIAS
|-
! Typical cruise speed at FL410
| 330 KTAS || 370 KTAS
|-
! Range at MTOW and full fuel, FL410, full throttle
| 1900 nmi || 2500 nmi
|-
! Endurance (hours) at full throttle
| 5:45 || 6:33
|-
! Climb rate at sea level
| 3000 fpm || 6000 fpm
|-
! Climb to FL410
| 45 min (stepped) || 22 min (direct)
|-
! Thrust reversers
| yes || no
|}

== Autopilot ==
The autopilot will disengage 500 feet above ground level or below the decision height selected on the radio altimeter, whichever is highest. This implies that you must climb at least to 500 ft above ground before you engage the autopilot. In addition, you should never engage autopilot while manoeuvering; always stabilize the aeroplane before you engage autopilot.

When the FD OFF button is illuminated, the autopilot is OFF. Clicking this button will engage the autopilot in wing leveler (horizontal) and pitch hold (vertical) modes. You can also engage autopilot, with the same effects, with the AP ENGAGE button between the seats. The following lateral, vertical and speed modes are available:

=== Lateral modes ===
; Wing Leveler: All lights are off
; HDG: Follow the magnetic heading bug selected on the pilot's HSI.
; NAV: Follow the radial selected on either NAV1 or NAV2. Switch between NAV1 and NAV2 using the NAV/HSI button.
; GPS: Follow the course selected by GPS. To engage, click on the NAV button a second time.
; APR: Click this button to engage both NAV1 and glideslope for an ILS approach. Note that, since the autopilot will disengage at least 500 ft above ground, this aeroplane is certified only for CAT I ILS approaches; it has no autoland capability.

=== Vertical modes ===
; Pitch hold: All lights are off. Adjust pitch (in increments of 1 degree) with the PITCH wheel between the seats.
; ALT: Climb or descend to, then maintain the altitude selected with the ALT knob left of the ADF radio. You can adjust the selected altitude with this knob or with the PITCH wheel between the seats.
; V/S: Hold current vertical speed. Adjust the selected vertical speed with the PITCH wheel between the seats.

You should engage ALT mode in more or less level flight with an angle of attack no greater than 0.2 and airspeed at least 220 KIAS. The autopilot includes a climb schedule and will climb at a speed appropriate for your engines; it will automatically decrease the rate of climb as you gain altitude.

On the base Citation II, you need a stepped climb and 45 minutes to reach FL410. The first step should be at FL330 or thereabouts.

On the re-engined Super II, you can climb all the way to FL430 in one step, even at MTOW, provided you respect the prerequisites listed above before engaging ALT mode.

=== Speed modes ===
; Autothrottle: Engage and disengage with Ctrl+S to hold current indicated airspeed. Note that the real Citation II does not have this, so you may consider using autothrottle cheating.

== Radio navigation ==
Tune the two NAV and COM radios and the sole ADF radio on the cockpit.

=== Horizontal Situation Indicators ===
On startup, the captain's [[HSI|horizontal situation indicator]] uses NAV1 and the copilot's HSI uses NAV2. The NAV/HSI button under each HSI switches between NAV1 and NAV2; you can switch the HSIs independently. If the autopilot is engaged in NAV mode, then the autopilot will also switch between NAV1 and NAV2, always following the radio selected on the captain's HSI. The best usage of this feature is as follows:

# Tune the NAV1 radio to a VOR beacon.
# Select the NAV1 radial on the captain's HSI.
# Fly the selected radial.
# Tune the NAV2 radio to another VOR beacon.
# Select the NAV2 radial on the copilot's HSI.
# When you intercept the radial selected on NAV2, click on the NAV/HSI button on the captain's side. The autopilot will now follow the NAV2 radial.
# Switch the copilot's HSI to NAV1.
# Tune NAV1 to a third VOR beacon.
# Select the NAV1 radial on the copilot's HSI.
# Repeat as necessary.

The two HSIs feature an integrated Radio Magnetic Indicator: the thin red arrow points to the selected VOR beacon (either NAV1 or NAV2). They also have a built-in Distance Measuring Equipment showing the distance between you and the selected beacon, in nautical miles.

=== Radio Magnetic Indicators ===
The cockpit has additional Radio Magnetic Indicators on both the pilot and copilot side. This indicator has two arrows and two buttons:

* The ''left'' button switches the single-stemmed arrow to point either to the NAV1 VOR beacon or to the NDB.
* The ''right'' button switches the double-stemmed arrow to point either to the NAV2 VOR beacon or to the NDB.

Combined with the HSI you can have arrows pointing simultaneously to all three beacons. By default:

* The ''single-stemmed'' arrow points to the NDB selected on the ADF radio
* The ''double-stemmed'' arrow points to the VOR beacon selected on the NAV2 radio
* The ''thin red needle'' of the HSI points to the VOR beacon selected on the NAV1 radio

=== Glideslope NAV1 indicator ===
To the left of the pilot's HSI is an additional NAV1 indicator with two needles; this merely repeats localizer and glideslope information from the HSI and from the attitude indicator.
Thus you have triple redundancy :) This instrument is hardwired to NAV1, so you can fly an ILS approach by hand while simultaneously pointing your HSI at the NAV2 beacon.

=== Distance Measuring Equipment ===
The DME shows the distance in nautical miles to the selected beacon. You can use it either to repeat the information on the HSI or to show the distance to the other beacon.
This instrument also shows your speed towards or from the beacon (''not'' your groundspeed: Only the component of your groundspeed that is on the line between you and the beacon), or
the time to go to the beacon in minutes at your current speed.

== GPS navigation ==
The original Citation II did not have a GPS but both it and the re-engined Sierra Super II have two aftermarket additions that enable basic GPS navigation.

=== ZVK500 GPS instrument ===
This instrument is available as part of the base FlightGear package and is shared with the [[Lionceau]] light propeller aircraft. It features a very basic display of current position,
next waypoint, time to waypoint, direct route (DTO) mode, etc. For more details, see [http://sourceforge.net/p/flightgear/fgdata/ci/next/tree/Aircraft/Instruments-3d/zkv500/manual.txt its documentation].

=== Control Display Unit ===
The CDU on the central console allows you to create a simple route from one airport to another.

To create a route:

# Click on the DEP ARR button.
# Type the ICAO code of your departure airport.
# Click on the ORIGIN (top left) button.
# Type the ICAO code of your destination airport.
# Click on the DEST (top right) button.
# Optionally type the departure runway number then click the RWY button.
# Click ACTIVATE.

This activates the Route Manager, which you can of course still control with the generic Route Manager dialog. The ZVK500 unit in POSITION mode will then display where you stand on the selected route.

== Development ==
=== Recently updated ===
==== Systems ====
* Several checklists have been added.
* A realistic startup procedure.
* A major overhaul of the Autopilot-systems.
* The FDM got upgraded and several bugs got fixed in the process.
* All knobs can now be turned with the mouse-wheel.

==== Instruments ====
* Added a new Lighting Panel to the pilots panel. All knobs and switches, which actually have a function are animated.
* Instrument Panel got new textures. Looks a bit more used now.
* RMI now is switchable on Nav1/ADF and Nav2/ADF.
* HSI can be switched between Nav1/Nav2/GPS with the AP control panel's NAV-button.
* A ZVK500 GPS instrument was added on the pilots instrument panel.
* A CDU was added on the center pedestal.

==== Model ====
* All exterior lights are now Rembrandt-capable.
* The missing door-ladder was added and animated.
* The speedbrakes got a major overhaul and are now much closer to the real thing, also the lower speedbrakes are added and animated.
* Several small additions to the cockpit and cabin, including an accurate circuit breaker panel, sadly without functionality for now.

=== Todo ===
* Interior Rembrandt lighting
* Fine-tuning of speedbrake's animations and add LOD
* More interior model details (e.g. better textures, overhead lights, air conditioning outlets etc.)
* Create different liveries for Citation II and Sierra Super II.
* CDU needs more functions and bug fixes

== External links ==
* {{wikipedia|Cessna Citation II}} Wikipedia article
* [http://www.sijet.com/page727822 Corporate site for the Sierra Super II aftermarket modification]

{{Cessna}}

[[Category:Business aircraft]]

User talk:Legoboyvdlp

2015-02-13T18:02:22Z

Circumn: Flooded airports

== USA Tour 15'th November ==

Hi,

thanks for contributing to the upcoming newsletter! Please note that the newsletter is only "published" at the end of the month though. Therefore, promoting an event that will have passed by then makes little sense. You'll either have to plan more in advance and place the announcement in the newsletter the month before the event, or write a wrapup on what the event was like when it has passed ;-)

Cheers,
[[User:Gijs|Gijs]] ([[User talk:Gijs|talk]]) 21:20, 5 November 2014 (UTC)

== Flooded airports ==

According to the January 2015 newsletter, you requested that this channel be used to report flooded airports; so here is one: SOCA (Cayenne), which was flooded in jungle today; so much so that it is impossible to take off as the patch of jungle over the runway stops the aeroplane in its tracks. I can send a screenshot on request but not before next week.

[[User talk:Circumn]] 13:02, 13 February 2015 (EST)

Lockheed Constellation

2015-02-04T18:25:11Z

Circumn: Add a rating.

Cessna 550 Citation II

2015-02-04T17:19:05Z

Circumn: Remove the status as it is computed automatically from the rating. Thanks to Gijs for pointing this out.

{{infobox Aircraft
|image =Cessna550.jpg
|name =Cessna 550 Citation II
|type =Business Jet
|authors = Curtis Olson, Syd Adams, Ludovic Brenta, chrisblues
|fdm =Yasim
|status-fdm=5
|status-systems=4
|status-cockpit=4
|status-model=4
|fgname = Citation-II<br/>Sierra-Super-II
|ready = rembrandt
|download = http://sourceforge.net/p/flightgear/fgaddon/HEAD/tarball?path=/trunk/Aircraft/Citation
}}

[[File:Cessna550_cockpit.jpg|thumb|270px|The cockpit of a Cessna 550]]

The '''Cessna 550 Citation II''' debuted in [[FlightGear]] 0.9.8 in January 2005. It has two "special views": passenger 1 and passenger 2.

{{note|This article describes the Citation II in Subversion (as of January 2015), not the 3.2 release.}}

== Overview ==
The Cessna 550/551 Citation II is a light corporate jet built between 1978 and 2006. The FlightGear model is a luxury corporate jet for two pilots and seven passengers. However you should not view the original Citation II as a real jet; with a cruising speed of only 330 KTAS, it was really intended as a competitor for high-end twin turboprops.

The Cessna 550 requires two pilots; the 551 is the same aircraft certified for single-pilot use.

Later variants of this aircraft include the [[Cessna_Citation_Bravo|Cessna Citation Bravo]], which has newer avionics (available separately in FlightGear), the Cessna Citation S/II with improved wings (not currently available in FlightGear), and the Sierra Super II, available together with this aircraft in FlightGear.

The Sierra Super II is an aftermarket modification of the Cessna 550/551 which replaces the engines with Williams International FJ44-3 turbofans introduced in 2004. They
provide more thrust and less fuel consumption. Climb performance in particular is dramatically improved.

The new engines lack thrust reversers; they are not needed because their idle thrust is only 40 lbf, as opposed to 400 lbf on the old engines.

Features available in FlightGear include:

* Choice of two variants: the basic Citation II or the re-engined Sierra Super II
* Several liveries
* Several checklists
* Autostart
* Weight and speed limitations
* Tuned autopilot with built-in climb schedule
* Working speedbrakes (engage with K, retract with J)
* Working thrust reversers (engage with DEL) on the Citation II only
* GPS navigation as an aftermarket modification

At low altitude, this aeroplane is light and slow enough for sightseeing in the canyons. At high altitude, it is fast enough for medium-haul, multiple-hour flights and GPS navigation. You can fly VFR or IFR, with or without GPS.

== Startup ==
Use the aircraft checklist for startup instructions; alternatively, press S for autostart.

== Performance ==
{| class="wikitable"
|-
! !! Citation II !! Sierra Super II
|-
! Never exceed speed
| 263 KIAS || 263 KIAS
|-
! Typical cruise speed at FL410
| 330 KTAS || 370 KTAS
|-
! Range at MTOW and full fuel, FL410, full throttle
| 1900 nmi || 2500 nmi
|-
! Endurance (hours) at full throttle
| 5:45 || 6:33
|-
! Climb rate at sea level
| 3000 fpm || 6000 fpm
|-
! Climb to FL410
| 45 min (stepped) || 22 min (direct)
|-
! Thrust reversers
| yes || no
|}

== Autopilot ==
The autopilot will disengage 500 feet above ground level or below the decision height selected on the radio altimeter, whichever is highest. This implies that you must climb at least to 500 ft above ground before you engage the autopilot. In addition, you should never engage autopilot while manoeuvering; always stabilize the aeroplane before you engage autopilot.

When the FD OFF button is illuminated, the autopilot is OFF. Clicking this button will engage the autopilot in wing leveler (horizontal) and pitch hold (vertical) modes. You can also engage autopilot, with the same effects, with the AP ENGAGE button between the seats. The following lateral, vertical and speed modes are available:

=== Lateral modes ===
; Wing Leveler: All lights are off
; HDG: Follow the magnetic heading bug selected on the pilot's HSI.
; NAV: Follow the radial selected on either NAV1 or NAV2. Switch between NAV1 and NAV2 using the NAV/HSI button.
; GPS: Follow the course selected by GPS. To engage, click on the NAV button a second time.
; APR: Click this button to engage both NAV1 and glideslope for an ILS approach. Note that, since the autopilot will disengage at least 500 ft above ground, this aeroplane is certified only for CAT I ILS approaches; it has no autoland capability.

=== Vertical modes ===
; Pitch hold: All lights are off. Adjust pitch (in increments of 1 degree) with the PITCH wheel between the seats.
; ALT: Climb or descend to, then maintain the altitude selected with the ALT knob left of the ADF radio. You can adjust the selected altitude with this knob or with the PITCH wheel between the seats.
; V/S: Hold current vertical speed. Adjust the selected vertical speed with the PITCH wheel between the seats.

You should engage ALT mode in more or less level flight with an angle of attack no greater than 0.2 and airspeed at least 220 KIAS. The autopilot includes a climb schedule and will climb at a speed appropriate for your engines; it will automatically decrease the rate of climb as you gain altitude.

On the base Citation II, you need a stepped climb and 45 minutes to reach FL410. The first step should be at FL330 or thereabouts.

On the re-engined Super II, you can climb all the way to FL430 in one step, even at MTOW, provided you respect the prerequisites listed above before engaging ALT mode.

=== Speed modes ===
; Autothrottle: Engage and disengage with Ctrl+S to hold current indicated airspeed. Note that the real Citation II does not have this, so you may consider using autothrottle cheating.

== Radio navigation ==
Tune the two NAV and COM radios and the sole ADF radio on the cockpit.

=== Horizontal Situation Indicators ===
On startup, the captain's [[HSI|horizontal situation indicator]] uses NAV1 and the copilot's HSI uses NAV2. The NAV/HSI button under each HSI switches between NAV1 and NAV2; you can switch the HSIs independently. If the autopilot is engaged in NAV mode, then the autopilot will also switch between NAV1 and NAV2, always following the radio selected on the captain's HSI. The best usage of this feature is as follows:

# Tune the NAV1 radio to a VOR beacon.
# Select the NAV1 radial on the captain's HSI.
# Fly the selected radial.
# Tune the NAV2 radio to another VOR beacon.
# Select the NAV2 radial on the copilot's HSI.
# When you intercept the radial selected on NAV2, click on the NAV/HSI button on the captain's side. The autopilot will now follow the NAV2 radial.
# Switch the copilot's HSI to NAV1.
# Tune NAV1 to a third VOR beacon.
# Select the NAV1 radial on the copilot's HSI.
# Repeat as necessary.

The two HSIs feature an integrated Radio Magnetic Indicator: the thin red arrow points to the selected VOR beacon (either NAV1 or NAV2). They also have a built-in Distance Measuring Equipment showing the distance between you and the selected beacon, in nautical miles.

=== Radio Magnetic Indicators ===
The cockpit has additional Radio Magnetic Indicators on both the pilot and copilot side. This indicator has two arrows and two buttons:

* The ''left'' button switches the single-stemmed arrow to point either to the NAV1 VOR beacon or to the NDB.
* The ''right'' button switches the double-stemmed arrow to point either to the NAV2 VOR beacon or to the NDB.

Combined with the HSI you can have arrows pointing simultaneously to all three beacons. By default:

* The ''single-stemmed'' arrow points to the NDB selected on the ADF radio
* The ''double-stemmed'' arrow points to the VOR beacon selected on the NAV2 radio
* The ''thin red needle'' of the HSI points to the VOR beacon selected on the NAV1 radio

=== Glideslope NAV1 indicator ===
To the left of the pilot's HSI is an additional NAV1 indicator with two needles; this merely repeats localizer and glideslope information from the HSI and from the attitude indicator.
Thus you have triple redundancy :) This instrument is hardwired to NAV1, so you can fly an ILS approach by hand while simultaneously pointing your HSI at the NAV2 beacon.

=== Distance Measuring Equipment ===
The DME shows the distance in nautical miles to the selected beacon. You can use it either to repeat the information on the HSI or to show the distance to the other beacon.
This instrument also shows your speed towards or from the beacon (''not'' your groundspeed: Only the component of your groundspeed that is on the line between you and the beacon), or
the time to go to the beacon in minutes at your current speed.

== GPS navigation ==
The original Citation II did not have a GPS but both it and the re-engined Sierra Super II have two aftermarket additions that enable basic GPS navigation.

=== ZVK500 GPS instrument ===
This instrument is available as part of the base FlightGear package and is shared with the [[Lionceau]] light propeller aircraft. It features a very basic display of current position,
next waypoint, time to waypoint, direct route (DTO) mode, etc. For more details, see [https://gitorious.org/fg/fgdata/source/Aircraft/Instruments-3d/zkv500/manual.txt its documentation].

=== Control Display Unit ===
The CDU on the central console allows you to create a simple route from one airport to another.

To create a route:

# Click on the DEP ARR button.
# Type the ICAO code of your departure airport.
# Click on the ORIGIN (top left) button.
# Type the ICAO code of your destination airport.
# Click on the DEST (top right) button.
# Optionally type the departure runway number then click the RWY button.
# Click ACTIVATE.

This activates the Route Manager, which you can of course still control with the generic Route Manager dialog. The ZVK500 unit in POSITION mode will then display where you stand on the selected route.

== External links ==
* {{wikipedia|Cessna Citation II}} Wikipedia article
* [http://www.sijet.com/page727822 Corporate site for the Sierra Super II aftermarket modification]

{{Cessna}}

[[Category:Business aircraft]]

Cessna 550 Citation II

2015-02-03T09:28:57Z

Circumn: Capitalize the status so the aircraft shows up in the category Aircraft by status: Advanced Production.

{{infobox Aircraft
|image =Cessna550.jpg
|name =Cessna 550 Citation II
|type =Business Jet
|authors = Curtis Olson, Syd Adams, Ludovic Brenta, chrisblues
|fdm =Yasim
|status = Advanced production
|status-fdm=5
|status-systems=4
|status-cockpit=4
|status-model=4
|fgname = Citation-II<br/>Sierra-Super-II
|ready = rembrandt
|download = http://sourceforge.net/p/flightgear/fgaddon/HEAD/tarball?path=/trunk/Aircraft/Citation
}}

[[File:Cessna550_cockpit.jpg|thumb|270px|The cockpit of a Cessna 550]]

The '''Cessna 550 Citation II''' debuted in [[FlightGear]] 0.9.8 in January 2005. It has two "special views": passenger 1 and passenger 2.

{{note|This article describes the Citation II in Subversion (as of January 2015), not the 3.2 release.}}

== Overview ==
The Cessna 550/551 Citation II is a light corporate jet built between 1978 and 2006. The FlightGear model is a luxury corporate jet for two pilots and seven passengers. However you should not view the original Citation II as a real jet; with a cruising speed of only 330 KTAS, it was really intended as a competitor for high-end twin turboprops.

The Cessna 550 requires two pilots; the 551 is the same aircraft certified for single-pilot use.

Later variants of this aircraft include the [[Cessna_Citation_Bravo|Cessna Citation Bravo]], which has newer avionics (available separately in FlightGear), the Cessna Citation S/II with improved wings (not currently available in FlightGear), and the Sierra Super II, available together with this aircraft in FlightGear.

The Sierra Super II is an aftermarket modification of the Cessna 550/551 which replaces the engines with Williams International FJ44-3 turbofans introduced in 2004. They
provide more thrust and less fuel consumption. Climb performance in particular is dramatically improved.

The new engines lack thrust reversers; they are not needed because their idle thrust is only 40 lbf, as opposed to 400 lbf on the old engines.

Features available in FlightGear include:

* Choice of two variants: the basic Citation II or the re-engined Sierra Super II
* Several liveries
* Several checklists
* Autostart
* Weight and speed limitations
* Tuned autopilot with built-in climb schedule
* Working speedbrakes (engage with K, retract with J)
* Working thrust reversers (engage with DEL) on the Citation II only
* GPS navigation as an aftermarket modification

At low altitude, this aeroplane is light and slow enough for sightseeing in the canyons. At high altitude, it is fast enough for medium-haul, multiple-hour flights and GPS navigation. You can fly VFR or IFR, with or without GPS.

== Startup ==
Use the aircraft checklist for startup instructions; alternatively, press S for autostart.

== Performance ==
{| class="wikitable"
|-
! !! Citation II !! Sierra Super II
|-
! Never exceed speed
| 263 KIAS || 263 KIAS
|-
! Typical cruise speed at FL410
| 330 KTAS || 370 KTAS
|-
! Range at MTOW and full fuel, FL410, full throttle
| 1900 nmi || 2500 nmi
|-
! Endurance (hours) at full throttle
| 5:45 || 6:33
|-
! Climb rate at sea level
| 3000 fpm || 6000 fpm
|-
! Climb to FL410
| 45 min (stepped) || 22 min (direct)
|-
! Thrust reversers
| yes || no
|}

== Autopilot ==
The autopilot will disengage 500 feet above ground level or below the decision height selected on the radio altimeter, whichever is highest. This implies that you must climb at least to 500 ft above ground before you engage the autopilot. In addition, you should never engage autopilot while manoeuvering; always stabilize the aeroplane before you engage autopilot.

When the FD OFF button is illuminated, the autopilot is OFF. Clicking this button will engage the autopilot in wing leveler (horizontal) and pitch hold (vertical) modes. You can also engage autopilot, with the same effects, with the AP ENGAGE button between the seats. The following lateral, vertical and speed modes are available:

=== Lateral modes ===
; Wing Leveler: All lights are off
; HDG: Follow the magnetic heading bug selected on the pilot's HSI.
; NAV: Follow the radial selected on either NAV1 or NAV2. Switch between NAV1 and NAV2 using the NAV/HSI button.
; GPS: Follow the course selected by GPS. To engage, click on the NAV button a second time.
; APR: Click this button to engage both NAV1 and glideslope for an ILS approach. Note that, since the autopilot will disengage at least 500 ft above ground, this aeroplane is certified only for CAT I ILS approaches; it has no autoland capability.

=== Vertical modes ===
; Pitch hold: All lights are off. Adjust pitch (in increments of 1 degree) with the PITCH wheel between the seats.
; ALT: Climb or descend to, then maintain the altitude selected with the ALT knob left of the ADF radio. You can adjust the selected altitude with this knob or with the PITCH wheel between the seats.
; V/S: Hold current vertical speed. Adjust the selected vertical speed with the PITCH wheel between the seats.

You should engage ALT mode in more or less level flight with an angle of attack no greater than 0.2 and airspeed at least 220 KIAS. The autopilot includes a climb schedule and will climb at a speed appropriate for your engines; it will automatically decrease the rate of climb as you gain altitude.

On the base Citation II, you need a stepped climb and 45 minutes to reach FL410. The first step should be at FL330 or thereabouts.

On the re-engined Super II, you can climb all the way to FL430 in one step, even at MTOW, provided you respect the prerequisites listed above before engaging ALT mode.

=== Speed modes ===
; Autothrottle: Engage and disengage with Ctrl+S to hold current indicated airspeed. Note that the real Citation II does not have this, so you may consider using autothrottle cheating.

== Radio navigation ==
Tune the two NAV and COM radios and the sole ADF radio on the cockpit.

=== Horizontal Situation Indicators ===
On startup, the captain's [[HSI|horizontal situation indicator]] uses NAV1 and the copilot's HSI uses NAV2. The NAV/HSI button under each HSI switches between NAV1 and NAV2; you can switch the HSIs independently. If the autopilot is engaged in NAV mode, then the autopilot will also switch between NAV1 and NAV2, always following the radio selected on the captain's HSI. The best usage of this feature is as follows:

# Tune the NAV1 radio to a VOR beacon.
# Select the NAV1 radial on the captain's HSI.
# Fly the selected radial.
# Tune the NAV2 radio to another VOR beacon.
# Select the NAV2 radial on the copilot's HSI.
# When you intercept the radial selected on NAV2, click on the NAV/HSI button on the captain's side. The autopilot will now follow the NAV2 radial.
# Switch the copilot's HSI to NAV1.
# Tune NAV1 to a third VOR beacon.
# Select the NAV1 radial on the copilot's HSI.
# Repeat as necessary.

The two HSIs feature an integrated Radio Magnetic Indicator: the thin red arrow points to the selected VOR beacon (either NAV1 or NAV2). They also have a built-in Distance Measuring Equipment showing the distance between you and the selected beacon, in nautical miles.

=== Radio Magnetic Indicators ===
The cockpit has additional Radio Magnetic Indicators on both the pilot and copilot side. This indicator has two arrows and two buttons:

* The ''left'' button switches the single-stemmed arrow to point either to the NAV1 VOR beacon or to the NDB.
* The ''right'' button switches the double-stemmed arrow to point either to the NAV2 VOR beacon or to the NDB.

Combined with the HSI you can have arrows pointing simultaneously to all three beacons. By default:

* The ''single-stemmed'' arrow points to the NDB selected on the ADF radio
* The ''double-stemmed'' arrow points to the VOR beacon selected on the NAV2 radio
* The ''thin red needle'' of the HSI points to the VOR beacon selected on the NAV1 radio

=== Glideslope NAV1 indicator ===
To the left of the pilot's HSI is an additional NAV1 indicator with two needles; this merely repeats localizer and glideslope information from the HSI and from the attitude indicator.
Thus you have triple redundancy :) This instrument is hardwired to NAV1, so you can fly an ILS approach by hand while simultaneously pointing your HSI at the NAV2 beacon.

=== Distance Measuring Equipment ===
The DME shows the distance in nautical miles to the selected beacon. You can use it either to repeat the information on the HSI or to show the distance to the other beacon.
This instrument also shows your speed towards or from the beacon (''not'' your groundspeed: Only the component of your groundspeed that is on the line between you and the beacon), or
the time to go to the beacon in minutes at your current speed.

== GPS navigation ==
The original Citation II did not have a GPS but both it and the re-engined Sierra Super II have two aftermarket additions that enable basic GPS navigation.

=== ZVK500 GPS instrument ===
This instrument is available as part of the base FlightGear package and is shared with the [[Lionceau]] light propeller aircraft. It features a very basic display of current position,
next waypoint, time to waypoint, direct route (DTO) mode, etc. For more details, see [https://gitorious.org/fg/fgdata/source/Aircraft/Instruments-3d/zkv500/manual.txt its documentation].

=== Control Display Unit ===
The CDU on the central console allows you to create a simple route from one airport to another.

To create a route:

# Click on the DEP ARR button.
# Type the ICAO code of your departure airport.
# Click on the ORIGIN (top left) button.
# Type the ICAO code of your destination airport.
# Click on the DEST (top right) button.
# Optionally type the departure runway number then click the RWY button.
# Click ACTIVATE.

This activates the Route Manager, which you can of course still control with the generic Route Manager dialog. The ZVK500 unit in POSITION mode will then display where you stand on the selected route.

== External links ==
* {{wikipedia|Cessna Citation II}} Wikipedia article
* [http://www.sijet.com/page727822 Corporate site for the Sierra Super II aftermarket modification]

{{Cessna}}

[[Category:Business aircraft]]

Cessna 550 Citation II

2015-01-28T20:21:37Z

Circumn: Typo.

{{infobox Aircraft
|image =Cessna550.jpg
|name =Cessna 550 Citation II
|type =Business Jet
|authors = Curtis Olson, Syd Adams, Ludovic Brenta, chrisblues
|fdm =Yasim
|status = advanced production
|status-fdm=5
|status-systems=4
|status-cockpit=4
|status-model=4
|fgname = Citation-II<br/>Sierra-Super-II
|ready = rembrandt
|download = http://sourceforge.net/p/flightgear/fgaddon/HEAD/tarball?path=/trunk/Aircraft/Citation
}}

[[File:Cessna550_cockpit.jpg|thumb|270px|The cockpit of a Cessna 550]]

The '''Cessna 550 Citation II''' debuted in [[FlightGear]] 0.9.8 in January 2005. It has two "special views": passenger 1 and passenger 2.

{{note|This article describes the Citation II in Subversion (as of January 2015), not the 3.2 release.}}

== Overview ==
The Cessna 550/551 Citation II is a light corporate jet built between 1978 and 2006. The FlightGear model is a luxury corporate jet for two pilots and seven passengers. However you should not view the original Citation II as a real jet; with a cruising speed of only 330 KTAS, it was really intended as a competitor for high-end twin turboprops.

The Cessna 550 requires two pilots; the 551 is the same aircraft certified for single-pilot use.

Later variants of this aircraft include the [[Cessna_Citation_Bravo|Cessna Citation Bravo]], which has newer avionics (available separately in FlightGear), the Cessna Citation S/II with improved wings (not currently available in FlightGear), and the Sierra Super II, available together with this aircraft in FlightGear.

The Sierra Super II is an aftermarket modification of the Cessna 550/551 which replaces the engines with Williams International FJ44-3 turbofans introduced in 2004. They
provide more thrust and less fuel consumption. Climb performance in particular is dramatically improved.

The new engines lack thrust reversers; they are not needed because their idle thrust is only 40 lbf, as opposed to 400 lbf on the old engines.

Features available in FlightGear include:

* Choice of two variants: the basic Citation II or the re-engined Sierra Super II
* Several liveries
* Several checklists
* Autostart
* Weight and speed limitations
* Tuned autopilot with built-in climb schedule
* Working speedbrakes (engage with K, retract with J)
* Working thrust reversers (engage with DEL) on the Citation II only
* GPS navigation as an aftermarket modification

At low altitude, this aeroplane is light and slow enough for sightseeing in the canyons. At high altitude, it is fast enough for medium-haul, multiple-hour flights and GPS navigation. You can fly VFR or IFR, with or without GPS.

== Startup ==
Use the aircraft checklist for startup instructions; alternatively, press S for autostart.

== Performance ==
{| class="wikitable"
|-
! !! Citation II !! Sierra Super II
|-
! Never exceed speed
| 263 KIAS || 263 KIAS
|-
! Typical cruise speed at FL410
| 330 KTAS || 370 KTAS
|-
! Range at MTOW and full fuel, FL410, full throttle
| 1900 nmi || 2500 nmi
|-
! Endurance (hours) at full throttle
| 5:45 || 6:33
|-
! Climb rate at sea level
| 3000 fpm || 6000 fpm
|-
! Climb to FL410
| 45 min (stepped) || 22 min (direct)
|-
! Thrust reversers
| yes || no
|}

== Autopilot ==
The autopilot will disengage 500 feet above ground level or below the decision height selected on the radio altimeter, whichever is highest. This implies that you must climb at least to 500 ft above ground before you engage the autopilot. In addition, you should never engage autopilot while manoeuvering; always stabilize the aeroplane before you engage autopilot.

When the FD OFF button is illuminated, the autopilot is OFF. Clicking this button will engage the autopilot in wing leveler (horizontal) and pitch hold (vertical) modes. You can also engage autopilot, with the same effects, with the AP ENGAGE button between the seats. The following lateral, vertical and speed modes are available:

=== Lateral modes ===
; Wing Leveler: All lights are off
; HDG: Follow the magnetic heading bug selected on the pilot's HSI.
; NAV: Follow the radial selected on either NAV1 or NAV2. Switch between NAV1 and NAV2 using the NAV/HSI button.
; GPS: Follow the course selected by GPS. To engage, click on the NAV button a second time.
; APR: Click this button to engage both NAV1 and glideslope for an ILS approach. Note that, since the autopilot will disengage at least 500 ft above ground, this aeroplane is certified only for CAT I ILS approaches; it has no autoland capability.

=== Vertical modes ===
; Pitch hold: All lights are off. Adjust pitch (in increments of 1 degree) with the PITCH wheel between the seats.
; ALT: Climb or descend to, then maintain the altitude selected with the ALT knob left of the ADF radio. You can adjust the selected altitude with this knob or with the PITCH wheel between the seats.
; V/S: Hold current vertical speed. Adjust the selected vertical speed with the PITCH wheel between the seats.

You should engage ALT mode in more or less level flight with an angle of attack no greater than 0.2 and airspeed at least 220 KIAS. The autopilot includes a climb schedule and will climb at a speed appropriate for your engines; it will automatically decrease the rate of climb as you gain altitude.

On the base Citation II, you need a stepped climb and 45 minutes to reach FL410. The first step should be at FL330 or thereabouts.

On the re-engined Super II, you can climb all the way to FL430 in one step, even at MTOW, provided you respect the prerequisites listed above before engaging ALT mode.

=== Speed modes ===
; Autothrottle: Engage and disengage with Ctrl+S to hold current indicated airspeed. Note that the real Citation II does not have this, so you may consider using autothrottle cheating.

== Radio navigation ==
Tune the two NAV and COM radios and the sole ADF radio on the cockpit.

=== Horizontal Situation Indicators ===
On startup, the captain's [[HSI|horizontal situation indicator]] uses NAV1 and the copilot's HSI uses NAV2. The NAV/HSI button under each HSI switches between NAV1 and NAV2; you can switch the HSIs independently. If the autopilot is engaged in NAV mode, then the autopilot will also switch between NAV1 and NAV2, always following the radio selected on the captain's HSI. The best usage of this feature is as follows:

# Tune the NAV1 radio to a VOR beacon.
# Select the NAV1 radial on the captain's HSI.
# Fly the selected radial.
# Tune the NAV2 radio to another VOR beacon.
# Select the NAV2 radial on the copilot's HSI.
# When you intercept the radial selected on NAV2, click on the NAV/HSI button on the captain's side. The autopilot will now follow the NAV2 radial.
# Switch the copilot's HSI to NAV1.
# Tune NAV1 to a third VOR beacon.
# Select the NAV1 radial on the copilot's HSI.
# Repeat as necessary.

The two HSIs feature an integrated Radio Magnetic Indicator: the thin red arrow points to the selected VOR beacon (either NAV1 or NAV2). They also have a built-in Distance Measuring Equipment showing the distance between you and the selected beacon, in nautical miles.

=== Radio Magnetic Indicators ===
The cockpit has additional Radio Magnetic Indicators on both the pilot and copilot side. This indicator has two arrows and two buttons:

* The ''left'' button switches the single-stemmed arrow to point either to the NAV1 VOR beacon or to the NDB.
* The ''right'' button switches the double-stemmed arrow to point either to the NAV2 VOR beacon or to the NDB.

Combined with the HSI you can have arrows pointing simultaneously to all three beacons. By default:

* The ''single-stemmed'' arrow points to the NDB selected on the ADF radio
* The ''double-stemmed'' arrow points to the VOR beacon selected on the NAV2 radio
* The ''thin red needle'' of the HSI points to the VOR beacon selected on the NAV1 radio

=== Glideslope NAV1 indicator ===
To the left of the pilot's HSI is an additional NAV1 indicator with two needles; this merely repeats localizer and glideslope information from the HSI and from the attitude indicator.
Thus you have triple redundancy :) This instrument is hardwired to NAV1, so you can fly an ILS approach by hand while simultaneously pointing your HSI at the NAV2 beacon.

=== Distance Measuring Equipment ===
The DME shows the distance in nautical miles to the selected beacon. You can use it either to repeat the information on the HSI or to show the distance to the other beacon.
This instrument also shows your speed towards or from the beacon (''not'' your groundspeed: Only the component of your groundspeed that is on the line between you and the beacon), or
the time to go to the beacon in minutes at your current speed.

== GPS navigation ==
The original Citation II did not have a GPS but both it and the re-engined Sierra Super II have two aftermarket additions that enable basic GPS navigation.

=== ZVK500 GPS instrument ===
This instrument is available as part of the base FlightGear package and is shared with the [[Lionceau]] light propeller aircraft. It features a very basic display of current position,
next waypoint, time to waypoint, direct route (DTO) mode, etc. For more details, see [https://gitorious.org/fg/fgdata/source/Aircraft/Instruments-3d/zkv500/manual.txt its documentation].

=== Control Display Unit ===
The CDU on the central console allows you to create a simple route from one airport to another.

To create a route:

# Click on the DEP ARR button.
# Type the ICAO code of your departure airport.
# Click on the ORIGIN (top left) button.
# Type the ICAO code of your destination airport.
# Click on the DEST (top right) button.
# Optionally type the departure runway number then click the RWY button.
# Click ACTIVATE.

This activates the Route Manager, which you can of course still control with the generic Route Manager dialog. The ZVK500 unit in POSITION mode will then display where you stand on the selected route.

== External links ==
* {{wikipedia|Cessna Citation II}} Wikipedia article
* [http://www.sijet.com/page727822 Corporate site for the Sierra Super II aftermarket modification]

{{Cessna}}

[[Category:Business aircraft]]

Cessna 550 Citation II

2015-01-28T20:20:44Z

Circumn: Add climb to FL410 performance in minutes

{{infobox Aircraft
|image =Cessna550.jpg
|name =Cessna 550 Citation II
|type =Business Jet
|authors = Curtis Olson, Syd Adams, Ludovic Brenta, chrisblues
|fdm =Yasim
|status = advanced production
|status-fdm=5
|status-systems=4
|status-cockpit=4
|status-model=4
|fgname = Citation-II<br/>Sierra-Super-II
|ready = rembrandt
|download = http://sourceforge.net/p/flightgear/fgaddon/HEAD/tarball?path=/trunk/Aircraft/Citation
}}

[[File:Cessna550_cockpit.jpg|thumb|270px|The cockpit of a Cessna 550]]

The '''Cessna 550 Citation II''' debuted in [[FlightGear]] 0.9.8 in January 2005. It has two "special views": passenger 1 and passenger 2.

{{note|This article describes the Citation II in Subversion (as of January 2015), not the 3.2 release.}}

== Overview ==
The Cessna 550/551 Citation II is a light corporate jet built between 1978 and 2006. The FlightGear model is a luxury corporate jet for two pilots and seven passengers. However you should not view the original Citation II as a real jet; with a cruising speed of only 330 KTAS, it was really intended as a competitor for high-end twin turboprops.

The Cessna 550 requires two pilots; the 551 is the same aircraft certified for single-pilot use.

Later variants of this aircraft include the [[Cessna_Citation_Bravo|Cessna Citation Bravo]], which has newer avionics (available separately in FlightGear), the Cessna Citation S/II with improved wings (not currently available in FlightGear), and the Sierra Super II, available together with this aircraft in FlightGear.

The Sierra Super II is an aftermarket modification of the Cessna 550/551 which replaces the engines with Williams International FJ44-3 turbofans introduced in 2004. They
provide more thrust and less fuel consumption. Climb performance in particular is dramatically improved.

The new engines lack thrust reversers; they are not needed because their idle thrust is only 40 lbf, as opposed to 400 lbf on the old engines.

Features available in FlightGear include:

* Choice of two variants: the basic Citation II or the re-engined Sierra Super II
* Several liveries
* Several checklists
* Autostart
* Weight and speed limitations
* Tuned autopilot with built-in climb schedule
* Working speedbrakes (engage with K, retract with J)
* Working thrust reversers (engage with DEL) on the Citation II only
* GPS navigation as an aftermarket modification

At low altitude, this aeroplane is light and slow enough for sightseeing in the canyons. At high altitude, it is fast enough for medium-haul, multiple-hour flights and GPS navigation. You can fly VFR or IFR, with or without GPS.

== Startup ==
Use the aircraft checklist for startup instructions; alternatively, press S for autostart.

== Performance ==
{| class="wikitable"
|-
! !! Citation II !! Sierra Super II
|-
! Never exceed speed
| 263 KIAS || 263 KIAS
|-
! Typical cruise speed at FL410
| 330 KTAS || 370 KTAS
|-
! Range at MTOW and full fuel, FL410, full throttle
| 1900 nmi || 2500 nmi
|-
! Endurance (hours) at full throttle
| 5:45 || 6:33
|-
! Climb rate at sea level
| 3000 fpm || 6000 fpm
|-
! Climb to FL410
| 45 min (stepped) | 22 min (direct)
|-
! Thrust reversers
| yes || no
|}

== Autopilot ==
The autopilot will disengage 500 feet above ground level or below the decision height selected on the radio altimeter, whichever is highest. This implies that you must climb at least to 500 ft above ground before you engage the autopilot. In addition, you should never engage autopilot while manoeuvering; always stabilize the aeroplane before you engage autopilot.

When the FD OFF button is illuminated, the autopilot is OFF. Clicking this button will engage the autopilot in wing leveler (horizontal) and pitch hold (vertical) modes. You can also engage autopilot, with the same effects, with the AP ENGAGE button between the seats. The following lateral, vertical and speed modes are available:

=== Lateral modes ===
; Wing Leveler: All lights are off
; HDG: Follow the magnetic heading bug selected on the pilot's HSI.
; NAV: Follow the radial selected on either NAV1 or NAV2. Switch between NAV1 and NAV2 using the NAV/HSI button.
; GPS: Follow the course selected by GPS. To engage, click on the NAV button a second time.
; APR: Click this button to engage both NAV1 and glideslope for an ILS approach. Note that, since the autopilot will disengage at least 500 ft above ground, this aeroplane is certified only for CAT I ILS approaches; it has no autoland capability.

=== Vertical modes ===
; Pitch hold: All lights are off. Adjust pitch (in increments of 1 degree) with the PITCH wheel between the seats.
; ALT: Climb or descend to, then maintain the altitude selected with the ALT knob left of the ADF radio. You can adjust the selected altitude with this knob or with the PITCH wheel between the seats.
; V/S: Hold current vertical speed. Adjust the selected vertical speed with the PITCH wheel between the seats.

You should engage ALT mode in more or less level flight with an angle of attack no greater than 0.2 and airspeed at least 220 KIAS. The autopilot includes a climb schedule and will climb at a speed appropriate for your engines; it will automatically decrease the rate of climb as you gain altitude.

On the base Citation II, you need a stepped climb and 45 minutes to reach FL410. The first step should be at FL330 or thereabouts.

On the re-engined Super II, you can climb all the way to FL430 in one step, even at MTOW, provided you respect the prerequisites listed above before engaging ALT mode.

=== Speed modes ===
; Autothrottle: Engage and disengage with Ctrl+S to hold current indicated airspeed. Note that the real Citation II does not have this, so you may consider using autothrottle cheating.

== Radio navigation ==
Tune the two NAV and COM radios and the sole ADF radio on the cockpit.

=== Horizontal Situation Indicators ===
On startup, the captain's [[HSI|horizontal situation indicator]] uses NAV1 and the copilot's HSI uses NAV2. The NAV/HSI button under each HSI switches between NAV1 and NAV2; you can switch the HSIs independently. If the autopilot is engaged in NAV mode, then the autopilot will also switch between NAV1 and NAV2, always following the radio selected on the captain's HSI. The best usage of this feature is as follows:

# Tune the NAV1 radio to a VOR beacon.
# Select the NAV1 radial on the captain's HSI.
# Fly the selected radial.
# Tune the NAV2 radio to another VOR beacon.
# Select the NAV2 radial on the copilot's HSI.
# When you intercept the radial selected on NAV2, click on the NAV/HSI button on the captain's side. The autopilot will now follow the NAV2 radial.
# Switch the copilot's HSI to NAV1.
# Tune NAV1 to a third VOR beacon.
# Select the NAV1 radial on the copilot's HSI.
# Repeat as necessary.

The two HSIs feature an integrated Radio Magnetic Indicator: the thin red arrow points to the selected VOR beacon (either NAV1 or NAV2). They also have a built-in Distance Measuring Equipment showing the distance between you and the selected beacon, in nautical miles.

=== Radio Magnetic Indicators ===
The cockpit has additional Radio Magnetic Indicators on both the pilot and copilot side. This indicator has two arrows and two buttons:

* The ''left'' button switches the single-stemmed arrow to point either to the NAV1 VOR beacon or to the NDB.
* The ''right'' button switches the double-stemmed arrow to point either to the NAV2 VOR beacon or to the NDB.

Combined with the HSI you can have arrows pointing simultaneously to all three beacons. By default:

* The ''single-stemmed'' arrow points to the NDB selected on the ADF radio
* The ''double-stemmed'' arrow points to the VOR beacon selected on the NAV2 radio
* The ''thin red needle'' of the HSI points to the VOR beacon selected on the NAV1 radio

=== Glideslope NAV1 indicator ===
To the left of the pilot's HSI is an additional NAV1 indicator with two needles; this merely repeats localizer and glideslope information from the HSI and from the attitude indicator.
Thus you have triple redundancy :) This instrument is hardwired to NAV1, so you can fly an ILS approach by hand while simultaneously pointing your HSI at the NAV2 beacon.

=== Distance Measuring Equipment ===
The DME shows the distance in nautical miles to the selected beacon. You can use it either to repeat the information on the HSI or to show the distance to the other beacon.
This instrument also shows your speed towards or from the beacon (''not'' your groundspeed: Only the component of your groundspeed that is on the line between you and the beacon), or
the time to go to the beacon in minutes at your current speed.

== GPS navigation ==
The original Citation II did not have a GPS but both it and the re-engined Sierra Super II have two aftermarket additions that enable basic GPS navigation.

=== ZVK500 GPS instrument ===
This instrument is available as part of the base FlightGear package and is shared with the [[Lionceau]] light propeller aircraft. It features a very basic display of current position,
next waypoint, time to waypoint, direct route (DTO) mode, etc. For more details, see [https://gitorious.org/fg/fgdata/source/Aircraft/Instruments-3d/zkv500/manual.txt its documentation].

=== Control Display Unit ===
The CDU on the central console allows you to create a simple route from one airport to another.

To create a route:

# Click on the DEP ARR button.
# Type the ICAO code of your departure airport.
# Click on the ORIGIN (top left) button.
# Type the ICAO code of your destination airport.
# Click on the DEST (top right) button.
# Optionally type the departure runway number then click the RWY button.
# Click ACTIVATE.

This activates the Route Manager, which you can of course still control with the generic Route Manager dialog. The ZVK500 unit in POSITION mode will then display where you stand on the selected route.

== External links ==
* {{wikipedia|Cessna Citation II}} Wikipedia article
* [http://www.sijet.com/page727822 Corporate site for the Sierra Super II aftermarket modification]

{{Cessna}}

[[Category:Business aircraft]]

Cessna 550 Citation II

2015-01-28T20:15:28Z

Circumn: External link to the Sierra Super II

{{infobox Aircraft
|image =Cessna550.jpg
|name =Cessna 550 Citation II
|type =Business Jet
|authors = Curtis Olson, Syd Adams, Ludovic Brenta, chrisblues
|fdm =Yasim
|status = advanced production
|status-fdm=5
|status-systems=4
|status-cockpit=4
|status-model=4
|fgname = Citation-II<br/>Sierra-Super-II
|ready = rembrandt
|download = http://sourceforge.net/p/flightgear/fgaddon/HEAD/tarball?path=/trunk/Aircraft/Citation
}}

[[File:Cessna550_cockpit.jpg|thumb|270px|The cockpit of a Cessna 550]]

The '''Cessna 550 Citation II''' debuted in [[FlightGear]] 0.9.8 in January 2005. It has two "special views": passenger 1 and passenger 2.

{{note|This article describes the Citation II in Subversion (as of January 2015), not the 3.2 release.}}

== Overview ==
The Cessna 550/551 Citation II is a light corporate jet built between 1978 and 2006. The FlightGear model is a luxury corporate jet for two pilots and seven passengers. However you should not view the original Citation II as a real jet; with a cruising speed of only 330 KTAS, it was really intended as a competitor for high-end twin turboprops.

The Cessna 550 requires two pilots; the 551 is the same aircraft certified for single-pilot use.

Later variants of this aircraft include the [[Cessna_Citation_Bravo|Cessna Citation Bravo]], which has newer avionics (available separately in FlightGear), the Cessna Citation S/II with improved wings (not currently available in FlightGear), and the Sierra Super II, available together with this aircraft in FlightGear.

The Sierra Super II is an aftermarket modification of the Cessna 550/551 which replaces the engines with Williams International FJ44-3 turbofans introduced in 2004. They
provide more thrust and less fuel consumption. Climb performance in particular is dramatically improved.

The new engines lack thrust reversers; they are not needed because their idle thrust is only 40 lbf, as opposed to 400 lbf on the old engines.

Features available in FlightGear include:

* Choice of two variants: the basic Citation II or the re-engined Sierra Super II
* Several liveries
* Several checklists
* Autostart
* Weight and speed limitations
* Tuned autopilot with built-in climb schedule
* Working speedbrakes (engage with K, retract with J)
* Working thrust reversers (engage with DEL) on the Citation II only
* GPS navigation as an aftermarket modification

At low altitude, this aeroplane is light and slow enough for sightseeing in the canyons. At high altitude, it is fast enough for medium-haul, multiple-hour flights and GPS navigation. You can fly VFR or IFR, with or without GPS.

== Startup ==
Use the aircraft checklist for startup instructions; alternatively, press S for autostart.

== Performance ==
{| class="wikitable"
|-
! !! Citation II !! Sierra Super II
|-
! Never exceed speed
| 263 KIAS || 263 KIAS
|-
! Typical cruise speed at FL410
| 330 KTAS || 370 KTAS
|-
! Range at MTOW and full fuel, FL410, full throttle
| 1900 nmi || 2500 nmi
|-
! Endurance (hours) at full throttle
| 5:45 || 6:33
|-
! Climb rate at sea level
| 3000 fpm || 6000 fpm
|-
! Thrust reversers
| yes || no
|}

== Autopilot ==
The autopilot will disengage 500 feet above ground level or below the decision height selected on the radio altimeter, whichever is highest. This implies that you must climb at least to 500 ft above ground before you engage the autopilot. In addition, you should never engage autopilot while manoeuvering; always stabilize the aeroplane before you engage autopilot.

When the FD OFF button is illuminated, the autopilot is OFF. Clicking this button will engage the autopilot in wing leveler (horizontal) and pitch hold (vertical) modes. You can also engage autopilot, with the same effects, with the AP ENGAGE button between the seats. The following lateral, vertical and speed modes are available:

=== Lateral modes ===
; Wing Leveler: All lights are off
; HDG: Follow the magnetic heading bug selected on the pilot's HSI.
; NAV: Follow the radial selected on either NAV1 or NAV2. Switch between NAV1 and NAV2 using the NAV/HSI button.
; GPS: Follow the course selected by GPS. To engage, click on the NAV button a second time.
; APR: Click this button to engage both NAV1 and glideslope for an ILS approach. Note that, since the autopilot will disengage at least 500 ft above ground, this aeroplane is certified only for CAT I ILS approaches; it has no autoland capability.

=== Vertical modes ===
; Pitch hold: All lights are off. Adjust pitch (in increments of 1 degree) with the PITCH wheel between the seats.
; ALT: Climb or descend to, then maintain the altitude selected with the ALT knob left of the ADF radio. You can adjust the selected altitude with this knob or with the PITCH wheel between the seats.
; V/S: Hold current vertical speed. Adjust the selected vertical speed with the PITCH wheel between the seats.

You should engage ALT mode in more or less level flight with an angle of attack no greater than 0.2 and airspeed at least 220 KIAS. The autopilot includes a climb schedule and will climb at a speed appropriate for your engines; it will automatically decrease the rate of climb as you gain altitude.

On the base Citation II, you need a stepped climb and 45 minutes to reach FL410. The first step should be at FL330 or thereabouts.

On the re-engined Super II, you can climb all the way to FL430 in one step, even at MTOW, provided you respect the prerequisites listed above before engaging ALT mode.

=== Speed modes ===
; Autothrottle: Engage and disengage with Ctrl+S to hold current indicated airspeed. Note that the real Citation II does not have this, so you may consider using autothrottle cheating.

== Radio navigation ==
Tune the two NAV and COM radios and the sole ADF radio on the cockpit.

=== Horizontal Situation Indicators ===
On startup, the captain's [[HSI|horizontal situation indicator]] uses NAV1 and the copilot's HSI uses NAV2. The NAV/HSI button under each HSI switches between NAV1 and NAV2; you can switch the HSIs independently. If the autopilot is engaged in NAV mode, then the autopilot will also switch between NAV1 and NAV2, always following the radio selected on the captain's HSI. The best usage of this feature is as follows:

# Tune the NAV1 radio to a VOR beacon.
# Select the NAV1 radial on the captain's HSI.
# Fly the selected radial.
# Tune the NAV2 radio to another VOR beacon.
# Select the NAV2 radial on the copilot's HSI.
# When you intercept the radial selected on NAV2, click on the NAV/HSI button on the captain's side. The autopilot will now follow the NAV2 radial.
# Switch the copilot's HSI to NAV1.
# Tune NAV1 to a third VOR beacon.
# Select the NAV1 radial on the copilot's HSI.
# Repeat as necessary.

The two HSIs feature an integrated Radio Magnetic Indicator: the thin red arrow points to the selected VOR beacon (either NAV1 or NAV2). They also have a built-in Distance Measuring Equipment showing the distance between you and the selected beacon, in nautical miles.

=== Radio Magnetic Indicators ===
The cockpit has additional Radio Magnetic Indicators on both the pilot and copilot side. This indicator has two arrows and two buttons:

* The ''left'' button switches the single-stemmed arrow to point either to the NAV1 VOR beacon or to the NDB.
* The ''right'' button switches the double-stemmed arrow to point either to the NAV2 VOR beacon or to the NDB.

Combined with the HSI you can have arrows pointing simultaneously to all three beacons. By default:

* The ''single-stemmed'' arrow points to the NDB selected on the ADF radio
* The ''double-stemmed'' arrow points to the VOR beacon selected on the NAV2 radio
* The ''thin red needle'' of the HSI points to the VOR beacon selected on the NAV1 radio

=== Glideslope NAV1 indicator ===
To the left of the pilot's HSI is an additional NAV1 indicator with two needles; this merely repeats localizer and glideslope information from the HSI and from the attitude indicator.
Thus you have triple redundancy :) This instrument is hardwired to NAV1, so you can fly an ILS approach by hand while simultaneously pointing your HSI at the NAV2 beacon.

=== Distance Measuring Equipment ===
The DME shows the distance in nautical miles to the selected beacon. You can use it either to repeat the information on the HSI or to show the distance to the other beacon.
This instrument also shows your speed towards or from the beacon (''not'' your groundspeed: Only the component of your groundspeed that is on the line between you and the beacon), or
the time to go to the beacon in minutes at your current speed.

== GPS navigation ==
The original Citation II did not have a GPS but both it and the re-engined Sierra Super II have two aftermarket additions that enable basic GPS navigation.

=== ZVK500 GPS instrument ===
This instrument is available as part of the base FlightGear package and is shared with the [[Lionceau]] light propeller aircraft. It features a very basic display of current position,
next waypoint, time to waypoint, direct route (DTO) mode, etc. For more details, see [https://gitorious.org/fg/fgdata/source/Aircraft/Instruments-3d/zkv500/manual.txt its documentation].

=== Control Display Unit ===
The CDU on the central console allows you to create a simple route from one airport to another.

To create a route:

# Click on the DEP ARR button.
# Type the ICAO code of your departure airport.
# Click on the ORIGIN (top left) button.
# Type the ICAO code of your destination airport.
# Click on the DEST (top right) button.
# Optionally type the departure runway number then click the RWY button.
# Click ACTIVATE.

This activates the Route Manager, which you can of course still control with the generic Route Manager dialog. The ZVK500 unit in POSITION mode will then display where you stand on the selected route.

== External links ==
* {{wikipedia|Cessna Citation II}} Wikipedia article
* [http://www.sijet.com/page727822 Corporate site for the Sierra Super II aftermarket modification]

{{Cessna}}

[[Category:Business aircraft]]

Cessna 550 Citation II

2015-01-28T20:10:25Z

Circumn: Hyperlink to the Lionceau. Typo corrections.

{{infobox Aircraft
|image =Cessna550.jpg
|name =Cessna 550 Citation II
|type =Business Jet
|authors = Curtis Olson, Syd Adams, Ludovic Brenta, chrisblues
|fdm =Yasim
|status = advanced production
|status-fdm=5
|status-systems=4
|status-cockpit=4
|status-model=4
|fgname = Citation-II<br/>Sierra-Super-II
|ready = rembrandt
|download = http://sourceforge.net/p/flightgear/fgaddon/HEAD/tarball?path=/trunk/Aircraft/Citation
}}

[[File:Cessna550_cockpit.jpg|thumb|270px|The cockpit of a Cessna 550]]

The '''Cessna 550 Citation II''' debuted in [[FlightGear]] 0.9.8 in January 2005. It has two "special views": passenger 1 and passenger 2.

{{note|This article describes the Citation II in Subversion (as of January 2015), not the 3.2 release.}}

== Overview ==
The Cessna 550/551 Citation II is a light corporate jet built between 1978 and 2006. The FlightGear model is a luxury corporate jet for two pilots and seven passengers. However you should not view the original Citation II as a real jet; with a cruising speed of only 330 KTAS, it was really intended as a competitor for high-end twin turboprops.

The Cessna 550 requires two pilots; the 551 is the same aircraft certified for single-pilot use.

Later variants of this aircraft include the [[Cessna_Citation_Bravo|Cessna Citation Bravo]], which has newer avionics (available separately in FlightGear), the Cessna Citation S/II with improved wings (not currently available in FlightGear), and the Sierra Super II, available together with this aircraft in FlightGear.

The Sierra Super II is an aftermarket modification of the Cessna 550/551 which replaces the engines with Williams International FJ44-3 turbofans introduced in 2004. They
provide more thrust and less fuel consumption. Climb performance in particular is dramatically improved.

The new engines lack thrust reversers; they are not needed because their idle thrust is only 40 lbf, as opposed to 400 lbf on the old engines.

Features available in FlightGear include:

* Choice of two variants: the basic Citation II or the re-engined Sierra Super II
* Several liveries
* Several checklists
* Autostart
* Weight and speed limitations
* Tuned autopilot with built-in climb schedule
* Working speedbrakes (engage with K, retract with J)
* Working thrust reversers (engage with DEL) on the Citation II only
* GPS navigation as an aftermarket modification

At low altitude, this aeroplane is light and slow enough for sightseeing in the canyons. At high altitude, it is fast enough for medium-haul, multiple-hour flights and GPS navigation. You can fly VFR or IFR, with or without GPS.

== Startup ==
Use the aircraft checklist for startup instructions; alternatively, press S for autostart.

== Performance ==
{| class="wikitable"
|-
! !! Citation II !! Sierra Super II
|-
! Never exceed speed
| 263 KIAS || 263 KIAS
|-
! Typical cruise speed at FL410
| 330 KTAS || 370 KTAS
|-
! Range at MTOW and full fuel, FL410, full throttle
| 1900 nmi || 2500 nmi
|-
! Endurance (hours) at full throttle
| 5:45 || 6:33
|-
! Climb rate at sea level
| 3000 fpm || 6000 fpm
|-
! Thrust reversers
| yes || no
|}

== Autopilot ==
The autopilot will disengage 500 feet above ground level or below the decision height selected on the radio altimeter, whichever is highest. This implies that you must climb at least to 500 ft above ground before you engage the autopilot. In addition, you should never engage autopilot while manoeuvering; always stabilize the aeroplane before you engage autopilot.

When the FD OFF button is illuminated, the autopilot is OFF. Clicking this button will engage the autopilot in wing leveler (horizontal) and pitch hold (vertical) modes. You can also engage autopilot, with the same effects, with the AP ENGAGE button between the seats. The following lateral, vertical and speed modes are available:

=== Lateral modes ===
; Wing Leveler: All lights are off
; HDG: Follow the magnetic heading bug selected on the pilot's HSI.
; NAV: Follow the radial selected on either NAV1 or NAV2. Switch between NAV1 and NAV2 using the NAV/HSI button.
; GPS: Follow the course selected by GPS. To engage, click on the NAV button a second time.
; APR: Click this button to engage both NAV1 and glideslope for an ILS approach. Note that, since the autopilot will disengage at least 500 ft above ground, this aeroplane is certified only for CAT I ILS approaches; it has no autoland capability.

=== Vertical modes ===
; Pitch hold: All lights are off. Adjust pitch (in increments of 1 degree) with the PITCH wheel between the seats.
; ALT: Climb or descend to, then maintain the altitude selected with the ALT knob left of the ADF radio. You can adjust the selected altitude with this knob or with the PITCH wheel between the seats.
; V/S: Hold current vertical speed. Adjust the selected vertical speed with the PITCH wheel between the seats.

You should engage ALT mode in more or less level flight with an angle of attack no greater than 0.2 and airspeed at least 220 KIAS. The autopilot includes a climb schedule and will climb at a speed appropriate for your engines; it will automatically decrease the rate of climb as you gain altitude.

On the base Citation II, you need a stepped climb and 45 minutes to reach FL410. The first step should be at FL330 or thereabouts.

On the re-engined Super II, you can climb all the way to FL430 in one step, even at MTOW, provided you respect the prerequisites listed above before engaging ALT mode.

=== Speed modes ===
; Autothrottle: Engage and disengage with Ctrl+S to hold current indicated airspeed. Note that the real Citation II does not have this, so you may consider using autothrottle cheating.

== Radio navigation ==
Tune the two NAV and COM radios and the sole ADF radio on the cockpit.

=== Horizontal Situation Indicators ===
On startup, the captain's [[HSI|horizontal situation indicator]] uses NAV1 and the copilot's HSI uses NAV2. The NAV/HSI button under each HSI switches between NAV1 and NAV2; you can switch the HSIs independently. If the autopilot is engaged in NAV mode, then the autopilot will also switch between NAV1 and NAV2, always following the radio selected on the captain's HSI. The best usage of this feature is as follows:

# Tune the NAV1 radio to a VOR beacon.
# Select the NAV1 radial on the captain's HSI.
# Fly the selected radial.
# Tune the NAV2 radio to another VOR beacon.
# Select the NAV2 radial on the copilot's HSI.
# When you intercept the radial selected on NAV2, click on the NAV/HSI button on the captain's side. The autopilot will now follow the NAV2 radial.
# Switch the copilot's HSI to NAV1.
# Tune NAV1 to a third VOR beacon.
# Select the NAV1 radial on the copilot's HSI.
# Repeat as necessary.

The two HSIs feature an integrated Radio Magnetic Indicator: the thin red arrow points to the selected VOR beacon (either NAV1 or NAV2). They also have a built-in Distance Measuring Equipment showing the distance between you and the selected beacon, in nautical miles.

=== Radio Magnetic Indicators ===
The cockpit has additional Radio Magnetic Indicators on both the pilot and copilot side. This indicator has two arrows and two buttons:

* The ''left'' button switches the single-stemmed arrow to point either to the NAV1 VOR beacon or to the NDB.
* The ''right'' button switches the double-stemmed arrow to point either to the NAV2 VOR beacon or to the NDB.

Combined with the HSI you can have arrows pointing simultaneously to all three beacons. By default:

* The ''single-stemmed'' arrow points to the NDB selected on the ADF radio
* The ''double-stemmed'' arrow points to the VOR beacon selected on the NAV2 radio
* The ''thin red needle'' of the HSI points to the VOR beacon selected on the NAV1 radio

=== Glideslope NAV1 indicator ===
To the left of the pilot's HSI is an additional NAV1 indicator with two needles; this merely repeats localizer and glideslope information from the HSI and from the attitude indicator.
Thus you have triple redundancy :) This instrument is hardwired to NAV1, so you can fly an ILS approach by hand while simultaneously pointing your HSI at the NAV2 beacon.

=== Distance Measuring Equipment ===
The DME shows the distance in nautical miles to the selected beacon. You can use it either to repeat the information on the HSI or to show the distance to the other beacon.
This instrument also shows your speed towards or from the beacon (''not'' your groundspeed: Only the component of your groundspeed that is on the line between you and the beacon), or
the time to go to the beacon in minutes at your current speed.

== GPS navigation ==
The original Citation II did not have a GPS but both it and the re-engined Sierra Super II have two aftermarket additions that enable basic GPS navigation.

=== ZVK500 GPS instrument ===
This instrument is available as part of the base FlightGear package and is shared with the [[Lionceau]] light propeller aircraft. It features a very basic display of current position,
next waypoint, time to waypoint, direct route (DTO) mode, etc. For more details, see [https://gitorious.org/fg/fgdata/source/Aircraft/Instruments-3d/zkv500/manual.txt its documentation].

=== Control Display Unit ===
The CDU on the central console allows you to create a simple route from one airport to another.

To create a route:

# Click on the DEP ARR button.
# Type the ICAO code of your departure airport.
# Click on the ORIGIN (top left) button.
# Type the ICAO code of your destination airport.
# Click on the DEST (top right) button.
# Optionally type the departure runway number then click the RWY button.
# Click ACTIVATE.

This activates the Route Manager, which you can of course still control with the generic Route Manager dialog. The ZVK500 unit in POSITION mode will then display where you stand on the selected route.

== External link ==
* {{wikipedia|Cessna Citation II}} Wikipedia article

{{Cessna}}

[[Category:Business aircraft]]

Cessna 550 Citation II

2015-01-28T19:53:36Z

Circumn: Hyperlink to the Bravo and HSI. Make it explicit that the two HSIs are independent.

{{infobox Aircraft
|image =Cessna550.jpg
|name =Cessna 550 Citation II
|type =Business Jet
|authors = Curtis Olson, Syd Adams, Ludovic Brenta, chrisblues
|fdm =Yasim
|status = advanced production
|status-fdm=5
|status-systems=4
|status-cockpit=4
|status-model=4
|fgname = Citation-II<br/>Sierra-Super-II
|ready = rembrandt
|download = http://sourceforge.net/p/flightgear/fgaddon/HEAD/tarball?path=/trunk/Aircraft/Citation
}}

[[File:Cessna550_cockpit.jpg|thumb|270px|The cockpit of a Cessna 550]]

The '''Cessna 550 Citation II''' debuted in [[FlightGear]] 0.9.8 in January 2005. It has two "special views": passenger 1 and passenger 2.

{{note|This article describes the Citation II in Subversion (as of January 2015), not the 3.2 release.}}

== Overview ==
The Cessna 550/551 Citation II is a light corporate jet built between 1978 and 2006. The FlightGear model is a luxury corporate jet for two pilots and seven passengers. However you should not view the original Citation II as a real jet; with a cruising speed of only 330 KTAS, it was really intended as a competitor for high-end twin turboprops.

The Cessna 550 requires two pilots; the 551 is the same aircraft certified for single-pilot use.

Later variants of this aircraft include the [[Cessna_Citation_Bravo|Cessna Citation Bravo]], which has newer avionics (available separately in FlightGear), the Cessna Citation S/II with improved wings (not currently available in FlightGear), and the Sierra Super II, available together with this aircraft in FlightGear.

The Sierra Super II is an aftermarket modification of the Cessna 550/551 which replaces the engines with Williams International FJ44-3 turbofans introduced in 2004. They
provide more thrust and less fuel consumption. Climb performance in particular is dramatically improved.

The new engines lack thrust reversers; they are not needed because their idle thrust is only 40 lbf, as opposed to 400 lbf on the old engines.

Features available in FlightGear include:

* Choice of two variants: the basic Citation II or the re-engined Sierra Super II
* Several liveries
* Several checklists
* Autostart
* Weight and speed limitations
* Tuned autopilot with built-in climb schedule
* Working speedbrakes (engage with K, retract with J)
* Working thrust reversers (engage with DEL) on the Citation II only
* GPS navigation as an aftermarket modification

At low altitude, this aeroplane is light and slow enough for sightseeing in the canyons. At high altitude, it is fast enough for medium-haul, multiple-hour flights and GPS navigation. You can fly VFR or IFR, with or without GPS.

== Startup ==
Use the aircraft checklist for startup instructions; alternatively, press S for autostart.

== Performance ==
{| class="wikitable"
|-
! !! Citation II !! Sierra Super II
|-
! Never exceed speed
| 263 KIAS || 263 KIAS
|-
! Typical cruise speed at FL410
| 330 KTAS || 370 KTAS
|-
! Range at MTOW and full fuel, FL410, full throttle
| 1900 nmi || 2500 nmi
|-
! Endurance (hours) at full throttle
| 5:45 || 6:33
|-
! Climb rate at sea level
| 3000 fpm || 6000 fpm
|-
! Thrust reversers
| yes || no
|}

== Autopilot ==
The autopilot will disengage 500 feet above ground level or below the decision height selected on the radio altimeter, whichever is highest. This implies that you must climb at least to 500 ft above ground before you engage the autopilot. In addition, you should never engage autopilot while manoeuvering; always stabilize the aeroplane before you engage autopilot.

When the FD OFF button is illuminated, the autopilot is OFF. Clicking this button will engage the autopilot in wing leveler (horizontal) and pitch hold (vertical) modes. You can also engage autopilot, with the same effects, with the AP ENGAGE button between the seats. The following lateral, vertical and speed modes are available:

=== Lateral modes ===
; Wing Leveler: All lights are off
; HDG: Follow the magnetic heading bug selected on the pilot's HSI.
; NAV: Follow the radial selected on either NAV1 or NAV2. Switch between NAV1 and NAV2 using the NAV/HSI button.
; GPS: Follow the course selected by GPS. To engage, click on the NAV button a second time.
; APR: Click this button to engage both NAV1 and glideslope for an ILS approach. Note that, since the autopilot will disengage at least 500 ft above ground, this aeroplane is certified only for CAT I ILS approaches; it has no autoland capability.

=== Vertical modes ===
; Pitch hold: All lights are off. Adjust pitch (in increments of 1 degree) with the PITCH wheel between the seats.
; ALT: Climb or descend to, then maintain the altitude selected with the ALT knob left of the ADF radio. You can adjust the selected altitude with this knob or with the PITCH wheel between the seats.
; V/S: Hold current vertical speed. Adjust the selected vertical speed with the PITCH wheel between the seats.

You should engage ALT mode in more or less level flight with an angle of attack no greater than 0.2 and airspeed at least 220 KIAS. The autopilot includes a climb schedule and will climb at a speed appropriate for your engines; it will automatically decrease the rate of climb as you gain altitude.

On the base Citation II, you need a stepped climb and 45 minutes to reach FL410. The first step should be at FL330 or thereabouts.

On the re-engined Super II, you can climb all the way to FL430 in one step, even at MTOW, provided you respect the prerequisites listed above before engaging ALT mode.

=== Speed modes ===
; Autothrottle: Engage and disengage with Ctrl+S to hold current indicated airspeed. Note that the real Citation II does not have this, so you may consider using autothrottle cheating.

== Radio navigation ==
Tune the two NAV and COM radios and the sole ADF radio on the cockpit.

=== Horizontal Situation Indicators ===
On startup, the captain's [[HSI|horizontal situation indicator]] uses NAV1 and the copilot's HSI uses NAV2. The NAV/HSI button under each HSI switches between NAV1 and NAV2; you can switch the HSIs independently. If the autopilot is engaged in NAV mode, then the autopilot will also switch between NAV1 and NAV2, always following the radio selected on the captain's HSI. The best usage of this feature is as follows:

# Tune the NAV1 radio to a VOR beacon.
# Select the NAV1 radial on the captain's HSI.
# Fly the selected radial.
# Tune the NAV2 radio to another VOR beacon.
# Select the NAV2 radial on the copilot's HSI.
# When you intercept the radial selected on NAV2, click on the NAV/HSI button on the captain's side. The autopilot will now follow the NAV2 radial.
# Switch the copilot's HSI to NAV1.
# Tune NAV1 to a third VOR beacon.
# Select the NAV1 radial on the copilot's HSI.
# Repeat as necessary.

The two HSIs feature an integrated Radio Magnetic Indicator: the thin red arrow points to the selected VOR beacon (either NAV1 or NAV2). They also have a built-in Distance Measuring Equipment showing the distance between you and the selected beacon, in nautical miles.

=== Radio Magnetic Indicators ===
The cockpit has additional Radio Magnetic Indicators on both the pilot and copilot side. This indicator has two arrows and two buttons:

* The ''left'' button switches the single-stemmed arrow to point either to the NAV1 VOR beacon or to the NDB.
* The ''right'' button switches the double-stemmed arrow to point either to the NAV2 VOR beacon or to the NDB.

Combined with the HSI you can have arrows pointing simultaneously to all three beacons. By default:

* The ''single-stemmed'' arrow points to the NDB selected on the ADF radio
* The ''double-stemmed'' arrow points to the VOR beacon selected on the NAV2 radio
* The ''thin red needle'' of the HSI points to the VOR beacon selected on the NAV1 radio

=== Glideslope NAV1 indicator ===
To the left of the pilot's HSI is an additional NAV1 indicator with two needles; this merely repeats localizer and glideslope information from the HSI and from the attitude indicator.
Thus you have triple redundancy :) This instrument is hardwired to NAV1, so you can fly an ILS approach by hand while simultaneously pointing your HSI at the NAV2 beacon.

=== Distance Measuring Equipment ===
The DME shows the distance in nautical miles to the selected beacon. You can use it either to repeat the information on the HSI or to show the distance to the other beacon.
This instrument also shows your speed towards or from the beacon (''not'' your groundspeed: Only the component of your groundspeed that is on the line between you and the beacon), or
the time to go to the beacon in minutes at your current speed.

== GPS navigation ==
The original Citation II did not have a GPS but both it and the re-engined Sierra Super II have two aftermarket additions that enable basic GPS navigation.

=== ZVK500 GPS instrument ===
This instrument is available as part of the base FlightGear package and is sahared with the Lionceau light propeller aircraft. It features a very basic display of current position,
next waypoint, time to waypoint, direct route (DTO) mode, etc. For more details, see [[https://gitorious.org/fg/fgdata/source/Aircraft/Instruments-3d/zkv500/manual.txt its documentation]].

=== Control Display Unit ===
The CDU on the central console allows you to create a simple route from one airport to another.

To create a route:

# Click on the DEP ARR button.
# Type the ICAO code of your departure airport.
# Click on the ORIGIN (top left) button.
# Type the ICAO code of your destination airport.
# Click on the DEST (top right) button.
# Optionally type the departure runway number then click the RWY button.
# Click ACTIVATE.

This activates the Route Manager, which you can of course still control with the generic Route Manager dialog. The ZVK500 unit in POSITION mode will then display where you stand on the selected route.

== External link ==
* {{wikipedia|Cessna Citation II}} Wikipedia article

{{Cessna}}

[[Category:Business aircraft]]

Cessna 550 Citation II

2015-01-27T22:19:07Z

Circumn: Turn this page from a stub to a full-featured article describing the current state of the Citation II in Subversion.

[[File:Rembrandtready.png|110px]]

{{infobox Aircraft
|image =Cessna550.jpg
|name =Cessna 550 Citation II
|type =Business Jet
|authors = Curtis Olson, Syd Adams, Ludovic Brenta, chrisblues
|fdm =Yasim
|status = advanced production
|status-fdm=5
|status-systems=4
|status-cockpit=4
|status-model=4
|fgname = Citation-II<br/>Sierra-Super-II
|download = http://sourceforge.net/p/flightgear/fgaddon/HEAD/tarball?path=/trunk/Aircraft/Citation
}}[[File:Cessna550_cockpit.jpg|thumb|270px|The cockpit of a Cessna 550]]

The '''Cessna 550 Citation II''' debuted in [[FlightGear]] 0.9.8 in January 2005. It has two "special views": passenger 1 and passenger 2.

'''Note: this article describes the Citation II in Subversion, not the 3.2 release.'''

= Overview =

The Cessna 550/551 Citation II is a light corporate jet built between 1978 and 2006.
The FlightGear model is a luxury corporate jet for two pilots and seven passengers.
However you should not view the original Citation II as a real jet; with a cruising speed of only 330 KTAS, it was
really intended as a competitor for high-end twin turboprops.

The Cessna 550 requires two pilots; the 551 is the same aircraft certified for
single-pilot use.

Later variants of this aircraft include the Cessna Citation Bravo, which has newer
avionics (available separately in FlightGear), the Cessna Citation S/II with improved
wings (not currently available in FlightGear), and the Sierra Super II, available
together with this aircraft in FlightGear.

The Sierra Super II is an aftermarket modification of the Cessna 550/551 which replaces
the engines with Williams International FJ44-3 turbofans introduced in 2004. They
provide more thrust and less fuel consumption. Climb performance in particular is
dramatically improved.

The new engines lack thrust reversers; they are not needed because their idle thrust is
only 40 lbf, as opposed to 400 lbf on the old engines.

Features available in FlightGear include:

* Choice of two variants: the basic Citation II or the re-engined Sierra Super II
* Several liveries
* Several checklists
* Autostart
* Weight and speed limitations
* Tuned autopilot with built-in climb schedule
* Working speedbrakes (engage with K, retract with J)
* Working thrust reversers (engage with DEL) on the Citation II only
* GPS navigation as an aftermarket modification

At low altitude, this aeroplane is light and slow enough for sightseeing in the canyons.
At high altitude, it is fast enough for medium-haul, multiple-hour flights and GPS
navigation. You can fly VFR or IFR, with or without GPS.

= Startup =

Use the aircraft checklist for startup instructions; alternatively, press S for autostart.

= Performance =

{| class="wikitable"
|-
! !! Citation II !! Sierra Super II
|-
! Never exceed speed
| 263 KIAS || 263 KIAS
|-
! Typical cruise speed at FL410
| 330 KTAS || 370 KTAS
|-
! Range at MTOW and full fuel, FL410, full throttle
| 1900 nmi || 2500 nmi
|-
! Endurance (hours) at full throttle
| 5:45 || 6:33
|-
! Climb rate at sea level
| 3000 fpm || 6000 fpm
|-
! Thrust reversers
| yes || no
|}

= Autopilot =

The autopilot will disengage 500 feet above ground level or below the decision height
selected on the radio altimeter, whichever is highest. This implies that you must climb
at least to 500 ft above ground before you engage the autopilot. In addition, you
should never engage autopilot while manoeuvering; always stabilize the aeroplane before
you engage autopilot.

When the FD OFF button is illuminated, the autopilot is OFF. Clicking this button will
engage the autopilot in wing leveler (horizontal) and pitch hold (vertical) modes. You
can also engage autopilot, with the same effects, with the AP ENGAGE button between the
seats. The following lateral, vertical and speed modes are available:

== Lateral modes ==

* Wing Leveler: all lights are off
* HDG: follow the magnetic heading bug selected on the pilot's HSI.
* NAV: follow the radial selected on either NAV1 or NAV2. Switch between NAV1 and NAV2 using the NAV/HSI button.
* GPS: follow the course selected by GPS. To engage, click on the NAV button a second time.
* APR: click this button to engage both NAV1 and glideslope for an ILS approach. Note that, since the autopilot will disengage at least 500 ft above ground, this aeroplane is certified only for CAT I ILS approaches; it has no autoland capability.

== Vertical modes ==

* Pitch hold: all lights are off. Adjust pitch (in increments of 1 degree) with the PITCH wheel between the seats.
* ALT: climb or descend to, then maintain the altitude selected with the ALT knob left of the ADF radio. You can adjust the selected altitude with this knob or with the PITCH wheel between the seats.
* V/S: hold current vertical speed. Adjust the selected vertical speed with the PITCH wheel between the seats.

You should engage ALT mode in more-or-less level flight with an angle of attack no greater than
0.2 and airspeed at least 220 KIAS. The autopilot includes a climb schedule and will climb
at a speed appropriate for your engines; it will automatically decrease the rate of climb as you gain
altitude.

On the base Citation II, you need a stepped climb and 45 minutes to reach FL410. The first step
should be at FL330 or thereabouts.

On the re-engined Super II, you can climb all the way to FL430 in one step, even at MTOW,
provided you respect the prerequisites listed above before engaging ALT mode.

== Speed modes ==

* Autothrottle: engage and disengage with Ctrl+S to hold current indicated airspeed. Note that the real Citation II does not have this, so you may consider using autothrottle cheating.

= Radio navigation =

Tune the two NAV and COM radios and the sole ADF radio on the cockpit.

=== Horizontal Situation Indicators ===

On startup, the captain's horizontal situation indicator uses NAV1 and the copilot's HSI uses NAV2.
The NAV/HSI button under each HSI switches between NAV1 and NAV2. If the autopilot is engaged
in NAV mode, then the autopilot will also switch between NAV1 and NAV2. The best usage of this
feature is as follows:

# Tune the NAV1 radio to a VOR beacon.
# Select the NAV1 radial on the captain's HSI.
# Fly the selected radial.
# Tune the NAV2 radio to another VOR beacon.
# Select the NAV2 radial on the copilot's HSI.
# When you intercept the radial selected on NAV2, click on the NAV/HSI button on the captain's side. The autopilot will now follow the NAV2 radial.
# Switch the copilot's HSI to NAV1.
# Tune NAV1 to a third VOR beacon.
# Select the NAV1 radial on the copilot's HSI.
# Repeat as necessary.

The two HSIs feature an integrated Radio Magnetic Indicator: the thin red arrow points to the
selected VOR beacon (either NAV1 or NAV2). They also have a built-in Distance Measuring
Equipment showing the distance between you and the selected beacon, in nautical miles.

== Radio Magnetic Indicators ==

The cockpit has additional Radio Magnetic Indicators on both the pilot and copilot side.
This indicator has two arrows and two buttons:

* the left button switches the single-stemmed arrow to point either to the NAV1 VOR beacon or to the NDB.
* the right button switches the double-stemmed arrow to point either to the NAV2 VOR beacon or to the NDB.

Combined with the HSI you can have arrows pointing simultaneously to all three beacons. By default:

* the single-stemmed arrow points to the NDB selected on the ADF radio
* the double-stemmed arrow points to the VOR beacon selected on the NAV2 radio
* the thin red needle of the HSI points to the VOR beacon selected on the NAV1 radio

== Glideslope NAV1 indicator ==

To the left of the pilot's HSI is an additional NAV1 indicator with two needles; this merely
repeats localizer and glideslope information from the HSI and from the attitude indicator.
Thus you have triple redundancy :) This instrument is hardwired to NAV1, so you can fly
an ILS approach by hand while simultaneously pointing your HSI at the NAV2 beacon.

== Distance Measuring Equipment ==

The DME shows the distance in nautical miles to the selected beacon. You can use
it either to repeat the information on the HSI or to show the distance to the other beacon.
This instrument also shows your speed towards or from the beacon (''not'' your groundspeed:
only the component of your groundspeed that is on the line between you and the beacon), or
the time to go to the beacon in minutes at your current speed.

= GPS navigation =

The original Citation II did not have a GPS but both it and the re-engined Sierra Super II
have two aftermarket additions that enable basic GPS navigation.

=== ZVK500 GPS instrument ===

This instrument is available as part of the base FlightGear package and is sahared with the
Lionceau light propeller aircraft. It features a very basic display of current position,
next waypoint, time to waypoint, direct route (DTO) mode, etc. For more details, see
[[https://gitorious.org/fg/fgdata/source/Aircraft/Instruments-3d/zkv500/manual.txt its documentation]].

=== Control Display Unit ===

The CDU on the central console allows you to create a simple route from one airport to another.
To create a route:

# Click on the DEP ARR button.
# Type the ICAO code of your departure airport.
# Click on the ORIGIN (top left) button.
# Type the ICAO code of your destination airport.
# Click on the DEST (top right) button.
# Optionally type the departure runway number then click the RWY button.
# Click ACTIVATE.

This activates the Route Manager, which you can of course still control with the generic Route Manager
dialog. The ZVK500 unit in POSITION mode will then display where you stand on the selected route.

= External link =
* [http://en.wikipedia.org/wiki/Cessna_Citation_II Wikipedia]

{{Cessna}}

[[Category:Business aircraft]]