FlightGear wiki - User contributions [en]

Instrument Landing System Tutorial

2011-05-23T21:23:12Z

Flightmonster: minor grammatical fixes

''See [[Instrument Landing System]] for the main article.''

In this tutorial we will land a [[Boeing 737]] at London Heathrow Airport (EGLL). The principle is at every airport the same, only the numbers are different. In some planes you might have to set the ILS settings by using the 3D [[Cockpit]].

== Preflight ==
Use these settings in the [[FlightGear Wizard]] (Advanced.. > Initial Position):

{| class="prettytable"
!
!
|-
| '''Longitude'''
| 0
|-
| '''Latitude'''
| 51.47759
|-
| '''Altitude'''
| 5000
|-
| '''Heading'''
| 270
|-
| '''Airspeed'''
| 350
|}

[[File:mpmap_ILS.jpg|thumb|270px|The [[MP Map]] with [[Instrument Landing System|ILS]] information for EGLL 27R.]]

=== MP Map ===
With a few modifications the MP Map is very useful for ILS landings. If we want to land at an airport we go to the 'nav'-tab and tick on the 'apt' button below 'show'. Now you'll see blue lines on the runways, a box with the name of the airport in red and a box at every end of a runway. To show the ILS info of a runway we press the square next to the runway name. Now a yellow triangle will appear. This is the area where the plane will pick up the ILS, so you need to get in this triangle to land.

== Approach ==
With this tutorial your flight will start 12 [[Nautical mile|nm]] out of EGLL. You're at 5000 ft and lined up with 27R. That's the runway we'll land on.

=== Long final ===
First thing to do is setting up the radio settings. We go to <tt>Equipment > Radio settings</tt> and fill our frequency (110.30) in the first NAV1 box. That's all we have to do to be sure our plane will find the ILS on 27R.

Now we need to slow down a bit and slowly descend to 2500 ft, this is the maximum height where our plane could find the ILS.

=== Final ===
Put your landing gear down at 7 miles out. Apply full flaps if you are within 4-5 nm of the airport. Try to maintain your height or descend a bit more to 2500 ft.

[[File:ILS_autopilot.jpg|thumb|270px|The [[autopilot]] settings for an ILS approach with the [[Boeing 737|B737]].]]

