FlightGear wiki - User contributions [en]

Poland

2025-10-20T23:26:54Z

SP-NTX:

'''Poland''' (Polish: '''Polska'''), officially the '''Republic of Poland''' (Polish: '''Rzeczpospolita Polska'''), is a country in Central Europe, bordered by Germany to the west; the Czech Republic and Slovakia to the south; Ukraine, Belarus and Lithuania to the east; and the Baltic Sea and Kaliningrad Oblast, a Russian exclave, to the north. The total area of Poland is 312,679 square kilometres (120,726 sq mi), making it the 9th largest in Europe. Poland has a population of over 38 million people.

== FlightGear community ==

[[FlightGear Polska|FlightGear Polska (FGPL)]] is the Polish FlightGear community, promoting FlightGear in Poland and organizing events and group flights. It also supports development projects, tutorials, and collaboration with the global FlightGear community.

== List of developed airports in Poland ==
{| class="wikitable sortable" border="0" cellpadding="4" cellspacing="0"
|-
! style="background:#efefef" | ICAO-Code !! style="background:#efefef" | Name of Airfield/Town !! style="background:#efefef" | Status (published) !! style="background:#efefef" | Status (development) !! class="unsortable" style="background:#efefef" | Comment
|-
| EPWA || [[Warsaw Chopin Airport]], Warsaw || custom layout, 3d models, airport service || stalled || Part of [https://github.com/marimigu/custom-scenery-polish/ Poland Custom Scenery]
|-
| EPSC || [[Goleniow Airport]], Goleniów/Sczecin || custom layout, 3d models, airport service || stalled || Part of [https://github.com/marimigu/custom-scenery-polish/ Poland Custom Scenery]
|-
| EPDE || [[Deblin Airport]], Dęblin || custom layout, 3d models || stalled || Part of [https://github.com/marimigu/custom-scenery-polish/ Poland Custom Scenery] Military/civil airport
|-
| EPZG || [[Zielona Góra Airport]], Zielona Góra || custom layout, 3d models || stalled || Part of [https://github.com/marimigu/custom-scenery-polish/ Poland Custom Scenery] Civil airport
|-
| EPLL || [[Łodź Airport]], Lublinek || custom layout, 3d models || stalled || Part of [https://github.com/marimigu/custom-scenery-polish/ Poland Custom Scenery] Civil airport
|-
| EPLB || [[Lublin Airport]], Lublin || v1000 layout, 3d models || stalled || Part of [https://github.com/marimigu/custom-scenery-polish/ Poland Custom Scenery] Civil airport
|-
| EPLR || [[Aeroclub of Lublin]] Radawiec || v850 layout, 3d models || stalled || Part of [https://github.com/marimigu/custom-scenery-polish/ Poland Custom Scenery] Grass
|-
| EPSW || [[Aeroclub of Swidnik]] Świdnik || v850 layout, 3d models || stalled || Part of [https://github.com/marimigu/custom-scenery-polish/ Poland Custom Scenery] Grass
|-
| EPWK || [[Wloclawek-Kruszyn]] || v1000 layout, 3d models || stalled || Part of [https://github.com/marimigu/custom-scenery-polish/ Poland Custom Scenery] Grass
|-
| EPPL || [[Plock-Kostrogaj]] || v1000 layout, 3d models, Rembrandt || stalled || Part of [https://github.com/marimigu/custom-scenery-polish/ Poland Custom Scenery] Grass
|-
| EP70 || [[Rzepin]] || v850 layout, 3d models || stalled || Part of [https://github.com/marimigu/custom-scenery-polish/ Poland Custom Scenery] Grass, forest landing
|-
| EPGD || [[Gdansk Airport ]] || v850 layout, 3d models || stalled || Part of [http://code.google.com/p/sceneria-epzg-babimost/downloads/detail?name=EPGDver.1.0.rar&can=2&q= Poland Custom Scenery] Civil airport
|-
| EPBC || [[Warszawa Babice ]] || v850 layout, 3d models || stalled || Part of [https://github.com/marimigu/custom-scenery-polish/ Poland Custom Scenery] Concrete, Warsaw Aeroclub airport
|-
| EPRZ || [[Rzeszów Jasionka ]] || layout ver.1000, OKL 3d models || in progress || Part of [https://github.com/marimigu/custom-scenery-polish/ Poland Custom Scenery] Civil airport, OKL Rzeszów, aeroclub
|-
| EP65 || [[Smolnik ]] || layout ver.1000, 3d models || in progress || Part of [https://github.com/marimigu/custom-scenery-polish/ Poland Custom Scenery] Grassy airstrip,
|-
| EPZA || [[Aeroklub Ziemi Zamojskiej]] || layout ver.1000, 3d models || stalled || Part of [https://github.com/marimigu/custom-scenery-polish/ Poland Custom Scenery] Grassy airstrip,
|-
| EPST || [[Aeroklub Stalowowolski]] || layout ver.1000, 3d models || stalled || Part of [https://github.com/marimigu/custom-scenery-polish/ Poland Custom Scenery] Grassy airstrip,
|-
| EPKA || [[Kielce Masłów]] || layout ver.1000, 3d models || stalled || Part of [https://github.com/marimigu/custom-scenery-polish/ Poland Custom Scenery] Civil airport, Aeroclub,
|-
|}

== Custom Scenery of Poland ==
[[File:Warsaw Skyline.png|thumb|Warsaw skycrapers.]]
[[File:Hel Peninsula.png|thumb|Hel Peninsula]]
[[File:Czorsztynskie Lake.png|thumb|Czorsztyńskie Lake]]
[[File:Warsaw area with OSMcity buildings.png|thumb|Area populated with OSM2CITY buildings, roads and pylons]]

=== Terrain ===
Custom Scenery of Poland includes whole Poland territory and border areas of surrounding countries. Terrain was generated using CORINE 2006 and OSM data for roads and railways.

=== Objects & airports ===
Currently we have objects on following airports:

International
* [[Warsaw Chopin Airport|EPWA Warsaw-Okęcie]]
* EPGD Gdańsk-Rębiechowo
* EPSC Szczecin-Goleniów
* [[Zielona Góra Airport|EPZG Zielona Góra-Babimost]]
* EPLL Łódź-Lublinek
* [[Lublin Airport|EPLB Lublin]]
* EPRZ Rzeszów Jasionka

Regional
* EPBC Warsaw-Babice
* [[Wloclawek-Kruszyn|EPWK Włocławek-Kruszyn]]
* [[Plock-Kostrogaj|EPPL Płock-Kostrogaj]]
* EP70 Rzepin
* [[Smolnik|EP65 Smolnik]]

Aeroclub
* [[Aeroklub Ziemi Zamojskiej|EPZA Zamość-Mokre]]
* [[Aeroclub of Lublin|EPLR Lublin-Radawiec]]
* [[Aeroklub Stalowowolski|EPST Stalowa-Wola-Turbia]]

Military
* EPDE Dęblin

Foreign
* EKRN Bornholm-Rønne
* LZTT Poprad-Tatry

See [http://wiki.flightgear.org/Category:Airports_in_Poland Category:Airports in Poland]

And some VFR landmarks including Warsaw skyline.

Most airports uses v.1000 layout. See full list here: [http://code.google.com/p/custom-scenery-polish/w/list]

=== Volunteer ===
Feel free to help us! This scenery still needs objects and v.1000 layouts. You can take some pictures of nearby airports or VFR landmarks and send them to us. We also appreciate new 3d models. If You'd like to contribute contact us by [https://www.facebook.com/pages/FlightGear-Polska/184032164996361 Facebook] or [https://plus.google.com/112579708746822167956/posts?hl=pl Google +].

=== Credits ===
* SP-DAM objects, layouts
* SP-MMA objects, layouts, terrain
* SP-MAKA objects
* SP-R22 objects
* Zbyszek objects, layouts

=== Download ===

=== OSM Scenery (Buildings, Roads, Pylons) ===

* Detailed scenery for Poland area can be fetched from [[Areas populated with osm2city scenery]]
* More information can be reached on the FlightGear forum: https://forum.flightgear.org/viewtopic.php?f=5&t=32172

[[Category:Poland]]

Discord

2025-10-20T23:22:53Z

SP-NTX:

'''Discord''' is used in the FlightGear community as an alternative to [[Mumble]], [[TeamSpeak]], [[FGCom]] or [[Ventrilo]].

Discord is a free voice and chat software that can be downloaded as an app or [https://discord.do/web/ used in a browser].

== Invite links ==
{{note|1=Its advised that you create a permanent account, instead of creating guest accounts as some people create duplicate accounts which clogs up the member logs and makes it more difficult to @mention people.}}

Furthermore many other FlightGear servers exist that you may need an personal invite to join. The easiest way to find them is to go to the FlightGear server and ask or ask in forums.

== FlightGear Communities on Discord ==

=== General, Help and Support, Communities ===

{| class=wikitable
! Topic !! Invite link
|-
| FlightGear
| https://discord.gg/rzuV2DR
|-
| FlightGear FDM School
| https://discord.gg/Uyrtsar
|-
| FlightGear Virtual Alliance
| https://discord.gg/VqzTG2N
|-
| FG Events
| https://discord.gg/GY4N6Cu
|-
| FG FDM School
| https://discord.gg/U5KXyMU
|-
| FlightGear Republic, A friendly community about FlightGear.
| https://discord.gg/sBJy46Uq7z
|-
|FlightGear soaring club
|https://discord.gg/NvJjmzMfRP
|}

=== Military Aviation Communities ===

{| class=wikitable
! Topic !! Invite link
|-
| Operation Red Flag military FG community (OPRF)
| https://discord.gg/ptVapkE
|-
| Combined Joint Task Force 50 (OPRF event planning/hosting and more)
| https://discord.gg/2nxjb6y
|-
|First Air Force (1 AF)
|[https://discord.com/invite/firstairforce https://discord.gg/firstairforce]
|}

=== Country Specific Communities ===

{| class=wikitable
! Topic !! Invite link
|-
|FlightGear Australia
| [https://discord.gg/8MY6cmDQbK https://discord.gg/nG76HMDjUE]
|-
| FlightGear Italia (ITA Mercenaries)
| https://discord.gg/5RzyXRf
|-
| FlightGear Germany
| https://discord.gg/FNnpjCPSze
|-
| FlightGear Indian Community
| https://discord.gg/Tu7n5FmG5S
|-
| FlightGear Asia
| https://discord.gg/7saCkA2jQj
|-
| FlightGear Hong Kong
| https://discord.gg/9QVKcT6skU
|-
|FlightGear Myanmar
|https://discord.gg/VbT88KEGrk
|-
|[[FlightGear Polska]]
|https://discord.gg/5J7uVYRhZV
|}

=== Aircraft-specific ===
{| class="wikitable"
! Aircraft !! Invite link
|-
| Aermacchi MB-339
| https://discord.gg/vNZ5ZPv
|-
| Airbus A350 Development
| https://discord.gg/vK5f2s6
|-
| Boeing F/A-18C Hornet
| https://discord.gg/8GzpdK4j8P
|-
| F-111 Aardvark
| https://discord.gg/DSrSbmx
|-
| [[General Dynamics F-16 Fighting Falcon]]
| https://discord.gg/8RcYnjA
|-
| Octal450 Hangar Development
| https://discord.gg/gxAhC3j
|-
| [[Mikoyan-Gurevich MiG-21bis]]
| https://discord.gg/bs8xyz3
|-
| [[Mirage 2000]]
| https://discord.gg/xZ3r2KR
|-
| Panavia Tornado
| https://discord.gg/SYxgzkCrSG
|-
| [[Saab 37 Viggen]]
| https://discord.gg/RJTwS9a
|-
| SEPECAT Jaguar
| https://discord.gg/G5q5XYN
|-
| FG-1000 Stealth Fighter
| https://discord.gg/3MFZauxyPW
|-
|Boeing 777
|https://discord.gg/k5RXxFgGDA
|-
|A-10 Warthog
|https://discord.gg/RmtjmsT5vS
|-
|Soviet Aviation for FGFS
|https://discord.gg/YC2EYGK5Xf
|-
|B-1 Lancer
|https://discord.gg/d2bhwFCnX2
|-
|[[PZL-Koliber-family | PZL Koliber family]]
|https://discord.gg/beADn2sWM6
|}

==External links==
*https://discord.com/ Official website

[[de:Discord]]

[[Category:Software]]
[[Category:Community]]
[[Category:Air Traffic Control]]

FlightGear Polska

2025-10-20T23:21:32Z

SP-NTX: Created page with "{{organization | name = FlightGear Polska | alt = Logo of FlightGear Polska | founded = 31st of August, 2020 | founders = SP-NTX, KizaK15, Sokoł | active = 50+ | website = [https://flightgear-polska.github.io/ FlightGear Polska Website] | forum = [https://discord.gg/PpwcM3YsZs FlightGear Polska Official Discord] }} = FlightGear Polska (FGPL) = '''FlightGear Polska (FGPL)''' is the Polish community for pilots and enthusiasts of the FlightGear flig..."

{{organization
| name = FlightGear Polska
| alt = Logo of FlightGear Polska
| founded = 31st of August, 2020
| founders = SP-NTX, KizaK15, Sokoł
| active = 50+
| website = [https://flightgear-polska.github.io/ FlightGear Polska Website]
| forum = [https://discord.gg/PpwcM3YsZs FlightGear Polska Official Discord]
}}

= FlightGear Polska (FGPL) =

'''FlightGear Polska (FGPL)''' is the Polish community for pilots and enthusiasts of the [[FlightGear]] flight simulator.

== History ==
FlightGear Polska was founded in 2020 by [[User:SP-NTX|SP-NTX]], KizaK, and Sokoł as a place for coordinating events, helping each other and as a home for Polish-speaking users.
The community's goal was to create a friendly, active, and informative environment for FlightGear enthusiasts in Poland, and to promote FlightGear locally and internationally

Over the years, the community experienced periods of high and low activity, and faced many challenges, both within the community, and with other communities.

== Goals ==
* Promote FlightGear in Poland.
* Organize group flights and virtual airshows.
* Support new pilots in learning the FlightGear.
* Develop add-ons and open-source projects for FlightGear.
* Collaborate with the global FlightGear community.
* Represent members of Polish community

== Activities ==
* Annual FlightGear Polska Anniversary Airshow
* Group flights and ATC services
* Development of Polish Scenery and aircrafts.
* Tutorials, guides, and support for new members.

== Projects ==
FlightGear Polska has got many side projects:
* vAF - Virtual (Polish) Air Force.
* 9vELT - Virtual squadron resembling 9 Eskadra Lotnictwa Taktycznego.
* PZL Koliber Development
* FlightGear Airshows Team

== Contact ==
* Email: flightgear.polska.fgpl@gmail.com
* Discord: @flightgearpl, https://discord.gg/PpwcM3YsZs
* Forum: @FlightGear Polska

== Notes ==
This page is actively maintained and updated by the FGPL administration.

File:Fgpl-logo.png

2025-10-20T23:09:56Z

SP-NTX: Uploaded own work with UploadWizard

=={{int:filedesc}}==
{{Information
|description={{en|1=FlightGear Polska Logo 2024+}}
|date=2024-08-30
|source={{own}}
|author=[[User:SP-NTX|SP-NTX]]
|permission=
|other versions=
}}

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

FlightGear Newsletter January 2025

2025-02-16T13:45:30Z

SP-NTX: Newsletter creation, automatic preload from here

{{User:Skybike/Template:Newsletter-header-translate|2025-01}}
{{TOC_right|limit=2}}
''We would like to emphasize that the monthly newsletter cannot live without the contributions of FlightGear users and developers. Everyone with a wiki account (free to register) is welcome to contribute to the newsletter. If you know about any FlightGear related news or projects such as for example updated scenery or aircraft, please do feel invited to add such news to the newsletter.''

''The new Visual Editor makes editing the wiki as simple as using a Word-processor, and even easier than using the forum as you don't even need to know the syntax for a url. Just hit the 'edit' link and start.''
{{WIP}}
== Development news ==
=== FlightGear repositories migration to GitLab ===
In January 2025, FlightGear developers transitioned most of the Git-based repositories from SourceForge to GitLab. While FGaddon remains on SourceForge for now, the rest of the repositories are now hosted on [[GitLab]], which offers a more modern and efficient development workflow.







== In the hangar ==









== Scenery corner ==
















== Help wanted ==
{{Help wanted}}

== AI ==


The AI team makes FlightGear more realistic, colorful and lively every month. You can support the development of ''Interactive Traffic'' and contribute at the FlightGear {{forum link|title=AI|f=23}}.



== Community news ==








=== FlightGear on Facebook ===
Since early December 2010, FlightGear has an [https://www.facebook.com/FlightGear official Facebook page]. If you have a Facebook account please feel free to join the page.

=== FlightGear on Instagram ===
In January 2018 the [https://www.instagram.com/flightgear_sim/ @flightgear_sim Instagram account] was brought back to life. If you've got nice screenshots to be featured, feel free to {{forum link|text=contact the maintainer|t=33636}}.

=== FlightGear on FlightSim.com ===
FlightGear has also a [https://www.flightsim.com/vbfs/forumdisplay.php?102-FlightGear sub-forum] on flightsim.com - just like the commercial flight sims. It is an opportunity to showcase what FG can do, get people curious and answer any questions they may have with regard to the software or the project.

== Multiplayer events ==









== Contributing ==
=== Translators needed ===
{|
| [[File:en.gif]]
| The FlightGear Wiki still needs help for translating it into various languages. If you are interested in making the FlightGear Wiki multilingual, you can start by looking at [[Help:Translate]].
|-
| [[File:fr.gif]]
| Le wiki de FlightGear a toujours besoin d'aide pour être traduit en différentes langues. Si vous êtes intéressé par le rendre multilingue, commencez par lire [[:fr:Help:Traduire|Help:Traduire]].
|-
| [[File:de.gif]]
| Das FlightGear Wiki benötigt immer noch Hilfe bei der Übersetzung in verschiedene Sprachen. Wenn Du Interesse daran hast, das FlightGear Wiki mehrsprachig zu machen, dann fang mit dem [[:de:Help:Übersetzen|Help:Übersetzen]] an.
|-
| [[File:nl.gif]]
| De FlightGear Wiki kan nog steed hulp gebruiken bij het vertalen van artikelen. Als je interesse hebt om de wiki meertalig te maken, raden we je aan om een kijkje te nemen bij [[:nl:Help:Vertalen|Help:Vertalen]].
|-
| [[File:es.gif]]
| La wiki de FlightGear todavía necesita ayuda para traducirla a varios lenguajes. Si estás interesado en hacer la FlightGear wiki multilingüe, entonces comienza en [[:es:Help:Traducir|Help:Traducir]].
|-
| [[File:cat.gif]]
| La wiki de FlightGear encara necessita ajuda per traduir-la a diverses llengües. Si esteu interessat en fer la wiki de FlightGear multilingüe, llavors comenceu a [[:ca:Help:Traduir|Help:Traduir]].
|-
| [[File:pt.gif]]
| A wiki de FlightGear ainda necessita de ajuda para traduzi-la em vários idiomas. Se estás interessado em tornar a wiki de FlightGear multi-lingual, por favor começa em [[:pt:Help:Traduzir|Help:Traduzir]].
|-
| [[File:zh.gif]]
| FlightGear 百科仍然需要志愿者将其翻译为各种语言。如果你有兴趣让FlightGear百科支持更多语言, 你可以查看 [[Help:Translate]].
|}

=== FlightGear logos ===
If you want some graphic elements for your FlightGear-related site (such as a hangar or YouTube channel), please feel free to visit [[FlightGear logos]] for a repository of logos. And if you have some art skills, please don't hesitate to contribute with your own design creations.

=== Screenshots ===
The FlightGear project always needs screenshots, which show features that were added since the last release. These should be of good quality, especially in content and technical image properties. It is therefore recommended to use the best viable filter settings ([[anti-aliasing]], texture sharpening, etc.). More info at [[Howto:Make nice screenshots]].

==== Screenshot of the Month ====

If you want to participate in the screenshot contest, you can submit your candidate to the {{forum link|title=this|f=88|t=}}. Be sure to see the first post for participation rules. For purposes of convenience and organization, at the end of the month or after 20 entries have been submitted, a new forum topic will be started containing all shots in an easy-to-view layout. The voting will then take place there.

''Thanks for reading {{PAGENAME}}!''

{{Appendix}}


[[Category:Changes after 2020.3]]
[[Category:FlightGear Newsletter|2025 01]]

User:SP-NTX

2025-01-07T22:37:36Z

SP-NTX: Remove not important info about me

This is a wiki page about me. I will share with you here everything I want you to know. This is by no means an informative page or something, just mine place to put some interesting things for others to see.{{user
| name = SP-NTX
| location = Zielona Góra, Poland
| age =
| job =
| interests = * FlightGear
* Sailing
* Astrophotography
* Plane Spotting
| callsign = * SP-NTX
* VIPER04
* VPR04
* PL-NEXT
| favourite = * McDonnell Douglas MD-11
* McDonnell Douglas KC-10
* Boeing 737
* PZL Koliber family
* Space Shuttle
* F16
| website = * https://flightgear-polska.github.io/
* https://github.com/SP-NTX
}}
==About me==
I’m from Poland. My home airport is EPZG - Zielona Góra Babimost, and I’m an avid plane spotter. But my passions extend far beyond aviation...

=== Sports ===
Since 2024, I’ve been sailing and racing on '''Laser (ILCA)''' class sailboats. Sailing is the most relaxing and interesting activity I know. The peacefulness of sailing in the evening with the sunset in the background is one of the most beautiful things you can imagine, but things get truly exciting when the wind picks up to 20 knots or more. There’s no better thing in this world than the power of the wind at full speed!

=== Photography ===
Photography is my second hobby. I love taking a lot of photos, especially when it comes to plane spotting. I'm a fan of old SLR cameras, especially Minolta Dynax 9, and Minolta X700. Taking photos on these old film cameras is something incredible (and expensive). On the other hand, my main photography equipment is old good Sony A900 and Sony A700. Awesome cameras. I also love astrophotography. It is hard, but on the other hand, when you finally get that image of Andromeda Galaxy, or Orion Nebula... You just can't stop doing it...

=== Music ===
Music is a very important part of me. I play both '''piano''' and '''guitar''', often composing and recording my own pieces. My musical tastes are varied, but I’m especially drawn to nu-metal and alternative rock. I also listen to synth-pop and new wave from time to time. My favorite bands include:
*'''Sick Puppies'''
*'''Linkin Park'''
*'''Evans Blue'''
*'''Lady Pank'''

If I were to recommend a few songs, check out:

* ''Cancer'' by Sick Puppies
* ''Pushing Me Away'' by Linkin Park
* ''Erase My Scars'' by Evans Blue
* ''Mała Wojna'' by Lady Pank

=== Musical Inspirations ===
Music isn’t just about listening; I enjoy creating it as well. On the guitar and piano, I compose original songs and experiment with different styles. From soft piano melodies to heavy guitar riffs. I promise that when I will record something which is not actually bad I will put it here...

=== Languages ===
I’m fluent in '''Polish''' and '''English'''. I can also speak in '''German''', though it isn't that good...

=== Programming ===
I code in:

* C++
* Python
* Nasal
* Visual Basic

==Everything about SP-NTX ==
<blockquote>''Hated by a majority for having a different opinion than others,''

''Forgotten by the rest,''

''Admired by a few,''

''Loved by some.''</blockquote>you actually have to read all this to understand me or hate me even more.

=== Where it all began?....===
I joined the community in the late 2019, found FlightGear after looking for Open Source projects. I started flying very frequently, I got into aviation and I was really happy to be a part of an amazing community, which FlightGear was back in the days. As some of you know, my callsign was PL-NEXT back then. I changed my callsign to SP-NTX on the 28th of April 2020.

Frequent flying with others was something I really enjoyed, flying alone - not really. Flying wing-to-wing with others was my favourite thing to do, and I still miss these days... Thanks SP-JBX, SP-BAN, SP-JAN, paf1, SP-KOK, SP-VOT for all our flights together, it was amazing... Hope you will read this, someday...

===The creation of FlightGear Polska ===
In August 2020, more precisely, on the 31st of August 2020, 15:44, with two of my friends (SP-VOT and KIZAK15) I started FlightGear Polska (Polish FlightGear Community), which still remains my biggest project and contribution to the FlightGear project. First pilots to be part of our Polish FlightGear community were SP-NTX (me), SP-VOT (Sokół), Kizak15 (Kizak), and LO126O (SP-MAO1). Next, as our discord server was growing, more people were joining the discord server, we made our YouTube channel (note to myself: put link here), and started posting some videos. We were flying very frequently with one another, it was the best time of my entire FlightGear carrer... Next, I got into developing aircrafts... I couldn't stand looking at... Boeing 737-800 trim wheel... It was the first half of November 2020 when I started re-modelling the throttle quadrant of 737... I had no idea where to start, what to do, but I knew the basics. After improving the model of that trim wheel, I started working on textures... that was complete hell... and still is... Some of my friends (SP-VOT, 2938) helped me with the project, but it turned out to be a complete failure... Meanwhile, we started our first Virtual Airline, the Polish Virtual Airlines, which was pretty nice, not gonna lie, not as advanced as others, but it was made to make flying even more interesting. And then it came, the 9vELT (9 wirtualna Eskadra Lotnictwa Taktycznego, or in english - 9th virtual Tactical Air Squadron)... It was a nice project started by SP-PAF (paf1). We started getting more and more people into it, and we started doing military operations. Our base was EP73 (Zegrze Pomorskie), and we were flying on MiG-21s... the one from the launcher, because OPRF one was too hard to fly for me back then. We switched to F16s and changed our airbase to EPZG, it was 23rd of November 2020, and it was a lot of fun... Flying all day with my friends and talking on voice channel, I wish I could do it at least one more time... Then we decided that we need some callsigns as a squadron, sooo, this is where VIPER callsigns began... VIPER01 was SP-PAF, VIPER02 was.... I am not sure, it doesn't matter... I was VIPER04, and I am so proud of that callsign... on the 24th of November we did a little airshow, which is actually FlightGear Polska first airshow ever, and for sure not the last one...

=== What goes up has got to fall===
25th of November, btw you won't believe if I told you one thing about that day but ok... We started arguing in the evening with SP-PAF and others... by we I mean I... I wanted Mirage 2000 to be added to the squadron, they wanted to stay with F16s only, and it went like that for a few hours, and you won't believe how from a little Mirage 2000 thing it came to FlightGear Polska fall down... 26th of November 2020, 15:11... The fall down of FlightGear Polska... let me not get into the details, let's just say FGPL is gone now. Maybe for the first time, but for sure not for the last. I started a new discord server, and believe or not, we had zero activity or at least nothing which could compare to the old FGPL in almost 3 years... I put A LOT of work into FGPL. Hundreds of hours of working on it, Thousands of flights, everything I could to make it the best and the biggest community in FlightGear.

===A new chapter===
In the late 2020, I started developing 737-400. It was my first big project, and it turned out pretty shitty, as you know, but I was proud that I've done something. Maybe I just made 737-400 out of 737-300, but with some nice new features, but I am proud that I have done something flyable. Around that time, I meet LOT87. He is a really ni... okay we will think about it later. He was a really nice guy, but remember this, as the story will turn around completely in... 3 years...

Early 2021, after loosing hope for bringing FGPL back to life - it doesn't matter - I never ever wanted FGPL back, I wanted my friends back, something you loose - you never get back (imagine this will happen one more time)... I started flying frequently again, very long flights, alone, and hated everyone and everything... Then I found one YouTube channel - Parrott 1221... He made a video about FG and he was from Poland. I got in contact with him, and we started flying together. He was, and is, a very nice guy. He started his own Virtual Airline, Parrott Airlines (note: double t at the end, it is very important and not a mistake xd). We were flying together very often, and I helped him with his Virtual Airline, also being a part of it. When he joined FlightGear Polska, for the first time since the fall down of FGPL, activity raised. The issue is - I always hated that new discord server, don't ask me why, I just hated it... And I still do... Early 2021 was a really hard time in my life irl, not gonna go into details, it was just really hard. Flying helped me - a bit, but it wasn't going well. Then Bysiek joined, he also made his own virtual airline - Performance Airlines. Later - I am not sure now... In 2021? Maybe in early 2022.... Janout joined the community. He also was and is and always will be a really nice person to me, I really enjoyed flying with him, but then he left the community for some time. Next, SP6FU joined, he was a very good developer, he started Evolving Airlines in the mid 2022, which was, is, and still remains the most advanced Virtual Airline out there, with website, flight logging system, and other features no other airline had. The only issue is Evolving Airlines is no more... Look how crazy it was, we had 5 Virtual Airlines in the same time, awesome, right? Around that time, I also joined The Random Developers, we started developing Boeing 747-400. It was a really nice project - and still is. I consider something as finished when it is actually finished, when there is nothing left to do. This might mean nothing will ever be finished... Also in the early 2021 I got banned from FlightGear discord server, maybe for the first time, for sure not for the last :D...

===We are VIPERs===
September 2022. We decided to bring some Virtual Air Forces back to life.... for example the one which never existed, but it actually did. When the drama with 9vELT started (look: FGPL fall down #1) I made my own squadron, PLvAF... So we decided to bring vAF back to life... First stage was Operacja Orzełek (Operation Eagle), which was a great success of VAF, the first big fight against FGRAF. Or at least it is because the enemy side didn't showed up?... The members of vAF back then were me, Parrott, SP6FU, SP-KOS, Noctol, and few more. Not gonna say who had which callsign (VIPER0x), but I had some other than the one I used in 9vELT. Then we made more and more missions, and it was, just, a lot of fun... for us, maybe not for others.

===One step forward - two step back===
February 2023. 2 years and 4 months since fall down of old FGPL. The FGPL shape was really, really bad. No flying, no activity on discord... guess what I've done. We switched to other discord server... other... the old one... and magically (with a big effort actually), the activity came back... and it came back a lot bigger than ever before. This might have been the best decision in terms of FGPL I have ever made.... of course other than actually starting the community. More and more new pilots joined, we started flying together, and new admins were SP-NTX, Parrott, Janout, LOT87, Marcin... Around that time - I am proud to say it - I became the first ever person to make a complete flight in FlightGear with HDR (with landing), and I was one of the few who had HDR working on their FlightGear builds (because back then we had issues with OSG, scenery, etc) But back to FGPL... we made a secret admin channel called #azbest on our discord server... don't ask me about why we called it like that (it was because one of the admins - Parrott, was collecting old gas masks which contained asbestos). This channel was like feel free to talk about anything and everything with no rules, I bet every single discord server have a channel like that. It actually was the most active channel on entire FGPL discord... 60% of the activity was that one channel... which actually is... 150 000 messages... if you are new to number of messages on discord channels etc this is A LOT. FlightGear Discord have 100k messages per year on avg iirc. Then it came - August 2023. We decided to make FlightGear Polska 3rd Anniversary event. It was a very big project, and the biggest event we have ever done (actually turned out to be the biggest airshow out there... ever....) I personally still can't believe we planned all this in a few days, and it turned out to be.... awesome. Good music, awesome pilots, excellent displays... Everything was perfect... but the activity wasn't at it's peak yet.

===The most active FlightGear community ===
In November 2023 we made the Independence Day Event, which is one of the best airshows we have ever made. This event made us even more confident that we are the best - the biggest community and so on. I was proud of it, my project - our project, became so big, so awesome... And the activity.... in November we had 22k messages on the server (which is awesome). The year was slowly ending, and at the end of 2023, we had over 100 000 messages in just 10 months (because we switched to a 'new' server in February). This, and the number of group flights, events, active members, made us the most active FlightGear community out there... for the first time... for the last time?...

===I am still a Developer ===
Around November 2023 I started working on DC-10 family cockpit rework. Sadly due to real life issues, no time and the fact that I always prefer quality over quantity - the development was going very slow. Around this time, I started flying less and less, focused on development and real life things. I also started working on new Boeing 737-400 model (which is the best 3D model I made likely, not public yet). I also continued working on PZL Koliber family, mainly focused on systems.

===We are FlightGear Polska===
On the 3rd of April 2024, member of our community got banned from FlightGear discord for racism. Actually, this was a thing which had absolutely nothing to do with his actions or whatever, he just had in his profile something which one admin and one other person decided that is a big issue, racism, and everything they could imagine... are you guys serious? We are in 2024. Instead of asking him to remove that thing from his profile, they just banned him and gave him no way to say sorry or whatever. The best part is that this thing actually wasn't against the rules of the server. We, with FlightGear Polska admins, stated an open letter to FlightGear Administration, which was created just to be an informative thing that rules do not cover such things and should be updates, and that we don't support racism or whatever. FlightGear discord administration considered this literally like some personal attack and FlightGear Polska administrators (and other members of our community?) got banned from FlightGear discord, when it almost came to the point where you could get banned just for being from Poland. This was how our community was treated by others. We didn't care, and all we cared about, is that we at least tried to defend member of our community - as he couldn't defend himself because of getting banned. I also got banned from FlightGear discord server...
==My projects==

*737-400 ([https://github.com/SP-NTX/737-400<nowiki>])</nowiki>
*Liveries ([https://github.com/SP-NTX/SP-NTX_Liveries<nowiki>])</nowiki>
*Aerolite 103
*PZL Koliber Family ([https://github.com/SP-NTX/PZL-Koliber-family<nowiki>])</nowiki>
*DC-10 Family cockpit development

==I'm actually working on==

*New 3D model for 737-400
*Translating & Updating fgwiki
*Creating High Quality Liveries & 3D models

and some another projects

==My favourite Aircrafts==

*MD-11
*Concorde
*Space Shuttle
*Boeing 737-800 and MAX 8
*Boeing 747(-400)
*Boeing 757
*Airbus A320
*Boeing 787

*Embraer E-Jets
*F16

==For the beginning developers :D==
Im writing that not as tutorial, just based on my small experience.
First of all, if you are in this moment, while you know, that you need to do something for FG, welcome, now you need to choose what to do, and you will be good at this.
Now, what you want to do? Liveries? Aircrafts? Scenery? or maybe Addons? I know, it's hard thing to choose. I suggest to start with Liveries if you never touched anything in the FG 'backend'.
Ok so download GIMP and find the aircraft folder, try to find the paintkit, and play with it. No, there is no any good tutorial for liveries on FGwiki, so try to find something on FGforum.
You should read few GIMP tutorials. Then export it to the liveries folder, copy another livery xml and edit it to make it work for your livery. And it should be easy.
Your first livery is not going to look amazing, it will probably be bad, but, do the next one, and next one, and then your liveries will look amazing.
If you think it's not for you, no problem, but other things will be harder. For aircrafts and scenery you will need to learn 3D modelling, and no one is going to write
tutorial for 3d modelling here, so open youtube and write '3D modelling tutorial for Blender' or other 3D modelling apps. then read some things about modelling on the FGwiki, but it will not make you get new skills...
Ok if you think the modelling is not for you, congratulations, it was good choice, then try programming. No, im not talking about the FG Core or addons, it's like trying to fly Space Shuttle, when you flew only Gliders ;).
Start with simple Nasal scripts, here i'm giving you what you should read first. YES I KNOW IT'S LOOKING SO BAD BUT TRY IT AND YOU WILL UNDERSTAND (F10 menu>Debug>Nasal Console).
Ok before i will add a lot of links here i want to say few things. Maybe, but only maybe, it's better to start with Canvas...

https://wiki.flightgear.org/Nasal_scripting_language - read this but it will not give you anything

https://wiki.flightgear.org/Nasal_Hello_World - it also will not give you anything

https://wiki.flightgear.org/Howto:Create_a_new_Nasal_module - ok, this may be useful, try to read the code after reading text

https://wiki.flightgear.org/Using_Nasal_functions - this is really, really important imo, look at the "Simple examples"

https://wiki.flightgear.org/Howto:Understand_Namespaces_and_Methods - and this is hard, even for me, but a lot of nice informations, should be easy to understand

https://wiki.flightgear.org/Nasal_Loops - its little harder, but very important

https://wiki.flightgear.org/Nasal_Operators - And remember those thing '~' for adding strings to each other, you will need this someday.

And, for now, that's all.
Later when i will have little more time i will create github repo with nice examples for those.

Ok now you can start programming simple things, try to make the simple kts2mph converter.
<syntaxhighlight line="1" start="1">
# Ok, lets start our code.
var loop func() { # Looks bad, but, look, its easy, its our main loop start
var ktsSpd = getprop("/"); # Im naming this variable ktsSpd, then im setting it to the property.
var mphSpd = (ktsSpd*1.15077945); # wait, where i get 1.15077945? 1 kts is 1.15077945 MPH
print(mphSpd); # i have nothing else to do with it than just printing it to console
} # Ok, this ends the loop
timer_loop = maketimer(0.25, loop); # i send link about Nasal_Loops, didn't I?
timer_loop.start(); # start the timer

</syntaxhighlight>
Ok so you tested my code? i wrote it in few minutes, and why i said in comment about the Nasal loops article? because i forgot how to do that, so i checked. No, you are not going to remember everything, you can always go back to those links.
What you can do next? Do something cool! It will make new things easier to remember, you don't have ideas? me too... But you can do even something stupid! Did you looked at the Nasal_Hello_Word atricle? I remember that there was code for popup message, maybe, when the property changes (here you can use setlistener , Nasal_Loops, gears/gear[]/wow) i mean, when you take off, make something like: You are taking off, and there will be message: Goog flight!? Yes this is stupid, but you will learn how to: Make loop, set setlistener(), finding property, making GUI popup, and why to not forget about ';' on end of the line. Isn't it nice? Code for that will be available on my github repo comeday, i will give link :-), but try to do this yourself. Do some other things, for example, automatic gear retraction and extending while alt > or < than some value. Code for that will be available too someday. Ok, so, you know basics of nasal, amazing, i hope you will like it. Ok so what now? Try Canvas, i started with it, thats why i said that before. Canvas is hard, its not easy thing, i will not give links this time, just read everything what you think it will be useful, also, check this https://forum.flightgear.org/viewtopic.php?f=71&t=38998 even if it's boring. After reading all that text, i just want to say you, thank you, you probably learned something new, from other point of view. I wasn't planning to make it as long, but, it's going to be extended later. Now i'm going to make tutorial about making addons, because i can't make tutorial for everything on this page. To be extended (someday)

==Modelling instruments in Blender (any version above 2.80)==
Everything I say here is based on my own experience, work and each and every time I told myself that modelling is complete sh*t

===Getting references===
First and at the same time most important thing out there. Is it hard? It depends, but usually you will have to do at least 'quick' search...

Where do you start? Look at aircraft POH, FCOM or service manual. Usually you will find some drawings in them, but remember that they are usually not very detailed. Next, try to find some images of the instrument you want to model, it might not be that easy if you model some unusual instrument like TCI for DC-10 or Boeing 747-200s vertictal tape engine instruments... There is another reference that some people forget, while it is actually very important. Look at the videos, cockpit tours, or any other thing like that. It might give better quality references than images. Cockpit posters are usually low quality and even more off than drawings, avoid using these if you don't really need them!

===Setting up references===
This may be a complex thing but don't worry, you will find it easier with each instrument you model.

First of all open your Blender and set up a new project. This sound complex but all you have to do is removing everything from the scene, so the select the default cube, camera and light and click delete.

I assume that you know a bit about navgation in Blender... if not, please watch tutorial about it before modelling your first instrument ok?...

What type of reference you should start with? Well, you would like to start with some drawing, it will be easiest to start modelling the instrument. I also assume you know how to add images to the viewport... (if not: shift+a image>reference, or easier drag and drop to the viewport).

You want the reference to be aligned with... x or axis... How to do it easily? 2 ways. If you go drag and drop method of adding references, align the camera with the X axis... no not manually, using that thing on top right part of the viewport clicking on X, and then just drag and drop the image. If you go shift+a way, then you have to rotate the image, for this use key r and then axis (x, y, z) and then value (deg), like r x 90. If you are new to blender you will find this pretty... strange... Actually this is saving so much time I use it more often than rotating by dragging mouse after pressing r.

[note for myself: add screenshots here because they will not understand what the hell I said]

===Modelling===
Finally my favourite part... not really...

This is the hardest thing you are going to do with the instrument at first. How do you start? It depends. How do you model it the more correct way? It depends. It depends....

What's the issue? There are a lot of types of instruments. Some of them are easy to do, some of them are hard (easy - TCI for DC-10, hard - Flap_Slat.ac (check it out I tried so hard and it looks amazing) for...)

Okay so let's get into real modelling. Usually you start with cube and model the frame of the instrument. Forget everything you know about how the instrument looks and make it align with references. Forget everything you know about how you saw it on the photos. If you don't have them next to your instrument, they are not going to be your references. I once made a big mistake modelling both TCI and Flaps instrument, well, I remembered that frame was smooth, and now I am fixing entire frame of the instrument...

Okay back to the tutorial. Turn on the Edit mode, and... use your knowledge about blender to align the model (aka cube which you are modifying) with references.[[File:Aligning the model with references.png|thumb|Aligning the model with references in Blender]]If you have done this, and you feel comfortable with it, that's very nice because this is the most important part of modelling instruments, aligning with references. You can make it look nice later.

But if you are new to 3D modelling, very likely you got stuck at this point. No worries, I will explain few things.

First of all aligning model with references is all about moving verts and edges to match the lines on the reference. You have few things that can help. First of all, to get more verts, aka to do a loop cut you use... yeah, Loop Cut tool which you can access on the left bar, or quicker using Ctrl+R (I suggest sticking to keyboard rather than mouse in modelling). Next thing is Bevel, which is the way to make curved edges. You can access that tool using Ctrl+B, or as usual on the left bar. After you do your Bevel you have few options that you can change, you will use mainly Width, and Segments. More segments make the edge, or whatever you apply the Bevel to, smoother. Technically at this stage you should be able to get something like I've got on the screenshot there ->.

What should I do after making the instrument frame (or anything else)? Honestly I have no idea what instrument you are modelling, so I can't tell you what to do... If you are starting with some Attitude Indicator, god bless you because this is the most complex thing you can do. I modelled entire main panel of Panavia Tornado and was literally unable to make a good looking Attitude Indicator.

If you are modelling some altimeter, usually you have to make cyllinder, then inset the front face a bit and then extrude back to make the frame and then apply a bit Bevel on the front part of the frame, move the face that you extruded to the correct place for the face of the instrument (aka the digits that I still have no idea how to do). Next add one more cyllinder which will be smaller and to that cyllinder the part that points to the value... the simplest type of instrument you can find...

In case the frame of altimeter or anything would be square, then again cube, and then make cyllinder and use Bool Tools' difference to cut cyllinder inside the cube, and then the same as with normal altimeter.

Modelling buttons is pretty simple thing... usually... You just align the cube or cyllinder with references, easy, right? Here you can do some more things, like applying Bevel to it, or making it more 3D by using Inset tool and after it you just extrude it.

[to be continued; note for myself: explain knobs and rounded dials]

===Texturing===

===Animating===

Discord

2025-01-03T19:16:17Z

SP-NTX: Fixed what Firstairforce, Virtual1stAF, and Xxxive broke. If some wiki moderator can take a look I would be very grateful.

'''Discord''' is used in the FlightGear community as an alternative to [[Mumble]], [[TeamSpeak]], [[FGCom]] or [[Ventrilo]].

Discord is a free voice and chat software that can be downloaded as an app or [https://discord.do/web/ used in a browser].

== Invite links ==
{{note|1=Its advised that you create a permanent account, instead of creating guest accounts as some people create duplicate accounts which clogs up the member logs and makes it more difficult to @mention people.}}

Furthermore many other FlightGear servers exist that you may need an personal invite to join. The easiest way to find them is to go to the FlightGear server and ask or ask in forums.

== FlightGear Communities on Discord ==

=== General, Help and Support, Communities ===

{| class=wikitable
! Topic !! Invite link
|-
| FlightGear
| https://discord.gg/rzuV2DR
|-
| FlightGear FDM School
| https://discord.gg/Uyrtsar
|-
| FlightGear Virtual Alliance
| https://discord.gg/VqzTG2N
|-
| FG Events
| https://discord.gg/GY4N6Cu
|-
| FG FDM School
| https://discord.gg/U5KXyMU
|-
| FlightGear Republic, A friendly community about FlightGear.
| https://discord.gg/sBJy46Uq7z
|-
|FlightGear soaring club
|https://discord.gg/NvJjmzMfRP
|}

=== Military Aviation Communities ===

{| class=wikitable
! Topic !! Invite link
|-
| Operation Red Flag military FG community (OPRF)
| https://discord.gg/ptVapkE
|-
| Combined Joint Task Force 50 (OPRF event planning/hosting and more)
| https://discord.gg/2nxjb6y
|-
|First Air Force
|https://discord.gg/thYdYUcq
|}

=== Country Specific Communities ===

{| class=wikitable
! Topic !! Invite link
|-
| FlightGear Australia (Scenery Development & Community)
| https://discord.gg/JzTEXsZ
|-
|FlightGear Australia 2 (New Server as original abandoned)
| https://discord.gg/8MY6cmDQbK
|-
| FlightGear Italia (ITA Mercenaries)
| https://discord.gg/5RzyXRf
|-
| FlightGear Germany
| https://discord.gg/FNnpjCPSze
|-
| FlightGear Indian Community
| https://discord.gg/Tu7n5FmG5S
|-
| FlightGear Asia
| https://discord.gg/7saCkA2jQj
|-
| FlightGear Hong Kong
| https://discord.gg/9QVKcT6skU
|-
|FlightGear Myanmar
|https://discord.gg/VbT88KEGrk
|-
|Flightgear Polska (Flightgear Poland)
|https://discord.gg/5J7uVYRhZV
|}

=== Aircraft-specific ===
{| class="wikitable"
! Aircraft !! Invite link
|-
| Aermacchi MB-339
| https://discord.gg/vNZ5ZPv
|-
| Airbus A350 Development
| https://discord.gg/vK5f2s6
|-
| Boeing F/A-18C Hornet
| https://discord.gg/8GzpdK4j8P
|-
| F-111 Aardvark
| https://discord.gg/DSrSbmx
|-
| [[General Dynamics F-16 Fighting Falcon]]
| https://discord.gg/8RcYnjA
|-
| Octal450 Hangar Development
| https://discord.gg/gxAhC3j
|-
| [[Mikoyan-Gurevich MiG-21bis]]
| https://discord.gg/bs8xyz3
|-
| [[Mirage 2000]]
| https://discord.gg/xZ3r2KR
|-
| Panavia Tornado
| https://discord.gg/SYxgzkCrSG
|-
| [[Saab 37 Viggen]]
| https://discord.gg/RJTwS9a
|-
| SEPECAT Jaguar
| https://discord.gg/G5q5XYN
|-
| FG-1000 Stealth Fighter
| https://discord.gg/3MFZauxyPW
|-
|Boeing 777
|https://discord.gg/k5RXxFgGDA
|-
|A-10 Warthog
|https://discord.gg/RmtjmsT5vS
|-
|Soviet Aviation for FGFS
|https://discord.gg/YC2EYGK5Xf
|-
|B-1 Lancer
|https://discord.gg/d2bhwFCnX2
|-
|[[PZL-Koliber-family | PZL Koliber family]]
|https://discord.gg/beADn2sWM6
|}

==External links==
*https://discord.com/ Official website

[[de:Discord]]

[[Category:Software]]
[[Category:Community]]
[[Category:Air Traffic Control]]

User:SP-NTX

2024-10-06T22:48:38Z

SP-NTX: A 'few' updates

This is a wiki page about me. I will share with you here everything I want you to know. This is by no means an informative page or something, just mine place to put some interesting things for others to see.{{user
| name = SP-NTX
| location = Zielona Góra, Poland
| age =
| job =
| interests = * FlightGear
* Sailing
* Astrophotography
* Plane Spotting
| callsign = * SP-NTX
* VIPER04
* VPR04
* PL-NEXT
| favourite = * McDonnell Douglas MD-11
* McDonnell Douglas KC-10
* Boeing 737
* PZL Koliber family
* Space Shuttle
* F16
| website = * https://flightgear-polska.github.io/
* https://github.com/SP-NTX
}}
==About me==
I’m from Poland. My home airport is EPZG - Zielona Góra Babimost, and I’m an avid plane spotter. But my passions extend far beyond aviation...

=== Sports ===
Since 2024, I’ve been sailing and racing on '''Laser (ILCA)''' class sailboats. Sailing is the most relaxing and interesting activity I know. The peacefulness of sailing in the evening with the sunset in the background is one of the most beautiful things you can imagine, but things get truly exciting when the wind picks up to 20 knots or more. There’s no better thing in this world than the power of the wind at full speed!

=== Photography ===
Photography is my second hobby. I love taking a lot of photos, especially when it comes to plane spotting. I'm a fan of old SLR cameras, especially Minolta Dynax 9, and Minolta X700. Taking photos on these old film cameras is something incredible (and expensive). On the other hand, my main photography equipment is old good Sony A900 and Sony A700. Awesome cameras. I also love astrophotography. It is hard, but on the other hand, when you finally get that image of Andromeda Galaxy, or Orion Nebula... You just can't stop doing it...

=== Music ===
Music is a very important part of me. I play both '''piano''' and '''guitar''', often composing and recording my own pieces. My musical tastes are varied, but I’m especially drawn to nu-metal and alternative rock. I also listen to synth-pop and new wave from time to time. My favorite bands include:
*'''Sick Puppies'''
*'''Linkin Park'''
*'''Evans Blue'''
*'''Lady Pank'''

If I were to recommend a few songs, check out:

* ''Cancer'' by Sick Puppies
* ''Pushing Me Away'' by Linkin Park
* ''Erase My Scars'' by Evans Blue
* ''Mała Wojna'' by Lady Pank

=== Musical Inspirations ===
Music isn’t just about listening; I enjoy creating it as well. On the guitar and piano, I compose original songs and experiment with different styles. From soft piano melodies to heavy guitar riffs. I promise that when I will record something which is not actually bad I will put it here...

=== Languages ===
I’m fluent in '''Polish''' and '''English'''. I can also speak in '''German''', though it isn't that good...

=== Programming ===
I code in:

* C++
* Python
* Nasal
* Visual Basic

==Everything about SP-NTX ==
<blockquote>''Hated by a majority for having a different opinion than others,''

''Forgotten by the rest,''

''Admired by a few,''

''Loved by some.''</blockquote>you actually have to read all this to understand me or hate me even more.

=== Where it all began?....===
I joined the community in the late 2019, found FlightGear after looking for Open Source projects. I started flying very frequently, I got into aviation and I was really happy to be a part of an amazing community, which FlightGear was back in the days. As some of you know, my callsign was PL-NEXT back then. I changed my callsign to SP-NTX on the 28th of April 2020.

Frequent flying with others was something I really enjoyed, flying alone - not really. Flying wing-to-wing with others was my favourite thing to do, and I still miss these days... Thanks SP-JBX, SP-BAN, SP-JAN, paf1, SP-KOK, SP-VOT for all our flights together, it was amazing... Hope you will read this, someday...

===The creation of FlightGear Polska ===
In August 2020, more precisely, on the 31st of August 2020, 15:44, with two of my friends (SP-VOT and KIZAK15) I started FlightGear Polska (Polish FlightGear Community), which still remains my biggest project and contribution to the FlightGear project. First pilots to be part of our Polish FlightGear community were SP-NTX (me), SP-VOT (Sokół), Kizak15 (Kizak), and LO126O (SP-MAO1). Next, as our discord server was growing, more people were joining the discord server, we made our YouTube channel (note to myself: put link here), and started posting some videos. We were flying very frequently with one another, it was the best time of my entire FlightGear carrer... Next, I got into developing aircrafts... I couldn't stand looking at... Boeing 737-800 trim wheel... It was the first half of November 2020 when I started re-modelling the throttle quadrant of 737... I had no idea where to start, what to do, but I knew the basics. After improving the model of that trim wheel, I started working on textures... that was complete hell... and still is... Some of my friends (SP-VOT, 2938) helped me with the project, but it turned out to be a complete failure... Meanwhile, we started our first Virtual Airline, the Polish Virtual Airlines, which was pretty nice, not gonna lie, not as advanced as others, but it was made to make flying even more interesting. And then it came, the 9vELT (9 wirtualna Eskadra Lotnictwa Taktycznego, or in english - 9th virtual Tactical Air Squadron)... It was a nice project started by SP-PAF (paf1). We started getting more and more people into it, and we started doing military operations. Our base was EP73 (Zegrze Pomorskie), and we were flying on MiG-21s... the one from the launcher, because OPRF one was too hard to fly for me back then. We switched to F16s and changed our airbase to EPZG, it was 23rd of November 2020, and it was a lot of fun... Flying all day with my friends and talking on voice channel, I wish I could do it at least one more time... Then we decided that we need some callsigns as a squadron, sooo, this is where VIPER callsigns began... VIPER01 was SP-PAF, VIPER02 was.... I am not sure, it doesn't matter... I was VIPER04, and I am so proud of that callsign... on the 24th of November we did a little airshow, which is actually FlightGear Polska first airshow ever, and for sure not the last one...

=== What goes up has got to fall===
25th of November, btw you won't believe if I told you one thing about that day but ok... We started arguing in the evening with SP-PAF and others... by we I mean I... I wanted Mirage 2000 to be added to the squadron, they wanted to stay with F16s only, and it went like that for a few hours, and you won't believe how from a little Mirage 2000 thing it came to FlightGear Polska fall down... 26th of November 2020, 15:11... The fall down of FlightGear Polska... let me not get into the details, let's just say FGPL is gone now. Maybe for the first time, but for sure not for the last. I started a new discord server, and believe or not, we had zero activity or at least nothing which could compare to the old FGPL in almost 3 years... I put A LOT of work into FGPL. Hundreds of hours of working on it, Thousands of flights, everything I could to make it the best and the biggest community in FlightGear.

===A new chapter===
In the late 2020, I started developing 737-400. It was my first big project, and it turned out pretty shitty, as you know, but I was proud that I've done something. Maybe I just made 737-400 out of 737-300, but with some nice new features, but I am proud that I have done something flyable. Around that time, I meet LOT87. He is a really ni... okay we will think about it later. He was a really nice guy, but remember this, as the story will turn around completely in... 3 years...

Early 2021, after loosing hope for bringing FGPL back to life - it doesn't matter - I never ever wanted FGPL back, I wanted my friends back, something you loose - you never get back (imagine this will happen one more time)... I started flying frequently again, very long flights, alone, and hated everyone and everything... Then I found one YouTube channel - Parrott 1221... He made a video about FG and he was from Poland. I got in contact with him, and we started flying together. He was, and is, a very nice guy. He started his own Virtual Airline, Parrott Airlines (note: double t at the end, it is very important and not a mistake xd). We were flying together very often, and I helped him with his Virtual Airline, also being a part of it. When he joined FlightGear Polska, for the first time since the fall down of FGPL, activity raised. The issue is - I always hated that new discord server, don't ask me why, I just hated it... And I still do... Early 2021 was a really hard time in my life irl, not gonna go into details, it was just really hard. Flying helped me - a bit, but it wasn't going well. Then Bysiek joined, he also made his own virtual airline - Performance Airlines. Later - I am not sure now... In 2021? Maybe in early 2022.... Janout joined the community. He also was and is and always will be a really nice person to me, I really enjoyed flying with him, but then he left the community for some time. Next, SP6FU joined, he was a very good developer, he started Evolving Airlines in the mid 2022, which was, is, and still remains the most advanced Virtual Airline out there, with website, flight logging system, and other features no other airline had. The only issue is Evolving Airlines is no more... Look how crazy it was, we had 5 Virtual Airlines in the same time, awesome, right? Around that time, I also joined The Random Developers, we started developing Boeing 747-400. It was a really nice project - and still is. I consider something as finished when it is actually finished, when there is nothing left to do. This might mean nothing will ever be finished... Also in the early 2021 I got banned from FlightGear discord server, maybe for the first time, for sure not for the last :D...

===We are VIPERs===
September 2022. We decided to bring some Virtual Air Forces back to life.... for example the one which never existed, but it actually did. When the drama with 9vELT started (look: FGPL fall down #1) I made my own squadron, PLvAF... So we decided to bring vAF back to life... First stage was Operacja Orzełek (Operation Eagle), which was a great success of VAF, the first big fight against FGRAF. Or at least it is because the enemy side didn't showed up?... The members of vAF back then were me, Parrott, SP6FU, SP-KOS, Noctol, and few more. Not gonna say who had which callsign (VIPER0x), but I had some other than the one I used in 9vELT. Then we made more and more missions, and it was, just, a lot of fun... for us, maybe not for others.

===One step forward - two step back===
February 2023. 2 years and 4 months since fall down of old FGPL. The FGPL shape was really, really bad. No flying, no activity on discord... guess what I've done. We switched to other discord server... other... the old one... and magically (with a big effort actually), the activity came back... and it came back a lot bigger than ever before. This might have been the best decision in terms of FGPL I have ever made.... of course other than actually starting the community. More and more new pilots joined, we started flying together, and new admins were SP-NTX, Parrott, Janout, LOT87, Marcin... Around that time - I am proud to say it - I became the first ever person to make a complete flight in FlightGear with HDR (with landing), and I was one of the few who had HDR working on their FlightGear builds (because back then we had issues with OSG, scenery, etc) But back to FGPL... we made a secret admin channel called #azbest on our discord server... don't ask me about why we called it like that (it was because one of the admins - Parrott, was collecting old gas masks which contained asbestos). This channel was like feel free to talk about anything and everything with no rules, I bet every single discord server have a channel like that. It actually was the most active channel on entire FGPL discord... 60% of the activity was that one channel... which actually is... 150 000 messages... if you are new to number of messages on discord channels etc this is A LOT. FlightGear Discord have 100k messages per year on avg iirc. Then it came - August 2023. We decided to make FlightGear Polska 3rd Anniversary event. It was a very big project, and the biggest event we have ever done (actually turned out to be the biggest airshow out there... ever....) I personally still can't believe we planned all this in a few days, and it turned out to be.... awesome. Good music, awesome pilots, excellent displays... Everything was perfect... but the activity wasn't at it's peak yet.

===The most active FlightGear community ===
In November 2023 we made the Independence Day Event, which is one of the best airshows we have ever made. This event made us even more confident that we are the best - the biggest community and so on. I was proud of it, my project - our project, became so big, so awesome... And the activity.... in November we had 22k messages on the server (which is awesome). The year was slowly ending, and at the end of 2023, we had over 100 000 messages in just 10 months (because we switched to a 'new' server in February). This, and the number of group flights, events, active members, made us the most active FlightGear community out there... for the first time... for the last time?...

===I am still a Developer ===
Around November 2023 I started working on DC-10 family cockpit rework. Sadly due to real life issues, no time and the fact that I always prefer quality over quantity - the development was going very slow. Around this time, I started flying less and less, focused on development and real life things. I also started working on new Boeing 737-400 model (which is the best 3D model I made likely, not public yet). I also continued working on PZL Koliber family, mainly focused on systems.

===''I hope this year will be better than the last one''===
2024... don't.... ask.....

Okay so it started pretty okay, pretty much nothing changed...

We started preparations to FlightGear Polska 4th Anniversary very early, like in February or something. We wanted it to be the biggest event of the year (it is), far bigger than FGPL3, a lot of airshow trainings were made, a lot of new pilots joined us, it was awesome. Next we started working on the new logo (the current one). Meanwhile, I was focused on developing a new cockpit for DC-10, but my laptop sadly broke and all my Autopilot Panel and Overhead Panel work was gone (along with thousands of plane spotting photos...).

===We are FlightGear Polska===
On the 3rd of April 2024, member of our community got banned from FlightGear discord for racism. Actually, this was a thing which had absolutely nothing to do with his actions or whatever, he just had in his profile something which one admin and one other person decided that is a big issue, racism, and everything they could imagine... are you guys serious? We are in 2024. Instead of asking him to remove that thing from his profile, they just banned him and gave him no way to say sorry or whatever. The best part is that this thing actually wasn't against the rules of the server. We, with FlightGear Polska admins, stated an open letter to FlightGear Administration, which was created just to be an informative thing that rules do not cover such things and should be updates, and that we don't support racism or whatever. FlightGear discord administration considered this literally like some personal attack and FlightGear Polska administrators (and other members of our community?) got banned from FlightGear discord, when it almost came to the point where you could get banned just for being from Poland. This was how our community was treated by others. We didn't care, and all we cared about, is that we at least tried to defend member of our community - as he couldn't defend himself because of getting banned. I also got banned from FlightGear discord server...

===What the hell? (or I wanna know the truth, instead of wondering why)===
There is one thing, around July, to be more precise, that is.... Okay so the thing is I can't tell you anything about it. As I promised to someone, we might or might not declassify it after 10 years. This is like, a strange thing... like for real. You wouldn't imagine such things can happen on FlightGear community server, that these things are so, so strange.... You wouldn't believe even if I told you... It was killing me a bit xd

===FlightGear Polska 4th Anniversary===
It was now just few weeks from the FGPL4, and... guess what... It turned out that we couldn't do the event on the date we planned (neither on the backup one).... Finally we decided it will be 21st and 22nd of August 2024.

I am not gonna write entire story of FGPL4 here, because it is not important

===What the hell? #2===
Now as we reach other stage of that thing, some people decided that I need to distance myself from them and what they do (even if I should), so to make me shut up, they decided to stalk me out and tell all my personal details they managed to find on voice channel after event... Pretty much 'what the hell?' thing, right? If you want to take a look at this, DM me on discord someday, I might or might not show you what happened... Remember that I care about privacy A LOT, that's why it actually made me shut up and stop trying to fix what I wanted to fix.... for 3 days XD. At least while this was happening, I meet someone in FlightGear, who I can really trust, this is the only good thing that happened to me in weeks. Also it was the end of SP-NTX btw... You might ask, what?... Well, you don't have to understand, just consider this as some new stage in my life.

===This is war, and it's on tonight===
In early September 2024, we made new administration on FGPL discord server, and banned Parrott and Janout for... well... the thing I described a while ago.... The new administration consisted of SP-RVB (Rybavenryba), SP-KAD (Kadman), 0001 (josalx), LOT87, SP-BFA (BlueFireAngel) and me - SP-NTX.... And it was the best administration we had (it was not). We were working together on new event, which was also an airshow, and we made one, special display. SP-NTX vs SP-LWP (Parrott) 1v1... I actually won! (Which later turned out to be a mistake and if I would lose it would have been better).

===It's going down===
We started arguing a bit in the new administration, it is a bit about that drama (what the hell), and the fact that I didn't cared so much about FGPL, I cared mostly about my friends. I didn't really even cared about myself, just others. It wasn't good, but this is who I am and who I will always be. I always care about others, a lot. Especially someone who is my real friend, I just can't focus on myself or whatever, I care about others. The thing is it was destroying me a bit, maybe, I don't know. So the thing is the new administration decided that I need to rethink what I am doing or they will leave... They made an event, which also was an airshow, and I just wanted the last display of the airshow to be mine final display in FlightGear before a long break, but they started telling me to f off and so on. Then they started threatening me that they will remove all channels and so on... So I removed their admin roles.... and everything was going pretty much okay... not really

===What is it I'm after, searching for disaster?===
They made a voting, whether I should be owner of FGPL or not, well... guess what... So I decided that I will respect the decision of the biased part of the community and give FGPL to someone I trusted a lot and he would just give me it back after a day or two... So LOT87 had the ownership of FGPL now, and I left.... Then after a hour or two one of my friends who was admin texted me that he lost his admin roles and 0001 (josalx) (actually maybe my biggest enemy in the entire FlightGear community now (?) had the ownership of FGPL.... I was damn mad at LOT87, because he told me that I can trust him and so on. Then they banned me from FGPL. I decided that I can use my own bot I made to just ban other admins from FGPL and copy all the channels, so I could at least try to fix all it, but it was far too late as they banned the bot. What was the real issue? They had access to the secret admin channel now.... which was okay as long as it was just me, Parrott, and Janout, but what was going on later, after I banned them, is something what is going to be secret for a long time... And they started threatening me that they will show it to Parrott and Janout (if they did, they would literally kill me...) And don't ask how, we managed to remove the channel (with help of SP-BFA, very bad decision making of 0001, and my skills of being idiot). Next I found a chance to fix all this... Well, FGPL was in the worst shape ever, and I made it appear like there is no way he can do anything with it, and after a hour of arguing he gave me the ownership back........ FGPL was and maybe still is gone for me at this stage, but who knows. It was 20th of September 2024. What happened the same evening after it, is.... I don't really understand, this was sad thing. I mean I understand.... Sometimes solutions aren't so simple.... sometimes goodbye is the only way...

===Don't walk away, and leave without a reason....===
So now as everything was completely destroyed, maybe, 0001 started his own Virtual Air Forces (well wait, again?), and well, what was happening later is the worst that ever happened to FGPL or just me...

Then SP-KAD decided that I was very bad to him etc so he decided to show some of my messages out of context to that person I trusted a lot etc etc and well, he managed to finally break me down by doing this. I couldn't stand being a part of FlightGear community at that moment. Lost all my friends, lost my community, lost everything I had worked for so long. Who knows, maybe things will turn around one day? For now, all I can say, is that I am broken down, FGPL is gone, and everything is fine.

And here I feel like I need to put a few verses from one song... Only one person other than me will understand what, why, and so on.... We're all out of time, this is how we find how it all unwinds... the sacrifice is never knowing...

I wanted, and still want to leave FlightGear... This all what happened, it broke me down completely. I spend so many years working on FGPL, lost so many friends..... This is how we fall apart....

But I can't, I can't leave. FlightGear is a part of me, I can't stop being a developer, I can't stop trying to save FGPL. I never give up....

===The best is yet to come, just need to wait for it, one day, everything will turn around===

==My projects==

*737-400 ([https://github.com/SP-NTX/737-400<nowiki>])</nowiki>
*Liveries ([https://github.com/SP-NTX/SP-NTX_Liveries<nowiki>])</nowiki>
*Aerolite 103
*PZL Koliber Family ([https://github.com/SP-NTX/PZL-Koliber-family<nowiki>])</nowiki>
*DC-10 Family cockpit development

==I'm actually working on==

*New 3D model for 737-400
*Translating & Updating fgwiki
*Creating High Quality Liveries & 3D models

and some another projects

==My favourite Aircrafts==

*MD-11
*Concorde
*Space Shuttle
*Boeing 737-800 and MAX 8
*Boeing 747(-400)
*Boeing 757
*Airbus A320
*Boeing 787

*Embraer E-Jets
*F16

==For the beginning developers :D==
Im writing that not as tutorial, just based on my small experience.
First of all, if you are in this moment, while you know, that you need to do something for FG, welcome, now you need to choose what to do, and you will be good at this.
Now, what you want to do? Liveries? Aircrafts? Scenery? or maybe Addons? I know, it's hard thing to choose. I suggest to start with Liveries if you never touched anything in the FG 'backend'.
Ok so download GIMP and find the aircraft folder, try to find the paintkit, and play with it. No, there is no any good tutorial for liveries on FGwiki, so try to find something on FGforum.
You should read few GIMP tutorials. Then export it to the liveries folder, copy another livery xml and edit it to make it work for your livery. And it should be easy.
Your first livery is not going to look amazing, it will probably be bad, but, do the next one, and next one, and then your liveries will look amazing.
If you think it's not for you, no problem, but other things will be harder. For aircrafts and scenery you will need to learn 3D modelling, and no one is going to write
tutorial for 3d modelling here, so open youtube and write '3D modelling tutorial for Blender' or other 3D modelling apps. then read some things about modelling on the FGwiki, but it will not make you get new skills...
Ok if you think the modelling is not for you, congratulations, it was good choice, then try programming. No, im not talking about the FG Core or addons, it's like trying to fly Space Shuttle, when you flew only Gliders ;).
Start with simple Nasal scripts, here i'm giving you what you should read first. YES I KNOW IT'S LOOKING SO BAD BUT TRY IT AND YOU WILL UNDERSTAND (F10 menu>Debug>Nasal Console).
Ok before i will add a lot of links here i want to say few things. Maybe, but only maybe, it's better to start with Canvas...

https://wiki.flightgear.org/Nasal_scripting_language - read this but it will not give you anything

https://wiki.flightgear.org/Nasal_Hello_World - it also will not give you anything

https://wiki.flightgear.org/Howto:Create_a_new_Nasal_module - ok, this may be useful, try to read the code after reading text

https://wiki.flightgear.org/Using_Nasal_functions - this is really, really important imo, look at the "Simple examples"

https://wiki.flightgear.org/Howto:Understand_Namespaces_and_Methods - and this is hard, even for me, but a lot of nice informations, should be easy to understand

https://wiki.flightgear.org/Nasal_Loops - its little harder, but very important

https://wiki.flightgear.org/Nasal_Operators - And remember those thing '~' for adding strings to each other, you will need this someday.

And, for now, that's all.
Later when i will have little more time i will create github repo with nice examples for those.

Ok now you can start programming simple things, try to make the simple kts2mph converter.
<syntaxhighlight line="1" start="1">
# Ok, lets start our code.
var loop func() { # Looks bad, but, look, its easy, its our main loop start
var ktsSpd = getprop("/"); # Im naming this variable ktsSpd, then im setting it to the property.
var mphSpd = (ktsSpd*1.15077945); # wait, where i get 1.15077945? 1 kts is 1.15077945 MPH
print(mphSpd); # i have nothing else to do with it than just printing it to console
} # Ok, this ends the loop
timer_loop = maketimer(0.25, loop); # i send link about Nasal_Loops, didn't I?
timer_loop.start(); # start the timer

</syntaxhighlight>
Ok so you tested my code? i wrote it in few minutes, and why i said in comment about the Nasal loops article? because i forgot how to do that, so i checked. No, you are not going to remember everything, you can always go back to those links.
What you can do next? Do something cool! It will make new things easier to remember, you don't have ideas? me too... But you can do even something stupid! Did you looked at the Nasal_Hello_Word atricle? I remember that there was code for popup message, maybe, when the property changes (here you can use setlistener , Nasal_Loops, gears/gear[]/wow) i mean, when you take off, make something like: You are taking off, and there will be message: Goog flight!? Yes this is stupid, but you will learn how to: Make loop, set setlistener(), finding property, making GUI popup, and why to not forget about ';' on end of the line. Isn't it nice? Code for that will be available on my github repo comeday, i will give link :-), but try to do this yourself. Do some other things, for example, automatic gear retraction and extending while alt > or < than some value. Code for that will be available too someday. Ok, so, you know basics of nasal, amazing, i hope you will like it. Ok so what now? Try Canvas, i started with it, thats why i said that before. Canvas is hard, its not easy thing, i will not give links this time, just read everything what you think it will be useful, also, check this https://forum.flightgear.org/viewtopic.php?f=71&t=38998 even if it's boring. After reading all that text, i just want to say you, thank you, you probably learned something new, from other point of view. I wasn't planning to make it as long, but, it's going to be extended later. Now i'm going to make tutorial about making addons, because i can't make tutorial for everything on this page. To be extended (someday)

==Modelling instruments in Blender (any version above 2.80)==
Everything I say here is based on my own experience, work and each and every time I told myself that modelling is complete sh*t

===Getting references===
First and at the same time most important thing out there. Is it hard? It depends, but usually you will have to do at least 'quick' search...

Where do you start? Look at aircraft POH, FCOM or service manual. Usually you will find some drawings in them, but remember that they are usually not very detailed. Next, try to find some images of the instrument you want to model, it might not be that easy if you model some unusual instrument like TCI for DC-10 or Boeing 747-200s vertictal tape engine instruments... There is another reference that some people forget, while it is actually very important. Look at the videos, cockpit tours, or any other thing like that. It might give better quality references than images. Cockpit posters are usually low quality and even more off than drawings, avoid using these if you don't really need them!

===Setting up references===
This may be a complex thing but don't worry, you will find it easier with each instrument you model.

First of all open your Blender and set up a new project. This sound complex but all you have to do is removing everything from the scene, so the select the default cube, camera and light and click delete.

I assume that you know a bit about navgation in Blender... if not, please watch tutorial about it before modelling your first instrument ok?...

What type of reference you should start with? Well, you would like to start with some drawing, it will be easiest to start modelling the instrument. I also assume you know how to add images to the viewport... (if not: shift+a image>reference, or easier drag and drop to the viewport).

You want the reference to be aligned with... x or axis... How to do it easily? 2 ways. If you go drag and drop method of adding references, align the camera with the X axis... no not manually, using that thing on top right part of the viewport clicking on X, and then just drag and drop the image. If you go shift+a way, then you have to rotate the image, for this use key r and then axis (x, y, z) and then value (deg), like r x 90. If you are new to blender you will find this pretty... strange... Actually this is saving so much time I use it more often than rotating by dragging mouse after pressing r.

[note for myself: add screenshots here because they will not understand what the hell I said]

===Modelling===
Finally my favourite part... not really...

This is the hardest thing you are going to do with the instrument at first. How do you start? It depends. How do you model it the more correct way? It depends. It depends....

What's the issue? There are a lot of types of instruments. Some of them are easy to do, some of them are hard (easy - TCI for DC-10, hard - Flap_Slat.ac (check it out I tried so hard and it looks amazing) for...)

Okay so let's get into real modelling. Usually you start with cube and model the frame of the instrument. Forget everything you know about how the instrument looks and make it align with references. Forget everything you know about how you saw it on the photos. If you don't have them next to your instrument, they are not going to be your references. I once made a big mistake modelling both TCI and Flaps instrument, well, I remembered that frame was smooth, and now I am fixing entire frame of the instrument...

Okay back to the tutorial. Turn on the Edit mode, and... use your knowledge about blender to align the model (aka cube which you are modifying) with references.[[File:Aligning the model with references.png|thumb|Aligning the model with references in Blender]]If you have done this, and you feel comfortable with it, that's very nice because this is the most important part of modelling instruments, aligning with references. You can make it look nice later.

But if you are new to 3D modelling, very likely you got stuck at this point. No worries, I will explain few things.

First of all aligning model with references is all about moving verts and edges to match the lines on the reference. You have few things that can help. First of all, to get more verts, aka to do a loop cut you use... yeah, Loop Cut tool which you can access on the left bar, or quicker using Ctrl+R (I suggest sticking to keyboard rather than mouse in modelling). Next thing is Bevel, which is the way to make curved edges. You can access that tool using Ctrl+B, or as usual on the left bar. After you do your Bevel you have few options that you can change, you will use mainly Width, and Segments. More segments make the edge, or whatever you apply the Bevel to, smoother. Technically at this stage you should be able to get something like I've got on the screenshot there ->.

What should I do after making the instrument frame (or anything else)? Honestly I have no idea what instrument you are modelling, so I can't tell you what to do... If you are starting with some Attitude Indicator, god bless you because this is the most complex thing you can do. I modelled entire main panel of Panavia Tornado and was literally unable to make a good looking Attitude Indicator.

If you are modelling some altimeter, usually you have to make cyllinder, then inset the front face a bit and then extrude back to make the frame and then apply a bit Bevel on the front part of the frame, move the face that you extruded to the correct place for the face of the instrument (aka the digits that I still have no idea how to do). Next add one more cyllinder which will be smaller and to that cyllinder the part that points to the value... the simplest type of instrument you can find...

In case the frame of altimeter or anything would be square, then again cube, and then make cyllinder and use Bool Tools' difference to cut cyllinder inside the cube, and then the same as with normal altimeter.

Modelling buttons is pretty simple thing... usually... You just align the cube or cyllinder with references, easy, right? Here you can do some more things, like applying Bevel to it, or making it more 3D by using Inset tool and after it you just extrude it.

[to be continued; note for myself: explain knobs and rounded dials]

===Texturing===

===Animating===

User:SP-NTX

2024-01-13T04:30:07Z

SP-NTX:

FlightGear aircraft & scenery developer.

I'm in FlightGear since 2020.

==My projects==

* 737-400 ([https://github.com/SP-NTX/737-400<nowiki>])</nowiki>
* Liveries ([https://github.com/SP-NTX/SP-NTX_Liveries<nowiki>])</nowiki>
* Aerolite 103

== I'm actually working on ==

* New 3D model for 737-400
* Translating & Updating fgwiki
* Creating High Quality Liveries & 3D models

and some another projects

== My favourite Aircrafts ==

* MD-11
* Concorde
* Space Shuttle
* Boeing 737-800 and MAX 8
* Boeing 747(-400)
* Boeing 757
* Airbus A320
* Boeing 787

* Embraer E-Jets
* F16

== For the beginning developers :D ==
Im writing that not as tutorial, just based on my small experience.
First of all, if you are in this moment, while you know, that you need to do something for FG, welcome, now you need to choose what to do, and you will be good at this.
Now, what you want to do? Liveries? Aircrafts? Scenery? or maybe Addons? I know, it's hard thing to choose. I suggest to start with Liveries if you never touched anything in the FG 'backend'.
Ok so download GIMP and find the aircraft folder, try to find the paintkit, and play with it. No, there is no any good tutorial for liveries on FGwiki, so try to find something on FGforum.
You should read few GIMP tutorials. Then export it to the liveries folder, copy another livery xml and edit it to make it work for your livery. And it should be easy.
Your first livery is not going to look amazing, it will probably be bad, but, do the next one, and next one, and then your liveries will look amazing.
If you think it's not for you, no problem, but other things will be harder. For aircrafts and scenery you will need to learn 3D modelling, and no one is going to write
tutorial for 3d modelling here, so open youtube and write '3D modelling tutorial for Blender' or other 3D modelling apps. then read some things about modelling on the FGwiki, but it will not make you get new skills...
Ok if you think the modelling is not for you, congratulations, it was good choice, then try programming. No, im not talking about the FG Core or addons, it's like trying to fly Space Shuttle, when you flew only Gliders ;).
Start with simple Nasal scripts, here i'm giving you what you should read first. YES I KNOW IT'S LOOKING SO BAD BUT TRY IT AND YOU WILL UNDERSTAND (F10 menu>Debug>Nasal Console).
Ok before i will add a lot of links here i want to say few things. Maybe, but only maybe, it's better to start with Canvas...

https://wiki.flightgear.org/Nasal_scripting_language - read this but it will not give you anything

https://wiki.flightgear.org/Nasal_Hello_World - it also will not give you anything

https://wiki.flightgear.org/Howto:Create_a_new_Nasal_module - ok, this may be useful, try to read the code after reading text

https://wiki.flightgear.org/Using_Nasal_functions - this is really, really important imo, look at the "Simple examples"

https://wiki.flightgear.org/Howto:Understand_Namespaces_and_Methods - and this is hard, even for me, but a lot of nice informations, should be easy to understand

https://wiki.flightgear.org/Nasal_Loops - its little harder, but very important

https://wiki.flightgear.org/Nasal_Operators - And remember those thing '~' for adding strings to each other, you will need this someday.

And, for now, that's all.
Later when i will have little more time i will create github repo with nice examples for those.

Ok now you can start programming simple things, try to make the simple kts2mph converter.
<syntaxhighlight line="1" start="1">
# Ok, lets start our code.
var loop func() { # Looks bad, but, look, its easy, its our main loop start
var ktsSpd = getprop("/"); # Im naming this variable ktsSpd, then im setting it to the property.
var mphSpd = (ktsSpd*1.15077945); # wait, where i get 1.15077945? 1 kts is 1.15077945 MPH
print(mphSpd); # i have nothing else to do with it than just printing it to console
} # Ok, this ends the loop
timer_loop = maketimer(0.25, loop); # i send link about Nasal_Loops, didn't I?
timer_loop.start(); # start the timer

</syntaxhighlight>
Ok so you tested my code? i wrote it in few minutes, and why i said in comment about the Nasal loops article? because i forgot how to do that, so i checked. No, you are not going to remember everything, you can always go back to those links.
What you can do next? Do something cool! It will make new things easier to remember, you don't have ideas? me too... But you can do even something stupid! Did you looked at the Nasal_Hello_Word atricle? I remember that there was code for popup message, maybe, when the property changes (here you can use setlistener , Nasal_Loops, gears/gear[]/wow) i mean, when you take off, make something like: You are taking off, and there will be message: Goog flight!? Yes this is stupid, but you will learn how to: Make loop, set setlistener(), finding property, making GUI popup, and why to not forget about ';' on end of the line. Isn't it nice? Code for that will be available on my github repo comeday, i will give link :-), but try to do this yourself. Do some other things, for example, automatic gear retraction and extending while alt > or < than some value. Code for that will be available too someday. Ok, so, you know basics of nasal, amazing, i hope you will like it. Ok so what now? Try Canvas, i started with it, thats why i said that before. Canvas is hard, its not easy thing, i will not give links this time, just read everything what you think it will be useful, also, check this https://forum.flightgear.org/viewtopic.php?f=71&t=38998 even if it's boring. After reading all that text, i just want to say you, thank you, you probably learned something new, from other point of view. I wasn't planning to make it as long, but, it's going to be extended later. Now i'm going to make tutorial about making addons, because i can't make tutorial for everything on this page. To be extended (someday)

== Modelling instruments in Blender (any version above 2.80) ==
Everything I say here is based on my own experience, work and each and every time I told myself that modelling is complete sh*t

=== Getting references ===
First and at the same time most important thing out there. Is it hard? It depends, but usually you will have to do at least 'quick' search...

Where do you start? Look at aircraft POH, FCOM or service manual. Usually you will find some drawings in them, but remember that they are usually not very detailed. Next, try to find some images of the instrument you want to model, it might not be that easy if you model some unusual instrument like TCI for DC-10 or Boeing 747-200s vertictal tape engine instruments... There is another reference that some people forget, while it is actually very important. Look at the videos, cockpit tours, or any other thing like that. It might give better quality references than images. Cockpit posters are usually low quality and even more off than drawings, avoid using these if you don't really need them!

=== Setting up references ===
This may be a complex thing but don't worry, you will find it easier with each instrument you model.

First of all open your Blender and set up a new project. This sound complex but all you have to do is removing everything from the scene, so the select the default cube, camera and light and click delete.

I assume that you know a bit about navgation in Blender... if not, please watch tutorial about it before modelling your first instrument ok?...

What type of reference you should start with? Well, you would like to start with some drawing, it will be easiest to start modelling the instrument. I also assume you know how to add images to the viewport... (if not: shift+a image>reference, or easier drag and drop to the viewport).

You want the reference to be aligned with... x or axis... How to do it easily? 2 ways. If you go drag and drop method of adding references, align the camera with the X axis... no not manually, using that thing on top right part of the viewport clicking on X, and then just drag and drop the image. If you go shift+a way, then you have to rotate the image, for this use key r and then axis (x, y, z) and then value (deg), like r x 90. If you are new to blender you will find this pretty... strange... Actually this is saving so much time I use it more often than rotating by dragging mouse after pressing r.

[note for myself: add screenshots here because they will not understand what the hell I said]

=== Modelling ===
Finally my favourite part... not really...

This is the hardest thing you are going to do with the instrument at first. How do you start? It depends. How do you model it the more correct way? It depends. It depends....

What's the issue? There are a lot of types of instruments. Some of them are easy to do, some of them are hard (easy - TCI for DC-10, hard - Flap_Slat.ac (check it out I tried so hard and it looks amazing) for...)

Okay so let's get into real modelling. Usually you start with cube and model the frame of the instrument. Forget everything you know about how the instrument looks and make it align with references. Forget everything you know about how you saw it on the photos. If you don't have them next to your instrument, they are not going to be your references. I once made a big mistake modelling both TCI and Flaps instrument, well, I remembered that frame was smooth, and now I am fixing entire frame of the instrument...

Okay back to the tutorial. Turn on the Edit mode, and... use your knowledge about blender to align the model (aka cube which you are modifying) with references.[[File:Aligning the model with references.png|thumb|Aligning the model with references in Blender]]If you have done this, and you feel comfortable with it, that's very nice because this is the most important part of modelling instruments, aligning with references. You can make it look nice later.

But if you are new to 3D modelling, very likely you got stuck at this point. No worries, I will explain few things.

First of all aligning model with references is all about moving verts and edges to match the lines on the reference. You have few things that can help. First of all, to get more verts, aka to do a loop cut you use... yeah, Loop Cut tool which you can access on the left bar, or quicker using Ctrl+R (I suggest sticking to keyboard rather than mouse in modelling). Next thing is Bevel, which is the way to make curved edges. You can access that tool using Ctrl+B, or as usual on the left bar. After you do your Bevel you have few options that you can change, you will use mainly Width, and Segments. More segments make the edge, or whatever you apply the Bevel to, smoother. Technically at this stage you should be able to get something like I've got on the screenshot there ->.

What should I do after making the instrument frame (or anything else)? Honestly I have no idea what instrument you are modelling, so I can't tell you what to do... If you are starting with some Attitude Indicator, god bless you because this is the most complex thing you can do. I modelled entire main panel of Panavia Tornado and was literally unable to make a good looking Attitude Indicator.

If you are modelling some altimeter, usually you have to make cyllinder, then inset the front face a bit and then extrude back to make the frame and then apply a bit Bevel on the front part of the frame, move the face that you extruded to the correct place for the face of the instrument (aka the digits that I still have no idea how to do). Next add one more cyllinder which will be smaller and to that cyllinder the part that points to the value... the simplest type of instrument you can find...

In case the frame of altimeter or anything would be square, then again cube, and then make cyllinder and use Bool Tools' difference to cut cyllinder inside the cube, and then the same as with normal altimeter.

Modelling buttons is pretty simple thing... usually... You just align the cube or cyllinder with references, easy, right? Here you can do some more things, like applying Bevel to it, or making it more 3D by using Inset tool and after it you just extrude it.

[to be continued; note for myself: explain knobs and rounded dials]

=== Texturing ===

=== Animating ===

File:Aligning the model with references.png

2024-01-13T04:05:25Z

SP-NTX: Uploaded own work with UploadWizard

=={{int:filedesc}}==
{{Information
|description={{en|1=Aligning the model with references in Blender}}
|date=2024-01-13
|source={{own}}
|author=[[User:SP-NTX|SP-NTX]]
|permission=
|other versions=
}}

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

User:SP-NTX

2024-01-13T00:13:48Z

SP-NTX: Modelling instruments in blender fromy my point of view WIP

FlightGear aircraft & scenery developer.

I'm in FlightGear since 2020.

==My projects==

* 737-400 ([https://github.com/SP-NTX/737-400<nowiki>])</nowiki>
* Liveries ([https://github.com/SP-NTX/SP-NTX_Liveries<nowiki>])</nowiki>
* Aerolite 103

== I'm actually working on ==

* New 3D model for 737-400
* Translating & Updating fgwiki
* Creating High Quality Liveries & 3D models

and some another projects

== My favourite Aircrafts ==

* MD-11
* Concorde
* Space Shuttle
* Boeing 737-800 and MAX 8
* Boeing 747(-400)
* Boeing 757
* Airbus A320
* Boeing 787

* Embraer E-Jets
* F16

== For the beginning developers :D ==
Im writing that not as tutorial, just based on my small experience.
First of all, if you are in this moment, while you know, that you need to do something for FG, welcome, now you need to choose what to do, and you will be good at this.
Now, what you want to do? Liveries? Aircrafts? Scenery? or maybe Addons? I know, it's hard thing to choose. I suggest to start with Liveries if you never touched anything in the FG 'backend'.
Ok so download GIMP and find the aircraft folder, try to find the paintkit, and play with it. No, there is no any good tutorial for liveries on FGwiki, so try to find something on FGforum.
You should read few GIMP tutorials. Then export it to the liveries folder, copy another livery xml and edit it to make it work for your livery. And it should be easy.
Your first livery is not going to look amazing, it will probably be bad, but, do the next one, and next one, and then your liveries will look amazing.
If you think it's not for you, no problem, but other things will be harder. For aircrafts and scenery you will need to learn 3D modelling, and no one is going to write
tutorial for 3d modelling here, so open youtube and write '3D modelling tutorial for Blender' or other 3D modelling apps. then read some things about modelling on the FGwiki, but it will not make you get new skills...
Ok if you think the modelling is not for you, congratulations, it was good choice, then try programming. No, im not talking about the FG Core or addons, it's like trying to fly Space Shuttle, when you flew only Gliders ;).
Start with simple Nasal scripts, here i'm giving you what you should read first. YES I KNOW IT'S LOOKING SO BAD BUT TRY IT AND YOU WILL UNDERSTAND (F10 menu>Debug>Nasal Console).
Ok before i will add a lot of links here i want to say few things. Maybe, but only maybe, it's better to start with Canvas...

https://wiki.flightgear.org/Nasal_scripting_language - read this but it will not give you anything

https://wiki.flightgear.org/Nasal_Hello_World - it also will not give you anything

https://wiki.flightgear.org/Howto:Create_a_new_Nasal_module - ok, this may be useful, try to read the code after reading text

https://wiki.flightgear.org/Using_Nasal_functions - this is really, really important imo, look at the "Simple examples"

https://wiki.flightgear.org/Howto:Understand_Namespaces_and_Methods - and this is hard, even for me, but a lot of nice informations, should be easy to understand

https://wiki.flightgear.org/Nasal_Loops - its little harder, but very important

https://wiki.flightgear.org/Nasal_Operators - And remember those thing '~' for adding strings to each other, you will need this someday.

And, for now, that's all.
Later when i will have little more time i will create github repo with nice examples for those.

Ok now you can start programming simple things, try to make the simple kts2mph converter.
<syntaxhighlight line="1" start="1">
# Ok, lets start our code.
var loop func() { # Looks bad, but, look, its easy, its our main loop start
var ktsSpd = getprop("/"); # Im naming this variable ktsSpd, then im setting it to the property.
var mphSpd = (ktsSpd*1.15077945); # wait, where i get 1.15077945? 1 kts is 1.15077945 MPH
print(mphSpd); # i have nothing else to do with it than just printing it to console
} # Ok, this ends the loop
timer_loop = maketimer(0.25, loop); # i send link about Nasal_Loops, didn't I?
timer_loop.start(); # start the timer

</syntaxhighlight>
Ok so you tested my code? i wrote it in few minutes, and why i said in comment about the Nasal loops article? because i forgot how to do that, so i checked. No, you are not going to remember everything, you can always go back to those links.
What you can do next? Do something cool! It will make new things easier to remember, you don't have ideas? me too... But you can do even something stupid! Did you looked at the Nasal_Hello_Word atricle? I remember that there was code for popup message, maybe, when the property changes (here you can use setlistener , Nasal_Loops, gears/gear[]/wow) i mean, when you take off, make something like: You are taking off, and there will be message: Goog flight!? Yes this is stupid, but you will learn how to: Make loop, set setlistener(), finding property, making GUI popup, and why to not forget about ';' on end of the line. Isn't it nice? Code for that will be available on my github repo comeday, i will give link :-), but try to do this yourself. Do some other things, for example, automatic gear retraction and extending while alt > or < than some value. Code for that will be available too someday. Ok, so, you know basics of nasal, amazing, i hope you will like it. Ok so what now? Try Canvas, i started with it, thats why i said that before. Canvas is hard, its not easy thing, i will not give links this time, just read everything what you think it will be useful, also, check this https://forum.flightgear.org/viewtopic.php?f=71&t=38998 even if it's boring. After reading all that text, i just want to say you, thank you, you probably learned something new, from other point of view. I wasn't planning to make it as long, but, it's going to be extended later. Now i'm going to make tutorial about making addons, because i can't make tutorial for everything on this page. To be extended (someday)

== Modelling instruments in Blender (any version above 2.80) ==

=== Getting references ===
First and at the same time most important thing out there. Is it hard? It depends, but usually you will have to do at least 'quick' search...

Where do you start? Look at aircraft POH, FCOM or service manual. Usually you will find some drawings in them, but remember that they are usually not very detailed. Next, try to find some images of the instrument you want to model, it might not be that easy if you model some unusual instrument like TCI for DC-10 or Boeing 747-200s vertictal tape engine instruments... There is another reference that some people forget, while it is actually very important. Look at the videos, cockpit tours, or any other thing like that. It might give better quality references than images. Cockpit posters are usually low quality and even more off than drawings, avoid using these if you don't really need them!

=== Setting up references ===
This may be a complex thing but don't worry, you will find it easier with each instrument you model.

First of all open your Blender and set up a new project. This sound complex but all you have to do is removing everything from the scene, so the select the default cube, camera and light and click delete.

I assume that you know a bit about navgation in Blender... if not, please watch tutorial about it before modelling your first instrument ok?...

What type of reference you should start with? Well, you would like to start with some drawing, it will be easiest to start modelling the instrument. I also assume you know how to add images to the viewport... (if not: shift+a image>reference, or easier drag and drop to the viewport).

You want the reference to be aligned with... x or axis... How to do it easily? 2 ways. If you go drag and drop method of adding references, align the camera with the X axis... no not manually, using that thing on top right part of the viewport clicking on X, and then just drag and drop the image. If you go shift+a way, then you have to rotate the image, for this use key r and then axis (x, y, z) and then value (deg), like r x 90. If you are new to blender you will find this pretty... strange... Actually this is saving so much time I use it more often than rotating by dragging mouse after pressing r.

[note for myself: add screenshots here because they will not understand what the hell I said]

=== Modelling ===
Finally my favourite part... not really...

This is the hardest thing you are going to do with the instrument at first. How do you start? It depends. How do you model it the more correct way? It depends. It depends....

What's the issue? There are a lot of types of instruments. Some of them are easy to do, some of them are hard (easy - TCI for DC-10, hard - Flap_Slat.ac (check it out I tried so hard and it looks amazing) for...)

Okay so let's get into real modelling. Usually you start with cube and model the frame of the instrument. Forget everything you know about how the instrument looks and make it align with references. Forget everything you know about how you saw it on the photos. If you don't have them next to your instrument, they are not going to be your references. I once made a big mistake modelling both TCI and Flaps instrument, well, I remembered that frame was smooth, and now I am fixing entire frame of the instrument...

[to be continued: note for myself #2: without some video there chances that anyone will understand are around 0]

PZL-Koliber-family

2023-09-03T15:25:50Z

SP-NTX:

{{infobox Aircraft
|name = PZL Koliber Family
|image = PZL-160A Koliber Development.png
|image2 = PZL-Koliber-160A-interior.png
|alt = PZL Koliber 160A in flight
|alt2 = PZL Koliber 160A cockpit
|type = Aerobatic aircraft//Civil aircraft/Civil trainer aircraft/Light aircraft/Light-sport aircraft
|config = Low wing aircraft/Monoplane aircraft
|propulsion = Piston aircraft/Propeller aircraft
|devel-hangar = https://github.com/SP-NTX/PZL-Koliber-family
|authors = jakkos98 (SP-KOS), SP-NTX, TheFGFSEagle (TheEagle), sryu1, Mariusz Migut (SP-MMA), Patrice Poly (WooT)
|status-fdm = 4
|status-systems = 2
|status-cockpit = 4
|status-model = 4
|fdm = JSBSIM
|license = GPLv2+
|download = https://github.com/SP-NTX/PZL-Koliber-family
}}
{{WIP}}
== About Koliber ==
The PZL-Koliber 160A is the last production version of the Polish PZL-110 Koliber series
developed on the basis of the SOCATA Rallye 100 ST license purchased by PZL in 1976, produced since 1979.
The PZL-Koliber 160A aircraft is a four-seat low-wing aircraft with a take-off weight of up to 950 kg, equipped with a 160 hp (120 kW) Lycoming O-320-D2A engine.
It was produced in the years 1997-2004 at PZL Okęcie in the number of 12 pieces, mainly exported to the USA.

== Updates ==

=== September 2023: ===

* Replaced AI with new one
* Changed Cabin Textures
[[File:PZL Koliber 160A - Old AI.png||left|thumb|PZL Koliber with old Attitude indicator]]
[[File:PZL Koliber 160A - New AI.png||center|thumb|New PZL Koliber Attitude Indicator]]
[[File:PZL Koliber 160A - Old Cabin.png|left|thumb|PZL Koliber 160A with old cabin (before updates)]]
[[File:PZL Koliber 160A New Cabin.png||center|thumb|PZL Koliber 160A New cabin textures and some things]]

PZL-Koliber-family

2023-09-03T15:25:24Z

SP-NTX:

{{infobox Aircraft
|name = PZL Koliber Family
|image = PZL-160A Koliber Development.png
|image2 = PZL-Koliber-160A-interior.png
|alt = PZL Koliber 160A in flight
|alt2 = PZL Koliber 160A cockpit
|type = Aerobatic aircraft//Civil aircraft/Civil trainer aircraft/Light aircraft/Light-sport aircraft
|config = Low wing aircraft/Monoplane aircraft
|propulsion = Piston aircraft/Propeller aircraft
|devel-hangar = https://github.com/SP-NTX/PZL-Koliber-family
|authors = jakkos98 (SP-KOS), SP-NTX, TheFGFSEagle (TheEagle), sryu1, Mariusz Migut (SP-MMA), Patrice Poly (WooT)
|status-fdm = 4
|status-systems = 2
|status-cockpit = 4
|status-model = 4
|fdm = JSBSIM
|license = GPLv2+
|download = https://github.com/SP-NTX/PZL-Koliber-family
}}
{{WIP}}
== About Koliber ==
The PZL-Koliber 160A is the last production version of the Polish PZL-110 Koliber series
developed on the basis of the SOCATA Rallye 100 ST license purchased by PZL in 1976, produced since 1979.
The PZL-Koliber 160A aircraft is a four-seat low-wing aircraft with a take-off weight of up to 950 kg, equipped with a 160 hp (120 kW) Lycoming O-320-D2A engine.
It was produced in the years 1997-2004 at PZL Okęcie in the number of 12 pieces, mainly exported to the USA.

== Updates ==
September 2023:
- Replaced AI with new one
- Changed Cabin Textures
[[File:PZL Koliber 160A - Old AI.png||left|thumb|PZL Koliber with old Attitude indicator]]
[[File:PZL Koliber 160A - New AI.png||center|thumb|New PZL Koliber Attitude Indicator]]
[[File:PZL Koliber 160A - Old Cabin.png|left|thumb|PZL Koliber 160A with old cabin (before updates)]]
[[File:PZL Koliber 160A New Cabin.png||center|thumb|PZL Koliber 160A New cabin textures and some things]]

File:PZL Koliber 160A New Cabin.png

2023-09-03T15:15:47Z

SP-NTX: Uploaded own work with UploadWizard

=={{int:filedesc}}==
{{Information
|description={{en|1=PZL Koliber 160A New cabin textures and some things}}
|date=2023-09-03
|source={{own}}
|author=[[User:SP-NTX|SP-NTX]]
|permission=
|other versions=
}}

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

File:PZL Koliber 160A - Old AI.png

2023-09-03T15:15:47Z

SP-NTX: Uploaded own work with UploadWizard

=={{int:filedesc}}==
{{Information
|description={{en|1=PZL Koliber with old Attitude indicator}}
|date=2023-09-03
|source={{own}}
|author=[[User:SP-NTX|SP-NTX]]
|permission=
|other versions=
}}

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

File:PZL Koliber 160A - Old Cabin.png

2023-09-03T15:15:47Z

SP-NTX: Uploaded own work with UploadWizard

=={{int:filedesc}}==
{{Information
|description={{en|1=PZL Koliber 160A with old cabin (before updates)}}
|date=2023-09-03
|source={{own}}
|author=[[User:SP-NTX|SP-NTX]]
|permission=
|other versions=
}}

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

File:PZL Koliber 160A - New AI.png

2023-09-03T15:15:47Z

SP-NTX: Uploaded own work with UploadWizard

=={{int:filedesc}}==
{{Information
|description={{en|1=New PZL Koliber Attitude Indicator}}
|date=2023-09-03
|source={{own}}
|author=[[User:SP-NTX|SP-NTX]]
|permission=
|other versions=
}}

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

FlightGear Newsletter September 2023

2023-09-03T15:02:50Z

SP-NTX:

{{User:Skybike/Template:Newsletter-header-translate|2023-09}}
{{TOC_right|limit=2}}
''We would like to emphasize that the monthly newsletter cannot live without the contributions of FlightGear users and developers. Everyone with a wiki account (free to register) is welcome to contribute to the newsletter. If you know about any FlightGear related news or projects such as for example updated scenery or aircraft, please do feel invited to add such news to the newsletter.''

''The new Visual Editor makes editing the wiki as simple as using a Word-processor, and even easier than using the forum as you don't even need to know the syntax for a url. Just hit the 'edit' link and start.''

==Development news==



=== Visual improvement for ROADS & RAILWAYS ===
The "roads.png" texture has been revised, now obtaining a smoother contrast in the visual integration of the roads to the terrain (the improvement is notable when applied to photorealistic scenarios created with JULIA and Photoscenary.jl)

The texture area dedicated to the railways has also been completely redesigned, correcting the scale a little and avoiding the repetition or "tiling" pattern of the tracks.

You can get this simple improvement directly by copying or downloading the "NEW roads.png" image texture that accompanies this article (it will need to be renamed "roads.png" and pasting it into the \Textures\osm2city folder on your FlighGear)

By Manuel ACE
[[File:NEW roads.PNG.png|center|thumb|NEW roads.png]]
[[File:NEW texture without railways tilling and runways more smoothly.jpg|center|thumb|1153x1153px|NEW texture without railways tilling and roads more smoothly]]
[[File:OLD texture with railway tilling and excesive contrast runways.jpg|center|thumb|637x637px|OLD texture with the tiling defect on railways and the roads with too much contrast.]]


==In the hangar==




=== [[PZL-Koliber-family|PZL Koliber Family]] updates ===

==== Cockpit updates: ====
Attitude Indicator replaced with new, more realistic 3D one.

Seats replaced by new, more realistic ones

Cabin interior textures replaced with new ones,

==== WIP: ====

* Changing cabin textures with livery
* Electrical System
* All cockpit instruments



==Scenery corner==
















==Help wanted==
{{Help wanted}}

==AI==


The AI team makes FlightGear more realistic, colorful and lively every month. You can support the development of ''Interactive Traffic'' and contribute at the FlightGear {{forum link|title=AI|f=23}}.



==Community news==







===FlightGear on Facebook===
Since early December 2010, FlightGear has an [https://www.facebook.com/FlightGear official Facebook page]. If you have a Facebook account please feel free to join the page.

===FlightGear on Instagram===
In January 2018 the [https://www.instagram.com/flightgear_sim/ @flightgear_sim Instagram account] was brought back to life. If you've got nice screenshots to be featured, feel free to {{forum link|text=contact the maintainer|t=33636}}.

===FlightGear on FlightSim.com===
FlightGear has also a [https://www.flightsim.com/vbfs/forumdisplay.php?102-FlightGear sub-forum] on flightsim.com - just like the commercial flight sims. It is an opportunity to showcase what FG can do, get people curious and answer any questions they may have with regard to the software or the project.

==Multiplayer events==









==Contributing==
===Translators needed===
{|
|[[File:en.gif]]
|The FlightGear Wiki still needs help for translating it into various languages. If you are interested in making the FlightGear Wiki multilingual, you can start by looking at [[Help:Translate]].
|-
|[[File:fr.gif]]
|Le wiki de FlightGear a toujours besoin d'aide pour être traduit en différentes langues. Si vous êtes intéressé par le rendre multilingue, commencez par lire [[:fr:Help:Traduire|Help:Traduire]].
|-
|[[File:de.gif]]
|Das FlightGear Wiki benötigt immer noch Hilfe bei der Übersetzung in verschiedene Sprachen. Wenn Du Interesse daran hast, das FlightGear Wiki mehrsprachig zu machen, dann fang mit dem [[:de:Help:Übersetzen|Help:Übersetzen]] an.
|-
|[[File:nl.gif]]
|De FlightGear Wiki kan nog steed hulp gebruiken bij het vertalen van artikelen. Als je interesse hebt om de wiki meertalig te maken, raden we je aan om een kijkje te nemen bij [[:nl:Help:Vertalen|Help:Vertalen]].
|-
|[[File:es.gif]]
|La wiki de FlightGear todavía necesita ayuda para traducirla a varios lenguajes. Si estás interesado en hacer la FlightGear wiki multilingüe, entonces comienza en [[:es:Help:Traducir|Help:Traducir]].
|-
|[[File:cat.gif]]
|La wiki de FlightGear encara necessita ajuda per traduir-la a diverses llengües. Si esteu interessat en fer la wiki de FlightGear multilingüe, llavors comenceu a [[:ca:Help:Traduir|Help:Traduir]].
|-
|[[File:pt.gif]]
|A wiki de FlightGear ainda necessita de ajuda para traduzi-la em vários idiomas. Se estás interessado em tornar a wiki de FlightGear multi-lingual, por favor começa em [[:pt:Help:Traduzir|Help:Traduzir]].
|-
|[[File:zh.gif]]
|FlightGear 百科仍然需要志愿者将其翻译为各种语言。如果你有兴趣让FlightGear百科支持更多语言, 你可以查看 [[Help:Translate]].
|}

===FlightGear logos===
If you want some graphic elements for your FlightGear-related site (such as a hangar or YouTube channel), please feel free to visit [[FlightGear logos]] for a repository of logos. And if you have some art skills, please don't hesitate to contribute with your own design creations.

===Screenshots===
The FlightGear project always needs screenshots, which show features that were added since the last release. These should be of good quality, especially in content and technical image properties. It is therefore recommended to use the best viable filter settings ([[anti-aliasing]], texture sharpening, etc.). More info at [[Howto:Make nice screenshots]].

====Screenshot of the Month====

If you want to participate in the screenshot contest, you can submit your candidate to the {{forum link|title=this|f=88|t=}}. Be sure to see the first post for participation rules. For purposes of convenience and organization, at the end of the month or after 20 entries have been submitted, a new forum topic will be started containing all shots in an easy-to-view layout. The voting will then take place there.

''Thanks for reading {{PAGENAME}}!''

{{Appendix}}


[[Category:Changes after 2020.3]]
[[Category:FlightGear Newsletter|2023 09]]

Discord

2023-02-22T00:41:03Z

SP-NTX:

'''Discord''' is used in the FlightGear community as an alternative to [[Mumble]], [[TeamSpeak]], [[FGCom]] or [[Ventrilo]].

Discord is a free voice and chat software that can be downloaded as an app or used in a browser.

== Invite links ==
{{note|1=Its advised that you create a permanent account, instead of creating guest accounts as some people create duplicate accounts which clogs up the member logs and makes it more difficult to @mention people.}}

Furthermore many other FlightGear servers exist that you may need an personal invite to join. The easiest way to find them is to go to the FlightGear server and ask or ask in forums.

== FlightGear Communities on Discord ==

=== General, Help and Support, Communities ===

{| class=wikitable
! Topic !! Invite link
|-
| FlightGear
| https://discord.gg/rzuV2DR
|-
| FlightGear FDM School
| https://discord.gg/Uyrtsar
|-
| FlightGear Air Race League
| https://discord.gg/HCAuU9D
|-
| FlightGear Virtual Alliance
| https://discord.gg/VqzTG2N
|-
| FG Events
| https://discord.gg/GY4N6Cu
|-
| FG FDM School
| https://discord.gg/U5KXyMU
|-
| FlightGear Republic, A friendly community about FlightGear.
| https://discord.gg/sBJy46Uq7z
|-
|FlightGear soaring club
|https://discord.gg/NvJjmzMfRP
|}

=== Military Aviation Communities ===

{| class=wikitable
! Topic !! Invite link
|-
| Operation Red Flag military FG community (OPRF)
| https://discord.gg/ptVapkE
|-
| Combined Joint Task Force 50 (OPRF event planning/hosting and more)
| https://discord.gg/2nxjb6y
|-
| Warbirds, WWII-era aircraft
| https://discord.gg/yJaP5Wn
|}

=== Country Specific Communities ===

{| class=wikitable
! Topic !! Invite link
|-
| FlightGear Australia (Scenery Development & Community)
| https://discord.gg/JzTEXsZ
|-
| FlightGear Italia (ITA Mercenaries)
| https://discord.gg/5RzyXRf
|-
| FlightGear Germany
| https://discord.gg/FNnpjCPSze
|-
| FlightGear Indian Community
| https://discord.gg/Tu7n5FmG5S
|-
| FlightGear Asia
| https://discord.gg/7saCkA2jQj
|-
| FlightGear Hong Kong
| https://discord.gg/9QVKcT6skU
|-
|FlightGear Myanmar
|https://discord.gg/VbT88KEGrk
|-
|FlightGear Poland (FlightGear Polska)
|https://discord.gg/5J7uVYRhZV
|}

=== Aircraft-specific ===
{| class=wikitable
! Aircraft !! Invite link
|-
| Aermacchi MB-339
| https://discord.gg/vNZ5ZPv
|-
| Airbus [[Airbus A320 Family|A320]] & A330 Development
| https://discord.gg/7kzg9Te
|-
| Airbus A350 Development
| https://discord.gg/vK5f2s6
|-
| Boeing F/A-18C Hornet
| https://discord.gg/8GzpdK4j8P
|-
| LincolnWorks (747 and A380)
| https://discord.gg/2DMVpnJ
|-
| F-111 Aardvark
| https://discord.gg/DSrSbmx
|-
| [[General Dynamics F-16 Fighting Falcon]]
| https://discord.gg/8RcYnjA
|-
| [[PZL-Koliber-family | PZL Koliber family]]
| https://discord.gg/beADn2sWM6
|-
| MD-11, MD-80, ITAF by Octal
| https://discord.gg/gxAhC3j
|-
| [[Mikoyan-Gurevich MiG-21bis]]
| https://discord.gg/bs8xyz3
|-
| [[Mirage 2000]]
| https://discord.gg/xZ3r2KR
|-
| Panavia Tornado
| https://discord.gg/26rvkr2
|-
| [[Saab 37 Viggen]]
| https://discord.gg/RJTwS9a
|-
| SEPECAT Jaguar
| https://discord.gg/G5q5XYN
|-
| FG-1000 Stealth Fighter
| https://discord.gg/3MFZauxyPW
|-
|Boeing 777
|https://discord.gg/8McTuYdK
|-
|A-10A Warthog
|https://discord.gg/RmtjmsT5vS
|-
|Soviet Aviation for FGFS
|https://discord.gg/YC2EYGK5Xf
|}

== External links ==
* https://discord.com/ Official website

[[de:Discord]]

[[Category:Software]]
[[Category:Community]]
[[Category:Air Traffic Control]]

WS3.0 Performance Testing

2023-01-31T11:40:32Z

SP-NTX:

This page is intended to collect data on users' systems to build a picture of what key properties are impacting performance with World Scenery 3.0.

For testing consistency, please use the following settings:

* UFO aircraft (to avoid the image of aircraft, Nasal etc)
* Use PNG WS3.0 scenery around KSFO
* osm2city building switched disabled (Terrasync contains some older version of osm2city buildings that have high occupancy and load time)
* Take-off from KSFO on heading 135 degrees at 3000ft and 1500 knots. This will take you over some of the built-up area of the Bay and then into the countryside.

== Database Pager Threads ==
/sim/rendering/database-pager/threads controls the number of threads that are used to load models and scenery. Most systems have multi-core processors, which having a larger number of threads can take advantage of. However, if the number of threads is too high, the system may become bottlenecked on I/O and swapping threads in and out.

The default setting is 4. Please record observations below.

{| class="wikitable"
|+/sim/rendering/database-pager/threads observations
!User
!CPU
!CPU Cores
!Memory (GB)
!GPU
!Observations
|-
|stuart
|Intel i7-4770
|4
|16
|NVidia GeForce GTX1660
|threads=2 - Obvious missing tiles.
threads=4 - some lag in loading tiles and stuttering

threads=8 - lag only around San Franscisco where there are a lot of roads. No problem in the countryside

threads=16 - No noticeably better than 8
|-
|SP-NTX
|Intel I5-6400
|4
|8
|NVidia GeForce GTX960
|threads=2 - Missing tiles, everything else was good till RAM was fully taken and system crashed
threads=4 - Lags, high RAM usage, no missing tiles, also crashed after 2 minutes

threads=8 -

threads=16 -
|-
|
|
|
|
|
|
|}

WS3.0 Performance Testing

2023-01-31T11:39:47Z

SP-NTX:

Discord

2022-09-26T18:29:03Z

SP-NTX: Added PZL Koliber dev.

'''Discord''' is used in the FlightGear community as an alternative to [[Mumble]], [[TeamSpeak]], [[FGCom]] or [[Ventrilo]].

Discord is a free voice and chat software that can be downloaded as an app or used in a browser.

== Invite links ==
{{note|1=Its advised that you create a permanent account, instead of creating guest accounts as some people create duplicate accounts which clogs up the member logs and makes it more difficult to @mention people.}}

Furthermore many other FlightGear servers exist that you may need an personal invite to join. The easiest way to find them is to go to the FlightGear server and ask or ask in forums.

== FlightGear Communities on Discord ==

=== General, Help and Support, Communities ===

{| class=wikitable
! Topic !! Invite link
|-
| FlightGear
| https://discord.gg/rzuV2DR
|-
| FlightGear FDM School
| https://discord.gg/Uyrtsar
|-
| FlightGear Air Race League
| https://discord.gg/HCAuU9D
|-
| FlightGear Virtual Alliance
| https://discord.gg/VqzTG2N
|-
| FG Events
| https://discord.gg/GY4N6Cu
|-
| FG FDM School
| https://discord.gg/U5KXyMU
|-
| FlightGear Republic, A friendly community about FlightGear.
| https://discord.gg/sBJy46Uq7z
|-
|FlightGear soaring club
|https://discord.gg/NvJjmzMfRP
|}

=== Military Aviation Communities ===

{| class=wikitable
! Topic !! Invite link
|-
| Operation Red Flag military FG community (OPRF)
| https://discord.gg/ptVapkE
|-
| Combined Joint Task Force 50 (OPRF event planning/hosting and more)
| https://discord.gg/2nxjb6y
|-
| Warbirds, WWII-era aircraft
| https://discord.gg/yJaP5Wn
|}

=== Country Specific Communities ===

{| class=wikitable
! Topic !! Invite link
|-
| FlightGear Australia (Scenery Development & Community)
| https://discord.gg/JzTEXsZ
|-
| FlightGear Italia (ITA Mercenaries)
| https://discord.gg/5RzyXRf
|-
| FlightGear Germany
| https://discord.gg/FNnpjCPSze
|-
| FlightGear Indian Community
| https://discord.gg/Tu7n5FmG5S
|-
| FlightGear Asia
| https://discord.gg/7saCkA2jQj
|-
| FlightGear Hong Kong
| https://discord.gg/9QVKcT6skU
|-
|FlightGear Myanmar
|https://discord.gg/VbT88KEGrk
|-
|FlightGear Poland (FlightGear Polska)
|https://discord.gg/gHEXsjB7b6
|}

=== Aircraft-specific ===
{| class=wikitable
! Aircraft !! Invite link
|-
| Aermacchi MB-339
| https://discord.gg/vNZ5ZPv
|-
| Airbus [[Airbus A320 Family|A320]] & A330 Development
| https://discord.gg/7kzg9Te
|-
| Airbus A350 Development
| https://discord.gg/vK5f2s6
|-
| Boeing F/A-18C Hornet
| https://discord.gg/8GzpdK4j8P
|-
| LincolnWorks (747 and A380)
| https://discord.gg/2DMVpnJ
|-
| F-111 Aardvark
| https://discord.gg/DSrSbmx
|-
| [[General Dynamics F-16 Fighting Falcon]]
| https://discord.gg/8RcYnjA
|-
| [[PZL-Koliber-family | PZL Koliber family]]
| https://discord.gg/beADn2sWM6
|-
| MD-11, MD-80, ITAF by Octal
| https://discord.gg/gxAhC3j
|-
| [[Mikoyan-Gurevich MiG-21bis]]
| https://discord.gg/bs8xyz3
|-
| [[Mirage 2000]]
| https://discord.gg/xZ3r2KR
|-
| Panavia Tornado
| https://discord.gg/26rvkr2
|-
| [[Saab 37 Viggen]]
| https://discord.gg/RJTwS9a
|-
| SEPECAT Jaguar
| https://discord.gg/G5q5XYN
|-
| FG-1000 Stealth Fighter
| https://discord.gg/3MFZauxyPW
|-
|Boeing 777
|https://discord.gg/8McTuYdK
|-
|A-10A Warthog
|https://discord.gg/RmtjmsT5vS
|}

== External links ==
* https://discord.com/ Official website

[[de:Discord]]

[[Category:Software]]
[[Category:Community]]
[[Category:Air Traffic Control]]

PZL-Koliber-family

2022-09-26T17:47:03Z

SP-NTX:

{{infobox Aircraft
|name = PZL Koliber Family
|image = PZL-160A Koliber Development.png
|image2 = PZL-Koliber-160A-interior.png
|alt = PZL Koliber 160A in flight
|alt2 = PZL Koliber 160A cockpit
|type = Aerobatic aircraft//Civil aircraft/Civil trainer aircraft/Light aircraft/Light-sport aircraft
|config = Low wing aircraft/Monoplane aircraft
|propulsion = Piston aircraft/Propeller aircraft
|devel-hangar = https://github.com/SP-NTX/PZL-Koliber-family
|authors = jakkos98 (SP-KOS), SP-NTX, TheFGFSEagle (TheEagle), Mariusz Migut (SP-MMA), Patrice Poly (WooT)
|status-fdm = 1
|status-systems = 2
|status-cockpit = 3
|status-model = 3
|fdm = JSBSIM
|license = GPLv2+
|download = https://github.com/SP-NTX/PZL-Koliber-family
}}
{{WIP}}
== About Koliber ==
The PZL-Koliber 160A is the last production version of the Polish PZL-110 Koliber series
developed on the basis of the SOCATA Rallye 100 ST license purchased by PZL in 1976, produced since 1979.
The PZL-Koliber 160A aircraft is a four-seat low-wing aircraft with a take-off weight of up to 950 kg, equipped with a 160 hp (120 kW) Lycoming O-320-D2A engine.
It was produced in the years 1997-2004 at PZL Okęcie in the number of 12 pieces, mainly exported to the USA.

File:PZL-160A Koliber Development.png

2022-09-26T17:45:34Z

SP-NTX: Uploaded own work with UploadWizard

=={{int:filedesc}}==
{{Information
|description={{en|1=PZL 160A Koliber in flight with some text under it}}
|date=2022-09-25
|source={{own}}
|author=[[User:SP-NTX|SP-NTX]]
|permission=
|other versions=
}}

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

PZL-Koliber-family

2022-09-19T15:53:21Z

SP-NTX: New aircraft

{{infobox Aircraft
|name = PZL Koliber Family
|image = PZL-Koliber-160A-on-ground.png
|image2 = PZL-Koliber-160A-interior.png
|alt = PZL Koliber 160A on ground
|alt2 = PZL Koliber 160A cockpit
|type = Aerobatic aircraft//Civil aircraft/Civil trainer aircraft/Light aircraft/Light-sport aircraft
|config = Low wing aircraft/Monoplane aircraft
|propulsion = Piston aircraft/Propeller aircraft
|devel-hangar = https://github.com/SP-NTX/PZL-Koliber-family
|authors = jakkos98 (SP-KOS), SP-NTX, TheFGFSEagle (TheEagle), Mariusz Migut (SP-MMA), Patrice Poly (WooT)
|status-fdm = 1
|status-systems = 2
|status-cockpit = 3
|status-model = 3
|fdm = JSBSIM
|license = GPLv2+
|download = https://github.com/SP-NTX/PZL-Koliber-family
}}
{{WIP}}
== About Koliber ==
The PZL-Koliber 160A is the last production version of the Polish PZL-110 Koliber series
developed on the basis of the SOCATA Rallye 100 ST license purchased by PZL in 1976, produced since 1979.
The PZL-Koliber 160A aircraft is a four-seat low-wing aircraft with a take-off weight of up to 950 kg, equipped with a 160 hp (120 kW) Lycoming O-320-D2A engine.
It was produced in the years 1997-2004 at PZL Okęcie in the number of 12 pieces, mainly exported to the USA.

File:PZL-Koliber-160A-interior.png

2022-09-19T15:32:33Z

SP-NTX: Uploaded own work with UploadWizard

=={{int:filedesc}}==
{{Information
|description={{en|1=PZL-110 Koliber 160A Cockpit panel}}
|date=2022-09-18
|source={{own}}
|author=[[User:SP-NTX|SP-NTX]]
|permission=
|other versions=
}}

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

File:PZL-Koliber-160A-on-ground.png

2022-09-19T15:32:33Z

SP-NTX: Uploaded own work with UploadWizard

=={{int:filedesc}}==
{{Information
|description={{en|1=PZL-110 Koliber 160A at EDLT}}
|date=2022-09-18
|source={{own}}
|author=[[User:SP-NTX|SP-NTX]]
|permission=
|other versions=
}}

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

Pl/Spolszczenie

2022-07-20T21:30:15Z

SP-NTX: a bit of changes

Obecnie FlightGear 2020.3.x umożliwia przetłumaczenie [[FlightGear Qt launcher|Launchera]] oraz menu górnego w symulatorze i te elementy mamy przetłumaczone na język polski. Jeśli u Ciebie elementy te nie wyświetlają się w wersji polskiej, to musisz uruchomić FlightGear z [[Pl/Opcje wiersza poleceń|opcją wiersza poleceń]] <code>--language=pl</code>.

Jednak wiele tekstów, np. w oknach dialogowych, wciąż pozostają na stałe wpisane w kod, dlatego nie ma obsługi przetłumaczenia ich i zawarcia w oficjalnym repozytorium. Dlatego wciąż pozostają w wersji angielskiej (domyślnej).

Jeśli nie zadowala Cię ten stan rzeczy, możesz pobrać dodatkowe spolszczenie z strony https://flightgear.org.pl/spolszczenia, które zawiera tłumaczenie pozostałych elementów GUI. Instalacja polega na podmianie oryginalnych plików z katalogu [[$FG_ROOT]], dlatego zalecane jest wykonanie kopii zapasowej tego katalogu, aby móc przywrócić oryginalną wersję.

'''UWAGA!''' Spolszczenie należy instalować tylko i wyłącznie dla wskazanej wersji FlightGeara. Instalacja dla różnych wersji grozi zepsuciem symulatora. Spolszczenie nie działa dla samolotów i dodatków, z powodu że nie są one zawarte w [[$FG_ROOT]].

== Poradniki na YouTube (2020.3.x)==
{{#ev:youtube|klxmL5_hF1U|480px||Poradnik na kanale SP-ROM, jak zainstalować spolszczenie/}}

Talk:Suggested aircraft

2022-06-04T18:07:25Z

SP-NTX:

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

== Goal of the page ==

Hi,

I'm not exactly sure what the goal of this page is. We definitely do not want to suggest the average FlightGear user to use a development repository to get their aircraft from with high risk of issues and bugs. Especially not in cases where the authors actively push releases to FGAddon when they reach a stable state (e.g., the Space Shuttle, c172 etc.). For those interested in finding the latest development version of an aircraft, each aircraft page on the wiki has (or can have) a "repository" link in the infobox behind this icon [[File:Preferences-system_32x32.png|16px]]. This makes me wonder what the added value of this page is in its current form?

Also note that linking to FGMembers is definitely a no-go [https://www.flightgear.org/fgmembers-statement/ per our statement].

[[User:Gijs|Gijs]] ([[User talk:Gijs|talk]]) 09:03, 31 May 2022 (UTC)

[[User:SP-NTX|SP-NTX]] ([[User talk:SP-NTX|talk]]) 18:14, 31 May 2022 (UTC) Yes, this have no sense of doing it. Well, suggesting aircrafts is nothing bad but someone should write why they are good, and not just spam links on possibly bugged version on usually FGLauncher ones. FGMembers ones need to be deleted, because fgmembers, i didn't wanted to deleted that fgmembers link that SidarDeha posted here, because i knew that there is no other version than FGmembers, so i wrote warning on start of the page. And yes, That what FGMembers did was not stupid, but they did it wrong. They maked one hangar with all aricrafts what can be added to launcher. But there are also license problems, especially for the FGMembers-nonGPL(what the hell is that). I think that page is not contributing anything to FG, may make some users experience bug with 3rd party aircrafts, and should be category of wiki pages with good aircrafts instead of few github links here

[[User:SP-NTX|SP-NTX]] ([[User talk:SP-NTX|talk]]) 18:07, 4 June 2022 (UTC) Also, adding something that you found on github, turned on and saw good cockpit is very bad thing. some aircrafts look nice, fly nice, and are unrealistic

Talk:Suggested aircraft

2022-06-04T18:07:12Z

SP-NTX:

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

== Goal of the page ==

Hi,

I'm not exactly sure what the goal of this page is. We definitely do not want to suggest the average FlightGear user to use a development repository to get their aircraft from with high risk of issues and bugs. Especially not in cases where the authors actively push releases to FGAddon when they reach a stable state (e.g., the Space Shuttle, c172 etc.). For those interested in finding the latest development version of an aircraft, each aircraft page on the wiki has (or can have) a "repository" link in the infobox behind this icon [[File:Preferences-system_32x32.png|16px]]. This makes me wonder what the added value of this page is in its current form?

Also note that linking to FGMembers is definitely a no-go [https://www.flightgear.org/fgmembers-statement/ per our statement].

[[User:Gijs|Gijs]] ([[User talk:Gijs|talk]]) 09:03, 31 May 2022 (UTC)

[[User:SP-NTX|SP-NTX]] ([[User talk:SP-NTX|talk]]) 18:14, 31 May 2022 (UTC) Yes, this have no sense of doing it. Well, suggesting aircrafts is nothing bad but someone should write why they are good, and not just spam links on possibly bugged version on usually FGLauncher ones. FGMembers ones need to be deleted, because fgmembers, i didn't wanted to deleted that fgmembers link that SidarDeha posted here, because i knew that there is no other version than FGmembers, so i wrote warning on start of the page. And yes, That what FGMembers did was not stupid, but they did it wrong. They maked one hangar with all aricrafts what can be added to launcher. But there are also license problems, especially for the FGMembers-nonGPL(what the hell is that). I think that page is not contributing anything to FG, may make some users experience bug with 3rd party aircrafts, and should be category of wiki pages with good aircrafts instead of few github links here
[[User:SP-NTX|SP-NTX]] ([[User talk:SP-NTX|talk]]) 18:07, 4 June 2022 (UTC) Also, adding something that you found on github, turned on and saw good cockpit is very bad thing. some aircrafts look nice, fly nice, and are unrealistic

Concorde

2022-05-31T18:19:29Z

SP-NTX: this was not about this model #2

{{:{{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.

== '''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-31T18:16:27Z

SP-NTX: this was not even about this aircraft

{{:{{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.

== 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]]

Talk:Suggested aircraft

2022-05-31T18:14:21Z

SP-NTX:

Talk:Suggested aircraft

2022-05-31T18:14:04Z

SP-NTX:

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

== Goal of the page ==

Hi,

I'm not exactly sure what the goal of this page is. We definitely do not want to suggest the average FlightGear user to use a development repository to get their aircraft from with high risk of issues and bugs. Especially not in cases where the authors actively push releases to FGAddon when they reach a stable state (e.g., the Space Shuttle, c172 etc.). For those interested in finding the latest development version of an aircraft, each aircraft page on the wiki has (or can have) a "repository" link in the infobox behind this icon [[File:Preferences-system_32x32.png|16px]]. This makes me wonder what the added value of this page is in its current form?

Also note that linking to FGMembers is definitely a no-go [https://www.flightgear.org/fgmembers-statement/ per our statement].

[[User:Gijs|Gijs]] ([[User talk:Gijs|talk]]) 09:03, 31 May 2022 (UTC)
[[User:SP-NTX|SP-NTX]] ([[User talk:SP-NTX|talk]]) 18:14, 31 May 2022 (UTC) Yes, this have no sense of doing it. Well, suggesting aircrafts is nothing bad but someone should write why they are good, and not just spam links on possibly bugged version on usually FGLauncher ones. FGMembers ones need to be deleted, because fgmembers, i didn't wanted to deleted that fgmembers link that SidarDeha posted here, because i knew that there is no other version than FGmembers, so i wrote warning on start of the page. And yes, That what FGMembers did was not stupid, but they did it wrong. They maked one hangar with all aricrafts what can be added to launcher. But there are also license problems, especially for the FGMembers-nonGPL(what the hell is that). I think that page is not contributing anything to FG, may make some users experience bug with 3rd party aircrafts, and should be category of wiki pages with good aircrafts instead of few github links here

Boeing 737NG

2022-05-29T14:17:38Z

SP-NTX:

{{:{{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.

Improved version can be downloaded from https://github.com/YV3399/737-800YV, but it includes only 737-800

== 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]]

Concorde

2022-05-29T14:15:42Z

SP-NTX:

{{:{{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.

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

== '''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
{{Note|Screenshots are possibly out-of-date and improved version has improved cockpit.}}

=== 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]]

Concorde

2022-05-29T14:14:06Z

SP-NTX:

{{:{{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.

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

== '''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.
{{Note|Screenshots are possibly out-of-date and improved version has improved cockpit.}}

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]]

Concorde

2022-05-29T14:13:19Z

SP-NTX:

{{:{{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.

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

== '''Panels & Instrumentation''' ==
{{Note|Screenshots are possibly out-of-date and improved version has improved cockpit.}}
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]]

Concorde

2022-05-29T14:11:56Z

SP-NTX:

{{:{{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.

{{Note|Improved version can be downloaded from https://github.com/FirstOfficerDelta/Concorde}}

{{Note|Screenshots are possibly out-of-date and improved version has improved 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]]

Istanbul Airport

2022-05-29T14:08:10Z

SP-NTX:

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

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

Şanlıurfa GAP Airport

2022-05-29T14:07:45Z

SP-NTX:

{{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 sceneries ==
https://github.com/TheFGFSEagle/LTCS-scenery

Dornier 328

2022-05-29T14:05:55Z

SP-NTX:

{{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!

This aircraft 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]]

Istanbul Airport

2022-05-29T14:04:08Z

SP-NTX:

{{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 can install it from https://github.com/Klaudiae/FGCompanion-TurkeyEnhanced

Talk:Suggested aircraft

2022-05-28T14:08:14Z

SP-NTX: Created page with "~~~~ Well, maybe someone should write WHY they are good, because only suggesting is not changing anything"

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

YouTube channels

2022-05-27T15:46:27Z

SP-NTX: Added few YT channells about FG that i know

'''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/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/UCexe4T0H9plEkiGY5njPGZg I make Videos]

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

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

User:SP-NTX

2022-05-21T20:47:03Z

SP-NTX:

User:SP-NTX

2022-05-21T20:38:16Z

SP-NTX: ctrl+c and ctrl+v-ing is not the best at all

User:SP-NTX

2022-05-21T20:33:12Z

SP-NTX: Small 'tutorial' about developing from my point of view

Addon

2022-05-21T11:17:48Z

SP-NTX:

[[File:Fgaddonslogo202x89.png|right]]
To make it easier to create '''addons''' there is since FlightGear 2017.3 a new way to create addons. In essence FlightGear will load an overlay XML into the property tree and start a well known Nasal function.<ref>{{cite web
|url = https://forum.flightgear.org/viewtopic.php?p=314620#p314620
|title = <nowiki> Re: New Feature: Addon - "API" </nowiki>
|author = <nowiki> Torsten </nowiki>
|date = Jul 19th, 2017
|added = Jul 19th, 2017
|script_version = 0.40
}}</ref>

We now have a simple way to add addons to FlightGear without the need to mess around with <code>FGData/Nasal</code> or <code>FGHome/Nasal</code> directories.<ref name="Forum_announcement">{{cite web
|url = https://forum.flightgear.org/viewtopic.php?p=314563#p314563
|title = <nowiki> New Feature: Addon - "API" </nowiki>
|author = <nowiki> Torsten </nowiki>
|date = Jul 18th, 2017
}}</ref>

{{TOC limit|3}}

== Installing and using an addon ==
Download and copy the addon to a directory on your computer.

If you use the launcher, select the Add-ons page from the icon bar on the left, then find the section Add-on Module folders and click the Add(+) button. Select the folder where you put the addon. Once the addon is shown in the list, make sure its check box is selected.

Use the command line switch <code>--addon=/path/to/some/addon</code>.<ref name="Forum_announcement"/>

== Creating an addon ==
There is a very simple Skeleton addon available in FGAddon to be used as a template.<ref name="Forum_announcement"/> See {{fgaddon source|path=Addons/Skeleton}}.

A leading slash (<code>/</code>) in this section indicates the base directory of the directory structure of the addon.

=== Minimum configuration ===
An addon may be installed in a directory anywhere on your hard disk and need at least two files:

* <code>/addon-config.xml</code> - A standard [[PropertyList XML files|PropertyList XML file]] to be used to populate or modify the [[property tree]]. (Same as to be used in <code>--config=foo.xml</code>)
* <code>/addon-main.nas</code> - The Nasal hook for the logic. This file needs a function called <code>main()</code> which will be called from the global addon initializer (<code>addons.nas</code>)

=== Additional common files ===
* <code>/addon-metadata.xml</code> - A PropertyList XML file with metadata about the addon it.
* <code>/addon-menubar-items.xml</code> - A PropertyList XML file describing menus to be added to the FlightGear menu bar.
* <code>/gui/dialogs/<my-foobar-dialog>.xml</code> - PropertyList XML files to create custom dialogs.

=== Good to know ===
The new addon mechanism lets you add a <code>addon-config.xml</code> to override the settings in <code>defaults.xml</code> and other files.

That will allow an addon to
* Override key bindings (as in the spoken ATC addon)
* Add or override autopilots and property rules
* Introduce XML state machines

Unless your really want to add/change/remove those at runtime, this should cater for most use cases.<ref>{{cite web
|url = https://forum.flightgear.org/viewtopic.php?p=314902#p314902
|title = <nowiki> Re: Spoken </nowiki>
|author = <nowiki> Torsten </nowiki>
|date = Jul 23rd, 2017
|added = Jul 23rd, 2017
|script_version = 0.40
}}</ref>

We have some instructions how to use SVN [[FGAddon|in our wiki]]. It covers mostly aircraft development but the workflow is pretty much the same for addons.<ref>{{cite web
|url = https://forum.flightgear.org/viewtopic.php?p=314647#p314647
|title = <nowiki> Re: Spoken ATC </nowiki>
|author = <nowiki> Torsten </nowiki>
|date = Jul 19th, 2017
|added = Jul 19th, 2017
|script_version = 0.40
}}</ref>

== Addon initialization ==
On initialization fgfs takes care of:
* Through {{flightgear source|path=src/Main/options.cxx|text=<code>options.cxx</code>}}:<ref name="Forum_announcement"/>
** Creating a property under <code>/addons/addon[n]/path=/path/to/some/addon</code>
** Loading <code>/path/to/some/addon/addon-config.xml</code> into the property tree (same as <code>--config=/path/to/some/addon/addon-config.xml</code>)
** Adding <code>/path/to/some/addon</code> to the list of allowed directories (same as <code>--fg-aircraft=/path/to/some/addon</code>)
* Through {{fgdata source|path=Nasal/addons.nas|text=<code>addons.nas</code>}}:
** Loading <code>/foo/bar/baz/addon-main.nas</code> into namespace <code>__addon[ADDON_ID]__</code>
** Calling <code>main(addonGhost)</code> from <code>/foo/bar/baz/addon-main.nas</code>.

== APIs ==
{{hatnote|For more details about these APIs, see the readme file, {{readme file|add-ons}}.}}
=== C++ API ===
There is a C++ API on FlightGear's side that handle some on the addon related tasks manly through the <code>AddonManager()</code>, <code>Addon()</code> and <code>AddonVersion()</code> classes.

=== Nasal API ===
The Nasal add-on API lives in the 'addons' namespace and can for example do queries to <code>AddonManager()</code> and read data from <code>addons.Addon</code> objects. It can for example compare addon versions if there is dependencies.

== Background ==
{{See also|Howto:Creating a simple modding framework}}

ATC chatter was removed in 2015, see fgdata commit: [https://sourceforge.net/p/flightgear/fgdata/ci/81607f734e13add9be02816ddaec305d05bc4e47/ 81607f734e13add9be02816ddaec305d05bc4e47]

And the devel list messages referenced in the commit log.
the other relevant commit is this: b60736ba7add2a7cd39af3d8a974d5be3ea46e8b
It would not be very difficult to restore this functionality, or even generalize/improve it significantly (which was the scope of the original discussion on the devel list)<ref>{{cite web
|url = https://forum.flightgear.org/viewtopic.php?p=288388#p288388
|title = <nowiki> Re: Whatever happened to radom radio </nowiki>
|author = <nowiki> Hooray </nowiki>
|date = Jun 11th, 2016
|added = Jun 11th, 2016
|script_version = 0.40
}}</ref>

The restored functionality could be distributed as a tarball that is extracted into $FG_ROOT - alternatively, into $FG_HOME, because Nasal files there are treated as overlays, which basically means that you can install user-specific extensions there without having to tamper with $FG_ROOT, it would only take very minor changes to turn the chatter feature into a corresponding "addon" - not unlike fgcamera ...<ref>{{cite web
|url = https://forum.flightgear.org/viewtopic.php?p=288392#p288392
|title = <nowiki> Re: Whatever happened to radom radio </nowiki>
|author = <nowiki> Hooray </nowiki>
|date = Jun 11th, 2016
|added = Jun 11th, 2016
|script_version = 0.40
}}</ref>

We should absolutely stop telling anyone to edit preferences.xml in FG_ROOT; any documentation or advice which says to should be changes ASAP. <ref>{{cite web
|url = https://forum.flightgear.org/viewtopic.php?p=192632#p192632
|title = <nowiki> Re: NavCache:init failed:Sqlite error:Sqlite API abuse </nowiki>
|author = <nowiki> zakalawe </nowiki>
|date = Oct 26th, 2013
|added = Oct 26th, 2013
|script_version = 0.40
}}</ref>

As of 12/2017, the addon API is in the process of being significantly updated <ref>https://sourceforge.net/p/flightgear/mailman/message/36146017/</ref> <ref>https://sourceforge.net/p/flightgear/mailman/message/36150159/</ref> <ref>https://sourceforge.net/p/flightgear/mailman/message/36150444/</ref>

== List of Addons ==
You can find the official repository at {{fgaddon source|path=Addons}}

* [https://github.com/slawekmikula/flightgear-addon-hudheli Additional Heli HUD's] - ([https://github.com/slawekmikula/flightgear-addon-hudheli/blob/master/doc/manual.md manual]) - encapsulation of HeliHUD package as an addon
* [https://github.com/SP-NTX/AnotherGUI AnotherGUI] - An add-on that adds a new GUI style.
* ATC Chatter (ported by Torsten) {{progressbar|100}}
* [[Cargo Towing Addon]] <ref>{{cite web
|url = https://forum.flightgear.org/viewtopic.php?t=36824
|title = <nowiki> Re: Cargo Towing Addon </nowiki>
|author = <nowiki> Wayne Bragg (wlbragg) </nowiki>
|date =
|added =
|script_version = 0.40
}}</ref>
* cockpit-view (work in progress by wkitty42)<ref>{{cite web
|url = https://forum.flightgear.org/viewtopic.php?p=316498#p316498
|title = <nowiki> Re: </nowiki>
|author = <nowiki> wkitty42 </nowiki>
|date = Aug 13th, 2017
|added = Aug 13th, 2017
|script_version = 0.40
}}</ref>
* [[Earthview#Customization]] - High resolution customization
* [[FaceTrackNoIR]] (ported by HHS)<ref>{{cite web
|url = https://sourceforge.net/p/flightgear/mailman/message/36454826/
|title = <nowiki> Re: </nowiki>
|author = <nowiki> Unknown, HHS</nowiki>
|date = Nov 1th, 2018
}}</ref> - An addon to interface this [[Head tracking|head tracker]] with FlightGear
* [https://forum.flightgear.org/viewtopic.php?f=5&t=24792 Fencemaker] (Eases creating Fence-like scenery objects. Originally by VaLeo, converted to an addon by sfr) - ([https://www.mediafire.com/file/cf0la63v9g352md/fencemaker_addon.zip/file download])<ref>{{cite web
|url = https://forum.flightgear.org/viewtopic.php?f=5&t=24792&start=45#p390066
|title = <nowiki> Re: </nowiki>
|author = <nowiki> Stefan Frank </nowiki>
|maintainer = <nowiki> Stefan Frank </nowiki>
|date = Aug 8th, 2021
}}</ref>
* [https://github.com/slawekmikula/flightgear-addon-fgcamera FGCamera] - ([https://github.com/slawekmikula/flightgear-addon-fgcamera/blob/master/Docs/manual.md manual]) - [[FGCamera | Wiki Page]]
* [[FGPlot]]
* [[Ground Services]] (ported by ThomasS)<ref>{{cite web
|url = https://forum.flightgear.org/viewtopic.php?p=316400#p316400
|title = <nowiki> Re: </nowiki>
|author = <nowiki> ThomasS </nowiki>
|date = Aug 12th, 2017
|added = Aug 12th, 2017
|script_version = 0.40
}}</ref>
* {{fgaddon source|path=Addons/Headtracker/|text=Headtracker addon}} Helps integrate FaceTrackNoIR and opentrack with FlightGear.
* [https://github.com/tdammers/fg-hoppie-acars Hoppie ACARS client] - connect to [http://www.hoppie.nl/acars Hoppie's ACARS], used on VATSIM and other networks.
* [https://github.com/slawekmikula/flightgear-addon-protocolkml KML Exporter (Google Earth)] - ([https://github.com/slawekmikula/flightgear-addon-protocolkml/blob/master/doc/manual.md manual])
* [[Landing Rate addon]] [https://forum.flightgear.org/viewtopic.php?f=6&t=33101&p=327787#p327787]
* [https://github.com/slawekmikula/flightgear-addon-linuxtrack LinuxTrack Head Tracker integration] - ([https://github.com/slawekmikula/flightgear-addon-linuxtrack/blob/master/doc/manual.md manual])
* [https://github.com/slawekmikula/flightgear-addon-littlenavmap LittleNavMap integration] - ([https://github.com/slawekmikula/flightgear-addon-littlenavmap/blob/master/doc/manual.md manual])
* [https://gitlab.com/mdanil/flightgear-hax mdanilov hax!]: landing evaluation and aircraft development tools, TerraSync toggler
* [[Model Cockpit View]]
* [https://github.com/SP-NTX/MPChatImprovments MPChatImprovments] Multi-key commands for Multiplayer, new features for chat,...
* [[Oscilloscope addon]] - Allows displaying a property of Nasal function over time
* [[PAR instrument]] - Precision Approach Radar and Ground Controlled Approach
* [[Red Griffin ATC]] - Speaking Air Traffic Controller<ref>{{cite web
|url = https://forum.flightgear.org/viewtopic.php?f=6&t=36755
|title = <nowiki> Re: </nowiki>
|author = <nowiki> RedGriffin </nowiki>
|date = Jan 6th, 2020
|added = Jan 6th, 2020
|script_version = 1.0.0 RC2
}}</ref>
* [https://github.com/tdammers/fg-simbrief-addon SimBrief import] - Import flightplans, weights, fuel, and winds alof, from SimBrief.
* [[Spoken ATC]] (ported by Torsten)<ref>{{cite web
|url = https://forum.flightgear.org/viewtopic.php?p=314095#p314095
|title = <nowiki> Re: </nowiki>
|author = <nowiki> Torsten </nowiki>
|date = Jul 10th, 2017
|added = Jul 10th, 2017
|script_version = 0.40
}}</ref>
* [[Spoken GCA]] - An offline ground controlled approach (GCA) addon
* [https://gitlab.com/mdanil/flightgear-mickey Tiny HUD for mouse flying in FlightGear] - Visual feedback for mouse flying, to make up for mouse's lack of self-centering
* [https://github.com/slawekmikula/flightgear-addon-vfrflight VFRFlight integration] - ([https://github.com/slawekmikula/flightgear-addon-vfrflight/blob/master/doc/manual.md manual])
* [https://github.com/slawekmikula/flightgear-addon-vfrnavigator VFR Flying Helper] - ([https://github.com/slawekmikula/flightgear-addon-vfrnavigator/blob/master/doc/usage.md manual])
* [[YASim Development Tools]] (by jsb)
* [https://github.com/hbeni/fgfs-noGroundDamage noGroundDamage] - Addon to temporarily disable damage after landing and for ground operations for the c172/c182

== Experimental Addons ==

Addons which are in the development stage/unfinished but can be used as a quick view of addon functionality
* [https://github.com/slawekmikula/flightgear-addon-missions FlightGear Missions addon] - Add-on for missions/adventures code

== Ideas ==
=== Hooking into features using legacy OpenGL code ===
{{See also|Unifying the 2D rendering backend via canvas}}
In 09/2018, James suggested that legacy features using raw OpenGL calls (e.g. HUD/2D panels) could be easily replaced via scripted Canvas/Nasal solutions at the mere cost of providing a mechanism to hook into the legacy code implementing these features (namely, the HUD/instrumentation subsystems) <ref>https://sourceforge.net/p/flightgear/mailman/message/36399261/</ref> <ref>https://sourceforge.net/p/flightgear/mailman/message/36399261/</ref>

=== Catalog & Package Manager support ===
if this works with more complex, pre-existing addons such as [[Bombable]], where the file layout is a replica of the old FGData layout, these types of mature addons might be better as SourceForge FlightGear sub-projects rather than being copied into FGAddon. Maybe the config file and nasal script could be used to automate the installation process ?<ref>{{cite web
|url = https://sourceforge.net/p/flightgear/mailman/message/35953179/
|title = <nowiki> Re: [Flightgear-devel] Simple API for creating FlightGear
addons/plugins </nowiki>
|author = <nowiki> Edward d'Auvergne </nowiki>
|date = Jul 19th, 2017
|added = Jul 19th, 2017
|script_version = 0.40
}}</ref>
The [[Bombable]] addon is one of the most popular addons out there, and a large number of aircraft in FGAddon have bombable support, so it is worth not forgetting about. Especially if the addon system one day becomes automated through a [[Catalog metadata|catalog.xml type system]]<ref>{{cite web
|url = https://sourceforge.net/p/flightgear/mailman/message/35953650/
|title = <nowiki> Re: [Flightgear-devel] Simple API for creating FlightGear
addons/plugins </nowiki>
|author = <nowiki> Edward d'Auvergne </nowiki>
|date = Jul 19th, 2017
|added = Jul 19th, 2017
|script_version = 0.40
}}</ref>

== References ==
{{Appendix}}

== Related content ==
=== Wiki articles ===
* [[FG Add-on FAQ]]
* [[FlightGear configuration via XML]]
* [[FlightGear configuration via XML#preferences.xml]]
* [[Nasal]]
* [[Property tree]]
* [[Properties persistent between sessions]]
* [[PropertyList XML File]]

=== Forum topics ===
* {{forum link|t=32561|title=New Feature: Addon - "API"}}

=== Readme files ===
* {{readme file|add-ons}}
* {{readme file|gui}} - Details on how to add menus and custom dialogs.

=== Source code ===
==== FGAddon ====
* {{fgaddon source|path=Addons/Skeleton}} - Skeleton addon to be used as a template.

==== FGData ====
* {{fgdata source|path=Nasal/addons.nas}}

==== FlightGear ====
* {{flightgear source|path=src/Main/options.cxx}}
* {{flightgear source|path=src/Add-ons/}}

[[Category:FlightGear addons| ]]

Howto:Add multi-key commands to an aircraft

2022-05-18T18:18:22Z

SP-NTX:

[[File:FlightGear vi-like commands on-screen help.png|thumb|The on-screen help for the multi-key commands.]]
This tutorial will guide you through '''how to add multi-key commands to an aircraft''' and how they work.

The [[multi-key commands]] are vi-like key sequences that begin with {{key press|:}} and is followed by other keys.

== Define the multi-key commands ==
* Begin the aircraft-specific sequences with {{key press|:}}{{key press|A}}.

* If for example an instrument have many bindings, begin its sequences with {{key press|:}}{{key press|A}} and a uppercase letter specific for that instrument followed by the rest of the sequence.

=== The multikey.xml file ===
The multi-key commands are defined in a [[PropertyList XML files|property-list xml file]], named for example <code>aircraft-multikey.xml</code>.

<syntaxhighlight lang="xml">
<?xml version="1.0" encoding="UTF-8"?>



<PropertyList>

<key n="65"> 
<name>A</name>
<desc>Aircraft</desc> 



</key>

</PropertyList>
</syntaxhighlight>

=== Syntax ===
The syntax builds up like a tree where the leaf nodes have bindings.

==== Non-leaf nodes ====
<syntaxhighlight lang="xml">
<key n="n"> 
<name><name> 
<desc></desc> 

<key n="n"> 

</key>

<key n="n"> 

</key>



</key>
</syntaxhighlight>

==== Leaf nodes ====
<syntaxhighlight lang="xml">
<key n="n"> 
<name><name> 
<desc></desc> 
<exit/> 
<binding> 

</binding>
<binding> 

</binding>
</key>
</syntaxhighlight>

==== Key codes ====
:''See [[Howto:Reassign keyboard keys#Finding keycodes]].''

==== Name and description ====
It is a very good idea to use the key name and a short but meaningful description as those are used by the multi-key command on-screen help dialog (when it is toggled on with {{key press|:}}{{key press|Tab}}).

==== Bindings ====
The bindings uses the same syntax as described in [[Bindings]] and [[Howto:Reassign keyboard keys#Adding or modifying key assignments]].

== Include the commands into the aircraft-set.xml file ==
Add this line to the <code>[[aircraft-set.xml]]</code> file:

<syntaxhighlight lang="xml">


<input>
<keyboard n="0">
<multikey include="aircraft-multikey.xml"/> 


</keyboard>
</input>


</syntaxhighlight>

== Technical details ==
{{stub|section=1}}
Among the nasal files in <code>$FGDATA/Nasal</code> that are loaded when FlightGear starts is <code>multikey.nas</code> that will load a number of Nasal functions. The keyboard configuration file <code>$FGDATA/keyboard.xml</code> will call <code>multikey.start()</code> when the {{key press|:}} key is used.

== Related content ==
=== Wiki articles ===
* [[Aircraft-set.xml]]
* [[Bindings]]
* [[Multi-key commands]]
* [[Howto:Reassign keyboard keys]]

=== Source code ===
==== fgdata files ====
* {{fgdata source|path=keyboard.xml|line=634|pre=$FG_ROOT}} Lines 634-641 of the keyboard configuration file delegates handling to multikey.start()
* {{fgdata source|path=Nasal/multikey.nas|pre=$FG_ROOT}} The global Nasal multi-key handler.

==== F-14B files ====
These are a good example of how one can do.
* {{fgaddon source|path=Aircraft/f-14b/f-14-common.xml|line=1367|pre=$FG_AIRCRAFT}} Line 1367 delegates the handling to Systems/instruments-multikey.xml.
* {{fgaddon source|path=Aircraft/f-14b/Systems/instruments-multikey.xml|pre=$FG_AIRCRAFT}}

[[Category:Aircraft enhancement]]
[[Category:Howto]]
[[Category:FlightGear keyboard]]