FlightGear wiki - User contributions [en]

OpenRadarFeatureWishlist

2013-02-12T17:12:52Z

Stepfaw: /* General */ Grammar

[[OpenRadar| Back to mainpage]]

This page collects the feature proposals for [[OpenRadar]].

== General ==

* Callsign greater than 7 characters, cannot even have ICAO_TWR as callsign. Would like at least 10 (comment ww: The flightgear MP protocol supports only 7 chars (max. 7 chars plus trailing zero equals 8 bytes, see [[Multiplayer protocol]])
* Inter ATC communication. Some method of talk/text just between ATC controllers would be nice, to coordinate handovers (ww: yes, but as much as I know they use mumble right now...)
* Make it not working at FG's [[KSFO|default airport]] (to guard against heart attacks on trying-to-be-KSFO-police people). ww: We are living in a free world of free software. Its like forbidding aircrafts at an airport. I have seen pilots missing all decency and mad ATC guys. We cannot lock them out without creating a closed environment... No, that is not the way it should be done... If someone wants to disturb he still can use aircrafts or the different ATC-models out there...

== RadarMap ==
* show more ground detail (data source?)
* separation rings
* alerts for collision and speed violations
* an alarm for when new aircraft enter the area so that when you are busy doing something else while waiting for someone to come into your area you will be notified

== RadarContact handling ==

== FGCom Integration ==
* Remove CTRL as PTT button, clashes with CTRL-Left click for "neglect", suggest Right Shift (ww: but the right hand is occupied with the mouse. maybe we move the neglected key to the right SHIFT)
* Add "set PTT button" feature

== ATC Coordination ==
* coordinate multiple instances of OpenRadar using a protocol a la VatSim (ww: this will work only for OpenRadar instances, not to ATC-ML, ATC-TOWER etc...)

[[Category:OpenRadar|FeatureWishlist]]

OpenRadarFeatureWishlist

2013-02-12T17:11:09Z

Stepfaw: added suggestion for alarm

[[OpenRadar| Back to mainpage]]

This page collects the feature proposals for [[OpenRadar]].

== General ==

* Callsign greater than 7 characters, cannot even have ICAO_TWR as callsign. Would like at least 10 (comment ww: The flightgear MP protocol supports only 7 chars (max. 7 chars plus trailing zero equals 8 bytes, see [[Multiplayer protocol]])
* Inter ATC communication. Some method of talk/text just between ATC controllers would be nice, to coordinate handovers (ww: yes, but as much as I know they use mumble right now...)
* Make it not working at FG's [[KSFO|default airport]] (to guard against heart attacks on trying-to-be-KSFO-police people). ww: We are living in a free world of free software. Its like forbidding aircrafts at an airport. I have seen pilots missing all decency and mad ATC guys. We cannot lock them out without creating an closed environment... No, that is not the way it should be done... If someone wants to disturb he still can use aircrafts or the different ATC-models out there...

== RadarMap ==
* show more ground detail (data source?)
* separation rings
* alerts for collision and speed violations
* an alarm for when new aircraft enter the area so that when you are busy doing something else while waiting for someone to come into your area you will be notified

== RadarContact handling ==

== FGCom Integration ==
* Remove CTRL as PTT button, clashes with CTRL-Left click for "neglect", suggest Right Shift (ww: but the right hand is occupied with the mouse. maybe we move the neglected key to the right SHIFT)
* Add "set PTT button" feature

== ATC Coordination ==
* coordinate multiple instances of OpenRadar using a protocol a la VatSim (ww: this will work only for OpenRadar instances, not to ATC-ML, ATC-TOWER etc...)

[[Category:OpenRadar|FeatureWishlist]]

ATC at EDDF

2013-02-10T03:53:44Z

Stepfaw: Gramar

For quite a while now, there has been regular ATC sessions at [[EDDF]], hosted by the user Jomo who also acts as TC.

== Considerations for users ==
Please only join the ATC training if you wish to participate and have at least basic knowledge of English and ATC procedures.
Everybody - of course - is welcome to the sessions and the users are all willing to help a new user, but just flying around
uncontrolled while people try to accomplish serious training, is not very polite. 
During EDDF-ATC we communicate basically in English (and hopefully more and more over [[FGCOM]]!).
On request (or when we deem it necessary) we can provide the basic ATC-Commands also in writing for: German, French, Spanish,
Polish, Portuguese, and hopefully soon for more and more languages! (Sorry: But you still have to reply in "something like English"!). 
It is our major goal to train Pilots to use FGCOM (in English) and learn to follow basic Flying-Rules! 
Please do not use Mpserver02, that server is overloaded most of the time and does not react fast enough for ATC-Controlling. 
Never start-up on Runways! Set Startpos e.g. for EDDF in cmd-line or wizard: --parkpos= B42..48, or A10..25, etc. For all parkinglots available see the parking plan. 

== Initial procedure ==
When inbound EDDF: Please contact ATC from about 60 mi outside. 
Maximum Speed below 10000 ft is 250 kts. 
Maximum Taxi-Speed is 30 kts 

== ATC times ==
Currently, ATC at EDDF is available on 
Wednesday,Friday, Saturday and Sunday 
From 17:00 - 21:00 UTC (DST does NOT apply)

== References / more information ==
* [http://www.emmerich-j.de/S0.html General EDDF-ATC information on Jomo's website]
* [http://www.emmerich-j.de/FGFS/EDDF-PARK.zip EDDF parking plan and other documents]

== More Airports regularly providing ATC ==
* [[Konrad Adenauer Airport|Köln Bonn Airport]]
* [[Leipzig/Halle Airport]]
* Luxembourg Airport
* [[Warsaw Chopin Airport]]

[[Category:Air Traffic Control]]

OpenRadarGuide

2013-02-07T20:27:17Z

Stepfaw: /* Operating */ Note for bug that minimizes screen at start up on OSX

[[OpenRadar| Back to mainpage]]
=='''''Preface'''''==
[[OpenRadar]] is a prototype to support Flight-Simulator ATCs in their work on our airports.
 
Some words to our project targets:
* '''Realism:''' That means we show all the data a real live ATC would need. For instance we simulate a radar antenna and perform one position update per antenna rotation. But we don't have professional ATCs, neither do we have professional pilots contacting our ATCs. So we have to make some compromises...
* '''Usability:''' The application should be handy, behave consistently, and require almost no training. The ATC has other things to do than to fight with the application

We hope that we met your needs and are happy to get feedback!

'''Important:''' We support you with tooltip texts, that appear when you hover over an active area with your mouse. They shall remind you of possible interactions that you may have forgotten. Try pointing your mouse everywhere - maybe there is something available that you missed until now...
 
----
=='''''Prerequisites'''''==
===Internet===
Of course you need an uninterrupted Internet access to exchange data between You and your clients/targets. The requirements for that connection are not very high -- but they must be uninterrupted!

===Communication / FGCOM===
We urge you to always offer your services as well in typing (MPchat) as also in speaking (FGcom).
*'''MPchat''' is an integral part of OpenRadar and needs no further installations. (ref.: http://wiki.flightgear.org/Howto:Multiplayer )
*But '''FGcom''' is a standard application which must be installed in addition.

You will soon discover, that FGcom makes it much easier to communicate
*as well for you ''(who hopefully will control many pilots at the same time)''
*as also for the pilots ''(who need both hands to control their plane)''.
For both of them there will be not enough time for typing!
 
If FGCOM is not yet installed, see:
:*For Windows and Linux: http://code.google.com/p/fgcomgui/
:*For OSX: We do not know of a standalone installation source - but we do know that starting with version 2.0.0 the FGFS-OSX-version does contain the FGCom. That fits and works for OSX >= 10.5.
:In addition you may inform yourself about FGCOM on:
:{| class="wikitable"
|-
|for general infos||http://wiki.flightgear.org/FGCom
|-
|for more detailed informations||http://wiki.flightgear.org/FGCOM_for_Windows
|-
|if you have problems with FGCOM||http://wiki.flightgear.org/FGCOM_Testing
|}

===Java V7===
Make sure you have installed at least Version 7 of Java. Verify and or Download the installation packages from: http://www.java.com/en/download/index.jsp

===OpenRadar===
For the currently available Prototype of OpenRadar see http://wagnerw.de/OpenRadar.zip. Extract the content of this ZIP to a place where it is easy to find. Make sure you have read and write permissions for that directory.
 
If you did already work with an OpenRadar installation you may want to
* RENAME your current OpenRadar-directory (i.e. to "OpenRadar-BU")
* then download and extract the new version into a newly created directory with the name of the old one (without the "-BU")
* now you can replace all data in the new "OpenRadar/data" directory with the ones in the "OpenRadar-BU/data"
** if you expect changes in the scenery etc. do not copy the the Airport (ICAO) directories
* delete the BU-version only after you are sure you verified that all your personal data were transferred, i.e. still accessible!
 
----
== '''''Startup''''' ==
Inside the downloaded OpenRadar base-directory you will find start-scripts. See
*for Windows: OpenRadar.bat
*for Linux: OpenRadar.sh
*for OSX: OpenRadar.jar
At Startup you will always be welcomed by the “OpenRadar – Welcome”. That window presents 2 TABs to define your preferences:
{|
|-
|[[File:OpenRadar - Welcome-Linux.png|thumb|left|Welcome tab on Linux]]||
[[File:OpenRadar- Settings-linux.png|thumb|left|Settings tab on Linux]]
|}
For all data there are standard values given as defaults. If you do change any values, they will be saved and presented to you during the next start.
 
If this is the very first time you start OpenRader, then you have to verify your “Settings” first, thus click onto the “Settings”-tab:

=== OpenRadar-Welcome - Settings ===
These settings are grouped into 3 parts:
===='''1) FGcom'''====
:OpenRadar can support up to 4 instances of FGcom in 2 ways:
:#It can start and control FgCom instances that operate in the background as sub-tasks of OpenRadar (except for OSX where FgCom must be run in a separate Terminal window)
:#or just control manually started FgCom-sessions.

:You select these modes of operation by the “'''FgComMode'''” selection:
 
:'''a) Internal:''' FGCom(s) are started and controlled internally by OpenRadar
::For this mode you have to define all available fields to tell OpenRader where your FGcom resides and what options shall be used:
::'''Path:''' Here you define where your FGcom is installed.
:::In the following some examples:

:::{| class="wikitable" style="text-align:center"
!type
!Windows
!Linux
!OSX
|-
|a standard installation || C:\Programs\FGcom ||/home/''YourName''/fgcom ||*)
|-
|on another disk || D:\FlighGear_2.6\FGcom || /media/''DiskName''/FGFS/fgcom ||*)
|-
|on a LAN-server || \\''ServerName''\Central\FGFS || /home/YourName//.gvfs/fgfs on nas-server/fgcom||*)
|}
::::'''*) for OSX this does not apply because you will be starting FgCom in a Terminal window before starting OpenRadar'''
::'''Executable:''' Here you define the program-name that shall be started

:::*For Windows: "fgcom.exe" or "anyName.bat"
:::*for Linux: "fgcom" or "anyName.sh"
:::*OSX: ''again for OSX this doe not apply''

::'''Server:''' There are 2 FGcom-servers available as of today:
::*delta384.server4you.de ''(we do suggest this one)''
::*fgcom.flightgear.org.uk
::'''Client:''' will always be “localhost” - unless you want to run FGcom on a different PC than OpenRadar.
::'''FGcom Ports:''' The here defined values are crucial for the operation because:
::*They are the only connection between the OpenRadar and FGcom. So you must define those the same in OpenRadar as well as in FGcom !!
::*They also define how many “Radio Units” (COM0, COM1, etc.) are generated within OpenRadar
::Simply provide a coma separated list of UDP Ports to be used by FGcom. But be warned: More than two are hard to handle!
:::::e.g. 16661,16662
 
:'''b) External:''' OpenRadar controls a manually started instance of FGcom - via the defined Port.
::For this one you only need to define where that FGcom is running and what the connecting port is. e.g.:
::*'''Client:''' locahost
::*'''FGcom Ports:''' 16661,16662 ''(if e.g. 2 FGcom instances were started)''
 
:'''c) OFF:''' No FGcom support
::That means that You do not want to work with FGcom during your ATC-session – thus you do not need to define any of the fields and there will not be defined any Radio (e.g. COM0) in OpenRadar. This mode is not suggested!

===='''2) FG Multiplayer'''====
:Here you find the server and connection port of FlightGears multiplayer server. It delivers the radar contact position informations and is used for chat. You won't have to change the settings, as long as the server won't change.
:In case you experience problems with the outside you may check and/or choose any "'''''Server'''''" that is listed in http://mpmap01.flightgear.org/mpstatus/: Look for a server nearest to your location that has a status of "OK" and shows the most "totals".
:'''''PLEASE NOTE:''''' The "'''''Client port'''''" is the port used by your computer to talk with that server. If you want to use FlightGears internal chat parallel to OpenRadar, you must use a different port than FlightGear. Because of that, the default port of OpenRadar is 5001 ''(in order to differentiate it to the 5000 used in FGFS)''.

===='''3) METAR'''====
:OpenRadar retrieves the weather information via METAR messages from a server in the INTERNET. This information is being displayed and used to calculate the usability of runways and the air speed of the radar contacts.
:If your airport is too small to be in that worldwide list, you can provide the code of another bigger airport with METAR data nearby in the sector.property file. But be aware that then your customers weather-settings may differ to yours, because they may use the standard FGFS-METAR-Source!

Please click on the verify button to have your settings checked!

===Select Airport===
This is always the first window that you will see after starting OpenRadar.
 

But at first, the available airport list (e.g. EDDF, KOAK,..) in the center will be empty. So at first define a location:
 

In order to '''define a new work-location''' simply enter the airport code (ICAO) or a part of the name into the search field and hit “search”: The list below then shows the results found in the airport database delivered with OpenRadar. There may be found several, so click on the one wanted and then activate the button "Download Scenery". Be patient and watch the Info-Field at the bottom: This first download of the required scenery will take some time before you see a "Ready"!
 

'''If the airport wanted does already exist''', it will be shown in the big center-field, with an "(exists)" at the end.
Double click onto the one wanted (or select it with one click and then click onto start) and you are in the ATC seat.
 
----

== '''''Operating''''' ==
[[File:OpenRadar Prototype.png|thumb|270px|Oakland international used in new OpenRadar]]
'''Note: As of this version when the main screen starts in OSX it is completely minimized at the bottom left corner of the screen and you must expand this window.'''

The OpenRadar main screen is divided into three regions:
#Top left you see the big '''Radar Map''' showing the airport, its surrounding, the navaids and the radar targets.
#Below it, bottom left, you see the '''MPchat Area''' for the FlightGear multiplayer chat feature.
#On the right side you see the '''Service Area''' with 4 subparts. From top to bottom those are
##'''Status Information'''
##'''COM-Radios''' ''(only if you have defined one or more)''
##'''Runway Manager''' to set up runways used
##the '''Flight Strip Manager''', where you can manage your radar targets.
Please notice in the following description the lightblue background at some items, indicating changes that may not yet be available in your version of the OpenRadar!

==== Radar Map ====
The radar map is the most complex part of OpenRadar, thus you have many options to zoom in on any area you are interested in. You can:
* set four functional zoom levels by clicking onto '''''GROUND, TOWER, APP and SECTOR.'''''
* zoom in and out using your mouse wheel ''(Mac: hold your right mousebutton pushed while moving over the radar-background in NorthWest respectively SouthEast)''
* adjust the map-center by dragging it with your mouse (click-hold left and drag)

* a double mouse-click onto the scope will move that point into the center of the scope
* a double right mouse-click will center the scope back to your location

You may assign any current settings to any of the 4 zoom levels (GROUND, TOWER, APP and SECTOR) by a right mouse-click onto the wanted level''
 
[[File:OpenRadar-Approach.png|thumb|right|250px|A typical tower operation]]
The '''''Radar-targets'''''
*do have a label attached with the following informations
:{| class="wikitable" style="text-align:center"
|-
|UID||heading direction
|-
|Flight Level||Airspeed
|}
*and are displayed in 5 different colors:
::''(See also the chapter "Flight Strip Manager")''
:{| class="wikitable"
|-
|align="center"|white||always the currently selected target, it's UID is also shown in the MPchat inputline (e.g. see "D-Leon" who just is getting his "clear to land")
|-
|align="middle"|blue||targets who's Flight-Stripe is placed to the left (e.g. see "Side" (just started) and "D-AHGM" just going to intercept the ILS: These 2 PLUS the white "D-LEON" are actively controlled right then!)
|-
|align="center"|yellow||targets who's Flight-Stripe is placed in the middle (e.g. could be assigned to "jomo2" as an indication that we wait for him to "wake up" soon - because then he may become a danger to others when taxiing uncontrolled)
|-
|align="center"|green||targets who's Flight-Stripe is placed to the right (e.g. see "jomo2" just parking - not actively controlled right now)
|-
|align="center"|gray||a neglected target or one for which there were no refresh data received from the MPserver for some time. In those cases the aircraft-type will be replaced by either "neglected" or by the time that elapsed since the last MPserver-update.
|}

[[File:OpenRadar-GND.png|thumb|right|250px|A GND layout with active PPN's]]
The radar map has so many details to display, that it is impossible to display all at once. Because of that we display details depending on the zoom level. For instance we hide Fixes and/or Runway Numbers etc. at a certain level of zoom. Thus OpenRadar features an adaptive detail level. In addition you can hide types of data by the following buttons:
{| class="wikitable"
|-
| '''''FIX''''' || Show/NoShow FIX's (they will automatically be set "NoShow" above distinct scale-settings!)
|-
| '''''NDB''''' || Show/NoShow NDB's (they will automatically be set "NoShow" above distinct scale-settings!)
|-
| '''''VOR''''' || Show/NoShow VOR's
|-
| '''''APT''''' || Show/NoShow Airports, inclusive their groundlayout (You may double-click onto a wanted airport and zoom in to see the layout)
|-
| '''''CIRC''''' || Show/NoShow circles at distinct distances around your present location. The distance between the circles shown depends on the chosen zoom-factor!
|-
| '''''GSH''''' || Show/NoShow Glide-Slope-Heights along the centerline of the runway for landings. They will automatically be set "NoShow" above distinct scale-settings!)
|-
| '''''PPN''''' || Show/NoShow the "Park Position Numbers", ''those may not yet be available on all airports!''. The PPNs will automatically be set "NoShow" above distinct scale-settings!)
|- style="background:lightblue"
| '''''StP''''' || Show/NoShow the "Selected (target) To Pointer" ''(doggy)'', an attachment to the mousepointer, showing some data about the relation of the selected target to the location of the mouse-pointer (similar to line 3 in the "Status Informations", see above)
|}

The "Runway Manager" (on the right side of the screen) allows you to define which runway(s) should be used for landing and/or starting. This status is shown with little green/red dots at the runway end. See in the picture "A typical tower operation" above:
*25L, 25R, and 18 are active (see the green and red dots at the ends)
*25L has in addition the blue approach center line and funnel, i.e. it is assigned for landings. This center line is drawn out for 100mi, helping you to align the arriving airplanes with the runway. In addition there is shown some kind of a funnel in a definable distance that may help you to align the planes coming via a base-leg for landing.

==== MPchat area ====
[[File:OpenRadar-MPchat.png|thumb|right|270px|The MPchat area]]
This area allows you to enter chat messages, view the chat history and filter it.
 
In the '''''entry-line''''' atop you define your messages to any radar-target by:
*Manually typing a message:
**A '''''left''''' mouse-click onto a Flight-Stripe or onto a Radar-Target will place the Target-UID at the beginning of the entry-line
**Then you may type or copy/past anything behind that - and send it out by ENTER
*Generate a standard message:
**A '''''right''''' mouse-click onto a Flight-Stripe or onto a Radar-Target will open a list with the available messages - select one with a left mouse-click
**That will place the message into the entry-line - you may now review/edit it and then send it out by ENTER
*OpenRadar will always set the ATC-name (as it appears on the very top of the service area - see the following chapter) in front of the message.

Below that entry-line is the '''''scrollable list''''' of exchanged MPchat-messages. In that list the messages related to the selected target are colored cyan. With the button "'''''SEL'''''" you set a filter to show only the messages related to the selected target. This filter will be reset as soon as you select another target - or by clicking onto "'''''ALL'''''".

You may enlarge that area by grabbing the upper edge with the left mouse-button and move it upward. Of course that will reduce the size of the radar-screen -- so use it with care!

==== Service Area ====
This column at the right side of the screen is for setting up the base-data for the operation, display needed data for traffic-guidance, and provide tools for guiding the pilots.

=====Status Informations=====
[[File:OpenRadar-Status_2.png|thumb|right|200px|The general Status Informations]]
This area shows in 4 lines the most used status-informations:
<ol><li>A text box that allows you to see and change your MP-callsign. So you can quickly change it, if a second ATC takes another role at the same airport (TW/APP/GND/RADAR, etc). At the right of it is placed a clock with the UTC-time. Because you probably will always have international guests you should refer to that modern "Coordinated Universal Time" (replacing nowadays the formerly used "Greenwich Mean Time" (GMT))
</li><li>In the second line you see the ICAO (the international Code for airports) and the long name of your airport. In addition you see on the right the currently selected radar contact (e.g. "jomo").
</li><li>The third line lets you predict several values for that "radar contact" (e.g. "jomo"). Whenever you place your mousepointer somewhere on the Radar Map, the third line will give you several informations about that target:
*StP = "Selection to Pointer": That is the compass direction between the target and the mousepointer, in both ways (TO/FROM)
*Miles: The distance between the target and the mouspointer.
*min: The time the target needs to get to that mousepointed area - '''IF''' the speed remains steady as is!! In this example there is given a "n/a" (not available) which most probably means the plane is not moving (may be parked)!
</li><li>The fourth line shows the mostly needed weather information '''Wind''', '''Pressure''' and '''Visibility'''. If you hover your mouse over it, you can see the complete last METAR-message received, in it's original form. (For help ref to http://wiki.flightgear.org/METAR#METAR). Please note that these values are similar to ATIS information: METAR directions is given in TRUE, ATIS in magnetic...
</li></ol>
====='''COM-Radios'''=====
[[File:OpenRadar-COM_2.png|thumb|right|200px|The COM-Setting (that can be none or up to 4)]]
According to the amount of FGcom-Ports you defined during setup (compare chapter "3.1.1 FGcom") you find here as many COM-Units (COM0 to max COM3). Each of them has a PopUp-List of Radio-frequencies available for the airport you are located on. You may
*choose a frequency out of the list by clicking onto the arrow at the right of the input-field
*or empty the field by a right mouseclick and enter any other frequency wanted.
At the right of that field you find a "Push To Talk" (PTT) button that you can operate by mouseclick -- or you can use the shortcuts given in the following table.
:{| class="wikitable" style="text-align:center"
!COMx
!left on keyboard
!right on keyboard
|-
|COM0||Ctrl||NumOff+Num0
|-
|COM1||SHIFT||NumOff+Num1
|-
|COM2|| ||NumOff+Num2
|-
|COM3|| ||NumOff+Num7
|}
Please watch the color change of the PTT buttons to know, when you can speak.

In case you operate the FGcom in the "'''''controlled by OpenRadar'''''" mode (compare the "FGComMode" in chapter "Startup"), then
*the radio label turns to red when FGcom is unable to establish a connection on this frequency. (Remember: OpenRadar has more frequencies available than FGcom knows of!!)
*you have an additional "'''''Restart'''''"-button: In case the communication becomes chopped or interrupted, you may click here to restart the FGCOM-program.
 
====='''Runway Settings'''=====
[[File:OpenRadar-Runways_2.png|thumb|right|200px|The Runway Manager]]
[[File:OpenRadar-Runway-Settings.png|thumb|right|200px|The Runway Manager Settings]]
Here you define the major variables for your airport operations: That are the assignments of the runways! For this purpose OpenRadar gives you a lot of precalculated and or default values to support your decisions findings and/or informations pilots may ask you about. See e.g. the pictures on the right:
*From top to bottom OpenRadar lists all runways available for that airport. For each runway you may define unique operating/display values. For these values see the picture "OpenRadar-Runway-Settings" below, e.g. see the 07C ''(you open that by a right mouseclick onto the runway-name (07C))'':
**In the header line you see left the now chosen runway to be edited, and at the left a button "'''''Copy to All'''''". With this switch you can copy the settings you make here to all the other runways - so e.g. for EDDF with its 8 settings you can save a lot! Only the values will be changed - all the selection-markers will remain as are in each unique setting table! These settings will then be saved separately for each unique airport in you private settings.
**With "'''''Main switches'''''" you define which functions may be available for that runway. Usually you can define for each runway as well a "Starting" as also a "Landing" function. In the given example for EDDF there is a complication: Per Law you are forbidden
:::to use runway 36 at all --> thus disable both lines: All data for that runway disappear
:::to use runway 18 for "Landing" only --> thus disable only "Landing": Just the Land-Option disappears
:::''(How do you know those details? Well, as a good ATC you prepare yourself by reading the official airport data (or look for something like e.g. http://en.wikipedia.org/wiki/Frankfurt_Airport, see on that page in the right column)''.
:*The "'''''Extended center line'''''" is the line you see in the above picture ''"A typical tower operation"'' at the right. If you want that line you may define how long it should be. Some people do not want it reaching over the whole screen. We suggest to limit it to the MPserver-range of 100 mi. It will only be visible for the runways defined for "Landing"!
:*The "'''''Distance markers'''''" are measurement markers on that "Extended center line". Here you define from were to were you want to have such markers ''(they may restrain your eyes if you use them all over!)''.
:*"'''''Vectoring and base leg'''''" define that funnel that you also see in the above picture ''"A typical tower operation"''. Also this will be shown only for the "Landing" runways.
:One tip to the handling of the "Landing" runways: Those are always shown in the "ATIS" message. If you define two (or even more) - in that "ATIS" message appear all those with the ILS data, etc.! So if you use mainly one we suggest to define only one - and activate more if you actually assign an additional one. Otherwise the pilots may become confused of that many informations and you yourself may have problems to differentiate which line the target should follow!

*From left to right you see the following informations for each runway (if available):
:*The runway-name
:*Check-boxes to define if that runway is used at all, may be just for landings or just for starts or for both. The program prevents you from assigning a runway in both directions (e.g. 25R and 07L)
:*A graphical display of the cross winds and and gusts: They are green from 0-5kn, orange 5-10kn and red above. When there are significant gusts that color-bar is divided into two. Typically the gusts then will be represented by the longer bar!
:*Above that bar you see the fractions of head- and crosswind. You may use especially the crosswind-fraction to warn pilots if those are => 10 kn! (Remember: You find the normal wind values in the METAR-data further up in the Status Informations)
:*To the right follows
::*in the upper line the exact runway heading (as needed for older type autopilots)
::*in the lower line the length and width of the runway in feet!
:*Then follow the ILS informations, if ILS is available for that runway. The data shown are: the ILS-beacon-name, the frequency, the glideslope, and the altitude at the threshold.

====='''Flight Strip Manager'''=====
[[File:OpenRadar-Stripes.png|thumb|right|200px|Handling the Flight-Stripes]]
Paper Flight Strips are the ATCs help to coordinate his traffic. In reality those strips contain many details about the flight, that we do not have (yet). Based on vertical space-limitations we have gathered the most critical informations into 2 lines, which are automatically initiated and controlled by the program. Those are:
:{| class="wikitable" style="text-align:center"
|-
|Target UID||Aircraft Type||colspan="2"|direction to it from ATC
|-
|distance to it||IAS+GND speed||Altitude (FL)||current heading
|}
In addition the user may add some more informations in additional lines. We urge you to reduce these additional lines to a minimum, because already with 2 lines the list will become that long, that you must scroll constantly! These additional lines will be saved as target-data and inserted each time a new stripe is created for that target! We suggest to maintain some target-data and some flight data for all frequent visitors. See as a suggestion several 3rd line examples:

"ILS VOR FGC NRW || GED MTR"
 This pilot knows how to use ILS, VOR, FGcom, the new Runway at EDDF || he is advised to approach via VOR GED and MTR.

"ILS VOR FGC NRW || KJFK 280° f510"
 This pilot also can use ILS, VOR, FGcom, NRW || and will depart to JFK on a straight course of 280° on FL510"

You are absolutely free to define your own codes and whatever. To do so
*enter/edit those data by opening the "'''''Note Editor'''''" with a right mouse-click ''(Mac: Alt + right mouse-click)'' while pressing onto the stripe
*add additional lines by Strg+ENTER (remember: Not more than 2, please!)
*Always exit that Editor with the ENTER-key in order to transfer the data to the stripe!
*At the bottom of this editor you can also select in which '''''additional language''''' the "standard commands" shall be transmitted to that target.

You can '''''manipulate the listing''''' of the flight strips:
*New radar-targets will always appear at the end of the list on the right side
*You can move the stripes in vertical order by drag and drop
*You can place them in three horizontal columns (left, middle and right) either by dragging them with the hold-down mouse button or by mouse-clicks left or right of the stripes ''(you may double-click to move directly from one side to the other)''
*with the "'''''AUTO'''''"-button at the upper edge of this area you can define that the stripes will be sorted automatically into groups according to their left/center/right position. This may be very irritating at first - so you may want to switch that "AUTO" off at first usages!
*The radar-targets will change their color according to the horizontal position of their stripe:
**the radar-targets for stripes at the right side will be '''green''' - these are all targets when initialized!
**the radar-targets for stripes in the center will be '''yellow'''
**the radar-targets for stripes at the left side will be '''cyan'''
On the radar-map the "cyan targets" will overlay the "yellow targets" - and the "yellow targets" will overlay the "green" ones!
 
You cannot change these combinations of color and position -- but you might define your own definition of what the positions mean! We suggest the following:
:'''''green''''' = right = initial position: Means not yet defined or not under my control (e.g. passing through on high altitude, is controlled by another ATC, etc.)
:'''''yellow''''' = center = I expect him to get under my control when in range (e.g. 60 mi), or he may be transfered to me by another ATC soon, etc. He may become a danger to the traffic controlled by me if he continues uncontrolled!
:'''''cyan''''' = left = under my control (light cyan when active in the MPchat input-line!)
Again: That is a proposal - you can define your on assignments!

You can apply the following mouse-actions onto the stripes as well as onto the radar-targets:
*a '''''single left''''' mouse-click '''''selects/activates''''' it, i.e. its radar-target becomes "light cyan" and its UID is set into the MPchat input-line. In addition
**its listed messages in the MPchat-list become colored cyan
**and the "doggy" at the mouse-pointer displays data about the relation between that target and the mouse-pointer
*a '''''double left''''' mouse-click helps you to find the target by highlighting the target on the scope. It also changes the radar-range to show both: The Target and your location. The selection of any of the "preset zoom levels" (GROUND, TOWER, APP, Sector) will reset the map-position again to its center!
*a '''''center''''' mouse-click opens the '''''Note Editor''''' (see above)
*a '''''right''''' mouse-click shows the dialog to choose pre-defined ATC messages to be sent to the current contact
*a '''''CTRL+left''''' mouse-click will define that target as '''''neglected'''''. Thus his radar-target will become just a light gray color, that will not overlay or otherwise disturb the radar-views.
 
----

== '''''Useful Features''''' ==
'''Radar Map'''
* On contact
:* '''left''' click '''selects''' and sets cursor into the chat input field
:* '''middle''' click opens the radar '''contact settings''' (ATC note and native language)
:* '''right''' click opens the '''ATC messages''' selection box

* '''left double''' click on map to '''center''' it '''on airport''' (return to airport)
* middle click on zoom level defines the current view as new center and zoom setting (stored in a file)
* a click on the texts, on the lower left, toggle display of FIX, NDB, VOR,...

'''Flight Strip Area'''
* On flight strip
:* '''left''' click '''selects''' the contact and sets cursor into the chat input field
:* '''middle''' click opens the radar '''contact settings''' (ATC note and native language)
:* '''right''' click opens the '''ATC messages''' selection box 

:* '''left double''' click '''centers''' radar '''map on''' the '''contact''' (to find contact)
:* '''CTRL+left''' click sets the contact to be '''neglected'''

* a click beside the flight strips moves the flight strips between the three columns (right, middle, left)

'''Runway area'''
* '''right''' click '''on runway number''' opens the '''runway settings dialog''' to define the centerline and vectoring settings
* If at least one runway is active you may '''double click''' the runway panel '''background to hide the inactive runways''' (frees space for flight strips)

'''Radios'''
* a '''right''' click '''on the frequency list''' changes the input to be '''editable''', so you can define the frequencies by yourself

''' Shortcuts '''
{| class="wikitable"
|-
! Shortcut !! Action
|-
| '''ESC''' || Close all open dialogs and cancel the text input (reset chat input field)

|-
| ALT + L || Toggle FGCom Log Window (only if you run FgCom started by OpenRadar)

|-
| '''Left CTRL''' || PTT Radio COM0 (if it has been activated via Port in Settings)
|-
| NUM off: Num0 || PTT Radio COM0 (if it has been activated via Port in Settings)
|-
| '''Left SHIFT''' || PTT Radio COM1 (if it has been activated via Port in Settings)
|-
| NUM off: Num1 || PTT Radio COM1 (if it has been activated via Port in Settings)
|-
| NUM off: Num2 || PTT Radio COM2 (if it has been activated via Port in Settings)
|-
| NUM off: Num3 || PTT Radio COM3 (if it has been activated via Port in Settings)
|}
 
----
== '''''Acknowledgments''''' ==
This project was founded and driven by Ralf Gerlich. Still today he is supporting it as a mentor.

And not to be forgotten: This project links different efforts of many people together. Thank you for your great work!

[[Category:OpenRadar|Guide]]

OpenRadarGuide

2013-02-07T20:17:24Z

Stepfaw: /* 1) FGcom */

[[OpenRadar| Back to mainpage]]
=='''''Preface'''''==
[[OpenRadar]] is a prototype to support Flight-Simulator ATCs in their work on our airports.
 
Some words to our project targets:
* '''Realism:''' That means we show all the data a real live ATC would need. For instance we simulate a radar antenna and perform one position update per antenna rotation. But we don't have professional ATCs, neither do we have professional pilots contacting our ATCs. So we have to make some compromises...
* '''Usability:''' The application should be handy, behave consistently, and require almost no training. The ATC has other things to do than to fight with the application

We hope that we met your needs and are happy to get feedback!

'''Important:''' We support you with tooltip texts, that appear when you hover over an active area with your mouse. They shall remind you of possible interactions that you may have forgotten. Try pointing your mouse everywhere - maybe there is something available that you missed until now...
 
----
=='''''Prerequisites'''''==
===Internet===
Of course you need an uninterrupted Internet access to exchange data between You and your clients/targets. The requirements for that connection are not very high -- but they must be uninterrupted!

===Communication / FGCOM===
We urge you to always offer your services as well in typing (MPchat) as also in speaking (FGcom).
*'''MPchat''' is an integral part of OpenRadar and needs no further installations. (ref.: http://wiki.flightgear.org/Howto:Multiplayer )
*But '''FGcom''' is a standard application which must be installed in addition.

You will soon discover, that FGcom makes it much easier to communicate
*as well for you ''(who hopefully will control many pilots at the same time)''
*as also for the pilots ''(who need both hands to control their plane)''.
For both of them there will be not enough time for typing!
 
If FGCOM is not yet installed, see:
:*For Windows and Linux: http://code.google.com/p/fgcomgui/
:*For OSX: We do not know of a standalone installation source - but we do know that starting with version 2.0.0 the FGFS-OSX-version does contain the FGCom. That fits and works for OSX >= 10.5.
:In addition you may inform yourself about FGCOM on:
:{| class="wikitable"
|-
|for general infos||http://wiki.flightgear.org/FGCom
|-
|for more detailed informations||http://wiki.flightgear.org/FGCOM_for_Windows
|-
|if you have problems with FGCOM||http://wiki.flightgear.org/FGCOM_Testing
|}

===Java V7===
Make sure you have installed at least Version 7 of Java. Verify and or Download the installation packages from: http://www.java.com/en/download/index.jsp

===OpenRadar===
For the currently available Prototype of OpenRadar see http://wagnerw.de/OpenRadar.zip. Extract the content of this ZIP to a place where it is easy to find. Make sure you have read and write permissions for that directory.
 
If you did already work with an OpenRadar installation you may want to
* RENAME your current OpenRadar-directory (i.e. to "OpenRadar-BU")
* then download and extract the new version into a newly created directory with the name of the old one (without the "-BU")
* now you can replace all data in the new "OpenRadar/data" directory with the ones in the "OpenRadar-BU/data"
** if you expect changes in the scenery etc. do not copy the the Airport (ICAO) directories
* delete the BU-version only after you are sure you verified that all your personal data were transferred, i.e. still accessible!
 
----
== '''''Startup''''' ==
Inside the downloaded OpenRadar base-directory you will find start-scripts. See
*for Windows: OpenRadar.bat
*for Linux: OpenRadar.sh
*for OSX: OpenRadar.jar
At Startup you will always be welcomed by the “OpenRadar – Welcome”. That window presents 2 TABs to define your preferences:
{|
|-
|[[File:OpenRadar - Welcome-Linux.png|thumb|left|Welcome tab on Linux]]||
[[File:OpenRadar- Settings-linux.png|thumb|left|Settings tab on Linux]]
|}
For all data there are standard values given as defaults. If you do change any values, they will be saved and presented to you during the next start.
 
If this is the very first time you start OpenRader, then you have to verify your “Settings” first, thus click onto the “Settings”-tab:

=== OpenRadar-Welcome - Settings ===
These settings are grouped into 3 parts:
===='''1) FGcom'''====
:OpenRadar can support up to 4 instances of FGcom in 2 ways:
:#It can start and control FgCom instances that operate in the background as sub-tasks of OpenRadar (except for OSX where FgCom must be run in a separate Terminal window)
:#or just control manually started FgCom-sessions.

:You select these modes of operation by the “'''FgComMode'''” selection:
 
:'''a) Internal:''' FGCom(s) are started and controlled internally by OpenRadar
::For this mode you have to define all available fields to tell OpenRader where your FGcom resides and what options shall be used:
::'''Path:''' Here you define where your FGcom is installed.
:::In the following some examples:

:::{| class="wikitable" style="text-align:center"
!type
!Windows
!Linux
!OSX
|-
|a standard installation || C:\Programs\FGcom ||/home/''YourName''/fgcom ||*)
|-
|on another disk || D:\FlighGear_2.6\FGcom || /media/''DiskName''/FGFS/fgcom ||*)
|-
|on a LAN-server || \\''ServerName''\Central\FGFS || /home/YourName//.gvfs/fgfs on nas-server/fgcom||*)
|}
::::'''*) for OSX this does not apply because you will be starting FgCom in a Terminal window before starting OpenRadar'''
::'''Executable:''' Here you define the program-name that shall be started

:::*For Windows: "fgcom.exe" or "anyName.bat"
:::*for Linux: "fgcom" or "anyName.sh"
:::*OSX: ''again for OSX this doe not apply''

::'''Server:''' There are 2 FGcom-servers available as of today:
::*delta384.server4you.de ''(we do suggest this one)''
::*fgcom.flightgear.org.uk
::'''Client:''' will always be “localhost” - unless you want to run FGcom on a different PC than OpenRadar.
::'''FGcom Ports:''' The here defined values are crucial for the operation because:
::*They are the only connection between the OpenRadar and FGcom. So you must define those the same in OpenRadar as well as in FGcom !!
::*They also define how many “Radio Units” (COM0, COM1, etc.) are generated within OpenRadar
::Simply provide a coma separated list of UDP Ports to be used by FGcom. But be warned: More than two are hard to handle!
:::::e.g. 16661,16662
 
:'''b) External:''' OpenRadar controls a manually started instance of FGcom - via the defined Port.
::For this one you only need to define where that FGcom is running and what the connecting port is. e.g.:
::*'''Client:''' locahost
::*'''FGcom Ports:''' 16661,16662 ''(if e.g. 2 FGcom instances were started)''
 
:'''c) OFF:''' No FGcom support
::That means that You do not want to work with FGcom during your ATC-session – thus you do not need to define any of the fields and there will not be defined any Radio (e.g. COM0) in OpenRadar. This mode is not suggested!

===='''2) FG Multiplayer'''====
:Here you find the server and connection port of FlightGears multiplayer server. It delivers the radar contact position informations and is used for chat. You won't have to change the settings, as long as the server won't change.
:In case you experience problems with the outside you may check and/or choose any "'''''Server'''''" that is listed in http://mpmap01.flightgear.org/mpstatus/: Look for a server nearest to your location that has a status of "OK" and shows the most "totals".
:'''''PLEASE NOTE:''''' The "'''''Client port'''''" is the port used by your computer to talk with that server. If you want to use FlightGears internal chat parallel to OpenRadar, you must use a different port than FlightGear. Because of that, the default port of OpenRadar is 5001 ''(in order to differentiate it to the 5000 used in FGFS)''.

===='''3) METAR'''====
:OpenRadar retrieves the weather information via METAR messages from a server in the INTERNET. This information is being displayed and used to calculate the usability of runways and the air speed of the radar contacts.
:If your airport is too small to be in that worldwide list, you can provide the code of another bigger airport with METAR data nearby in the sector.property file. But be aware that then your customers weather-settings may differ to yours, because they may use the standard FGFS-METAR-Source!

Please click on the verify button to have your settings checked!

===Select Airport===
This is always the first window that you will see after starting OpenRadar.
 

But at first, the available airport list (e.g. EDDF, KOAK,..) in the center will be empty. So at first define a location:
 

In order to '''define a new work-location''' simply enter the airport code (ICAO) or a part of the name into the search field and hit “search”: The list below then shows the results found in the airport database delivered with OpenRadar. There may be found several, so click on the one wanted and then activate the button "Download Scenery". Be patient and watch the Info-Field at the bottom: This first download of the required scenery will take some time before you see a "Ready"!
 

'''If the airport wanted does already exist''', it will be shown in the big center-field, with an "(exists)" at the end.
Double click onto the one wanted (or select it with one click and then click onto start) and you are in the ATC seat.
 
----

== '''''Operating''''' ==
[[File:OpenRadar Prototype.png|thumb|270px|Oakland international used in new OpenRadar]]
The OpenRadar main screen is divided into three regions:
#Top left you see the big '''Radar Map''' showing the airport, its surrounding, the navaids and the radar targets.
#Below it, bottom left, you see the '''MPchat Area''' for the FlightGear multiplayer chat feature.
#On the right side you see the '''Service Area''' with 4 subparts. From top to bottom those are
##'''Status Information'''
##'''COM-Radios''' ''(only if you have defined one or more)''
##'''Runway Manager''' to set up runways used
##the '''Flight Strip Manager''', where you can manage your radar targets.
Please notice in the following description the lightblue background at some items, indicating changes that may not yet be available in your version of the OpenRadar!

==== Radar Map ====
The radar map is the most complex part of OpenRadar, thus you have many options to zoom in on any area you are interested in. You can:
* set four functional zoom levels by clicking onto '''''GROUND, TOWER, APP and SECTOR.'''''
* zoom in and out using your mouse wheel ''(Mac: hold your right mousebutton pushed while moving over the radar-background in NorthWest respectively SouthEast)''
* adjust the map-center by dragging it with your mouse (click-hold left and drag)

* a double mouse-click onto the scope will move that point into the center of the scope
* a double right mouse-click will center the scope back to your location

You may assign any current settings to any of the 4 zoom levels (GROUND, TOWER, APP and SECTOR) by a right mouse-click onto the wanted level''
 
[[File:OpenRadar-Approach.png|thumb|right|250px|A typical tower operation]]
The '''''Radar-targets'''''
*do have a label attached with the following informations
:{| class="wikitable" style="text-align:center"
|-
|UID||heading direction
|-
|Flight Level||Airspeed
|}
*and are displayed in 5 different colors:
::''(See also the chapter "Flight Strip Manager")''
:{| class="wikitable"
|-
|align="center"|white||always the currently selected target, it's UID is also shown in the MPchat inputline (e.g. see "D-Leon" who just is getting his "clear to land")
|-
|align="middle"|blue||targets who's Flight-Stripe is placed to the left (e.g. see "Side" (just started) and "D-AHGM" just going to intercept the ILS: These 2 PLUS the white "D-LEON" are actively controlled right then!)
|-
|align="center"|yellow||targets who's Flight-Stripe is placed in the middle (e.g. could be assigned to "jomo2" as an indication that we wait for him to "wake up" soon - because then he may become a danger to others when taxiing uncontrolled)
|-
|align="center"|green||targets who's Flight-Stripe is placed to the right (e.g. see "jomo2" just parking - not actively controlled right now)
|-
|align="center"|gray||a neglected target or one for which there were no refresh data received from the MPserver for some time. In those cases the aircraft-type will be replaced by either "neglected" or by the time that elapsed since the last MPserver-update.
|}

[[File:OpenRadar-GND.png|thumb|right|250px|A GND layout with active PPN's]]
The radar map has so many details to display, that it is impossible to display all at once. Because of that we display details depending on the zoom level. For instance we hide Fixes and/or Runway Numbers etc. at a certain level of zoom. Thus OpenRadar features an adaptive detail level. In addition you can hide types of data by the following buttons:
{| class="wikitable"
|-
| '''''FIX''''' || Show/NoShow FIX's (they will automatically be set "NoShow" above distinct scale-settings!)
|-
| '''''NDB''''' || Show/NoShow NDB's (they will automatically be set "NoShow" above distinct scale-settings!)
|-
| '''''VOR''''' || Show/NoShow VOR's
|-
| '''''APT''''' || Show/NoShow Airports, inclusive their groundlayout (You may double-click onto a wanted airport and zoom in to see the layout)
|-
| '''''CIRC''''' || Show/NoShow circles at distinct distances around your present location. The distance between the circles shown depends on the chosen zoom-factor!
|-
| '''''GSH''''' || Show/NoShow Glide-Slope-Heights along the centerline of the runway for landings. They will automatically be set "NoShow" above distinct scale-settings!)
|-
| '''''PPN''''' || Show/NoShow the "Park Position Numbers", ''those may not yet be available on all airports!''. The PPNs will automatically be set "NoShow" above distinct scale-settings!)
|- style="background:lightblue"
| '''''StP''''' || Show/NoShow the "Selected (target) To Pointer" ''(doggy)'', an attachment to the mousepointer, showing some data about the relation of the selected target to the location of the mouse-pointer (similar to line 3 in the "Status Informations", see above)
|}

The "Runway Manager" (on the right side of the screen) allows you to define which runway(s) should be used for landing and/or starting. This status is shown with little green/red dots at the runway end. See in the picture "A typical tower operation" above:
*25L, 25R, and 18 are active (see the green and red dots at the ends)
*25L has in addition the blue approach center line and funnel, i.e. it is assigned for landings. This center line is drawn out for 100mi, helping you to align the arriving airplanes with the runway. In addition there is shown some kind of a funnel in a definable distance that may help you to align the planes coming via a base-leg for landing.

==== MPchat area ====
[[File:OpenRadar-MPchat.png|thumb|right|270px|The MPchat area]]
This area allows you to enter chat messages, view the chat history and filter it.
 
In the '''''entry-line''''' atop you define your messages to any radar-target by:
*Manually typing a message:
**A '''''left''''' mouse-click onto a Flight-Stripe or onto a Radar-Target will place the Target-UID at the beginning of the entry-line
**Then you may type or copy/past anything behind that - and send it out by ENTER
*Generate a standard message:
**A '''''right''''' mouse-click onto a Flight-Stripe or onto a Radar-Target will open a list with the available messages - select one with a left mouse-click
**That will place the message into the entry-line - you may now review/edit it and then send it out by ENTER
*OpenRadar will always set the ATC-name (as it appears on the very top of the service area - see the following chapter) in front of the message.

Below that entry-line is the '''''scrollable list''''' of exchanged MPchat-messages. In that list the messages related to the selected target are colored cyan. With the button "'''''SEL'''''" you set a filter to show only the messages related to the selected target. This filter will be reset as soon as you select another target - or by clicking onto "'''''ALL'''''".

You may enlarge that area by grabbing the upper edge with the left mouse-button and move it upward. Of course that will reduce the size of the radar-screen -- so use it with care!

==== Service Area ====
This column at the right side of the screen is for setting up the base-data for the operation, display needed data for traffic-guidance, and provide tools for guiding the pilots.

=====Status Informations=====
[[File:OpenRadar-Status_2.png|thumb|right|200px|The general Status Informations]]
This area shows in 4 lines the most used status-informations:
<ol><li>A text box that allows you to see and change your MP-callsign. So you can quickly change it, if a second ATC takes another role at the same airport (TW/APP/GND/RADAR, etc). At the right of it is placed a clock with the UTC-time. Because you probably will always have international guests you should refer to that modern "Coordinated Universal Time" (replacing nowadays the formerly used "Greenwich Mean Time" (GMT))
</li><li>In the second line you see the ICAO (the international Code for airports) and the long name of your airport. In addition you see on the right the currently selected radar contact (e.g. "jomo").
</li><li>The third line lets you predict several values for that "radar contact" (e.g. "jomo"). Whenever you place your mousepointer somewhere on the Radar Map, the third line will give you several informations about that target:
*StP = "Selection to Pointer": That is the compass direction between the target and the mousepointer, in both ways (TO/FROM)
*Miles: The distance between the target and the mouspointer.
*min: The time the target needs to get to that mousepointed area - '''IF''' the speed remains steady as is!! In this example there is given a "n/a" (not available) which most probably means the plane is not moving (may be parked)!
</li><li>The fourth line shows the mostly needed weather information '''Wind''', '''Pressure''' and '''Visibility'''. If you hover your mouse over it, you can see the complete last METAR-message received, in it's original form. (For help ref to http://wiki.flightgear.org/METAR#METAR). Please note that these values are similar to ATIS information: METAR directions is given in TRUE, ATIS in magnetic...
</li></ol>
====='''COM-Radios'''=====
[[File:OpenRadar-COM_2.png|thumb|right|200px|The COM-Setting (that can be none or up to 4)]]
According to the amount of FGcom-Ports you defined during setup (compare chapter "3.1.1 FGcom") you find here as many COM-Units (COM0 to max COM3). Each of them has a PopUp-List of Radio-frequencies available for the airport you are located on. You may
*choose a frequency out of the list by clicking onto the arrow at the right of the input-field
*or empty the field by a right mouseclick and enter any other frequency wanted.
At the right of that field you find a "Push To Talk" (PTT) button that you can operate by mouseclick -- or you can use the shortcuts given in the following table.
:{| class="wikitable" style="text-align:center"
!COMx
!left on keyboard
!right on keyboard
|-
|COM0||Ctrl||NumOff+Num0
|-
|COM1||SHIFT||NumOff+Num1
|-
|COM2|| ||NumOff+Num2
|-
|COM3|| ||NumOff+Num7
|}
Please watch the color change of the PTT buttons to know, when you can speak.

In case you operate the FGcom in the "'''''controlled by OpenRadar'''''" mode (compare the "FGComMode" in chapter "Startup"), then
*the radio label turns to red when FGcom is unable to establish a connection on this frequency. (Remember: OpenRadar has more frequencies available than FGcom knows of!!)
*you have an additional "'''''Restart'''''"-button: In case the communication becomes chopped or interrupted, you may click here to restart the FGCOM-program.
 
====='''Runway Settings'''=====
[[File:OpenRadar-Runways_2.png|thumb|right|200px|The Runway Manager]]
[[File:OpenRadar-Runway-Settings.png|thumb|right|200px|The Runway Manager Settings]]
Here you define the major variables for your airport operations: That are the assignments of the runways! For this purpose OpenRadar gives you a lot of precalculated and or default values to support your decisions findings and/or informations pilots may ask you about. See e.g. the pictures on the right:
*From top to bottom OpenRadar lists all runways available for that airport. For each runway you may define unique operating/display values. For these values see the picture "OpenRadar-Runway-Settings" below, e.g. see the 07C ''(you open that by a right mouseclick onto the runway-name (07C))'':
**In the header line you see left the now chosen runway to be edited, and at the left a button "'''''Copy to All'''''". With this switch you can copy the settings you make here to all the other runways - so e.g. for EDDF with its 8 settings you can save a lot! Only the values will be changed - all the selection-markers will remain as are in each unique setting table! These settings will then be saved separately for each unique airport in you private settings.
**With "'''''Main switches'''''" you define which functions may be available for that runway. Usually you can define for each runway as well a "Starting" as also a "Landing" function. In the given example for EDDF there is a complication: Per Law you are forbidden
:::to use runway 36 at all --> thus disable both lines: All data for that runway disappear
:::to use runway 18 for "Landing" only --> thus disable only "Landing": Just the Land-Option disappears
:::''(How do you know those details? Well, as a good ATC you prepare yourself by reading the official airport data (or look for something like e.g. http://en.wikipedia.org/wiki/Frankfurt_Airport, see on that page in the right column)''.
:*The "'''''Extended center line'''''" is the line you see in the above picture ''"A typical tower operation"'' at the right. If you want that line you may define how long it should be. Some people do not want it reaching over the whole screen. We suggest to limit it to the MPserver-range of 100 mi. It will only be visible for the runways defined for "Landing"!
:*The "'''''Distance markers'''''" are measurement markers on that "Extended center line". Here you define from were to were you want to have such markers ''(they may restrain your eyes if you use them all over!)''.
:*"'''''Vectoring and base leg'''''" define that funnel that you also see in the above picture ''"A typical tower operation"''. Also this will be shown only for the "Landing" runways.
:One tip to the handling of the "Landing" runways: Those are always shown in the "ATIS" message. If you define two (or even more) - in that "ATIS" message appear all those with the ILS data, etc.! So if you use mainly one we suggest to define only one - and activate more if you actually assign an additional one. Otherwise the pilots may become confused of that many informations and you yourself may have problems to differentiate which line the target should follow!

*From left to right you see the following informations for each runway (if available):
:*The runway-name
:*Check-boxes to define if that runway is used at all, may be just for landings or just for starts or for both. The program prevents you from assigning a runway in both directions (e.g. 25R and 07L)
:*A graphical display of the cross winds and and gusts: They are green from 0-5kn, orange 5-10kn and red above. When there are significant gusts that color-bar is divided into two. Typically the gusts then will be represented by the longer bar!
:*Above that bar you see the fractions of head- and crosswind. You may use especially the crosswind-fraction to warn pilots if those are => 10 kn! (Remember: You find the normal wind values in the METAR-data further up in the Status Informations)
:*To the right follows
::*in the upper line the exact runway heading (as needed for older type autopilots)
::*in the lower line the length and width of the runway in feet!
:*Then follow the ILS informations, if ILS is available for that runway. The data shown are: the ILS-beacon-name, the frequency, the glideslope, and the altitude at the threshold.

====='''Flight Strip Manager'''=====
[[File:OpenRadar-Stripes.png|thumb|right|200px|Handling the Flight-Stripes]]
Paper Flight Strips are the ATCs help to coordinate his traffic. In reality those strips contain many details about the flight, that we do not have (yet). Based on vertical space-limitations we have gathered the most critical informations into 2 lines, which are automatically initiated and controlled by the program. Those are:
:{| class="wikitable" style="text-align:center"
|-
|Target UID||Aircraft Type||colspan="2"|direction to it from ATC
|-
|distance to it||IAS+GND speed||Altitude (FL)||current heading
|}
In addition the user may add some more informations in additional lines. We urge you to reduce these additional lines to a minimum, because already with 2 lines the list will become that long, that you must scroll constantly! These additional lines will be saved as target-data and inserted each time a new stripe is created for that target! We suggest to maintain some target-data and some flight data for all frequent visitors. See as a suggestion several 3rd line examples:

"ILS VOR FGC NRW || GED MTR"
 This pilot knows how to use ILS, VOR, FGcom, the new Runway at EDDF || he is advised to approach via VOR GED and MTR.

"ILS VOR FGC NRW || KJFK 280° f510"
 This pilot also can use ILS, VOR, FGcom, NRW || and will depart to JFK on a straight course of 280° on FL510"

You are absolutely free to define your own codes and whatever. To do so
*enter/edit those data by opening the "'''''Note Editor'''''" with a right mouse-click ''(Mac: Alt + right mouse-click)'' while pressing onto the stripe
*add additional lines by Strg+ENTER (remember: Not more than 2, please!)
*Always exit that Editor with the ENTER-key in order to transfer the data to the stripe!
*At the bottom of this editor you can also select in which '''''additional language''''' the "standard commands" shall be transmitted to that target.

You can '''''manipulate the listing''''' of the flight strips:
*New radar-targets will always appear at the end of the list on the right side
*You can move the stripes in vertical order by drag and drop
*You can place them in three horizontal columns (left, middle and right) either by dragging them with the hold-down mouse button or by mouse-clicks left or right of the stripes ''(you may double-click to move directly from one side to the other)''
*with the "'''''AUTO'''''"-button at the upper edge of this area you can define that the stripes will be sorted automatically into groups according to their left/center/right position. This may be very irritating at first - so you may want to switch that "AUTO" off at first usages!
*The radar-targets will change their color according to the horizontal position of their stripe:
**the radar-targets for stripes at the right side will be '''green''' - these are all targets when initialized!
**the radar-targets for stripes in the center will be '''yellow'''
**the radar-targets for stripes at the left side will be '''cyan'''
On the radar-map the "cyan targets" will overlay the "yellow targets" - and the "yellow targets" will overlay the "green" ones!
 
You cannot change these combinations of color and position -- but you might define your own definition of what the positions mean! We suggest the following:
:'''''green''''' = right = initial position: Means not yet defined or not under my control (e.g. passing through on high altitude, is controlled by another ATC, etc.)
:'''''yellow''''' = center = I expect him to get under my control when in range (e.g. 60 mi), or he may be transfered to me by another ATC soon, etc. He may become a danger to the traffic controlled by me if he continues uncontrolled!
:'''''cyan''''' = left = under my control (light cyan when active in the MPchat input-line!)
Again: That is a proposal - you can define your on assignments!

You can apply the following mouse-actions onto the stripes as well as onto the radar-targets:
*a '''''single left''''' mouse-click '''''selects/activates''''' it, i.e. its radar-target becomes "light cyan" and its UID is set into the MPchat input-line. In addition
**its listed messages in the MPchat-list become colored cyan
**and the "doggy" at the mouse-pointer displays data about the relation between that target and the mouse-pointer
*a '''''double left''''' mouse-click helps you to find the target by highlighting the target on the scope. It also changes the radar-range to show both: The Target and your location. The selection of any of the "preset zoom levels" (GROUND, TOWER, APP, Sector) will reset the map-position again to its center!
*a '''''center''''' mouse-click opens the '''''Note Editor''''' (see above)
*a '''''right''''' mouse-click shows the dialog to choose pre-defined ATC messages to be sent to the current contact
*a '''''CTRL+left''''' mouse-click will define that target as '''''neglected'''''. Thus his radar-target will become just a light gray color, that will not overlay or otherwise disturb the radar-views.
 
----

== '''''Useful Features''''' ==
'''Radar Map'''
* On contact
:* '''left''' click '''selects''' and sets cursor into the chat input field
:* '''middle''' click opens the radar '''contact settings''' (ATC note and native language)
:* '''right''' click opens the '''ATC messages''' selection box

* '''left double''' click on map to '''center''' it '''on airport''' (return to airport)
* middle click on zoom level defines the current view as new center and zoom setting (stored in a file)
* a click on the texts, on the lower left, toggle display of FIX, NDB, VOR,...

'''Flight Strip Area'''
* On flight strip
:* '''left''' click '''selects''' the contact and sets cursor into the chat input field
:* '''middle''' click opens the radar '''contact settings''' (ATC note and native language)
:* '''right''' click opens the '''ATC messages''' selection box 

:* '''left double''' click '''centers''' radar '''map on''' the '''contact''' (to find contact)
:* '''CTRL+left''' click sets the contact to be '''neglected'''

* a click beside the flight strips moves the flight strips between the three columns (right, middle, left)

'''Runway area'''
* '''right''' click '''on runway number''' opens the '''runway settings dialog''' to define the centerline and vectoring settings
* If at least one runway is active you may '''double click''' the runway panel '''background to hide the inactive runways''' (frees space for flight strips)

'''Radios'''
* a '''right''' click '''on the frequency list''' changes the input to be '''editable''', so you can define the frequencies by yourself

''' Shortcuts '''
{| class="wikitable"
|-
! Shortcut !! Action
|-
| '''ESC''' || Close all open dialogs and cancel the text input (reset chat input field)

|-
| ALT + L || Toggle FGCom Log Window (only if you run FgCom started by OpenRadar)

|-
| '''Left CTRL''' || PTT Radio COM0 (if it has been activated via Port in Settings)
|-
| NUM off: Num0 || PTT Radio COM0 (if it has been activated via Port in Settings)
|-
| '''Left SHIFT''' || PTT Radio COM1 (if it has been activated via Port in Settings)
|-
| NUM off: Num1 || PTT Radio COM1 (if it has been activated via Port in Settings)
|-
| NUM off: Num2 || PTT Radio COM2 (if it has been activated via Port in Settings)
|-
| NUM off: Num3 || PTT Radio COM3 (if it has been activated via Port in Settings)
|}
 
----
== '''''Acknowledgments''''' ==
This project was founded and driven by Ralf Gerlich. Still today he is supporting it as a mentor.

And not to be forgotten: This project links different efforts of many people together. Thank you for your great work!

[[Category:OpenRadar|Guide]]

OpenRadarGuide

2013-02-07T19:48:41Z

Stepfaw: /* 1) FGcom */

[[OpenRadar| Back to mainpage]]
=='''''Preface'''''==
[[OpenRadar]] is a prototype to support Flight-Simulator ATCs in their work on our airports.
 
Some words to our project targets:
* '''Realism:''' That means we show all the data a real live ATC would need. For instance we simulate a radar antenna and perform one position update per antenna rotation. But we don't have professional ATCs, neither do we have professional pilots contacting our ATCs. So we have to make some compromises...
* '''Usability:''' The application should be handy, behave consistently, and require almost no training. The ATC has other things to do than to fight with the application

We hope that we met your needs and are happy to get feedback!

'''Important:''' We support you with tooltip texts, that appear when you hover over an active area with your mouse. They shall remind you of possible interactions that you may have forgotten. Try pointing your mouse everywhere - maybe there is something available that you missed until now...
 
----
=='''''Prerequisites'''''==
===Internet===
Of course you need an uninterrupted Internet access to exchange data between You and your clients/targets. The requirements for that connection are not very high -- but they must be uninterrupted!

===Communication / FGCOM===
We urge you to always offer your services as well in typing (MPchat) as also in speaking (FGcom).
*'''MPchat''' is an integral part of OpenRadar and needs no further installations. (ref.: http://wiki.flightgear.org/Howto:Multiplayer )
*But '''FGcom''' is a standard application which must be installed in addition.

You will soon discover, that FGcom makes it much easier to communicate
*as well for you ''(who hopefully will control many pilots at the same time)''
*as also for the pilots ''(who need both hands to control their plane)''.
For both of them there will be not enough time for typing!
 
If FGCOM is not yet installed, see:
:*For Windows and Linux: http://code.google.com/p/fgcomgui/
:*For OSX: We do not know of a standalone installation source - but we do know that starting with version 2.0.0 the FGFS-OSX-version does contain the FGCom. That fits and works for OSX >= 10.5.
:In addition you may inform yourself about FGCOM on:
:{| class="wikitable"
|-
|for general infos||http://wiki.flightgear.org/FGCom
|-
|for more detailed informations||http://wiki.flightgear.org/FGCOM_for_Windows
|-
|if you have problems with FGCOM||http://wiki.flightgear.org/FGCOM_Testing
|}

===Java V7===
Make sure you have installed at least Version 7 of Java. Verify and or Download the installation packages from: http://www.java.com/en/download/index.jsp

===OpenRadar===
For the currently available Prototype of OpenRadar see http://wagnerw.de/OpenRadar.zip. Extract the content of this ZIP to a place where it is easy to find. Make sure you have read and write permissions for that directory.
 
If you did already work with an OpenRadar installation you may want to
* RENAME your current OpenRadar-directory (i.e. to "OpenRadar-BU")
* then download and extract the new version into a newly created directory with the name of the old one (without the "-BU")
* now you can replace all data in the new "OpenRadar/data" directory with the ones in the "OpenRadar-BU/data"
** if you expect changes in the scenery etc. do not copy the the Airport (ICAO) directories
* delete the BU-version only after you are sure you verified that all your personal data were transferred, i.e. still accessible!
 
----
== '''''Startup''''' ==
Inside the downloaded OpenRadar base-directory you will find start-scripts. See
*for Windows: OpenRadar.bat
*for Linux: OpenRadar.sh
*for OSX: OpenRadar.jar
At Startup you will always be welcomed by the “OpenRadar – Welcome”. That window presents 2 TABs to define your preferences:
{|
|-
|[[File:OpenRadar - Welcome-Linux.png|thumb|left|Welcome tab on Linux]]||
[[File:OpenRadar- Settings-linux.png|thumb|left|Settings tab on Linux]]
|}
For all data there are standard values given as defaults. If you do change any values, they will be saved and presented to you during the next start.
 
If this is the very first time you start OpenRader, then you have to verify your “Settings” first, thus click onto the “Settings”-tab:

=== OpenRadar-Welcome - Settings ===
These settings are grouped into 3 parts:
===='''1) FGcom'''====
:OpenRadar can support up to 4 instances of FGcom in 2 ways:
:#It can start and control FgCom instances that operate in the background as sub-tasks of OpenRadar (except for OSX where FgCom must be run in a separate Terminal window)
:#or just control manually started FgCom-sessions.

:You select these modes of operation by the “'''FgComMode'''” selection:
 
:'''a) Internal:''' FGCom(s) are started and controlled internally by OpenRadar
::For this mode you have to define all available fields to tell OpenRader where your FGcom resides and what options shall be used:
::'''Path:''' Here you define where your FGcom is installed.
:::In the following some examples:

:::{| class="wikitable" style="text-align:center"
!type
!Windows
!Linux
!OSX
|-
|a standard installation || C:\Programs\FGcom ||/home/''YourName''/fgcom ||*)
|-
|on another disk || D:\FlighGear_2.6\FGcom || /media/''DiskName''/FGFS/fgcom ||*)
|-
|on a LAN-server || \\''ServerName''\Central\FGFS || /home/YourName//.gvfs/fgfs on nas-server/fgcom||*)
|}
::::*) for OSX we do not know – pls help us by defining it here or send a PersonalMessage to “Wagnerw” or “jomo”

::'''Executable:''' Here you define the program-name that shall be started

:::*For Windows: "fgcom.exe" or "anyName.bat"
:::*for Linux: "fgcom" or "anyName.sh"
:::*OSX: ''We do not know – pls help us by defining it here or send a PersonalMessage to “Wagnerw” or “jomo”''

::'''Server:''' There are 2 FGcom-servers available as of today:
::*delta384.server4you.de ''(we do suggest this one)''
::*fgcom.flightgear.org.uk
::'''Client:''' will always be “localhost” - unless you want to run FGcom on a different PC than OpenRadar.
::'''FGcom Ports:''' The here defined values are crucial for the operation because:
::*They are the only connection between the OpenRadar and FGcom. So you must define those the same in OpenRadar as well as in FGcom !!
::*They also define how many “Radio Units” (COM0, COM1, etc.) are generated within OpenRadar
::Simply provide a coma separated list of UDP Ports to be used by FGcom. But be warned: More than two are hard to handle!
:::::e.g. 16661,16662
 
:'''b) External:''' OpenRadar controls a manually started instance of FGcom - via the defined Port.
::For this one you only need to define where that FGcom is running and what the connecting port is. e.g.:
::*'''Client:''' locahost
::*'''FGcom Ports:''' 16661,16662 ''(if e.g. 2 FGcom instances were started)''
 
:'''c) OFF:''' No FGcom support
::That means that You do not want to work with FGcom during your ATC-session – thus you do not need to define any of the fields and there will not be defined any Radio (e.g. COM0) in OpenRadar. This mode is not suggested!

===='''2) FG Multiplayer'''====
:Here you find the server and connection port of FlightGears multiplayer server. It delivers the radar contact position informations and is used for chat. You won't have to change the settings, as long as the server won't change.
:In case you experience problems with the outside you may check and/or choose any "'''''Server'''''" that is listed in http://mpmap01.flightgear.org/mpstatus/: Look for a server nearest to your location that has a status of "OK" and shows the most "totals".
:'''''PLEASE NOTE:''''' The "'''''Client port'''''" is the port used by your computer to talk with that server. If you want to use FlightGears internal chat parallel to OpenRadar, you must use a different port than FlightGear. Because of that, the default port of OpenRadar is 5001 ''(in order to differentiate it to the 5000 used in FGFS)''.

===='''3) METAR'''====
:OpenRadar retrieves the weather information via METAR messages from a server in the INTERNET. This information is being displayed and used to calculate the usability of runways and the air speed of the radar contacts.
:If your airport is too small to be in that worldwide list, you can provide the code of another bigger airport with METAR data nearby in the sector.property file. But be aware that then your customers weather-settings may differ to yours, because they may use the standard FGFS-METAR-Source!

Please click on the verify button to have your settings checked!

===Select Airport===
This is always the first window that you will see after starting OpenRadar.
 

But at first, the available airport list (e.g. EDDF, KOAK,..) in the center will be empty. So at first define a location:
 

In order to '''define a new work-location''' simply enter the airport code (ICAO) or a part of the name into the search field and hit “search”: The list below then shows the results found in the airport database delivered with OpenRadar. There may be found several, so click on the one wanted and then activate the button "Download Scenery". Be patient and watch the Info-Field at the bottom: This first download of the required scenery will take some time before you see a "Ready"!
 

'''If the airport wanted does already exist''', it will be shown in the big center-field, with an "(exists)" at the end.
Double click onto the one wanted (or select it with one click and then click onto start) and you are in the ATC seat.
 
----

== '''''Operating''''' ==
[[File:OpenRadar Prototype.png|thumb|270px|Oakland international used in new OpenRadar]]
The OpenRadar main screen is divided into three regions:
#Top left you see the big '''Radar Map''' showing the airport, its surrounding, the navaids and the radar targets.
#Below it, bottom left, you see the '''MPchat Area''' for the FlightGear multiplayer chat feature.
#On the right side you see the '''Service Area''' with 4 subparts. From top to bottom those are
##'''Status Information'''
##'''COM-Radios''' ''(only if you have defined one or more)''
##'''Runway Manager''' to set up runways used
##the '''Flight Strip Manager''', where you can manage your radar targets.
Please notice in the following description the lightblue background at some items, indicating changes that may not yet be available in your version of the OpenRadar!

==== Radar Map ====
The radar map is the most complex part of OpenRadar, thus you have many options to zoom in on any area you are interested in. You can:
* set four functional zoom levels by clicking onto '''''GROUND, TOWER, APP and SECTOR.'''''
* zoom in and out using your mouse wheel ''(Mac: hold your right mousebutton pushed while moving over the radar-background in NorthWest respectively SouthEast)''
* adjust the map-center by dragging it with your mouse (click-hold left and drag)

* a double mouse-click onto the scope will move that point into the center of the scope
* a double right mouse-click will center the scope back to your location

You may assign any current settings to any of the 4 zoom levels (GROUND, TOWER, APP and SECTOR) by a right mouse-click onto the wanted level''
 
[[File:OpenRadar-Approach.png|thumb|right|250px|A typical tower operation]]
The '''''Radar-targets'''''
*do have a label attached with the following informations
:{| class="wikitable" style="text-align:center"
|-
|UID||heading direction
|-
|Flight Level||Airspeed
|}
*and are displayed in 5 different colors:
::''(See also the chapter "Flight Strip Manager")''
:{| class="wikitable"
|-
|align="center"|white||always the currently selected target, it's UID is also shown in the MPchat inputline (e.g. see "D-Leon" who just is getting his "clear to land")
|-
|align="middle"|blue||targets who's Flight-Stripe is placed to the left (e.g. see "Side" (just started) and "D-AHGM" just going to intercept the ILS: These 2 PLUS the white "D-LEON" are actively controlled right then!)
|-
|align="center"|yellow||targets who's Flight-Stripe is placed in the middle (e.g. could be assigned to "jomo2" as an indication that we wait for him to "wake up" soon - because then he may become a danger to others when taxiing uncontrolled)
|-
|align="center"|green||targets who's Flight-Stripe is placed to the right (e.g. see "jomo2" just parking - not actively controlled right now)
|-
|align="center"|gray||a neglected target or one for which there were no refresh data received from the MPserver for some time. In those cases the aircraft-type will be replaced by either "neglected" or by the time that elapsed since the last MPserver-update.
|}

[[File:OpenRadar-GND.png|thumb|right|250px|A GND layout with active PPN's]]
The radar map has so many details to display, that it is impossible to display all at once. Because of that we display details depending on the zoom level. For instance we hide Fixes and/or Runway Numbers etc. at a certain level of zoom. Thus OpenRadar features an adaptive detail level. In addition you can hide types of data by the following buttons:
{| class="wikitable"
|-
| '''''FIX''''' || Show/NoShow FIX's (they will automatically be set "NoShow" above distinct scale-settings!)
|-
| '''''NDB''''' || Show/NoShow NDB's (they will automatically be set "NoShow" above distinct scale-settings!)
|-
| '''''VOR''''' || Show/NoShow VOR's
|-
| '''''APT''''' || Show/NoShow Airports, inclusive their groundlayout (You may double-click onto a wanted airport and zoom in to see the layout)
|-
| '''''CIRC''''' || Show/NoShow circles at distinct distances around your present location. The distance between the circles shown depends on the chosen zoom-factor!
|-
| '''''GSH''''' || Show/NoShow Glide-Slope-Heights along the centerline of the runway for landings. They will automatically be set "NoShow" above distinct scale-settings!)
|-
| '''''PPN''''' || Show/NoShow the "Park Position Numbers", ''those may not yet be available on all airports!''. The PPNs will automatically be set "NoShow" above distinct scale-settings!)
|- style="background:lightblue"
| '''''StP''''' || Show/NoShow the "Selected (target) To Pointer" ''(doggy)'', an attachment to the mousepointer, showing some data about the relation of the selected target to the location of the mouse-pointer (similar to line 3 in the "Status Informations", see above)
|}

The "Runway Manager" (on the right side of the screen) allows you to define which runway(s) should be used for landing and/or starting. This status is shown with little green/red dots at the runway end. See in the picture "A typical tower operation" above:
*25L, 25R, and 18 are active (see the green and red dots at the ends)
*25L has in addition the blue approach center line and funnel, i.e. it is assigned for landings. This center line is drawn out for 100mi, helping you to align the arriving airplanes with the runway. In addition there is shown some kind of a funnel in a definable distance that may help you to align the planes coming via a base-leg for landing.

==== MPchat area ====
[[File:OpenRadar-MPchat.png|thumb|right|270px|The MPchat area]]
This area allows you to enter chat messages, view the chat history and filter it.
 
In the '''''entry-line''''' atop you define your messages to any radar-target by:
*Manually typing a message:
**A '''''left''''' mouse-click onto a Flight-Stripe or onto a Radar-Target will place the Target-UID at the beginning of the entry-line
**Then you may type or copy/past anything behind that - and send it out by ENTER
*Generate a standard message:
**A '''''right''''' mouse-click onto a Flight-Stripe or onto a Radar-Target will open a list with the available messages - select one with a left mouse-click
**That will place the message into the entry-line - you may now review/edit it and then send it out by ENTER
*OpenRadar will always set the ATC-name (as it appears on the very top of the service area - see the following chapter) in front of the message.

Below that entry-line is the '''''scrollable list''''' of exchanged MPchat-messages. In that list the messages related to the selected target are colored cyan. With the button "'''''SEL'''''" you set a filter to show only the messages related to the selected target. This filter will be reset as soon as you select another target - or by clicking onto "'''''ALL'''''".

You may enlarge that area by grabbing the upper edge with the left mouse-button and move it upward. Of course that will reduce the size of the radar-screen -- so use it with care!

==== Service Area ====
This column at the right side of the screen is for setting up the base-data for the operation, display needed data for traffic-guidance, and provide tools for guiding the pilots.

=====Status Informations=====
[[File:OpenRadar-Status_2.png|thumb|right|200px|The general Status Informations]]
This area shows in 4 lines the most used status-informations:
<ol><li>A text box that allows you to see and change your MP-callsign. So you can quickly change it, if a second ATC takes another role at the same airport (TW/APP/GND/RADAR, etc). At the right of it is placed a clock with the UTC-time. Because you probably will always have international guests you should refer to that modern "Coordinated Universal Time" (replacing nowadays the formerly used "Greenwich Mean Time" (GMT))
</li><li>In the second line you see the ICAO (the international Code for airports) and the long name of your airport. In addition you see on the right the currently selected radar contact (e.g. "jomo").
</li><li>The third line lets you predict several values for that "radar contact" (e.g. "jomo"). Whenever you place your mousepointer somewhere on the Radar Map, the third line will give you several informations about that target:
*StP = "Selection to Pointer": That is the compass direction between the target and the mousepointer, in both ways (TO/FROM)
*Miles: The distance between the target and the mouspointer.
*min: The time the target needs to get to that mousepointed area - '''IF''' the speed remains steady as is!! In this example there is given a "n/a" (not available) which most probably means the plane is not moving (may be parked)!
</li><li>The fourth line shows the mostly needed weather information '''Wind''', '''Pressure''' and '''Visibility'''. If you hover your mouse over it, you can see the complete last METAR-message received, in it's original form. (For help ref to http://wiki.flightgear.org/METAR#METAR). Please note that these values are similar to ATIS information: METAR directions is given in TRUE, ATIS in magnetic...
</li></ol>
====='''COM-Radios'''=====
[[File:OpenRadar-COM_2.png|thumb|right|200px|The COM-Setting (that can be none or up to 4)]]
According to the amount of FGcom-Ports you defined during setup (compare chapter "3.1.1 FGcom") you find here as many COM-Units (COM0 to max COM3). Each of them has a PopUp-List of Radio-frequencies available for the airport you are located on. You may
*choose a frequency out of the list by clicking onto the arrow at the right of the input-field
*or empty the field by a right mouseclick and enter any other frequency wanted.
At the right of that field you find a "Push To Talk" (PTT) button that you can operate by mouseclick -- or you can use the shortcuts given in the following table.
:{| class="wikitable" style="text-align:center"
!COMx
!left on keyboard
!right on keyboard
|-
|COM0||Ctrl||NumOff+Num0
|-
|COM1||SHIFT||NumOff+Num1
|-
|COM2|| ||NumOff+Num2
|-
|COM3|| ||NumOff+Num7
|}
Please watch the color change of the PTT buttons to know, when you can speak.

In case you operate the FGcom in the "'''''controlled by OpenRadar'''''" mode (compare the "FGComMode" in chapter "Startup"), then
*the radio label turns to red when FGcom is unable to establish a connection on this frequency. (Remember: OpenRadar has more frequencies available than FGcom knows of!!)
*you have an additional "'''''Restart'''''"-button: In case the communication becomes chopped or interrupted, you may click here to restart the FGCOM-program.
 
====='''Runway Settings'''=====
[[File:OpenRadar-Runways_2.png|thumb|right|200px|The Runway Manager]]
[[File:OpenRadar-Runway-Settings.png|thumb|right|200px|The Runway Manager Settings]]
Here you define the major variables for your airport operations: That are the assignments of the runways! For this purpose OpenRadar gives you a lot of precalculated and or default values to support your decisions findings and/or informations pilots may ask you about. See e.g. the pictures on the right:
*From top to bottom OpenRadar lists all runways available for that airport. For each runway you may define unique operating/display values. For these values see the picture "OpenRadar-Runway-Settings" below, e.g. see the 07C ''(you open that by a right mouseclick onto the runway-name (07C))'':
**In the header line you see left the now chosen runway to be edited, and at the left a button "'''''Copy to All'''''". With this switch you can copy the settings you make here to all the other runways - so e.g. for EDDF with its 8 settings you can save a lot! Only the values will be changed - all the selection-markers will remain as are in each unique setting table! These settings will then be saved separately for each unique airport in you private settings.
**With "'''''Main switches'''''" you define which functions may be available for that runway. Usually you can define for each runway as well a "Starting" as also a "Landing" function. In the given example for EDDF there is a complication: Per Law you are forbidden
:::to use runway 36 at all --> thus disable both lines: All data for that runway disappear
:::to use runway 18 for "Landing" only --> thus disable only "Landing": Just the Land-Option disappears
:::''(How do you know those details? Well, as a good ATC you prepare yourself by reading the official airport data (or look for something like e.g. http://en.wikipedia.org/wiki/Frankfurt_Airport, see on that page in the right column)''.
:*The "'''''Extended center line'''''" is the line you see in the above picture ''"A typical tower operation"'' at the right. If you want that line you may define how long it should be. Some people do not want it reaching over the whole screen. We suggest to limit it to the MPserver-range of 100 mi. It will only be visible for the runways defined for "Landing"!
:*The "'''''Distance markers'''''" are measurement markers on that "Extended center line". Here you define from were to were you want to have such markers ''(they may restrain your eyes if you use them all over!)''.
:*"'''''Vectoring and base leg'''''" define that funnel that you also see in the above picture ''"A typical tower operation"''. Also this will be shown only for the "Landing" runways.
:One tip to the handling of the "Landing" runways: Those are always shown in the "ATIS" message. If you define two (or even more) - in that "ATIS" message appear all those with the ILS data, etc.! So if you use mainly one we suggest to define only one - and activate more if you actually assign an additional one. Otherwise the pilots may become confused of that many informations and you yourself may have problems to differentiate which line the target should follow!

*From left to right you see the following informations for each runway (if available):
:*The runway-name
:*Check-boxes to define if that runway is used at all, may be just for landings or just for starts or for both. The program prevents you from assigning a runway in both directions (e.g. 25R and 07L)
:*A graphical display of the cross winds and and gusts: They are green from 0-5kn, orange 5-10kn and red above. When there are significant gusts that color-bar is divided into two. Typically the gusts then will be represented by the longer bar!
:*Above that bar you see the fractions of head- and crosswind. You may use especially the crosswind-fraction to warn pilots if those are => 10 kn! (Remember: You find the normal wind values in the METAR-data further up in the Status Informations)
:*To the right follows
::*in the upper line the exact runway heading (as needed for older type autopilots)
::*in the lower line the length and width of the runway in feet!
:*Then follow the ILS informations, if ILS is available for that runway. The data shown are: the ILS-beacon-name, the frequency, the glideslope, and the altitude at the threshold.

====='''Flight Strip Manager'''=====
[[File:OpenRadar-Stripes.png|thumb|right|200px|Handling the Flight-Stripes]]
Paper Flight Strips are the ATCs help to coordinate his traffic. In reality those strips contain many details about the flight, that we do not have (yet). Based on vertical space-limitations we have gathered the most critical informations into 2 lines, which are automatically initiated and controlled by the program. Those are:
:{| class="wikitable" style="text-align:center"
|-
|Target UID||Aircraft Type||colspan="2"|direction to it from ATC
|-
|distance to it||IAS+GND speed||Altitude (FL)||current heading
|}
In addition the user may add some more informations in additional lines. We urge you to reduce these additional lines to a minimum, because already with 2 lines the list will become that long, that you must scroll constantly! These additional lines will be saved as target-data and inserted each time a new stripe is created for that target! We suggest to maintain some target-data and some flight data for all frequent visitors. See as a suggestion several 3rd line examples:

"ILS VOR FGC NRW || GED MTR"
 This pilot knows how to use ILS, VOR, FGcom, the new Runway at EDDF || he is advised to approach via VOR GED and MTR.

"ILS VOR FGC NRW || KJFK 280° f510"
 This pilot also can use ILS, VOR, FGcom, NRW || and will depart to JFK on a straight course of 280° on FL510"

You are absolutely free to define your own codes and whatever. To do so
*enter/edit those data by opening the "'''''Note Editor'''''" with a right mouse-click ''(Mac: Alt + right mouse-click)'' while pressing onto the stripe
*add additional lines by Strg+ENTER (remember: Not more than 2, please!)
*Always exit that Editor with the ENTER-key in order to transfer the data to the stripe!
*At the bottom of this editor you can also select in which '''''additional language''''' the "standard commands" shall be transmitted to that target.

You can '''''manipulate the listing''''' of the flight strips:
*New radar-targets will always appear at the end of the list on the right side
*You can move the stripes in vertical order by drag and drop
*You can place them in three horizontal columns (left, middle and right) either by dragging them with the hold-down mouse button or by mouse-clicks left or right of the stripes ''(you may double-click to move directly from one side to the other)''
*with the "'''''AUTO'''''"-button at the upper edge of this area you can define that the stripes will be sorted automatically into groups according to their left/center/right position. This may be very irritating at first - so you may want to switch that "AUTO" off at first usages!
*The radar-targets will change their color according to the horizontal position of their stripe:
**the radar-targets for stripes at the right side will be '''green''' - these are all targets when initialized!
**the radar-targets for stripes in the center will be '''yellow'''
**the radar-targets for stripes at the left side will be '''cyan'''
On the radar-map the "cyan targets" will overlay the "yellow targets" - and the "yellow targets" will overlay the "green" ones!
 
You cannot change these combinations of color and position -- but you might define your own definition of what the positions mean! We suggest the following:
:'''''green''''' = right = initial position: Means not yet defined or not under my control (e.g. passing through on high altitude, is controlled by another ATC, etc.)
:'''''yellow''''' = center = I expect him to get under my control when in range (e.g. 60 mi), or he may be transfered to me by another ATC soon, etc. He may become a danger to the traffic controlled by me if he continues uncontrolled!
:'''''cyan''''' = left = under my control (light cyan when active in the MPchat input-line!)
Again: That is a proposal - you can define your on assignments!

You can apply the following mouse-actions onto the stripes as well as onto the radar-targets:
*a '''''single left''''' mouse-click '''''selects/activates''''' it, i.e. its radar-target becomes "light cyan" and its UID is set into the MPchat input-line. In addition
**its listed messages in the MPchat-list become colored cyan
**and the "doggy" at the mouse-pointer displays data about the relation between that target and the mouse-pointer
*a '''''double left''''' mouse-click helps you to find the target by highlighting the target on the scope. It also changes the radar-range to show both: The Target and your location. The selection of any of the "preset zoom levels" (GROUND, TOWER, APP, Sector) will reset the map-position again to its center!
*a '''''center''''' mouse-click opens the '''''Note Editor''''' (see above)
*a '''''right''''' mouse-click shows the dialog to choose pre-defined ATC messages to be sent to the current contact
*a '''''CTRL+left''''' mouse-click will define that target as '''''neglected'''''. Thus his radar-target will become just a light gray color, that will not overlay or otherwise disturb the radar-views.
 
----

== '''''Useful Features''''' ==
'''Radar Map'''
* On contact
:* '''left''' click '''selects''' and sets cursor into the chat input field
:* '''middle''' click opens the radar '''contact settings''' (ATC note and native language)
:* '''right''' click opens the '''ATC messages''' selection box

* '''left double''' click on map to '''center''' it '''on airport''' (return to airport)
* middle click on zoom level defines the current view as new center and zoom setting (stored in a file)
* a click on the texts, on the lower left, toggle display of FIX, NDB, VOR,...

'''Flight Strip Area'''
* On flight strip
:* '''left''' click '''selects''' the contact and sets cursor into the chat input field
:* '''middle''' click opens the radar '''contact settings''' (ATC note and native language)
:* '''right''' click opens the '''ATC messages''' selection box 

:* '''left double''' click '''centers''' radar '''map on''' the '''contact''' (to find contact)
:* '''CTRL+left''' click sets the contact to be '''neglected'''

* a click beside the flight strips moves the flight strips between the three columns (right, middle, left)

'''Runway area'''
* '''right''' click '''on runway number''' opens the '''runway settings dialog''' to define the centerline and vectoring settings
* If at least one runway is active you may '''double click''' the runway panel '''background to hide the inactive runways''' (frees space for flight strips)

'''Radios'''
* a '''right''' click '''on the frequency list''' changes the input to be '''editable''', so you can define the frequencies by yourself

''' Shortcuts '''
{| class="wikitable"
|-
! Shortcut !! Action
|-
| '''ESC''' || Close all open dialogs and cancel the text input (reset chat input field)

|-
| ALT + L || Toggle FGCom Log Window (only if you run FgCom started by OpenRadar)

|-
| '''Left CTRL''' || PTT Radio COM0 (if it has been activated via Port in Settings)
|-
| NUM off: Num0 || PTT Radio COM0 (if it has been activated via Port in Settings)
|-
| '''Left SHIFT''' || PTT Radio COM1 (if it has been activated via Port in Settings)
|-
| NUM off: Num1 || PTT Radio COM1 (if it has been activated via Port in Settings)
|-
| NUM off: Num2 || PTT Radio COM2 (if it has been activated via Port in Settings)
|-
| NUM off: Num3 || PTT Radio COM3 (if it has been activated via Port in Settings)
|}
 
----
== '''''Acknowledgments''''' ==
This project was founded and driven by Ralf Gerlich. Still today he is supporting it as a mentor.

And not to be forgotten: This project links different efforts of many people together. Thank you for your great work!

[[Category:OpenRadar|Guide]]

OpenRadarGuide

2013-02-07T19:41:20Z

Stepfaw: /* Startup */ for Mac

[[OpenRadar| Back to mainpage]]
=='''''Preface'''''==
[[OpenRadar]] is a prototype to support Flight-Simulator ATCs in their work on our airports.
 
Some words to our project targets:
* '''Realism:''' That means we show all the data a real live ATC would need. For instance we simulate a radar antenna and perform one position update per antenna rotation. But we don't have professional ATCs, neither do we have professional pilots contacting our ATCs. So we have to make some compromises...
* '''Usability:''' The application should be handy, behave consistently, and require almost no training. The ATC has other things to do than to fight with the application

We hope that we met your needs and are happy to get feedback!

'''Important:''' We support you with tooltip texts, that appear when you hover over an active area with your mouse. They shall remind you of possible interactions that you may have forgotten. Try pointing your mouse everywhere - maybe there is something available that you missed until now...
 
----
=='''''Prerequisites'''''==
===Internet===
Of course you need an uninterrupted Internet access to exchange data between You and your clients/targets. The requirements for that connection are not very high -- but they must be uninterrupted!

===Communication / FGCOM===
We urge you to always offer your services as well in typing (MPchat) as also in speaking (FGcom).
*'''MPchat''' is an integral part of OpenRadar and needs no further installations. (ref.: http://wiki.flightgear.org/Howto:Multiplayer )
*But '''FGcom''' is a standard application which must be installed in addition.

You will soon discover, that FGcom makes it much easier to communicate
*as well for you ''(who hopefully will control many pilots at the same time)''
*as also for the pilots ''(who need both hands to control their plane)''.
For both of them there will be not enough time for typing!
 
If FGCOM is not yet installed, see:
:*For Windows and Linux: http://code.google.com/p/fgcomgui/
:*For OSX: We do not know of a standalone installation source - but we do know that starting with version 2.0.0 the FGFS-OSX-version does contain the FGCom. That fits and works for OSX >= 10.5.
:In addition you may inform yourself about FGCOM on:
:{| class="wikitable"
|-
|for general infos||http://wiki.flightgear.org/FGCom
|-
|for more detailed informations||http://wiki.flightgear.org/FGCOM_for_Windows
|-
|if you have problems with FGCOM||http://wiki.flightgear.org/FGCOM_Testing
|}

===Java V7===
Make sure you have installed at least Version 7 of Java. Verify and or Download the installation packages from: http://www.java.com/en/download/index.jsp

===OpenRadar===
For the currently available Prototype of OpenRadar see http://wagnerw.de/OpenRadar.zip. Extract the content of this ZIP to a place where it is easy to find. Make sure you have read and write permissions for that directory.
 
If you did already work with an OpenRadar installation you may want to
* RENAME your current OpenRadar-directory (i.e. to "OpenRadar-BU")
* then download and extract the new version into a newly created directory with the name of the old one (without the "-BU")
* now you can replace all data in the new "OpenRadar/data" directory with the ones in the "OpenRadar-BU/data"
** if you expect changes in the scenery etc. do not copy the the Airport (ICAO) directories
* delete the BU-version only after you are sure you verified that all your personal data were transferred, i.e. still accessible!
 
----
== '''''Startup''''' ==
Inside the downloaded OpenRadar base-directory you will find start-scripts. See
*for Windows: OpenRadar.bat
*for Linux: OpenRadar.sh
*for OSX: OpenRadar.jar
At Startup you will always be welcomed by the “OpenRadar – Welcome”. That window presents 2 TABs to define your preferences:
{|
|-
|[[File:OpenRadar - Welcome-Linux.png|thumb|left|Welcome tab on Linux]]||
[[File:OpenRadar- Settings-linux.png|thumb|left|Settings tab on Linux]]
|}
For all data there are standard values given as defaults. If you do change any values, they will be saved and presented to you during the next start.
 
If this is the very first time you start OpenRader, then you have to verify your “Settings” first, thus click onto the “Settings”-tab:

=== OpenRadar-Welcome - Settings ===
These settings are grouped into 3 parts:
===='''1) FGcom'''====
:OpenRadar can support up to 4 instances of FGcom in 2 ways:
:#It can start and control FgCom instances that operate in the background as sub-tasks of OpenRadar
:#or just control manually started FgCom-sessions.

:You select these modes of operation by the “'''FgComMode'''” selection:
 
:'''a) Internal:''' FGCom(s) are started and controlled internally by OpenRadar
::For this mode you have to define all available fields to tell OpenRader where your FGcom resides and what options shall be used:
::'''Path:''' Here you define where your FGcom is installed.
:::In the following some examples:

:::{| class="wikitable" style="text-align:center"
!type
!Windows
!Linux
!OSX
|-
|a standard installation || C:\Programs\FGcom ||/home/''YourName''/fgcom ||*)
|-
|on another disk || D:\FlighGear_2.6\FGcom || /media/''DiskName''/FGFS/fgcom ||*)
|-
|on a LAN-server || \\''ServerName''\Central\FGFS || /home/YourName//.gvfs/fgfs on nas-server/fgcom||*)
|}
::::*) for OSX we do not know – pls help us by defining it here or send a PersonalMessage to “Wagnerw” or “jomo”

::'''Executable:''' Here you define the program-name that shall be started

:::*For Windows: "fgcom.exe" or "anyName.bat"
:::*for Linux: "fgcom" or "anyName.sh"
:::*OSX: ''We do not know – pls help us by defining it here or send a PersonalMessage to “Wagnerw” or “jomo”''

::'''Server:''' There are 2 FGcom-servers available as of today:
::*delta384.server4you.de ''(we do suggest this one)''
::*fgcom.flightgear.org.uk
::'''Client:''' will always be “localhost” - unless you want to run FGcom on a different PC than OpenRadar.
::'''FGcom Ports:''' The here defined values are crucial for the operation because:
::*They are the only connection between the OpenRadar and FGcom. So you must define those the same in OpenRadar as well as in FGcom !!
::*They also define how many “Radio Units” (COM0, COM1, etc.) are generated within OpenRadar
::Simply provide a coma separated list of UDP Ports to be used by FGcom. But be warned: More than two are hard to handle!
:::::e.g. 16661,16662
 
:'''b) External:''' OpenRadar controls a manually started instance of FGcom - via the defined Port.
::For this one you only need to define where that FGcom is running and what the connecting port is. e.g.:
::*'''Client:''' locahost
::*'''FGcom Ports:''' 16661,16662 ''(if e.g. 2 FGcom instances were started)''
 
:'''c) OFF:''' No FGcom support
::That means that You do not want to work with FGcom during your ATC-session – thus you do not need to define any of the fields and there will not be defined any Radio (e.g. COM0) in OpenRadar. This mode is not suggested!

===='''2) FG Multiplayer'''====
:Here you find the server and connection port of FlightGears multiplayer server. It delivers the radar contact position informations and is used for chat. You won't have to change the settings, as long as the server won't change.
:In case you experience problems with the outside you may check and/or choose any "'''''Server'''''" that is listed in http://mpmap01.flightgear.org/mpstatus/: Look for a server nearest to your location that has a status of "OK" and shows the most "totals".
:'''''PLEASE NOTE:''''' The "'''''Client port'''''" is the port used by your computer to talk with that server. If you want to use FlightGears internal chat parallel to OpenRadar, you must use a different port than FlightGear. Because of that, the default port of OpenRadar is 5001 ''(in order to differentiate it to the 5000 used in FGFS)''.

===='''3) METAR'''====
:OpenRadar retrieves the weather information via METAR messages from a server in the INTERNET. This information is being displayed and used to calculate the usability of runways and the air speed of the radar contacts.
:If your airport is too small to be in that worldwide list, you can provide the code of another bigger airport with METAR data nearby in the sector.property file. But be aware that then your customers weather-settings may differ to yours, because they may use the standard FGFS-METAR-Source!

Please click on the verify button to have your settings checked!

===Select Airport===
This is always the first window that you will see after starting OpenRadar.
 

But at first, the available airport list (e.g. EDDF, KOAK,..) in the center will be empty. So at first define a location:
 

In order to '''define a new work-location''' simply enter the airport code (ICAO) or a part of the name into the search field and hit “search”: The list below then shows the results found in the airport database delivered with OpenRadar. There may be found several, so click on the one wanted and then activate the button "Download Scenery". Be patient and watch the Info-Field at the bottom: This first download of the required scenery will take some time before you see a "Ready"!
 

'''If the airport wanted does already exist''', it will be shown in the big center-field, with an "(exists)" at the end.
Double click onto the one wanted (or select it with one click and then click onto start) and you are in the ATC seat.
 
----

== '''''Operating''''' ==
[[File:OpenRadar Prototype.png|thumb|270px|Oakland international used in new OpenRadar]]
The OpenRadar main screen is divided into three regions:
#Top left you see the big '''Radar Map''' showing the airport, its surrounding, the navaids and the radar targets.
#Below it, bottom left, you see the '''MPchat Area''' for the FlightGear multiplayer chat feature.
#On the right side you see the '''Service Area''' with 4 subparts. From top to bottom those are
##'''Status Information'''
##'''COM-Radios''' ''(only if you have defined one or more)''
##'''Runway Manager''' to set up runways used
##the '''Flight Strip Manager''', where you can manage your radar targets.
Please notice in the following description the lightblue background at some items, indicating changes that may not yet be available in your version of the OpenRadar!

==== Radar Map ====
The radar map is the most complex part of OpenRadar, thus you have many options to zoom in on any area you are interested in. You can:
* set four functional zoom levels by clicking onto '''''GROUND, TOWER, APP and SECTOR.'''''
* zoom in and out using your mouse wheel ''(Mac: hold your right mousebutton pushed while moving over the radar-background in NorthWest respectively SouthEast)''
* adjust the map-center by dragging it with your mouse (click-hold left and drag)

* a double mouse-click onto the scope will move that point into the center of the scope
* a double right mouse-click will center the scope back to your location

You may assign any current settings to any of the 4 zoom levels (GROUND, TOWER, APP and SECTOR) by a right mouse-click onto the wanted level''
 
[[File:OpenRadar-Approach.png|thumb|right|250px|A typical tower operation]]
The '''''Radar-targets'''''
*do have a label attached with the following informations
:{| class="wikitable" style="text-align:center"
|-
|UID||heading direction
|-
|Flight Level||Airspeed
|}
*and are displayed in 5 different colors:
::''(See also the chapter "Flight Strip Manager")''
:{| class="wikitable"
|-
|align="center"|white||always the currently selected target, it's UID is also shown in the MPchat inputline (e.g. see "D-Leon" who just is getting his "clear to land")
|-
|align="middle"|blue||targets who's Flight-Stripe is placed to the left (e.g. see "Side" (just started) and "D-AHGM" just going to intercept the ILS: These 2 PLUS the white "D-LEON" are actively controlled right then!)
|-
|align="center"|yellow||targets who's Flight-Stripe is placed in the middle (e.g. could be assigned to "jomo2" as an indication that we wait for him to "wake up" soon - because then he may become a danger to others when taxiing uncontrolled)
|-
|align="center"|green||targets who's Flight-Stripe is placed to the right (e.g. see "jomo2" just parking - not actively controlled right now)
|-
|align="center"|gray||a neglected target or one for which there were no refresh data received from the MPserver for some time. In those cases the aircraft-type will be replaced by either "neglected" or by the time that elapsed since the last MPserver-update.
|}

[[File:OpenRadar-GND.png|thumb|right|250px|A GND layout with active PPN's]]
The radar map has so many details to display, that it is impossible to display all at once. Because of that we display details depending on the zoom level. For instance we hide Fixes and/or Runway Numbers etc. at a certain level of zoom. Thus OpenRadar features an adaptive detail level. In addition you can hide types of data by the following buttons:
{| class="wikitable"
|-
| '''''FIX''''' || Show/NoShow FIX's (they will automatically be set "NoShow" above distinct scale-settings!)
|-
| '''''NDB''''' || Show/NoShow NDB's (they will automatically be set "NoShow" above distinct scale-settings!)
|-
| '''''VOR''''' || Show/NoShow VOR's
|-
| '''''APT''''' || Show/NoShow Airports, inclusive their groundlayout (You may double-click onto a wanted airport and zoom in to see the layout)
|-
| '''''CIRC''''' || Show/NoShow circles at distinct distances around your present location. The distance between the circles shown depends on the chosen zoom-factor!
|-
| '''''GSH''''' || Show/NoShow Glide-Slope-Heights along the centerline of the runway for landings. They will automatically be set "NoShow" above distinct scale-settings!)
|-
| '''''PPN''''' || Show/NoShow the "Park Position Numbers", ''those may not yet be available on all airports!''. The PPNs will automatically be set "NoShow" above distinct scale-settings!)
|- style="background:lightblue"
| '''''StP''''' || Show/NoShow the "Selected (target) To Pointer" ''(doggy)'', an attachment to the mousepointer, showing some data about the relation of the selected target to the location of the mouse-pointer (similar to line 3 in the "Status Informations", see above)
|}

The "Runway Manager" (on the right side of the screen) allows you to define which runway(s) should be used for landing and/or starting. This status is shown with little green/red dots at the runway end. See in the picture "A typical tower operation" above:
*25L, 25R, and 18 are active (see the green and red dots at the ends)
*25L has in addition the blue approach center line and funnel, i.e. it is assigned for landings. This center line is drawn out for 100mi, helping you to align the arriving airplanes with the runway. In addition there is shown some kind of a funnel in a definable distance that may help you to align the planes coming via a base-leg for landing.

==== MPchat area ====
[[File:OpenRadar-MPchat.png|thumb|right|270px|The MPchat area]]
This area allows you to enter chat messages, view the chat history and filter it.
 
In the '''''entry-line''''' atop you define your messages to any radar-target by:
*Manually typing a message:
**A '''''left''''' mouse-click onto a Flight-Stripe or onto a Radar-Target will place the Target-UID at the beginning of the entry-line
**Then you may type or copy/past anything behind that - and send it out by ENTER
*Generate a standard message:
**A '''''right''''' mouse-click onto a Flight-Stripe or onto a Radar-Target will open a list with the available messages - select one with a left mouse-click
**That will place the message into the entry-line - you may now review/edit it and then send it out by ENTER
*OpenRadar will always set the ATC-name (as it appears on the very top of the service area - see the following chapter) in front of the message.

Below that entry-line is the '''''scrollable list''''' of exchanged MPchat-messages. In that list the messages related to the selected target are colored cyan. With the button "'''''SEL'''''" you set a filter to show only the messages related to the selected target. This filter will be reset as soon as you select another target - or by clicking onto "'''''ALL'''''".

You may enlarge that area by grabbing the upper edge with the left mouse-button and move it upward. Of course that will reduce the size of the radar-screen -- so use it with care!

==== Service Area ====
This column at the right side of the screen is for setting up the base-data for the operation, display needed data for traffic-guidance, and provide tools for guiding the pilots.

=====Status Informations=====
[[File:OpenRadar-Status_2.png|thumb|right|200px|The general Status Informations]]
This area shows in 4 lines the most used status-informations:
<ol><li>A text box that allows you to see and change your MP-callsign. So you can quickly change it, if a second ATC takes another role at the same airport (TW/APP/GND/RADAR, etc). At the right of it is placed a clock with the UTC-time. Because you probably will always have international guests you should refer to that modern "Coordinated Universal Time" (replacing nowadays the formerly used "Greenwich Mean Time" (GMT))
</li><li>In the second line you see the ICAO (the international Code for airports) and the long name of your airport. In addition you see on the right the currently selected radar contact (e.g. "jomo").
</li><li>The third line lets you predict several values for that "radar contact" (e.g. "jomo"). Whenever you place your mousepointer somewhere on the Radar Map, the third line will give you several informations about that target:
*StP = "Selection to Pointer": That is the compass direction between the target and the mousepointer, in both ways (TO/FROM)
*Miles: The distance between the target and the mouspointer.
*min: The time the target needs to get to that mousepointed area - '''IF''' the speed remains steady as is!! In this example there is given a "n/a" (not available) which most probably means the plane is not moving (may be parked)!
</li><li>The fourth line shows the mostly needed weather information '''Wind''', '''Pressure''' and '''Visibility'''. If you hover your mouse over it, you can see the complete last METAR-message received, in it's original form. (For help ref to http://wiki.flightgear.org/METAR#METAR). Please note that these values are similar to ATIS information: METAR directions is given in TRUE, ATIS in magnetic...
</li></ol>
====='''COM-Radios'''=====
[[File:OpenRadar-COM_2.png|thumb|right|200px|The COM-Setting (that can be none or up to 4)]]
According to the amount of FGcom-Ports you defined during setup (compare chapter "3.1.1 FGcom") you find here as many COM-Units (COM0 to max COM3). Each of them has a PopUp-List of Radio-frequencies available for the airport you are located on. You may
*choose a frequency out of the list by clicking onto the arrow at the right of the input-field
*or empty the field by a right mouseclick and enter any other frequency wanted.
At the right of that field you find a "Push To Talk" (PTT) button that you can operate by mouseclick -- or you can use the shortcuts given in the following table.
:{| class="wikitable" style="text-align:center"
!COMx
!left on keyboard
!right on keyboard
|-
|COM0||Ctrl||NumOff+Num0
|-
|COM1||SHIFT||NumOff+Num1
|-
|COM2|| ||NumOff+Num2
|-
|COM3|| ||NumOff+Num7
|}
Please watch the color change of the PTT buttons to know, when you can speak.

In case you operate the FGcom in the "'''''controlled by OpenRadar'''''" mode (compare the "FGComMode" in chapter "Startup"), then
*the radio label turns to red when FGcom is unable to establish a connection on this frequency. (Remember: OpenRadar has more frequencies available than FGcom knows of!!)
*you have an additional "'''''Restart'''''"-button: In case the communication becomes chopped or interrupted, you may click here to restart the FGCOM-program.
 
====='''Runway Settings'''=====
[[File:OpenRadar-Runways_2.png|thumb|right|200px|The Runway Manager]]
[[File:OpenRadar-Runway-Settings.png|thumb|right|200px|The Runway Manager Settings]]
Here you define the major variables for your airport operations: That are the assignments of the runways! For this purpose OpenRadar gives you a lot of precalculated and or default values to support your decisions findings and/or informations pilots may ask you about. See e.g. the pictures on the right:
*From top to bottom OpenRadar lists all runways available for that airport. For each runway you may define unique operating/display values. For these values see the picture "OpenRadar-Runway-Settings" below, e.g. see the 07C ''(you open that by a right mouseclick onto the runway-name (07C))'':
**In the header line you see left the now chosen runway to be edited, and at the left a button "'''''Copy to All'''''". With this switch you can copy the settings you make here to all the other runways - so e.g. for EDDF with its 8 settings you can save a lot! Only the values will be changed - all the selection-markers will remain as are in each unique setting table! These settings will then be saved separately for each unique airport in you private settings.
**With "'''''Main switches'''''" you define which functions may be available for that runway. Usually you can define for each runway as well a "Starting" as also a "Landing" function. In the given example for EDDF there is a complication: Per Law you are forbidden
:::to use runway 36 at all --> thus disable both lines: All data for that runway disappear
:::to use runway 18 for "Landing" only --> thus disable only "Landing": Just the Land-Option disappears
:::''(How do you know those details? Well, as a good ATC you prepare yourself by reading the official airport data (or look for something like e.g. http://en.wikipedia.org/wiki/Frankfurt_Airport, see on that page in the right column)''.
:*The "'''''Extended center line'''''" is the line you see in the above picture ''"A typical tower operation"'' at the right. If you want that line you may define how long it should be. Some people do not want it reaching over the whole screen. We suggest to limit it to the MPserver-range of 100 mi. It will only be visible for the runways defined for "Landing"!
:*The "'''''Distance markers'''''" are measurement markers on that "Extended center line". Here you define from were to were you want to have such markers ''(they may restrain your eyes if you use them all over!)''.
:*"'''''Vectoring and base leg'''''" define that funnel that you also see in the above picture ''"A typical tower operation"''. Also this will be shown only for the "Landing" runways.
:One tip to the handling of the "Landing" runways: Those are always shown in the "ATIS" message. If you define two (or even more) - in that "ATIS" message appear all those with the ILS data, etc.! So if you use mainly one we suggest to define only one - and activate more if you actually assign an additional one. Otherwise the pilots may become confused of that many informations and you yourself may have problems to differentiate which line the target should follow!

*From left to right you see the following informations for each runway (if available):
:*The runway-name
:*Check-boxes to define if that runway is used at all, may be just for landings or just for starts or for both. The program prevents you from assigning a runway in both directions (e.g. 25R and 07L)
:*A graphical display of the cross winds and and gusts: They are green from 0-5kn, orange 5-10kn and red above. When there are significant gusts that color-bar is divided into two. Typically the gusts then will be represented by the longer bar!
:*Above that bar you see the fractions of head- and crosswind. You may use especially the crosswind-fraction to warn pilots if those are => 10 kn! (Remember: You find the normal wind values in the METAR-data further up in the Status Informations)
:*To the right follows
::*in the upper line the exact runway heading (as needed for older type autopilots)
::*in the lower line the length and width of the runway in feet!
:*Then follow the ILS informations, if ILS is available for that runway. The data shown are: the ILS-beacon-name, the frequency, the glideslope, and the altitude at the threshold.

====='''Flight Strip Manager'''=====
[[File:OpenRadar-Stripes.png|thumb|right|200px|Handling the Flight-Stripes]]
Paper Flight Strips are the ATCs help to coordinate his traffic. In reality those strips contain many details about the flight, that we do not have (yet). Based on vertical space-limitations we have gathered the most critical informations into 2 lines, which are automatically initiated and controlled by the program. Those are:
:{| class="wikitable" style="text-align:center"
|-
|Target UID||Aircraft Type||colspan="2"|direction to it from ATC
|-
|distance to it||IAS+GND speed||Altitude (FL)||current heading
|}
In addition the user may add some more informations in additional lines. We urge you to reduce these additional lines to a minimum, because already with 2 lines the list will become that long, that you must scroll constantly! These additional lines will be saved as target-data and inserted each time a new stripe is created for that target! We suggest to maintain some target-data and some flight data for all frequent visitors. See as a suggestion several 3rd line examples:

"ILS VOR FGC NRW || GED MTR"
 This pilot knows how to use ILS, VOR, FGcom, the new Runway at EDDF || he is advised to approach via VOR GED and MTR.

"ILS VOR FGC NRW || KJFK 280° f510"
 This pilot also can use ILS, VOR, FGcom, NRW || and will depart to JFK on a straight course of 280° on FL510"

You are absolutely free to define your own codes and whatever. To do so
*enter/edit those data by opening the "'''''Note Editor'''''" with a right mouse-click ''(Mac: Alt + right mouse-click)'' while pressing onto the stripe
*add additional lines by Strg+ENTER (remember: Not more than 2, please!)
*Always exit that Editor with the ENTER-key in order to transfer the data to the stripe!
*At the bottom of this editor you can also select in which '''''additional language''''' the "standard commands" shall be transmitted to that target.

You can '''''manipulate the listing''''' of the flight strips:
*New radar-targets will always appear at the end of the list on the right side
*You can move the stripes in vertical order by drag and drop
*You can place them in three horizontal columns (left, middle and right) either by dragging them with the hold-down mouse button or by mouse-clicks left or right of the stripes ''(you may double-click to move directly from one side to the other)''
*with the "'''''AUTO'''''"-button at the upper edge of this area you can define that the stripes will be sorted automatically into groups according to their left/center/right position. This may be very irritating at first - so you may want to switch that "AUTO" off at first usages!
*The radar-targets will change their color according to the horizontal position of their stripe:
**the radar-targets for stripes at the right side will be '''green''' - these are all targets when initialized!
**the radar-targets for stripes in the center will be '''yellow'''
**the radar-targets for stripes at the left side will be '''cyan'''
On the radar-map the "cyan targets" will overlay the "yellow targets" - and the "yellow targets" will overlay the "green" ones!
 
You cannot change these combinations of color and position -- but you might define your own definition of what the positions mean! We suggest the following:
:'''''green''''' = right = initial position: Means not yet defined or not under my control (e.g. passing through on high altitude, is controlled by another ATC, etc.)
:'''''yellow''''' = center = I expect him to get under my control when in range (e.g. 60 mi), or he may be transfered to me by another ATC soon, etc. He may become a danger to the traffic controlled by me if he continues uncontrolled!
:'''''cyan''''' = left = under my control (light cyan when active in the MPchat input-line!)
Again: That is a proposal - you can define your on assignments!

You can apply the following mouse-actions onto the stripes as well as onto the radar-targets:
*a '''''single left''''' mouse-click '''''selects/activates''''' it, i.e. its radar-target becomes "light cyan" and its UID is set into the MPchat input-line. In addition
**its listed messages in the MPchat-list become colored cyan
**and the "doggy" at the mouse-pointer displays data about the relation between that target and the mouse-pointer
*a '''''double left''''' mouse-click helps you to find the target by highlighting the target on the scope. It also changes the radar-range to show both: The Target and your location. The selection of any of the "preset zoom levels" (GROUND, TOWER, APP, Sector) will reset the map-position again to its center!
*a '''''center''''' mouse-click opens the '''''Note Editor''''' (see above)
*a '''''right''''' mouse-click shows the dialog to choose pre-defined ATC messages to be sent to the current contact
*a '''''CTRL+left''''' mouse-click will define that target as '''''neglected'''''. Thus his radar-target will become just a light gray color, that will not overlay or otherwise disturb the radar-views.
 
----

== '''''Useful Features''''' ==
'''Radar Map'''
* On contact
:* '''left''' click '''selects''' and sets cursor into the chat input field
:* '''middle''' click opens the radar '''contact settings''' (ATC note and native language)
:* '''right''' click opens the '''ATC messages''' selection box

* '''left double''' click on map to '''center''' it '''on airport''' (return to airport)
* middle click on zoom level defines the current view as new center and zoom setting (stored in a file)
* a click on the texts, on the lower left, toggle display of FIX, NDB, VOR,...

'''Flight Strip Area'''
* On flight strip
:* '''left''' click '''selects''' the contact and sets cursor into the chat input field
:* '''middle''' click opens the radar '''contact settings''' (ATC note and native language)
:* '''right''' click opens the '''ATC messages''' selection box 

:* '''left double''' click '''centers''' radar '''map on''' the '''contact''' (to find contact)
:* '''CTRL+left''' click sets the contact to be '''neglected'''

* a click beside the flight strips moves the flight strips between the three columns (right, middle, left)

'''Runway area'''
* '''right''' click '''on runway number''' opens the '''runway settings dialog''' to define the centerline and vectoring settings
* If at least one runway is active you may '''double click''' the runway panel '''background to hide the inactive runways''' (frees space for flight strips)

'''Radios'''
* a '''right''' click '''on the frequency list''' changes the input to be '''editable''', so you can define the frequencies by yourself

''' Shortcuts '''
{| class="wikitable"
|-
! Shortcut !! Action
|-
| '''ESC''' || Close all open dialogs and cancel the text input (reset chat input field)

|-
| ALT + L || Toggle FGCom Log Window (only if you run FgCom started by OpenRadar)

|-
| '''Left CTRL''' || PTT Radio COM0 (if it has been activated via Port in Settings)
|-
| NUM off: Num0 || PTT Radio COM0 (if it has been activated via Port in Settings)
|-
| '''Left SHIFT''' || PTT Radio COM1 (if it has been activated via Port in Settings)
|-
| NUM off: Num1 || PTT Radio COM1 (if it has been activated via Port in Settings)
|-
| NUM off: Num2 || PTT Radio COM2 (if it has been activated via Port in Settings)
|-
| NUM off: Num3 || PTT Radio COM3 (if it has been activated via Port in Settings)
|}
 
----
== '''''Acknowledgments''''' ==
This project was founded and driven by Ralf Gerlich. Still today he is supporting it as a mentor.

And not to be forgotten: This project links different efforts of many people together. Thank you for your great work!

[[Category:OpenRadar|Guide]]

Concorde

2012-10-03T03:09:28Z

Stepfaw: oops spelling again

{{infobox Aircraft
|image = Concorde.png
|name = Concorde
|type = Airliner
|authors =
|fdm = JSBSim
|status = Development
|fgname = Concorde
|livery = British Airways
|liverydbid = 58
|download =
}}
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:''' <<<<To Be Defined>>>> (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
 

== '''Tutorial: A First Trip''' ==
In order to familiarize yourself with the basic functions of the Concorde, we describe in the following a short supersonic flight from Amsterdam (EHAM) to Rom (LIRF). That flight will take about 1.5 h (~30 Min climbing/accelerating, ~10 Min cruising at Mach 2.02 at 51.300 ft, and another 30 Min descending). We will use the 2D-panel so that you can concentrate on the functions, without having to loose time by searching/switching between many panels. Please see the given flight-data just as a reference – your own data will deviate, because they will depend a lot on actual weather, time delays, different approach/arrival routes, and very certainly on the amount of fuel: For this kind of plane the payload (max 13.380 kg) is just about neglectable compared to the fuel (max 95.680 kg).
 
Later you might want to test some original Concorde-flight-plans in the directory: FlightGear/Aircraft/Concorde/Doc/*.fp.
See also some short comments/instructions in chapter “Example” of: FlightGear/Aircraft/Concorde/ReadmeConcorde-jbsim.txt
 
In the Appendix you find a [[#Recorded Flight Data EHAM --> LIRF|table of all significant flight data of one of my test-flights]] – just in case you wonder about some unusual behavior of the Concorde, that you might discover during that flight – especially during the climb-out! Many of those I did not believe at first myself!
=== ''Preflight'' ===
* '''Runways:''' Check minimums: for Takeoff 11.200 ft (3.500 m), for Landing 7.300 ft (2.300 m)
* '''Fuel-level:''' Set via: Menu → Concorde → Fuel:
** if changed: Restart FGFS or goto “Engineering Panel” (Ctrl+E) and press the Reset (the small black button in the center, between “TOTAL FUEL REM” and “A/C WEIGHT”
* '''Altimeter:''' Set the actual QNH (Nautical Height) into '''(25)'''. Set altimeter according to:
** as given by ATC/ATIS
** or to the airport height
** or look up the Hg-value in: Menu → Environment → Weather Conditions
** or check the metar data in MPmap
* '''Emergency return:''' Set VOR/ILS + Radials into NAV1 '''(19)''' & '''(21)''', in case something happens during Take-Off etc.
* '''INS-Target:''' Input Target(s) (e.g. just LIRF into "Menu → Autopilot → Rout Manager")
* '''COM's, VOR's, NDB's:''' Set as needed. For the target airport you have enough time to do so during descent!
* '''Altitude:''' Just preset the next needed “Altitude Acquired” '''(62)''' (e.g. the final AA=51.300)
* '''Nose 5°:''' set with '''(49)'''
 
'''If ATC is available you need approval prior doing the following:'''
* '''Start only engines 2+3 for taxiing''' (that is the official pilot-manual, I usually forget to switch off 1+4 when the model started up with all 4 engines running already!)
* '''Release “Parking Break”:''' Key “Alt b” and check instruments '''(34, 35, 36)'''
* '''Push back:''' key “Ctrl+B” and check the blue indicators in '''(40)''' (off = normal, blinking = in transit, blue = reverse). The “in transit” takes rather long compared to other planes (up to 10 sec)!
 
=== ''Taxi'' ===
* '''Taxi''' according to Tower instructions (or UNICOM-announcement)
* '''switch on all 4 engines''' at Hold-Position (e.g. by clicking onto the corresponding “HP VALVE” in the 2D Engineering panel (“Upper S”)
* '''Verify trimming (53)'''
* '''Verify Nose = 5 degrees (49)'''
* if tower has given a max altitude for departure preset AA = maxAlt (this would have priority above the already set max “Altitude Acquired”=51.300.
* '''max Speed:''' preset max Speed to 250 kt/h '''(62)''' for up to 10.000 feet
 

=== Takeoff ===
From Rolling to 10.000 ft it takes about 5 Min and brings you just about 3 mi closer to the target (if starting from runway 27 at EHAM, which is about at 90° to the target (INS ~170°) - as during my test-flights)!
 
*
{|
|-
|[[File:Concorde-Head-Lights.jpg|250px]]
|
* '''Main Landing Light on''' when “Cleared to Start” (see the 4 left switches on the panel above the windshield: 2 extender '''(1)''' + 2 lights '''(2)'''). Notice this panel also for later: When warnings have been set – you may spot and reset those on this panel by mouse-click onto the warning-light.
|}
 
* '''Start timer'''
* '''AB on:''' Set Afterburner on (ctrl+F, verify CTY-indicator '''(13)''' blinking)
* '''Activate T/O (37)'''
* '''Release brakes:''' (alt+b) → “Rolling”:
** '''V1 165 kt/h''' (must Take-off)
** '''VR 195 kt/h''' (start rotating)
** '''Pitch 12.5 degrees''' at rotation (check Attitude Indicator in '''(17)''')
** '''Gear Up''' (g) at ~200 ft
** '''V2: 220 kt/h''' (minimum speed to hold)

* '''Climb out on Runway-Heading:'''
** '''AP on:''' activates also '''HH+PH''' ''("Autopilot" activates "Heading Hold" and "Pitch-Hold")'' that will hold the current attitude until we have time to complete all the other settings. When flying with 3D-panels make sure you use the left or right AP, according to who is the "Pilot in Command"!
** '''FD on + AT on:''' Activate both FD's (Flight-Director) and and both AT's (Auto-Throttle) ''(in 2D panel only 1 each!)''
** '''IA on:''' (Indicated Airspeed Acquire) restricts the speed to the preset 250 kt/h and then switches IH on (IAS Hold) and IA off (hold 250 till 10.000 ft)
** '''Nose Up''' 2 times “Alt-Gr + ]”
** '''AB off''' (Afterburner - Ctrl+F) verify CTY '''(13)''' off
** '''IA+IH off, VS on → ~ 4.000 FPM:''' If allowed by ATC use the maximum climb-rate while maintaining 250 kt/h max. Thus control the Speed by the "Rate of Climb" '''VS''' (Vertical Speed Hold) and adjust the “to be hold speed” by the vertical speed indicator '''(20)''' (hot-spots at the center of upper and lower ¼ border).
::'''Warning:''' With “IA off” the throttle must be manually moved completely off and on again, in order to ensure it is set in the max throttle position!
* '''After OK from Tower go onto Course to (first) target'''
** '''IN on''' (for Instrument Navigation System) or '''VL on''' (for VOR navigation) or '''TH on''' (for True Heading (manual)), or similar. This will switch '''HH off''' automatically. I had set ROM (LIRF) into the Rout-Manager, so I chose '''IN on'''.
 
=== ''Climb to Cruise Altitude'' ===
The climb from 10.000 ft to 51.300 ft and Mach 2.02 will take about 25 Min and 240 miles:
* '''Above 10.000'''
* '''Main Landing Light off''' above 10.000 ft (Panel above windshield, left corner)
* '''Accelerate''' to max. allowed speed (yellow pointer in '''(8)''')
** '''AB on:''' Use the Afterburner to speed up
** '''FPM → 3.500:''' reduce the FPM '''(20)''' to increase the actual speed (white pointer in '''(8)''')
** '''AFT+ENGI on:''' Switch the fuel pumping to “AFT” as soon as the indicator in the C/MG '''(31)''' reaches about the center between allowed Min and Max (the sooner the better!). Directly after that switch on also "Engi" to continue pumping when Tank 11 is full. (compare chapter "[[#Balancing by Fuel-Pumping|Balancing by Fuel-Pumping]]")
** '''AB off:''' As soon as the “White Pointer” merges with the “Yellow Pointer” (in '''(8)''') switch the Afterburner off again.
* '''MAX Speed == Actual Speed''' (FPM → 3.000 varying): After the actual speed is about equal to the maximum allowed CAS '''(8)''' (i.e. the white pointer is completely covered by the yellow pointer – but NOT above it!), begin holding the allowed maximum CAS by varying the FPM (with '''(20)'''). The closer you stay at the maximum speed the less altitude you gain and accordingly the better you control the M/CG!
** '''watch M/CG''' between marks in '''(31)'''. Control this by the Mach-Meter '''(8b)'''.
::If the Speed gets above the M/CG maximum, it generally means that you are too high for the actual speed or your balancing by fuel tanking does not work properly (compare chapter "[[#Balancing by Fuel-Pumping|Balancing by Fuel-Pumping]]"). In that case reduce the speed by throttle (not by increasing FPM – because you are too high already) – keep a minimum of 500 to 750 FPM. It may take quite some time to recover!
* watch for '''Warnings:''' Hi Frequency = Stall Warning, Clicking = Over Speed
* '''18.000 ft:''' set altimeter to QNH = 29.92 (=1005 hPa) (Nautical Height = Flight-Levels)
* '''AA on for FL513:''' This ensures that you do not overshoot the allowed maximum of 51.300 ft!
* '''Mach 0.95 (~ FL280): AB ON again, FPM → ~ 4.000 reducing constantly to ~500'''. The support of the Afterburner will increase the speed drastically, so be prepared to increase the FPM accordingly - and then reduce it again slowly.
{|
|-
|
:[[File:Forward-Fuel-mgt.jpg|200px]]
|
* '''activate Tank 10:''' Now is a good time to activate tank 10 - before it might get hectic! Goto Engineering Panel (Ctrl+E), switch the Tank 10 valves open and return again with (Ctrl+E). (compare chapter "[[#Balancing by Fuel-Pumping|Balancing by Fuel-Pumping]]")
|}
* '''Mach 1.1 (~ FL 330), FPM → ~2.000:''' somewhere above Mach 1.1 drag reduces significantly – be prepared to increase the climb rate again drastically to about ~2.000, then again reducing to ~1.000
{|
|-
|
:[[File:Concorde-MCG-Cross.png|150px]]
|
:''Somewhere in this area it may become difficult to keep the speed inside the M/CG-markers (without reducing speed drastically!). Be sure that does not happen before Mach 1.5 – otherwise it may not be possible to correct it later in level flight, and thus you either never reach Mach 2.02 or at least the drag will result in significantly increased fuel consumption.''
|}
* '''Mach 1.3 (FL~360):''' Air-Intakes open automatically, providing more thrust. Be prepared to increase FPM ~2.500 again
* '''Mach 1.7 (~FL470):''' '''AB OFF''' again (Stop afterburner (ctrl+F))
* '''ensure 513 is preset in (62)''' and '''AA''' is active !!
* '''FL513:''' System will automatically switch from '''AA''' to '''AH'''
* '''MACH 2.02: MH on''' ''(Mach Hold)'' + both '''AT on''' ''(Auto-Throttle)''
* continue Fuel-Pumping until M/CG is centered, otherwise you fly with much drag which will increase your fuel consumption
* check Target Airport, Weather, Runways, etc.
 
=== ''Supersonic descent'' ===
The descent from FL513 and Mach 2.02 will take about 30 Min and/or 250-270 miles:
* '''Between 270-250 miles to target: MH off + Throttle off''', decelerate to '''350 kt/h''' at FL513
::'''WARNING:''' make sure you move the throttle once completely forward and then to idle – otherwise it may stay engaged in the previous condition!
::'''AT''' might start blinking because the throttle is idle!
* '''watch M/CG:''' you may need fuel '''FORW'''ard very soon! During the whole descent you may need to switch '''FORW on/off''' several times!
* '''at 350 kt/h --> VS on''' (AH off), start descent with''' FPM 2.000 (20)'''
** preset '''AA''' to FL410, then prime AA (Altitude Acquire)
* '''at FL410''' hold Altitude and decelerate to '''Mach 0.95''' with min. throttle
* '''at Mach 0.95''' continue descending with 2000 FPM ('''VS on''' enforces '''AA off''' automatically)
** preset '''AA''' = 10.000, predefining your minimum altitude prior to approach. You may vary the FPM according to your needs
* '''below 18.000 ft set QFE in (25)''' (field elevation pressure), check ATIS (or ask ATC or check weather of the airport in MPmap). Be aware that this QFE might be very different to the one set at the beginning of the flight! And it should be correct, if you plan to land with Autopilot (support)!
 
=== ''Approach'' ===
* '''~40 miles from threshold:''' prepare the approach to the expected Runway – or define a STAR-approach – or ...
* '''for a normal "straight in approach":'''
** '''Set VOR''' into NAV2 '''(64)''' & ILS into NAV1 '''(55)''', also set the radials according to the expected runway into '''(58), (59), (60), (61)'''.
** Switch '''(56) to INS''' (Inertial Navigation System)
:[[File:Concorde-INS-Radial-3.png|400px|left]]
:'''Align your flightpath with runway:''' ''if e.g. you want to land on runway 25, but the direct INS-radial (yellow pointer) actually points to 25.8°, then you should start correcting the INS-radial to 25°:''
* '''set True Heading (58)''' to e.g. 28.5° and activate TH.
::'''''Watch it:''' The TH marker (now on “N”) does not follow because the instrument shows INS values! The actual TH values you would see only when you switch the INS-display to VOR with switch (56) – which we do not do, because we want to watch the INS-pointer!)''
* While the '''TH''' of the plane moves slowly to the preset TH=28.5° (i.e. to the right), the INS-pointer moves slowly towards 25° (to the left). And the vertical deviation bar starts showing that the actual heading of the plane does not match the direct path to the INS-target.
** Continue with that TH heading until the INS-pointer points directly onto '''25°, then IN on''' (forces TH off). The plane will turn and approach the target on that radial. The deviation bar will center
** ''(Of course you also could use a VOR if there is one midfield of the airport and if it reaches that far – the nice thing about INS is: It always is available (even 20.000 miles away and always is located in the center of the target.)''

{| border="1"
|-
|
:Max Speed for Visor down and/or Nose 5°:
| 325 kt/h (M 0.8)
|-
|
:Max. Speed for “Nose Down” 12.5°:
| 270 kt/h AND below 20.000 ft
|-
|
:Max Speed for Gear down & Landing-light:
| 270 kt/h (M 0.7)
|}

* '''Below 10.000 ft''' → 250 kt/h maximum speed
** '''Main Landing Light on''' (over windshield at left)
** '''Nose down 5°'''
* '''contact ATC and follow advise, or:'''
** ~'''25 miles from threshold:''' descent to 2.000 ft and hold 220 kt/h
** '''Approach Radial:''' Make sure you are close to the radial of the active runway, either by above INS-settings or by standard VOR-procedures
** '''VL on (VOR1 Lock):''' Check '''(11)''' (The indications in '''(18)''' and '''(17)''' are not usable because they still show INS – not VOR!): Only after the yellow needle shows the ILS-localizer active switch '''VL on''' (forcing IN off).
** '''RAD/INS → RAD (56):''' That will display the VOR1 in '''(18)''' and '''(17)''' (''of course also '''(4)''' must be switched to DEV1! Remember: Only DEV1 can be used for Radial flying!)''. There should be needed only minor corrections to center the localizer, and those are done now by the Autopilot!
** '''GL on (Glideslope):''' Watch '''(9)''' and/or '''(21)''' for a stable confirmation that the DME reading is stable and wait till the Glideslope indicator (in '''(17)''' and/or '''(18)''') is centered, only then activate''' GL'''. ''''Otherwise the plane might perform a very drastic climb or descent in order to acquire the Glideslope altitude!''''
** '''~10 mi from threshold:''' keep 200 kt/h (You may still have a gross-weight far above the maximum landing weight – so keep speed a little higher than usual!)
** '''Follow the ILS beam'''
 

=== ''Landing'' ===
* Watch "Altitude to Ground" in '''(23)'''
* Landing Gear (G) ''at about "Outer Marker" (32) blue''
* Nose 12.5 degrees (full down)
* 750 ft AGL: switch '''AP off''' (Autopilot with Ctrl+D) and '''AT off''' (Auto-throttle)
* hold '''pitch at 10°''' - adjust descent-rate with speed/throttle
* VREF 162 kt/h for touchdown (rather stay a little faster!)
 
=== ''Taxiing'' ===
* Nose up to 5°
* Switch Off engines 2 + 3
* get clearance to taxi
 
=== ''Parking'' ===
* Switch off engines
* Nose and visor up, as weather seal.

== '''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.
<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.

 
=== '''Recorded Flight Data EHAM --> LIRF''' ===
{| border = "1" align="center"
|+EHAM - LIRF, start at EHAM RW 18C with wind 290@4, 1008 hPa
! Time !! FL !! FPM !! T/CG !! TAS !! MaxMach !! Mach !! CAS !! Miles !! Fuel !! remark
|-
!Start
|-
| 00:00:00 || 0 || 0 >> 2000 || --- || --- || --- || --- || --- || 700 || 93,000 || AB on
|-
| 00:02:15 || 20 || 2000 >> 4000 || 0.9 || 260 || 0,55 || --- || 250 || 702 || 91,400 || AB off
|-
| 00:04:53 || 100 || <3500> || 0.9 || 294 || 0,7 || 0.46 || 250 || 697 || 90,156 || AB on
|-
| 00:06:00 || 140 || <3000> || 0.9 || 388 || 0,77 || 0.61 || 316 || 689 || 88,824 || AFT Pumps on
|-
| 00:06:54 || 170 || 3000 >> 750 || 0.9 || 494 || 0.8 || 0.8 || 391 || 683 || 88,085 || AB off
|-
| 00:09:55 || 240 || 4000 >> 400 || 1 || 569 || 0.95 || 0.95 || 406 || 656 || 86,291 || AB on
|-
| 00:13:10 || 330 || 2000 >> 1000 || 1.12 || 637 || 1.12 || 1.12 ||405 || 624 || 83,617 || WATCH: Steep Speed Increase
|-
| 00:16:00 || 360 || 2500 >> 2000 || 1.25 || 746 || 1.33 || 1.33 ||451 || 592 || 81,505 || WATCH: again increase to FPM 2500ppp
|-
| 00:19:25 || 440 || 2000 || 1.4 || 992 || 1.7 || 1.7 || 525 || 543 || 78,451 || AB off
|-
| 00:23:45 || 513 || 0 || 1.49 ||1160 || 2.02 || 2.02 || 524 || 464 || 75,925 ||
|-
!descent
|-
| 00:00:00 || 513 || 0 || 1.2 || 1160 || 2.02 || 202 || 524 || 270 || 70,056
|-
| 00:04:23 || 513 || 2000 || 1.2 || 783 || --- || 1.37 || 350 || 200 || 69367
|-
| 00:09:51 || 410 || 0 || 2.15-1.1 || 542 || --- || 0.95 || 266 || 138 || 68650
|-
| 00:25:19 || 100 || 2000 || 0.7-1.12 || 245 || --- || --- || 250 || 32 || 67700
|-
!landed
|-
| 00:37:47 || || || || || || || || || 65257|| Landed –-> at terminal
|-
|}

=== Concorde unique Keys ===
{| class="prettytable"
!Key
!Function
|-
|[ ]
|raise/lower nose
|-
|left/right
|autopilot heading
|-
|
|floating view left/right
|-
|up/down
|increase/decrease autopilot altitude
|-
|
|floating view front/aft
|-
|home/end
|increase/decrease autopilot altitude (slow)
|-
|
|floating view front/aft (fast)
|-
|page up/down
|increase/decrease autothrottle speed
|-
|
|floating view up/down
|-
|a/A
|speed-up
|-
|alt-b
|emergency brakes
|-
|f
|full cockpit
|-
|alt-g
|gear standby
|-
|alt-n
|nose standby
|-
|q
|quit speed-up
|-
|S
|swaps 2D panel
|-
|y
|toggle yoke
|-
|ctrl-A
|altitude acquire
|-
|ctrl-D
|disconnect autopilot
|-
|ctrl-E
|engineer view
|-
|ctrl-F
|reheat (afterburner)
|-
|ctrl-G
|glide slope
|-
|ctrl-H
|heading hold
|-
|ctrl-I
|menu
|-
|ctrl-J
|copilot view
|-
|ctrl-K
|observer (floating) view
|-
|ctrl-N
|nav 1 hold
|-
|ctrl-O
|overhead view
|-
|ctrl-P
|pitch hold
|-
|ctrl-R
|radio frequencies
|-
|shift-ctrl-R
|crew text
|-
|ctrl-S
|speed acquire
|-
|ctrl-T
|altitude hold
|-
|ctrl-W
|steward (floating) view
|-
|shift-ctrl-X
|restore floating view
|-
|ctrl-Z
|virtual crew
|}

{{British Aerospace}}
{{British Aircraft Corporation}}

[[de:Concorde]]

[[Category:Airliners]]

Concorde

2012-10-03T03:07:45Z

Stepfaw: spelling

{{infobox Aircraft
|image = Concorde.png
|name = Concorde
|type = Airliner
|authors =
|fdm = JSBSim
|status = Development
|fgname = Concorde
|livery = British Airways
|liverydbid = 58
|download =
}}
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:''' <<<<To Be Defined>>>> (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
 

== '''Tutorial: A First Trip''' ==
In order to familiarize yourself with the basic functions of the Concorde, we describe in the following a short supersonic flight from Amsterdam (EHAM) to Rom (LIRF). That flight will take about 1.5 h (~30 Min climbing/accelerating, ~10 Min cruising at Mach 2.02 at 51.300 ft, and another 30 Min descending). We will use the 2D-panel so that you can concentrate on the functions, without having to loose time by searching/switching between many panels. Please see the given flight-data just as a reference – your own data will deviate, because they will depend a lot on actual weather, time delays, different approach/arrival routes, and very certainly on the amount of fuel: For this kind of plane the payload (max 13.380 kg) is just about neglectable compared to the fuel (max 95.680 kg).
 
Later you might want to test some original Concorde-flight-plans in the directory: FlightGear/Aircraft/Concorde/Doc/*.fp.
See also some short comments/instructions in chapter “Example” of: FlightGear/Aircraft/Concorde/ReadmeConcorde-jbsim.txt
 
In the Appendix you find a [[#Recorded Flight Data EHAM --> LIRF|table of all significant flight data of one of my test-flights]] – just in case you wonder about some unusual behavior of the Concorde, that you might discover during that flight – especially during the climb-out! Many of those I did not believe at first myself!
=== ''Preflight'' ===
* '''Runways:''' Check minimums: for Takeoff 11.200 ft (3.500 m), for Landing 7.300 ft (2.300 m)
* '''Fuel-level:''' Set via: Menu → Concorde → Fuel:
** if changed: Restart FGFS or goto “Engineering Panel” (Ctrl+E) and press the Reset (the small black button in the center, between “TOTAL FUEL REM” and “A/C WEIGHT”
* '''Altimeter:''' Set the actual QNH (Nautical Height) into '''(25)'''. Set altimeter according to:
** as given by ATC/ATIS
** or to the airport height
** or look up the Hg-value in: Menu → Environment → Weather Conditions
** or check the metar data in MPmap
* '''Emergency return:''' Set VOR/ILS + Radials into NAV1 '''(19)''' & '''(21)''', in case something happens during Take-Off etc.
* '''INS-Target:''' Input Target(s) (e.g. just LIRF into "Menu → Autopilot → Rout Manager")
* '''COM's, VOR's, NDB's:''' Set as needed. For the target airport you have enough time to do so during descent!
* '''Altitude:''' Just preset the next needed “Altitude Acquired” '''(62)''' (e.g. the final AA=51.300)
* '''Nose 5°:''' set with '''(49)'''
 
'''If ATC is available you need approval prior doing the following:'''
* '''Start only engines 2+3 for taxiing''' (that is the official pilot-manual, I usually forget to switch off 1+4 when the model started up with all 4 engines running already!)
* '''Release “Parking Break”:''' Key “Alt b” and check instruments '''(34, 35, 36)'''
* '''Push back:''' key “Ctrl+B” and check the blue indicators in '''(40)''' (off = normal, blinking = in transit, blue = reverse). The “in transit” takes rather long compared to other planes (up to 10 sec)!
 
=== ''Taxi'' ===
* '''Taxi''' according to Tower instructions (or UNICOM-announcement)
* '''switch on all 4 engines''' at Hold-Position (e.g. by clicking onto the corresponding “HP VALVE” in the 2D Engineering panel (“Upper S”)
* '''Verify trimming (53)'''
* '''Verify Nose = 5 degrees (49)'''
* if tower has given a max altitude for departure preset AA = maxAlt (this would have priority above the already set max “Altitude Acquired”=51.300.
* '''max Speed:''' preset max Speed to 250 kt/h '''(62)''' for up to 10.000 feet
 

=== Takeoff ===
From Rolling to 10.000 ft it takes about 5 Min and brings you just about 3 mi closer to the target (if starting from runway 27 at EHAM, which is about at 90° to the target (INS ~170°) - as during my test-flights)!
 
*
{|
|-
|[[File:Concorde-Head-Lights.jpg|250px]]
|
* '''Main Landing Light on''' when “Cleared to Start” (see the 4 left switches on the panel above the windshield: 2 extender '''(1)''' + 2 lights '''(2)'''). Notice this panel also for later: When warnings have been set – you may spot and reset those on this panel by mouse-click onto the warning-light.
|}
 
* '''Start timer'''
* '''AB on:''' Set Afterburner on (ctrl+F, verify CTY-indicator '''(13)''' blinking)
* '''Activate T/O (37)'''
* '''Release brakes:''' (alt+b) → “Rolling”:
** '''V1 165 kt/h''' (must Take-off)
** '''VR 195 kt/h''' (start rotating)
** '''Pitch 12.5 degrees''' at rotation (check Attitude Indicator in '''(17)''')
** '''Gear Up''' (g) at ~200 ft
** '''V2: 220 kt/h''' (minimum speed to hold)

* '''Climb out on Runway-Heading:'''
** '''AP on:''' activates also '''HH+PH''' ''("Autopilot" activates "Heading Hold" and "Pitch-Hold")'' that will hold the current attitude until we have time to complete all the other settings. When flying with 3D-panels make sure you use the left or right AP, according to who is the "Pilot in Command"!
** '''FD on + AT on:''' Activate both FD's (Flight-Director) and and both AT's (Auto-Throttle) ''(in 2D panel only 1 each!)''
** '''IA on:''' (Indicated Airspeed Acquire) restricts the speed to the preset 250 kt/h and then switches IH on (IAS Hold) and IA off (hold 250 till 10.000 ft)
** '''Nose Up''' 2 times “Alt-Gr + ]”
** '''AB off''' (Afterburner - Ctrl+F) verify CTY '''(13)''' off
** '''IA+IH off, VS on → ~ 4.000 FPM:''' If allowed by ATC use the maximum climb-rate while maintaining 250 kt/h max. Thus control the Speed by the "Rate of Climb" '''VS''' (Vertical Speed Hold) and adjust the “to be hold speed” by the vertical speed indicator '''(20)''' (hot-spots at the center of upper and lower ¼ border).
::'''Warning:''' With “IA off” the throttle must be manually moved completely off and on again, in order to ensure it is set in the max throttle position!
* '''After OK from Tower go onto Course to (first) target'''
** '''IN on''' (for Instrument Navigation System) or '''VL on''' (for VOR navigation) or '''TH on''' (for True Heading (manual)), or similar. This will switch '''HH off''' automatically. I had set ROM (LIRF) into the Rout-Manager, so I chose '''IN on'''.
 
=== ''Climb to Cruise Altitude'' ===
The climb from 10.000 ft to 51.300 ft and Mach 2.02 will take about 25 Min and 240 miles:
* '''Above 10.000'''
* '''Main Landing Light off''' above 10.000 ft (Panel above windshield, left corner)
* '''Accelerate''' to max. allowed speed (yellow pointer in '''(8)''')
** '''AB on:''' Use the Afterburner to speed up
** '''FPM → 3.500:''' reduce the FPM '''(20)''' to increase the actual speed (white pointer in '''(8)''')
** '''AFT+ENGI on:''' Switch the fuel pumping to “AFT” as soon as the indicator in the C/MG '''(31)''' reaches about the center between allowed Min and Max (the sooner the better!). Directly after that switch on also "Engi" to continue pumping when Tank 11 is full. (compare chapter "[[#Balancing by Fuel-Pumping|Balancing by Fuel-Pumping]]")
** '''AB off:''' As soon as the “White Pointer” merges with the “Yellow Pointer” (in '''(8)''') switch the Afterburner off again.
* '''MAX Speed == Actual Speed''' (FPM → 3.000 varying): After the actual speed is about equal to the maximum allowed CAS '''(8)''' (i.e. the white pointer is completely covered by the yellow pointer – but NOT above it!), begin holding the allowed maximum CAS by varying the FPM (with '''(20)'''). The closer you stay at the maximum speed the less altitude you gain and accordingly the better you control the M/CG!
** '''watch M/CG''' between marks in '''(31)'''. Control this by the Mach-Meter '''(8b)'''.
::If the Speed gets above the M/CG maximum, it generally means that you are too high for the actual speed or your balancing by fuel tanking does not work properly (compare chapter "[[#Balancing by Fuel-Pumping|Balancing by Fuel-Pumping]]"). In that case reduce the speed by throttle (not by increasing FPM – because you are too high already) – keep a minimum of 500 to 750 FPM. It may take quite some time to recover!
* watch for '''Warnings:''' Hi Frequency = Stall Warning, Clicking = Over Speed
* '''18.000 ft:''' set altimeter to QNH = 29.92 (=1005 hPa) (Nautical Height = Flight-Levels)
* '''AA on for FL513:''' This ensures that you do not overshoot the allowed maximum of 51.300 ft!
* '''Mach 0.95 (~ FL280): AB ON again, FPM → ~ 4.000 reducing constantly to ~500'''. The support of the Afterburner will increase the speed drastically, so be prepared to increase the FPM accordingly - and then reduce it again slowly.
{|
|-
|
:[[File:Forward-Fuel-mgt.jpg|200px]]
|
* '''activate Tank 10:''' Now is a good time to activate tank 10 - before it might get hectic! Goto Engineering Panel (Ctrl+E), switch the Tank 10 valves open and return again with (Ctrl+E). (compare chapter "[[#Balancing by Fuel-Pumping|Balancing by Fuel-Pumping]]")
|}
* '''Mach 1.1 (~ FL 330), FPM → ~2.000:''' somewhere above Mach 1.1 drag reduces significantly – be prepared to increase the climb rate again drastically to about ~2.000, then again reducing to ~1.000
{|
|-
|
:[[File:Concorde-MCG-Cross.png|150px]]
|
:''Somewhere in this area it may become difficult to keep the speed inside the M/CG-markers (without reducing speed drastically!). Be sure that does not happen before Mach 1.5 – otherwise it may not be possible to correct it later in level flight, and thus you either never reach Mach 2.02 or at least the drag will result in significantly increased fuel consumption.''
|}
* '''Mach 1.3 (FL~360):''' Air-Intakes open automatically, providing more thrust. Be prepared to increase FPM ~2.500 again
* '''Mach 1.7 (~FL470):''' '''AB OFF''' again (Stop afterburner (ctrl+F))
* '''ensure 513 is preset in (62)''' and '''AA''' is active !!
* '''FL513:''' System will automatically switch from '''AA''' to '''AH'''
* '''MACH 2.02: MH on''' ''(Mach Hold)'' + both '''AT on''' ''(Auto-Throttle)''
* continue Fuel-Pumping until M/CG is centered, otherwise you fly with much drag which will increase your fuel consumption
* check Target Airport, Weather, Runways, etc.
 
=== ''Supersonic descent'' ===
The descent from FL513 and Mach 2.02 will take about 30 Min and/or 250-270 miles:
* '''Between 270-250 miles to target: MH off + Throttle off''', decelerate to '''350 kt/h''' at FL513
::'''WARNING:''' make sure you move the throttle once completely forward and then to idle – otherwise it may stay engaged in the previous condition!
::'''AT''' might start blinking because the throttle is idle!
* '''watch M/CG:''' you may need fuel '''FORW'''ard very soon! During the whole descent you may need to switch '''FORW on/off''' several times!
* '''at 350 kt/h --> VS on''' (AH off), start descent with''' FPM 2.000 (20)'''
** preset '''AA''' to FL410, then prime AA (Altitude Acquire)
* '''at FL410''' hold Altitude and decelerate to '''Mach 0.95''' with min. throttle
* '''at Mach 0.95''' continue descending with 2000 FPM ('''VS on''' enforces '''AA off''' automatically)
** preset '''AA''' = 10.000, predefining your minimum altitude prior to approach. You may vary the FPM according to your needs
* '''below 18.000 ft set QFE in (25)''' (field elevation pressure), check ATIS (or ask ATC or check weather of the airport in MPmap). Be aware that this QFE might be very different to the one set at the beginning of the flight! And it should be correct, if you plan to land with Autopilot (support)!
 
=== ''Approach'' ===
* '''~40 miles from threshold:''' prepare the approach to the expected Runway – or define a STAR-approach – or ...
* '''for a normal "straight in approach":'''
** '''Set VOR''' into NAV2 '''(64)''' & ILS into NAV1 '''(55)''', also set the radials according to the expected runway into '''(58), (59), (60), (61)'''.
** Switch '''(56) to INS''' (Inertial Navigation System)
:[[File:Concorde-INS-Radial-3.png|400px|left]]
:'''Align your flightpath with runway:''' ''if e.g. you want to land on runway 25, but the direct INS-radial (yellow pointer) actually points to 25.8°, then you should start correcting the INS-radial to 25°:''
* '''set True Heading (58)''' to e.g. 28.5° and activate TH.
::'''''Watch it:''' The TH marker (now on “N”) does not follow because the instrument shows INS values! The actual TH values you would see only when you switch the INS-display to VOR with switch (56) – which we do not do, because we want to watch the INS-pointer!)''
* While the '''TH''' of the plane moves slowly to the preset TH=28.5° (i.e. to the right), the INS-pointer moves slowly towards 25° (to the left). And the vertical deviation bar starts showing that the actual heading of the plane does not match the direct path to the INS-target.
** Continue with that TH heading until the INS-pointer points directly onto '''25°, then IN on''' (forces TH off). The plane will turn and approach the target on that radial. The deviation bar will center
** ''(Of course you also could use a VOR if there is one midfield of the airport and if it reaches that far – the nice thing about INS is: It always is available (even 20.000 miles away and always is located in the center of the target.)''

{| border="1"
|-
|
:Max Speed for Visor down and/or Nose 5°:
| 325 kt/h (M 0.8)
|-
|
:Max. Speed for “Nose Down” 12.5°:
| 270 kt/h AND below 20.000 ft
|-
|
:Max Speed for Gear down & Landing-light:
| 270 kt/h (M 0.7)
|}

* '''Below 10.000 ft''' → 250 kt/h maximum speed
** '''Main Landing Light on''' (over windshield at left)
** '''Nose down 5°'''
* '''contact ATC and follow advise, or:'''
** ~'''25 miles from threshold:''' descent to 2.000 ft and hold 220 kt/h
** '''Approach Radial:''' Make sure you are close to the radial of the active runway, either by above INS-settings or by standard VOR-procedures
** '''VL on (VOR1 Lock):''' Check '''(11)''' (The indications in '''(18)''' and '''(17)''' are not usable because they still show INS – not VOR!): Only after the yellow needle shows the ILS-localizer active switch '''VL on''' (forcing IN off).
** '''RAD/INS → RAD (56):''' That will display the VOR1 in '''(18)''' and '''(17)''' (''of course also '''(4)''' must be switched to DEV1! Remember: Only DEV1 can be used for Radial flying!)''. There should be needed only minor corrections to center the localizer, and those are done now by the Autopilot!
** '''GL on (Glideslope):''' Watch '''(9)''' and/or '''(21)''' for a stable confirmation that the DME reading is stable and wait till the Glideslope indicator (in '''(17)''' and/or '''(18)''') is centered, only then activate''' GL'''. ''''Otherwise the plane might perform a very drastic climb or descent in order to acquire the Glideslope altitude!''''
** '''~10 mi from threshold:''' keep 200 kt/h (You may still have a gross-weight far above the maximum landing weight – so keep speed a little higher than usual!)
** '''Follow the ILS beam'''
 

=== ''Landing'' ===
* Watch "Altitude to Ground" in '''(23)'''
* Landing Gear (G) ''at about "Outer Marker" (32) blue''
* Nose 12.5 degrees (full down)
* 750 ft AGL: switch '''AP off''' (Autopilot with Ctrl+D) and '''AT off''' (Auto-throttle)
* hold '''pitch at 10°''' - adjust descent-rate with speed/throttle
* VREF 162 kt/h for touchdown (rather stay a little faster!)
 
=== ''Taxiing'' ===
* Nose up to 5°
* Switch Off engines 2 + 3
* get clearance to taxi
 
=== ''Parking'' ===
* Switch off engines
* Nose and visor up, as weather seal.

== '''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', swicth 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.
<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.

 
=== '''Recorded Flight Data EHAM --> LIRF''' ===
{| border = "1" align="center"
|+EHAM - LIRF, start at EHAM RW 18C with wind 290@4, 1008 hPa
! Time !! FL !! FPM !! T/CG !! TAS !! MaxMach !! Mach !! CAS !! Miles !! Fuel !! remark
|-
!Start
|-
| 00:00:00 || 0 || 0 >> 2000 || --- || --- || --- || --- || --- || 700 || 93,000 || AB on
|-
| 00:02:15 || 20 || 2000 >> 4000 || 0.9 || 260 || 0,55 || --- || 250 || 702 || 91,400 || AB off
|-
| 00:04:53 || 100 || <3500> || 0.9 || 294 || 0,7 || 0.46 || 250 || 697 || 90,156 || AB on
|-
| 00:06:00 || 140 || <3000> || 0.9 || 388 || 0,77 || 0.61 || 316 || 689 || 88,824 || AFT Pumps on
|-
| 00:06:54 || 170 || 3000 >> 750 || 0.9 || 494 || 0.8 || 0.8 || 391 || 683 || 88,085 || AB off
|-
| 00:09:55 || 240 || 4000 >> 400 || 1 || 569 || 0.95 || 0.95 || 406 || 656 || 86,291 || AB on
|-
| 00:13:10 || 330 || 2000 >> 1000 || 1.12 || 637 || 1.12 || 1.12 ||405 || 624 || 83,617 || WATCH: Steep Speed Increase
|-
| 00:16:00 || 360 || 2500 >> 2000 || 1.25 || 746 || 1.33 || 1.33 ||451 || 592 || 81,505 || WATCH: again increase to FPM 2500ppp
|-
| 00:19:25 || 440 || 2000 || 1.4 || 992 || 1.7 || 1.7 || 525 || 543 || 78,451 || AB off
|-
| 00:23:45 || 513 || 0 || 1.49 ||1160 || 2.02 || 2.02 || 524 || 464 || 75,925 ||
|-
!descent
|-
| 00:00:00 || 513 || 0 || 1.2 || 1160 || 2.02 || 202 || 524 || 270 || 70,056
|-
| 00:04:23 || 513 || 2000 || 1.2 || 783 || --- || 1.37 || 350 || 200 || 69367
|-
| 00:09:51 || 410 || 0 || 2.15-1.1 || 542 || --- || 0.95 || 266 || 138 || 68650
|-
| 00:25:19 || 100 || 2000 || 0.7-1.12 || 245 || --- || --- || 250 || 32 || 67700
|-
!landed
|-
| 00:37:47 || || || || || || || || || 65257|| Landed –-> at terminal
|-
|}

=== Concorde unique Keys ===
{| class="prettytable"
!Key
!Function
|-
|[ ]
|raise/lower nose
|-
|left/right
|autopilot heading
|-
|
|floating view left/right
|-
|up/down
|increase/decrease autopilot altitude
|-
|
|floating view front/aft
|-
|home/end
|increase/decrease autopilot altitude (slow)
|-
|
|floating view front/aft (fast)
|-
|page up/down
|increase/decrease autothrottle speed
|-
|
|floating view up/down
|-
|a/A
|speed-up
|-
|alt-b
|emergency brakes
|-
|f
|full cockpit
|-
|alt-g
|gear standby
|-
|alt-n
|nose standby
|-
|q
|quit speed-up
|-
|S
|swaps 2D panel
|-
|y
|toggle yoke
|-
|ctrl-A
|altitude acquire
|-
|ctrl-D
|disconnect autopilot
|-
|ctrl-E
|engineer view
|-
|ctrl-F
|reheat (afterburner)
|-
|ctrl-G
|glide slope
|-
|ctrl-H
|heading hold
|-
|ctrl-I
|menu
|-
|ctrl-J
|copilot view
|-
|ctrl-K
|observer (floating) view
|-
|ctrl-N
|nav 1 hold
|-
|ctrl-O
|overhead view
|-
|ctrl-P
|pitch hold
|-
|ctrl-R
|radio frequencies
|-
|shift-ctrl-R
|crew text
|-
|ctrl-S
|speed acquire
|-
|ctrl-T
|altitude hold
|-
|ctrl-W
|steward (floating) view
|-
|shift-ctrl-X
|restore floating view
|-
|ctrl-Z
|virtual crew
|}

{{British Aerospace}}
{{British Aircraft Corporation}}

[[de:Concorde]]

[[Category:Airliners]]

Concorde

2012-10-03T02:55:28Z

Stepfaw: Grammar and clean up

{{infobox Aircraft
|image = Concorde.png
|name = Concorde
|type = Airliner
|authors =
|fdm = JSBSim
|status = Development
|fgname = Concorde
|livery = British Airways
|liverydbid = 58
|download =
}}
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:''' <<<<To Be Defined>>>> (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
 

== '''Tutorial: A First Trip''' ==
In order to familiarize yourself with the basic functions of the Concorde, we describe in the following a short supersonic flight from Amsterdam (EHAM) to Rom (LIRF). That flight will take about 1.5 h (~30 Min climbing/accelerating, ~10 Min cruising at Mach 2.02 at 51.300 ft, and another 30 Min descending). We will use the 2D-panel so that you can concentrate on the functions, without having to loose time by searching/switching between many panels. Please see the given flight-data just as a reference – your own data will deviate, because they will depend a lot on actual weather, time delays, different approach/arrival routes, and very certainly on the amount of fuel: For this kind of plane the payload (max 13.380 kg) is just about neglectable compared to the fuel (max 95.680 kg).
 
Later you might want to test some original Concorde-flight-plans in the directory: FlightGear/Aircraft/Concorde/Doc/*.fp.
See also some short comments/instructions in chapter “Example” of: FlightGear/Aircraft/Concorde/ReadmeConcorde-jbsim.txt
 
In the Appendix you find a [[#Recorded Flight Data EHAM --> LIRF|table of all significant flight data of one of my test-flights]] – just in case you wonder about some unusual behavior of the Concorde, that you might discover during that flight – especially during the climb-out! Many of those I did not believe at first myself!
=== ''Preflight'' ===
* '''Runways:''' Check minimums: for Takeoff 11.200 ft (3.500 m), for Landing 7.300 ft (2.300 m)
* '''Fuel-level:''' Set via: Menu → Concorde → Fuel:
** if changed: Restart FGFS or goto “Engineering Panel” (Ctrl+E) and press the Reset (the small black button in the center, between “TOTAL FUEL REM” and “A/C WEIGHT”
* '''Altimeter:''' Set the actual QNH (Nautical Height) into '''(25)'''. Set altimeter according to:
** as given by ATC/ATIS
** or to the airport height
** or look up the Hg-value in: Menu → Environment → Weather Conditions
** or check the metar data in MPmap
* '''Emergency return:''' Set VOR/ILS + Radials into NAV1 '''(19)''' & '''(21)''', in case something happens during Take-Off etc.
* '''INS-Target:''' Input Target(s) (e.g. just LIRF into "Menu → Autopilot → Rout Manager")
* '''COM's, VOR's, NDB's:''' Set as needed. For the target airport you have enough time to do so during descent!
* '''Altitude:''' Just preset the next needed “Altitude Acquired” '''(62)''' (e.g. the final AA=51.300)
* '''Nose 5°:''' set with '''(49)'''
 
'''If ATC is available you need approval prior doing the following:'''
* '''Start only engines 2+3 for taxiing''' (that is the official pilot-manual, I usually forget to switch off 1+4 when the model started up with all 4 engines running already!)
* '''Release “Parking Break”:''' Key “Alt b” and check instruments '''(34, 35, 36)'''
* '''Push back:''' key “Ctrl+B” and check the blue indicators in '''(40)''' (off = normal, blinking = in transit, blue = reverse). The “in transit” takes rather long compared to other planes (up to 10 sec)!
 
=== ''Taxi'' ===
* '''Taxi''' according to Tower instructions (or UNICOM-announcement)
* '''switch on all 4 engines''' at Hold-Position (e.g. by clicking onto the corresponding “HP VALVE” in the 2D Engineering panel (“Upper S”)
* '''Verify trimming (53)'''
* '''Verify Nose = 5 degrees (49)'''
* if tower has given a max altitude for departure preset AA = maxAlt (this would have priority above the already set max “Altitude Acquired”=51.300.
* '''max Speed:''' preset max Speed to 250 kt/h '''(62)''' for up to 10.000 feet
 

=== Takeoff ===
From Rolling to 10.000 ft it takes about 5 Min and brings you just about 3 mi closer to the target (if starting from runway 27 at EHAM, which is about at 90° to the target (INS ~170°) - as during my test-flights)!
 
*
{|
|-
|[[File:Concorde-Head-Lights.jpg|250px]]
|
* '''Main Landing Light on''' when “Cleared to Start” (see the 4 left switches on the panel above the windshield: 2 extender '''(1)''' + 2 lights '''(2)'''). Notice this panel also for later: When warnings have been set – you may spot and reset those on this panel by mouse-click onto the warning-light.
|}
 
* '''Start timer'''
* '''AB on:''' Set Afterburner on (ctrl+F, verify CTY-indicator '''(13)''' blinking)
* '''Activate T/O (37)'''
* '''Release brakes:''' (alt+b) → “Rolling”:
** '''V1 165 kt/h''' (must Take-off)
** '''VR 195 kt/h''' (start rotating)
** '''Pitch 12.5 degrees''' at rotation (check Attitude Indicator in '''(17)''')
** '''Gear Up''' (g) at ~200 ft
** '''V2: 220 kt/h''' (minimum speed to hold)

* '''Climb out on Runway-Heading:'''
** '''AP on:''' activates also '''HH+PH''' ''("Autopilot" activates "Heading Hold" and "Pitch-Hold")'' that will hold the current attitude until we have time to complete all the other settings. When flying with 3D-panels make sure you use the left or right AP, according to who is the "Pilot in Command"!
** '''FD on + AT on:''' Activate both FD's (Flight-Director) and and both AT's (Auto-Throttle) ''(in 2D panel only 1 each!)''
** '''IA on:''' (Indicated Airspeed Acquire) restricts the speed to the preset 250 kt/h and then switches IH on (IAS Hold) and IA off (hold 250 till 10.000 ft)
** '''Nose Up''' 2 times “Alt-Gr + ]”
** '''AB off''' (Afterburner - Ctrl+F) verify CTY '''(13)''' off
** '''IA+IH off, VS on → ~ 4.000 FPM:''' If allowed by ATC use the maximum climb-rate while maintaining 250 kt/h max. Thus control the Speed by the "Rate of Climb" '''VS''' (Vertical Speed Hold) and adjust the “to be hold speed” by the vertical speed indicator '''(20)''' (hot-spots at the center of upper and lower ¼ border).
::'''Warning:''' With “IA off” the throttle must be manually moved completely off and on again, in order to ensure it is set in the max throttle position!
* '''After OK from Tower go onto Course to (first) target'''
** '''IN on''' (for Instrument Navigation System) or '''VL on''' (for VOR navigation) or '''TH on''' (for True Heading (manual)), or similar. This will switch '''HH off''' automatically. I had set ROM (LIRF) into the Rout-Manager, so I chose '''IN on'''.
 
=== ''Climb to Cruise Altitude'' ===
The climb from 10.000 ft to 51.300 ft and Mach 2.02 will take about 25 Min and 240 miles:
* '''Above 10.000'''
* '''Main Landing Light off''' above 10.000 ft (Panel above windshield, left corner)
* '''Accelerate''' to max. allowed speed (yellow pointer in '''(8)''')
** '''AB on:''' Use the Afterburner to speed up
** '''FPM → 3.500:''' reduce the FPM '''(20)''' to increase the actual speed (white pointer in '''(8)''')
** '''AFT+ENGI on:''' Switch the fuel pumping to “AFT” as soon as the indicator in the C/MG '''(31)''' reaches about the center between allowed Min and Max (the sooner the better!). Directly after that switch on also "Engi" to continue pumping when Tank 11 is full. (compare chapter "[[#Balancing by Fuel-Pumping|Balancing by Fuel-Pumping]]")
** '''AB off:''' As soon as the “White Pointer” merges with the “Yellow Pointer” (in '''(8)''') switch the Afterburner off again.
* '''MAX Speed == Actual Speed''' (FPM → 3.000 varying): After the actual speed is about equal to the maximum allowed CAS '''(8)''' (i.e. the white pointer is completely covered by the yellow pointer – but NOT above it!), begin holding the allowed maximum CAS by varying the FPM (with '''(20)'''). The closer you stay at the maximum speed the less altitude you gain and accordingly the better you control the M/CG!
** '''watch M/CG''' between marks in '''(31)'''. Control this by the Mach-Meter '''(8b)'''.
::If the Speed gets above the M/CG maximum, it generally means that you are too high for the actual speed or your balancing by fuel tanking does not work properly (compare chapter "[[#Balancing by Fuel-Pumping|Balancing by Fuel-Pumping]]"). In that case reduce the speed by throttle (not by increasing FPM – because you are too high already) – keep a minimum of 500 to 750 FPM. It may take quite some time to recover!
* watch for '''Warnings:''' Hi Frequency = Stall Warning, Clicking = Over Speed
* '''18.000 ft:''' set altimeter to QNH = 29.92 (=1005 hPa) (Nautical Height = Flight-Levels)
* '''AA on for FL513:''' This ensures that you do not overshoot the allowed maximum of 51.300 ft!
* '''Mach 0.95 (~ FL280): AB ON again, FPM → ~ 4.000 reducing constantly to ~500'''. The support of the Afterburner will increase the speed drastically, so be prepared to increase the FPM accordingly - and then reduce it again slowly.
{|
|-
|
:[[File:Forward-Fuel-mgt.jpg|200px]]
|
* '''activate Tank 10:''' Now is a good time to activate tank 10 - before it might get hectic! Goto Engineering Panel (Ctrl+E), switch the Tank 10 valves open and return again with (Ctrl+E). (compare chapter "[[#Balancing by Fuel-Pumping|Balancing by Fuel-Pumping]]")
|}
* '''Mach 1.1 (~ FL 330), FPM → ~2.000:''' somewhere above Mach 1.1 drag reduces significantly – be prepared to increase the climb rate again drastically to about ~2.000, then again reducing to ~1.000
{|
|-
|
:[[File:Concorde-MCG-Cross.png|150px]]
|
:''Somewhere in this area it may become difficult to keep the speed inside the M/CG-markers (without reducing speed drastically!). Be sure that does not happen before Mach 1.5 – otherwise it may not be possible to correct it later in level flight, and thus you either never reach Mach 2.02 or at least the drag will result in significantly increased fuel consumption.''
|}
* '''Mach 1.3 (FL~360):''' Air-Intakes open automatically, providing more thrust. Be prepared to increase FPM ~2.500 again
* '''Mach 1.7 (~FL470):''' '''AB OFF''' again (Stop afterburner (ctrl+F))
* '''ensure 513 is preset in (62)''' and '''AA''' is active !!
* '''FL513:''' System will automatically switch from '''AA''' to '''AH'''
* '''MACH 2.02: MH on''' ''(Mach Hold)'' + both '''AT on''' ''(Auto-Throttle)''
* continue Fuel-Pumping until M/CG is centered, otherwise you fly with much drag which will increase your fuel consumption
* check Target Airport, Weather, Runways, etc.
 
=== ''Supersonic descent'' ===
The descent from FL513 and Mach 2.02 will take about 30 Min and/or 250-270 miles:
* '''Between 270-250 miles to target: MH off + Throttle off''', decelerate to '''350 kt/h''' at FL513
::'''WARNING:''' make sure you move the throttle once completely forward and then to idle – otherwise it may stay engaged in the previous condition!
::'''AT''' might start blinking because the throttle is idle!
* '''watch M/CG:''' you may need fuel '''FORW'''ard very soon! During the whole descent you may need to switch '''FORW on/off''' several times!
* '''at 350 kt/h --> VS on''' (AH off), start descent with''' FPM 2.000 (20)'''
** preset '''AA''' to FL410, then prime AA (Altitude Acquire)
* '''at FL410''' hold Altitude and decelerate to '''Mach 0.95''' with min. throttle
* '''at Mach 0.95''' continue descending with 2000 FPM ('''VS on''' enforces '''AA off''' automatically)
** preset '''AA''' = 10.000, predefining your minimum altitude prior to approach. You may vary the FPM according to your needs
* '''below 18.000 ft set QFE in (25)''' (field elevation pressure), check ATIS (or ask ATC or check weather of the airport in MPmap). Be aware that this QFE might be very different to the one set at the beginning of the flight! And it should be correct, if you plan to land with Autopilot (support)!
 
=== ''Approach'' ===
* '''~40 miles from threshold:''' prepare the approach to the expected Runway – or define a STAR-approach – or ...
* '''for a normal "straight in approach":'''
** '''Set VOR''' into NAV2 '''(64)''' & ILS into NAV1 '''(55)''', also set the radials according to the expected runway into '''(58), (59), (60), (61)'''.
** Switch '''(56) to INS''' (Inertial Navigation System)
:[[File:Concorde-INS-Radial-3.png|400px|left]]
:'''Align your flightpath with runway:''' ''if e.g. you want to land on runway 25, but the direct INS-radial (yellow pointer) actually points to 25.8°, then you should start correcting the INS-radial to 25°:''
* '''set True Heading (58)''' to e.g. 28.5° and activate TH.
::'''''Watch it:''' The TH marker (now on “N”) does not follow because the instrument shows INS values! The actual TH values you would see only when you switch the INS-display to VOR with switch (56) – which we do not do, because we want to watch the INS-pointer!)''
* While the '''TH''' of the plane moves slowly to the preset TH=28.5° (i.e. to the right), the INS-pointer moves slowly towards 25° (to the left). And the vertical deviation bar starts showing that the actual heading of the plane does not match the direct path to the INS-target.
** Continue with that TH heading until the INS-pointer points directly onto '''25°, then IN on''' (forces TH off). The plane will turn and approach the target on that radial. The deviation bar will center
** ''(Of course you also could use a VOR if there is one midfield of the airport and if it reaches that far – the nice thing about INS is: It always is available (even 20.000 miles away and always is located in the center of the target.)''

{| border="1"
|-
|
:Max Speed for Visor down and/or Nose 5°:
| 325 kt/h (M 0.8)
|-
|
:Max. Speed for “Nose Down” 12.5°:
| 270 kt/h AND below 20.000 ft
|-
|
:Max Speed for Gear down & Landing-light:
| 270 kt/h (M 0.7)
|}

* '''Below 10.000 ft''' → 250 kt/h maximum speed
** '''Main Landing Light on''' (over windshield at left)
** '''Nose down 5°'''
* '''contact ATC and follow advise, or:'''
** ~'''25 miles from threshold:''' descent to 2.000 ft and hold 220 kt/h
** '''Approach Radial:''' Make sure you are close to the radial of the active runway, either by above INS-settings or by standard VOR-procedures
** '''VL on (VOR1 Lock):''' Check '''(11)''' (The indications in '''(18)''' and '''(17)''' are not usable because they still show INS – not VOR!): Only after the yellow needle shows the ILS-localizer active switch '''VL on''' (forcing IN off).
** '''RAD/INS → RAD (56):''' That will display the VOR1 in '''(18)''' and '''(17)''' (''of course also '''(4)''' must be switched to DEV1! Remember: Only DEV1 can be used for Radial flying!)''. There should be needed only minor corrections to center the localizer, and those are done now by the Autopilot!
** '''GL on (Glideslope):''' Watch '''(9)''' and/or '''(21)''' for a stable confirmation that the DME reading is stable and wait till the Glideslope indicator (in '''(17)''' and/or '''(18)''') is centered, only then activate''' GL'''. ''''Otherwise the plane might perform a very drastic climb or descent in order to acquire the Glideslope altitude!''''
** '''~10 mi from threshold:''' keep 200 kt/h (You may still have a gross-weight far above the maximum landing weight – so keep speed a little higher than usual!)
** '''Follow the ILS beam'''
 

=== ''Landing'' ===
* Watch "Altitude to Ground" in '''(23)'''
* Landing Gear (G) ''at about "Outer Marker" (32) blue''
* Nose 12.5 degrees (full down)
* 750 ft AGL: switch '''AP off''' (Autopilot with Ctrl+D) and '''AT off''' (Auto-throttle)
* hold '''pitch at 10°''' - adjust descent-rate with speed/throttle
* VREF 162 kt/h for touchdown (rather stay a little faster!)
 
=== ''Taxiing'' ===
* Nose up to 5°
* Switch Off engines 2 + 3
* get clearance to taxi
 
=== ''Parking'' ===
* Switch off engines
* Nose and visor up, as weather seal.

== '''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', swith 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.
<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.

 
=== '''Recorded Flight Data EHAM --> LIRF''' ===
{| border = "1" align="center"
|+EHAM - LIRF, start at EHAM RW 18C with wind 290@4, 1008 hPa
! Time !! FL !! FPM !! T/CG !! TAS !! MaxMach !! Mach !! CAS !! Miles !! Fuel !! remark
|-
!Start
|-
| 00:00:00 || 0 || 0 >> 2000 || --- || --- || --- || --- || --- || 700 || 93,000 || AB on
|-
| 00:02:15 || 20 || 2000 >> 4000 || 0.9 || 260 || 0,55 || --- || 250 || 702 || 91,400 || AB off
|-
| 00:04:53 || 100 || <3500> || 0.9 || 294 || 0,7 || 0.46 || 250 || 697 || 90,156 || AB on
|-
| 00:06:00 || 140 || <3000> || 0.9 || 388 || 0,77 || 0.61 || 316 || 689 || 88,824 || AFT Pumps on
|-
| 00:06:54 || 170 || 3000 >> 750 || 0.9 || 494 || 0.8 || 0.8 || 391 || 683 || 88,085 || AB off
|-
| 00:09:55 || 240 || 4000 >> 400 || 1 || 569 || 0.95 || 0.95 || 406 || 656 || 86,291 || AB on
|-
| 00:13:10 || 330 || 2000 >> 1000 || 1.12 || 637 || 1.12 || 1.12 ||405 || 624 || 83,617 || WATCH: Steep Speed Increase
|-
| 00:16:00 || 360 || 2500 >> 2000 || 1.25 || 746 || 1.33 || 1.33 ||451 || 592 || 81,505 || WATCH: again increase to FPM 2500ppp
|-
| 00:19:25 || 440 || 2000 || 1.4 || 992 || 1.7 || 1.7 || 525 || 543 || 78,451 || AB off
|-
| 00:23:45 || 513 || 0 || 1.49 ||1160 || 2.02 || 2.02 || 524 || 464 || 75,925 ||
|-
!descent
|-
| 00:00:00 || 513 || 0 || 1.2 || 1160 || 2.02 || 202 || 524 || 270 || 70,056
|-
| 00:04:23 || 513 || 2000 || 1.2 || 783 || --- || 1.37 || 350 || 200 || 69367
|-
| 00:09:51 || 410 || 0 || 2.15-1.1 || 542 || --- || 0.95 || 266 || 138 || 68650
|-
| 00:25:19 || 100 || 2000 || 0.7-1.12 || 245 || --- || --- || 250 || 32 || 67700
|-
!landed
|-
| 00:37:47 || || || || || || || || || 65257|| Landed –-> at terminal
|-
|}

=== Concorde unique Keys ===
{| class="prettytable"
!Key
!Function
|-
|[ ]
|raise/lower nose
|-
|left/right
|autopilot heading
|-
|
|floating view left/right
|-
|up/down
|increase/decrease autopilot altitude
|-
|
|floating view front/aft
|-
|home/end
|increase/decrease autopilot altitude (slow)
|-
|
|floating view front/aft (fast)
|-
|page up/down
|increase/decrease autothrottle speed
|-
|
|floating view up/down
|-
|a/A
|speed-up
|-
|alt-b
|emergency brakes
|-
|f
|full cockpit
|-
|alt-g
|gear standby
|-
|alt-n
|nose standby
|-
|q
|quit speed-up
|-
|S
|swaps 2D panel
|-
|y
|toggle yoke
|-
|ctrl-A
|altitude acquire
|-
|ctrl-D
|disconnect autopilot
|-
|ctrl-E
|engineer view
|-
|ctrl-F
|reheat (afterburner)
|-
|ctrl-G
|glide slope
|-
|ctrl-H
|heading hold
|-
|ctrl-I
|menu
|-
|ctrl-J
|copilot view
|-
|ctrl-K
|observer (floating) view
|-
|ctrl-N
|nav 1 hold
|-
|ctrl-O
|overhead view
|-
|ctrl-P
|pitch hold
|-
|ctrl-R
|radio frequencies
|-
|shift-ctrl-R
|crew text
|-
|ctrl-S
|speed acquire
|-
|ctrl-T
|altitude hold
|-
|ctrl-W
|steward (floating) view
|-
|shift-ctrl-X
|restore floating view
|-
|ctrl-Z
|virtual crew
|}

{{British Aerospace}}
{{British Aircraft Corporation}}

[[de:Concorde]]

[[Category:Airliners]]

User:Stepfaw

2012-09-26T00:21:57Z

Stepfaw:

{{User
|name = Stepfaw
|location = Canada
|age = 50
|job = N/A
|interests = Composing and correcting Wiki articles. Intercepting Flights or Formation flying.
|callsign = sjf
|favourite = B1900D, Concorde
}}

First Language English, Second Language French.

Presently working on Aiports in Canada in the Wiki and with TaxiDraw.
[[Image:TGA_2-12-11_YSCB_1.jpg|thumb|left|800px|Transgear Airway Event Febuary 12, 2011]]
[[Image:TGA_2-12-11_YSCB_2.jpg|thumb|left|800px|Transgear Airway Event Febuary 12, 2011]]
[[Image:TGA_2-12-11_YSCB_3.jpg|thumb|left|800px|Transgear Airway Event Febuary 12, 2011]]
[[Image:TGA_2-12-11_YSCB_4.jpg|thumb|left|800px|Transgear Airway Event Febuary 12, 2011]]
[[Image:TGA_2-12-11_YSCB_5.jpg|thumb|left|800px|Transgear Airway Event Febuary 12, 2011]]
[[Image:TGA_2-12-11_YSCB_6.jpg|thumb|left|800px|Transgear Airway Event Febuary 12, 2011]]
[[Image:TGA_2-12-11_YSCB_7.jpg|thumb|left|800px|Transgear Airway Event Febuary 12, 2011]]
[[Image:TGA_2-12-11_YSCB_8.jpg|thumb|left|800px|Transgear Airway Event Febuary 12, 2011]]
[[Image:TGA_2-12-11_YSCB_9.jpg|thumb|left|800px|Transgear Airway Event Febuary 12, 2011]]
[[Image:TGA_2-12-11_YSCB_10.jpg|thumb|left|800px|Transgear Airway Event Febuary 12, 2011]]

Frankfurt am Main Airport

2011-03-03T03:33:00Z

Stepfaw: Added runway section.

{{stub}}

{{infobox Airport
|name = Frankfurt am Main Airport
|image =EDDF1.jpg
|alt =
|iata =FRA
|icao =EDDF
|type =Public
|city =Frankfurt am Main
|owner =Fraport
|website =http://www.frankfurt-airport.com/
|runway= 07L/25R
|length= 4000 m
|material= Asphalt
|runway2= 07R/25L
|length2= 4000 m
|material2= Asphalt
|runway3= 18
|length3= 4000 m
|material3= Concrete
}}

== EDDF (Frankfurt Scenery) ==
Back to [[Germany|Germany Scenery Overview]]

{|
| Autor: || Christian Schmitt and others
|-
|-
| Where to get: || Many yet unpublished updates are collected on papillon81's GIT repo: http://gitorious.org/papillon81/flightgear-custom-scenery
|}

=== Description ===
'''Frankfurt am Main Airport''' is also known as '''Flughafen Frankfurt am Main or Rhein-Main-Flughafen''' and is the international airport that serves the city of Frankfurt am Main. It is located 12 km (7.5mi) southwest of downtown Frankfurt am Main, and is the busiest airport in Germany. This airport is complete with respect to the Terminals. However, as there are constant changes going on in reality, work is never really finished. In addition to the airport the scenery also contains a fair amount of skyscrapers of Frankfurt and some other details. The version available through terrasync is reasonably up-to date.

The version in the GIT repo contains some future changes (new runway, buildings under construction). In addition to that there is a new custom scenery with many details for the area around the airport.

==Runways==
EDDF has 3 runways. The runways are positioned approximately parallel. Two of them are east-west, and the other is north-south. All three runways are the same length at 4,000 meters.

===Runway 07L-25R===
[[Instrument Landing System]] is available for runway 07L, tune you NAV radio to 110.55 with a heading of 069.614. [[Instrument Landing System]] is available for runway 25R, tune you NAV radio to 109.50 with a heading of 249.568.

===Runway 07R-25L===
[[Instrument Landing System]] is available for runway 07R, tune you NAV radio to 110.95 with a heading of 069.619. [[Instrument Landing System]] is available for runway 25L, tune you NAV radio to 110.70 with a heading of 249.571.

===Runway 18-36===
Runway 18-36 is the only runway that does not have [[Instrument Landing System]] available.

==External links==
* [http://www.vacc-sag.org/airport/EDDF Airport Diagrams]

[[Category:Airports in Germany]]

Frankfurt am Main Airport

2011-03-02T02:39:36Z

Stepfaw: minor Description Improvements

File:TGA 2-12-11 YSCB 10.jpg

2011-02-12T19:24:52Z

Stepfaw:

User:Stepfaw

2011-02-12T19:21:27Z

Stepfaw:

{| style="background: white; width: 280px; font-size: 90%; text-align: left; border: 1px silver solid; border-collapse: collapse; margin-left:1em;" cellpadding="3" border="1" align="right"
! colspan="6" style="text-align: center; background-color: #0f7a71; color: white; font-size: larger;" | {{{StepFaw}}}
|-

{{#if:{{{location|<noinclude>x</noinclude>}}}|
{{!}} colspan="3" {{!}} Location: Canada
{{!}} colspan="3" {{!}} {{{Location|}}} }}
|-
{{#if:{{{age|<noinclude>x</noinclude>}}}|
{{!}} colspan="3" {{!}} Age: 50
{{!}} colspan="3" {{!}} {{{age|}}} }}
|-
{{#if:{{{job|<noinclude>x</noinclude>}}}|
{{!}} colspan="3" {{!}} Job: N/A
{{!}} colspan="3" {{!}} {{{job|}}} }}
|-
{{#if:{{{interests|<noinclude>x</noinclude>}}}|
{{!}} colspan="3" {{!}} Interests: Composing and correcting Wiki articles. Intercepting Flights or Formation flying.
{{!}} colspan="3" {{!}} {{{interests|}}} }}
|-
{{#if:{{{callsign|<noinclude>x</noinclude>}}}|
{{!}} colspan="3" {{!}} Callsign: sjf, KSFO TWR
{{!}} colspan="3" {{!}} {{{callsign|}}} }}
|-
{{#if:{{{favourite|<noinclude>x</noinclude>}}}|
{{!}} colspan="3" {{!}} Favourite Aircraft: B1900D, B-1B
{{!}} colspan="3" {{!}} {{{favourite|}}} }}
|-
{{#if:{{{website|<noinclude>x</noinclude>}}}|
{{!}} colspan="3" {{!}} Website
{{!}} colspan="3" {{!}} {{{website|}}}
|-
|}<noinclude></noinclude>
First Language English, Second Language French. Presently working on Aiports in Canada in the Wiki and with TaxiDraw.
[[Image:TGA_2-12-11_YSCB_1.jpg|thumb|left|800px|Transgear Airway Event Febuary 12, 2011]]]]
[[Image:TGA_2-12-11_YSCB_2.jpg|thumb|left|800px|Transgear Airway Event Febuary 12, 2011]]]]
[[Image:TGA_2-12-11_YSCB_3.jpg|thumb|left|800px|Transgear Airway Event Febuary 12, 2011]]]]
[[Image:TGA_2-12-11_YSCB_4.jpg|thumb|left|800px|Transgear Airway Event Febuary 12, 2011]]]]
[[Image:TGA_2-12-11_YSCB_5.jpg|thumb|left|800px|Transgear Airway Event Febuary 12, 2011]]]]
[[Image:TGA_2-12-11_YSCB_6.jpg|thumb|left|800px|Transgear Airway Event Febuary 12, 2011]]]]
[[Image:TGA_2-12-11_YSCB_7.jpg|thumb|left|800px|Transgear Airway Event Febuary 12, 2011]]]]
[[Image:TGA_2-12-11_YSCB_8.jpg|thumb|left|800px|Transgear Airway Event Febuary 12, 2011]]]]
[[Image:TGA_2-12-11_YSCB_9.jpg|thumb|left|800px|Transgear Airway Event Febuary 12, 2011]]]]
[[Image:TGA_2-12-11_YSCB_10.jpg|thumb|left|800px|Transgear Airway Event Febuary 12, 2011]]]]

File:TGA 2-12-11 YSCB 10.png

2011-02-12T19:17:39Z

Stepfaw:

File:TGA 2-12-11 YSCB 9.jpg

2011-02-12T19:15:23Z

Stepfaw:

File:TGA 2-12-11 YSCB 8.jpg

2011-02-12T19:14:05Z

Stepfaw:

File:TGA 2-12-11 YSCB 7.jpg

2011-02-12T19:13:25Z

Stepfaw:

File:TGA 2-12-11 YSCB 6.jpg

2011-02-12T19:09:21Z

Stepfaw:

File:TGA 2-12-11 YSCB 5.jpg

2011-02-12T19:08:34Z

Stepfaw:

File:TGA 2-12-11 YSCB 4.jpg

2011-02-12T19:07:54Z

Stepfaw:

File:TGA 2-12-11 YSCB 3.jpg

2011-02-12T19:06:43Z

Stepfaw:

User:Stepfaw

2011-02-12T19:06:08Z

Stepfaw:

User:Stepfaw

2011-02-12T19:05:24Z

Stepfaw:

File:TGA 2-12-11 YSCB 2.jpg

2011-02-12T19:02:34Z

Stepfaw:

User:Stepfaw

2011-02-12T19:00:48Z

Stepfaw:

User:Stepfaw

2011-02-12T18:57:05Z

Stepfaw:

{| style="background: white; width: 280px; font-size: 90%; text-align: left; border: 1px silver solid; border-collapse: collapse; margin-left:1em;" cellpadding="3" border="1" align="right"
! colspan="6" style="text-align: center; background-color: #0f7a71; color: white; font-size: larger;" | {{{StepFaw}}}
|-

{{#if:{{{location|<noinclude>x</noinclude>}}}|
{{!}} colspan="3" {{!}} Location: Canada
{{!}} colspan="3" {{!}} {{{Location|}}} }}
|-
{{#if:{{{age|<noinclude>x</noinclude>}}}|
{{!}} colspan="3" {{!}} Age: 50
{{!}} colspan="3" {{!}} {{{age|}}} }}
|-
{{#if:{{{job|<noinclude>x</noinclude>}}}|
{{!}} colspan="3" {{!}} Job: N/A
{{!}} colspan="3" {{!}} {{{job|}}} }}
|-
{{#if:{{{interests|<noinclude>x</noinclude>}}}|
{{!}} colspan="3" {{!}} Interests: Composing and correcting Wiki articles. Intercepting Flights or Formation flying.
{{!}} colspan="3" {{!}} {{{interests|}}} }}
|-
{{#if:{{{callsign|<noinclude>x</noinclude>}}}|
{{!}} colspan="3" {{!}} Callsign: sjf, KSFO TWR
{{!}} colspan="3" {{!}} {{{callsign|}}} }}
|-
{{#if:{{{favourite|<noinclude>x</noinclude>}}}|
{{!}} colspan="3" {{!}} Favourite Aircraft: B1900D, B-1B
{{!}} colspan="3" {{!}} {{{favourite|}}} }}
|-
{{#if:{{{website|<noinclude>x</noinclude>}}}|
{{!}} colspan="3" {{!}} Website
{{!}} colspan="3" {{!}} {{{website|}}} }}
|-
|}<noinclude></noinclude>
First Language English, Second Language French. Presently working on Aiports in Canada in the Wiki and with TaxiDraw.
[[Image:Snapshot 2010-01-01 sjf xyz.jpg|thumb|left|750px|Formation Flying with xyz on New Years Day 2010 over the ocean near KSFO at 4000 ft]]

[[Image:bob123.jpg|thumb|left|800px|Following bob123 flying a (777-200) at 2500 ft over Newfoundland 8:20 PM 1 January 2010.]]

[[Image:TGA_2-12-11_YSCB_1.jpg|thumb|left|800px|[[Image:bob123.jpg|thumb|left|800px|Following bob123 flying a (777-200) at 2500 ft over Newfoundland 8:20 PM 1 January 2010.]]]]

User:Stepfaw

2011-02-12T18:55:54Z

Stepfaw:

{| style="background: white; width: 280px; font-size: 90%; text-align: left; border: 1px silver solid; border-collapse: collapse; margin-left:1em;" cellpadding="3" border="1" align="right"
! colspan="6" style="text-align: center; background-color: #0f7a71; color: white; font-size: larger;" | {{{StepFaw}}}
|-

{{#if:{{{location|<noinclude>x</noinclude>}}}|
{{!}} colspan="3" {{!}} Location: Canada
{{!}} colspan="3" {{!}} {{{Location|}}} }}
|-
{{#if:{{{age|<noinclude>x</noinclude>}}}|
{{!}} colspan="3" {{!}} Age: 50
{{!}} colspan="3" {{!}} {{{age|}}} }}
|-
{{#if:{{{job|<noinclude>x</noinclude>}}}|
{{!}} colspan="3" {{!}} Job: N/A
{{!}} colspan="3" {{!}} {{{job|}}} }}
|-
{{#if:{{{interests|<noinclude>x</noinclude>}}}|
{{!}} colspan="3" {{!}} Interests: Composing and correcting Wiki articles. Intercepting Flights or Formation flying.
{{!}} colspan="3" {{!}} {{{interests|}}} }}
|-
{{#if:{{{callsign|<noinclude>x</noinclude>}}}|
{{!}} colspan="3" {{!}} Callsign: sjf, KSFO TWR
{{!}} colspan="3" {{!}} {{{callsign|}}} }}
|-
{{#if:{{{favourite|<noinclude>x</noinclude>}}}|
{{!}} colspan="3" {{!}} Favourite Aircraft: B1900D, B-1B
{{!}} colspan="3" {{!}} {{{favourite|}}} }}
|-
{{#if:{{{website|<noinclude>x</noinclude>}}}|
{{!}} colspan="3" {{!}} Website
{{!}} colspan="3" {{!}} {{{website|}}} }}
|-
|}<noinclude></noinclude>
First Language English, Second Language French. Presently working on Aiports in Canada in the Wiki and with TaxiDraw.
[[Image:Snapshot 2010-01-01 sjf xyz.jpg|thumb|left|750px|Formation Flying with xyz on New Years Day 2010 over the ocean near KSFO at 4000 ft]]

[[Image:bob123.jpg|thumb|left|800px|Following bob123 flying a (777-200) at 2500 ft over Newfoundland 8:20 PM 1 January 2010.]]

[[Image:bob123.jpg|thumb|left|800px|[[Image:bob123.jpg|thumb|left|800px|Following bob123 flying a (777-200) at 2500 ft over Newfoundland 8:20 PM 1 January 2010.]]]]

File:TGA 2-12-11 YSCB 1.jpg

2011-02-12T18:54:06Z

Stepfaw: Transgear Airways February 12, 2011, Airport YSCB

Transgear Airways February 12, 2011, Airport YSCB

User talk:Stepfaw

2010-04-17T23:01:23Z

Stepfaw: Blanked the page

FlightGear Newsletter January 2010

2010-01-21T03:57:16Z

Stepfaw: grammar and spelling

{{newsletter}}

This is the draft of the next edition of the [[FlightGear]] Newsletter. Please feel free to edit and add your contribution.

==What's new in CVS==

==In the hangar==
===Liveries===
For over a year, realistically (meaning: they exist, have existed, or will exist on the corresponding aircraft with the corresponding airline) FlightGear liveries have been available from [http://flightgear.oxyhost.com this website]. Due to the increasing amount of visitors and liveries, the website has moved to a new server, resulting in much faster downloads. The server switch was a good oppurtunity to re-design the website and its internal structure. It used to be a simple list, now it is as a fully functional database, improving the use and maintainablity significantly. The database can be searched by aircraft, airline or author.

Everyone is free to upload his/her liveries, which can be done through [http://liveries.flightgear.org/contribute.php this page].

[http://liveries.flightgear.org Visit the new livery database]

===Aircraft===

====Bell UH-1 ====
[[File:Fgfs-screen-740.jpg|thumb|270px|Bell UH-1]]
The [[Bell UH-1]], originally created by Helijah, has now been improved.
Most all of the model, including the exterior and interior have been redone using drawings freely available from a real flight manual.
The [[FDM]], created by Maik Justus, is based on real data and measurements done by NASA.

It is a first release and the author plans to continue, as soon he has finished some other projects.

It is compatible with 1.9.1 and later!

'''Features;'''

*besides the BO105 it is the most realistic fdm!
*nice shaded interior textures!
*higher resolution of the textures!
*accurate and correct proportions of the models
*the beginnings of a realistic cockpit!
*original sound!

and finally: tested and supported by a real Bell UH-1 Navy Pilot!

'''Known Issues:'''

*poor engine simulation- no autorotation possible (clutch simulation missing!)
*panel not ready- needs detailed pictures of the middle panel of the engine instrumentation
*no lights yet
*no gun/ rocket sounds
*missing parts in the cockpit like stick, pedals, overhead etc....
*Only one livery for the Gunship

'''Important for Repainters:'''
There are two livery-folders:

-Gunship

-UH1-D

Please make sure that you choose the right folder.

Have fun!

Thanks to JAG007, Helijah; Maik Justus, MOJO!

====Boeing 767-300 near its primary release====
{{Main article|Boeing 767-300}}
[[File:Airport2.png|thumb|270px|767-300 Exterior view with open cargo and front passenger doors, displaying its passenger stairways]]
[[File:Arkefly.jpg|thumb|270px|767-300 Exterior view with gear up]]
For a while the 767-300 has been a slow moving project, due to Isaías V. Preste temporarily leaving the forum and all FlightGear works. Liam has yet continued on from where Prestes left off, given a complete overhall to the old FDM, added plenty of new features and started animations. Thanks to the whole FlightGear community for providing some nice liveries, sounds, and other assistance to questions, With luck it should be submitted to CVS before the next release of FlightGear, with some new features not yet seen on many other Aircraft in FlightGear. This is a truly promising project!

====Boeing 737-100 updates====
{{Main article|Boeing 737-100}}
[[File:737-100_outside.jpg|thumb|270px|737-100 Outside view with open doors]]
[[File:737-100_cockpit.jpg|thumb|270px|737-100 Cockpit view from pilot seat]]
Since October we have had the 737-100 by helijah in CVS.
The aircraft has now been further improved.
Mike (aka D-SKY1) is building the autopilot, updating the 3D models, and the following changes were implemented:

* FDM refined
* Working instruments in front panel
* Doors (front and back) open with the keys D and Shift-D
* Front door also extends stairs
* Detailed overhead panel (not yet wired)
* Detailed pedestal (not yet wired)
* Autopilot incl. ILS approach (partly wired) [http://imagebin.ca/view/uaxeKd.html (actual screenshot of the glareshield)]
* Several liveries available via menu:
** Lufthansa
** Canadian
** Continental
** Qatar
** Swiss Air
** Air France
** Alitalia
** KLM
** Kuwait Airways
** Boeing Prototype-Livery

==Scenery Corner==
===Manila===
The Airport of Manila, Philippines (RPLL) has been improved. Besides Terminals 1 and 2, Terminal 3 has now been added. The Tower has also been redesigned to more accurately reflect the original. Many shared models on the ground have been added and as always all buildings are [[Howto:|illuminated]] at night and [[Howto:_Add_smooth_("Ambient_Occlusion")_shadows_in_Blender|ambient occlusion]] has been added to all new textures.

===San Francisco International Airport===
[[File:KSFO.jpg|thumb|270px|Overview of the SFO airport.]]
{{Main article|San Francisco International Airport}}
With the upcoming release in mind, FlightGear's main airport has been populated with more buildings than ever before. Dock your plane at one of the many gates, follow the airtrain as it moves from station to station, land your helicopter in the famous parkingarea hole or simply enjoy the visuals on final. In addition to this, the terrain has been refined, especially the bay area. These changes will be available with the next scenery release.

==Community News==
===FlightGear Wiki===
On 4 January 2010, the 900th article was added to the wiki! Back in May 2009, the 700th article was welcomed, which means an average of 1 article is created each day. A big "thank you" to all those who helped to extend and improve the wiki over the past years!

* More wiki stats can be found [[Special:Statistics|here]]
* Read the article at [[Howto: Add details to your airport‎‎]].

===Virtual Airline News===

==Addons==

==Useful links==

==And finally....==

[[Category:FlightGear Newsletter|2010 01]]

FlightGear Newsletter January 2010

2010-01-21T03:55:20Z

Stepfaw: grammar and spelling

{{newsletter}}

This is the draft of the next edition of the [[FlightGear]] Newsletter. Please feel free to edit and add your contribution.

==What's new in CVS==

==In the hangar==
===Liveries===
For over a year, realistically (meaning: they exist, have existed, or will exist on the corresponding aircraft with the corresponding airline) FlightGear liveries have been available from [http://flightgear.oxyhost.com this website]. Due to the increasing amount of visitors and liveries, the website has moved to a new server, resulting in much faster downloads. The server switch was a good oppurtunity to re-design the website and its internal structure. It used to be a simple list, now it is as a fully functional database, improving the use and maintainablity significantly. The database can be searched by aircraft, airline or author.

Everyone is free to upload his/her liveries, which can be done through [http://liveries.flightgear.org/contribute.php this page].

[http://liveries.flightgear.org Visit the new livery database]

===Aircraft===

====Bell UH-1 ====
[[File:Fgfs-screen-740.jpg|thumb|270px|Bell UH-1]]
The [[Bell UH-1]], originally created by Helijah, has now been improved.
Most all of the model, including the exterior and interior have been redone using drawings freely available from a real flight manual.
The [[FDM]], created by Maik Justus, is based on real data and measurements done by NASA.

It is a first release and the author plans to continue, as soon he has finished some other projects.

It is compatible with 1.9.1 and later!

'''Features;'''

*besides the BO105 it is the most realistic fdm!
*nice shaded interior textures!
*higher resolution of the textures!
*accurate and correct proportions of the models
*the beginnings of a realistic cockpit!
*original sound!

and finally: tested and supported by a real Bell UH-1 Navy Pilot!

'''Known Issues:'''

*poor engine simulation- no autorotation possible (clutch simulation missing!)
*panel not ready- needs detailed pictures of the middle panel of the engine instrumentation
*no lights yet
*no gun/ rocket sounds
*missing parts in the cockpit like stick, pedals, overhead etc....
*Only one livery for the Gunship

'''Important for Repainters:'''
There are two livery-folders:

-Gunship

-UH1-D

Please make sure that you choose the right folder.

Have fun!

Thanks to JAG007, Helijah; Maik Justus, MOJO!

====Boeing 767-300 near its primary release====
{{Main article|Boeing 767-300}}
[[File:Airport2.png|thumb|270px|767-300 Exterior view with open cargo and front passenger doors, displaying its passenger stairways]]
[[File:Arkefly.jpg|thumb|270px|767-300 Exterior view with gear up]]
For a while the 767-300 has been a slow moving project, due to Isaías V. Preste temporarily leaving the forum and all FlightGear works. Liam has yet continued on from where Prestes left off, given a complete overhall to the old FDM, added plenty of new features and started animations. Thanks to the whole FlightGear community for providing some nice liveries, sounds, and other assistance to questions, With luck it should be submitted to CVS before the next release of FlightGear, with some new features not yet seen on many other Aircraft in FlightGear. This is a truly promising project!

====Boeing 737-100 updates====
{{Main article|Boeing 737-100}}
[[File:737-100_outside.jpg|thumb|270px|737-100 Outside view with open doors]]
[[File:737-100_cockpit.jpg|thumb|270px|737-100 Cockpit view from pilot seat]]
Since October we have had the 737-100 by helijah in CVS.
The aircraft has now been further improved.
Mike (aka D-SKY1) is building the autopilot, updating the 3D models, and the following changes were implemented:

* FDM refined
* Working instruments in front panel
* Doors (front and back) open with the keys D and Shift-D
* Front door also extends stairs
* Detailed overhead panel (not yet wired)
* Detailed pedestal (not yet wired)
* Autopilot incl. ILS approach (partly wired) [http://imagebin.ca/view/uaxeKd.html (actual screenshot of the glareshield)]
* Several liveries available via menu:
** Lufthansa
** Canadian
** Continental
** Qatar
** Swiss Air
** Air France
** Alitalia
** KLM
** Kuwait Airways
** Boeing Prototype-Livery

==Scenery Corner==
===Manila===
The Airport of Manila, Philippines (RPLL) has been improved. Besides Terminals 1 and 2, Terminal 3 has now been added. The Tower has also been redesigned to more accurately reflect the original. Many shared models on the ground have been added and as always all buildings are [[Howto:|illuminated]] at night and [[Howto:_Add_smooth_("Ambient_Occlusion")_shadows_in_Blender|ambient occlusion]] is added to all new textures.

===San Francisco International Airport===
[[File:KSFO.jpg|thumb|270px|Overview of the SFO airport.]]
{{Main article|San Francisco International Airport}}
With the upcoming release in mind, FlightGear's main airport has been populated with more buildings than ever before. Dock your plane at one of the many gates, follow the airtrain as it moves from station to station, land your helicopter in the famous parkingarea hole or simply enjoy the visuals on final. In addition to this, the terrain has been refined, especially the bay area. These changes will be available with the next scenery release.

==Community News==
===FlightGear Wiki===
On 4 January 2010, the 900th article was added to the wiki! Back in May 2009, the 700th article was welcomed, which means an average of 1 article is created each day. A big "thank you" to all those who helped to extend and improve the wiki over the past years!

* More wiki stats can be found [[Special:Statistics|here]]
* Read the article at [[Howto: Add details to your airport‎‎]].

===Virtual Airline News===

==Addons==

==Useful links==

==And finally....==

[[Category:FlightGear Newsletter|2010 01]]

FlightGear Newsletter January 2010

2010-01-21T03:45:28Z

Stepfaw: grammar and spelling

{{newsletter}}

This is the draft of the next edition of the [[FlightGear]] Newsletter. Please feel free to edit and add your contribution.

==What's new in CVS==

==In the hangar==
===Liveries===
For over a year, realistically (meaning: they exist, have existed, or will exist on the corresponding aircraft with the corresponding airline) FlightGear liveries have been available from [http://flightgear.oxyhost.com this website]. Due to the increasing amount of visitors and liveries, the website has moved to a new server, resulting in much faster downloads. The server switch was a good oppurtunity to re-design the website and its internal structure. It used to be a simple list, now it is as a fully functional database, improving the use and maintainablity significantly. The database can be searched by aircraft, airline or author.

Everyone is free to upload his/her liveries, which can be done through [http://liveries.flightgear.org/contribute.php this page].

[http://liveries.flightgear.org Visit the new livery database]

===Aircraft===

====Bell UH-1 ====
[[File:Fgfs-screen-740.jpg|thumb|270px|Bell UH-1]]
The [[Bell UH-1]], originally created by Helijah, has now been improved.
Most all of the model, including the exterior and interior have been redone using drawings freely available from a real flight manual.
The [[FDM]], created by Maik Justus, is based on real data and measurements done by NASA.

It is a first release and the author plans to continue, as soon he has finished some other projects.

It is compatible with 1.9.1 and later!

'''Features;'''

*besides the BO105 it is the most realistic fdm!
*nice shaded interior textures!
*higher resolution of the textures!
*accurate and correct proportions of the models
*the beginnings of a realistic cockpit!
*original sound!

and finally: tested and supported by a real Bell UH-1 Navy Pilot!

'''Known Issues:'''

*poor engine simulation- no autorotation possible (clutch simulation missing!)
*panel not ready- needs detailed pictures of the middle panel of the engine instrumentation
*no lights yet
*no gun/ rocket sounds
*missing parts in the cockpit like stick, pedals, overhead etc....
*Only one livery for the Gunship

'''Important for Repainters:'''
There are two livery-folders:

-Gunship

-UH1-D

Please make sure that you choose the right folder.

Have fun!

Thanks to JAG007, Helijah; Maik Justus, MOJO!

====Boeing 767-300 near its primary release====
{{Main article|Boeing 767-300}}
[[File:Airport2.png|thumb|270px|767-300 Exterior view with open cargo and front passenger doors, displaying its passenger stairways]]
[[File:Arkefly.jpg|thumb|270px|767-300 Exterior view with gear up]]
For a while the 767-300 has been a slow moving project, due to Isaías V. Preste temporarily leaving the forum and all FlightGear works. Liam has yet continued on from where Prestes left off, given a complete overhall to the old FDM, added plenty of new features and started animations. Thanks to the whole FlightGear community for providing some nice liveries, sounds, and other assistance to questions, With luck it should be submitted to CVS before the next release of FlightGear, with some new features not yet seen on many other Aircraft in FlightGear. This is a truly promising project!

====Boeing 737-100 updates====
{{Main article|Boeing 737-100}}
[[File:737-100_outside.jpg|thumb|270px|737-100 Outside view with open doors]]
[[File:737-100_cockpit.jpg|thumb|270px|737-100 Cockpit view from pilot seat]]
Since October we have had the 737-100 by helijah in CVS.
The aircraft has now been further improved.
Mike (aka D-SKY1) is building the autopilot, updating the 3D models, and the following changes were implemented:

* FDM refined
* Working instruments in front panel
* Doors (front and back) open with the keys D and Shift-D
* Front door also extends stairs
* Detailed overhead panel (not yet wired)
* Detailed pedestal (not yet wired)
* Autopilot incl. ILS approach (partly wired) [http://imagebin.ca/view/uaxeKd.html (actual screenshot of the glareshield)]
* Several liveries available via menu:
** Lufthansa
** Canadian
** Continental
** Qatar
** Swiss Air
** Air France
** Alitalia
** KLM
** Kuwait Airways
** Boeing Prototype-Livery

==Scenery Corner==
===Manila===
The Airport of Manila, Philippines (RPLL) has been improved. Beside the Terminals 1 and 2, Terminal 3 is now built. The Tower is redesigned to be closer to the original. Many shared models on the ground has been added and like always all buildings are [[Howto:_Illuminate_faces|illuminated]] at night and [[Howto:_Add_smooth_("Ambient_Occlusion")_shadows_in_Blender|ambient occlusion]] is added to all new textures..

===San Francisco International Airport===
[[File:KSFO.jpg|thumb|270px|Overview of the SFO airport.]]
{{Main article|San Francisco International Airport}}
With the upcoming release in mind, FlightGear's main airport has been populated with more buildings than ever before. Dock your plane at one of the many gates, follow the airtrain as it moves from station to station, land your helicopter in the famous parkingarea hole or simply enjoy the visuals on final. In addition to this, the terrain has been refined, especially the bay area. These changes will be available with the next scenery release.

==Community News==
===FlightGear Wiki===
On 4 January 2010, the 900th article was added to the wiki! Back in May 2009, the 700th article was welcomed, which means an average of 1 article is created each day. A big "thank you" to all those who helped to extend and improve the wiki over the past years!

* More wiki stats can be found [[Special:Statistics|here]]
* Read the article at [[Howto: Add details to your airport‎‎]].

===Virtual Airline News===

==Addons==

==Useful links==

==And finally....==

[[Category:FlightGear Newsletter|2010 01]]

FlightGear Newsletter January 2010

2010-01-21T03:40:49Z

Stepfaw: grammar and spelling

{{newsletter}}

This is the draft of the next edition of the [[FlightGear]] Newsletter. Please feel free to edit and add your contribution.

==What's new in CVS==

==In the hangar==
===Liveries===
For over a year, realistic (meaning: they have to exist, have existed, or will exist on the corresponding aircraft with the corresponding airline) FlightGear liveries have been available from [http://flightgear.oxyhost.com this website]. Due to the increasing amount of visitors and liveries, the website is moved to a new server, resulting in much faster downloads. The serverswitch was a good oppurtunity to re-design the website and its internal structure. It used to be a simple list, now it exists of a fully functional database, improving the use- and maintainablity significantly. The database can be searched by aircraft, airline or author.

Everyone is free to upload his/her liveries, which can be done through [http://liveries.flightgear.org/contribute.php this page].

[http://liveries.flightgear.org Visit the new livery database]

===Aircraft===

====Bell UH-1 ====
[[File:Fgfs-screen-740.jpg|thumb|270px|Bell UH-1]]
The [[Bell UH-1]], originally created by Helijah, has now been improved.
Most all of the model, including the exterior and interior have been redone using drawings freely available from a real flight manual.
The [[FDM]], created by Maik Justus, is based on real data and measurements done by NASA.

It is a first release and the author plans to continue, as soon he has finished some other projects.

It is compatible with 1.9.1 and later!

'''Features;'''

*besides the BO105 it is the most realistic fdm!
*nice shaded interior textures!
*higher resolution of the textures!
*accurate and correct proportions of the models
*the beginnings of a realistic cockpit!
*original sound!

and finally: tested and supported by a real Bell UH-1 Navy Pilot!

'''Known Issues:'''

*poor engine simulation- no autorotation possible (clutch simulation missing!)
*panel not ready- needs detailed pictures of the middle panel of the engine instrumentation
*no lights yet
*no gun/ rocket sounds
*missing parts in the cockpit like stick, pedals, overhead etc....
*Only one livery for the Gunship

'''Important for Repainters:'''
There are two livery-folders:

-Gunship

-UH1-D

Please make sure that you choose the right folder.

Have fun!

Thanks to JAG007, Helijah; Maik Justus, MOJO!

====Boeing 767-300 near its primary release====
{{Main article|Boeing 767-300}}
[[File:Airport2.png|thumb|270px|767-300 Exterior view with open cargo and front passenger doors, displaying its passenger stairways]]
[[File:Arkefly.jpg|thumb|270px|767-300 Exterior view with gear up]]
For a while the 767-300 has been a slow moving project, due to Isaías V. Preste temporarily leaving the forum and all FlightGear works. Liam has yet continued on from where Prestes left off, given a complete overhall to the old FDM, added plenty of new features and started animations. Thanks to the whole FlightGear community for providing some nice liveries, sounds, and other assistance to questions, With luck it should be submitted to CVS before the next release of FlightGear, with some new features not yet seen on many other Aircraft in FlightGear. This is a truly promising project!

====Boeing 737-100 updates====
{{Main article|Boeing 737-100}}
[[File:737-100_outside.jpg|thumb|270px|737-100 Outside view with open doors]]
[[File:737-100_cockpit.jpg|thumb|270px|737-100 Cockpit view from pilot seat]]
Since October we have had the 737-100 by helijah in CVS.
The aircraft has now been further improved.
Mike (aka D-SKY1) is building the autopilot, updating the 3D models, and the following changes were implemented:

* FDM refined
* Working instruments in front panel
* Doors (front and back) open with the keys D and Shift-D
* Front door also extends stairs
* Detailed overhead panel (not yet wired)
* Detailed pedestal (not yet wired)
* Autopilot incl. ILS approach (partly wired) [http://imagebin.ca/view/uaxeKd.html (actual screenshot of the glareshield)]
* Several liveries available via menu:
** Lufthansa
** Canadian
** Continental
** Qatar
** Swiss Air
** Air France
** Alitalia
** KLM
** Kuwait Airways
** Boeing Prototype-Livery

==Scenery Corner==
===Manila===
The Airport of Manila, Philippines (RPLL) has been improved. Beside the Terminals 1 and 2, Terminal 3 is now built. The Tower is redesigned to be closer to the original. Many shared models on the ground has been added and like always all buildings are [[Howto:_Illuminate_faces|illuminated]] at night and [[Howto:_Add_smooth_("Ambient_Occlusion")_shadows_in_Blender|ambient occlusion]] is added to all new textures..

===San Francisco International Airport===
[[File:KSFO.jpg|thumb|270px|Overview of the SFO airport.]]
{{Main article|San Francisco International Airport}}
With the upcoming release in mind, FlightGear's main airport has been populated with more buildings than ever before. Dock your plane at one of the many gates, follow the airtrain as it moves from station to station, land your helicopter in the famous parkingarea hole or simply enjoy the visuals on final. In addition to this, the terrain has been refined, especially the bay area. These changes will be available with the next scenery release.

==Community News==
===FlightGear Wiki===
On 4 January 2010, the 900th article was added to the wiki! Back in May 2009, the 700th article was welcomed, which means an average of 1 article is created each day. A big "thank you" to all those who helped to extend and improve the wiki over the past years!

* More wiki stats can be found [[Special:Statistics|here]]
* Read the article at [[Howto: Add details to your airport‎‎]].

===Virtual Airline News===

==Addons==

==Useful links==

==And finally....==

[[Category:FlightGear Newsletter|2010 01]]

Amsterdam Airport Schiphol

2010-01-03T13:57:59Z

Stepfaw: english grammar

{{infobox Airport
|name = Amsterdam Airport Schiphol
|image =EHAM.jpg
|alt =Schiphol in the [[FlightGear NL]] scenery
|iata =AMS
|icao =EHAM
|type =public
|owner =Schiphol Group
|city =Amsterdam, [[The Netherlands]]
|runway= 18R/36L
|length= 3800 m
|material= Asfalt
|runway2= 06/24
|length2= 3490 m
|material2=Asfalt
|runway3= 09/27
|length3= 3450 m
|material3= Asfalt
|runway4 = 18L/36R
|length4= 3400 m
|material4= Asfalt
|runway5 = 18C/36C
|length5= 3300 m
|material5= Asfalt
|runway6 = 04/22
|length6= 2015 m
|material6= Asfalt
|website =http://www.schiphol.nl
}}'''Amsterdam Airport Schiphol''' (IATA: '''AMS''', ICAO: '''EHAM''') is [[the Netherlands]]' main airport, located 20 minutes (17.5 km or 10.8 miles) southwest of Amsterdam, in the municipality of Haarlemmermeer. The airport's official English name, Amsterdam Airport Schiphol, places the words in the Dutch sequence (Luchthaven Schiphol) instead of Amsterdam Schiphol Airport. The airport also had the IATA code of SPL but this has fallen into disuse.

In 2007, Schiphol handled 47,793,602 passengers, ranking fifth in Europe behind London, Paris, Frankfurt and Madrid.

Schiphol is the home base of KLM (Royal Dutch Airlines), Martinair and Transavia, and a hub for United States based Northwest Airlines in cooperation with KLM.

== Runways ==
Schiphol has five long runways and one short runway.

=== Aalsmeerbaan (18L - 36R) ===
The Aalsmeerbaan is 3400 meters long.
From the northern head, runway 18L planes takeoff to the south. On the southern head, runway 36R planes land in northern direction. Runway 18L is common used during daylight in combination with runway 24 for departing traffic. Runway 36R is commonly used for incoming traffic in combination with runway 06. Usage of the Aalsmeerbaan is prohibited between 23:00 and 06:00 (local time).

'''Rules:'''
* Landing on 18L is always prohibited.
* Landing on 36R is prohibited between 23.00 and 06.00 (local time).
* Takeoff from 36R is always prohibited.
* Takeoff from 18L is prohibited between 23.00 and 06.00 (local time).

Runway 36R is equiped with [[ILS]]. The Aalsmeerbaan lies parallel to the Polderbaan and Zwanenburgbaan.

=== Buitenveldertbaan (09 - 27) ===
The Buitenveldertbaan is 3400 meters long.

From the western head, runway 09, planes takeoff in eastern direction. On the eastern head, runway 27 planes land from the east in western direction. Takeoff from 27 and landing on 09 is only permitted in extrordinary cases. Usage of the Buitenvelderbaan is prohibited between 23.00 and 06.00 (local time).

'''Rules:'''
* Landing on 09 is prohibited between 23.00 and 06.00 (local time).
* Takeoff from 09 is prohibited between 23.00 and 06.00 (local time).
* Takeoff from 27 is prohibited between 23.00 and 06.00 (local time).
* Landing on 27 is prohibited between 23.00 and 06.00 (local time).

Runway 27 is equiped with ILS.

=== Kaagbaan (06 - 24) ===
The Kaagbaan is 3490 meters long.

From the northern head, runway 24 planes regurlary takeoff to southwestern direction. On the southwestern head, runway 06 planes frequently land in northeastern direction. Only with strong northeastern wind planes takeoff from runway 06. On runway 24 planes only land with strong southwestern wind.

'''Rules:'''
* Landing on 06 is alwasy permitted.
* Takeoff from 06 is always permited.
* Landing on 24 is prohibited between 23.00 and 06.00 (local time)
* Takeoff from 24 is always permitted.

Runway 06 is equiped with ILS. This runway and the Polderbaan are the primary combination used at night.

=== Polderbaan (18R - 36L) ===
The Polderbaan is 3800 meters long, which makes it the longest runway of Schiphol.

From the southern head, runway 36L planes takeoff in northern direction. On the northern head, runway 18R planes land in southern direction.

'''Rules:'''
* Landing on 36L is always prohibited.
* Takeoff from 36L is always permitted.
* Landing on 18R is always permitted.
* Takeoff from 18R is always prohibited.

Runway 18R is equiped with ILS. The Polderbaan lies parallel to the Zwanenburgbaan and Aalsmeerbaan. This runway and the Kaagbaan are the primary combination used at night.

=== Zwanenburgbaan (18C - 36C) ===
The Zwanenburgbaan is 3300 meters long.

On the northern head, runway 18C planes land in southern direction. This usually hapens in combination with the usage of runway 18R for landings. From the northern head, runway 36C planes takeoff in northern direction. This usually hapens in combination with the usage of runway 18L for takeoffs. From the northern head, runway 18C planes takeoff in southern direction. This usually hapens in combination with the usage of runway 18L for takeoffs. From the southern head, runway 36C, planes takeoff in northern direction. This usually hapens in combination with the usage of runway 36L for takeoffs. On the southern head, runway 36C planes land from the south. This usually hapens in combination with the usage of runway 36R for landings.

'''Rules:'''
* Takeoff from 36C is prohibited between 23.00 and 06.00 (local time).
* Landing on 36C is always permitted.
* Takeoff from 18C is always permitted
* Landing on 18C is prohibited between 23.00 and 06.00 (local time).

Runways 18C and 36C are equiped with ILS.

=== Schiphol-Oostbaan (04- 22) ===
The Schiphol-Oostbaan is 2015 meters long, which makes it the shortest runway of Schiphol. That's why this runway isn't adequate for large, longdistance planes. The runway is mainly used for small traffic, called general aviation. Only when the weather conditions make the need to use the Schiphol-Oostbaan, it's used for regular traffic. Usage of the Schiphol-Oostbaan is prohibited between 23.00 and 06.00 (local time).

'''Rules:'''
* Takeoff from 04 is prohibited between 23.00 and 06.00 (local time).
* Landing on 04 is prohibited between 23.00 and 06.00 (local time).
* Takeoff from 22 is prohibited between 23.00 and 06.00 (local time).
* Landing on 22 is prohibited between 23.00 and 06.00 (local time).

==Scenery==
Schiphol is included in the [[FlightGear NL]] scenery, which is available at [http://www.flightgear.nl.tp www.flightgear.nl.tp].

==External links==
* [http://www.flightgear.nl.tp/en/maps.html Airport Diagrams]

[[Category:Airports in the Netherlands]]

[[nl:Luchthaven Schiphol]]

Amsterdam Airport Schiphol

2010-01-03T13:49:03Z

Stepfaw: spelling "prohibited"

{{infobox Airport
|name = Amsterdam Airport Schiphol
|image =EHAM.jpg
|alt =Schiphol in the [[FlightGear NL]] scenery
|iata =AMS
|icao =EHAM
|type =public
|owner =Schiphol Group
|city =Amsterdam, [[The Netherlands]]
|runway= 18R/36L
|length= 3800 m
|material= Asfalt
|runway2= 06/24
|length2= 3490 m
|material2=Asfalt
|runway3= 09/27
|length3= 3450 m
|material3= Asfalt
|runway4 = 18L/36R
|length4= 3400 m
|material4= Asfalt
|runway5 = 18C/36C
|length5= 3300 m
|material5= Asfalt
|runway6 = 04/22
|length6= 2015 m
|material6= Asfalt
|website =http://www.schiphol.nl
}}'''Amsterdam Airport Schiphol''' (IATA: '''AMS''', ICAO: '''EHAM''') is [[the Netherlands]]' main airport, located 20 minutes (17.5 km or 10.8 miles) southwest of Amsterdam, in the municipality of Haarlemmermeer. The airport's official English name, Amsterdam Airport Schiphol, places the words in the Dutch sequence (Luchthaven Schiphol) instead of Amsterdam Schiphol Airport. The airport also had the IATA code of SPL but this has fallen into disuse.

In 2007, Schiphol handled 47,793,602 passengers, ranking fifth in Europe behind London, Paris, Frankfurt and Madrid.

Schiphol is the home base of KLM (Royal Dutch Airlines), Martinair and Transavia, and a hub for United States based Northwest Airlines in cooperation with KLM.

== Runways ==
Schiphol has five long runways and one short runway.

=== Aalsmeerbaan (18L - 36R) ===
The Aalsmeerbaan is 3400 meters long.
From the northern head, runway 18L planes takeoff to the south. On the southern head, runway 36R planes land in northern direction. Runway 18L is common used during daylight in combination with runway 24 for leaving traffic. Runway 36R is common used for incoming traffic in combination with runway 06. Usage of the Aalsmeerbaan is prohibited between 23:00 and 06:00 (local time).

'''Rules:'''
* Landing on 18L is always prohibited.
* Landing on 36R is prohibited between 23.00 and 06.00 (local time).
* Takeoff from 36R is always prohibited.
* Takeoff from 18L is prohibited between 23.00 and 06.00 (local time).

Runway 36R is equiped with [[ILS]]. The Aalsmeerbaan lies parallel to the Polderbaan and Zwanenburgbaan.

=== Buitenveldertbaan (09 - 27) ===
The Buitenveldertbaan is 3400 meters long.

From the western head, runway 09, planes takeoff in eastern direction. On the eastern head, runway 27 planes land from the east in western direction. Takeoff from 27 and landing on 09 is only permitted in extrordinary cases. Usage of the Buitenvelderbaan is prohibited between 23.00 and 06.00 (local time).

'''Rules:'''
* Landing on 09 is prohibited between 23.00 and 06.00 (local time).
* Takeoff from 09 is prohibited between 23.00 and 06.00 (local time).
* Takeoff from 27 is prohibited between 23.00 and 06.00 (local time).
* Landing on 27 is prohibited between 23.00 and 06.00 (local time).

Runway 27 is equiped with ILS.

=== Kaagbaan (06 - 24) ===
The Kaagbaan is 3490 meters long.

From the northern head, runway 24 planes regurlary takeoff to southwestern direction. On the southwestern head, runway 06 planes frequently land in northeastern direction. Only with hard northeastern wind planes takeoff from runway 06. On runway 24 planes only land with hard southwestern wind.

'''Rules:'''
* Landing on 06 is alwasy permitted.
* Takeoff from 06 is always permited.
* Landing on 24 is prohibited between 23.00 and 06.00 (local time)
* Takeoff from 24 is always permitted.

Runway 06 is equiped with ILS. This runway and the Polderbaan are the primary combination used at night.

=== Polderbaan (18R - 36L) ===
The Polderbaan is 3800 meters long, which makes it the longest runway of Schiphol.

From the southern head, runway 36L planes takeoff in northern direction. On the northern head, runway 18R planes land in southern direction.

'''Rules:'''
* Landing on 36L is always prohibited.
* Takeoff from 36L is always permitted.
* Landing on 18R is always permitted.
* Takeoff from 18R is always prohibited.

Runway 18R is equiped with ILS. The Polderbaan lies parallel to the Zwanenburgbaan and Aalsmeerbaan. This runway and the Kaagbaan are the primary combination used at night.

=== Zwanenburgbaan (18C - 36C) ===
The Zwanenburgbaan is 3300 meters long.

On the northern head, runway 18C planes land in southern direction. This usually hapens in combination with the usage of runway 18R for landings. From the northern head, runway 36C planes takeoff in northern direction. This usually hapens in combination with the usage of runway 18L for takeoffs. From the northern head, runway 18C planes takeoff in southern direction. This usually hapens in combination with the usage of runway 18L for takeoffs. From the southern head, runway 36C, planes takeoff in northern direction. This usually hapens in combination with the usage of runway 36L for takeoffs. On the southern head, runway 36C planes land from the south. This usually hapens in combination with the usage of runway 36R for landings.

'''Rules:'''
* Takeoff from 36C is prohibited between 23.00 and 06.00 (local time).
* Landing on 36C is always permitted.
* Takeoff from 18C is always permitted
* Landing on 18C is prohibited between 23.00 and 06.00 (local time).

Runways 18C and 36C are equiped with ILS.

=== Schiphol-Oostbaan (04- 22) ===
The Schiphol-Oostbaan is 2015 meters long, which makes it the shortest runway of Schiphol. That's why this runway isn't adequate for large, longdistance planes. The runway is mainly used voor the small traffic, called general aviation. Only when the weather conditions make the need to use the Schiphol-Oostbaan, it's used for regular traffic. Usage of the Schiphol-Oostbaan is prohibited between 23.00 and 06.00 (local time).

'''Rules:'''
* Takeoff from 04 is prohibited between 23.00 and 06.00 (local time).
* Landing on 04 is prohibited between 23.00 and 06.00 (local time).
* Takeoff from 22 is prohibited between 23.00 and 06.00 (local time).
* Landing on 22 is prohibited between 23.00 and 06.00 (local time).

==Scenery==
Schiphol is included in the [[FlightGear NL]] scenery, which is available at [http://www.flightgear.nl.tp www.flightgear.nl.tp].

==External links==
* [http://www.flightgear.nl.tp/en/maps.html Airport Diagrams]

[[Category:Airports in the Netherlands]]

[[nl:Luchthaven Schiphol]]

User:Stepfaw

2010-01-03T13:26:34Z

Stepfaw:

{| style="background: white; width: 280px; font-size: 90%; text-align: left; border: 1px silver solid; border-collapse: collapse; margin-left:1em;" cellpadding="3" border="1" align="right"
! colspan="6" style="text-align: center; background-color: #0f7a71; color: white; font-size: larger;" | {{{StepFaw}}}
|-

{{#if:{{{location|<noinclude>x</noinclude>}}}|
{{!}} colspan="3" {{!}} Location: Canada
{{!}} colspan="3" {{!}} {{{Location|}}} }}
|-
{{#if:{{{age|<noinclude>x</noinclude>}}}|
{{!}} colspan="3" {{!}} Age: 50
{{!}} colspan="3" {{!}} {{{age|}}} }}
|-
{{#if:{{{job|<noinclude>x</noinclude>}}}|
{{!}} colspan="3" {{!}} Job: N/A
{{!}} colspan="3" {{!}} {{{job|}}} }}
|-
{{#if:{{{interests|<noinclude>x</noinclude>}}}|
{{!}} colspan="3" {{!}} Interests: Composing and correcting Wiki articles. Intercepting Flights or Formation flying.
{{!}} colspan="3" {{!}} {{{interests|}}} }}
|-
{{#if:{{{callsign|<noinclude>x</noinclude>}}}|
{{!}} colspan="3" {{!}} Callsign: sjf, KSFO TWR
{{!}} colspan="3" {{!}} {{{callsign|}}} }}
|-
{{#if:{{{favourite|<noinclude>x</noinclude>}}}|
{{!}} colspan="3" {{!}} Favourite Aircraft: B1900D, B-1B
{{!}} colspan="3" {{!}} {{{favourite|}}} }}
|-
{{#if:{{{website|<noinclude>x</noinclude>}}}|
{{!}} colspan="3" {{!}} Website
{{!}} colspan="3" {{!}} {{{website|}}} }}
|-
|}<noinclude></noinclude>
First Language English, Second Language French. Presently working on Aiports in Canada in the Wiki and with TaxiDraw.
[[Image:Snapshot 2010-01-01 sjf xyz.jpg|thumb|left|750px|Formation Flying with xyz on New Years Day 2010 over the ocean near KSFO at 4000 ft]]

[[Image:bob123.jpg|thumb|left|800px|Following bob123 flying a (777-200) at 2500 ft over Newfoundland 8:20 PM 1 January 2010.]]

User:Stepfaw

2010-01-02T01:57:47Z

Stepfaw:

{| style="background: white; width: 280px; font-size: 90%; text-align: left; border: 1px silver solid; border-collapse: collapse; margin-left:1em;" cellpadding="3" border="1" align="right"
! colspan="6" style="text-align: center; background-color: #0f7a71; color: white; font-size: larger;" | {{{StepFaw}}}
|-

{{#if:{{{location|<noinclude>x</noinclude>}}}|
{{!}} colspan="3" {{!}} Location: Canada
{{!}} colspan="3" {{!}} {{{Location|}}} }}
|-
{{#if:{{{age|<noinclude>x</noinclude>}}}|
{{!}} colspan="3" {{!}} Age: 50
{{!}} colspan="3" {{!}} {{{age|}}} }}
|-
{{#if:{{{job|<noinclude>x</noinclude>}}}|
{{!}} colspan="3" {{!}} Job: N/A
{{!}} colspan="3" {{!}} {{{job|}}} }}
|-
{{#if:{{{interests|<noinclude>x</noinclude>}}}|
{{!}} colspan="3" {{!}} Interests: Composing and correcting Wiki articles. Intercepting Flights or Formation flying.
{{!}} colspan="3" {{!}} {{{interests|}}} }}
|-
{{#if:{{{callsign|<noinclude>x</noinclude>}}}|
{{!}} colspan="3" {{!}} Callsign: sjf, KSFO TWR
{{!}} colspan="3" {{!}} {{{callsign|}}} }}
|-
{{#if:{{{favourite|<noinclude>x</noinclude>}}}|
{{!}} colspan="3" {{!}} Favourite Aircraft: B1900D, B-1B
{{!}} colspan="3" {{!}} {{{favourite|}}} }}
|-
{{#if:{{{website|<noinclude>x</noinclude>}}}|
{{!}} colspan="3" {{!}} Website
{{!}} colspan="3" {{!}} {{{website|}}} }}
|-
|}<noinclude></noinclude>
First Language English, Second Language French. Presently working on Aiports in Canada in the Wiki and with TaxiDraw.
[[Image:Snapshot 2010-01-01 sjf xyz.jpg|thumb|right|800px|Formation Flying with xyz on New Years Day 2010 over the ocean near KSFO at 4000 ft]]

[[Image:bob123.jpg|thumb|right|800px|Following bob123 flying a (777-200) at 2500 ft over Newfoundland 8:20 PM 1 January 2010.]]

File:Bob123.jpg

2010-01-02T01:54:52Z

Stepfaw: Following bob123 flying a (777-200) at 2500 ft over Newfoundland 8:20 PM 1 January 2010.

Following bob123 flying a (777-200) at 2500 ft over Newfoundland 8:20 PM 1 January 2010.

User:Stepfaw

2010-01-02T01:45:47Z

Stepfaw:

User:Stepfaw

2010-01-01T18:32:12Z

Stepfaw:

User:Stepfaw

2010-01-01T18:27:52Z

Stepfaw:

File:Snapshot 2010-01-01 sjf xyz.jpg

2010-01-01T18:25:08Z

Stepfaw: Formation Flying New Years Day - sjf and xyz over the ocean near KSFO at 400 ft

Formation Flying New Years Day - sjf and xyz over the ocean near KSFO at 400 ft

S-Turns

2009-10-20T10:51:17Z

Stepfaw: undo change made by Toto1919

OBJECTIVE: To develop the pilot's ability to compensate for drift during turns, orient the flightpath with ground references, and divide the pilot's attention

ELEMENTS:

A. How to select a suitable altitude.
B. How to select a suitable ground reference line with suitable emergency landing areas.
C. Orientation, division of attention, and planning.
D. Configuration and airspeed prior to entry.
E. Entry technique.
F. Wind drifts correction.
G. Tracking of semicircles of equal radii on either side of the selected ground reference line.
H. How to maintain desired altitude and airspeed.
I. Turn reversal over the ground reference line.
J. Coordination of flight controls.

ASSOCIATED MANEUVERS:

SCHEDULE: Pre-flight instruction: 10 Minutes
Travel to training area: 10 Minutes
Instructor Demonstration: 10 Minutes
Student Practice: 20 Minutes
Return from practice area: 10 minutes
Post-flight Review: 10 Minutes
Total Time: 1:10

EQUIPMENT: Functional aircraft.

INSTRUCTOR’S ACTIONS: A. Conduct preflight training on the elements of S Turns.
B. Demonstrate S Turns
F. Conduct post flight briefing.

STUDENT’S ACTIONS: A. Ask questions, review homework.
B. Perform preflight.
C. Observe demonstrations.
D. Perform IAW PTS.

COMPLETION STANDARDS: Student performs S Turns IAW the PTS.

COMMON ERRORS: A. Faulty entry technique.
B. Poor planning, orientation, or division of attention.
C. Uncoordinated flight control application.
D. Improper correction for wind drift.
E. A non-symmetrical ground track.
F. Failure to maintain selected altitude or airspeed.
G. Selection of a ground reference line where this is no suitable emergency landing area within gliding distance.

Introduction: Every time we turn the airplane we make adjustments for the wind. This is especially true for flying in the traffic pattern. In the pattern we want to maintain the same relative distance to the runway until we turn final. S-turns show us the effect that wind has on an airplane and how we compensate for that while in a turn. Basically we will do this about 1000 feet agl. We will use a road or some other clearly identifiable straight line on the ground. We will fly across the road with the wind, then turn back toward the road, level of in time to cross the road and then turn again towards the road. This makes an “S” pattern across the road. The object here is to maintain perfect half circles on either side of the road and to be wings level ONLY long enough to cross the road. You maintain your relative position by adjusting your angle of bank and hence your rate of turn. You need to keep your altitude and airspeed where you start the maneuver.

A. Lesson Requirements:

1. Task: Perform a S-turn.

2. Condition: Given a functional aircraft.

3. Standard: IAW the PTS.

a. Exhibits knowledge of the elements related to S-turns.

b. Determines the wind direction and speed.

c. Selects the reference line with an emergency landing area within gliding distance.

d. Plans the maneuver so as to enter at 600 to 1,000 feet (180 to 300 meters) AGL, perpendicular to the selected reference line, downwind, with the first series of turns to the left.

e. Applies adequate wind-drift correction to track a constant radius half-circle on each side of the selected reference line.

f. Divides attention between airplane control and the ground track and maintains coordinated flight.

g. Reverses course, as directed by the examiner, and exits at the point of entry at the same altitude and airspeed at which the maneuver was started.

h. Maintains altitude +- 100 feet (30 m) and airspeed +- 10 knots.

B. ELO 1: Understand the effects of wind on a flying airplane.

1. The air is more like the ocean than a solid mass. As the wind blows it will tend to push an airplane in the direction of airflow. This is just like an boat in a river as it flows in the direction of the stream. Pilots compensate for this by adjusting the crab angle in straight slight, and by adjusting the angle of bank in turns.

2. How do winds affect groundspeed? Moving downwind (with the wind) causes the airplane to have an increase in groundspeed. Moving upwind (against the wind) causes the airplane to have a decrease in groundspeed. In both cases the airspeed indicator may read the same.

3. How do winds affect the angle of bank and rate of turn? When traveling on the downwind side of the turn the airplane tends to increase speed and a greater rate of turn must be used to compensate for the increased airspeed. On the upwind side of the turn, the bank will be shallower because the airplane is moving slower.

4. Student Check:

What portion of the S-turn will have a steeper turn? _______
Where do you enter the S-turn relative to the wind? ______

C. ELO 2: Identify common errors in the S-turn.

1. Faulty entry technique.

2. Poor planning, orientation, or division of attention.

3. Uncoordinated flight control application.

4. Improper correction for wind drift.

5. A non-symmetrical ground track.

6. Failure to maintain selected altitude or airspeed.

7. Selection of a ground reference line where this is no suitable emergency landing area within gliding distance.

8. Student Check:

i. What is Vx on this aircraft? ________
ii. What is Vy on this aircraft? ________

D. ELO 3: Perform a S-turn.

1. Pick an appropriate entry altitude (700-1000 ft agl works well). NO LOWER than 500 feet agl.

2. Pick your reference line.

3. Enter the maneuver WITH the wind and perpendicular to the line. Once you cross the reference line, start a 180 degree turn.

4. Maintain the turn until you come about 180 degrees. This should be just as you are about to cross your reference line.

5. Once you cross the reference line begin a turn in the other direction to complete the S.

6. Maintain the turn until you come about 180 degrees. This should be just as you are about to cross your reference line.

7. Continue the maneuver until told to stop.

Route manager

2009-10-13T21:00:35Z

Stepfaw: added internal links

A real route-manager page!

==Introduction==

(in the following sections, familiarity with basic IFR concepts, [[Autopilot]] usage and radio navigation is assumed)

The route-manager models part of the functionality found in real-world [[GPS]] and FMS devices, but is usable in any aircraft. Some panel instruments may provide access to the route manager via their own UI, but the route-manager is always available through a generic dialog box. The route-manager is also how a flight plan is made available to FlightGear - in the future this will hopefully permit better [[ATC]] and multi-player interactions, since [[ATC]] logic or controllers will be able to observe the filed plan associated with a pilot.

It's important to realize that the route-manager (and [[GPS]]) are pieces that a panel instrument might present as a single real world device - the mapping between C++ modules, generic user interface and in-panel instruments is very fluid, by design. In general core features exist in whichever place seems the most natural, and it's up to instruments to aggregate the core modules as they require.

==Concepts==
The route-manager maintains a flight-plan, consisting of departure, destination, alternate airport and cruise information, as well as a list of waypoints (technically, route segments, or legs). A flight plan must have a departure airport and destination airport specified; all other information is currently optional, which is highly unrealistic, but convenient.

Route manager waypoints are entered as a navaid ident, an explicit latitude/longitude pair, or as an offset (bearing and distance) from another navaid. Each waypoint may also have an altitude associated with it, for vertical navigation modes (VNAV). In the future, other data, especially speed restrictions, may also be associated with waypoints.

==Defining a Route==
The simplest way to define a route is to add waypoints one at a time by identifier. Since navaid identifiers are not unique, the route-manager uses your departure airport or the previously defined waypoint to 'locate' the identifier search. In practice, navaids with conflicting names are located far enough apart that this works automatically in practice.

Until departure and arrival procedures are supported, you can often define them yourself, by creating offset waypoints. The syntax is <tt>ident/radial/distance</tt>, for example <tt>TLA/347/13</tt> defines a waypoint (which will be named 'TLA13') which is 13nm away from the TLA VOR on magnetic radial 347.

Routes can be loaded (and soon, saved) to a simple XML format, so you may prefer to create the routes in a text editor, and load them instead of entering them by hand. Support for flight-planning tools is also planned, contact the developer list if you are interested on working on such a feature.

In the future, auto-routing using airways or VOR-VOR routing will also be added.

==Activating a Route==
Activating a route performs certain checks, and creates start and end waypoints based on the selected departure and arrival info. For the moment, that consists of adding the departure runway as waypoint zero, but in the future (when departure procedures are supported) this will create the appropriate procedure waypoints.

This will also be the hook point for calculating cruise information, such as top-of-climb and top-of-descent points in the future.

Other devices (especially a GPS/FMS) may trigger other changes based on activating a route, such as sequencing the first leg of the route, resetting internal counters / timers, and so on.

==Flying a Route==

Flying a route depends partly on whether the aircraft includes a navigation computer system (for example, an INS or GPS), or not.

===Aircraft without a navigation system===
The route-manager is in 'auto-sequencing' mode; it will compute some basic route data (such as the total route distance remaining), and automatically switch to the next waypoint (sequencing) when passing the current waypoint. This will never drive the aircraft's autopilot (generic or aircraft-specific) - there is no connection between the route-manager and autopilot systems in this situation.

This mode lets you use the route-manger in aircraft that would never have featured a navigation computer (eg, a WW1-era fighter), but only to the extent that the pilot reads the route-manager information and flies accordingly.

===Aircraft with a GPS, INS, FMS===
It is assumed the navigation system disables route-manager auto-sequencing (and some other automatic behaviours), and handles all navigation itself. In this case, the route manager is simply providing a library of waypoints; it's up to a specific navigation / autopilot system to follow courses, establish vertical navigation, and so on. Depending on the real-world system being modelled, fully automatic flight may be possible, controlling lateral and vertical navigation as well as speed - but equally, some real world GPS and INS units may not even be connected to the autopilot, and require manual intervention to command the aircraft.

==Properties==
When a route is active, the route-manage provides various pieces of information based upon current aircraft position / speed, and the route progress. These values would be calculated by the navigation computer in a real system, but are handled by route-manage in FG for convenience. Values logged include the takeoff time, estimated time enroute (ETE), distance remaining enroute, and so on - browse the property tree to see what's available.

FlightGear Launch Control

2009-10-07T03:51:04Z

Stepfaw: /* Advanced Options */

'''Fgrun''' is a graphical front end for [[FlightGear]], distributed and developed separately at http://sourceforge.net/projects/fgrun. However, it was included in officially distributed binaries for FlightGear, even though it is not technically a part the FlightGear program, like several other frontends (see also [[FlightGear related projects]]). Fgrun allows one to choose options more easily than with the [[Command_Line_Parameters|command line]]. (see also [[FlightGear 1.0 aircraft names for command line]])

The application has two main parts : a wizard to choose common options, and an advanced section where all options are available for advanced users.

Options choosen are automatically saved in a file and are reused the next time fgrun is restarted.

For information on compiling this software see [[Building FlightGear Launch Control]].

== The Wizard ==
The wizard appears to the user when fgrun is started. The first time, when no path are set, the first page is shown, otherwise, it jumps directly to the second page, but the first one is still accessible by hitting the "Prev" button.

[[Image:fgrun-page1.jpg|thumb|300px]]
=== Page One - Paths ===
In the first page, the paths needed by fgrun are recalled and can be set. If fgrun was installed with a binary package, either under Windows or Linux, these paths are normally initialized by the installation procedure.

The 'Executable' box is the full path to the FlightGear program. One can choose it directly using the file selection dialog that pops up when the folder button is hit.

The 'FG_ROOT' field is the full path to the FlightGear Base Package. It isn't the value of the $FG_ROOT ( or %FG_ROOT% under Windows ) environment variable. If this path is wrong, no [[Aircraft]] would be displayed and FlightGear won't run.

The 'FG_SCENERY' list is the path list to [[scenery]] folders. These folders usually have a 'Terrain', and optionally a 'Objects' , subfolders. One add a new path with the 'Add...' button. Priorities among folders are managed with the up and down arrows.

The 'Airports Cache' field shows the location of the file that stores the airport ids found in the scenery. It is faster to access that file than to scan scenery directories to build the airport list. It is possible to delete that file if things go wrong. That will force a new scan when the third page will be shown.

: '''Hint'''
:If things goes wrong and FlightGear can't start anymore, and you want to start over with a bare installation, remove or rename the file named 'fgrun.prefs' located in the parent directory of the airport cache file. You will have to reenter path by hand, but the silly options you could have entered will be deleted.

[[Image:fgrun-page2.jpg|thumb|300px]]

=== Page Two - Aircraft Selection ===
The second page, usually the first page seen by users when starting fgrun, is the aircraft selection page. It shows the list of aircrafts found in FG_ROOT/Aircraft and the model of the selected aircraft, spinning.

[[Image:fgrun-page3.jpg|thumb|300px]]
=== Page Three - Airport Selection ===
The third page is the Airport and Runway selection box. It only shows the content of the Airport Cache file, that should be the reflect of the content of the scenery folders. If a new scenery has been installed and doesn't show up, or an old scenery has been deleted and airport are still there, click on the 'Refresh' button to rescan the scenery directories. The scan occurs the first time or when the Airport Cache has been deleted.

[[Image:fgrun-page4.jpg|thumb|300px]]
=== Page Four - Options and Run ===
The last page shows common options without the need to go to the Advanced section.

:'''Hint'''
: Usually, people new to FlightGear should stick there and experience a simple flight before going to the advanced section. This way, it will be easier to diagnose problem if, by accident, FlightGear would not start or run. Often problems come from incoherent options choosen, and there is no fool guard beyond this limit. If FG doen't run anyway, it will be time to look at the hardware setup.

The command line is helpful to people wanting to diagnose a problem. Last released fgrun for Windows doesn't allow copy / paste due to a problem in fltk. The next one will allow that.

The 'Run' button starts FlightGear with the options shown in the command line box.

== Advanced Options ==
[[Image:fgrun-wiki-a01.jpg|thumb|300px]]
===General===
* '''FG_SCENERY:''' Where's your [[scenery]] saved on your computer?
* '''Control:''' Wich controller do you use?
* '''Airport:''' Your start airport.
* '''Runway:''' Start runway of your airport (see above).
* '''Aircraft:''' Your flying vehicle/[[aircraft]].
* '''Language:''' The language of FlightGear.

[[Image:fgrun-wiki-a02.jpg|thumb|300px]]
===Features===
* '''Game Mode:''' The full screen game mode.
* '''Random Objects:''' Enable random [[scenery]] objects.
* '''Sound:''' Enable sound effects like engine sounds.
* '''HUD:''' Enable Heads Up Display (HUD).
* '''AI Traffic:''' Enable [[AI traffic]].

[[Image:fgrun-wiki-a03.jpg|thumb|300px]]
===Flight Model===

[[Image:fgrun-wiki-a04.jpg|thumb|300px]]
===Freeze===
* '''Freeze:''' Start paused'.

[[Image:fgrun-wiki-a05.jpg|thumb|300px]]
===Initial Posititon===
* '''Longitude:''' What's your longitude?
* '''Latitude:''' What's your latitude?
* '''Altitude:''' What's your altitude?
* '''Heading:''' The aircraft heading (yaw) angle.
* '''Airspeed:''' Your airspeed in knots.

[[Image:fgrun-wiki-a06.jpg|thumb|300px]]
===Rendering===
* '''Clouds:''' Are there any clouds up in the air?
* '''3D Clouds:''' Are the clouds 3D?
* '''Full Screen:''' Want to play on full screen?
* '''Wireframe:''' Do you wanna see only the wires of the [[scenery]] and the [[aircraft]]s?
* '''Visibility:''' Visibility distance in meters or miles.
* '''Bpp:''' Color depth in Bits per pixel.
* '''FOV:''' Field of View angle.

[[Image:fgrun-wiki-a07.jpg|thumb|300px]]
===Time===
* '''Time match local:''' Synchronisize simulation time with local time.
* '''Time of day:''' What's the time of the day?

[[Image:fgrun-wiki-a08.jpg|thumb|300px]]
===Network===
* '''Callsign:''' your callsign for the network. This is used to recognize other pilots and for tracking your flights.

'''See:''' [[Multiplayer Howto]]

[[Image:fgrun-wiki-a09.jpg|thumb|300px]]
===Input/Output===

[[Image:fgrun-wiki-a10.jpg|thumb|300px]]
===Avionics===

[[Image:fgrun-wiki-a11.jpg|thumb|300px]]
===Properties===
This is where you could edit or add new parameters. It's same as configuring the Command Line.

'''See:''' [[Command Line Parameters]]

[[Image:fgrun-wiki-a12.jpg|thumb|300px]]
=== Debugging ===
* '''Log Level:''' The lower the log level, the less errors you'll see. A higher log level can increase the loading time extremely.
* '''Trace Read Properties:'''
* '''Trace Write Properties:'''

[[Image:fgrun-wiki-a13.jpg|thumb|300px]]

=== Environment ===

[[Image:fgrun-wiki-a14.jpg|thumb|300px]]
=== Weather ===
* '''Wind Direction:''' Direction of the wind.
* '''Heading:''' Directon wind is coming from.
* '''Speed:''' Wind speed in knots (kts).

[[Image:fgrun-wiki-a15.jpg|thumb|300px]]
=== Clouds ===
* '''Elevation:''' How high (in feet) are the clouds?
* '''Thickness:''' How thick (in feet) are the clouds?

[[Category:Software]]
[[Category:GPL]]

FlightGear Launch Control

2009-10-07T03:49:12Z

Stepfaw: /* Page One - Paths */

'''Fgrun''' is a graphical front end for [[FlightGear]], distributed and developed separately at http://sourceforge.net/projects/fgrun. However, it was included in officially distributed binaries for FlightGear, even though it is not technically a part the FlightGear program, like several other frontends (see also [[FlightGear related projects]]). Fgrun allows one to choose options more easily than with the [[Command_Line_Parameters|command line]]. (see also [[FlightGear 1.0 aircraft names for command line]])

The application has two main parts : a wizard to choose common options, and an advanced section where all options are available for advanced users.

Options choosen are automatically saved in a file and are reused the next time fgrun is restarted.

For information on compiling this software see [[Building FlightGear Launch Control]].

== The Wizard ==
The wizard appears to the user when fgrun is started. The first time, when no path are set, the first page is shown, otherwise, it jumps directly to the second page, but the first one is still accessible by hitting the "Prev" button.

[[Image:fgrun-page1.jpg|thumb|300px]]
=== Page One - Paths ===
In the first page, the paths needed by fgrun are recalled and can be set. If fgrun was installed with a binary package, either under Windows or Linux, these paths are normally initialized by the installation procedure.

The 'Executable' box is the full path to the FlightGear program. One can choose it directly using the file selection dialog that pops up when the folder button is hit.

The 'FG_ROOT' field is the full path to the FlightGear Base Package. It isn't the value of the $FG_ROOT ( or %FG_ROOT% under Windows ) environment variable. If this path is wrong, no [[Aircraft]] would be displayed and FlightGear won't run.

The 'FG_SCENERY' list is the path list to [[scenery]] folders. These folders usually have a 'Terrain', and optionally a 'Objects' , subfolders. One add a new path with the 'Add...' button. Priorities among folders are managed with the up and down arrows.

The 'Airports Cache' field shows the location of the file that stores the airport ids found in the scenery. It is faster to access that file than to scan scenery directories to build the airport list. It is possible to delete that file if things go wrong. That will force a new scan when the third page will be shown.

: '''Hint'''
:If things goes wrong and FlightGear can't start anymore, and you want to start over with a bare installation, remove or rename the file named 'fgrun.prefs' located in the parent directory of the airport cache file. You will have to reenter path by hand, but the silly options you could have entered will be deleted.

[[Image:fgrun-page2.jpg|thumb|300px]]

=== Page Two - Aircraft Selection ===
The second page, usually the first page seen by users when starting fgrun, is the aircraft selection page. It shows the list of aircrafts found in FG_ROOT/Aircraft and the model of the selected aircraft, spinning.

[[Image:fgrun-page3.jpg|thumb|300px]]
=== Page Three - Airport Selection ===
The third page is the Airport and Runway selection box. It only shows the content of the Airport Cache file, that should be the reflect of the content of the scenery folders. If a new scenery has been installed and doesn't show up, or an old scenery has been deleted and airport are still there, click on the 'Refresh' button to rescan the scenery directories. The scan occurs the first time or when the Airport Cache has been deleted.

[[Image:fgrun-page4.jpg|thumb|300px]]
=== Page Four - Options and Run ===
The last page shows common options without the need to go to the Advanced section.

:'''Hint'''
: Usually, people new to FlightGear should stick there and experience a simple flight before going to the advanced section. This way, it will be easier to diagnose problem if, by accident, FlightGear would not start or run. Often problems come from incoherent options choosen, and there is no fool guard beyond this limit. If FG doen't run anyway, it will be time to look at the hardware setup.

The command line is helpful to people wanting to diagnose a problem. Last released fgrun for Windows doesn't allow copy / paste due to a problem in fltk. The next one will allow that.

The 'Run' button starts FlightGear with the options shown in the command line box.

== Advanced Options ==
[[Image:fgrun-wiki-a01.jpg|thumb|300px]]
===General===
* '''FG_SCENERY:''' Where's your [[scenery]] saved on your computer?
* '''Control:''' Wich controller do you use?
* '''Airport:''' Your start [[airport]].
* '''Runway:''' Start runway of your airport (see above).
* '''Aircraft:''' Your flying vehicle/[[aircraft]].
* '''Language:''' The language of FlightGear.

[[Image:fgrun-wiki-a02.jpg|thumb|300px]]
===Features===
* '''Game Mode:''' The full screen game mode.
* '''Random Objects:''' Enable random [[scenery]] objects.
* '''Sound:''' Enable sound effects like engine sounds.
* '''HUD:''' Enable Heads Up Display (HUD).
* '''AI Traffic:''' Enable [[AI traffic]].

[[Image:fgrun-wiki-a03.jpg|thumb|300px]]
===Flight Model===

[[Image:fgrun-wiki-a04.jpg|thumb|300px]]
===Freeze===
* '''Freeze:''' Start paused'.

[[Image:fgrun-wiki-a05.jpg|thumb|300px]]
===Initial Posititon===
* '''Longitude:''' What's your longitude?
* '''Latitude:''' What's your latitude?
* '''Altitude:''' What's your altitude?
* '''Heading:''' The aircraft heading (yaw) angle.
* '''Airspeed:''' Your airspeed in knots.

[[Image:fgrun-wiki-a06.jpg|thumb|300px]]
===Rendering===
* '''Clouds:''' Are there any clouds up in the air?
* '''3D Clouds:''' Are the clouds 3D?
* '''Full Screen:''' Want to play on full screen?
* '''Wireframe:''' Do you wanna see only the wires of the [[scenery]] and the [[aircraft]]s?
* '''Visibility:''' Visibility distance in meters or miles.
* '''Bpp:''' Color depth in Bits per pixel.
* '''FOV:''' Field of View angle.

[[Image:fgrun-wiki-a07.jpg|thumb|300px]]
===Time===
* '''Time match local:''' Synchronisize simulation time with local time.
* '''Time of day:''' What's the time of the day?

[[Image:fgrun-wiki-a08.jpg|thumb|300px]]
===Network===
* '''Callsign:''' your callsign for the network. This is used to recognize other pilots and for tracking your flights.

'''See:''' [[Multiplayer Howto]]

[[Image:fgrun-wiki-a09.jpg|thumb|300px]]
===Input/Output===

[[Image:fgrun-wiki-a10.jpg|thumb|300px]]
===Avionics===

[[Image:fgrun-wiki-a11.jpg|thumb|300px]]
===Properties===
This is where you could edit or add new parameters. It's same as configuring the Command Line.

'''See:''' [[Command Line Parameters]]

[[Image:fgrun-wiki-a12.jpg|thumb|300px]]
=== Debugging ===
* '''Log Level:''' The lower the log level, the less errors you'll see. A higher log level can increase the loading time extremely.
* '''Trace Read Properties:'''
* '''Trace Write Properties:'''

[[Image:fgrun-wiki-a13.jpg|thumb|300px]]

=== Environment ===

[[Image:fgrun-wiki-a14.jpg|thumb|300px]]
=== Weather ===
* '''Wind Direction:''' Direction of the wind.
* '''Heading:''' Directon wind is coming from.
* '''Speed:''' Wind speed in knots (kts).

[[Image:fgrun-wiki-a15.jpg|thumb|300px]]
=== Clouds ===
* '''Elevation:''' How high (in feet) are the clouds?
* '''Thickness:''' How thick (in feet) are the clouds?

[[Category:Software]]
[[Category:GPL]]

File:Montreal Airport.jpg

2009-10-06T21:58:55Z

Stepfaw: Montréal-Pierre Elliott Trudeau International Airport

Montréal-Pierre Elliott Trudeau International Airport

User:Stepfaw

2009-10-06T17:02:13Z

Stepfaw: