FlightGear wiki - User contributions [en]

Airbus A320 family

2026-08-10T09:41:43Z

Octal450: Removed AI-slop and useless AI slop "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 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)

== Fly-by-Wire ==
Compared to Boeing aircraft, the A320 fly-by-wire system several differences:
* The aircraft trims the elevators automatically when in Normal Law. Attempting to trim will result in "fighting" the fly-by-wire.
* The aircraft holds pitch and roll angles when the sidestick is centered.
* Moving the sidestick commands a roll rate and/or a load factor maneuver (for pitch).
* In Normal Law, the system will overpower the pilot to prevent overspeeds, stalls, bank angles above 67 degrees, and a few others.

== FADEC ==
* Engine thrust levers command manual thrust, with fixed detents providing Climb, MCT/Flex, or TOGA power. When Auto Thrust is engaged, the lever position dictates the max power Auto Thrust may command. MCT/Flex and TOGA continue to provide fixed thrust, while the Climb position allows Auto Thrust operation, and dictates that the maximum power allowed is the climb thrust limit.

== FCU Selector Knobs ==
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 counterclockwise
|-
! 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
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]]
[[fr:Airbus A320 family]]

Airbus A330

2026-08-10T09:33:49Z

Octal450: Undo revision 146747 by Servo (talk)

{{:{{PAGENAME}}/info}}

The '''Airbus A330''' is a series of twinjet narrow body commercial passenger jets manufactured by Airbus Industrié (Airbus SE).

This is an accurate, and complex recreation of the Airbus A330.

Remove to remove -master when downloading!

'''Development is currently on hold awaiting restructuring.'''

== Airbus_A330 Overview ==

GE - [https://en.m.wikipedia.org/wiki/General_Electric_CF6 General Electric CF6]

PW - [https://en.m.wikipedia.org/wiki/Pratt_%26_Whitney_PW4000 Pratt & Whitney PW4000] (-100)

RR - [https://en.m.wikipedia.org/wiki/Rolls-Royce_Trent_700 Rolls Royce Trent 700]

Includes:
* A330-203 (GE)
* A330-223 (PW)
* A330-243 (RR)
* A330-223F (PW)
* A330-243F (RR)
* A330-303 (GE)
* A330-323 (PW)
* A330-343 (RR)
* Voyager KC2/KC3 (A330-243 RR)
* KC-30A (A330 MRTT) (A330-203 GE)

Solely, the KC2, KC3 and KC30A (A330 MRTT) are damage comapatiable by OPRF standards and are the most advanced aerial refueling tankers currently available in FG.

== Development Team ==
* FDM: Josh Davidson (Octal450)
* Systems: Josh Davidson (Octal450), Jonanthan Redpath (legoboyvdlp)
* Cockpit: Thorsten Herrmann (TH-555), Josh Davidson (Octal450), Jonanthan Redpath (legoboyvdlp)
* Instruments: Josh Davidson (Octal450), Jonanthan Redpath (legoboyvdlp)

== Aircraft help ==
{| class="keytable"
! Key !! Function
|-
| {{key press|1}}
| Show Captain's View
|-
| {{key press|2}}
| Show First Officer's View
|-
| {{key press|3}}
| Show Overhead View
|-
| {{key press|4}}
| Show Forward Pedestal View
|-
| {{key press|5}}
| Show Aft Pedestal View
|-
| {{key press|6}}
| Show FCU Panel View
|-
| {{key press|F1}}
| Disengage/Decrease Reverse Thrust
|-
| {{key press|F2}}
| Engage/Increase Reverse Thrust
|-
| {{key press|DEL}}
| Toggle Thrust Reversers
|-
| {{key press|E}}
| Set Idle Thrust
|-
| {{key press|F}}
| Set TOGA Thrust
|-
| {{key press|CTRL|B}}
| Cycle Spoilers
|-
| {{key press|Shift|B}}
| Toggle Parking Brake
|-
| {{key press|CTRL|D}}
| Disconnect Autothrottle
|-
| {{key press|Shift|D}}
| Disconnect Autopilot
|-
| {{key press|CTRL|F}}
| Set MCT/FLX Thrust
|-
| {{key press|Shift|F}}
| Set CL Thrust
|}

{{Airbus}}

[[Category:Airliners]]
[[Category:Red Griffin ATC compatible aircraft]]
[[Category:Octal450 hangar]]

Template:Boeing

2026-08-10T09:21:14Z

Octal450:

{{Navbox
| name = Boeing
| title = {{LangSwitch
| de = [[:Category:Boeing|Boeing]] Flugzeuge
| en = [[:Category:Boeing|Boeing]] aircraft
| fr = Aéronefs [[:Category:Boeing|Boeing]]
| zh = [[:Category:Boeing|波音]]飞机
}}
| listclass = hlist

| group1 = {{LangSwitch
| de = Ziviles Flugzeuge
| en = Civilian aircraft
| fr = Aéronefs civil
| zh = 民用飞机
}}
| list1 =
* {{LangSwitch
| de = [[:de:Boeing 314|314]]
| en = [[Boeing 314|314]]
}}
* {{LangSwitch
| de = [[:de:Boeing 707-420|707]] ([[Boeing 707-320C|-320C/älter]])
| en = [[Boeing 707|707]] ([[Boeing 707-320C|older]])
| pt = [[Boeing 707|707]] ([[Boeing 707-320C|anterior]])
}}
* [[Boeing 717|717]]
* [[Boeing 727|727]]
* {{LangSwitch
| de = [[Boeing 737|737]] ([[:de:Boeing 737-100|-100]]/[[Boeing 737-300|-300]]/[[Boeing 737NG|NG]])
| en = [[Boeing 737|737]] ([[Boeing 737-100|-100]]/[[Boeing 737-300|-300]]/[[Boeing 737NG|NG]]/[[Boeing 737-800YV|YV]])
| fr = [[Boeing 737|737]] ([[Boeing 737-100|-100]]/[[Boeing 737-300|-300]]/[[Boeing 737NG|NG]])
}}
* {{LangSwitch
| de = [[Boeing 747|747]] ([[Boeing 747-100|-100]]/[[Boeing 747-200|-200]]/[[:de:Boeing 747-400|-400]]/[[Boeing 747-8i|-8]])
| en = [[Boeing 747|747]] ([[Boeing 747-100|-100]]/[[Boeing 747-200|-200]]/[[Boeing 747-400|-400]]/[[Boeing 747-8i|-8]])
| nl = [[Boeing 747|747]] ([[Boeing 747-100|-100]]/[[Boeing 747-200|-200]]/[[:nl:Boeing 747-400|-400]]/[[Boeing 747-8i|-8]])
}}
* [[Boeing 757|757]]
* [[Boeing 767|767]]
* {{LangSwitch
| en = [[Boeing 777|777]]
| fr = [[:fr:Boeing 777|777]]
}}
* [[Boeing 787-8 Dreamliner|787]]

| group2 = {{LangSwitch
| de = Militärisches Flugzeuge
| en = Military aircraft
| fr = Aéronefs militaire
| zh = 军用飞机
}}
| list2 =
* {{LangSwitch
| de = [[:de:Douglas A-4 Skyhawk|A-4]]
| en = [[Douglas A-4 Skyhawk|A-4]]
}}
* [[Boeing B-17 Flying Fortress|B-17]]
* {{LangSwitch
| en = [[Boeing B-29 Superfortress|B-29]]
| fr = [[:fr:Boeing B-29 Superfortress|B-29]]
}}
* [[Boeing B-52|B-52]]
* [[C-17 Globemaster III]]
* [[Boeing 757|C-32A/B]]
* [[Boeing E-3 Sentry|E-3]]
* {{LangSwitch
| en = [[McDonnell Douglas F-15 Eagle|F-15]]
| fr = [[:fr:McDonnell Douglas F-15 Eagle|F-15]]
}}
* [[Boeing KC-135E|KC-135E]]
* {{LangSwitch
| en = [[Boeing-Stearman Model 75|PT-17]]
| es = [[:es:Boeing-Stearman Model 75|PT-17]]
}}

| group3 = {{LangSwitch
| de = Hubschrauber
| en = Helicopters
| fr = Hélicoptères
| zh = 直升机
}}
| list3 =
* [[AH-64 Apache|AH-64]]
* [[CH-47 Chinook Helicopter|CH-47]]
* [[Boeing-Sikorsky RAH-66 Comanche|RAH-66]]
* [[Bell Boeing V-22 Osprey|V-22]]
}}<includeonly>{{main other|[[Category:Boeing]]}}</includeonly><noinclude>
{{Informative template|1=
__NOTOC__
== Goal ==
This navigation template links together aircraft manufactured by Boeing.

Adding this template to a page in the article namespace will automatically add [[:Category:Boeing]] to that page.

== Usage ==
Put this line before the categories and the language links at the bottom of the article.

{{obr}}'''Boeing'''{{cbr}}

}}

[[Category:Manufacturer navigation templates]]
</noinclude>

Boeing 737-800YV/info

2026-08-10T09:19:43Z

Octal450:

<includeonly>{{infobox aircraft
| name = Boeing 737-800YV
| hangar = none
| image = 737-800YV.png
| aircraft = 737-800YV
| type = Airliner
| config = Narrow-body aircraft/Low wing aircraft/Retractable gear aircraft
| propulsion = Twinjet
| manufacturer = Boeing
| authors = Michael Soitanen, YV3399, and Octal450
| fdm = JSBSim
| status = Early production
| navbar = 1
| devel-repo = https://github.com/YV3399/737-800YV
}}</includeonly><noinclude>
This is the aircraft infobox subpage of the [[Boeing 737-800YV]].
[[Category:Aircraft infobox documentation]]
</noinclude>

User talk:SP-NTX

2026-08-09T16:34:07Z

Octal450:

{{Welcome to the wiki|added-by=Johan G}}

== content about AI ==

I sincerely apologize for posting invitation links, but I believe we are now in the AI era, and integrating AI usage is necessary. If FG doesn't adopt AI, it will inevitably be overtaken by other open-source flight simulators.

Actually, the page [[Howto:Create new landmark models]] is created by me.

Ask me if I give a f
[[User:SP-NTX|SP-NTX]] ([[User talk:SP-NTX|talk]]) 22:51, 8 August 2026 (UTC)

you posted it on a public website on my own discussion page and I will do whatever I want with it [[User:SP-NTX|SP-NTX]] ([[User talk:SP-NTX|talk]]) 22:56, 8 August 2026 (UTC)

@Sierra - FG is adopting AI. Please see the statement at https://docs.flightgear.org/contributors-guide/guidelines/generative-AI.html. In addition to this, there are several core developers who are using AI to aid them in developing new features for FG releases. at the moment a lot of these are infra related so an end user typically will not notice the impact, if it is done well. [[User:SammySkycrafts|SammySkycrafts]] ([[User talk:SammySkycrafts|talk]]) 22:58, 8 August 2026 (UTC)

"I believe we are now in the AI era, and integrating AI usage is necessary. If FG doesn't adopt AI, it will inevitably be overtaken by other open-source flight simulators."

Is this some sort of joke? Or do you really believe such nonsense? AI is a ridiculous fad of nonsense and false information. [[User:Octal450|Octal450]] ([[User talk:Octal450|talk]]) 16:34, 9 August 2026 (UTC)

Boeing 717

2026-08-03T06:20:28Z

Octal450: /* Development Status */

{{:{{PAGENAME}}/info}}

The '''Boeing 717''' is a twinjet narrowbody commercial airliner originally created by the McDonnell Douglas Corporation as the MD-95, to replace aging [[DC-9]]s. It is essentially a DC-9 with new avionics, systems, and engines, adopting several technologies from the [[MD-90]]. The project was completed by Boeing when Boeing bought McDonnell Douglas and rebranded as the Boeing 717. Boeing implemented several changes from the originally adopted MD-95 project, however, the airplane was completed by the former MD-95 project team.

This is an accurate and complex recreation of the Boeing 717.

== Overview ==
Includes the Boeing 717-200 with selectable Rolls-Royce BR715A1-30 or BR715C1-30 engines.

See the right InfoBox for the repository or download. Remember to rename the aircraft's folder to "717". DOWNLOAD NOT YET AVAILABLE.

== Development Status ==
Status denotes simulated functionality. Items marked as done may still be improved upon.

* Aerodynamics: {{done}}
* Air Conditioning: {{done}}
* APU: {{done}}
* Autoflight: {{progressbar|90}}
* Caution and Warning: {{progressbar|30}}
* EAD Display: {{progressbar|90}}
* Electrical: {{done}}
* Exterior Model: {{done}}
* Flight Controls: {{done}}
* FMS and MCDU: {{progressbar|50}}
* Fuel: {{done}}
* Hydraulics: {{done}}
* ISFD Display: {{done}}
* IRS: {{done}}
* Landing Gear and Brakes: {{done}}
* Mach Trim and Yaw Damper: {{done}}
* ND Displays: {{progressbar|10}}
* PFD Displays: {{progressbar|90}}
* Pneumatics: {{done}}
* Pressurization: {{done}}
* RR BR715 Engines and FADEC: {{done}}
* SD Display: {{progressbar|90}}
* Virtual Cockpit: {{progressbar|50}}
* Weight/Balance: {{done}}

== Development Team ==
* Flight Dynamics, Systems, Instruments: Josh Davidson (Octal450)
* 3D/Textures: Gary Neely (Buckaroo), Josh Davidson (Octal450)

== Documentation ==
=== Written Documentation ===
Written documentation for this aircraft is available [https://github.com/Octal450/FlightGear-Aircraft-Documentation/tree/master/717 here].

=== Shortcut Keys ===
{| class="keytable"
! Key !! Function
|-
| {{key press|1}}
| Show Captain View
|-
| {{key press|2}}
| Show First Officer View
|-
| {{key press|3}}
| Show Overhead View
|-
| {{key press|4}}
| Show Forward Pedestal View
|-
| {{key press|5}}
| Show Aft Pedestal View
|-
| {{key press|6}}
| Show Glareshield View
|-
| {{key press|7}}
| Show MCDU View
|-
| {{key press|F1}}
| Disengage/Decrease Reverse Thrust
|-
| {{key press|F2}}
| Engage/Increase Reverse Thrust
|-
| {{key press|DEL}}
| Toggle Thrust Reversers
|-
| {{key press|C}}
| Reset Current View
|-
| {{key press|E}}
| Set Throttles to Idle
|-
| {{key press|F}}
| Set Throttles to Thrust Limit
|-
| {{key press|CTRL|B}}
| Cycle Spoilers
|-
| {{key press|Shift|B}}
| Toggle Parking Brake
|-
| {{key press|Shift|C}}
| Open Checklists
|-
| {{key press|CTRL|D}}
| Autothrust Disconnect Button
|-
| {{key press|Shift|D}}
| Autoflight Disconnect Button
|-
| {{key press|Shift|F}}
| Set Throttles to Full
|-
| {{key press|CTRL|G}}
| Go Around Button
|-
| {{key press|Shift|P}}
| Open CG Applet
|}

{{Boeing}}
{{MDouglas}}

[[Category:Airliners]]
[[Category:Octal450 hangar]]
[[Category:Red Griffin ATC compatible aircraft]]

McDonnell Douglas MD-90

2026-08-03T06:20:20Z

Octal450: /* Development Status */

{{:{{PAGENAME}}/info}}

The '''McDonnell Douglas MD-90''' is a twinjet narrowbody commercial airliners created by the McDonnell Douglas Corporation as the successor to the [[MD-80]].

This is an accurate and complex recreation of the MD-90-30, the only series produced. Other variants such as the MD-90-55 were cancelled and never built.

== Overview ==
Currently, this project is simulating the Enhanced Flight Deck (EFD) version of the MD-90-30 with V2528-D5 engines. This is the only simulation project attempting to do so with any degree of accuracy. This project was announced celebrating Octal450's 10-year development anniversary.

See the right InfoBox for the repository or download. Remember to rename the aircraft's folder to "MD-90". DOWNLOAD NOT YET AVAILABLE.

== Development Status ==
Status denotes simulated functionality. Items marked as done may still be improved upon.

* Aerodynamics: {{done}}
* AFMS and MCDU: {{progressbar|50}}
* Air Conditioning: {{done}}
* APU: {{done}}
* Autoflight: {{progressbar|90}}
* Caution and Warning: {{progressbar|30}}
* EAD Display: {{progressbar|90}}
* Electrical: {{done}}
* Exterior Model: {{done}}
* Flight Controls: {{done}}
* Fuel: {{done}}
* Hydraulics: {{done}}
* IAE V2500 Engines and FADEC: {{done}}
* IRS: {{done}}
* Landing Gear and Brakes: {{done}}
* Mach Trim and Yaw Damper: {{done}}
* ND Displays: {{progressbar|10}}
* PFD Displays: {{progressbar|90}}
* Pneumatics: {{done}}
* Pressurization: {{done}}
* SD Display: {{progressbar|90}}
* Virtual Cockpit: {{progressbar|80}}
* Weight/Balance: {{done}}

== Development Team ==
* Flight Dynamics, Systems, Instruments: Josh Davidson (Octal450)
* 3D/Textures: Semir Gebran (CaptB), Gary Neely (Buckaroo)

== Documentation ==
=== Written Documentation ===
Written documentation for this aircraft is available [https://github.com/Octal450/FlightGear-Aircraft-Documentation/tree/master/MD-90 here].

=== Shortcut Keys ===
{| class="keytable"
! Key !! Function
|-
| {{key press|1}}
| Show Captain View
|-
| {{key press|2}}
| Show First Officer View
|-
| {{key press|3}}
| Show Overhead View
|-
| {{key press|4}}
| Show Forward Pedestal View
|-
| {{key press|5}}
| Show Aft Pedestal View
|-
| {{key press|6}}
| Show Glareshield View
|-
| {{key press|7}}
| Show MCDU View
|-
| {{key press|F1}}
| Disengage/Decrease Reverse Thrust
|-
| {{key press|F2}}
| Engage/Increase Reverse Thrust
|-
| {{key press|C}}
| Reset Current View
|-
| {{key press|E}}
| Set Throttles to Idle
|-
| {{key press|F}}
| Set Throttles to Thrust Limit
|-
| {{key press|DEL}}
| Toggle Thrust Reversers
|-
| {{key press|CTRL|B}}
| Cycle Spoilers
|-
| {{key press|Shift|B}}
| Toggle Parking Brake
|-
| {{key press|Shift|C}}
| Open Checklists
|-
| {{key press|CTRL|D}}
| Autothrust Disconnect Button
|-
| {{key press|Shift|D}}
| Autoflight Disconnect Button
|-
| {{key press|Shift|F}}
| Set Throttles to Full
|-
| {{key press|CTRL|G}}
| Takeoff/Go Around Button
|-
| {{key press|Shift|P}}
| Open CG Applet
|}

{{MDouglas}}

[[Category:Airliners]]
[[Category:Octal450 hangar]]
[[Category:Red Griffin ATC compatible aircraft]]

McDonnell Douglas MD-80

2026-08-03T06:19:59Z

Octal450: /* Development Status */

{{:{{PAGENAME}}/info}}

The '''McDonnell Douglas MD-80''' is a series of twinjet narrowbody commercial airliners created by the McDonnell Douglas Corporation as the successor to the [[DC-9]].

This is an accurate and complex recreation of the MD-80 series. Stable versions of the aircraft are uploaded to [[FGAddon]].

== Overview ==
Includes:
* MD-81 (JT8D-217)
* MD-82 (JT8D-217A)
* MD-83 (JT8D-219)
* MD-87 (JT8D-217C, Optional Firetank System)

See the right InfoBox for the repository or download. Remember to rename the aircraft's folder to "MD-80".

== Development Status ==
Status denotes simulated functionality. Items marked as done may still be improved upon.

* Aerodynamics: {{done}}
* AHRS: {{done}}
* Air Conditioning: {{done}}
* Analog Instruments: {{progressbar|90}}
* APU: {{done}}
* Autoflight: {{progressbar|90}}
* Caution and Warning: {{progressbar|30}}
* EDP and SDP Instruments: {{done}}
* Electrical: {{done}}
* Exterior Model: {{done}}
* Flight Controls: {{done}}
* Fuel: {{done}}
* Honeywell AFMS and MCDU: {{not done}}
* Honeywell HT9100 FMS and MCDU: {{progressbar|40}}
* Hydraulics: {{done}}
* IRS: {{done}}
* Landing Gear and Brakes: {{done}}
* Mach Trim and Yaw Damper: {{done}}
* ND Displays: {{progressbar|10}}
* PFD Displays: {{progressbar|90}}
* Pneumatics: {{done}}
* Pressurization: {{done}}
* PW JT8D Engines and TRI/TRP: {{done}}
* Virtual Cockpit: {{progressbar|80}}
* Weight/Balance: {{done}}

== Development Team ==
* Flight Dynamics, Systems, Instruments: Josh Davidson (Octal450)
* 3D/Textures: Gary Neely (Buckaroo)

== Documentation ==
=== Written Documentation ===
Written documentation for this aircraft is available [https://github.com/Octal450/FlightGear-Aircraft-Documentation/tree/master/MD-80 here].

Written documentation for the HT9100 FMS and MCDU is available [https://github.com/Octal450/FlightGear-Aircraft-Documentation/tree/master/HT9100 here].

=== Shortcut Keys ===
{| class="keytable"
! Key !! Function
|-
| {{key press|1}}
| Show Captain View
|-
| {{key press|2}}
| Show First Officer View
|-
| {{key press|3}}
| Show Overhead View
|-
| {{key press|4}}
| Show Forward Pedestal View
|-
| {{key press|5}}
| Show Aft Pedestal View
|-
| {{key press|6}}
| Show Glareshield View
|-
| {{key press|7}}
| Show MCDU View
|-
| {{key press|F1}}
| Disengage/Decrease Reverse Thrust
|-
| {{key press|F2}}
| Engage/Increase Reverse Thrust
|-
| {{key press|C}}
| Reset Current View
|-
| {{key press|E}}
| Set Throttles to Idle
|-
| {{key press|F}}
| Set Throttles to Thrust Limit
|-
| {{key press|DEL}}
| Toggle Thrust Reversers
|-
| {{key press|CTRL|B}}
| Cycle Spoilers
|-
| {{key press|Shift|B}}
| Toggle Parking Brake
|-
| {{key press|Shift|C}}
| Open Checklists
|-
| {{key press|CTRL|D}}
| Autothrust Disconnect Button
|-
| {{key press|Shift|D}}
| Autoflight Disconnect Button
|-
| {{key press|Shift|F}}
| Set Throttles to Full
|-
| {{key press|CTRL|G}}
| Takeoff/Go Around Button
|-
| {{key press|Shift|K}}
| Toggle MD-87 Firetank Salvo Drop
|-
| {{key press|Shift|P}}
| Open Performance Applet
|}

== Development Videos ==
[[User:Octal450|Octal450]] publishes periodic videos showcasing the latest developments in a [https://www.youtube.com/playlist?list=PL8TVI6JZUbxlSboD5L-jQ-MXkhPBBVnJE YouTube playlist].

{{MDouglas}}

[[Category:Airliners]]
[[Category:Octal450 hangar]]
[[Category:Red Griffin ATC compatible aircraft]]

McDonnell Douglas MD-80

2026-07-31T22:17:34Z

Octal450:

{{:{{PAGENAME}}/info}}

The '''McDonnell Douglas MD-80''' is a series of twinjet narrowbody commercial airliners created by the McDonnell Douglas Corporation as the successor to the [[DC-9]].

This is an accurate and complex recreation of the MD-80 series. Stable versions of the aircraft are uploaded to [[FGAddon]].

== Overview ==
Includes:
* MD-81 (JT8D-217)
* MD-82 (JT8D-217A)
* MD-83 (JT8D-219)
* MD-87 (JT8D-217C, Optional Firetank System)

See the right InfoBox for the repository or download. Remember to rename the aircraft's folder to "MD-80".

== Development Status ==
Status denotes simulated functionality. Items marked as done may still be improved upon.

* Aerodynamics: {{done}}
* AHRS: {{done}}
* Air Conditioning: {{done}}
* Analog Instruments: {{progressbar|90}}
* APU: {{done}}
* Autoflight: {{progressbar|90}}
* Caution and Warning: {{progressbar|30}}
* EDP and SDP Instruments: {{done}}
* Electrical: {{done}}
* Exterior Model: {{done}}
* Flight Controls: {{done}}
* Fuel: {{done}}
* Honeywell AFMS and MCDU: {{not done}}
* Honeywell HT9100 FMS and MCDU: {{progressbar|40}}
* Hydraulics: {{done}}
* IRS: {{done}}
* Landing Gear and Brakes: {{done}}
* Mach Trim and Yaw Damper: {{done}}
* ND Displays: {{progressbar|10}}
* PFD Displays: {{progressbar|90}}
* Pneumatics: {{progressbar|90}}
* Pressurization: {{done}}
* PW JT8D Engines and TRI/TRP: {{done}}
* Virtual Cockpit: {{progressbar|80}}
* Weight/Balance: {{done}}

== Development Team ==
* Flight Dynamics, Systems, Instruments: Josh Davidson (Octal450)
* 3D/Textures: Gary Neely (Buckaroo)

== Documentation ==
=== Written Documentation ===
Written documentation for this aircraft is available [https://github.com/Octal450/FlightGear-Aircraft-Documentation/tree/master/MD-80 here].

Written documentation for the HT9100 FMS and MCDU is available [https://github.com/Octal450/FlightGear-Aircraft-Documentation/tree/master/HT9100 here].

=== Shortcut Keys ===
{| class="keytable"
! Key !! Function
|-
| {{key press|1}}
| Show Captain View
|-
| {{key press|2}}
| Show First Officer View
|-
| {{key press|3}}
| Show Overhead View
|-
| {{key press|4}}
| Show Forward Pedestal View
|-
| {{key press|5}}
| Show Aft Pedestal View
|-
| {{key press|6}}
| Show Glareshield View
|-
| {{key press|7}}
| Show MCDU View
|-
| {{key press|F1}}
| Disengage/Decrease Reverse Thrust
|-
| {{key press|F2}}
| Engage/Increase Reverse Thrust
|-
| {{key press|C}}
| Reset Current View
|-
| {{key press|E}}
| Set Throttles to Idle
|-
| {{key press|F}}
| Set Throttles to Thrust Limit
|-
| {{key press|DEL}}
| Toggle Thrust Reversers
|-
| {{key press|CTRL|B}}
| Cycle Spoilers
|-
| {{key press|Shift|B}}
| Toggle Parking Brake
|-
| {{key press|Shift|C}}
| Open Checklists
|-
| {{key press|CTRL|D}}
| Autothrust Disconnect Button
|-
| {{key press|Shift|D}}
| Autoflight Disconnect Button
|-
| {{key press|Shift|F}}
| Set Throttles to Full
|-
| {{key press|CTRL|G}}
| Takeoff/Go Around Button
|-
| {{key press|Shift|K}}
| Toggle MD-87 Firetank Salvo Drop
|-
| {{key press|Shift|P}}
| Open Performance Applet
|}

== Development Videos ==
[[User:Octal450|Octal450]] publishes periodic videos showcasing the latest developments in a [https://www.youtube.com/playlist?list=PL8TVI6JZUbxlSboD5L-jQ-MXkhPBBVnJE YouTube playlist].

{{MDouglas}}

[[Category:Airliners]]
[[Category:Octal450 hangar]]
[[Category:Red Griffin ATC compatible aircraft]]

McDonnell Douglas MD-90

2026-07-31T05:46:03Z

Octal450: /* Development Status */

{{:{{PAGENAME}}/info}}

The '''McDonnell Douglas MD-90''' is a twinjet narrowbody commercial airliners created by the McDonnell Douglas Corporation as the successor to the [[MD-80]].

This is an accurate and complex recreation of the MD-90-30, the only series produced. Other variants such as the MD-90-55 were cancelled and never built.

== Overview ==
Currently, this project is simulating the Enhanced Flight Deck (EFD) version of the MD-90-30 with V2528-D5 engines. This is the only simulation project attempting to do so with any degree of accuracy. This project was announced celebrating Octal450's 10-year development anniversary.

See the right InfoBox for the repository or download. Remember to rename the aircraft's folder to "MD-90". DOWNLOAD NOT YET AVAILABLE.

== Development Status ==
Status denotes simulated functionality. Items marked as done may still be improved upon.

* Aerodynamics: {{done}}
* AFMS and MCDU: {{progressbar|50}}
* Air Conditioning: {{done}}
* APU: {{done}}
* Autoflight: {{progressbar|90}}
* Caution and Warning: {{progressbar|30}}
* EAD Display: {{progressbar|90}}
* Electrical: {{done}}
* Exterior Model: {{done}}
* Flight Controls: {{done}}
* Fuel: {{done}}
* Hydraulics: {{done}}
* IAE V2500 Engines and FADEC: {{done}}
* IRS: {{done}}
* Landing Gear and Brakes: {{done}}
* Mach Trim and Yaw Damper: {{done}}
* ND Displays: {{progressbar|10}}
* PFD Displays: {{progressbar|90}}
* Pneumatics: {{progressbar|90}}
* Pressurization: {{done}}
* SD Display: {{progressbar|90}}
* Virtual Cockpit: {{progressbar|80}}
* Weight/Balance: {{done}}

== Development Team ==
* Flight Dynamics, Systems, Instruments: Josh Davidson (Octal450)
* 3D/Textures: Semir Gebran (CaptB), Gary Neely (Buckaroo)

== Documentation ==
=== Written Documentation ===
Written documentation for this aircraft is available [https://github.com/Octal450/FlightGear-Aircraft-Documentation/tree/master/MD-90 here].

=== Shortcut Keys ===
{| class="keytable"
! Key !! Function
|-
| {{key press|1}}
| Show Captain View
|-
| {{key press|2}}
| Show First Officer View
|-
| {{key press|3}}
| Show Overhead View
|-
| {{key press|4}}
| Show Forward Pedestal View
|-
| {{key press|5}}
| Show Aft Pedestal View
|-
| {{key press|6}}
| Show Glareshield View
|-
| {{key press|7}}
| Show MCDU View
|-
| {{key press|F1}}
| Disengage/Decrease Reverse Thrust
|-
| {{key press|F2}}
| Engage/Increase Reverse Thrust
|-
| {{key press|C}}
| Reset Current View
|-
| {{key press|E}}
| Set Throttles to Idle
|-
| {{key press|F}}
| Set Throttles to Thrust Limit
|-
| {{key press|DEL}}
| Toggle Thrust Reversers
|-
| {{key press|CTRL|B}}
| Cycle Spoilers
|-
| {{key press|Shift|B}}
| Toggle Parking Brake
|-
| {{key press|Shift|C}}
| Open Checklists
|-
| {{key press|CTRL|D}}
| Autothrust Disconnect Button
|-
| {{key press|Shift|D}}
| Autoflight Disconnect Button
|-
| {{key press|Shift|F}}
| Set Throttles to Full
|-
| {{key press|CTRL|G}}
| Takeoff/Go Around Button
|-
| {{key press|Shift|P}}
| Open CG Applet
|}

{{MDouglas}}

[[Category:Airliners]]
[[Category:Octal450 hangar]]
[[Category:Red Griffin ATC compatible aircraft]]

Boeing 717

2026-07-31T05:02:18Z

Octal450: /* Development Status */

{{:{{PAGENAME}}/info}}

The '''Boeing 717''' is a twinjet narrowbody commercial airliner originally created by the McDonnell Douglas Corporation as the MD-95, to replace aging [[DC-9]]s. It is essentially a DC-9 with new avionics, systems, and engines, adopting several technologies from the [[MD-90]]. The project was completed by Boeing when Boeing bought McDonnell Douglas and rebranded as the Boeing 717. Boeing implemented several changes from the originally adopted MD-95 project, however, the airplane was completed by the former MD-95 project team.

This is an accurate and complex recreation of the Boeing 717.

== Overview ==
Includes the Boeing 717-200 with selectable Rolls-Royce BR715A1-30 or BR715C1-30 engines.

See the right InfoBox for the repository or download. Remember to rename the aircraft's folder to "717". DOWNLOAD NOT YET AVAILABLE.

== Development Status ==
Status denotes simulated functionality. Items marked as done may still be improved upon.

* Aerodynamics: {{done}}
* Air Conditioning: {{done}}
* APU: {{done}}
* Autoflight: {{progressbar|90}}
* Caution and Warning: {{progressbar|30}}
* EAD Display: {{progressbar|90}}
* Electrical: {{done}}
* Exterior Model: {{done}}
* Flight Controls: {{done}}
* FMS and MCDU: {{progressbar|50}}
* Fuel: {{done}}
* Hydraulics: {{done}}
* ISFD Display: {{done}}
* IRS: {{done}}
* Landing Gear and Brakes: {{done}}
* Mach Trim and Yaw Damper: {{done}}
* ND Displays: {{progressbar|10}}
* PFD Displays: {{progressbar|90}}
* Pneumatics: {{progressbar|90}}
* Pressurization: {{done}}
* RR BR715 Engines and FADEC: {{done}}
* SD Display: {{progressbar|90}}
* Virtual Cockpit: {{progressbar|50}}
* Weight/Balance: {{done}}

== Development Team ==
* Flight Dynamics, Systems, Instruments: Josh Davidson (Octal450)
* 3D/Textures: Gary Neely (Buckaroo), Josh Davidson (Octal450)

== Documentation ==
=== Written Documentation ===
Written documentation for this aircraft is available [https://github.com/Octal450/FlightGear-Aircraft-Documentation/tree/master/717 here].

=== Shortcut Keys ===
{| class="keytable"
! Key !! Function
|-
| {{key press|1}}
| Show Captain View
|-
| {{key press|2}}
| Show First Officer View
|-
| {{key press|3}}
| Show Overhead View
|-
| {{key press|4}}
| Show Forward Pedestal View
|-
| {{key press|5}}
| Show Aft Pedestal View
|-
| {{key press|6}}
| Show Glareshield View
|-
| {{key press|7}}
| Show MCDU View
|-
| {{key press|F1}}
| Disengage/Decrease Reverse Thrust
|-
| {{key press|F2}}
| Engage/Increase Reverse Thrust
|-
| {{key press|DEL}}
| Toggle Thrust Reversers
|-
| {{key press|C}}
| Reset Current View
|-
| {{key press|E}}
| Set Throttles to Idle
|-
| {{key press|F}}
| Set Throttles to Thrust Limit
|-
| {{key press|CTRL|B}}
| Cycle Spoilers
|-
| {{key press|Shift|B}}
| Toggle Parking Brake
|-
| {{key press|Shift|C}}
| Open Checklists
|-
| {{key press|CTRL|D}}
| Autothrust Disconnect Button
|-
| {{key press|Shift|D}}
| Autoflight Disconnect Button
|-
| {{key press|Shift|F}}
| Set Throttles to Full
|-
| {{key press|CTRL|G}}
| Go Around Button
|-
| {{key press|Shift|P}}
| Open CG Applet
|}

{{Boeing}}
{{MDouglas}}

[[Category:Airliners]]
[[Category:Octal450 hangar]]
[[Category:Red Griffin ATC compatible aircraft]]

McDonnell Douglas MD-11

2026-07-27T04:12:40Z

Octal450: /* Development Status */

{{:{{PAGENAME}}/info}}

The '''McDonnell Douglas MD-11''' is a trijet widebody commercial airliner created by the McDonnell Douglas Corporation as the successor to the [[DC-10]]. It is the only modern trijet airliner, with a full glass cockpit, automatic systems, digital flight control system, and a full flight management system.

This is an accurate and complex recreation of the MD-11. Stable versions of the aircraft are uploaded to [[FGAddon]].

== Overview ==
Includes:
* MD-11 (GE CF6-80C2D1F and PW4462)
* MD-11F (GE CF6-80C2D1F and PW4462)
* Bonus KMD-11 (PW4462, Fictional)
** OPRF compatible

See the right InfoBox for the repository or download. Remember to rename the aircraft's folder to "MD-11".

== Development Status ==
Status denotes simulated functionality. Items marked as done may still be improved upon.

* Aerodynamics: {{done}}
* Air Conditioning: {{done}}
* APU: {{done}}
* Autoflight: {{progressbar|90}}
* Caution and Warning: {{progressbar|30}}
* EAD Display: {{progressbar|90}}
* Electrical: {{done}}
* Exterior Model: {{done}}
* Flight Controls: {{done}}
* FMS and MCDU: {{progressbar|50}}
* Fuel: {{done}}
* GE CF6 Engines and FADEC: {{done}}
* Hydraulics: {{done}}
* ISFD Display: {{done}}
* IRS: {{done}}
* Landing Gear and Brakes: {{done}}
* LSAS, RCWS, Yaw Damper: {{done}}
* ND Displays: {{progressbar|10}}
* PFD Displays: {{progressbar|90}}
* Pneumatics: {{done}}
* Pressurization: {{done}}
* PW4000 Engines and FADEC: {{done}}
* SD Display: {{progressbar|90}}
* Virtual Cockpit: {{progressbar|90}}
* Weight/Balance: {{done}}

== Development Team ==
* Flight Dynamics, Systems, Instruments: Josh Davidson (Octal450)
* 3D/Textures: Semir Gebran (CaptB), John Williams (tikibar), and Jormapaappa1235

== Documentation ==

=== Written Documentation ===
Written documentation for this aircraft is available [https://github.com/Octal450/FlightGear-Aircraft-Documentation/tree/master/MD-11 here].

=== Shortcut Keys ===
{| class="keytable"
! Key !! Function
|-
| {{key press|1}}
| Show Captain View
|-
| {{key press|2}}
| Show First Officer View
|-
| {{key press|3}}
| Show Overhead View
|-
| {{key press|4}}
| Show Forward Pedestal View
|-
| {{key press|5}}
| Show Aft Pedestal View
|-
| {{key press|6}}
| Show Glareshield View
|-
| {{key press|7}}
| Show MCDU View
|-
| {{key press|F1}}
| Disengage/Decrease Reverse Thrust
|-
| {{key press|F2}}
| Engage/Increase Reverse Thrust
|-
| {{key press|DEL}}
| Toggle Thrust Reversers
|-
| {{key press|C}}
| Reset Current View
|-
| {{key press|E}}
| Set Throttles to Idle
|-
| {{key press|F}}
| Set Throttles to Thrust Limit
|-
| {{key press|CTRL|B}}
| Cycle Spoilers
|-
| {{key press|Shift|B}}
| Toggle Parking Brake
|-
| {{key press|Shift|C}}
| Open Checklists
|-
| {{key press|CTRL|D}}
| Autothrust Disconnect Button
|-
| {{key press|Shift|D}}
| Autoflight Disconnect Button
|-
| {{key press|Shift|F}}
| Set Throttles to Full
|-
| {{key press|CTRL|G}}
| Go Around Button
|-
| {{key press|Shift|P}}
| Open CG Applet
|}

== Development Videos ==
[[User:Octal450|Octal450]] publishes periodic videos showcasing the latest developments in a [https://www.youtube.com/playlist?list=PL8TVI6JZUbxkrFiKIv8JQy9rl1_W_rI5v YouTube playlist].

== Tutorial Videos ==
{{#ev:youtube|K5gTjiUmslY|700px||Tutorial video in the '''Polish''' language by SP-ROM showing a flight in the MD-11 and some explanations. The demonstration may help people who don't speak Polish. (MD-11 state as at September 2025)}}

{{MDouglas}}

[[Category:Airliners]]
[[Category:Octal450 hangar]]
[[Category:Red Griffin ATC compatible aircraft]]

User talk:Servo

2026-07-20T05:34:56Z

Octal450: /* Scraping */

{{Template:Welcome to the wiki|realName=|name=Servo}}

-- [[User:New user message|New user message]] ([[User talk:New user message|talk]]) 20:52, 20 May 2026 (UTC)

== Repository link templates ==

Hi,

Minor request regarding links. To ease wiki maintenance, e.g., whenever we move the code again to another repository, please use templates for all infrastructural links. For example:
<pre><nowiki>[https://gitlab.com/flightgear/flightgear/blob/next/docs-mini/README-recordings.md docs-mini/README-recordings.md]</nowiki></pre>
Should be
<pre><nowiki>{{flightgear source | docs-mini/README-recordings.md | text = docs-mini/README-recordings.md}}</nowiki></pre>
You can find an overview of these templates at [[:Category:Repository link templates]].

Thanks and keep up the good work!

[[User:Gijs|Gijs]] ([[User talk:Gijs|talk]]) 09:29, 10 June 2026 (UTC)

: Thank you for the tip, and for keeping the infrastructure tidy. [[User:Servo|Servo]] ([[User talk:Servo|talk]]) 16:10, 10 June 2026 (UTC)

== Wiki crawler ==

Hi,

What is the idea behind your wiki crawler? If you need a dump for some legitimate goal, I'd rather provide you with a direct dump instead of encouraging people to run their own crawlers...

Thanks!

[[User:Gijs|Gijs]] ([[User talk:Gijs|talk]]) 18:40, 11 June 2026 (UTC)

: Actually my idea is to use the wiki dump for an MCP server. In addition, I've removed the crawler scripts in the repository. [[User:Servo|Servo]] ([[User talk:Servo|talk]]) 20:50, 11 June 2026 (UTC)

== Command line options ==

Hi! On the "Command line options" page, you pasted this part twice by mistake I think:

Gnome Applications > Accessories > Terminal
Xfce Applications > Terminal
A different approach would be pressing Alt F2. That should open a dialog box, wh

Could you please look into it and fix it? Thanks!
[[User:PlayeRom|PlayeRom]] ([[User talk:PlayeRom|talk]]) 18:57, 10 July 2026 (UTC)

: Ok, this has been fixed. [[User:Servo|Servo]] ([[User talk:Servo|talk]])

== Scraping ==
Hi, I hope your AI scraper isn't causing the immense lag the wiki has had. Can you confirm?
[[User:Octal450|Octal450]] ([[User talk:Octal450|talk]]) 22:12, 19 July 2026 (UTC)
:Actually, I didn't use a massive scraper. I just incrementally update the recently changed pages every few days after doing the initial full crawl. [[User:Servo|Servo]] ([[User talk:Servo|talk]]) 23:35, 19 July 2026 (UTC)
::Okay, and what exactly are you trying to do? I didn't understand from your page. [[User:Octal450|Octal450]] ([[User talk:Octal450|talk]]) 05:34, 20 July 2026 (UTC)

User talk:Servo

2026-07-20T05:34:47Z

Octal450: /* Scraping */

{{Template:Welcome to the wiki|realName=|name=Servo}}

-- [[User:New user message|New user message]] ([[User talk:New user message|talk]]) 20:52, 20 May 2026 (UTC)

== Repository link templates ==

Hi,

Minor request regarding links. To ease wiki maintenance, e.g., whenever we move the code again to another repository, please use templates for all infrastructural links. For example:
<pre><nowiki>[https://gitlab.com/flightgear/flightgear/blob/next/docs-mini/README-recordings.md docs-mini/README-recordings.md]</nowiki></pre>
Should be
<pre><nowiki>{{flightgear source | docs-mini/README-recordings.md | text = docs-mini/README-recordings.md}}</nowiki></pre>
You can find an overview of these templates at [[:Category:Repository link templates]].

Thanks and keep up the good work!

[[User:Gijs|Gijs]] ([[User talk:Gijs|talk]]) 09:29, 10 June 2026 (UTC)

: Thank you for the tip, and for keeping the infrastructure tidy. [[User:Servo|Servo]] ([[User talk:Servo|talk]]) 16:10, 10 June 2026 (UTC)

== Wiki crawler ==

Hi,

What is the idea behind your wiki crawler? If you need a dump for some legitimate goal, I'd rather provide you with a direct dump instead of encouraging people to run their own crawlers...

Thanks!

[[User:Gijs|Gijs]] ([[User talk:Gijs|talk]]) 18:40, 11 June 2026 (UTC)

: Actually my idea is to use the wiki dump for an MCP server. In addition, I've removed the crawler scripts in the repository. [[User:Servo|Servo]] ([[User talk:Servo|talk]]) 20:50, 11 June 2026 (UTC)

== Command line options ==

Hi! On the "Command line options" page, you pasted this part twice by mistake I think:

Gnome Applications > Accessories > Terminal
Xfce Applications > Terminal
A different approach would be pressing Alt F2. That should open a dialog box, wh

Could you please look into it and fix it? Thanks!
[[User:PlayeRom|PlayeRom]] ([[User talk:PlayeRom|talk]]) 18:57, 10 July 2026 (UTC)

: Ok, this has been fixed. [[User:Servo|Servo]] ([[User talk:Servo|talk]])

== Scraping ==
Hi, I hope your AI scraper isn't causing the immense lag the wiki has had. Can you confirm?
[[User:Octal450|Octal450]] ([[User talk:Octal450|talk]]) 22:12, 19 July 2026 (UTC)
:Actually, I didn't use a massive scraper. I just incrementally update the recently changed pages every few days after doing the initial full crawl. [[User:Servo|Servo]] ([[User talk:Servo|talk]]) 23:35, 19 July 2026 (UTC)
::Okay, and what exactly are you trying to do? I didn't understand from your page.[[User:Octal450|Octal450]] ([[User talk:Octal450|talk]]) 05:34, 20 July 2026 (UTC)

McDonnell Douglas MD-80

2026-07-20T05:34:06Z

Octal450: /* Overview */

{{:{{PAGENAME}}/info}}

The '''McDonnell Douglas MD-80''' is a series of twinjet narrowbody commercial airliners created by the McDonnell Douglas Corporation as the successor to the [[DC-9]].

This is an accurate and complex recreation of the MD-80 series. Stable versions of the aircraft are uploaded to [[FGAddon]].

== Overview ==
Includes:
* MD-81 (JT8D-217)
* MD-82 (JT8D-217A)
* MD-83 (JT8D-219)
* MD-87 (JT8D-217C, Optional Firetank System)

See the right InfoBox for the repository or download. Remember to rename the aircraft's folder to "MD-80".

== Development Status ==
Status denotes simulated functionality. Items marked as done may still be improved upon.

* Aerodynamics: {{done}}
* AHRS: {{done}}
* Air Conditioning: {{done}}
* Analog Instruments: {{progressbar|90}}
* APU: {{done}}
* Autoflight: {{progressbar|90}}
* Caution and Warning: {{progressbar|30}}
* EDP and SDP Instruments: {{done}}
* Electrical: {{done}}
* Exterior Model: {{done}}
* Flight Controls: {{done}}
* Fuel: {{done}}
* Honeywell AFMS and MCDU: {{not done}}
* Honeywell HT9100 FMS and MCDU: {{progressbar|40}}
* Hydraulics: {{done}}
* IRS: {{done}}
* Landing Gear and Brakes: {{done}}
* Mach Trim and Yaw Damper: {{done}}
* ND Displays: {{progressbar|10}}
* PFD Displays: {{progressbar|90}}
* Pneumatics: {{progressbar|90}}
* Pressurization: {{not done}}
* PW JT8D Engines and TRI/TRP: {{done}}
* Virtual Cockpit: {{progressbar|80}}
* Weight/Balance: {{done}}

== Development Team ==
* Flight Dynamics, Systems, Instruments: Josh Davidson (Octal450)
* 3D/Textures: Gary Neely (Buckaroo)

== Documentation ==
=== Written Documentation ===
Written documentation for this aircraft is available [https://github.com/Octal450/FlightGear-Aircraft-Documentation/tree/master/MD-80 here].

Written documentation for the HT9100 FMS and MCDU is available [https://github.com/Octal450/FlightGear-Aircraft-Documentation/tree/master/HT9100 here].

=== Shortcut Keys ===
{| class="keytable"
! Key !! Function
|-
| {{key press|1}}
| Show Captain View
|-
| {{key press|2}}
| Show First Officer View
|-
| {{key press|3}}
| Show Overhead View
|-
| {{key press|4}}
| Show Forward Pedestal View
|-
| {{key press|5}}
| Show Aft Pedestal View
|-
| {{key press|6}}
| Show Glareshield View
|-
| {{key press|7}}
| Show MCDU View
|-
| {{key press|F1}}
| Disengage/Decrease Reverse Thrust
|-
| {{key press|F2}}
| Engage/Increase Reverse Thrust
|-
| {{key press|C}}
| Reset Current View
|-
| {{key press|E}}
| Set Throttles to Idle
|-
| {{key press|F}}
| Set Throttles to Thrust Limit
|-
| {{key press|DEL}}
| Toggle Thrust Reversers
|-
| {{key press|CTRL|B}}
| Cycle Spoilers
|-
| {{key press|Shift|B}}
| Toggle Parking Brake
|-
| {{key press|Shift|C}}
| Open Checklists
|-
| {{key press|CTRL|D}}
| Autothrust Disconnect Button
|-
| {{key press|Shift|D}}
| Autoflight Disconnect Button
|-
| {{key press|Shift|F}}
| Set Throttles to Full
|-
| {{key press|CTRL|G}}
| Takeoff/Go Around Button
|-
| {{key press|Shift|K}}
| Toggle MD-87 Firetank Salvo Drop
|-
| {{key press|Shift|P}}
| Open Performance Applet
|}

== Development Videos ==
[[User:Octal450|Octal450]] publishes periodic videos showcasing the latest developments in a [https://www.youtube.com/playlist?list=PL8TVI6JZUbxlSboD5L-jQ-MXkhPBBVnJE YouTube playlist].

{{MDouglas}}

[[Category:Airliners]]
[[Category:Octal450 hangar]]
[[Category:Red Griffin ATC compatible aircraft]]

McDonnell Douglas MD-80

2026-07-20T03:55:29Z

Octal450: /* Development Status */

{{:{{PAGENAME}}/info}}

The '''McDonnell Douglas MD-80''' is a series of twinjet narrowbody commercial airliners created by the McDonnell Douglas Corporation as the successor to the [[DC-9]].

This is an accurate and complex recreation of the MD-80 series. Stable versions of the aircraft are uploaded to [[FGAddon]].

== Overview ==
Includes:
* MD-81 (JT8D-209)
* MD-82 (JT8D-217A)
* MD-83 (JT8D-219)
* MD-87 (JT8D-217C, Optional Firetank System)

See the right InfoBox for the repository or download. Remember to rename the aircraft's folder to "MD-80".

== Development Status ==
Status denotes simulated functionality. Items marked as done may still be improved upon.

* Aerodynamics: {{done}}
* AHRS: {{done}}
* Air Conditioning: {{done}}
* Analog Instruments: {{progressbar|90}}
* APU: {{done}}
* Autoflight: {{progressbar|90}}
* Caution and Warning: {{progressbar|30}}
* EDP and SDP Instruments: {{done}}
* Electrical: {{done}}
* Exterior Model: {{done}}
* Flight Controls: {{done}}
* Fuel: {{done}}
* Honeywell AFMS and MCDU: {{not done}}
* Honeywell HT9100 FMS and MCDU: {{progressbar|40}}
* Hydraulics: {{done}}
* IRS: {{done}}
* Landing Gear and Brakes: {{done}}
* Mach Trim and Yaw Damper: {{done}}
* ND Displays: {{progressbar|10}}
* PFD Displays: {{progressbar|90}}
* Pneumatics: {{progressbar|90}}
* Pressurization: {{not done}}
* PW JT8D Engines and TRI/TRP: {{done}}
* Virtual Cockpit: {{progressbar|80}}
* Weight/Balance: {{done}}

== Development Team ==
* Flight Dynamics, Systems, Instruments: Josh Davidson (Octal450)
* 3D/Textures: Gary Neely (Buckaroo)

== Documentation ==
=== Written Documentation ===
Written documentation for this aircraft is available [https://github.com/Octal450/FlightGear-Aircraft-Documentation/tree/master/MD-80 here].

Written documentation for the HT9100 FMS and MCDU is available [https://github.com/Octal450/FlightGear-Aircraft-Documentation/tree/master/HT9100 here].

=== Shortcut Keys ===
{| class="keytable"
! Key !! Function
|-
| {{key press|1}}
| Show Captain View
|-
| {{key press|2}}
| Show First Officer View
|-
| {{key press|3}}
| Show Overhead View
|-
| {{key press|4}}
| Show Forward Pedestal View
|-
| {{key press|5}}
| Show Aft Pedestal View
|-
| {{key press|6}}
| Show Glareshield View
|-
| {{key press|7}}
| Show MCDU View
|-
| {{key press|F1}}
| Disengage/Decrease Reverse Thrust
|-
| {{key press|F2}}
| Engage/Increase Reverse Thrust
|-
| {{key press|C}}
| Reset Current View
|-
| {{key press|E}}
| Set Throttles to Idle
|-
| {{key press|F}}
| Set Throttles to Thrust Limit
|-
| {{key press|DEL}}
| Toggle Thrust Reversers
|-
| {{key press|CTRL|B}}
| Cycle Spoilers
|-
| {{key press|Shift|B}}
| Toggle Parking Brake
|-
| {{key press|Shift|C}}
| Open Checklists
|-
| {{key press|CTRL|D}}
| Autothrust Disconnect Button
|-
| {{key press|Shift|D}}
| Autoflight Disconnect Button
|-
| {{key press|Shift|F}}
| Set Throttles to Full
|-
| {{key press|CTRL|G}}
| Takeoff/Go Around Button
|-
| {{key press|Shift|K}}
| Toggle MD-87 Firetank Salvo Drop
|-
| {{key press|Shift|P}}
| Open Performance Applet
|}

== Development Videos ==
[[User:Octal450|Octal450]] publishes periodic videos showcasing the latest developments in a [https://www.youtube.com/playlist?list=PL8TVI6JZUbxlSboD5L-jQ-MXkhPBBVnJE YouTube playlist].

{{MDouglas}}

[[Category:Airliners]]
[[Category:Octal450 hangar]]
[[Category:Red Griffin ATC compatible aircraft]]

User talk:Servo

2026-07-19T22:13:08Z

Octal450:

User talk:Servo

2026-07-19T22:12:37Z

Octal450:

{{Template:Welcome to the wiki|realName=|name=Servo}}

-- [[User:New user message|New user message]] ([[User talk:New user message|talk]]) 20:52, 20 May 2026 (UTC)

== Repository link templates ==

Hi,

Minor request regarding links. To ease wiki maintenance, e.g., whenever we move the code again to another repository, please use templates for all infrastructural links. For example:
<pre><nowiki>[https://gitlab.com/flightgear/flightgear/blob/next/docs-mini/README-recordings.md docs-mini/README-recordings.md]</nowiki></pre>
Should be
<pre><nowiki>{{flightgear source | docs-mini/README-recordings.md | text = docs-mini/README-recordings.md}}</nowiki></pre>
You can find an overview of these templates at [[:Category:Repository link templates]].

Thanks and keep up the good work!

[[User:Gijs|Gijs]] ([[User talk:Gijs|talk]]) 09:29, 10 June 2026 (UTC)

: Thank you for the tip, and for keeping the infrastructure tidy. [[User:Servo|Servo]] ([[User talk:Servo|talk]]) 16:10, 10 June 2026 (UTC)

== Wiki crawler ==

Hi,

What is the idea behind your wiki crawler? If you need a dump for some legitimate goal, I'd rather provide you with a direct dump instead of encouraging people to run their own crawlers...

Thanks!

[[User:Gijs|Gijs]] ([[User talk:Gijs|talk]]) 18:40, 11 June 2026 (UTC)

: Actually my idea is to use the wiki dump for an MCP server. In addition, I've removed the crawler scripts in the repository. [[User:Servo|Servo]] ([[User talk:Servo|talk]]) 20:50, 11 June 2026 (UTC)

== Command line options ==

Hi! On the "Command line options" page, you pasted this part twice by mistake I think:

Gnome Applications > Accessories > Terminal
Xfce Applications > Terminal
A different approach would be pressing Alt F2. That should open a dialog box, wh

Could you please look into it and fix it? Thanks!
[[User:PlayeRom|PlayeRom]] ([[User talk:PlayeRom|talk]]) 18:57, 10 July 2026 (UTC)

: Ok, this has been fixed. [[User:Servo|Servo]] ([[User talk:Servo|talk]])

Hi, I hope your AI scraper isn't causing the immense lag the wiki has had. Can you confirm?
[[User:Octal450|Octal450]] ([[User talk:Octal450|talk]]) 22:12, 19 July 2026 (UTC)

McDonnell Douglas MD-80

2026-07-16T05:39:01Z

Octal450:

{{:{{PAGENAME}}/info}}

The '''McDonnell Douglas MD-80''' is a series of twinjet narrowbody commercial airliners created by the McDonnell Douglas Corporation as the successor to the [[DC-9]].

This is an accurate and complex recreation of the MD-80 series. Stable versions of the aircraft are uploaded to [[FGAddon]].

== Overview ==
Includes:
* MD-81 (JT8D-209)
* MD-82 (JT8D-217A)
* MD-83 (JT8D-219)
* MD-87 (JT8D-217C, Optional Firetank System)

See the right InfoBox for the repository or download. Remember to rename the aircraft's folder to "MD-80".

== Development Status ==
Status denotes simulated functionality. Items marked as done may still be improved upon.

* Aerodynamics: {{done}}
* AHRS: {{done}}
* Air Conditioning: {{done}}
* Analog Instruments: {{progressbar|90}}
* APU: {{done}}
* Autoflight: {{progressbar|90}}
* Caution and Warning: {{progressbar|30}}
* EDP and SDP Instruments: {{not done}}
* Electrical: {{done}}
* Exterior Model: {{done}}
* Flight Controls: {{done}}
* Fuel: {{done}}
* Honeywell AFMS and MCDU: {{not done}}
* Honeywell HT9100 FMS and MCDU: {{progressbar|40}}
* Hydraulics: {{done}}
* IRS: {{done}}
* Landing Gear and Brakes: {{done}}
* Mach Trim and Yaw Damper: {{done}}
* ND Displays: {{progressbar|10}}
* PFD Displays: {{progressbar|90}}
* Pneumatics: {{progressbar|90}}
* Pressurization: {{not done}}
* PW JT8D Engines and TRI/TRP: {{done}}
* Virtual Cockpit: {{progressbar|80}}
* Weight/Balance: {{done}}

== Development Team ==
* Flight Dynamics, Systems, Instruments: Josh Davidson (Octal450)
* 3D/Textures: Gary Neely (Buckaroo)

== Documentation ==
=== Written Documentation ===
Written documentation for this aircraft is available [https://github.com/Octal450/FlightGear-Aircraft-Documentation/tree/master/MD-80 here].

Written documentation for the HT9100 FMS and MCDU is available [https://github.com/Octal450/FlightGear-Aircraft-Documentation/tree/master/HT9100 here].

=== Shortcut Keys ===
{| class="keytable"
! Key !! Function
|-
| {{key press|1}}
| Show Captain View
|-
| {{key press|2}}
| Show First Officer View
|-
| {{key press|3}}
| Show Overhead View
|-
| {{key press|4}}
| Show Forward Pedestal View
|-
| {{key press|5}}
| Show Aft Pedestal View
|-
| {{key press|6}}
| Show Glareshield View
|-
| {{key press|7}}
| Show MCDU View
|-
| {{key press|F1}}
| Disengage/Decrease Reverse Thrust
|-
| {{key press|F2}}
| Engage/Increase Reverse Thrust
|-
| {{key press|C}}
| Reset Current View
|-
| {{key press|E}}
| Set Throttles to Idle
|-
| {{key press|F}}
| Set Throttles to Thrust Limit
|-
| {{key press|DEL}}
| Toggle Thrust Reversers
|-
| {{key press|CTRL|B}}
| Cycle Spoilers
|-
| {{key press|Shift|B}}
| Toggle Parking Brake
|-
| {{key press|Shift|C}}
| Open Checklists
|-
| {{key press|CTRL|D}}
| Autothrust Disconnect Button
|-
| {{key press|Shift|D}}
| Autoflight Disconnect Button
|-
| {{key press|Shift|F}}
| Set Throttles to Full
|-
| {{key press|CTRL|G}}
| Takeoff/Go Around Button
|-
| {{key press|Shift|K}}
| Toggle MD-87 Firetank Salvo Drop
|-
| {{key press|Shift|P}}
| Open Performance Applet
|}

== Development Videos ==
[[User:Octal450|Octal450]] publishes periodic videos showcasing the latest developments in a [https://www.youtube.com/playlist?list=PL8TVI6JZUbxlSboD5L-jQ-MXkhPBBVnJE YouTube playlist].

{{MDouglas}}

[[Category:Airliners]]
[[Category:Octal450 hangar]]
[[Category:Red Griffin ATC compatible aircraft]]

Boeing 717

2026-07-16T04:42:58Z

Octal450: /* Development Status */

{{:{{PAGENAME}}/info}}

The '''Boeing 717''' is a twinjet narrowbody commercial airliner originally created by the McDonnell Douglas Corporation as the MD-95, to replace aging [[DC-9]]s. It is essentially a DC-9 with new avionics, systems, and engines, adopting several technologies from the [[MD-90]]. The project was completed by Boeing when Boeing bought McDonnell Douglas and rebranded as the Boeing 717. Boeing implemented several changes from the originally adopted MD-95 project, however, the airplane was completed by the former MD-95 project team.

This is an accurate and complex recreation of the Boeing 717.

== Overview ==
Includes the Boeing 717-200 with selectable Rolls-Royce BR715A1-30 or BR715C1-30 engines.

See the right InfoBox for the repository or download. Remember to rename the aircraft's folder to "717". DOWNLOAD NOT YET AVAILABLE.

== Development Status ==
Status denotes simulated functionality. Items marked as done may still be improved upon.

* Aerodynamics: {{done}}
* Air Conditioning: {{done}}
* APU: {{done}}
* Autoflight: {{progressbar|90}}
* Caution and Warning: {{progressbar|30}}
* EAD Display: {{progressbar|90}}
* Electrical: {{done}}
* Exterior Model: {{done}}
* Flight Controls: {{done}}
* FMS and MCDU: {{progressbar|50}}
* Fuel: {{done}}
* Hydraulics: {{done}}
* ISFD Display: {{done}}
* IRS: {{done}}
* Landing Gear and Brakes: {{done}}
* Mach Trim and Yaw Damper: {{done}}
* ND Displays: {{progressbar|10}}
* PFD Displays: {{progressbar|90}}
* Pneumatics: {{progressbar|90}}
* Pressurization: {{not done}}
* RR BR715 Engines and FADEC: {{done}}
* SD Display: {{progressbar|90}}
* Virtual Cockpit: {{progressbar|50}}
* Weight/Balance: {{done}}

== Development Team ==
* Flight Dynamics, Systems, Instruments: Josh Davidson (Octal450)
* 3D/Textures: Gary Neely (Buckaroo), Josh Davidson (Octal450)

== Documentation ==
=== Written Documentation ===
Written documentation for this aircraft is available [https://github.com/Octal450/FlightGear-Aircraft-Documentation/tree/master/717 here].

=== Shortcut Keys ===
{| class="keytable"
! Key !! Function
|-
| {{key press|1}}
| Show Captain View
|-
| {{key press|2}}
| Show First Officer View
|-
| {{key press|3}}
| Show Overhead View
|-
| {{key press|4}}
| Show Forward Pedestal View
|-
| {{key press|5}}
| Show Aft Pedestal View
|-
| {{key press|6}}
| Show Glareshield View
|-
| {{key press|7}}
| Show MCDU View
|-
| {{key press|F1}}
| Disengage/Decrease Reverse Thrust
|-
| {{key press|F2}}
| Engage/Increase Reverse Thrust
|-
| {{key press|DEL}}
| Toggle Thrust Reversers
|-
| {{key press|C}}
| Reset Current View
|-
| {{key press|E}}
| Set Throttles to Idle
|-
| {{key press|F}}
| Set Throttles to Thrust Limit
|-
| {{key press|CTRL|B}}
| Cycle Spoilers
|-
| {{key press|Shift|B}}
| Toggle Parking Brake
|-
| {{key press|Shift|C}}
| Open Checklists
|-
| {{key press|CTRL|D}}
| Autothrust Disconnect Button
|-
| {{key press|Shift|D}}
| Autoflight Disconnect Button
|-
| {{key press|Shift|F}}
| Set Throttles to Full
|-
| {{key press|CTRL|G}}
| Go Around Button
|-
| {{key press|Shift|P}}
| Open CG Applet
|}

{{Boeing}}
{{MDouglas}}

[[Category:Airliners]]
[[Category:Octal450 hangar]]
[[Category:Red Griffin ATC compatible aircraft]]

McDonnell Douglas MD-90

2026-07-16T04:42:53Z

Octal450: /* Development Status */

{{:{{PAGENAME}}/info}}

The '''McDonnell Douglas MD-90''' is a twinjet narrowbody commercial airliners created by the McDonnell Douglas Corporation as the successor to the [[MD-80]].

This is an accurate and complex recreation of the MD-90-30, the only series produced. Other variants such as the MD-90-55 were cancelled and never built.

== Overview ==
Currently, this project is simulating the Enhanced Flight Deck (EFD) version of the MD-90-30 with V2528-D5 engines. This is the only simulation project attempting to do so with any degree of accuracy. This project was announced celebrating Octal450's 10-year development anniversary.

See the right InfoBox for the repository or download. Remember to rename the aircraft's folder to "MD-90". DOWNLOAD NOT YET AVAILABLE.

== Development Status ==
Status denotes simulated functionality. Items marked as done may still be improved upon.

* Aerodynamics: {{done}}
* AFMS and MCDU: {{progressbar|50}}
* Air Conditioning: {{done}}
* APU: {{done}}
* Autoflight: {{progressbar|90}}
* Caution and Warning: {{progressbar|30}}
* EAD Display: {{progressbar|90}}
* Electrical: {{done}}
* Exterior Model: {{done}}
* Flight Controls: {{done}}
* Fuel: {{done}}
* Hydraulics: {{done}}
* IAE V2500 Engines and FADEC: {{done}}
* IRS: {{done}}
* Landing Gear and Brakes: {{done}}
* Mach Trim and Yaw Damper: {{done}}
* ND Displays: {{progressbar|10}}
* PFD Displays: {{progressbar|90}}
* Pneumatics: {{progressbar|90}}
* Pressurization: {{not done}}
* SD Display: {{progressbar|90}}
* Virtual Cockpit: {{progressbar|80}}
* Weight/Balance: {{done}}

== Development Team ==
* Flight Dynamics, Systems, Instruments: Josh Davidson (Octal450)
* 3D/Textures: Semir Gebran (CaptB), Gary Neely (Buckaroo)

== Documentation ==
=== Written Documentation ===
Written documentation for this aircraft is available [https://github.com/Octal450/FlightGear-Aircraft-Documentation/tree/master/MD-90 here].

=== Shortcut Keys ===
{| class="keytable"
! Key !! Function
|-
| {{key press|1}}
| Show Captain View
|-
| {{key press|2}}
| Show First Officer View
|-
| {{key press|3}}
| Show Overhead View
|-
| {{key press|4}}
| Show Forward Pedestal View
|-
| {{key press|5}}
| Show Aft Pedestal View
|-
| {{key press|6}}
| Show Glareshield View
|-
| {{key press|7}}
| Show MCDU View
|-
| {{key press|F1}}
| Disengage/Decrease Reverse Thrust
|-
| {{key press|F2}}
| Engage/Increase Reverse Thrust
|-
| {{key press|C}}
| Reset Current View
|-
| {{key press|E}}
| Set Throttles to Idle
|-
| {{key press|F}}
| Set Throttles to Thrust Limit
|-
| {{key press|DEL}}
| Toggle Thrust Reversers
|-
| {{key press|CTRL|B}}
| Cycle Spoilers
|-
| {{key press|Shift|B}}
| Toggle Parking Brake
|-
| {{key press|Shift|C}}
| Open Checklists
|-
| {{key press|CTRL|D}}
| Autothrust Disconnect Button
|-
| {{key press|Shift|D}}
| Autoflight Disconnect Button
|-
| {{key press|Shift|F}}
| Set Throttles to Full
|-
| {{key press|CTRL|G}}
| Takeoff/Go Around Button
|-
| {{key press|Shift|P}}
| Open CG Applet
|}

{{MDouglas}}

[[Category:Airliners]]
[[Category:Octal450 hangar]]
[[Category:Red Griffin ATC compatible aircraft]]

McDonnell Douglas MD-11

2026-07-13T23:42:21Z

Octal450: /* Development Status */

{{:{{PAGENAME}}/info}}

The '''McDonnell Douglas MD-11''' is a trijet widebody commercial airliner created by the McDonnell Douglas Corporation as the successor to the [[DC-10]]. It is the only modern trijet airliner, with a full glass cockpit, automatic systems, digital flight control system, and a full flight management system.

This is an accurate and complex recreation of the MD-11. Stable versions of the aircraft are uploaded to [[FGAddon]].

== Overview ==
Includes:
* MD-11 (GE CF6-80C2D1F and PW4462)
* MD-11F (GE CF6-80C2D1F and PW4462)
* Bonus KMD-11 (PW4462, Fictional)
** OPRF compatible

See the right InfoBox for the repository or download. Remember to rename the aircraft's folder to "MD-11".

== Development Status ==
Status denotes simulated functionality. Items marked as done may still be improved upon.

* Aerodynamics: {{done}}
* Air Conditioning: {{done}}
* APU: {{done}}
* Autoflight: {{progressbar|90}}
* Caution and Warning: {{progressbar|30}}
* EAD Display: {{progressbar|90}}
* Electrical: {{done}}
* Exterior Model: {{done}}
* Flight Controls: {{done}}
* FMS and MCDU: {{progressbar|50}}
* Fuel: {{done}}
* GE CF6 Engines and FADEC: {{done}}
* Hydraulics: {{done}}
* ISFD Display: {{done}}
* IRS: {{done}}
* Landing Gear and Brakes: {{done}}
* LSAS, RCWS, Yaw Damper: {{done}}
* ND Displays: {{progressbar|10}}
* PFD Displays: {{progressbar|90}}
* Pneumatics: {{done}}
* Pressurization: {{not done}}
* PW4000 Engines and FADEC: {{done}}
* SD Display: {{progressbar|90}}
* Virtual Cockpit: {{progressbar|90}}
* Weight/Balance: {{done}}

== Development Team ==
* Flight Dynamics, Systems, Instruments: Josh Davidson (Octal450)
* 3D/Textures: Semir Gebran (CaptB), John Williams (tikibar), and Jormapaappa1235

== Documentation ==

=== Written Documentation ===
Written documentation for this aircraft is available [https://github.com/Octal450/FlightGear-Aircraft-Documentation/tree/master/MD-11 here].

=== Shortcut Keys ===
{| class="keytable"
! Key !! Function
|-
| {{key press|1}}
| Show Captain View
|-
| {{key press|2}}
| Show First Officer View
|-
| {{key press|3}}
| Show Overhead View
|-
| {{key press|4}}
| Show Forward Pedestal View
|-
| {{key press|5}}
| Show Aft Pedestal View
|-
| {{key press|6}}
| Show Glareshield View
|-
| {{key press|7}}
| Show MCDU View
|-
| {{key press|F1}}
| Disengage/Decrease Reverse Thrust
|-
| {{key press|F2}}
| Engage/Increase Reverse Thrust
|-
| {{key press|DEL}}
| Toggle Thrust Reversers
|-
| {{key press|C}}
| Reset Current View
|-
| {{key press|E}}
| Set Throttles to Idle
|-
| {{key press|F}}
| Set Throttles to Thrust Limit
|-
| {{key press|CTRL|B}}
| Cycle Spoilers
|-
| {{key press|Shift|B}}
| Toggle Parking Brake
|-
| {{key press|Shift|C}}
| Open Checklists
|-
| {{key press|CTRL|D}}
| Autothrust Disconnect Button
|-
| {{key press|Shift|D}}
| Autoflight Disconnect Button
|-
| {{key press|Shift|F}}
| Set Throttles to Full
|-
| {{key press|CTRL|G}}
| Go Around Button
|-
| {{key press|Shift|P}}
| Open CG Applet
|}

== Development Videos ==
[[User:Octal450|Octal450]] publishes periodic videos showcasing the latest developments in a [https://www.youtube.com/playlist?list=PL8TVI6JZUbxkrFiKIv8JQy9rl1_W_rI5v YouTube playlist].

== Tutorial Videos ==
{{#ev:youtube|K5gTjiUmslY|700px||Tutorial video in the '''Polish''' language by SP-ROM showing a flight in the MD-11 and some explanations. The demonstration may help people who don't speak Polish. (MD-11 state as at September 2025)}}

{{MDouglas}}

[[Category:Airliners]]
[[Category:Octal450 hangar]]
[[Category:Red Griffin ATC compatible aircraft]]

Boeing 727

2026-07-13T23:42:00Z

Octal450:

{{:{{PAGENAME}}/info}}

The '''Boeing 727''' is a trijet narrowbody commercial airliner created by The Boeing Company.

== Overview ==
Includes:
* 727-200 (JT8D-9)
* 727-200 Advanced (JT8D-15A)
* 727-200F Advanced (JT8D-15A)
* 727-200 Super 27 (JT8D-217C and JT8D-17A)
* 727-200F Super 27 (JT8D-217C and JT8D-17A)

Planned Models:
* 727-100 series

See the right InfoBox for the repository or download. Remember to rename the aircraft's folder to "727". DOWNLOAD NOT YET AVAILABLE!

== Development Status ==
Status denotes simulated functionality. Items marked as done may still be improved upon.

* Aerodynamics: {{done}}
* Air Conditioning: {{not done}}
* Analog Instruments: {{progressbar|70}}
* APU: {{done}}
* Autothrottle: {{done}}
* Caution and Warning: {{progressbar|10}}
* Collins Flight Director: {{done}}
* Electrical: {{done}}
* Exterior Model: {{progressbar|80}}
* Flight Controls: {{done}}
* Fuel: {{done}}
* Hydraulics: {{done}}
* Landing Gear and Brakes: {{done}}
* Pneumatics: {{not done}}
* Pratt & Whitney JT8D Engines: {{done}}
* Pressurization: {{not done}}
* SP-50 Autopilot: {{done}}
* SP-150 Autopilot: {{done}}
* Virtual Cockpit: {{progressbar|30}}
* Weight/Balance: {{done}}
* Yaw Damper: {{done}}

== Development Team ==
* Flight Dynamics, Systems, Instruments: Josh Davidson (Octal450)
* 3D/Textures: Heiko Schulz (HHS81)

== Documentation ==

=== Shortcut Keys ===
{| class="keytable"
! Key !! Function
|-
| {{key press|1}}
| Show Captain View
|-
| {{key press|2}}
| Show First Officer View
|-
| {{key press|3}}
| Show Overhead View
|-
| {{key press|4}}
| Show Forward Pedestal View
|-
| {{key press|5}}
| Show Aft Pedestal View
|-
| {{key press|6}}
| Show Glareshield View
|-
| {{key press|F1}}
| Disengage/Decrease Reverse Thrust
|-
| {{key press|F2}}
| Engage/Increase Reverse Thrust
|-
| {{key press|DEL}}
| Toggle Thrust Reversers
|-
| {{key press|C}}
| Reset Current View
|-
| {{key press|E}}
| Set Throttles to Idle
|-
| {{key press|F}}
| Set Thrust to EPR Bugs
|-
| {{key press|CTRL|B}}
| Cycle Spoilers
|-
| {{key press|Shift|B}}
| Toggle Parking Brake
|-
| {{key press|Shift|C}}
| Open Checklists
|-
| {{key press|Shift|D}}
| Autoflight Disconnect Button
|-
| {{key press|Shift|P}}
| Open Performance Applet
|}

{{Boeing}}

[[Category:Airliners]]
[[Category:Octal450 hangar]]

Boeing 717

2026-07-13T23:41:47Z

Octal450:

{{:{{PAGENAME}}/info}}

The '''Boeing 717''' is a twinjet narrowbody commercial airliner originally created by the McDonnell Douglas Corporation as the MD-95, to replace aging [[DC-9]]s. It is essentially a DC-9 with new avionics, systems, and engines, adopting several technologies from the [[MD-90]]. The project was completed by Boeing when Boeing bought McDonnell Douglas and rebranded as the Boeing 717. Boeing implemented several changes from the originally adopted MD-95 project, however, the airplane was completed by the former MD-95 project team.

This is an accurate and complex recreation of the Boeing 717.

== Overview ==
Includes the Boeing 717-200 with selectable Rolls-Royce BR715A1-30 or BR715C1-30 engines.

See the right InfoBox for the repository or download. Remember to rename the aircraft's folder to "717". DOWNLOAD NOT YET AVAILABLE.

== Development Status ==
Status denotes simulated functionality. Items marked as done may still be improved upon.

* Aerodynamics: {{done}}
* Air Conditioning: {{not done}}
* APU: {{done}}
* Autoflight: {{progressbar|90}}
* Caution and Warning: {{progressbar|30}}
* EAD Display: {{progressbar|90}}
* Electrical: {{done}}
* Exterior Model: {{done}}
* Flight Controls: {{done}}
* FMS and MCDU: {{progressbar|50}}
* Fuel: {{done}}
* Hydraulics: {{done}}
* ISFD Display: {{done}}
* IRS: {{done}}
* Landing Gear and Brakes: {{done}}
* Mach Trim and Yaw Damper: {{done}}
* ND Displays: {{progressbar|10}}
* PFD Displays: {{progressbar|90}}
* Pneumatics: {{progressbar|90}}
* Pressurization: {{not done}}
* RR BR715 Engines and FADEC: {{done}}
* SD Display: {{progressbar|90}}
* Virtual Cockpit: {{progressbar|50}}
* Weight/Balance: {{done}}

== Development Team ==
* Flight Dynamics, Systems, Instruments: Josh Davidson (Octal450)
* 3D/Textures: Gary Neely (Buckaroo), Josh Davidson (Octal450)

== Documentation ==
=== Written Documentation ===
Written documentation for this aircraft is available [https://github.com/Octal450/FlightGear-Aircraft-Documentation/tree/master/717 here].

=== Shortcut Keys ===
{| class="keytable"
! Key !! Function
|-
| {{key press|1}}
| Show Captain View
|-
| {{key press|2}}
| Show First Officer View
|-
| {{key press|3}}
| Show Overhead View
|-
| {{key press|4}}
| Show Forward Pedestal View
|-
| {{key press|5}}
| Show Aft Pedestal View
|-
| {{key press|6}}
| Show Glareshield View
|-
| {{key press|7}}
| Show MCDU View
|-
| {{key press|F1}}
| Disengage/Decrease Reverse Thrust
|-
| {{key press|F2}}
| Engage/Increase Reverse Thrust
|-
| {{key press|DEL}}
| Toggle Thrust Reversers
|-
| {{key press|C}}
| Reset Current View
|-
| {{key press|E}}
| Set Throttles to Idle
|-
| {{key press|F}}
| Set Throttles to Thrust Limit
|-
| {{key press|CTRL|B}}
| Cycle Spoilers
|-
| {{key press|Shift|B}}
| Toggle Parking Brake
|-
| {{key press|Shift|C}}
| Open Checklists
|-
| {{key press|CTRL|D}}
| Autothrust Disconnect Button
|-
| {{key press|Shift|D}}
| Autoflight Disconnect Button
|-
| {{key press|Shift|F}}
| Set Throttles to Full
|-
| {{key press|CTRL|G}}
| Go Around Button
|-
| {{key press|Shift|P}}
| Open CG Applet
|}

{{Boeing}}
{{MDouglas}}

[[Category:Airliners]]
[[Category:Octal450 hangar]]
[[Category:Red Griffin ATC compatible aircraft]]

McDonnell Douglas MD-90

2026-07-13T23:41:42Z

Octal450: /* Development Status */

{{:{{PAGENAME}}/info}}

The '''McDonnell Douglas MD-90''' is a twinjet narrowbody commercial airliners created by the McDonnell Douglas Corporation as the successor to the [[MD-80]].

This is an accurate and complex recreation of the MD-90-30, the only series produced. Other variants such as the MD-90-55 were cancelled and never built.

== Overview ==
Currently, this project is simulating the Enhanced Flight Deck (EFD) version of the MD-90-30 with V2528-D5 engines. This is the only simulation project attempting to do so with any degree of accuracy. This project was announced celebrating Octal450's 10-year development anniversary.

See the right InfoBox for the repository or download. Remember to rename the aircraft's folder to "MD-90". DOWNLOAD NOT YET AVAILABLE.

== Development Status ==
Status denotes simulated functionality. Items marked as done may still be improved upon.

* Aerodynamics: {{done}}
* AFMS and MCDU: {{progressbar|50}}
* Air Conditioning: {{not done}}
* APU: {{done}}
* Autoflight: {{progressbar|90}}
* Caution and Warning: {{progressbar|30}}
* EAD Display: {{progressbar|90}}
* Electrical: {{done}}
* Exterior Model: {{done}}
* Flight Controls: {{done}}
* Fuel: {{done}}
* Hydraulics: {{done}}
* IAE V2500 Engines and FADEC: {{done}}
* IRS: {{done}}
* Landing Gear and Brakes: {{done}}
* Mach Trim and Yaw Damper: {{done}}
* ND Displays: {{progressbar|10}}
* PFD Displays: {{progressbar|90}}
* Pneumatics: {{progressbar|90}}
* Pressurization: {{not done}}
* SD Display: {{progressbar|90}}
* Virtual Cockpit: {{progressbar|80}}
* Weight/Balance: {{done}}

== Development Team ==
* Flight Dynamics, Systems, Instruments: Josh Davidson (Octal450)
* 3D/Textures: Semir Gebran (CaptB), Gary Neely (Buckaroo)

== Documentation ==
=== Written Documentation ===
Written documentation for this aircraft is available [https://github.com/Octal450/FlightGear-Aircraft-Documentation/tree/master/MD-90 here].

=== Shortcut Keys ===
{| class="keytable"
! Key !! Function
|-
| {{key press|1}}
| Show Captain View
|-
| {{key press|2}}
| Show First Officer View
|-
| {{key press|3}}
| Show Overhead View
|-
| {{key press|4}}
| Show Forward Pedestal View
|-
| {{key press|5}}
| Show Aft Pedestal View
|-
| {{key press|6}}
| Show Glareshield View
|-
| {{key press|7}}
| Show MCDU View
|-
| {{key press|F1}}
| Disengage/Decrease Reverse Thrust
|-
| {{key press|F2}}
| Engage/Increase Reverse Thrust
|-
| {{key press|C}}
| Reset Current View
|-
| {{key press|E}}
| Set Throttles to Idle
|-
| {{key press|F}}
| Set Throttles to Thrust Limit
|-
| {{key press|DEL}}
| Toggle Thrust Reversers
|-
| {{key press|CTRL|B}}
| Cycle Spoilers
|-
| {{key press|Shift|B}}
| Toggle Parking Brake
|-
| {{key press|Shift|C}}
| Open Checklists
|-
| {{key press|CTRL|D}}
| Autothrust Disconnect Button
|-
| {{key press|Shift|D}}
| Autoflight Disconnect Button
|-
| {{key press|Shift|F}}
| Set Throttles to Full
|-
| {{key press|CTRL|G}}
| Takeoff/Go Around Button
|-
| {{key press|Shift|P}}
| Open CG Applet
|}

{{MDouglas}}

[[Category:Airliners]]
[[Category:Octal450 hangar]]
[[Category:Red Griffin ATC compatible aircraft]]

McDonnell Douglas MD-80

2026-07-13T23:41:34Z

Octal450:

{{:{{PAGENAME}}/info}}

The '''McDonnell Douglas MD-80''' is a series of twinjet narrowbody commercial airliners created by the McDonnell Douglas Corporation as the successor to the [[DC-9]].

This is an accurate and complex recreation of the MD-80 series. Stable versions of the aircraft are uploaded to [[FGAddon]].

== Overview ==
Includes:
* MD-81 (JT8D-209)
* MD-82 (JT8D-217A)
* MD-83 (JT8D-219)
* MD-87 (JT8D-217C, Optional Firetank System)

See the right InfoBox for the repository or download. Remember to rename the aircraft's folder to "MD-80".

== Development Status ==
Status denotes simulated functionality. Items marked as done may still be improved upon.

* Aerodynamics: {{done}}
* AHRS: {{done}}
* Air Conditioning: {{not done}}
* Analog Instruments: {{progressbar|90}}
* APU: {{done}}
* Autoflight: {{progressbar|90}}
* Caution and Warning: {{progressbar|30}}
* EDP and SDP Instruments: {{not done}}
* Electrical: {{done}}
* Exterior Model: {{done}}
* Flight Controls: {{done}}
* Fuel: {{done}}
* Honeywell AFMS and MCDU: {{not done}}
* Honeywell HT9100 FMS and MCDU: {{progressbar|40}}
* Hydraulics: {{done}}
* IRS: {{done}}
* Landing Gear and Brakes: {{done}}
* Mach Trim and Yaw Damper: {{done}}
* ND Displays: {{progressbar|10}}
* PFD Displays: {{progressbar|90}}
* Pneumatics: {{progressbar|90}}
* Pressurization: {{not done}}
* PW JT8D Engines and TRI/TRP: {{done}}
* Virtual Cockpit: {{progressbar|80}}
* Weight/Balance: {{done}}

== Development Team ==
* Flight Dynamics, Systems, Instruments: Josh Davidson (Octal450)
* 3D/Textures: Gary Neely (Buckaroo)

== Documentation ==
=== Written Documentation ===
Written documentation for this aircraft is available [https://github.com/Octal450/FlightGear-Aircraft-Documentation/tree/master/MD-80 here].

Written documentation for the HT9100 FMS and MCDU is available [https://github.com/Octal450/FlightGear-Aircraft-Documentation/tree/master/HT9100 here].

=== Shortcut Keys ===
{| class="keytable"
! Key !! Function
|-
| {{key press|1}}
| Show Captain View
|-
| {{key press|2}}
| Show First Officer View
|-
| {{key press|3}}
| Show Overhead View
|-
| {{key press|4}}
| Show Forward Pedestal View
|-
| {{key press|5}}
| Show Aft Pedestal View
|-
| {{key press|6}}
| Show Glareshield View
|-
| {{key press|7}}
| Show MCDU View
|-
| {{key press|F1}}
| Disengage/Decrease Reverse Thrust
|-
| {{key press|F2}}
| Engage/Increase Reverse Thrust
|-
| {{key press|C}}
| Reset Current View
|-
| {{key press|E}}
| Set Throttles to Idle
|-
| {{key press|F}}
| Set Throttles to Thrust Limit
|-
| {{key press|DEL}}
| Toggle Thrust Reversers
|-
| {{key press|CTRL|B}}
| Cycle Spoilers
|-
| {{key press|Shift|B}}
| Toggle Parking Brake
|-
| {{key press|Shift|C}}
| Open Checklists
|-
| {{key press|CTRL|D}}
| Autothrust Disconnect Button
|-
| {{key press|Shift|D}}
| Autoflight Disconnect Button
|-
| {{key press|Shift|F}}
| Set Throttles to Full
|-
| {{key press|CTRL|G}}
| Takeoff/Go Around Button
|-
| {{key press|Shift|K}}
| Toggle MD-87 Firetank Salvo Drop
|-
| {{key press|Shift|P}}
| Open Performance Applet
|}

== Development Videos ==
[[User:Octal450|Octal450]] publishes periodic videos showcasing the latest developments in a [https://www.youtube.com/playlist?list=PL8TVI6JZUbxlSboD5L-jQ-MXkhPBBVnJE YouTube playlist].

{{MDouglas}}

[[Category:Airliners]]
[[Category:Octal450 hangar]]
[[Category:Red Griffin ATC compatible aircraft]]

McDonnell Douglas MD-11

2026-07-13T23:41:10Z

Octal450: /* Development Status */

{{:{{PAGENAME}}/info}}

The '''McDonnell Douglas MD-11''' is a trijet widebody commercial airliner created by the McDonnell Douglas Corporation as the successor to the [[DC-10]]. It is the only modern trijet airliner, with a full glass cockpit, automatic systems, digital flight control system, and a full flight management system.

This is an accurate and complex recreation of the MD-11. Stable versions of the aircraft are uploaded to [[FGAddon]].

== Overview ==
Includes:
* MD-11 (GE CF6-80C2D1F and PW4462)
* MD-11F (GE CF6-80C2D1F and PW4462)
* Bonus KMD-11 (PW4462, Fictional)
** OPRF compatible

See the right InfoBox for the repository or download. Remember to rename the aircraft's folder to "MD-11".

== Development Status ==
Status denotes simulated functionality. Items marked as done may still be improved upon.

* Aerodynamics: {{done}}
* Air Conditioning: {{done}}
* APU: {{done}}
* Autoflight: {{progressbar|90}}
* Caution and Warning: {{progressbar|30}}
* EAD Display: {{progressbar|90}}
* Electrical: {{done}}
* Exterior Model: {{done}}
* Flight Controls: {{done}}
* FMS and MCDU: {{progressbar|50}}
* Fuel: {{done}}
* GE CF6 Engines and FADEC: {{done}}
* Hydraulics: {{done}}
* ISFD Display: {{done}}
* IRS: {{done}}
* Landing Gear and Brakes: {{done}}
* LSAS, RCWS, Yaw Damper: {{done}}
* ND Displays: {{progressbar|10}}
* PFD Displays: {{progressbar|90}}
* Pneumatics: {{progressbar|90}}
* Pressurization: {{not done}}
* PW4000 Engines and FADEC: {{done}}
* SD Display: {{progressbar|90}}
* Virtual Cockpit: {{progressbar|90}}
* Weight/Balance: {{done}}

== Development Team ==
* Flight Dynamics, Systems, Instruments: Josh Davidson (Octal450)
* 3D/Textures: Semir Gebran (CaptB), John Williams (tikibar), and Jormapaappa1235

== Documentation ==

=== Written Documentation ===
Written documentation for this aircraft is available [https://github.com/Octal450/FlightGear-Aircraft-Documentation/tree/master/MD-11 here].

=== Shortcut Keys ===
{| class="keytable"
! Key !! Function
|-
| {{key press|1}}
| Show Captain View
|-
| {{key press|2}}
| Show First Officer View
|-
| {{key press|3}}
| Show Overhead View
|-
| {{key press|4}}
| Show Forward Pedestal View
|-
| {{key press|5}}
| Show Aft Pedestal View
|-
| {{key press|6}}
| Show Glareshield View
|-
| {{key press|7}}
| Show MCDU View
|-
| {{key press|F1}}
| Disengage/Decrease Reverse Thrust
|-
| {{key press|F2}}
| Engage/Increase Reverse Thrust
|-
| {{key press|DEL}}
| Toggle Thrust Reversers
|-
| {{key press|C}}
| Reset Current View
|-
| {{key press|E}}
| Set Throttles to Idle
|-
| {{key press|F}}
| Set Throttles to Thrust Limit
|-
| {{key press|CTRL|B}}
| Cycle Spoilers
|-
| {{key press|Shift|B}}
| Toggle Parking Brake
|-
| {{key press|Shift|C}}
| Open Checklists
|-
| {{key press|CTRL|D}}
| Autothrust Disconnect Button
|-
| {{key press|Shift|D}}
| Autoflight Disconnect Button
|-
| {{key press|Shift|F}}
| Set Throttles to Full
|-
| {{key press|CTRL|G}}
| Go Around Button
|-
| {{key press|Shift|P}}
| Open CG Applet
|}

== Development Videos ==
[[User:Octal450|Octal450]] publishes periodic videos showcasing the latest developments in a [https://www.youtube.com/playlist?list=PL8TVI6JZUbxkrFiKIv8JQy9rl1_W_rI5v YouTube playlist].

== Tutorial Videos ==
{{#ev:youtube|K5gTjiUmslY|700px||Tutorial video in the '''Polish''' language by SP-ROM showing a flight in the MD-11 and some explanations. The demonstration may help people who don't speak Polish. (MD-11 state as at September 2025)}}

{{MDouglas}}

[[Category:Airliners]]
[[Category:Octal450 hangar]]
[[Category:Red Griffin ATC compatible aircraft]]

Ground proximity warning system

2026-06-28T21:12:28Z

Octal450: /* Decoding Outputs */

'''Ground Proximity Warning System''' ('''GPWS''') is a system designed to alert pilots if their [[aircraft]] is in immediate danger of flying into the ground or an obstacle. Another common name for such a system is '''Ground-Collision Warning System''' ('''GCWS''').
More advanced systems, providing additional protection based on GPS position and a terrain database, are known as '''Enhanced Ground Proximity Warning Systems''' ('''EGPWS''').

The EGPWS provided by FlightGear emulates the '''MK VIII''' made by Honeywell Inc.
It provides all inputs and outputs of the original hardware.
Also the configuration categories and their encodings are modeled to match the original equipment.

Since FG2018.1 the simulation was extended with optional support for Airbus-specific callouts, which would normally not be supported by the real-world MK VIII hardware unit (which is not intended to be installed on Airbus aircraft).

= Features =
== Warnings ==
The module provides warnings for different alerting modes:

* '''Mode 1: Excessive Descent Rate'''
: Provides 'Sink rate!' and 'Pull up!' alerts based on descent rate at low radio altitudes (below 2500').

* '''Mode 2: Excessive Terrain Closure Rate'''
: Provides 'Pull up!' and 'Terrain!' callouts around rising terrain.

* '''Mode 3: Altitude Loss After Takeoff'''
: Provides alerts against altitude loss after takeoff (or a go-around). Losing altitude triggers a 'Don't sink!' alert.

* '''Mode 4: Unsafe Terrain Clearance'''
: Provides alerts against insufficient clearance, based upon the aircraft configuration and flight phase (takeoff, cruise, approach), and independent of terrain closure rate (i.e situations that modes 1 & 2 would not alert). Alerts include 'Too low - terrain!', 'Too low - gear!' and 'Too low - flaps!'. Also protects against a gear-up landing or approach without flaps in the landing configuration.

* '''Mode 5: Excessive Deviation Below Glideslope'''
: Provides 'Glideslope!' alerts when deviating below a glideslope while established on a localizer.

* '''Mode 6: Advisory Callouts'''
: Provides callouts based on the specified decision-height and radio altitude. This includes a 'Minimums' alert based upon the decision-height, and callouts while descending through various radio altitudes (1000', 500', 200', 100', 50', 40', 30', 20' and 10'). Also provides a 'Bank angle' alert based upon excessive aircraft roll.

* '''Mode 7: Windshear Protection'''
: Windshear protection is currently ''not'' implemented.

== Other ==

* '''Self-test'''
: Triggers all warnings enabled for the specific plane one by one.

* '''Status display'''
: Shows module configuration and status.

= Add to an Aircraft =
== Instrument List ==
Add the device to your plane by adding it to the sim/instrumentation section (usually in a separate instrumentation.xml file).

Example:
<PropertyList>
<sim>
<instrumentation>

'''<mk-viii>'''
'''<name>mk-viii</name>'''
'''<number>0</number>'''
'''</mk-viii>'''

</instrumentation>
</sim>
</PropertyList>
Usually planes only have a single GPWS installed - so using multiple instances wouldn't be too common.

== <Plane>-set.xml file ==
Configuration parameters are stored in a different section.
Add the following XML template to the instrumentation section of the plane's ...-set.xml file.
Do not mix up this section with the one above (section above was ''within'' the <sim> tag, this section is ''outside'' the <sim> tag).

'''Notes''':
* The values in the <tt><configuration-module></tt> section (below) list the module's default. You can omit specific <tt><category-''n''></tt> lines unless you need to change the default.
* All configuration categories require valid settings. If you do explicitly configure a category to change the default, you must provide a valid value. See sections below for valid options.
* Do ''not'' omit the <serviceable>true</serviceable> part...

=== XML Template ===
<PropertyList>
<nowiki></nowiki>

<instrumentation>
<mk-viii> <nowiki></nowiki>

<serviceable>true</serviceable> <nowiki></nowiki>

<configuration-module>
<category-1> 0 </category-1> <nowiki></nowiki>
<category-3> 2 </category-3> <nowiki></nowiki>
<category-4> 13 </category-4> <nowiki></nowiki>
<category-5> 0 </category-5> <nowiki></nowiki>
<category-6> 1 </category-6> <nowiki></nowiki>
<category-7> 124 </category-7> <nowiki></nowiki>
<category-8> 2 </category-8> <nowiki></nowiki>
<category-9> 3 </category-9> <nowiki></nowiki>
<category-10> 6 </category-10> <nowiki></nowiki>
<category-13> 7 </category-13> <nowiki></nowiki>
<category-14> 0 </category-14> <nowiki></nowiki>
</configuration-module>

<inputs> <nowiki></nowiki>
<arinc429>
<decision-height-ncd> false </decision-height-ncd>
<decision-height> 200 </decision-height>
</arinc429>
</inputs>

<speaker> <nowiki></nowiki>
<max-dist> 2 </max-dist> <nowiki></nowiki>
<reference-dist> 1 </reference-dist> <nowiki></nowiki>
<volume> 0.4 </volume> <nowiki></nowiki>
</speaker>

<voice>
<file-prefix type="string">Sounds/mk-viii/</file-prefix>
<nowiki></nowiki>
</voice>

</mk-viii>
</instrumentation>

</PropertyList>

The example above provides the decision height as a fixed value. Since this value is an input, you can also provide this value at run-time instead - e.g. depending on whether an ILS or visual approach is flown.

=== Unimplemented Categories ===
Some configuration categories are currently ''not'' implemented. The following elements are therefore omitted in the XML template:
<category-2> 1 </category-2> <nowiki></nowiki>
<category-11> 2 </category-11> <nowiki></nowiki>
<category-12> 0 </category-12> <nowiki></nowiki>
<category-15> 0 </category-15> <nowiki></nowiki>
<category-16> 0 </category-16> <nowiki></nowiki>
<category-17> 0 </category-17> <nowiki></nowiki>

== Electric Power ==
The mk-viii module needs (virtual) electric power. The module also simulates the behavior of the original hardware device when applying over or under voltage - i.e. it withstands short periods of too low or high voltage (within certain limits). Supply a nominal value of 28 volts. Usually you'll provide power via Nasal by connecting the module to the electrical bus simulation. If you're plane doesn't provide such a simulation you can also configure a fixed value (i.e. '''28''') to the following property:
/systems/electrical/outputs/''<name>''[''<num>'']
where ''<name>'' and ''<num>'' match the values you specified in the instrument list, e.g. for ''<name>=mk-viii and ''<num>''=0
/systems/electrical/outputs/mk-viii[0]

= Configuration =
== Hints ==
* Trigger the self-test to check if the EGPWS is enabled and to check which callouts are enabled for this airplane. Set the property <tt>/instrumentation/mk-viii/inputs/discretes/self-test</tt> to <tt>true</tt> to trigger the self-test. Enabling this input for 2 seconds triggers short self-test, enabling it for at least 5 seconds triggers a full self-test. The plane must be on ground and stopped, otherwise the self-test is inhibited.
* You can test EGPWS configuration without restarting FlightGear by modifying the configuration values in the Property Browser manually and then forcing the EGPWS to reload the configuration by toggling the plane's electrical power (OFF-ON).

== Configuration Categories ==
=== Aircraft Mode Select ===
<category-1> 0 </category-1> <nowiki></nowiki>
This is the device's main configuration setting. It selects the envelops for allowed speeds and minimum heights for all EGPWS modes. The envelops are configured by selecting an entire set of configuration values. This simplifies the configuration, however, new airplane types may require to modify the mk-viii sources in order to support an appropriate configuration set.

{|border="1" cellspacing="0" align="center"
!category-1
!Aircraft Type Description
!Type
!Gear down at 500ft
when slower than
!Flaps down at
!Max airspeed
flaps/gear down*
!Min Runway Length
|-
|align="right"|'''(default) 0'''
|Fast turboprop, normal flap deployment
|align="center"|T6
|align="center"|178 knots
|align="center"|170 ft / 150 knots
|align="center"|250 / 290 knots
|align="center"|2000m
|-
|align="right"|1
|Fast turboprop, delayed flap deployment
|align="center"|T8
|align="center"|178 knots
|align="center"|150 ft / 148 knots
|align="center"|250 / 290 knots
|align="center"|2000m
|-
|align="right"|2
|Fast turboprop (old GPWS emulation)
|align="center"|T5
|align="center"|178 knots
|align="center"|200 ft / 148 knots
|align="center"|250 / 290 knots
|align="center"|2000m
|-
|align="right"|3
|Slow turboprop, normal flap deployment
|align="center"|T7
|align="center"|148 knots
|align="center"|170 ft / 120 knots
|align="center"|180 / 200 knots
|align="center"|2000m
|-
|align="right"|4
|Slow turboprop, delayed flap deployment
|align="center"|T9
|align="center"|148 knots
|align="center"|150 ft / 118 knots
|align="center"|180 / 200 knots
|align="center"|2000m
|-
|align="right"|254
|Fast, heavy turbofans (jets), requiring 3500m runways
|align="center"|T1
|align="center"|190 knots
|align="center"|245 ft / 159 knots
|align="center"|250 / 290 knots
|align="center"|3500m
|-
|align="right"|255
|Fast turbofans (jets), requiring 2000m runways
|align="center"|T1
|align="center"|190 knots
|align="center"|200 ft / 159 knots
|align="center"|250 / 290 knots
|align="center"|2000m
|}
* When maximum gear down/flaps down airspeeds are exceeded for at least 60 seconds the EGPWS triggers a fault and assumes the gear down / flaps down inputs to be invalid.

=== Position Input Select ===
<category-3> 2 </category-3> <nowiki></nowiki>
Some warning modes require the plane's GPS position, e.g. in order to find the nearest runway in its internal database to provide correct height callouts.
* 1: GPS data is supplied to the inputs externally (e.g. NASAL script). You need to provide input to
:<tt>/instrumentation/mk-viii/inputs/arinc429/gps-altitude</tt>
:<tt>/instrumentation/mk-viii/inputs/arinc429/gps-latitude</tt>
:<tt>/instrumentation/mk-viii/inputs/arinc429/gps-longitude</tt>
:<tt>/instrumentation/mk-viii/inputs/arinc429/gps-vertical-figure-of-merit</tt>
* '''2 (default)''': GPS data uses internal source (enables a hard-wired connection within the simulator)

=== Altitude Callouts ===
<category-4> 13 </category-4> <nowiki></nowiki>
Select a set of callouts for the approach phase.

{|border="1" cellspacing="0" align="center"
!category-4
!Callouts
|-
|align="right"|0
|Minimums, SMART_500, 200, 100, 50, 40, 30, 20, 10. ''"SMART_500" limits the 500ft callout to non-precision approaches (when no glideslope is captured or g/s is at least 2 dots above/below).''
|-
|align="right"|1
|Minimums, SMART_500, 200
|-
|align="right"|2
|Minimums, SMART_500, 100, 50, 40, 30, 20, 10
|-
|align="right"|3
|Minimums, SMART_500
|-
|align="right"|4
|Minimums, 200, 100, 50, 40, 30, 20, 10
|-
|align="right"|5
|Minimums, 200
|-
|align="right"|6
|Minimums, 100, 50, 40, 30, 20, 10
|-
|align="right"|7
|''All call-outs disabled.''
|-
|align="right"|8
|Minimums. ''All altitude callouts disabled.''
|-
|align="right"|9
|Minimums, 500, 200, 100, 50, 40, 30, 20, 10
|-
|align="right"|10
|Minimums, 500, 200
|-
|align="right"|11
|Minimums, 500, 100, 50, 40, 30, 20, 10
|-
|align="right"|12
|Minimums, 500
|-
|align="right"|'''(default) 13'''
|Minimums, 1000, 500, 400, 300, 200, 100, 50, 40, 30, 20, 10 ''(This option should match Boeing and most other airliners, except Airbus.)''
|-
|align="right"|14
|Minimums, 100
|-
|align="right"|15
|Minimums, 200, 100
|-
|align="right"|100
|FIELD_500. ''Provides “500” callout at an altitude 500ft above the actual runway altitude.''
|-
|align="right"|101
|FIELD_500_ABOVE. ''Provides “500 above” callout at an altitude 500ft above the actual runway altitude.''
|-
|colspan="2"|''The options below are not available with the original mk-viii hardware unit. They were added for the FlightGear simulation (with FG 2018.1 and newer) to support typical GPWS callouts of Airbus aircraft.''
|-
|align="right"|'''1000'''
|Above_100, Minimums, 2500, 1000, 500, 400, 300, 200, 100, 50, 40, 30, 20, 10, Retard ''(This option should match most Airbus aircraft.)''
|-
|align="right"|1001
|Minimums, 2500, 1000, 500, 400, 300, 200, 100, 50, 40, 30, 20, 10, Retard
|-
|align="right"|1002
|Minimums, 2500, 1000, 500, 400, 300, 200, 100, 50, 40, 30, 20, 10
|-
|align="right"|1010
|Above_100, Minimums, 1000, 500, 400, 300, 200, 100, 50, 40, 30, 20, 10, Retard
|-
|align="right"|1011
|Minimums, 1000, 500, 400, 300, 200, 100, 50, 40, 30, 20, 10, Retard
|}

The 500ft callout is available in four options:
* "SMART_500" limits the 500ft callout to non-precision approaches (when no glideslope is captured or g/s is at least 2 dots above/below).
* "FIELD_500" configures the 500ft callout to consider the altitude above the actual runway altitude (instead of the current radio altitude).
* "FIELD_500_ABOVE" is like "FIELD_500", but triggers a "500 '''above'''" callout (instead of "500").
* "500" enables the standard callout, i.e. triggers whenever the radio altimeter reports a current altitude of 500ft.

=== Audio Menu Select ===
<category-5> 0 </category-5> <nowiki></nowiki>
Configure retractable or fixed gear aircraft.
* '''0 (default)''': Configured for retractable gear aircraft. „Too low - gear!“ and „Too low - flaps!“ callouts enabled.
* 2: Configured for fixed gear aircraft. „Too low, flaps!“ callout enabled.

=== Terrain Collision Warning ===
<category-6> 1 </category-6> <nowiki></nowiki>
Enable/disable terrain collision warnings.
* '''1 (default)''': Terrain collision warnings enabled.
* 2: Terrain collision warnings disabled.

=== Options Select ===
<category-7> 124 </category-7> <nowiki></nowiki>
Enable/disable bank angle and steep approach warnings and select flap type.
* bit 0: ''not implemented''
* bit 1: flap reversal.
: '''0 = normal logic (default)'''
: 2 = invert logic when detecting extended/retracted flaps
* bit 2: bank angle alert
: 0 = bank angle alert disabled
: '''4 = enabled (default)'''
* bit 3-5: ''not implemented but enabled by default''
* bit 6: steep approach
: 0 = steep approach warning disabled
: '''64 = steep approach warning enabled (default)'''
* bit 7: ''not implemented''

'''Example''': Value 68 (= 64+ 4) enables bank angle, steep approach alert and normal flap logic.

'''Note''': Default is 124. This also enables additional feature bits (which are currently unsupported).

=== Radio Altitude Input Select ===
<category-8> 2 </category-8> <nowiki></nowiki>
Select radio altimeter input source.

* '''2 (default)''': Altitude source is property "/position/altitude-agl-ft". Works for all FDMs - but this is ''not precise enough to drive useful 20ft and 10ft callouts'' (see below).
* 3: Altitude source is "/position/gear-agl-ft". Very precise altitude of gear-above-ground - but only available for planes with YASim FDM (so far).
* 4: Altitude source is "/instrumentation/radar-altimeter/radar-altitude-ft". A radar altimeter instrument must be installed.

'''Hint''': Most simulator altitude properties refer to the plane's center (of gravity) - but not to the altitude of the main gear. A radar altimeter on a real plane is always calibrated to the gear, hence provides precise information (yes, only within a certain degree of the angle of attack...).
Without a precise altitude source the final callouts before touch down, especially 20ft and 10ft, make no sense or may not even work - very annoying, since most aircraft require a final nose up flare at about 20ft. So precise callouts are very welcome.
Using a radar altimeter instrument is recommended since this is most realistic - and it can (and should) be calibrated to the main gear. See ...(TODO)... for a configuration example.

'''Note''': This configuration category is supported beginning with FlightGear 2.2.

=== Navigation Input Select ===
<category-9> 3 </category-9> <nowiki></nowiki>
Enable/disable glideslope warnings.
* 0: localizer input disabled (disables glideslope warnings)
* '''3 (default)''': localizer input enabled (enables glideslope warning)
: '''Note''': By default, the module is hard-wired to the NAV0 receiver for glideslope warnings, i.e. in order to use the NAV1 receiver you need to update the inputs externally through nasal, etc (see [[#Module I/O|Module I/O]]).

=== Attitude Input Select ===
<category-10> 6 </category-10> <nowiki></nowiki>
Select attitude input source.

'''Note''': This configuration category is implemented for the latest FlightGear version only (GIT sources as of ''''2010-07-30'''' or newer).
* 2: Read data from attitude instrument (requires vacuum system to work).
* '''6 (default)''': Read data from hard-wired connection within simulator.

=== Input and Output Configuration ===
<category-13> 7 </category-13> <nowiki></nowiki>
This configuration value configures the behavior of the module's outputs, usually connected to warning lamps in the cockpit, and enables inputs, which should be connected to cockpit switches.

{|border="1" cellspacing="0" align="center"
!
|colspan="2"|'''Output Lamp Configuration'''
|colspan="3"|'''Input Switch Configuration'''
When enabled, appropriate inputs are supplied to the module
(e.g. inputs should be connected to cockpit switches).
|-
!category-13
!Output
Format *
!Lamp
Flashing **
!GPWS Inhibit
Switch Enabled
!Momentary Flap
Override Switch Enabled
!Alternate Steep
Approach Switch Enabled
|-
|align="right"|0
|align="center"|warning
|align="center"|steady
|
|align="center"|x
|align="center"|x
|-
|align="right"|1
|align="center"|alert
|align="center"|steady
|
|align="center"|x
|align="center"|x
|-
|align="right"|2
|align="center"|warning
|align="center"|steady
|align="center"|x
|align="center"|x
|align="center"|x
|-
|align="right"|3
|align="center"|alert
|align="center"|steady
|align="center"|x
|align="center"|x
|align="center"|x
|-
|align="right"|4
|align="center"|warning
|align="center"|flashing
|align="center"|x
|align="center"|x
|align="center"|x
|-
|align="right"|5
|align="center"|alert
|align="center"|flashing
|align="center"|x
|align="center"|x
|align="center"|x
|-
|align="right"|6
|align="center"|warning
|align="center"|steady
|align="center"|x
|align="center"|x
|
|-
|align="right"|'''(default) 7'''
|align="center"|alert
|align="center"|steady
|align="center"|x
|align="center"|x
|
|-
|align="right"|254
|align="center"|warning
|align="center"|steady
|align="center"|x
|
|align="center"|x
|-
|align="right"|255
|align="center"|warning
|align="center"|steady
|align="center"|x
|
|align="center"|x
|}

* '''Output Format''': 'alert': caution conditions trigger the alert output lamp, otherwise caution conditions triggers warning output.

** '''Lamp Flashing''': Selects whether output lamps should flash or be lit steadily when warning/alert/caution is triggered.

=== Audio Output Level ===
<category-14> 0 </category-14> <nowiki></nowiki>
Basic audio configuration.

{|border="1" cellspacing="0"
!category-14
!Audio Relative
Volume
|-
|align="right"|'''(default) 0'''
|align="right"|0 dB
|-
|align="right"|1
|align="right"| -6 dB
|-
|align="right"|2
|align="right"| -12 dB
|-
|align="right"|3
|align="right"| -18 dB
|-
|align="right"|4
|align="right"| -24 dB
|}

== Speaker Configuration ==
The audio speaker can be configured by modifying the properties beneath <tt>/instrumentation/mk-viii/speaker</tt>.
These properties match the xmlsound properties.

For additional information, check out <tt>[[$FG_ROOT]]/Docs/README.xmlsound</tt>.

== Voice Configuration ==
The GPWS uses a fixed default voice. The voice can be changed by providing custom voice samples and providing a different path and filename prefix.

<voice>
<file-prefix type="string">Sounds/mk-viii/</file-prefix>
<nowiki></nowiki>
</voice>

'''Note:'''
* The voice configuration option is supported by FlightGear '''2.3.0''' and newer.

= Advanced =
This section lists some advanced configuration and integration options.

== Example ==
You may want to check the FG implementation of the [[Boeing 777-200]] aircraft for an extensive example of GPWS integration. This plane provides a Nasal GPWS wrapper for the mk-viii module and implements all standard (Boeing) buttons and displays, i.e.:
* Self-test push button
* Glide-slope warning disable button (e.g. to silence warnings during a visual approach)
* Flap and gear override buttons (e.g. to silence flap/gear warnings in emergency situations, like stuck gear etc).
* Terrain/GPWS disable buttons
* GPWS connection to master-warning light.
* GPWS connection to PFD (to display "PULL UP").

== Module I/O ==
* The inputs and outputs match those of the real device and are made available through the FlightGear property tree.
* Input monitoring is implemented. The loss of inputs required for a particular function is annunciated through the GPWS INOP and/or TERR FAIL lamps.
* The "Present Status" function, which enumerates current faults and lists other device details, is implemented.
* Connect outputs to cockpit instruments, e.g. the EGPWS alert and glideslope outputs to the appropriate warning lamps.
* Connect the <tt>/instrumentation/mk-viii/inputs/discretes/self-test</tt> property to the GPWS self-test button in your cockpit. Testing GPWS operation may be part of the preflight check-list.
* To assist the aircraft designer with the installation of the EGPWS, most inputs are connected to standard FlightGear properties by default. When an input feeder (<tt>...-ncd</tt> property) is set to true, the input it is associated with is automatically updated, using a standard FlightGear property. When the <tt>...-ncd</tt> property it is set to false, its associated input must be manually updated every frame, using a Nasal script or some other mechanism.
* The aircraft's decision height needs to be configured when the 'Minimums' warning is enabled. You can provide the decision height as fixed input value to <tt>/instruments/mk-viii/inputs/arinc429/decision-height</tt>:
<arinc429>
<decision-height-ncd> false </decision-height-ncd>
<decision-height> 200 </decision-height>
</arinc429>

=== Decoding Outputs ===
For some reason, the developers of this module decided to output status via a simulated ARINC429 bus, instead of normal booleans, which makes things infinitely more complex than they need to be for developers looking to interface with this module. Thus, the below section will explain how to interpret the outputs.

The "bit" position for the number (for example, 4096 being the value for bit 12, the "Pull Up" warning) can be checked in the word input from the property tree to see if the warning is active.

;Example Decoder for "Pull Up"
<syntaxhighlight lang="nasal">
var MkViiiTranslator = {
discrete1: 0,
pullUp: 0,
decode: func() {
me.discrete1 = getprop("/instrumentation/mk-viii/outputs/arinc429/egpws-alert-discrete-1");
me.pullUp = me.hasBit(me.discrete1, 4096);
},
hasBit: func(word, bit) {
return math.mod(int(word / bit), 2);
},
};
</syntaxhighlight>

;Properties:
* <code>/instrumentation/mk-viii/outputs/arinc429/egpws-alert-discrete-1</code>
* <code>/instrumentation/mk-viii/outputs/arinc429/egpws-alert-discrete-2</code>
* <code>/instrumentation/mk-viii/outputs/arinc429/egpwc-alert-discrete-3</code>
* <code>/instrumentation/mk-viii/outputs/arinc429/egpwc-logic-discretes</code>
* <code>/instrumentation/mk-viii/outputs/arinc429/mode6-callouts-discrete-1</code>
* <code>/instrumentation/mk-viii/outputs/arinc429/mode6-callouts-discrete-2</code>
 

;Warning Bit Matrix:
;egpws-alert-discrete-1
{|class="wikitable"
! Alert !! Bit
|-
| Sink Rate || 2048
|-
| Pull Up || 4096
|-
| Terrain || 8192
|-
| Don't Sink || 16384
|-
| Too Low Gear || 32768
|-
| Too Low Flaps || 65536
|-
| Too Low Terrain || 131072
|-
| Glideslope || 262144
|-
| Minimums || 524288
|}

;egpws-alert-discrete-2
{|class="wikitable"
! Alert !! Bit
|-
| Glideslope Cancel || 2048
|-
| GPWS Alert Lamp || 4096
|-
| GPWS Warning Lamp || 8192
|-
| GPWS Inop || 16384
|-
| Audio Active || 65536
|-
| TAD Inop || 16777216
|-
| Fault Present || 33554432
|-
| Terrain NA || 134217728
|}

;egpwc-alert-discrete-3
{|class="wikitable"
! Alert !! Bit
|-
| Modes 1-4 Inop || 2048
|-
| Mode 5 Inop || 4096
|-
| Mode 6 Inop || 8192
|-
| Bank Angle Inop || 16384
|-
| TAD Inop || 65536
|-
| Always set || 131072
|-
| Always set || 262144
|}

;egpwc-logic-discretes
{|class="wikitable"
! Alert !! Bit
|-
| TCF Too Low Terrain || 8192
|-
| Takeoff Mode || 262144
|-
| Mode 1 Sink Rate || 524288
|-
| Mode 1 Pull Up || 1048576
|-
| Mode 2 Terrain || 2097152
|-
| Mode 2 Warning || 4194304
|-
| Mode 3 Don't Sink || 8388608
|-
| Mode 4 Too Low Gear/Flaps/Terrain || 16777216
|-
| Mode 5 Glideslope || 33554432
|}

;mode6-callouts-discrete-1
{|class="wikitable"
! Alert !! Bit
|-
| Minimums || 2048
|-
| 10 || 65536
|-
| 20 || 131072
|-
| 30 || 262144
|-
| 40 || 524288
|-
| 50 || 1048576
|-
| 100 || 8388608
|-
| 200 || 16777216
|-
| 300 || 33554432
|}

;mode6-callouts-discrete-2
{|class="wikitable"
! Alert !! Bit
|-
| 400 || 2048
|-
| 500 || 4096
|-
| 1000 || 8192
|-
| 2500 || 16384
|-
| Bank Angle || 262144
|-
| 100/500 Above|| 524288
|}

== Module Status ==
The original MK VIII supports an RS232 interface to read the module status. Since FlightGear does not support RS232 interfaces, all data is printed to the standard output. Trigger <tt>/instrumentation/mk-viii/inputs/discretes/rs-232/present-status</tt> to print the current module configuration and status:

EGPWC CONFIGURATION
PART NUMBER: 965-1220-000
MOD STATUS: N/A
SERIAL NUMBER: N/A

APPLICATION S/W VERSION: 2.0.0
TERRAIN DATABASE VERSION: 2.0.0
ENVELOPE MOD DATABASE VERSION: N/A
BOOT CODE VERSION: 2.0.0

CURRENT FAULTS
NO FAULTS

CONFIGURATION:
AIRCRAFT TYPE = 0
AIR DATA TYPE = 1
POSITION INPUT TYPE = 2
CALLOUTS OPTION TYPE = 13
AUDIO MENU TYPE = 0
TERRAIN DISPLAY TYPE = 1
OPTIONS 1 TYPE = 124
RADIO ALTITUDE TYPE = 2
NAVIGATION INPUT TYPE = 3
ATTITUDE TYPE = 6
MAGNETIC HEADING TYPE = 2
WINDSHEAR INPUT TYPE = 0
IO DISCRETE TYPE = 7
VOLUME SELECT = 0

= External Links =
* Documentation by the original module developer [http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg01902.html 1] [http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg01902/mk-viii-manual.tgz 2]
* Original manufacturer documentation
** [http://www.egpws.com/engineering_support/documents/install/060-4314-150.pdf Honeywell Inc., "MK VI, MK VIII, Enhanced Ground Proximity Warning System (Class A TAWS), Installation Design Guide", July 2003]
** [http://www51.honeywell.com/sites/aero/common/documents/Mk_VI_VIII_EGPWS.pdf Honeywell Inc., "MK VI and MK VIII Enhanced Ground Proximity Warning System Pilot's Guide", February 2002]

[[Category:Aircraft enhancement]]

Ground proximity warning system

2026-06-28T21:08:24Z

Octal450: /* Decoding Outputs */

'''Ground Proximity Warning System''' ('''GPWS''') is a system designed to alert pilots if their [[aircraft]] is in immediate danger of flying into the ground or an obstacle. Another common name for such a system is '''Ground-Collision Warning System''' ('''GCWS''').
More advanced systems, providing additional protection based on GPS position and a terrain database, are known as '''Enhanced Ground Proximity Warning Systems''' ('''EGPWS''').

The EGPWS provided by FlightGear emulates the '''MK VIII''' made by Honeywell Inc.
It provides all inputs and outputs of the original hardware.
Also the configuration categories and their encodings are modeled to match the original equipment.

Since FG2018.1 the simulation was extended with optional support for Airbus-specific callouts, which would normally not be supported by the real-world MK VIII hardware unit (which is not intended to be installed on Airbus aircraft).

= Features =
== Warnings ==
The module provides warnings for different alerting modes:

* '''Mode 1: Excessive Descent Rate'''
: Provides 'Sink rate!' and 'Pull up!' alerts based on descent rate at low radio altitudes (below 2500').

* '''Mode 2: Excessive Terrain Closure Rate'''
: Provides 'Pull up!' and 'Terrain!' callouts around rising terrain.

* '''Mode 3: Altitude Loss After Takeoff'''
: Provides alerts against altitude loss after takeoff (or a go-around). Losing altitude triggers a 'Don't sink!' alert.

* '''Mode 4: Unsafe Terrain Clearance'''
: Provides alerts against insufficient clearance, based upon the aircraft configuration and flight phase (takeoff, cruise, approach), and independent of terrain closure rate (i.e situations that modes 1 & 2 would not alert). Alerts include 'Too low - terrain!', 'Too low - gear!' and 'Too low - flaps!'. Also protects against a gear-up landing or approach without flaps in the landing configuration.

* '''Mode 5: Excessive Deviation Below Glideslope'''
: Provides 'Glideslope!' alerts when deviating below a glideslope while established on a localizer.

* '''Mode 6: Advisory Callouts'''
: Provides callouts based on the specified decision-height and radio altitude. This includes a 'Minimums' alert based upon the decision-height, and callouts while descending through various radio altitudes (1000', 500', 200', 100', 50', 40', 30', 20' and 10'). Also provides a 'Bank angle' alert based upon excessive aircraft roll.

* '''Mode 7: Windshear Protection'''
: Windshear protection is currently ''not'' implemented.

== Other ==

* '''Self-test'''
: Triggers all warnings enabled for the specific plane one by one.

* '''Status display'''
: Shows module configuration and status.

= Add to an Aircraft =
== Instrument List ==
Add the device to your plane by adding it to the sim/instrumentation section (usually in a separate instrumentation.xml file).

Example:
<PropertyList>
<sim>
<instrumentation>

'''<mk-viii>'''
'''<name>mk-viii</name>'''
'''<number>0</number>'''
'''</mk-viii>'''

</instrumentation>
</sim>
</PropertyList>
Usually planes only have a single GPWS installed - so using multiple instances wouldn't be too common.

== <Plane>-set.xml file ==
Configuration parameters are stored in a different section.
Add the following XML template to the instrumentation section of the plane's ...-set.xml file.
Do not mix up this section with the one above (section above was ''within'' the <sim> tag, this section is ''outside'' the <sim> tag).

'''Notes''':
* The values in the <tt><configuration-module></tt> section (below) list the module's default. You can omit specific <tt><category-''n''></tt> lines unless you need to change the default.
* All configuration categories require valid settings. If you do explicitly configure a category to change the default, you must provide a valid value. See sections below for valid options.
* Do ''not'' omit the <serviceable>true</serviceable> part...

=== XML Template ===
<PropertyList>
<nowiki></nowiki>

<instrumentation>
<mk-viii> <nowiki></nowiki>

<serviceable>true</serviceable> <nowiki></nowiki>

<configuration-module>
<category-1> 0 </category-1> <nowiki></nowiki>
<category-3> 2 </category-3> <nowiki></nowiki>
<category-4> 13 </category-4> <nowiki></nowiki>
<category-5> 0 </category-5> <nowiki></nowiki>
<category-6> 1 </category-6> <nowiki></nowiki>
<category-7> 124 </category-7> <nowiki></nowiki>
<category-8> 2 </category-8> <nowiki></nowiki>
<category-9> 3 </category-9> <nowiki></nowiki>
<category-10> 6 </category-10> <nowiki></nowiki>
<category-13> 7 </category-13> <nowiki></nowiki>
<category-14> 0 </category-14> <nowiki></nowiki>
</configuration-module>

<inputs> <nowiki></nowiki>
<arinc429>
<decision-height-ncd> false </decision-height-ncd>
<decision-height> 200 </decision-height>
</arinc429>
</inputs>

<speaker> <nowiki></nowiki>
<max-dist> 2 </max-dist> <nowiki></nowiki>
<reference-dist> 1 </reference-dist> <nowiki></nowiki>
<volume> 0.4 </volume> <nowiki></nowiki>
</speaker>

<voice>
<file-prefix type="string">Sounds/mk-viii/</file-prefix>
<nowiki></nowiki>
</voice>

</mk-viii>
</instrumentation>

</PropertyList>

The example above provides the decision height as a fixed value. Since this value is an input, you can also provide this value at run-time instead - e.g. depending on whether an ILS or visual approach is flown.

=== Unimplemented Categories ===
Some configuration categories are currently ''not'' implemented. The following elements are therefore omitted in the XML template:
<category-2> 1 </category-2> <nowiki></nowiki>
<category-11> 2 </category-11> <nowiki></nowiki>
<category-12> 0 </category-12> <nowiki></nowiki>
<category-15> 0 </category-15> <nowiki></nowiki>
<category-16> 0 </category-16> <nowiki></nowiki>
<category-17> 0 </category-17> <nowiki></nowiki>

== Electric Power ==
The mk-viii module needs (virtual) electric power. The module also simulates the behavior of the original hardware device when applying over or under voltage - i.e. it withstands short periods of too low or high voltage (within certain limits). Supply a nominal value of 28 volts. Usually you'll provide power via Nasal by connecting the module to the electrical bus simulation. If you're plane doesn't provide such a simulation you can also configure a fixed value (i.e. '''28''') to the following property:
/systems/electrical/outputs/''<name>''[''<num>'']
where ''<name>'' and ''<num>'' match the values you specified in the instrument list, e.g. for ''<name>=mk-viii and ''<num>''=0
/systems/electrical/outputs/mk-viii[0]

= Configuration =
== Hints ==
* Trigger the self-test to check if the EGPWS is enabled and to check which callouts are enabled for this airplane. Set the property <tt>/instrumentation/mk-viii/inputs/discretes/self-test</tt> to <tt>true</tt> to trigger the self-test. Enabling this input for 2 seconds triggers short self-test, enabling it for at least 5 seconds triggers a full self-test. The plane must be on ground and stopped, otherwise the self-test is inhibited.
* You can test EGPWS configuration without restarting FlightGear by modifying the configuration values in the Property Browser manually and then forcing the EGPWS to reload the configuration by toggling the plane's electrical power (OFF-ON).

== Configuration Categories ==
=== Aircraft Mode Select ===
<category-1> 0 </category-1> <nowiki></nowiki>
This is the device's main configuration setting. It selects the envelops for allowed speeds and minimum heights for all EGPWS modes. The envelops are configured by selecting an entire set of configuration values. This simplifies the configuration, however, new airplane types may require to modify the mk-viii sources in order to support an appropriate configuration set.

{|border="1" cellspacing="0" align="center"
!category-1
!Aircraft Type Description
!Type
!Gear down at 500ft
when slower than
!Flaps down at
!Max airspeed
flaps/gear down*
!Min Runway Length
|-
|align="right"|'''(default) 0'''
|Fast turboprop, normal flap deployment
|align="center"|T6
|align="center"|178 knots
|align="center"|170 ft / 150 knots
|align="center"|250 / 290 knots
|align="center"|2000m
|-
|align="right"|1
|Fast turboprop, delayed flap deployment
|align="center"|T8
|align="center"|178 knots
|align="center"|150 ft / 148 knots
|align="center"|250 / 290 knots
|align="center"|2000m
|-
|align="right"|2
|Fast turboprop (old GPWS emulation)
|align="center"|T5
|align="center"|178 knots
|align="center"|200 ft / 148 knots
|align="center"|250 / 290 knots
|align="center"|2000m
|-
|align="right"|3
|Slow turboprop, normal flap deployment
|align="center"|T7
|align="center"|148 knots
|align="center"|170 ft / 120 knots
|align="center"|180 / 200 knots
|align="center"|2000m
|-
|align="right"|4
|Slow turboprop, delayed flap deployment
|align="center"|T9
|align="center"|148 knots
|align="center"|150 ft / 118 knots
|align="center"|180 / 200 knots
|align="center"|2000m
|-
|align="right"|254
|Fast, heavy turbofans (jets), requiring 3500m runways
|align="center"|T1
|align="center"|190 knots
|align="center"|245 ft / 159 knots
|align="center"|250 / 290 knots
|align="center"|3500m
|-
|align="right"|255
|Fast turbofans (jets), requiring 2000m runways
|align="center"|T1
|align="center"|190 knots
|align="center"|200 ft / 159 knots
|align="center"|250 / 290 knots
|align="center"|2000m
|}
* When maximum gear down/flaps down airspeeds are exceeded for at least 60 seconds the EGPWS triggers a fault and assumes the gear down / flaps down inputs to be invalid.

=== Position Input Select ===
<category-3> 2 </category-3> <nowiki></nowiki>
Some warning modes require the plane's GPS position, e.g. in order to find the nearest runway in its internal database to provide correct height callouts.
* 1: GPS data is supplied to the inputs externally (e.g. NASAL script). You need to provide input to
:<tt>/instrumentation/mk-viii/inputs/arinc429/gps-altitude</tt>
:<tt>/instrumentation/mk-viii/inputs/arinc429/gps-latitude</tt>
:<tt>/instrumentation/mk-viii/inputs/arinc429/gps-longitude</tt>
:<tt>/instrumentation/mk-viii/inputs/arinc429/gps-vertical-figure-of-merit</tt>
* '''2 (default)''': GPS data uses internal source (enables a hard-wired connection within the simulator)

=== Altitude Callouts ===
<category-4> 13 </category-4> <nowiki></nowiki>
Select a set of callouts for the approach phase.

{|border="1" cellspacing="0" align="center"
!category-4
!Callouts
|-
|align="right"|0
|Minimums, SMART_500, 200, 100, 50, 40, 30, 20, 10. ''"SMART_500" limits the 500ft callout to non-precision approaches (when no glideslope is captured or g/s is at least 2 dots above/below).''
|-
|align="right"|1
|Minimums, SMART_500, 200
|-
|align="right"|2
|Minimums, SMART_500, 100, 50, 40, 30, 20, 10
|-
|align="right"|3
|Minimums, SMART_500
|-
|align="right"|4
|Minimums, 200, 100, 50, 40, 30, 20, 10
|-
|align="right"|5
|Minimums, 200
|-
|align="right"|6
|Minimums, 100, 50, 40, 30, 20, 10
|-
|align="right"|7
|''All call-outs disabled.''
|-
|align="right"|8
|Minimums. ''All altitude callouts disabled.''
|-
|align="right"|9
|Minimums, 500, 200, 100, 50, 40, 30, 20, 10
|-
|align="right"|10
|Minimums, 500, 200
|-
|align="right"|11
|Minimums, 500, 100, 50, 40, 30, 20, 10
|-
|align="right"|12
|Minimums, 500
|-
|align="right"|'''(default) 13'''
|Minimums, 1000, 500, 400, 300, 200, 100, 50, 40, 30, 20, 10 ''(This option should match Boeing and most other airliners, except Airbus.)''
|-
|align="right"|14
|Minimums, 100
|-
|align="right"|15
|Minimums, 200, 100
|-
|align="right"|100
|FIELD_500. ''Provides “500” callout at an altitude 500ft above the actual runway altitude.''
|-
|align="right"|101
|FIELD_500_ABOVE. ''Provides “500 above” callout at an altitude 500ft above the actual runway altitude.''
|-
|colspan="2"|''The options below are not available with the original mk-viii hardware unit. They were added for the FlightGear simulation (with FG 2018.1 and newer) to support typical GPWS callouts of Airbus aircraft.''
|-
|align="right"|'''1000'''
|Above_100, Minimums, 2500, 1000, 500, 400, 300, 200, 100, 50, 40, 30, 20, 10, Retard ''(This option should match most Airbus aircraft.)''
|-
|align="right"|1001
|Minimums, 2500, 1000, 500, 400, 300, 200, 100, 50, 40, 30, 20, 10, Retard
|-
|align="right"|1002
|Minimums, 2500, 1000, 500, 400, 300, 200, 100, 50, 40, 30, 20, 10
|-
|align="right"|1010
|Above_100, Minimums, 1000, 500, 400, 300, 200, 100, 50, 40, 30, 20, 10, Retard
|-
|align="right"|1011
|Minimums, 1000, 500, 400, 300, 200, 100, 50, 40, 30, 20, 10, Retard
|}

The 500ft callout is available in four options:
* "SMART_500" limits the 500ft callout to non-precision approaches (when no glideslope is captured or g/s is at least 2 dots above/below).
* "FIELD_500" configures the 500ft callout to consider the altitude above the actual runway altitude (instead of the current radio altitude).
* "FIELD_500_ABOVE" is like "FIELD_500", but triggers a "500 '''above'''" callout (instead of "500").
* "500" enables the standard callout, i.e. triggers whenever the radio altimeter reports a current altitude of 500ft.

=== Audio Menu Select ===
<category-5> 0 </category-5> <nowiki></nowiki>
Configure retractable or fixed gear aircraft.
* '''0 (default)''': Configured for retractable gear aircraft. „Too low - gear!“ and „Too low - flaps!“ callouts enabled.
* 2: Configured for fixed gear aircraft. „Too low, flaps!“ callout enabled.

=== Terrain Collision Warning ===
<category-6> 1 </category-6> <nowiki></nowiki>
Enable/disable terrain collision warnings.
* '''1 (default)''': Terrain collision warnings enabled.
* 2: Terrain collision warnings disabled.

=== Options Select ===
<category-7> 124 </category-7> <nowiki></nowiki>
Enable/disable bank angle and steep approach warnings and select flap type.
* bit 0: ''not implemented''
* bit 1: flap reversal.
: '''0 = normal logic (default)'''
: 2 = invert logic when detecting extended/retracted flaps
* bit 2: bank angle alert
: 0 = bank angle alert disabled
: '''4 = enabled (default)'''
* bit 3-5: ''not implemented but enabled by default''
* bit 6: steep approach
: 0 = steep approach warning disabled
: '''64 = steep approach warning enabled (default)'''
* bit 7: ''not implemented''

'''Example''': Value 68 (= 64+ 4) enables bank angle, steep approach alert and normal flap logic.

'''Note''': Default is 124. This also enables additional feature bits (which are currently unsupported).

=== Radio Altitude Input Select ===
<category-8> 2 </category-8> <nowiki></nowiki>
Select radio altimeter input source.

* '''2 (default)''': Altitude source is property "/position/altitude-agl-ft". Works for all FDMs - but this is ''not precise enough to drive useful 20ft and 10ft callouts'' (see below).
* 3: Altitude source is "/position/gear-agl-ft". Very precise altitude of gear-above-ground - but only available for planes with YASim FDM (so far).
* 4: Altitude source is "/instrumentation/radar-altimeter/radar-altitude-ft". A radar altimeter instrument must be installed.

'''Hint''': Most simulator altitude properties refer to the plane's center (of gravity) - but not to the altitude of the main gear. A radar altimeter on a real plane is always calibrated to the gear, hence provides precise information (yes, only within a certain degree of the angle of attack...).
Without a precise altitude source the final callouts before touch down, especially 20ft and 10ft, make no sense or may not even work - very annoying, since most aircraft require a final nose up flare at about 20ft. So precise callouts are very welcome.
Using a radar altimeter instrument is recommended since this is most realistic - and it can (and should) be calibrated to the main gear. See ...(TODO)... for a configuration example.

'''Note''': This configuration category is supported beginning with FlightGear 2.2.

=== Navigation Input Select ===
<category-9> 3 </category-9> <nowiki></nowiki>
Enable/disable glideslope warnings.
* 0: localizer input disabled (disables glideslope warnings)
* '''3 (default)''': localizer input enabled (enables glideslope warning)
: '''Note''': By default, the module is hard-wired to the NAV0 receiver for glideslope warnings, i.e. in order to use the NAV1 receiver you need to update the inputs externally through nasal, etc (see [[#Module I/O|Module I/O]]).

=== Attitude Input Select ===
<category-10> 6 </category-10> <nowiki></nowiki>
Select attitude input source.

'''Note''': This configuration category is implemented for the latest FlightGear version only (GIT sources as of ''''2010-07-30'''' or newer).
* 2: Read data from attitude instrument (requires vacuum system to work).
* '''6 (default)''': Read data from hard-wired connection within simulator.

=== Input and Output Configuration ===
<category-13> 7 </category-13> <nowiki></nowiki>
This configuration value configures the behavior of the module's outputs, usually connected to warning lamps in the cockpit, and enables inputs, which should be connected to cockpit switches.

{|border="1" cellspacing="0" align="center"
!
|colspan="2"|'''Output Lamp Configuration'''
|colspan="3"|'''Input Switch Configuration'''
When enabled, appropriate inputs are supplied to the module
(e.g. inputs should be connected to cockpit switches).
|-
!category-13
!Output
Format *
!Lamp
Flashing **
!GPWS Inhibit
Switch Enabled
!Momentary Flap
Override Switch Enabled
!Alternate Steep
Approach Switch Enabled
|-
|align="right"|0
|align="center"|warning
|align="center"|steady
|
|align="center"|x
|align="center"|x
|-
|align="right"|1
|align="center"|alert
|align="center"|steady
|
|align="center"|x
|align="center"|x
|-
|align="right"|2
|align="center"|warning
|align="center"|steady
|align="center"|x
|align="center"|x
|align="center"|x
|-
|align="right"|3
|align="center"|alert
|align="center"|steady
|align="center"|x
|align="center"|x
|align="center"|x
|-
|align="right"|4
|align="center"|warning
|align="center"|flashing
|align="center"|x
|align="center"|x
|align="center"|x
|-
|align="right"|5
|align="center"|alert
|align="center"|flashing
|align="center"|x
|align="center"|x
|align="center"|x
|-
|align="right"|6
|align="center"|warning
|align="center"|steady
|align="center"|x
|align="center"|x
|
|-
|align="right"|'''(default) 7'''
|align="center"|alert
|align="center"|steady
|align="center"|x
|align="center"|x
|
|-
|align="right"|254
|align="center"|warning
|align="center"|steady
|align="center"|x
|
|align="center"|x
|-
|align="right"|255
|align="center"|warning
|align="center"|steady
|align="center"|x
|
|align="center"|x
|}

* '''Output Format''': 'alert': caution conditions trigger the alert output lamp, otherwise caution conditions triggers warning output.

** '''Lamp Flashing''': Selects whether output lamps should flash or be lit steadily when warning/alert/caution is triggered.

=== Audio Output Level ===
<category-14> 0 </category-14> <nowiki></nowiki>
Basic audio configuration.

{|border="1" cellspacing="0"
!category-14
!Audio Relative
Volume
|-
|align="right"|'''(default) 0'''
|align="right"|0 dB
|-
|align="right"|1
|align="right"| -6 dB
|-
|align="right"|2
|align="right"| -12 dB
|-
|align="right"|3
|align="right"| -18 dB
|-
|align="right"|4
|align="right"| -24 dB
|}

== Speaker Configuration ==
The audio speaker can be configured by modifying the properties beneath <tt>/instrumentation/mk-viii/speaker</tt>.
These properties match the xmlsound properties.

For additional information, check out <tt>[[$FG_ROOT]]/Docs/README.xmlsound</tt>.

== Voice Configuration ==
The GPWS uses a fixed default voice. The voice can be changed by providing custom voice samples and providing a different path and filename prefix.

<voice>
<file-prefix type="string">Sounds/mk-viii/</file-prefix>
<nowiki></nowiki>
</voice>

'''Note:'''
* The voice configuration option is supported by FlightGear '''2.3.0''' and newer.

= Advanced =
This section lists some advanced configuration and integration options.

== Example ==
You may want to check the FG implementation of the [[Boeing 777-200]] aircraft for an extensive example of GPWS integration. This plane provides a Nasal GPWS wrapper for the mk-viii module and implements all standard (Boeing) buttons and displays, i.e.:
* Self-test push button
* Glide-slope warning disable button (e.g. to silence warnings during a visual approach)
* Flap and gear override buttons (e.g. to silence flap/gear warnings in emergency situations, like stuck gear etc).
* Terrain/GPWS disable buttons
* GPWS connection to master-warning light.
* GPWS connection to PFD (to display "PULL UP").

== Module I/O ==
* The inputs and outputs match those of the real device and are made available through the FlightGear property tree.
* Input monitoring is implemented. The loss of inputs required for a particular function is annunciated through the GPWS INOP and/or TERR FAIL lamps.
* The "Present Status" function, which enumerates current faults and lists other device details, is implemented.
* Connect outputs to cockpit instruments, e.g. the EGPWS alert and glideslope outputs to the appropriate warning lamps.
* Connect the <tt>/instrumentation/mk-viii/inputs/discretes/self-test</tt> property to the GPWS self-test button in your cockpit. Testing GPWS operation may be part of the preflight check-list.
* To assist the aircraft designer with the installation of the EGPWS, most inputs are connected to standard FlightGear properties by default. When an input feeder (<tt>...-ncd</tt> property) is set to true, the input it is associated with is automatically updated, using a standard FlightGear property. When the <tt>...-ncd</tt> property it is set to false, its associated input must be manually updated every frame, using a Nasal script or some other mechanism.
* The aircraft's decision height needs to be configured when the 'Minimums' warning is enabled. You can provide the decision height as fixed input value to <tt>/instruments/mk-viii/inputs/arinc429/decision-height</tt>:
<arinc429>
<decision-height-ncd> false </decision-height-ncd>
<decision-height> 200 </decision-height>
</arinc429>

=== Decoding Outputs ===
For some reason, the developers of this module decided to output status via a simulated ARINC429 bus, instead of normal booleans, which makes things infinitely more complex than they need to be for developers looking to interface with this module. Thus, the below section will explain how to interpret the outputs.

The "bit" position for the number (for example, 4096 being the value for bit 12, the "Pull Up" warning) can be checked in the word input from the property tree to see if the warning is active.

;Example Decoder for "Pull Up"
<syntaxhighlight lang="nasal">
var MkViiiTranslator = {
discrete1: 0,
pullUp: 0,
decode: func() {
me.discrete1 = getprop("/instrumentation/mk-viii/outputs/arinc429/egpws-alert-discrete-1");
me.pullUp = me.hasBit(me.discrete1, 4096);
},
hasBit: func(word, bit) {
return math.mod(int(word / bit), 2);
},
};
</syntaxhighlight>

;Properties:
* <code>/instrumentation/mk-viii/outputs/arinc429/egpws-alert-discrete-1</code>
* <code>/instrumentation/mk-viii/outputs/arinc429/egpws-alert-discrete-2</code>
* <code>/instrumentation/mk-viii/outputs/arinc429/egpwc-alert-discrete-3</code>
* <code>/instrumentation/mk-viii/outputs/arinc429/egpwc-logic-discretes</code>
* <code>/instrumentation/mk-viii/outputs/arinc429/mode6-callouts-discrete-1</code>
* <code>/instrumentation/mk-viii/outputs/arinc429/mode6-callouts-discrete-2</code>
 

;Warning Bit Matrix:
;egpws-alert-discrete-1
{|class="wikitable"
! Alert !! Bit
|-
| Sink Rate || 2048
|-
| Pull Up || 4096
|-
| Terrain || 8192
|-
| Don't Sink || 16384
|-
| Too Low Gear || 32768
|-
| Too Low Flaps || 65536
|-
| Too Low Terrain || 131072
|-
| Glideslope || 262144
|-
| Minimums || 524288
|}

;egpws-alert-discrete-2
{|class="wikitable"
! Alert !! Bit
|-
| Glideslope Cancel || 2048
|-
| GPWS Alert Lamp || 4096
|-
| GPWS Warning Lamp || 8192
|-
| GPWS Inop || 16384
|-
| Audio Active || 65536
|-
| TAD Inop || 16777216
|-
| Fault Present || 33554432
|-
| Terrain NA || 134217728
|}

;egpwc-alert-discrete-3
{|class="wikitable"
! Alert !! Bit
|-
| Modes 1-4 Inop || 2048
|-
| Mode 5 Inop || 4096
|-
| Mode 6 Inop || 8192
|-
| Bank Angle Inop || 16384
|-
| TAD Inop || 65536
|-
| Always set || 131072
|-
| Always set || 262144
|}

;egpwc-logic-discretes
{|class="wikitable"
! Alert !! Bit
|-
| TCF Too Low Terrain || 8192
|-
| Takeoff Mode || 262144
|-
| Mode 1 Sink Rate || 524288
|-
| Mode 1 Pull Up || 1048576
|-
| Mode 2 Terrain || 2097152
|-
| Mode 2 Warning || 4194304
|-
| Mode 3 Don't Sink || 8388608
|-
| Mode 4 Too Low Gear/Flaps/Terrain || 16777216
|-
| Mode 5 Glideslope || 33554432
|}

;mode6-callouts-discrete-1
{|class="wikitable"
! Alert !! Bit
|-
| Minimums || 2048
|-
| 10 || 65536
|-
| 20 || 131072
|-
| 30 || 262144
|-
| 40 || 524288
|-
| 50 || 1048576
|-
| 100 || 8388608
|-
| 200 || 16777216
|-
| 300 || 33554432
|}

;mode6-callouts-discrete-2
{|class="wikitable"
! Alert !! Bit
|-
| 400 || 2048
|-
| 500 || 4096
|-
| 1000 || 8192
|-
| 2500 || 16384
|-
| Bank Angle || 262144
|-
| 500 Above|| 524288
|}

== Module Status ==
The original MK VIII supports an RS232 interface to read the module status. Since FlightGear does not support RS232 interfaces, all data is printed to the standard output. Trigger <tt>/instrumentation/mk-viii/inputs/discretes/rs-232/present-status</tt> to print the current module configuration and status:

EGPWC CONFIGURATION
PART NUMBER: 965-1220-000
MOD STATUS: N/A
SERIAL NUMBER: N/A

APPLICATION S/W VERSION: 2.0.0
TERRAIN DATABASE VERSION: 2.0.0
ENVELOPE MOD DATABASE VERSION: N/A
BOOT CODE VERSION: 2.0.0

CURRENT FAULTS
NO FAULTS

CONFIGURATION:
AIRCRAFT TYPE = 0
AIR DATA TYPE = 1
POSITION INPUT TYPE = 2
CALLOUTS OPTION TYPE = 13
AUDIO MENU TYPE = 0
TERRAIN DISPLAY TYPE = 1
OPTIONS 1 TYPE = 124
RADIO ALTITUDE TYPE = 2
NAVIGATION INPUT TYPE = 3
ATTITUDE TYPE = 6
MAGNETIC HEADING TYPE = 2
WINDSHEAR INPUT TYPE = 0
IO DISCRETE TYPE = 7
VOLUME SELECT = 0

= External Links =
* Documentation by the original module developer [http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg01902.html 1] [http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg01902/mk-viii-manual.tgz 2]
* Original manufacturer documentation
** [http://www.egpws.com/engineering_support/documents/install/060-4314-150.pdf Honeywell Inc., "MK VI, MK VIII, Enhanced Ground Proximity Warning System (Class A TAWS), Installation Design Guide", July 2003]
** [http://www51.honeywell.com/sites/aero/common/documents/Mk_VI_VIII_EGPWS.pdf Honeywell Inc., "MK VI and MK VIII Enhanced Ground Proximity Warning System Pilot's Guide", February 2002]

[[Category:Aircraft enhancement]]

Ground proximity warning system

2026-06-28T21:05:50Z

Octal450: /* Module I/O */ Add decoding information because this is annoyingly overcomplicated and undocumented...

'''Ground Proximity Warning System''' ('''GPWS''') is a system designed to alert pilots if their [[aircraft]] is in immediate danger of flying into the ground or an obstacle. Another common name for such a system is '''Ground-Collision Warning System''' ('''GCWS''').
More advanced systems, providing additional protection based on GPS position and a terrain database, are known as '''Enhanced Ground Proximity Warning Systems''' ('''EGPWS''').

The EGPWS provided by FlightGear emulates the '''MK VIII''' made by Honeywell Inc.
It provides all inputs and outputs of the original hardware.
Also the configuration categories and their encodings are modeled to match the original equipment.

Since FG2018.1 the simulation was extended with optional support for Airbus-specific callouts, which would normally not be supported by the real-world MK VIII hardware unit (which is not intended to be installed on Airbus aircraft).

= Features =
== Warnings ==
The module provides warnings for different alerting modes:

* '''Mode 1: Excessive Descent Rate'''
: Provides 'Sink rate!' and 'Pull up!' alerts based on descent rate at low radio altitudes (below 2500').

* '''Mode 2: Excessive Terrain Closure Rate'''
: Provides 'Pull up!' and 'Terrain!' callouts around rising terrain.

* '''Mode 3: Altitude Loss After Takeoff'''
: Provides alerts against altitude loss after takeoff (or a go-around). Losing altitude triggers a 'Don't sink!' alert.

* '''Mode 4: Unsafe Terrain Clearance'''
: Provides alerts against insufficient clearance, based upon the aircraft configuration and flight phase (takeoff, cruise, approach), and independent of terrain closure rate (i.e situations that modes 1 & 2 would not alert). Alerts include 'Too low - terrain!', 'Too low - gear!' and 'Too low - flaps!'. Also protects against a gear-up landing or approach without flaps in the landing configuration.

* '''Mode 5: Excessive Deviation Below Glideslope'''
: Provides 'Glideslope!' alerts when deviating below a glideslope while established on a localizer.

* '''Mode 6: Advisory Callouts'''
: Provides callouts based on the specified decision-height and radio altitude. This includes a 'Minimums' alert based upon the decision-height, and callouts while descending through various radio altitudes (1000', 500', 200', 100', 50', 40', 30', 20' and 10'). Also provides a 'Bank angle' alert based upon excessive aircraft roll.

* '''Mode 7: Windshear Protection'''
: Windshear protection is currently ''not'' implemented.

== Other ==

* '''Self-test'''
: Triggers all warnings enabled for the specific plane one by one.

* '''Status display'''
: Shows module configuration and status.

= Add to an Aircraft =
== Instrument List ==
Add the device to your plane by adding it to the sim/instrumentation section (usually in a separate instrumentation.xml file).

Example:
<PropertyList>
<sim>
<instrumentation>

'''<mk-viii>'''
'''<name>mk-viii</name>'''
'''<number>0</number>'''
'''</mk-viii>'''

</instrumentation>
</sim>
</PropertyList>
Usually planes only have a single GPWS installed - so using multiple instances wouldn't be too common.

== <Plane>-set.xml file ==
Configuration parameters are stored in a different section.
Add the following XML template to the instrumentation section of the plane's ...-set.xml file.
Do not mix up this section with the one above (section above was ''within'' the <sim> tag, this section is ''outside'' the <sim> tag).

'''Notes''':
* The values in the <tt><configuration-module></tt> section (below) list the module's default. You can omit specific <tt><category-''n''></tt> lines unless you need to change the default.
* All configuration categories require valid settings. If you do explicitly configure a category to change the default, you must provide a valid value. See sections below for valid options.
* Do ''not'' omit the <serviceable>true</serviceable> part...

=== XML Template ===
<PropertyList>
<nowiki></nowiki>

<instrumentation>
<mk-viii> <nowiki></nowiki>

<serviceable>true</serviceable> <nowiki></nowiki>

<configuration-module>
<category-1> 0 </category-1> <nowiki></nowiki>
<category-3> 2 </category-3> <nowiki></nowiki>
<category-4> 13 </category-4> <nowiki></nowiki>
<category-5> 0 </category-5> <nowiki></nowiki>
<category-6> 1 </category-6> <nowiki></nowiki>
<category-7> 124 </category-7> <nowiki></nowiki>
<category-8> 2 </category-8> <nowiki></nowiki>
<category-9> 3 </category-9> <nowiki></nowiki>
<category-10> 6 </category-10> <nowiki></nowiki>
<category-13> 7 </category-13> <nowiki></nowiki>
<category-14> 0 </category-14> <nowiki></nowiki>
</configuration-module>

<inputs> <nowiki></nowiki>
<arinc429>
<decision-height-ncd> false </decision-height-ncd>
<decision-height> 200 </decision-height>
</arinc429>
</inputs>

<speaker> <nowiki></nowiki>
<max-dist> 2 </max-dist> <nowiki></nowiki>
<reference-dist> 1 </reference-dist> <nowiki></nowiki>
<volume> 0.4 </volume> <nowiki></nowiki>
</speaker>

<voice>
<file-prefix type="string">Sounds/mk-viii/</file-prefix>
<nowiki></nowiki>
</voice>

</mk-viii>
</instrumentation>

</PropertyList>

The example above provides the decision height as a fixed value. Since this value is an input, you can also provide this value at run-time instead - e.g. depending on whether an ILS or visual approach is flown.

=== Unimplemented Categories ===
Some configuration categories are currently ''not'' implemented. The following elements are therefore omitted in the XML template:
<category-2> 1 </category-2> <nowiki></nowiki>
<category-11> 2 </category-11> <nowiki></nowiki>
<category-12> 0 </category-12> <nowiki></nowiki>
<category-15> 0 </category-15> <nowiki></nowiki>
<category-16> 0 </category-16> <nowiki></nowiki>
<category-17> 0 </category-17> <nowiki></nowiki>

== Electric Power ==
The mk-viii module needs (virtual) electric power. The module also simulates the behavior of the original hardware device when applying over or under voltage - i.e. it withstands short periods of too low or high voltage (within certain limits). Supply a nominal value of 28 volts. Usually you'll provide power via Nasal by connecting the module to the electrical bus simulation. If you're plane doesn't provide such a simulation you can also configure a fixed value (i.e. '''28''') to the following property:
/systems/electrical/outputs/''<name>''[''<num>'']
where ''<name>'' and ''<num>'' match the values you specified in the instrument list, e.g. for ''<name>=mk-viii and ''<num>''=0
/systems/electrical/outputs/mk-viii[0]

= Configuration =
== Hints ==
* Trigger the self-test to check if the EGPWS is enabled and to check which callouts are enabled for this airplane. Set the property <tt>/instrumentation/mk-viii/inputs/discretes/self-test</tt> to <tt>true</tt> to trigger the self-test. Enabling this input for 2 seconds triggers short self-test, enabling it for at least 5 seconds triggers a full self-test. The plane must be on ground and stopped, otherwise the self-test is inhibited.
* You can test EGPWS configuration without restarting FlightGear by modifying the configuration values in the Property Browser manually and then forcing the EGPWS to reload the configuration by toggling the plane's electrical power (OFF-ON).

== Configuration Categories ==
=== Aircraft Mode Select ===
<category-1> 0 </category-1> <nowiki></nowiki>
This is the device's main configuration setting. It selects the envelops for allowed speeds and minimum heights for all EGPWS modes. The envelops are configured by selecting an entire set of configuration values. This simplifies the configuration, however, new airplane types may require to modify the mk-viii sources in order to support an appropriate configuration set.

{|border="1" cellspacing="0" align="center"
!category-1
!Aircraft Type Description
!Type
!Gear down at 500ft
when slower than
!Flaps down at
!Max airspeed
flaps/gear down*
!Min Runway Length
|-
|align="right"|'''(default) 0'''
|Fast turboprop, normal flap deployment
|align="center"|T6
|align="center"|178 knots
|align="center"|170 ft / 150 knots
|align="center"|250 / 290 knots
|align="center"|2000m
|-
|align="right"|1
|Fast turboprop, delayed flap deployment
|align="center"|T8
|align="center"|178 knots
|align="center"|150 ft / 148 knots
|align="center"|250 / 290 knots
|align="center"|2000m
|-
|align="right"|2
|Fast turboprop (old GPWS emulation)
|align="center"|T5
|align="center"|178 knots
|align="center"|200 ft / 148 knots
|align="center"|250 / 290 knots
|align="center"|2000m
|-
|align="right"|3
|Slow turboprop, normal flap deployment
|align="center"|T7
|align="center"|148 knots
|align="center"|170 ft / 120 knots
|align="center"|180 / 200 knots
|align="center"|2000m
|-
|align="right"|4
|Slow turboprop, delayed flap deployment
|align="center"|T9
|align="center"|148 knots
|align="center"|150 ft / 118 knots
|align="center"|180 / 200 knots
|align="center"|2000m
|-
|align="right"|254
|Fast, heavy turbofans (jets), requiring 3500m runways
|align="center"|T1
|align="center"|190 knots
|align="center"|245 ft / 159 knots
|align="center"|250 / 290 knots
|align="center"|3500m
|-
|align="right"|255
|Fast turbofans (jets), requiring 2000m runways
|align="center"|T1
|align="center"|190 knots
|align="center"|200 ft / 159 knots
|align="center"|250 / 290 knots
|align="center"|2000m
|}
* When maximum gear down/flaps down airspeeds are exceeded for at least 60 seconds the EGPWS triggers a fault and assumes the gear down / flaps down inputs to be invalid.

=== Position Input Select ===
<category-3> 2 </category-3> <nowiki></nowiki>
Some warning modes require the plane's GPS position, e.g. in order to find the nearest runway in its internal database to provide correct height callouts.
* 1: GPS data is supplied to the inputs externally (e.g. NASAL script). You need to provide input to
:<tt>/instrumentation/mk-viii/inputs/arinc429/gps-altitude</tt>
:<tt>/instrumentation/mk-viii/inputs/arinc429/gps-latitude</tt>
:<tt>/instrumentation/mk-viii/inputs/arinc429/gps-longitude</tt>
:<tt>/instrumentation/mk-viii/inputs/arinc429/gps-vertical-figure-of-merit</tt>
* '''2 (default)''': GPS data uses internal source (enables a hard-wired connection within the simulator)

=== Altitude Callouts ===
<category-4> 13 </category-4> <nowiki></nowiki>
Select a set of callouts for the approach phase.

{|border="1" cellspacing="0" align="center"
!category-4
!Callouts
|-
|align="right"|0
|Minimums, SMART_500, 200, 100, 50, 40, 30, 20, 10. ''"SMART_500" limits the 500ft callout to non-precision approaches (when no glideslope is captured or g/s is at least 2 dots above/below).''
|-
|align="right"|1
|Minimums, SMART_500, 200
|-
|align="right"|2
|Minimums, SMART_500, 100, 50, 40, 30, 20, 10
|-
|align="right"|3
|Minimums, SMART_500
|-
|align="right"|4
|Minimums, 200, 100, 50, 40, 30, 20, 10
|-
|align="right"|5
|Minimums, 200
|-
|align="right"|6
|Minimums, 100, 50, 40, 30, 20, 10
|-
|align="right"|7
|''All call-outs disabled.''
|-
|align="right"|8
|Minimums. ''All altitude callouts disabled.''
|-
|align="right"|9
|Minimums, 500, 200, 100, 50, 40, 30, 20, 10
|-
|align="right"|10
|Minimums, 500, 200
|-
|align="right"|11
|Minimums, 500, 100, 50, 40, 30, 20, 10
|-
|align="right"|12
|Minimums, 500
|-
|align="right"|'''(default) 13'''
|Minimums, 1000, 500, 400, 300, 200, 100, 50, 40, 30, 20, 10 ''(This option should match Boeing and most other airliners, except Airbus.)''
|-
|align="right"|14
|Minimums, 100
|-
|align="right"|15
|Minimums, 200, 100
|-
|align="right"|100
|FIELD_500. ''Provides “500” callout at an altitude 500ft above the actual runway altitude.''
|-
|align="right"|101
|FIELD_500_ABOVE. ''Provides “500 above” callout at an altitude 500ft above the actual runway altitude.''
|-
|colspan="2"|''The options below are not available with the original mk-viii hardware unit. They were added for the FlightGear simulation (with FG 2018.1 and newer) to support typical GPWS callouts of Airbus aircraft.''
|-
|align="right"|'''1000'''
|Above_100, Minimums, 2500, 1000, 500, 400, 300, 200, 100, 50, 40, 30, 20, 10, Retard ''(This option should match most Airbus aircraft.)''
|-
|align="right"|1001
|Minimums, 2500, 1000, 500, 400, 300, 200, 100, 50, 40, 30, 20, 10, Retard
|-
|align="right"|1002
|Minimums, 2500, 1000, 500, 400, 300, 200, 100, 50, 40, 30, 20, 10
|-
|align="right"|1010
|Above_100, Minimums, 1000, 500, 400, 300, 200, 100, 50, 40, 30, 20, 10, Retard
|-
|align="right"|1011
|Minimums, 1000, 500, 400, 300, 200, 100, 50, 40, 30, 20, 10, Retard
|}

The 500ft callout is available in four options:
* "SMART_500" limits the 500ft callout to non-precision approaches (when no glideslope is captured or g/s is at least 2 dots above/below).
* "FIELD_500" configures the 500ft callout to consider the altitude above the actual runway altitude (instead of the current radio altitude).
* "FIELD_500_ABOVE" is like "FIELD_500", but triggers a "500 '''above'''" callout (instead of "500").
* "500" enables the standard callout, i.e. triggers whenever the radio altimeter reports a current altitude of 500ft.

=== Audio Menu Select ===
<category-5> 0 </category-5> <nowiki></nowiki>
Configure retractable or fixed gear aircraft.
* '''0 (default)''': Configured for retractable gear aircraft. „Too low - gear!“ and „Too low - flaps!“ callouts enabled.
* 2: Configured for fixed gear aircraft. „Too low, flaps!“ callout enabled.

=== Terrain Collision Warning ===
<category-6> 1 </category-6> <nowiki></nowiki>
Enable/disable terrain collision warnings.
* '''1 (default)''': Terrain collision warnings enabled.
* 2: Terrain collision warnings disabled.

=== Options Select ===
<category-7> 124 </category-7> <nowiki></nowiki>
Enable/disable bank angle and steep approach warnings and select flap type.
* bit 0: ''not implemented''
* bit 1: flap reversal.
: '''0 = normal logic (default)'''
: 2 = invert logic when detecting extended/retracted flaps
* bit 2: bank angle alert
: 0 = bank angle alert disabled
: '''4 = enabled (default)'''
* bit 3-5: ''not implemented but enabled by default''
* bit 6: steep approach
: 0 = steep approach warning disabled
: '''64 = steep approach warning enabled (default)'''
* bit 7: ''not implemented''

'''Example''': Value 68 (= 64+ 4) enables bank angle, steep approach alert and normal flap logic.

'''Note''': Default is 124. This also enables additional feature bits (which are currently unsupported).

=== Radio Altitude Input Select ===
<category-8> 2 </category-8> <nowiki></nowiki>
Select radio altimeter input source.

* '''2 (default)''': Altitude source is property "/position/altitude-agl-ft". Works for all FDMs - but this is ''not precise enough to drive useful 20ft and 10ft callouts'' (see below).
* 3: Altitude source is "/position/gear-agl-ft". Very precise altitude of gear-above-ground - but only available for planes with YASim FDM (so far).
* 4: Altitude source is "/instrumentation/radar-altimeter/radar-altitude-ft". A radar altimeter instrument must be installed.

'''Hint''': Most simulator altitude properties refer to the plane's center (of gravity) - but not to the altitude of the main gear. A radar altimeter on a real plane is always calibrated to the gear, hence provides precise information (yes, only within a certain degree of the angle of attack...).
Without a precise altitude source the final callouts before touch down, especially 20ft and 10ft, make no sense or may not even work - very annoying, since most aircraft require a final nose up flare at about 20ft. So precise callouts are very welcome.
Using a radar altimeter instrument is recommended since this is most realistic - and it can (and should) be calibrated to the main gear. See ...(TODO)... for a configuration example.

'''Note''': This configuration category is supported beginning with FlightGear 2.2.

=== Navigation Input Select ===
<category-9> 3 </category-9> <nowiki></nowiki>
Enable/disable glideslope warnings.
* 0: localizer input disabled (disables glideslope warnings)
* '''3 (default)''': localizer input enabled (enables glideslope warning)
: '''Note''': By default, the module is hard-wired to the NAV0 receiver for glideslope warnings, i.e. in order to use the NAV1 receiver you need to update the inputs externally through nasal, etc (see [[#Module I/O|Module I/O]]).

=== Attitude Input Select ===
<category-10> 6 </category-10> <nowiki></nowiki>
Select attitude input source.

'''Note''': This configuration category is implemented for the latest FlightGear version only (GIT sources as of ''''2010-07-30'''' or newer).
* 2: Read data from attitude instrument (requires vacuum system to work).
* '''6 (default)''': Read data from hard-wired connection within simulator.

=== Input and Output Configuration ===
<category-13> 7 </category-13> <nowiki></nowiki>
This configuration value configures the behavior of the module's outputs, usually connected to warning lamps in the cockpit, and enables inputs, which should be connected to cockpit switches.

{|border="1" cellspacing="0" align="center"
!
|colspan="2"|'''Output Lamp Configuration'''
|colspan="3"|'''Input Switch Configuration'''
When enabled, appropriate inputs are supplied to the module
(e.g. inputs should be connected to cockpit switches).
|-
!category-13
!Output
Format *
!Lamp
Flashing **
!GPWS Inhibit
Switch Enabled
!Momentary Flap
Override Switch Enabled
!Alternate Steep
Approach Switch Enabled
|-
|align="right"|0
|align="center"|warning
|align="center"|steady
|
|align="center"|x
|align="center"|x
|-
|align="right"|1
|align="center"|alert
|align="center"|steady
|
|align="center"|x
|align="center"|x
|-
|align="right"|2
|align="center"|warning
|align="center"|steady
|align="center"|x
|align="center"|x
|align="center"|x
|-
|align="right"|3
|align="center"|alert
|align="center"|steady
|align="center"|x
|align="center"|x
|align="center"|x
|-
|align="right"|4
|align="center"|warning
|align="center"|flashing
|align="center"|x
|align="center"|x
|align="center"|x
|-
|align="right"|5
|align="center"|alert
|align="center"|flashing
|align="center"|x
|align="center"|x
|align="center"|x
|-
|align="right"|6
|align="center"|warning
|align="center"|steady
|align="center"|x
|align="center"|x
|
|-
|align="right"|'''(default) 7'''
|align="center"|alert
|align="center"|steady
|align="center"|x
|align="center"|x
|
|-
|align="right"|254
|align="center"|warning
|align="center"|steady
|align="center"|x
|
|align="center"|x
|-
|align="right"|255
|align="center"|warning
|align="center"|steady
|align="center"|x
|
|align="center"|x
|}

* '''Output Format''': 'alert': caution conditions trigger the alert output lamp, otherwise caution conditions triggers warning output.

** '''Lamp Flashing''': Selects whether output lamps should flash or be lit steadily when warning/alert/caution is triggered.

=== Audio Output Level ===
<category-14> 0 </category-14> <nowiki></nowiki>
Basic audio configuration.

{|border="1" cellspacing="0"
!category-14
!Audio Relative
Volume
|-
|align="right"|'''(default) 0'''
|align="right"|0 dB
|-
|align="right"|1
|align="right"| -6 dB
|-
|align="right"|2
|align="right"| -12 dB
|-
|align="right"|3
|align="right"| -18 dB
|-
|align="right"|4
|align="right"| -24 dB
|}

== Speaker Configuration ==
The audio speaker can be configured by modifying the properties beneath <tt>/instrumentation/mk-viii/speaker</tt>.
These properties match the xmlsound properties.

For additional information, check out <tt>[[$FG_ROOT]]/Docs/README.xmlsound</tt>.

== Voice Configuration ==
The GPWS uses a fixed default voice. The voice can be changed by providing custom voice samples and providing a different path and filename prefix.

<voice>
<file-prefix type="string">Sounds/mk-viii/</file-prefix>
<nowiki></nowiki>
</voice>

'''Note:'''
* The voice configuration option is supported by FlightGear '''2.3.0''' and newer.

= Advanced =
This section lists some advanced configuration and integration options.

== Example ==
You may want to check the FG implementation of the [[Boeing 777-200]] aircraft for an extensive example of GPWS integration. This plane provides a Nasal GPWS wrapper for the mk-viii module and implements all standard (Boeing) buttons and displays, i.e.:
* Self-test push button
* Glide-slope warning disable button (e.g. to silence warnings during a visual approach)
* Flap and gear override buttons (e.g. to silence flap/gear warnings in emergency situations, like stuck gear etc).
* Terrain/GPWS disable buttons
* GPWS connection to master-warning light.
* GPWS connection to PFD (to display "PULL UP").

== Module I/O ==
* The inputs and outputs match those of the real device and are made available through the FlightGear property tree.
* Input monitoring is implemented. The loss of inputs required for a particular function is annunciated through the GPWS INOP and/or TERR FAIL lamps.
* The "Present Status" function, which enumerates current faults and lists other device details, is implemented.
* Connect outputs to cockpit instruments, e.g. the EGPWS alert and glideslope outputs to the appropriate warning lamps.
* Connect the <tt>/instrumentation/mk-viii/inputs/discretes/self-test</tt> property to the GPWS self-test button in your cockpit. Testing GPWS operation may be part of the preflight check-list.
* To assist the aircraft designer with the installation of the EGPWS, most inputs are connected to standard FlightGear properties by default. When an input feeder (<tt>...-ncd</tt> property) is set to true, the input it is associated with is automatically updated, using a standard FlightGear property. When the <tt>...-ncd</tt> property it is set to false, its associated input must be manually updated every frame, using a Nasal script or some other mechanism.
* The aircraft's decision height needs to be configured when the 'Minimums' warning is enabled. You can provide the decision height as fixed input value to <tt>/instruments/mk-viii/inputs/arinc429/decision-height</tt>:
<arinc429>
<decision-height-ncd> false </decision-height-ncd>
<decision-height> 200 </decision-height>
</arinc429>

=== Decoding Outputs ===
For some reason, the developers of this module decided to output status via a simulated ARINC429 bus, instead of normal booleans, which makes things infinitely more complex than they need to be for developers looking to interface with this module. Thus, the below section will explain how to interpret the outputs.

The "bit" position for the number (for example, 4096 being the value for bit 12, the "Pull Up" warning) can be checked in the word input from the property tree to see if the warning is active.

;Example Decoder Code for "Pull Up"
<syntaxhighlight lang="nasal">
var MkViiiTranslator = {
discrete1: 0,
pullUp: 0,
decode: func() {
me.discrete1 = getprop("/instrumentation/mk-viii/outputs/arinc429/egpws-alert-discrete-1");
me.pullUp = me.hasBit(me.discrete1, 4096);
},
hasBit: func(word, bit) {
return math.mod(int(word / bit), 2);
},
};
</syntaxhighlight>

;Properties:
* <code>/instrumentation/mk-viii/outputs/arinc429/egpws-alert-discrete-1</code>
* <code>/instrumentation/mk-viii/outputs/arinc429/egpws-alert-discrete-2</code>
* <code>/instrumentation/mk-viii/outputs/arinc429/egpwc-alert-discrete-3</code>
* <code>/instrumentation/mk-viii/outputs/arinc429/egpwc-logic-discretes</code>
* <code>/instrumentation/mk-viii/outputs/arinc429/mode6-callouts-discrete-1</code>
* <code>/instrumentation/mk-viii/outputs/arinc429/mode6-callouts-discrete-2</code>
 

;Warning Bit Matrix:
;egpws-alert-discrete-1
{|class="wikitable"
! Alert !! Bit
|-
| Sink Rate || 2048
|-
| Pull Up || 4096
|-
| Terrain || 8192
|-
| Don't Sink || 16384
|-
| Too Low Gear || 32768
|-
| Too Low Flaps || 65536
|-
| Too Low Terrain || 131072
|-
| Glideslope || 262144
|-
| Minimums || 524288
|}

;egpws-alert-discrete-2
{|class="wikitable"
! Alert !! Bit
|-
| Glideslope Cancel || 2048
|-
| GPWS Alert Lamp || 4096
|-
| GPWS Warning Lamp || 8192
|-
| GPWS Inop || 16384
|-
| Audio Active || 65536
|-
| TAD Inop || 16777216
|-
| Fault Present || 33554432
|-
| Terrain NA || 134217728
|}

;egpwc-alert-discrete-3
{|class="wikitable"
! Alert !! Bit
|-
| Modes 1-4 Inop || 2048
|-
| Mode 5 Inop || 4096
|-
| Mode 6 Inop || 8192
|-
| Bank Angle Inop || 16384
|-
| TAD Inop || 65536
|-
| Always set || 131072
|-
| Always set || 262144
|}

;egpwc-logic-discretes
{|class="wikitable"
! Alert !! Bit
|-
| TCF Too Low Terrain || 8192
|-
| Takeoff Mode || 262144
|-
| Mode 1 Sink Rate || 524288
|-
| Mode 1 Pull Up || 1048576
|-
| Mode 2 Terrain || 2097152
|-
| Mode 2 Warning || 4194304
|-
| Mode 3 Don't Sink || 8388608
|-
| Mode 4 Too Low Gear/Flaps/Terrain || 16777216
|-
| Mode 5 Glideslope || 33554432
|}

;mode6-callouts-discrete-1
{|class="wikitable"
! Alert !! Bit
|-
| Minimums || 2048
|-
| 10 || 65536
|-
| 20 || 131072
|-
| 30 || 262144
|-
| 40 || 524288
|-
| 50 || 1048576
|-
| 100 || 8388608
|-
| 200 || 16777216
|-
| 300 || 33554432
|}

;mode6-callouts-discrete-2
{|class="wikitable"
! Alert !! Bit
|-
| 400 || 2048
|-
| 500 || 4096
|-
| 1000 || 8192
|-
| 2500 || 16384
|-
| Bank Angle || 262144
|-
| 500 Above|| 524288
|}

== Module Status ==
The original MK VIII supports an RS232 interface to read the module status. Since FlightGear does not support RS232 interfaces, all data is printed to the standard output. Trigger <tt>/instrumentation/mk-viii/inputs/discretes/rs-232/present-status</tt> to print the current module configuration and status:

EGPWC CONFIGURATION
PART NUMBER: 965-1220-000
MOD STATUS: N/A
SERIAL NUMBER: N/A

APPLICATION S/W VERSION: 2.0.0
TERRAIN DATABASE VERSION: 2.0.0
ENVELOPE MOD DATABASE VERSION: N/A
BOOT CODE VERSION: 2.0.0

CURRENT FAULTS
NO FAULTS

CONFIGURATION:
AIRCRAFT TYPE = 0
AIR DATA TYPE = 1
POSITION INPUT TYPE = 2
CALLOUTS OPTION TYPE = 13
AUDIO MENU TYPE = 0
TERRAIN DISPLAY TYPE = 1
OPTIONS 1 TYPE = 124
RADIO ALTITUDE TYPE = 2
NAVIGATION INPUT TYPE = 3
ATTITUDE TYPE = 6
MAGNETIC HEADING TYPE = 2
WINDSHEAR INPUT TYPE = 0
IO DISCRETE TYPE = 7
VOLUME SELECT = 0

= External Links =
* Documentation by the original module developer [http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg01902.html 1] [http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg01902/mk-viii-manual.tgz 2]
* Original manufacturer documentation
** [http://www.egpws.com/engineering_support/documents/install/060-4314-150.pdf Honeywell Inc., "MK VI, MK VIII, Enhanced Ground Proximity Warning System (Class A TAWS), Installation Design Guide", July 2003]
** [http://www51.honeywell.com/sites/aero/common/documents/Mk_VI_VIII_EGPWS.pdf Honeywell Inc., "MK VI and MK VIII Enhanced Ground Proximity Warning System Pilot's Guide", February 2002]

[[Category:Aircraft enhancement]]

Building using CMake - Windows

2026-06-25T08:38:54Z

Octal450: Finished updating it for VS2026

This article is intended to give an overview of '''building FlightGear on modern Windows systems'''. It was created using Windows 11 and VS 2022. It ought to be transferable to earlier versions of the Windows OS and software.

As FlightGear is now 64-bit only, the guide only describes building on a 64-bit system.

== Required software ==
* [https://cmake.org/download/ CMake for Windows]. Download and install the Windows Win64-x64 Installer.
* [https://visualstudio.microsoft.com/downloads/ Microsoft Visual Studio 2026] (for MSVC). The Community version is free. There is no need for the premium versions; none of their features are required to build FlightGear. The C++ compiler will not be installed by default. You either choose this component during installation or after installation by starting MSVC and trying to create a new C++ project. The one to download is "Desktop Development with C++". Make sure to have the latest version of the Windows SDK for your Windows version and the C++ Compiler checked. As of 6/25/2026, the option to select is "MSVC Built Tools for X64/X86 (Latest)".
* [https://www.qt.io/download-open-source/ Qt6] for the [[FlightGear Qt launcher|Integrated Qt Launcher]]. Download the online installer to install and choose the latest version of Qt. Leave the default Developer and Designer Tools selection - these are needed for coding and compiling. Otherwise, here is [https://www.qt.io/offline-installers Offline Qt Downloads] for the optional offline-installer versions of Qt. Make sure you select MSVC in the Qt version to be installed, but note that as of 6/25/2026 it is still marked for VS2022, but will work with VS2026.
* [https://git-scm.com/download/win Git] to keep your build up to date. It also simplifies downloads of components. Optional, but can't recommend it enough!

== Obtaining source ==
{{Main article|FlightGear and Git}}
Throughout this article it is assumed that you have set up git clones of the various source repositories (FlightGear, SimGear, data...).
Using an organized directory (see below) will help significantly.

The commands to run are:

{{#tag:syntaxhighlight|
{{repo link
| site = gitlab
| cmd = git clone
| proj = flightgear
| repo = simgear
| type = git
| full = 1
}} simgear
{{repo link
| site = gitlab
| cmd = git clone
| proj = flightgear
| repo = flightgear
| type = git
| full = 1
}} flightgear
{{repo link
| site = gitlab
| cmd = git clone
| proj = flightgear
| repo = fgdata
| type = git
| full = 1
}} fgdata
{{repo link
| site = gitlab
| cmd = git clone
| proj = flightgear
| repo = windows-3rd-party
| type = git
| full = 1
}} windows-3rd-party
{{repo link
| site = gitlab
| cmd = git clone
| proj = flightgear
| repo = openscenegraph
| type = git
| full = 1
}} osg
| lang = "sh"
}}

After downloading these, I would suggest assembling a folder structure as below:

== Directory Tree ==
On Windows, assumptions on the directory structure are made to automate the discovery of dependencies. This recommended directory structure is described below. The components can be downloaded from the links above. If you do not use the recommended structure you will need to enter paths by hand and some parts may not input correctly.

Caveat -- spaces in the directory names will cause errors. It is best to make sure there are no spaces in the path anywhere.

<tt>
: FlightGearBuild / </tt> (Main root directory) <tt>
:: fgdata / </tt> (FlightGear data files) <tt>
:: flightgear / </tt> (FlightGear sources) <tt>
:: install / </tt> (Directory where you will install the built binaries to) <tt>
::: launch.bat / </tt> (launch script if desired, see below) <tt>
:: osg / </tt> (OSG sources) <tt>
:: simgear / </tt> (SimGear sources) <tt>
:: windows-3rd-party /
:: build.bat / </tt> (build script, see below) <tt>
:: update.bat / </tt> (update script, see below)

== Building ==
=== Scripted Compilation ===
This script will allow you to build OpenSceneGraph, SimGear and FlightGear automatically.

If you would like debug info, change Release to RelWithDebInfo in the --config commands.

{{collapsible script
| type = Windows batch file
| title = The <code>build.bat</code> script for configuring and compiling OSG, SG, and FG
| lang = batch
| script =
SET PATH=%PATH%;%ProgramFiles%\CMake\bin
SET QT6SDK64=C:\Qt\6.x\msvc2022_64
SET CMAKE_TOOLCHAIN="Visual Studio 18 2026"
SET ROOT_DIR=C:\path\to\FlightGearBuild

md osg-build
md simgear-build
md flightgear-build

cd %ROOT_DIR%\osg-build

cmake %ROOT_DIR%\osg -G %CMAKE_TOOLCHAIN% -A x64 ^
-DACTUAL_3RDPARTY_DIR=%ROOT_DIR%\windows-3rd-party/msvc140/3rdParty.x64 ^
-DCMAKE_RELWITHDEBINFO_POSTFIX:STRING= ^
-DOSG_USE_UTF8_FILENAME:BOOL=ON ^
-DWIN32_USE_MP:BOOL=ON ^
-DCMAKE_INSTALL_PREFIX:PATH=%ROOT_DIR%\install
cmake --build . --config Release --target INSTALL

cd %ROOT_DIR%\simgear-build
cmake %ROOT_DIR%\simgear -G %CMAKE_TOOLCHAIN% -A x64 ^
-DOSG_FSTREAM_EXPORT_FIXED:BOOL=ON ^
-DCMAKE_INSTALL_PREFIX:PATH=%ROOT_DIR%\install
cmake --build . --config Release --target INSTALL

cd %ROOT_DIR%\flightgear-build
cmake %ROOT_DIR%\flightgear -G %CMAKE_TOOLCHAIN% -A x64 ^
-DCMAKE_INSTALL_PREFIX:PATH=%ROOT_DIR%\install ^
-DCMAKE_PREFIX_PATH=%QT6SDK64% ^
-DFG_BUILD_TYPE:STRING=Release ^
-DOSG_FSTREAM_EXPORT_FIXED:BOOL=ON

cmake --build . --config Release --target INSTALL

pause
| show = 1
}}

{{tip | 10/2024: When using VS2022 or newer make sure your osg has this fix applied: https://gitlab.com/flightgear/openscenegraph/-/commit/31082758036c12738467a7210a17604275a79517<ref>https://sourceforge.net/p/flightgear/mailman/message/58821522/</ref>

Some folks encountered the following problem when building flightgear:
<syntaxhighlight>
CMake Error at CMakeLists.txt:283 (find_package):
By not providing "FindBoost.cmake" in CMAKE_MODULE_PATH this project has
asked CMake to find a package configuration file provided by "Boost", but
CMake did not find one.

Could not find a package configuration file provided by "Boost" with any of
the following names:

BoostConfig.cmake
boost-config.cmake

Add the installation prefix of "Boost" to CMAKE_PREFIX_PATH or set
"Boost_DIR" to a directory containing one of the above files. If "Boost"
provides a separate development package or SDK, be sure it has been
installed.
</syntaxhighlight>
This could be solved by doing the following in the top-level <code>CMakeLists.txt</code> of [https://sourceforge.net/p/flightgear/simgear/ci/next/tree/CMakeLists.txt#l16 simgear] and [https://sourceforge.net/p/flightgear/flightgear/ci/next/tree/CMakeLists.txt#l26 flightgear]:

In each file search for the line
<syntaxhighlight lang='CMake'>
cmake_policy(SET CMP0167 NEW)
</syntaxhighlight>
(it should be near the top of each file) and change from <code>NEW</code> to <code>OLD</code> like this<ref>https://sourceforge.net/p/flightgear/mailman/message/58815368/</ref>:
<syntaxhighlight lang='CMake'>
cmake_policy(SET CMP0167 OLD)
</syntaxhighlight>

In addition there are reports that a linking error occurs when building flightgear:
<syntaxhighlight>
pui.lib(puValue.obj) : error LNK2019: unresolved external symbol __imp_strncat referenced in function "protected: void__cdecl puValue::copy_stringval(char const *)" (?copy_stringval@puValue@@IEAAXPEBD@Z) [F:\git\flightgear-build\src\Main\fgfs.vcxproj]
F:\git\flightgear-build\src\Main\RelWithDebInfo\fgfs.exe : fatal error LNK1120: 1 unresolved externals [F:\git\flightgear-build\src\Main\fgfs.vcxproj]
</syntaxhighlight>
A workaround could be by changing the build type from <code>RelWithDebInfo</code> to <code>Release</code> when building osg, simgear and flightgear<ref>https://sourceforge.net/p/flightgear/mailman/message/58824438/</ref>:

In the <code>build.bat</code> change all three occurrences of
<syntaxhighlight lang='batch'>
cmake --build . --config RelWithDebInfo --target INSTALL
</syntaxhighlight>
to
<syntaxhighlight lang='batch'>
cmake --build . --config Release --target INSTALL
</syntaxhighlight>
}}

Before starting to use the script, you need to edit the top few lines of the script. You will have to:

# Set the path to your CMake installation.
# Ensure that the path to your QT SDK is correct for your version of MSVC.
# Ensure your toolchain version matches, e.g. "Visual Studio 16 2019" for MSVC 2019 or "Visual Studio 17 2022" for MSVC 2022.
# Set ROOT_DIR to the FlightGearBuild folder you created (the above directory structure)

==== Post-compilation: Launching FlightGear ====
'''In the debugger:'''
Open flightgear-build/FlightGear.sln. You can then perform all your development / debugging directly in VS. You normally only need to run build.bat again, if you update SimGear or OSG.

To launch FlightGear from Visual Studio, you can follow the following steps:
The first time only:
# Make sure you set your build type to RelWithDebInfo in the top bar.
# To start with the launcher, click on the small black arrow beside Local Windows Debugger to open 'fgfs debug properties'. Switch to debugging; add {{code|--launcher}} to the 'Command Arguments'. Click Apply and then OK.
# Press the green arrow (Local Windows Debugger) to start up FlightGear.
# The first time you'll have to choose where FGDATA is -- to do this, select the 'fgdata' directory you cloned at the start.

Thereafter, simply press the green arrow directly each time you want to start. If there are any local changes, it will recompile; alternatively it will start up directly. It will take a little longer to start as it loads symbols; however you also have the benefit that any segfaults will be caught allowing you to report them!

'''As a standard .exe:'''
NB these instructions overall are intended for setting up for development; there's a slightly more convoluted process for setting up for just plain flying (e.g. taking advantage of new features for aircraft development).

Essentially, Visual Studio doesn't copy in the DLLs into the /bin/ folder. It's also not ideal to manually copy in the DLLs as it can cause all sorts of issues. However, without the DLLs FlightGear won't work; therefore, you need to set the PATH so it knows where to look for them.
This launch script should work, put into your /install/bin/ folder:
{{collapsible script
| type = Windows batch file
| title = The <code>launch.bat</code> script for launching flightgear
| lang = batch
| script =
SET PATH=C:\path\to\FlightGearBuild\install\bin;C:\path\to\FlightGearBuild\windows-3rd-party\msvc140\3rdParty.x64\bin;C:\Qt\5.15.2\msvc2019_64\bin;%PATH%
SET FG_ROOT=C:\path\to\FlightGearBuild\fgdata
fgfs.exe --launcher
| show = 1
}}

Adjust the "path\to" references to suit your own personal installation, as well as the QT5 path.

=== Updating ===
To update FlightGear, in general, just run ''git pull'' on the source directories and then re-run the build.bat script -- it will update what it needs to, relatively quickly.

{{collapsible script
| type = Windows batch file
| title = The <code>update.bat</code> script for updating repositories
| lang = batch
| script =
SET ROOT_DIR=C:\path\to\FlightGearBuild

cd %ROOT_DIR%\osg
git pull

cd %ROOT_DIR%\fgdata
git pull

cd %ROOT_DIR%\flightgear
git pull

cd %ROOT_DIR%\simgear
git pull

cd %ROOT_DIR%\windows-3rd-party
git pull

pause
| show = 1
}}

=== Changing the Configuration ===
When the SimGear/FlightGear version numbers change, or you change configuration options (e.g. toggling Compositor, changing OSG versions, changing Qt versions) you do have to re-configure in CMake. To do this, it's usually safest to delete the simgear-build and flightgear-build folders and re-run the build.bat script, to ensure the build is clean. There is no need to delete osg-build unless changing OSG version.

In case of problems, most of the time deleting the simgear-build and flightgear-build folders and re-running the build.bat script will be sufficient.

{{building}}
[[fr:compiler flightear avec CMake - Windows]]
[[Category:Windows specific]]
[[Category:Hackathon Materials]]

Building using CMake - Windows

2026-06-25T08:38:30Z

Octal450: /* Required software */

This article is intended to give an overview of '''building FlightGear on modern Windows systems'''. It was created using Windows 11 and VS 2022. It ought to be transferable to earlier versions of the Windows OS and software.

As FlightGear is now 64-bit only, the guide only describes building on a 64-bit system.

== Required software ==
* [https://cmake.org/download/ CMake for Windows]. Download and install the Windows Win64-x64 Installer.
* [https://visualstudio.microsoft.com/downloads/ Microsoft Visual Studio 2026] (for MSVC). The Community version is free. There is no need for the premium versions; none of their features are required to build FlightGear. The C++ compiler will not be installed by default. You either choose this component during installation or after installation by starting MSVC and trying to create a new C++ project. The one to download is "Desktop Development with C++". Make sure to have the latest version of the Windows SDK for your Windows version and the C++ Compiler checked. As of 6/25/2026, the option to select is "MSVC Built Tools for X64/X86 (Latest)".
* [https://www.qt.io/download-open-source/ Qt6] for the [[FlightGear Qt launcher|Integrated Qt Launcher]]. Download the online installer to install and choose the latest version of Qt. Leave the default Developer and Designer Tools selection - these are needed for coding and compiling. Otherwise, here is [https://www.qt.io/offline-installers Offline Qt Downloads] for the optional offline-installer versions of Qt. Make sure you select MSVC in the Qt version to be installed, but note that as of 6/25/2026 it is still marked for VS2022, but will work with 2026.
* [https://git-scm.com/download/win Git] to keep your build up to date. It also simplifies downloads of components. Optional, but can't recommend it enough!

== Obtaining source ==
{{Main article|FlightGear and Git}}
Throughout this article it is assumed that you have set up git clones of the various source repositories (FlightGear, SimGear, data...).
Using an organized directory (see below) will help significantly.

The commands to run are:

{{#tag:syntaxhighlight|
{{repo link
| site = gitlab
| cmd = git clone
| proj = flightgear
| repo = simgear
| type = git
| full = 1
}} simgear
{{repo link
| site = gitlab
| cmd = git clone
| proj = flightgear
| repo = flightgear
| type = git
| full = 1
}} flightgear
{{repo link
| site = gitlab
| cmd = git clone
| proj = flightgear
| repo = fgdata
| type = git
| full = 1
}} fgdata
{{repo link
| site = gitlab
| cmd = git clone
| proj = flightgear
| repo = windows-3rd-party
| type = git
| full = 1
}} windows-3rd-party
{{repo link
| site = gitlab
| cmd = git clone
| proj = flightgear
| repo = openscenegraph
| type = git
| full = 1
}} osg
| lang = "sh"
}}

After downloading these, I would suggest assembling a folder structure as below:

== Directory Tree ==
On Windows, assumptions on the directory structure are made to automate the discovery of dependencies. This recommended directory structure is described below. The components can be downloaded from the links above. If you do not use the recommended structure you will need to enter paths by hand and some parts may not input correctly.

Caveat -- spaces in the directory names will cause errors. It is best to make sure there are no spaces in the path anywhere.

<tt>
: FlightGearBuild / </tt> (Main root directory) <tt>
:: fgdata / </tt> (FlightGear data files) <tt>
:: flightgear / </tt> (FlightGear sources) <tt>
:: install / </tt> (Directory where you will install the built binaries to) <tt>
::: launch.bat / </tt> (launch script if desired, see below) <tt>
:: osg / </tt> (OSG sources) <tt>
:: simgear / </tt> (SimGear sources) <tt>
:: windows-3rd-party /
:: build.bat / </tt> (build script, see below) <tt>
:: update.bat / </tt> (update script, see below)

== Building ==
=== Scripted Compilation ===
This script will allow you to build OpenSceneGraph, SimGear and FlightGear automatically.

If you would like debug info, change Release to RelWithDebInfo in the --config commands.

{{collapsible script
| type = Windows batch file
| title = The <code>build.bat</code> script for configuring and compiling OSG, SG, and FG
| lang = batch
| script =
SET PATH=%PATH%;%ProgramFiles%\CMake\bin
SET QT6SDK64=C:\Qt\6.x\msvc2022_64
SET CMAKE_TOOLCHAIN="Visual Studio 18 2026"
SET ROOT_DIR=C:\path\to\FlightGearBuild

md osg-build
md simgear-build
md flightgear-build

cd %ROOT_DIR%\osg-build

cmake %ROOT_DIR%\osg -G %CMAKE_TOOLCHAIN% -A x64 ^
-DACTUAL_3RDPARTY_DIR=%ROOT_DIR%\windows-3rd-party/msvc140/3rdParty.x64 ^
-DCMAKE_RELWITHDEBINFO_POSTFIX:STRING= ^
-DOSG_USE_UTF8_FILENAME:BOOL=ON ^
-DWIN32_USE_MP:BOOL=ON ^
-DCMAKE_INSTALL_PREFIX:PATH=%ROOT_DIR%\install
cmake --build . --config Release --target INSTALL

cd %ROOT_DIR%\simgear-build
cmake %ROOT_DIR%\simgear -G %CMAKE_TOOLCHAIN% -A x64 ^
-DOSG_FSTREAM_EXPORT_FIXED:BOOL=ON ^
-DCMAKE_INSTALL_PREFIX:PATH=%ROOT_DIR%\install
cmake --build . --config Release --target INSTALL

cd %ROOT_DIR%\flightgear-build
cmake %ROOT_DIR%\flightgear -G %CMAKE_TOOLCHAIN% -A x64 ^
-DCMAKE_INSTALL_PREFIX:PATH=%ROOT_DIR%\install ^
-DCMAKE_PREFIX_PATH=%QT6SDK64% ^
-DFG_BUILD_TYPE:STRING=Release ^
-DOSG_FSTREAM_EXPORT_FIXED:BOOL=ON

cmake --build . --config Release --target INSTALL

pause
| show = 1
}}

{{tip | 10/2024: When using VS2022 or newer make sure your osg has this fix applied: https://gitlab.com/flightgear/openscenegraph/-/commit/31082758036c12738467a7210a17604275a79517<ref>https://sourceforge.net/p/flightgear/mailman/message/58821522/</ref>

Some folks encountered the following problem when building flightgear:
<syntaxhighlight>
CMake Error at CMakeLists.txt:283 (find_package):
By not providing "FindBoost.cmake" in CMAKE_MODULE_PATH this project has
asked CMake to find a package configuration file provided by "Boost", but
CMake did not find one.

Could not find a package configuration file provided by "Boost" with any of
the following names:

BoostConfig.cmake
boost-config.cmake

Add the installation prefix of "Boost" to CMAKE_PREFIX_PATH or set
"Boost_DIR" to a directory containing one of the above files. If "Boost"
provides a separate development package or SDK, be sure it has been
installed.
</syntaxhighlight>
This could be solved by doing the following in the top-level <code>CMakeLists.txt</code> of [https://sourceforge.net/p/flightgear/simgear/ci/next/tree/CMakeLists.txt#l16 simgear] and [https://sourceforge.net/p/flightgear/flightgear/ci/next/tree/CMakeLists.txt#l26 flightgear]:

In each file search for the line
<syntaxhighlight lang='CMake'>
cmake_policy(SET CMP0167 NEW)
</syntaxhighlight>
(it should be near the top of each file) and change from <code>NEW</code> to <code>OLD</code> like this<ref>https://sourceforge.net/p/flightgear/mailman/message/58815368/</ref>:
<syntaxhighlight lang='CMake'>
cmake_policy(SET CMP0167 OLD)
</syntaxhighlight>

In addition there are reports that a linking error occurs when building flightgear:
<syntaxhighlight>
pui.lib(puValue.obj) : error LNK2019: unresolved external symbol __imp_strncat referenced in function "protected: void__cdecl puValue::copy_stringval(char const *)" (?copy_stringval@puValue@@IEAAXPEBD@Z) [F:\git\flightgear-build\src\Main\fgfs.vcxproj]
F:\git\flightgear-build\src\Main\RelWithDebInfo\fgfs.exe : fatal error LNK1120: 1 unresolved externals [F:\git\flightgear-build\src\Main\fgfs.vcxproj]
</syntaxhighlight>
A workaround could be by changing the build type from <code>RelWithDebInfo</code> to <code>Release</code> when building osg, simgear and flightgear<ref>https://sourceforge.net/p/flightgear/mailman/message/58824438/</ref>:

In the <code>build.bat</code> change all three occurrences of
<syntaxhighlight lang='batch'>
cmake --build . --config RelWithDebInfo --target INSTALL
</syntaxhighlight>
to
<syntaxhighlight lang='batch'>
cmake --build . --config Release --target INSTALL
</syntaxhighlight>
}}

Before starting to use the script, you need to edit the top few lines of the script. You will have to:

# Set the path to your CMake installation.
# Ensure that the path to your QT SDK is correct for your version of MSVC.
# Ensure your toolchain version matches, e.g. "Visual Studio 16 2019" for MSVC 2019 or "Visual Studio 17 2022" for MSVC 2022.
# Set ROOT_DIR to the FlightGearBuild folder you created (the above directory structure)

==== Post-compilation: Launching FlightGear ====
'''In the debugger:'''
Open flightgear-build/FlightGear.sln. You can then perform all your development / debugging directly in VS. You normally only need to run build.bat again, if you update SimGear or OSG.

To launch FlightGear from Visual Studio, you can follow the following steps:
The first time only:
# Make sure you set your build type to RelWithDebInfo in the top bar.
# To start with the launcher, click on the small black arrow beside Local Windows Debugger to open 'fgfs debug properties'. Switch to debugging; add {{code|--launcher}} to the 'Command Arguments'. Click Apply and then OK.
# Press the green arrow (Local Windows Debugger) to start up FlightGear.
# The first time you'll have to choose where FGDATA is -- to do this, select the 'fgdata' directory you cloned at the start.

Thereafter, simply press the green arrow directly each time you want to start. If there are any local changes, it will recompile; alternatively it will start up directly. It will take a little longer to start as it loads symbols; however you also have the benefit that any segfaults will be caught allowing you to report them!

'''As a standard .exe:'''
NB these instructions overall are intended for setting up for development; there's a slightly more convoluted process for setting up for just plain flying (e.g. taking advantage of new features for aircraft development).

Essentially, Visual Studio doesn't copy in the DLLs into the /bin/ folder. It's also not ideal to manually copy in the DLLs as it can cause all sorts of issues. However, without the DLLs FlightGear won't work; therefore, you need to set the PATH so it knows where to look for them.
This launch script should work, put into your /install/bin/ folder:
{{collapsible script
| type = Windows batch file
| title = The <code>launch.bat</code> script for launching flightgear
| lang = batch
| script =
SET PATH=C:\path\to\FlightGearBuild\install\bin;C:\path\to\FlightGearBuild\windows-3rd-party\msvc140\3rdParty.x64\bin;C:\Qt\5.15.2\msvc2019_64\bin;%PATH%
SET FG_ROOT=C:\path\to\FlightGearBuild\fgdata
fgfs.exe --launcher
| show = 1
}}

Adjust the "path\to" references to suit your own personal installation, as well as the QT5 path.

=== Updating ===
To update FlightGear, in general, just run ''git pull'' on the source directories and then re-run the build.bat script -- it will update what it needs to, relatively quickly.

{{collapsible script
| type = Windows batch file
| title = The <code>update.bat</code> script for updating repositories
| lang = batch
| script =
SET ROOT_DIR=C:\path\to\FlightGearBuild

cd %ROOT_DIR%\osg
git pull

cd %ROOT_DIR%\fgdata
git pull

cd %ROOT_DIR%\flightgear
git pull

cd %ROOT_DIR%\simgear
git pull

cd %ROOT_DIR%\windows-3rd-party
git pull

pause
| show = 1
}}

=== Changing the Configuration ===
When the SimGear/FlightGear version numbers change, or you change configuration options (e.g. toggling Compositor, changing OSG versions, changing Qt versions) you do have to re-configure in CMake. To do this, it's usually safest to delete the simgear-build and flightgear-build folders and re-run the build.bat script, to ensure the build is clean. There is no need to delete osg-build unless changing OSG version.

In case of problems, most of the time deleting the simgear-build and flightgear-build folders and re-running the build.bat script will be sufficient.

{{building}}
[[fr:compiler flightear avec CMake - Windows]]
[[Category:Windows specific]]
[[Category:Hackathon Materials]]

Building using CMake - Windows

2026-06-25T08:37:53Z

Octal450: /* Required software */

This article is intended to give an overview of '''building FlightGear on modern Windows systems'''. It was created using Windows 11 and VS 2022. It ought to be transferable to earlier versions of the Windows OS and software.

As FlightGear is now 64-bit only, the guide only describes building on a 64-bit system.

== Required software ==
* [https://cmake.org/download/ CMake for Windows]. Download and install the Windows Win64-x64 Installer.
* [https://visualstudio.microsoft.com/downloads/ Microsoft Visual Studio 2026] (for MSVC). The Community version is free. There is no need for the premium versions; none of their features are required to build FlightGear. The C++ compiler will not be installed by default. You either choose this component during installation or after installation by starting MSVC and trying to create a new C++ project. The one to download is "Desktop Development with C++". Make sure to have the latest version of the Windows SDK for your Windows version and the C++ Compiler checked. As of 6/25/2026, the option to select is "MSVC Built Tools for X64/X86 (Latest)".
* [https://www.qt.io/download-open-source/ Qt6] for the [[FlightGear Qt launcher|Integrated Qt Launcher]]. Download the online installer to install and choose the latest version of Qt. Leave the default Developer and Designer Tools selection - these are needed for coding and compiling. Otherwise, here is [https://www.qt.io/offline-installers Offline Qt Downloads] for the optional offline-installer versions of Qt. Make sure you select MSVC, but note that as of 6/25/2026 it is still marked for VS2022, but will work with 2026.
* [https://git-scm.com/download/win Git] to keep your build up to date. It also simplifies downloads of components. Optional, but can't recommend it enough!

== Obtaining source ==
{{Main article|FlightGear and Git}}
Throughout this article it is assumed that you have set up git clones of the various source repositories (FlightGear, SimGear, data...).
Using an organized directory (see below) will help significantly.

The commands to run are:

{{#tag:syntaxhighlight|
{{repo link
| site = gitlab
| cmd = git clone
| proj = flightgear
| repo = simgear
| type = git
| full = 1
}} simgear
{{repo link
| site = gitlab
| cmd = git clone
| proj = flightgear
| repo = flightgear
| type = git
| full = 1
}} flightgear
{{repo link
| site = gitlab
| cmd = git clone
| proj = flightgear
| repo = fgdata
| type = git
| full = 1
}} fgdata
{{repo link
| site = gitlab
| cmd = git clone
| proj = flightgear
| repo = windows-3rd-party
| type = git
| full = 1
}} windows-3rd-party
{{repo link
| site = gitlab
| cmd = git clone
| proj = flightgear
| repo = openscenegraph
| type = git
| full = 1
}} osg
| lang = "sh"
}}

After downloading these, I would suggest assembling a folder structure as below:

== Directory Tree ==
On Windows, assumptions on the directory structure are made to automate the discovery of dependencies. This recommended directory structure is described below. The components can be downloaded from the links above. If you do not use the recommended structure you will need to enter paths by hand and some parts may not input correctly.

Caveat -- spaces in the directory names will cause errors. It is best to make sure there are no spaces in the path anywhere.

<tt>
: FlightGearBuild / </tt> (Main root directory) <tt>
:: fgdata / </tt> (FlightGear data files) <tt>
:: flightgear / </tt> (FlightGear sources) <tt>
:: install / </tt> (Directory where you will install the built binaries to) <tt>
::: launch.bat / </tt> (launch script if desired, see below) <tt>
:: osg / </tt> (OSG sources) <tt>
:: simgear / </tt> (SimGear sources) <tt>
:: windows-3rd-party /
:: build.bat / </tt> (build script, see below) <tt>
:: update.bat / </tt> (update script, see below)

== Building ==
=== Scripted Compilation ===
This script will allow you to build OpenSceneGraph, SimGear and FlightGear automatically.

If you would like debug info, change Release to RelWithDebInfo in the --config commands.

{{collapsible script
| type = Windows batch file
| title = The <code>build.bat</code> script for configuring and compiling OSG, SG, and FG
| lang = batch
| script =
SET PATH=%PATH%;%ProgramFiles%\CMake\bin
SET QT6SDK64=C:\Qt\6.x\msvc2022_64
SET CMAKE_TOOLCHAIN="Visual Studio 18 2026"
SET ROOT_DIR=C:\path\to\FlightGearBuild

md osg-build
md simgear-build
md flightgear-build

cd %ROOT_DIR%\osg-build

cmake %ROOT_DIR%\osg -G %CMAKE_TOOLCHAIN% -A x64 ^
-DACTUAL_3RDPARTY_DIR=%ROOT_DIR%\windows-3rd-party/msvc140/3rdParty.x64 ^
-DCMAKE_RELWITHDEBINFO_POSTFIX:STRING= ^
-DOSG_USE_UTF8_FILENAME:BOOL=ON ^
-DWIN32_USE_MP:BOOL=ON ^
-DCMAKE_INSTALL_PREFIX:PATH=%ROOT_DIR%\install
cmake --build . --config Release --target INSTALL

cd %ROOT_DIR%\simgear-build
cmake %ROOT_DIR%\simgear -G %CMAKE_TOOLCHAIN% -A x64 ^
-DOSG_FSTREAM_EXPORT_FIXED:BOOL=ON ^
-DCMAKE_INSTALL_PREFIX:PATH=%ROOT_DIR%\install
cmake --build . --config Release --target INSTALL

cd %ROOT_DIR%\flightgear-build
cmake %ROOT_DIR%\flightgear -G %CMAKE_TOOLCHAIN% -A x64 ^
-DCMAKE_INSTALL_PREFIX:PATH=%ROOT_DIR%\install ^
-DCMAKE_PREFIX_PATH=%QT6SDK64% ^
-DFG_BUILD_TYPE:STRING=Release ^
-DOSG_FSTREAM_EXPORT_FIXED:BOOL=ON

cmake --build . --config Release --target INSTALL

pause
| show = 1
}}

{{tip | 10/2024: When using VS2022 or newer make sure your osg has this fix applied: https://gitlab.com/flightgear/openscenegraph/-/commit/31082758036c12738467a7210a17604275a79517<ref>https://sourceforge.net/p/flightgear/mailman/message/58821522/</ref>

Some folks encountered the following problem when building flightgear:
<syntaxhighlight>
CMake Error at CMakeLists.txt:283 (find_package):
By not providing "FindBoost.cmake" in CMAKE_MODULE_PATH this project has
asked CMake to find a package configuration file provided by "Boost", but
CMake did not find one.

Could not find a package configuration file provided by "Boost" with any of
the following names:

BoostConfig.cmake
boost-config.cmake

Add the installation prefix of "Boost" to CMAKE_PREFIX_PATH or set
"Boost_DIR" to a directory containing one of the above files. If "Boost"
provides a separate development package or SDK, be sure it has been
installed.
</syntaxhighlight>
This could be solved by doing the following in the top-level <code>CMakeLists.txt</code> of [https://sourceforge.net/p/flightgear/simgear/ci/next/tree/CMakeLists.txt#l16 simgear] and [https://sourceforge.net/p/flightgear/flightgear/ci/next/tree/CMakeLists.txt#l26 flightgear]:

In each file search for the line
<syntaxhighlight lang='CMake'>
cmake_policy(SET CMP0167 NEW)
</syntaxhighlight>
(it should be near the top of each file) and change from <code>NEW</code> to <code>OLD</code> like this<ref>https://sourceforge.net/p/flightgear/mailman/message/58815368/</ref>:
<syntaxhighlight lang='CMake'>
cmake_policy(SET CMP0167 OLD)
</syntaxhighlight>

In addition there are reports that a linking error occurs when building flightgear:
<syntaxhighlight>
pui.lib(puValue.obj) : error LNK2019: unresolved external symbol __imp_strncat referenced in function "protected: void__cdecl puValue::copy_stringval(char const *)" (?copy_stringval@puValue@@IEAAXPEBD@Z) [F:\git\flightgear-build\src\Main\fgfs.vcxproj]
F:\git\flightgear-build\src\Main\RelWithDebInfo\fgfs.exe : fatal error LNK1120: 1 unresolved externals [F:\git\flightgear-build\src\Main\fgfs.vcxproj]
</syntaxhighlight>
A workaround could be by changing the build type from <code>RelWithDebInfo</code> to <code>Release</code> when building osg, simgear and flightgear<ref>https://sourceforge.net/p/flightgear/mailman/message/58824438/</ref>:

In the <code>build.bat</code> change all three occurrences of
<syntaxhighlight lang='batch'>
cmake --build . --config RelWithDebInfo --target INSTALL
</syntaxhighlight>
to
<syntaxhighlight lang='batch'>
cmake --build . --config Release --target INSTALL
</syntaxhighlight>
}}

Before starting to use the script, you need to edit the top few lines of the script. You will have to:

# Set the path to your CMake installation.
# Ensure that the path to your QT SDK is correct for your version of MSVC.
# Ensure your toolchain version matches, e.g. "Visual Studio 16 2019" for MSVC 2019 or "Visual Studio 17 2022" for MSVC 2022.
# Set ROOT_DIR to the FlightGearBuild folder you created (the above directory structure)

==== Post-compilation: Launching FlightGear ====
'''In the debugger:'''
Open flightgear-build/FlightGear.sln. You can then perform all your development / debugging directly in VS. You normally only need to run build.bat again, if you update SimGear or OSG.

To launch FlightGear from Visual Studio, you can follow the following steps:
The first time only:
# Make sure you set your build type to RelWithDebInfo in the top bar.
# To start with the launcher, click on the small black arrow beside Local Windows Debugger to open 'fgfs debug properties'. Switch to debugging; add {{code|--launcher}} to the 'Command Arguments'. Click Apply and then OK.
# Press the green arrow (Local Windows Debugger) to start up FlightGear.
# The first time you'll have to choose where FGDATA is -- to do this, select the 'fgdata' directory you cloned at the start.

Thereafter, simply press the green arrow directly each time you want to start. If there are any local changes, it will recompile; alternatively it will start up directly. It will take a little longer to start as it loads symbols; however you also have the benefit that any segfaults will be caught allowing you to report them!

'''As a standard .exe:'''
NB these instructions overall are intended for setting up for development; there's a slightly more convoluted process for setting up for just plain flying (e.g. taking advantage of new features for aircraft development).

Essentially, Visual Studio doesn't copy in the DLLs into the /bin/ folder. It's also not ideal to manually copy in the DLLs as it can cause all sorts of issues. However, without the DLLs FlightGear won't work; therefore, you need to set the PATH so it knows where to look for them.
This launch script should work, put into your /install/bin/ folder:
{{collapsible script
| type = Windows batch file
| title = The <code>launch.bat</code> script for launching flightgear
| lang = batch
| script =
SET PATH=C:\path\to\FlightGearBuild\install\bin;C:\path\to\FlightGearBuild\windows-3rd-party\msvc140\3rdParty.x64\bin;C:\Qt\5.15.2\msvc2019_64\bin;%PATH%
SET FG_ROOT=C:\path\to\FlightGearBuild\fgdata
fgfs.exe --launcher
| show = 1
}}

Adjust the "path\to" references to suit your own personal installation, as well as the QT5 path.

=== Updating ===
To update FlightGear, in general, just run ''git pull'' on the source directories and then re-run the build.bat script -- it will update what it needs to, relatively quickly.

{{collapsible script
| type = Windows batch file
| title = The <code>update.bat</code> script for updating repositories
| lang = batch
| script =
SET ROOT_DIR=C:\path\to\FlightGearBuild

cd %ROOT_DIR%\osg
git pull

cd %ROOT_DIR%\fgdata
git pull

cd %ROOT_DIR%\flightgear
git pull

cd %ROOT_DIR%\simgear
git pull

cd %ROOT_DIR%\windows-3rd-party
git pull

pause
| show = 1
}}

=== Changing the Configuration ===
When the SimGear/FlightGear version numbers change, or you change configuration options (e.g. toggling Compositor, changing OSG versions, changing Qt versions) you do have to re-configure in CMake. To do this, it's usually safest to delete the simgear-build and flightgear-build folders and re-run the build.bat script, to ensure the build is clean. There is no need to delete osg-build unless changing OSG version.

In case of problems, most of the time deleting the simgear-build and flightgear-build folders and re-running the build.bat script will be sufficient.

{{building}}
[[fr:compiler flightear avec CMake - Windows]]
[[Category:Windows specific]]
[[Category:Hackathon Materials]]

Building using CMake - Windows

2026-06-25T08:37:33Z

Octal450:

This article is intended to give an overview of '''building FlightGear on modern Windows systems'''. It was created using Windows 11 and VS 2022. It ought to be transferable to earlier versions of the Windows OS and software.

As FlightGear is now 64-bit only, the guide only describes building on a 64-bit system.

== Required software ==
* [https://cmake.org/download/ CMake for Windows]. Download and install the Windows Win64-x64 Installer.
* [https://visualstudio.microsoft.com/downloads/ Microsoft Visual Studio 2026] (MSVC). The Community version is free. There is no need for the premium versions; none of their features are required to build FlightGear. The C++ compiler will not be installed by default. You either choose this component during installation or after installation by starting MSVC and trying to create a new C++ project. The one to download is "Desktop Development with C++". Make sure to have the latest version of the Windows SDK for your Windows version and the C++ Compiler checked. As of 6/25/2026, the option to select is "MSVC Built Tools for X64/X86 (Latest)".
* [https://www.qt.io/download-open-source/ Qt6] for the [[FlightGear Qt launcher|Integrated Qt Launcher]]. Download the online installer to install and choose the latest version of Qt. Leave the default Developer and Designer Tools selection - these are needed for coding and compiling. Otherwise, here is [https://www.qt.io/offline-installers Offline Qt Downloads] for the optional offline-installer versions of Qt. Make sure you select MSVC, but note that as of 6/25/2026 it is still marked for VS2022, but will work with 2026.
* [https://git-scm.com/download/win Git] to keep your build up to date. It also simplifies downloads of components. Optional, but can't recommend it enough!

== Obtaining source ==
{{Main article|FlightGear and Git}}
Throughout this article it is assumed that you have set up git clones of the various source repositories (FlightGear, SimGear, data...).
Using an organized directory (see below) will help significantly.

The commands to run are:

{{#tag:syntaxhighlight|
{{repo link
| site = gitlab
| cmd = git clone
| proj = flightgear
| repo = simgear
| type = git
| full = 1
}} simgear
{{repo link
| site = gitlab
| cmd = git clone
| proj = flightgear
| repo = flightgear
| type = git
| full = 1
}} flightgear
{{repo link
| site = gitlab
| cmd = git clone
| proj = flightgear
| repo = fgdata
| type = git
| full = 1
}} fgdata
{{repo link
| site = gitlab
| cmd = git clone
| proj = flightgear
| repo = windows-3rd-party
| type = git
| full = 1
}} windows-3rd-party
{{repo link
| site = gitlab
| cmd = git clone
| proj = flightgear
| repo = openscenegraph
| type = git
| full = 1
}} osg
| lang = "sh"
}}

After downloading these, I would suggest assembling a folder structure as below:

== Directory Tree ==
On Windows, assumptions on the directory structure are made to automate the discovery of dependencies. This recommended directory structure is described below. The components can be downloaded from the links above. If you do not use the recommended structure you will need to enter paths by hand and some parts may not input correctly.

Caveat -- spaces in the directory names will cause errors. It is best to make sure there are no spaces in the path anywhere.

<tt>
: FlightGearBuild / </tt> (Main root directory) <tt>
:: fgdata / </tt> (FlightGear data files) <tt>
:: flightgear / </tt> (FlightGear sources) <tt>
:: install / </tt> (Directory where you will install the built binaries to) <tt>
::: launch.bat / </tt> (launch script if desired, see below) <tt>
:: osg / </tt> (OSG sources) <tt>
:: simgear / </tt> (SimGear sources) <tt>
:: windows-3rd-party /
:: build.bat / </tt> (build script, see below) <tt>
:: update.bat / </tt> (update script, see below)

== Building ==
=== Scripted Compilation ===
This script will allow you to build OpenSceneGraph, SimGear and FlightGear automatically.

If you would like debug info, change Release to RelWithDebInfo in the --config commands.

{{collapsible script
| type = Windows batch file
| title = The <code>build.bat</code> script for configuring and compiling OSG, SG, and FG
| lang = batch
| script =
SET PATH=%PATH%;%ProgramFiles%\CMake\bin
SET QT6SDK64=C:\Qt\6.x\msvc2022_64
SET CMAKE_TOOLCHAIN="Visual Studio 18 2026"
SET ROOT_DIR=C:\path\to\FlightGearBuild

md osg-build
md simgear-build
md flightgear-build

cd %ROOT_DIR%\osg-build

cmake %ROOT_DIR%\osg -G %CMAKE_TOOLCHAIN% -A x64 ^
-DACTUAL_3RDPARTY_DIR=%ROOT_DIR%\windows-3rd-party/msvc140/3rdParty.x64 ^
-DCMAKE_RELWITHDEBINFO_POSTFIX:STRING= ^
-DOSG_USE_UTF8_FILENAME:BOOL=ON ^
-DWIN32_USE_MP:BOOL=ON ^
-DCMAKE_INSTALL_PREFIX:PATH=%ROOT_DIR%\install
cmake --build . --config Release --target INSTALL

cd %ROOT_DIR%\simgear-build
cmake %ROOT_DIR%\simgear -G %CMAKE_TOOLCHAIN% -A x64 ^
-DOSG_FSTREAM_EXPORT_FIXED:BOOL=ON ^
-DCMAKE_INSTALL_PREFIX:PATH=%ROOT_DIR%\install
cmake --build . --config Release --target INSTALL

cd %ROOT_DIR%\flightgear-build
cmake %ROOT_DIR%\flightgear -G %CMAKE_TOOLCHAIN% -A x64 ^
-DCMAKE_INSTALL_PREFIX:PATH=%ROOT_DIR%\install ^
-DCMAKE_PREFIX_PATH=%QT6SDK64% ^
-DFG_BUILD_TYPE:STRING=Release ^
-DOSG_FSTREAM_EXPORT_FIXED:BOOL=ON

cmake --build . --config Release --target INSTALL

pause
| show = 1
}}

{{tip | 10/2024: When using VS2022 or newer make sure your osg has this fix applied: https://gitlab.com/flightgear/openscenegraph/-/commit/31082758036c12738467a7210a17604275a79517<ref>https://sourceforge.net/p/flightgear/mailman/message/58821522/</ref>

Some folks encountered the following problem when building flightgear:
<syntaxhighlight>
CMake Error at CMakeLists.txt:283 (find_package):
By not providing "FindBoost.cmake" in CMAKE_MODULE_PATH this project has
asked CMake to find a package configuration file provided by "Boost", but
CMake did not find one.

Could not find a package configuration file provided by "Boost" with any of
the following names:

BoostConfig.cmake
boost-config.cmake

Add the installation prefix of "Boost" to CMAKE_PREFIX_PATH or set
"Boost_DIR" to a directory containing one of the above files. If "Boost"
provides a separate development package or SDK, be sure it has been
installed.
</syntaxhighlight>
This could be solved by doing the following in the top-level <code>CMakeLists.txt</code> of [https://sourceforge.net/p/flightgear/simgear/ci/next/tree/CMakeLists.txt#l16 simgear] and [https://sourceforge.net/p/flightgear/flightgear/ci/next/tree/CMakeLists.txt#l26 flightgear]:

In each file search for the line
<syntaxhighlight lang='CMake'>
cmake_policy(SET CMP0167 NEW)
</syntaxhighlight>
(it should be near the top of each file) and change from <code>NEW</code> to <code>OLD</code> like this<ref>https://sourceforge.net/p/flightgear/mailman/message/58815368/</ref>:
<syntaxhighlight lang='CMake'>
cmake_policy(SET CMP0167 OLD)
</syntaxhighlight>

In addition there are reports that a linking error occurs when building flightgear:
<syntaxhighlight>
pui.lib(puValue.obj) : error LNK2019: unresolved external symbol __imp_strncat referenced in function "protected: void__cdecl puValue::copy_stringval(char const *)" (?copy_stringval@puValue@@IEAAXPEBD@Z) [F:\git\flightgear-build\src\Main\fgfs.vcxproj]
F:\git\flightgear-build\src\Main\RelWithDebInfo\fgfs.exe : fatal error LNK1120: 1 unresolved externals [F:\git\flightgear-build\src\Main\fgfs.vcxproj]
</syntaxhighlight>
A workaround could be by changing the build type from <code>RelWithDebInfo</code> to <code>Release</code> when building osg, simgear and flightgear<ref>https://sourceforge.net/p/flightgear/mailman/message/58824438/</ref>:

In the <code>build.bat</code> change all three occurrences of
<syntaxhighlight lang='batch'>
cmake --build . --config RelWithDebInfo --target INSTALL
</syntaxhighlight>
to
<syntaxhighlight lang='batch'>
cmake --build . --config Release --target INSTALL
</syntaxhighlight>
}}

Before starting to use the script, you need to edit the top few lines of the script. You will have to:

# Set the path to your CMake installation.
# Ensure that the path to your QT SDK is correct for your version of MSVC.
# Ensure your toolchain version matches, e.g. "Visual Studio 16 2019" for MSVC 2019 or "Visual Studio 17 2022" for MSVC 2022.
# Set ROOT_DIR to the FlightGearBuild folder you created (the above directory structure)

==== Post-compilation: Launching FlightGear ====
'''In the debugger:'''
Open flightgear-build/FlightGear.sln. You can then perform all your development / debugging directly in VS. You normally only need to run build.bat again, if you update SimGear or OSG.

To launch FlightGear from Visual Studio, you can follow the following steps:
The first time only:
# Make sure you set your build type to RelWithDebInfo in the top bar.
# To start with the launcher, click on the small black arrow beside Local Windows Debugger to open 'fgfs debug properties'. Switch to debugging; add {{code|--launcher}} to the 'Command Arguments'. Click Apply and then OK.
# Press the green arrow (Local Windows Debugger) to start up FlightGear.
# The first time you'll have to choose where FGDATA is -- to do this, select the 'fgdata' directory you cloned at the start.

Thereafter, simply press the green arrow directly each time you want to start. If there are any local changes, it will recompile; alternatively it will start up directly. It will take a little longer to start as it loads symbols; however you also have the benefit that any segfaults will be caught allowing you to report them!

'''As a standard .exe:'''
NB these instructions overall are intended for setting up for development; there's a slightly more convoluted process for setting up for just plain flying (e.g. taking advantage of new features for aircraft development).

Essentially, Visual Studio doesn't copy in the DLLs into the /bin/ folder. It's also not ideal to manually copy in the DLLs as it can cause all sorts of issues. However, without the DLLs FlightGear won't work; therefore, you need to set the PATH so it knows where to look for them.
This launch script should work, put into your /install/bin/ folder:
{{collapsible script
| type = Windows batch file
| title = The <code>launch.bat</code> script for launching flightgear
| lang = batch
| script =
SET PATH=C:\path\to\FlightGearBuild\install\bin;C:\path\to\FlightGearBuild\windows-3rd-party\msvc140\3rdParty.x64\bin;C:\Qt\5.15.2\msvc2019_64\bin;%PATH%
SET FG_ROOT=C:\path\to\FlightGearBuild\fgdata
fgfs.exe --launcher
| show = 1
}}

Adjust the "path\to" references to suit your own personal installation, as well as the QT5 path.

=== Updating ===
To update FlightGear, in general, just run ''git pull'' on the source directories and then re-run the build.bat script -- it will update what it needs to, relatively quickly.

{{collapsible script
| type = Windows batch file
| title = The <code>update.bat</code> script for updating repositories
| lang = batch
| script =
SET ROOT_DIR=C:\path\to\FlightGearBuild

cd %ROOT_DIR%\osg
git pull

cd %ROOT_DIR%\fgdata
git pull

cd %ROOT_DIR%\flightgear
git pull

cd %ROOT_DIR%\simgear
git pull

cd %ROOT_DIR%\windows-3rd-party
git pull

pause
| show = 1
}}

=== Changing the Configuration ===
When the SimGear/FlightGear version numbers change, or you change configuration options (e.g. toggling Compositor, changing OSG versions, changing Qt versions) you do have to re-configure in CMake. To do this, it's usually safest to delete the simgear-build and flightgear-build folders and re-run the build.bat script, to ensure the build is clean. There is no need to delete osg-build unless changing OSG version.

In case of problems, most of the time deleting the simgear-build and flightgear-build folders and re-running the build.bat script will be sufficient.

{{building}}
[[fr:compiler flightear avec CMake - Windows]]
[[Category:Windows specific]]
[[Category:Hackathon Materials]]

Boeing 717

2026-06-22T18:22:51Z

Octal450: /* Development Status */

{{:{{PAGENAME}}/info}}

The '''Boeing 717''' is a twinjet narrowbody commercial airliner originally created by the McDonnell Douglas Corporation as the MD-95, to replace aging [[DC-9]]s. It is essentially a DC-9 with new avionics, systems, and engines, adopting several technologies from the [[MD-90]]. The project was completed by Boeing when Boeing bought McDonnell Douglas and rebranded as the Boeing 717. Boeing implemented several changes from the originally adopted MD-95 project, however, the airplane was completed by the former MD-95 project team.

This is an accurate and complex recreation of the Boeing 717.

== Overview ==
Includes the Boeing 717-200 with selectable Rolls-Royce BR715A1-30 or BR715C1-30 engines.

See the right InfoBox for the repository or download. Remember to rename the aircraft's folder to "717". DOWNLOAD NOT YET AVAILABLE.

== Development Status ==
Status denotes simulated functionality. Items marked as done may still be improved upon.

* Aerodynamics: {{done}}
* APU: {{done}}
* Autoflight: {{progressbar|90}}
* Caution and Warning: {{progressbar|30}}
* EAD Display: {{progressbar|90}}
* Electrical: {{done}}
* Exterior Model: {{done}}
* Flight Controls: {{done}}
* FMS and MCDU: {{progressbar|50}}
* Fuel: {{done}}
* Hydraulics: {{done}}
* ISFD Display: {{done}}
* IRS: {{done}}
* Landing Gear and Brakes: {{done}}
* Mach Trim and Yaw Damper: {{done}}
* ND Displays: {{progressbar|10}}
* PFD Displays: {{progressbar|90}}
* Pneumatics: {{progressbar|90}}
* Pressurization: {{not done}}
* RR BR715 Engines and FADEC: {{done}}
* SD Display: {{progressbar|90}}
* Virtual Cockpit: {{progressbar|50}}
* Weight/Balance: {{done}}

== Development Team ==
* Flight Dynamics, Systems, Instruments: Josh Davidson (Octal450)
* 3D/Textures: Gary Neely (Buckaroo), Josh Davidson (Octal450)

== Documentation ==
=== Written Documentation ===
Written documentation for this aircraft is available [https://github.com/Octal450/FlightGear-Aircraft-Documentation/tree/master/717 here].

=== Shortcut Keys ===
{| class="keytable"
! Key !! Function
|-
| {{key press|1}}
| Show Captain View
|-
| {{key press|2}}
| Show First Officer View
|-
| {{key press|3}}
| Show Overhead View
|-
| {{key press|4}}
| Show Forward Pedestal View
|-
| {{key press|5}}
| Show Aft Pedestal View
|-
| {{key press|6}}
| Show Glareshield View
|-
| {{key press|7}}
| Show MCDU View
|-
| {{key press|F1}}
| Disengage/Decrease Reverse Thrust
|-
| {{key press|F2}}
| Engage/Increase Reverse Thrust
|-
| {{key press|DEL}}
| Toggle Thrust Reversers
|-
| {{key press|C}}
| Reset Current View
|-
| {{key press|E}}
| Set Throttles to Idle
|-
| {{key press|F}}
| Set Throttles to Thrust Limit
|-
| {{key press|CTRL|B}}
| Cycle Spoilers
|-
| {{key press|Shift|B}}
| Toggle Parking Brake
|-
| {{key press|Shift|C}}
| Open Checklists
|-
| {{key press|CTRL|D}}
| Autothrust Disconnect Button
|-
| {{key press|Shift|D}}
| Autoflight Disconnect Button
|-
| {{key press|Shift|F}}
| Set Throttles to Full
|-
| {{key press|CTRL|G}}
| Go Around Button
|-
| {{key press|Shift|P}}
| Open CG Applet
|}

{{Boeing}}
{{MDouglas}}

[[Category:Airliners]]
[[Category:Octal450 hangar]]
[[Category:Red Griffin ATC compatible aircraft]]

FlightGear history

2026-06-15T05:55:58Z

Octal450: /* Cycled default airports */

[[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.

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.

== Beginnings (1996-1997) ==
[[File:FG SUNHALO.JPG|thumb|270px|March 18, 1999: one of the oldest surviving screenshots of FlightGear. Back then, FlightGear was the only PC based flight simulator rendering the [[Moon|sun, moon, and celestial]] objects at the correct position, and under the correct lighting conditions, in the sky. ]]
[[File:Image103.gif|thumb|Original Win95 icon]]
The FlightGear project was conceived on April 8, 1996 by David Murr who proposed a new flight simulator to be developed by volunteers<ref>David Murr (Apr 9, 1996). FlightGear proposal 1.0: [https://groups.google.com/forum/#!msg/rec.aviation.simulators/ny8HFBE5_T8/OdtIiGNGJc8J "A PROPOSAL FOR A NEW FLIGHT SIMULATOR - home built!@"]. Published on the rec.aviation.simulators newsgroup.</ref><ref>David Murr (1996). FlightGear proposal 2.0: [http://www.flightgear.org/proposal-2.0 FLIGHT GEAR "This truly is as real as it gets!" - a proposal for a new flight simulator - REVISION 2.0].</ref><ref>David Murr (Oct 29, 1996). FlightGear proposal 3.0: [http://www.flightgear.org/proposal-3.0 FLIGHT GEAR FLIGHT SIMULATOR, revision 3.0 - Wednesday, 10.30.96, "The future of flight simulation is here"]. Published on the [http://ftp.igh.cnrs.fr/pub/flightgear/www/old-stuff/flight-gear.9610 flight-gear@infoplane.com mailing list].</ref><ref>David Murr (Sep 11, 1998). FlightGear proposal 3.0.1: [http://www.flightgear.org/proposal-3.0.1 FLIGHT GEAR FLIGHT SIMULATOR, revision 3.0.1 - Friday, Sep.11.98, "The future of flight simulation is here"].</ref>. Part of the initial goals were to develop 2D and 3D graphics routines for the simulator. However this was a huge task that came to an unfinished halt at the start of 1997 as the main developer, Eric Korpela, was finishing his thesis.
 
Development of an OpenGL based version was spearheaded by Curtis Olsen starting in 1997, after the initial start in 1996. A large community response lead to many contributing to the project from its start in late '90s up to the present.
 

"''I was working at the University of Minnesota at the time, and had access to Sun and SGI graphical work stations which offered OpenGL for 3d graphics. OpenGl was just starting to become available on PC hardware with things like the 3dfx voodoo card. Somewhere at this point it occurred to me that a far better path would be to leverage an existing multi-platform 3d graphics system (like OpenGL) to build our flight simulator upon.'' 
''So I proceeded to rough together a basic scenery system, pasted on the larcsim flight model, and in a relatively short time was able to show actual flight over real 3d terrain. Good, realistic 3d terrain was something the other existing flight sims at the time were pretty far behind on ... and I think my work was enough of a breakthrough that it got a lot of people excited about the possibilities.''"~Curt Olson <ref>Curtis Olson (Sep 28, 2015). [http://forum.flightgear.org/viewtopic.php?f=42&t=27558&p=259048#p259021 Re: A PROPOSAL FOR A NEW FLIGHT SIMULATOR - home built!@]. Published on the FlightGear forum.</ref>
 

Rather than start entirely from scratch, FlightGear developers made use of the [[LaRCsim]] flight model from NASA, with OpenGL for 3D graphic code, and freely available elevation data. First working binaries came out in 1997, with an intense updating of newer versions for several years resulting in progressively more stable and advanced programs.

== Versions 0.7–0.9 (2001–2003) ==
By 2001, the team was releasing new beta versions regularly (0.7.x, 0.8.0, over 2001-2003) and with 0.9.xx (2003-2006). Later in the decade, the rate of final public releases slowed, but had larger amounts of content (0.9.10, 1.0.0 etc.). The maturity of software by 2005 lead to more widespread reviews, and increased popularity.

== Version 0.9.0-0.9.11 (2002-2007) ==
The use of version numbers slowed dramatically after the late 2002 release of version 0.9.0. Versions 0.9.9 (2005) and 0.9.10 (2006) had about 8 all-new or redone [[aircraft]] adding to a total of 70-90 aircraft. [[Nasal]] was also integrated into FlightGear in version 0.9.4. FlightGear 0.9.10 won Softpedia's "Pick" award (5 out of 5 stars) on June 3, 2006 as well as the "100% CLEAN" Softpedia award.

Behind the scenes there was a 0.9.11-pre1 released in 2007 that ended up being superseded by FlightGear 1.0. The pre-version had about 33 new or redone aircraft.

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

== Version 1.0 (2008) ==
The version number marked a formal transition out of beta development since the software's first release in 1997, ten years prior.

== Version 1.9.0 (2008) ==
At the time version 1.9.0 was released FlightGear switched from [[PLIB]] to [[OSG]], which caused the temporary loss of some of the features like 3D clouds and shadows. On the contrary new features such as particles add another degree of realism to the simulation. Most aircraft developed for OSG do not work with older versions. The user is able to choose from 230 aircraft provided with 1.9.0, although only a few are included in the base package.
Version 1.9.1, released shortly afterwards, was a bug fix release.

== Version 2.0.0 (2010) ==
FlightGear 2.0.0 reflects the maturation of the OpenSceneGraph port that started with the previous 1.9.0 release. In addition to many internal code improvements, FlightGear 2.0.0 marks the introduction of many new exciting improvements in the graphics and sound system, as well as improved usability of key features, and improved behavior of existing features. Highlights of this new version include: Dramatic new 3D clouds, dramatic lighting conditions, improved support for custom scenery, and many many new and detailed aircraft models.

== Version 2.4.0 (2011) ==
Starting with version 2.4.0, the FlightGear team adopted a [[release plan]]. From then on, a new version is released every February and August.

==Version 3.8.0/2016.1.0==
{{Main article|Release plan#Detailed time schedule and checklist}}
Following the cancellation of 3.6, the modern FlightGear team revised the release plan and process. New releases are essentially selected and tuned "nightlies" instead of special compilations.

Also, in this release the concept of rotating default airports first started. All FlightGear releases after 2016.1 have unique default airports and 'codenames'.

{{Main article|Release plan/Lessons learned#2016.1}}

== Version 2018.1 "Honolulu" (2018) ==
Released in April 2018, version 2018.1 was the first major update in the 2018 release cycle. This version focused on environmental realism and significant improvements to the YASim flight dynamics model (FDM), including support for multiple wing sections to model variable wing geometry. The "Honolulu" release featured PHNL as the default airport and introduced active volcanoes such as Kilauea and Etna, which integrated environmental physics by generating increased turbulence in their vicinity. The [[Atmospheric light scattering|ALS (Atmospheric Light Scattering)]] renderer was also updated with extra volumetric vegetation layers for denser undergrowth.

== Version 2019.1 (2019) ==
Version 2019.1, released in March 2019, introduced the "Compositor," an experimental XML-configurable rendering framework designed to replace legacy hard-coded rendering paths. This framework enabled advanced post-processing effects and Cascaded Shadow Mapping (CSM) for more realistic environmental shadows. Other technical advancements included the introduction of a DDS Texture Cache to speed up loading times and the implementation of 8.33 kHz radio frequency spacing for aircraft like the [[Boeing 777]] to comply with modern European airspace requirements.

== Version 2020.1 and 2020.3 LTS (2020) ==
The 2020 cycle saw the release of 2020.1 in May and the Long Term Support (LTS) version, 2020.3, in October. This era was marked by a shift toward data integrity, particularly in the JSBSim FDM, where gyros were updated to measure rotation rates rather than rotational accelerations to better match physical reality. Graphical performance was enhanced through instanced-based rendering for OpenStreetMap (OSM) buildings, which was later integrated into the [[TerraSync]] system (v2020.3.7) for global coverage. The release also featured expanded aircraft carrier support with new launcher options for takeoff and approach positions.

== Version 2024.1 (2025-2026) ==
Replacing the 2020.3 LTS, version 2024.1 (officially released in February 2025 as v2024.1.1) represents a major technological pivot for the project. Key highlights include:

* [[VR]] Support: Preliminary integration of VR headsets using the OpenXR standard.

* [[World Scenery 3.0]] (WS3.0): A preview of a new Quadtree-based scenery system utilizing Virtual Planet Builder, providing higher frame rates and lower memory usage through multiple levels of detail.

* Dynamic Lighting and Shadows: Real-time dynamic shadows and lighting were added to the core rendering engine.

* Climate Modeling: The legacy season selection was replaced with a holistic climate model calculating environmental factors like snow lines and ocean temperatures dynamically.

== Release timeline ==
Final build code release dates by year.

{| class="mw-collapsible mw-collapsed wikitable" style="width:40%; margin:auto"
! Date !! Version
|-
| Jul 17, 1997 || First major code release
|-
| Sep 23, 1997 || 0.12
|-
| Dec 9, 1997 || 0.15
|-
| Dec 17, 1997 || 0.18
|-
| Dec 30, 1997 || 0.19 (first binaries)
|-
| Jan 6, 1998 || 0.22
|-
| Mar 11 98 || 0.37
|-
| Apr 8, 1998 || 0.41
|-
| Apr 14, 1998 || 0.42
|-
| Apr 23, 1998 || 0.43
|-
| Apr 28, 1998 || 0.44
|-
| May 7, 1998 || 0.45
|-
| May 11, 1998 || 0.46
|-
| May 18, 1998 || 0.47
|-
| Jun 9, 1998 || 0.48
|-
| Jun 27, 1998 || 0.49
|-
| Jul 13, 1998 || 0.50
|-
| Jul 21, 1998 || 0.51
|-
| Aug 15, 1998 || 0.52
|-
| Sep 2, 1998 || 0.53
|-
| Sep 25, 1998 || 0.54
|-
| Oct 23, 1998 || 0.55
|-
| Nov 23, 1998 || 0.56
|-
| Jan 21, 1999 || 0.57
|-
| Feb 10, 1999 || 0.58
|-
| Mar 31, 1999 || 0.59
|-
| May 26, 1999 || 0.6.0
|-
| Jun 21, 1999 || 0.6.1 (Stable)
|-
|rowspan=2 | Sep 11, 1999 || 0.7.0 (Development)
|-
| 0.6.2 (Stable)
|-
| Oct 22, 1999 || 0.7.1 (Development)
|-
| Feb 17, 2000 || 0.7.2 (Development)
|-
| May 18, 2000 || 0.7.3 (Development)
|-
| Jul 20, 2000 || 0.7.4
|-
| Sep 18, 2000 || 0.7.5
|-
| Dec 19, 2000 || 0.7.6
|-
| Jun 20, 2001 || 0.7.7
|-
| Jul 13, 2001 || 0.7.8
|-
| Feb 16, 2002 || 0.7.9
|-
| Apr 20, 2002 || 0.7.10
|-
| Sep 7, 2002 || 0.8.0
|-
| Dec 3, 2002 || 0.9.0
|-
| Dec 5, 2002 || 0.9.1
|-
| Jun 4, 2003 || 0.9.2
|-
| Oct 24, 2003 || 0.9.3
|-
| Mar 26, 2004 || 0.9.4
|-
| Jul 29, 2004 || 0.9.5
|-
| Oct 12, 2004 || 0.9.6
|-
| Jan 18, 2005 || 0.9.8
|-
| Nov 17, 2005 || 0.9.9
|-
| Apr 5, 2006 || 0.9.10
|-
| May 2007 || 0.9.11-pre1
|-
| Dec 17, 2007 || 1.0.0
|-
| Dec 22, 2008 || 1.9.0
|-
| Jan 25, 2009 || 1.9.1
|-
| Feb 25, 2010 || 2.0.0
|-
| Aug 17, 2011 || 2.4.0
|-
| Feb 17, 2012 || 2.6.0
|-
| Aug 17, 2012 || 2.8.0
|-
| Feb 17, 2013 || 2.10
|-
| Sep 21, 2013 || 2.12
|-
| Feb 17, 2014 || 3.0
|-
| Oct 15, 2014 || 3.2
|-
| Feb 17, 2015 || 3.4
|-
| {{N/a}} || 3.6 (unreleased, see [[FlightGear Newsletter November 2015#FlightGear v3.6 canceled|here]])
|-
| Feb 17, 2016 || 2016.1.1 (new versioning scheme)
|-
| May 7, 2016 || 2016.1.2
|-
| May 17, 2016 || 2016.2.1
|-
| Sep 12, 2016 || 2016.3.1
|-
| Nov 19, 2016 || 2016.4.1
|-
| Nov 23, 2016 || 2016.4.2
|-
| Dec 5, 2016 || 2016.4.3
|-
| Dec 28, 2016 || 2016.4.4
|-
| Feb 23, 2017 || 2017.1.1
|-
| Mar 1, 2017 || 2017.1.2
|-
| Apr 4, 2017 || 2017.1.3
|-
| May 22, 2017 || 2017.2.1
|-
| Sep 20, 2017 || 2017.3.1
|-
| Apr 11, 2018 || 2018.1.1
|-
| May 22, 2018 || 2018.2.1
|-
| Dec 3, 2018 || 2018.3.1
|-
| Jan 29, 2019 || 2018.3.2
|-
| {{N/a}} || 2018.3.3 (not released)
|-
| Aug 9, 2019 || 2018.3.4
|-
| Apr 20, 2020 || 2018.3.5
|-
| Aug 9, 2020 || 2018.3.6
|-
| Mar 14, 2019 || 2019.1.1
|-
| Sep 1, 2019 || 2019.1.2
|-
| May 11, 2020 || 2020.1.1
|-
| May 25, 2020 || 2020.1.2
|-
| Jun 26, 2020 || 2020.1.3
|-
| Oct 13, 2020 || 2020.2.1
|-
| Oct 29, 2020 || 2020.3.1
|-
| Nov 6, 2020 || 2020.3.2
|-
| Nov 23, 2020 || 2020.3.3
|-
| Dec 1, 2020 || 2020.3.4
|-
| Dec 19, 2020 || 2020.3.5
|-
| Jan 24, 2021 || 2020.3.6
|-
| Mar 21, 2021 || 2020.3.7
|-
| Mar 25, 2021 || 2020.3.8
|-
| Jun 14, 2021 || 2020.3.9
|-
| Jul 26, 2021 || 2020.3.10
|-
| Jul 29, 2021 || 2020.3.11
|-
|Feb 6, 2022
|2020.3.12
|-
|Mar 30, 2022
|2020.3.13
|-
|Sep 27, 2022
|2020.3.14
|-
|Oct 12, 2022
|2020.3.15
|-
|Oct 20, 2022
|2020.3.16
|-
|Sep 22, 2022
|2020.3.17
|-
|Mar 21, 2023
|2020.3.18
|-
|Feb 27, 2025
|2024.1.1
|-
|Sep 18, 2025
|2024.1.2
|-
|Nov 2, 2025
|2024.1.3
|-
|Jan 21, 2026
|2024.1.4
|-
|Mar 22, 2026
|2024.1.5
|-
|June 4, 2026
|2024.1.6
|}

== Cycled default airports ==

FlightGear did not start changing the default airport until version 2016.1 was released. At that time, the idea was that each new release would have a new default airport. This chart lists the default airports since 2016.1 was released. Since 2018.1, the selection of a new default airport has been changed so that a new airport is selected for each new major version release instead of for each minor version release (except 2024.1, for whatever reason).

{| class="wikitable"
|-
! Release !! ICAO !! Default Airport
|-
| 2016.1 || [[KSFO]] || San Francisco ''(transition)''
|-
| 2016.2 || [[LEBL]] || Barcelona
|-
| 2016.3 || [[SBRJ]] || Rio de Janeiro
|-
| 2016.4 || [[LSZH]] || Zürich
|-
| 2017.1 || [[ENBR]] || Bergen
|-
| 2017.2 || [[KBOS]] || Boston
|-
| 2017.3 || [[LKPR]] || Prague
|-
| 2018.1 || rowspan="4" | [[PHNL]] || rowspan="4" | Honolulu
|-
| 2018.2
|-
| 2018.3
|-
| 2019.1
|-
| 2020.1 || rowspan="4" | [[BIKF]] || rowspan="4" | Keflavik
|-
| 2020.2
|-
| 2020.3
|-
| 2024.1
|}

== External links ==
* [http://web.archive.org/web/*/http://www.flightgear.org/ Internet Archive: Wayback Machine for http://www.flightgear.org/ ]
* [http://web.archive.org/web/19981212014011/http://flightgear.org/ Old website on December 5, 1998]
* [https://github.com/clolsonus/FlightGear-vault Historic FlightGear code since 1996] ([https://forum.flightgear.org/viewtopic.php?f=42&t=42351 forum])
* [http://web.archive.org/web/19990209050729/http://www.flightgear.org/Gallery/texture2.jpg link] ("Here's one of the Grand Canyon with a rock face texture. I know this looks funny, but I'm just experimenting here.", old FlightGear screenshot)

{{Appendix|2=
* {{wikipedia|FlightGear}}
* [http://www.flightgear.org/proposal-3.0.1 Original Flight Gear Proposal] by David L. Murr (Revision 3.0.1)
* [ftp://flightgear.wo0t.de/flightgear-ftp/ FlightGear FTP Archive]
----
{{References}}
}}
[[fr:FlightGear history]]

[[Category:FlightGear]]
[[Category:Articles to be updated for each release]]

FlightGear history

2026-06-15T05:52:37Z

Octal450: /* Version 2024.1 (2025-2026) */ UIUC was not removed yet, that's in next.

[[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.

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.

== Beginnings (1996-1997) ==
[[File:FG SUNHALO.JPG|thumb|270px|March 18, 1999: one of the oldest surviving screenshots of FlightGear. Back then, FlightGear was the only PC based flight simulator rendering the [[Moon|sun, moon, and celestial]] objects at the correct position, and under the correct lighting conditions, in the sky. ]]
[[File:Image103.gif|thumb|Original Win95 icon]]
The FlightGear project was conceived on April 8, 1996 by David Murr who proposed a new flight simulator to be developed by volunteers<ref>David Murr (Apr 9, 1996). FlightGear proposal 1.0: [https://groups.google.com/forum/#!msg/rec.aviation.simulators/ny8HFBE5_T8/OdtIiGNGJc8J "A PROPOSAL FOR A NEW FLIGHT SIMULATOR - home built!@"]. Published on the rec.aviation.simulators newsgroup.</ref><ref>David Murr (1996). FlightGear proposal 2.0: [http://www.flightgear.org/proposal-2.0 FLIGHT GEAR "This truly is as real as it gets!" - a proposal for a new flight simulator - REVISION 2.0].</ref><ref>David Murr (Oct 29, 1996). FlightGear proposal 3.0: [http://www.flightgear.org/proposal-3.0 FLIGHT GEAR FLIGHT SIMULATOR, revision 3.0 - Wednesday, 10.30.96, "The future of flight simulation is here"]. Published on the [http://ftp.igh.cnrs.fr/pub/flightgear/www/old-stuff/flight-gear.9610 flight-gear@infoplane.com mailing list].</ref><ref>David Murr (Sep 11, 1998). FlightGear proposal 3.0.1: [http://www.flightgear.org/proposal-3.0.1 FLIGHT GEAR FLIGHT SIMULATOR, revision 3.0.1 - Friday, Sep.11.98, "The future of flight simulation is here"].</ref>. Part of the initial goals were to develop 2D and 3D graphics routines for the simulator. However this was a huge task that came to an unfinished halt at the start of 1997 as the main developer, Eric Korpela, was finishing his thesis.
 
Development of an OpenGL based version was spearheaded by Curtis Olsen starting in 1997, after the initial start in 1996. A large community response lead to many contributing to the project from its start in late '90s up to the present.
 

"''I was working at the University of Minnesota at the time, and had access to Sun and SGI graphical work stations which offered OpenGL for 3d graphics. OpenGl was just starting to become available on PC hardware with things like the 3dfx voodoo card. Somewhere at this point it occurred to me that a far better path would be to leverage an existing multi-platform 3d graphics system (like OpenGL) to build our flight simulator upon.'' 
''So I proceeded to rough together a basic scenery system, pasted on the larcsim flight model, and in a relatively short time was able to show actual flight over real 3d terrain. Good, realistic 3d terrain was something the other existing flight sims at the time were pretty far behind on ... and I think my work was enough of a breakthrough that it got a lot of people excited about the possibilities.''"~Curt Olson <ref>Curtis Olson (Sep 28, 2015). [http://forum.flightgear.org/viewtopic.php?f=42&t=27558&p=259048#p259021 Re: A PROPOSAL FOR A NEW FLIGHT SIMULATOR - home built!@]. Published on the FlightGear forum.</ref>
 

Rather than start entirely from scratch, FlightGear developers made use of the [[LaRCsim]] flight model from NASA, with OpenGL for 3D graphic code, and freely available elevation data. First working binaries came out in 1997, with an intense updating of newer versions for several years resulting in progressively more stable and advanced programs.

== Versions 0.7–0.9 (2001–2003) ==
By 2001, the team was releasing new beta versions regularly (0.7.x, 0.8.0, over 2001-2003) and with 0.9.xx (2003-2006). Later in the decade, the rate of final public releases slowed, but had larger amounts of content (0.9.10, 1.0.0 etc.). The maturity of software by 2005 lead to more widespread reviews, and increased popularity.

== Version 0.9.0-0.9.11 (2002-2007) ==
The use of version numbers slowed dramatically after the late 2002 release of version 0.9.0. Versions 0.9.9 (2005) and 0.9.10 (2006) had about 8 all-new or redone [[aircraft]] adding to a total of 70-90 aircraft. [[Nasal]] was also integrated into FlightGear in version 0.9.4. FlightGear 0.9.10 won Softpedia's "Pick" award (5 out of 5 stars) on June 3, 2006 as well as the "100% CLEAN" Softpedia award.

Behind the scenes there was a 0.9.11-pre1 released in 2007 that ended up being superseded by FlightGear 1.0. The pre-version had about 33 new or redone aircraft.

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

== Version 1.0 (2008) ==
The version number marked a formal transition out of beta development since the software's first release in 1997, ten years prior.

== Version 1.9.0 (2008) ==
At the time version 1.9.0 was released FlightGear switched from [[PLIB]] to [[OSG]], which caused the temporary loss of some of the features like 3D clouds and shadows. On the contrary new features such as particles add another degree of realism to the simulation. Most aircraft developed for OSG do not work with older versions. The user is able to choose from 230 aircraft provided with 1.9.0, although only a few are included in the base package.
Version 1.9.1, released shortly afterwards, was a bug fix release.

== Version 2.0.0 (2010) ==
FlightGear 2.0.0 reflects the maturation of the OpenSceneGraph port that started with the previous 1.9.0 release. In addition to many internal code improvements, FlightGear 2.0.0 marks the introduction of many new exciting improvements in the graphics and sound system, as well as improved usability of key features, and improved behavior of existing features. Highlights of this new version include: Dramatic new 3D clouds, dramatic lighting conditions, improved support for custom scenery, and many many new and detailed aircraft models.

== Version 2.4.0 (2011) ==
Starting with version 2.4.0, the FlightGear team adopted a [[release plan]]. From then on, a new version is released every February and August.

==Version 3.8.0/2016.1.0==
{{Main article|Release plan#Detailed time schedule and checklist}}
Following the cancellation of 3.6, the modern FlightGear team revised the release plan and process. New releases are essentially selected and tuned "nightlies" instead of special compilations.

Also, in this release the concept of rotating default airports first started. All FlightGear releases after 2016.1 have unique default airports and 'codenames'.

{{Main article|Release plan/Lessons learned#2016.1}}

== Version 2018.1 "Honolulu" (2018) ==
Released in April 2018, version 2018.1 was the first major update in the 2018 release cycle. This version focused on environmental realism and significant improvements to the YASim flight dynamics model (FDM), including support for multiple wing sections to model variable wing geometry. The "Honolulu" release featured PHNL as the default airport and introduced active volcanoes such as Kilauea and Etna, which integrated environmental physics by generating increased turbulence in their vicinity. The [[Atmospheric light scattering|ALS (Atmospheric Light Scattering)]] renderer was also updated with extra volumetric vegetation layers for denser undergrowth.

== Version 2019.1 (2019) ==
Version 2019.1, released in March 2019, introduced the "Compositor," an experimental XML-configurable rendering framework designed to replace legacy hard-coded rendering paths. This framework enabled advanced post-processing effects and Cascaded Shadow Mapping (CSM) for more realistic environmental shadows. Other technical advancements included the introduction of a DDS Texture Cache to speed up loading times and the implementation of 8.33 kHz radio frequency spacing for aircraft like the [[Boeing 777]] to comply with modern European airspace requirements.

== Version 2020.1 and 2020.3 LTS (2020) ==
The 2020 cycle saw the release of 2020.1 in May and the Long Term Support (LTS) version, 2020.3, in October. This era was marked by a shift toward data integrity, particularly in the JSBSim FDM, where gyros were updated to measure rotation rates rather than rotational accelerations to better match physical reality. Graphical performance was enhanced through instanced-based rendering for OpenStreetMap (OSM) buildings, which was later integrated into the [[TerraSync]] system (v2020.3.7) for global coverage. The release also featured expanded aircraft carrier support with new launcher options for takeoff and approach positions.

== Version 2024.1 (2025-2026) ==
Replacing the 2020.3 LTS, version 2024.1 (officially released in February 2025 as v2024.1.1) represents a major technological pivot for the project. Key highlights include:

* [[VR]] Support: Preliminary integration of VR headsets using the OpenXR standard.

* [[World Scenery 3.0]] (WS3.0): A preview of a new Quadtree-based scenery system utilizing Virtual Planet Builder, providing higher frame rates and lower memory usage through multiple levels of detail.

* Dynamic Lighting and Shadows: Real-time dynamic shadows and lighting were added to the core rendering engine.

* Climate Modeling: The legacy season selection was replaced with a holistic climate model calculating environmental factors like snow lines and ocean temperatures dynamically.

== Release timeline ==
Final build code release dates by year.

{| class="mw-collapsible mw-collapsed wikitable" style="width:40%; margin:auto"
! Date !! Version
|-
| Jul 17, 1997 || First major code release
|-
| Sep 23, 1997 || 0.12
|-
| Dec 9, 1997 || 0.15
|-
| Dec 17, 1997 || 0.18
|-
| Dec 30, 1997 || 0.19 (first binaries)
|-
| Jan 6, 1998 || 0.22
|-
| Mar 11 98 || 0.37
|-
| Apr 8, 1998 || 0.41
|-
| Apr 14, 1998 || 0.42
|-
| Apr 23, 1998 || 0.43
|-
| Apr 28, 1998 || 0.44
|-
| May 7, 1998 || 0.45
|-
| May 11, 1998 || 0.46
|-
| May 18, 1998 || 0.47
|-
| Jun 9, 1998 || 0.48
|-
| Jun 27, 1998 || 0.49
|-
| Jul 13, 1998 || 0.50
|-
| Jul 21, 1998 || 0.51
|-
| Aug 15, 1998 || 0.52
|-
| Sep 2, 1998 || 0.53
|-
| Sep 25, 1998 || 0.54
|-
| Oct 23, 1998 || 0.55
|-
| Nov 23, 1998 || 0.56
|-
| Jan 21, 1999 || 0.57
|-
| Feb 10, 1999 || 0.58
|-
| Mar 31, 1999 || 0.59
|-
| May 26, 1999 || 0.6.0
|-
| Jun 21, 1999 || 0.6.1 (Stable)
|-
|rowspan=2 | Sep 11, 1999 || 0.7.0 (Development)
|-
| 0.6.2 (Stable)
|-
| Oct 22, 1999 || 0.7.1 (Development)
|-
| Feb 17, 2000 || 0.7.2 (Development)
|-
| May 18, 2000 || 0.7.3 (Development)
|-
| Jul 20, 2000 || 0.7.4
|-
| Sep 18, 2000 || 0.7.5
|-
| Dec 19, 2000 || 0.7.6
|-
| Jun 20, 2001 || 0.7.7
|-
| Jul 13, 2001 || 0.7.8
|-
| Feb 16, 2002 || 0.7.9
|-
| Apr 20, 2002 || 0.7.10
|-
| Sep 7, 2002 || 0.8.0
|-
| Dec 3, 2002 || 0.9.0
|-
| Dec 5, 2002 || 0.9.1
|-
| Jun 4, 2003 || 0.9.2
|-
| Oct 24, 2003 || 0.9.3
|-
| Mar 26, 2004 || 0.9.4
|-
| Jul 29, 2004 || 0.9.5
|-
| Oct 12, 2004 || 0.9.6
|-
| Jan 18, 2005 || 0.9.8
|-
| Nov 17, 2005 || 0.9.9
|-
| Apr 5, 2006 || 0.9.10
|-
| May 2007 || 0.9.11-pre1
|-
| Dec 17, 2007 || 1.0.0
|-
| Dec 22, 2008 || 1.9.0
|-
| Jan 25, 2009 || 1.9.1
|-
| Feb 25, 2010 || 2.0.0
|-
| Aug 17, 2011 || 2.4.0
|-
| Feb 17, 2012 || 2.6.0
|-
| Aug 17, 2012 || 2.8.0
|-
| Feb 17, 2013 || 2.10
|-
| Sep 21, 2013 || 2.12
|-
| Feb 17, 2014 || 3.0
|-
| Oct 15, 2014 || 3.2
|-
| Feb 17, 2015 || 3.4
|-
| {{N/a}} || 3.6 (unreleased, see [[FlightGear Newsletter November 2015#FlightGear v3.6 canceled|here]])
|-
| Feb 17, 2016 || 2016.1.1 (new versioning scheme)
|-
| May 7, 2016 || 2016.1.2
|-
| May 17, 2016 || 2016.2.1
|-
| Sep 12, 2016 || 2016.3.1
|-
| Nov 19, 2016 || 2016.4.1
|-
| Nov 23, 2016 || 2016.4.2
|-
| Dec 5, 2016 || 2016.4.3
|-
| Dec 28, 2016 || 2016.4.4
|-
| Feb 23, 2017 || 2017.1.1
|-
| Mar 1, 2017 || 2017.1.2
|-
| Apr 4, 2017 || 2017.1.3
|-
| May 22, 2017 || 2017.2.1
|-
| Sep 20, 2017 || 2017.3.1
|-
| Apr 11, 2018 || 2018.1.1
|-
| May 22, 2018 || 2018.2.1
|-
| Dec 3, 2018 || 2018.3.1
|-
| Jan 29, 2019 || 2018.3.2
|-
| {{N/a}} || 2018.3.3 (not released)
|-
| Aug 9, 2019 || 2018.3.4
|-
| Apr 20, 2020 || 2018.3.5
|-
| Aug 9, 2020 || 2018.3.6
|-
| Mar 14, 2019 || 2019.1.1
|-
| Sep 1, 2019 || 2019.1.2
|-
| May 11, 2020 || 2020.1.1
|-
| May 25, 2020 || 2020.1.2
|-
| Jun 26, 2020 || 2020.1.3
|-
| Oct 13, 2020 || 2020.2.1
|-
| Oct 29, 2020 || 2020.3.1
|-
| Nov 6, 2020 || 2020.3.2
|-
| Nov 23, 2020 || 2020.3.3
|-
| Dec 1, 2020 || 2020.3.4
|-
| Dec 19, 2020 || 2020.3.5
|-
| Jan 24, 2021 || 2020.3.6
|-
| Mar 21, 2021 || 2020.3.7
|-
| Mar 25, 2021 || 2020.3.8
|-
| Jun 14, 2021 || 2020.3.9
|-
| Jul 26, 2021 || 2020.3.10
|-
| Jul 29, 2021 || 2020.3.11
|-
|Feb 6, 2022
|2020.3.12
|-
|Mar 30, 2022
|2020.3.13
|-
|Sep 27, 2022
|2020.3.14
|-
|Oct 12, 2022
|2020.3.15
|-
|Oct 20, 2022
|2020.3.16
|-
|Sep 22, 2022
|2020.3.17
|-
|Mar 21, 2023
|2020.3.18
|-
|Feb 27, 2025
|2024.1.1
|-
|Sep 18, 2025
|2024.1.2
|-
|Nov 2, 2025
|2024.1.3
|-
|Jan 21, 2026
|2024.1.4
|-
|Mar 22, 2026
|2024.1.5
|-
|June 4, 2026
|2024.1.6
|}

== Cycled default airports ==

FlightGear did not start changing the default airport until version 2016.1 was released. At that time, the idea was that each new release would have a new default airport. This chart lists the default airports since 2016.1 was released. Since 2018.1, the selection of a new default airport has been changed so that a new airport is selected for each new major version release instead of for each minor version release.

{| class="wikitable"
|-
! Release !! ICAO !! Default Airport
|-
| 2016.1 || [[KSFO]] || San Francisco ''(transition)''
|-
| 2016.2 || [[LEBL]] || Barcelona
|-
| 2016.3 || [[SBRJ]] || Rio de Janeiro
|-
| 2016.4 || [[LSZH]] || Zürich
|-
| 2017.1 || [[ENBR]] || Bergen
|-
| 2017.2 || [[KBOS]] || Boston
|-
| 2017.3 || [[LKPR]] || Prague
|-
| 2018.1 || rowspan="4" | [[PHNL]] || rowspan="4" | Honolulu
|-
| 2018.2
|-
| 2018.3
|-
| 2019.1
|-
| 2020.1 || rowspan="4" | [[BIKF]] || rowspan="4" | Keflavik
|-
| 2020.2
|-
| 2020.3
|-
| 2024.1
|}

== External links ==
* [http://web.archive.org/web/*/http://www.flightgear.org/ Internet Archive: Wayback Machine for http://www.flightgear.org/ ]
* [http://web.archive.org/web/19981212014011/http://flightgear.org/ Old website on December 5, 1998]
* [https://github.com/clolsonus/FlightGear-vault Historic FlightGear code since 1996] ([https://forum.flightgear.org/viewtopic.php?f=42&t=42351 forum])
* [http://web.archive.org/web/19990209050729/http://www.flightgear.org/Gallery/texture2.jpg link] ("Here's one of the Grand Canyon with a rock face texture. I know this looks funny, but I'm just experimenting here.", old FlightGear screenshot)

{{Appendix|2=
* {{wikipedia|FlightGear}}
* [http://www.flightgear.org/proposal-3.0.1 Original Flight Gear Proposal] by David L. Murr (Revision 3.0.1)
* [ftp://flightgear.wo0t.de/flightgear-ftp/ FlightGear FTP Archive]
----
{{References}}
}}
[[fr:FlightGear history]]

[[Category:FlightGear]]
[[Category:Articles to be updated for each release]]

Talk:YSFlight

2026-06-15T05:51:03Z

Octal450:

== Relevance for FlightGear wiki ==

Hi,

What is the relevance of this article to FlightGear? Just being another open source flight simulator does not make it in scope as far as I'd say.

[[User:Gijs|Gijs]] ([[User talk:Gijs|talk]]) 09:43, 8 June 2026 (UTC)

: Sorry, I don't know it initially. [[User:Servo|Servo]] ([[User talk:Servo|talk]]) 20:36, 8 June 2026 (UTC)

:: I was wondering myself... why is this here? Should be deleted imo. [[User:Octal450|Octal450]] ([[User talk:Octal450|talk]]) 05:51, 15 June 2026 (UTC)

Building using CMake - Windows

2026-06-14T02:43:09Z

Octal450: /* Scripted Compilation */

This article is intended to give an overview of '''building FlightGear on modern Windows systems'''. It was created using Windows 11 and VS 2022. It ought to be transferable to earlier versions of the Windows OS and software.

As FlightGear is now 64-bit only, the guide only describes building on a 64-bit system.

== Required software ==
* [https://cmake.org/download/ CMake for Windows]. Download and install the Windows Win64-x64 Installer.
* [https://visualstudio.microsoft.com/downloads/ Microsoft Visual Studio 2022] (MSVC). The Community version is free. There is no need for the premium versions; none of their features are required to build FlightGear. The C++ compiler will not be installed by default. You either choose this component during installation or after installation by starting MSVC and trying to create a new C++ project. The one to download is "Desktop Development with C++". Make sure to have the latest version of the Windows SDK for your Windows version and the C++ Compiler checked. As of 8/5/2025, the option to select is "MSVC 2022 64-bit".
* [https://www.qt.io/download-open-source/ Qt6] for the [[FlightGear Qt launcher|Integrated Qt Launcher]]. Download the online installer to install and choose the latest version of Qt. Leave the default Developer and Designer Tools selection - these are needed for coding and compiling. Otherwise, here is [https://www.qt.io/offline-installers Offline Qt Downloads] for the optional offline-installer versions of Qt.
* [https://git-scm.com/download/win Git] to keep your build up to date. It also simplifies downloads of components. Optional, but can't recommend it enough!

== Obtaining source ==
{{Main article|FlightGear and Git}}
Throughout this article it is assumed that you have set up git clones of the various source repositories (FlightGear, SimGear, data...).
Using an organized directory (see below) will help significantly.

The commands to run are:

{{#tag:syntaxhighlight|
{{repo link
| site = gitlab
| cmd = git clone
| proj = flightgear
| repo = simgear
| type = git
| full = 1
}} simgear
{{repo link
| site = gitlab
| cmd = git clone
| proj = flightgear
| repo = flightgear
| type = git
| full = 1
}} flightgear
{{repo link
| site = gitlab
| cmd = git clone
| proj = flightgear
| repo = fgdata
| type = git
| full = 1
}} fgdata
{{repo link
| site = gitlab
| cmd = git clone
| proj = flightgear
| repo = windows-3rd-party
| type = git
| full = 1
}} windows-3rd-party
{{repo link
| site = gitlab
| cmd = git clone
| proj = flightgear
| repo = openscenegraph
| type = git
| full = 1
}} osg
| lang = "sh"
}}

After downloading these, I would suggest assembling a folder structure as below:

== Directory Tree ==
On Windows, assumptions on the directory structure are made to automate the discovery of dependencies. This recommended directory structure is described below. The components can be downloaded from the links above. If you do not use the recommended structure you will need to enter paths by hand and some parts may not input correctly.

Caveat -- spaces in the directory names will cause errors. It is best to make sure there are no spaces in the path anywhere.

<tt>
: FlightGearBuild / </tt> (Main root directory) <tt>
:: fgdata / </tt> (FlightGear data files) <tt>
:: flightgear / </tt> (FlightGear sources) <tt>
:: install / </tt> (Directory where you will install the built binaries to) <tt>
::: launch.bat / </tt> (launch script if desired, see below) <tt>
:: osg / </tt> (OSG sources) <tt>
:: simgear / </tt> (SimGear sources) <tt>
:: windows-3rd-party /
:: build.bat / </tt> (build script, see below) <tt>
:: update.bat / </tt> (update script, see below)

== Building ==
=== Scripted Compilation ===
This script will allow you to build OpenSceneGraph, SimGear and FlightGear automatically.

If you would like debug info, change Release to RelWithDebInfo in the --config commands.

{{collapsible script
| type = Windows batch file
| title = The <code>build.bat</code> script for configuring and compiling OSG, SG, and FG
| lang = batch
| script =
SET PATH=%PATH%;%ProgramFiles%\CMake\bin
SET QT6SDK64=C:\Qt\6.x\msvc2022_64
SET CMAKE_TOOLCHAIN="Visual Studio 17 2022"
SET ROOT_DIR=C:\path\to\FlightGearBuild

md osg-build
md simgear-build
md flightgear-build

cd %ROOT_DIR%\osg-build

cmake %ROOT_DIR%\osg -G %CMAKE_TOOLCHAIN% -A x64 ^
-DACTUAL_3RDPARTY_DIR=%ROOT_DIR%\windows-3rd-party/msvc140/3rdParty.x64 ^
-DCMAKE_RELWITHDEBINFO_POSTFIX:STRING= ^
-DOSG_USE_UTF8_FILENAME:BOOL=ON ^
-DWIN32_USE_MP:BOOL=ON ^
-DCMAKE_INSTALL_PREFIX:PATH=%ROOT_DIR%\install
cmake --build . --config Release --target INSTALL

cd %ROOT_DIR%\simgear-build
cmake %ROOT_DIR%\simgear -G %CMAKE_TOOLCHAIN% -A x64 ^
-DOSG_FSTREAM_EXPORT_FIXED:BOOL=ON ^
-DCMAKE_INSTALL_PREFIX:PATH=%ROOT_DIR%\install
cmake --build . --config Release --target INSTALL

cd %ROOT_DIR%\flightgear-build
cmake %ROOT_DIR%\flightgear -G %CMAKE_TOOLCHAIN% -A x64 ^
-DCMAKE_INSTALL_PREFIX:PATH=%ROOT_DIR%\install ^
-DCMAKE_PREFIX_PATH=%QT6SDK64% ^
-DFG_BUILD_TYPE:STRING=Release ^
-DOSG_FSTREAM_EXPORT_FIXED:BOOL=ON

cmake --build . --config Release --target INSTALL

pause
| show = 1
}}

{{tip | 10/2024: When using VS2022 make sure your osg has this fix applied: https://gitlab.com/flightgear/openscenegraph/-/commit/31082758036c12738467a7210a17604275a79517<ref>https://sourceforge.net/p/flightgear/mailman/message/58821522/</ref>

Some folks encountered the following problem when building flightgear:
<syntaxhighlight>
CMake Error at CMakeLists.txt:283 (find_package):
By not providing "FindBoost.cmake" in CMAKE_MODULE_PATH this project has
asked CMake to find a package configuration file provided by "Boost", but
CMake did not find one.

Could not find a package configuration file provided by "Boost" with any of
the following names:

BoostConfig.cmake
boost-config.cmake

Add the installation prefix of "Boost" to CMAKE_PREFIX_PATH or set
"Boost_DIR" to a directory containing one of the above files. If "Boost"
provides a separate development package or SDK, be sure it has been
installed.
</syntaxhighlight>
This could be solved by doing the following in the top-level <code>CMakeLists.txt</code> of [https://sourceforge.net/p/flightgear/simgear/ci/next/tree/CMakeLists.txt#l16 simgear] and [https://sourceforge.net/p/flightgear/flightgear/ci/next/tree/CMakeLists.txt#l26 flightgear]:

In each file search for the line
<syntaxhighlight lang='CMake'>
cmake_policy(SET CMP0167 NEW)
</syntaxhighlight>
(it should be near the top of each file) and change from <code>NEW</code> to <code>OLD</code> like this<ref>https://sourceforge.net/p/flightgear/mailman/message/58815368/</ref>:
<syntaxhighlight lang='CMake'>
cmake_policy(SET CMP0167 OLD)
</syntaxhighlight>

In addition there are reports that a linking error occurs when building flightgear:
<syntaxhighlight>
pui.lib(puValue.obj) : error LNK2019: unresolved external symbol __imp_strncat referenced in function "protected: void__cdecl puValue::copy_stringval(char const *)" (?copy_stringval@puValue@@IEAAXPEBD@Z) [F:\git\flightgear-build\src\Main\fgfs.vcxproj]
F:\git\flightgear-build\src\Main\RelWithDebInfo\fgfs.exe : fatal error LNK1120: 1 unresolved externals [F:\git\flightgear-build\src\Main\fgfs.vcxproj]
</syntaxhighlight>
A workaround could be by changing the build type from <code>RelWithDebInfo</code> to <code>Release</code> when building osg, simgear and flightgear<ref>https://sourceforge.net/p/flightgear/mailman/message/58824438/</ref>:

In the <code>build.bat</code> change all three occurrences of
<syntaxhighlight lang='batch'>
cmake --build . --config RelWithDebInfo --target INSTALL
</syntaxhighlight>
to
<syntaxhighlight lang='batch'>
cmake --build . --config Release --target INSTALL
</syntaxhighlight>
}}

Before starting to use the script, you need to edit the top few lines of the script. You will have to:

# Set the path to your CMake installation.
# Ensure that the path to your QT SDK is correct for your version of MSVC.
# Ensure your toolchain version matches, e.g. "Visual Studio 16 2019" for MSVC 2019 or "Visual Studio 17 2022" for MSVC 2022.
# Set ROOT_DIR to the FlightGearBuild folder you created (the above directory structure)

==== Post-compilation: Launching FlightGear ====
'''In the debugger:'''
Open flightgear-build/FlightGear.sln. You can then perform all your development / debugging directly in VS. You normally only need to run build.bat again, if you update SimGear or OSG.

To launch FlightGear from Visual Studio, you can follow the following steps:
The first time only:
# Make sure you set your build type to RelWithDebInfo in the top bar.
# To start with the launcher, click on the small black arrow beside Local Windows Debugger to open 'fgfs debug properties'. Switch to debugging; add {{code|--launcher}} to the 'Command Arguments'. Click Apply and then OK.
# Press the green arrow (Local Windows Debugger) to start up FlightGear.
# The first time you'll have to choose where FGDATA is -- to do this, select the 'fgdata' directory you cloned at the start.

Thereafter, simply press the green arrow directly each time you want to start. If there are any local changes, it will recompile; alternatively it will start up directly. It will take a little longer to start as it loads symbols; however you also have the benefit that any segfaults will be caught allowing you to report them!

'''As a standard .exe:'''
NB these instructions overall are intended for setting up for development; there's a slightly more convoluted process for setting up for just plain flying (e.g. taking advantage of new features for aircraft development).

Essentially, Visual Studio doesn't copy in the DLLs into the /bin/ folder. It's also not ideal to manually copy in the DLLs as it can cause all sorts of issues. However, without the DLLs FlightGear won't work; therefore, you need to set the PATH so it knows where to look for them.
This launch script should work, put into your /install/bin/ folder:
{{collapsible script
| type = Windows batch file
| title = The <code>launch.bat</code> script for launching flightgear
| lang = batch
| script =
SET PATH=C:\path\to\FlightGearBuild\install\bin;C:\path\to\FlightGearBuild\windows-3rd-party\msvc140\3rdParty.x64\bin;C:\Qt\5.15.2\msvc2019_64\bin;%PATH%
SET FG_ROOT=C:\path\to\FlightGearBuild\fgdata
fgfs.exe --launcher
| show = 1
}}

Adjust the "path\to" references to suit your own personal installation, as well as the QT5 path.

=== Updating ===
To update FlightGear, in general, just run ''git pull'' on the source directories and then re-run the build.bat script -- it will update what it needs to, relatively quickly.

{{collapsible script
| type = Windows batch file
| title = The <code>update.bat</code> script for updating repositories
| lang = batch
| script =
SET ROOT_DIR=C:\path\to\FlightGearBuild

cd %ROOT_DIR%\osg
git pull

cd %ROOT_DIR%\fgdata
git pull

cd %ROOT_DIR%\flightgear
git pull

cd %ROOT_DIR%\simgear
git pull

cd %ROOT_DIR%\windows-3rd-party
git pull

pause
| show = 1
}}

=== Changing the Configuration ===
When the SimGear/FlightGear version numbers change, or you change configuration options (e.g. toggling Compositor, changing OSG versions, changing Qt versions) you do have to re-configure in CMake. To do this, it's usually safest to delete the simgear-build and flightgear-build folders and re-run the build.bat script, to ensure the build is clean. There is no need to delete osg-build unless changing OSG version.

In case of problems, most of the time deleting the simgear-build and flightgear-build folders and re-running the build.bat script will be sufficient.

{{building}}
[[fr:compiler flightear avec CMake - Windows]]
[[Category:Windows specific]]
[[Category:Hackathon Materials]]

Building using CMake - Windows

2026-06-14T02:42:14Z

Octal450: /* Scripted Compilation */ Fixed build script to stop sentry spammmm

This article is intended to give an overview of '''building FlightGear on modern Windows systems'''. It was created using Windows 11 and VS 2022. It ought to be transferable to earlier versions of the Windows OS and software.

As FlightGear is now 64-bit only, the guide only describes building on a 64-bit system.

== Required software ==
* [https://cmake.org/download/ CMake for Windows]. Download and install the Windows Win64-x64 Installer.
* [https://visualstudio.microsoft.com/downloads/ Microsoft Visual Studio 2022] (MSVC). The Community version is free. There is no need for the premium versions; none of their features are required to build FlightGear. The C++ compiler will not be installed by default. You either choose this component during installation or after installation by starting MSVC and trying to create a new C++ project. The one to download is "Desktop Development with C++". Make sure to have the latest version of the Windows SDK for your Windows version and the C++ Compiler checked. As of 8/5/2025, the option to select is "MSVC 2022 64-bit".
* [https://www.qt.io/download-open-source/ Qt6] for the [[FlightGear Qt launcher|Integrated Qt Launcher]]. Download the online installer to install and choose the latest version of Qt. Leave the default Developer and Designer Tools selection - these are needed for coding and compiling. Otherwise, here is [https://www.qt.io/offline-installers Offline Qt Downloads] for the optional offline-installer versions of Qt.
* [https://git-scm.com/download/win Git] to keep your build up to date. It also simplifies downloads of components. Optional, but can't recommend it enough!

== Obtaining source ==
{{Main article|FlightGear and Git}}
Throughout this article it is assumed that you have set up git clones of the various source repositories (FlightGear, SimGear, data...).
Using an organized directory (see below) will help significantly.

The commands to run are:

{{#tag:syntaxhighlight|
{{repo link
| site = gitlab
| cmd = git clone
| proj = flightgear
| repo = simgear
| type = git
| full = 1
}} simgear
{{repo link
| site = gitlab
| cmd = git clone
| proj = flightgear
| repo = flightgear
| type = git
| full = 1
}} flightgear
{{repo link
| site = gitlab
| cmd = git clone
| proj = flightgear
| repo = fgdata
| type = git
| full = 1
}} fgdata
{{repo link
| site = gitlab
| cmd = git clone
| proj = flightgear
| repo = windows-3rd-party
| type = git
| full = 1
}} windows-3rd-party
{{repo link
| site = gitlab
| cmd = git clone
| proj = flightgear
| repo = openscenegraph
| type = git
| full = 1
}} osg
| lang = "sh"
}}

After downloading these, I would suggest assembling a folder structure as below:

== Directory Tree ==
On Windows, assumptions on the directory structure are made to automate the discovery of dependencies. This recommended directory structure is described below. The components can be downloaded from the links above. If you do not use the recommended structure you will need to enter paths by hand and some parts may not input correctly.

Caveat -- spaces in the directory names will cause errors. It is best to make sure there are no spaces in the path anywhere.

<tt>
: FlightGearBuild / </tt> (Main root directory) <tt>
:: fgdata / </tt> (FlightGear data files) <tt>
:: flightgear / </tt> (FlightGear sources) <tt>
:: install / </tt> (Directory where you will install the built binaries to) <tt>
::: launch.bat / </tt> (launch script if desired, see below) <tt>
:: osg / </tt> (OSG sources) <tt>
:: simgear / </tt> (SimGear sources) <tt>
:: windows-3rd-party /
:: build.bat / </tt> (build script, see below) <tt>
:: update.bat / </tt> (update script, see below)

== Building ==
=== Scripted Compilation ===
This script will allow you to build OpenSceneGraph, SimGear and FlightGear automatically.

{{collapsible script
| type = Windows batch file
| title = The <code>build.bat</code> script for configuring and compiling OSG, SG, and FG
| lang = batch
| script =
SET PATH=%PATH%;%ProgramFiles%\CMake\bin
SET QT6SDK64=C:\Qt\6.x\msvc2022_64
SET CMAKE_TOOLCHAIN="Visual Studio 17 2022"
SET ROOT_DIR=C:\path\to\FlightGearBuild

md osg-build
md simgear-build
md flightgear-build

cd %ROOT_DIR%\osg-build

cmake %ROOT_DIR%\osg -G %CMAKE_TOOLCHAIN% -A x64 ^
-DACTUAL_3RDPARTY_DIR=%ROOT_DIR%\windows-3rd-party/msvc140/3rdParty.x64 ^
-DCMAKE_RELWITHDEBINFO_POSTFIX:STRING= ^
-DOSG_USE_UTF8_FILENAME:BOOL=ON ^
-DWIN32_USE_MP:BOOL=ON ^
-DCMAKE_INSTALL_PREFIX:PATH=%ROOT_DIR%\install
cmake --build . --config Release --target INSTALL

cd %ROOT_DIR%\simgear-build
cmake %ROOT_DIR%\simgear -G %CMAKE_TOOLCHAIN% -A x64 ^
-DOSG_FSTREAM_EXPORT_FIXED:BOOL=ON ^
-DCMAKE_INSTALL_PREFIX:PATH=%ROOT_DIR%\install
cmake --build . --config Release --target INSTALL

cd %ROOT_DIR%\flightgear-build
cmake %ROOT_DIR%\flightgear -G %CMAKE_TOOLCHAIN% -A x64 ^
-DCMAKE_INSTALL_PREFIX:PATH=%ROOT_DIR%\install ^
-DCMAKE_PREFIX_PATH=%QT6SDK64% ^
-DFG_BUILD_TYPE:STRING=Release ^
-DOSG_FSTREAM_EXPORT_FIXED:BOOL=ON

cmake --build . --config Release --target INSTALL

pause
| show = 1
}}

{{tip | 10/2024: When using VS2022 make sure your osg has this fix applied: https://gitlab.com/flightgear/openscenegraph/-/commit/31082758036c12738467a7210a17604275a79517<ref>https://sourceforge.net/p/flightgear/mailman/message/58821522/</ref>

Some folks encountered the following problem when building flightgear:
<syntaxhighlight>
CMake Error at CMakeLists.txt:283 (find_package):
By not providing "FindBoost.cmake" in CMAKE_MODULE_PATH this project has
asked CMake to find a package configuration file provided by "Boost", but
CMake did not find one.

Could not find a package configuration file provided by "Boost" with any of
the following names:

BoostConfig.cmake
boost-config.cmake

Add the installation prefix of "Boost" to CMAKE_PREFIX_PATH or set
"Boost_DIR" to a directory containing one of the above files. If "Boost"
provides a separate development package or SDK, be sure it has been
installed.
</syntaxhighlight>
This could be solved by doing the following in the top-level <code>CMakeLists.txt</code> of [https://sourceforge.net/p/flightgear/simgear/ci/next/tree/CMakeLists.txt#l16 simgear] and [https://sourceforge.net/p/flightgear/flightgear/ci/next/tree/CMakeLists.txt#l26 flightgear]:

In each file search for the line
<syntaxhighlight lang='CMake'>
cmake_policy(SET CMP0167 NEW)
</syntaxhighlight>
(it should be near the top of each file) and change from <code>NEW</code> to <code>OLD</code> like this<ref>https://sourceforge.net/p/flightgear/mailman/message/58815368/</ref>:
<syntaxhighlight lang='CMake'>
cmake_policy(SET CMP0167 OLD)
</syntaxhighlight>

In addition there are reports that a linking error occurs when building flightgear:
<syntaxhighlight>
pui.lib(puValue.obj) : error LNK2019: unresolved external symbol __imp_strncat referenced in function "protected: void__cdecl puValue::copy_stringval(char const *)" (?copy_stringval@puValue@@IEAAXPEBD@Z) [F:\git\flightgear-build\src\Main\fgfs.vcxproj]
F:\git\flightgear-build\src\Main\RelWithDebInfo\fgfs.exe : fatal error LNK1120: 1 unresolved externals [F:\git\flightgear-build\src\Main\fgfs.vcxproj]
</syntaxhighlight>
A workaround could be by changing the build type from <code>RelWithDebInfo</code> to <code>Release</code> when building osg, simgear and flightgear<ref>https://sourceforge.net/p/flightgear/mailman/message/58824438/</ref>:

In the <code>build.bat</code> change all three occurrences of
<syntaxhighlight lang='batch'>
cmake --build . --config RelWithDebInfo --target INSTALL
</syntaxhighlight>
to
<syntaxhighlight lang='batch'>
cmake --build . --config Release --target INSTALL
</syntaxhighlight>
}}

Before starting to use the script, you need to edit the top few lines of the script. You will have to:

# Set the path to your CMake installation.
# Ensure that the path to your QT SDK is correct for your version of MSVC.
# Ensure your toolchain version matches, e.g. "Visual Studio 16 2019" for MSVC 2019 or "Visual Studio 17 2022" for MSVC 2022.
# Set ROOT_DIR to the FlightGearBuild folder you created (the above directory structure)

==== Post-compilation: Launching FlightGear ====
'''In the debugger:'''
Open flightgear-build/FlightGear.sln. You can then perform all your development / debugging directly in VS. You normally only need to run build.bat again, if you update SimGear or OSG.

To launch FlightGear from Visual Studio, you can follow the following steps:
The first time only:
# Make sure you set your build type to RelWithDebInfo in the top bar.
# To start with the launcher, click on the small black arrow beside Local Windows Debugger to open 'fgfs debug properties'. Switch to debugging; add {{code|--launcher}} to the 'Command Arguments'. Click Apply and then OK.
# Press the green arrow (Local Windows Debugger) to start up FlightGear.
# The first time you'll have to choose where FGDATA is -- to do this, select the 'fgdata' directory you cloned at the start.

Thereafter, simply press the green arrow directly each time you want to start. If there are any local changes, it will recompile; alternatively it will start up directly. It will take a little longer to start as it loads symbols; however you also have the benefit that any segfaults will be caught allowing you to report them!

'''As a standard .exe:'''
NB these instructions overall are intended for setting up for development; there's a slightly more convoluted process for setting up for just plain flying (e.g. taking advantage of new features for aircraft development).

Essentially, Visual Studio doesn't copy in the DLLs into the /bin/ folder. It's also not ideal to manually copy in the DLLs as it can cause all sorts of issues. However, without the DLLs FlightGear won't work; therefore, you need to set the PATH so it knows where to look for them.
This launch script should work, put into your /install/bin/ folder:
{{collapsible script
| type = Windows batch file
| title = The <code>launch.bat</code> script for launching flightgear
| lang = batch
| script =
SET PATH=C:\path\to\FlightGearBuild\install\bin;C:\path\to\FlightGearBuild\windows-3rd-party\msvc140\3rdParty.x64\bin;C:\Qt\5.15.2\msvc2019_64\bin;%PATH%
SET FG_ROOT=C:\path\to\FlightGearBuild\fgdata
fgfs.exe --launcher
| show = 1
}}

Adjust the "path\to" references to suit your own personal installation, as well as the QT5 path.

=== Updating ===
To update FlightGear, in general, just run ''git pull'' on the source directories and then re-run the build.bat script -- it will update what it needs to, relatively quickly.

{{collapsible script
| type = Windows batch file
| title = The <code>update.bat</code> script for updating repositories
| lang = batch
| script =
SET ROOT_DIR=C:\path\to\FlightGearBuild

cd %ROOT_DIR%\osg
git pull

cd %ROOT_DIR%\fgdata
git pull

cd %ROOT_DIR%\flightgear
git pull

cd %ROOT_DIR%\simgear
git pull

cd %ROOT_DIR%\windows-3rd-party
git pull

pause
| show = 1
}}

=== Changing the Configuration ===
When the SimGear/FlightGear version numbers change, or you change configuration options (e.g. toggling Compositor, changing OSG versions, changing Qt versions) you do have to re-configure in CMake. To do this, it's usually safest to delete the simgear-build and flightgear-build folders and re-run the build.bat script, to ensure the build is clean. There is no need to delete osg-build unless changing OSG version.

In case of problems, most of the time deleting the simgear-build and flightgear-build folders and re-running the build.bat script will be sufficient.

{{building}}
[[fr:compiler flightear avec CMake - Windows]]
[[Category:Windows specific]]
[[Category:Hackathon Materials]]

Building using CMake - Windows

2026-06-11T05:06:55Z

Octal450: /* Scripted Compilation */

This article is intended to give an overview of '''building FlightGear on modern Windows systems'''. It was created using Windows 11 and VS 2022. It ought to be transferable to earlier versions of the Windows OS and software.

As FlightGear is now 64-bit only, the guide only describes building on a 64-bit system.

== Required software ==
* [https://cmake.org/download/ CMake for Windows]. Download and install the Windows Win64-x64 Installer.
* [https://visualstudio.microsoft.com/downloads/ Microsoft Visual Studio 2022] (MSVC). The Community version is free. There is no need for the premium versions; none of their features are required to build FlightGear. The C++ compiler will not be installed by default. You either choose this component during installation or after installation by starting MSVC and trying to create a new C++ project. The one to download is "Desktop Development with C++". Make sure to have the latest version of the Windows SDK for your Windows version and the C++ Compiler checked. As of 8/5/2025, the option to select is "MSVC 2022 64-bit".
* [https://www.qt.io/download-open-source/ Qt6] for the [[FlightGear Qt launcher|Integrated Qt Launcher]]. Download the online installer to install and choose the latest version of Qt. Leave the default Developer and Designer Tools selection - these are needed for coding and compiling. Otherwise, here is [https://www.qt.io/offline-installers Offline Qt Downloads] for the optional offline-installer versions of Qt.
* [https://git-scm.com/download/win Git] to keep your build up to date. It also simplifies downloads of components. Optional, but can't recommend it enough!

== Obtaining source ==
{{Main article|FlightGear and Git}}
Throughout this article it is assumed that you have set up git clones of the various source repositories (FlightGear, SimGear, data...).
Using an organized directory (see below) will help significantly.

The commands to run are:

{{#tag:syntaxhighlight|
{{repo link
| site = gitlab
| cmd = git clone
| proj = flightgear
| repo = simgear
| type = git
| full = 1
}} simgear
{{repo link
| site = gitlab
| cmd = git clone
| proj = flightgear
| repo = flightgear
| type = git
| full = 1
}} flightgear
{{repo link
| site = gitlab
| cmd = git clone
| proj = flightgear
| repo = fgdata
| type = git
| full = 1
}} fgdata
{{repo link
| site = gitlab
| cmd = git clone
| proj = flightgear
| repo = windows-3rd-party
| type = git
| full = 1
}} windows-3rd-party
{{repo link
| site = gitlab
| cmd = git clone
| proj = flightgear
| repo = openscenegraph
| type = git
| full = 1
}} osg
| lang = "sh"
}}

After downloading these, I would suggest assembling a folder structure as below:

== Directory Tree ==
On Windows, assumptions on the directory structure are made to automate the discovery of dependencies. This recommended directory structure is described below. The components can be downloaded from the links above. If you do not use the recommended structure you will need to enter paths by hand and some parts may not input correctly.

Caveat -- spaces in the directory names will cause errors. It is best to make sure there are no spaces in the path anywhere.

<tt>
: FlightGearBuild / </tt> (Main root directory) <tt>
:: fgdata / </tt> (FlightGear data files) <tt>
:: flightgear / </tt> (FlightGear sources) <tt>
:: install / </tt> (Directory where you will install the built binaries to) <tt>
::: launch.bat / </tt> (launch script if desired, see below) <tt>
:: osg / </tt> (OSG sources) <tt>
:: simgear / </tt> (SimGear sources) <tt>
:: windows-3rd-party /
:: build.bat / </tt> (build script, see below) <tt>
:: update.bat / </tt> (update script, see below)

== Building ==
=== Scripted Compilation ===
This script will allow you to build OpenSceneGraph, SimGear and FlightGear automatically.

{{collapsible script
| type = Windows batch file
| title = The <code>build.bat</code> script for configuring and compiling OSG, SG, and FG
| lang = batch
| script =
SET PATH=%PATH%;%ProgramFiles%\CMake\bin
SET QT6SDK64=C:\Qt\6.x\msvc2022_64
SET CMAKE_TOOLCHAIN="Visual Studio 17 2022"
SET ROOT_DIR=C:\path\to\FlightGearBuild
SET FG_BUILD_TYPE="Release"

md osg-build
md simgear-build
md flightgear-build

cd %ROOT_DIR%\osg-build

cmake %ROOT_DIR%\osg -G %CMAKE_TOOLCHAIN% -A x64 ^
-DACTUAL_3RDPARTY_DIR=%ROOT_DIR%\windows-3rd-party/msvc140/3rdParty.x64 ^
-DCMAKE_RELWITHDEBINFO_POSTFIX:STRING= ^
-DOSG_USE_UTF8_FILENAME:BOOL=ON ^
-DWIN32_USE_MP:BOOL=ON ^
-DCMAKE_INSTALL_PREFIX:PATH=%ROOT_DIR%\install
cmake --build . --config RelWithDebInfo --target INSTALL

cd %ROOT_DIR%\simgear-build
cmake %ROOT_DIR%\simgear -G %CMAKE_TOOLCHAIN% -A x64 ^
-DOSG_FSTREAM_EXPORT_FIXED:BOOL=ON ^
-DCMAKE_INSTALL_PREFIX:PATH=%ROOT_DIR%\install
cmake --build . --config RelWithDebInfo --target INSTALL

cd %ROOT_DIR%\flightgear-build
cmake %ROOT_DIR%\flightgear -G %CMAKE_TOOLCHAIN% -A x64 ^
-DCMAKE_INSTALL_PREFIX:PATH=%ROOT_DIR%\install ^
-DCMAKE_PREFIX_PATH=%QT6SDK64% ^
-D FG_BUILD_TYPE=$FG_BUILD_TYPE ^
-DOSG_FSTREAM_EXPORT_FIXED:BOOL=ON

cmake --build . --config RelWithDebInfo --target INSTALL

pause
| show = 1
}}

{{tip | 10/2024: When using VS2022 make sure your osg has this fix applied: https://gitlab.com/flightgear/openscenegraph/-/commit/31082758036c12738467a7210a17604275a79517<ref>https://sourceforge.net/p/flightgear/mailman/message/58821522/</ref>

Some folks encountered the following problem when building flightgear:
<syntaxhighlight>
CMake Error at CMakeLists.txt:283 (find_package):
By not providing "FindBoost.cmake" in CMAKE_MODULE_PATH this project has
asked CMake to find a package configuration file provided by "Boost", but
CMake did not find one.

Could not find a package configuration file provided by "Boost" with any of
the following names:

BoostConfig.cmake
boost-config.cmake

Add the installation prefix of "Boost" to CMAKE_PREFIX_PATH or set
"Boost_DIR" to a directory containing one of the above files. If "Boost"
provides a separate development package or SDK, be sure it has been
installed.
</syntaxhighlight>
This could be solved by doing the following in the top-level <code>CMakeLists.txt</code> of [https://sourceforge.net/p/flightgear/simgear/ci/next/tree/CMakeLists.txt#l16 simgear] and [https://sourceforge.net/p/flightgear/flightgear/ci/next/tree/CMakeLists.txt#l26 flightgear]:

In each file search for the line
<syntaxhighlight lang='CMake'>
cmake_policy(SET CMP0167 NEW)
</syntaxhighlight>
(it should be near the top of each file) and change from <code>NEW</code> to <code>OLD</code> like this<ref>https://sourceforge.net/p/flightgear/mailman/message/58815368/</ref>:
<syntaxhighlight lang='CMake'>
cmake_policy(SET CMP0167 OLD)
</syntaxhighlight>

In addition there are reports that a linking error occurs when building flightgear:
<syntaxhighlight>
pui.lib(puValue.obj) : error LNK2019: unresolved external symbol __imp_strncat referenced in function "protected: void__cdecl puValue::copy_stringval(char const *)" (?copy_stringval@puValue@@IEAAXPEBD@Z) [F:\git\flightgear-build\src\Main\fgfs.vcxproj]
F:\git\flightgear-build\src\Main\RelWithDebInfo\fgfs.exe : fatal error LNK1120: 1 unresolved externals [F:\git\flightgear-build\src\Main\fgfs.vcxproj]
</syntaxhighlight>
A workaround could be by changing the build type from <code>RelWithDebInfo</code> to <code>Release</code> when building osg, simgear and flightgear<ref>https://sourceforge.net/p/flightgear/mailman/message/58824438/</ref>:

In the <code>build.bat</code> change all three occurrences of
<syntaxhighlight lang='batch'>
cmake --build . --config RelWithDebInfo --target INSTALL
</syntaxhighlight>
to
<syntaxhighlight lang='batch'>
cmake --build . --config Release --target INSTALL
</syntaxhighlight>
}}

Before starting to use the script, you need to edit the top few lines of the script. You will have to:

# Set the path to your CMake installation.
# Ensure that the path to your QT SDK is correct for your version of MSVC.
# Ensure your toolchain version matches, e.g. "Visual Studio 16 2019" for MSVC 2019 or "Visual Studio 15 2017" for MSVC 2017.
# Set ROOT_DIR to the FlightGearBuild folder you created (the above directory structure)

==== Post-compilation: Launching FlightGear ====
'''In the debugger:'''
Open flightgear-build/FlightGear.sln. You can then perform all your development / debugging directly in VS. You normally only need to run build.bat again, if you update SimGear or OSG.

To launch FlightGear from Visual Studio, you can follow the following steps:
The first time only:
# Make sure you set your build type to RelWithDebInfo in the top bar.
# To start with the launcher, click on the small black arrow beside Local Windows Debugger to open 'fgfs debug properties'. Switch to debugging; add {{code|--launcher}} to the 'Command Arguments'. Click Apply and then OK.
# Press the green arrow (Local Windows Debugger) to start up FlightGear.
# The first time you'll have to choose where FGDATA is -- to do this, select the 'fgdata' directory you cloned at the start.

Thereafter, simply press the green arrow directly each time you want to start. If there are any local changes, it will recompile; alternatively it will start up directly. It will take a little longer to start as it loads symbols; however you also have the benefit that any segfaults will be caught allowing you to report them!

'''As a standard .exe:'''
NB these instructions overall are intended for setting up for development; there's a slightly more convoluted process for setting up for just plain flying (e.g. taking advantage of new features for aircraft development).

Essentially, Visual Studio doesn't copy in the DLLs into the /bin/ folder. It's also not ideal to manually copy in the DLLs as it can cause all sorts of issues. However, without the DLLs FlightGear won't work; therefore, you need to set the PATH so it knows where to look for them.
This launch script should work, put into your /install/bin/ folder:
{{collapsible script
| type = Windows batch file
| title = The <code>launch.bat</code> script for launching flightgear
| lang = batch
| script =
SET PATH=C:\path\to\FlightGearBuild\install\bin;C:\path\to\FlightGearBuild\windows-3rd-party\msvc140\3rdParty.x64\bin;C:\Qt\5.15.2\msvc2019_64\bin;%PATH%
SET FG_ROOT=C:\path\to\FlightGearBuild\fgdata
fgfs.exe --launcher
| show = 1
}}

Adjust the "path\to" references to suit your own personal installation, as well as the QT5 path.

=== Updating ===
To update FlightGear, in general, just run ''git pull'' on the source directories and then re-run the build.bat script -- it will update what it needs to, relatively quickly.

{{collapsible script
| type = Windows batch file
| title = The <code>update.bat</code> script for updating repositories
| lang = batch
| script =
SET ROOT_DIR=C:\path\to\FlightGearBuild

cd %ROOT_DIR%\osg
git pull

cd %ROOT_DIR%\fgdata
git pull

cd %ROOT_DIR%\flightgear
git pull

cd %ROOT_DIR%\simgear
git pull

cd %ROOT_DIR%\windows-3rd-party
git pull

pause
| show = 1
}}

=== Changing the Configuration ===
When the SimGear/FlightGear version numbers change, or you change configuration options (e.g. toggling Compositor, changing OSG versions, changing Qt versions) you do have to re-configure in CMake. To do this, it's usually safest to delete the simgear-build and flightgear-build folders and re-run the build.bat script, to ensure the build is clean. There is no need to delete osg-build unless changing OSG version.

In case of problems, most of the time deleting the simgear-build and flightgear-build folders and re-running the build.bat script will be sufficient.

{{building}}
[[fr:compiler flightear avec CMake - Windows]]
[[Category:Windows specific]]
[[Category:Hackathon Materials]]

Airbus A320 family/info

2026-06-05T08:08:04Z

Octal450:

<includeonly>{{infobox aircraft
| name = Airbus A320 family
| hangar = fgaddon
| aircraft = A320-family
| image = A320-family.jpg
| image2 = A320VirtualCockpit.png
| alt2 = The 3d [[cockpit]] of the A320-family
| type = Airliner
| config = Low wing aircraft/Monoplane aircraft/Retractable gear aircraft/Tricycle landing gear aircraft
| propulsion = Twinjet
| manufacturer = Airbus
| authors = Josh Davidson (Octal450)/legoboyvdlp/Nia/Matthew Maring (hayden2000)/Thorsten Herrmann (TH-555)/Semir Gebran (CaptB)
| fdm = JSBsim
| fgname = A320-200-CFM/A320-200-IAE/A320neo-CFM/A320neo-PW
| status-fdm = 5
| status-systems = 5
| status-cockpit = 5
| status-model = 5
| ready = checklist/canvas
| navbar = 1
| devel-repo = {{github url|user=legoboyvdlp|repo=A320-family}}
}}</includeonly><noinclude>
This is the aircraft infobox subpage of the [[Airbus A320 family]].
[[Category:Aircraft infobox documentation]]
</noinclude>

Airbus A330/info

2026-06-05T08:03:32Z

Octal450:

<includeonly>{{infobox aircraft
| name = Airbus A330
| hangar = JMaverick16
| aircraft = Airbus_A330
| image = Fgfs-20230726152543.png
| alt = An Airbus A330 cruises in the dusk

| image2 = IDG-A33X-VC.jpg
| alt2 = The Virtual Cockpit
| type = Airliner
| config = Low wing aircraft/Monoplane aircraft/Retractable gear aircraft/Tricycle landing gear aircraft
| propulsion = Twinjet
| manufacturer = Airbus
| authors = Josh Davidson/legoboyvdlp/Thorsten Herrmann (TH-555)/J Maverick 16
| fdm = JSBsim
| status-fdm = 4
| status-systems = 4
| status-cockpit = 4
| status-model = 4
| navbar = 1
| ready = checklist/canvas/airrefuel
| forumtid = 33022
}}</includeonly><noinclude>
This is the aircraft infobox subpage of the [[Airbus_A330]].
[[Category:Aircraft infobox documentation]]
</noinclude>

FlightGear Newsletter May 2026

2026-06-01T05:20:42Z

Octal450: /* Updated aircraft */

{{User:Skybike/Template:Newsletter-header-translate|2026-05}}
{{TOC_right|limit=2}}
''We would like to emphasize that the monthly newsletter cannot live without the contributions of FlightGear users and developers. Everyone with a wiki account (free to register) is welcome to contribute to the newsletter. If you know about any FlightGear related news or projects such as for example updated scenery or aircraft, please do feel invited to add such news to the newsletter.''

''The new Visual Editor makes editing the wiki as simple as using a Word-processor, and even easier than using the forum as you don't even need to know the syntax for a url. Just hit the 'edit' link and start.''

== Development news ==


[[File:2024.2_HDR_PBR_rendering.png|400px|thumb|HDR and PBR rendered scene.]][[File:PBR-rendered cockpit 2024.2.png|400px|thumb|PBR rendered cockpit.]]
The 2024.2 version, which is currently under development, adds [[FlightGear and OpenGL Core Profile|core profile support]], [[HDR]] and PBR, and a new [[Canvas GUI]] replacing [[PUI]], delivering near cinema-grade image quality for FlightGear, narrowing the gap between FG and commercial simulators.



== In the hangar ==

You can now report and track FGAddon (launcher) aircraft bugs over in the "Aircraft Issues" project, on the FlightGear bug tracker! If there is already an existing bug tracker or repository for an aircraft, we would prefer if issues were reported there instead. But if you are in doubt, create an issue and we can triage it and forward it on to the appropriate place, if that is not the FGAddon tracker. A link to the bug tracker can be found on the left of every wiki page, and at the top of every forum page. If you have a spare hour or 2, and fancy getting involved, we would love for you to come on over, choose an issue, and have a crack at fixing it!


=== Updated aircraft ===
The [[McDonnell Douglas MD-11]] has received an advanced new load manager for managing fuel and payload amongst other updates. There are tweaks to the manager based on flying the passenger or freighter.

[[File:MD-11-Load-Manager.jpg|500px|MD-11 LM]]

=== Liveries ===
The default livery of [[Airbus A320 family|A320-271N (PW1100G)]] in the dev branch has been changed to Lufthansa, due to Spirit's shutdown. <ref>https://github.com/legoboyvdlp/A320-family/pull/403</ref>



== Scenery corner ==




















== Community news ==



=== Wiki updates ===
The FlightGear [[FlightGear wiki|wiki]] has been renovated by contributors since the end of April 2026, including the cleanup of content, the removal of old information (e.g., [[FGRun]]), and the update of existing pages (e.g., [[New to FlightGear]]).

In addition, a book called [https://en.wikibooks.org/wiki/FlightGear_Flight_Simulator FlightGear Flight Simulator] has been created on Wikibooks based on the content of this wiki.


== Multiplayer events ==









== Screenshot of the Month ==

If you want to participate in the screenshot contest, you can submit your candidate to the {{forum link|title=this|f=88|t=}}. Be sure to see the first post for participation rules. For purposes of convenience and organization, at the end of the month or after 20 entries have been submitted, a new forum topic will be started containing all shots in an easy-to-view layout. The voting will then take place there.

{{Appendix}}

[[Category:Changes after 2024.1]]
[[Category:FlightGear Newsletter|2026 05]]


[[fr:FlightGear Newsletter May 2026]]

Tupolev Tu-134/info

2026-05-31T23:16:27Z

Octal450: Match rating to what is in FGAddon -set

<includeonly>{{infobox aircraft
| name = Tupolev Tu-134
| hangar = fgaddon
| aircraft = Tu-134
| image = Tu134 aeroflot.png
| type = Airliner
| config = Low wing aircraft
| propulsion = Twinjet
| manufacturer = Tupolev
| authors = Emmanuel Baranger (3D & FDM)/Buckaroo (FDM)/Cossack90 (Liveries, Translation)
| fdm = YASim
| fgname = tu134
| status-fdm = 4
| status-systems = 1
| status-cockpit = 2
| status-model = 4
| devel-hangar = helijah
| forumtid = 15908
| navbar = 1
}}</includeonly><noinclude>
This is the aircraft infobox subpage of the [[Tupolev Tu-134]].
[[Category:Aircraft infobox documentation]]
</noinclude>

Bombardier CRJ700 series

2026-05-31T22:49:57Z

Octal450: /* My personal wishlist */

{{:{{PAGENAME}}/info}}
[[File:CRJ700-cockpit-night.jpg|The cockpit at night, demonstrating night lighting capabilities|thumb|350px|right]]
[[File:CRJ700-cabin-night.jpg|The interior cabin, also at night|thumb|350px|right]]

The '''Bombardier CRJ700 series''' is a family of 70- to 100- seat regional jet airliners manufactured by Bombardier Aerospace. Its primary competition is the Embraer E-jet series. The family consists of the Bombardier CRJ700, CRJ900, and CRJ1000. The CRJ700 series was developed from the [[Bombardier CRJ-200LR|Bombardier CRJ200]], and remains one of the most popular regional airliner series in the world.

It belongs to the few aircraft for FlightGear that feature a ''[[walk view]]''.

=Variants=

* CRJ700 - the original CRJ700
* CRJ700ER - extended range version
* CRJ700LR - long-range version
* CRJ900 - the first stretch of the airframe
* CRJ900ER - extended range version
* CRJ900LR - long-range version
* CRJ1000 - the final stretch of the airframe
* CRJ1000 EuroLite - low-range/low-cost version targeted at European operators
* CRJ1000ER - extended range version

=Aircraft help=

HTML documentation is included in the Docs/ folder.

==Key commands==

{| class="keytable"
! Key
! Function
|-
! colspan="2" | Speedbrakes/spoilers
|-
| {{key press|Ctrl|B}}
| Cycle speedbrake setting
|-
| {{key press|j}}
| Decrease ground lift dump setting
|-
| {{key press|k}}
| Increase ground lift dump setting
|-
! colspan="2"|Engines
|-
| {{key press|Ctrl|Del}}
| Arm/disarm thrust reversers
|-
| {{key press|Del}}
| Toggle thrust reversers
|-
! colspan="2" | Autopilot
|-
| {{key press|Ctrl|A}}
| Toggle autopilot altitude mode
|-
| {{key press|Ctrl|F}}
|Engage/disengage autopilot
|-
| {{key press|Ctrl|G}}
| Toggle autopilot approach mode
|-
| {{key press|Ctrl|H}}
| Toggle autopilot heading mode
|-
| {{key press|Ctrl|N}}
| Toggle autopilot NAV mode
|-
| {{key press|Ctrl|P}}
| Set autopilot basic pitch mode
|-
| {{key press|Ctrl|W}}
| Set autopilot basic heading/roll mode
|-
| {{key press|F6}}
| Cycle NAV source
|-
! colspan="2" | Tiller/Nose gear steering
|-
| {{key press|q}}
| Steer tiller left
|-
| {{key press|Shift|Q}}
| Set tiller to full left
|-
| {{key press|w}}
| Center tiller
|-
| {{key press|Shift|W}}
| Pop up tiller dialog
|-
| {{key press|e}}
| Steer tiller right
|-
| {{key press|Shift|E}}
| Set tiller to full right
|-
! colspan="2" | Walk view
|-
| {{key press|r}}
| Walk forward toward view
|-
| {{key press|Shift|R}}
| Run forward toward view
|-
| {{key press|f}}
| Walk backwards from view
|-
| {{key press|y}}
| View point down
|-
| {{key press|Y}}
| View point up
|}

==Simplified procedures==
===Startup===
[[File:Start-123.png|thumb|right|CRJ700 Startup (1,2,3)]]
#Battery switch ... on
#APU start/stop switch ... on
#Bleed air source ... automatic
#Fuel Pumps ... enable
#Engine 1 thrust lever ... idle
#Engine 1 start sequence ... initiated
#Engine 2 thrust lever ... idle
#Engine 2 start sequence ... initiated
#Engine 1 electric generator ... on
#Engine 2 electric generator ... on
#APU start/stop switch ... off

===Takeoff===
#Flaps/slats ... 8 or 20
#Landing lights ... on
#Engine thrust modes ... TO/GA

===Climb and cruise===
#Engine thrust modes ... climb
Nominal cruise speed Mach 0.78 (0.80 for CRJ900)

===Approach and landing===
Remain below 250 knots below 10,000 feet at all times
#Thrust reversers ... armed
#Obey speed limits for flaps and gear extension
#Flaps/slats on final ... 45

===Shutdown===
#Parking break ... set
#External power ... select
#Engine thrust levers ... shutoff
#Engine 1 electric generator ... off
#Engine 2 electric generator ... off

=Downloading=

The latest version is always available on the official FlightGear aircraft download page and will be committed regularly to [[FGAddon]].

The latest development version at GitHub can also be downloaded [https://github.com/d-jsb/CRJ700-family/archive/master.zip here].

=Aircraft of the Week/Month=

The CRJ700 was reviewed by Thorsten R as part of the "Aircraft of the Week/Month" feature on the FlightGear Forums.

====Model====

The 3d cockpit of the CRJ-700 is very detailed and contains not only functionality on the main panel but also on the central console and an overhead panel. However, as often seen, the cockpit surfaces not covered by instrumentation are very simply textured by a monochromatic grey color - a more natural texture resembling a real material with some wear and tear could add a lot here.

[http://www.phy.duke.edu/~trenk/pics/crj700-cockpit.jpg View image]

There is a lot of functionality in the cockpit - a startup procedure using the APU is supported as well as a full set of external lights and no-smoking and seat belt signs for the passengers. A nice touch of the model is that it also contains an interior view of the cabin in which the signs can be observed. Switches and knobs are usually animated, and the clickspots are placed fairly intuitively. The MFD's all have various selectable functions.

The exterior model of the aircraft is also very nicely done, contains good animations and shows all the light switch settings in the cockpit faithfully. An option to switch livery exists as well.

[http://www.phy.duke.edu/~trenk/pics/crj700-model.jpg View image]

====Flight characteristics====

The FDM of the CRJ-700 is quite plausible for an airliner of its size. I haven't really tested the behaviour at the edge of the performance envelope, but during normal operations, the plane behaves well and reaches basic performance characteristics. All in all, the plane is an airliner (albeit a small one) - it turns slowly, it does not descent rapidly without picking up a lot of excess speed and all maneuvers need to be planned well in advance. Having said that, it's actually fun to fly.

I found the AP nicely tuned and able to fly turns, climb or dive at all altitudes without oscillations or weird behaviour. Unfortunately, the support for AP modes involving navaids is not as good: While I could home in on a VOR station, the AP seems to be tracking the station rather than the chosen radial, i.e. the angle under which I approached the station kept changing. Also, I was unable to intercept an ILS glideslope automatically. However, the plane can be operated well in IFR conditions just using the instruments to display the navaid signals and the heading and altitude modes of the AP to control the plane.

====My personal wishlist====

Fixing the AP to a more consistent behaviour with navaids would be high on my priority list. Some more natural texturing in the cockpit would also be nice. I realize that the CRJ-700 is a fairly recent addition to the aircraft repository of Flightgear - but I like where the model is going very much.

====Things to experience====

Try flying at night - the CRJ-700 has one of the best light concepts I've ever seen. The instrument lights are very beautifully done and can be dimmed at need, the cabin lights likewise, and all lighting is visible both from internal and external views.

''Editor's note: The autopilot VOR-LOC/ILS holds have been fixed as of CRJ700 v1.0.2.''

=Development status/Issues/Todo=
==Key features==
* Startup and shutdown procedures
* Mostly complete cockpit
* Realistic autopilot
* Functional flight management system (FMS), advisory-only vertical navigation system (VNAV), and control display unit (CDU)
* Emergency procedures with ram air turbine (RAT) and auxiliary power unit (APU)
* Small library of tutorials
* Cockpit, cabin, and exterior model lightmaps
* Reflection shader on the engines
* Developed aircraft systems
* Tiller steering system

==Todo==
For rating information, see [[Formalizing Aircraft Status]].
===FDM (current rating 3)===
* Make something a little more refined than my [[YASim]] solution (any [[JSBSim]] masters?)
===Exterior (current rating 4)===
* Add minor elements like antennas, ram air turbine, improve gear bay texturing and geometry
* More liveries!
===Flight deck (current rating 4)===
* Improve texturing
* Model circuit breakers
===Systems (current rating 3)===
* Add more pages to EICAS

== Development (section added May 2015) ==
D-JSB et al. work on the CRJ700 family.

=== Status without any particular order ===
==== done ====
* Some bugfixes (e.g. MFD wind indicator, nav pointers, MFD symbols)
* Removed 2D panel which depended on Boing 737-300
* More views (cabin windows, gear)
* OHP switches / switchlights (gimmick: implemented the light test button)
* Details of auto pilot panel behaviour like push function of CRS and HDG
* Modified slats/flaps indicator on EICAS
* APU details on EICAS
* EICAS pages for doors
* Simulation of hydraulic system
* EICAS pages for hydraulic system
* Extend failures dialog (hydraulics)
* Re-implement the electrical system (AC and DC).
* Add cargo doors to model
* Add APU door to model

==== In progress / testing ====
* Update of documentation

==== Planed ====
* Canvas implementation of glas cockpit

== Canvas implementation (planed) ==
[[CRJ 700 family canvas ]]

=External links=
* [http://en.wikipedia.org/wiki/Bombardier_CRJ700_series Bombardier CRJ700 series at Wikipedia]
* [http://forum.flightgear.org/viewtopic.php?t=11863 Development thread at the FlightGear Forums]
* [http://www.smartcockpit.com/data/...700.../HGS_00_Pilots_Guide_CRJ_00.pdf GHS Pilots Guide CRJ]
* [http://aligero.us/files/FMS%204200.pdf FMS 4200 Intro]
* [http://www.4shared.com/get/Q_rDeIsz/Collins_FMS-4200_Flight_Manage.html FMS-4200 Manual]
* [https://360.schnurstracks.de/panoramafotografie/cockpit/cockpit-panorama-bombardier.html?initvars.internlink=1 360° cockpit photo]

{{Template:Bombardier}}
[[Category: Aircraft with cabin view]]

Transponder

2026-05-25T19:42:13Z

Octal450: /* Configuration in FlightGear */

'''Transponders''' are radio beacons which make [[aircraft]] more identifiable on [[ATC]] displays and systems and by other aircrafts. Modern transponders support transmitting additional data such as an identification ('squawk') code and aircraft altitude. See more at {{wikipedia|Transponder (aeronautics)}}.

== ID Codes ==
* The ‘squawk code’ 7000 is used for VFR flights in Europe, while in the US, 1200 is used for the same purpose.
* IFR aircraft will be assigned an “attributed code” by ATC services at clearance delivery time, typically during startup. The code is selected by ATC from a regionally allocated pool of currently unused codes.
* NATO and other military aircraft sharing civil airspace use several codes from conventional tables, such as “0300 or 0400 - NATO - CAOC 9 Exercises (activated by NOTAM)” and “3500 - NATO - Aircraft receiving a service from AEW aircraft.”
* An aircraft unable to use voice radio communications will select the special code 7600.
* An aircraft experiencing an emergency (technical, medical, etc.) will select the special code 7700.

While some codes are used worldwide, such as the emergency codes, other codes have different regional meanings, like the special code ‘0000’.

* In the UK, by convention, the code ‘0000’ may be automatically selected by some transponders to report a transponder malfunction; pilots are not allowed to select it manually.
* In Europe, it is no longer used and its use has become prohibited. In the early days of transponders (Mode A), it was used to indicate “no ORCAM code inserted yet.” Its use today is strictly forbidden.
* In the US, it is a bit more confusing:
** It is used for some military interception operations.
** It may be used by ARTCC en route control centers for aircraft in cruise within controlled airspace when no more unassigned ORCAM codes are available.
** The Department of Transportation and the FAA have advocated, since 1981, for abandoning its use and moving toward full prohibition.

See: https://en.wikipedia.org/wiki/List_of_transponder_codes

Codes are composed of a sequence of 4 digits, each with 8 possible values, ranging from [ 0 ][ 0 ][ 0 ][ 0 ] to [ 7 ][ 7 ][ 7 ][ 7 ].

Codes specifically define either:

* 1 aircraft, and 1 aircraft only;
* 1 particular situation.

== Special Codes ==
Codes ending in “00” define situations.

* 7500 - Hijacking
* 7600 - Unable to use voice radio communications - “Communications failure”
* 7700 - Emergency (technical / medical)

These codes do not identify 1 aircraft only.

Codes ending with other numbers (0 to 7) identify 1 and only 1 aircraft.

* They are assigned by ATC, usually by radio during departure clearance.
* They can be changed during the flight to accommodate traffic management needs.

Codes identifying 1 and only 1 aircraft are called discrete or conspicuous codes.

Codes defining situations are called non-discrete or non-conspicuous codes.

This is also why transponder codes are called Conspicuity Codes.

See: https://skybrary.aero/articles/discrete-and-non-discrete-ssr-codes

== ORCAM method ==
There are far more aircraft to manage than available squawk codes.

To solve this problem, the ORCAM method is used.

ORCAM stands for Originating Regional Code Allocation Method.

Every region, airspace, airport, or service (such as military operations) is assigned a range of codes.

When an aircraft leaves one controlled zone and enters another, if, the current code conflicts with another code already in use nearby, ATC will ask the aircraft to recycle the code and select a new unused one.

ORCAM is a method, not a “table,” although the method excludes a subset of fixed codes from its management, and those are defined in tables.

Note that the following table is valid for the UK only; the US and Europe use some different assignments.

https://www.flightradars.eu/squawkcodes.html#top

== Modes A, B, C, S ==
Detailed illustrated explanation:

* https://skybrary.aero/articles/transponder
* https://pilotinstitute.com/transponder-modes-explained
* https://en.wikipedia.org/wiki/Aviation_transponder_interrogation_modes

Needs are constantly evolving, and technology merely adapts to those changes. Transponder modes are a reflection of the evolution of those needs.

=== Mode A ===
From the WWII era, when aircraft were returning and approaching their bases, it was difficult to determine whether they were Friend or Enemy (FOE). To avoid unwanted activation of the DCA systems, pilots would activate a conventional code by switching a set of buttons ON and OFF to define an identity code.

After the war, this concept carried over into civil aviation, but the mode was very basic and additional identification features were soon desired.

=== Mode B ===
It was an evolution of Mode A, but due to some quirks it was quickly abandoned in favor of Mode C.

=== Mode C ===
It added reporting of aircraft altitude.

This reported altitude was originally transmitted after barometric correction, which led to several problems. In the later Mode S, this was changed to transmitting uncorrected altitude instead.

The reason for this is not obvious. Imagine an aircraft on final approach: an incorrectly set altimetric pressure could cause the aircraft to “hit” the ground before the runway, or touch down too late and trigger a runway excursion.

Other situations involving altitude busts (loss of vertical separation) have also occurred, although more rarely.

Mode C altitude reports are transmitted in 100 ft increments.

=== Mode S ===
Mode S has been a game changer.

In Mode C, there were too many aircraft sending information at the same time. The radio frequency was congested, and often life-and-death information became lost as a result of all the transponders “speaking at the same time.”

In Mode S, transponders are quiet and remain silent unless “interrogated” by the surveillance system.

Well, almost silent. The surveillance system needs to know whom to direct the interrogation to. For this reason, all transponders still continue to repeatedly emit a very short ID called the squitter.

The surveillance system keeps a table of all the squitters for management.

With the frequency no longer congested, interrogated transponders have the ability to send more extensive information.

Mode S itself has 2 variants: ELS and EHS, meaning ELementary Surveillance and EnHanced Surveillance.

The former sends altitude (before calibration), speed, direction, and a few more aircraft and flight parameters.

The latter also sends the “selected” altitude in the autopilot, which allows ATC to detect misunderstandings early and prevent possible level busts before they happen.

See: https://skybrary.aero/articles/mode-s

Mode S altitude reports are in 10 ft increments, which is uncalibrated.

To do this, the transponder needs an altitude source. In real life this can be a separate box called an encoder, or it may be derived from FMC / ADIRU sources. It's important to note this altitude is referenced to standard pressure (29.92 inHg / 1013 hPa), and is not corrected for actual barometric pressure in the local environment.

Additional support for military modes is possible if anyone wishes to add it.

== Transponder in the Cockpit ==
Bear in mind that no two transponders are exactly the same.

* Older aircraft may still have older transponders that are not Mode S capable.
* There are several manufacturers with differing control panels.

Some transponders have a knob position labeled “ALTITUDE,” which can be Mode C or Mode S. Transponders with TCAS support usually use "TA/RA" and "TA" and "ON" modes instead of "ALTITUDE", all of which send altitude information.

The usual transponder modes encountered in real life are:

* Off - switched off / no power
* Test - maintenance mode
* Standby - powered on, but not sending information except the squitter (see above)
* Ground - sends out the squawk code only
* Altitude - in Mode C, sends altitude information; in Mode S, sends additional information as well

== Traffic and Resolution Advisories ==
* TA = Traffic Advisory
* RA = Resolution Advisory

On some transponders, TA/RA functions may be switched on separately.

Coordinated resolution advisory <big>require</big> '''Mode S''' in order to work properly.

A common myth is that Mode S and TA/RA should only be activated while airborne.

Nothing could be further from the truth.

Airports where visibility is frequently poor and foggy, such as Paris Orly, Milano Linate, Birmingham, among others, may require departing aircraft to activate Mode S and TA from the gate/stand, even before pushback. This is also standard practice in the United States.

TA on the ground uses a special mode with different sensitivity settings adapted to detect converging taxiing aircraft. Many severe accidents with fatalities have involved ground collisions.

Examples:

Scandinavian Airlines Flight 686 (a Scandinavian Airlines McDonnell Douglas MD-87) collided with a private Cessna Citation, resulting in 118 fatalities.
https://en.wikipedia.org/wiki/Linate_Airport_disaster

Paris Orly is historically so fog-prone that it became one of the first airports to develop “Turbo Clear” anti-fog systems in 1963. Airports around the world later adopted similar systems before the introduction of ATT (“Atterrissages Tous Temps” / “All Weather Landings”), precursors to modern Instrument Landing Systems.
https://www.aeroport-paris-orly.com/systemes-anti-brouillard

The myth likely originates from the fact that procedures vary between airports and situations. Someone discovering the rule enforced at one airport may incorrectly assume the same rule applies everywhere.

Usually, airport administration and chart briefing pages clearly specify the procedures enforced at that particular airport.

On the ground:
* Mode S + Traffic Alert may be required.

Airborne:
* Mode S + Traffic Alert + Resolution Advisory is generally expected whenever available.
* Older aircraft frequently operating in controlled airspace are increasingly required to upgrade their transponders.

== IDENT ==
Transponders have a separate function called IDENT, activated by pressing a dedicated button.

This is not actually a “mode” like Mode A, C, or S.

It should never be pressed unless requested by the ATC providing the service.

It also <big>must not</big> be activated automatically during squawk code changes, which is a frequent error.

IDENT allows ATC to instantly spot a particular aircraft among many others, and its sole purpose is to help in cases where conspicuity has been lost.

Squawk codes change quite frequently. If IDENT were activated every time a squawk code was recycled, many blips (aircraft symbols on the ATC screen) would constantly start blinking. Then, when ATC actually requests an aircraft to press IDENT, the usefulness of the feature would be lost because it would be drowned among many other IDENT activations.

== Configuration in FlightGear ==
Transponder support was overhauled in May 2013; earlier versions (2.10 and prior) have different support and are not documented here. Updating an aircraft to use the new config is straightforward. Key transponder properties (altitude, ident and transmitted-id) are now sent via the MP protocols for use in ATC clients.

The default altimeter can act as an altitude encoder; in its configuration, set either or both of the following boolean flags:

* encode-mode-c
* encode-mode-s

The transponder has various config properties:

* '''minimum-supply-volts''': required volts for operations, defaults to 8.0 ''(old '''bus-volts''' is now deprecated)''
* '''encoder-path''': defaults to '/instruments/altimeter', but can be changed to any other location. The transponder looks for child properties 'mode-c-alt-ft' and 'mode-s-alt-ft' at this path for altitude data.
* '''kt70-compatibility''': boolean, default to false. Set this to enable legacy compatibility with the old KT-70 C++ instrument. Do not use in new/updated aircraft!
* '''mode''': this is 0 for Mode-A, 1 for Mode-C and 2 for Mode-S. Other modes can be added, ask on the [[Mailing list|devel list]]!

=== Run-time properties ===
* '''altitude''': gives the transmitted altitude in feet (or -9999 for invalid)
* '''altitude-valid''': indicates if altitude value is valid data or not
* '''id-code''': allows the id-code to be read and set
* '''serviceable''': can be set to control the instrument serviceability
* '''transmitted-id''': gives the value being transmitted, including over the network via MP

==== Input properties ====
These live under <tt>/inputs</tt>.
* '''knob-mode''': sets the transponder operating mode. This corresponds to the KT-70 knob positions for convenience, but the actual modes should work for any transponder instrument. Knob modes are documented below
* '''ident-btn''': can be set to place the transponder in ident mode for 18 seconds. Note this property is not spring-loaded, i.e you must manually reset it to false
* '''digit[0]-[4]''': properties allow the id code individual digits to be read and set

In KT-70 compatibility mode, additional properties are read and set, to preserve legacy aircraft. Do not use these properties in new aircraft.

==== Knob/Functional Modes ====
* 0 - off
* 1 - standby, basically the same as off for the C++ code (3D instrument would power up the display, presumably)
* 2 - test, again the C++ largely ignores this since the test configuration of real-world instruments varies. In particular the unit does *not* set altitude or transmitted-id to any test values, you should do that in your own logic. (Maybe we should allow the test values to be defined int he config section?)
* 3 - Ground mode, responds to altitude interrogation but does not broadcast an ID. This would typically be used while taxiing prior to takeoff.
* 4 - On, normal operation but altitude transmission is inhibited
* 5 - Alt, same as on but altitude is broadcast if transponder was configured in Mode-S or Mode-C

=== Generic transponder ===
Below are all available property that you can set for your instrumentation.xml file :

<syntaxhighlight lang="xml">
<transponder>
<name type="string">transponder</name>
<number type="int">0</number>
<mode type="int">1</mode> 
<minimum-supply-volts type="double">8.0</minimum-supply-volts>
<encoder-path type="string">/instrumentation/altimeter</encoder-path>
<kt70-compatibility type="bool">0</kt70-compatibility>
<auto-ground>...</auto-ground> 
<airspeed-path>...</airspeed-path>
<mach-path>...</mach-path>
</transponder>
</syntaxhighlight>Please note that ''<bus-volts>'' is now '''deprecated'''. Use ''<minimum-supply-volts>'' instead.
The following is a copy of a comment in instrument source, explaining the use of Mode-S related properties
<
// Mode-S transponders (configured with mode = 2) can transmit a ground bit to
// indicate ground operation. If auto-ground is not defined, the ground bit is
// switched manually by setting the transponder knob to GND. If auto-ground is
// defined, the transponder simulates automatic switching of the ground bit
// using the value of the property defined in auto-ground.
//
// For a squat switch, use "/gear/gear/wow". For automatic switching based on
// airspeed, use a property rule to make a new boolean property that indicates,
// for example, airspeed < 80, and reference your new property in auto-ground.
//
// Note that Mode-A and Mode-C transponders do not transmit a ground bit, even
// if the transponder knob is set to the GND position.
//
// Mode-S transponders also transmit indicated airspeed and Mach number. The
// default sources are "/instrumentation/airspeed-indicator/indicated-speed-kt"
// and ".../indicated-mach", but this can be changed by setting "airspeed-path"
// and "mach-path" properties respectively as shown above.

==Related content==
===Wiki articles===
*[[Howto:Develop an aircraft transponder in Nasal]] – Most probably obsolete
*[[FLARM]]
*[[Multiplayer protocol]] – The IDs 1501-1503 are earmarked for transmitting transponder properties
*[[OpenRadar: Transponder]]
*[[Traffic alert and collision avoidance system]]

===Forum topics===
*[https://forum.flightgear.org/viewtopic.php?f=4&t=31492 Transponder properties over MP] (January-June 2017)
*[https://forum.flightgear.org/viewtopic.php?f=75&t=19826 Transponder over network] (April-December 2018)
*[https://forum.flightgear.org/viewtopic.php?f=4&t=6395 Transponder] (November 2009-December 2010)

===Developer mailing list===
*[https://sourceforge.net/p/flightgear/mailman/message/30785263/ <nowiki>[</nowiki>Flightgear-devel<nowiki>]</nowiki> Improve tranponder instrument] (Apr 2009)
*[https://sourceforge.net/p/flightgear/mailman/flightgear-devel/thread/1388915221.2195.15.camel%40duter.localdomain/#msg31810053 <nowiki>[</nowiki>Flightgear-devel<nowiki>]</nowiki> Transponder Ident not transmitted via MP Protocol?] (Jan-Feb 2014)

===Source code===
*{{flightgear source|src/Instrumentation/transponder.hxx}}
*{{flightgear source|src/Instrumentation/transponder.cxx}}

[[Category:Aircraft enhancement]]
[[Category:Aircraft instruments]]

FlightGear hangars

2026-05-23T19:57:47Z

Octal450: /* Other FlightGear repositories/mirrors */

[[Aircraft]] in FlightGear are often distributed from a hangar. The official FlightGear hangar is called [[FGAddon]] and it contains hundreds of aircraft at different stages of development (including aircraft from up to 20 years ago). Many aircraft are also distributed via 3rd-party hangars.

== Licensing ==

The [[FGAddon]] hangar is distributed using the GPLv2+ licensing terms - see the official [http://www.flightgear.org/flightgear-policy-document/ FlightGear policy document]. Third party hangars are free to license their content as they wish.

{{caution|If licensing violations are found in a 3rd party hangar - including copying images, sounds, 3D objects or any other content that cannot be legally copied, or any non-legal licensing combinations - the FlightGear developers reserve the right to remove all mentions of that hangar from the official FlightGear web infrastructure (wiki, forum, mailing lists, etc.). The advertisement of illegal content via the official infrastructure could lead to legal problems for the FlightGear developers.}}

== Official FGAddon hangar ==
The [[FGAddon|FGAddon hangar]] is the official FlightGear hangar.

=== Aircraft downloads ===
[[File:FGAddon logo.png|270px|right|link=FGAddon]]

All official release aircraft can now be individually downloaded and updated with FlightGear itself. This is a nice way to browse new aircraft and make sure your favorites are always kept up to date.

=== Aircraft development ===
The [[FGAddon]] version controlled repository contains in-development aircraft as well as aircraft tagged for FlightGear 3.4 and higher stable releases.

* {{fgaddon aircraft source|text=FGAddon Hangar}} The Subversion version controlled repository for the official FlightGear aircraft on the SourceForge infrastructure, see [[FGAddon]] for details.
* {{gitorious source|proj=fg|repo=fgdata|path=Aircraft|view=tree|text=Old fgdata Hangar}} The Gitorious archive of the official aircraft, migrated to the [https://archive.org/ Internet Archive] for archival and history preservation purposes. Aircraft were migrated to [[FGAddon]] in September 2014. For further details see the [[FlightGear Newsletter September 2014#Aircraft moved to SVN|September 2014 newsletter announcement]] and the [http://forum.flightgear.org/viewtopic.php?f=28&t=24045 announcement topic on the forum]

=== Liveries ===
* [http://liveries.flightgear.org FlightGear Livery Database]

== Third party sites ==
=== Aircraft catalogues ===
If a hangar provides a [[hangar catalog|catalog URL]] file (catalog.xml), it can be added to the FlightGear QtLauncher to display all the aircraft of that hangar. You add the URL to the <code>catalog.xml</code> on the ''Add-ons'' page in the ''Aircraft hangars'' section.

For details on how to create your own <code>catalog.xml</code> file, see [[Hangar catalog]].

=== Aircraft hangars ===
These are links where you can download individual planes manually.

{| class="wikitable sortable"
|-
! Hangar
! Category
! Description
! [[Hangar catalog|Catalog URL]]
|-
| [http://www.gidenstam.org/FlightGear/Airships/ Anders' Lighter-than-air Hangar]
|
| With U.S. Navy K-type, ''Nordstern'', Zeppelin NT, SSZero airships and ZF free balloon and additional craft at [http://github.com/andgi?tab=repositories Anders' aircraft repositories at GitHub].
|
|-
| [http://andinogonthaeler.wordpress.com/ Andino's Hangar]
|
| An-124, A340-600HGW, MD80's, Boeing 707-3J9C and 707-320C.
|
|-
| Bermuda Triangle
| [[:Category:Bermuda Triangle|Category]]
| A hypothetical hangar used to categorize temporarily or permanently lost aircraft.
|
|-
| [http://www.buckarooshangar.com/flightgear/ Buckaroo's Hangar]
| [[:Category:Buckaroo's hangar|Category]]
| Velocity XL RG, Edgley Optica, Lockheed 1049H Constellation, Grumman Goose, McDonnell Douglas MD-81 (& a YASim intro).
|
|-
| [http://www.daveshangar.org/ Dave's Hangar]
| [[:Category:Dave's hangar|Category]]
|
| [http://www.daveshangar.org/catalog.xml catalog.xml]
|-
| [http://www.fgpipistrel.org/ FG Pipistrel Hangar]
|
| Developing Pipistrel aircraft.
|
|-
| [https://sites.google.com/view/fgukhangar/flightgear-uk-home-page/hangar FlightGear UK - FGUK Hangar]
| [[:Category:FGUK hangar|Category]]
| UK based group improving, mainly European, aircraft and scenery for FG. Weekly MP FlightNights. A lot of helicopters are in the "[https://sites.google.com/view/fgukhangar/flightgear-uk-home-page/hangar/rotary-wing Rotary Wing]" section (November 2020). Over 60 Open Source aircraft so far. [https://forum.fguk.me/ Friendly community forum]
|
|-
| [http://charles.ingels.free.fr/flightgear/ French FlightGear Hangar]
|
| (FR) Aermacchi MB326, Dassault Mirage F1 Mikoyan Gurevitch Mig 31 Foxhound, and more.
|
|-
| [http://hcilab.uniud.it/pan/downloads.html HCI Lab - University of Udine]
|
| Aermacchi MB339 Frecce Tricolori.
|
|-
| [http://helijah.free.fr/flightgear/hangar.htm Helijah FlightGear Hangar]
| [[:Category:Helijah hangar|Category]]
| 275+ original aircraft, the majority of which are maintained in [[FGAddon]].
|
|-
| [http://hhfgfs.weebly.com/index.html Hellcat's FlightGear Hangar]
|
| Scenarios, skins, film inspired aerospace vehicles.
|
|-
| [https://github.com/HerbyW HerbyW Hanger]
| [[:Category:HerbyW's hangar|Category]]
| Antonov-MilMi-Iljushin-Followme all Rembrandt and Multiplayer support.
| [http://static.djgummikuh.de/Aircraft/catalog.xml catalog.xml]
|-
| [http://www.hoerbird.net/aircrafts.html Hoerbird Hangar]
|
| Misc. projects.
|
|-
| [http://www.grafikavirtual.com/fgfs/ Horacio's Hangar]
|
| Spanish site.
|
|-
| [http://horizonflightgearhangar.yolasite.com/ Horizon FlightGear Hangar]
|
| Dabolim Naval Air Station (VAGO), Goa, India; Murray Bridge/Pallama Airfield (YMBD), Australia; and ADFX-02 Morgan, a fictional aircraft.
|
|-
| [http://hsotfhangar.wordpress.com/ HSOTF Official Hangar]
|
|
|
|-
| [http://marc-kraus.de/ Lake of Constance Hangar]
| [[:Category:Lake of Constance hangar|Category]]
| Quality Signature Series Aircrafts by Marc Kraus from Friedrichshafen home of The Dornier Museum.
|
|-
| [http://longfly.square7.ch Longfly's Hangar]
|
|
|
|-
| [http://nickfg.blogspot.com/ Nick's FlightGear Hangar]
|
| Blog, CRJ-200.
|
|-
| [https://github.com/Octal450?tab=repositories Octal450 Hanger]
| [[:Category:Octal450 hangar|Category]]
| High Quality Airliners
| [http://static.djgummikuh.de/octal450/catalog.xml catalog.xml]
|-
| [http://opredflag.com/ Operation Red Flag Hangar]
|
| Flightgear Flight Sim Military Community
| [http://static.djgummikuh.de/OPRF/catalog.xml catalog.xml]
|-
| [http://equipe-flightgear.forumactif.com/t835-hangar-de-la-paf-paf-team-hangar#14330 PAF team Hangar]
| [[:Category:PAF hangar|Category]]
| [http://pattenflightgear.wifeo.com/cessna-citationx.php Cessna Citation X], [[Mudry Cap10b|Cap 10b]], [[Robin DR400 Dauphin|Robin DR400 JSBSim]], [[Douglas C-47 Skytrain|Douglas DC-3 C47]], Tecnam P92 Echo...
|
|-
| [http://pattenflightgear.wifeo.com/avions.php Patten's hangar]
|
| Alouette-2, DHC6-300, Robin DR400 JSBsim, Tecnam P92 Echo, CAP 10 C, CAP 10 B, Douglas DC3 C47-JSBsim, Sceneries, Ground textures...
|
|-
| [http://presteshangar.wikidot.com/start Prestes Hangar]
| [[:Category:Prestes hangar|Category]]
| Many Brazilian aircraft articles.
|
|-
| [http://riktov.synthasite.com/ Riktov's FlightGear Hangar]
|
| BN-2 Islander, Giant Marshmallow Man.
|
|-
|[https://gitlab.com/fg_shfsn/hangar ShFsn's Hangar]
|
|Various Soviet and Russian aircrafts updated and/or maintained by ShFsn (Tu-144D, Tu-154B-2, An-24B, MiG-15bis, MiG-29, Su-27; as of 2023-11)
|[https://gitlab.com/fg_shfsn/hangar/-/raw/main/catalog.xml catalog.xml]
|-
|[http://seahorseCorral.org/flightgear_aircraft.html Stewart's SEA-horse Aircraft Hanger]
|
|Newest bluebird version.
|[http://www.seahorsecorral.org/FGMEMBERS/catalog.xml catalog.xml]
|-
|[http://macflightgear.sourceforge.net/home/aircraft Tat's Aircraft for FlightGear]
|
|A6M2 "Zero", J7W, Ki-84, T-4, HondaJet, OH-1, K5Y1, RV-6A, YS-11.
|
|-
|[http://vicmar.weebly.com/ VicMar]
|
|Yanagisawa Gen H-4, Stung Biker, Quad Bikes, SRN4, Water Skier, G2 Thunderpack, Martin Jetpack.
|
|-
|[http://www.treborlogic.com/fgfs/hangar/ Yourgod's Hangar]
|
|Douglas DC-8.
|
|}

===Old Hangars===
These are old or abandoned aircraft hangars.

{| class="wikitable sortable"
|-
! Hangar
!Description
!Status
|-
| [https://web.archive.org/http://croo.murgl.org/fgfs/index.html A-10 and A-6 stuff (Web Archive link)]
| A-10, A-6
| Dead link as of unknown.
|-
|<s>[http://fg-acjza.wix.com/hangar/ ACJZA Hangar]</s>{{dead link|2017-01-02}}
|Land, Sea, Air.
|Dead link as of 2017-01-02.
|-
|<s>{{gitorious source|text=Airbus Aircraft Development Git}}</s>{{dead link|2018-08-05}}
|A320, A330, A340-300, A380 - various authors, see the projects under <code>airbus-aircraft</code>.
| Dead link as of 2018-08-05.
|-
|[https://web.archive.org/web/20101202031445/http://www.sol2500.net:80/flightgear/aircraft.html DFaber Hangar (Web Archive link)]
|Eurofighter, PC-6, Bf 109, Beufighter, F4U, Ju 52, DH Mosquito, G. Albatross, F-86, and more.
|Dead link as of 2012-04.
|-
|<s>[http://thefancyflightgearhangar.blogspot.com The Fancy FlightGear Hangar]</s>
|A few well made aircraft.
|Dead download links as of 2020-06.
|-
| [https://gitlab.com/femboywings-fgfs/ Fboy Wings]
| [[Tupolev Tu-144|Tu-144D]].
| Outdated as of 2023-11.
|-
|<s>[http://flier95-flightgear.blogspot.com/ Flier95's Hangar]</s>{{dead link|2012-08}}
|Blog format.
|Seems to be replaced by advertisement blog (2020-06).
|-
|<s>[https://sites.google.com/site/grtuxhangar GRTux Hangar]</s>{{dead link|2024-10}}
|28+ aircraft and add-ons; you need to mail to GRTux for download.
| Dead link as of 2024-10.
|-
| <s>[https://sites.google.com/site/fghangar JOFH - Just Another Flightgear Hangar]</s>{{dead link|2024-10}}
| JA-37, scenario.
| Dead link as of 2024-10.
|-
|[https://web.archive.org/http://mysite.verizon.net/vzeuyecs/ Kent Esbenshade's Boneyard Hangar (Web Archive link)]
|Classic aircraft.
|Dead link as of 2015-09.
|-
|[https://melbournemotorworks.wordpress.com/ <s>Melbourne Motor Works</s>]
|Web Archive link is blank
|Dead link as of 2026-05-22
|-
|[https://web.archive.org/web/20160616195014/http://theomegahangar.flymerlion.org/ Omega Hangar (Web Archive link)]
|Embraer E-jet Family, A330-200, A320neo, CRJ-700 Full First Class, ATR-42-family, A321-series, Mobile Stairway.
|Dead link as of 2017-01-02.
|-
|[https://web.archive.org/http://pjedvaj.wordpress.com/ pjedvaj's Hangar (Web Archive link)]
|PC-9M, PC-21, MiG-21bis, T-50, Harrier GR.1, F-35B, RAH-66, Su-25, Yak-130.
|Dead link as of 2018-07-24.
|-
|[https://web.archive.org/web/20180201073847/http://digilander.libero.it/scighera_fg/index.html Scighera's Hangar (Web Archive link)]
|Models & liveries.
| Dead link as of 2020-06
|-
|<s>[https://sites.google.com/site/sydshangar/ Syd's Google Hangar]</s>{{dead link|2024-10}}
|"Newer 2.0 versions."
|Dead link as of 2024-10.
|-
|[https://m-selig.ae.illinois.edu/apasim/fgfs-models.html UIUC Hangar]
|For FGFS 0.7.8.
|Old aircraft FDMs with no 3D models.
|}

===Livery/Scenery hangars===
*<s>[http://AAliveries.yolasite.com/ AA Liveries]</s>{{dead link|2015-01}} Another livery site
*[http://berwickskins.yolasite.com/ Berwick-skins]
*<s>[http://dliveryhangar.synthasite.com/ Dodger4's Livery Hangar]</s> {{dead link|2017-02}}
*[http://hsotfhangar.wordpress.com/ HSOTF Official Hangar]
*[http://jchnd.blogspot.com/ JcHnd's Liveries for FlightGear]
*[http://lukashangar.jimdo.com/ Lukas' hangar] (Scenery projects, Liveries)
*<s>[http://mojos-hangar.webs.com/ MOJO's Flightgear Livery Hangar]</s>{{dead link|2020-06}}
*<s>[http://members.cox.net/scotsg8r/hangar/ N-SCOT's Hangar]</s>{{dead link|2012-04}} (5+ liveries & mods)
*<s>[https://planepainter.yolasite.com/ The Planepainter]</s>{{dead link|2012-04}} (Liveries, Scenery)
*<s>[http://simbabeathangar.webs.com/ Simbabeat's Livery Hangar]</s>{{dead link|2020-06}}
*[http://victorhangar.blogspot.com/ Victor Hangar] (in Portuguese - Brazilian; many download links broken (2020-06), but some are still working)
*[http://www.fgau.org/ FlightGear Australia/FGAU.org] Australian scenery development.

=== Other FlightGear repositories/mirrors===
*[http://hsotfhangar.wordpress.com/ HSOTF Official Hangar]
*Unitedfreeworld (scenery, plane models, and livery) - New owners of the Unitedfreeworld domain have reuploaded all prior work released by xsaint, as of September 2018 (link now dead)
*[https://mirrors.tuna.tsinghua.edu.cn/flightgear/ftp/ Tsinghua mirror] - Available for downloading installation packages, aircraft and scenery

==Related content==
*[[Aircraft]] - [[Helicopter]] - [[Vehicle]]
*[[Hangar catalog]]
*[[Table of models]]

==References==
{{Appendix}}

[[Category:Lists]]
[[ca:Hangars de FlightGear]]
[[es:Hangares_Flightgear]]
[[fr:FlightGear hangars]]
[[pl:FlightGear hangars]]

Transponder

2026-05-23T19:53:30Z

Octal450:

'''Transponders''' are radio beacons which make [[aircraft]] more identifiable on [[ATC]] displays and systems and by other aircrafts. Modern transponders support transmitting additional data such as an identification ('squawk') code and aircraft altitude. See more at {{wikipedia|Transponder (aeronautics)}}.

== ID Codes ==
* The ‘squawk code’ 7000 is used for VFR flights in Europe, while in the US, 1200 is used for the same purpose.
* IFR aircraft will be assigned an “attributed code” by ATC services at clearance delivery time, typically during startup. The code is selected by ATC from a regionally allocated pool of currently unused codes.
* NATO and other military aircraft sharing civil airspace use several codes from conventional tables, such as “0300 or 0400 - NATO - CAOC 9 Exercises (activated by NOTAM)” and “3500 - NATO - Aircraft receiving a service from AEW aircraft.”
* An aircraft unable to use voice radio communications will select the special code 7600.
* An aircraft experiencing an emergency (technical, medical, etc.) will select the special code 7700.

While some codes are used worldwide, such as the emergency codes, other codes have different regional meanings, like the special code ‘0000’.

* In the UK, by convention, the code ‘0000’ may be automatically selected by some transponders to report a transponder malfunction; pilots are not allowed to select it manually.
* In Europe, it is no longer used and its use has become prohibited. In the early days of transponders (Mode A), it was used to indicate “no ORCAM code inserted yet.” Its use today is strictly forbidden.
* In the US, it is a bit more confusing:
** It is used for some military interception operations.
** It may be used by ARTCC en route control centers for aircraft in cruise within controlled airspace when no more unassigned ORCAM codes are available.
** The Department of Transportation and the FAA have advocated, since 1981, for abandoning its use and moving toward full prohibition.

See: https://en.wikipedia.org/wiki/List_of_transponder_codes

Codes are composed of a sequence of 4 digits, each with 8 possible values, ranging from [ 0 ][ 0 ][ 0 ][ 0 ] to [ 7 ][ 7 ][ 7 ][ 7 ].

Codes specifically define either:

* 1 aircraft, and 1 aircraft only;
* 1 particular situation.

== Special Codes ==
Codes ending in “00” define situations.

* 7500 - Hijacking
* 7600 - Unable to use voice radio communications - “Communications failure”
* 7700 - Emergency (technical / medical)

These codes do not identify 1 aircraft only.

Codes ending with other numbers (0 to 7) identify 1 and only 1 aircraft.

* They are assigned by ATC, usually by radio during departure clearance.
* They can be changed during the flight to accommodate traffic management needs.

Codes identifying 1 and only 1 aircraft are called discrete or conspicuous codes.

Codes defining situations are called non-discrete or non-conspicuous codes.

This is also why transponder codes are called Conspicuity Codes.

See: https://skybrary.aero/articles/discrete-and-non-discrete-ssr-codes

== ORCAM method ==
There are far more aircraft to manage than available squawk codes.

To solve this problem, the ORCAM method is used.

ORCAM stands for Originating Regional Code Allocation Method.

Every region, airspace, airport, or service (such as military operations) is assigned a range of codes.

When an aircraft leaves one controlled zone and enters another, if, the current code conflicts with another code already in use nearby, ATC will ask the aircraft to recycle the code and select a new unused one.

ORCAM is a method, not a “table,” although the method excludes a subset of fixed codes from its management, and those are defined in tables.

Note that the following table is valid for the UK only; the US and Europe use some different assignments.

https://www.flightradars.eu/squawkcodes.html#top

== Modes A, B, C, S ==
Detailed illustrated explanation:

* https://skybrary.aero/articles/transponder
* https://pilotinstitute.com/transponder-modes-explained
* https://en.wikipedia.org/wiki/Aviation_transponder_interrogation_modes

Needs are constantly evolving, and technology merely adapts to those changes. Transponder modes are a reflection of the evolution of those needs.

=== Mode A ===
From the WWII era, when aircraft were returning and approaching their bases, it was difficult to determine whether they were Friend or Enemy (FOE). To avoid unwanted activation of the DCA systems, pilots would activate a conventional code by switching a set of buttons ON and OFF to define an identity code.

After the war, this concept carried over into civil aviation, but the mode was very basic and additional identification features were soon desired.

=== Mode B ===
It was an evolution of Mode A, but due to some quirks it was quickly abandoned in favor of Mode C.

=== Mode C ===
It added reporting of aircraft altitude.

This reported altitude was originally transmitted after barometric correction, which led to several problems. In the later Mode S, this was changed to transmitting uncorrected altitude instead.

The reason for this is not obvious. Imagine an aircraft on final approach: an incorrectly set altimetric pressure could cause the aircraft to “hit” the ground before the runway, or touch down too late and trigger a runway excursion.

Other situations involving altitude busts (loss of vertical separation) have also occurred, although more rarely.

Mode C altitude reports are transmitted in 100 ft increments.

=== Mode S ===
Mode S has been a game changer.

In Mode C, there were too many aircraft sending information at the same time. The radio frequency was congested, and often life-and-death information became lost as a result of all the transponders “speaking at the same time.”

In Mode S, transponders are quiet and remain silent unless “interrogated” by the surveillance system.

Well, almost silent. The surveillance system needs to know whom to direct the interrogation to. For this reason, all transponders still continue to repeatedly emit a very short ID called the squitter.

The surveillance system keeps a table of all the squitters for management.

With the frequency no longer congested, interrogated transponders have the ability to send more extensive information.

Mode S itself has 2 variants: ELS and EHS, meaning ELementary Surveillance and EnHanced Surveillance.

The former sends altitude (before calibration), speed, direction, and a few more aircraft and flight parameters.

The latter also sends the “selected” altitude in the autopilot, which allows ATC to detect misunderstandings early and prevent possible level busts before they happen.

See: https://skybrary.aero/articles/mode-s

Mode S altitude reports are in 10 ft increments, which is uncalibrated.

To do this, the transponder needs an altitude source. In real life this can be a separate box called an encoder, or it may be derived from FMC / ADIRU sources. It's important to note this altitude is referenced to standard pressure (29.92 inHg / 1013 hPa), and is not corrected for actual barometric pressure in the local environment.

Additional support for military modes is possible if anyone wishes to add it.

== Transponder in the Cockpit ==
Bear in mind that no two transponders are exactly the same.

* Older aircraft may still have older transponders that are not Mode S capable.
* There are several manufacturers with differing control panels.

Some transponders have a knob position labeled “ALTITUDE,” which can be Mode C or Mode S. Transponders with TCAS support usually use "TA/RA" and "TA" and "ON" modes instead of "ALTITUDE", all of which send altitude information.

The usual transponder modes encountered in real life are:

* Off - switched off / no power
* Test - maintenance mode
* Standby - powered on, but not sending information except the squitter (see above)
* Ground - sends out the squawk code only
* Altitude - in Mode C, sends altitude information; in Mode S, sends additional information as well

== Traffic and Resolution Advisories ==
* TA = Traffic Advisory
* RA = Resolution Advisory

On some transponders, TA/RA functions may be switched on separately.

Coordinated resolution advisory <big>require</big> '''Mode S''' in order to work properly.

A common myth is that Mode S and TA/RA should only be activated while airborne.

Nothing could be further from the truth.

Airports where visibility is frequently poor and foggy, such as Paris Orly, Milano Linate, Birmingham, among others, may require departing aircraft to activate Mode S and TA from the gate/stand, even before pushback. This is also standard practice in the United States.

TA on the ground uses a special mode with different sensitivity settings adapted to detect converging taxiing aircraft. Many severe accidents with fatalities have involved ground collisions.

Examples:

Scandinavian Airlines Flight 686 (a Scandinavian Airlines McDonnell Douglas MD-87) collided with a private Cessna Citation, resulting in 118 fatalities.
https://en.wikipedia.org/wiki/Linate_Airport_disaster

Paris Orly is historically so fog-prone that it became one of the first airports to develop “Turbo Clear” anti-fog systems in 1963. Airports around the world later adopted similar systems before the introduction of ATT (“Atterrissages Tous Temps” / “All Weather Landings”), precursors to modern Instrument Landing Systems.
https://www.aeroport-paris-orly.com/systemes-anti-brouillard

The myth likely originates from the fact that procedures vary between airports and situations. Someone discovering the rule enforced at one airport may incorrectly assume the same rule applies everywhere.

Usually, airport administration and chart briefing pages clearly specify the procedures enforced at that particular airport.

On the ground:
* Mode S + Traffic Alert may be required.

Airborne:
* Mode S + Traffic Alert + Resolution Advisory is generally expected whenever available.
* Older aircraft frequently operating in controlled airspace are increasingly required to upgrade their transponders.

== IDENT ==
Transponders have a separate function called IDENT, activated by pressing a dedicated button.

This is not actually a “mode” like Mode A, C, or S.

It should never be pressed unless requested by the ATC providing the service.

It also <big>must not</big> be activated automatically during squawk code changes, which is a frequent error.

IDENT allows ATC to instantly spot a particular aircraft among many others, and its sole purpose is to help in cases where conspicuity has been lost.

Squawk codes change quite frequently. If IDENT were activated every time a squawk code was recycled, many blips (aircraft symbols on the ATC screen) would constantly start blinking. Then, when ATC actually requests an aircraft to press IDENT, the usefulness of the feature would be lost because it would be drowned among many other IDENT activations.

== Configuration in FlightGear ==
Transponder support was overhauled in May 2013; earlier versions (2.10 and prior) have different support and are not documented here. Updating an aircraft to use the new config is straightforward. Key transponder properties (altitude, ident and transmitted-id) are now sent via the MP protocols for use in ATC clients.

The default altimeter can act as an altitude encoder; in its configuration, set either or both of the following boolean flags:

* encode-mode-c
* encode-mode-s

The transponder has various config properties:

* '''minimum-supply-volts''': required DV volts for operations, defaults to 8.0 ''(old '''bus-volts''' is now deprecated)''
* '''encoder-path''': defaults to '/instruments/altimeter', but can be changed to any other location. The transponder looks for child properties 'mode-c-alt-ft' and 'mode-s-alt-ft' at this path for altitude data.
* '''kt70-compatibility''': boolean, default to false. Set this to enable legacy compatibility with the old KT-70 C++ instrument. Do not use in new/updated aircraft!
* '''mode''': this is 0 for Mode-A, 1 for Mode-C and 2 for Mode-S. Other modes can be added, ask on the [[Mailing list|devel list]]!

=== Run-time properties ===
* '''altitude''': gives the transmitted altitude in feet (or -9999 for invalid)
* '''altitude-valid''': indicates if altitude value is valid data or not
* '''id-code''': allows the id-code to be read and set
* '''serviceable''': can be set to control the instrument serviceability
* '''transmitted-id''': gives the value being transmitted, including over the network via MP

==== Input properties ====
These live under <tt>/inputs</tt>.
* '''knob-mode''': sets the transponder operating mode. This corresponds to the KT-70 knob positions for convenience, but the actual modes should work for any transponder instrument. Knob modes are documented below
* '''ident-btn''': can be set to place the transponder in ident mode for 18 seconds. Note this property is not spring-loaded, i.e you must manually reset it to false
* '''digit[0]-[4]''': properties allow the id code individual digits to be read and set

In KT-70 compatibility mode, additional properties are read and set, to preserve legacy aircraft. Do not use these properties in new aircraft.

==== Knob/Functional Modes ====
* 0 - off
* 1 - standby, basically the same as off for the C++ code (3D instrument would power up the display, presumably)
* 2 - test, again the C++ largely ignores this since the test configuration of real-world instruments varies. In particular the unit does *not* set altitude or transmitted-id to any test values, you should do that in your own logic. (Maybe we should allow the test values to be defined int he config section?)
* 3 - Ground mode, responds to altitude interrogation but does not broadcast an ID. This would typically be used while taxiing prior to takeoff.
* 4 - On, normal operation but altitude transmission is inhibited
* 5 - Alt, same as on but altitude is broadcast if transponder was configured in Mode-S or Mode-C

=== Generic transponder ===
Below are all available property that you can set for your instrumentation.xml file :

<syntaxhighlight lang="xml">
<transponder>
<name type="string">transponder</name>
<number type="int">0</number>
<mode type="int">1</mode> 
<minimum-supply-volts type="double">8.0</minimum-supply-volts>
<encoder-path type="string">/instrumentation/altimeter</encoder-path>
<kt70-compatibility type="bool">0</kt70-compatibility>
<auto-ground>...</auto-ground> 
<airspeed-path>...</airspeed-path>
<mach-path>...</mach-path>
</transponder>
</syntaxhighlight>Please note that ''<bus-volts>'' is now '''deprecated'''. Use ''<minimum-supply-volts>'' instead.
The following is a copy of a comment in instrument source, explaining the use of Mode-S related properties
<
// Mode-S transponders (configured with mode = 2) can transmit a ground bit to
// indicate ground operation. If auto-ground is not defined, the ground bit is
// switched manually by setting the transponder knob to GND. If auto-ground is
// defined, the transponder simulates automatic switching of the ground bit
// using the value of the property defined in auto-ground.
//
// For a squat switch, use "/gear/gear/wow". For automatic switching based on
// airspeed, use a property rule to make a new boolean property that indicates,
// for example, airspeed < 80, and reference your new property in auto-ground.
//
// Note that Mode-A and Mode-C transponders do not transmit a ground bit, even
// if the transponder knob is set to the GND position.
//
// Mode-S transponders also transmit indicated airspeed and Mach number. The
// default sources are "/instrumentation/airspeed-indicator/indicated-speed-kt"
// and ".../indicated-mach", but this can be changed by setting "airspeed-path"
// and "mach-path" properties respectively as shown above.

==Related content==
===Wiki articles===
*[[Howto:Develop an aircraft transponder in Nasal]] – Most probably obsolete
*[[FLARM]]
*[[Multiplayer protocol]] – The IDs 1501-1503 are earmarked for transmitting transponder properties
*[[OpenRadar: Transponder]]
*[[Traffic alert and collision avoidance system]]

===Forum topics===
*[https://forum.flightgear.org/viewtopic.php?f=4&t=31492 Transponder properties over MP] (January-June 2017)
*[https://forum.flightgear.org/viewtopic.php?f=75&t=19826 Transponder over network] (April-December 2018)
*[https://forum.flightgear.org/viewtopic.php?f=4&t=6395 Transponder] (November 2009-December 2010)

===Developer mailing list===
*[https://sourceforge.net/p/flightgear/mailman/message/30785263/ <nowiki>[</nowiki>Flightgear-devel<nowiki>]</nowiki> Improve tranponder instrument] (Apr 2009)
*[https://sourceforge.net/p/flightgear/mailman/flightgear-devel/thread/1388915221.2195.15.camel%40duter.localdomain/#msg31810053 <nowiki>[</nowiki>Flightgear-devel<nowiki>]</nowiki> Transponder Ident not transmitted via MP Protocol?] (Jan-Feb 2014)

===Source code===
*{{flightgear source|src/Instrumentation/transponder.hxx}}
*{{flightgear source|src/Instrumentation/transponder.cxx}}

[[Category:Aircraft enhancement]]
[[Category:Aircraft instruments]]

Transponder

2026-05-23T19:52:21Z

Octal450: /* Mode IDENT */

'''Transponders''' are radio beacons which make [[aircraft]] more identifiable on [[ATC]] displays and systems and by other aircrafts. Modern transponders support transmitting additional data such as an identification ('squawk') code and aircraft altitude. See more at {{wikipedia|Transponder (aeronautics)}}.

== ID Codes ==
* The ‘squawk code’ 7000 is used for VFR flights in Europe, while in the US, 1200 is used for the same purpose.
* IFR aircraft will be assigned an “attributed code” by ATC services at clearance delivery time, typically during startup. The code is selected by ATC from a regionally allocated pool of currently unused codes.
* NATO and other military aircraft sharing civil airspace use several codes from conventional tables, such as “0300 or 0400 - NATO - CAOC 9 Exercises (activated by NOTAM)” and “3500 - NATO - Aircraft receiving a service from AEW aircraft.”
* An aircraft unable to use voice radio communications will select the special code 7600.
* An aircraft experiencing an emergency (technical, medical, etc.) will select the special code 7700.

While some codes are used worldwide, such as the emergency codes, other codes have different regional meanings, like the special code ‘0000’.

* In the UK, by convention, the code ‘0000’ may be automatically selected by some transponders to report a transponder malfunction; pilots are not allowed to select it manually.
* In Europe, it is no longer used and its use has become prohibited. In the early days of transponders (Mode A), it was used to indicate “no ORCAM code inserted yet.” Its use today is strictly forbidden.
* In the US, it is a bit more confusing:
** It is used for some military interception operations.
** It may be used by ARTCC en route control centers for aircraft in cruise within controlled airspace when no more unassigned ORCAM codes are available.
** The Department of Transportation and the FAA have advocated, since 1981, for abandoning its use and moving toward full prohibition.

ref. https://en.wikipedia.org/wiki/List_of_transponder_codes

Codes are composed of a sequence of 4 digits, each with 8 possible values, ranging from [ 0 ][ 0 ][ 0 ][ 0 ] to [ 7 ][ 7 ][ 7 ][ 7 ].

Codes specifically define either:

* 1 aircraft, and 1 aircraft only;
* 1 particular situation.

== Special Codes ==
Codes ending in “00” define situations.

* 7500 - Hijacking
* 7600 - Unable to use voice radio communications - “Communications failure”
* 7700 - Emergency (technical / medical)

These codes do not identify 1 aircraft only.

Codes ending with other numbers (0 to 7) identify 1 and only 1 aircraft.

* They are assigned by ATC, usually by radio during departure clearance.
* They can be changed during the flight to accommodate traffic management needs.

Codes identifying 1 and only 1 aircraft are called discrete or conspicuous codes.

Codes defining situations are called non-discrete or non-conspicuous codes.

This is also why transponder codes are called Conspicuity Codes.

ref: https://skybrary.aero/articles/discrete-and-non-discrete-ssr-codes

== ORCAM method ==
There are far more aircraft to manage than available squawk codes.

To solve this problem, the ORCAM method is used.

ORCAM stands for Originating Regional Code Allocation Method.

Every region, airspace, airport, or service (such as military operations) is assigned a range of codes.

When an aircraft leaves one controlled zone and enters another, if, the current code conflicts with another code already in use nearby, ATC will ask the aircraft to recycle the code and select a new unused one.

ORCAM is a method, not a “table,” although the method excludes a subset of fixed codes from its management, and those are defined in tables.

Note that the following table is valid for the UK only; the US and Europe use some different assignments.

https://www.flightradars.eu/squawkcodes.html#top

== Modes A, B, C, S ==
Detailed illustrated explanation:

* https://skybrary.aero/articles/transponder
* https://pilotinstitute.com/transponder-modes-explained
* https://en.wikipedia.org/wiki/Aviation_transponder_interrogation_modes

Needs are constantly evolving, and technology merely adapts to those changes. Transponder modes are a reflection of the evolution of those needs.

=== Mode A ===
From the WWII era, when aircraft were returning and approaching their bases, it was difficult to determine whether they were Friend or Enemy (FOE). To avoid unwanted activation of the DCA systems, pilots would activate a conventional code by switching a set of buttons ON and OFF to define an identity code.

After the war, this concept carried over into civil aviation, but the mode was very basic and additional identification features were soon desired.

=== Mode B ===
It was an evolution of Mode A, but due to some quirks it was quickly abandoned in favor of Mode C.

=== Mode C ===
It added reporting of aircraft altitude.

This reported altitude was originally transmitted after barometric correction, which led to several problems. In the later Mode S, this was changed to transmitting uncorrected altitude instead.

The reason for this is not obvious. Imagine an aircraft on final approach: an incorrectly set altimetric pressure could cause the aircraft to “hit” the ground before the runway, or touch down too late and trigger a runway excursion.

Other situations involving altitude busts (loss of vertical separation) have also occurred, although more rarely.

Mode C altitude reports are transmitted in 100 ft increments.

=== Mode S ===
Mode S has been a game changer.

In Mode C, there were too many aircraft sending information at the same time. The radio frequency was congested, and often life-and-death information became lost as a result of all the transponders “speaking at the same time.”

In Mode S, transponders are quiet and remain silent unless “interrogated” by the surveillance system.

Well, almost silent. The surveillance system needs to know whom to direct the interrogation to. For this reason, all transponders still continue to repeatedly emit a very short ID called the squitter.

The surveillance system keeps a table of all the squitters for management.

With the frequency no longer congested, interrogated transponders have the ability to send more extensive information.

Mode S itself has 2 variants: ELS and EHS, meaning ELementary Surveillance and EnHanced Surveillance.

The former sends altitude (before calibration), speed, direction, and a few more aircraft and flight parameters.

The latter also sends the “selected” altitude in the autopilot, which allows ATC to detect misunderstandings early and prevent possible level busts before they happen.

ref.: https://skybrary.aero/articles/mode-s

Mode S altitude reports are in 10 ft increments, which is uncalibrated.

To do this, the transponder needs an altitude source. In real life this can be a separate box called an encoder, or it may be derived from FMC / ADIRU sources. It's important to note this altitude is referenced to standard pressure (29.92 inHg / 1013 hPa), and is not corrected for actual barometric pressure in the local environment.

Additional support for military modes is possible if anyone wishes to add it.

== Transponder in the Cockpit ==
Bear in mind that no two transponders are exactly the same.

* Older aircraft may still have older transponders that are not Mode S capable.
* There are several manufacturers with differing control panels.

Some transponders have a knob position labeled “ALTITUDE,” which can be Mode C or Mode S. Transponders with TCAS support usually use "TA/RA" and "TA" and "ON" modes instead of "ALTITUDE", all of which send altitude information.

The usual transponder modes encountered in real life are:

* Off - switched off / no power
* Test - maintenance mode
* Standby - powered on, but not sending information except the squitter (see above)
* Ground - sends out the squawk code only
* Altitude - in Mode C, sends altitude information; in Mode S, sends additional information as well

== Traffic and Resolution Advisories ==
* TA = Traffic Advisory
* RA = Resolution Advisory

On some transponders, TA/RA functions may be switched on separately.

Coordinated resolution advisory <big>require</big> '''Mode S''' in order to work properly.

A common myth is that Mode S and TA/RA should only be activated while airborne.

Nothing could be further from the truth.

Airports where visibility is frequently poor and foggy, such as Paris Orly, Milano Linate, Birmingham, among others, may require departing aircraft to activate Mode S and TA from the gate/stand, even before pushback. This is also standard practice in the United States.

TA on the ground uses a special mode with different sensitivity settings adapted to detect converging taxiing aircraft. Many severe accidents with fatalities have involved ground collisions.

Examples:

Scandinavian Airlines Flight 686 (a Scandinavian Airlines McDonnell Douglas MD-87) collided with a private Cessna Citation, resulting in 118 fatalities.
[https://en.wikipedia.org/wiki/Linate_Airport_disaster](https://en.wikipedia.org/wiki/Linate_Airport_disaster)

Paris Orly is historically so fog-prone that it became one of the first airports to develop “Turbo Clear” anti-fog systems in 1963. Airports around the world later adopted similar systems before the introduction of ATT (“Atterrissages Tous Temps” / “All Weather Landings”), precursors to modern Instrument Landing Systems.
[https://www.aeroport-paris-orly.com/systemes-anti-brouillard](https://www.aeroport-paris-orly.com/systemes-anti-brouillard)

The myth likely originates from the fact that procedures vary between airports and situations. Someone discovering the rule enforced at one airport may incorrectly assume the same rule applies everywhere.

Usually, airport administration and chart briefing pages clearly specify the procedures enforced at that particular airport.

On the ground:
* Mode S + Traffic Alert may be required.

Airborne:
* Mode S + Traffic Alert + Resolution Advisory is generally expected whenever available.
* Older aircraft frequently operating in controlled airspace are increasingly required to upgrade their transponders.

== Mode IDENT ==
Transponders have a separate function called IDENT, activated by pressing a dedicated button.

This is not actually a “mode” like Mode A, C, or S.

It should never be pressed unless requested by the ATC providing the service.

It also <big>must not</big> be activated automatically during squawk code changes, which is a frequent error.

IDENT allows ATC to instantly spot a particular aircraft among many others, and its sole purpose is to help in cases where conspicuity has been lost.

Squawk codes change quite frequently. If IDENT were activated every time a squawk code was recycled, many blips (aircraft symbols on the ATC screen) would constantly start blinking. Then, when ATC actually requests an aircraft to press IDENT, the usefulness of the feature would be lost because it would be drowned among many other IDENT activations.

== Configuration in FlightGear ==
Transponder support was overhauled in May 2013; earlier versions (2.10 and prior) have different support and are not documented here. Updating an aircraft to use the new config is straightforward. Key transponder properties (altitude, ident and transmitted-id) are now sent via the MP protocols for use in ATC clients.

The default altimeter can act as an altitude encoder; in its configuration, set either or both of the following boolean flags:

* encode-mode-c
* encode-mode-s

The transponder has various config properties:

* '''minimum-supply-volts''': required DV volts for operations, defaults to 8.0 ''(old '''bus-volts''' is now deprecated)''
* '''encoder-path''': defaults to '/instruments/altimeter', but can be changed to any other location. The transponder looks for child properties 'mode-c-alt-ft' and 'mode-s-alt-ft' at this path for altitude data.
* '''kt70-compatibility''': boolean, default to false. Set this to enable legacy compatibility with the old KT-70 C++ instrument. Do not use in new/updated aircraft!
* '''mode''': this is 0 for Mode-A, 1 for Mode-C and 2 for Mode-S. Other modes can be added, ask on the [[Mailing list|devel list]]!

=== Run-time properties ===
* '''altitude''': gives the transmitted altitude in feet (or -9999 for invalid)
* '''altitude-valid''': indicates if altitude value is valid data or not
* '''id-code''': allows the id-code to be read and set
* '''serviceable''': can be set to control the instrument serviceability
* '''transmitted-id''': gives the value being transmitted, including over the network via MP

==== Input properties ====
These live under <tt>/inputs</tt>.
* '''knob-mode''': sets the transponder operating mode. This corresponds to the KT-70 knob positions for convenience, but the actual modes should work for any transponder instrument. Knob modes are documented below
* '''ident-btn''': can be set to place the transponder in ident mode for 18 seconds. Note this property is not spring-loaded, i.e you must manually reset it to false
* '''digit[0]-[4]''': properties allow the id code individual digits to be read and set

In KT-70 compatibility mode, additional properties are read and set, to preserve legacy aircraft. Do not use these properties in new aircraft.

==== Knob/Functional Modes ====
* 0 - off
* 1 - standby, basically the same as off for the C++ code (3D instrument would power up the display, presumably)
* 2 - test, again the C++ largely ignores this since the test configuration of real-world instruments varies. In particular the unit does *not* set altitude or transmitted-id to any test values, you should do that in your own logic. (Maybe we should allow the test values to be defined int he config section?)
* 3 - Ground mode, responds to altitude interrogation but does not broadcast an ID. This would typically be used while taxiing prior to takeoff.
* 4 - On, normal operation but altitude transmission is inhibited
* 5 - Alt, same as on but altitude is broadcast if transponder was configured in Mode-S or Mode-C

=== Generic transponder ===
Below are all available property that you can set for your instrumentation.xml file :

<syntaxhighlight lang="xml">
<transponder>
<name type="string">transponder</name>
<number type="int">0</number>
<mode type="int">1</mode> 
<minimum-supply-volts type="double">8.0</minimum-supply-volts>
<encoder-path type="string">/instrumentation/altimeter</encoder-path>
<kt70-compatibility type="bool">0</kt70-compatibility>
<auto-ground>...</auto-ground> 
<airspeed-path>...</airspeed-path>
<mach-path>...</mach-path>
</transponder>
</syntaxhighlight>Please note that ''<bus-volts>'' is now '''deprecated'''. Use ''<minimum-supply-volts>'' instead.
The following is a copy of a comment in instrument source, explaining the use of Mode-S related properties
<
// Mode-S transponders (configured with mode = 2) can transmit a ground bit to
// indicate ground operation. If auto-ground is not defined, the ground bit is
// switched manually by setting the transponder knob to GND. If auto-ground is
// defined, the transponder simulates automatic switching of the ground bit
// using the value of the property defined in auto-ground.
//
// For a squat switch, use "/gear/gear/wow". For automatic switching based on
// airspeed, use a property rule to make a new boolean property that indicates,
// for example, airspeed < 80, and reference your new property in auto-ground.
//
// Note that Mode-A and Mode-C transponders do not transmit a ground bit, even
// if the transponder knob is set to the GND position.
//
// Mode-S transponders also transmit indicated airspeed and Mach number. The
// default sources are "/instrumentation/airspeed-indicator/indicated-speed-kt"
// and ".../indicated-mach", but this can be changed by setting "airspeed-path"
// and "mach-path" properties respectively as shown above.

==Related content==
===Wiki articles===
*[[Howto:Develop an aircraft transponder in Nasal]] – Most probably obsolete
*[[FLARM]]
*[[Multiplayer protocol]] – The IDs 1501-1503 are earmarked for transmitting transponder properties
*[[OpenRadar: Transponder]]
*[[Traffic alert and collision avoidance system]]

===Forum topics===
*[https://forum.flightgear.org/viewtopic.php?f=4&t=31492 Transponder properties over MP] (January-June 2017)
*[https://forum.flightgear.org/viewtopic.php?f=75&t=19826 Transponder over network] (April-December 2018)
*[https://forum.flightgear.org/viewtopic.php?f=4&t=6395 Transponder] (November 2009-December 2010)

===Developer mailing list===
*[https://sourceforge.net/p/flightgear/mailman/message/30785263/ <nowiki>[</nowiki>Flightgear-devel<nowiki>]</nowiki> Improve tranponder instrument] (Apr 2009)
*[https://sourceforge.net/p/flightgear/mailman/flightgear-devel/thread/1388915221.2195.15.camel%40duter.localdomain/#msg31810053 <nowiki>[</nowiki>Flightgear-devel<nowiki>]</nowiki> Transponder Ident not transmitted via MP Protocol?] (Jan-Feb 2014)

===Source code===
*{{flightgear source|src/Instrumentation/transponder.hxx}}
*{{flightgear source|src/Instrumentation/transponder.cxx}}

[[Category:Aircraft enhancement]]
[[Category:Aircraft instruments]]