==== Autopilot ====
If you are withing the ILS range you could turn on the autopilot. To get your plane lined up with the runway and on the correct glideslope you have to use the settings shown on the picture on the right (the speed depends on your plane's landing speed!). Now change nothing and let the ILS do its work. Watch your plane lining up perfectly with the runway and see it descend slowly.

== Touch down ==
A few seconds before you touch down (let's say on a height of 150 ft) you should turn off the autopilot and manually land the plane. If not, your plane may crash. Use thrust reversers, airbrakes and brakes to slow your plane down. Vacate the runway as directed by the air traffic controller.

Boeing 717

2011-05-10T21:53:17Z

Flightmonster: startup procedures provided by Skyop

{{infobox Aircraft
|image =717-200.jpg
|alt =The Boeing 717 in the AirTran Airways livery
|name =Boeing 717
|type =Regional Airliner
|livery =AirTran Airways
|authors =Malik Guest, Skyop, Gary Neely
|fdm =JSBsim
|status =Development
|fgname =717-200
|download =http://flightgear.org/forums/viewtopic.php?f=4&t=6145&start=555#p119978
}}
[[File:717-cockpit.jpg|thumb|270px|The 3d cockpit, looking downward at the instruments]]
[[File:717-cockpit-overhead.jpg|thumb|270px|The 3d cockpit, looking upward at the overhead panel]]
[[File:717-mfd.jpg|thumb|270px|The 717's mult-function display, showing the selected [[VOR]]s, [[Multiplayer|multiplayer traffic]] in the area, and the next waypoint entered in the [[Route Manager]]]]
The '''Boeing 717''' is a twin-engine, single-aisle jet [[:Category:Airliners|airliner]], developed for the 100-seat market. The airliner was designed and marketed by [[:Category:McDonnell Douglas|McDonnell Douglas]] as the MD-95, a third-generation derivative of the DC-9.

The first order was placed in October 1995; however, McDonnell Douglas and Boeing merged in 1997 prior to production. The first planes entered service in 1999 as the Boeing 717. Production ceased in May 2006 after 156 units were produced. This plane is currently under production in flightgear with an expected release sometime halfway through 2010.

== Aircraft help ==
The knobs on the [[autopilot]] control panel can be adjusted by clicking the sides to increase and middle-clicking to decrease. You can also use the scroll wheel if your mouse includes one. Click the face on the front of a knob to perform its function.

=== Key commands ===
{| class="wikitable"
|-
! style="border: 0.125em solid black; padding: 0.25em;" | Delete
| style="border: 0.125em solid black; padding: 0.25em;" | activate reverse thrust
|-
! style="border: 0.125em solid black; padding: 0.25em;" | Ctrl-b
| style="border: 0.125em solid black; padding: 0.25em;" | cycle speedbrake setting
|-
! style="border: 0.125em solid black; padding: 0.25em;" | Tab
| style="border: 0.125em solid black; padding: 0.25em;" | cycle autobrake setting
|-
! style="border: 0.125em solid black; padding: 0.25em;" | Ctrl-z
| style="border: 0.125em solid black; padding: 0.25em;" | toggle autopilot Master Arm switch
|-
! style="border: 0.125em solid black; padding: 0.25em;" | Ctrl-y
| style="border: 0.125em solid black; padding: 0.25em;" | toggle autopilot Mach speed hold
|-
! style="border: 0.125em solid black; padding: 0.25em;" | Ctrl-o
| style="border: 0.125em solid black; padding: 0.25em;" | toggle autothrottle TO/GA set
|}

You can find a full list of autopilot key commands in the documentation included with [[FlightGear]].

=== Startup procedures===
1. APU master switch START. 
2. (Wait some seconds...) APU master switch RUN. 
3. APU electric generator ON. 
4. Engine 1 and engine 2 starters ON. 
5. Engine 1 and engine 2 cutoff switches RUN. 
6. Engine 1 and engine 2 electric generators ON. APU electric generator OFF. 
7. APU master switch OFF.

== Development status ==

=== Completed ===
* Animations
* Custom instruments
* Autobrake/speedbrake systems
* Autostart system
* APU system
* [[Livery over MP|Livery select]]
* [[Howto: Implement generic tyre smoke|Tire smoke]]
* [[Howto: Add contrails|Contrails]]
* [[Howto: Implement pushback|Pushback]]
* Engine fire system
* [[Howto: Animated jetways|Animated jetway]] definition

=== To-do ===
* FDM tweaking (as always)

== External Links ==
* [http://www.boeing.com/commercial/717 Official website]
* [http://flightgear.org/forums/viewtopic.php?f=4&t=6145&st=0&sk=t&sd=a Boeing 717 FlightGear Forum Topic]

== Reference ==
* [http://en.wikipedia.org/wiki/Boeing_717 Wikipedia]

{{Boeing}}

[[Category:Aircraft]]
[[Category:Aircraft TODO]]
[[Category:Airliners]]
[[Category:Civilian aircraft]]

Airbus A320 family

2011-05-10T21:41:22Z

Flightmonster: /* Startup procedures */ bah

''This includes the following models: A318-111, A319-111, A319-131, A320-111, A320-211, A320-231, A321-211, A321-231, A320-family''

{{infobox Aircraft
|image =A320-family.jpg
|name =Airbus A320 Family
|type =Narrow-body Commercial Airliner(s)
|livery =Nearly every livery in [http://liveries.flightgear.org/aircraft.php?id=8 the database]
|fdm =JSBSim
|status =Alpha
|authors =Ampere K. Hardraade, Skyop
|fgname =A318-111, A319-111, A319-131, A320-111, A320-211, A320-231, A321-211, A321-231
|download =http://flightgear.org/forums/viewtopic.php?t=9032&p=115034#p115034
|development =http://gitorious.org/airbus-aircraft/a320
}}
[[File:A320-cockpit.jpg|thumb|300px|The 3d [[cockpit]] of the A320 family, currently under development]]

The '''Airbus A320 Family''' is a series of narrow-body commercial passenger jets manufactured by [[Airbus|Airbus Industries]]. Designed for short to medium hauls, the aircraft pioneer fly-by-wire technology and regularly compete with the [[Boeing 737|Boeing 737 series]]. The series includes the Airbus A318, the A319, the A320, and the A321. The [[Airbus A320E|"A320 Enhanced" program]] aims to further improve the A320 family with longer range and better fuel economy.

== Variants ==
* <tt>A318-111</tt>: Airbus A318-111 with CFM56 engines
* <tt>A319-111</tt>: Airbus A319-111 with CFM56 engines
* <tt>A319-131</tt>: Airbus A319-131 with IAE V2500 engines
* <tt>A320-111</tt>: Airbus A320-111 with CFM56 engines
* <tt>A320-211</tt>: Airbus A320-211 with CFM56 engines
* <tt>A230-231</tt>: Airbus A320-231 with IAE V2500 engines
* <tt>A321-211</tt>: Airbus A321-211 with CFM56 engines
* <tt>A321-231</tt>: Airbus A321-231 with IAE V2500 engines

== Startup procedures ==
''This applies to all the A320 models'' 

1. Start the APU. APU starter ON and APU master switch ON. 
2. APU electric generator ON. 
3. Engine start knob START. 
4. (Wait a couple seconds...) Engine cutoff switches RUN. 
5. Engine 1 and engine 2 electric generators ON. APU electric generator OFF. 
6. APU starter and master switch off. Engine start knob OFF.

== Development status ==

=== Completed ===
* Base model(s)
* Animations
* Instruments
* 3d [[cockpit]]
* Autobrake/speedbrake systems '''[Git-only]'''
* Autopilot system '''[Git-only]'''
* [[Livery over MP|Livery select]]
* [[Howto: Implement generic tyre smoke|Tire smoke]]
* [[Howto: Add contrails|Contrails]]
* [[Howto: Implement pushback|Pushback]]
* Engine fire system
* [[Howto: Animated jetways|Animated jetway]] definitions

=== To-do ===
* Fly-by-wire system
* Animate slats

== Related content ==
* [[Aircraft]]
* [[Aircraft Todo]]
* [[Airbus A319]] (in development separately)
* [[Airbus A321]] (in development separately)

= External links =
* [http://www.flightgear.org/forums/viewtopic.php?t=9032 Development thread]
* [http://gitorious.org/airbus-aircraft/a320 A320-family at Gitorious]
* [http://gitorious.org/airbus-aircraft/a320/archive-tarball/master Download the latest version of A320-family]
* [http://www.airbus.com/en/aircraftfamilies/a320/ Airbus A320 Family official homepage]

{{Airbus}}

[[Category:Aircraft]]
[[Category:Airliners]]
[[Category:Civilian aircraft]]
[[Category:Aircraft TODO]]

Airbus A320 family

2011-05-10T21:29:27Z

Flightmonster: /* Startup procedures */ space

''This includes the following models: A318-111, A319-111, A319-131, A320-111, A320-211, A320-231, A321-211, A321-231, A320-family''

{{infobox Aircraft
|image =A320-family.jpg
|name =Airbus A320 Family
|type =Narrow-body Commercial Airliner(s)
|livery =Nearly every livery in [http://liveries.flightgear.org/aircraft.php?id=8 the database]
|fdm =JSBSim
|status =Alpha
|authors =Ampere K. Hardraade, Skyop
|fgname =A318-111, A319-111, A319-131, A320-111, A320-211, A320-231, A321-211, A321-231
|download =http://flightgear.org/forums/viewtopic.php?t=9032&p=115034#p115034
|development =http://gitorious.org/airbus-aircraft/a320
}}
[[File:A320-cockpit.jpg|thumb|300px|The 3d [[cockpit]] of the A320 family, currently under development]]

The '''Airbus A320 Family''' is a series of narrow-body commercial passenger jets manufactured by [[Airbus|Airbus Industries]]. Designed for short to medium hauls, the aircraft pioneer fly-by-wire technology and regularly compete with the [[Boeing 737|Boeing 737 series]]. The series includes the Airbus A318, the A319, the A320, and the A321. The [[Airbus A320E|"A320 Enhanced" program]] aims to further improve the A320 family with longer range and better fuel economy.

== Variants ==
* <tt>A318-111</tt>: Airbus A318-111 with CFM56 engines
* <tt>A319-111</tt>: Airbus A319-111 with CFM56 engines
* <tt>A319-131</tt>: Airbus A319-131 with IAE V2500 engines
* <tt>A320-111</tt>: Airbus A320-111 with CFM56 engines
* <tt>A320-211</tt>: Airbus A320-211 with CFM56 engines
* <tt>A230-231</tt>: Airbus A320-231 with IAE V2500 engines
* <tt>A321-211</tt>: Airbus A321-211 with CFM56 engines
* <tt>A321-231</tt>: Airbus A321-231 with IAE V2500 engines

== Startup procedures ==
''This applies to all the A320 models''

1. Start the APU. APU starter ON and APU master switch ON.
2. APU electric generator ON.
3. Engine start knob START.
4. (Wait a couple seconds...) Engine cutoff switches RUN.
5. Engine 1 and engine 2 electric generators ON. APU electric generator OFF.
6. APU starter and master switch off. Engine start knob OFF.

== Development status ==

=== Completed ===
* Base model(s)
* Animations
* Instruments
* 3d [[cockpit]]
* Autobrake/speedbrake systems '''[Git-only]'''
* Autopilot system '''[Git-only]'''
* [[Livery over MP|Livery select]]
* [[Howto: Implement generic tyre smoke|Tire smoke]]
* [[Howto: Add contrails|Contrails]]
* [[Howto: Implement pushback|Pushback]]
* Engine fire system
* [[Howto: Animated jetways|Animated jetway]] definitions

=== To-do ===
* Fly-by-wire system
* Animate slats

== Related content ==
* [[Aircraft]]
* [[Aircraft Todo]]
* [[Airbus A319]] (in development separately)
* [[Airbus A321]] (in development separately)

= External links =
* [http://www.flightgear.org/forums/viewtopic.php?t=9032 Development thread]
* [http://gitorious.org/airbus-aircraft/a320 A320-family at Gitorious]
* [http://gitorious.org/airbus-aircraft/a320/archive-tarball/master Download the latest version of A320-family]
* [http://www.airbus.com/en/aircraftfamilies/a320/ Airbus A320 Family official homepage]

{{Airbus}}

[[Category:Aircraft]]
[[Category:Airliners]]
[[Category:Civilian aircraft]]
[[Category:Aircraft TODO]]

Airbus A320 family

2011-05-10T21:28:57Z

Flightmonster: startup procedures kindly provided by Skyop

''This includes the following models: A318-111, A319-111, A319-131, A320-111, A320-211, A320-231, A321-211, A321-231, A320-family''

{{infobox Aircraft
|image =A320-family.jpg
|name =Airbus A320 Family
|type =Narrow-body Commercial Airliner(s)
|livery =Nearly every livery in [http://liveries.flightgear.org/aircraft.php?id=8 the database]
|fdm =JSBSim
|status =Alpha
|authors =Ampere K. Hardraade, Skyop
|fgname =A318-111, A319-111, A319-131, A320-111, A320-211, A320-231, A321-211, A321-231
|download =http://flightgear.org/forums/viewtopic.php?t=9032&p=115034#p115034
|development =http://gitorious.org/airbus-aircraft/a320
}}
[[File:A320-cockpit.jpg|thumb|300px|The 3d [[cockpit]] of the A320 family, currently under development]]

The '''Airbus A320 Family''' is a series of narrow-body commercial passenger jets manufactured by [[Airbus|Airbus Industries]]. Designed for short to medium hauls, the aircraft pioneer fly-by-wire technology and regularly compete with the [[Boeing 737|Boeing 737 series]]. The series includes the Airbus A318, the A319, the A320, and the A321. The [[Airbus A320E|"A320 Enhanced" program]] aims to further improve the A320 family with longer range and better fuel economy.

== Variants ==
* <tt>A318-111</tt>: Airbus A318-111 with CFM56 engines
* <tt>A319-111</tt>: Airbus A319-111 with CFM56 engines
* <tt>A319-131</tt>: Airbus A319-131 with IAE V2500 engines
* <tt>A320-111</tt>: Airbus A320-111 with CFM56 engines
* <tt>A320-211</tt>: Airbus A320-211 with CFM56 engines
* <tt>A230-231</tt>: Airbus A320-231 with IAE V2500 engines
* <tt>A321-211</tt>: Airbus A321-211 with CFM56 engines
* <tt>A321-231</tt>: Airbus A321-231 with IAE V2500 engines

== Startup procedures ==
''This applies to all the A320 models''
1. Start the APU. APU starter ON and APU master switch ON.
2. APU electric generator ON.
3. Engine start knob START.
4. (Wait a couple seconds...) Engine cutoff switches RUN.
5. Engine 1 and engine 2 electric generators ON. APU electric generator OFF.
6. APU starter and master switch off. Engine start knob OFF.

== Development status ==

=== Completed ===
* Base model(s)
* Animations
* Instruments
* 3d [[cockpit]]
* Autobrake/speedbrake systems '''[Git-only]'''
* Autopilot system '''[Git-only]'''
* [[Livery over MP|Livery select]]
* [[Howto: Implement generic tyre smoke|Tire smoke]]
* [[Howto: Add contrails|Contrails]]
* [[Howto: Implement pushback|Pushback]]
* Engine fire system
* [[Howto: Animated jetways|Animated jetway]] definitions

=== To-do ===
* Fly-by-wire system
* Animate slats

== Related content ==
* [[Aircraft]]
* [[Aircraft Todo]]
* [[Airbus A319]] (in development separately)
* [[Airbus A321]] (in development separately)

= External links =
* [http://www.flightgear.org/forums/viewtopic.php?t=9032 Development thread]
* [http://gitorious.org/airbus-aircraft/a320 A320-family at Gitorious]
* [http://gitorious.org/airbus-aircraft/a320/archive-tarball/master Download the latest version of A320-family]
* [http://www.airbus.com/en/aircraftfamilies/a320/ Airbus A320 Family official homepage]

{{Airbus}}

[[Category:Aircraft]]
[[Category:Airliners]]
[[Category:Civilian aircraft]]
[[Category:Aircraft TODO]]

KJFK

2011-01-22T05:12:47Z

Flightmonster: redirect

#REDIRECT [[John F. Kennedy International Airport]]

Autopilot

2011-01-14T16:49:42Z

Flightmonster: /* Autopilot Settings */ typo

[[File:Autopilot.jpg|thumb|270px|The autopilot setting dialog of FlightGear.]]

An '''autopilot''' ('''AP''') is a mechanical, electrical, or hydraulic system used to guide a vehicle without assistance from a human being. Most people understand an autopilot to refer specifically to [[aircraft]], but self-steering gear for ships, boats, space craft and missiles is often also called by this term.

The autopilot of an aircraft is sometimes referred to as "George".

== Autopilot in FlightGear ==
We have a generic one and custom ones written for a certain aircraft, which are supposed to simulate particular autopilot types/models for a specific aircraft.

The generic one can be used for aircraft which don't have a custom autopilot implementation, and seems to work reasonably well on most aircraft using [[JSBSim]]. You can enable it with the "Autopilot Settings" which you can open using the F11-key or in the menu bar using the "Autopilot" item.

In real life, aircraft have specifically-programmed/customized autopilot system to cater for individual aircraft characteristics.
To a certain extent, Flightgear has the possibility to simulate this as well.

So it is possible to write a custom <tt>autopilot.xml</tt> to override the generic autopilot implementation.
This custom autopilot configuration file can be driven by either the standard autopilot dialog, custom cockpit panel hotspots or a combination of both.
Also, it is possible to provide enhanced or completely new implementations of the standard autopilot dialog to cater for autopilot/aircraft-specific features (for examples, see the b1900d or Citation Bravo in Git/HEAD). [[File:Custom-autopilot-dialog.png|thumb|300px|A custom autopilot dialog]]

Some aircraft in FlightGear however only provide one means of interacting with the autopilot (i.e. autopilot dialog '''or''' panel hotspots).
For example, the [[Piper PA34-200T Seneca II|Seneca II]] and the [[Piper PA-24 Comanche|Piper Comanche]] autopilots can be only used from the virtual cockpit using custom panel hotspots. This is in fact increasingly the case, as new emulations of autopilot systems are implemented using the built-in scripting language [[Nasal scripting language|Nasal]] which provides for much more flexible system design and functionality, compared to the relatively static way of describing autopilot systems and their relevant and modes using only the [[XML]]-configurable autopilot system. In fact, to properly emulate more complex autoflight systems that provide support for more abstract flight modes, using a combination of XML-configurable PID controllers and Nasal is likely to be the most promising approach.

In general, it can be considered to be more complex to provide proper cockpit panel implementations than wiring up the autopilot properties to the standard autopilot GUI dialog, so if an aircraft's autopilot doesn't seem to work properly using cockpit panel hotspots, you may want to try using the standard GUI dialog instead.

Also, please note that not all aircraft/autopilot combinations provide full support for all features offered by the standard autopilot dialog. This may be due to an aircraft's completion status, but also due to technical limitations in certain aircraft/autopilot, so that only certain modes are provided.
This may also apply to aircraft panels, that are seemingly offering functionality that may not yet be implemented.

In addition, JSBSim also features support for a standalone autopilot implementation, that works without any dependency to FlightGear/Nasal.

For further information about programing autopilots in FlightGear look at [[Autopilot Tuning Resources]] and http://www.flightgear.org/Docs/XMLAutopilot/.

== Autopilot Settings ==
The AP Settings dialog can be found at '''Autopilot > Autopilot Settings'''.

=== Heading control ===
* '''Wings Level''': enable this to keep your plane horizontal- usually used at Go-Arounds.
* '''Heading Bug:''' located on the compass rose of your instrument panel is a movable heading bug, the purple triangles that are pointing at your runways heading (283 for KSFO default). This bug is moved around the rose by setting the Heading Bug. The heading bug can be used several ways. When hand flying the aircraft turn the bug to your desired heading. This way you will have a constant visual reminder. If [[ATC|Air Traffic Control]] gives you a new heading move the heading bug to the new heading and you have your visual reminder.
* '''True Heading:''' your true heading as shown on the compass (of the [[Head-up display|HUD]]) and [[Multiplayer Howto|MP Map]].
* '''NAV1 CDI Course:''' used for VOR-by VOR flying like in old days and used with [[ILS]].

=== Velocity control ===
* '''Speed with Throttle:''' speed will be regulated to the selected speed by controlling throttle.
* '''Speed with Pitch:''' your plane will be pushed down or up to reach the selected speed. This can not be used during takeoff, landing or low altitude flights. Doing so could cause a crash.
=== Pitch/Altitude control ===
* '''Vertical Speed:''' set the speed of vertical climb. Usually used as "feet per minute"
* '''Pitch Hold:''' pitch degrees of your plane. Use a negative number to lower your nose.
* '''AoA Hold:''' The Ange of Attack describes the angle of the wings compared to the direction of the circumfluent air. The lift of the wing depends on the AoA. A too high AoA will cause the aircraft to stall.
* '''Altitude Hold:''' the desired altitude of your plane in feet (FL1=100 ft, FL25=2500 ft etc.).
* '''AGL Hold:''' The Altitude about Ground Level. Usually the altitude is given about sea level.
* '''NAV1 Glideslope:''' The vertical slope which led the aircraft from the interception point down to Runway level-used only with [[ILS]].

=== FlightDirector Mode ===
The flight director computes and displays the proper pitch and bank angles required in order for the aircraft to follow a selected path. A simple example: the aircraft is in level flight on a heading of 045 degree and at an altitude of 15000 feet maintaining a speed of 260 kts, the FD bars are thus centered. Then the flight director is set to a new heading of 090 degrees and a new altitude of 20000 feet. The aircraft must thus turn to the right and climb. This is done by rolling to the right and pulling up. The roll bar will deflect to the right and the pitch bar will deflect upwards. The pilot will then pull back on the control column while rolling the aircraft to the right. Once he reaches the proper pitch and bank angle the FD bars will again center and remain centered until it is time to roll back to wings level (when the heading starts to approach 090). When the aircraft approaches 20000 feet the pitch bar will deflect downwards thus commanding the pilot to reduce pitch in order to level off at the new altitude.

The FD is generally used in direct connection with the Autopilot. Where the FD commands the AP to put the aircraft in the attitude necessary to follow a trajectory. The FD/AP combination is typically used in autopilot coupled low instrument approaches, (below 200 feet agl) or CAT II and CAT III ILS instrument approaches.

The exact form of the flight director's display varies with the instrument type either crosshair or command bars.

== Route manager ==
The Route Manager in FlightGear is something like a very simple FMC- Flight Management Control/Computer.
In FGFS you can input a list of waypoints like NAVAIDS, Fixes and Airports, which the aircrafts flies along. You can also add the altitude which the aircraft should have at a certain waypoint. So it is possible to let the aircraft fly along a certain route.

At the moment, it is not possible to add velocities or other constraints.

{{main article | Route Manager}}

Autopilot

2010-10-21T18:30:43Z

Flightmonster: /* Pitch/Altitude control */ copyedit

[[Image:Autopilot.jpg|thumb|270px|The autopilot setting dialog of FlightGear.]]

An [[autopilot]] ('''AP''') is a mechanical, electrical, or hydraulic system used to guide a vehicle without assistance from a human being. Most people understand an autopilot to refer specifically to [[aircraft]], but self-steering gear for ships, boats, space craft and missiles is often also called by this term.

The autopilot of an aircraft is sometimes referred to as "George".

==Autopilot in FlightGear==
We have a generic one and custom ones written for a certain aircraft, which are supposed to simulate particular autopilot types/models for a specific aircraft.

The generic one can be used for aircraft which don't have a custom autopilot implementation, and seems to work reasonably well on most aircraft using [[JSBSim]]. You can enable it with the "Autopilot Settings" which you can open using the F11-key or in the menu bar using the "Autopilot" item.

In real life, aircraft have specifically-programmed/customized autopilot system to cater for individual aircraft characteristics.
To a certain extent, Flightgear has the possibility to simulate this as well.

So it is possible to write a custom <tt>autopilot.xml</tt> to override the generic autopilot implementation.
This custom autopilot configuration file can be driven by either the standard autopilot dialog, custom cockpit panel hotspots or a combination of both.
Also, it is possible to provide enhanced or completely new implementations of the standard autopilot dialog to cater for autopilot/aircraft-specific features (for examples, see the b1900d or Citation Bravo in CVS/HEAD). [[Image:Custom-autopilot-dialog.png|thumb|300px|A custom autopilot dialog]]

Some aircraft in FlightGear however only provide one means of interacting with the autopilot (i.e. autopilot dialog '''or''' panel hotspots).
For example, the [[Piper PA34-200T Seneca II|Seneca II]] and the [[Piper PA-24 Comanche|Piper Comanche]] autopilots can be only used from the virtual cockpit using custom panel hotspots. This is in fact increasingly the case, as new emulations of autopilot systems are implemented using the built-in scripting language [[Nasal scripting language|Nasal]] which provides for much more flexible system design and functionality, compared to the relatively static way of describing autopilot systems and their relevant and modes using only the [[XML]]-configurable autopilot system. In fact, to properly emulate more complex autoflight systems that provide support for more abstract flight modes, using a combination of XML-configurable PID controllers and Nasal is likely to be the most promising approach.

In general, it can be considered to be more complex to provide proper cockpit panel implementations than wiring up the autopilot properties to the standard autopilot GUI dialog, so if an aircraft's autopilot doesn't seem to work properly using cockpit panel hotspots, you may want to try using the standard GUI dialog instead.

Also, please note that not all aircraft/autopilot combinations provide full support for all features offered by the standard autopilot dialog. This may be due to an aircraft's completion status, but also due to technical limitations in certain aircraft/autopilot, so that only certain modes are provided.
This may also apply to aircraft panels, that are seemingly offering functionality that may not yet be implemented.

In addition, JSBSim also features support for a standalone autopilot implementation, that works without any dependency to FlightGear/Nasal.

For further information about programing autopilots in FlightGear look at [[Autopilot Tuning Resources]] and http://www.flightgear.org/Docs/XMLAutopilot/.

==Autopilot Settings==
The AP Settings dialog can be found at '''Autopilot > Autopilot Settings'''.

===Heading control===
* '''Wings Level''': enable this to keep your plane horizontal- ususally used at Go-Arounds.
* '''Heading Bug:''' located on the compass rose of your instrument panel is a movable heading bug, the purple triangles that are pointing at your runways heading (283 for KSFO default). This bug is moved around the rose by setting the Heading Bug. The heading bug can be used several ways. When hand flying the aircraft turn the bug to your desired heading. This way you will have a constant visual reminder. If [[ATC|Air Traffic Control]] gives you a new heading move the heading bug to the new heading and you have your visual reminder.
* '''True Heading:''' your true heading as shown on the compass (of the [[Head-up display|HUD]]) and [[Multiplayer Howto|MP Map]].
* '''NAV1 CDI Course:''' used for VOR-by VOR flying like in old days and used with [[ILS]].

===Velocity control===
* '''Speed with Throttle:''' speed will be regulated to the selected speed by controlling throttle.
* '''Speed with Pitch:''' your plane will be pushed down or up to reach the selected speed. This can not be used during takeoff, landing or low altitude flights. Doing so could cause a crash.
===Pitch/Altitude control===
* '''Vertical Speed:''' set the speed of vertical climb. Usually used as "feet per minute"
* '''Pitch Hold:''' pitch degrees of your plane. Use a negative number to lower your nose.
* '''AoA Hold:''' The Ange of Attack describes the angle of the wings compared to the direction of the circumfluent air. The lift of the wing depends on the AoA. A too high AoA will cause the aircraft to stall.
* '''Altitude Hold:''' the desired altitude of your plane in feet (FL1=100 ft, FL25=2500 ft etc.).
* '''AGL Hold:''' The Altitude about Ground Level. Usually the altitude is given about sea level.
* '''NAV1 Glideslope:''' The vertical slope which led the aircraft from the interception point down to Runway level-used only with [[ILS]].

===FlightDirector Mode===
The flight director computes and displays the proper pitch and bank angles required in order for the aircraft to follow a selected path. A simple example: the aircraft is in level flight on a heading of 045 degree and at an altitude of 15000 feet maintaining a speed of 260 kts, the FD bars are thus centered. Then the flight director is set to a new heading of 090 degrees and a new altitude of 20000 feet. The aircraft must thus turn to the right and climb. This is done by rolling to the right and pulling up. The roll bar will deflect to the right and the pitch bar will deflect upwards. The pilot will then pull back on the control column while rolling the aircraft to the right. Once he reaches the proper pitch and bank angle the FD bars will again center and remain centered until it is time to roll back to wings level (when the heading starts to approach 090). When the aircraft approaches 20000 feet the pitch bar will deflect downwards thus commanding the pilot to reduce pitch in order to level off at the new altitude.

The FD is generally used in direct connection with the Autopilot. Where the FD commands the AP to put the aircraft in the attitude necessary to follow a trajectory. The FD/AP combination is typically used in autopilot coupled low instrument approaches, (below 200 feet agl) or CAT II and CAT III ILS instrument approaches.

The exact form of the flight director's display varies with the instrument type either crosshair or command bars.

==Route manager==
The Route Manager in FlightGear is something like a very simple FMC- Flight Management Control/Computer.
In FGFS you can input a list of waypoints like NAVAIDS, Fixes and Airports, which the aircrafts flies along. You can also add the altitude which the aircraft should have at a certain waypoint. So it is possible to let the aircraft fly along a certain route.

At the moment, it is not possible to add velocities or other constraints.

User talk:Chris blues

2010-10-19T13:17:56Z

Flightmonster: /* Hiding table of contents */ cmt

===Hiding table of contents===
Hi Chris...

According to the question about the ''index-table'' on [[FGo!]]: if you mean the ''table of contents''? It can easily removed by adding "<tt><nowiki>__NOTOC__</nowiki></tt>" (2x"_") at the top of the article. Hope it helps, --[[User:LarsP|LarsP]] 12:12, 16 October 2010 (UTC)

: Hi LarsP!
: Thx a lot! [[User:Chris blues|Chris blues]] 15:40, 17 October 2010 (UTC)
:: Hi guys,
:: At the time it wasn't neccesary to add the NOTOC command, as the wiki auto-hides TOCs for articles with less than four subheadings. Anyway, I've added the infobox, some wiki links and a related content "list" (so now the NOTOC command is neccesary to hide the TOC).
:: Cheers and thanks for your additions to the wiki!
:: [[User:Gijs|Gijs]] 16:19, 17 October 2010 (UTC)
::: Hi! That's the point. There's a time when no command is needed. But then the article expands (as a wiki article should naturally do) and then it's suddenly needesd. Who takes care of this? Therefore I prefer adding such a command right from the beginning... --[[User:LarsP|LarsP]] 13:12, 19 October 2010 (UTC)
:::Gijs is incorrect. When I added the NOTOC, I removed a section that was unneeded at the time (which I expected to be re-added as content was added). This resulted in 3 sections. Thus, if I had not edited the article, there would have been 4 sections, resulting in a table of contents. I find TOCs to be helpful on long articles, but on short ones, such as FGo, they take up space. [[User:Flightmonster|The]][[User talk:Flightmonster#top|Flight]][[Special:Contributions/Flightmonster|Monster]] 13:17, 19 October 2010 (UTC)

Talk:BAe-146

2010-10-19T13:14:49Z

Flightmonster: redirect?

Requesting that this page be deleted in favor of [[BAe 146|the new BAe 146 article]].

--[[User:Skyop|Skyop]] 03:40, 19 October 2010 (UTC)

:Redirected as a plausible redirect. Delete if unneeded. [[User:Flightmonster|The]][[User talk:Flightmonster#top|Flight]][[Special:Contributions/Flightmonster|Monster]] 13:14, 19 October 2010 (UTC)

BAe-146

2010-10-19T13:12:04Z

Flightmonster: redirect (for now?)

#REDIRECT [[BAe 146]]

Template talk:Infobox aircraft

2010-10-18T00:30:22Z

Flightmonster: /* Suggestion: Field for aircraft's name in FlightGear in the Info box. */ indent fix

== Aircraft Ratings ==
This issues of having an aircraft rating system have been previously discussed at lengths, see [http://wiki.flightgear.org/index.php/Formalizing_Aircraft_Status].

== Infobox Parser ==

It would give more control over the infobox if we had the parser installed. http://meta.wikimedia.org/wiki/ParserFunctions#.23if: --[[User:Sek|Sek]]

I agree. By the way, we seem to have lost our abilities to upload files. Can we get that back? -[[User:Ampere|Ampere]] 00:28, 12 June 2006 (EDT)

Uploads should be working again - not sure how I missed that. The parser extension is also now installed. [[User:Hellosimon|Hellosimon]] 01:17, 12 June 2006 (EDT)

The parser functions don't seem to work. Can anyone confirm? -[[User:70.48.6.31|70.48.6.31]] 21:59, 12 June 2006 (EDT)

The parser functions still aren't working. For example: <code>{{ #if: {{{status|}}} | Status }}</code> gives me this instead: <code>{{ #if: | Status }}</code>

See the [[Template:Infobox Aircraft|template]].

-[[User:Ampere|Ampere]] 15:43, 17 June 2006 (EDT)

The extension is installed - see [[Special:Version]], but the installation page for the extension reports that #if is broken with 1.6.x. [[User:Hellosimon|Hellosimon]] 11:44, 19 June 2006 (EDT)

== Suggestion: Field for aircraft's name in FlightGear in the Info box. ==

I think it would be good to have a field in the info box for the aircraft's name(s) in FlightGear (i.e. the ones used with --aircraft=<name>). These are not seldom short and a bit cryptic, hence (IMHO) not suitable as the displayed main name of the aircraft or as the page name. Nice work with the new info box template, btw! --[[User:AndersG|AndersG]] 18:29, 24 October 2007 (EDT)
:I can do, just tell me how to name it. What's IMHO? Btw, thanks for your compliment. --[[User:Gijs|Gijs]] 16:33, 25 October 2007 (EDT)

What to name it is a bit tricky. Maybe it could have the label --aircraft=
in a displayed box and the "property" could perhaps be called fgname?
Some aircraft have several names/-set files too, can one make the info box cope with that? --[[User:AndersG|AndersG]] 17:44, 25 October 2007 (EDT)

:I've give it a try (see an example here: [[Boeing 737]]). Is this what you mean? --[[User:Gijs|Gijs]] 15:42, 26 October 2007 (EDT)

Close, but I was aiming for "--aircraft" where FG Name is now and just 737-300 in the other column of the displayed box. (Or just remove --aircraft -- I think most people will be able to figure out that FG Name is what you use with the --aircraft command line parameter.) --[[User:AndersG|AndersG]] 09:32, 27 October 2007 (EDT)

FGo!

2010-10-16T15:37:17Z

Flightmonster: better, remove TOC

__NOTOC__
FGo! is a simple GUI front-end for FlightGear written in Python. It takes slightly different approach than any other such application - it combines a simple GUI which allows you to select a plane, airport, runway, park position and scenario. In addition, there is a text window where you can write more advanced command line options that will be passed to FlightGear.

In its current state it also provides a checkbox for TerraGear and supports different languages. FGo! is available for download from in the first post of its [http://www.flightgear.org/forums/viewtopic.php?f=6&t=6279 forums thread].

[[Image:Fgo01.jpg|thumb|270px|FGo!]]

All one have to know to set it up and run it is in FGo!s README.

==Installation prerequisites:==

===Windows:===
Download and install [http://www.python.org/ftp/python/2.6.6/python-2.6.6.msi python-2.6.6.msi] and [http://effbot.org/downloads/PIL-1.1.7.win32-py2.6.exe PIL-1.1.7.win32-py2.6.exe]. These are the needed Python2.6-libs and binaries.

It may help to rename the file '''fgo''' in the root of your FGo!-Installation to '''fgo.py''' .
Now you're setup for click and fly!

===Linux===
Just install python-imaging-tk (including all its dependencies) from your favourite software-manager. That's it!

Shuttle Landing Facility

2010-10-15T13:41:29Z

Flightmonster: civilian aircraft at the facility, yeah, right

{{stub}}
{{infobox Airport
|name = Shuttle Landing Facility
|image =
|iata =TTS
|icao =KTTS
|type =Private
|owner =National Aeronautics & Space Administration
|city =Titusville, Florida, USA
|runway= 15/33
|length= 4572 m
|material= Concrete
|website =
}}

The Shuttle Landing Facility (IATA: TTS, ICTO: KTTS, FAA LID:TTS) is a private airport owned and operated by NASA (National Aeronautics and Space Administration) for landing the Space Shuttles. Most space shuttle landings are on Runway 33.

[[Category:Airports in the United States of America]]

John F. Kennedy International Airport

2010-10-15T13:39:57Z

Flightmonster: missed a spot

{{Infobox Airport
|name = John F. Kennedy International Airport
|image =banner1.jpg
|iata =JFK
|icao =KJFK
|type =Public
|owner =Port Authority of New York and New Jersey
|city = New York City, New York, USA
|runway = 13R/31L
|length= 4442 m
|material= Asphalt
|runway2= 4L/22R
|length2= 3460 m
|material2= Asphalt
|runway3= 13L/31R
|length3= 3048 m
|material3= Concrete
|runway4= 4R/22L
|length4= 2560 m
|material4= Asphalt
|website =http://www.kennedyairport.com
}}
[[Category:Airports in the United States of America]]

John F. Kennedy International Airport (IATA: JFK, ICTO: KJFK, FAA LID: JFK) is one of three international airports serving the New York City area. It is also the busiest international air passenger gateway to the U.S. Originally called '''Idlewild Airport''', it has been renamed several times with names such as '''Major General Alexander E. Anderson Airport''', '''New York International Airport''', and '''Anderson Field'''. One month after the assassination of President John F. Kennedy in 1963, the airport's name was changed to John F. Kennedy International Airport. In 2009, about 45,915,069 passengers flew through JFK, making it the 12th busiest airport worldwide.

==Airline Hubs==

===Current===
*American Airlines
*Delta Air Lines
*JetBlue Airways
*Evergreen International Airways (Cargo)

===Former===

*United Airlines (Ended their hub after the September 11th attacks)
*Pan American World Airways (Went bankrupt in 1991)
*Trans World Airlines (Merged with American Airlines)
*National Airlines NA (Merged with Pan American)
*Carnival Airlines (purchased by Pacific International Airlines)
*Vanguard Airlines (Ended their hub, and later went bankrupt in 2002)

John F. Kennedy International Airport

2010-10-15T13:39:23Z

Flightmonster: some cleanup....if you have questions, post on the talk page

{{Infobox Airport
|name = John F. Kennedy International Airport
|image =banner1.jpg
|iata =JFK
|icao =KJFK
|type =Public
|owner =Port Authority of New York and New Jersey
|city = New York City, New York, USA
|runway = 13R/31L
|length= 4442 m
|material= Asphalt
|runway2= 4L/22R
|length2= 3460 m
|material2= Asphalt
|runway3= 13L/31R
|length3= 3048 m
|material3= Concrete
|runway4= 4R/22L
|length4= 2560 m
|material4= Asphalt
|website =http://www.kennedyairport.com
}}
[[Category:Airports in the United States of America]]

John F. Kennedy International Airport (IATA: JFK, ICTO: KJFK, FAA LID: JFK) is one of three international airports serving the New York City area. It is also the busiest international air passenger gateway to the U.S. Originally called '''Idlewild Airport''', it has been renamed several times with names such as '''Major General Alexander E. Anderson Airport''', '''New York International Airport''', and '''Anderson Field''' One month after the assassination of President John F. Kennedy in 1963, the airport's name was changed to John F. Kennedy International Airport. In 2009, about 45,915,069 passengers flew through JFK, making it the 12th busiest airport worldwide.

==Airline Hubs==

===Current===
*American Airlines
*Delta Air Lines
*JetBlue Airways
*Evergreen International Airways (Cargo)

===Former===

*United Airlines (Ended their hub after the September 11th attacks)
*Pan American World Airways (Went bankrupt in 1991)
*Trans World Airlines (Merged with American Airlines)
*National Airlines NA (Merged with Pan American)
*Carnival Airlines (purchased by Pacific International Airlines)
*Vanguard Airlines (Ended their hub, and later went bankrupt in 2002)

Communications

2010-10-15T02:14:53Z

Flightmonster: more fixes

== CTAF/UNICOM ==

Airports (in the United States) lacking a tower are sometimes served by a UNICOM radio. The UNICOM frequency gives pilots a common channel to communicate their intentions to other pilots in the vicinity of an uncontrolled airport.

It is generally required that pilots of aircraft having radio equipment permitting two-way communications should contact the Airport UNICOM to obtain advisory information and announce their intentions when within ten (10) miles of the Airport. Pilots are also encouraged to maintain a listening watch on the frequency when operating within a ten mile radius of the Airport. All departing aircraft shall announce on the UNICOM their intention and runway to be used for departure.

On initial contact, pilots report altitude, aircraft type and identification, and location relative to the airport and state their intention, to land or overfly.

Pilots give a status report on downwind, base and final approach.

=== FlightGear UNICOM ===

FlightGear does not fully implement UNICOM entirely. UNICOM works best in multiplayer, where you actually have listeners.

* To access UNICOM, press the dash key (-) to enter the radio chat menu. Press the number that corresponds to '[XXX TRAFFIC]'
(where 'XXX' corresponds to the airport you are closest), then choose your message.

== Air Traffic Control ==

Flightgear has a basic ATC system in place. There are two kinds of ATC in FlightGear:

* Multiplayer: A person chooses to fly an [[ATC-aircraft]] in multiplayer. He/She can be many types of control. Covered further in [[Air traffic control]] and [[Howto: Be a controller]].

* AI Control/AI Traffic: By default, AI Traffic exists in Multiplayer and Local sessions. More often than not, you can see AI Traffic and AI Tower communicate with each other in colourful messages.

To communicate with ATC, you can press the dash key: (-). It will bring up a menu. Use the number keys (not the Number Pad!) to select your message.

In multiplayer, you can also press the underscore character (_/Shift+-) to type your own message. You can also chat with others, too!

Other helpful ATC links:
*[[ATC Tutorial]]
*[[ATC_phraseology]]

== ATIS ==

The Automatic Terminal Information Service is broadcasted from most airports. Look up the ATIS frequency of an airport and set it to COM1. You will hear a faint broadcast about active runways, conditions, and airport info. Sometimes, in a multiplayer session with a person as ATC, he/she will send out an ATIS on Multiplayer Chat.

== Transponder ==
Wikipedia: [http://en.wikipedia.org/wiki/Transponder_code Transponder]

{{Understanding}}
[[es:Communications]]

User:Flightmonster

2010-10-15T02:12:32Z

Flightmonster: better

I frequently monitor the [[Special:RecentChanges|recent changes]] and fix things I find wrong. If you have any questions about what I'm doing, feel free to ask (see below for instructions).

If you have comments, questions, complaints, or concerns about the edits I make, please contact me using a Forum PM, on the talk page of this page, or through an e-mail. --[[User:Flightmonster|The]][[User talk:Flightmonster#top|Flight]][[Special:Contributions/Flightmonster|Monster]]

Talk:Sydney International Airport

2010-10-15T02:10:47Z

Flightmonster: sign your posts properly, it's the cool thing to do! use ~~~~ at the end of all your posts

There's no reason for this page to include a big list of IATA airline codes, and the runway / ILS data would be far more useful as a table than prose.''—This unsigned comment was added by'' [[User:Zakalawe |Zakalawe ]] ([[User talk:Zakalawe |talk]] • [[Special:Contributions/Zakalawe |changes]]) 13:37, 13 October 2010 (UTC)

The runway/ils is the format used in other airport pages, so I just copied it.
As for the airline stuff, yeah I'm not sure of it usefulness, I think I got the idea from one of the other airport pages, but I'll probably remove it as I refine the pages, along with refining what is useful in the runway section, I'm still thinking of how to add RNAV and VOR approaches, and how much STAR/SID information would be useful to summarise.... Since I only have about 1hour each night to work on it, it might take me a little while to refine it.

S.''—This unsigned comment was added by'' [[User:Scotth1|Scotth1]] ([[User talk:Scotth1|talk]] • [[Special:Contributions/Scotth1|changes]]) 08:10, 14 October 2010 (UTC)

Template:Unsigned

2010-10-15T02:09:34Z

Flightmonster: simpler wikipedia, simpler code, http://simple.wikipedia.org/w/index.php?title=Template:Unsigned2&oldid=658410 <- from Wikipedia too

''—This unsigned comment was added by'' [[User:{{{2}}}|{{{2}}}]] ([[User talk:{{{2}}}|talk]] • [[Special:Contributions/{{{2}}}|changes]]) {{{1}}} (UTC{{{3|}}})

Template:Unsigned

2010-10-15T02:07:54Z

Flightmonster: http://en.wikipedia.org/w/index.php?title=Template:Unsigned2&oldid=358415698 <- from Wikipedia

{{ {{{|safesubst:}}}unsigned|1={{{2}}}|2={{{1|}}}}}

User:Flightmonster/sig

2010-10-15T02:04:38Z

Flightmonster: new signature

[[User:Flightmonster|The]][[User talk:Flightmonster#top|Flight]][[Special:Contributions/Flightmonster|Monster]]

User:Flightmonster

2010-10-15T02:00:16Z

Flightmonster: concerns etc

If you have comments, questions, complaints, or concerns about the edits I make, please contact me using a Forum PM, on the talk page of this page, or through an e-mail. --The FlightMonster

FSweekend 2010

2010-10-15T01:52:44Z

Flightmonster: copyediting

[[Image:FSweekend_banner_2010.jpg|right|350px]]
This wiki page lists all information required for participants to the [[FSweekend]] and the attached multiplayer event(s). [[FlightGear]] will be represented by a team of seven regular FlightGear developers and users.

<eventcountdown date="06-November-2010">'''<daysuntil in="days">06-November-2010</daysuntil>''' until the FSweekend</eventcountdown>

==Booth information==
This year's booth will probably exist of:
[[image:Anaglyph-glasses.jpg|right]]
* an UMTS USB stick for unlimited date use at high speed, so users from all over the world can visit us virtually.
* a bunch of 3D glasses, to demo the [[Anaglyph (3D)|anaglyph]] ability of FlightGear.
* a FlightGear based [[Howto:_Build_your_own_procedure_trainer|procedure trainer]].
* a Linux-based triple-screen PC, with a generic set of input devices for general purpose flight demonstrations.
* a top-end workstation equipped with 4(!) nVidia GTX460 to showcase our multi-screen capabilities

=== Equipment Checklist ===
* One main power extension cord (DT: yellow)
* One main power extension cord (DT: green)
* One main power extension cord (TD: black)
* One main power extension cord (JVDV: red)
* One Linux-based PC (DT)
** Three monitors
** Saitek Joystick
** Saitek Rudder Pedals
** Headset
** Sound system
* One Linux-based PC (JVDV)
** Three monitors
** Thrustmaster HOTAS Cougar
** Saitek Rudder Pedals
** USB Headset
* One Macbook Pro (DT)
** simple joystick
* One Macbook, white (TD)
* One Linx-based Notebook (TD)
** simple joystick
** ELITE yoke
** simple, homemade multi-engine and view controller
** 3Dconnexion 3d-mouse
* One FlightGear based procedure trainer (TD) [[image:Pmpt-0.1.jpg|right|thumb]]
** ELITE ProPanelII
** FlightLink rudder set
** Two TFT Displays
** Panel controller
** old (historic?) tablet pc running Atlas
* One Thomas-Krens-AG workstation (TD)
** Eight monitors (probably)
* Two FlightGear banners (TD)
** mounting material (last year's setup from Durk)
* FlightGear business cards (TD)
* Coffee maker (Senseo, bring your own pads!) (TD)
* two or three sets of aviation headsets (deco) (TD)
* One CH Flight Sim Yoke
* One CH Pro Pedals

==Flight information==
===Airports===
Activities will mainly take place at and around [[Amsterdam Airport Schiphol]] (EHAM), [[Lelystad Airport]] (EHLE), [[Volkel Air Base]] (EHVK) and the VU University Medical Center Helipad [[EH0001]].

===Charts===
All charts that you may have to use on your flights are available at http://ais-netherlands.nl (AIS Publications > Integrated Package). Please note that these are the most up to date charts available, so certain situations might not have been changed in FlightGear (EHAM, EHLE and EHVK taxiways should be correct though).

Parking positions have been created for most of the Dutch airports including EHAM, EHRD, EHVK and EHLE (A1-A6, B1 and B2).

All named airports are for civil usage, except for [[Volkel Air Base]] (EHVK). This base will be occupied by the (AI) F-16 squadrons and likely one setup in Lelystad. Feel free to join with your F-16 or other Dutch/NATO mil aircraft.

===Weather information===
Reallife weather information can be found at the KNMI (Dutch Meteorological institute) website.
* [http://knmi.nl/actueel/metar.html METAR] current weather at airports
* [http://knmi.nl/waarschuwingen_en_verwachtingen/luchtvaart/nederlandse_vliegveldverwachtingen.html TAF] expected weather at airports
If the weather is really bad, it is likely that the FSweekend guys will use a preset weather scenario.

==Scenery==
We will be using newly generated scenery in Lelystad.

==Events==
The guys from [[TransGear]] will organise a multiplayer event on both days. The event consist pilots flying pre-requested routes from and to Schiphol (EHAM). All activity at EHAM will take place around 13:00 GMT (that is 14:00 local time in the Netherlands). Traffic will be controlled by at least one (likely more) air traffic controller(s).

The people in Lelystad will have something to show to the public and might be able to participate during parts of the event (maybe there are even some visitors to our booth that would like to fly in one of our best MP events).

More information in the [http://flightgear.org/forums/viewtopic.php?f=10&t=9773 forum topic] and on the [http://transgear.treborlogic.com/ TransGear website].

FlightGear Newsletter October 2010

2010-10-10T00:42:19Z

Flightmonster: /* Gulf of Finland sightseeing tour */

{{newsletter}}
{{TOC_right}}
''We would like to emphasize that the monthly newsletter can not live without the contributions of FlightGear users and developers. Everyone with a wiki account (free to register) can edit the newsletter and every contribution is welcome. So if you know about any FlightGear related projects such as for example updated scenery or aircraft, please do feel invited to add such news to the newsletter.''

==Newsletter mailing list==
To fulfill some requests, we now have a special newsletter [[mailing list]], thanks to Curt! Please [https://lists.sourceforge.net/lists/listinfo/flightgear-newsletter register yourself]. Emails will be sent when a newsletter is released, and possibly also a week in advance of the release, in order to remind anyone that their help is welcome.

==FlightGear events==
==Call for volunteers==
The [[OpenRadar]] project is looking for a new maintainer.

==Development news==
==Nasal for newbies==
==New software tools and projects==

==FlightGear addons and mods==
''Zakharov'' is working on a new glass cockpit and is improving the ZKV1000 instrument, turning it into a replica of the Garmin Primus 1000. The interface is based on a Garmin Primus 1000 user manual found in a DA40 aircraft. It is designed for simple integration in an aircraft panel, and in the future it will be possible to configure the graphic interface and automatic behavior for specific aircraft (i.e. speed warnings).

A user manual will be released when the instrument is completed. For now, it features:
* PFD and MFD (including revisionary mode)
* Altimeter, speedometer, TAS, and VSI
* Artificial horizon with flight director
* HSI with two VOR radios, GPS, and ADF
* Full menu interface
* Full radio stack
* Integration with the [[autopilot]]
* Flight plan creation "on the fly"
* External perl script for MFD map creation using the [[Atlas|Atlas mapping utility]] (works under Linux/UNIX and Windows only at the moment)

A release is still a few weeks off, but a [http://seb.marque.free.fr/fichiers/flightgear/zkv1000.tgz development snapshot] is available. Screenshots can be found [http://seb.marque.free.fr/fichiers/flightgear/snapshots/index.php?/category/5 here].

[[File:Zkv1000.jpg|thumb|250px|The zkv 1000 glass cockpit project]]

== In the hangar ==
===Boeing 747-400===
The [[Boeing 747-400]] has seen some extensive developments going on over the past month. Some of these include:
* EICAS pages
* Electrical system
* Sounds, recorded in from a real 747

===Lockheed L-1011-500 Tristar===
A new cockpit is being developed for the historic [[Lockheed L-1011-500|L-1011-500]] airliner by [[User:Armchair_Ace|Armchair Ace]] and ''statto'', hopefully making it an enjoyable aircraft to fly!

===Sikorsky S92 "Helibus"===
The S92 is currently under development by ''Arthur Maiden''. So far, the following are completed:
* Basic fuselage and rotor assembly
* Basic [[YASim]] FDM
* Openable cargo and crew doors
* Basic animations

Still on the to-do list:
* Animate tail rotor
* Add glass to windows
* Add further detail to fuselage, smooth out the model, add antennas

===Liveries===

==Scenery corner==
===Airports===

==Aircraft of the month==
==Airport of the month==
==Screenshot of the month==

==Suggested flights==
===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 modeled 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.

==Aircraft reviews==

==Wiki updates==

==Community news==
===FlightGear on YouTube===
* FlightGear user ''planetacancun'' uploaded an [http://www.youtube.com/watch?v=VB0N7MvQDkk excellent video] showing the equally excellent [[MiG-15]].
* Two videos ([http://www.youtube.com/watch?v=ZMEfzPGfXRU] [http://www.youtube.com/watch?v=3OXplTr96S4]) featuring the photo-scenery at [[Brest]], were uploaded by ''Dawid''. Pictures used are CC-BY-SA Brest Métropole Océane. http://www.brest.fr/territoire-competences/brest-metropole-oceane/bmo-vue-du-ciel.html
* A [http://www.youtube.com/watch?v=xd_WEpRKStc nice example] of some [[Howto: Multiplayer|multiplayer]] fun (chasing the [[An-225]] in a [[F-16]]) is uploaded by SweetChinMusic1133.
* A [http://www.youtube.com/watch?v=i2BSUOMyiIg video tutorial] showing how to add objects with the UFO uploaded by ''draoi99''.

[http://www.youtube.com/watch?v=XkeApfVUnVk&feature=PlayList&p=3B31CCD15245D0AA&playnext_from=PL&index=0&playnext=1 Watch the FlightGear PlayList] for a collection of all (somewhat) quality FlightGear videos ever uploaded to YouTube.

===New tutorials and screencasts===
===Forum news===
===Multiplayer===
===Virtual airlines===

==Useful links==
==And finally...==
===FAA adopts "line-up and wait"===
The American Federal Aviation Administration adopted the ICAO standard for [[ATC]] clearance to enter the runway. The command "[taxi into] position and hold" has been replaced with "line-up and wait" now, already in use at most non-US airports. FlightGear pilots and controllers are requested to bring this change in practice.

Read the official announcement at the [http://www.faa.gov/airports/runway_safety/news/current_events/lauw/ FAA website].

===Did you know===

[[Category:FlightGear Newsletter|2010 10]]

User talk:Nickyivyca

2010-10-08T14:59:35Z

Flightmonster: Dash 7

== Dash 7 ==
A year or so ago, you created [[De Havilland Canada DHC-7 Dash 7|this]] article, which showed that the status (at the time) was in early development. What is the current status now? [[User:Flightmonster|Flightmonster]] 14:59, 8 October 2010 (UTC)

Template:Boeing

2010-10-04T16:11:56Z

Flightmonster: spaces

{{Navigation
|title=Boeing
|content=
<div align=left>
'''Civilian aircraft:''' [[Boeing 314|314]] • [[Boeing 707|707]] • [[Boeing 717|717]] • [[Boeing 727-230|727-230]] • [[Boeing 737|737]] ([[Boeing 737-100|-100]]/[[Boeing 737-300|-300]]/[[Boeing 737-400|-400]]/[[Boeing 737-700|-700]]) • [[Boeing 747|747]] ([[Boeing 747-100|-100]]/[[Boeing 747-200|-200]]/[[Boeing 747-400|-400]]/[[Boeing 747-8i|-8i]]) • [[Boeing 757|757]] ([[Boeing 757-200|-200]]) • [[Boeing 777|777]] ([[Boeing 777-200|-200]]) • [[Boeing 787|787]] '''Military aircraft:''' [[Boeing-Stearman_Model_75|PT-17]] • [[Boeing B-17 Flying Fortress|B-17]] • [[Boeing B-29 Superfortress|B-29]] • [[Boeing B-52|B-52]] • [[C-17 Globemaster III|C-17]] • [[Boeing E-3 Sentry|E-3]] • [[Boeing KC-135E|KC-135E]] '''Helicopter:''' [[CH-47 Chinook Helicopter|CH-47]] • [[Bell Boeing V-22 Osprey|V-22]]</div>
}}
<includeonly>[[Category:Boeing]]</includeonly>

<noinclude>[[Category:Navigation template]]</noinclude>

Template:Beechcraft

2010-10-04T16:11:05Z

Flightmonster: space

{{Navigation
|title=Beechcraft
|content=
<div align=left>
'''Civilian aircraft:''' [[Beechcraft Model 99| Model 99]] • [[Beechcraft Baron 58|Baron]] • [[Beechcraft B1900D|B1900D]] • [[Beechcraft_Starship|Starship]]</div>
}}
<includeonly>[[Category:Beechcraft]]</includeonly>

<noinclude>[[Category:Navigation template]]</noinclude>

Beechcraft B1900D

2010-10-04T16:10:39Z

Flightmonster: switch from simply text to a more step by step guide, also, added a livery in the infobox that is included in the base package

{{infobox Aircraft
|image =BeechcraftB1900D.jpg
|name =Beechcraft B1900D
|type =Airliner
|livery=Air New Zealand, Central Mountain Air, Northern Thunderbird Air, [[Island Virtual Airways]], [[Air San Francisco]]
|authors =Syd Adams (3D model/FDM), Jean-Yves Lefort (MKVIII gpws)
|fdm =YASim
|status =Development
|fgname =b1900d
|download =http://www.flightgear.org/Downloads/aircraft/#b1900d
|ratingfdm =4
|ratingexterior =5
|ratingcockpit =4
|ratingsounds =4
}}

==About the aircraft ==

The '''Beechcraft 1900''' series aircraft is the most popular 19-passenger airliner in history. It is a pressurized, twin-engine [[Powerplant#Turboprop|turboprop]] manufactured by the Beechcraft Division of the Raytheon Company (now Hawker Beechcraft). Designed primarily as an all weather regional airliner capable of landing on relatively short runways it has also been used by the United States military and other governments.

Beech announced the improved '''1900D''', simulated here, at the US Regional Airlines Association meeting in 1989. The main difference in the 1900D was the substantially deeper fuselage allowing stand up headroom in the cabin. It also had larger passenger and cargo doors and windows, twin ventral strakes and auxiliary horizontal fixed tails. To carry the extra weight Beech upgraded to two PT6A-67D engines, each rated at 1,279 shaft horsepower. Although rarely used a fully fueled Beechcraft 1900 has a range of 860 miles.

The [[Beechcraft B1900D]] is one of the default aircraft in [[FlightGear]] and has been available since [[FlightGear 0.9.8]].

== Procedures ==

=== Starting Procedure ===
In the menu bar at the top of the screen you may select B1900D and then Autostart. You may also choose to start-up manually. In the help menu you will find a start up tutorial this is a quick summary.

*Switch on the battery
*Switch on the left and right generators located on the lower left pilots panel. This should bring up the electrical systems and you should have instrumentation lights
*Switch on the avionics located just below the battery and generator switches.
*Look at the throttle panel in between the pilot and co-pilot. The two far right levers are labeled Condition. Move them fully forward by clicking at the top of the lever slots or by pressing “m”. You should now hear the engines starting up.
*Move the levers labeled Propeller forward by clicking at the top of the lever slots or by pressing “n”.
*Move the levers labeled Throttle to the idle position by clicking at the top of the lever slots or by pressing “9” or “PAGEUP”.
*Switch on Master Panel and any lights needed on the left side of the overhead console.
*Reset the Master Caution Warning in the middle top of the pilot panel that is probably flashing red now that all systems are powered up.
*The aircraft is now ready for take off.

=== Takeoff ===
*Decision at 105 KIAS
*Rotation at 110 KIAS
*Pitch 10-15 degrees
*Trim before engaging autopilot

=== Climb ===
*Airspeed 160 KIAS
*Climb Rate 1500 fpm

=== Cruise ===
*220 –240 KIAS

=== Descent ===
*180 KIAS
*Descent Rate –1500 fpm

=== Approach ===
*Establish 150 KIAS
*Set flaps to approach
*Establish 130 KIAS
*Landing gear down – set flaps full down
*Final glide slope 110 KIAS

=== Landing ===
*100 KIAS
*Main wheels down first
*Lower nose gear

== [[GPS]] ==
The B1900D is equipped with a functioning Bendix/King KLN 908 [[GPS]] that can be slaved to the autopilot. In the help menu you will find a tutorial on [[GPS]] navigation.

== See also ==
*[[Table of models]]
*[[FlightGear 1.0 default aircraft]]

[[Image:Beechcraft_B1900D.JPG|thumb|270px|Cockpit of the B1900D]]
{{Beechcraft}}
[[Category:Aircraft]]
[[Category:Civilian aircraft]]
[[Category:Model with well-implemented cockpit]]
[[Category:Beechcraft]]