FlightGear wiki - User contributions [en]

YouTube channels

2022-06-05T16:12:46Z

Anonymous2: Added new 3 channels

'''YouTube''' is an International free video sharing and social networking website and app on the internet. The website lets people upload, view, and share videos. YouTube was founded on February 14, 2005 by three former members of PayPal. Google has owned and operated YouTube since 2006. YouTube now carries paid advertisements on all pages.

== Channels that share contents about FlightGear ==
[https://www.youtube.com/channel/UCsXEFrdNHdVptY29WuN5VNg AeroOne]

[https://www.youtube.com/c/AVIONADE/ AVIONADE]

[https://www.youtube.com/channel/UCrVRffVIGcbPveC0Jx-bEIg Charly FlightGear Airline]

[https://www.youtube.com/user/PYCDorDek DorDek Kiddy]

[https://www.youtube.com/user/osjcag osjcag]

[https://www.youtube.com/user/FlightGearUKTV FGUK TV]

[https://www.youtube.com/channel/UCIHpioh89v6EVc2f3V-ToBw flight with realism]

[https://www.youtube.com/channel/UCZf9IU9DjLNlAqWbKvAlj_w FlightGear Polska]

[https://www.youtube.com/user/ThePalpatine59 FlightGear VMD]

[https://www.youtube.com/channel/UCNjxjEd54hYWR_IS5UwUZnw gerardll51]

[https://www.youtube.com/channel/UCpEh7CEVdBMERlmVn3WalxA Hornet]

[https://www.youtube.com/channel/UCexe4T0H9plEkiGY5njPGZg I make Videos]

[https://www.youtube.com/channel/UCpadzFrscZ8ZyiNLzrwVCZQ SE-JG | Johan G]

[https://www.youtube.com/channel/UCmB-vZlR03XU1RHE4DinEWw SP-ROM]

[https://www.youtube.com/channel/UCYAgyCtCB3I8SyS_8Fatu6w YLA Team]

Bombardier CSeries

2022-05-30T17:27:06Z

Anonymous2: Added GitHub link

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

The A220 (C-Series) is a bombardier made regional jet with 2 engines. It has 2 variants. A220-100 (CS100) and A220-300 (CS300). The A220 is a narrow body, twin-jet, medium range airliner. The -100 can carry 110 passengers and the -300 can carry 130 passengers.

Can be downloaded from https://github.com/GodBoyBr/CSeries

== Development ==
=== Liveries ===
'''CS100'''
* Bombardier {{Done}}
* Delta Airlines {{Done}}
* Lufthansa/Swiss International Airlines {{Done}}
* Malmo Aviation
* Ilyushin Finance Co.
* Gulf Air
* Odyssey
* Porter
* PrivateAir
* Merlion Virtual Airline {{Done}}

'''CS300'''
* Bombardier
* Air Baltic {{Done}}
* Atlas Jet
* lyushin Finance Co.
* Korean Air
* Lease Corporation
* Republic Airways
* Lufthansa/Swiss

== To Do ==
* Fly By Wire
* Cockpit Improvements
* Finish Cabin
* Glareshield Radio Panel
* FMC and CDU
* MFD Enhancements
* Fix A223 after A221 is decent

== Done==
* Exterior Model

=== Model & Effects ===
* Great Exterior Model
* 3D Cockpit with
** clickable Autopilot
** clickable Overhead display
** Canvas displays
**PFDs with system indicators

* Additional lights

=== Sounds ===
* uses 36 sounds of the [[Bombardier CRJ700 series]]
* Announcements

=== Systems & Dialogs ===
* Tutorial and failure dialog (left/right engine and flaps)
* IT-AUTOFLIGHT
* Airport Operations (Stairs, External Power)
* Pushback
* Fuel Balance
* A/C Registration
{{bombardier}}

[[Category:Airliners]]
[[Category:Twinjets]]

Talk:Suggested aircrafts

2022-05-29T08:27:31Z

Anonymous2: SidarDeha moved page Talk:Suggested aircrafts to Talk:Suggested aircraft: "Aircrafts" is wrong word

#REDIRECT [[Talk:Suggested aircraft]]

Talk:Suggested aircraft

2022-05-29T08:27:31Z

Anonymous2: SidarDeha moved page Talk:Suggested aircrafts to Talk:Suggested aircraft: "Aircrafts" is wrong word

[[User:SP-NTX|SP-NTX]] ([[User talk:SP-NTX|talk]]) 14:08, 28 May 2022 (UTC) Well, maybe someone should write WHY they are good, because only suggesting is not changing anything

Boeing E-3 Sentry

2022-05-28T09:16:53Z

Anonymous2: added related links

{{aero-stub}}
{{:{{PAGENAME}}/info}}
The '''Boeing E-3 Sentry''' is an American military airborne warning and control system (AWACS) [[aircraft]] that provides all-weather surveillance, command, control and communications, to the United States, United Kingdom, France, Saudi Arabia, and NATO air defense forces. Production ended in 1992 after 68 had been built.

== Design ==
The E-3 as equipped in USAF and NATO service can fly without refueling for 8 hours or 4000 miles, whilst newer examples in British, French and Saudi service, equipped with CFM56-2 engines can fly for 10 hours or 5000 miles without refuelling. Its range and on-station time can be increased through [[Howto: Air-Air Refueling|inflight refueling]] and the use of an on-board crew rest area. The range and loiter time can be used to alter the flight plan as required for operation reasons.

=== Variants ===
There is currently one variant modeled in [[FlightGear]]:
* E-3B

== Related links ==
[[Boeing EC-137R Sentry]]{{Boeing}}

Suggested custom scenery

2022-05-28T07:40:35Z

Anonymous2: Added Turkey, Şanlıurfa and Poland sceneries with links

Besides the official TerraSync scenery that is automatically synced while FlightGear is running, there are a number of custom sceneries available, created by users for beautifying some specific areas of the scenery. This page is a list of some '''suggested custom scenery''' for downloading and visiting. This list can not be complete as custom sceneries might come and go. It's worth to search the forum for additional custom sceneries.

FlightGear [[Changelog 2020.3#2020.3.7|2020.3.7]] and later will ''automatically'' download buildings, roads, pylons, and other objects, based on Open Street Map (OSM) data - see [[OSM2City 1st Worldbuild|OSM2City 1st world build]]. You don't have to download OSM2City custom sceneries for these anymore. (March 2021)

'''Quick update, March 2020/May 2020:'''

* See '''[[Suggested_airports]]''' for a quick list of featured airports situated in well developed regions, with links to OSM2City scenery. It's suitable for newcomers to start at to explore surrounding regions. (March 2020)

* '''[[Project3000]]''' adds a lot of clutter and buildings to airports which do not have models or details. It's a must have. It is planned to be integrated into the FG core eventually. [https://forum.flightgear.org/viewtopic.php?f=5&t=27688 Forum thread]. (March 2020)

* '''OSM2City scenery''' buildings, roads, pylons, and other objects, for the whole planet is now on TerraSync, and ''automatically downloaded'' by FlightGear [[Changelog 2020.3#2020.3.7|2020.3.7 and later]]. The current OSM2City output on TerraSync is from the [[Osm2city_worldbuild|1st world build of OSM2City]] scenery ([https://forum.flightgear.org/viewtopic.php?f=5&t=35581 forum thread]). Custom sceneries for countries and regions are available [[Areas_populated_with_osm2city_scenery|'''here''']]. Note: Old custom sceneries (before March 2021) will contain folders for OSM2City output like Buildings, Roads or Pylons with outdated and obsolete objects. These folders will override the new higher quality and faster rendering objects from TerraSync. Remember to remove these from your custom scenery folder list! If your custom scenery contains sub-folders that are not obsolete, like Terrain, you can leave these alone and only delete OSM2City sub-folders in your custom scenery folder. There are some OSM2City custom sceneries that are not obsolete - these have builds of OSM2City with different options from the 1st worldbuild - for example, custom scenery with auto-generation on in areas without good OSM coverage like the Hawaii custom scenery. (March 2021)

* '''[[:Category:Scenery_enhancement_projects|Custom terrain & region definition projects]]''': There are ongoing scenery enhancement projects to update both regional definitions and terrain in large areas like the [[Australia_Custom_Scenery|Australia]] (regional definitions are planned to be added to FG core). This a partial list, search the '''[https://forum.flightgear.org/viewforum.php?f=5 scenery forum]''' for details. Some of the output of projects like Hawaii terrain has already been integrated into Terrasync. (March 2020)

* Status of terrain in Terrasync: Terrasync scenery which is automatically downloaded has high resolution terrain. All of Europe currently has high resolution terrain from CORINE data. A lot of old pre-world scenery 2 should be obsolete. (March 2020)

* ''Status of next generation of scenery technology: World Scenery 3.0'': There is ongoing work being done towards WS 3.0 which will use [[Virtual Planet Builder]] (VPB) toolchain from the Open Scene Graph project, whose scenegraph is already used in Flightgear. A prototype of the world scenery technology is available in the FlightGear next branch, and an example scenery for the current prototype is available (March 2021). For more information see the [[World_Scenery_3.0_roadmap|World Scenery 3.0 Roadmap]]. To help with the WS 3.0 effort contact the team via the "[[Mailing lists|fg-devel]]" mailing list.
* ''Status of next world-build of scenery: World Scenery 3.x'': There is ongoing work towards the next world build - see the the [[World Scenery 3.0 roadmap]]. Contributing land cover and terrain data currently used in custom sceneries to the central repository when it's established in future will help get work into WS 3.0. It is intended for there to be a way to contribute improvements back to a central source. For example, a landcover shapefile server. People who have generated higher quality landcover and terrain for custom sceneries from multiple sources should keep in touch with WS 3.0 development to get their contributions in the next world build. Clipped landcover shapefiles from various sources used for WS 2.0 have been available for a while and re-generated in preparation for a new world scenery build, see [https://sourceforge.net/p/flightgear/mailman/message/36730169/ this] mailinglist post. WS3 development is organised via the "[[Mailing lists|fg-devel]]" mailing list. (March 2021)

* Status of terrain in custom sceneries: The page as it stands is missing almost all custom terrain. Some old island custom sceneries have been merged into the automatically downloaded sceneries terrasync. [[User:Wlbragg#Kansas_Custom_Scenery|Kansas/Midwest]] and [[US-Tennessee_Custom_Scenery|Tennessee]] are two examples of custom sceneries that aren't obsolete (March 2020).

:: ''If you are the creator of an island scenery you can add it to [[TerraSync]] by contacting the flightgear-devel [[Mailing_lists|mailing list]]''.

* Status of regional definitions in FG core: Areas with regional definitions and materials which use recent engine features, that are in areas with reasonably high resolution terrain, have ''extremely'' high fidelity at high settings. ''The following list is not comprehensive''. It's just off the top of my head.
::''Areas with regional definitions and materials that were updated with recent features like overlays and have high resolution terrain'':
:::Hawaii, Norway, Iceland, Sweden, Mediterranean landscapes (Spain, Sicily, Portugal, southern Italy, Greece).
::''Areas with partial overlays and developed scenery with high resolution terrain'':
:::Swizerland, Alps (in many countries), central Europe & England, Corsica.
::''Well developed areas with regional definitions that predate overlays'':
:::Alaska, Caribbean Islands, Bermuda, South America (lower res terrain), Grand Canyon, California (USA), Mojave Desert (lower res terrain than Europe), Madagascar (lower res terrain than Europe).
::''Somewhat recently developed areas:''
:::South Africa in places (lower res terrain), Dubai, Mediterranean part of Africa.

:: ''If you are the author of an existing scenery that has regional definitions and/or GPL compatible textures that are an improvement to what is present in [[FGData]] ([[Howto:Regional_texturing#Guidelines|Checklist]]), you can add it to FGData by having it reviewed and merged. Regional definitions can be merged even when the terrain part cannot be merged until a rebuild of the complete landmass is done.''

== Custom scenery that is not obsolete (May 2021) ==

''This is only a fraction of available scenery (May 2021). Search the [https://forum.flightgear.org/viewforum.php?f=5 scenery forum] for more.''

''See [[Howto:Install_scenery|How to install custom scenery packages]].''

* '''USA, Tennessee:''' custom scenery for Tennessee by [[User:Scttgs|Scott Giese]](xDraconianx). This is very high resolution scenery created to test potential resolution & performance for the next world scenery build. See the [https://forum.flightgear.org/viewtopic.php?f=5&t=35521 forum thread] for feedback and more info. See the [[US-Tennessee_Custom_Scenery|wiki page]] for downloads. (March 2020)

<gallery mode="packed">
File:US-Tennessee-EastCentral.jpg
File:US-Tennessee-West.jpg
File:US-Tennessee-East.jpg
File:US-Tennessee-WestCentral.jpg
</gallery>

* '''USA, Kansas & Ohio:''' custom scenery for the entire states of Kansas and Ohio created by [[User:Wlbragg|Wlbragg]]. This high resolution scenery includes textures. See the [[User:Wlbragg#Kansas_Custom_Scenery|wiki page]] for downloads and info. (March 2020)

<gallery mode="packed">
File:Kansas_Scenery_Two.jpg
File:KDAY_James_M._Cox_Dayton_International_Airport.jpg
File:Kansas_Scenery_One.jpg
File:Kansas_Scenery_Three.jpg
</gallery>

* '''Scandinavia''': custom scenery covering Scandinavian countries such as Norway, Sweden, and Finland by [[User:D-ECHO|D-ECHO]]. Norway and Sweden have some of the most detailed regional definitions using recent engine features. This custom scenery project further improves it by mainly adding more detailed land type classification, digital elevation data, as well as updated airports. As of March 2020 it updates parts of these countries. See the [[Scandinavia Custom Scenery]] page for download and details.

* '''USA, Pennsylvania, New Jersey, and New York City''': custom scenery for these Eastern US states by montagdude. See [https://forum.flightgear.org/viewtopic.php?f=5&t=38041 forum thread]. Contains custom terrain, OSM2City, and custom materials. (September 2020)

<gallery mode="packed">
File:Ec135-manhattan.jpg
File:Pa28-wilkes-barre.jpg
File:C182s-atlantic-city.jpg
File:Dr400-philadelphia.jpg
</gallery>

* '''USA, Virginia, Maryland, Delaware, and the District of Columbia''': custom scenery for these Mid-Atlantic US states by montagdude. See [https://forum.flightgear.org/viewtopic.php?f=5&t=37322 forum thread]. Contains custom terrain, OSM2City, and custom materials. (April 2020)

* '''USA, Rhode Island and southeastern Massachusetts''': custom scenery for Rhode Island and southeastern parts of the state of Massachusetts by montagdude. See [https://forum.flightgear.org/viewtopic.php?f=5&t=36977 forum thread]. Contains OSM2City. (March 2020)

* '''USA, Champaign, Chicago, Milwaukee and surrounding areas''': custom scenery for Champaign, Bloomington, Chicago, Milwaukee and northern Illinois by pb321. See [https://forum.flightgear.org/viewtopic.php?f=5&t=39209 forum thread] and to report issues. Contains OSM2City and (optional) color corrected USGS orthophotos. (May 2021)
<gallery mode="packed">
File:KPWK-Chicago_Executive.jpg
File:ChicagoAM-OrthoCropped.jpg
File:Approaching KMKE.jpg
</gallery>

* '''USA, Oshkosh, Green Bay, U.P. of Michigan and surrounding areas''': custom scenery for Oshkosh, Appleton, Green Bay and the central Upper Peninsula of Michigan by pb321. See [https://forum.flightgear.org/viewtopic.php?f=5&t=39264 forum thread] and to report issues. Contains OSM2City and (optional) color corrected USGS orthophotos. (May 2021)
<gallery mode="packed">
File:GreenBayNorth.jpg
File:Near Houghton MIa.jpg
File:MarquetteA.jpg
</gallery>

* '''Venezuela: [[Project Venezuela]]:''' custom scenery for Venezuela by [[User:Legoboyvdlp|J. Redpath]], with improved airport layouts, and objects at several airports. Highly improved over TerraSync status. (March 2020)

* '''Canary Islands:''' custom scenery for the Canary Islands by [[User:D-ECHO|D-ECHO]] with improved terrain, objects, vegetation, building, reworked airports, mostly with buildings and furniture. Check out the [[Canary_Islands_Custom_Scenery|wiki page]]. (March 2020)

<gallery mode="packed">
GCLP-1.jpg
GCLP-2.jpg
GCLP-3.jpg
</gallery>

* '''Argentina''': OSM-based custom scenery for Argentina and parts of Chile and Uruguay by Barta. Updated airports, landcover from OSM polygons, line data and objects using Osm2City. Updated frequently! Downloads:
:: All output: [http://scenery.bartatech.net/ http://scenery.bartatech.net/] . As of July 2020 these areas are available: Santiago (including Valparaiso), Mendoza, Buenos Aires, complete Rosario area. The other parts only have terrain (no roads, buildings etc). The server will eventually contain all of the sceneries in the southern cone of South America: Argentina, Chile, Uruguay.
::: It's possible to use the [http://scenery.bartatech.net/ scenery.bartatech.net] server directly as a Terrasync server. Just use the following in the [[FlightGear_Qt_launcher|launcher]] or .fgfsrc file:
::: ''--prop:/sim/terrasync/http-server=<nowiki>http://scenery.bartatech.net/</nowiki>''
:: Buenos Aires province: https://github.com/bartacruz/scenery-6040
:: Cuyo Area + Santiago: https://github.com/bartacruz/scenery-cuyo

* '''USA, Florida''': custom scenery for Florida by [[User:Legoboyvdlp|J. Redpath]] with both terrain and OSM2City. It also covers the [[Space Shuttle]] landing site at [[Shuttle_Landing_Facility|KTTS]]. See the [https://github.com/legoboyvdlp/Florida-fg-CustomScenery repository] downloads section for the [https://github.com/legoboyvdlp/Florida-fg-CustomScenery/archive/master.zip zip-file].

* '''London, England''': custom scenery by [[User:Legoboyvdlp|J. Redpath]] for the London area including an improved Gatwick Airport (ICAO: EGKK). See the [https://forum.flightgear.org/viewtopic.php?f=5&t=37444 forum thread] and [https://github.com/legoboyvdlp/London-fg-CustomScenery repository] downloads section for the [https://github.com/legoboyvdlp/London-fg-CustomScenery/archive/master.zip zip-file].

* '''Moscow area, Russia''': custom scenery by [[User:Legoboyvdlp|J. Redpath]] for the Moscow area covering 14 tiles. See the [https://forum.flightgear.org/viewtopic.php?f=5&t=37887 forum thread] for the github [https://github.com/legoboyvdlp/Moscow-fg-CustomScenery/archive/master.zip download]. (August 2020)

* '''Valdivostock area, Russia''': custom scenery by [[User:Legoboyvdlp|J. Redpath]] for the Vadivostock area. See the [https://forum.flightgear.org/viewtopic.php?f=5&t=37887 forum thread] for the github [https://github.com/legoboyvdlp/Vladivostok-fg-CustomScenery/archive/master.zip download]. (August 2020)

* '''Eastern China''': custom scenery by [[User:Legoboyvdlp|J. Redpath]] for the eastern portion of China covering the area around ZSAM and ZSNJ airports. See the [https://forum.flightgear.org/viewtopic.php?f=5&t=37887 forum thread] for the github [https://github.com/legoboyvdlp/EastChina-fg-CustomScenery/archive/master.zip download]. (August 2020)

* '''Beijing area, China''': custom scenery by [[User:Legoboyvdlp|J. Redpath]] for the area around Beijing covering 15 tiles. See the [https://forum.flightgear.org/viewtopic.php?f=5&t=37887 forum thread] for the github [https://github.com/legoboyvdlp/Beijing-fg-CustomScenery/archive/master.zip download]. (August 2020)

* '''Sri Lanka''': 2019 custom scenery by [[User:Legoboyvdlp|J. Redpath]] for the island of Sri Lanka in the Indian ocean including rebuilt terrain, OSM2City output, and improved airports. See the [https://forum.flightgear.org/viewtopic.php?f=5&t=37887 forum thread] for github [https://codeload.github.com/legoboyvdlp/SriLanka-fg-CustomScenery/zip/master download].
* '''Dominican Republic:''' 2021 custom scenery by flc972 for [[Gregorio Luperon International Airport]] (MDPP) with detailed modeling of interiors, night lightmaps, ground net and animated jetways as well as some terrain. The airport is located on the Caribbean island of Hispaniola. See the [https://forum.flightgear.org/viewtopic.php?f=5&t=39179 forum thread] for bitbucket [https://bitbucket.org/fableb/flcs-mdpp_airport/downloads/ download] .
* '''Turkey:''' custom scenery including 12 airports. Can be downloaded from https://github.com/Klaudiae/FGCompanion-TurkeyEnhanced
* '''Turkey, Şanlıurfa:''' custom scenery by TheFGFSEagle. Can be downloaded from https://github.com/TheFGFSEagle/LTCS-scenery
* '''Poland:''' custom scenery including 14 airports. Can be downloaded from https://github.com/Klaudiae/FGCompanion-PolandEnhanced

== Custom scenery set to be merged into TerraSync and FGData ==

''These are now in the process of being merged. If you know of custom sceneries of islands or complete landmasses that have not been merged yet, contact the developers. (March 2021).''
* New Zealand scenery ([https://forum.flightgear.org/viewtopic.php?f=5&t=36892 forum thread]). (March 2020)
* [[Australia_Custom_Scenery|Australian custom scenery project]] output - Regional definitions, and textures. See these forum threads for download and details: [https://forum.flightgear.org/viewtopic.php?f=5&t=36145 official thread], demo scenery [https://forum.flightgear.org/viewtopic.php?f=19&t=36956 install details (March 2020)]. A partially completed Sydney airport (YSSY) is also available for download. The terrain in the demo scenery release is likely to be merged when a re-build of Australia is done.
* All Channel Islands (Jersey, Guernsey, Alderney, Sark, etc) ([https://github.com/legoboyvdlp/Jersey-fg-CustomScenery github]). (March 2020).
* Sri Lanka, [https://forum.flightgear.org/viewtopic.php?f=5&t=37887 forum thread] and [https://github.com/legoboyvdlp/SriLanka-fg-CustomScenery Github]

== Custom scenery which has been merged into TerraSync and FGData ==

''You can remove old scenery folders containing known merged sceneries from your [[Howto:Install_scenery|scenery folder list]].''

* Islands merged recently (2018-2019): Hawaii, Iceland, Island of Jan Mayen (Norway)

== Old and undetermined custom scenery ==

''Some of these may have been obsoleted by the release of the [[FlightGear World Scenery 2.0|new world scenery in November 2013]].''

''Please move sceneries that aren't obsolete into other categories.''

* '''France''': Custom scenery for France with improved landcover information and more detailed elevation information (no improvements on the objects) is under development. See the [[Custom France Scenery|Custom France Scenery page]]. (Pre WS 2.0)

<gallery>
Image:High_textures_transitions3.png|High detail France scenery
Image:High_textures_transitions4_1.png|High detail France scenery
Image:High_textures_transitions6_2.png|High detail France scenery
Image:High_textures_transitions10_1.png|Mont Blanc
Image:High_textures_transitions11_1.png|Aguille du midi?
Image:High_textures_transitions13_1.png|Matterhorn without landclass, just slope transitions
</gallery>

* '''Innsbruck (Austria) area''': The scenery currently covers a 1x1 degree area containing parts of Austria and Germany, and makes use of accurate data from the Corine Land Cover, and Open Street Map projects. See [http://forum.flightgear.org/viewtopic.php?f=5&t=5350 this forum post] and [[FlightGear Newsletter August 2009#Innsbruck Gets A Face Lift|the August 2009 newsletter]] for details. (Pre WS 2.0)

* '''LOWI & Austria Scenery Preview''': This scenery includes the Innsbruck scenario and is much more complete than the previous. It is still experimental, but should try it as having been really good. Info and download can be found [[Innsbruck Airport|here]].

* '''Iberian Peninsula: Spain and Portugal''': custom scenery for Spain and Portugal with improved landcover and additional airports and objects. See the [[Custom Spain and Portugal Scenery|custom Spain and Portugal scenery page]].

* '''EDDK''': Custom scenery for the Cologne/Bonn airport in Germany with very nice and realistic terminal buildings. Available from https://github.com/mherweg/EDDK-fg-CustomScenery.

* '''Argentina''': OSM-based custom scenery for Argentina and parts of Chile and Uruguay. Updated airports, landcover from OSM polygons, line data and objects using Osm2City. Updated frequently! Downloads:
** Buenos Aires province: https://github.com/bartacruz/scenery-6040
** Cuyo Area + Santiago: https://github.com/bartacruz/scenery-cuyo

{{suggested}}

[[Category:Custom scenery]]

Dornier 328

2022-05-27T14:33:49Z

Anonymous2: Added download link to template

{{infobox Aircraft
|image = Dornier328.2.jpg
|name = Fairchild Dornier 328-1XX (-100; -110, -120, -130) Turboprop
|type = Airliner
|livery = SkyWork, Dornier TAC1, Dornier TAC3, Dornier TAC4, Sun of Scandinavia, United Express, Air A!ps
|liverydbid =
|authors = Heiko Schulz (3D model, FDM)/Daniel Overbeck (Systems like Electrical; PFD, MFD, EICAS Display)/C. Le Moigne (CDU from CitationX)
|fdm = JSBSim
|status-fdm = 3
|status-systems = 3
|status-cockpit = 4
|status-model = 5
|fgname = do328-110
|note = "Available on FGAddon when ready"
|download =https://github.com/HHS81/do328
}}

{{infobox Aircraft
|image = Dornier_328-300_(Jet).jpg
|name = Fairchild Dornier 328-3XX (-300, -310; Envoy) Jet
|type = Airliner
|livery = ADAC, Dornier TAC2, Sun of Scandinavia, United Express, Greed Fictional
|liverydbid =
|authors = Heiko Schulz (3D model, FDM)/Daniel Overbeck (Systems like Electrical; PFD, MFD, EICAS Display)/C. Le Moigne (CDU from CitationX)
|fdm = JSBSim
|status-fdm = 2
|status-systems = 3
|status-cockpit = 4
|status-model = 5
|fgname = do328-300
|note = "Available on FGAddon when ready"
|download =
}}

[[File:DO328 CopilotView.jpg |thumb|270px |Latest progress: view from the CoPilot]]
[[File:DO328 JumpseatView.jpg |thumb|270px |Latest progress: Jumpseat View showing the canvas displays]]
[[File:DO328 Cockpit1.jpg|thumb|270px |Latest progress: cockpit overview - the sunvisors are adjustable!]]
[[File:DO328 PropCenterPedestal.jpg|thumb|270px |Latest progress: center pedestal of the Turboprop]]
[[File:DO328 Placards.jpg|thumb|270px |Latest progress: redable Safety Placards]]
[[File:Dornier 328 First Prototype.jpg|thumb|270px |First prototype of Dornier 328 in its House colors- model before prop had been textured but I do like the sky in the background and the light effect on the tail]]
[[File:Dornier 328 above the autrian alps.jpg|thumb|270px |upper side of the Dornier 328, showing wing structure]]
[[File:DO328 Multiple Lightmaps.jpg|thumb|270px|Testing the multiple lightmap feature.]]

The '''Dornier 328''' [[aircraft]] is a shortrange commuter, developed and built by [[Dornier|Dornier]]. It was the last flying aircraft made by Dornier, and the last airliner completely developed and built in Germany.

The FlightGear model is currently in development, simulating the Dornier 328-110 Turboprop with ground spoilers and the Dornier 328-300 Jet. It features a realistic fdm, detailed PFD, MFD and EICAS displays with many subpages, a realistic electrical systems and has an incredible good framerate. A very detailed cockpit is in progress and will feature ALS shadows and lightmaps. It will have the same good quality like the [[EC135|EC135 P2]] and [[Cessna 182S|Cessna 182 S]], with comparable good framerate!

Special Thanks to the user Groucho from the FlightGear forums, who made it possible for me look into the flight manual! Also special thanks to xcvb85 who is programming the systems and is responsible for the great Canvas displays and systems!

Can be downloaded from https://github.com/HHS81/do328

__TOC__

== NOTAM ==

# # Please regard FlightGear's etiquette: contact the authors first you help and contribute - this helps to prevent chaos in developing, since the efforts can be coordinated.

== History ==

The development has been started back in the 1980s as successor for the Dornier 228. Dornier found that there was a market for a 33-passenger aircraft, so they created an aircraft with a complete round fuselage and the TNT-wing (Tragflügel neuer Technologie = Wing of New Technology) of the Dornier 228.

Development started December 1988; its maiden flight was on December 6, 1991 and in October 1993 was certified.

The aircraft had been developed for high climb rate and high speed, but short landing which was possible due the wing and the new developed propeller. As non-typical for this class of aircraft the flight deck has been fitted with 5 Displays from the Honeywell Primus 2000 avionic. The cabin was very comfortable for its class, as it was wide and round, and there was an active electronic noise suppression, giving a jet-like feeling.

In the 90s turboprop aircraft were unpopular, as flight companies preferred smaller jets. So Fairchild-Dornier developed the Dornier 328 JET, a jet driven version of the Dornier 328.
There had been larger versions of this aircraft planned: Dornier 428 and 528, stretched versions of the Dornier 328, but these were never built.

When Fairchild-Dornier went bankrupt, the production of the Dornier 328 had been stopped in 2005, only 217 aircraft (prop and jet version) had been built, plus 3 prototypes.

=== Variants in real life===
There are 4 Turboprop- variants available, and 3 Jet variants:
* Dornier 328-100 (basic version, 33 passengers, Pratt & Whitney Canada PW119)
* Dornier 328-110 (increased MTOW by 350kg, increased range), Pratt & Whitney Canada PW119B)
* Dornier 328-120 (special short range equipment)
* Dornier 328-130 (higher speed, improved rudder, Pratt & Whitney Canada PW119C)

Ground spoilers and APU were optional on all turboprop variants

* Dornier 328-300/-310/ 328JET (jet driven version)
* Dornier 328 Envoy 3 (Business Jet version)
* Dornier 328DBJ (Replacement of the Envoy 3 with a larger cabin)

== Development notes ==
=== Features ===
==== FDM ====
* Realistic JSBSim fdm, matching AoA, Climbrates and [[Aircraft speed#V speeds|V speeds]] based on following Data:

<ref>datas like wing incidence, CoG, etc.... from the Original Flight Manual Dornier 328-100</ref>
<ref>{{cite web |url=http://www.flightglobal.com/pdfarchive/view/1995/1995%20-%203235.html |title=Pilot report |publisher=www.flightglobal.com }}</ref> <ref>{{cite web |url=http://compair.aviationresearch.com/database_files/TheImage_41.pdf |title=Pilot report 2 |publisher=compair.aviationresearch.com }}</ref> <ref>{{cite web |url=http://www.skybrary.aero/bookshelf/books/1285.pdf |title= Accident report |publisher=www.skybrary.aero }}</ref> <ref>{{cite web |url=http://www.caa.co.uk/docs/1455/SRG_FLT_CFS_284_Issue1_27072006.pdf |title= some stall speeds |publisher=http://www.caa.co.uk }}</ref> <ref>{{cite web |url=http://www.bfu-web.de/DE/Publikationen/Untersuchungsberichte/2001/Bericht_1X004-0.01.pdf?__blob=publicationFile |title= Accident Report Bremen 2001 |publisher= BFU Germany }}</ref> <ref>{{cite web |url=http://www.bfu-web.de/DE/Publikationen/Untersuchungsberichte/2004/Bericht_04_5X001-0-DO328-Saarbruecken.pdf?__blob=publicationFile |title= Accident report Saarbrücken |publisher=BFU Germany }}</ref> <ref>{{cite web |url=http://www.easa.eu.int/certification/type-certificates/docs/aircrafts/EASA-TCDS-A.096_DORNIER_328_Series-04-01082011.pdf |title= EASA Type certification |publisher=EASA }}</ref> <ref>{{cite web |url=https://assets.digital.cabinet-office.gov.uk/media/5423016ce5274a1314000aa1/Dornier_328_100__TF-CSB_1-08.pdf |title= Accident report Aberdeen }}</ref>
<ref>{{cite web |url=http://www.bfu-web.de/DE/Publikationen/Untersuchungsberichte/2008/Bericht_08_1X001_DO328_Mannheim_RE.pdf?__blob=publicationFile |title= Accident report Mannheim in german language }}</ref>
<ref>{{cite web |url=http://www.bfu-web.de/EN/Publications/Investigation%20Report/2008/Report_08_1X001_DO328_Mannheim_RE.pdf?__blob=publicationFile |title= Accident report Mannheim in english language }}</ref>
<ref>{{cite web |url=http://www.flashcardmachine.com/dornier.html | title= Real life procedures |publisher=flashcardgame }}</ref>

==== Systems ====
* Complex EFIS with many EICAS pages (but still not finished)
* Complex RMU with many features (but still not finished)
* Electrical System: Complex system which also simulates currents and bus ties
* Pressurization System: Nothing special

====328-1XX (Prop)====
* accurate 3d-model based on original drawings with many details like static discharge antennas, animation of each prop blade, latest shaders with dynamic reflections, rain and lightmaps (landinglight, logolight, winglight, beacon)
* correct size of tires (different to Jet version)
* correct animation of groundspoiler
* Ice shield on fuselage modelled
* realistic wing flex
* Flightdeck progress- PFD and MFD working; working throttle quadrant, autoflight panel in progress
* paintkit for Inkscape
* 3 different realistic liveries and one blank livery

====328-3XX (Jet)====
* accurate 3d-model based on original drawings with many details like static discharge antennas, latest shaders with dynamic reflections, rain and lightmaps (landinglight, logolight, winglight, beacon)
* correct size of tires (different to Prop version)
* realistic wing flex
* paintkit for Inkscape
* 2 different liveries

== To-do list ==
=== Near term tasks ===
==== FDM ====
# 328-1xx Prop: Fine Tuning engine and prop files for fuel and take off distance so it will match the published datas from FM.
# Correct groundspoiler logic (missing dependency on condition lever, different logic on jet version)
# Simulating roll spoiler (starts at aileron deflection > 4°)
# Simulating latch of throttle

==== Finishing the flightdeck ====
# Working autoflight panel
# Overhead Panel with fully 3d models knobs, switches, warning lights
# Center Pedestal
# Adding small details (pencils, placards...)

==== Systems ====
# Autoflight: More tuning, implement armed mode, add remaining operation modes
# Electrical System: Find out which devices are connected to which bus
# Fuel system: Pumps and valves missing
# Bleed air: Not even started
# Anti ice: Also missing

==== 3D-model ====
# Optimize for Rembrandt (No-shadow tags, lights)
# Realistic sounds

==== Dornier 328-300/JET ====
# Modifiying the flightdeck to jet version (Overhead panel, center pedestal, Primus 2000 EICAS)

=== Mid term tasks ===
# Add cabin

=== Long term tasks ===
All that is left

{{Appendix}}

{{Dornier}}

[[Category:Airliners]]
[[Category:Twin-engine aircraft]]
[[Category:Red Griffin ATC compatible aircraft]]

Dornier 328

2022-05-27T14:30:59Z

Anonymous2: Added GitHub link

{{infobox Aircraft
|image = Dornier328.2.jpg
|name = Fairchild Dornier 328-1XX (-100; -110, -120, -130) Turboprop
|type = Airliner
|livery = SkyWork, Dornier TAC1, Dornier TAC3, Dornier TAC4, Sun of Scandinavia, United Express, Air A!ps
|liverydbid =
|authors = Heiko Schulz (3D model, FDM)/Daniel Overbeck (Systems like Electrical; PFD, MFD, EICAS Display)/C. Le Moigne (CDU from CitationX)
|fdm = JSBSim
|status-fdm = 3
|status-systems = 3
|status-cockpit = 4
|status-model = 5
|fgname = do328-110
|note = "Available on FGAddon when ready"
|download =
}}

{{infobox Aircraft
|image = Dornier_328-300_(Jet).jpg
|name = Fairchild Dornier 328-3XX (-300, -310; Envoy) Jet
|type = Airliner
|livery = ADAC, Dornier TAC2, Sun of Scandinavia, United Express, Greed Fictional
|liverydbid =
|authors = Heiko Schulz (3D model, FDM)/Daniel Overbeck (Systems like Electrical; PFD, MFD, EICAS Display)/C. Le Moigne (CDU from CitationX)
|fdm = JSBSim
|status-fdm = 2
|status-systems = 3
|status-cockpit = 4
|status-model = 5
|fgname = do328-300
|note = "Available on FGAddon when ready"
|download =
}}

[[File:DO328 CopilotView.jpg |thumb|270px |Latest progress: view from the CoPilot]]
[[File:DO328 JumpseatView.jpg |thumb|270px |Latest progress: Jumpseat View showing the canvas displays]]
[[File:DO328 Cockpit1.jpg|thumb|270px |Latest progress: cockpit overview - the sunvisors are adjustable!]]
[[File:DO328 PropCenterPedestal.jpg|thumb|270px |Latest progress: center pedestal of the Turboprop]]
[[File:DO328 Placards.jpg|thumb|270px |Latest progress: redable Safety Placards]]
[[File:Dornier 328 First Prototype.jpg|thumb|270px |First prototype of Dornier 328 in its House colors- model before prop had been textured but I do like the sky in the background and the light effect on the tail]]
[[File:Dornier 328 above the autrian alps.jpg|thumb|270px |upper side of the Dornier 328, showing wing structure]]
[[File:DO328 Multiple Lightmaps.jpg|thumb|270px|Testing the multiple lightmap feature.]]

The '''Dornier 328''' [[aircraft]] is a shortrange commuter, developed and built by [[Dornier|Dornier]]. It was the last flying aircraft made by Dornier, and the last airliner completely developed and built in Germany.

The FlightGear model is currently in development, simulating the Dornier 328-110 Turboprop with ground spoilers and the Dornier 328-300 Jet. It features a realistic fdm, detailed PFD, MFD and EICAS displays with many subpages, a realistic electrical systems and has an incredible good framerate. A very detailed cockpit is in progress and will feature ALS shadows and lightmaps. It will have the same good quality like the [[EC135|EC135 P2]] and [[Cessna 182S|Cessna 182 S]], with comparable good framerate!

Special Thanks to the user Groucho from the FlightGear forums, who made it possible for me look into the flight manual! Also special thanks to xcvb85 who is programming the systems and is responsible for the great Canvas displays and systems!

Can be downloaded from https://github.com/HHS81/do328

__TOC__

== NOTAM ==

# # Please regard FlightGear's etiquette: contact the authors first you help and contribute - this helps to prevent chaos in developing, since the efforts can be coordinated.

== History ==

The development has been started back in the 1980s as successor for the Dornier 228. Dornier found that there was a market for a 33-passenger aircraft, so they created an aircraft with a complete round fuselage and the TNT-wing (Tragflügel neuer Technologie = Wing of New Technology) of the Dornier 228.

Development started December 1988; its maiden flight was on December 6, 1991 and in October 1993 was certified.

The aircraft had been developed for high climb rate and high speed, but short landing which was possible due the wing and the new developed propeller. As non-typical for this class of aircraft the flight deck has been fitted with 5 Displays from the Honeywell Primus 2000 avionic. The cabin was very comfortable for its class, as it was wide and round, and there was an active electronic noise suppression, giving a jet-like feeling.

In the 90s turboprop aircraft were unpopular, as flight companies preferred smaller jets. So Fairchild-Dornier developed the Dornier 328 JET, a jet driven version of the Dornier 328.
There had been larger versions of this aircraft planned: Dornier 428 and 528, stretched versions of the Dornier 328, but these were never built.

When Fairchild-Dornier went bankrupt, the production of the Dornier 328 had been stopped in 2005, only 217 aircraft (prop and jet version) had been built, plus 3 prototypes.

=== Variants in real life===
There are 4 Turboprop- variants available, and 3 Jet variants:
* Dornier 328-100 (basic version, 33 passengers, Pratt & Whitney Canada PW119)
* Dornier 328-110 (increased MTOW by 350kg, increased range), Pratt & Whitney Canada PW119B)
* Dornier 328-120 (special short range equipment)
* Dornier 328-130 (higher speed, improved rudder, Pratt & Whitney Canada PW119C)

Ground spoilers and APU were optional on all turboprop variants

* Dornier 328-300/-310/ 328JET (jet driven version)
* Dornier 328 Envoy 3 (Business Jet version)
* Dornier 328DBJ (Replacement of the Envoy 3 with a larger cabin)

== Development notes ==
=== Features ===
==== FDM ====
* Realistic JSBSim fdm, matching AoA, Climbrates and [[Aircraft speed#V speeds|V speeds]] based on following Data:

<ref>datas like wing incidence, CoG, etc.... from the Original Flight Manual Dornier 328-100</ref>
<ref>{{cite web |url=http://www.flightglobal.com/pdfarchive/view/1995/1995%20-%203235.html |title=Pilot report |publisher=www.flightglobal.com }}</ref> <ref>{{cite web |url=http://compair.aviationresearch.com/database_files/TheImage_41.pdf |title=Pilot report 2 |publisher=compair.aviationresearch.com }}</ref> <ref>{{cite web |url=http://www.skybrary.aero/bookshelf/books/1285.pdf |title= Accident report |publisher=www.skybrary.aero }}</ref> <ref>{{cite web |url=http://www.caa.co.uk/docs/1455/SRG_FLT_CFS_284_Issue1_27072006.pdf |title= some stall speeds |publisher=http://www.caa.co.uk }}</ref> <ref>{{cite web |url=http://www.bfu-web.de/DE/Publikationen/Untersuchungsberichte/2001/Bericht_1X004-0.01.pdf?__blob=publicationFile |title= Accident Report Bremen 2001 |publisher= BFU Germany }}</ref> <ref>{{cite web |url=http://www.bfu-web.de/DE/Publikationen/Untersuchungsberichte/2004/Bericht_04_5X001-0-DO328-Saarbruecken.pdf?__blob=publicationFile |title= Accident report Saarbrücken |publisher=BFU Germany }}</ref> <ref>{{cite web |url=http://www.easa.eu.int/certification/type-certificates/docs/aircrafts/EASA-TCDS-A.096_DORNIER_328_Series-04-01082011.pdf |title= EASA Type certification |publisher=EASA }}</ref> <ref>{{cite web |url=https://assets.digital.cabinet-office.gov.uk/media/5423016ce5274a1314000aa1/Dornier_328_100__TF-CSB_1-08.pdf |title= Accident report Aberdeen }}</ref>
<ref>{{cite web |url=http://www.bfu-web.de/DE/Publikationen/Untersuchungsberichte/2008/Bericht_08_1X001_DO328_Mannheim_RE.pdf?__blob=publicationFile |title= Accident report Mannheim in german language }}</ref>
<ref>{{cite web |url=http://www.bfu-web.de/EN/Publications/Investigation%20Report/2008/Report_08_1X001_DO328_Mannheim_RE.pdf?__blob=publicationFile |title= Accident report Mannheim in english language }}</ref>
<ref>{{cite web |url=http://www.flashcardmachine.com/dornier.html | title= Real life procedures |publisher=flashcardgame }}</ref>

==== Systems ====
* Complex EFIS with many EICAS pages (but still not finished)
* Complex RMU with many features (but still not finished)
* Electrical System: Complex system which also simulates currents and bus ties
* Pressurization System: Nothing special

====328-1XX (Prop)====
* accurate 3d-model based on original drawings with many details like static discharge antennas, animation of each prop blade, latest shaders with dynamic reflections, rain and lightmaps (landinglight, logolight, winglight, beacon)
* correct size of tires (different to Jet version)
* correct animation of groundspoiler
* Ice shield on fuselage modelled
* realistic wing flex
* Flightdeck progress- PFD and MFD working; working throttle quadrant, autoflight panel in progress
* paintkit for Inkscape
* 3 different realistic liveries and one blank livery

====328-3XX (Jet)====
* accurate 3d-model based on original drawings with many details like static discharge antennas, latest shaders with dynamic reflections, rain and lightmaps (landinglight, logolight, winglight, beacon)
* correct size of tires (different to Prop version)
* realistic wing flex
* paintkit for Inkscape
* 2 different liveries

== To-do list ==
=== Near term tasks ===
==== FDM ====
# 328-1xx Prop: Fine Tuning engine and prop files for fuel and take off distance so it will match the published datas from FM.
# Correct groundspoiler logic (missing dependency on condition lever, different logic on jet version)
# Simulating roll spoiler (starts at aileron deflection > 4°)
# Simulating latch of throttle

==== Finishing the flightdeck ====
# Working autoflight panel
# Overhead Panel with fully 3d models knobs, switches, warning lights
# Center Pedestal
# Adding small details (pencils, placards...)

==== Systems ====
# Autoflight: More tuning, implement armed mode, add remaining operation modes
# Electrical System: Find out which devices are connected to which bus
# Fuel system: Pumps and valves missing
# Bleed air: Not even started
# Anti ice: Also missing

==== 3D-model ====
# Optimize for Rembrandt (No-shadow tags, lights)
# Realistic sounds

==== Dornier 328-300/JET ====
# Modifiying the flightdeck to jet version (Overhead panel, center pedestal, Primus 2000 EICAS)

=== Mid term tasks ===
# Add cabin

=== Long term tasks ===
All that is left

{{Appendix}}

{{Dornier}}

[[Category:Airliners]]
[[Category:Twin-engine aircraft]]
[[Category:Red Griffin ATC compatible aircraft]]

YouTube channels

2022-05-27T13:05:51Z

Anonymous2: Created article

'''YouTube''' is an International free video sharing and social networking website and app on the internet. The website lets people upload, view, and share videos. YouTube was founded on February 14, 2005 by three former members of PayPal. Google has owned and operated YouTube since 2006. YouTube now carries paid advertisements on all pages.

== Channels that share contents about FlightGear ==
[https://www.youtube.com/channel/UCrVRffVIGcbPveC0Jx-bEIg Charly FlightGear Airline]

[https://www.youtube.com/user/PYCDorDek DorDek Kiddy]

[https://www.youtube.com/user/FlightGearUKTV FGUK TV]

[https://www.youtube.com/channel/UCIHpioh89v6EVc2f3V-ToBw flight with realism]

[https://www.youtube.com/user/ThePalpatine59 FlightGear VMD]

[https://www.youtube.com/channel/UCNjxjEd54hYWR_IS5UwUZnw gerardll51]

[https://www.youtube.com/channel/UCexe4T0H9plEkiGY5njPGZg I make Videos]

[https://www.youtube.com/channel/UCmB-vZlR03XU1RHE4DinEWw SP-ROM]

[https://www.youtube.com/channel/UCYAgyCtCB3I8SyS_8Fatu6w YLA Team]

Boeing EC-137R Sentry

2022-05-27T12:22:37Z

Anonymous2: Created article

{{Infobox aircraft|status-fdm=4|status-systems=5|status-cockpit=5|status-model=5|name=Boeing EC-137R Sentry|devel-repo=https://github.com/JMaverick16/KC-137R}}

The Boeing EC-137R Sentry, commonly known as AWACS, is an American airborne early warning and control (AEW and C) aircraft developed by Boeing. Derived from the Boeing 707, it provides all-weather surveillance, command, control, and communications, and is mainly used by the United States Air Force and NATO. The EC-137R is distinguished by the distinctive rotating radar dome (ROTODOME) above the fuselage.

Şanlıurfa GAP Airport

2022-05-27T12:02:50Z

Anonymous2: Created article

{{Infobox Airport|icao=LTCS|iata=GNY|city=Şanlıurfa}}

'''Şanlıurfa GAP Airport''' is an airport located in Şanlıurfa Province, Turkey. It is located about 18.3 nautical miles (33.9 km; 21.1 mi) northeast of the city centre of Şanlıurfa.

The airport is part of the Southeastern Anatolia Project, a regional development project in the area of the Atatürk Dam. The new airport is known as the "GAP airport" because it is designed to service the workers in the GAP project as well as the city of Şanlıurfa. Opened the 17 June 2007, it replaced the old Şanlıurfa Airport (IATA: '''SFQ''', ICAO: '''LTCH'''), which was located 9 km (5.6 mi) south of the city.

== Custom scenery to download ==
https://github.com/TheFGFSEagle/LTCS-scenery

Istanbul Airport

2022-05-27T11:46:13Z

Anonymous2: Added scenery download link

{{Infobox Airport|icao=LTFM|city=Istanbul|iata=IST|website=https://www.istairport.com/en}}

'''Istanbul Airport''' is the main international airport serving Istanbul, Turkey. It is located in the Arnavutköy district on the European side of the city.

All scheduled commercial passenger flights were transferred from Istanbul Atatürk Airport to Istanbul Airport on 6 April 2019, following the closure of Istanbul Atatürk Airport for scheduled passenger flights.

It served more than 37 million passengers in 2021, making it the busiest airport in Europe and 13th-busiest airport in the world in terms of total passenger traffic and by serving more than 27 million international passengers the 2nd-busiest airport in the world.

== Download scenery ==
Istanbul Airport is not available on 2020.3.x versions by default. You should install it from https://github.com/Klaudiae/FGCompanion-TurkeyEnhanced

Istanbul Airport

2022-05-27T11:42:51Z

Anonymous2: Fixed airport website

Istanbul Airport

2022-05-27T11:41:11Z

Anonymous2: Created "Istanbul Airport" article

{{Infobox Airport|icao=LTFM|city=Istanbul|iata=IST|website=www.istairport.com}}

'''Istanbul Airport''' is the main international airport serving Istanbul, Turkey. It is located in the Arnavutköy district on the European side of the city.

All scheduled commercial passenger flights were transferred from Istanbul Atatürk Airport to Istanbul Airport on 6 April 2019, following the closure of Istanbul Atatürk Airport for scheduled passenger flights.

It served more than 37 million passengers in 2021, making it the busiest airport in Europe and 13th-busiest airport in the world in terms of total passenger traffic and by serving more than 27 million international passengers the 2nd-busiest airport in the world.

ATR 72-500

2022-05-27T11:16:46Z

Anonymous2: Added GitHub link

{{Stub}}
{{:{{PAGENAME}}/info}}
[[File:ATR_72-500-cabin.jpg|thumb|300px|The interior cabin.]]

The '''ATR 72-500''', also known as the '''ATR 72-212A''', is a short-haul twin-engine turboprop airliner manufactured by the French-Italian aircraft company ATR. It seats up to 78 passengers and is flown by a two-person crew. The ATR 72-500 is an upgrade of the original ATR 72-200 and is equipped with PW127F or PW127M engines with 6-blade propellers. It also features increased takeoff weights and higher overall performance.

Improved version can be downloaded from https://github.com/FGMEMBERS/ATR72

== Aircraft help ==
For general aircraft help and information, look under the <code>Docs/</code> folder. It is recommended to read over <code>README.pdf</code> before flying this airplane, especially the section about tiller steering.

== Development status ==
=== Completed ===
# 3D model
# 3D [[cockpit]]
# [[YASim]] FDM
# Engine control system
# Hydraulics system
# Passenger cabin
# Lights

=== To-Do ===
# Improve cockpit
# FDM tweaking

== External links ==
* [http://forum.flightgear.org/viewtopic.php?t=10634 Development topic at the FlightGear Forums]
* [http://en.wikipedia.org/wiki/ATR_72#ATR_72.E2.80.93500 ATR 72-500 at Wikipedia]

Lockheed Constellation

2022-05-27T10:58:22Z

Anonymous2: Added GitHub link

''This includes the following models: Lockheed 1049H Super Constellation''
{{:{{PAGENAME}}/info}}

[[Image:Checklistready.png|link=Aircraft Checklists]][[Image:Dualcontrolready.png|link=Dual control]]

The '''Lockheed Constellation''', affectionately known as the “Connie”, was a four-engine propeller-driven airliner built by [[Category:Lockheed|Lockheed]] between 1943 and 1958 at its Burbank, California, USA, facility. A total of 856 aircraft were produced in four models, all distinguished by a distinctive triple-tail design and graceful, dolphin-shaped fuselage. It was used as both a civilian airliner and U.S. military air transport plane, seeing service in the Berlin Airlift and as the presidential aircraft for U.S. President Dwight D. Eisenhower.

The Lockheed L-1049 Super Constellation was a member of the Lockheed Constellation aircraft line, and was Lockheed's response to the successful [[Douglas DC-6|Douglas DC-6]] airliner, first flying in 1950. The L-1049H variant flew on November 20, 1956. Called "Super H" and "Husky", the L-1049H was a convertible passenger/freight aircraft, mating a C-121C-based fuselage with L-1049G components. The cargo hold had a volume of 565 ft³ (16 m³) when including the lower hold. The aircraft could carry up to 120 people with seats, luggage lockers and toilets all available along with the option of decorating the walls of the aircraft. When not in use, the luggage lockers and seats could be stowed in the lower hold.

The aircraft entered service with QANTAS a month later. Some L-1049G and H aircraft in later production were fitted with the TC-18EA series engines used on the L-1649 Starliner. A final variant was planned in 1957, known as the L-1049J. Powered by four R-3350-988-TC-18EA-6 engines, the L-1049J was based on the L-1049H with the wings of the R7V-2 Constellation and an extra fuselage-mounted fuel tank.

Improved version can be downloaded from https://github.com/puku-777/Lockheed1049h

==Compatibility==

FlightGear 2.x: Loads and runs 
FlightGear 3.0: Loads and runs 
FlightGear 2016.4:Loads and runs 

== External links ==
* {{wikipedia|Lockheed Constellation}}

== Current features ==

As of version 3.0 (May 2017), advanced features of the Lockheed1049h include:

* [http://liveries.flightgear.org/aircraft.php?id=54&display=2 Livery support].
* Realistic and tuned FDM.
* Realistic and tuned, 1956-vintage autopilot (but the generic autopilot dialog also works, for beginners).
* Realistic and complex fuel system with several presets, from no fuel management for beginners to full manual fuel management.
* Detailed checklists.
* Engine fire.
* Engine fire extinguishing.
* Fuel jettison.
* Realistic Fuel and Payload system.
* Dynamic load factor and speed limits (they depend on flight conditions).
* Windshield wipers.
* Autostart via the checklists.
* Dual control with a pilot and a flight engineer, using an all-new multiplayer protocol (not compatible with earlier versions of the Lockheed1049h).

== Future (planned) features ==

* Realistic electrical system to power lights, engine starter, instruments, autopilot, auxiliary fuel pumps.
* Realistic hydraulic system to power control surfaces, main fuel pumps, brakes.
* Pressurization?
* Radar?

{{Lockheed}}

[[de:Lockheed Constellation]]

[[Category:Airliners]]
[[Category:Propeller aircraft]]
[[Category:Aircraft with Checklists]]

Concorde

2022-05-27T10:54:34Z

Anonymous2: Added GitHub link and a note

{{:{{PAGENAME}}/info}}
The '''Aérospatiale-BAC Concorde''' supersonic transport (SST) was the more successful of the only two supersonic passenger [[:Category:Airliners|airliners]] to have ever operated commercially, the [[Tupolev Tu-144]] being the other.

As a result of the type's only crash on 25 July 2000, world economic effects arising from the 9/11 attacks, and other factors, operations ceased on 24 October 2003. The last "retirement" flight occurred on 26 November that year.

The Concorde has been in development for a long time with [[FlightGear]], and it has many advanced abilities including ability to control different wing and systems, 3D interior locations, and animations.

Improved version can be downloaded from https://github.com/FirstOfficerDelta/Concorde

Note: Screenshots are outdated and improved version has better cockpit.

== '''Panels & Instrumentation''' ==
The Concord-Model comes with 2 panel-versions:
# '''with 2 “2D”-panels''': The "2D-Main" contains only the major System-Controls, independent of the location and or grouping in the real aircraft. In addition it combines some complex functions into simple buttons or switches (e.g. the fuel pumping tasks). This 2D-panel gets supported by only one very “faked” engineering panel (to be reached with “upper S” from the 2D-panel). These 2 “non realistic” panels make it much easier to “get a first feeling”, prior to having to concentrate onto the Concorde unique technicalities.
# '''and many 3D-panels''' (Captain, Co-pilot, Center, Overhead, Engineer, Pedestals, etc.). With those panels you may discover the whole wide range of this technical masterpiece.

You can switch between 2D and 3D in the usual manner ''(menu → View → “Toggle 2D Panel”)''. In addition the system switches automatically from 2D into 3D if you change the view-direction – and will return to 3D when the view returns to the standard setting.
 
The following description covers both versions – thus all common instruments are numbered the same in both versions. Instruments not shown in the simple 2D-version are indicated in the description by “no2D”.
 
The panel pictures show all “Hot-Spots”, i.e. areas in which you can adjust the values by mouse-clicks. Notice that many datum-fields do have up to 8 fields to set. See e.g. the NAV settings '''(55)''' in the Autopilot: The most left 2 vertical spots increase/decrease just the most left digit. The second pair the digits 2 and 3 (and overflow into 1), the next pair the first decimal digit, etc.
 
For a more detailed descriptions and real photos of the cockpit etc. see e.g. http://www.concordesst.com/cockpitsys.html

=== The 2D-Panels ===
[[File:Concord-Panel-2D.jpg|600px]]
 
In the center you see the standard instruments, on top the Autopilot, and on the right the Fuel handling. Especially the Fuel-Handling in the 2D-version is not realistic at all, for “reality” key “Ctrl+E” (and return with the same “Ctrl+E”).

Typing “Uppercase + S” will bring you (after about 10 sec!) to:

'''The additional 2D-Engineering-Panel:''' 
[[File:Concord-Engineering-Panel-2D.jpg|600px]]
 Because of the very long response-times while switching back and forth we suggest to get used to just moving the angle of view ''(if e.g. you want to see the engine instruments or similar)'', the 3D panel then pops up at once!

=== The 3D-Panels ===
[[File:Concord-Main-Panel.jpg|800px]]
 In addition to the 2D-panel-instrumentation you see here especially the center with the Engine-Controls and to the right ''(already on the Co-Pilots side)'' the Gear, Nose and Trim-controls. On top of all is the “Autopilot” or formally the AFCS = “Automated Flight Control System”.

Key “f” if you do not see all instruments on a panel. The amount of displayed instruments is reduced by default, in order to not reduce the frame rate of your PC - “f” cancels these display-limitation.
 
''>>>> Other panels will be shown when unique tasks are described <<<<<''

 
=== Description of the Basic-Instruments ===
''Some instruments are not available in the 2D-panel. Those you find by keying “upper S” to look onto the 2D-engineering panel. But that switch takes very long. So I suggest to use 2D at the beginning. When the wanted instrument is not there just change the view-point and the 3D-panel pops up. And if it is not there use CTRL+E to go to the 3D-Engineering panel. Whenever you reset the view-point the 2D-panel will again pop into the foreground (unless you disable that be selecting "Menu --> View --> Toggle 2D Panel”.
 All instruments in the pictures are labeled with numbers within a light circle, except the AFCS buttons which are referred to by there visible big inscription. In the description the numbers are referred to by (nn). ''(no2D)'' means that there is no equivalent in 2D-panels.
The picture of the 3D-panel shows only the left and the center part of the main panel. The right part is just a replication of the Pilot-instruments for the Co-Pilot, those instruments would carry the same numbers.
 
<ol>
<li>Not yet used
<li>'''ATT-INS 1/2''' ''(no2D)'': (Not yet functional)
<li>'''COMP 1/2''' ''(no2D)'': (Not yet functional)
<li>'''DEV 1/2''' ''(no2D)'': Switches '''(18)''' to display either NAV1 or NAV2
<li>'''NAV INS 1/2''' ''(no2D)'': Switches between left/right INS (Inertial Navigation System) on the center pedestal
<li>'''G-meter + AoA''' (angle of attack) ''(no2D)'': The index at the left shows the actual “G”-forces (forces that occur when accelerating a body), the white bar on the right the actual AoA.
<li>'''Warnings:'''
<ul><li>TERRAIN:
<ul><li>excessive rate of descent below 2500 ft.
<li>excessive closure rate with ground.
<li>loss of altitude below 700 ft, after takeoff or go-around.
<li>gear not locked below 500 ft, or nose not down below 200 ft on approach
<li>Nose not down at Touch-Down
</ul><li>M/CG: Center of Gravity is out of tolerance ''(see '''(20)''' and chapter "[[#Balancing by Fuel-Pumping|Balancing by Fuel-Pumping]]")''
<li>TYRE: Tire pressure at fault (tyre=BR == tire=Am)
</ul>
<li>'''CAS''' (Calibrated Airspeed in Knots): The white pointer indicates the actual CAS analog (and digital), the yellow one indicates the maximum allowed CAS (according to altitude, density, temperature, etc.). The yellow light at the upper left corner is on when the autopilot '''(IA)''' is acquiring a CAS.
<ul><li>'''8a''' ''(no2D)'': A backup for '''(8)'''
<li>'''8b:''' The same as '''(8)''', but in Mach. In addition there are 2 moving yellow markers indicating the minimum and maximum Mach numbers according to the M/CG '''(31)'''.
</ul>
<li>'''DME:''' Distance in miles to VOR/ILS 1 and 2
<li>'''TAS:''' Actual airspeed over terrain in kt/h
<li>'''VOR 1/2'''-pointer, direct pointing into the directions of the VOR's, set in '''(55)''' and '''(64)''' (see also [[#The VOR/INS/ILS System|The VOR/INS/ILS System]]). (The yellow pointer for VOR1, the white pointer for VOR2)
<li>'''AP-Warning''' ''(no2D)'':
* Instrument failure
* abnormal pitch
* abnormal AoA (Angle of Attack, pitch)
<li>'''AT-Warning''' if:
* altitude acquired active without auto-throttle
* glide or auto-land active without auto-throttle
* airspeed indicator out of order
<li>'''ILS:''' ILS signal missing
<li>'''Landing Display:'''
* '''LAND 2 :''' Landing with category 2 capabilities:
** Flight controls in an electrical mode.
** One autopilot engaged in LAND mode.
** The flare light test successful.
** At least one landing display serviceable.
** At least one auto-throttle engaged in IAS ACQ mode
* '''LAND 3 :''' Landing with category 3 capabilities:
** All LAND 2 capabilities (see above), plus:
** At least one flight director engaged.
** Green/yellow hydraulic system pressure correct.
** Both AFCS VOR LOC selectors at the same course.
** Electrical generation split.
* '''DH on''' signals the aircraft being below the “decisions height” set in '''(23)'''
<li>'''Lamp-Test''' ''(no2D)''
<li>'''Attitude Indicator:''' Indicates the attitude of the aircraft compared to the real horizon. In addition:
* DH will light when below Decision Height set in '''(23)'''
* ATT will light if attitude is excessive or data might not be trustable
* if the autopilot''' FD''' is activated it will show a horizontal and a vertical bar indicating the airplane position relative to the ILS-Glide-Slope
* You can adjust the artificial plane by rotating the dial at the lower center.
<li>'''Gyro-Compass''' with integrated VOR, INS, and ILS indicators ''(see [[#The VOR/INS/ILS System|The VOR/INS/ILS System]])''
<li>'''Horizontal Slip Indicator'''
<li>'''Vertical-Speed-Indicator:''' The scale is in 1.000 FPM (Feet Per Minute). The yellow marker shows the actual FPM, the white one the preselected value. In the center of both, upper and lower half's, there are the “hot points” for preselecting when e.g. autopilot (VS) is active.
<li>'''R NAV''' ''(no2D)'': Indicates when the DME signal of the VOR/ILS is usable. The light on the pilot-side indicates for DEV1, the one on the co-pilots side DEV2.
<li>'''WX RDR:''' WxRadar (weather radar)
<li>'''Altitude to Ground:''' Indicates the altitude from ground up 2.500 ft. With the knob in the lower left you define the decision height (see '''(15 + 17)'''.
<li>A backup for '''(17)''' ''(no2D)''
<li>'''Altimeter:''' The digital Indicator shows the Height in 1000 ft, the analog pointer shows the values in between. With the knob in the lower left corner you adjust the static pressure. The yellow light at the upper left corner is on when the autopilot is acquiring an altitude '''(AA)'''.
<li>'''FD1 / FD2 switch''' ''(no2D)'' displays the ADF signal inside the Attitude Indicator '''(17)'''
<li>'''ADF 1/2-pointer''', directly pointing towards the ADF's, set in “menu → Concorde → Radio”. The yellow one is for ADF1, the white one for ADF2.
<li>'''Chronometer''' without special functions.
<li>'''Vertical Speed:''' When the Autopilot initiates a descent it will set the descent typically to the standard 750 FPM. After activating '''(VS)''' you can vary that climb/descent between +/- 6.000 FPM (see also '''(20)''')
<li>'''INS''' (Inertial Navigation System) ''(no2D)'': Warning if one of the INS-systems is not aligned or in failure. ''(see [[#The VOR/INS/ILS System|The VOR/INS/ILS System]])''
<li>'''M/CG''' (Mach/Center of Gravity) : Indicating the actual balance of the plane. ''(see [[#Balancing by Fuel-Pumping|Balancing by Fuel-Pumping]])''
<li>'''ILS-Marker:'''
* White + sound 3000 Hz: Aircraft over '''airway marker''' beacon
* Amber + sound 1300 Hz: Aircraft over a terminal '''middle marker''' beacon
* Blue + sound 400 Hz: Aircraft over a terminal '''outer marker''' beacon
* Test button (for bulbs)
<li>'''Status-Display:''' From Top to button
* CTY: if blinking indicates afterburner activated
* T/O: “Take-Off” engine rating
* CLB: “Climb” engine rating
* CRS: “Cruise” engine rating
<li>'''Brakes Control:''' show the applied forces
<li>'''BRAKES FAIL''' ''(no2D)'': no normal breaks available (green hydraulics missing)
<li>'''BRAKES EMERG''' ''(no2D)'': Parking or Emergency brake problems (no green hydraulic)
<li>'''T/O MONITOR:''' Activate before TakeOff to allow engines to operate beyond N2 (see '''(40)''')
<li>'''AFCS-MODE:''' Dims the “on”-lights inside the AFCS-control-buttons
<li>'''TOTAL CONTENT''' in kg
<li>'''Power management:'''
* '''GO''' (green): Indicates that the secondary nozzle buckets are positioned within limits, the CON light is off and the set bug values of P7 and FUEL FLOW have been achieved, and the ENG 4 T/O N1 LIMITER has returned to NORMAL position. It also allows you to exceed the N2-limits – armed by '''(37)'''.
* '''CON''' (Yellow):
** with no decrease in N2, indicates loss of reheat thrust.
** with reverse thrust selected indicates that the primary nozzle is greater than 15%
* '''REV''' (blue):
** FLASHING - indicates that the reverser-buckets are in transit (to toggle: “ctrl+B”)
** ON - indicates that the buckets are closed (reverser active)
** OFF - indicates that the buckets are within the forward thrust range
<li>'''N2 instruments:''' Percentage of the maximum RPM (revolutions per minute). 100% may be exceeded if Takeoff Monitor '''(37)''' is active (Compare '''(40)''' green).
<li>'''N1 instruments:''' Percentage of the maximum low pressure spool
<li>'''FF instruments:''' Fuel Flow in “kg/h * 1000”, in analog and digital.
With the knob at the lower right you can adjust the indicator bug in the scale and also the digital indicator to vary and indicate the required take-off value
<li>'''EGT instruments:''' Temperature in the jet pipe, in analog and digital
<li>'''Area instruments:''' Primary nozzle exhaust gas discharge area in %.
* when in the white area Reheat/Afterburner operate correct
* the extra yellow area at Eng.#4 indicates correct Reheat/Afterburner operation below 60 kt/h
* The yellow light on the top left indicates that the Reheat/Afterburner selector is not off
<li>'''WHEEL:''' Break overheat
<li>'''GEAR up/down''' switch (see also the control '''(52)''')
<li>'''Nose Wheel:''' Nose steering without hydraulic support
<li>'''NOSE operation:''' Clicking on the top marker of the lever lowers the Nose, and reverse. This is needed during Taxiing and Start-/Landing, because otherwise the Concord crew can hardly see the Taxi- and runways. In addition the Nose acts like flaps, by adding drag.
<li>'''Visor & Nose indicator''' (watch that the Hot-Spots for raising/lowering the nose are on the lever – not on the buttons!)
<li>'''Windshield wiper'''
<li>'''Gear controls''' (see switch '''(47)'''): The 4 gears are: Left, Nose, Right, and "Tail-protection without an unique door"
* Upper 3 yellow indicators: Doors in transit/unlocked
* Middle 4 red indicators: Gear in transit/unlocked
* Lower 4 green indicators: Gears locked in down position
* All off: Gears and Doors locked in upper position
<li>'''Trim-Indicator:''' For supersonic flights you should not use “Elevator-Trimming”, because that increases drag – instead you must balance the plane by pumping fuel back and force (see chapter balancing)
<li>'''AUTO-LAND warning:'''
* 100 ft above ground → ILS Glide-Slope not reliable
* excessive ILS deviation below 200 ft for Localizer
* excessive ILS deviation between 200 and 100 ft for Glideslope
* ILS failure below 200 ft for Localizer
* ILS failure between 200 and 75 ft for Glideslope
* missing auto-throttle below 600 ft.
<li>'''NAV1:''' This is usually set to the ILS-frequency for Landing. Set the radial for it at '''(59)'''. (see also [[#The VOR/INS/ILS System|The VOR/INS/ILS System]])
<li>'''RAD / INS: ''' Switches ONLY THE DISPLAYS between the common navigation (VOR) and the “Inertial Navigation System”. To navigate accordingly see [[#The VOR/INS/ILS System|The VOR/INS/ILS System]]
<li>'''Speed preset:''' The selector for the wanted speed (if control is given to the Autopilot). Be aware that with the selector you just define which speed you want to acquire next – the autopilot will execute that command only after you activated '''IA''' (see also [[#AFCS (Automated Flight Control System)|AFCS (Automated Flight Control System)]]) – thus you can predefine your needs well in advance.
<li>'''Radial TH:''' The radial setting for flying with autopilot TH (True (magnetic) Heading). This one moves the little yellow marker on the scale inside the Pilot-Gyro-Compass '''(18)''', when the instrument is not switched to INS or NAV2 (see '''(4)''' and '''(56)''').
<li>'''Radial NAV1:''' The radial setting for NAV1 '''(55)''', this will turn the ILS-Indicators inside the '''(18)''', if DEV1 is selected ('''(4)''' and '''(56)''').
<li>'''Radial TH:''' The radial setting for flying with autopilot TH (True (magnetic) Heading). This one moves the little yellow marker on the scale inside the Co-pilot-Gyro-Compass (not shown).
<li>'''Radial NAV2:''' The radial setting for NAV2 '''(64)''', this will turn the ILS-Indicators inside the Co-pilot-Gyro-Compass(not shown).
<li>'''Altitude preset:''' The selector for the wanted altitude if flying under autopilot control. To acquire this set altitude activate '''AA'''.
<li>'''RAD / INS''' switch for the Co-pilot (compare '''(56)''')
<li>'''NAV2:''' Is located on the Co-pilots side. It is usually used for the VOR-navigation.
</ol>

 

=== AFCS (Automated Flight Control System) ===
The AFCS is the panel between the main-panel and the front-windshield. It is what you usually call the “Autopilot”. In the following you will find only a short explanation – if you are interested in more details, see: http://www.concordesst.com/autopilot.html (but be aware that there may be some functions described, which are not (yet) implemented in the model).

 
==== AP & FD (Autopilot & Flight-Director) ====
* Both have two independent systems, but only both FD's are engaged to supervise each other.
* Activate '''AP''' as soon as you have established a steady climb after Take Off. That will also activate '''HH''' + '''PH''', thus enabling you to hold the runway-heading and climb-rate after start. Only one '''AP''' can be activated – be sure you activate the left one when the pilot is flying or the right one when the copilot is flying!
* If '''AP''' gets activated after '''FD''' it will not activate '''PH''' and/or '''HH'''
* If '''FD''' gets activated it will automatically activate '''PH''' (if not yet active) and the NAV indicators inside the Horizon '''(17)'''. You should always activate both '''FD'''-switches: One will be acting onto the pilots instruments, the other onto the copilot's instruments.

 
==== AP Speed-Control ====
* '''AT = Auto-Throttle:''' Needs to be activated if you want to fly a predefined speed. There are 2 independent Auto-Throttle systems which supervise each other and automatically take over in case of trouble. So you should always activate both at the same time.
* '''MH = Mach Hold:''' Will hold the actual Mach at the moment when '''MH''' is pushed. Because of the drastically changing relation of Mach to CAS, you should use it for cruise control, but not during significant changes in altitude.
* '''IH = Indicated Airspeed Hold:''' Will hold the actual CAS (calibrated Indicated Airspeed) at the moment when '''IH''' is pushed. Be aware, that a constant CAS will result in very different Ground-Speeds at different altitudes! Also: During supersonic flying your CAS will be above 500 kt/h - if you try to descent with that speed you might find yourself on the ground very fast - broken into pieces!
* '''IA = Indicated Airspeed Acquire:''' If '''IA''' is activated the Autopilot will try to acquire the Speed predefined in '''(57)'''. Whenever you change the value in '''(57)''' you have to reactivate '''AP''' before the plan will follow the new setting.
* For any time-distance Calculations use the '''TAS''' indicated at '''(10)'''.

 
==== AP Heading-Control ====
* '''IN = Inertial Navigation System Mode:''' Will hold a straight course to the target set in “Autopilot → Route Manager” or which are set in the Concord own INS-system (center pedestal).
* '''TH = True Heading:''' Will follow the Course set by the Control-Setting '''(58 or 60 remember: Only one AP may be actictive!))''', see the small widget inside the '''(18)''' compass-scale. Whenever you change that widget (and TH is active) the plane will follow immediately.
* '''HH = Heading Hold:''' Holds the actual magnetic Heading, independent of any presets. Thus you may continue with the present heading with HH, predefine the next wanted heading, and switch over to that new heading at any given time by just pressing TH!
* '''TU = Turbulence Mode:''' Will automatically smoothen down heavy attacks of turbulences by slowing down the automatic-reactions.
* '''BB = Back Beam:''' Sets the course to 180 degrees of the VOR/ILS-Beam.'' (is not yet functional)''
* '''VL = VOR1 Lock:''' Sets the heading according to the preselected radial in '''(59)'''. The pure selection will be indicated by an underlining light, the button itself will be lit when on the radial.
* '''GA = Go Around:''' Terminates any ILS-approach immediately and initiates a Go Around. This may be caused by a malfunctions (see above) or by pushing the throttle fully forward while on the glide-slope.

 
==== AP Altitude Control ====
''ATTANTION: If something is scontrolled by pitch, that can lead to stall or overspeed, if not watched by a human being!''
* '''PH = Pitch Hold:''' Will hold the Pitch as predefined in “Autopilot → Autopilot Setting” or indicated in '''(17)'''
* '''MP = Mach Hold per Pitch:''' Means the pitch will be adjusted to hold the speed in Mach – in opposite to the usual controlling of the CAS via '''IP'''. Remember: During climb/descent the relation between Mach and CAS may change drastically!
* '''CL = Max Climb rate hold''' by variable pitch
* '''IP = Indicated Airspeed hold''' by variable pitch
* '''LA = Auto-Land:''' You can activate '''LA''' any time. At best when you activate '''VL''' to intercept the Localizer and before you activate '''GL''' mode to follow the glide-slope:
** At some time LA will take over the VL, GL, and Speed - and will stay lit as only one.
** When at interception the '''AT''' (Auto-Throttle) is not engaged the '''AUTOLAND''' will start continuous flashing!
* '''GL = Glideslope:''' Will follow the ILS Glideslope defined by NAV1, if the NAV1-Lock is active (see '''VL''' under Heading options).
** ''WARNING: If you activate '''GL''' while the plane is far off the Glideslope, then the plane will very rapidly try to assume the right slope - even if that means a very steep climb or descent (or even crash!)!''
* '''CR = Max Cruise:''' Will reduce to Max Speed and then engages '''MH''' (Mach Hold))
* '''VS = Vertical Speed Hold:''' Holds the actual FPM when the button is pressed
* '''AH = Altitude hold:''' Holds the actual Altitude when the button is pressed
* '''AA = Altitude Acquired:''' Acquires the Altitude defined with '''(62)''', then activates '''AH'''. Whenever you change '''AA''' you have to reactivate it again (even if active already!) before the plan will follow the new setting.

 

=== The VOR/INS/ILS System ===
In the Concord there are 3 independent navigation-structures with the following components:
* '''2 NAV-Radios:''' Each having a “selected” and a “standby” frequency as usual, in basic FlightGear they are called NAV1 and NAV2, in the Concorde they are defined as DEV 1 and DEV2:
** Per default NAV1 is switched to be used by the pilot, NAV2 to the copilot
** '''Only NAV1 can be used for VOR/ILS tracking''' (as long as the center pedestal is not designed to switch the NAV's).
** The easiest way to set these radios is via “menu-bar → Concord → Radio” (which is the same as the standard FGFS “menu-bar → Equipment → Radio Setting”, but has 2 ADF settings, instead of only 1 in the standard FGFS)
*** You can switch the (selected) frequencies also by '''(55)''' for NAV-1 and '''(64)''' for NAV-2
*** and set the wanted radial via '''(59)''' for NAV-1 and '''(61)''' for NAV-2
* '''1 INS''' (Inertial Navigation System). You can set the so called “waypoints”
** via the standard FGFS “menu-bar → Autopilot → Route Manager”
** or via the 2 Concord unique input panels on the center pedestal (not yet described here)
* '''2 VOR Pointers (11)''', one for the pilot and one for the copilot, both pointing to both tuned in VOR-transmitter-stations (if they are in range!). On both pointer-instruments the yellow pointer points to VOR-1, the one with the white arrow to VOR-2.
* '''4 Displays:''' 2 inside the Gyros '''(18)''' and 2 more in the Attitude Indicator '''(17)''' when FD is active. 2 of those are on the pilot side, the other 2 on the copilot side. To enable both pilots to select any of the two NAV's in their Gyro, there are several switches:
** '''To DISPLAY:''' With switch '''(56)''' you define which type navigation will be displayed inside the Gyros '''(18)''' and/or '''(17)'''. Then you define with
*** switch '''(4)''' which NAV (1/2) is displayed
*** switch '''(5)''' which of the 2 INS (on the pedestal) are displayed
** '''To ACTIVATE:''' To actually activate the predefined navigation you have to activate either '''VL''' for navigation by VOR, or '''IN''' for navigation by way-points.
::Notice that you very well can display (and adjust) the VOR-navigation while actually you might be flying under INS-control.
:Be aware that you seldom see an “Off-course-Tracker” when flying by INS, because it always takes the shortest way to the next way-point, independent of any radial. You might use '''TH''' to bring the plane on to another radial, and then switch back to '''IN''' to hold that radial. ''(e.g. in case you are too far out from the airport for VOR-navigation, but want to approach that airport already on a different radial. Of course you could use that procedure also to approach an airport on the Runway-Radial you want, if the airport does not have any VOR/ILS (not very likely for a Supersonic flight with the Concord!!)!).''
 The ILS/VOR interception and then staying on the Localizer and Glideslope works very well, if you keep in mind:
* If you are just doing some “pleasure-flying” or short trips, then your plane might not have the correct “maximum landing weight”! But the Autopilot might reduce speed to the official “Touch Down Speed” of 162 kt/h – and depending on your overload that very likely results in a stall/crash! So just make it a habit to take manual control of the speed at about 1000 ft above the touchdown point, i.e. ensure that '''MH, IH, IA''' and both '''AT''' are off and remain off.

 

=== Balancing by Fuel-Pumping ===
In the present level of FGFS and/or Concord there exists a problem that prevents the display of the actual tank-fillings, as well on the 2D-panel as also on the Eng.-panel. (See also a note in the “Concorde-fuel.nas”). To show these figures you can edit all occurrences of “level-lbs” to “level-lb” in files: “/Concorde/Nasal/Concorde-fuelXML.nas”, “/Concorde/Panels/Concorde-2D-captain.xml”, “/Concorde/Panels/Concorde-engineer-fuel.xml”, and “Concorde/Panels/Concorde-engineering-fuel-top.xml”.

'''''The Concorde Tank-Schematic:''''' 
[[File:Concorde-Fueltanks.jpg|400px]]
 
* ''1 + 2 + 3 + 4 are the Collector-Tanks, feeding the engines directly. Usually they feed there counterpart engines – but they can be cross-switched to feed more and/or other engines at the same time.''
* ''5 + 7 and 8 + 6 are the Main-Transfer Tanks, feeding the 4 Collector-Tanks. Initially 5 + 7 are active. If those are empty 6 + 8 take over (or must be activated from the Engineering Panel!).''
* ''5a + 7a are Auxiliary-Tanks (to 5 and 7).''
* ''9 + 10 are the Trim-Tanks for balancing forward''
* ''11 is the Trim-Tank for balancing afterward''
 
'''The "Full-Balancing" can be categorized into the following groups''' [[#The 2D-Panels|(compare the scheme on the 2D-panel)]]:
:"'''Aft'''" transfers fuel from the forward trim tanks (9, 10) to the afterward trim tank (11).
:* Of course only until 11 is filled - and that may occur very soon if you start with full tanks! So switch to “Engi” directly after “Aft”, that will continue pumping from 9 (and/or 10) into 5 and 7, after 11 is filled.
:* During the climb tank 9 usually gets empty before the balancing-needs end. Then you have to activate tank 10 to continue pumping into 5 and 7 (or 11, if that is not filled). To activate this, open the Engineering-Panel (Ctrl+E). See in the upper part of the Fuel Management: 
{|
|-
|[[File:Forward-Fuel-mgt.jpg|400px|thumb|left]] ||
* the switches for Tank 9 (1a and 1b) should be already in the upper position (due to the initiated “Aft”)
* switch 2a and 2b into the upper position (mouse-click) to enable fuel-flow also from Tank 10
 
Be aware of different balancing-speeds, especially during the initial climb:
* at the beginning the balancing effect is 100%, because the weight of the fuel is moved from far before the Center of Gravity (tank 9) to far behind it (tank 11).
* After 11 is filled, there is only a weight-reduction in the front – because that weight now ends up in the Center of Gravity (tanks 5+7).
* After 9 is empty the balancing effect is even more reduced, because the weight reduction happens closer to the Center of Gravity (from tank 10).
|
|}
:"'''Forw'''" does the reverse, i.e. transferring from 11 to 9 – and has similar limits if the target tanks are filled. But “Forw” is usually used only during the final descent with relatively empty tanks, so there is room enough to pump into all tanks.
:"'''Engi'''" transfers trim tanks to the main tanks (5, 7). Before engaging “Engi” choose the direction "Aft" or "Forw"
:“'''Aux'''” feeds the main tanks (5, 7) from their auxiliary tanks (5A, 7A)
:"'''Jettis'''" (2 buttons for confirmation) dumps the trim (9, 10, 11) and collector tanks (1, 2, 3, 4)
:"'''Cross'''" balances the symmetrical tanks
 

== '''Advanced Topics''' ==
=== '''Pre-flight fuel planning''' ===

Since the Concorde is trimmed by pumping fuel, one cannot simply fill a few tanks from the standard Flightgear menu and fly away. The Concorde menu (Ctrl+I) offers under 'Fuel' a few options, some of which are useful for flights of the full range ('max takeoff') or short subsonic test flights ('max landing'). However, if one flies an intermediate distance with the max. takeoff fuel load (as in the above tutorial), the Concorde could be above its maximal landing weight on arrival. Thus, it will probably be necessary to adjust the fuel load manually for such flights via the Flightgear menu.

The first problem in doing so is that the tank numbers in the Flightgear menu are not the same as in the Concorde internal scheme. The following table provides an accurate mapping In the following, tanks are always referenced by the Concorde scheme.

{| border="1" style="text-align:center"
|+ Tank designations and trim
! Flightgear menu !! Concorde scheme !! trim
|-
| 0
| 1 || F
|-
| 1
| 2 || A
|-
| 2
| 3 || A
|-
| 3
| 4 || F
|-
| 4
| 5 || F
|-
| 5
| 6 || A
|-
| 6
| 7 || A
|-
| 7
| 8 || F
|-
| 8
| 9 || F
|-
| 9
| 10 || F
|-
| 10
| 11 || A
|-
| 11
| 5A || A
|-
| 12
| 7A || A
|}

The table also shows the trim effect of the tank as 'F' (forward) or 'A' (aft), e.g. if tank 11 is filled, it shifts weight to the rear (which should be also clear from tank location schematics above). For ease of handling, first fill the four collector tanks (1-4) equally. Their trim effect roughly cancels apart from a small weight shift aft. If you need more fuel, fill the transfer tanks (5-8) equally. Again, their trim effect tends to cancel, leaving only a small weight shift aft. For still more fuel load, fill the auxiliary tanks next (5A and 7A), again this results in a weight shift aft.

Whatever the fuel load of the tanks so far, it is always possible to trim the Concorde properly by using the trim tanks, which when completely filled give a strong weight shift forward (this is the reason tank 11 is not completely filled when 'max. takeoff weight' is chosen). So, after selecting the desired fuel load of collector, transfer and auxiliary tanks, trim properly for takeoff using the trim tanks (9-11).

When taking off without full fuel load, it is actually best to have the smallest amount of fuel needed to center M/CG in the trim tanks. This makes fuel management in flight much easier - basically one can treat the fuel system as two separate systems - the fuel in the trim tanks is only used to balance the aircraft by pumping it back and forth, whereas the rest of the tanks feed the engines. As a result, trimming is achieved very quickly.

=== '''Engine Startup''' ===

Since the Concorde model is initialized with all four engines running, knowing the engine startup procedures is not absolutely necessary. Note that there is also a simplified engine startup/shutdown available on the 2-d panel. The full engine startup procedure utilizes the engineering panel (Ctrl+E) quite heavily, and only the final engine start is controlled by the pilot by the four HP valves (overhead).

[[File:Concorde_HP-valves.jpg|400px]]

==== Important panels ====

In order to start, an engine needs fuel, airstream and electrical power. The relevant areas of the engineering panel (Ctrl+E) are:

'''The engine feed pumps''' 
[[File:Concorde_engine-feed-pumps.jpg|800px]]

The pump controls are located at the low end of the fuel management panel. Each pump has a set of three switches (1a - 1d), if they are put to 'off', the engine will no longer receive fuel. Usually the switches should be 'on' before trying to start an engine (also check fuel level in the tanks above - the engines will not start if the plane has no fuel). In case an engine should be completely deactivated (because of damage or overheat) it is probably a good idea to shut down its fuel supply.

'''Air bleed control''' 
[[File:Concorde_airbleed-control.jpg|500px]]

The airbleed control panel has a series of switches (1a - 1d) for the primary airstream which should be 'open'. The pressure gauges (2a - 2d) show if there is air pressure available in the engine. If the gauge reads zero, the engine cannot be started. The cross bleed valves (3a and 3b) can be opened to start an engine utilizing the pressure of an adjacent engine, or using ground supply. In flight, they should normally be closed.

'''Electrical generating''' 
[[File:Concorde_electrical generating.jpg|500px]]

Electrical power is usually generated from the engines, the relevant panel is located on the right hand side of engineering. The power gauges (1a - 1d) show the power generation. The ground power indicator (2) lights up if the Concorde is plugged into an external power source - the switch below must be in 'close' position to utilize external power and in 'trip' before taxiing. The four generator switches (3a - 3d) activate power generation from a running engine. They should probably be 'off' before starting an engine and only 'on' as soon as the engine is running.

'''Engine starting''' 
[[File:Concorde_engine_starters.jpg|400px]]

The four engine starter switches (1) are hidden on the lower left side of the engineering panel. They should be switched to 'start' to start an engine on the ground and to 'relight' to restart an engine in the air (that requires the 3rd mouse button). Below is the busbar switch (2) and the RAM air turbine (3) which are needed for emergency engine restart in the air.

==== Cold engine startup on the ground ====

Since the plane is initialized with running engines, in order to get into the situation of a cold start you have to switch them off. From the pilot's seat, close all four HP valves (overhead). A bunch of warnings informs you that the engines, electricity and other systems are down - deactivate the warning lights.

* '''External power:''' Bring up the concorde menu (Ctrl+I), check that under 'Ground' 'Air bleed' and 'Electrical power' are activated. Next bring up the Steward view (Ctrl+W) and switch 'Ground supply' to 'on'.

* '''Generators:''' Go to engineering (Ctrl+E), switch the four generator switches to 'off', switch ground power to 'close' - all panel gauges should come to life, indicating that there is power available.

* '''Air bleed:''' On the Air bleed control panel, open one of the cross bleed valves. The corresponding pressure gauge should show some pressure (generated by the ground crew).

* '''Engine starter:''' On the engine starting panel, put the switch for the selected engine to 'start'.

* '''HP valve:''' Back in the cockpit, open the HP valve for the selected engine. The engine should now start.

* '''Power generator:''' Back in engineering, start the power generator assoicated with the running engine. The power gauge should now show that power is generated. You can switch the ground power to 'trip'. You can also close the cross bleed valve of the running engine. Do not switch 'Ground supply' in the steward view off yet - air bleed from the ground is still needed.

* '''Opposite engine:''' Now repeat the procedure from '''air bleed''' on for the opposite engine, i.e. after starting engine 1 start 4, or after starting 2 start 3. With two engines ready, the Concorde is now prepared for taxiing - disconnect ground power from steward view (Ctrl+W) and taxi to the runway.

==== Remaining engine startup on the ground ====

Following usual procedure, you should reach the runway with two engines running. Then the Concorde is independent of any ground supply. In order to start the two remaining engines before takeoff, do the following:

* '''Air bleed:''' On the airbleed control, open ''two'' adjacent cross-bleed valves. The pressure gauge next to the running engine will now also show pressure.

* '''Engine starter:''' Put the switch for the selected engine to 'start'.

* '''HP valve:''' Back in the cockpit, start the engine by opening the HP valve.

* '''Cleanup:''' Switch on the electrical generator for the engine and close the cross bleed valves.

* '''Repeat''' Now repeat the procedure with the last engine.

==== Engine restart after flameout in the air ====

Should an engine go out during flight, restart is actually quite simple, as the ambient airstream through the engine is usually enough to start it, and power is produced by the remaining engines. Make sure that the HP valve is closed before re-starting the engine. To re-activate an engine in-flight, do the following:

* '''Power generator:''' Switch the power generator 'off'

* '''Engine starter:''' Switch the engine starter to 'relight'

* '''HP valve:''' Back in the cockpit, open the corresponding HP valve. The engine should come alive.

* '''Power generator:''' Switch the power generator back to 'on'

==== Emergency engine restart after full flameout ====

If all four engines fail during flight, the situation is a bit more complicated, since no electrical power is available. Nevertheless, the following procedure works:

* '''Copilot:''' Since the autopilot is off without electrical power, someone needs to fly the plane while you are busy in engineering. Call up the Concorde menu (Ctrl+I) and activate the virtual Copilot, he takes care of the cockpit.

* '''HP valves and power:''' Close all HP valves, switch the power generators off.

* '''RAM air turbine''' Switch both switches of the RAM air turbine on. This is a power generator which utilizes the airstream around the plane. Some electricity should come back.

* '''Busbar switch''' With the busbar switch above, select an engine to start.

* '''HP valve:''' Back in the cockpit, open the corresponding HP valve. The engine should come alive.

* '''Power generator:''' Switch the power generator back to 'on', switch the busbar to 'off'

* '''Remaining engines''' Now that power is back on, start the remaining engines with 'relight' as described above

When this is done, switch autopilot back on, kindly thank your copilot and ask the stewardess for a cup of coffee - you earned that...

=== '''Fuel Management''' ===

The simplified trimming procedure using the 2-d panel options is described [[#Balancing by Fuel-Pumping|above]]. The realistic handling of trimming and fuel flow is done from engineering (Ctrl+E) using the Fuel Management panel. The main elements of this panel are the various valves connecting the different tanks, the switches for pumps pressurizing the tanks and the gauges for fuel content, fuel consumption and M/CG. The basic operating principle is simple - open a valve and fuel may flow between tanks, activating a pump will make fuel flow if the valve is open and more active pumps cause faster fuel flow. The trick is of course knowing which valves and pumps to activate in what situation. The system has a lot of redundancy, so that the flight engineer can compensate for failing pumps or valves. For example, tanks have at least two fuel pumps.

==== '''Description of the Fuel Management Panel''' ====
'''The upper part of the Fuel Management Panel'''
[[File:Concorde_upper-fuel-management.jpg|600px]]

<ol>
<li>'''Inlet valve switches''' - these control the connection between tanks 9 and 11 and need to be opened for balancing into forward or aft direction. Nearby are override switches.
<li>'''Fuel gauge''' of tank 9.
<li>'''Pump switches''' for tank 9.
<li>'''Standby inlet valves''' which allow to pump fuel from tank 9 to almost any other tank. From left to right, the valve switches open connections to tanks 5,6,1,2,3,4,10,7 and 8. Tank 11 can be filled via the switches 1a and 1b, and only the auxiliary tanks 5A and 7A cannot be connected directly from tank 9.
<li>'''Pump switches''' for tank 5A.
<li>'''Pump switches''' for tank 7A.
<li>'''Pump switches''' for tank 10.
<li>'''Fuel gauge''' of tank 5A.
<li>'''Fuel gauge''' of tank 10.
<li>'''Fuel gauge''' of tank 7A.
<li>'''Jettison''' buttons.
</ol>

'''The lower part of the Fuel Management Panel'''
[[File:Concorde_lower-fuel-management.jpg|800px]]

<ol start="12">
<li>'''Trasfer valve switch''' for the connection between tanks 5 and 5A.
<li>'''Trasfer valve switch''' for the connection between tanks 7 and 7A.
<li>'''M/CG gauge''' (same instrument as in the cockpit).
<li>'''Trim transfer auto master switch'''
<li>'''Pump switches''' for tank 5.
<li>'''Fuel gauge''' of tank 5.
<li>'''Inlet valve switch'''
<li>???
<li>'''Inlet valve switch'''
<li>'''Pump switches''' for tank 7.
<li>'''Fuel gauge''' of tank 7.
<li>'''Total fuel gauges'''
<li>'''Pump switches''' for tank 6.
<li>'''Fuel gauge''' of tank 6.
<li>'''Interconnecting valve switch''' between tank 6 and 7.
<li>'''Interconnecting valve switch''' between tank 5 and 8.
<li>'''Pump switches''' for tank 8.
<li>'''Fuel gauge''' of tank 8.
<li>'''Fuel gauge''' of tank 1.
<li>'''Fuel gauge''' of tank 2.
<li>'''Fuel gauge''' of tank 3.
<li>'''Fuel gauge''' of tank 4.
<li>'''Pump switch''' for system green and override.
<li>'''Pump switch''' for system blue and override.
<li>'''Engine feed pumps''' for engine 1.
<li>'''Engine feed pumps''' for engine 2.
<li>'''Engine feed pumps''' for engine 3.
<li>'''Engine feed pumps''' for engine 4.
<li>'''Fuel gauge''' of tank 11.
<li>'''Crossfeed valve switches''' between engines 1 and 2.
<li>'''Crossfeed valve switches''' between engines 3 and 4.
<li>'''Pump switches''' for tank 11.
<li>'''Pump switches''' for tank 11.
<li>'''Fuel consumption gauges''' for engines 1-4.
</ol>

==== '''Trimming procedures''' ====

In order to trim the Concorde properly, typically three different procedures are needed: 1) Fuel transfer from tanks 9 and 10 into tank 11 (this corresponds to the '''Aft''' option in the simplified fuel management of the 2-d panel) 2) fuel transfer from tanks 9 and 10 to the engines if tank 11 is already filled to continue trimming (this is only needed if the fuel load is close to maximum takeoff weight) and 3) fuel transfer from tank 11 into tanks 9 and 10 (this corresponds to the '''Forw''' option in the simplified scheme.

In order to shift fuel from front to rear tanks, do the following:

<ul>
<li>'''Inlet valves''' Open the inlet valves (1a and 1b) to connect tank 9 and 11.
Edit: with the Concorde by V12, it seems you have to also open tank 11's inlet valves - look down to the very bottom.
<li>'''Fuel pumps''' Switch the fuel pumps of tank 9 (3a and 3b) on, and fuel flow should start.
<li>'''Further trim''' If more trim is needed, also open the standby inlet valve (4b, 3rd switch) connecting tank 9 and 10, activate the fuel pumps of tank 10 (7a and 7b). This transfers fuel from tank 10 into tank 9, where it is pumped on to tank 11 as long as the pumps of tank 9 are running and the inlet valves are open.
<li>'''End trimming''' Close the inlet valves, the standby inlet valve and switch off the pumps.
</ul>

In order to transfer fuel from the forward trim tanks to the engines, follow this procedure:

<ul>
<li>'''Standby inlet valves''' Open the standby inlet valves (4a and 4b) connecting tank 9 with tanks 1,2,3 and 4.
<li>'''Fuel pumps''' Switch the fuel pumps of tank 9 (3a and 3b) on, and fuel flow should start.
<li>'''Further trim''' If more trim is needed, also open the standby inlet valve (4b, 3rd switch) connecting tank 9 and 10, activate the fuel pumps of tank 10 (7a and 7b). This transfers fuel from tank 10 into tank 9, where it is pumped on to tanks 1,2,3 and 4 as long as the pumps of tank 9 are running and the valves are open.
<li>'''End trimming''' Close the standby inlet valves and switch off the pumps.
</ul>

On descent when forward trim is again needed, the following is required:

<ul>
<li>'''Inlet valves''' Open the inlet valves (1a and 1b) to connect tank 9 and 11.
<li>'''Fuel pumps''' Switch the fuel pumps of tank 11 (44a and 44b) on, and fuel flow should start.
<li>'''End trimming''' Close the inlet valves, the standby inlet valve and switch off the pumps.
</ul>

==== '''Managing normal fuel flow''' ====

Managing the normal flow of fuel to the engines is not particularly involved. The engines are connected to tanks 1-4 via the engine feeding pumps (36, 37, 38 and 39), so all fuel must eventually pass through these tanks. If there is a problem with one of these tanks or fuel pumps, the crossfeed switches (41a, 41b and 42a, 42b) can be activated to feed both engines 1+2 or 3+4 from a single tank. The fuel consumption gauges (45a, 45b) show the actual fuel flow to the engines.

Tanks 1-4 should normally be fed from tanks 5-8 (except when there is need to empty a trim tank). It seems to be sufficient to activate the fuel pumps (16, 21, 24 and 28) to empty the set of transfer tanks into the collector tanks. If needed, there are also interconnection valves between tanks 6 and 7 (26) and 5 and 8 (27). If they are used, this corresponds to the '''Cross''' balancing option in the simplified scheme.

Finally, the auxiliary tanks 5A and 7A can be connected to the transfer tanks 5 and 7 via the transfer valves (12 and 13) - if the fuel pumps on 5A and 7A (5 and 6) are switched on, the tanks empty into 5 and 7. This corresponds to the '''Aux''' option in the simplified scheme.

== Airplane of the Week/Month ==

The Concorde was reviewed as 'Airplane of the Week/Month' on May 12, 2011 as follows:

Model

The Concorde comes with an extremely detailed flight deck, with instrumentation for pilot, copilot and flight engineer. Almost all of the gauges and levers are functional, thus the Concorde supports many procedures including de-icing, engine restart in the air, fuel dump,... A lot of work in-flight is done from the engineer panel, for example the rather complex fuel management on a supersonic trip. In addition to the main panel shown, there are also overhead panels, side panels and a center console - on a first trip, it is easy to get lost in the cockpit...

[[File:Concorde-cockpit.jpg]]

Unfortunately, the texturing level of the cockpit is not really competitive and somewhat rough - but the Concorde is a great model in spite of that.

The exterior model is very elegant, as befits this beautiful plane.

[[File:Concorde-hawaii.jpg]]

Flight characteristics

The Concorde can teach quite a lot about supersonic flight and its problems. The plane consumes an amzing lot of fuel, this in turn influences the flight characteristics in a significant way, thus one can easily feel that the Concorde handles completely different at takeoff and landing. The max. landing weight is called that for a reason - try approaching too heavy and see what happens! The Concorde has rather nasty stall characteristics.

Supersonic cruise requires quite a different trim from subsonic cruise - in the Concorde, this is done via fuel transfer into trim tanks from the engineer's panel (all that is modelled in detail up to individual valves and override valves) - if the trim isn't done correctly, the Concorde doesn't reach its cruise altitude and velocity. Also, the different stages of the climb to supersonic cruise and the role of the afterburners is addressed.

The Concorde also happens to have a very well-tuned autopilot which can manage the flight from takeoff till 100 ft above the runway for landing - there are no weird oscillations in the AP, and intercepting the ILS glideslope works like a charm (the Concorde is currently the only plane I'm aware off with which that can be done without problems). Thus, very suited to IFR flights, as one doesn't have to monitor if the AP does weird things all the time. The AP is increasingly required at higher altitudes - try climbing to cruise altitude of 50.000 ft under manual control for a challenge. Otherwise the Concorde has the characteristics of an airliner - no quick maneuvers.

My personal wishlist

Apart from the cockpit texturing, I believe the Concorde is one of the best and most complex planes in the repository. The amount of detail in the modelling of the systems and the FDM is simply enormous. This plane deserves a much better cockpit, and it would be great if someone who understands texturing could devote some attention to the task.

It is somewhat complicated by the fact that the author of the plane remains anonymous, so one can't easily coordinate with him any cockpit design, but my changes to the cockpit were eventually incorporated, so it may be worth a shot.

Things to experience

Let all four engines flame out in mid-air. The plane then has to be flown in a descending trajectory, and since the AP is off (no power), the copilot has to do it. Since the Concorde comes with virtual crew members, no problem. Then a ram air turbine is used to generate some electricity, which can be used to relight one engine, which can then power the generator again to relight the rest of the engines. All in all, it's a fairly complicated procedure involving both pilot and flight engineer - and it's all modelled.

== '''Appendix''' ==
=== '''General Climb Performance''' ===
Just for those who wonder why the "Climb" is that complex: See here the theoretical calculations for the Concord, and merged into it the data resulting from my flight-tests. See also my data-recordings in the next chapter.
 
[[File:Concorde-Climb-Rate.jpg]]
 
:::red : The theoretical max/min speed-envelope
:::green: The “Maximum Operating Speed” limits
:::blue/white: the theoretical Mach values according to speed and altitude
:::gray + FPM values: The “Recorded Flight Data” of one of my trips, see the data in the following table
See especially the very much changing relationships between CAS, Mach, Gnd-Speed with altitude.

 
=== Concorde unique Keys ===
{| class="keytable"
!Key
!Function
|-
|{{key press|[}}/{{key press|]}}
|Raise/lower nose
|-
|{{key press|left}}/{{key press|right}}
|Autopilot heading
|-
|
|Floating view left/right
|-
|{{key press|up}}/{{key press|down}}
|Increase/decrease autopilot altitude
|-
|
|Floating view front/aft
|-
|{{key press|Home}}/{{key press|End}}
|Increase/decrease autopilot altitude (slow)
|-
|
|Floating view front/aft (fast)
|-
|{{key press|Page up}}/{{key press|Page down}}
|Increase/decrease autothrottle speed
|-
|
|Floating view up/down
|-
|{{key press|a}}/{{key press|A}}
|Speed-up
|-
|{{key press|Alt|b}}
|Emergency brakes
|-
|{{key press|f}}
|Full cockpit
|-
|{{key press|Alt|g}}
|Gear standby
|-
|{{key press|Alt|n}}
|Nose standby
|-
|{{key press|q}}
|Quit speed-up
|-
|{{key press|S}}
|Swaps 2D panel
|-
|{{key press|y}}
|Toggle yoke
|-
|{{key press|Ctrl|A}}
|Altitude acquire
|-
|{{key press|Ctrl|D}}
|Disconnect autopilot
|-
|{{key press|Ctrl|E}}
|Engineer view
|-
|{{key press|Ctrl|F}}
|Reheat (afterburner)
|-
|{{key press|Ctrl|G}}
|Glide slope
|-
|{{key press|Ctrl|H}}
|Heading hold
|-
|{{key press|Ctrl|I}}
|Menu
|-
|{{key press|Ctrl|J}}
|Copilot view
|-
|{{key press|Ctrl|K}}
|Observer (floating) view
|-
|{{key press|Ctrl|N}}
|Nav 1 hold
|-
|{{key press|Ctrl|O}}
|Overhead view
|-
|{{key press|Ctrl|P}}
|Pitch hold
|-
|{{key press|Ctrl|R}}
|Radio frequencies
|-
|{{key press|Shift|Ctrl|R}}
|Crew text
|-
|{{key press|Ctrl|S}}
|Speed acquire
|-
|{{key press|Ctrl|T}}
|Altitude hold
|-
|{{key press|Ctrl|W}}
|Steward (floating) view
|-
|{{key press|Shift|Ctrl|X}}
|Restore floating view
|-
|{{key press|Ctrl|Z}}
|Virtual crew
|}

{{Aérospatiale}}
{{Airbus}}
{{British Aerospace}}
{{British Aircraft Corporation}}

[[de:Concorde]]
[[Category:Red Griffin ATC compatible aircraft]]

Boeing 737NG

2022-05-27T07:15:38Z

Anonymous2: Added GitHub link

{{:{{PAGENAME}}/info}}
[[File:737-800 EDDL.png|thumb|737-800 at EDDL with Ryanair livery]]
The '''Boeing 737 Next Generation''' or '''Boeing 737NG''', is the name given to the −600/-700/-800/-900 series of the [[Boeing 737]] aircraft. Its direct competitor is the [[Airbus A320 Family]].

As of FlightGear 2.10.0, the various NG variants are combined into a single directory, with shared cockpits, instruments and engines. -ER variants do not exist at present, but are planned.

Latest release can be downloaded from https://github.com/YV3399/737-800YV

== Active Development Areas ==

* Porting the '3D' PFD from 777 - fortunately it's very similar to the 777
* Creating a stable AP, including autobrake, autospoiler and other automatic modes (auto-slates, flap load relief)
* Creating a working FMC and CDU

== Future Development / Help Wanted ==

* Overhauling the warning / caution systems
* Reworked instrument panel textures and meshes for knobs / buttons / switches

== External links ==
* [http://en.wikipedia.org/wiki/Boeing_737_Next_Generation Boeing 737 Next Generation] (Wikipedia)
* [http://www.b737.org.uk The Boeing 737 Technical Site]

{{Boeing}}
[[DE:Boeing 737NG]]
[[Category:Red Griffin ATC compatible aircraft]]

Tupolev Tu-154B

2022-05-27T06:59:49Z

Anonymous2: GitHub link updated with newer fork

{{Distinguish|Tupolev Tu-154 (YASim)}}
{{:{{PAGENAME}}/info}}
The '''Tupolev Tu-154B2-2''' is a Russian medium-range jet [[:Category:Airliners|airliner]].

[[FlightGear]]'s Tu-154 was converted from a model originally designed for Microsoft Flight Simulator by [http://www.protu-154.org/index_e.html Project Tupolev]. Systems and animations had to be re-rewritten especially for FlightGear though.

== Download ==
There are two ways to download the Tupolev Tu-154B-2: as a stable release and as a development revision from the SVN server. The latter is known to be a better option since releases are not created very often. However, keep in mind that due to an additional liveries pack in the development revisions, the SVN version of the Tu-154B-2 is not [[GPL]] compliant!

* To download the last release, pick the latest package from https://github.com/ShFsn/tu154b
* For to download files tu154b-master.zip open the page and click on the greeb [clone or download] button. Begins to download a 200 MB file. When finished, unzip the file and rename the directory from "tu154b-master" to "tu154b" and then put everything in the folder that contains the Flightgear aircraft.

It was featured in the [[FlightGear_Newsletter_July_2013#In_the_hangar|July 2013 Newsletter]], which announced its latest updates. For a small manual in English, you can go to this forum post: https://forum.flightgear.org/viewtopic.php?f=4&t=1193&start=30

== External links ==
* [http://www.flightgear.ru/wiki/index.php/Tu-154B Official website] of the project
* [http://forum.flightgear.org/viewtopic.php?f=4&t=4925 Forum topic V1.0]
* [http://forum.flightgear.org/viewtopic.php?f=4&t=20356 Forum topic V3.0]

{{Tupolev}}