FlightGear wiki - User contributions [en]

File:2024.2 PBR-rendered cockpit.png

2026-05-25T04:39:37Z

Fgf5: Uploaded own work with UploadWizard

=={{int:filedesc}}==
{{Information
|description={{en|1=PBR-rendered cockpit of c172 in 2024.2}}
|date=2026-05-25
|source={{own}}
|author=[[User:Fgf5|Fgf5]]
|permission=
|other versions=
}}

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

Main Page

2026-05-25T04:29:25Z

Fgf5: format

{{Main page/Header
|title = Welcome to the [[FlightGear wiki]]
|subtitle = ''Fly free!''
|rightbox = {{Main page/Languages}}
|introduction =
[[Help:Your first article|Get involved]] by starting, improving, or extending articles.

|rightcolumn1 = [[File:Portal user.png|40px]]</div>
[[Portal:User|Using]] 
'''[[New to FlightGear]]''' 
[[Frequently asked questions]] • [[Troubleshooting problems|Troubleshooting]] 
[[Howto: Install scenery|Installing scenery]] • [[Howto: Install aircraft|Installing aircraft]] 
[[Aircraft|Aircraft list]] • [[Howto: Fly a helicopter|Helicopter flying]]
|rightcolumn2 = [[File:Portal developer.png|40px]]</div>
[[Portal:Developer|Developing]] 

[[Portal:Developer/Aircraft|Aircraft]] • [[Portal:Developer/Scenery|Scenery]] • [[Portal:Embedded|Embedded]] 
[[Howto: Place 3D objects with the UFO|Placing objects]] • [[Howto: Create custom terrain|Editing terrain]] [[Howto:Improve scenery in your area, or area of interest|Scenery: Improving your area]] 
[[How the FlightGear project works]]
|rightcolumn3 = [[File:Portal wiki.png|40px]]</div>
 [[Portal:Wiki|Wiki]] 

[[FlightGear Wiki|About the wiki]] • [[Help:Contents|Help]] 
[[Help:Your first article|Your first article]] • [[Help:Translate|Translate]] 
[[Special:Categories|Categories]]

|sections =
{{Main page/Leftbox
|title = About FlightGear
|logo = FlightGear logo.png
|contents = '''[[FlightGear]]''' is a flight-simulator created by an international group of volunteers, and released as free, open-source [[GNU General Public License|GPL]] software. It has been used for [[Professional and educational FlightGear users|academic research, education]], and for fun.

FlightGear comes with a set of illustrated documentation, notably "[https://flightgear.org/support/manual The Manual]," which is included in the installation package. This wiki provides additional documentation on both user and development topics.

=== I am looking for … ===
* [[Portal:User|Help on using FlightGear]]
* [[Portal:Developer|How to contribute something to FlightGear]]
* [[table of models|Information about aircraft developed for FlightGear]]
}}
{{Main page/Leftbox
|title = News
|logo = Nuvola apps knewsticker.png
|contents = {{News}}
}}
{{Main page/Leftbox
|title = Did you know …
|logo = Nuvola apps ktip.png
|contents = {{Did you know}}
}}

}}

{{Main page/Rightcolumn
|title = Highlight
|contents = <center style="padding-top: 0.9em">[[File:2024.2 HDR PBR rendering.png|frameless]]</center>
|padding-right = 23px
}}Coming HDR/PBR rendering in version 2024.2 (nightly).
{{Main page/Rightcolumn
|title = [[:Category:Screenshot of the month|Screenshot of the month]]
|contents = <center style="padding-top: 0.9em">{{POTM/{{#ifexpr: {{#time: m}} = 01 | {{#expr: {{#time: Y}} - 1 }}-12 | {{#time: Y }}-{{padleft: {{#expr: {{#time: m}} - 1}} | 2 | 0}}}}}}</center>
|padding-right = 23px
}}
{{Main page/Rightcolumn end
|title = [[FlightGear and Git|Development repository status]]
|contents = <center style="padding-top: 0.9em">{{GitStatus}}</center>
|padding-right = 23px
}}

[[Category:FlightGear wiki]]

Main Page

2026-05-25T04:28:22Z

Fgf5: changed the highlight picture (admins can revert it if dissatisfied)

{{Main page/Header
|title = Welcome to the [[FlightGear wiki]]
|subtitle = ''Fly free!''
|rightbox = {{Main page/Languages}}
|introduction =
[[Help:Your first article|Get involved]] by starting, improving, or extending articles.

|rightcolumn1 = [[File:Portal user.png|40px]]</div>
[[Portal:User|Using]] 
'''[[New to FlightGear]]''' 
[[Frequently asked questions]] • [[Troubleshooting problems|Troubleshooting]] 
[[Howto: Install scenery|Installing scenery]] • [[Howto: Install aircraft|Installing aircraft]] 
[[Aircraft|Aircraft list]] • [[Howto: Fly a helicopter|Helicopter flying]]
|rightcolumn2 = [[File:Portal developer.png|40px]]</div>
[[Portal:Developer|Developing]] 

[[Portal:Developer/Aircraft|Aircraft]] • [[Portal:Developer/Scenery|Scenery]] • [[Portal:Embedded|Embedded]] 
[[Howto: Place 3D objects with the UFO|Placing objects]] • [[Howto: Create custom terrain|Editing terrain]] [[Howto:Improve scenery in your area, or area of interest|Scenery: Improving your area]] 
[[How the FlightGear project works]]
|rightcolumn3 = [[File:Portal wiki.png|40px]]</div>
 [[Portal:Wiki|Wiki]] 

[[FlightGear Wiki|About the wiki]] • [[Help:Contents|Help]] 
[[Help:Your first article|Your first article]] • [[Help:Translate|Translate]] 
[[Special:Categories|Categories]]

|sections =
{{Main page/Leftbox
|title = About FlightGear
|logo = FlightGear logo.png
|contents = '''[[FlightGear]]''' is a flight-simulator created by an international group of volunteers, and released as free, open-source [[GNU General Public License|GPL]] software. It has been used for [[Professional and educational FlightGear users|academic research, education]], and for fun.

FlightGear comes with a set of illustrated documentation, notably "[https://flightgear.org/support/manual The Manual]," which is included in the installation package. This wiki provides additional documentation on both user and development topics.

=== I am looking for … ===
* [[Portal:User|Help on using FlightGear]]
* [[Portal:Developer|How to contribute something to FlightGear]]
* [[table of models|Information about aircraft developed for FlightGear]]
}}
{{Main page/Leftbox
|title = News
|logo = Nuvola apps knewsticker.png
|contents = {{News}}
}}
{{Main page/Leftbox
|title = Did you know …
|logo = Nuvola apps ktip.png
|contents = {{Did you know}}
}}

}}

{{Main page/Rightcolumn
|title = Highlight
|contents = <center style="padding-top: 0.9em">[[File:2024.2 HDR PBR rendering.png|frameless]]</center>
|padding-right = 23px
}}.
{{Main page/Rightcolumn
|title = [[:Category:Screenshot of the month|Screenshot of the month]]
|contents = <center style="padding-top: 0.9em">{{POTM/{{#ifexpr: {{#time: m}} = 01 | {{#expr: {{#time: Y}} - 1 }}-12 | {{#time: Y }}-{{padleft: {{#expr: {{#time: m}} - 1}} | 2 | 0}}}}}}</center>
|padding-right = 23px
}}Coming HDR/PBR rendering in version 2024.2 (nightly).
{{Main page/Rightcolumn end
|title = [[FlightGear and Git|Development repository status]]
|contents = <center style="padding-top: 0.9em">{{GitStatus}}</center>
|padding-right = 23px
}}

[[Category:FlightGear wiki]]

File:Canvas menu 2024.2+.png

2026-05-25T04:22:14Z

Fgf5: Uploaded own work with UploadWizard

=={{int:filedesc}}==
{{Information
|description={{en|1=The menu in the canvas UI in 2024.2+}}
|date=2026-05-25
|source={{own}}
|author=[[User:Fgf5|Fgf5]]
|permission=
|other versions=
}}

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

File:2024.2 HDR PBR rendering.png

2026-05-25T04:20:38Z

Fgf5: Uploaded own work with UploadWizard

=={{int:filedesc}}==
{{Information
|description={{en|1=HDR and PBR rendering in 2024.2}}
|date=2026-05-25
|source={{own}}
|author=[[User:Fgf5|Fgf5]]
|permission=
|other versions=
}}

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

Aircraft speed

2026-05-23T04:52:16Z

Fgf5: /* V speeds */ links

Speed combines two factors, the ''distance'' travelled in a certain amount of ''time''. In aviation speed is most often expressed in '''knots''' (kt). One knot is one nautical mile per hour. In an aircraft the speed is "measured" with a [[#Pitot tube|pitot tube]]. Together with the static pressure one can determine not the speed of the aircraft, but the speed of the air flowing around the aircraft, the [http://en.wikipedia.org/wiki/Airspeed '''airspeed''']. Thus the speed of the aircraft relative to the airmass it is flying in.

The airspeed can be indicated in knots, km/h or even m/s. In general however, knots are used. But in some countries (like Russia and China), km/h is used.
In older planes, notably German WW II fighter planes, the airspeed is indicated in kilometers per hour (km/h), which is still used in present-day European glider planes. The conversion factor is 1.852, i.e. you can roughly divide a reading in km/h by two in order to get the value in knot.

If the speed is indicated in knot, sometimes a 'K' is put before the acronym, so KEAS stands for 'equivalent airspeed in knot'.

For (near-)supersonic planes the speed can be expressed in Mach.

== Expressing speed ==
=== Ground speed ===
* [http://en.wikipedia.org/wiki/Ground_speed '''Ground''' speed (GS)] is the horizontal speed in which the aircraft moves relative to a fixed point on the ground.

One needs to know the GS in order to see how long a flight from A to B actually takes. Nowadays GS can be directly measured using a GPS system, and some aircraft equipped with such a system have a GS indicator. The GS can be calculated from TAS by correcting it for the prevailing wind at altitude or by measuring the time between passing two points on the ground [[radio beacons]] with a known distance, but in Flightgear you can always cheat and get it from the property browser under <tt>velocities/groundspeed-kt</tt>.

GS is the velocity in the horizontal direction of the aircraft. I.e. in a steep dive, the aircraft can move very fast, but because the motion is chiefly vertical, the ground-speed can be very small at the same time. This is where the GS differs from the ground-speed of a car.

=== True airspeed ===
* [http://en.wikipedia.org/wiki/True_airspeed '''True''' airspeed (TAS)] is the speed in which the aircraft moves relative to the surrounding air.

[[File:C182s-ais-tas.png|thumb|Airspeed Indicator from the [[Cessna_182S]] showing difference between IAS (118 knots) and TAS (134 knots).Note the white TAS disc was rotated to match OAT and pressure altitude (+10° / 8000ft)]]

The difference between TAS and GS is that the air itself may move with respect to the ground (that's wind), and dependent on course relative to the wind direction a discrepancy between TAS and GS is induced. TAS can't really be measured directly but needs to be calculated, unless standing still on the ground where the TAS can be "seen" with the windbag.

Knowing TAS during flight is surprisingly useless - for navigation, ground speed is needed, and aerodynamic limits do not depend on TAS but rather IAS. The chief value of TAS is as a measure of aircraft performance and in pre-flight planning before the wind effect is taken into account.

The TAS can be calculated from CAS, air temperature and [[Altitude#Pressure altitude|pressure altitude]] and is the second step to calculate the GS from IAS for navigation.

Often TAS and GS are assumed (confused) to be the same, they are not.

Some planes Airspeed Indicators have a disc that can be rotated to obtain the TAS. Usually you need to set your Altimeter to pressure Altitude (29.92 inHg / 1013.25 hPa) and rotate the disc so the altitude and outside air temperature (OAT) align. The needle then will point to the TAS. The differences can get quite huge.

=== Indicated airspeed ===
* [http://en.wikipedia.org/wiki/Indicated_airspeed '''Indicated''' airspeed (IAS)] is the number displayed on the [http://en.wikipedia.org/wiki/Airspeed_indicator airspeed indicator].

The Indicated Airspeed is determined with Total Pressure (measured with a [[#Pitot tube]]) and Static Pressure. Because of measurement faults IAS usually has a failure. Without this failure you get CAS. The IAS is not the TAS since the pressure differs greatly with [[altitude]] (more specific the density of the air). The higher the [[altitude]] the lower the IAS while flying the same TAS.

In spite of this dependence on [[altitude]], IAS is a very useful quantity in flight. Many aerodynamic properties, for example drag, lift, the stress on the airframe, stall speed or the forces on control surfaces depend on the dynamic pressure generated by the airstream, not on the actual aircraft speed. The stall speed of an aircraft at sea level is very different from the stall speed (in TAS) at 30.000 ft - but they correspond to the same IAS reading.

Per definition CAS = TAS in standard ISA conditions and sea level. At 80.000 feet (the cruising altitude of a [[SR-71]]), the IAS of 400 knot corresponds to a TAS in excess of 1600 knot (..that corresponds with about Mach 3 at that altitude).

=== Calibrated airspeed ===
* [http://en.wikipedia.org/wiki/Calibrated_airspeed '''Calibrated''' airspeed (CAS)] is calculated from IAS and correcting it for measurement errors.

Modern equipment can most often can indicate the CAS. For navigation the CAS is the first step to calculate the GS.

=== Equivalent airspeed ===
* [http://en.wikipedia.org/wiki/Equivalent_airspeed '''Equivalent''' airspeed (EAS)] takes into account another correction (above [[#Calibrated airspeed]], this time having to do with air properties rather than sensor errors. EAS at low altitude and low airspeeds is very close to CAS, but CAS incorporates compressibility effects, EAS assumes no compressibility.

At high altitude, the compressibility of air changes, so even CAS becomes more and more unreliable. For the [[SR-71]] Blackbird with a ceiling of 85.000 feet, the CAS becomes very unreliable and the plane has to be flown based on a EAS. For more conventional aircraft, EAS is not used. Thus, EAS is what a perfect dynamic pressure sensor would show when properly calibrated for the air compressibility at the current altitude.

=== Mach number ===
* The [http://en.wikipedia.org/wiki/Mach_number '''Mach number''' (M)] is the speed of the aircraft divided by the speed of sound (at that temperature). It is usually calculated, but can also be directly determined with Impact and Static pressure. Mach has no dimension.

The aircraft's behavior at Mach 1 at sea level is about the same as the behavior of the aircraft at an altitude of 60000 feet.
A Mach number below 1 means that the plane moves subsonic. A Mach number above 1 indicates supersonic flight. The Mach number is critical because a number of phenomena take place just around Mach 1 (transonic speed), for example a sudden increase in drag induced by shock-wave generation (sonic-boom). Aircraft that are not designed to fly supersonic will break up at Mach 1. The shape of the aircraft can cause parts of the aircraft being at or above Mach 1 while the fuselage is subsonic. Flying near Mach 1 can be quite dangerous, for most fast (but subsonic) aircraft Mach 0.83 is the limit. High flying aircraft, like passenger aircraft, can reach that limit easy while descending.

The speed of sound changes with the compressibility (and hence temperature) of air, the Mach number is dependent on [[altitude]] (as the air temperature drops at higher altitudes). This implies that Mach 2 at sea level corresponds to a faster TAS than Mach 2 at 30.000 ft. The precise relation between TAS, Mach number and altitude is a complicated formulae and depends in essence on the local weather pattern determining the pressure and temperature gradients in the atmosphere.
The Mach number is measured/calculated from the same information as the EAS ([[#Pitot tube]] and [[altimeter]])

== V speeds ==
For the complete V speed "definitions" list please visit [http://en.wikipedia.org/wiki/V_speeds Wikipedia]. Here a small abstract. Note that V speed definitions can depend of local [[Flight rules]]. Most V speeds depend on the aircraft configuration (how much it weights etc.) so must be calculated forehand and must be included in the flight-plan. V speeds are used to compare aircraft performance and will be mentioned in the aircraft flight manual (AFM).

* M speeds are expressed in Mach.

{|
|- valign="top"
| V1 || Take-off decision speed & Critical engine failure recognition speed.
During take-off the speed at which the aircraft safely can take-off even when one (of more) engine fails ("eats a bird"). The co-pilot (FO) will call out V1 during take-off, the pilot will check if all engines are running and decides to continue or abort take-off.
|-
| V2 || Take-off safety speed.
|-
| V3 || [[Flap]] retraction speed.
|-
| VA|| Design maneuvering speed. Above this speed it is a bad idea to make sudden manoeuvres.
|-
| VC || Design cruising speed is like VA related to the loads on the aircraft structure. For non-reciprocating aircraft it is the red line on the airspeed indicator.
|-
| VD || Max dive speed (for certification only). It is always higher as VC and it has a margin towards the speed where the aircraft is shown to be free from flutter.
|-
| VFE || Maximum flap extended speed.
|-
| VLE || Maximum landing gear extended speed.
|-
| VLO || Maximum landing gear operating speed.
|-
| VMO / MMO || Maximum operating limit speed (Turbine aircraft). Usually the same as VC and the redline on your airspeed indicator.
|-
| VNE || Never exceed speed (Reciprocating aircraft). The red line on your airspeed indicator.
|-
| VNO || Maximum structural cruising speed or maximum speed for normal operations (Reciprocating aircraft). Usually the same as VC. the speed on your airspeed indicator where the green arc changes to yellow.
|- valign="top"
| VR || Nose-wheel take off speed.
The speed at which the nose-wheel leaves (should leave) the ground. As the speed increases the yokes will be pulled at Vr. It is also the speed at which the aircraft still can be stopped if there is a critical failure. The co-pilot (FO) will call out "rotate" during take off. VR is very similar to VROT and VREF.
|-
| VRef|| Landing reference speed or threshold crossing speed.
|- valign="top"
| VS || [[Stall]] speed or minimum steady flight speed for which the aircraft is still controllable.
|- valign="top"
| VS0 || Stall speed or minimum flight speed in landing configuration.
|-
| VS1 || Stalling speed in a specified configuration
|-
| VX || Best angle of climb speed
|-
| VXSE || Best angle of climb speed, one engine out
|-
| VY || Best rate of climb speed
|-
| VYSE || Best rate of climb speed, one engine out
|}

* Not knowing the (complete list of) V speeds has caused dramatic accidents. It has occurred that the pilot and co-pilot were not aware of the minimal speed of an aircraft during landing with one engine damaged causing loss of control just before touch-down (the pilot gave full throttle hoping to gain speed expecting to get back control causing the left-over engine push the aircraft to one side).

== Pitot tube ==
The [http://en.wikipedia.org/wiki/Pitot_tube pitot tube] is the tool to measure the Total Pressure. It is a tube directed forwards, exposed to the airstream. The air is being pushed inwards (rammed) by the motion of the aircraft and the (ram) pressure is measured. The indicated airspeed is determined with the impact pressure which is per definition: total pressure - static pressure. The impact pressure is NOT the dynamic pressure as impact pressure incorporates compressibility effects. Bigger aircraft have two (or even three) pitot tubes.

The pitot tube can be blocked easy, once blocked, or worse, partially blocked the IAS will have no relation with the speed of the aircraft. This situation is enhanced if the pitot tube controlling the autopilot is blocked.

Ice is a known cause of blockage of the pitot tube hence there are pitot heaters that should prevent forming of ice. Another known cause of blockage are insects. Blockage of pitot tubes is a known cause of some very dramatic accidents and every pilot should learn how to deal with strange behaving speed indicators and autopilots.

== Additional information ==

* Velocity: A vector combining speed and (angle of) direction. Often used as synonym of speed.
* [[Understanding Supersonic Flight]]

== External links ==
* [http://en.wikipedia.org/wiki/V_speeds V speeds] on English Wikipedia
* [http://www.ecfr.gov/cgi-bin/text-idx?SID=08466be6bfab4f37b995be61ff13ec21&node=14:1.0.1.3.11.3.164.8&rgn=div8 US. CFR 14 §25.335 – Design airspeeds] Do note that these are EAS (equivalent airspeed), not IAS (indicated airspeed).
* [http://code7700.com/v-speeds.html V-Speeds] at Code 7700

[[Category:Aviation]]

{{Understanding}}
[[de:Fluggeschwindigkeit]]
[[fr:Vitesse de l'avion]]
[[es:velocidad de la aeronave]]

Airbus A320 family

2026-05-23T04:47:59Z

Fgf5: /* Overview */

{{:{{PAGENAME}}/info}}
The '''Airbus A320 family''' is a series of twinjet narrowbody commercial passenger jets manufactured by [[Airbus|Airbus Industrie]]. Designed for short to medium haul flights, the aircraft pioneered fly-by-wire technology and regularly competes with the [[Boeing 737]] series. This is an accurate and complex recreation of the A320 family.

Main development is currently on hold awaiting restructuring, but fixes and minor improvements are still received from [https://github.com/legoboyvdlp/A320-family GitHub].

== Overview ==
Includes:
* A320-214 (CFM56)
* A320-232 (IAE V2500)
* A320-251N (CFM Leap)
* A320-271N (PW1100G)

This aircraft is available from the [[FlightGear Qt launcher|launcher]]. If you want to install it manually, see the right InfoBox for the repository to download and remember to rename the aircraft's folder to "A320-family" after downloading if needed.

== Development Team ==
* Flight Dynamics: Josh Davidson (Octal450)
* Systems, Instruments: Josh Davidson (Octal450), legoboyvdlp, Nia, Matthew Maring (hayden2000)
* 3D/Textures: Thorsten Herrmann (TH-555), Semir Gebran (CaptB)

== Tutorial ==

=== Takeoff ===
Click "Aircraft > Configuration Center > Ready for takeoff" and wait for a while, then push the throttle in the 3D cockpit to TO/GA. When the airspeed exceeds [[airspeed#V speeds|Vr]], pull back to rotate.

=== Climb ===
After takeoff, press <code>[</code> to retract the flaps and <code>g</code> to retract the landing gear, allowing the aircraft to accelerate to a higher airspeed. If you climb to high altitudes (higher than 30000 ft / 9150 m), note that the max airspeed Vmo (shown on PFD) will decrease at higher altitudes.

=== Cruise ===
Once at cruising altitude, reduce the throttle to a suitable cruise setting. You can press <code>v</code> or <code>shift+v</code> to switch views and enjoy the scenery, and press <code>ctrl+v</code> to switch back to the cockpit.

=== Approach ===
Begin the approach by reducing throttle to idle or a low cruise setting. Extend the landing gear by pressing <code>shift+g</code>, and extend flaps gradually according to the aircraft's speed by pressing <code>]</code>. Monitor the airspeed carefully; extending flaps and gear will increase drag and reduce speed.

Adjust pitch and throttle to keep the aircraft on the glideslope (click "View > Toggle glide scope tunnel" to [[Glideslope Tunnel|enable it]]). Set the [[ILS]] frequency if available, or navigate visually to the runway heading. Maintain a stable descent rate, typically 500-800 feet per minute for most airliners.

=== Landing ===
When the runway is in sight and the aircraft is properly aligned, continue descending toward the threshold. As the aircraft approaches the runway, reduce throttle to idle and begin the flare by gently pulling back on the stick just above the runway. The main landing gear should touch down first, followed by the nose gear.

After touchdown, deploy spoilers if available and apply reverse thrust if equipped. Brake as needed to slow the aircraft to taxi speed. Retract flaps and turn off landing lights once clear of the runway.

=== After Landing ===
Taxi to the parking position at a safe speed. Set the parking brake (by pressing shift+b), shut down engines, and turn off electrical systems in the configuration dialog (Aircraft > Configuration Center).

=== Notices ===
==== Warning lights ====
Monitor the yellow (CAUTION) or red (WARNING) lights on the instrument panel. If they appear, immediate actions are required.

==== Fly-by-Wire ====
Compared to other yoke-controlled aircrafts, the fly-by-wire system of A320 has several different characteristics:
* Sidestick is not linked: The captain and first officer sidesticks move independently. You cannot feel what the other pilot is doing.
* No autotrim: The aircraft trims automatically. Do not attempt manual trim.
* Release returns to neutral: Releasing the sidestick centers it, but the aircraft holds its current attitude.
* Flight envelope protection: The system prevents stalls, excessive bank angles, and overloads. You may feel a "hard stop" when limits are reached.
* Thrust levers have detents: Use the physical detents (TO/GA, FLX/MCT, CL, IDLE) rather than smooth movement. Leave levers in CL during autothrust operation.

=== Using the selector knobs on the FCU ===
The flight control unit (FCU) is the panel on the glareshield that contains controls for the auto flight system, electronic flight information system (EFIS) screens and other systems. It contains various selector knobs that rotate. Some knobs can also be pushed or pulled in order to change modes or other settings.

{| class="wikitable"
|+Turning, pushing or pulling FCU knobs with a mouse
|-moved
|
! style="font-weight:bold;" | Left click
! style="font-weight:bold;" | Middle click <nowiki>*</nowiki>
! style="font-weight:bold;" | Right click
! style="font-weight:bold;" | Scroll Up
! style="font-weight:bold;" | Scroll Down
|-
! style="font-weight:bold" | Normal (no modifier keys)
| style="text-align:center;" | Push
| rowspan="2" style="text-align:center;" | Pull
| rowspan="2" style="text-align:center;" | ---
| style="text-align:center;" | Turn clockwise
| style="text-align:center;" | Turn counterclocwise
|-
! style="font-weight:bold;" | While holding {{key press|Shift}} key 
| style="text-align:center;" | Pull
| style="text-align:center;" | Turn clockwise (10× faster)
| style="text-align:center;" | Turn counterclockwise (10× faster) 
|}

''<nowiki>*</nowiki> On many setups, the scroll wheel of a mouse can be used as a middle button by pressing directly down on the wheel.''

Note: This section describes how to physically manipulate controls within the cockpit. Details about what the controls do, when they should be used, etc., are beyond the scope of this section.

== Gallery ==
<gallery mode="packed">
File:SOTM_2020-03_Winter_Evening_Departure_by_legoboyvdlp_(A320).jpg|Rain effect (March 2020)
File:A320-family-cockpit.png|The cockpit
</gallery>

== Related content ==
=== Forum topics ===
* {{forum link|t=38387|title=Is the TCA Airbus edition Compatible with Flightgear ?}} (February 2021 -) - Hints and tips on using the Thrustmaster TCA Airbus edition sidestick and throttle quadrant with FlightGear.

== External links ==
* [https://github.com/legoboyvdlp/A320-family/blob/dev/Docs/checklist.pdf The checklist]
* [https://forum.flightgear.org/viewtopic.php?f=4&t=36410 Development thread]
* [https://www.airbus.com/aircraft/passenger-aircraft/a320-family.html Airbus A320 Family official homepage]

{{Airbus}}

[[fr:Airbus A320 Family]]
[[Category:Red Griffin ATC compatible aircraft]]
[[Category:Octal450 hangar]]

Airbus A320 family

2026-05-23T04:46:24Z

Fgf5: /* Overview */

{{:{{PAGENAME}}/info}}
The '''Airbus A320 family''' is a series of twinjet narrowbody commercial passenger jets manufactured by [[Airbus|Airbus Industrie]]. Designed for short to medium haul flights, the aircraft pioneered fly-by-wire technology and regularly competes with the [[Boeing 737]] series. This is an accurate and complex recreation of the A320 family.

Main development is currently on hold awaiting restructuring, but fixes and minor improvements are still received from [https://github.com/legoboyvdlp/A320-family GitHub].

== Overview ==
Includes:
* A320-214 (CFM56)
* A320-232 (IAE V2500)
* A320-251N (CFM Leap)
* A320-271N (PW1100G)

This aircraft is available from the [[FlightGear Qt launcher|launcher]]. If you want to install it manually, see the right InfoBox for the repository or download and remember to rename the aircraft's folder to "A320-family" after downloading if needed.

== Development Team ==
* Flight Dynamics: Josh Davidson (Octal450)
* Systems, Instruments: Josh Davidson (Octal450), legoboyvdlp, Nia, Matthew Maring (hayden2000)
* 3D/Textures: Thorsten Herrmann (TH-555), Semir Gebran (CaptB)

== Tutorial ==

=== Takeoff ===
Click "Aircraft > Configuration Center > Ready for takeoff" and wait for a while, then push the throttle in the 3D cockpit to TO/GA. When the airspeed exceeds [[airspeed#V speeds|Vr]], pull back to rotate.

=== Climb ===
After takeoff, press <code>[</code> to retract the flaps and <code>g</code> to retract the landing gear, allowing the aircraft to accelerate to a higher airspeed. If you climb to high altitudes (higher than 30000 ft / 9150 m), note that the max airspeed Vmo (shown on PFD) will decrease at higher altitudes.

=== Cruise ===
Once at cruising altitude, reduce the throttle to a suitable cruise setting. You can press <code>v</code> or <code>shift+v</code> to switch views and enjoy the scenery, and press <code>ctrl+v</code> to switch back to the cockpit.

=== Approach ===
Begin the approach by reducing throttle to idle or a low cruise setting. Extend the landing gear by pressing <code>shift+g</code>, and extend flaps gradually according to the aircraft's speed by pressing <code>]</code>. Monitor the airspeed carefully; extending flaps and gear will increase drag and reduce speed.

Adjust pitch and throttle to keep the aircraft on the glideslope (click "View > Toggle glide scope tunnel" to [[Glideslope Tunnel|enable it]]). Set the [[ILS]] frequency if available, or navigate visually to the runway heading. Maintain a stable descent rate, typically 500-800 feet per minute for most airliners.

=== Landing ===
When the runway is in sight and the aircraft is properly aligned, continue descending toward the threshold. As the aircraft approaches the runway, reduce throttle to idle and begin the flare by gently pulling back on the stick just above the runway. The main landing gear should touch down first, followed by the nose gear.

After touchdown, deploy spoilers if available and apply reverse thrust if equipped. Brake as needed to slow the aircraft to taxi speed. Retract flaps and turn off landing lights once clear of the runway.

=== After Landing ===
Taxi to the parking position at a safe speed. Set the parking brake (by pressing shift+b), shut down engines, and turn off electrical systems in the configuration dialog (Aircraft > Configuration Center).

=== Notices ===
==== Warning lights ====
Monitor the yellow (CAUTION) or red (WARNING) lights on the instrument panel. If they appear, immediate actions are required.

==== Fly-by-Wire ====
Compared to other yoke-controlled aircrafts, the fly-by-wire system of A320 has several different characteristics:
* Sidestick is not linked: The captain and first officer sidesticks move independently. You cannot feel what the other pilot is doing.
* No autotrim: The aircraft trims automatically. Do not attempt manual trim.
* Release returns to neutral: Releasing the sidestick centers it, but the aircraft holds its current attitude.
* Flight envelope protection: The system prevents stalls, excessive bank angles, and overloads. You may feel a "hard stop" when limits are reached.
* Thrust levers have detents: Use the physical detents (TO/GA, FLX/MCT, CL, IDLE) rather than smooth movement. Leave levers in CL during autothrust operation.

=== Using the selector knobs on the FCU ===
The flight control unit (FCU) is the panel on the glareshield that contains controls for the auto flight system, electronic flight information system (EFIS) screens and other systems. It contains various selector knobs that rotate. Some knobs can also be pushed or pulled in order to change modes or other settings.

{| class="wikitable"
|+Turning, pushing or pulling FCU knobs with a mouse
|-moved
|
! style="font-weight:bold;" | Left click
! style="font-weight:bold;" | Middle click <nowiki>*</nowiki>
! style="font-weight:bold;" | Right click
! style="font-weight:bold;" | Scroll Up
! style="font-weight:bold;" | Scroll Down
|-
! style="font-weight:bold" | Normal (no modifier keys)
| style="text-align:center;" | Push
| rowspan="2" style="text-align:center;" | Pull
| rowspan="2" style="text-align:center;" | ---
| style="text-align:center;" | Turn clockwise
| style="text-align:center;" | Turn counterclocwise
|-
! style="font-weight:bold;" | While holding {{key press|Shift}} key 
| style="text-align:center;" | Pull
| style="text-align:center;" | Turn clockwise (10× faster)
| style="text-align:center;" | Turn counterclockwise (10× faster) 
|}

''<nowiki>*</nowiki> On many setups, the scroll wheel of a mouse can be used as a middle button by pressing directly down on the wheel.''

Note: This section describes how to physically manipulate controls within the cockpit. Details about what the controls do, when they should be used, etc., are beyond the scope of this section.

== Gallery ==
<gallery mode="packed">
File:SOTM_2020-03_Winter_Evening_Departure_by_legoboyvdlp_(A320).jpg|Rain effect (March 2020)
File:A320-family-cockpit.png|The cockpit
</gallery>

== Related content ==
=== Forum topics ===
* {{forum link|t=38387|title=Is the TCA Airbus edition Compatible with Flightgear ?}} (February 2021 -) - Hints and tips on using the Thrustmaster TCA Airbus edition sidestick and throttle quadrant with FlightGear.

== External links ==
* [https://github.com/legoboyvdlp/A320-family/blob/dev/Docs/checklist.pdf The checklist]
* [https://forum.flightgear.org/viewtopic.php?f=4&t=36410 Development thread]
* [https://www.airbus.com/aircraft/passenger-aircraft/a320-family.html Airbus A320 Family official homepage]

{{Airbus}}

[[fr:Airbus A320 Family]]
[[Category:Red Griffin ATC compatible aircraft]]
[[Category:Octal450 hangar]]

Glideslope Tunnel

2026-05-23T04:24:45Z

Fgf5: related content and link

[[File:Glideslope.JPG|thumb|270px]]
The '''Glideslope Tunnel''' is a feature which visually shows pilots in [[FlightGear]] the descent angle (3 degrees) and heading they should follow during their approach. It can be loosely compared to [[Instrument Landing System|ILS]], a real-life radio navigation system which provides precision guidance to an aircraft approaching a runway. The tunnel directs the pilot to the best suitable runway (considering wind direction and runway length) of the nearest [[:Category:Airports|airport]]. The tunnel can be activated from the [[menu]] while running the simulator: View > Toggle Glideslope Tunnel.

The [[Nasal]] script that is behind the tunnel is part of each FlightGear installation and can be found in <tt>[[$FG_ROOT]]/Nasal/glide_slope_tunnel.nas</tt>.

The script checks in 5 second intervals for the nearest airport, selects a "decent" runway (based on wind direction, runway length and width) and draws a glide slope tunnel for it consisting of red U-shaped geometries.

== Feature requests ==
There's much that can be improved. One could draw only the next three or four gates instead of the whole tunnel, consider wind direction etc. Also, one might prefer to be able to select a particular airport,
and have the tunnel drawn on the runway told by ATC, or one might want a circuit tunnel for tutorials, etc. All doable.

The whole thing is quite simple and flexible. Most of what's needed is already there in one of the Nasal library scripts in [[$FG_ROOT]]/Nasal/ and available as built-in Nasal functions. The rest is just combining them and placing square (or other models) in the landscape. The power of fgfs & Nasal.

== Related content ==
* [[Glideslope]]

== External links ==
* [http://forum.flightgear.org/viewtopic.php?f=36&t=19210 Drawing lines in the sky/environment] (forum topic)
* [http://www.mail-archive.com/search?l=flightgear-devel%40lists.sourceforge.net&q=glide_slope_tunnel&submit.x=0&submit.y=0 Related mailing list discussions]

[[Category:FlightGear feature]]

''For the technical details about the menubar, see [[Menubar]].''

The in-game '''menu''' provides access to Flightgear's various features.

[[File:Menubar2.jpg|frame]]

= List of built-in menus =

Here is an incomplete list of FlightGear's menus, with links to their descriptions.

== File ==
* Reset
* [[Instant Replay#Continuous (disk-based) recordings|Flight Recorder Control]]
* Time Mode
* Screenshot
* Sound Configuration
* Input Devices
* [[TerraSync|Scenery Download]]
* Quit

== View ==
* Toggle Fullscreen
* [[Rendering Options]]
* View Options
* [[Cockpit view options|Cockpit View Options]]
* [[Glideslope Tunnel|Toggle Glide Scope Tunnel]]
* [[Instant Replay]]
* [[Earthview|Earthview Orbital Rendering]]
* ALS Filter Effects

== Location ==
* Position Aircraft In Air
* Select Airport
* Random Altitude
* Tower Position

== Autopilot ==
* [[Autopilot#Autopilot Settings|Autopilot Settings]]
* [[Route Manager]]
* Previous Waypoint
* Next Waypoint

== Environment ==
* [[Weather]]
* Environment Settings
* [[Time|Time Settings]]
* [[Volcanoes]]

== Equipment ==
* [[Map]]
* Stopwatch
* Fuel and Payload
* Radio Settings
* [[GPS|GPS Settings]]
* Instrument Settings
* Light Switches
* [[Aircraft failure system|Random Failures]]
* [[Aircraft failure system|System Failures]]
* [[Aircraft failure system|Instrument Failures]]

== AI ==
* Traffic and Scenario Settings
* ATC Services in Range
* Wingman Controls
* [[AI Scenery Objects|AI Objects]]

== Multiplayer ==
* [[Multiplayer|Multiplayer Settings]]
* [[FGCom|FGCom Settings]]
* [[Chat Menu]]
* [[Pilot List]]
* [[Carrier over MP|MPCarrier Selection]]
* [[Swift|Swift Connection]]

== Debug ==
* Reload GUI
* Reload HUD
* [[Property Browser]]
* [[Nasal Console]]
...

== Help ==
* Aircraft Help
* [[Aircraft Checklists]]
* Common Aircraft Keys
* [[Tutorials]]
* About

= Related content =
* [https://flightgear.gitlab.io/getstart/release-{{current release|cr}}/en/HTML/getstart-ench5.html#menu-entries FlightGear Manual - Menu entries]

[[Category:FlightGear feature]]
[[Category:Menubar]]
[[Category:Lists]]

[[fr:menu]]

Airbus A320 family

2026-05-23T04:21:40Z

Fgf5: add tutorial

{{:{{PAGENAME}}/info}}
The '''Airbus A320 family''' is a series of twinjet narrowbody commercial passenger jets manufactured by [[Airbus|Airbus Industrie]]. Designed for short to medium haul flights, the aircraft pioneered fly-by-wire technology and regularly competes with the [[Boeing 737]] series. This is an accurate and complex recreation of the A320 family.

Main development is currently on hold awaiting restructuring, but fixes and minor improvements are still received from [https://github.com/legoboyvdlp/A320-family GitHub].

== Overview ==
Includes:
* A320-214 (CFM56)
* A320-232 (IAE V2500)
* A320-251N (CFM Leap)
* A320-271N (PW1100G)

This aircraft is available from the [[FlightGear Qt launcher|launcher]]. If you download it manually, see the right InfoBox for the repository or download and remember to rename the aircraft's folder to "A320-family" after downloading if needed.

== Development Team ==
* Flight Dynamics: Josh Davidson (Octal450)
* Systems, Instruments: Josh Davidson (Octal450), legoboyvdlp, Nia, Matthew Maring (hayden2000)
* 3D/Textures: Thorsten Herrmann (TH-555), Semir Gebran (CaptB)

== Tutorial ==

=== Takeoff ===
Click "Aircraft > Configuration Center > Ready for takeoff" and wait for a while, then push the throttle in the 3D cockpit to TO/GA. When the airspeed exceeds [[airspeed#V speeds|Vr]], pull back to rotate.

=== Climb ===
After takeoff, press <code>[</code> to retract the flaps and <code>g</code> to retract the landing gear, allowing the aircraft to accelerate to a higher airspeed. If you climb to high altitudes (higher than 30000 ft / 9150 m), note that the max airspeed Vmo (shown on PFD) will decrease at higher altitudes.

=== Cruise ===
Once at cruising altitude, reduce the throttle to a suitable cruise setting. You can press <code>v</code> or <code>shift+v</code> to switch views and enjoy the scenery, and press <code>ctrl+v</code> to switch back to the cockpit.

=== Approach ===
Begin the approach by reducing throttle to idle or a low cruise setting. Extend the landing gear by pressing <code>shift+g</code>, and extend flaps gradually according to the aircraft's speed by pressing <code>]</code>. Monitor the airspeed carefully; extending flaps and gear will increase drag and reduce speed.

Adjust pitch and throttle to keep the aircraft on the glideslope (click "View > Toggle glide scope tunnel" to [[Glideslope Tunnel|enable it]]). Set the [[ILS]] frequency if available, or navigate visually to the runway heading. Maintain a stable descent rate, typically 500-800 feet per minute for most airliners.

=== Landing ===
When the runway is in sight and the aircraft is properly aligned, continue descending toward the threshold. As the aircraft approaches the runway, reduce throttle to idle and begin the flare by gently pulling back on the stick just above the runway. The main landing gear should touch down first, followed by the nose gear.

After touchdown, deploy spoilers if available and apply reverse thrust if equipped. Brake as needed to slow the aircraft to taxi speed. Retract flaps and turn off landing lights once clear of the runway.

=== After Landing ===
Taxi to the parking position at a safe speed. Set the parking brake (by pressing shift+b), shut down engines, and turn off electrical systems in the configuration dialog (Aircraft > Configuration Center).

=== Notices ===
==== Warning lights ====
Monitor the yellow (CAUTION) or red (WARNING) lights on the instrument panel. If they appear, immediate actions are required.

==== Fly-by-Wire ====
Compared to other yoke-controlled aircrafts, the fly-by-wire system of A320 has several different characteristics:
* Sidestick is not linked: The captain and first officer sidesticks move independently. You cannot feel what the other pilot is doing.
* No autotrim: The aircraft trims automatically. Do not attempt manual trim.
* Release returns to neutral: Releasing the sidestick centers it, but the aircraft holds its current attitude.
* Flight envelope protection: The system prevents stalls, excessive bank angles, and overloads. You may feel a "hard stop" when limits are reached.
* Thrust levers have detents: Use the physical detents (TO/GA, FLX/MCT, CL, IDLE) rather than smooth movement. Leave levers in CL during autothrust operation.

=== Using the selector knobs on the FCU ===
The flight control unit (FCU) is the panel on the glareshield that contains controls for the auto flight system, electronic flight information system (EFIS) screens and other systems. It contains various selector knobs that rotate. Some knobs can also be pushed or pulled in order to change modes or other settings.

{| class="wikitable"
|+Turning, pushing or pulling FCU knobs with a mouse
|-moved
|
! style="font-weight:bold;" | Left click
! style="font-weight:bold;" | Middle click <nowiki>*</nowiki>
! style="font-weight:bold;" | Right click
! style="font-weight:bold;" | Scroll Up
! style="font-weight:bold;" | Scroll Down
|-
! style="font-weight:bold" | Normal (no modifier keys)
| style="text-align:center;" | Push
| rowspan="2" style="text-align:center;" | Pull
| rowspan="2" style="text-align:center;" | ---
| style="text-align:center;" | Turn clockwise
| style="text-align:center;" | Turn counterclocwise
|-
! style="font-weight:bold;" | While holding {{key press|Shift}} key 
| style="text-align:center;" | Pull
| style="text-align:center;" | Turn clockwise (10× faster)
| style="text-align:center;" | Turn counterclockwise (10× faster) 
|}

''<nowiki>*</nowiki> On many setups, the scroll wheel of a mouse can be used as a middle button by pressing directly down on the wheel.''

Note: This section describes how to physically manipulate controls within the cockpit. Details about what the controls do, when they should be used, etc., are beyond the scope of this section.

== Gallery ==
<gallery mode="packed">
File:SOTM_2020-03_Winter_Evening_Departure_by_legoboyvdlp_(A320).jpg|Rain effect (March 2020)
File:A320-family-cockpit.png|The cockpit
</gallery>

== Related content ==
=== Forum topics ===
* {{forum link|t=38387|title=Is the TCA Airbus edition Compatible with Flightgear ?}} (February 2021 -) - Hints and tips on using the Thrustmaster TCA Airbus edition sidestick and throttle quadrant with FlightGear.

== External links ==
* [https://github.com/legoboyvdlp/A320-family/blob/dev/Docs/checklist.pdf The checklist]
* [https://forum.flightgear.org/viewtopic.php?f=4&t=36410 Development thread]
* [https://www.airbus.com/aircraft/passenger-aircraft/a320-family.html Airbus A320 Family official homepage]

{{Airbus}}

[[fr:Airbus A320 Family]]
[[Category:Red Griffin ATC compatible aircraft]]
[[Category:Octal450 hangar]]

New to FlightGear

2026-05-20T19:47:39Z

Fgf5: /* Flying */ F-16

'''Welcome to [[FlightGear]]!''' Here we will try to get you up in the virtual air in the shortest time possible. We will also introduce you to some of the features of this flight simulator and also a few information on its community.

== Installation and setup ==
=== Hardware requirements ===
For FlightGear to run smoothly, it requires a video card with OpenGL drivers 4.0 or higher. This is usually not a problem, but take a look at the [[hardware recommendations]] to have a better idea.

=== Getting FlightGear ===
You may download the latest files from the [https://www.flightgear.org/download/ FlightGear download] page. Choose the source or binary files appropriate for your particular system. {{Wikipedia|AppImage|AppImage}} binary files for Linux are also available with 2020.3 LTS and later. Most Linux users will find that most distributions have a packaged version of FlightGear (the package name could be <code>fgfs</code> or <code>flightgear</code>.)

Depending on your technical expertise you may choose the [[Git]] development version of FlightGear, which typically has more features and can be required by some of the latest developmental aircraft, but can be unstable and is more complicated to get for non-Windows users. In general, the development version is not advised to the average user, but if you are willing to do some testing there is a nightly build available for [https://www.flightgear.org/download/nightly/ download]. If you are using a Git version controlled copy of FlightGear, you may choose to synchronise your aircraft using the version controlled [[FGAddon|FGAddon aircraft development repository]].

=== Installing on Windows ===
After you downloaded the installer, run it and follow its instructions to install FlightGear.

Defender SmartScreen on Windows may block the installation simply because the binary file is not signed with a key that Microsoft respects. Of course, the key is paid. In this case, we need to click on the inconspicuous "More info" link. Only then will the "Run anyway" button appear. You can safely trust that this is not a dangerous application, as long as you have actually downloaded it from official sources.

If you're using third-party antivirus software for some reason, it may be blocking FlightGear from installing. This isn't something we can control, so it's entirely up to you how you want to handle it.

With the Windows installer, you may choose where to install FlightGear. The [[$FG_ROOT]] directory would be <code><your chosen directory>/data</code>.

=== Installing on macOS ===
Installing FlightGear on macOS is very simple. Just drag and drop the FlightGear icon to the <code>/Applications</code> folder. That is it.

The first time you launch FlightGear, its icon on the Dock bounces for several seconds while loading aircraft and airport info. When the GUI launcher appears, select the aircraft and airport, then click "Fly!" to launch the simulator. You can configure more options using the GUI launcher. See the [http://flightgear.sourceforge.net/manual/next/en/getstart-ench4.html#takeoff-how-to-start-the-program official manual] for more details.

If you would like to launch FlightGear using command-line, launch <code>/Applications/Utilities/Terminal.app</code> and type the following.

cd /Applications/FlightGear.app/Contents/MacOS
./fgfs --options.....

The [[$FG ROOT]] and [[$FG SCENERY]] are not set on macOS. If you want to specify these variables yourself for command-line use, run the followings on Terminal.app:

FG_ROOT=/Applications/FlightGear.app/Contents/Resources/data
FG_SCENERY=[[$FG_ROOT]]/Scenery

After launching the GUI launcher, you will have the alias to [[$FG_ROOT]] at <code>$HOME/Documents/Flightgear/<version></code> so you can browse the data folder using Finder.

Note: Once you have installed FlightGear, Mac users can locate their [[$FG_ROOT]] folder by opening their applications folder in Finder, right clicking on FlightGear, and clicking "Show Package Contents". This will take you inside the FlightGear folder. You are now able to access all files including Data/Aircraft to [[Howto: Install aircraft#Macintosh OS X|install new aircraft]].

=== Installing from source ===
Main article: [[Building FlightGear]]

=== Getting scenery ===
A limited set of [[scenery]] comes installed with FlightGear. For FlightGear 2024.1 this consists of
* The area surrounding the featured airport for the release which is [[Keflavik_Airport|Keflavik International Airport]] (BIKF)
* The tutorial airport for the [[Cessna_172P|Cessna 172P]] which is [[Hilo_International_Airport|Hilo International Airport]] (PHTO)

In FlightGear, scenery is generally stored in you [[$FG ROOT]] directory, and is divided into three kinds of data:
* '''Airports''' holds airport data, like runway usage and parking spots.
* '''Objects''' and '''Models''' are the buildings, bridges and radio towers, etc. that represent three-dimensional structures.
* '''Terrain''' represents the contours, elevations and type of ground you fly/taxi over.

The current way of "installing" new scenery is enabling [[TerraSync]], which will automatically download and update any place you visit - even on the fly! If you have a slow Internet connection and/or computer you could instead use a scenery manager, for example [[TerraMaster]]. In addition you can also manually download and install new scenery parts, either the official [[World Scenery]] or custom scenery.

The official, although outdated, scenery is available at [http://www.flightgear.org/download/scenery/ the scenery download section] of the FlightGear website, and can be installed following [[Howto: Install scenery]]. You may obtain additional and more up to date scenery objects as they become available through the [http://scenemodels.flightgear.org/ FlightGear Scenery Database]. '''This is recommended for users with weak internet connections or weak computers!'''

Custom scenery is available in many places. For example, on the {{forum link|f=5|text=FlightGear forum}} or within repositories. An internet search should be able to find them. See [[Suggested_custom_scenery|suggested custom scenery]] page for a few recent releases.

FlightGear 2020.3.7 LTS and later added an experimental rollout of 3 dimensional buildings, roads, and objects based on OpenStreetMap data for the entire world to automatically downloaded TerraSync data - see [[OSM2City 1st Worldbuild|1st OSM2City world-build]] notes (March 2021). Some manual downloads of 3d structures for regions or entire countries is available on the [[Areas populated with osm2city scenery|osm2City downloads]] wiki page.

=== Getting aircraft ===
Additional [[aircraft]] can be downloaded and installed through the [[Qt-launcher|launcher]]. Alternatively, you can go to the FlightGear website and navigate to the [http://www.flightgear.org/download/ download page], then choose the aircraft download link that fits your FlightGear version. In addition there are many third party [[hangars]]. For the installation, see [[Howto: Install aircraft]].

== Running FlightGear ==
=== Starting FlightGear ===
The easiest way to start FlightGear is to use the desktop icon. This starts the graphical interface [[FlightGear Qt launcher]] where you can choose aircraft, start position etc. Remember the Qt launcher only has basic options to get you started. A lot of options for graphics, scenery, [[Weather|weather]], [https://www.flightgear.org/tours/simulating-the-ever-changing-scenery/ environment], [[Input_device|input devices]] etc. are available from the [[menu]] inside the simulator.

Many users choose however to start FlightGear directly from the command line. The executable name is <code>fgfs</code> and can be run without options. If it is "not found", it is likely not in your [https://en.wikipedia.org/wiki/PATH_(variable) path]. The location depends on your particular system and choices you made during compile and installation. There is a list of [[Command Line Parameters]] which must be used to change many options, like the aircraft you want. The most important:

fgfs --launcher # opens the FlightGear Qt launcher
fgfs --show-aircraft # displays a list of installed aircraft
fgfs --aircraft=c172p # start FG with the aircraft "c172p" (from the list)

The Qt launcher also lets users add command line parameters for options that are normally changed from the menu inside the simulator, as well as quite advanced options that are only available from the command line (as of August 2020).

=== Configuring rendering and UI ===
[[File:Rendering options 2024.1.png|thumb|View > Rendering Options dialog.]]
If your render quality or framerate is too low, click "View > Rendering Options" to adjust the graphic settings. For newer hardware, it's recommended to set "graphics quality" to high and check "use disk space for faster loading", "animated jetways" and "satellite photoscenery".

If the menu text appears too small on high DPI or large screens, you can manually [[Menubar#How to Change the Default Menubar Font Size|change the menubar font size]] by editing the data file, or simply click "Debug > Cycle GUI Style".

=== Using the keyboard and/or mouse ===
Users with limited access to a [[joystick]] or other controllers sometimes use the keyboard or mouse to control their aircraft. Using the keyboard to fly can be difficult and the mouse is recommended over the keyboard for flying, yet even a cheap joystick would improve the experience so much.

To get help with keyboard commands, with FlightGear running, go to the ''Help'' menu, look under ''Basic Keys'' (for simulator related commands) and ''Common Aircraft Keys'' (for commands universal to all aircraft) and ''Aircraft Help'' (for key commands specific to your aircraft). If the main menu is hidden press {{key press|F10}}. If you come from other simulators, check [[key commands compared to other simulators]] for an overview of the difference between the key commands of that sim and FlightGear.

To use the mouse to fly the aircraft, press {{key press|Tab}} (the cursor should change to a cross) and move the mouse to direct the aircraft. Press {{key press|Tab}} again to look around (cursor should show a two sided arrow), and press {{key press|Tab}} again to return to normal mode, used to click stuff in the cockpit. In some aircraft, such as the [[A320neo]] and [[Airbus A330 (disambiguation)|A330]] this unfortunately will not work, so you will have to use right click to look around and mouse mode is disabled. Fortunately, those planes are airliners, which are really stable and easy to fly with the keyboard.

For most users lacking a rudder axis control, it’s difficult to manually coordinate [[aileron]] and [[rudder]] movements during a turn. To enable auto-coordination and make flight easier, you may click "Settings", then click the "Show more" button on the right of "General", and finally click "Enable auto-coordination" in the launcher.

=== First time in the cockpit ===
Finding your way around the cockpit can be daunting the first time.

Where is the "virtual cockpit"? Not all FlightGear aircraft come with an interior actually, some research projects may not even come with an exterior model. A 2D panel may display over the 3D cockpit if one exists. You may turn this off through ''Main Menu'' > ''View'' > ''View Options'' and deselecting ''Show 2D panel'' in the ''Display Options'' section, or by pressing {{key press|Shift|P}}. Otherwise, you should be sitting in the virtual cockpit when FlightGear starts, as long as the Cockpit View is selected (if not pressing {{key press|Ctrl|V}} should get you to the pilot view).

You may find it difficult to read some of the displays, dials and gauges on the instrument panel. You can use the ''view'' mode of the mouse (press {{key press|Tab}} until you get a cursor shaped like a double arrow) to pan and the mouse wheel to zoom, or pan with the joystick hat and zoom with {{key press|X}} and {{key press|Shift|X}}.

One of the first steps that many take on entering an unfamiliar cockpit is to press {{key press|Ctrl|C}} to highlight all the "hotspots", that is instrument controls, buttons, knobs, etc. Many aircraft also offer a specific help menu.

Some functions, such as starter or magneto, may be difficult to use or simply lack clickable "hotspots", especially in aircraft models which are in development. In most cases you can go for the equivalent controls on a 2D panel or resort to the keyboard. The keyboard always work according to the assignments listed on the ''Help'' menu, but sometimes these are reassigned by an aircraft or configuration. Again, remember to check all the help dialogs.

=== Starting the engine ===
You are eager to fly, but the engine is off. Well, turning on the engines is not always easy. Some aircraft have an ''autostart'' entry in their custom menu, but here is a general procedure that should work in many cases:

In general to start the engine on a piston-engine type aircraft, you need (after making sure the game is not paused {{key press|p}}):
# Fuel: Some aircraft start the simulation with no fuel. You can add it in ''Equipment'' > ''Fuel and Payload''.
# Correct fuel mixture: This is generally ''rich'', so push the red knob all the way in, or use the key {{key press|m}} to enrich ({{key press|Shift|m}} leans.)
# Magnetos set on ''both'': Turn the key or press {{key press|}}} ''three times'' to move through ''R'', ''L'', ''Both''.
# Throttle: Some engines start better with a little gas.
# Run the starter: Click the ''Start'' position of the key on the panel, or press {{key press|s}}. Hold the starter for sufficient time, even 10 seconds.

Starting all engines in a multi-engine aircraft is similar to the single engine - except you must follow the same start sequence for each and every engine. FlightGear provides a convenient way to do this for all engines at once: Press {{key press|~}} and all the procedure above will work for all the engines. Note though that the default 2D panel is connected to ''only one engine'' and the {{key press|~}} trick might not work. Also, give some gas to be sure that all the engines are on.

These instructions may not work for jet aircraft, helicopters, or other types of aircraft with complex start procedures. Check the instructions in the aircraft help menu (press {{key press|?}}) and/or look at [[Aircraft|the aircraft's article on this wiki]]. In general to start the engine on a jet engine type aircraft, you need to:
# Set cutoff ''ON''
# Engage the starter
# Once the engines spools up to approximately 5% N1, set cutoff ''OFF''
# Disengage the starter once the engine has reached operational speed

== Learning to fly ==
=== FlightGear's Manual ===
FlightGear has an official [https://www.flightgear.org/support/manual/ manual] that covers the basics of flight. As a beginner, you may want to start with "Chapter 8: A Basic Flight Simulator Tutorial."

=== Tutorials ===
Many aircraft have their own interactive [[tutorials|tutorial]]. With tutorials, you can learn to operate particular aircraft but also learn to fly. You can access tutorials by going to ''Main menu'' > ''Help'' > ''Tutorial''. A great place to start is the tutorial for the [[Cessna 172P]] aircraft, commonly used in real life to learn to fly fixed-winged aircraft.

If the tutorial starts without a runway and surrounded by water, your setup of FlightGear is missing the scenery for the airport at which the tutorial was supposed to run. To get scenery see the [[#Getting scenery]] section above.

== Making your first flight ==
=== Realism ===
One of the most frequent questions novice pilots ask about any flight simulator, but more so to FlightGear, is "Why is my aircraft turning left all the time?" Although it could be due to wind gusts crossing the runway, it is more likely due to the [[Understanding Propeller Torque and P-Factor|propeller torque and p-factor]].

In certain other flight simulators, despite marketing slogans to the contrary, some settings are turned down to make the aircraft easier to fly. This reduces effects such as the above. The realism is always turned up in FlightGear.

Here are some of the FlightGear realism points, which may be confusing to first time pilots:
* "Left turning syndrome" for the previously mentioned reasons.
* Compass turning error: A compass, when subjected to the forces of flight, tends to turn in the opposite direction for a brief period before settling on the correct heading. This is not a malfunction (see also the Wikipedia article {{wikipedia|Aircraft compass turns}}).
* The Vertical Speed Indicator (VSI) is also subject to error.
* The [[Horizontal Situation Indicator]] (HSI) is driven by a gyroscope (that is why it is sometimes called a Directional Gyroscope), which is subject to ''gyro drift''. The indicator will drift from its current heading and must be periodically (every ~15 minutes) calibrated to agree with the magnetic compass heading.
* You cannot just cancel a turn or climb by centering the yoke or stick. You must turn or push the stick the other way to get to level and level flight. But even then, the plane will not maintain its altitude or heading by itself. A common mistake is trying to find a hands off yoke position. While with trimming one could leave the plane for a couple of seconds, one must use autopilot or constantly adjust the yoke.

Many forces act on an aircraft in flight as well as on the [[avionics and instruments]] used for control and navigation, and may be counter-intuitive. Pilots must learn to recognize these phenomena and compensate for their effects. ''FlightGear models instrument errors that exist in the real world''.

=== Airports and navigation aids ===
When you first start FlightGear, whether from the command line or the graphical interface of the launchers, you may wonder how to determine what airports are available. The launcher displays a list of airports, but you will not see details such as tower or [[ILS]] frequencies. You will not find a map showing [[VOR]]s and their frequencies. What can you do? See [[Getting aeronautical charts]].

In-sim, there is a map you can use in ''Main Menu'' > ''Equipment'' > ''Map'', which will allow you to see navigation data and the position of airports and aids. For more help with navigation see [[Understanding navigation]].

=== Flying using the autopilot ===
Some aircraft require you to use the [[autopilot]] available from the ''Autopilot'' menu, which is the original FlightGear autopilot. This is a ''generic'' autopilot and as such, many aircraft come with their own ''specific'' autopilot, frequently a model of the real life one.

For aircraft that provide their own autopilot, you should use the autopilot controls available in the virtual cockpit. This means clicking on the instrument panel in the virtual cockpit. The Autopilot menu will be grayed out and unavailable when the aircraft supplies its own autopilot in some aircraft, including the Airbuses and the [[Cessna 172P|C172P]].

The Cessna 172 comes with a [[Bendix/King KAP140 Autopilot]] in its virtual cockpit. You can use both the autopilot device in the cockpit and the [[Autopilot#Autopilot Settings|autopilot settings]] from the menu.

== Advanced ==
=== Flying ===
{{Main article|Aircraft}}

* If you continue to fly light civilian aircraft, [[Cessna 182S]] which is more complex than C172P and [[Piper PA28 Warrior II|PA28]] are good choices.
* If you are interested in flying airlines, [[Airbus A320 family]], Boeing [[Boeing 777|777]]/[[Boeing 787-8 Dreamliner|787]], [[MD-11]] and [[MD-80]] are suggested.
* If you are fascinated by fighter aircrafts, choose a highly rated military aircraft (such as [[General Dynamics F-16 Fighting Falcon|F-16]]/[[F-15]]) from [[Aircraft#Modern military aircraft|here]], and enable multiplayer damage or install [[Bombable]].
* If you switch to helicopters, it is recommended to fly [[Eurocopter EC130 B4]].

Besides common aircraft, there are also detailed [[Space Shuttle|space shuttles]] available.

=== Scenery ===
It is fascinating to explore the [[scenery]] (or just test the graphics/frame rate) with [[UFO]]. First of all, [[#Configuring rendering and UI|increase your graphics quality]]. If you don't see buildings initially, keep FG open and wait for a while for [[TerraSync]] to finish downloading and for the buildings to appear.
There are plenty of [[Suggested airports|well-developed airports]] and scenery areas. You can also explore the scenery objects on the [https://scenery.flightgear.org/map model map].

=== Multiplayer ===
FlightGear has some multiplayer servers that will let you fly in more lively skies, see [[Howto: Multiplayer]]. There are also [[OpenRadar]] and [[ATC-pie]], standalone programs that will let you be an [[Air traffic control|air traffic controller]].

There is also a [[MPMap|multiplayer map]] that lets you see who is online right now, and even what [[navaids]] are nearby.

=== Menu items ===
For a quick reference about the usage of each menu item in FlightGear, see [[menu]].

=== Addons ===
FlightGear has a lot of third-party [[Addon|addons]] containing enhancements. For beginners, [[Logbook Add-on|Logbook]] and [[Which Runway Add-on|Which Runway]] may be the most useful addons.

== The FlightGear community ==
=== Getting help ===
This page is designed to give the user the essential things they need to know about using FlightGear for the first time. Besides the [[Portal:User|User portal]] of this wiki, there are other pages you may want to read:
*[[Troubleshooting problems]] to help you with the most common issues;
*[[Frequently asked questions]];
...and communication channels that can be used to obtain information or request help:
*The [[FlightGear Manual]], a ''must read'' for beginners;
*{{forum link|text=FlightGear Forum}} and its subforums;
*[[Discord|FlightGear's Discord server]], the quickest way to get help;
*[[FlightGear IRC channel]];
*[[Mailing list|FlightGear users mailing list]], biggest chance to get in contact with core developers;
*Documents bundled with the release package.

=== Customizing FlightGear without compiling it ===
[https://www.flightgear.org/download/ Our website] offers precompiled binaries for download and install on Windows, macOS and Linux. In addition, most Linux distributions provide a packaged version in their repositories.

Although the install is binary, most of FlightGear's systems are open to configuration through [[XML]] files and [[NASAL scripting]]. You are free ''and encouraged'' to make changes to aircraft flight models, scenery, textures, OpenGL [[shader]]s and any other feature you wish to change for your personal satisfaction or to share with other FlightGear users. If this is what you intend to do, take a look at the [[Portal:Developer|Developer portal]].

=== How you can help ===
{{Main article|Volunteer}}
FlightGear is an open source, volunteer based project. That means that whatever you find here comes from passion, spare time and nothing else. This includes the simulator, the scenery, the aircraft, the wiki, the {{forum link|text=forum}} and everything else. Volunteers, in essence ''people that do things'', are fundamental to this project. Without them, it would not make a single step forward. So it is essential that contributors have fun in what they do.

If you plan to contribute to this project, you should take a look at some articles that will give you some hints:
*[[Howto:Understand the FlightGear development process]]
*[[Implementing new features for FlightGear]]
*[[How the FlightGear project works]]

There are never enough people contributing, and the fields where their help would be appreciated are many:
;Testing:
*[[Building FlightGear|Build]] the latest Git code
*[https://gitlab.com/flightgear/flightgear/-/issues File bug reports]
*Running FlightGear via valgrind to track down memory leaks

;Support:
*Help new users with downloading, compiling, installing and running FlightGear ({{forum link|text=on the forum}} or on [[Discord]])
*Provide ideas & suggestions, see: [[Feature Requests / Proposals / Ideas]]
*Help [[Portal:Wiki|clean up this wiki]]
*Help provide new contents for missing wiki pages

;Development:
*C/C++ Coding:
**Provide source code cleanups
**Provide bug fixes [[Bugs]] or new features
**Get involved in any of the other FlightGear-affiliated projects
*Aircraft development (3D modeling, textures, FDMs, scripting)
*Scenery development (terrain, model, weather)

[[Category:FlightGear]]

[[ca:Nou a FlightGear]]
[[de:Neu bei FlightGear]]
[[es:Nuevo en FlightGear]]
[[fi:Uusi_käyttäjä]]
[[fr:Nouveau sur flightgear]]
[[it:Nuovo per FlightGear]]
[[ja:FlightGear入門]]
[[nl:Nieuw bij FlightGear]]
[[pl:Nowy w FlightGear]]
[[pt:Novo no FlightGear]]
[[sr:Novi u FlightGear-u]]
[[th:New to FlightGear]]

General Dynamics F-16 Fighting Falcon/info

2026-05-20T19:45:11Z

Fgf5: repository

<includeonly>{{infobox aircraft
| name = General Dynamics F-16 Fighting Falcon
| hangar = fgaddon
| aircraft = f16
| image = F16CJ50 WildWeasel.png
| image2 = F-16C Cockpit.png
| alt2 = {{LangSwitch
| en = F-16CG Cockpit view
| de = F-16CG cockpit aussicht
}}
| type = Military aircraft/Fighter aircraft/Attack aircraft
| config = Retractable gear aircraft
| propulsion = Single-engine jet
| manufacturer = General Dynamics/Lockheed
| authors = Erik Hofman/Martin "Pegasus" Schmitt/Pensacola/Nikolai V. Chr./J Maverick 16/Richard Harrison/Josh Davidson/Martien Van Der Plas/Jonathan Redpath/Gary Brown/Justin Nicholson/Enrico Castaldi/Timi/Barszczisbad/PH-JAKE/Baptiste Campion/LJQCN101
| fdm = JSBSim
| fgname1 = f16-block-10
| fgname2 = f16-block-20
| fgname3 = f16-block-30
| fgname4 = f16-block-32
| fgname5 = f16-block-40
| fgname6 = f16-block-42
| fgname7 = f16-block-50
| fgname8 = f16-block-52
| fgname9 = f16-block-60
| fgname10 = f16-simplified
| fgname11 = YF-16
| status-fdm = 5
| status-systems = 4
| status-cockpit = 4
| status-model = 4
| ready = airrefuel/canvas/checklist
| liverydbid = 20
| license = GPLv2+
| forumtid = 2003
| manual = https://github.com/NikolaiVChr/f16/wiki
| devel-repo = https://github.com/NikolaiVChr/f16
| navbar = 1
}}
</includeonly><noinclude>
This is the aircraft infobox subpage of the [[General Dynamics F-16 Fighting Falcon]].
[[Category:Aircraft infobox documentation]]
</noinclude>

General Dynamics F-16 Fighting Falcon

2026-05-20T19:41:49Z

Fgf5: multiplayer damage and tutorial

{{:{{PAGENAME}}/info}}
The '''General Dynamics F-16 Fighting Falcon''' (nicknamed Viper by pilots) is a single-engine supersonic multirole fighter aircraft by General Dynamics, exported to many countries. Designed as an air superiority day fighter for the US Air Force, it evolved into a successful all-weather multirole aircraft.
The Fighting Falcon has key features including a frameless bubble canopy for better visibility, side-mounted control stick to ease control while maneuvering, a seat reclined 30 degrees to reduce the effect of g-forces on the pilot, and the first use of a relaxed static stability/fly-by-wire flight control system which helps to make it a nimble aircraft.

== Keyboard Controls ==
====Flight Controls====
{| class="keytable"
! Key
! Function
|-
|{{Key press|Ctrl|B}}
|Toggles speed brake
|-
|{{Key press|Delete}}
|Toggles FBW (fly by wire) override (F-16 Simplified)
|-
|{{Key press|Delete}}
|Toggles MPO
|}

====Radar====
{| class="keytable"
! Key
! Function
|-
|{{Key press|Shift|E}}
|Decreases radar range
|-
|{{Key press|Shift|R}}
|Increases radar range
|-
|{{Key press|R}}
|Toggles radar standby mode
|-
|{{Key press|Y}}
|Toggles next target
|-
|}

====Tactical====
{| class="keytable"
! Key
! Function
|-
|{{Key press|E}}
|Fires the cannon
|-
| {{Key press|Q}}
| Chaff/flare
|-
| {{Key press|M}}
| Master arm
|-
| {{Key press|W}}
| Cycle weapon
|}
====Miscellaneous====
{| class="keytable"
! Key
! Function
|-
|{{Key press|Ctrl|H}}
|Toggles arrester hook
|-
|{{Key press|Shift|C}}
|Toggles canopy
|-
| {{Key press|Q}}
| Reset cockpit view
|-
| {{Key press|Ctrl|Q}}
| View right MFD
|-
| {{Key press|Shift|W}}
| View left MFD and RWR
|-
|{{Key press|F}}
| Toggles refuel door
|-
| {{Key press|Shift|S}}
| Toggle smoke
|-
| {{Key press|U}}
| Seat up
|-
| {{Key press|Shift|U}}
| Seat down
|}

== Features ==
=== Canvas HUD ===
[[File:Canvasready.png|left|caption|link=Howto:Aerial refueling]] The F-16 has a canvas {{wikipedia|Head-Up Display}}. 

=== Air-to-air refueling ===
[[File:Airrefuelingready.png|left|caption|link=Howto:Aerial refueling]]
The General Dynamics F-16 Fighting Falcon supports ''in-flight refueling''. You need to start a specific scenario or do that in multiplayer to get a tanker [[aircraft]]. See [[Howto:Aerial refueling]] for more information. Also look on the box at the [[{{PAGENAME}}#External link|bottom]] of the page. 

=== Aircraft carrier ===
Although the Viper wasn't designed for maritime operations, there is the possibility to start from and land on a [[Aircraft carrier|carrier]]. You can toggle the '''arrester hook''' with {{Key press|Ctrl|H}}. There are several [[Aircraft carrier]] available. How to set it up start your aircraft there is described in [[Howto:Carrier]]. If you fly in multiplayer mode see [[Carrier over MP]].

=== Multiplayer damage ===
F-16 supports the multiplayer damage system, which is different from [[Bombable]]. Click "F-16 > Configuration" on the menu to enable it.

== Tutorials ==
There is an official manual, '''[https://github.com/NikolaiVChr/f16/wiki github.com/NikolaiVChr/f16/wiki]'''.

[[File:F16-cockpit-pano.jpg|480px|thumb|right|[[Howto: Make full spherical panorama|A full spherical panorama]] of the f-16 cockpit]]

=== Videos ===

{{#ev:youtube|iSkxDhy8-zk}}

{{#ev:youtube|uN6pddgHaog}}

{{#ev:youtube|AjTw77d_lzo}}

{{#ev:youtube|Dd1Ddqr8-A0}}

== Development Status ==
{{Main article|F16/Development}}
[[File:F-16 AV029.JPG|thumb|400px|'''F-16''' taxiing to parking at [[LIPA]] after landing on rwy 05 with home livery]] [[File:F-16 RNLAF J015-demo 3.png|thumb|400px|The RNLAF J015-demo livery of the F-16]]

== External link ==
* [https://github.com/NikolaiVChr/f16/wiki Flightgear F-16 Manual]
* [http://brenthugh.com/flightgear/Sun_Valley_Tank_Invasion1.zip Several ground bombing scenarios suitable for the F-16, involving moving and static tank formations, explodable M1 Abrams tanks, etc.]
* [https://info.publicintelligence.net/USAF-F16.pdf F-16 A/B Flight manual] ([http://web.archive.org/web/20220407051211/http://info.publicintelligence.net/USAF-F16.pdf backup])
* [https://info.publicintelligence.net/HAF-F16.pdf F-16 C/D Flight manual] ([http://web.archive.org/web/20220406200504/https://info.publicintelligence.net/HAF-F16.pdf backup]), [https://info.publicintelligence.net/HAF-F16-Supplement.pdf supplement] ([http://web.archive.org/web/20211026112336/https://info.publicintelligence.net/HAF-F16-Supplement.pdf backup]), [https://info.publicintelligence.net/HAF-F16-FlightChecklist.pdf checklists] ([http://web.archive.org/web/20211108090746/https://info.publicintelligence.net/HAF-F16-FlightChecklist.pdf backup])

[[Category:Military aircraft]]

{{Lockheed}}
{{air-to-air refueling}}

[[Category:Fighter aircraft]]
[[de:General Dynamics F-16 Fighting Falcon]]
[[fr:General Dynamics F-16]]

Follow me e-tron

2026-05-19T13:24:12Z

Fgf5: /* Installation */

{{:{{PAGENAME}}/info}}
The '''Follow me e-tron''' or '''Follow me EV''' is a semi-fictional Follow-me vehicle based on [[Follow_me|Gijs's work]], but an electric-powered version with Chinese characteristics. It was made initially just for fun.

The vehicle implements a detailed electric powertrain and electrical system in Nasal, along with key features including an advanced steering helper and systems such as 'AutoCrash' and 'AutoSpeed' for driving assistance. Additional functionalities encompass an Auto Hold feature, parking radar, working airbags, and an experimental Advanced Emergency Braking (AEB) system.

The model offers multiple interior configurations with functional controls and different instrument panel options, including a Canvas-based glass display. Customization options extend to Chinese-style license plates and various livery choices. A stretched limousine variant is also available.

The vehicle is fully equipped for multiplayer with multiplayer passengers supported. It also has a dynamic scenery object placement system, allowing vehicles-related objects such as highway tollgates and recharging stations to be placed on the scenery for more immersive driving.

== Features ==
Being the '''very first electric car''' in FlightGear, the Follow me e-tron features a realistic electric supercar driving experience while having an exterior of the classic Renault Kangoo I Follow me vehicle.

[[File:FollowmeEV广州.png|center|700px|Screenshot of the FollowmeEV in Guangzhou]]

* Realistic electric engine written in Nasal.
* Detailed electrical system written in Nasal.
* Advanced steering helper (experimental)
* 'AutoCrash' system, which tries its best to keep you on the road.
* 'AutoSpeed' system, which keeps your speed constant.
* Auto Hold function
* Parking radar that detects terrain and alerts driver.
* Working airbags.
* Experimental AEB system.
* Configurable interior with several fully remodeled interior and working switches.
* Configurable instruments with several styles to choose from.
* Canvas glass display instrument for certain interior styles
* Compositor light support.
* Selectable license plate in Chinese style.
* Various of liveries
* Various of messages
* Full multiplayer support.
* Multiplayer passenger.
* Dynamic scenery object placement and management
* Limo variant
* Tutorials support in different languages
* Different interior styles to choose from.
* Save / Resume function.

== Installation ==
{{main article|Howto:Install aircraft#Manual installation process}}
Follow me e-tron is not in the official hangar and you have to install it manually. You can download the zip file from the [https://github.com/sidi762/followme_e-tron/releases/latest latest release], unpack it and add the aircraft path to the launcher. For the installation instructions, see [[Howto:Install aircraft#Manual installation process|here]].

== Videos ==
{{#ev:youtube|p-P6SkRu6PE}}
{{#ev:youtube|pq6Lb5GA3Bc}}
{{#ev:youtube|MGZU85t5LCo}}

== Version ==
The Follow me EV is currently released as v5.2.

=== Change Log ===
V5.2 Updates:

* The advanced steering received a major update and renamed to realistic steering, adapted the Pacejka tire model into the calculation which should provide more realism.

* Various bug fixes and optimization.

* Improved aircraft help and documentation.

* Added drifting sound.

* New splash screen images.

* New preview image.

V5.1 Updates:

* Major improvements to the reset function
* Bug fixes and improvements

V5.0 Updates:

* Added an option to adjust brake intensity for keyboard control
* Further tuned engine and fixed the bug related to gear changing
* New liveries: Blackwhite, C919 Memorial
* Interior updates
* New magic bush tyre option for driving on killer grass
* New interior: 404Design 2.0, 404Design 2022 and Luxury 2.0
* New charging pile
* Exterior model improvements, especially on charging cap, wheels and doors
* Added rear plate with multiplayer support
* Improvements on sounds
* Added option to re-enable ALS procedural lights
* Default interior switched to 404Design
* Added door warnings for smart instruments
* General improvements, cleanups and bug fixes

V4.0 New Features:

* Added a limo varient
* New texture selector which works better under multiplayer
* New interior style: Race, 404Design
* New canvas glass display instrument for 404Design Interior
* New dynamic scenery object system
* New models for service station, toll gates, etc
* Added reverse indicator light

Updates and improvements:

* Major updates to the UV
* Major update to the Engine & electrical systems, (much) more realistic performance
* FDM improvements
* AEB improvements
* Minor texture and exterior/interior model updates
* Sounds updates
* Added multiplayer model detection support to radar(and AEB which relies on the radar)
* Many bug fixes

Changes after v4.0 alpha:

* Added battery remaining display
* Improvements to Nasal performance
* Huge bug fixes to the electrical system
* Many minor bug fixes
* Added option to adjust steering

Changes after v4.0 beta.1:

* Added error message to the smart instruments after the battery is drained
* Bug fixes

Changes after v4.0 beta.2:

* Bug fixes

V3.0 New Features:

* Configurable interior with several fully remodeled interior and working switches
* Functioning Airbags
* Experimental AEB system
* Experimental compositor light support
* Auto Hold function
* Save / Resume
* New tutorials

Improvements:

* Electrical system
* Brake system
* Sounds
* Effects
* Several bugs fixed

V2.0:

Updated features:

* Updated interior
* Exterior improvements
* Autospeed system
* New experimental steering system
* Parking radar system
* Sound improvements
* FDM improvements
* Liveries updates
* Tons of bug fixes

V1.0:

Initial Release

== Statistics ==
''Note: The figures below was measured before the v4.0 release. The entire engine received an update in the v4.0 release and the performance is now way more realistic.''

Top speed:
≤300kts/555.6km/h
=== Acceleration ===
Accelerate up to:
100km/h: 2.48 seconds
200km/h: 7.20 seconds
=== Battery ===
Electricity usage:
---km/charge (Yet to be determined)

== Gallery ==

=== Newer Versions ===
<gallery mode="packed">
File:Followme EV interior preview 2.jpg|Followme EV Interior
File:Followme EV in ZBNY.jpg|Followme EV inside ZBNY
File:Followme EV interior preview.jpg|Followme EV Interior
File:Followme EV.png|Three Followme EVs lining up
File:Followme EV in a charging station.png|Followme EVs in a charging station, showcasing the dynamic scenery object system
File:Followme EV in front of a toll station, at the endpoint of G1 National Highway.png|Followme EV in front of the Wapenyao toll station, at the endpoint of G1 National Highway
File:Followme EV in a service station.png|Followme EV inside a service station
File:Followme EV on the G318 Sichuan-Tibet Route.png|Followme EV on the famous G318 Sichuan-Tibet Route
File:Followme EV in a valley.png|Followme EV in a valley on the G318 Sichuan-Tibet Route
File:Followme EV recharging alongside the G318 Sichuan-Tibet Route.png|Followme EV recharging alongside the G318 Sichuan-Tibet Route
</gallery>

=== Earlier Versions ===
<gallery mode="packed">
Followme EV historical screenshot.png|Screenshot of early versions of the Followme EV
Followme EV historical screenshot2.png|Screenshot of early versions of the Followme EV
Followme EV historical screenshot3.png|Screenshot of early versions of the Followme EV
Followme EV historical screenshot4.png|Screenshot of early versions of the Followme EV
Followme EV historical screenshot5.png|Screenshot of early versions of the Followme EV
Followme EV historical screenshot6.png|Screenshot of early versions of the Followme EV
FollowmeEV广州.png|Screenshot of the FollowmeEV in Guangzhou
FollowmeEV武汉2.png|Screenshot of the FollowmeEV in Wuhan
FollowmeEV武汉3.png|Screenshot of the FollowmeEV in Wuhan
FollowmeEV武汉4.png|Screenshot of the FollowmeEV in Wuhan
</gallery>

== Related content ==
=== Forum topic ===
* {{forum link|title=Grand Tour with Follow me: From Beijing to Shenzhen|t=36211}}
* [[FlightGear China]]
* [http://www.fgprc.org FGPRC homepage]

FlightGear

2026-05-18T23:33:16Z

Fgf5: /* Aircraft */

{{Infobox Software
|title = FlightGear Flight Simulator
|logo = FlightGear logo.png
|logosize = 200px
|image = Boeing 777-200ER cockpit.jpg
|alt = The cockpit of the [[Boeing 777-200ER]]
|developedby = FlightGear developers & contributors
|initialrelease = July 17, 1997
|latestrelease = {{current release|full}} ({{#time: j F Y |{{current release|fulldate}}}})
|writtenin = C/C++/Nasal
|os = Windows, macOS, Linux, and FreeBSD
|platform = Cross-platform
|developmentstatus = Active (1996-present)
|type = Flight simulator
|license = [[GNU General Public License]]
|website = http://www.flightgear.org/
}}
[[File:OV10A-NASA-in-action.jpg|thumb|right|270px|NASA [[OV-10]] in FlightGear 1.0]]
'''FlightGear Flight Simulator''' (often shortened to '''FlightGear''' or '''FGFS''') is a sophisticated, free, and completely open-source flight simulator framework, created by volunteers. FlightGear is released under the terms of the [[GNU General Public License]]. FlightGear is mostly written in the C and C++ programming languages.

Increasingly detailed and realistic versions of FlightGear have been released every year since the project was started in 1996.

The latest public release is [https://www.flightgear.org/download available as a free download], with easy to install packages for a variety of operating systems including Microsoft Windows, macOS, and Linux.

== History ==
{{main article|FlightGear History}}

FlightGear development started with an online proposal in 1996, using custom 3D graphics code. Development of an [[OpenGL]] based version was spearheaded by Curtis Olson starting in 1997. Many people have contributed to the project in the years since its inception.

FlightGear incorporated other open-source resources, including the [[LaRCsim]] flight model from NASA, and freely available elevation data. The first working binaries, using OpenGL for 3D graphic code, came out in 1997. Enthusiastic development of newer versions for several years resulted in progressively more stable and advanced versions. By 2001, the team was releasing new beta versions regularly, and by 2005, the maturity of software lead to more widespread reviews, and increased popularity. 2007 marked a formal transition out of beta development with the release of version 1.0.0, ten years after FlightGear's first release in 1997.

[[File:FG-A-10.jpg|thumb|270px|3D Cockpit panel for [[A-10]] in version 1.0.0 in 2008]]

In 2008, version 1.9.0 of FlightGear included a major change from [[PLIB]] to [[OSG]], which caused the temporarily loss of some features like 3D clouds and shadows, while newly added features, such as particles, imparted another degree of realism to the simulation.

== Software ==

The simulation engine in FlightGear is called [[SimGear]]. It is used both as an end-user application and in academic and research environments, for the development and pursuit of flight simulation ideas.

This customizability of FlightGear is illustrated by the wide range of aircraft models that are available in FlightGear, from [[:Category:Gliders|glider]]s to [[Helicopter]]s, and from [[:Category:Airliners|airliners]] to [[Military aircraft|fighter jets]]. These aircraft models have been contributed by many different people.

The FlightGear aircraft in general use one of two main flight data models [[JSBSim]] and [[YAsim]]. Currently only one terrain engine is used, TerraGear. Weather effects include 3D clouds, lighting effects, and time of day.

=== Flight Dynamics Models ===
[[Flight Dynamics Models]] (FDM) are how the flight for an aircraft is simulated in the program. FlightGear uses a variety of internally written and imported flight model projects. Any aircraft must be programmed to use one of these models. Currently FlightGear is the only flight graphical flight simulator all the FDM are used for, and UIUC and YASim were developed specifically for FlightGear.

Early version used a FDM based on [[LaRCsim]] by NASA, which was replaced with more flexible FDM.

* [[JSBSim]] - the default flight dynamics model software since 2000.
* [[YASim]] - another FDM using different calculation method. Introduced starting in 0.7.9 in 2002.
* [[UIUC]] - developed by the UIUC Applied Aerodynamics Group at University of Illinois at Urbana-Champaign, also made use of LaRCsim. Once being widely used, it is no longer included in FlightGear.
* FlightGear can also be setup to render using inputs from an external FDM source, such as from [[MATLAB]].
* Other custom FDM for a specific aircraft type have been written, such as for lighter than air aircraft.

=== Aircraft ===
{{Main article|aircraft}}

FlightGear started out with one aircraft included in NASA's LaRCsim, a Navion, which was replaced by a [[Cessna 172]] by 2000. UIUC as well as JSBsim development brought several more aircraft with them, as did the development of YASim which have since become the main FDM used in FG. Over 400 aircraft in more than 900 unique liveries, are available for version 2.12, although only a few are included in the base package.

[[File:EHAM.jpg|thumb|270px|[[Boeing 737-300|Boeing 737]] docked in the [[EHAM]] scenery]]

=== Scenery ===
{{Main article|Scenery}}
FlightGear's [[world scenery]] project contains elevation and landclass data of the entire world. Objects -like terminals, windmills and bridges- are collected in the [[FlightGear Scenery Database|Scenery Database]].

=== Networking and multi-display ===
Several networking options allow FlightGear to communicate with other instances of FlightGear. A [[Howto:Multiplayer|multiplayer]] protocol is available for using FlightGear on a local network in a multi aircraft environment. This could be used for formation flight or [[ATC|control tower]] simulation. Multiplayer was soon expanded to allow playing over the internet. Other features include a Google maps based moving up that allows users to observe where other players are.

Several instances of FlightGear can be synchronized to allow for a multi-monitor environment. If all instances are running at the same frame rate consistently, it is possible to get good and tight synchronization between displays.

==Applications and usages==
{{Main article|Professional and educational FlightGear users}}
FlightGear has been used and is being used in a wide range of projects in academia, industry (including NASA) and home-built cockpits.

== External links ==
{{Main article|Links}}
* [https://www.flightgear.org Official website]
* {{forum link|text=Forum}}
* {{tickets|Bug tracker}}
* [https://www.flightgear.org/blog/proposal-1-0/ Original FlightGear proposal]
* {{Wikipedia|FlightGear}}

[[Category:FlightGear]]

[[ca:FlightGear]]
[[de:FlightGear]]
[[es:FlightGear]]
[[fr:FlightGear]]
[[it:FlightGear]]
[[nl:FlightGear]]
[[pl:FlightGear]]
[[pt:FlightGear]]
[[pt-br:FlightGear]]
[[ru:FlightGear]]

New to FlightGear

2026-05-18T22:39:48Z

Fgf5: /* Advanced */ which runway addon and space shuttle

'''Welcome to [[FlightGear]]!''' Here we will try to get you up in the virtual air in the shortest time possible. We will also introduce you to some of the features of this flight simulator and also a few information on its community.

== Installation and setup ==
=== Hardware requirements ===
For FlightGear to run smoothly, it requires a video card with OpenGL drivers 4.0 or higher. This is usually not a problem, but take a look at the [[hardware recommendations]] to have a better idea.

=== Getting FlightGear ===
You may download the latest files from the [https://www.flightgear.org/download/ FlightGear download] page. Choose the source or binary files appropriate for your particular system. {{Wikipedia|AppImage|AppImage}} binary files for Linux are also available with 2020.3 LTS and later. Most Linux users will find that most distributions have a packaged version of FlightGear (the package name could be <code>fgfs</code> or <code>flightgear</code>.)

Depending on your technical expertise you may choose the [[Git]] development version of FlightGear, which typically has more features and can be required by some of the latest developmental aircraft, but can be unstable and is more complicated to get for non-Windows users. In general, the development version is not advised to the average user, but if you are willing to do some testing there is a nightly build available for [https://www.flightgear.org/download/nightly/ download]. If you are using a Git version controlled copy of FlightGear, you may choose to synchronise your aircraft using the version controlled [[FGAddon|FGAddon aircraft development repository]].

=== Installing on Windows ===
After you downloaded the installer, run it and follow its instructions to install FlightGear.

Defender SmartScreen on Windows may block the installation simply because the binary file is not signed with a key that Microsoft respects. Of course, the key is paid. In this case, we need to click on the inconspicuous "More info" link. Only then will the "Run anyway" button appear. You can safely trust that this is not a dangerous application, as long as you have actually downloaded it from official sources.

If you're using third-party antivirus software for some reason, it may be blocking FlightGear from installing. This isn't something we can control, so it's entirely up to you how you want to handle it.

With the Windows installer, you may choose where to install FlightGear. The [[$FG_ROOT]] directory would be <code><your chosen directory>/data</code>.

=== Installing on macOS ===
Installing FlightGear on macOS is very simple. Just drag and drop the FlightGear icon to the <code>/Applications</code> folder. That is it.

The first time you launch FlightGear, its icon on the Dock bounces for several seconds while loading aircraft and airport info. When the GUI launcher appears, select the aircraft and airport, then click "Fly!" to launch the simulator. You can configure more options using the GUI launcher. See the [http://flightgear.sourceforge.net/manual/next/en/getstart-ench4.html#takeoff-how-to-start-the-program official manual] for more details.

If you would like to launch FlightGear using command-line, launch <code>/Applications/Utilities/Terminal.app</code> and type the following.

cd /Applications/FlightGear.app/Contents/MacOS
./fgfs --options.....

The [[$FG ROOT]] and [[$FG SCENERY]] are not set on macOS. If you want to specify these variables yourself for command-line use, run the followings on Terminal.app:

FG_ROOT=/Applications/FlightGear.app/Contents/Resources/data
FG_SCENERY=[[$FG_ROOT]]/Scenery

After launching the GUI launcher, you will have the alias to [[$FG_ROOT]] at <code>$HOME/Documents/Flightgear/<version></code> so you can browse the data folder using Finder.

Note: Once you have installed FlightGear, Mac users can locate their [[$FG_ROOT]] folder by opening their applications folder in Finder, right clicking on FlightGear, and clicking "Show Package Contents". This will take you inside the FlightGear folder. You are now able to access all files including Data/Aircraft to [[Howto: Install aircraft#Macintosh OS X|install new aircraft]].

=== Installing from source ===
Main article: [[Building FlightGear]]

=== Getting scenery ===
A limited set of [[scenery]] comes installed with FlightGear. For FlightGear 2024.1 this consists of
* The area surrounding the featured airport for the release which is [[Keflavik_Airport|Keflavik International Airport]] (BIKF)
* The tutorial airport for the [[Cessna_172P|Cessna 172P]] which is [[Hilo_International_Airport|Hilo International Airport]] (PHTO)

In FlightGear, scenery is generally stored in you [[$FG ROOT]] directory, and is divided into three kinds of data:
* '''Airports''' holds airport data, like runway usage and parking spots.
* '''Objects''' and '''Models''' are the buildings, bridges and radio towers, etc. that represent three-dimensional structures.
* '''Terrain''' represents the contours, elevations and type of ground you fly/taxi over.

The current way of "installing" new scenery is enabling [[TerraSync]], which will automatically download and update any place you visit - even on the fly! If you have a slow Internet connection and/or computer you could instead use a scenery manager, for example [[TerraMaster]]. In addition you can also manually download and install new scenery parts, either the official [[World Scenery]] or custom scenery.

The official, although outdated, scenery is available at [http://www.flightgear.org/download/scenery/ the scenery download section] of the FlightGear website, and can be installed following [[Howto: Install scenery]]. You may obtain additional and more up to date scenery objects as they become available through the [http://scenemodels.flightgear.org/ FlightGear Scenery Database]. '''This is recommended for users with weak internet connections or weak computers!'''

Custom scenery is available in many places. For example, on the {{forum link|f=5|text=FlightGear forum}} or within repositories. An internet search should be able to find them. See [[Suggested_custom_scenery|suggested custom scenery]] page for a few recent releases.

FlightGear 2020.3.7 LTS and later added an experimental rollout of 3 dimensional buildings, roads, and objects based on OpenStreetMap data for the entire world to automatically downloaded TerraSync data - see [[OSM2City 1st Worldbuild|1st OSM2City world-build]] notes (March 2021). Some manual downloads of 3d structures for regions or entire countries is available on the [[Areas populated with osm2city scenery|osm2City downloads]] wiki page.

=== Getting aircraft ===
Additional [[aircraft]] can be downloaded and installed through the [[Qt-launcher|launcher]]. Alternatively, you can go to the FlightGear website and navigate to the [http://www.flightgear.org/download/ download page], then choose the aircraft download link that fits your FlightGear version. In addition there are many third party [[hangars]]. For the installation, see [[Howto: Install aircraft]].

== Running FlightGear ==
=== Starting FlightGear ===
The easiest way to start FlightGear is to use the desktop icon. This starts the graphical interface [[FlightGear Qt launcher]] where you can choose aircraft, start position etc. Remember the Qt launcher only has basic options to get you started. A lot of options for graphics, scenery, [[Weather|weather]], [https://www.flightgear.org/tours/simulating-the-ever-changing-scenery/ environment], [[Input_device|input devices]] etc. are available from the [[menu]] inside the simulator.

Many users choose however to start FlightGear directly from the command line. The executable name is <code>fgfs</code> and can be run without options. If it is "not found", it is likely not in your [https://en.wikipedia.org/wiki/PATH_(variable) path]. The location depends on your particular system and choices you made during compile and installation. There is a list of [[Command Line Parameters]] which must be used to change many options, like the aircraft you want. The most important:

fgfs --launcher # opens the FlightGear Qt launcher
fgfs --show-aircraft # displays a list of installed aircraft
fgfs --aircraft=c172p # start FG with the aircraft "c172p" (from the list)

The Qt launcher also lets users add command line parameters for options that are normally changed from the menu inside the simulator, as well as quite advanced options that are only available from the command line (as of August 2020).

=== Configuring rendering and UI ===
[[File:Rendering options 2024.1.png|thumb|View > Rendering Options dialog.]]
If your render quality or framerate is too low, click "View > Rendering Options" to adjust the graphic settings. For newer hardware, it's recommended to set "graphics quality" to high and check "use disk space for faster loading", "animated jetways" and "satellite photoscenery".

If the menu text appears too small on high DPI or large screens, you can manually [[Menubar#How to Change the Default Menubar Font Size|change the menubar font size]] by editing the data file, or simply click "Debug > Cycle GUI Style".

=== Using the keyboard and/or mouse ===
Users with limited access to a [[joystick]] or other controllers sometimes use the keyboard or mouse to control their aircraft. Using the keyboard to fly can be difficult and the mouse is recommended over the keyboard for flying, yet even a cheap joystick would improve the experience so much.

To get help with keyboard commands, with FlightGear running, go to the ''Help'' menu, look under ''Basic Keys'' (for simulator related commands) and ''Common Aircraft Keys'' (for commands universal to all aircraft) and ''Aircraft Help'' (for key commands specific to your aircraft). If the main menu is hidden press {{key press|F10}}. If you come from other simulators, check [[key commands compared to other simulators]] for an overview of the difference between the key commands of that sim and FlightGear.

To use the mouse to fly the aircraft, press {{key press|Tab}} (the cursor should change to a cross) and move the mouse to direct the aircraft. Press {{key press|Tab}} again to look around (cursor should show a two sided arrow), and press {{key press|Tab}} again to return to normal mode, used to click stuff in the cockpit. In some aircraft, such as the [[A320neo]] and [[Airbus A330 (disambiguation)|A330]] this unfortunately will not work, so you will have to use right click to look around and mouse mode is disabled. Fortunately, those planes are airliners, which are really stable and easy to fly with the keyboard.

For most users lacking a rudder axis control, it’s difficult to manually coordinate [[aileron]] and [[rudder]] movements during a turn. To enable auto-coordination and make flight easier, you may click "Settings", then click the "Show more" button on the right of "General", and finally click "Enable auto-coordination" in the launcher.

=== First time in the cockpit ===
Finding your way around the cockpit can be daunting the first time.

Where is the "virtual cockpit"? Not all FlightGear aircraft come with an interior actually, some research projects may not even come with an exterior model. A 2D panel may display over the 3D cockpit if one exists. You may turn this off through ''Main Menu'' > ''View'' > ''View Options'' and deselecting ''Show 2D panel'' in the ''Display Options'' section, or by pressing {{key press|Shift|P}}. Otherwise, you should be sitting in the virtual cockpit when FlightGear starts, as long as the Cockpit View is selected (if not pressing {{key press|Ctrl|V}} should get you to the pilot view).

You may find it difficult to read some of the displays, dials and gauges on the instrument panel. You can use the ''view'' mode of the mouse (press {{key press|Tab}} until you get a cursor shaped like a double arrow) to pan and the mouse wheel to zoom, or pan with the joystick hat and zoom with {{key press|X}} and {{key press|Shift|X}}.

One of the first steps that many take on entering an unfamiliar cockpit is to press {{key press|Ctrl|C}} to highlight all the "hotspots", that is instrument controls, buttons, knobs, etc. Many aircraft also offer a specific help menu.

Some functions, such as starter or magneto, may be difficult to use or simply lack clickable "hotspots", especially in aircraft models which are in development. In most cases you can go for the equivalent controls on a 2D panel or resort to the keyboard. The keyboard always work according to the assignments listed on the ''Help'' menu, but sometimes these are reassigned by an aircraft or configuration. Again, remember to check all the help dialogs.

=== Starting the engine ===
You are eager to fly, but the engine is off. Well, turning on the engines is not always easy. Some aircraft have an ''autostart'' entry in their custom menu, but here is a general procedure that should work in many cases:

In general to start the engine on a piston-engine type aircraft, you need (after making sure the game is not paused {{key press|p}}):
# Fuel: Some aircraft start the simulation with no fuel. You can add it in ''Equipment'' > ''Fuel and Payload''.
# Correct fuel mixture: This is generally ''rich'', so push the red knob all the way in, or use the key {{key press|m}} to enrich ({{key press|Shift|m}} leans.)
# Magnetos set on ''both'': Turn the key or press {{key press|}}} ''three times'' to move through ''R'', ''L'', ''Both''.
# Throttle: Some engines start better with a little gas.
# Run the starter: Click the ''Start'' position of the key on the panel, or press {{key press|s}}. Hold the starter for sufficient time, even 10 seconds.

Starting all engines in a multi-engine aircraft is similar to the single engine - except you must follow the same start sequence for each and every engine. FlightGear provides a convenient way to do this for all engines at once: Press {{key press|~}} and all the procedure above will work for all the engines. Note though that the default 2D panel is connected to ''only one engine'' and the {{key press|~}} trick might not work. Also, give some gas to be sure that all the engines are on.

These instructions may not work for jet aircraft, helicopters, or other types of aircraft with complex start procedures. Check the instructions in the aircraft help menu (press {{key press|?}}) and/or look at [[Aircraft|the aircraft's article on this wiki]]. In general to start the engine on a jet engine type aircraft, you need to:
# Set cutoff ''ON''
# Engage the starter
# Once the engines spools up to approximately 5% N1, set cutoff ''OFF''
# Disengage the starter once the engine has reached operational speed

== Learning to fly ==
=== FlightGear's Manual ===
FlightGear has an official [https://www.flightgear.org/support/manual/ manual] that covers the basics of flight. As a beginner, you may want to start with "Chapter 8: A Basic Flight Simulator Tutorial."

=== Tutorials ===
Many aircraft have their own interactive [[tutorials|tutorial]]. With tutorials, you can learn to operate particular aircraft but also learn to fly. You can access tutorials by going to ''Main menu'' > ''Help'' > ''Tutorial''. A great place to start is the tutorial for the [[Cessna 172P]] aircraft, commonly used in real life to learn to fly fixed-winged aircraft.

If the tutorial starts without a runway and surrounded by water, your setup of FlightGear is missing the scenery for the airport at which the tutorial was supposed to run. To get scenery see the [[#Getting scenery]] section above.

== Making your first flight ==
=== Realism ===
One of the most frequent questions novice pilots ask about any flight simulator, but more so to FlightGear, is "Why is my aircraft turning left all the time?" Although it could be due to wind gusts crossing the runway, it is more likely due to the [[Understanding Propeller Torque and P-Factor|propeller torque and p-factor]].

In certain other flight simulators, despite marketing slogans to the contrary, some settings are turned down to make the aircraft easier to fly. This reduces effects such as the above. The realism is always turned up in FlightGear.

Here are some of the FlightGear realism points, which may be confusing to first time pilots:
* "Left turning syndrome" for the previously mentioned reasons.
* Compass turning error: A compass, when subjected to the forces of flight, tends to turn in the opposite direction for a brief period before settling on the correct heading. This is not a malfunction (see also the Wikipedia article {{wikipedia|Aircraft compass turns}}).
* The Vertical Speed Indicator (VSI) is also subject to error.
* The [[Horizontal Situation Indicator]] (HSI) is driven by a gyroscope (that is why it is sometimes called a Directional Gyroscope), which is subject to ''gyro drift''. The indicator will drift from its current heading and must be periodically (every ~15 minutes) calibrated to agree with the magnetic compass heading.
* You cannot just cancel a turn or climb by centering the yoke or stick. You must turn or push the stick the other way to get to level and level flight. But even then, the plane will not maintain its altitude or heading by itself. A common mistake is trying to find a hands off yoke position. While with trimming one could leave the plane for a couple of seconds, one must use autopilot or constantly adjust the yoke.

Many forces act on an aircraft in flight as well as on the [[avionics and instruments]] used for control and navigation, and may be counter-intuitive. Pilots must learn to recognize these phenomena and compensate for their effects. ''FlightGear models instrument errors that exist in the real world''.

=== Airports and navigation aids ===
When you first start FlightGear, whether from the command line or the graphical interface of the launchers, you may wonder how to determine what airports are available. The launcher displays a list of airports, but you will not see details such as tower or [[ILS]] frequencies. You will not find a map showing [[VOR]]s and their frequencies. What can you do? See [[Getting aeronautical charts]].

In-sim, there is a map you can use in ''Main Menu'' > ''Equipment'' > ''Map'', which will allow you to see navigation data and the position of airports and aids. For more help with navigation see [[Understanding navigation]].

=== Flying using the autopilot ===
Some aircraft require you to use the [[autopilot]] available from the ''Autopilot'' menu, which is the original FlightGear autopilot. This is a ''generic'' autopilot and as such, many aircraft come with their own ''specific'' autopilot, frequently a model of the real life one.

For aircraft that provide their own autopilot, you should use the autopilot controls available in the virtual cockpit. This means clicking on the instrument panel in the virtual cockpit. The Autopilot menu will be grayed out and unavailable when the aircraft supplies its own autopilot in some aircraft, including the Airbuses and the [[Cessna 172P|C172P]].

The Cessna 172 comes with a [[Bendix/King KAP140 Autopilot]] in its virtual cockpit. You can use both the autopilot device in the cockpit and the [[Autopilot#Autopilot Settings|autopilot settings]] from the menu.

== Advanced ==
=== Flying ===
{{Main article|Aircraft}}

* If you continue to fly light civilian aircraft, [[Cessna 182S]] which is more complex than C172P and [[Piper PA28 Warrior II|PA28]] are good choices.
* If you are interested in flying airlines, [[Airbus A320 family]], Boeing [[Boeing 777|777]]/[[Boeing 787-8 Dreamliner|787]], [[MD-11]] and [[MD-80]] are suggested.
* If you are fascinated by fighter aircrafts, choose a highly rated military aircraft (such as [[F-15]]) from [[Aircraft#Modern military aircraft|here]] and install [[Bombable]] if possible.
* If you switch to helicopters, it is recommended to fly [[Eurocopter EC130 B4]].

Besides common aircraft, there are also detailed [[Space Shuttle|space shuttles]] available.

=== Scenery ===
It is fascinating to explore the [[scenery]] (or just test the graphics/frame rate) with [[UFO]]. First of all, [[#Configuring rendering and UI|increase your graphics quality]]. If you don't see buildings initially, keep FG open and wait for a while for [[TerraSync]] to finish downloading and for the buildings to appear.
There are plenty of [[Suggested airports|well-developed airports]] and scenery areas. You can also explore the scenery objects on the [https://scenery.flightgear.org/map model map].

=== Multiplayer ===
FlightGear has some multiplayer servers that will let you fly in more lively skies, see [[Howto: Multiplayer]]. There are also [[OpenRadar]] and [[ATC-pie]], standalone programs that will let you be an [[Air traffic control|air traffic controller]].

There is also a [[MPMap|multiplayer map]] that lets you see who is online right now, and even what [[navaids]] are nearby.

=== Menu items ===
For a quick reference about the usage of each menu item in FlightGear, see [[menu]].

=== Addons ===
FlightGear has a lot of third-party [[Addon|addons]] containing enhancements. For beginners, [[Logbook Add-on|Logbook]] and [[Which Runway Add-on|Which Runway]] may be the most useful addons.

== The FlightGear community ==
=== Getting help ===
This page is designed to give the user the essential things they need to know about using FlightGear for the first time. Besides the [[Portal:User|User portal]] of this wiki, there are other pages you may want to read:
*[[Troubleshooting problems]] to help you with the most common issues;
*[[Frequently asked questions]];
...and communication channels that can be used to obtain information or request help:
*The [[FlightGear Manual]], a ''must read'' for beginners;
*{{forum link|text=FlightGear Forum}} and its subforums;
*[[Discord|FlightGear's Discord server]], the quickest way to get help;
*[[FlightGear IRC channel]];
*[[Mailing list|FlightGear users mailing list]], biggest chance to get in contact with core developers;
*Documents bundled with the release package.

=== Customizing FlightGear without compiling it ===
[https://www.flightgear.org/download/ Our website] offers precompiled binaries for download and install on Windows, macOS and Linux. In addition, most Linux distributions provide a packaged version in their repositories.

Although the install is binary, most of FlightGear's systems are open to configuration through [[XML]] files and [[NASAL scripting]]. You are free ''and encouraged'' to make changes to aircraft flight models, scenery, textures, OpenGL [[shader]]s and any other feature you wish to change for your personal satisfaction or to share with other FlightGear users. If this is what you intend to do, take a look at the [[Portal:Developer|Developer portal]].

=== How you can help ===
{{Main article|Volunteer}}
FlightGear is an open source, volunteer based project. That means that whatever you find here comes from passion, spare time and nothing else. This includes the simulator, the scenery, the aircraft, the wiki, the {{forum link|text=forum}} and everything else. Volunteers, in essence ''people that do things'', are fundamental to this project. Without them, it would not make a single step forward. So it is essential that contributors have fun in what they do.

If you plan to contribute to this project, you should take a look at some articles that will give you some hints:
*[[Howto:Understand the FlightGear development process]]
*[[Implementing new features for FlightGear]]
*[[How the FlightGear project works]]

There are never enough people contributing, and the fields where their help would be appreciated are many:
;Testing:
*[[Building FlightGear|Build]] the latest Git code
*[https://gitlab.com/flightgear/flightgear/-/issues File bug reports]
*Running FlightGear via valgrind to track down memory leaks

;Support:
*Help new users with downloading, compiling, installing and running FlightGear ({{forum link|text=on the forum}} or on [[Discord]])
*Provide ideas & suggestions, see: [[Feature Requests / Proposals / Ideas]]
*Help [[Portal:Wiki|clean up this wiki]]
*Help provide new contents for missing wiki pages

;Development:
*C/C++ Coding:
**Provide source code cleanups
**Provide bug fixes [[Bugs]] or new features
**Get involved in any of the other FlightGear-affiliated projects
*Aircraft development (3D modeling, textures, FDMs, scripting)
*Scenery development (terrain, model, weather)

[[Category:FlightGear]]

[[ca:Nou a FlightGear]]
[[de:Neu bei FlightGear]]
[[es:Nuevo en FlightGear]]
[[fi:Uusi_käyttäjä]]
[[fr:Nouveau sur flightgear]]
[[it:Nuovo per FlightGear]]
[[ja:FlightGear入門]]
[[nl:Nieuw bij FlightGear]]
[[pl:Nowy w FlightGear]]
[[pt:Novo no FlightGear]]
[[sr:Novi u FlightGear-u]]
[[th:New to FlightGear]]

Aircraft

2026-05-18T19:29:24Z

Fgf5: /* Lighter than air aircraft (Available since version 1.9.0) */ changed the title

[[File:FlightGear Launcher Aircraft Tab.png|thumb|The FlightGear Qt launcher, showing a handful of the aircraft that are able to be downloaded or updated from the FGAddon repository.]]

This list is not updated to include all the official [[GNU General Public License|GPL licensed]] aircraft for [[FlightGear]], but gives a visual sampling of the different types of aircraft and genres of aircraft officially available.

Most models shown here are available from the official FlightGear project and can be downloaded from the FlightGear launcher, with no additional steps required for installation. Alternatively these aircraft can be obtained directly from the [https://sourceforge.net/p/flightgear/fgaddon/HEAD/tree/ FGAddon SVN repository]. If the aircraft is installed manually, you will lose the ability to check for, and install updates from within the launcher. Some models shown here are available from [[FlightGear hangars|non-official hangars]].

FlightGear aircraft features, quality, and compatibility vary significantly. Their development is dependent on the [[volunteer]]s who worked on them, with exception of some University and Government funded projects. Aircraft are listed by completeness status in [[:Category:Aircraft by status]].

To edit this list, see here: [[Template:Model_Gallery]].

=== Light civilian aircraft ===
The Cessna 172 has been the default aircraft since 2000. These aircraft typically have 1-2 piston engines, props, and avionics geared towards those with civilian pilot licenses.
{{Model Gallery | section=light_civilian_aircraft}}

===Business Jets===
Smaller aircraft with 1-2 turbofan engines, usually used by businesses and private companies.
{{Model Gallery| section=business_jets}}

===Airliners===
These typically have 2-4 turbofan engines and some of the more complicated takeoff and landing procedures (such as multiple [[flaps]]).

See [[Airliner development status]] for more info.

====Narrowbody & Midsize====
{{Model Gallery| section=modern_airliners_narrowbody_midsize}}

====Widebody & Jumbo Airliners====
{{Model Gallery| section=modern_airliners_widebody_jumbo}}

===Helicopters===
{{Main article|Helicopter}}

Helicopters have fundamentally different controls than fixed wing aircraft (see ''[[Flying the Helicopter]]''). Modern helicopter typically feature 1-2 turbine engines, which power a main rotor with 2-6 blades.
{{Model Gallery| section=helicopters}}

===Gliders, Sailplanes, & Ultralights===
These typically have the simplest controls, with minimal avionics. Flying [[:Category:Gliders|gliders]] or sailplanes using [[Soaring|thermals]] can provide more complicated experience. Ultralights on the other hand are among the simplest aircraft in FG.
{{Model Gallery| section=ultra_light}}

===Warbirds===
FlightGear includes a wide variety of vintage military aircraft. Complexity and realism is typically tied to the level of development work with a specific aircraft.
{{Model Gallery| section=warbirds}}

===Carrier-borne aircraft===
FlightGear supports landing on and taking off from [[carriers]].
{{Model Gallery| section=carrier_borne_aircraft}}

===Modern military aircraft ===
FlightGear has a wide variety of modern and retired military jets available, highlighted by features such as air-to-air refueling from the venerable KC-135 and the ability to simulate A-10 ordnance release.
{{Model Gallery| section=modern_military_aircraft}}

===Historical===
Many obscure to famous older aircraft of varying quality are available.
{{Model Gallery| section=historical_aircraft}}

===Experimental & Unique===
Experimental and special purpose aircraft.
{{Model Gallery| section=experimental}}

===Lighter than air aircraft===
These aircraft take advantage of lighter than air gas to become buoyant. In addition to typical aircraft control methods such as elevator, rudder and engine throttle, ballast and control of gas volume and pressure become options.
{{Model Gallery| section=lighter_than_air}}

===Vehicles===
Some useful utility cars in FlightGear.
{{Model Gallery| section=vehicles}}

===Science Fiction===
Alternative models provide a diversion of realistic simulation, but can also be useful for exploring scenery.
{{Model Gallery| section=science_fiction}}

===Spacecraft===
Things that show how small our planet Earth really is.
{{Model Gallery| section=spacecraft}}

==See Also ==
* [[Howto:Make an aircraft]]
* [[How to install aircraft]]
* [[Airliner Development Status]]



[[it:Aerei]]

[[Category:Lists]]
[[Category:Aircraft| ]]

[[ca:Aeronau]]
[[de:Flugzeuge]]
[[es:Avión]]
[[fa:هواپیما]]
[[fi:Lentokoneet]]
[[fr:Avions]]
[[nl:Luchtvaartuigen]]
[[pl:Samoloty]]
[[pt:Avião]]
[[ru:Самолет]]
[[zh:插件飞机]]

Aircraft

2026-05-18T19:10:51Z

Fgf5: /* Lighter than air aircraft (Available from version 1.9.0) */

[[File:FlightGear Launcher Aircraft Tab.png|thumb|The FlightGear Qt launcher, showing a handful of the aircraft that are able to be downloaded or updated from the FGAddon repository.]]

This list is not updated to include all the official [[GNU General Public License|GPL licensed]] aircraft for [[FlightGear]], but gives a visual sampling of the different types of aircraft and genres of aircraft officially available.

Most models shown here are available from the official FlightGear project and can be downloaded from the FlightGear launcher, with no additional steps required for installation. Alternatively these aircraft can be obtained directly from the [https://sourceforge.net/p/flightgear/fgaddon/HEAD/tree/ FGAddon SVN repository]. If the aircraft is installed manually, you will lose the ability to check for, and install updates from within the launcher. Some models shown here are available from [[FlightGear hangars|non-official hangars]].

FlightGear aircraft features, quality, and compatibility vary significantly. Their development is dependent on the [[volunteer]]s who worked on them, with exception of some University and Government funded projects. Aircraft are listed by completeness status in [[:Category:Aircraft by status]].

To edit this list, see here: [[Template:Model_Gallery]].

=== Light civilian aircraft ===
The Cessna 172 has been the default aircraft since 2000. These aircraft typically have 1-2 piston engines, props, and avionics geared towards those with civilian pilot licenses.
{{Model Gallery | section=light_civilian_aircraft}}

===Business Jets===
Smaller aircraft with 1-2 turbofan engines, usually used by businesses and private companies.
{{Model Gallery| section=business_jets}}

===Airliners===
These typically have 2-4 turbofan engines and some of the more complicated takeoff and landing procedures (such as multiple [[flaps]]).

See [[Airliner development status]] for more info.

====Narrowbody & Midsize====
{{Model Gallery| section=modern_airliners_narrowbody_midsize}}

====Widebody & Jumbo Airliners====
{{Model Gallery| section=modern_airliners_widebody_jumbo}}

===Helicopters===
{{Main article|Helicopter}}

Helicopters have fundamentally different controls than fixed wing aircraft (see ''[[Flying the Helicopter]]''). Modern helicopter typically feature 1-2 turbine engines, which power a main rotor with 2-6 blades.
{{Model Gallery| section=helicopters}}

===Gliders, Sailplanes, & Ultralights===
These typically have the simplest controls, with minimal avionics. Flying [[:Category:Gliders|gliders]] or sailplanes using [[Soaring|thermals]] can provide more complicated experience. Ultralights on the other hand are among the simplest aircraft in FG.
{{Model Gallery| section=ultra_light}}

===Warbirds===
FlightGear includes a wide variety of vintage military aircraft. Complexity and realism is typically tied to the level of development work with a specific aircraft.
{{Model Gallery| section=warbirds}}

===Carrier-borne aircraft===
FlightGear supports landing on and taking off from [[carriers]].
{{Model Gallery| section=carrier_borne_aircraft}}

===Modern military aircraft ===
FlightGear has a wide variety of modern and retired military jets available, highlighted by features such as air-to-air refueling from the venerable KC-135 and the ability to simulate A-10 ordnance release.
{{Model Gallery| section=modern_military_aircraft}}

===Historical===
Many obscure to famous older aircraft of varying quality are available.
{{Model Gallery| section=historical_aircraft}}

===Experimental & Unique===
Experimental and special purpose aircraft.
{{Model Gallery| section=experimental}}

===Lighter than air aircraft (Available since version 1.9.0)===
These aircraft take advantage of lighter than air gas to become buoyant. In addition to typical aircraft control methods such as elevator, rudder and engine throttle, ballast and control of gas volume and pressure become options.
{{Model Gallery| section=lighter_than_air}}

===Vehicles===
Some useful utility cars in FlightGear.
{{Model Gallery| section=vehicles}}

===Science Fiction===
Alternative models provide a diversion of realistic simulation, but can also be useful for exploring scenery.
{{Model Gallery| section=science_fiction}}

===Spacecraft===
Things that show how small our planet Earth really is.
{{Model Gallery| section=spacecraft}}

==See Also ==
* [[Howto:Make an aircraft]]
* [[How to install aircraft]]
* [[Airliner Development Status]]



[[it:Aerei]]

[[Category:Lists]]
[[Category:Aircraft| ]]

[[ca:Aeronau]]
[[de:Flugzeuge]]
[[es:Avión]]
[[fa:هواپیما]]
[[fi:Lentokoneet]]
[[fr:Avions]]
[[nl:Luchtvaartuigen]]
[[pl:Samoloty]]
[[pt:Avião]]
[[ru:Самолет]]
[[zh:插件飞机]]

Aircraft

2026-05-18T19:10:28Z

Fgf5: vehicles

[[File:FlightGear Launcher Aircraft Tab.png|thumb|The FlightGear Qt launcher, showing a handful of the aircraft that are able to be downloaded or updated from the FGAddon repository.]]

This list is not updated to include all the official [[GNU General Public License|GPL licensed]] aircraft for [[FlightGear]], but gives a visual sampling of the different types of aircraft and genres of aircraft officially available.

Most models shown here are available from the official FlightGear project and can be downloaded from the FlightGear launcher, with no additional steps required for installation. Alternatively these aircraft can be obtained directly from the [https://sourceforge.net/p/flightgear/fgaddon/HEAD/tree/ FGAddon SVN repository]. If the aircraft is installed manually, you will lose the ability to check for, and install updates from within the launcher. Some models shown here are available from [[FlightGear hangars|non-official hangars]].

FlightGear aircraft features, quality, and compatibility vary significantly. Their development is dependent on the [[volunteer]]s who worked on them, with exception of some University and Government funded projects. Aircraft are listed by completeness status in [[:Category:Aircraft by status]].

To edit this list, see here: [[Template:Model_Gallery]].

=== Light civilian aircraft ===
The Cessna 172 has been the default aircraft since 2000. These aircraft typically have 1-2 piston engines, props, and avionics geared towards those with civilian pilot licenses.
{{Model Gallery | section=light_civilian_aircraft}}

===Business Jets===
Smaller aircraft with 1-2 turbofan engines, usually used by businesses and private companies.
{{Model Gallery| section=business_jets}}

===Airliners===
These typically have 2-4 turbofan engines and some of the more complicated takeoff and landing procedures (such as multiple [[flaps]]).

See [[Airliner development status]] for more info.

====Narrowbody & Midsize====
{{Model Gallery| section=modern_airliners_narrowbody_midsize}}

====Widebody & Jumbo Airliners====
{{Model Gallery| section=modern_airliners_widebody_jumbo}}

===Helicopters===
{{Main article|Helicopter}}

Helicopters have fundamentally different controls than fixed wing aircraft (see ''[[Flying the Helicopter]]''). Modern helicopter typically feature 1-2 turbine engines, which power a main rotor with 2-6 blades.
{{Model Gallery| section=helicopters}}

===Gliders, Sailplanes, & Ultralights===
These typically have the simplest controls, with minimal avionics. Flying [[:Category:Gliders|gliders]] or sailplanes using [[Soaring|thermals]] can provide more complicated experience. Ultralights on the other hand are among the simplest aircraft in FG.
{{Model Gallery| section=ultra_light}}

===Warbirds===
FlightGear includes a wide variety of vintage military aircraft. Complexity and realism is typically tied to the level of development work with a specific aircraft.
{{Model Gallery| section=warbirds}}

===Carrier-borne aircraft===
FlightGear supports landing on and taking off from [[carriers]].
{{Model Gallery| section=carrier_borne_aircraft}}

===Modern military aircraft ===
FlightGear has a wide variety of modern and retired military jets available, highlighted by features such as air-to-air refueling from the venerable KC-135 and the ability to simulate A-10 ordnance release.
{{Model Gallery| section=modern_military_aircraft}}

===Historical===
Many obscure to famous older aircraft of varying quality are available.
{{Model Gallery| section=historical_aircraft}}

===Experimental & Unique===
Experimental and special purpose aircraft.
{{Model Gallery| section=experimental}}

===Lighter than air aircraft (Available from version 1.9.0)===
These aircraft take advantage of lighter than air gas to become buoyant. In addition to typical aircraft control methods such as elevator, rudder and engine throttle, ballast and control of gas volume and pressure become options.
{{Model Gallery| section=lighter_than_air}}

===Vehicles===
Some useful utility cars in FlightGear.
{{Model Gallery| section=vehicles}}

===Science Fiction===
Alternative models provide a diversion of realistic simulation, but can also be useful for exploring scenery.
{{Model Gallery| section=science_fiction}}

===Spacecraft===
Things that show how small our planet Earth really is.
{{Model Gallery| section=spacecraft}}

==See Also ==
* [[Howto:Make an aircraft]]
* [[How to install aircraft]]
* [[Airliner Development Status]]



[[it:Aerei]]

[[Category:Lists]]
[[Category:Aircraft| ]]

[[ca:Aeronau]]
[[de:Flugzeuge]]
[[es:Avión]]
[[fa:هواپیما]]
[[fi:Lentokoneet]]
[[fr:Avions]]
[[nl:Luchtvaartuigen]]
[[pl:Samoloty]]
[[pt:Avião]]
[[ru:Самолет]]
[[zh:插件飞机]]

Follow me e-tron/info

2026-05-18T18:58:40Z

Fgf5: change the repository url and name

<includeonly>{{infobox aircraft
| name = Follow Me e-tron
| aircraft = Follow Me e-tron
| image = Preview-etron 4.0.jpg
| image2 = Preview-etron.png
| type = Automobile/Utility vehicle
| devel-team = FlightGear China
| authors = Sidi Liang (梁思地)/Qiyuan Luo (罗启元)/ValKmjolnir/Weihao Lee (李维昊)/Marsdolphin
| fdm = JSBSim
| fgname = followmeEV/followme-PAX
| status-fdm = 4
| status-systems = 3
| status-cockpit = 5
| status-model = 4
| craft = vehicle
| ready = tutorials
| devel-website = https://www.fgprc.org.cn/followmeev.html
| devel-repo = https://github.com/sidi762/followme_e-tron
| download = https://github.com/sidi762/followme_e-tron/releases/latest
| forumtid = 36211
| licence = GPLv2
| navbar = 1
}}</includeonly><noinclude>
This is the aircraft infobox subpage of the [[Follow me e-tron]].
[[Category:Aircraft infobox documentation]]
</noinclude>

Follow me e-tron

2026-05-18T18:55:04Z

Fgf5:

{{:{{PAGENAME}}/info}}
The '''Follow me e-tron''' or '''Follow me EV''' is a semi-fictional Follow-me vehicle based on [[Follow_me|Gijs's work]], but an electric-powered version with Chinese characteristics. It was made initially just for fun.

The vehicle implements a detailed electric powertrain and electrical system in Nasal, along with key features including an advanced steering helper and systems such as 'AutoCrash' and 'AutoSpeed' for driving assistance. Additional functionalities encompass an Auto Hold feature, parking radar, working airbags, and an experimental Advanced Emergency Braking (AEB) system.

The model offers multiple interior configurations with functional controls and different instrument panel options, including a Canvas-based glass display. Customization options extend to Chinese-style license plates and various livery choices. A stretched limousine variant is also available.

The vehicle is fully equipped for multiplayer with multiplayer passengers supported. It also has a dynamic scenery object placement system, allowing vehicles-related objects such as highway tollgates and recharging stations to be placed on the scenery for more immersive driving.

== Features ==
Being the '''very first electric car''' in FlightGear, the Follow me e-tron features a realistic electric supercar driving experience while having an exterior of the classic Renault Kangoo I Follow me vehicle.

[[File:FollowmeEV广州.png|center|700px|Screenshot of the FollowmeEV in Guangzhou]]

* Realistic electric engine written in Nasal.
* Detailed electrical system written in Nasal.
* Advanced steering helper (experimental)
* 'AutoCrash' system, which tries its best to keep you on the road.
* 'AutoSpeed' system, which keeps your speed constant.
* Auto Hold function
* Parking radar that detects terrain and alerts driver.
* Working airbags.
* Experimental AEB system.
* Configurable interior with several fully remodeled interior and working switches.
* Configurable instruments with several styles to choose from.
* Canvas glass display instrument for certain interior styles
* Compositor light support.
* Selectable license plate in Chinese style.
* Various of liveries
* Various of messages
* Full multiplayer support.
* Multiplayer passenger.
* Dynamic scenery object placement and management
* Limo variant
* Tutorials support in different languages
* Different interior styles to choose from.
* Save / Resume function.

== Installation ==
{{main article|Howto:Install aircraft#Manual installation process}}
Follow me e-tron is not in the official hangar and you have to install it manually. Download the zip file from the [https://github.com/sidi762/followme_e-tron/releases/latest latest release], unpack it and add the aircraft path to the launcher. For installation instructions, see [[Howto:Install aircraft#Manual installation process|here]].

== Videos ==
{{#ev:youtube|p-P6SkRu6PE}}
{{#ev:youtube|pq6Lb5GA3Bc}}
{{#ev:youtube|MGZU85t5LCo}}

== Version ==
The Follow me EV is currently released as v5.2.

=== Change Log ===
V5.2 Updates:

* The advanced steering received a major update and renamed to realistic steering, adapted the Pacejka tire model into the calculation which should provide more realism.

* Various bug fixes and optimization.

* Improved aircraft help and documentation.

* Added drifting sound.

* New splash screen images.

* New preview image.

V5.1 Updates:

* Major improvements to the reset function
* Bug fixes and improvements

V5.0 Updates:

* Added an option to adjust brake intensity for keyboard control
* Further tuned engine and fixed the bug related to gear changing
* New liveries: Blackwhite, C919 Memorial
* Interior updates
* New magic bush tyre option for driving on killer grass
* New interior: 404Design 2.0, 404Design 2022 and Luxury 2.0
* New charging pile
* Exterior model improvements, especially on charging cap, wheels and doors
* Added rear plate with multiplayer support
* Improvements on sounds
* Added option to re-enable ALS procedural lights
* Default interior switched to 404Design
* Added door warnings for smart instruments
* General improvements, cleanups and bug fixes

V4.0 New Features:

* Added a limo varient
* New texture selector which works better under multiplayer
* New interior style: Race, 404Design
* New canvas glass display instrument for 404Design Interior
* New dynamic scenery object system
* New models for service station, toll gates, etc
* Added reverse indicator light

Updates and improvements:

* Major updates to the UV
* Major update to the Engine & electrical systems, (much) more realistic performance
* FDM improvements
* AEB improvements
* Minor texture and exterior/interior model updates
* Sounds updates
* Added multiplayer model detection support to radar(and AEB which relies on the radar)
* Many bug fixes

Changes after v4.0 alpha:

* Added battery remaining display
* Improvements to Nasal performance
* Huge bug fixes to the electrical system
* Many minor bug fixes
* Added option to adjust steering

Changes after v4.0 beta.1:

* Added error message to the smart instruments after the battery is drained
* Bug fixes

Changes after v4.0 beta.2:

* Bug fixes

V3.0 New Features:

* Configurable interior with several fully remodeled interior and working switches
* Functioning Airbags
* Experimental AEB system
* Experimental compositor light support
* Auto Hold function
* Save / Resume
* New tutorials

Improvements:

* Electrical system
* Brake system
* Sounds
* Effects
* Several bugs fixed

V2.0:

Updated features:

* Updated interior
* Exterior improvements
* Autospeed system
* New experimental steering system
* Parking radar system
* Sound improvements
* FDM improvements
* Liveries updates
* Tons of bug fixes

V1.0:

Initial Release

== Statistics ==
''Note: The figures below was measured before the v4.0 release. The entire engine received an update in the v4.0 release and the performance is now way more realistic.''

Top speed:
≤300kts/555.6km/h
=== Acceleration ===
Accelerate up to:
100km/h: 2.48 seconds
200km/h: 7.20 seconds
=== Battery ===
Electricity usage:
---km/charge (Yet to be determined)

== Gallery ==

=== Newer Versions ===
<gallery mode="packed">
File:Followme EV interior preview 2.jpg|Followme EV Interior
File:Followme EV in ZBNY.jpg|Followme EV inside ZBNY
File:Followme EV interior preview.jpg|Followme EV Interior
File:Followme EV.png|Three Followme EVs lining up
File:Followme EV in a charging station.png|Followme EVs in a charging station, showcasing the dynamic scenery object system
File:Followme EV in front of a toll station, at the endpoint of G1 National Highway.png|Followme EV in front of the Wapenyao toll station, at the endpoint of G1 National Highway
File:Followme EV in a service station.png|Followme EV inside a service station
File:Followme EV on the G318 Sichuan-Tibet Route.png|Followme EV on the famous G318 Sichuan-Tibet Route
File:Followme EV in a valley.png|Followme EV in a valley on the G318 Sichuan-Tibet Route
File:Followme EV recharging alongside the G318 Sichuan-Tibet Route.png|Followme EV recharging alongside the G318 Sichuan-Tibet Route
</gallery>

=== Earlier Versions ===
<gallery mode="packed">
Followme EV historical screenshot.png|Screenshot of early versions of the Followme EV
Followme EV historical screenshot2.png|Screenshot of early versions of the Followme EV
Followme EV historical screenshot3.png|Screenshot of early versions of the Followme EV
Followme EV historical screenshot4.png|Screenshot of early versions of the Followme EV
Followme EV historical screenshot5.png|Screenshot of early versions of the Followme EV
Followme EV historical screenshot6.png|Screenshot of early versions of the Followme EV
FollowmeEV广州.png|Screenshot of the FollowmeEV in Guangzhou
FollowmeEV武汉2.png|Screenshot of the FollowmeEV in Wuhan
FollowmeEV武汉3.png|Screenshot of the FollowmeEV in Wuhan
FollowmeEV武汉4.png|Screenshot of the FollowmeEV in Wuhan
</gallery>

== Related content ==
=== Forum topic ===
* {{forum link|title=Grand Tour with Follow me: From Beijing to Shenzhen|t=36211}}
* [[FlightGear China]]
* [http://www.fgprc.org FGPRC homepage]

Follow me e-tron

2026-05-18T18:52:35Z

Fgf5: installation

{{:{{PAGENAME}}/info}}
The '''Follow me e-tron''' or '''Follow me EV''' is a semi-fictional Follow-me vehicle based on [[Follow_me|Gijs's work]], but an electric-powered version with Chinese characteristics. It was made initially just for fun.

The vehicle implements a detailed electric powertrain and electrical system in Nasal, along with key features including an advanced steering helper and systems such as 'AutoCrash' and 'AutoSpeed' for driving assistance. Additional functionalities encompass an Auto Hold feature, parking radar, working airbags, and an experimental Advanced Emergency Braking (AEB) system.

The model offers multiple interior configurations with functional controls and different instrument panel options, including a Canvas-based glass display. Customization options extend to Chinese-style license plates and various livery choices. A stretched limousine variant is also available.

The vehicle is fully equipped for multiplayer with multiplayer passengers supported. It also has a dynamic scenery object placement system, allowing vehicles-related objects such as highway tollgates and recharging stations to be placed on the scenery for more immersive driving.

== Features ==
Being the '''very first electric car''' in FlightGear, the Follow me e-tron features a realistic electric supercar driving experience while having an exterior of the classic Renault Kangoo I Follow me vehicle.

[[File:FollowmeEV广州.png|center|700px|Screenshot of the FollowmeEV in Guangzhou]]

* Realistic electric engine written in Nasal.
* Detailed electrical system written in Nasal.
* Advanced steering helper (experimental)
* 'AutoCrash' system, which tries its best to keep you on the road.
* 'AutoSpeed' system, which keeps your speed constant.
* Auto Hold function
* Parking radar that detects terrain and alerts driver.
* Working airbags.
* Experimental AEB system.
* Configurable interior with several fully remodeled interior and working switches.
* Configurable instruments with several styles to choose from.
* Canvas glass display instrument for certain interior styles
* Compositor light support.
* Selectable license plate in Chinese style.
* Various of liveries
* Various of messages
* Full multiplayer support.
* Multiplayer passenger.
* Dynamic scenery object placement and management
* Limo variant
* Tutorials support in different languages
* Different interior styles to choose from.
* Save / Resume function.

== Installation ==
{{main article|Howto:Install aircraft#Manual installation process}}
Follow me e-tron is not in the official hangar and you have to install it manually. Download the zip file from the [https://github.com/FGPRC-FlightGearChina/followme_e-tron/releases/latest latest release], unpack it and add the aircraft path to the launcher. For installation instructions, see [[Howto:Install aircraft#Manual installation process|here]].

== Videos ==
{{#ev:youtube|p-P6SkRu6PE}}
{{#ev:youtube|pq6Lb5GA3Bc}}
{{#ev:youtube|MGZU85t5LCo}}

== Version ==
The Follow me EV is currently released as v5.2.

=== Change Log ===
V5.2 Updates:

* The advanced steering received a major update and renamed to realistic steering, adapted the Pacejka tire model into the calculation which should provide more realism.

* Various bug fixes and optimization.

* Improved aircraft help and documentation.

* Added drifting sound.

* New splash screen images.

* New preview image.

V5.1 Updates:

* Major improvements to the reset function
* Bug fixes and improvements

V5.0 Updates:

* Added an option to adjust brake intensity for keyboard control
* Further tuned engine and fixed the bug related to gear changing
* New liveries: Blackwhite, C919 Memorial
* Interior updates
* New magic bush tyre option for driving on killer grass
* New interior: 404Design 2.0, 404Design 2022 and Luxury 2.0
* New charging pile
* Exterior model improvements, especially on charging cap, wheels and doors
* Added rear plate with multiplayer support
* Improvements on sounds
* Added option to re-enable ALS procedural lights
* Default interior switched to 404Design
* Added door warnings for smart instruments
* General improvements, cleanups and bug fixes

V4.0 New Features:

* Added a limo varient
* New texture selector which works better under multiplayer
* New interior style: Race, 404Design
* New canvas glass display instrument for 404Design Interior
* New dynamic scenery object system
* New models for service station, toll gates, etc
* Added reverse indicator light

Updates and improvements:

* Major updates to the UV
* Major update to the Engine & electrical systems, (much) more realistic performance
* FDM improvements
* AEB improvements
* Minor texture and exterior/interior model updates
* Sounds updates
* Added multiplayer model detection support to radar(and AEB which relies on the radar)
* Many bug fixes

Changes after v4.0 alpha:

* Added battery remaining display
* Improvements to Nasal performance
* Huge bug fixes to the electrical system
* Many minor bug fixes
* Added option to adjust steering

Changes after v4.0 beta.1:

* Added error message to the smart instruments after the battery is drained
* Bug fixes

Changes after v4.0 beta.2:

* Bug fixes

V3.0 New Features:

* Configurable interior with several fully remodeled interior and working switches
* Functioning Airbags
* Experimental AEB system
* Experimental compositor light support
* Auto Hold function
* Save / Resume
* New tutorials

Improvements:

* Electrical system
* Brake system
* Sounds
* Effects
* Several bugs fixed

V2.0:

Updated features:

* Updated interior
* Exterior improvements
* Autospeed system
* New experimental steering system
* Parking radar system
* Sound improvements
* FDM improvements
* Liveries updates
* Tons of bug fixes

V1.0:

Initial Release

== Statistics ==
''Note: The figures below was measured before the v4.0 release. The entire engine received an update in the v4.0 release and the performance is now way more realistic.''

Top speed:
≤300kts/555.6km/h
=== Acceleration ===
Accelerate up to:
100km/h: 2.48 seconds
200km/h: 7.20 seconds
=== Battery ===
Electricity usage:
---km/charge (Yet to be determined)

== Gallery ==

=== Newer Versions ===
<gallery mode="packed">
File:Followme EV interior preview 2.jpg|Followme EV Interior
File:Followme EV in ZBNY.jpg|Followme EV inside ZBNY
File:Followme EV interior preview.jpg|Followme EV Interior
File:Followme EV.png|Three Followme EVs lining up
File:Followme EV in a charging station.png|Followme EVs in a charging station, showcasing the dynamic scenery object system
File:Followme EV in front of a toll station, at the endpoint of G1 National Highway.png|Followme EV in front of the Wapenyao toll station, at the endpoint of G1 National Highway
File:Followme EV in a service station.png|Followme EV inside a service station
File:Followme EV on the G318 Sichuan-Tibet Route.png|Followme EV on the famous G318 Sichuan-Tibet Route
File:Followme EV in a valley.png|Followme EV in a valley on the G318 Sichuan-Tibet Route
File:Followme EV recharging alongside the G318 Sichuan-Tibet Route.png|Followme EV recharging alongside the G318 Sichuan-Tibet Route
</gallery>

=== Earlier Versions ===
<gallery mode="packed">
Followme EV historical screenshot.png|Screenshot of early versions of the Followme EV
Followme EV historical screenshot2.png|Screenshot of early versions of the Followme EV
Followme EV historical screenshot3.png|Screenshot of early versions of the Followme EV
Followme EV historical screenshot4.png|Screenshot of early versions of the Followme EV
Followme EV historical screenshot5.png|Screenshot of early versions of the Followme EV
Followme EV historical screenshot6.png|Screenshot of early versions of the Followme EV
FollowmeEV广州.png|Screenshot of the FollowmeEV in Guangzhou
FollowmeEV武汉2.png|Screenshot of the FollowmeEV in Wuhan
FollowmeEV武汉3.png|Screenshot of the FollowmeEV in Wuhan
FollowmeEV武汉4.png|Screenshot of the FollowmeEV in Wuhan
</gallery>

== Related content ==
=== Forum topic ===
* {{forum link|title=Grand Tour with Follow me: From Beijing to Shenzhen|t=36211}}
* [[FlightGear China]]
* [http://www.fgprc.org FGPRC homepage]

Follow me

2026-05-18T18:40:12Z

Fgf5: related content

{{:{{PAGENAME}}/info}}
'''Follow me''' is a [[Vehicles|car]] that leads [[aircraft]] to the right gate or runway. Mostly used for pilots that are not known with the airport.

In [[FlightGear]], the car can show various messages in its textbar to the following aircraft, which can be an other pilot [[Howto: Multiplayer|flying online]]. Making use of these messages, the aircraft can be guided to its gate, or to the runway.

== Related content ==
* [[Follow me e-tron]] - an improved version of Follow me.

== External links ==
* [http://forum.flightgear.org/viewtopic.php?t=858 Forum topic]

Howto:Install aircraft

2026-05-18T18:39:07Z

Fgf5: /* Notes */

{{installing}}

The preferred option to install the latest official [[aircraft]] is through the ''Aircraft'' tab in the [[FlightGear Qt launcher|built-in launcher]], as explained in the following video. The remainder of this article describes the manual process, only to be performed when you don't use the aircrafts from the official FGAddon hangar.

{{#ev:youtube|a-UIrw7nEy4}}

== Manual installation process ==

=== Linux ===
# Download the aircraft
# Create a directory to store your aircraft if you have not already done so. Make sure this directory is outside your <tt>[[$FG_ROOT]]</tt> directory (e.g., <tt>/usr/share/games/flightgear/</tt>). For example, use <tt>/home/{YourUserName}/fg/CustomAircraft</tt>.
# Extract your aircraft file into the folder (the one you created above)
#: unzip XXXXX.zip
# Start up FlightGear with the launcher. In the launcher, go to the ''Add-ons'' tab. In the ''Additional aircraft folders'' section, click the ''Add'' button and select the main folder for additional aircrafts (in our case <tt>/home/{YourUserName}/fg/CustomAircraft</tt>). Now your plane should appear on the list of planes, otherwise restart FlightGear.

If you want to install more aircraft, you just need to unzip the next downloaded aircraft in the same directory and it should already be visible on FlightGear.

=== macOS ===

# Download the aircraft
# Create a directory to store your aircraft if you have not already done so. Make sure this directory is somewhere you can find easily, For example, use <code>/Users/{YourUserName}/Aircraft</code>.
# Extract your aircraft file into the folder (the one you created above)
# Start up FlightGear with Launcher. In Launcher, go to the ''Add-ons'' tab. In the ''Additional aircraft folders'' section, click the ''Add'' button and select the main folder for additional aircrafts (in our case <code>/Users/{YourUserName}/Aircraft</code>). Now your plane should appear on the list of planes, otherwise restart FlightGear.

If you want to install more aircraft, you just need to unzip the next downloaded aircraft in the same directory and it should already be visible on FlightGear. This method is preferred over modifying FGData as it allows you to more easily access the aircrafts files, as well as having the benefit of persisting across FG updates, saving the hassle of having to redownload and install your aircraft each time you update FlightGear.

=== Windows ===
# Download an aircraft and save it on your desktop.
# Unzip the file using a file archiver, for example the open source file archiver [http://www.7-zip.org/ 7-Zip].
# Create a directory to store your aircraft if you have not already done so. Make sure this directory is outside your <tt>[[$FG_ROOT]]</tt> directory. For example, use <tt>C:\Users\{YourUserName}\fg\CustomAircraft</tt>.
# Move the unzipped folder (usually the aircraft's name) to your that aircraft directory.
# Start up FlightGear with Launcher. In Launcher, go to the ''Add-ons'' tab. In the ''Additional aircraft folders'' section, click the ''Add'' button and select the main folder for additional aircrafts (in our case <tt>C:\Users\{YourUserName}\fg\CustomAircraft</tt>). Now your plane should appear on the list of planes, otherwise restart FlightGear.

If you want to install more aircraft, you just need to unzip the next downloaded aircraft in the same directory and it should already be visible on FlightGear.

=== From the command line ===
If you launch FlightGear from the command line, use the <code>--fg-aircraft=path</code> option, which in our case can be: <code>--fg-aircraft=/home/{YourUserName}/fg/CustomAircraft</code>.

=== Notes ===
The path added in the [[FlightGear Qt launcher|launcher]] is the parent directory and should NOT be the directory of specific aircraft. For example, if the aircraft path is <code>.../CustomAircraft/c182s</code>, you should select <code>.../CustomAircraft</code> instead of <code>.../CustomAircraft/c182s</code> in the launcher.

== When installing an aircraft fails ==
=== Rename aircraft folder ===
If FlightGear fails to start with the new aircraft you have installed, or if it starts but the aircraft is invisible you might have to rename the folder where the aircraft files are.
This issue is most often encountered when downloading a .zip file from some online git repository. In those cases you will most likely end up with a folder name of the following form MyZippedRepo-[branch]. In this case you should rename the folder to be just '''MyZippedRepo'''.

If the above doesn't work, or for other cases, check for a readme file and have a look there for instructions.

Otherwise open the aircraft-set.xml file and search in it for paths containing '''Aircraft/AircraftFolderName'''. The name of the folder should match '''AircraftFolderName'''.

For instance if in the imaginary-set.xml you would find an instance like this:
<syntaxhighlight lang="xml">
<splash-texture>Aircraft/MyCreation/splash1.png</splash-texture>
</syntaxhighlight>
that means that you should rename the folder where imaginary-set.xml is to '''MyCreation'''.

=== XML files with wrong encoding ===
If you start FlightGear with the new plane you installed and there is no cockpit or exterior, this may be because the XML files are in the wrong encoding.

To fix this on Linux try this:
<syntaxhighlight lang="bash">
$ cd path/to/aircraft/directory/
$ find . -name "*.xml" -print | xargs sed -i 's/<?xml version="1.0" encoding="UTF-8"?>/<?xml version="1.0" encoding="ISO-8859-1"?>/g'
</syntaxhighlight>

If any of the methods above do not work, ask around on the [[Howto:Multiplayer#Multiplayer chat|multiplayer chat]], [[FlightGear IRC channel|IRC]] or on the {{forum link|f=11|text=forum}}.

== Choosing aircraft ==
If you are looking for information to decide what aircraft to download, try:
* [[Aircraft]]
* [[Helicopter]]
* [[Vehicle]]
* [[Table of models]]
External links to third party aircraft can be found at [[FlightGear hangars]]. Remember that the latest aircraft may not load with previous versions. If you happen to use an older version of FlightGear, look for older aircraft in the links section.

==Video tutorial by the community==
{{#ev:youtube|OiqGjc8W880|480px||Tutorial on downloading and installing aircraft from Github pages by PINTO. Adding manually downloaded aircraft folders in the [[FlightGear_Qt_launcher|qt-launcher]] is pretty much the same for non-github downloads too. Aircraft are often developed on Github. This shows you to the download Github versions of aircraft that are not in FGAddon yet for whatever reason, and the latest work-in-progress state of some aircraft in FGAddon for testing and feedback. (September 2019)}}

== Related content ==
* [[Installing Scenery]]

[[Category:Howto|Install aircraft]]

[[de:Howto:Flugzeuge Installieren]]
[[es:Cómo:Instalar_aviones]]
[[fr:Howto Installer un avion]]
[[pl:Instalowanie_samolotów]]

Howto:Install aircraft

2026-05-18T18:38:14Z

Fgf5: /* From the command line */

{{installing}}

The preferred option to install the latest official [[aircraft]] is through the ''Aircraft'' tab in the [[FlightGear Qt launcher|built-in launcher]], as explained in the following video. The remainder of this article describes the manual process, only to be performed when you don't use the aircrafts from the official FGAddon hangar.

{{#ev:youtube|a-UIrw7nEy4}}

== Manual installation process ==

=== Linux ===
# Download the aircraft
# Create a directory to store your aircraft if you have not already done so. Make sure this directory is outside your <tt>[[$FG_ROOT]]</tt> directory (e.g., <tt>/usr/share/games/flightgear/</tt>). For example, use <tt>/home/{YourUserName}/fg/CustomAircraft</tt>.
# Extract your aircraft file into the folder (the one you created above)
#: unzip XXXXX.zip
# Start up FlightGear with the launcher. In the launcher, go to the ''Add-ons'' tab. In the ''Additional aircraft folders'' section, click the ''Add'' button and select the main folder for additional aircrafts (in our case <tt>/home/{YourUserName}/fg/CustomAircraft</tt>). Now your plane should appear on the list of planes, otherwise restart FlightGear.

If you want to install more aircraft, you just need to unzip the next downloaded aircraft in the same directory and it should already be visible on FlightGear.

=== macOS ===

# Download the aircraft
# Create a directory to store your aircraft if you have not already done so. Make sure this directory is somewhere you can find easily, For example, use <code>/Users/{YourUserName}/Aircraft</code>.
# Extract your aircraft file into the folder (the one you created above)
# Start up FlightGear with Launcher. In Launcher, go to the ''Add-ons'' tab. In the ''Additional aircraft folders'' section, click the ''Add'' button and select the main folder for additional aircrafts (in our case <code>/Users/{YourUserName}/Aircraft</code>). Now your plane should appear on the list of planes, otherwise restart FlightGear.

If you want to install more aircraft, you just need to unzip the next downloaded aircraft in the same directory and it should already be visible on FlightGear. This method is preferred over modifying FGData as it allows you to more easily access the aircrafts files, as well as having the benefit of persisting across FG updates, saving the hassle of having to redownload and install your aircraft each time you update FlightGear.

=== Windows ===
# Download an aircraft and save it on your desktop.
# Unzip the file using a file archiver, for example the open source file archiver [http://www.7-zip.org/ 7-Zip].
# Create a directory to store your aircraft if you have not already done so. Make sure this directory is outside your <tt>[[$FG_ROOT]]</tt> directory. For example, use <tt>C:\Users\{YourUserName}\fg\CustomAircraft</tt>.
# Move the unzipped folder (usually the aircraft's name) to your that aircraft directory.
# Start up FlightGear with Launcher. In Launcher, go to the ''Add-ons'' tab. In the ''Additional aircraft folders'' section, click the ''Add'' button and select the main folder for additional aircrafts (in our case <tt>C:\Users\{YourUserName}\fg\CustomAircraft</tt>). Now your plane should appear on the list of planes, otherwise restart FlightGear.

If you want to install more aircraft, you just need to unzip the next downloaded aircraft in the same directory and it should already be visible on FlightGear.

=== From the command line ===
If you launch FlightGear from the command line, use the <code>--fg-aircraft=path</code> option, which in our case can be: <code>--fg-aircraft=/home/{YourUserName}/fg/CustomAircraft</code>.

=== Notes ===
The path added in the [[FlightGear Qt launcher|launcher]] should NOT be the directory of specific aircraft. For example, if the aircraft path is <code>.../CustomAircraft/c182s</code>, you should select <code>.../CustomAircraft</code> instead of <code>.../CustomAircraft/c182s</code> in the launcher.

== When installing an aircraft fails ==
=== Rename aircraft folder ===
If FlightGear fails to start with the new aircraft you have installed, or if it starts but the aircraft is invisible you might have to rename the folder where the aircraft files are.
This issue is most often encountered when downloading a .zip file from some online git repository. In those cases you will most likely end up with a folder name of the following form MyZippedRepo-[branch]. In this case you should rename the folder to be just '''MyZippedRepo'''.

If the above doesn't work, or for other cases, check for a readme file and have a look there for instructions.

Otherwise open the aircraft-set.xml file and search in it for paths containing '''Aircraft/AircraftFolderName'''. The name of the folder should match '''AircraftFolderName'''.

For instance if in the imaginary-set.xml you would find an instance like this:
<syntaxhighlight lang="xml">
<splash-texture>Aircraft/MyCreation/splash1.png</splash-texture>
</syntaxhighlight>
that means that you should rename the folder where imaginary-set.xml is to '''MyCreation'''.

=== XML files with wrong encoding ===
If you start FlightGear with the new plane you installed and there is no cockpit or exterior, this may be because the XML files are in the wrong encoding.

To fix this on Linux try this:
<syntaxhighlight lang="bash">
$ cd path/to/aircraft/directory/
$ find . -name "*.xml" -print | xargs sed -i 's/<?xml version="1.0" encoding="UTF-8"?>/<?xml version="1.0" encoding="ISO-8859-1"?>/g'
</syntaxhighlight>

If any of the methods above do not work, ask around on the [[Howto:Multiplayer#Multiplayer chat|multiplayer chat]], [[FlightGear IRC channel|IRC]] or on the {{forum link|f=11|text=forum}}.

== Choosing aircraft ==
If you are looking for information to decide what aircraft to download, try:
* [[Aircraft]]
* [[Helicopter]]
* [[Vehicle]]
* [[Table of models]]
External links to third party aircraft can be found at [[FlightGear hangars]]. Remember that the latest aircraft may not load with previous versions. If you happen to use an older version of FlightGear, look for older aircraft in the links section.

==Video tutorial by the community==
{{#ev:youtube|OiqGjc8W880|480px||Tutorial on downloading and installing aircraft from Github pages by PINTO. Adding manually downloaded aircraft folders in the [[FlightGear_Qt_launcher|qt-launcher]] is pretty much the same for non-github downloads too. Aircraft are often developed on Github. This shows you to the download Github versions of aircraft that are not in FGAddon yet for whatever reason, and the latest work-in-progress state of some aircraft in FGAddon for testing and feedback. (September 2019)}}

== Related content ==
* [[Installing Scenery]]

[[Category:Howto|Install aircraft]]

[[de:Howto:Flugzeuge Installieren]]
[[es:Cómo:Instalar_aviones]]
[[fr:Howto Installer un avion]]
[[pl:Instalowanie_samolotów]]

Howto:Install aircraft

2026-05-18T18:37:00Z

Fgf5: /* Manual installation process */

{{installing}}

The preferred option to install the latest official [[aircraft]] is through the ''Aircraft'' tab in the [[FlightGear Qt launcher|built-in launcher]], as explained in the following video. The remainder of this article describes the manual process, only to be performed when you don't use the aircrafts from the official FGAddon hangar.

{{#ev:youtube|a-UIrw7nEy4}}

== Manual installation process ==

=== Linux ===
# Download the aircraft
# Create a directory to store your aircraft if you have not already done so. Make sure this directory is outside your <tt>[[$FG_ROOT]]</tt> directory (e.g., <tt>/usr/share/games/flightgear/</tt>). For example, use <tt>/home/{YourUserName}/fg/CustomAircraft</tt>.
# Extract your aircraft file into the folder (the one you created above)
#: unzip XXXXX.zip
# Start up FlightGear with the launcher. In the launcher, go to the ''Add-ons'' tab. In the ''Additional aircraft folders'' section, click the ''Add'' button and select the main folder for additional aircrafts (in our case <tt>/home/{YourUserName}/fg/CustomAircraft</tt>). Now your plane should appear on the list of planes, otherwise restart FlightGear.

If you want to install more aircraft, you just need to unzip the next downloaded aircraft in the same directory and it should already be visible on FlightGear.

=== macOS ===

# Download the aircraft
# Create a directory to store your aircraft if you have not already done so. Make sure this directory is somewhere you can find easily, For example, use <code>/Users/{YourUserName}/Aircraft</code>.
# Extract your aircraft file into the folder (the one you created above)
# Start up FlightGear with Launcher. In Launcher, go to the ''Add-ons'' tab. In the ''Additional aircraft folders'' section, click the ''Add'' button and select the main folder for additional aircrafts (in our case <code>/Users/{YourUserName}/Aircraft</code>). Now your plane should appear on the list of planes, otherwise restart FlightGear.

If you want to install more aircraft, you just need to unzip the next downloaded aircraft in the same directory and it should already be visible on FlightGear. This method is preferred over modifying FGData as it allows you to more easily access the aircrafts files, as well as having the benefit of persisting across FG updates, saving the hassle of having to redownload and install your aircraft each time you update FlightGear.

=== Windows ===
# Download an aircraft and save it on your desktop.
# Unzip the file using a file archiver, for example the open source file archiver [http://www.7-zip.org/ 7-Zip].
# Create a directory to store your aircraft if you have not already done so. Make sure this directory is outside your <tt>[[$FG_ROOT]]</tt> directory. For example, use <tt>C:\Users\{YourUserName}\fg\CustomAircraft</tt>.
# Move the unzipped folder (usually the aircraft's name) to your that aircraft directory.
# Start up FlightGear with Launcher. In Launcher, go to the ''Add-ons'' tab. In the ''Additional aircraft folders'' section, click the ''Add'' button and select the main folder for additional aircrafts (in our case <tt>C:\Users\{YourUserName}\fg\CustomAircraft</tt>). Now your plane should appear on the list of planes, otherwise restart FlightGear.

If you want to install more aircraft, you just need to unzip the next downloaded aircraft in the same directory and it should already be visible on FlightGear.

=== From the command line ===
If you launch FlightGear from the command line, use the <code>--fg-aircraft=path</code> option, which in our case can be: <code>--fg-aircraft=/home/{YourUserName}/FlightGear/CustomAircraft</code>.

=== Notes ===
The path added in the [[FlightGear Qt launcher|launcher]] should NOT be the directory of specific aircraft. For example, if the aircraft path is <code>.../CustomAircraft/c182s</code>, you should select <code>.../CustomAircraft</code> instead of <code>.../CustomAircraft/c182s</code> in the launcher.

== When installing an aircraft fails ==
=== Rename aircraft folder ===
If FlightGear fails to start with the new aircraft you have installed, or if it starts but the aircraft is invisible you might have to rename the folder where the aircraft files are.
This issue is most often encountered when downloading a .zip file from some online git repository. In those cases you will most likely end up with a folder name of the following form MyZippedRepo-[branch]. In this case you should rename the folder to be just '''MyZippedRepo'''.

If the above doesn't work, or for other cases, check for a readme file and have a look there for instructions.

Otherwise open the aircraft-set.xml file and search in it for paths containing '''Aircraft/AircraftFolderName'''. The name of the folder should match '''AircraftFolderName'''.

For instance if in the imaginary-set.xml you would find an instance like this:
<syntaxhighlight lang="xml">
<splash-texture>Aircraft/MyCreation/splash1.png</splash-texture>
</syntaxhighlight>
that means that you should rename the folder where imaginary-set.xml is to '''MyCreation'''.

=== XML files with wrong encoding ===
If you start FlightGear with the new plane you installed and there is no cockpit or exterior, this may be because the XML files are in the wrong encoding.

To fix this on Linux try this:
<syntaxhighlight lang="bash">
$ cd path/to/aircraft/directory/
$ find . -name "*.xml" -print | xargs sed -i 's/<?xml version="1.0" encoding="UTF-8"?>/<?xml version="1.0" encoding="ISO-8859-1"?>/g'
</syntaxhighlight>

If any of the methods above do not work, ask around on the [[Howto:Multiplayer#Multiplayer chat|multiplayer chat]], [[FlightGear IRC channel|IRC]] or on the {{forum link|f=11|text=forum}}.

== Choosing aircraft ==
If you are looking for information to decide what aircraft to download, try:
* [[Aircraft]]
* [[Helicopter]]
* [[Vehicle]]
* [[Table of models]]
External links to third party aircraft can be found at [[FlightGear hangars]]. Remember that the latest aircraft may not load with previous versions. If you happen to use an older version of FlightGear, look for older aircraft in the links section.

==Video tutorial by the community==
{{#ev:youtube|OiqGjc8W880|480px||Tutorial on downloading and installing aircraft from Github pages by PINTO. Adding manually downloaded aircraft folders in the [[FlightGear_Qt_launcher|qt-launcher]] is pretty much the same for non-github downloads too. Aircraft are often developed on Github. This shows you to the download Github versions of aircraft that are not in FGAddon yet for whatever reason, and the latest work-in-progress state of some aircraft in FGAddon for testing and feedback. (September 2019)}}

== Related content ==
* [[Installing Scenery]]

[[Category:Howto|Install aircraft]]

[[de:Howto:Flugzeuge Installieren]]
[[es:Cómo:Instalar_aviones]]
[[fr:Howto Installer un avion]]
[[pl:Instalowanie_samolotów]]

Howto:Install aircraft

2026-05-18T18:21:46Z

Fgf5: /* Manual installation process */ notes

{{installing}}

The preferred option to install the latest official [[aircraft]] is through the ''Aircraft'' tab in the [[FlightGear Qt launcher|built-in launcher]], as explained in the following video. The remainder of this article describes the manual process, only to be performed when you don't use the aircrafts from the official FGAddon hangar.

{{#ev:youtube|a-UIrw7nEy4}}

== Manual installation process ==

=== Linux ===
# Download the aircraft
# Create a directory to store your aircraft if you have not already done so. Make sure this directory is outside <tt>/usr/share/games/flightgear/</tt>. For example, use <tt>/home/{YourUserName}/FlightGear/CustomAircraft</tt>.
# Extract your aircraft file into the folder (the one you created above)
#: unzip XXXXX.zip
# Start up FlightGear with the launcher. In the launcher, go to the ''Add-ons'' tab. In the ''Additional aircraft folders'' section, click the ''Add'' button and select the main folder for additional aircrafts (in our case <tt>/home/{YourUserName}/FlightGear/CustomAircraft</tt>). Now your plane should appear on the list of planes, otherwise restart FlightGear.

Now, you just need to unzip the next downloaded aircraft in the same directory and it should already be visible on FlightGear.

=== macOS ===

# Download the aircraft
# Create a directory to store your aircraft if you have not already done so. Make sure this directory is somewhere you can find easily, For example, use <code>/Users/{YourUserName}/Aircraft</code>.
# Extract your aircraft file into the folder (the one you created above)
# Start up FlightGear with Launcher. In Launcher, go to the ''Add-ons'' tab. In the ''Additional aircraft folders'' section, click the ''Add'' button and select the main folder for additional aircrafts (in our case <code>/Users/{YourUserName}/Aircraft</code>). Now your plane should appear on the list of planes, otherwise restart FlightGear.

Now, you just need to unzip the next downloaded aircraft in the same directory and it should already be visible on FlightGear. This method is preferred over modifying FGData as it allows you to more easily access the aircrafts files, as well as having the benefit of persisting across FG updates, saving the hassle of having to redownload and install your aircraft each time you update FlightGear.

=== Windows ===
# Download an aircraft and save it on your desktop.
# Unzip the file using a file archiver, for example the open source file archiver [http://www.7-zip.org/ 7-Zip].
# Create a directory to store your aircraft if you have not already done so. Make sure this directory is outside your <tt>[[$FG_ROOT]]</tt> directory. For example, use <tt>C:\Users\{YourUserName}\FlightGear\CustomAircraft</tt>.
# Move the unzipped folder (usually the aircraft's name) to your that aircraft directory.
# Start up FlightGear with Launcher. In Launcher, go to the ''Add-ons'' tab. In the ''Additional aircraft folders'' section, click the ''Add'' button and select the main folder for additional aircrafts (in our case <tt>C:\Users\{YourUserName}\FlightGear\CustomAircraft</tt>). Now your plane should appear on the list of planes, otherwise restart FlightGear.

Now, you just need to unzip the next downloaded aircraft in the same directory and it should already be visible on FlightGear.

=== From the command line ===
If you launch FlightGear from the command line, use the <code>--fg-aircraft=path</code> option, which in our case can be: <code>--fg-aircraft=/home/{YourUserName}/FlightGear/CustomAircraft</code>.

=== Notes ===
The path added in the [[FlightGear Qt launcher|launcher]] should NOT end with the specific aircraft name. For example, if the aircraft path is <code>.../CustomAircraft/c182s</code>, you should select <code>.../CustomAircraft</code> instead of <code>.../CustomAircraft/c182s</code> in the launcher.

== When installing an aircraft fails ==
=== Rename aircraft folder ===
If FlightGear fails to start with the new aircraft you have installed, or if it starts but the aircraft is invisible you might have to rename the folder where the aircraft files are.
This issue is most often encountered when downloading a .zip file from some online git repository. In those cases you will most likely end up with a folder name of the following form MyZippedRepo-[branch]. In this case you should rename the folder to be just '''MyZippedRepo'''.

If the above doesn't work, or for other cases, check for a readme file and have a look there for instructions.

Otherwise open the aircraft-set.xml file and search in it for paths containing '''Aircraft/AircraftFolderName'''. The name of the folder should match '''AircraftFolderName'''.

For instance if in the imaginary-set.xml you would find an instance like this:
<syntaxhighlight lang="xml">
<splash-texture>Aircraft/MyCreation/splash1.png</splash-texture>
</syntaxhighlight>
that means that you should rename the folder where imaginary-set.xml is to '''MyCreation'''.

=== XML files with wrong encoding ===
If you start FlightGear with the new plane you installed and there is no cockpit or exterior, this may be because the XML files are in the wrong encoding.

To fix this on Linux try this:
<syntaxhighlight lang="bash">
$ cd path/to/aircraft/directory/
$ find . -name "*.xml" -print | xargs sed -i 's/<?xml version="1.0" encoding="UTF-8"?>/<?xml version="1.0" encoding="ISO-8859-1"?>/g'
</syntaxhighlight>

If any of the methods above do not work, ask around on the [[Howto:Multiplayer#Multiplayer chat|multiplayer chat]], [[FlightGear IRC channel|IRC]] or on the {{forum link|f=11|text=forum}}.

== Choosing aircraft ==
If you are looking for information to decide what aircraft to download, try:
* [[Aircraft]]
* [[Helicopter]]
* [[Vehicle]]
* [[Table of models]]
External links to third party aircraft can be found at [[FlightGear hangars]]. Remember that the latest aircraft may not load with previous versions. If you happen to use an older version of FlightGear, look for older aircraft in the links section.

==Video tutorial by the community==
{{#ev:youtube|OiqGjc8W880|480px||Tutorial on downloading and installing aircraft from Github pages by PINTO. Adding manually downloaded aircraft folders in the [[FlightGear_Qt_launcher|qt-launcher]] is pretty much the same for non-github downloads too. Aircraft are often developed on Github. This shows you to the download Github versions of aircraft that are not in FGAddon yet for whatever reason, and the latest work-in-progress state of some aircraft in FGAddon for testing and feedback. (September 2019)}}

== Related content ==
* [[Installing Scenery]]

[[Category:Howto|Install aircraft]]

[[de:Howto:Flugzeuge Installieren]]
[[es:Cómo:Instalar_aviones]]
[[fr:Howto Installer un avion]]
[[pl:Instalowanie_samolotów]]

Vehicle

2026-05-18T18:11:32Z

Fgf5: remove table of models

{{Stub}}
Visual examples of some of the [[FlightGear]] '''vehicles'''.


{{Model Gallery | section=vehicles}}

[[Category:Vehicles]]

[[de:Fahrzeuge]]
[[es:Vehículo]]
[[fr:Vehicules]]

''For the technical details about the menubar, see [[Menubar]].''

The in-game '''menu''' provides access to Flightgear's various features.

[[File:Menubar2.jpg|frame]]

= List of built-in menus =

Here is an incomplete list of FlightGear's menus, with links to their descriptions.

== File ==
* Reset
* [[Instant Replay#Continuous (disk-based) recordings|Flight Recorder Control]]
* Time Mode
* Screenshot
* Sound Configuration
* Input Devices
* [[TerraSync|Scenery Download]]
* Quit

== View ==
* Toggle Fullscreen
* Rendering Options
* View Options
* [[Cockpit view options|Cockpit View Options]]
* Toggle Glide Scope Tunnel
* [[Instant Replay]]
* [[Earthview|Earthview Orbital Rendering]]
* ALS Filter Effects

== Location ==
* Position Aircraft In Air
* Select Airport
* Random Altitude
* Tower Position

== Autopilot ==
* [[Autopilot#Autopilot Settings|Autopilot Settings]]
* [[Route Manager]]
* Previous Waypoint
* Next Waypoint

== Environment ==
* [[Weather]]
* Environment Settings
* [[Time|Time Settings]]
* [[Volcanoes]]

== Equipment ==
* [[Map]]
* Stopwatch
* Fuel and Payload
* Radio Settings
* [[GPS|GPS Settings]]
* Instrument Settings
* Light Switches
* [[Aircraft failure system|Random Failures]]
* [[Aircraft failure system|System Failures]]
* [[Aircraft failure system|Instrument Failures]]

== AI ==
* Traffic and Scenario Settings
* ATC Services in Range
* Wingman Controls
* [[AI Scenery Objects|AI Objects]]

== Multiplayer ==
* [[Multiplayer|Multiplayer Settings]]
* [[FGCom|FGCom Settings]]
* [[Chat Menu]]
* [[Pilot List]]
* [[Carrier over MP|MPCarrier Selection]]
* [[Swift|Swift Connection]]

== Debug ==
* Reload GUI
* Reload HUD
* [[Property Browser]]
* [[Nasal Console]]
...

== Help ==
* Aircraft Help
* [[Aircraft Checklists]]
* Common Aircraft Keys
* [[Tutorials]]
* About

= Related content =
* [https://flightgear.gitlab.io/getstart/release-{{current release|cr}}/en/HTML/getstart-ench5.html#menu-entries FlightGear Manual - Menu entries]

[[Category:FlightGear feature]]
[[Category:Menubar]]
[[Category:Lists]]

Sound

2026-05-17T21:58:47Z

Fgf5:

'''Sound''' can be either:
* Sound effects of [[Howto:Add sound effects to aircraft|aircraft]]
* Sound generated by [[Flite TTS|TTS]]
{{disambiguation|page-title=Sound}}

Sound

2026-05-17T21:58:26Z

Fgf5: disambiguation

'''Sound''' can be either:
* Sound effects of [[[[Howto:Add sound effects to aircraft|aircraft]]
* Sound generated by [[Flite TTS|TTS]]
{{disambiguation|page-title=Sound}}

Turbulence

2026-05-17T20:33:48Z

Fgf5: /* Adjusting turbulence severity */ link

Turbulence is fluid motion exhibiting chaotic changes in pressure and flow velocity, which affects aircraft.<ref>https://en.wikipedia.org/wiki/Turbulence</ref> By default, the severity of in-simulator turbulence is based on the weather.

== Adjusting turbulence severity ==
In the launcher, click "Settings" and add <code> --turbulence=n</code> to the command line at the bottom. The n is the severity of turbulence, from 0 to 1:
* none: 0
* light: 0.33
* moderate: 0.67
* severe: 1

If you want to change the severity during flight, press {{key press|/}} to open the [[property browser]], navigate to <code>/environment/config/presets/turbulence-magnitude-norm</code> and edit the value, then ensure <code>/environment/config/presets/turbulence-magnitude-norm-override</code> is set to <code>true</code>.

If [[advanced weather]] is enabled, the severity can be adjusted via "Environment > Weather > Advanced Settings".

== Related content ==
=== Wiki articles ===
* [[Weather]]

=== Forum topics ===
* [http://forum.flightgear.org/viewtopic.php?f=25&t=24659 Turning off turbulence]
* [http://forum.flightgear.org/viewtopic.php?f=69&t=28335 Turbulence numbers]
* [http://forum.flightgear.org/viewtopic.php?f=17&t=28807 Processing the option --turbulence=n.n]

[[Category:Weather]]
[[Category:Aviation]]

JSBSim Aerodynamics

2026-05-17T20:33:37Z

Fgf5: /* See also */ format

[[JSBSim]] provides a framework for aerodynamics. This page will attempt to explain how to translate traditional aerodynamics concepts into the [[JSBSim]] framework, and how to create [[FDM]]s that are sane for any flight value.

This page uses the term "coefficient" both the traditional sense of a constant multiplicative factor or in the [[JSBSim]] sense of the output of a function derived from a coefficient.

JSBSim provides three [[#Forces|Forces]] and three [[#Moments|Moments]] (a moment is a twisting or turning force), therefore it is a 'six degree of freedom' simulation.

== Frames ==
JSBSim incorporates several frame of reference. The body frame and wind frame are the most important to the aerodynamic model.
* '''Body XYZ''' The body frame uses the X axis for forward and aft, with + to the front. The Y axis is side to side with + to the right. The Z axis is up and down, with + being down. The origin of this frame is the Center of Gravity (CG), about which the aircraft forces and moments are summed and the resulting accelerations are integrated to get velocities.

* '''Wind XYZ''' The wind frame X-axis points directly into the relative wind. The Z-axis is perpendicular to the X-axis, and remains within the aircraft body axis XZ plane (also called the reference plane). The Y-axis completes a right hand coordinate system. The origin of this frame is the AeroRP.

* '''Wind UVW''' This isn't really a frame, but it is the components of the wind velocity vector. The relative wind is imposed on the body frame using variables U,V, and W. U to represent the velocity of the wind flowing past the aircraft. U represents the wind blowing down the X or longitudinal axis of the aircraft. V represents the wind blowing down the body frame Y axis, that is, wind in your ear. W represents wind blowing down the body frame Z axis, or wind from above.

== Angles ==
These two angles define the direction the relative wind is blowing in regard to the body frame.
* '''Alpha''' Alpha is the angle between the X body axis and the X wind axis measured on the UV plane. In standard aerodynamics Alpha is often referenced to the main wing chord line, this is not the case in [[JSBSim]].
* '''Beta''' Beta is the angle between the X body axis and the X wind axis measured in the UW plane.

== QBar ==
QBar, or dynamic pressure, is the product of velocity^2*(air density)/2
* '''QBarUW''' Use this value for formula involving Alpha. It is the value of QBar restricted to the vertical plane airspeed components contribution.
* '''QBarUV''' Use this value for formula involving Beta. It is the value of QBar restricted to the horizontal plane airspeed components contribution.
* It is possible to calculate other dynamic pressures for special purposes, such as QBarU for control surfaces.

The Greek letter rho or "ρ" is commonly used for air density. Normally, Qbar is based on the total free stream velocity, V[∞], so:

'''qbar = 1/2*ρ*(V[∞])^2'''

V[∞] is a vector and can be broken down into components commonly called U, V, W. By definition, U, V, and W are all at right angle to each other, so we use Pythagoras to say:

'''(V[∞])^2 = U^2 + V^2 + W^2'''

and rewrite

'''qbar = 1/2*ρ*(U^2 + V^2 + W^2)'''

QbarUV drops the vertical component, W, and just uses:

'''qbarUV = 1/2*ρ*(U^2 + V^2)'''

QbarUW drops the horizontal component and just uses:

'''qbarUW = 1/2*ρ*(U^2 + W^2)'''

And for the special case of qbarU, only use the axial component.

'''qbarU = 1/2*rho*(U^2)'''

Since its one dimensional, preserving the sign to show direction is valid:

'''qbarU = 1/2*ρ*(U*abs(U))'''

Qbar, qbarUV and qbarUW, can not have signs because they are multidimensional, use the reported alpha or beta angles to decide where the pressure is coming from.

== Metrics ==
The metrics section provides a standard place to record common aircraft dimensions. [[Aeromatic]] built [[FDM]]s only use four of the defined properties.
* Wing Area - metrics/Sw-sqft
* Wing Span - metrics/bw-ft
* Wing Chord - metrics/cbarw-ft
* AeroRP - the location where the aerodynamic forces are applied to the model. If this location is not exactly equal to the center of gravity (CoG) then moments, or twisting forces, will be created. Conventional aircraft need AeroRP to be aft of the CoG for stability.

Other dimensions [[Aeromatic]] creates but does not use are: (tail arms are used by the JSBSim Turbulence code)
* Horizontal Tail Area - Sh-sqft
* Horizontal Tail Arm - lh-ft
* Vertical Tail Area - Sv-sqft
* Vertical Tail Arm - lv-ft

Other elements in metrics:
* EYEPOINT - where G-forces are computed for the pilot
* VRP - the world position reported by JSBSim to FlightGear is for this location in the structural frame. Hence, the VRP location should match the origin of the coordinate system(s) used to position views, sounds and the 3d model in the FlightGear XML files.

<syntaxhighlight lang="xml">
<metrics>
<wingarea unit="{FT2 | M2}"> {number} </wingarea>
<wingspan unit="{FT | M}"> {number} </wingspan>
<chord unit="{FT | M}"> {number} </chord>
<htailarea unit="{FT2 | M2}"> {number} </htailarea>
<htailarm unit="{FT | M}"> {number} </htailarm>
<vtailarea unit="{FT2 | M}"> {number} </vtailarea>
<vtailarm unit="{FT | M}"> {number} </vtailarm>
<wing_incidence unit="{RAD | DEG}"> {number} </wing_incidence>
<pitot_angle unit="{RAD | DEG}"> {number} </pitot_angle>
<location name="{AERORP | EYEPOINT | VRP}" unit="{IN | M}">
<x> {number} </x>
<y> {number} </y>
<z> {number} </z>
</location>
{other location blocks}
</metrics>
</syntaxhighlight>

== Forces ==

For purposes of the Aerodynamics section the entire aircraft creates a single, unified aerodynamic force. This force is split into three component vectors. The most common way of splitting this force into vectors is the Lift Drag Side method. Another, potential better way from the perspective of generating a full 360 degree capable [[FDM]], is the Normal, Axial, Side method.
* '''Lift: CL''' Lift is the portion of the aerodynamic force that is at a right angle to the relative wind '''and''' lies within the x-z-axis plane (usually the aircraft's symmetry plane) '''and''' is oriented towards the aircraft's upside. (During inverted flight, it points to the ground).
** Lift is a function of QBar * Wing Area * Cllift. Cllift is generally derived from a 2D table as a function of AoA. In the real world it is also a function of the Reynolds and Mach Numbers. At least for unswept wings, using '''QBarUW''' is more appropriate for CL than the generic QBar. Otherwise, your aircraft will likely be prone to the issue [https://github.com/JSBSim-Team/jsbsim/issues/89 Pitch oscillations at rest, Brakes ON, with pure crosswind]. Swept wings might need a different treatment that we have not investigated further. ''However this has only been tested for the particular case of the c172, these are not universal laws but rather guidance or at the very least trouble shooting.''
* '''Drag: CD''' Drag is the portion of the aerodynamic force that is parallel to the relative wind.
** It is important to ensure all coefficient functions in the drag section remain positive. When drag coefficient functions are negative, drag is effectively acting as thrust opposite the relative wind.
* '''Side: CY''' Side is the portion of the aerodynamic force that is at a right angle to both the Lift and the Drag vector. It usually points to the aircraft's right side.

This system was developed by and for people using wind tunnels. Lift is to the top of the wind tunnel, drag is out the back and side is to the side. As a real aircraft in free space yanks and banks it may become ambiguous which direction the forces are applied. If an aircraft's body-x-axis is oriented exactly perpendicular to the relative wind, the definitions given above cannot be applied.

Enter the Axial, Normal, Side system.
* '''Axial: CA''' Axial force is the portion of the aerodynamic force that is parallel to the aircraft's longitudinal (X) axis. For very small angles of attack it is analogous to Drag.
* '''Normal: CN''' Normal force is the portion of the aerodynamic force that is parallel to the aircraft's vertical (Z) axis. For very small angles of attack it is analogous to Lift.
* '''Side: CY''' Side is the portion of the aerodynamic force that is parallel to the aircraft's lateral (Y) axis.

Which ever system is used, the forces are applied at the Aerodynamic Reference Point (AeroRP). If the AeroRP is not coincident to the model's center of gravity (CG), yaw, pitch and roll moments are created that do not appear in the moments sections.

== Moments ==
* '''Roll: Cl''' Aerodynamic rolling moment comes from multiple sources:
** One is the lift generated by the vertical tail. On most aircraft the center of pressure for the vertical tail is not on the X body axis. This sets up a moment arm creating a moment of (moment arm length)*(vertical tail lift force).
** Another roll moment source is main wing dihedral angle. If a dihedral wing encounters a sidewind component, let's say from the right, then the effective angle of attack will slightly increase for the right wing and decrease for the left wing. This is because - from the wing's perspective - the side wind component approaches the right wing from below (leading to an increase in AOA and more lift) and the left wing from above (leading to a decrease in AOA and less lift). Rolling the aircraft to one side will induce a side motion which leads to a resulting difference in lift, creating a roll moment counteracting the initial roll angle and providing roll stability.

* '''Pitch: Cm''' The primary contributor to the pitching moment is the lift generated by the horizontal tail. The pitching moment of the main wing airfoil is a secondary contributor. Because of this fact it makes sense that the value for Cm will resemble the CL curve for the horizontal tail airfoil. The standard CL curve does not take into account the changes in tail Angle of Attack (AoA) and QBar due to main wing down-wash and rotational velocity around the Y axis. At least for unswept wings, using '''QBarUW''' is more appropriate for Cm than the generic QBar. Otherwise, your aircraft will likely be prone to the issue [https://github.com/JSBSim-Team/jsbsim/issues/89 Pitch oscillations at rest, Brakes ON, with pure crosswind]. Swept wings might need a different treatment that we have not investigated further. ''However this has only been tested for the particular case of the c172, these are not universal laws but rather guidance or at the very least trouble shooting.''
* '''Yaw: Cn''' The primary contributor to the yawing moment is the lift generated by the vertical tail. The wind force on the fuselage is a secondary contributor. Because of this fact it makes sense that the value for Cn will resemble the CL curve for the vertical tail airfoil. Changes in QBar due to the vertical tail moving into the 'shadow' of a stalled main wing may need to be accounted for, as well. The source for vertical tail Angle of Attack (AoA) should be Beta and QBarUV is more appropriate for Cn than the generic QBar.

== Effects ==
* '''Stall''' - A 'stall' is generally regarded as a loss of lift due to flow separation over the top of a wing, however, examination of lift polar for an airfoil over a full 360 degrees shows that significant amounts of lift are NOT lost as the stall occurs. The biggest aerodynamic effect of a stall is a large and rapid increase in drag.

<syntaxhighlight lang="xml">
<hysteresis_limits unit="{RAD | DEG}">
<min> {number} </min>
<max> {number} </max>
</hysteresis_limits>
</syntaxhighlight>

* '''Spin''' - Spins are caused loss of stability in the Yaw Moment axis. A stock [[Aeromatic]] [[FDM]] yaw section does not take alpha into account when calculating the yaw moment.
* '''Aerodynamic Reference Point''' - JSBSim provides a way to shift the aerodynamic reference point (AeroRP) forward (negative values) and aft (positive) in response to mach, pitch or other influences. Use the tag <aero_ref_pt_shift_x> in the <aerodynamics> section. The value this tag function returns is internally multiplied by the chord entered in the <metrics> section to get the final shift. You could use this by setting the AeroRP to the leading edge of the wing and use a 1D table indexed by mach starting at .25 chord and getting bigger as the mach number increases to simulate mach tuck.

<syntaxhighlight lang="xml">
<aero_ref_pt_shift_x>
<function>
{function contents}
</function>
</aero_ref_pt_shift_x>
</syntaxhighlight>

*'''Lift Due To Elevator''' - There are two interrelated effects from elevator deflection, the Force change and the Moment. These have two different coefficients in two different sections of the FDM but should be considered together. The formula is:

CLde * lh-ft = Cmde * cbarw-ft

That is, the force (lift) created by the elevator times its length from the CG is equal to the moment. For some reason standard aerodynamics uses the chord as the reference length.

A similar formula:

CYdr * lv-ft = Cndr * bw-ft

Is applicable the rudder's side force and yawing moment. The force (side) created by the rudder times its length from the CG is equal to the moment. For some reason standard aerodynamics uses the wing span as the reference length.
{{JSBSim}}

== See also ==
* [[Aero input and outputs]]

Turbulence

2026-05-17T20:27:29Z

Fgf5: /* Adjusting turbulence severity */

Turbulence is fluid motion exhibiting chaotic changes in pressure and flow velocity, which affects aircraft.<ref>https://en.wikipedia.org/wiki/Turbulence</ref> By default, the severity of in-simulator turbulence is based on the weather.

== Adjusting turbulence severity ==
In the launcher, click "Settings" and add <code> --turbulence=n</code> to the command line at the bottom. The n is the severity of turbulence, from 0 to 1:
* none: 0
* light: 0.33
* moderate: 0.67
* severe: 1

If you want to change the severity during flight, press {{key press|/}} to open the [[property browser]], navigate to <code>/environment/config/presets/turbulence-magnitude-norm</code> and edit the value, then ensure <code>/environment/config/presets/turbulence-magnitude-norm-override</code> is set to <code>true</code>.

If advanced weather is enabled, the severity can be adjusted via "Environment > Weather > Advanced Settings".

== Related content ==
=== Wiki articles ===
* [[Weather]]

=== Forum topics ===
* [http://forum.flightgear.org/viewtopic.php?f=25&t=24659 Turning off turbulence]
* [http://forum.flightgear.org/viewtopic.php?f=69&t=28335 Turbulence numbers]
* [http://forum.flightgear.org/viewtopic.php?f=17&t=28807 Processing the option --turbulence=n.n]

[[Category:Weather]]
[[Category:Aviation]]

Turbulence

2026-05-17T20:26:35Z

Fgf5: add "adjusting turbulence severity" and remove old contents

Turbulence is fluid motion exhibiting chaotic changes in pressure and flow velocity, which affects aircraft.<ref>https://en.wikipedia.org/wiki/Turbulence</ref> By default, the severity of in-simulator turbulence is based on the weather.

== Adjusting turbulence severity ==
In the launcher, click "Settings" and add <code> --turbulence= n</code> to the command line at the bottom. The n is the severity of turbulence, from 0 to 1:
* none: 0
* light: 0.33
* moderate: 0.67
* severe: 1

If you want to change the severity during flight, press {{key press|/}} to open the [[property browser]], navigate to <code>/environment/config/presets/turbulence-magnitude-norm</code> and edit the value, then ensure <code>/environment/config/presets/turbulence-magnitude-norm-override</code> is set to <code>true</code>.

If advanced weather is enabled, the severity can be adjusted via "Environment > Weather > Advanced Settings".

== Related content ==
=== Wiki articles ===
* [[Weather]]

=== Forum topics ===
* [http://forum.flightgear.org/viewtopic.php?f=25&t=24659 Turning off turbulence]
* [http://forum.flightgear.org/viewtopic.php?f=69&t=28335 Turbulence numbers]
* [http://forum.flightgear.org/viewtopic.php?f=17&t=28807 Processing the option --turbulence=n.n]

[[Category:Weather]]
[[Category:Aviation]]

Volcanoes

2026-05-17T18:54:28Z

Fgf5: category

[[File:Volcanic_Activity_in_FlightGear.jpg|thumbnail|right|Volcanic Activity in FlightGear. Clockwise starting from bottom left: Kiluea, Kiluea, Etna (low level eruption), Beerenberg (high level eruption)]]
FlightGear is able to simulate different types and levels of [https://en.wikipedia.org/wiki/Types_of_volcanic_eruptions volcanic activity]. Activity can range from lava lakes and fountains, to small eruptions at newly forming islands like Surtsey, to the massive eruptions of Eyjafjallajökull which caused [https://en.wikipedia.org/wiki/Air_travel_disruption_after_the_2010_Eyjafjallaj%C3%B6kull_eruption severe disruption] of aviation in 2010. Advanced weather is able to simulate turbulent windfields associated with eruptions currently (2019/2020).

== Volcano list ==
{| class="wikitable"
|-
! Volcano !! Location !! Closest smaller airfields (ICAO) !! Close larger airports (ICAO) !! Volcano scenery state !! FG version added
|-
| [https://en.wikipedia.org/wiki/K%C4%ABlauea Kiluea] || Hawaii || Lihue (PHLI) || Hilo International (PHTO), Honolulu International || || 2018.1
|-
| [https://en.wikipedia.org/wiki/Mount_Etna Mount Etna] || Sicily, Italy || || Catania–Fontanarossa (LICC) || || 2018.1
|-
| [https://en.wikipedia.org/wiki/Stromboli Mount Stromboli] || Stromboli, Italy || || Lamezia Terme International (LICA), Catania–Fontanarossa (LICC) || || 2018.1
|-
| [https://en.wikipedia.org/wiki/Beerenberg Beerenberg] || Island of Jan Mayen, Norway || Jan Mayensfield (ENJA) || || || 2018.3
|-
| [https://en.wikipedia.org/wiki/Surtsey Surtsey] || Iceland || Vestmannaeyjar Airport (BIVM), Vik (BIVI) || Keflavík Airport (BIKF) || || 2019.2 nightly/2020.1
|-
| [https://en.wikipedia.org/wiki/Eyjafjallaj%C3%B6kull Eyjafjallajökull] || Iceland || Vik (BIVI) || Keflavík Airport (BIKF) || || 2019.2 nightly/2020.1
|-
| [https://en.wikipedia.org/wiki/Katla_(volcano) Katla] || Iceland || Vik (BIVI) || Keflavík Airport (BIKF) || || 2019.2 nightly/2020.1
|}

== Improving and adding volcanos ==

See {{forum link|title=Volcanos|t=32982}} for more information and future enhancements needing 3d model work.

== Gallery ==
<gallery mode=packed>
Kilauea_Lava_Lake,_Hawaii_(Flightgear_2019.x).jpg| Lava lake, Island of Hawaii, Hawaii
SOTM_2019-06_Ice_and_fire_by_vnts.jpg| Low level eruption of snowcapped Mount Etna in winter, Sicily
</gallery>

[[Category:Scenery]]
[[Category:Volcanoes]]
[[Category:Scenery enhancement]]

Volcanoes

2026-05-17T18:51:50Z

Fgf5:

Howto:Fly a helicopter

2026-05-15T14:58:18Z

Fgf5: /* Tail rotor controls */

{{note|Some updated helicopters in FGAddon: [[Alouette-III]] (AI [[Alouette-III#Amelia|copilot]] can assist with takeoff, hovering, and landing. Crash proof.) , [[Eurocopter EC135]] , [[Eurocopter EC130 B4]] (most detailed systems) , [[Robinson R22]] (A small helicopter that is popular for training because it is inexpensive. It is difficult to control, try one of the other helicopters first.) }}

[[File:SOTM-Sept17.jpg|thumb|[[Eurocopter_EC135|Eurocopter EC135]] around "weeping wall" waterfalls at Mount Waialeale on the lush island of Kauai, near PHLI. (FG 2017).]]

[[File:Alouette-lll_over_the_Carpathian_Mountains_in_Romania_in_Autumn_(Flightgear_2018.x).jpg|thumb|[[Alouette-III]] has an AI simulation of an (intentionally imperfect) [[Alouette-III#Amelia|human copilot]] that can assist people learning to fly helicopters to take off, hover, and land. (FG 2018)]]

[[File:EC_130_on_the_slope_of_a_shield_volcano_in_Hawaii_-_Flightgear_2018.x.jpg|thumb|[[Eurocopter_EC130|Eurocopter EC130]] on the slope of a shield volcano in Hawaii. The EC130 has the most detailed systems of helicopters available through FGAddon in Flightgear. (FG 2018)]]

[[File:Truman06.jpg|thumb|[[Eurocopter EC 135]] landing on the [[Howto:Carrier|carrier]] Harry S. Truman which is positioned off the island of O'ahu in Hawaii near Honolulu International Airport (PHNL). You can start on a carrier from the [[Howto:Carrier#From_the_launcher_.28Version_2020.1_and_later.29|launcher]] in Flightgear 2020.x.]]

[[File:EC135_Heer.jpeg|thumb|[[Eurocopter_EC135|Eurocopter EC135]] showing rotor downwash on grass. Individual grass blades react to the local windfield. Enable overlays to show grass (transparency anti-aliasing should be set to MSAA or higher). (FG 2020)]]

[[File:Alouette_gallery04.jpg|thumb|[[Alouette-III]] has a winch rope with a soft-body simulation of rope physics. Flightgear has a [[Cargo Towing Addon]] that will allow you attach ropes and move/assemble objects on a range of helicopters.]]

[[File:EC_130_in_Zurich,_Switzerland_in_Autumn_(Flightgear_2018.x).jpg|thumb|[[Eurocopter_EC130|Eurocopter EC130]] over Zurich in Switzerland. OSM2City output with buildings, roads, and other objects such as pylons for regions and entire countries are available for [[Areas_populated_with_osm2city_scenery|separate downloads]]. OSM2City for Flightgear 2020.x or later have buildings that render faster. For nice airports to start at and fly around with OSM2City see [[Suggested_airports#Developed_airports_situated_in_developed_regions|developed airports in developed regions]]. ]]

== Preface ==
In principle everything that applies to real helicopters, applies also to helicopters in [[FlightGear]]. It is important to be familiar with fundamental {{wikipedia|Helicopter flight controls|helicopter flight controls}}. Some details are simplified in FlightGear, in particular the engine handling and some overstresses are not simulated or are without any consequence.

[[File:bo105_cockpit.jpg]]

=== Control hardware ===

==== Stick and Pitch control ====

On the hardware side a use of a good [[joystick]] is recommended:A joystick without centering springs is recommended for cyclic control. You can achieve this with a normal joystick by removing or disabling the centring spring(s), or you could use a [[force feedback]] joystick with a disconnected voltage supply. Further, the joystick should have a “thrust controller” (throttle).

==== Tail rotor controls ====

For controlling the tail rotor you should have pedals, or at least a joystick that can twist in in a yawing motion. You may have to turn off auto-coordination, as you need full controls for the tail rotor. This can be done by clicking "Settings", then clicking the "Show more" button to the right of "General", and clicking "Enable auto-coordination" in the [[FlightGear Qt launcher|launcher]], or by adding the flag <code>--enable-auto-coordination</code> to the command line.

==== Joystick ====

While a joystick feels more natural, it won't have the same deflections like a real heli stick. In most cases it is even less, which makes the heli in FlightGear more difficult to control than the real thing. Usually the full control travel way of a real helicopter stick is between 6 inches and 11 inches depending on the helicopter. The deflections of a real heli stick can be also asymmetrical depending on the helicopter, while our joysticks always have symmetrical deflections.

==== Mouse ====

A mouse can be also used, Joystick and mouse has both advantages and disadvantages. The mouse won't feel natural, but you can change the control travel in <code>mice.xml</code> to your need. By decreasing the <factor> you can increase the control travel way and having less sensitive controls, which might improve the handling.

==== Keyboard ====

Flying helicopters by keyboard is not possible, as it won't provide sensitive enough control!

== Getting started ==

=== Launch ===

The number of available helicopters in FlightGear is increasing rather quickly. As helicopters have become more popular in FlightGear, many others have been developed. Each of them have their unique flight behaviour.

In my opinion the [[Eurocopter Bo105|Bo105]] is the easiest to fly, since it reacts substantially more directly than other helicopters.
The Bell UH-1 is also recommended, though behaving completely different as the Bo105. Nevertheless both models shows very realistic handling qualities, are tested by their real pilots, and their real counterparts are used in some armies for training of pilot novices.
The [[Robinson R44]], is also very easy to fly, although possibly unrealistically so.

Once you have loaded FlightGear, take a moment to centralize the controls by moving them around. However, as noted below, the throttle should be at maximum to equal the same as low throttle.

[[File:s76c_landed.jpg]]

=== Controls ===

The helicopter is controlled by four functions. The stick controls two of them, the inclination of the rotor disc (and thus the inclination of the helicopter) to the right/left and forwards/back. Together these functions are called [https://en.wikipedia.org/wiki/Helicopter_flight_controls#Cyclic cyclic blade control]. Next there is the [https://en.wikipedia.org/wiki/Helicopter_flight_controls#Collective collective blade control], which is controlled by the thrust controller. This causes a change of the thrust produced by the rotor. Since the powering of the main rotor transfers torque (as a twisting or turning force) to the fuselage, this must be compensated by the tail rotor. Since the torque is dependent on the collective and on the flight condition as well as wind can add additional torque on the fuselage, the [https://en.wikipedia.org/wiki/Tail_rotor tail rotor] is also controlled by the pilot using the pedals. If you push the right pedal, the helicopter turns to the right. The pedals are not a steering wheel. Using the pedals you can yaw helicopter around the vertical axis. The number of revolutions of the rotor is kept constant (if possible) by the aircraft.

[[File:ec135_in_the_air.jpg]]

=== Behavior of helicopters ===

Helicopters are natural unstable. It is like balancing a ball sitting on another bigger ball, which is sitting on a much bigger ball.
Every control input leads to another control input to compensate: So if you increase the collective, you have to push the pedals to compensate the torque. With this you are increasing
the tail rotor thrust and the helicopter wants to drift to the side. So you have to compensate this with the stick...And so on, and so on.

This makes helicopter flying much more difficult than fixed-wings. But with some practice it will become as easy as riding a bicycle!

== Lift-Off ==

{{Note|Increasing the throttle (pushing the throttle forward) will cause the helicopter to go down, not up. Likewise, decreasing the throttle (pulling back on the throttle) will cause the helicopter to go up.}}

First reduce the collective to minimum. To increase the rotor thrust, you have to “pull” the collective. Therefore for minimum collective you have to push the control down (that is the full acceleration position of the thrust controller). Equally, “full power” has the thrust controller at idle. Started the engine by pressing {{key press|<nowiki>}</nowiki>}}. After few seconds the rotor will start to turn and accelerates slowly. Keep the stick and the pedals approximately entered. Wait until the rotor has finished accelerating. For the Bo105 there is an instruments for engine and rotor speed on the left of the upper row. The RPM percentage of the rotor should be at 97-100%.

Once rotor acceleration is complete, pull the collective very slowly. Keep your eye on the horizon. If the heli tilts or turns even slightly, stop increasing the collective and correct the position/movement with stick and pedals. If you are successful, continue pulling the collective (slowly!).

As the helicopter takes off, increase the collective a little bit more and try to keep the helicopter in a levelled position. The main challenge is reacting to the inadvertent rotating motion of the helicopter with the correct control inputs. Only three things can help you: practice, practice and practice. It is quite common for it to take hours of practice to achieve a halfway good looking hovering flight. It should be noted that the stick position in a stable hover is not the centre position of the joystick.

{{Note|Making small inputs will lead you to success! Most helicopters are controlled just by small inputs by the fingers or the hand, the forearm resting on the thigh.}}

Quick Reference:
# Press {{key press|<nowiki>}</nowiki>}} to start the turbines; use Automatic startup from the aircraft menu or follow the specific startup tutorial, depending on the helicopter.
# Disengage parking or rotor brake. (If applicable)
# Wait for your turbine to come to full speed
# '''Push the throttle down, not up.''' Pushing up makes the chopper go down.
# When at desired altitude, push throttle to about 60%
# Fly freely

== In the air ==
To avoid the continual frustration of trying to achieve level flight, you may want to try forward flight. After take off continue pulling the collective a short time and then lower the nose a slightly using the control stick. The helicopter will accelerate forward. With forward speed the tail rotor does not have to be controlled as precisely due to the relative wind coming from directly ahead. Altogether the flight behaviour in forward flight is quite similar to that of a badly trimmed airplane. The “neutral” position of the stick will depend upon airspeed and collective.

Transitioning from forward flight to hovering is easiest if you reduce speed slowly by raising the nose of the helicopter. At the same time, reduce the collective to stop the helicopter from climbing. As the helicopter slows, “translation lift” is reduced, and you will have to compensate by pulling the collective. When the speed is nearly zero, lower the nose to the position it was when hovering. Otherwise the helicopter will accelerate backwards!

You may wonder about that the heli banking to the side. Don't worry, thats normal for helicopters. Due to the thrust of the tail rotor and the fins which also prevents the effect of the main rotor torque, the helicopter is pushed to one side. The helicopter would drift laterally. So to keep the heli straight you have to counteract this effect. That means you have to steer the helicopter so that you don't drift away- so bank the heli against the drift. The more tail rotor thrust you give, the more banking you will have. As an example while hovering. In cruise the fins will take over more and more the work of the tail rotor and will produce the same effect.

The side of the banking depends on the direction of turn of the main rotor: Counterclockwise --> left banking. Clockwise --> right banking.
That's the reason why on modern helicopters like the [[EC135]] the attitude indicator is even mounted with a bank on the panel.

== Back to Earth I ==
To land the helicopter transition to a hover as described above while reducing the altitude using the collective. Briefly before hitting the ground reduce the rate of descent slowly. A perfect landing is achieved if you managed to zero the altitude, speed and descent rate at the same time (gently). However, such landing are extremely difficult. Most pilots perform a hover more or less near to the ground and then decent slowly to the ground. Landing with forward velocity is easier, however you must make sure you don't land with any lateral (sideways) component to avoid a rollover.

Quick Reference
# Get to the airport
# Throttle up slowly to about 80%
# Keep it level
# Don't come down too hard
# Land and turn your turbines off by pressing {{key press|<nowiki>{</nowiki>}}

[[File:bo105_landed.jpg]]

== Back to Earth II ==
It is worth mentioning autorotation briefly. This is an unpowered flight condition, where the flow of air through the rotors rotates the rotor itself. At an appropriate altitude select a landing point (at first in the size of a larger airfield) and then switch the engine off by pressing {{key press|<nowiki>{</nowiki>}}. Reduce collective to minimum, place the tail rotor to approximately 0 degrees incidence (with the Bo push the right pedal about half , with Russian or French helicopters (like the [[Aérospatiale Alouette II|Alouette 2]]) the left). Approach at approximately 80 knots. Don't allow the rotor speed to rise more than a few percent over 100%, otherwise the rotor will be damaged (though this is not currently simulated).

As you reach the ground, reduce the airspeed by lifting the nose. The descent rate will drop at the same time, so you do not need to pull the collective. It may be the case that the rotor speed rises beyond the permitted range. Counteract this by raising the collective if required. Just above the ground, reduce the descent rate by pulling the collective. The goal is it to touch down with a very low descent rate and no forward speed. With forward speed it is easier, but there is a danger of a roll over if the skids are not aligned parallel to the flight direction. During the approach it is not necessary to adjust the tail rotor, since without power there is almost no torque. If you feel (after some practice), that autorotation is too easy, try it with a more realistic payload via the payload menu.

[[File:bo105_auto.jpg]]

==The real thing ==
Watch a pilot flying the real thing from his own perspective. Note the small inputs he is making. Before takeoff the stick is already centered at the needed position, due to the asymmetrical deflection it looks different than in FGFS: https://www.youtube.com/watch?v=HArfICZs5H4

== Challenging places to fly ==
Once you have mastered to take off and land safely, you might want to try more challenging places to take your heli. Here are a few suggestions:
* One of the [[aircraft carrier]]s
* An [[oil platform]] in the North Sea
* After all - [http://www.youtube.com/watch?v=j7aHqDkCzCw who needs a helipad?]

[[Category:Howto]]

[[de:Fliegen mit dem Helikopter]]
[[es:Volando el helicoptero]]
[[fr:Piloter l'hélicoptère]]
[[it:Pilotare un elicottero]]
[[nl:Vliegen met de helicopter‎]]
[[pl:Lot śmigłowcem]]
[[pt:Voando_de_Helicóptero]]

Howto:Fly a helicopter

2026-05-15T14:38:52Z

Fgf5: remove old contents

{{note|Some updated helicopters in FGAddon: [[Alouette-III]] (AI [[Alouette-III#Amelia|copilot]] can assist with takeoff, hovering, and landing. Crash proof.) , [[Eurocopter EC135]] , [[Eurocopter EC130 B4]] (most detailed systems) , [[Robinson R22]] (A small helicopter that is popular for training because it is inexpensive. It is difficult to control, try one of the other helicopters first.) }}

[[File:SOTM-Sept17.jpg|thumb|[[Eurocopter_EC135|Eurocopter EC135]] around "weeping wall" waterfalls at Mount Waialeale on the lush island of Kauai, near PHLI. (FG 2017).]]

[[File:Alouette-lll_over_the_Carpathian_Mountains_in_Romania_in_Autumn_(Flightgear_2018.x).jpg|thumb|[[Alouette-III]] has an AI simulation of an (intentionally imperfect) [[Alouette-III#Amelia|human copilot]] that can assist people learning to fly helicopters to take off, hover, and land. (FG 2018)]]

[[File:EC_130_on_the_slope_of_a_shield_volcano_in_Hawaii_-_Flightgear_2018.x.jpg|thumb|[[Eurocopter_EC130|Eurocopter EC130]] on the slope of a shield volcano in Hawaii. The EC130 has the most detailed systems of helicopters available through FGAddon in Flightgear. (FG 2018)]]

[[File:Truman06.jpg|thumb|[[Eurocopter EC 135]] landing on the [[Howto:Carrier|carrier]] Harry S. Truman which is positioned off the island of O'ahu in Hawaii near Honolulu International Airport (PHNL). You can start on a carrier from the [[Howto:Carrier#From_the_launcher_.28Version_2020.1_and_later.29|launcher]] in Flightgear 2020.x.]]

[[File:EC135_Heer.jpeg|thumb|[[Eurocopter_EC135|Eurocopter EC135]] showing rotor downwash on grass. Individual grass blades react to the local windfield. Enable overlays to show grass (transparency anti-aliasing should be set to MSAA or higher). (FG 2020)]]

[[File:Alouette_gallery04.jpg|thumb|[[Alouette-III]] has a winch rope with a soft-body simulation of rope physics. Flightgear has a [[Cargo Towing Addon]] that will allow you attach ropes and move/assemble objects on a range of helicopters.]]

[[File:EC_130_in_Zurich,_Switzerland_in_Autumn_(Flightgear_2018.x).jpg|thumb|[[Eurocopter_EC130|Eurocopter EC130]] over Zurich in Switzerland. OSM2City output with buildings, roads, and other objects such as pylons for regions and entire countries are available for [[Areas_populated_with_osm2city_scenery|separate downloads]]. OSM2City for Flightgear 2020.x or later have buildings that render faster. For nice airports to start at and fly around with OSM2City see [[Suggested_airports#Developed_airports_situated_in_developed_regions|developed airports in developed regions]]. ]]

== Preface ==
In principle everything that applies to real helicopters, applies also to helicopters in [[FlightGear]]. It is important to be familiar with fundamental {{wikipedia|Helicopter flight controls|helicopter flight controls}}. Some details are simplified in FlightGear, in particular the engine handling and some overstresses are not simulated or are without any consequence.

[[File:bo105_cockpit.jpg]]

=== Control hardware ===

==== Stick and Pitch control ====

On the hardware side a use of a good [[joystick]] is recommended:A joystick without centering springs is recommended for cyclic control. You can achieve this with a normal joystick by removing or disabling the centring spring(s), or you could use a [[force feedback]] joystick with a disconnected voltage supply. Further, the joystick should have a “thrust controller” (throttle).

==== Tail rotor controls ====

For controlling the tail rotor you should have pedals, or at least a joystick that can twist in in a yawing motion. You may have to turn off auto-coordination, as you need full controls for the tail rotor. This can be done by clicking "Settings", then clicking the "Show more" button to the right of "General", and clicking "Enable auto-coordination" in the [[launcher]], or by adding the flag <code>--enable-auto-coordination</code> to the command line.

==== Joystick ====

While a joystick feels more natural, it won't have the same deflections like a real heli stick. In most cases it is even less, which makes the heli in FlightGear more difficult to control than the real thing. Usually the full control travel way of a real helicopter stick is between 6 inches and 11 inches depending on the helicopter. The deflections of a real heli stick can be also asymmetrical depending on the helicopter, while our joysticks always have symmetrical deflections.

==== Mouse ====

A mouse can be also used, Joystick and mouse has both advantages and disadvantages. The mouse won't feel natural, but you can change the control travel in <code>mice.xml</code> to your need. By decreasing the <factor> you can increase the control travel way and having less sensitive controls, which might improve the handling.

==== Keyboard ====

Flying helicopters by keyboard is not possible, as it won't provide sensitive enough control!

== Getting started ==

=== Launch ===

The number of available helicopters in FlightGear is increasing rather quickly. As helicopters have become more popular in FlightGear, many others have been developed. Each of them have their unique flight behaviour.

In my opinion the [[Eurocopter Bo105|Bo105]] is the easiest to fly, since it reacts substantially more directly than other helicopters.
The Bell UH-1 is also recommended, though behaving completely different as the Bo105. Nevertheless both models shows very realistic handling qualities, are tested by their real pilots, and their real counterparts are used in some armies for training of pilot novices.
The [[Robinson R44]], is also very easy to fly, although possibly unrealistically so.

Once you have loaded FlightGear, take a moment to centralize the controls by moving them around. However, as noted below, the throttle should be at maximum to equal the same as low throttle.

[[File:s76c_landed.jpg]]

=== Controls ===

The helicopter is controlled by four functions. The stick controls two of them, the inclination of the rotor disc (and thus the inclination of the helicopter) to the right/left and forwards/back. Together these functions are called [https://en.wikipedia.org/wiki/Helicopter_flight_controls#Cyclic cyclic blade control]. Next there is the [https://en.wikipedia.org/wiki/Helicopter_flight_controls#Collective collective blade control], which is controlled by the thrust controller. This causes a change of the thrust produced by the rotor. Since the powering of the main rotor transfers torque (as a twisting or turning force) to the fuselage, this must be compensated by the tail rotor. Since the torque is dependent on the collective and on the flight condition as well as wind can add additional torque on the fuselage, the [https://en.wikipedia.org/wiki/Tail_rotor tail rotor] is also controlled by the pilot using the pedals. If you push the right pedal, the helicopter turns to the right. The pedals are not a steering wheel. Using the pedals you can yaw helicopter around the vertical axis. The number of revolutions of the rotor is kept constant (if possible) by the aircraft.

[[File:ec135_in_the_air.jpg]]

=== Behavior of helicopters ===

Helicopters are natural unstable. It is like balancing a ball sitting on another bigger ball, which is sitting on a much bigger ball.
Every control input leads to another control input to compensate: So if you increase the collective, you have to push the pedals to compensate the torque. With this you are increasing
the tail rotor thrust and the helicopter wants to drift to the side. So you have to compensate this with the stick...And so on, and so on.

This makes helicopter flying much more difficult than fixed-wings. But with some practice it will become as easy as riding a bicycle!

== Lift-Off ==

{{Note|Increasing the throttle (pushing the throttle forward) will cause the helicopter to go down, not up. Likewise, decreasing the throttle (pulling back on the throttle) will cause the helicopter to go up.}}

First reduce the collective to minimum. To increase the rotor thrust, you have to “pull” the collective. Therefore for minimum collective you have to push the control down (that is the full acceleration position of the thrust controller). Equally, “full power” has the thrust controller at idle. Started the engine by pressing {{key press|<nowiki>}</nowiki>}}. After few seconds the rotor will start to turn and accelerates slowly. Keep the stick and the pedals approximately entered. Wait until the rotor has finished accelerating. For the Bo105 there is an instruments for engine and rotor speed on the left of the upper row. The RPM percentage of the rotor should be at 97-100%.

Once rotor acceleration is complete, pull the collective very slowly. Keep your eye on the horizon. If the heli tilts or turns even slightly, stop increasing the collective and correct the position/movement with stick and pedals. If you are successful, continue pulling the collective (slowly!).

As the helicopter takes off, increase the collective a little bit more and try to keep the helicopter in a levelled position. The main challenge is reacting to the inadvertent rotating motion of the helicopter with the correct control inputs. Only three things can help you: practice, practice and practice. It is quite common for it to take hours of practice to achieve a halfway good looking hovering flight. It should be noted that the stick position in a stable hover is not the centre position of the joystick.

{{Note|Making small inputs will lead you to success! Most helicopters are controlled just by small inputs by the fingers or the hand, the forearm resting on the thigh.}}

Quick Reference:
# Press {{key press|<nowiki>}</nowiki>}} to start the turbines; use Automatic startup from the aircraft menu or follow the specific startup tutorial, depending on the helicopter.
# Disengage parking or rotor brake. (If applicable)
# Wait for your turbine to come to full speed
# '''Push the throttle down, not up.''' Pushing up makes the chopper go down.
# When at desired altitude, push throttle to about 60%
# Fly freely

== In the air ==
To avoid the continual frustration of trying to achieve level flight, you may want to try forward flight. After take off continue pulling the collective a short time and then lower the nose a slightly using the control stick. The helicopter will accelerate forward. With forward speed the tail rotor does not have to be controlled as precisely due to the relative wind coming from directly ahead. Altogether the flight behaviour in forward flight is quite similar to that of a badly trimmed airplane. The “neutral” position of the stick will depend upon airspeed and collective.

Transitioning from forward flight to hovering is easiest if you reduce speed slowly by raising the nose of the helicopter. At the same time, reduce the collective to stop the helicopter from climbing. As the helicopter slows, “translation lift” is reduced, and you will have to compensate by pulling the collective. When the speed is nearly zero, lower the nose to the position it was when hovering. Otherwise the helicopter will accelerate backwards!

You may wonder about that the heli banking to the side. Don't worry, thats normal for helicopters. Due to the thrust of the tail rotor and the fins which also prevents the effect of the main rotor torque, the helicopter is pushed to one side. The helicopter would drift laterally. So to keep the heli straight you have to counteract this effect. That means you have to steer the helicopter so that you don't drift away- so bank the heli against the drift. The more tail rotor thrust you give, the more banking you will have. As an example while hovering. In cruise the fins will take over more and more the work of the tail rotor and will produce the same effect.

The side of the banking depends on the direction of turn of the main rotor: Counterclockwise --> left banking. Clockwise --> right banking.
That's the reason why on modern helicopters like the [[EC135]] the attitude indicator is even mounted with a bank on the panel.

== Back to Earth I ==
To land the helicopter transition to a hover as described above while reducing the altitude using the collective. Briefly before hitting the ground reduce the rate of descent slowly. A perfect landing is achieved if you managed to zero the altitude, speed and descent rate at the same time (gently). However, such landing are extremely difficult. Most pilots perform a hover more or less near to the ground and then decent slowly to the ground. Landing with forward velocity is easier, however you must make sure you don't land with any lateral (sideways) component to avoid a rollover.

Quick Reference
# Get to the airport
# Throttle up slowly to about 80%
# Keep it level
# Don't come down too hard
# Land and turn your turbines off by pressing {{key press|<nowiki>{</nowiki>}}

[[File:bo105_landed.jpg]]

== Back to Earth II ==
It is worth mentioning autorotation briefly. This is an unpowered flight condition, where the flow of air through the rotors rotates the rotor itself. At an appropriate altitude select a landing point (at first in the size of a larger airfield) and then switch the engine off by pressing {{key press|<nowiki>{</nowiki>}}. Reduce collective to minimum, place the tail rotor to approximately 0 degrees incidence (with the Bo push the right pedal about half , with Russian or French helicopters (like the [[Aérospatiale Alouette II|Alouette 2]]) the left). Approach at approximately 80 knots. Don't allow the rotor speed to rise more than a few percent over 100%, otherwise the rotor will be damaged (though this is not currently simulated).

As you reach the ground, reduce the airspeed by lifting the nose. The descent rate will drop at the same time, so you do not need to pull the collective. It may be the case that the rotor speed rises beyond the permitted range. Counteract this by raising the collective if required. Just above the ground, reduce the descent rate by pulling the collective. The goal is it to touch down with a very low descent rate and no forward speed. With forward speed it is easier, but there is a danger of a roll over if the skids are not aligned parallel to the flight direction. During the approach it is not necessary to adjust the tail rotor, since without power there is almost no torque. If you feel (after some practice), that autorotation is too easy, try it with a more realistic payload via the payload menu.

[[File:bo105_auto.jpg]]

==The real thing ==
Watch a pilot flying the real thing from his own perspective. Note the small inputs he is making. Before takeoff the stick is already centered at the needed position, due to the asymmetrical deflection it looks different than in FGFS: https://www.youtube.com/watch?v=HArfICZs5H4

== Challenging places to fly ==
Once you have mastered to take off and land safely, you might want to try more challenging places to take your heli. Here are a few suggestions:
* One of the [[aircraft carrier]]s
* An [[oil platform]] in the North Sea
* After all - [http://www.youtube.com/watch?v=j7aHqDkCzCw who needs a helipad?]

[[Category:Howto]]

[[de:Fliegen mit dem Helikopter]]
[[es:Volando el helicoptero]]
[[fr:Piloter l'hélicoptère]]
[[it:Pilotare un elicottero]]
[[nl:Vliegen met de helicopter‎]]
[[pl:Lot śmigłowcem]]
[[pt:Voando_de_Helicóptero]]

World Scenery 3.0

2026-05-14T07:51:17Z

Fgf5: link

{{WS30 Navbar}}
World Scenery 3.0 is a project to replace the tiled single-mesh [[World Scenery 2.0]] with an [[Scenery LoD#WS3.0 LoD|LoD-based]] approach using a regular elevation mesh, landclass texture and vector line features.

This leverages OSG's Virtual Planet Builder and OpenStreetmap APIs.


== Currently Available Scenery ==

=== Terrain ===
Scenery is now distributed using the official [[TerraSync]], on next, automatic download does work. For manual download point your terrasync client to https://terrasync.b-cdn.net/ws3/.

Below you can find custom scenery that has been created before the global build and inclusion in terrasync.
{| class="wikitable"
|+
Currently Available World Scenery 3.0
!Scenery
!Area
!Size
!Bottom Left
!Top Right
!Area (degrees^2)
!Landclass Source
!Landclass Resolution (m)
!Raster format
!Comments
!Osm2city Scenery for WS3
|-
|[https://drive.google.com/file/d/1EapHG6qEYU6CWdXnp0_aqjUaX61Lk5EL/view?usp=sharing WS30_UK]
|UK and Eire
|1.5GB
| -11,49
|1,60
|121
|CORINE
|10
|PNG
|Includes detailed roads and water features.
|
|-
|[https://drive.google.com/file/d/120QOxfTWEm6EBmjK0eCNb07hrm3clavi/view?usp=sharing NL (terrain only)]
|Amsterdam and Lelystad
|716MB (ca. 8GB uncompressed)
|2,50
|10,53
|24
|CORINE
|10
|PNG
|Includes high resolution water raster from OpenStreetMap. Check out the canals!
|[https://drive.google.com/file/d/13inL4UqSyvRh5FVq62quVOYXnlEhxU1G/view?usp=sharing contains osm2city stuff incl. trees etc. also contains the static objects from Terrascync]. NB: contains also the terrain - no need to download the terrain seperatly (as per first column). Use with the new airport download and do NOT run on top of WS2.0 scenery.
|-
|[https://drive.google.com/file/d/1MrYuDKbMl4WhCEq9gnnt8Tz61lTAScvD/view?usp=share_link WS_Alps]
|
|49MB
|6,45
|8,47
|4
|CORINE
|25
|DDS
|
|
|-
|[https://drive.google.com/file/d/1x-kuCTfyMWddTi0fbr_nl41LR41Ylvwb/view?usp=share_link WS30_MTQ]
|Martinique
|7MB
| -62,14
| -60,15
|2
|CORINE
|10
|PNG
|Small French Caribbean island. One airport (TFFF)
|[https://drive.google.com/file/d/1QtojSTbnAAfkMzirQHnDJWbBDGOtnwIK/view?usp=sharing osm2city buildings, trees, maritime, pylons etc.] (ca. 40 MB).
|-
|[https://drive.google.com/file/d/14kbbgXbofDmqxho-bMCfOG4jDwcDqwBd/view?usp=share_link WS30_MTQ_25m]
|Martinique
|7MB
| -62,14
| -60,15
|2
|CORINE
|25
|PNG
|Small French Caribbean island. One airport (TFFF)
|(see above)
|-
|[https://drive.google.com/file/d/1-LS3yQZ0OkWX38Ne89n69wtrT7SreV69/view?usp=sharing WS_MTQ_5m]
|Martinique
|8MB
| -62,14
| -60,15
|2
|CORINE
|5
|PNG
|Includes high resolution water raster from OpenStreetMap. Small French Caribbean island. One airport (TFFF)
|(see above)
|-
|[https://drive.google.com/file/d/1Um7WC8h8Y4BlwgoVSd2xoVO5gTd3E-bI/view?usp=sharing Switzerland_5m]
|Switzerland plus small border
|1.4 GB (ca. 7 GB unzipped)
| 5.75,45.75
| 10.75,48
|10
|CORINE
|5
|PNG
|By mistake taken default airports. If you are using Nia's updated airports, then it will most often work fine, but there might be residuals with osm2city (e.g. tree on APRON).
|included
|-
|[https://de1mirror.flightgear.org/hosting/wayne/ WS3.0 USA]
|USA
|200 to 400 KB (zipped)
| 125,48
| 81,24
|
|NLCD, Tree Canopy Data
|30
|
|by state
|
|-
|[https://github.com/SP-NTX/PolandWS30/ Poland]
|Poland
|1.2GiB
|
|
|
|
|
|
|
|
|-
|[https://drive.google.com/file/d/1hDuTA9DVnAySxQvicqZK9u0JlE8irTqA/view?usp=sharing Scotland_5m]
|Scotland without Orkney/Shetland
|1.8 GB (ca. 16 GB unzipped)
| -8,54
| -1,59
|
|CORINE
|5
|PNG
|
|included
|-
|[https://drive.google.com/file/d/10M-K0XA_MQV8eCx4Xaidfje_4Uw2STQC/view?usp=drive_link WS30_FR]
|Mainland France
|3.5GB (ca 3.8GB unzipped)
| -5,43
|8,53
|129
|CORINE
|10
|PNG
|Terrain, water features and roads only
|
|-
|[https://drive.google.com/file/d/1NqBq8iEC6oqYCKgsllZfw5sT1lPPY5it/view?usp=sharing WS30_UG]
|Uganda and Lake Victoria
|1.3GB
|28,-4
|36,3
|56
|SENTINEL-2
|10
|PNG
|Terrain, water features and roads only
|
|}

=== Airports ===
In addition to the selected areas above, global up-to-date WS3.0 airports have been built. You can find them [https://us1mirror.flightgear.org/terrasync/ws3/ here]

=== Scenery Files Placement ===
Uncompress the downloaded scenery files into a folder of your choice, such as E:\MySceneryFolder. To be recognized by FlightGear, the selected scenery (from the table above) must be located in a folder with a "vpb" subfolder, such as (EX: C:\mysceneryfolder\hawaii\vpb). The scenery files above are compressed and include the "vpb" folder.

=== Installing ===
Using the [[FlightGear Qt launcher]] both the terrain and the airport are "installed" by going to tab "Add-ons" and then add the respective folders to "Additional scenery folders". When adding an additional scenery folder, you need to point to the folder immediately above the "vpb" subfolder.

If you add the airports the first time you might have to close the launcher and reopen it again to get the navigation data loaded properly into the session.

== Running World Scenery 3.0 ==
To run WS3.0 you need to set the <code>/scenery/use-vpb</code> property to <code>true</code> at startup. Either set <code>--prop:/scenery/use-vpb=true</code> on your command-line, or in the Launcher in "Settings" -> "Rendering" (you might need to click on "Show more" on the right side to see the choice for "Scenery version".

WS3.0 can use a lot of memory - significantly more than WS2.0. You can control the memory usage with the following properties:

* <code>/sim/rendering/max-paged-lod</code> controls the minimum number of objects that will be kept in memory. The default setting is 200.
* <code>/sim/rendering/plod-minimum-expiry-time-secs</code> controls how long objects remain loaded for after they are no-longer in view. The default value is 180 (3 minutes).

Reducing these properties will reduce the memory footprint of WS3.0.

If you have lots of spare cores, you can run multiple threads to load scenery by setting <code>/sim/rendering/database-pager/threads</code> to a number greater than 4 on startup. E.g. <code>--prop:/sim/rendering/database-pager/threads=8</code>.

=== WS 2.0 scenery might still be needed ===
To have airports displayed plus some of the default scenery objects, you might still want to have the WS 2.0 scenery for the same area installed.

However, if you want updated airports, checkout the global WS3.0 airports above. To avoid collisions you need to not have any WS2.0 airports enabled if you use these.

=== Using osm2city ===
WS3.0 has built-in support for OpenStreetMap roads, so you should not have it enabled in rendering settings.

You have 2 options:

* If you have WS2.0 world scenery, then it already contains osm2city buildings etc. You can just use these and live with slight elevation offsets.
* The other option is to use the provided osm2city scenery in the table above instead. If doing so you need to makes sure that WS2.0 osm2city has not been downloaded (or delete the folders manually). E.g. if you are using [[TerraMaster]] then you can remove the ticks in Settings for "Buildings", "Pylons" and "Roads".

Using the explicitly provided osm2city scenery gives you trees in gardens/parks and some improvements only available on NEXT.

== Related content ==
* [[Howto:Create WS3.0 terrain]]

Photoscenery

2026-05-14T07:50:46Z

Fgf5: removed out-of-date info

[[File:Brest.jpg|thumb|270px|A [[Cessna 172P]] flying over 1 m/pixel photoscenery of Brest, France.]]
'''Photoscenery''' is [[scenery]] in which orthoimagery (aerial photographs) is placed over the terrain.

== Why use photoscenery? ==
'''Advantages:'''
* Photoscenery shows the real world, it does not try to resemble it.
* Areas blend realistically, instead of a hard cut between urban and forest, or water and land for example.
* For VFR flight, more easy navigation in known locations because landmarks are more easily recognized.

'''Disadvantages:'''
* One needs large (or many) textures for high resolution scenery. For low level (VFR) flying, {{abbr|1 m/pixel|1 pixel spans 1 x 1 m}} is the absolute minimum.
* Orthoimagery is often hard to obtain, especially under an open license.
* The system running photoscenery has a higher memory (RAM) demand.

== Enabling photoscenery ==
Photoscenery can be enabled by navigating to the menubar: View, Rendering Options, and click on the Satellite Photoscenery checkbox.

This will load Photoscenery from your normal Scenery folders (subfolder "Orthophotos/").

== Obtaining orthoimagery ==
* [http://www.usgs.gov/ USGS], provides {{abbr|3 m/pixel|1 pixel spans 3 x 3 m}} imagery for the entire United States of America, released in the public domain (and thus GNU GPL compatible).

The prefered way of downloading these images depends on the used method Please read [[#Creating photoscenery|how to create photoscenery]], before starting.

{{note|The most easy and quick way nowadays is to install [https://julialang.org/ Julia] and use the [[Julia photoscenery generator]].}}

=== Preprocessing ===
* Since FlightGear adds haze to the scene, the textures should be "unhazed" to avoid double hazing.
* Shadows included in the images will conflict with shadows added by FlightGear. When creating small areas, shadows can be removed by hand from the textures, but this is usually undoable.

== Creating photoscenery ==
There are several ways of creating photoscenery for [[FlightGear]], of which some are discussed here.
{| class="wikitable"
! Feature
! [[#Texture overlays|Texture overlays]]
! [[#Texture materials|Texture materials]]
! [[#3D Model|3D Model]]
! [[Building FlightGear with osgEarth Integration|osgEarth]]

! Comment
|-
! style="text-align:left;" | Supported by stable FlightGear release (requires no patching)
| {{no}}
| {{no}}
| {{yes}}
| {{no}}
|
|-
! style="text-align:left;" | Toggle on run-time
| {{yes}}
| {{no}}
| {{yes}}
| {{yes}}
| With the current patch, the textures overlays are always loaded.
|-
! style="text-align:left;" | Water reflections, random buildings/trees
| {{yes}}
| {{no}}
| {{no}}
| {{no}}
| Depends on accuracy of underlying terrain (shapefiles)
|-
! style="text-align:left;" | Texture masks (not-so random objects)
| {{no}}
| {{yes}}
| {{no}}
| {{no}}
|
|-
! style="text-align:left;" | Requires no adapted scenery
| {{yes}}
| {{no}}
| {{no}}
| {{no}}
|
|-
! style="text-align:left;" | High resolution
| {{no|ca. {{abbr|4m/pixel|1 pixel spans 4 x 4 m}}}}
| {{yes|{{abbr|1m/pixel|1 pixel spans 1 x 1 m}} or higher|colspan{{=}}"2"}}
| {{yes}}
|
|-
! style="text-align:left;" | Advanced weather support
| {{yes}}
| {{no}}
| {{no}}
| {{no}}
| Depends on accuracy of underlying terrain (shapefiles)
|-
! style="text-align:left;" | Requires no custom materials file
| {{yes}}
| {{no}}
| {{yes}}
| {{yes}}
|
|}

=== Texture overlays ===
This method places the photo texture on top of the normal scenery. It requires [http://blaniel.free.fr/pub/flightgear/brest/ patches to be applied] to the FGData and SimGear sources.

# Calculate the tile bounds.
# Cut the orthoimagery to the bounds of the tile and save it with the name of the tile (for example <code>3023737.png</code>).
#: A 4096 x 4096 pixel texture gives roughly a 4 m/pixel resolution. Most graphics cards cannot handle larger textures, so when distributing the scenery this can be considered to be the limit. Tests on various machines showed that 16384 x 16384 pixel textures are possible (1 m/pixel).
# Mirror the texture upside down.
# Convert the texture to <code>.dds</code> via NVidia's nvcompress (part of the [http://developer.nvidia.com/legacy-texture-tools NVidia Tools]).
#: It was found that 16384 x 16384 pixel textures can not be processed by nvcompress. The [http://code.google.com/p/gimp-dds/ DDS plugin for GIMP] worked fine though.
# Place this texture next to the respective <code>.btg.gz</code> file.
Simply launch FlightGear with [[$FG_SCENERY]] set to your scenery directory. Disable all shaders in the ''Main Menu'' > ''View'' > ''Rendering Options'' dialog. Model and Water can be enabled, but all other shaders will disable the photoscenery.

{{note|Step 1 to 5 can be done by the photoscenery perl script from the {{sourceforge source|flightgear|fgscenery/tools|path=Photoscenery|text=FGScenery tools}}, when the imagery is obtained via a [http://en.wikipedia.org/wiki/Web_Map_Service Web Map Service] (WMS).}}

=== Texture materials ===
Another approach is to add each photo texture as a "material" in the <code>materials.xml</code> file.

# Calculate the tile bounds with the python scripts from http://fgphotoscenery.square7.ch/#howto.
#: When creating low resolution scenery ({{abbr|4 m/pixel|1 pixel spans 4 x 4 m}} or lower), a single 4096 x 4096 pixel texture can cover one tile. Higher resolution scenery requires the tile to be cut into smaller pieces: we'll call those photo tiles.
# Repeat the following steps for each single photo tile.
## Mirror the texture upside down.
## Convert the texture to <code>.dds</code> via NVidia's nvcompress (part of the [http://developer.nvidia.com/legacy-texture-tools NVidia Tools]).
## Create a shapefile with the size/location of the texture. Save the shapefile with an unique name (for example <code>302373_3_2.shp</code>, where the <code>3_2</code> indicates the horizontal/vertical tile id. This is not needed when using just one texture per tile).
# Generate the scenery with [[TerraGear]], using the shapefiles as input.
# Currently TerraGear does not create good UV maps, so some manual steps are needed:
# Import (one of) the <code>.btg.gz</code> file(s) in [[Blender]] via the [[Blender and BTG]] plugin.
## Correct the uvmapping of each single sub-tile. The map should cover the texture exactly.
## Export the file again. Please note that you cannot re-import the file after exporting, so do not close Blender before verifying that the UV mapping is correct!
# Create a <code>materials.xml</code> file for your project. For example <code>[[$FG_ROOT]]/Photoscenery/materials-nl.xml</code> for Dutch scenery.
# Add a material definition for each single sub-tile, like:
#: <code><nowiki><material><name>3023745_1_1</name><texture>NL/3023745/3023745.1.1.dds</texture></material></nowiki></code>
#: The texture path is relative to <code>[[$FG_ROOT]]/Textures</code>.
Now launch FlightGear with [[$FG_SCENERY]] set to the output directory of TerraGear and the command <code>--materials-file=Photoscenery/materials-nl.xml</code> (for example).

=== 3D Model ===
[[File:Prague 3D photoscenery.png|thumb|270px|Prague, using the 3D model method.]]
Instead of using the normal terrain, one could replace it by a big 3D model.
# Create a 3D model of the terrain and texturize it with the orthoimagery.
# Place the model as any other 3D object in the scenery.
# Remove the corresponding <code>Terrain/.../... .stg</code> file to hide the normal scenery.

== Projects ==
Several example photoscenery projects. The text between brackets indicates what method is used.
* [[Brest]], France (texture materials)
* [http://helijah.free.fr/flightgear/scenes.html Paris and surroundings], France (texture overlay)
* [http://flightgear-cz.wz.cz/ Prague], Czech Republic (3D Model)
* Selected places of the [http://fgphotoscenery.square7.ch/ United States of America] (texture overlay)

== Related content ==
=== Wiki articles ===
* [[Julia photoscenery generator]]

=== Forum topics ===
* {{forum link|t=39066|title=Photoscenery generator for Julia compiler}} (April 2021-) Programs to generate and manipulate photoscenery for FGFS
* {{forum link|t=38057|title=16k Photoscenery}} (September 2020-)
* {{forum link|t=37866|title=Photoscenery?}} (August 2020-) Discussing a patch that simplifies adding photoscenery, that later was added to FlightGear
* {{forum link|p=201862|title=Re: DDS for textures Rotterdam}} (February 2014)
* {{forum link|t=22784|title=A project to create a source of free geo-referenced instrument charts}} (April 2014-June 2014)

[[Category:Photoscenery]]
[[Category:Scenery]]

World Scenery

2026-05-14T07:44:06Z

Fgf5: /* World Scenery 3.0 */

'''World Scenery''' is the name of the corresponding Terrain and [[Scenery]] data for [[FlightGear]].
The latest published release is [[FlightGear_World_Scenery_2.0|World Scenery 2.0]] released in November 2013.

== World Scenery releases ==
* [[World Scenery 3.0]] - currently in Alpha testing
* [[World Scenery 2.0]] - November, 2013
* World Scenery 1.0.1 - October 27, 2008
* [[World Scenery v1.0.0]] - March 4, 2008
* World Scenery v0.9.10 - January 17, 2006

== Version Notes ==

=== World Scenery 3.0 ===
A new, LoD-based approach to scenery using landclass textures over a regular elevation mesh. For more information see [[World Scenery 3.0]].

=== World Scenery 2.0 ===
3D models on the terrain such as landmarks and airports are contributed and maintained under the Scenery Object database, with new World Scenery releases including updates to models since the last release. However, new models can usually be updated using the site before the next WS release.
=== World Scenery 1.0.1 ===
Released October 27, 2008, it works with [[FlightGear 1.9.0]] and [[FlightGear 1.0]], and probably some older releases although not all scenery objects may be fully supported. Elevation data for 1.0.1 uses SRTM3 version 2, SRTM30/GTOPO30 version 2 from ftp://e0srp01u.ecs.nasa.gov/srtm/version2/ .
=== World Scenery v1.0.0 ===
=== World Scenery v0.9.10 ===
Released 17th January 2006.

== Related ==
* [[FlightGear Scenery Database]]
== Links ==
* [https://www.flightgear.org/download/scenery/ Scenery Download at FlightGear.org]

[[Category:Scenery]]

JSBSim

2026-05-14T07:34:08Z

Fgf5:

'''JSBSim''' is an open source [[Flight Dynamics Model]] (FDM) software library that models the flight dynamics of an aerospace vehicle. The library has been incorporated into the flight simulation packages [[FlightGear]] and [http://www.openeaagles.org/ OpenEaagles]. It can also be called from a small standalone program to create a batch simulation tool. JSBSim has been in development and use since 1996, and has been built on all of the most popular platforms in use today including those running Linux, Macintosh, and Microsoft Windows operating systems. JSBSim is written in C++ and uses [[File Formats#|XML]] configuration files.

* JSBSim is also used by [[OpenEaagles]].
* [[JSBSim Commander]] is a software program for developing FDM for aircraft with JSBSim.

== Overview ==
JSBSim provides several different physics models which work together to calculate the overall vehicle dynamics.
* [[JSBSim Mass and balance|Mass Balance]] - This model uses weight (mass) to provide a force due to gravity and moments of inertia to damp changes in rotational velocity. Empty mass and inertia are specified, and point masses (which can have a shape and size) and fuel load are added in.

* [[JSBSim GroundReactions|Ground Reactions]] - JSBSim has a fairly simple system for ground reactions. You can have structural contacts which are uni-directional or bogeys which act only in a given direction. Both are modeled as spring and damper systems. Each bogey or structural contact provides a force on the vehicle when in contact with the ground. If the contact is not at the CG it also provides a rotating moment.

* [[JSBSim Engines|Propulsion]] - JSBSim models a variety of engine types using different methods. All engines provide a force along their X axis, and create moments if this force in not applied at the CG. The propeller and rotor thrusters also create turning moments.

* [[JSBSim Aerodynamics|Aerodynamics]] - JSBSim's aerodyamics are a blank slate. It is entirely up to the vehicle author to use valid formulas. The aerodynamic force is divided into Lift, Drag, and Side. You can also create Roll, Pitch and Yaw moments. In addition, if the aerodynamic force reference point is not coincident to the CoG the forces will create a hidden moment.

* [[JSBSim Buoyant forces|Buoyant forces]] - Lighter than air craft, e.g. gas balloons, pressure airships (e.g. blimps) and rigid airships, can be simulated with this model.

* [[JSBSim External forces|External forces]] - If the aerodynamic section is too limiting, or you want to simulate [[Towing|glider tow]] ropes, catapults or other things, you can add forces at arbitrary points.

* [[JSBSim Atmosphere|Atmosphere]] - JSBSim can be set up to use its own atmosphere model, or it can use an externally supplied model. There are three turbulence models to chose from.

* [[JSBSim Systems|Systems]] - A JSBSim system can implement any sort of model. This is a very useful facility as you can have any number of systems referenced from the aircraft configuration file. JSBSim Systems can be used to model items required in the FDM, and non-flight items, such electrics, hydraulics.

* Gravity - The G Force.

== Aeromatic ==

{| style="margin-top:0.1em; margin-bottom:0.1em; margin-left:2em; padding:2px; font-size:95%; text-align:left; background: transparent;"
|-
| [[File:1rightarrow.png|15px]] ''See [[Aeromatic]] for the main article about this subject.''
|}

[http://jsbsim.sourceforge.net/aeromatic2.html Aeromatic] can be used to create aircraft configuration files for use with the JSBSim Flight Dynamics Model. The configuration file format produced using this utility is version 2.0, and is incompatable with older formats because of an extensive overhaul of JSBSim's XML code that occured in December of 2004. Aeromatic is a online web tool, written in PHP, not a standalone program.

You will need at least three files for a complete configuration, an '''aircraft file''' containing information on the aircraft's mass properties, propulsion, flight control, aerodynamic properties, etc., an [http://wiki.flightgear.org/JSBSim_Engines engine file] describing the engine(s), and a [http://wiki.flightgear.org/JSBSim_Thrusters thruster file]. Thrusters can be rotors, propellers, nozzles or direct. All turbine engines use the default "direct" thruster. Piston, electric and turboprops need rotors or propellers. Rockets need nozzles. Aeromatic will generate plausible configuration files for your aircraft using some simplifying assumptions. Note that Aeromatic allows only one type of engine to be defined per aircraft. If you want to mix engine types you'll have to make the necessary changes by hand.

Be careful when tweaking the resulting configuration file, because it's easy to make changes that will result in an unflyable FDM. Common errors are: moving things around so they are not left/right symmetrical, and moving the CG too far away from the AeroRP.

== Related content ==
* [[JSBSim Aerodynamics|JSBSim Aerodynamics notes]]
* [[Aero input and outputs|JSBSim Aerodynamics input and outputs]]
* [[JSBSim GroundReactions]]
* [[JSBSim Engines|JSBSim Engine configuration]]
* [[JSBSim Thrusters|JSBSim Thruster configuration]]
* [[JSBSim Fuel System]]
* [[Howto: Write a fuel system in JSBSim]]
* [[DATCOM|DATCOM, lets you input many more variables than Aeromatic]]
* [[Howto: Setup winch and aerotowing for JSBSim-aircraft]]
* [[Howto: methods to replace the NASAL code with JSBSim code]]
* [[JSBSim Buoyant forces]]
* [[Howto:Modelling hydrodynamics in JSBSim]]

== External links ==
* [http://www.jsbsim.org/ JSBSim web site]
* [https://github.com/JSBSim-Team/jsbsim JSBSim site on github]
* [http://jsbsim.sourceforge.net/JSBSim/annotated.html JSBSim annotated reference] – Though meant for programmers, it also document the JSBSim xml markup language.
* {{cite web
| url = http://jsbsim.sf.net/JSBSimReferenceManual.pdf
| title = JSBSim – An open source, platform-independent, flight dynamics model in C++ (a.k.a. JSBSim Reference Manual v1.0)
| author = Jon S. Berndt and the JSBSim Development Team
| date = 9 July 2011 
| format = pdf
| accessdate = 15 January 2014
}} (WIP)
* {{cite web
| url = http://jsbsim.sourceforge.net/CreatingJSBSimAircraft.pdf
| title = A Journal for the Creation and Refinement of a JSBSim Aircraft Flight Model
| author = Jon S. Berndt
| format = pdf
| accessdate = 15 January 2014
}} Detailed report on an aircraft FDM improvement process.
* [http://jsbsimcommander.sf.net/ JSBSim Commander] (beta)
* [http://jsbsim.sourceforge.net/aeromatic2.html Aeromatic 0.95 (online)]
* [http://build.flightgear.org:8080/job/JSBSim-win/ws/dist/bin/aeromatic.exe AeromatiC++ 3.3.8 (Windows)]
* [http://build.flightgear.org:8080/job/JSBSim/ws/dist/bin/aeromatic AeromatiC++ 3.3.8 (Linux)]
* [http://www.holycows.net/datcom/ DATCOM+]

[[es:JSBSim]]

{{FDM}}

{{JSBSim}}

New to FlightGear

2026-05-14T07:31:01Z

Fgf5: menu item

'''Welcome to [[FlightGear]]!''' Here we will try to get you up in the virtual air in the shortest time possible. We will also introduce you to some of the features of this flight simulator and also a few information on its community.

== Installation and setup ==
=== Hardware requirements ===
For FlightGear to run smoothly, it requires a video card with OpenGL drivers 4.0 or higher. This is usually not a problem, but take a look at the [[hardware recommendations]] to have a better idea.

=== Getting FlightGear ===
You may download the latest files from the [https://www.flightgear.org/download/ FlightGear download] page. Choose the source or binary files appropriate for your particular system. {{Wikipedia|AppImage|AppImage}} binary files for Linux are also available with 2020.3 LTS and later. Most Linux users will find that most distributions have a packaged version of FlightGear (the package name could be <code>fgfs</code> or <code>flightgear</code>.)

Depending on your technical expertise you may choose the [[Git]] development version of FlightGear, which typically has more features and can be required by some of the latest developmental aircraft, but can be unstable and is more complicated to get for non-Windows users. In general, the development version is not advised to the average user, but if you are willing to do some testing there is a nightly build available for [https://www.flightgear.org/download/nightly/ download]. If you are using a Git version controlled copy of FlightGear, you may choose to synchronise your aircraft using the version controlled [[FGAddon|FGAddon aircraft development repository]].

=== Installing on Windows ===
After you downloaded the installer, run it and follow its instructions to install FlightGear.

Defender SmartScreen on Windows may block the installation simply because the binary file is not signed with a key that Microsoft respects. Of course, the key is paid. In this case, we need to click on the inconspicuous "More info" link. Only then will the "Run anyway" button appear. You can safely trust that this is not a dangerous application, as long as you have actually downloaded it from official sources.

If you're using third-party antivirus software for some reason, it may be blocking FlightGear from installing. This isn't something we can control, so it's entirely up to you how you want to handle it.

With the Windows installer, you may choose where to install FlightGear. The [[$FG_ROOT]] directory would be <code><your chosen directory>/data</code>.

=== Installing on macOS ===
Installing FlightGear on macOS is very simple. Just drag and drop the FlightGear icon to the <code>/Applications</code> folder. That is it.

The first time you launch FlightGear, its icon on the Dock bounces for several seconds while loading aircraft and airport info. When the GUI launcher appears, select the aircraft and airport, then click "Fly!" to launch the simulator. You can configure more options using the GUI launcher. See the [http://flightgear.sourceforge.net/manual/next/en/getstart-ench4.html#takeoff-how-to-start-the-program official manual] for more details.

If you would like to launch FlightGear using command-line, launch <code>/Applications/Utilities/Terminal.app</code> and type the following.

cd /Applications/FlightGear.app/Contents/MacOS
./fgfs --options.....

The [[$FG ROOT]] and [[$FG SCENERY]] are not set on macOS. If you want to specify these variables yourself for command-line use, run the followings on Terminal.app:

FG_ROOT=/Applications/FlightGear.app/Contents/Resources/data
FG_SCENERY=[[$FG_ROOT]]/Scenery

After launching the GUI launcher, you will have the alias to [[$FG_ROOT]] at <code>$HOME/Documents/Flightgear/<version></code> so you can browse the data folder using Finder.

Note: Once you have installed FlightGear, Mac users can locate their [[$FG_ROOT]] folder by opening their applications folder in Finder, right clicking on FlightGear, and clicking "Show Package Contents". This will take you inside the FlightGear folder. You are now able to access all files including Data/Aircraft to [[Howto: Install aircraft#Macintosh OS X|install new aircraft]].

=== Installing from source ===
Main article: [[Building FlightGear]]

=== Getting scenery ===
A limited set of [[scenery]] comes installed with FlightGear. For FlightGear 2024.1 this consists of
* The area surrounding the featured airport for the release which is [[Keflavik_Airport|Keflavik International Airport]] (BIKF)
* The tutorial airport for the [[Cessna_172P|Cessna 172P]] which is [[Hilo_International_Airport|Hilo International Airport]] (PHTO)

In FlightGear, scenery is generally stored in you [[$FG ROOT]] directory, and is divided into three kinds of data:
* '''Airports''' holds airport data, like runway usage and parking spots.
* '''Objects''' and '''Models''' are the buildings, bridges and radio towers, etc. that represent three-dimensional structures.
* '''Terrain''' represents the contours, elevations and type of ground you fly/taxi over.

The current way of "installing" new scenery is enabling [[TerraSync]], which will automatically download and update any place you visit - even on the fly! If you have a slow Internet connection and/or computer you could instead use a scenery manager, for example [[TerraMaster]]. In addition you can also manually download and install new scenery parts, either the official [[World Scenery]] or custom scenery.

The official, although outdated, scenery is available at [http://www.flightgear.org/download/scenery/ the scenery download section] of the FlightGear website, and can be installed following [[Howto: Install scenery]]. You may obtain additional and more up to date scenery objects as they become available through the [http://scenemodels.flightgear.org/ FlightGear Scenery Database]. '''This is recommended for users with weak internet connections or weak computers!'''

Custom scenery is available in many places. For example, on the {{forum link|f=5|text=FlightGear forum}} or within repositories. An internet search should be able to find them. See [[Suggested_custom_scenery|suggested custom scenery]] page for a few recent releases.

FlightGear 2020.3.7 LTS and later added an experimental rollout of 3 dimensional buildings, roads, and objects based on OpenStreetMap data for the entire world to automatically downloaded TerraSync data - see [[OSM2City 1st Worldbuild|1st OSM2City world-build]] notes (March 2021). Some manual downloads of 3d structures for regions or entire countries is available on the [[Areas populated with osm2city scenery|osm2City downloads]] wiki page.

=== Getting aircraft ===
Additional [[aircraft]] can be downloaded and installed through the [[Qt-launcher|launcher]]. Alternatively, you can go to the FlightGear website and navigate to the [http://www.flightgear.org/download/ download page], then choose the aircraft download link that fits your FlightGear version. In addition there are many third party [[hangars]]. For the installation, see [[Howto: Install aircraft]].

== Running FlightGear ==
=== Starting FlightGear ===
The easiest way to start FlightGear is to use the desktop icon. This starts the graphical interface [[FlightGear Qt launcher]] where you can choose aircraft, start position etc. Remember the Qt launcher only has basic options to get you started. A lot of options for graphics, scenery, [[Weather|weather]], [https://www.flightgear.org/tours/simulating-the-ever-changing-scenery/ environment], [[Input_device|input devices]] etc. are available from the [[menu]] inside the simulator.

Many users choose however to start FlightGear directly from the command line. The executable name is <code>fgfs</code> and can be run without options. If it is "not found", it is likely not in your [https://en.wikipedia.org/wiki/PATH_(variable) path]. The location depends on your particular system and choices you made during compile and installation. There is a list of [[Command Line Parameters]] which must be used to change many options, like the aircraft you want. The most important:

fgfs --launcher # opens the FlightGear Qt launcher
fgfs --show-aircraft # displays a list of installed aircraft
fgfs --aircraft=c172p # start FG with the aircraft "c172p" (from the list)

The Qt launcher also lets users add command line parameters for options that are normally changed from the menu inside the simulator, as well as quite advanced options that are only available from the command line (as of August 2020).

=== Configuring rendering and UI ===
[[File:Rendering options 2024.1.png|thumb|View > Rendering Options dialog.]]
If your render quality or framerate is too low, click "View > Rendering Options" to adjust the graphic settings. For newer hardware, it's recommended to set "graphics quality" to high and check "use disk space for faster loading", "animated jetways" and "satellite photoscenery".

If the menu text appears too small on high DPI or large screens, you can manually [[Menubar#How to Change the Default Menubar Font Size|change the menubar font size]] by editing the data file, or simply click "Debug > Cycle GUI Style".

=== Using the keyboard and/or mouse ===
Users with limited access to a [[joystick]] or other controllers sometimes use the keyboard or mouse to control their aircraft. Using the keyboard to fly can be difficult and the mouse is recommended over the keyboard for flying, yet even a cheap joystick would improve the experience so much.

To get help with keyboard commands, with FlightGear running, go to the ''Help'' menu, look under ''Basic Keys'' (for simulator related commands) and ''Common Aircraft Keys'' (for commands universal to all aircraft) and ''Aircraft Help'' (for key commands specific to your aircraft). If the main menu is hidden press {{key press|F10}}. If you come from other simulators, check [[key commands compared to other simulators]] for an overview of the difference between the key commands of that sim and FlightGear.

To use the mouse to fly the aircraft, press {{key press|Tab}} (the cursor should change to a cross) and move the mouse to direct the aircraft. Press {{key press|Tab}} again to look around (cursor should show a two sided arrow), and press {{key press|Tab}} again to return to normal mode, used to click stuff in the cockpit. In some aircraft, such as the [[A320neo]] and [[Airbus A330 (disambiguation)|A330]] this unfortunately will not work, so you will have to use right click to look around and mouse mode is disabled. Fortunately, those planes are airliners, which are really stable and easy to fly with the keyboard.

For most users lacking a rudder axis control, it’s difficult to manually coordinate [[aileron]] and [[rudder]] movements during a turn. To enable auto-coordination and make flight easier, you may click "Settings", then click the "Show more" button on the right of "General", and finally click "Enable auto-coordination" in the launcher.

=== First time in the cockpit ===
Finding your way around the cockpit can be daunting the first time.

Where is the "virtual cockpit"? Not all FlightGear aircraft come with an interior actually, some research projects may not even come with an exterior model. A 2D panel may display over the 3D cockpit if one exists. You may turn this off through ''Main Menu'' > ''View'' > ''View Options'' and deselecting ''Show 2D panel'' in the ''Display Options'' section, or by pressing {{key press|Shift|P}}. Otherwise, you should be sitting in the virtual cockpit when FlightGear starts, as long as the Cockpit View is selected (if not pressing {{key press|Ctrl|V}} should get you to the pilot view).

You may find it difficult to read some of the displays, dials and gauges on the instrument panel. You can use the ''view'' mode of the mouse (press {{key press|Tab}} until you get a cursor shaped like a double arrow) to pan and the mouse wheel to zoom, or pan with the joystick hat and zoom with {{key press|X}} and {{key press|Shift|X}}.

One of the first steps that many take on entering an unfamiliar cockpit is to press {{key press|Ctrl|C}} to highlight all the "hotspots", that is instrument controls, buttons, knobs, etc. Many aircraft also offer a specific help menu.

Some functions, such as starter or magneto, may be difficult to use or simply lack clickable "hotspots", especially in aircraft models which are in development. In most cases you can go for the equivalent controls on a 2D panel or resort to the keyboard. The keyboard always work according to the assignments listed on the ''Help'' menu, but sometimes these are reassigned by an aircraft or configuration. Again, remember to check all the help dialogs.

=== Starting the engine ===
You are eager to fly, but the engine is off. Well, turning on the engines is not always easy. Some aircraft have an ''autostart'' entry in their custom menu, but here is a general procedure that should work in many cases:

In general to start the engine on a piston-engine type aircraft, you need (after making sure the game is not paused {{key press|p}}):
# Fuel: Some aircraft start the simulation with no fuel. You can add it in ''Equipment'' > ''Fuel and Payload''.
# Correct fuel mixture: This is generally ''rich'', so push the red knob all the way in, or use the key {{key press|m}} to enrich ({{key press|Shift|m}} leans.)
# Magnetos set on ''both'': Turn the key or press {{key press|}}} ''three times'' to move through ''R'', ''L'', ''Both''.
# Throttle: Some engines start better with a little gas.
# Run the starter: Click the ''Start'' position of the key on the panel, or press {{key press|s}}. Hold the starter for sufficient time, even 10 seconds.

Starting all engines in a multi-engine aircraft is similar to the single engine - except you must follow the same start sequence for each and every engine. FlightGear provides a convenient way to do this for all engines at once: Press {{key press|~}} and all the procedure above will work for all the engines. Note though that the default 2D panel is connected to ''only one engine'' and the {{key press|~}} trick might not work. Also, give some gas to be sure that all the engines are on.

These instructions may not work for jet aircraft, helicopters, or other types of aircraft with complex start procedures. Check the instructions in the aircraft help menu (press {{key press|?}}) and/or look at [[Aircraft|the aircraft's article on this wiki]]. In general to start the engine on a jet engine type aircraft, you need to:
# Set cutoff ''ON''
# Engage the starter
# Once the engines spools up to approximately 5% N1, set cutoff ''OFF''
# Disengage the starter once the engine has reached operational speed

== Learning to fly ==
=== FlightGear's Manual ===
FlightGear has an official [https://www.flightgear.org/support/manual/ manual] that covers the basics of flight. As a beginner, you may want to start with "Chapter 8: A Basic Flight Simulator Tutorial."

=== Tutorials ===
Many aircraft have their own interactive [[tutorials|tutorial]]. With tutorials, you can learn to operate particular aircraft but also learn to fly. You can access tutorials by going to ''Main menu'' > ''Help'' > ''Tutorial''. A great place to start is the tutorial for the [[Cessna 172P]] aircraft, commonly used in real life to learn to fly fixed-winged aircraft.

If the tutorial starts without a runway and surrounded by water, your setup of FlightGear is missing the scenery for the airport at which the tutorial was supposed to run. To get scenery see the [[#Getting scenery]] section above.

== Making your first flight ==
=== Realism ===
One of the most frequent questions novice pilots ask about any flight simulator, but more so to FlightGear, is "Why is my aircraft turning left all the time?" Although it could be due to wind gusts crossing the runway, it is more likely due to the [[Understanding Propeller Torque and P-Factor|propeller torque and p-factor]].

In certain other flight simulators, despite marketing slogans to the contrary, some settings are turned down to make the aircraft easier to fly. This reduces effects such as the above. The realism is always turned up in FlightGear.

Here are some of the FlightGear realism points, which may be confusing to first time pilots:
* "Left turning syndrome" for the previously mentioned reasons.
* Compass turning error: A compass, when subjected to the forces of flight, tends to turn in the opposite direction for a brief period before settling on the correct heading. This is not a malfunction (see also the Wikipedia article {{wikipedia|Aircraft compass turns}}).
* The Vertical Speed Indicator (VSI) is also subject to error.
* The [[Horizontal Situation Indicator]] (HSI) is driven by a gyroscope (that is why it is sometimes called a Directional Gyroscope), which is subject to ''gyro drift''. The indicator will drift from its current heading and must be periodically (every ~15 minutes) calibrated to agree with the magnetic compass heading.
* You cannot just cancel a turn or climb by centering the yoke or stick. You must turn or push the stick the other way to get to level and level flight. But even then, the plane will not maintain its altitude or heading by itself. A common mistake is trying to find a hands off yoke position. While with trimming one could leave the plane for a couple of seconds, one must use autopilot or constantly adjust the yoke.

Many forces act on an aircraft in flight as well as on the [[avionics and instruments]] used for control and navigation, and may be counter-intuitive. Pilots must learn to recognize these phenomena and compensate for their effects. ''FlightGear models instrument errors that exist in the real world''.

=== Airports and navigation aids ===
When you first start FlightGear, whether from the command line or the graphical interface of the launchers, you may wonder how to determine what airports are available. The launcher displays a list of airports, but you will not see details such as tower or [[ILS]] frequencies. You will not find a map showing [[VOR]]s and their frequencies. What can you do? See [[Getting aeronautical charts]].

In-sim, there is a map you can use in ''Main Menu'' > ''Equipment'' > ''Map'', which will allow you to see navigation data and the position of airports and aids. For more help with navigation see [[Understanding navigation]].

=== Flying using the autopilot ===
Some aircraft require you to use the [[autopilot]] available from the ''Autopilot'' menu, which is the original FlightGear autopilot. This is a ''generic'' autopilot and as such, many aircraft come with their own ''specific'' autopilot, frequently a model of the real life one.

For aircraft that provide their own autopilot, you should use the autopilot controls available in the virtual cockpit. This means clicking on the instrument panel in the virtual cockpit. The Autopilot menu will be grayed out and unavailable when the aircraft supplies its own autopilot in some aircraft, including the Airbuses and the [[Cessna 172P|C172P]].

The Cessna 172 comes with a [[Bendix/King KAP140 Autopilot]] in its virtual cockpit. You can use both the autopilot device in the cockpit and the [[Autopilot#Autopilot Settings|autopilot settings]] from the menu.

== Advanced ==
=== Flying ===
{{Main article|Aircraft}}

* If you continue to fly light civilian aircraft, [[Cessna 182S]] which is more complex than C172P and [[Piper PA28 Warrior II|PA28]] are good choices.
* If you are interested in flying airlines, [[Airbus A320 family]], Boeing [[Boeing 777|777]]/[[Boeing 787-8 Dreamliner|787]], [[MD-11]] and [[MD-80]] are suggested.
* If you are fascinated by fighter aircrafts, choose a highly rated military aircraft (such as [[F-15]]) from [[Aircraft#Modern military aircraft|here]] and install [[Bombable]] if possible.
* If you switch to helicopters, it is recommended to fly [[Eurocopter EC130 B4]].

=== Scenery ===
It is fascinating to explore the [[scenery]] (or just test the graphics/frame rate) with [[UFO]]. First of all, [[#Configuring rendering and UI|increase your graphics quality]]. If you don't see buildings initially, keep FG open and wait for a while for [[TerraSync]] to finish downloading and for the buildings to appear.
There are plenty of [[Suggested airports|well-developed airports]] and scenery areas. You can also explore the scenery objects on the [https://scenery.flightgear.org/map model map].

=== Multiplayer ===
FlightGear has some multiplayer servers that will let you fly in more lively skies, see [[Howto: Multiplayer]]. There are also [[OpenRadar]] and [[ATC-pie]], standalone programs that will let you be an [[Air traffic control|air traffic controller]].

There is also a [[MPMap|multiplayer map]] that lets you see who is online right now, and even what [[navaids]] are nearby.

=== Menu items ===
For a quick reference about the usage of each menu item in FlightGear, see [[menu]].

=== Addons ===
FlightGear has a lot of third-party [[Addon|addons]] containing enhancements. For beginners, [[Logbook Add-on|Logbook]] that records your flights may be the most useful.

== The FlightGear community ==
=== Getting help ===
This page is designed to give the user the essential things they need to know about using FlightGear for the first time. Besides the [[Portal:User|User portal]] of this wiki, there are other pages you may want to read:
*[[Troubleshooting problems]] to help you with the most common issues;
*[[Frequently asked questions]];
...and communication channels that can be used to obtain information or request help:
*The [[FlightGear Manual]], a ''must read'' for beginners;
*{{forum link|text=FlightGear Forum}} and its subforums;
*[[Discord|FlightGear's Discord server]], the quickest way to get help;
*[[FlightGear IRC channel]];
*[[Mailing list|FlightGear users mailing list]], biggest chance to get in contact with core developers;
*Documents bundled with the release package.

=== Customizing FlightGear without compiling it ===
[https://www.flightgear.org/download/ Our website] offers precompiled binaries for download and install on Windows, macOS and Linux. In addition, most Linux distributions provide a packaged version in their repositories.

Although the install is binary, most of FlightGear's systems are open to configuration through [[XML]] files and [[NASAL scripting]]. You are free ''and encouraged'' to make changes to aircraft flight models, scenery, textures, OpenGL [[shader]]s and any other feature you wish to change for your personal satisfaction or to share with other FlightGear users. If this is what you intend to do, take a look at the [[Portal:Developer|Developer portal]].

=== How you can help ===
{{Main article|Volunteer}}
FlightGear is an open source, volunteer based project. That means that whatever you find here comes from passion, spare time and nothing else. This includes the simulator, the scenery, the aircraft, the wiki, the {{forum link|text=forum}} and everything else. Volunteers, in essence ''people that do things'', are fundamental to this project. Without them, it would not make a single step forward. So it is essential that contributors have fun in what they do.

If you plan to contribute to this project, you should take a look at some articles that will give you some hints:
*[[Howto:Understand the FlightGear development process]]
*[[Implementing new features for FlightGear]]
*[[How the FlightGear project works]]

There are never enough people contributing, and the fields where their help would be appreciated are many:
;Testing:
*[[Building FlightGear|Build]] the latest Git code
*[https://gitlab.com/flightgear/flightgear/-/issues File bug reports]
*Running FlightGear via valgrind to track down memory leaks

;Support:
*Help new users with downloading, compiling, installing and running FlightGear ({{forum link|text=on the forum}} or on [[Discord]])
*Provide ideas & suggestions, see: [[Feature Requests / Proposals / Ideas]]
*Help [[Portal:Wiki|clean up this wiki]]
*Help provide new contents for missing wiki pages

;Development:
*C/C++ Coding:
**Provide source code cleanups
**Provide bug fixes [[Bugs]] or new features
**Get involved in any of the other FlightGear-affiliated projects
*Aircraft development (3D modeling, textures, FDMs, scripting)
*Scenery development (terrain, model, weather)

[[Category:FlightGear]]

[[ca:Nou a FlightGear]]
[[de:Neu bei FlightGear]]
[[es:Nuevo en FlightGear]]
[[fi:Uusi_käyttäjä]]
[[fr:Nouveau sur flightgear]]
[[it:Nuovo per FlightGear]]
[[ja:FlightGear入門]]
[[nl:Nieuw bij FlightGear]]
[[pl:Nowy w FlightGear]]
[[pt:Novo no FlightGear]]
[[sr:Novi u FlightGear-u]]
[[th:New to FlightGear]]

New to FlightGear

2026-05-12T21:25:17Z

Fgf5: /* Addons */

'''Welcome to [[FlightGear]]!''' Here we will try to get you up in the virtual air in the shortest time possible. We will also introduce you to some of the features of this flight simulator and also a few information on its community.

== Installation and setup ==
=== Hardware requirements ===
For FlightGear to run smoothly, it requires a video card with OpenGL drivers 4.0 or higher. This is usually not a problem, but take a look at the [[hardware recommendations]] to have a better idea.

=== Getting FlightGear ===
You may download the latest files from the [https://www.flightgear.org/download/ FlightGear download] page. Choose the source or binary files appropriate for your particular system. {{Wikipedia|AppImage|AppImage}} binary files for Linux are also available with 2020.3 LTS and later. Most Linux users will find that most distributions have a packaged version of FlightGear (the package name could be <code>fgfs</code> or <code>flightgear</code>.)

Depending on your technical expertise you may choose the [[Git]] development version of FlightGear, which typically has more features and can be required by some of the latest developmental aircraft, but can be unstable and is more complicated to get for non-Windows users. In general, the development version is not advised to the average user, but if you are willing to do some testing there is a nightly build available for [https://www.flightgear.org/download/nightly/ download]. If you are using a Git version controlled copy of FlightGear, you may choose to synchronise your aircraft using the version controlled [[FGAddon|FGAddon aircraft development repository]].

=== Installing on Windows ===
After you downloaded the installer, run it and follow its instructions to install FlightGear.

Defender SmartScreen on Windows may block the installation simply because the binary file is not signed with a key that Microsoft respects. Of course, the key is paid. In this case, we need to click on the inconspicuous "More info" link. Only then will the "Run anyway" button appear. You can safely trust that this is not a dangerous application, as long as you have actually downloaded it from official sources.

If you're using third-party antivirus software for some reason, it may be blocking FlightGear from installing. This isn't something we can control, so it's entirely up to you how you want to handle it.

With the Windows installer, you may choose where to install FlightGear. The [[$FG_ROOT]] directory would be <code><your chosen directory>/data</code>.

=== Installing on macOS ===
Installing FlightGear on macOS is very simple. Just drag and drop the FlightGear icon to the <code>/Applications</code> folder. That is it.

The first time you launch FlightGear, its icon on the Dock bounces for several seconds while loading aircraft and airport info. When the GUI launcher appears, select the aircraft and airport, then click "Fly!" to launch the simulator. You can configure more options using the GUI launcher. See the [http://flightgear.sourceforge.net/manual/next/en/getstart-ench4.html#takeoff-how-to-start-the-program official manual] for more details.

If you would like to launch FlightGear using command-line, launch <code>/Applications/Utilities/Terminal.app</code> and type the following.

cd /Applications/FlightGear.app/Contents/MacOS
./fgfs --options.....

The [[$FG ROOT]] and [[$FG SCENERY]] are not set on macOS. If you want to specify these variables yourself for command-line use, run the followings on Terminal.app:

FG_ROOT=/Applications/FlightGear.app/Contents/Resources/data
FG_SCENERY=[[$FG_ROOT]]/Scenery

After launching the GUI launcher, you will have the alias to [[$FG_ROOT]] at <code>$HOME/Documents/Flightgear/<version></code> so you can browse the data folder using Finder.

Note: Once you have installed FlightGear, Mac users can locate their [[$FG_ROOT]] folder by opening their applications folder in Finder, right clicking on FlightGear, and clicking "Show Package Contents". This will take you inside the FlightGear folder. You are now able to access all files including Data/Aircraft to [[Howto: Install aircraft#Macintosh OS X|install new aircraft]].

=== Installing from source ===
Main article: [[Building FlightGear]]

=== Getting scenery ===
A limited set of [[scenery]] comes installed with FlightGear. For FlightGear 2024.1 this consists of
* The area surrounding the featured airport for the release which is [[Keflavik_Airport|Keflavik International Airport]] (BIKF)
* The tutorial airport for the [[Cessna_172P|Cessna 172P]] which is [[Hilo_International_Airport|Hilo International Airport]] (PHTO)

In FlightGear, scenery is generally stored in you [[$FG ROOT]] directory, and is divided into three kinds of data:
* '''Airports''' holds airport data, like runway usage and parking spots.
* '''Objects''' and '''Models''' are the buildings, bridges and radio towers, etc. that represent three-dimensional structures.
* '''Terrain''' represents the contours, elevations and type of ground you fly/taxi over.

The current way of "installing" new scenery is enabling [[TerraSync]], which will automatically download and update any place you visit - even on the fly! If you have a slow Internet connection and/or computer you could instead use a scenery manager, for example [[TerraMaster]]. In addition you can also manually download and install new scenery parts, either the official [[World Scenery]] or custom scenery.

The official, although outdated, scenery is available at [http://www.flightgear.org/download/scenery/ the scenery download section] of the FlightGear website, and can be installed following [[Howto: Install scenery]]. You may obtain additional and more up to date scenery objects as they become available through the [http://scenemodels.flightgear.org/ FlightGear Scenery Database]. '''This is recommended for users with weak internet connections or weak computers!'''

Custom scenery is available in many places. For example, on the {{forum link|f=5|text=FlightGear forum}} or within repositories. An internet search should be able to find them. See [[Suggested_custom_scenery|suggested custom scenery]] page for a few recent releases.

FlightGear 2020.3.7 LTS and later added an experimental rollout of 3 dimensional buildings, roads, and objects based on OpenStreetMap data for the entire world to automatically downloaded TerraSync data - see [[OSM2City 1st Worldbuild|1st OSM2City world-build]] notes (March 2021). Some manual downloads of 3d structures for regions or entire countries is available on the [[Areas populated with osm2city scenery|osm2City downloads]] wiki page.

=== Getting aircraft ===
Additional [[aircraft]] can be downloaded and installed through the [[Qt-launcher|launcher]]. Alternatively, you can go to the FlightGear website and navigate to the [http://www.flightgear.org/download/ download page], then choose the aircraft download link that fits your FlightGear version. In addition there are many third party [[hangars]]. For the installation, see [[Howto: Install aircraft]].

== Running FlightGear ==
=== Starting FlightGear ===
The easiest way to start FlightGear is to use the desktop icon. This starts the graphical interface [[FlightGear Qt launcher]] where you can choose aircraft, start position etc. Remember the Qt launcher only has basic options to get you started. A lot of options for graphics, scenery, [[Weather|weather]], [https://www.flightgear.org/tours/simulating-the-ever-changing-scenery/ environment], [[Input_device|input devices]] etc. are available from the [[menu]] inside the simulator.

Many users choose however to start FlightGear directly from the command line. The executable name is <code>fgfs</code> and can be run without options. If it is "not found", it is likely not in your [https://en.wikipedia.org/wiki/PATH_(variable) path]. The location depends on your particular system and choices you made during compile and installation. There is a list of [[Command Line Parameters]] which must be used to change many options, like the aircraft you want. The most important:

fgfs --launcher # opens the FlightGear Qt launcher
fgfs --show-aircraft # displays a list of installed aircraft
fgfs --aircraft=c172p # start FG with the aircraft "c172p" (from the list)

The Qt launcher also lets users add command line parameters for options that are normally changed from the menu inside the simulator, as well as quite advanced options that are only available from the command line (as of August 2020).

=== Configuring rendering and UI ===
[[File:Rendering options 2024.1.png|thumb|View > Rendering Options dialog.]]
If your render quality or framerate is too low, click "View > Rendering Options" to adjust the graphic settings. For newer hardware, it's recommended to set "graphics quality" to high and check "use disk space for faster loading", "animated jetways" and "satellite photoscenery".

If the menu text appears too small on high DPI or large screens, you can manually [[Menubar#How to Change the Default Menubar Font Size|change the menubar font size]] by editing the data file, or simply click "Debug > Cycle GUI Style".

=== Using the keyboard and/or mouse ===
Users with limited access to a [[joystick]] or other controllers sometimes use the keyboard or mouse to control their aircraft. Using the keyboard to fly can be difficult and the mouse is recommended over the keyboard for flying, yet even a cheap joystick would improve the experience so much.

To get help with keyboard commands, with FlightGear running, go to the ''Help'' menu, look under ''Basic Keys'' (for simulator related commands) and ''Common Aircraft Keys'' (for commands universal to all aircraft) and ''Aircraft Help'' (for key commands specific to your aircraft). If the main menu is hidden press {{key press|F10}}. If you come from other simulators, check [[key commands compared to other simulators]] for an overview of the difference between the key commands of that sim and FlightGear.

To use the mouse to fly the aircraft, press {{key press|Tab}} (the cursor should change to a cross) and move the mouse to direct the aircraft. Press {{key press|Tab}} again to look around (cursor should show a two sided arrow), and press {{key press|Tab}} again to return to normal mode, used to click stuff in the cockpit. In some aircraft, such as the [[A320neo]] and [[Airbus A330 (disambiguation)|A330]] this unfortunately will not work, so you will have to use right click to look around and mouse mode is disabled. Fortunately, those planes are airliners, which are really stable and easy to fly with the keyboard.

For most users lacking a rudder axis control, it’s difficult to manually coordinate [[aileron]] and [[rudder]] movements during a turn. To enable auto-coordination and make flight easier, you may click "Settings", then click the "Show more" button on the right of "General", and finally click "Enable auto-coordination" in the launcher.

=== First time in the cockpit ===
Finding your way around the cockpit can be daunting the first time.

Where is the "virtual cockpit"? Not all FlightGear aircraft come with an interior actually, some research projects may not even come with an exterior model. A 2D panel may display over the 3D cockpit if one exists. You may turn this off through ''Main Menu'' > ''View'' > ''View Options'' and deselecting ''Show 2D panel'' in the ''Display Options'' section, or by pressing {{key press|Shift|P}}. Otherwise, you should be sitting in the virtual cockpit when FlightGear starts, as long as the Cockpit View is selected (if not pressing {{key press|Ctrl|V}} should get you to the pilot view).

You may find it difficult to read some of the displays, dials and gauges on the instrument panel. You can use the ''view'' mode of the mouse (press {{key press|Tab}} until you get a cursor shaped like a double arrow) to pan and the mouse wheel to zoom, or pan with the joystick hat and zoom with {{key press|X}} and {{key press|Shift|X}}.

One of the first steps that many take on entering an unfamiliar cockpit is to press {{key press|Ctrl|C}} to highlight all the "hotspots", that is instrument controls, buttons, knobs, etc. Many aircraft also offer a specific help menu.

Some functions, such as starter or magneto, may be difficult to use or simply lack clickable "hotspots", especially in aircraft models which are in development. In most cases you can go for the equivalent controls on a 2D panel or resort to the keyboard. The keyboard always work according to the assignments listed on the ''Help'' menu, but sometimes these are reassigned by an aircraft or configuration. Again, remember to check all the help dialogs.

=== Starting the engine ===
You are eager to fly, but the engine is off. Well, turning on the engines is not always easy. Some aircraft have an ''autostart'' entry in their custom menu, but here is a general procedure that should work in many cases:

In general to start the engine on a piston-engine type aircraft, you need (after making sure the game is not paused {{key press|p}}):
# Fuel: Some aircraft start the simulation with no fuel. You can add it in ''Equipment'' > ''Fuel and Payload''.
# Correct fuel mixture: This is generally ''rich'', so push the red knob all the way in, or use the key {{key press|m}} to enrich ({{key press|Shift|m}} leans.)
# Magnetos set on ''both'': Turn the key or press {{key press|}}} ''three times'' to move through ''R'', ''L'', ''Both''.
# Throttle: Some engines start better with a little gas.
# Run the starter: Click the ''Start'' position of the key on the panel, or press {{key press|s}}. Hold the starter for sufficient time, even 10 seconds.

Starting all engines in a multi-engine aircraft is similar to the single engine - except you must follow the same start sequence for each and every engine. FlightGear provides a convenient way to do this for all engines at once: Press {{key press|~}} and all the procedure above will work for all the engines. Note though that the default 2D panel is connected to ''only one engine'' and the {{key press|~}} trick might not work. Also, give some gas to be sure that all the engines are on.

These instructions may not work for jet aircraft, helicopters, or other types of aircraft with complex start procedures. Check the instructions in the aircraft help menu (press {{key press|?}}) and/or look at [[Aircraft|the aircraft's article on this wiki]]. In general to start the engine on a jet engine type aircraft, you need to:
# Set cutoff ''ON''
# Engage the starter
# Once the engines spools up to approximately 5% N1, set cutoff ''OFF''
# Disengage the starter once the engine has reached operational speed

== Learning to fly ==
=== FlightGear's Manual ===
FlightGear has an official [https://www.flightgear.org/support/manual/ manual] that covers the basics of flight. As a beginner, you may want to start with "Chapter 8: A Basic Flight Simulator Tutorial."

=== Tutorials ===
Many aircraft have their own interactive [[tutorials|tutorial]]. With tutorials, you can learn to operate particular aircraft but also learn to fly. You can access tutorials by going to ''Main menu'' > ''Help'' > ''Tutorial''. A great place to start is the tutorial for the [[Cessna 172P]] aircraft, commonly used in real life to learn to fly fixed-winged aircraft.

If the tutorial starts without a runway and surrounded by water, your setup of FlightGear is missing the scenery for the airport at which the tutorial was supposed to run. To get scenery see the [[#Getting scenery]] section above.

== Making your first flight ==
=== Realism ===
One of the most frequent questions novice pilots ask about any flight simulator, but more so to FlightGear, is "Why is my aircraft turning left all the time?" Although it could be due to wind gusts crossing the runway, it is more likely due to the [[Understanding Propeller Torque and P-Factor|propeller torque and p-factor]].

In certain other flight simulators, despite marketing slogans to the contrary, some settings are turned down to make the aircraft easier to fly. This reduces effects such as the above. The realism is always turned up in FlightGear.

Here are some of the FlightGear realism points, which may be confusing to first time pilots:
* "Left turning syndrome" for the previously mentioned reasons.
* Compass turning error: A compass, when subjected to the forces of flight, tends to turn in the opposite direction for a brief period before settling on the correct heading. This is not a malfunction (see also the Wikipedia article {{wikipedia|Aircraft compass turns}}).
* The Vertical Speed Indicator (VSI) is also subject to error.
* The [[Horizontal Situation Indicator]] (HSI) is driven by a gyroscope (that is why it is sometimes called a Directional Gyroscope), which is subject to ''gyro drift''. The indicator will drift from its current heading and must be periodically (every ~15 minutes) calibrated to agree with the magnetic compass heading.
* You cannot just cancel a turn or climb by centering the yoke or stick. You must turn or push the stick the other way to get to level and level flight. But even then, the plane will not maintain its altitude or heading by itself. A common mistake is trying to find a hands off yoke position. While with trimming one could leave the plane for a couple of seconds, one must use autopilot or constantly adjust the yoke.

Many forces act on an aircraft in flight as well as on the [[avionics and instruments]] used for control and navigation, and may be counter-intuitive. Pilots must learn to recognize these phenomena and compensate for their effects. ''FlightGear models instrument errors that exist in the real world''.

=== Airports and navigation aids ===
When you first start FlightGear, whether from the command line or the graphical interface of the launchers, you may wonder how to determine what airports are available. The launcher displays a list of airports, but you will not see details such as tower or [[ILS]] frequencies. You will not find a map showing [[VOR]]s and their frequencies. What can you do? See [[Getting aeronautical charts]].

In-sim, there is a map you can use in ''Main Menu'' > ''Equipment'' > ''Map'', which will allow you to see navigation data and the position of airports and aids. For more help with navigation see [[Understanding navigation]].

=== Flying using the autopilot ===
Some aircraft require you to use the [[autopilot]] available from the ''Autopilot'' menu, which is the original FlightGear autopilot. This is a ''generic'' autopilot and as such, many aircraft come with their own ''specific'' autopilot, frequently a model of the real life one.

For aircraft that provide their own autopilot, you should use the autopilot controls available in the virtual cockpit. This means clicking on the instrument panel in the virtual cockpit. The Autopilot menu will be grayed out and unavailable when the aircraft supplies its own autopilot in some aircraft, including the Airbuses and the [[Cessna 172P|C172P]].

The Cessna 172 comes with a [[Bendix/King KAP140 Autopilot]] in its virtual cockpit. You can use both the autopilot device in the cockpit and the [[Autopilot#Autopilot Settings|autopilot settings]] from the menu.

== Advanced ==
=== Flying ===
{{Main article|Aircraft}}

* If you continue to fly light civilian aircraft, [[Cessna 182S]] which is more complex than C172P and [[Piper PA28 Warrior II|PA28]] are good choices.
* If you are interested in flying airlines, [[Airbus A320 family]], Boeing [[Boeing 777|777]]/[[Boeing 787-8 Dreamliner|787]], [[MD-11]] and [[MD-80]] are suggested.
* If you are fascinated by fighter aircrafts, choose a highly rated military aircraft (such as [[F-15]]) from [[Aircraft#Modern military aircraft|here]] and install [[Bombable]] if possible.
* If you switch to helicopters, it is recommended to fly [[Eurocopter EC130 B4]].

=== Scenery ===
It is fascinating to explore the [[scenery]] (or just test the graphics/frame rate) with [[UFO]]. First of all, [[#Configuring rendering and UI|increase your graphics quality]]. If you don't see buildings initially, keep FG open and wait for a while for [[TerraSync]] to finish downloading and for the buildings to appear.
There are plenty of [[Suggested airports|well-developed airports]] and scenery areas. You can also explore the scenery objects on the [https://scenery.flightgear.org/map model map].

=== Multiplayer ===
FlightGear has some multiplayer servers that will let you fly in more lively skies, see [[Howto: Multiplayer]]. There are also [[OpenRadar]] and [[ATC-pie]], standalone programs that will let you be an [[Air traffic control|air traffic controller]].

There is also a [[MPMap|multiplayer map]] that lets you see who is online right now, and even what [[navaids]] are nearby.

=== FG's advanced features ===
For a quick reference about the menu items in FlightGear, see [[menu]].

=== Addons ===
FlightGear has a lot of third-party [[Addon|addons]] containing enhancements. For beginners, [[Logbook Add-on|Logbook]] that records your flights may be the most useful.

== The FlightGear community ==
=== Getting help ===
This page is designed to give the user the essential things they need to know about using FlightGear for the first time. Besides the [[Portal:User|User portal]] of this wiki, there are other pages you may want to read:
*[[Troubleshooting problems]] to help you with the most common issues;
*[[Frequently asked questions]];
...and communication channels that can be used to obtain information or request help:
*The [[FlightGear Manual]], a ''must read'' for beginners;
*{{forum link|text=FlightGear Forum}} and its subforums;
*[[Discord|FlightGear's Discord server]], the quickest way to get help;
*[[FlightGear IRC channel]];
*[[Mailing list|FlightGear users mailing list]], biggest chance to get in contact with core developers;
*Documents bundled with the release package.

=== Customizing FlightGear without compiling it ===
[https://www.flightgear.org/download/ Our website] offers precompiled binaries for download and install on Windows, macOS and Linux. In addition, most Linux distributions provide a packaged version in their repositories.

Although the install is binary, most of FlightGear's systems are open to configuration through [[XML]] files and [[NASAL scripting]]. You are free ''and encouraged'' to make changes to aircraft flight models, scenery, textures, OpenGL [[shader]]s and any other feature you wish to change for your personal satisfaction or to share with other FlightGear users. If this is what you intend to do, take a look at the [[Portal:Developer|Developer portal]].

=== How you can help ===
{{Main article|Volunteer}}
FlightGear is an open source, volunteer based project. That means that whatever you find here comes from passion, spare time and nothing else. This includes the simulator, the scenery, the aircraft, the wiki, the {{forum link|text=forum}} and everything else. Volunteers, in essence ''people that do things'', are fundamental to this project. Without them, it would not make a single step forward. So it is essential that contributors have fun in what they do.

If you plan to contribute to this project, you should take a look at some articles that will give you some hints:
*[[Howto:Understand the FlightGear development process]]
*[[Implementing new features for FlightGear]]
*[[How the FlightGear project works]]

There are never enough people contributing, and the fields where their help would be appreciated are many:
;Testing:
*[[Building FlightGear|Build]] the latest Git code
*[https://gitlab.com/flightgear/flightgear/-/issues File bug reports]
*Running FlightGear via valgrind to track down memory leaks

;Support:
*Help new users with downloading, compiling, installing and running FlightGear ({{forum link|text=on the forum}} or on [[Discord]])
*Provide ideas & suggestions, see: [[Feature Requests / Proposals / Ideas]]
*Help [[Portal:Wiki|clean up this wiki]]
*Help provide new contents for missing wiki pages

;Development:
*C/C++ Coding:
**Provide source code cleanups (in essence help in the process of migrating over to a primarily smart pointer-based memory management approach using SGSharedPtr)
**Provide bug fixes [[Bugs]] or new features
**Get involved in any of the other FlightGear-affiliated projects
*Aircraft development (3D modeling, textures, FDMs, scripting)
*Scenery development (terrain, model, weather)

[[Category:FlightGear]]

[[ca:Nou a FlightGear]]
[[de:Neu bei FlightGear]]
[[es:Nuevo en FlightGear]]
[[fi:Uusi_käyttäjä]]
[[fr:Nouveau sur flightgear]]
[[it:Nuovo per FlightGear]]
[[ja:FlightGear入門]]
[[nl:Nieuw bij FlightGear]]
[[pl:Nowy w FlightGear]]
[[pt:Novo no FlightGear]]
[[sr:Novi u FlightGear-u]]
[[th:New to FlightGear]]
[[zh:FlightGear新手]]

New to FlightGear

2026-05-12T21:00:12Z

Fgf5: /* Addons */

'''Welcome to [[FlightGear]]!''' Here we will try to get you up in the virtual air in the shortest time possible. We will also introduce you to some of the features of this flight simulator and also a few information on its community.

== Installation and setup ==
=== Hardware requirements ===
For FlightGear to run smoothly, it requires a video card with OpenGL drivers 4.0 or higher. This is usually not a problem, but take a look at the [[hardware recommendations]] to have a better idea.

=== Getting FlightGear ===
You may download the latest files from the [https://www.flightgear.org/download/ FlightGear download] page. Choose the source or binary files appropriate for your particular system. {{Wikipedia|AppImage|AppImage}} binary files for Linux are also available with 2020.3 LTS and later. Most Linux users will find that most distributions have a packaged version of FlightGear (the package name could be <code>fgfs</code> or <code>flightgear</code>.)

Depending on your technical expertise you may choose the [[Git]] development version of FlightGear, which typically has more features and can be required by some of the latest developmental aircraft, but can be unstable and is more complicated to get for non-Windows users. In general, the development version is not advised to the average user, but if you are willing to do some testing there is a nightly build available for [https://www.flightgear.org/download/nightly/ download]. If you are using a Git version controlled copy of FlightGear, you may choose to synchronise your aircraft using the version controlled [[FGAddon|FGAddon aircraft development repository]].

=== Installing on Windows ===
After you downloaded the installer, run it and follow its instructions to install FlightGear.

Defender SmartScreen on Windows may block the installation simply because the binary file is not signed with a key that Microsoft respects. Of course, the key is paid. In this case, we need to click on the inconspicuous "More info" link. Only then will the "Run anyway" button appear. You can safely trust that this is not a dangerous application, as long as you have actually downloaded it from official sources.

If you're using third-party antivirus software for some reason, it may be blocking FlightGear from installing. This isn't something we can control, so it's entirely up to you how you want to handle it.

With the Windows installer, you may choose where to install FlightGear. The [[$FG_ROOT]] directory would be <code><your chosen directory>/data</code>.

=== Installing on macOS ===
Installing FlightGear on macOS is very simple. Just drag and drop the FlightGear icon to the <code>/Applications</code> folder. That is it.

The first time you launch FlightGear, its icon on the Dock bounces for several seconds while loading aircraft and airport info. When the GUI launcher appears, select the aircraft and airport, then click "Fly!" to launch the simulator. You can configure more options using the GUI launcher. See the [http://flightgear.sourceforge.net/manual/next/en/getstart-ench4.html#takeoff-how-to-start-the-program official manual] for more details.

If you would like to launch FlightGear using command-line, launch <code>/Applications/Utilities/Terminal.app</code> and type the following.

cd /Applications/FlightGear.app/Contents/MacOS
./fgfs --options.....

The [[$FG ROOT]] and [[$FG SCENERY]] are not set on macOS. If you want to specify these variables yourself for command-line use, run the followings on Terminal.app:

FG_ROOT=/Applications/FlightGear.app/Contents/Resources/data
FG_SCENERY=[[$FG_ROOT]]/Scenery

After launching the GUI launcher, you will have the alias to [[$FG_ROOT]] at <code>$HOME/Documents/Flightgear/<version></code> so you can browse the data folder using Finder.

Note: Once you have installed FlightGear, Mac users can locate their [[$FG_ROOT]] folder by opening their applications folder in Finder, right clicking on FlightGear, and clicking "Show Package Contents". This will take you inside the FlightGear folder. You are now able to access all files including Data/Aircraft to [[Howto: Install aircraft#Macintosh OS X|install new aircraft]].

=== Installing from source ===
Main article: [[Building FlightGear]]

=== Getting scenery ===
A limited set of [[scenery]] comes installed with FlightGear. For FlightGear 2024.1 this consists of
* The area surrounding the featured airport for the release which is [[Keflavik_Airport|Keflavik International Airport]] (BIKF)
* The tutorial airport for the [[Cessna_172P|Cessna 172P]] which is [[Hilo_International_Airport|Hilo International Airport]] (PHTO)

In FlightGear, scenery is generally stored in you [[$FG ROOT]] directory, and is divided into three kinds of data:
* '''Airports''' holds airport data, like runway usage and parking spots.
* '''Objects''' and '''Models''' are the buildings, bridges and radio towers, etc. that represent three-dimensional structures.
* '''Terrain''' represents the contours, elevations and type of ground you fly/taxi over.

The current way of "installing" new scenery is enabling [[TerraSync]], which will automatically download and update any place you visit - even on the fly! If you have a slow Internet connection and/or computer you could instead use a scenery manager, for example [[TerraMaster]]. In addition you can also manually download and install new scenery parts, either the official [[World Scenery]] or custom scenery.

The official, although outdated, scenery is available at [http://www.flightgear.org/download/scenery/ the scenery download section] of the FlightGear website, and can be installed following [[Howto: Install scenery]]. You may obtain additional and more up to date scenery objects as they become available through the [http://scenemodels.flightgear.org/ FlightGear Scenery Database]. '''This is recommended for users with weak internet connections or weak computers!'''

Custom scenery is available in many places. For example, on the {{forum link|f=5|text=FlightGear forum}} or within repositories. An internet search should be able to find them. See [[Suggested_custom_scenery|suggested custom scenery]] page for a few recent releases.

FlightGear 2020.3.7 LTS and later added an experimental rollout of 3 dimensional buildings, roads, and objects based on OpenStreetMap data for the entire world to automatically downloaded TerraSync data - see [[OSM2City 1st Worldbuild|1st OSM2City world-build]] notes (March 2021). Some manual downloads of 3d structures for regions or entire countries is available on the [[Areas populated with osm2city scenery|osm2City downloads]] wiki page.

=== Getting aircraft ===
Additional [[aircraft]] can be downloaded and installed through the [[Qt-launcher|launcher]]. Alternatively, you can go to the FlightGear website and navigate to the [http://www.flightgear.org/download/ download page], then choose the aircraft download link that fits your FlightGear version. In addition there are many third party [[hangars]]. For the installation, see [[Howto: Install aircraft]].

== Running FlightGear ==
=== Starting FlightGear ===
The easiest way to start FlightGear is to use the desktop icon. This starts the graphical interface [[FlightGear Qt launcher]] where you can choose aircraft, start position etc. Remember the Qt launcher only has basic options to get you started. A lot of options for graphics, scenery, [[Weather|weather]], [https://www.flightgear.org/tours/simulating-the-ever-changing-scenery/ environment], [[Input_device|input devices]] etc. are available from the [[menu]] inside the simulator.

Many users choose however to start FlightGear directly from the command line. The executable name is <code>fgfs</code> and can be run without options. If it is "not found", it is likely not in your [https://en.wikipedia.org/wiki/PATH_(variable) path]. The location depends on your particular system and choices you made during compile and installation. There is a list of [[Command Line Parameters]] which must be used to change many options, like the aircraft you want. The most important:

fgfs --launcher # opens the FlightGear Qt launcher
fgfs --show-aircraft # displays a list of installed aircraft
fgfs --aircraft=c172p # start FG with the aircraft "c172p" (from the list)

The Qt launcher also lets users add command line parameters for options that are normally changed from the menu inside the simulator, as well as quite advanced options that are only available from the command line (as of August 2020).

=== Configuring rendering and UI ===
[[File:Rendering options 2024.1.png|thumb|View > Rendering Options dialog.]]
If your render quality or framerate is too low, click "View > Rendering Options" to adjust the graphic settings. For newer hardware, it's recommended to set "graphics quality" to high and check "use disk space for faster loading", "animated jetways" and "satellite photoscenery".

If the menu text appears too small on high DPI or large screens, you can manually [[Menubar#How to Change the Default Menubar Font Size|change the menubar font size]] by editing the data file, or simply click "Debug > Cycle GUI Style".

=== Using the keyboard and/or mouse ===
Users with limited access to a [[joystick]] or other controllers sometimes use the keyboard or mouse to control their aircraft. Using the keyboard to fly can be difficult and the mouse is recommended over the keyboard for flying, yet even a cheap joystick would improve the experience so much.

To get help with keyboard commands, with FlightGear running, go to the ''Help'' menu, look under ''Basic Keys'' (for simulator related commands) and ''Common Aircraft Keys'' (for commands universal to all aircraft) and ''Aircraft Help'' (for key commands specific to your aircraft). If the main menu is hidden press {{key press|F10}}. If you come from other simulators, check [[key commands compared to other simulators]] for an overview of the difference between the key commands of that sim and FlightGear.

To use the mouse to fly the aircraft, press {{key press|Tab}} (the cursor should change to a cross) and move the mouse to direct the aircraft. Press {{key press|Tab}} again to look around (cursor should show a two sided arrow), and press {{key press|Tab}} again to return to normal mode, used to click stuff in the cockpit. In some aircraft, such as the [[A320neo]] and [[Airbus A330 (disambiguation)|A330]] this unfortunately will not work, so you will have to use right click to look around and mouse mode is disabled. Fortunately, those planes are airliners, which are really stable and easy to fly with the keyboard.

For most users lacking a rudder axis control, it’s difficult to manually coordinate [[aileron]] and [[rudder]] movements during a turn. To enable auto-coordination and make flight easier, you may click "Settings", then click the "Show more" button on the right of "General", and finally click "Enable auto-coordination" in the launcher.

=== First time in the cockpit ===
Finding your way around the cockpit can be daunting the first time.

Where is the "virtual cockpit"? Not all FlightGear aircraft come with an interior actually, some research projects may not even come with an exterior model. A 2D panel may display over the 3D cockpit if one exists. You may turn this off through ''Main Menu'' > ''View'' > ''View Options'' and deselecting ''Show 2D panel'' in the ''Display Options'' section, or by pressing {{key press|Shift|P}}. Otherwise, you should be sitting in the virtual cockpit when FlightGear starts, as long as the Cockpit View is selected (if not pressing {{key press|Ctrl|V}} should get you to the pilot view).

You may find it difficult to read some of the displays, dials and gauges on the instrument panel. You can use the ''view'' mode of the mouse (press {{key press|Tab}} until you get a cursor shaped like a double arrow) to pan and the mouse wheel to zoom, or pan with the joystick hat and zoom with {{key press|X}} and {{key press|Shift|X}}.

One of the first steps that many take on entering an unfamiliar cockpit is to press {{key press|Ctrl|C}} to highlight all the "hotspots", that is instrument controls, buttons, knobs, etc. Many aircraft also offer a specific help menu.

Some functions, such as starter or magneto, may be difficult to use or simply lack clickable "hotspots", especially in aircraft models which are in development. In most cases you can go for the equivalent controls on a 2D panel or resort to the keyboard. The keyboard always work according to the assignments listed on the ''Help'' menu, but sometimes these are reassigned by an aircraft or configuration. Again, remember to check all the help dialogs.

=== Starting the engine ===
You are eager to fly, but the engine is off. Well, turning on the engines is not always easy. Some aircraft have an ''autostart'' entry in their custom menu, but here is a general procedure that should work in many cases:

In general to start the engine on a piston-engine type aircraft, you need (after making sure the game is not paused {{key press|p}}):
# Fuel: Some aircraft start the simulation with no fuel. You can add it in ''Equipment'' > ''Fuel and Payload''.
# Correct fuel mixture: This is generally ''rich'', so push the red knob all the way in, or use the key {{key press|m}} to enrich ({{key press|Shift|m}} leans.)
# Magnetos set on ''both'': Turn the key or press {{key press|}}} ''three times'' to move through ''R'', ''L'', ''Both''.
# Throttle: Some engines start better with a little gas.
# Run the starter: Click the ''Start'' position of the key on the panel, or press {{key press|s}}. Hold the starter for sufficient time, even 10 seconds.

Starting all engines in a multi-engine aircraft is similar to the single engine - except you must follow the same start sequence for each and every engine. FlightGear provides a convenient way to do this for all engines at once: Press {{key press|~}} and all the procedure above will work for all the engines. Note though that the default 2D panel is connected to ''only one engine'' and the {{key press|~}} trick might not work. Also, give some gas to be sure that all the engines are on.

These instructions may not work for jet aircraft, helicopters, or other types of aircraft with complex start procedures. Check the instructions in the aircraft help menu (press {{key press|?}}) and/or look at [[Aircraft|the aircraft's article on this wiki]]. In general to start the engine on a jet engine type aircraft, you need to:
# Set cutoff ''ON''
# Engage the starter
# Once the engines spools up to approximately 5% N1, set cutoff ''OFF''
# Disengage the starter once the engine has reached operational speed

== Learning to fly ==
=== FlightGear's Manual ===
FlightGear has an official [https://www.flightgear.org/support/manual/ manual] that covers the basics of flight. As a beginner, you may want to start with "Chapter 8: A Basic Flight Simulator Tutorial."

=== Tutorials ===
Many aircraft have their own interactive [[tutorials|tutorial]]. With tutorials, you can learn to operate particular aircraft but also learn to fly. You can access tutorials by going to ''Main menu'' > ''Help'' > ''Tutorial''. A great place to start is the tutorial for the [[Cessna 172P]] aircraft, commonly used in real life to learn to fly fixed-winged aircraft.

If the tutorial starts without a runway and surrounded by water, your setup of FlightGear is missing the scenery for the airport at which the tutorial was supposed to run. To get scenery see the [[#Getting scenery]] section above.

== Making your first flight ==
=== Realism ===
One of the most frequent questions novice pilots ask about any flight simulator, but more so to FlightGear, is "Why is my aircraft turning left all the time?" Although it could be due to wind gusts crossing the runway, it is more likely due to the [[Understanding Propeller Torque and P-Factor|propeller torque and p-factor]].

In certain other flight simulators, despite marketing slogans to the contrary, some settings are turned down to make the aircraft easier to fly. This reduces effects such as the above. The realism is always turned up in FlightGear.

Here are some of the FlightGear realism points, which may be confusing to first time pilots:
* "Left turning syndrome" for the previously mentioned reasons.
* Compass turning error: A compass, when subjected to the forces of flight, tends to turn in the opposite direction for a brief period before settling on the correct heading. This is not a malfunction (see also the Wikipedia article {{wikipedia|Aircraft compass turns}}).
* The Vertical Speed Indicator (VSI) is also subject to error.
* The [[Horizontal Situation Indicator]] (HSI) is driven by a gyroscope (that is why it is sometimes called a Directional Gyroscope), which is subject to ''gyro drift''. The indicator will drift from its current heading and must be periodically (every ~15 minutes) calibrated to agree with the magnetic compass heading.
* You cannot just cancel a turn or climb by centering the yoke or stick. You must turn or push the stick the other way to get to level and level flight. But even then, the plane will not maintain its altitude or heading by itself. A common mistake is trying to find a hands off yoke position. While with trimming one could leave the plane for a couple of seconds, one must use autopilot or constantly adjust the yoke.

Many forces act on an aircraft in flight as well as on the [[avionics and instruments]] used for control and navigation, and may be counter-intuitive. Pilots must learn to recognize these phenomena and compensate for their effects. ''FlightGear models instrument errors that exist in the real world''.

=== Airports and navigation aids ===
When you first start FlightGear, whether from the command line or the graphical interface of the launchers, you may wonder how to determine what airports are available. The launcher displays a list of airports, but you will not see details such as tower or [[ILS]] frequencies. You will not find a map showing [[VOR]]s and their frequencies. What can you do? See [[Getting aeronautical charts]].

In-sim, there is a map you can use in ''Main Menu'' > ''Equipment'' > ''Map'', which will allow you to see navigation data and the position of airports and aids. For more help with navigation see [[Understanding navigation]].

=== Flying using the autopilot ===
Some aircraft require you to use the [[autopilot]] available from the ''Autopilot'' menu, which is the original FlightGear autopilot. This is a ''generic'' autopilot and as such, many aircraft come with their own ''specific'' autopilot, frequently a model of the real life one.

For aircraft that provide their own autopilot, you should use the autopilot controls available in the virtual cockpit. This means clicking on the instrument panel in the virtual cockpit. The Autopilot menu will be grayed out and unavailable when the aircraft supplies its own autopilot in some aircraft, including the Airbuses and the [[Cessna 172P|C172P]].

The Cessna 172 comes with a [[Bendix/King KAP140 Autopilot]] in its virtual cockpit. You can use both the autopilot device in the cockpit and the [[Autopilot#Autopilot Settings|autopilot settings]] from the menu.

== Advanced ==
=== Flying ===
{{Main article|Aircraft}}

* If you continue to fly light civilian aircraft, [[Cessna 182S]] which is more complex than C172P and [[Piper PA28 Warrior II|PA28]] are good choices.
* If you are interested in flying airlines, [[Airbus A320 family]], Boeing [[Boeing 777|777]]/[[Boeing 787-8 Dreamliner|787]], [[MD-11]] and [[MD-80]] are suggested.
* If you are fascinated by fighter aircrafts, choose a highly rated military aircraft (such as [[F-15]]) from [[Aircraft#Modern military aircraft|here]] and install [[Bombable]] if possible.
* If you switch to helicopters, it is recommended to fly [[Eurocopter EC130 B4]].

=== Scenery ===
It is fascinating to explore the [[scenery]] (or just test the graphics/frame rate) with [[UFO]]. First of all, [[#Configuring rendering and UI|increase your graphics quality]]. If you don't see buildings initially, keep FG open and wait for a while for [[TerraSync]] to finish downloading and for the buildings to appear.
There are plenty of [[Suggested airports|well-developed airports]] and scenery areas. You can also explore the scenery objects on the [https://scenery.flightgear.org/map model map].

=== Multiplayer ===
FlightGear has some multiplayer servers that will let you fly in more lively skies, see [[Howto: Multiplayer]]. There are also [[OpenRadar]] and [[ATC-pie]], standalone programs that will let you be an [[Air traffic control|air traffic controller]].

There is also a [[MPMap|multiplayer map]] that lets you see who is online right now, and even what [[navaids]] are nearby.

=== FG's advanced features ===
For a quick reference about the menu items in FlightGear, see [[menu]].

=== Addons ===
FlightGear has a lot of third-party [[Addon|addons]] containing enhancements. For beginners, [[Logbook Add-on|Logbook]] that records your flights is the most useful.

== The FlightGear community ==
=== Getting help ===
This page is designed to give the user the essential things they need to know about using FlightGear for the first time. Besides the [[Portal:User|User portal]] of this wiki, there are other pages you may want to read:
*[[Troubleshooting problems]] to help you with the most common issues;
*[[Frequently asked questions]];
...and communication channels that can be used to obtain information or request help:
*The [[FlightGear Manual]], a ''must read'' for beginners;
*{{forum link|text=FlightGear Forum}} and its subforums;
*[[Discord|FlightGear's Discord server]], the quickest way to get help;
*[[FlightGear IRC channel]];
*[[Mailing list|FlightGear users mailing list]], biggest chance to get in contact with core developers;
*Documents bundled with the release package.

=== Customizing FlightGear without compiling it ===
[https://www.flightgear.org/download/ Our website] offers precompiled binaries for download and install on Windows, macOS and Linux. In addition, most Linux distributions provide a packaged version in their repositories.

Although the install is binary, most of FlightGear's systems are open to configuration through [[XML]] files and [[NASAL scripting]]. You are free ''and encouraged'' to make changes to aircraft flight models, scenery, textures, OpenGL [[shader]]s and any other feature you wish to change for your personal satisfaction or to share with other FlightGear users. If this is what you intend to do, take a look at the [[Portal:Developer|Developer portal]].

=== How you can help ===
{{Main article|Volunteer}}
FlightGear is an open source, volunteer based project. That means that whatever you find here comes from passion, spare time and nothing else. This includes the simulator, the scenery, the aircraft, the wiki, the {{forum link|text=forum}} and everything else. Volunteers, in essence ''people that do things'', are fundamental to this project. Without them, it would not make a single step forward. So it is essential that contributors have fun in what they do.

If you plan to contribute to this project, you should take a look at some articles that will give you some hints:
*[[Howto:Understand the FlightGear development process]]
*[[Implementing new features for FlightGear]]
*[[How the FlightGear project works]]

There are never enough people contributing, and the fields where their help would be appreciated are many:
;Testing:
*[[Building FlightGear|Build]] the latest Git code
*[https://gitlab.com/flightgear/flightgear/-/issues File bug reports]
*Running FlightGear via valgrind to track down memory leaks

;Support:
*Help new users with downloading, compiling, installing and running FlightGear ({{forum link|text=on the forum}} or on [[Discord]])
*Provide ideas & suggestions, see: [[Feature Requests / Proposals / Ideas]]
*Help [[Portal:Wiki|clean up this wiki]]
*Help provide new contents for missing wiki pages

;Development:
*C/C++ Coding:
**Provide source code cleanups (in essence help in the process of migrating over to a primarily smart pointer-based memory management approach using SGSharedPtr)
**Provide bug fixes [[Bugs]] or new features
**Get involved in any of the other FlightGear-affiliated projects
*Aircraft development (3D modeling, textures, FDMs, scripting)
*Scenery development (terrain, model, weather)

[[Category:FlightGear]]

[[ca:Nou a FlightGear]]
[[de:Neu bei FlightGear]]
[[es:Nuevo en FlightGear]]
[[fi:Uusi_käyttäjä]]
[[fr:Nouveau sur flightgear]]
[[it:Nuovo per FlightGear]]
[[ja:FlightGear入門]]
[[nl:Nieuw bij FlightGear]]
[[pl:Nowy w FlightGear]]
[[pt:Novo no FlightGear]]
[[sr:Novi u FlightGear-u]]
[[th:New to FlightGear]]
[[zh:FlightGear新手]]

Aircraft

2026-05-12T20:58:34Z

Fgf5: /* Light civilian aircraft */

[[File:FlightGear Launcher Aircraft Tab.png|thumb|The FlightGear Qt launcher, showing a handful of the aircraft that are able to be downloaded or updated from the FGAddon repository.]]

This list is not updated to include all the official [[GNU General Public License|GPL licensed]] aircraft for [[FlightGear]], but gives a visual sampling of the different types of aircraft and genres of aircraft officially available.

Most models shown here are available from the official FlightGear project and can be downloaded from the FlightGear launcher, with no additional steps required for installation. Alternatively these aircraft can be obtained directly from the [https://sourceforge.net/p/flightgear/fgaddon/HEAD/tree/ FGAddon SVN repository]. If the aircraft is installed manually, you will lose the ability to check for, and install updates from within the launcher. Some models shown here are available from [[FlightGear hangars|non-official hangars]].

FlightGear aircraft features, quality, and compatibility vary significantly. Their development is dependent on the [[volunteer]]s who worked on them, with exception of some University and Government funded projects. Aircraft are listed by completeness status in [[:Category:Aircraft by status]].

To edit this list, see here: [[Template:Model_Gallery]].

=== Light civilian aircraft ===
The Cessna 172 has been the default aircraft since FGFS 2.0. These aircraft typically have 1-2 piston engines, props, and avionics geared towards those with civilian pilot licenses.
{{Model Gallery | section=light_civilian_aircraft}}

===Business Jets===
Smaller aircraft with 1-2 turbofan engines, usually used by businesses and private companies.
{{Model Gallery| section=business_jets}}

===Airliners===
These typically have 2-4 turbofan engines and some of the more complicated takeoff and landing procedures (such as multiple [[flaps]]).

See [[Airliner development status]] for more info.

====Narrowbody & Midsize====
{{Model Gallery| section=modern_airliners_narrowbody_midsize}}

====Widebody & Jumbo Airliners====
{{Model Gallery| section=modern_airliners_widebody_jumbo}}

===Helicopters===
{{Main article|Helicopter}}

Helicopters have fundamentally different controls than fixed wing aircraft (see ''[[Flying the Helicopter]]''). Modern helicopter typically feature 1-2 turbine engines, which power a main rotor with 2-6 blades.
{{Model Gallery| section=helicopters}}

===Gliders, Sailplanes, & Ultralights===
These typically have the simplest controls, with minimal avionics. Flying [[:Category:Gliders|gliders]] or sailplanes using [[Soaring|thermals]] can provide more complicated experience. Ultralights on the other hand are among the simplest aircraft in FG.
{{Model Gallery| section=ultra_light}}

===Warbirds===
FlightGear includes a wide variety of vintage military aircraft. Complexity and realism is typically tied to the level of development work with a specific aircraft.
{{Model Gallery| section=warbirds}}

===Carrier-borne aircraft===
FlightGear supports landing on and taking off from [[carriers]].
{{Model Gallery| section=carrier_borne_aircraft}}

===Modern military aircraft ===
FlightGear has a wide variety of modern and retired military jets available, highlighted by features such as air-to-air refueling from the venerable KC-135 and the ability to simulate A-10 ordnance release.
{{Model Gallery| section=modern_military_aircraft}}

===Historical===
Many obscure to famous older aircraft of varying quality are available.
{{Model Gallery| section=historical_aircraft}}

===Experimental & Unique===
Experimental and special purpose aircraft.
{{Model Gallery| section=experimental}}

===Lighter than air aircraft (Available from version 1.9.0)===
These aircraft take advantage of lighter than air gas to become buoyant. In addition to typical aircraft control methods such as elevator, rudder and engine throttle, ballast and control of gas volume and pressure become options.
{{Model Gallery| section=lighter_than_air}}

===Science Fiction===
Alternative models provide a diversion of realistic simulation, but can also be useful for exploring scenery.
{{Model Gallery| section=science_fiction}}

===Spacecraft===
Things that show how small our planet Earth really is.
{{Model Gallery| section=spacecraft}}

==See Also ==
* [[Howto:Make an aircraft]]
* [[How to install aircraft]]
* [[Airliner Development Status]]



[[it:Aerei]]

[[Category:Lists]]
[[Category:Aircraft| ]]

[[ca:Aeronau]]
[[de:Flugzeuge]]
[[es:Avión]]
[[fa:هواپیما]]
[[fi:Lentokoneet]]
[[fr:Avions]]
[[nl:Luchtvaartuigen]]
[[pl:Samoloty]]
[[pt:Avião]]
[[ru:Самолет]]
[[zh:插件飞机]]

New to FlightGear

2026-05-12T20:57:59Z

Fgf5: add "advanced" and auto-coordination

'''Welcome to [[FlightGear]]!''' Here we will try to get you up in the virtual air in the shortest time possible. We will also introduce you to some of the features of this flight simulator and also a few information on its community.

== Installation and setup ==
=== Hardware requirements ===
For FlightGear to run smoothly, it requires a video card with OpenGL drivers 4.0 or higher. This is usually not a problem, but take a look at the [[hardware recommendations]] to have a better idea.

=== Getting FlightGear ===
You may download the latest files from the [https://www.flightgear.org/download/ FlightGear download] page. Choose the source or binary files appropriate for your particular system. {{Wikipedia|AppImage|AppImage}} binary files for Linux are also available with 2020.3 LTS and later. Most Linux users will find that most distributions have a packaged version of FlightGear (the package name could be <code>fgfs</code> or <code>flightgear</code>.)

Depending on your technical expertise you may choose the [[Git]] development version of FlightGear, which typically has more features and can be required by some of the latest developmental aircraft, but can be unstable and is more complicated to get for non-Windows users. In general, the development version is not advised to the average user, but if you are willing to do some testing there is a nightly build available for [https://www.flightgear.org/download/nightly/ download]. If you are using a Git version controlled copy of FlightGear, you may choose to synchronise your aircraft using the version controlled [[FGAddon|FGAddon aircraft development repository]].

=== Installing on Windows ===
After you downloaded the installer, run it and follow its instructions to install FlightGear.

Defender SmartScreen on Windows may block the installation simply because the binary file is not signed with a key that Microsoft respects. Of course, the key is paid. In this case, we need to click on the inconspicuous "More info" link. Only then will the "Run anyway" button appear. You can safely trust that this is not a dangerous application, as long as you have actually downloaded it from official sources.

If you're using third-party antivirus software for some reason, it may be blocking FlightGear from installing. This isn't something we can control, so it's entirely up to you how you want to handle it.

With the Windows installer, you may choose where to install FlightGear. The [[$FG_ROOT]] directory would be <code><your chosen directory>/data</code>.

=== Installing on macOS ===
Installing FlightGear on macOS is very simple. Just drag and drop the FlightGear icon to the <code>/Applications</code> folder. That is it.

The first time you launch FlightGear, its icon on the Dock bounces for several seconds while loading aircraft and airport info. When the GUI launcher appears, select the aircraft and airport, then click "Fly!" to launch the simulator. You can configure more options using the GUI launcher. See the [http://flightgear.sourceforge.net/manual/next/en/getstart-ench4.html#takeoff-how-to-start-the-program official manual] for more details.

If you would like to launch FlightGear using command-line, launch <code>/Applications/Utilities/Terminal.app</code> and type the following.

cd /Applications/FlightGear.app/Contents/MacOS
./fgfs --options.....

The [[$FG ROOT]] and [[$FG SCENERY]] are not set on macOS. If you want to specify these variables yourself for command-line use, run the followings on Terminal.app:

FG_ROOT=/Applications/FlightGear.app/Contents/Resources/data
FG_SCENERY=[[$FG_ROOT]]/Scenery

After launching the GUI launcher, you will have the alias to [[$FG_ROOT]] at <code>$HOME/Documents/Flightgear/<version></code> so you can browse the data folder using Finder.

Note: Once you have installed FlightGear, Mac users can locate their [[$FG_ROOT]] folder by opening their applications folder in Finder, right clicking on FlightGear, and clicking "Show Package Contents". This will take you inside the FlightGear folder. You are now able to access all files including Data/Aircraft to [[Howto: Install aircraft#Macintosh OS X|install new aircraft]].

=== Installing from source ===
Main article: [[Building FlightGear]]

=== Getting scenery ===
A limited set of [[scenery]] comes installed with FlightGear. For FlightGear 2024.1 this consists of
* The area surrounding the featured airport for the release which is [[Keflavik_Airport|Keflavik International Airport]] (BIKF)
* The tutorial airport for the [[Cessna_172P|Cessna 172P]] which is [[Hilo_International_Airport|Hilo International Airport]] (PHTO)

In FlightGear, scenery is generally stored in you [[$FG ROOT]] directory, and is divided into three kinds of data:
* '''Airports''' holds airport data, like runway usage and parking spots.
* '''Objects''' and '''Models''' are the buildings, bridges and radio towers, etc. that represent three-dimensional structures.
* '''Terrain''' represents the contours, elevations and type of ground you fly/taxi over.

The current way of "installing" new scenery is enabling [[TerraSync]], which will automatically download and update any place you visit - even on the fly! If you have a slow Internet connection and/or computer you could instead use a scenery manager, for example [[TerraMaster]]. In addition you can also manually download and install new scenery parts, either the official [[World Scenery]] or custom scenery.

The official, although outdated, scenery is available at [http://www.flightgear.org/download/scenery/ the scenery download section] of the FlightGear website, and can be installed following [[Howto: Install scenery]]. You may obtain additional and more up to date scenery objects as they become available through the [http://scenemodels.flightgear.org/ FlightGear Scenery Database]. '''This is recommended for users with weak internet connections or weak computers!'''

Custom scenery is available in many places. For example, on the {{forum link|f=5|text=FlightGear forum}} or within repositories. An internet search should be able to find them. See [[Suggested_custom_scenery|suggested custom scenery]] page for a few recent releases.

FlightGear 2020.3.7 LTS and later added an experimental rollout of 3 dimensional buildings, roads, and objects based on OpenStreetMap data for the entire world to automatically downloaded TerraSync data - see [[OSM2City 1st Worldbuild|1st OSM2City world-build]] notes (March 2021). Some manual downloads of 3d structures for regions or entire countries is available on the [[Areas populated with osm2city scenery|osm2City downloads]] wiki page.

=== Getting aircraft ===
Additional [[aircraft]] can be downloaded and installed through the [[Qt-launcher|launcher]]. Alternatively, you can go to the FlightGear website and navigate to the [http://www.flightgear.org/download/ download page], then choose the aircraft download link that fits your FlightGear version. In addition there are many third party [[hangars]]. For the installation, see [[Howto: Install aircraft]].

== Running FlightGear ==
=== Starting FlightGear ===
The easiest way to start FlightGear is to use the desktop icon. This starts the graphical interface [[FlightGear Qt launcher]] where you can choose aircraft, start position etc. Remember the Qt launcher only has basic options to get you started. A lot of options for graphics, scenery, [[Weather|weather]], [https://www.flightgear.org/tours/simulating-the-ever-changing-scenery/ environment], [[Input_device|input devices]] etc. are available from the [[menu]] inside the simulator.

Many users choose however to start FlightGear directly from the command line. The executable name is <code>fgfs</code> and can be run without options. If it is "not found", it is likely not in your [https://en.wikipedia.org/wiki/PATH_(variable) path]. The location depends on your particular system and choices you made during compile and installation. There is a list of [[Command Line Parameters]] which must be used to change many options, like the aircraft you want. The most important:

fgfs --launcher # opens the FlightGear Qt launcher
fgfs --show-aircraft # displays a list of installed aircraft
fgfs --aircraft=c172p # start FG with the aircraft "c172p" (from the list)

The Qt launcher also lets users add command line parameters for options that are normally changed from the menu inside the simulator, as well as quite advanced options that are only available from the command line (as of August 2020).

=== Configuring rendering and UI ===
[[File:Rendering options 2024.1.png|thumb|View > Rendering Options dialog.]]
If your render quality or framerate is too low, click "View > Rendering Options" to adjust the graphic settings. For newer hardware, it's recommended to set "graphics quality" to high and check "use disk space for faster loading", "animated jetways" and "satellite photoscenery".

If the menu text appears too small on high DPI or large screens, you can manually [[Menubar#How to Change the Default Menubar Font Size|change the menubar font size]] by editing the data file, or simply click "Debug > Cycle GUI Style".

=== Using the keyboard and/or mouse ===
Users with limited access to a [[joystick]] or other controllers sometimes use the keyboard or mouse to control their aircraft. Using the keyboard to fly can be difficult and the mouse is recommended over the keyboard for flying, yet even a cheap joystick would improve the experience so much.

To get help with keyboard commands, with FlightGear running, go to the ''Help'' menu, look under ''Basic Keys'' (for simulator related commands) and ''Common Aircraft Keys'' (for commands universal to all aircraft) and ''Aircraft Help'' (for key commands specific to your aircraft). If the main menu is hidden press {{key press|F10}}. If you come from other simulators, check [[key commands compared to other simulators]] for an overview of the difference between the key commands of that sim and FlightGear.

To use the mouse to fly the aircraft, press {{key press|Tab}} (the cursor should change to a cross) and move the mouse to direct the aircraft. Press {{key press|Tab}} again to look around (cursor should show a two sided arrow), and press {{key press|Tab}} again to return to normal mode, used to click stuff in the cockpit. In some aircraft, such as the [[A320neo]] and [[Airbus A330 (disambiguation)|A330]] this unfortunately will not work, so you will have to use right click to look around and mouse mode is disabled. Fortunately, those planes are airliners, which are really stable and easy to fly with the keyboard.

For most users lacking a rudder axis control, it’s difficult to manually coordinate [[aileron]] and [[rudder]] movements during a turn. To enable auto-coordination and make flight easier, you may click "Settings", then click the "Show more" button on the right of "General", and finally click "Enable auto-coordination" in the launcher.

=== First time in the cockpit ===
Finding your way around the cockpit can be daunting the first time.

Where is the "virtual cockpit"? Not all FlightGear aircraft come with an interior actually, some research projects may not even come with an exterior model. A 2D panel may display over the 3D cockpit if one exists. You may turn this off through ''Main Menu'' > ''View'' > ''View Options'' and deselecting ''Show 2D panel'' in the ''Display Options'' section, or by pressing {{key press|Shift|P}}. Otherwise, you should be sitting in the virtual cockpit when FlightGear starts, as long as the Cockpit View is selected (if not pressing {{key press|Ctrl|V}} should get you to the pilot view).

You may find it difficult to read some of the displays, dials and gauges on the instrument panel. You can use the ''view'' mode of the mouse (press {{key press|Tab}} until you get a cursor shaped like a double arrow) to pan and the mouse wheel to zoom, or pan with the joystick hat and zoom with {{key press|X}} and {{key press|Shift|X}}.

One of the first steps that many take on entering an unfamiliar cockpit is to press {{key press|Ctrl|C}} to highlight all the "hotspots", that is instrument controls, buttons, knobs, etc. Many aircraft also offer a specific help menu.

Some functions, such as starter or magneto, may be difficult to use or simply lack clickable "hotspots", especially in aircraft models which are in development. In most cases you can go for the equivalent controls on a 2D panel or resort to the keyboard. The keyboard always work according to the assignments listed on the ''Help'' menu, but sometimes these are reassigned by an aircraft or configuration. Again, remember to check all the help dialogs.

=== Starting the engine ===
You are eager to fly, but the engine is off. Well, turning on the engines is not always easy. Some aircraft have an ''autostart'' entry in their custom menu, but here is a general procedure that should work in many cases:

In general to start the engine on a piston-engine type aircraft, you need (after making sure the game is not paused {{key press|p}}):
# Fuel: Some aircraft start the simulation with no fuel. You can add it in ''Equipment'' > ''Fuel and Payload''.
# Correct fuel mixture: This is generally ''rich'', so push the red knob all the way in, or use the key {{key press|m}} to enrich ({{key press|Shift|m}} leans.)
# Magnetos set on ''both'': Turn the key or press {{key press|}}} ''three times'' to move through ''R'', ''L'', ''Both''.
# Throttle: Some engines start better with a little gas.
# Run the starter: Click the ''Start'' position of the key on the panel, or press {{key press|s}}. Hold the starter for sufficient time, even 10 seconds.

Starting all engines in a multi-engine aircraft is similar to the single engine - except you must follow the same start sequence for each and every engine. FlightGear provides a convenient way to do this for all engines at once: Press {{key press|~}} and all the procedure above will work for all the engines. Note though that the default 2D panel is connected to ''only one engine'' and the {{key press|~}} trick might not work. Also, give some gas to be sure that all the engines are on.

These instructions may not work for jet aircraft, helicopters, or other types of aircraft with complex start procedures. Check the instructions in the aircraft help menu (press {{key press|?}}) and/or look at [[Aircraft|the aircraft's article on this wiki]]. In general to start the engine on a jet engine type aircraft, you need to:
# Set cutoff ''ON''
# Engage the starter
# Once the engines spools up to approximately 5% N1, set cutoff ''OFF''
# Disengage the starter once the engine has reached operational speed

== Learning to fly ==
=== FlightGear's Manual ===
FlightGear has an official [https://www.flightgear.org/support/manual/ manual] that covers the basics of flight. As a beginner, you may want to start with "Chapter 8: A Basic Flight Simulator Tutorial."

=== Tutorials ===
Many aircraft have their own interactive [[tutorials|tutorial]]. With tutorials, you can learn to operate particular aircraft but also learn to fly. You can access tutorials by going to ''Main menu'' > ''Help'' > ''Tutorial''. A great place to start is the tutorial for the [[Cessna 172P]] aircraft, commonly used in real life to learn to fly fixed-winged aircraft.

If the tutorial starts without a runway and surrounded by water, your setup of FlightGear is missing the scenery for the airport at which the tutorial was supposed to run. To get scenery see the [[#Getting scenery]] section above.

== Making your first flight ==
=== Realism ===
One of the most frequent questions novice pilots ask about any flight simulator, but more so to FlightGear, is "Why is my aircraft turning left all the time?" Although it could be due to wind gusts crossing the runway, it is more likely due to the [[Understanding Propeller Torque and P-Factor|propeller torque and p-factor]].

In certain other flight simulators, despite marketing slogans to the contrary, some settings are turned down to make the aircraft easier to fly. This reduces effects such as the above. The realism is always turned up in FlightGear.

Here are some of the FlightGear realism points, which may be confusing to first time pilots:
* "Left turning syndrome" for the previously mentioned reasons.
* Compass turning error: A compass, when subjected to the forces of flight, tends to turn in the opposite direction for a brief period before settling on the correct heading. This is not a malfunction (see also the Wikipedia article {{wikipedia|Aircraft compass turns}}).
* The Vertical Speed Indicator (VSI) is also subject to error.
* The [[Horizontal Situation Indicator]] (HSI) is driven by a gyroscope (that is why it is sometimes called a Directional Gyroscope), which is subject to ''gyro drift''. The indicator will drift from its current heading and must be periodically (every ~15 minutes) calibrated to agree with the magnetic compass heading.
* You cannot just cancel a turn or climb by centering the yoke or stick. You must turn or push the stick the other way to get to level and level flight. But even then, the plane will not maintain its altitude or heading by itself. A common mistake is trying to find a hands off yoke position. While with trimming one could leave the plane for a couple of seconds, one must use autopilot or constantly adjust the yoke.

Many forces act on an aircraft in flight as well as on the [[avionics and instruments]] used for control and navigation, and may be counter-intuitive. Pilots must learn to recognize these phenomena and compensate for their effects. ''FlightGear models instrument errors that exist in the real world''.

=== Airports and navigation aids ===
When you first start FlightGear, whether from the command line or the graphical interface of the launchers, you may wonder how to determine what airports are available. The launcher displays a list of airports, but you will not see details such as tower or [[ILS]] frequencies. You will not find a map showing [[VOR]]s and their frequencies. What can you do? See [[Getting aeronautical charts]].

In-sim, there is a map you can use in ''Main Menu'' > ''Equipment'' > ''Map'', which will allow you to see navigation data and the position of airports and aids. For more help with navigation see [[Understanding navigation]].

=== Flying using the autopilot ===
Some aircraft require you to use the [[autopilot]] available from the ''Autopilot'' menu, which is the original FlightGear autopilot. This is a ''generic'' autopilot and as such, many aircraft come with their own ''specific'' autopilot, frequently a model of the real life one.

For aircraft that provide their own autopilot, you should use the autopilot controls available in the virtual cockpit. This means clicking on the instrument panel in the virtual cockpit. The Autopilot menu will be grayed out and unavailable when the aircraft supplies its own autopilot in some aircraft, including the Airbuses and the [[Cessna 172P|C172P]].

The Cessna 172 comes with a [[Bendix/King KAP140 Autopilot]] in its virtual cockpit. You can use both the autopilot device in the cockpit and the [[Autopilot#Autopilot Settings|autopilot settings]] from the menu.

== Advanced ==
=== Flying ===
{{Main article|Aircraft}}

* If you continue to fly light civilian aircraft, [[Cessna 182S]] which is more complex than C172P and [[Piper PA28 Warrior II|PA28]] are good choices.
* If you are interested in flying airlines, [[Airbus A320 family]], Boeing [[Boeing 777|777]]/[[Boeing 787-8 Dreamliner|787]], [[MD-11]] and [[MD-80]] are suggested.
* If you are fascinated by fighter aircrafts, choose a highly rated military aircraft (such as [[F-15]]) from [[Aircraft#Modern military aircraft|here]] and install [[Bombable]] if possible.
* If you switch to helicopters, it is recommended to fly [[Eurocopter EC130 B4]].

=== Scenery ===
It is fascinating to explore the [[scenery]] (or just test the graphics/frame rate) with [[UFO]]. First of all, [[#Configuring rendering and UI|increase your graphics quality]]. If you don't see buildings initially, keep FG open and wait for a while for [[TerraSync]] to finish downloading and for the buildings to appear.
There are plenty of [[Suggested airports|well-developed airports]] and scenery areas. You can also explore the scenery objects on the [https://scenery.flightgear.org/map model map].

=== Multiplayer ===
FlightGear has some multiplayer servers that will let you fly in more lively skies, see [[Howto: Multiplayer]]. There are also [[OpenRadar]] and [[ATC-pie]], standalone programs that will let you be an [[Air traffic control|air traffic controller]].

There is also a [[MPMap|multiplayer map]] that lets you see who is online right now, and even what [[navaids]] are nearby.

=== FG's advanced features ===
For a quick reference about the menu items in FlightGear, see [[menu]].

=== Addons ===
FlightGear has a lot of [[Addon|addons]] containing enhancements. For beginners, [[Logbook Add-on|Logbook]] that records your flights is the most useful.

== The FlightGear community ==
=== Getting help ===
This page is designed to give the user the essential things they need to know about using FlightGear for the first time. Besides the [[Portal:User|User portal]] of this wiki, there are other pages you may want to read:
*[[Troubleshooting problems]] to help you with the most common issues;
*[[Frequently asked questions]];
...and communication channels that can be used to obtain information or request help:
*The [[FlightGear Manual]], a ''must read'' for beginners;
*{{forum link|text=FlightGear Forum}} and its subforums;
*[[Discord|FlightGear's Discord server]], the quickest way to get help;
*[[FlightGear IRC channel]];
*[[Mailing list|FlightGear users mailing list]], biggest chance to get in contact with core developers;
*Documents bundled with the release package.

=== Customizing FlightGear without compiling it ===
[https://www.flightgear.org/download/ Our website] offers precompiled binaries for download and install on Windows, macOS and Linux. In addition, most Linux distributions provide a packaged version in their repositories.

Although the install is binary, most of FlightGear's systems are open to configuration through [[XML]] files and [[NASAL scripting]]. You are free ''and encouraged'' to make changes to aircraft flight models, scenery, textures, OpenGL [[shader]]s and any other feature you wish to change for your personal satisfaction or to share with other FlightGear users. If this is what you intend to do, take a look at the [[Portal:Developer|Developer portal]].

=== How you can help ===
{{Main article|Volunteer}}
FlightGear is an open source, volunteer based project. That means that whatever you find here comes from passion, spare time and nothing else. This includes the simulator, the scenery, the aircraft, the wiki, the {{forum link|text=forum}} and everything else. Volunteers, in essence ''people that do things'', are fundamental to this project. Without them, it would not make a single step forward. So it is essential that contributors have fun in what they do.

If you plan to contribute to this project, you should take a look at some articles that will give you some hints:
*[[Howto:Understand the FlightGear development process]]
*[[Implementing new features for FlightGear]]
*[[How the FlightGear project works]]

There are never enough people contributing, and the fields where their help would be appreciated are many:
;Testing:
*[[Building FlightGear|Build]] the latest Git code
*[https://gitlab.com/flightgear/flightgear/-/issues File bug reports]
*Running FlightGear via valgrind to track down memory leaks

;Support:
*Help new users with downloading, compiling, installing and running FlightGear ({{forum link|text=on the forum}} or on [[Discord]])
*Provide ideas & suggestions, see: [[Feature Requests / Proposals / Ideas]]
*Help [[Portal:Wiki|clean up this wiki]]
*Help provide new contents for missing wiki pages

;Development:
*C/C++ Coding:
**Provide source code cleanups (in essence help in the process of migrating over to a primarily smart pointer-based memory management approach using SGSharedPtr)
**Provide bug fixes [[Bugs]] or new features
**Get involved in any of the other FlightGear-affiliated projects
*Aircraft development (3D modeling, textures, FDMs, scripting)
*Scenery development (terrain, model, weather)

[[Category:FlightGear]]

[[ca:Nou a FlightGear]]
[[de:Neu bei FlightGear]]
[[es:Nuevo en FlightGear]]
[[fi:Uusi_käyttäjä]]
[[fr:Nouveau sur flightgear]]
[[it:Nuovo per FlightGear]]
[[ja:FlightGear入門]]
[[nl:Nieuw bij FlightGear]]
[[pl:Nowy w FlightGear]]
[[pt:Novo no FlightGear]]
[[sr:Novi u FlightGear-u]]
[[th:New to FlightGear]]
[[zh:FlightGear新手]]

''For the technical details about the menubar, see [[Menubar]].''

The in-game '''menu''' provides access to Flightgear's various features.

[[File:Menubar2.jpg|frame]]

= List of built-in menus =

Here is an incomplete list of FlightGear's menus, with links to their descriptions.

== File ==
* Reset
* [[Instant Replay#Continuous (disk-based) recordings|Flight Recorder Control]]
* Time Mode
* Screenshot
* Sound Configuration
* Input Devices
* [[TerraSync|Scenery Download]]
* Quit

== View ==
* Toggle Fullscreen
* Rendering Options
* View Options
* [[Cockpit view options|Cockpit View Options]]
* Toggle Glide Scope Tunnel
* [[Instant Replay]]
* [[Earthview|Earthview Orbital Rendering]]
* ALS Filter Effects

== Location ==
* Position Aircraft In Air
* Select Airport
* Random Altitude
* Tower Position

== Autopilot ==
* [[Autopilot#Autopilot Settings|Autopilot Settings]]
* [[Route Manager]]
* Previous Waypoint
* Next Waypoint

== Environment ==
* [[Weather]]
* Environment Settings
* [[Time|Time Settings]]
* [[Volcanoes]]

== Equipment ==
* [[Map]]
* Stopwatch
* Fuel and Payload
* Radio Settings
* [[GPS|GPS Settings]]
* Instrument Settings
* Light Switches
* [[Aircraft failure system|Random Failures]]
* [[Aircraft failure system|System Failures]]
* [[Aircraft failure system|Instrument Failures]]

== AI ==
* Traffic and Scenario Settings
* ATC Services in Range
* Wingman Controls
* [[AI Scenery Objects|AI Objects]]

== Multiplayer ==
* [[Multiplayer|Multiplayer Settings]]
* [[FGCom|FGCom Settings]]
* [[Chat Menu]]
* [[Pilot List]]
* [[Carrier over MP|MPCarrier Selection]]
* [[Swift|Swift Connection]]

== Debug ==
* Reload GUI
* Reload HUD
* [[Property Browser]]
* [[Nasal Console]]
...

== Help ==
* Aircraft Help
* [[Aircraft Checklists]]
* Common Aircraft Keys
* [[Tutorials]]
* About

[[Category:FlightGear feature]]
[[Category:Menubar]]
[[Category:Lists]]