FlightGear wiki - User contributions [en]

FlightGear hangars

2014-05-16T20:42:26Z

Rickace:

{{cleanup}}

''See [[Links]] for an overall listing of FlightGear related external websites''

FlightGear has [[aircraft]] and other content available from 3rd-party hangars, some which are GPL compatible and also included in official distributions while others are independent. Aircraft versions range from requiring a developmental build, to being compatible with the latest primary release, to requiring an older version.

Be careful with external links!

== Official hangars ==
=== Aircraft ===
* [http://www.flightgear.org/download/aircraft-2-12-filterable/ FlightGear Official 2.12 Hangar]
* [http://www.flightgear.org/download/aircraft-2-10-filterable/ FlightGear Official 2.10 Hangar]
* [http://www.flightgear.org/download/aircraft-v2-8/ FlightGear Official 2.8 Hangar]
* [http://www.flightgear.org/download/aircraft-v2-6/ FlightGear Official 2.6 Hangar]
* [http://www.flightgear.org/download/aircraft-v2-4/ FlightGear Official 2.4 Hangar] (Legacy site)
* [http://www.flightgear.org/Downloads/aircraft-2.0.0/ FlightGear Official 2.0 Hangar] (Legacy site)
* [http://gitorious.org/fg/fgdata/trees/master/Aircraft Git Hangar] (for [[Git]] builds)

=== Liveries ===
* [http://liveries.flightgear.org FlightGear Livery Database]

== Unofficial sites ==
=== Aircraft hangars ===
* [http://fg-acjza.wix.com/hangar/ ACJZA Hangar] (Land, Sea, Air)
* [https://www.gitorious.org/airbus-aircraft Airbus Aircraft Development Git] (A320, A330, A340-300, A380 - various authors)
* [http://www.gidenstam.org/FlightGear/Airships/ Anders Lighter-than-air Hangar] with [http://gitorious.org/anders-hangar aircraft repositories at gitorious].
* [http://andinogonthaeler.wordpress.com/ Andino's Hangar] (Boeing 707-3J9C and 707-320C, 777-200LR).
* [http://flighthgearcolombia.jimdo.com/ Hangar colombiano] Colombian airlines and militaries aircraft FAC.
* [http://www.buckarooshangar.com/flightgear/ Buckaroo's Hangar] (Velocity XL RG, Edgley Optica, Lockheed 1049H Constellation, Grumman Goose, McDonnell Douglas MD-81) (& a YASim intro)
* [http://charles.ingels.free.fr/flightgear/ French FlightGear Hangar] (FR) (Aermacchi MB326, Dassault Mirage F1 Mikoyan Gurevitch Mig 31 Foxhound, and more)
* [http://fgnl.freehostia.com/ Gijs Hangar] (Aircraft, Liveries, Scenery, Vehicles)
* [https://sites.google.com/site/fghangar JOFH - Just Another Flightgear Hangar] (JA-37, scenario)
* [http://hcilab.uniud.it/pan/downloads.html HCI Lab - University of Udine] (Aermacchi MB339 Frecce Tricolori)
* [http://helijah.free.fr/flightgear/hangar.htm Helijah FlightGear Hangar] (200+ original aircraft)
* [http://hhfgfs.weebly.com/index.html Hellcat's FlightGear Hangar] (scenarios, skins, film inspired aerospace vehicles)
* [http://www.hoerbird.net/aircrafts.html Hoerbird Hangar] (misc. projects)
* [http://horizonflightgearhangar.yolasite.com/ Horizon Flightgear Hangar] Dabolim Naval Air Station (VAGO), Goa, India; Murray Bridge/Pallama Airfield (YMBD), Australia; and ADFX-02 Morgan, a fictional aircraft.
* [http://hsotfhangar.wordpress.com/ HSOTF Official Hangar]
* [http://mysite.verizon.net/vzeuyecs/ Kent Esbenshade's Boneyard Hangar] (Classic aircraft)
* <s>[http://flightgear.bplaced.de/ longfly's hangar] (not only German!)</s> {{dead link|2014-01}}
** <s>[http://flightgear.bplaced.de/filemanager/aircraft-list/index.html list of all aircrafts]</s> (under development) {{dead link|2014-01}}
* [http://nickfg.blogspot.com/ Nick's FlightGear Hangar] (Blog, CRJ-200)
* [http://theomegahangar.flymerlion.org/ Omega Hangar] (Embraer E-jet Family, A330-200, A320neo, CRJ-700 Full First Class, ATR-42-family, A321-series, Mobile Stairway)
* [http://equipe-flightgear.forumactif.com/t835-hangar-de-la-paf-paf-team-hangar#14330 PAF team Hangar] (Cap 10b, Robin DR400 JSBSim, Douglas DC-3 C47, Tecnam P92 Echo...)
* [http://pjedvaj.eu5.org/ pjedvaj's Hangar] (MiG-21bis, PC-9M, PC-21, T-50, Harrier GR.1, F-35B, RAH-66)
* [http://presteshangar.wikidot.com/start Prestes Hangar] (many Brazilian aircraft articles)
* [http://riktov.synthasite.com/ Riktov's FlightGear Hangar] (BN-2 Islander, Giant Marshmallow Man)
* [http://digilander.libero.it/scighera_fg/index.html Scighera's Hangar] (models & liveries)
* [http://seahorseCorral.org/flightgear_aircraft.html Stewart's SEA-horse Aircraft Hanger]
* <s>[http://sydhangar.daffodil.uk.com/ Syd's Hangar ]</s>{{dead link|2012-04}} (older 1.9 versions) [https://sites.google.com/site/sydshangar/ Syd's Google Hangar ] (newer 2.0 versions)
* [http://macflightgear.sourceforge.net/home/aircraft Tat's Aircraft for FlightGear] (A6M2 "Zero", J7W, Ki-84, T-4, HondaJet, OH-1, K5Y1, RV-6A, YS-11)
* [http://vicmar.weebly.com/ VicMar] (Yanagisawa Gen H-4, Stung Biker, Quad Bikes, SRN4, Water Skier, G2 Thunderpack, Martin Jetpack)
* [http://www.treborlogic.com/fgfs/hangar/ Yourgod's Hangar: Douglas DC-8]

=== Old Hangars ===
* <s>[http://croo.murgl.org/fgfs/index.html A-10 and A-6 stuff]</s>
* <s>[http://www.sol2500.net/flightgear/aircraft.html DFaber Hangar]</s>{{dead link|2012-04}} (Eurofighter, PC-6, Bf 109, Beufighter, F4U, Ju 52, DH Mosquito, G. Albatross, F-86, and more)
* [http://pagesperso-orange.fr/GRTux/tux/index-en.html GRTux Hangar] (28+ aircraft and add-ons) (last updated 2011)
* <s>[http://thefancyflightgearhangar.blogspot.com the fancy flight gear hangar]</s>{{dead link|2012-04}} (a few well made aircraft)
* <s>[http://flier95-flightgear.blogspot.com/ Flier95's Hangar]</s>{{dead link|2012-08}} (Blog format)
* [http://www.ae.uiuc.edu/m-selig/apasim/Aircraft-uiuc.html UIUC Hangar] (for FGFS 0.7.8, last update 2002)

=== Livery/Scenery hangars ===
* [http://berwickskins.yolasite.com/ Berwick-skins]
* [http://dliveryhangar.synthasite.com/ Dodger4's Livery Hangar]
* [http://hsotfhangar.wordpress.com/ HSOTF Official Hangar]
* [http://jchnd.blogspot.com/ JcHnd's Liveries for FlightGear]
* [http://lukashangar.jimdo.com/ Lukas' hangar] (Scenery projects, Liveries)
* [http://mojos-hangar.webs.com/ MOJO's Flightgear Livery Hangar]
* <s>[http://members.cox.net/scotsg8r/hangar/ N-SCOT's Hangar]</s>{{dead link|2012-04}} (5+ liveries & mods)
* <s>[https://planepainter.yolasite.com/ The Planepainter]</s>{{dead link|2012-04}} (Liveries, Scenery)
* [http://simbabeathangar.webs.com/ Simbabeat's Livery Hangar]

=== Homepages, blogs, etc. ===
* [http://www.jaunty.bplaced.net/flightgear/index.php A small FlightGear page]
* <s>[http://www.flightgeararg.com.ar/ Argentina Flightgear Community Portal]</s>{{dead link|2013-01}}
* [http://daveshangar.blogspot.com/ Dave's Hangar Blog]
* [http://helldiversquadron.wordpress.com/ Helldiver Squadron Offensive Tactical Force Homepage]
* [http://djrick1.wix.com/grupofgbr Grupo FGBR Brazilian Portal] (Broken site - only accesible with flash player)
* [http://flightgearblog.blogspot.com/ FlightGear Blog] (Last post Dec. 2008)
* [http://flightgear2009.blogspot.com/ FlightGear Brasil 2009] (non-english)
* [http://geoffmclane.com/fg/index.htm FlightGear Build Centre]
* [http://www.flightgearcanada.ca/ FlightGear Canada] (The home of everything Canadian for FlightGear)
* [http://flightgearcorner.tk The FlightGear Corner] (News, Downloads, Tutorials and more)
* [http://www.fguk.eu/ FlightGear United Kingdom]
* [http://hsotfhangar.wordpress.com/ HSOTF Official Hangar]
* [http://www.emmerich-j.de/FGFS/index.html jomo's FlightGear Homepage]
* [http://flightgear.mxchange.org/ Quix0r's FlightGear Website] Simple tutorials and fgdata.bundle
* <s>[http://tehwarlock.tk/ Tehwarlock Blog]</s>{{dead link|2012-04}}
* [http://www.vivefg.org/ Vive FlightGear!] Aircrafts, scenery, manuals and forum (non-english)

=== Other FlightGear repositories/mirrors ===
* [http://www.flightgearplanes.com Flightgear Planes Website]
* [http://hsotfhangar.wordpress.com/ HSOTF Official Hangar]
* [http://lukeafg.com/ LukeaFG] (FlightGear tutorials and developments)
* [http://ftp.riken.go.jp/pub/FreeBSD/distfiles/flightgear-aircrafts/ Older versions of FlightGear aircraft]
* [http://www.unitedfreeworld.com/ Unitedfreeworld] (scenery, plane models, and livery)

== Related content ==
* [[Table of models]]
* [[Aircraft]] - [[Helicopter]] - [[Vehicle]]

[[Category:Lists]]

FlightGear hangars

2014-05-16T20:39:53Z

Rickace: Git repositories are not hangars. Removed secondary GIT repository links where hangars were already available.

{{cleanup}}

''See [[Links]] for an overall listing of FlightGear related external websites''

FlightGear has [[aircraft]] and other content available from 3rd-party hangars, some which are GPL compatible and also included in official distributions while others are independent. Aircraft versions range from requiring a developmental build, to being compatible with the latest primary release, to requiring an older version.

Be careful with external links!

== Official hangars ==
=== Aircraft ===
* [http://www.flightgear.org/download/aircraft-2-12-filterable/ FlightGear Official 2.12 Hangar]
* [http://www.flightgear.org/download/aircraft-2-10-filterable/ FlightGear Official 2.10 Hangar]
* [http://www.flightgear.org/download/aircraft-v2-8/ FlightGear Official 2.8 Hangar]
* [http://www.flightgear.org/download/aircraft-v2-6/ FlightGear Official 2.6 Hangar]
* [http://www.flightgear.org/download/aircraft-v2-4/ FlightGear Official 2.4 Hangar] (Legacy site)
* [http://www.flightgear.org/Downloads/aircraft-2.0.0/ FlightGear Official 2.0 Hangar] (Legacy site)
* [http://gitorious.org/fg/fgdata/trees/master/Aircraft Git Hangar] (for [[Git]] builds)

=== Liveries ===
* [http://liveries.flightgear.org FlightGear Livery Database]

== Unofficial sites ==
=== Aircraft hangars ===
* [http://fg-acjza.wix.com/hangar/ ACJZA Hangar] (Land, Sea, Air)
* [http://www.gidenstam.org/FlightGear/Airships/ Anders Lighter-than-air Hangar] with [http://gitorious.org/anders-hangar aircraft repositories at gitorious].
* [http://andinogonthaeler.wordpress.com/ Andino's Hangar] (Boeing 707-3J9C and 707-320C, 777-200LR).
* [http://flighthgearcolombia.jimdo.com/ Hangar colombiano] Colombian airlines and militaries aircraft FAC.
* [http://www.buckarooshangar.com/flightgear/ Buckaroo's Hangar] (Velocity XL RG, Edgley Optica, Lockheed 1049H Constellation, Grumman Goose, McDonnell Douglas MD-81) (& a YASim intro)
* [http://charles.ingels.free.fr/flightgear/ French FlightGear Hangar] (FR) (Aermacchi MB326, Dassault Mirage F1 Mikoyan Gurevitch Mig 31 Foxhound, and more)
* [http://fgnl.freehostia.com/ Gijs Hangar] (Aircraft, Liveries, Scenery, Vehicles)
* [https://sites.google.com/site/fghangar JOFH - Just Another Flightgear Hangar] (JA-37, scenario)
* [http://hcilab.uniud.it/pan/downloads.html HCI Lab - University of Udine] (Aermacchi MB339 Frecce Tricolori)
* [http://helijah.free.fr/flightgear/hangar.htm Helijah FlightGear Hangar] (200+ original aircraft)
* [http://hhfgfs.weebly.com/index.html Hellcat's FlightGear Hangar] (scenarios, skins, film inspired aerospace vehicles)
* [http://www.hoerbird.net/aircrafts.html Hoerbird Hangar] (misc. projects)
* [http://horizonflightgearhangar.yolasite.com/ Horizon Flightgear Hangar] Dabolim Naval Air Station (VAGO), Goa, India; Murray Bridge/Pallama Airfield (YMBD), Australia; and ADFX-02 Morgan, a fictional aircraft.
* [http://hsotfhangar.wordpress.com/ HSOTF Official Hangar]
* [http://mysite.verizon.net/vzeuyecs/ Kent Esbenshade's Boneyard Hangar] (Classic aircraft)
* <s>[http://flightgear.bplaced.de/ longfly's hangar] (not only German!)</s> {{dead link|2014-01}}
** <s>[http://flightgear.bplaced.de/filemanager/aircraft-list/index.html list of all aircrafts]</s> (under development) {{dead link|2014-01}}
* [http://nickfg.blogspot.com/ Nick's FlightGear Hangar] (Blog, CRJ-200)
* [http://theomegahangar.flymerlion.org/ Omega Hangar] (Embraer E-jet Family, A330-200, A320neo, CRJ-700 Full First Class, ATR-42-family, A321-series, Mobile Stairway)
* [http://equipe-flightgear.forumactif.com/t835-hangar-de-la-paf-paf-team-hangar#14330 PAF team Hangar] (Cap 10b, Robin DR400 JSBSim, Douglas DC-3 C47, Tecnam P92 Echo...)
* [http://pjedvaj.eu5.org/ pjedvaj's Hangar] (MiG-21bis, PC-9M, PC-21, T-50, Harrier GR.1, F-35B, RAH-66)
* [http://presteshangar.wikidot.com/start Prestes Hangar] (many Brazilian aircraft articles)
* [http://riktov.synthasite.com/ Riktov's FlightGear Hangar] (BN-2 Islander, Giant Marshmallow Man)
* [http://digilander.libero.it/scighera_fg/index.html Scighera's Hangar] (models & liveries)
* [http://seahorseCorral.org/flightgear_aircraft.html Stewart's SEA-horse Aircraft Hanger]
* <s>[http://sydhangar.daffodil.uk.com/ Syd's Hangar ]</s>{{dead link|2012-04}} (older 1.9 versions) [https://sites.google.com/site/sydshangar/ Syd's Google Hangar ] (newer 2.0 versions)
* [http://macflightgear.sourceforge.net/home/aircraft Tat's Aircraft for FlightGear] (A6M2 "Zero", J7W, Ki-84, T-4, HondaJet, OH-1, K5Y1, RV-6A, YS-11)
* [http://vicmar.weebly.com/ VicMar] (Yanagisawa Gen H-4, Stung Biker, Quad Bikes, SRN4, Water Skier, G2 Thunderpack, Martin Jetpack)
* [http://www.treborlogic.com/fgfs/hangar/ Yourgod's Hangar: Douglas DC-8]

=== Old Hangars ===
* <s>[http://croo.murgl.org/fgfs/index.html A-10 and A-6 stuff]</s>
* <s>[http://www.sol2500.net/flightgear/aircraft.html DFaber Hangar]</s>{{dead link|2012-04}} (Eurofighter, PC-6, Bf 109, Beufighter, F4U, Ju 52, DH Mosquito, G. Albatross, F-86, and more)
* [http://pagesperso-orange.fr/GRTux/tux/index-en.html GRTux Hangar] (28+ aircraft and add-ons) (last updated 2011)
* <s>[http://thefancyflightgearhangar.blogspot.com the fancy flight gear hangar]</s>{{dead link|2012-04}} (a few well made aircraft)
* <s>[http://flier95-flightgear.blogspot.com/ Flier95's Hangar]</s>{{dead link|2012-08}} (Blog format)
* [http://www.ae.uiuc.edu/m-selig/apasim/Aircraft-uiuc.html UIUC Hangar] (for FGFS 0.7.8, last update 2002)

=== Livery/Scenery hangars ===
* [http://berwickskins.yolasite.com/ Berwick-skins]
* [http://dliveryhangar.synthasite.com/ Dodger4's Livery Hangar]
* [http://hsotfhangar.wordpress.com/ HSOTF Official Hangar]
* [http://jchnd.blogspot.com/ JcHnd's Liveries for FlightGear]
* [http://lukashangar.jimdo.com/ Lukas' hangar] (Scenery projects, Liveries)
* [http://mojos-hangar.webs.com/ MOJO's Flightgear Livery Hangar]
* <s>[http://members.cox.net/scotsg8r/hangar/ N-SCOT's Hangar]</s>{{dead link|2012-04}} (5+ liveries & mods)
* <s>[https://planepainter.yolasite.com/ The Planepainter]</s>{{dead link|2012-04}} (Liveries, Scenery)
* [http://simbabeathangar.webs.com/ Simbabeat's Livery Hangar]

=== Homepages, blogs, etc. ===
* [http://www.jaunty.bplaced.net/flightgear/index.php A small FlightGear page]
* <s>[http://www.flightgeararg.com.ar/ Argentina Flightgear Community Portal]</s>{{dead link|2013-01}}
* [http://daveshangar.blogspot.com/ Dave's Hangar Blog]
* [http://helldiversquadron.wordpress.com/ Helldiver Squadron Offensive Tactical Force Homepage]
* [http://djrick1.wix.com/grupofgbr Grupo FGBR Brazilian Portal] (Broken site - only accesible with flash player)
* [http://flightgearblog.blogspot.com/ FlightGear Blog] (Last post Dec. 2008)
* [http://flightgear2009.blogspot.com/ FlightGear Brasil 2009] (non-english)
* [http://geoffmclane.com/fg/index.htm FlightGear Build Centre]
* [http://www.flightgearcanada.ca/ FlightGear Canada] (The home of everything Canadian for FlightGear)
* [http://flightgearcorner.tk The FlightGear Corner] (News, Downloads, Tutorials and more)
* [http://www.fguk.eu/ FlightGear United Kingdom]
* [http://hsotfhangar.wordpress.com/ HSOTF Official Hangar]
* [http://www.emmerich-j.de/FGFS/index.html jomo's FlightGear Homepage]
* [http://flightgear.mxchange.org/ Quix0r's FlightGear Website] Simple tutorials and fgdata.bundle
* <s>[http://tehwarlock.tk/ Tehwarlock Blog]</s>{{dead link|2012-04}}
* [http://www.vivefg.org/ Vive FlightGear!] Aircrafts, scenery, manuals and forum (non-english)

=== Other FlightGear repositories/mirrors ===
* [http://www.flightgearplanes.com Flightgear Planes Website]
* [http://hsotfhangar.wordpress.com/ HSOTF Official Hangar]
* [http://lukeafg.com/ LukeaFG] (FlightGear tutorials and developments)
* [http://ftp.riken.go.jp/pub/FreeBSD/distfiles/flightgear-aircrafts/ Older versions of FlightGear aircraft]
* [http://www.unitedfreeworld.com/ Unitedfreeworld] (scenery, plane models, and livery)

== Related content ==
* [[Table of models]]
* [[Aircraft]] - [[Helicopter]] - [[Vehicle]]

[[Category:Lists]]

State Capitol Buildings in the United States

2014-05-06T02:36:09Z

Rickace:

== State Capitol Buildings ==

Most U.S. states (39 of the 50) have facilities named "State Capitol". Indiana and Ohio use the term "Statehouse" and eight states use "State House": Maine, Maryland, Massachusetts, New Hampshire, New Jersey, Rhode Island, South Carolina, and Vermont. Delaware has a "Legislative Hall". The State of Alabama has a State Capitol, but the Legislature has since 1985 met in the State House.

A capitol typically contains the meeting place for its state's legislature and offices for the state's governor, though this is not true for every state. The legislatures of Alabama, Nevada and North Carolina meet in other nearby buildings, but their governor's offices remain in the capitol. The Arizona State Capitol is now strictly a museum, and both the legislature and the governor's office are in nearby buildings. Only Arizona does not have its governor's office in the state capitol, though in Delaware, Ohio, Michigan, Vermont and Virginia,[1] the office there is for ceremonial use only.

In 9 states, the state's highest court also routinely meets in the capitol: Indiana, Kentucky, Nebraska, North Dakota, Oklahoma (both civil and criminal courts), Pennsylvania (one of three sites), South Dakota, West Virginia, and Wisconsin. The other 40 states have separate buildings for their supreme courts, though in Minnesota and Utah the high court also has ceremonial meetings at the capitol.

Eleven state capitols do not feature a dome: the Alaska, Florida, Hawaii, Louisiana, New Mexico, New York, North Dakota, Ohio, Oregon, Tennessee and Virginia state capitols.

== Current Development Status ==

The project asks volunteers to submit a state capitol building for a state that is NOT LISTED below.

* Hawaii - '''''Taken/In Development'''''
* Idaho - '''Completed'''
* Louisiana - '''Completed'''
* Nebraska - '''''Taken/In Development'''''
* New York - '''''Taken/In Development'''''

== Developers' Forum Topic ==

There is a [http://forum.flightgear.org/viewtopic.php?f=5&t=22715 forum topic] dedicated to the development of State Capitol Buildings [http://forum.flightgear.org/viewtopic.php?f=5&t=22715 here].

State Capitol Buildings in the United States

2014-05-06T02:35:23Z

Rickace: Created page with " == State Capitol Project for the United States == Most U.S. states (39 of the 50) have facilities named "State Capitol". Indiana and Ohio use the term "Statehouse" and eight..."

== State Capitol Project for the United States ==

Most U.S. states (39 of the 50) have facilities named "State Capitol". Indiana and Ohio use the term "Statehouse" and eight states use "State House": Maine, Maryland, Massachusetts, New Hampshire, New Jersey, Rhode Island, South Carolina, and Vermont. Delaware has a "Legislative Hall". The State of Alabama has a State Capitol, but the Legislature has since 1985 met in the State House.

A capitol typically contains the meeting place for its state's legislature and offices for the state's governor, though this is not true for every state. The legislatures of Alabama, Nevada and North Carolina meet in other nearby buildings, but their governor's offices remain in the capitol. The Arizona State Capitol is now strictly a museum, and both the legislature and the governor's office are in nearby buildings. Only Arizona does not have its governor's office in the state capitol, though in Delaware, Ohio, Michigan, Vermont and Virginia,[1] the office there is for ceremonial use only.

In 9 states, the state's highest court also routinely meets in the capitol: Indiana, Kentucky, Nebraska, North Dakota, Oklahoma (both civil and criminal courts), Pennsylvania (one of three sites), South Dakota, West Virginia, and Wisconsin. The other 40 states have separate buildings for their supreme courts, though in Minnesota and Utah the high court also has ceremonial meetings at the capitol.

Eleven state capitols do not feature a dome: the Alaska, Florida, Hawaii, Louisiana, New Mexico, New York, North Dakota, Ohio, Oregon, Tennessee and Virginia state capitols.

== Current Development Status ==

The project asks volunteers to submit a state capitol building for a state that is NOT LISTED below.

* Hawaii - '''''Taken/In Development'''''
* Idaho - '''Completed'''
* Louisiana - '''Completed'''
* Nebraska - '''''Taken/In Development'''''
* New York - '''''Taken/In Development'''''

== Developers' Forum Topic ==

There is a [http://forum.flightgear.org/viewtopic.php?f=5&t=22715 forum topic] dedicated to the development of State Capitol Buildings [http://forum.flightgear.org/viewtopic.php?f=5&t=22715 here].

FlightGear Newsletter May 2013

2013-05-30T20:25:51Z

Rickace:

{{newsletter}}
{{TOC_right|limit=2}}

''We would like to emphasize that the monthly newsletter can not live without the contributions of FlightGear users and developers. Everyone with a wiki account (free to register) can edit the newsletter and every contribution is welcome. So if you know about any FlightGear related news or projects such as for example updated scenery or aircraft, please do feel invited to add such news to the newsletter. Core developers are encouraged to add news about their latest work to the newsletter's development section and [[Next Changelog|the changelog of the upcoming release]]. At the end of each month, it's generally a good idea to get in touch with other contributors to ask them to add news about their contributions to the newsletter.''

== Development news ==
Note to all contributors: Please also copy your newsletter additions to the changelog for the upcoming release: [[Next Changelog]].

=== Aircraft Checklists ===
Stuart has pushed a further enhancement to the checklist feature. Aircraft authors may now add one or more <binding> elements to a checklist
<item>. Conceptually, these are the actions that the user should execute to complete the item. The checklist GUI displays items with such <binding>
elements with an additional [>] button. Clicking on the button executes the bindings, allowing the user to watch as the
computer/co-pilot/instructor executes the checklist item.

The <binding> element is exactly as you would expect - so property-assign, nasal etc. works.

Due to the power of Nasal and properties, this feature only required 13 lines of code to write, most of which is displaying the button!

Stuart is planning to extend this function so that checklists with one or more items containing a <binding> element can have an (optional) button
to execute the entire checklist. I'm still thinking of how best to implement this, as I think one would want a gap between each item.

Stuart highlights the property-interpolate command which provides a very convenient way to interpolate a property to a new value. See
Docs/README.commands if you were unaware of this.

Stuart has updated the c172p checklists to use this feature, including some rather cute interpolations of the throttle, mixture and trim controls.

Learn more at [[Aircraft Checklists]]...

=== Transponder ===

Clement (with some help from Vivian) has overhauled the [[Transponder|transponder]] instrument, making it easier to use from panels, supporting Mode-S altitude encoding, and sending the important properties over multi-player. This will allow more realistic ATC interactions, since id (squawk) codes now matter! See [[Transponder|this wiki page]] for more information on installing / updating the transponder installation in aircraft. The common panel-mounted KT-70 instrument will also be getting an overhaul to use the updated C++ code in the next few days.

=== Random Buildings ===


=== Project Rembrandt ===
A number of Mac users have been reporting issues related to running [[Project Rembrandt]] (deferred rendering/shadows) on Mac OSX with ATI/AMD GPUS, we are now looking for Mac users to provide feedback on running Rembrandt on Mac OSX, required information includes errors and warnings shown during startup/runtime, but also screen shots showing any issues. Please see: [[Project Rembrandt#Mac Issues]].

=== Tutorial: Porting custom PUI widgets to Canvas ===
[[File:Nasal-console-with-canvas-loglist-widget-prototype.png|thumb|canvas based loglist widget]]

The shortcomings of our old PUI-based GUI have been repeatedly brought up on the devel list over the years.

In order to eventually phase out PUI completely, we need to stop adding PUI dependencies to the source tree. We now have the Canvas system, and there’s a formal decision to modernize the GUI using the Canvas, and completely replace PUI sooner rather than later.

It was a lot of work to get rid of hard-coded PUI dialogs, and we still have a bunch of hard-coded PUI widgets – as long as we have those, getting totally rid of PUI will be increasingly difficult, because each hard-coded widget will either need to be phased out or manually ported.

Which is exactly the reason why adding additional PUI widgets to the source tree is a really bad idea and counter-constructive to accomplish our long-term goal of phasing out PUI completely.

This is why we now have a dedicated tutorial about porting our old custom PUI widgets to make use of the Canvas system: [[Canvas GUI]].
Core developers are requested not to add any new PUI widgets to the source tree, but instead help identify shortcomings of the existing Canvas/Nasal interface, so that it can be accordingly extended, in order to allow custom widgets to be specified outside C++ space - which can usually be quickly accomplished using the cppbind framework.

=== Canvas System ===

If you have been wanting to play around with the new [[Canvas]] system, make sure to check out the [[Howto:Adding a canvas to a GUI dialog]] tutorial, which demonstrates how to easily add a canvas rendering region to a conventional FlightGear dialog. Using the combination of Nasal scripting, standard FlightGear GUI dialogs and embedded canvas regions for 2D rendering, you can even create standalone "FlightGear applications" in the form of self-contained FlightGear XML dialogs that you can easily share with fellow FlightGear users.

This can for example be used to create a plotting application like FGPlot, which would look to FlightGear like a conventional dialog.
[[File:Fgplot-canvas.png|thumb|Stub]]

=== FGPlot ===
kuifje09 has started a little Linux project creating a plotter program for use with creating/tuning the autopilot in flightgear. kuifje09 provides a download which can be found at sourceforge. kuijfe09 already added some updates, removing bugs and adding new features (version 03b), see [[FGPlot]].

=== High Level Architecture ===
=== FlightGear an Android ===

=== Usability Improvements ===

=== Mailing list digest ===

(by far the easiest option to populate the newsletter with contents is copying/pasting stuff from the forum and the mailing list or the git logs)

=== Forum digest ===

=== Git digest ===

=== Getting involved as a programmer ===
Unfortunately, most of the active FG developers are currently very overstretched in terms of the areas that they have ownership of, which is affecting how much can actually be done. Fundamentally we need more core devs.

If you are interested in contributing as a core developer, please see [[Howto:Start core development]].

== Release ChangeLog ==
This section lists changes committed this month that will be available in the next release, these will be copied to the release changelog shortly before a release (for each month), so that we hopefully get a comprehensive list of new features.

== Interview with a contributor (NAME) ==
''In each edition we have an interview with a contributor. Suggestions for possible questions are available on [[interview questions]], you are invited to come up with new questions and interview ideas obviously! Anyone is free to write an interview (with him-/herself or others) for next month's newsletter! If you'd like to help interview a contributor or get interviewed, please do consider adding yourself to the [[list of interview volunteers]]! To keep this going and less awkward, we are currently trying to come up with the convention that former interviewees become next month's interviewers.''

* How long have you been involved in FlightGear?
* What are your major interests in FlightGear?
* What project are you working on right now?
* What do you plan on doing in the future?
* Are you happy with the way the FlightGear project is going?
* What do you enjoy most about developing for FlightGear?
* Are there any "hidden features" you have worked on in FlightGear that new users may miss?
* What advice can you give to new developers who want to get started on their first aircraft/new feature/Nasal script?

More questions are being collected here: [[Interview questions]].

Stay tuned for next month's interview, featuring FlightGear contributor XXXXXXXX

== International FlightGear Official Sites ==
Enjoy the awesome international FlightGear community and experiment the dream to fly with the best Free Flight Simulation Software ever built. With more than 15 years of experience FlightGear has a wide user community, from professionals to normal users from all around the world. For sure you'll find good friends in this amazing virtual community.

Please visit FlightGear websites in other languages:

*[http://www.flightgear.org.cn/portal.php 中文]
*[http://www.flightgear.org English]
*[http://vivefg.org/ Español]
*[http://fr.flightgear.org/website/ Français]
*[http://www.flightgear.jpn.org/ 日本語]
*[http://www.br.flightgear.org/ Português]
*[http://www.flightgear.ru/ Русский]

== Translators required ==
{|
|[[File:en.gif]]
|The FlightGear Wiki still needs help for translating it into various languages. If you are interested in making the FlightGear Wiki multi-language then start at [[Help:Translate]].
|-
|[[File:de.gif]]
|Das FlightGear Wiki benötigt immer noch Hilfe bei der Übersetzung in verschiedene Sprachen. Wenn Du Interesse daran hast, das FlightGear Wiki Mehrsprachig zu machen, dann fang doch mit [[:de:Help:Übersetzen|Help:Übersetzen]] an.
|-
|[[File:nl.gif]]
|De FlightGear Wiki kan nog steed hulp gebruiken bij het vertalen van artikelen. Als je interesse hebt om de wiki meertalig te maken, raden we je aan om een kijkje te nemen bij [[:nl:Help:Vertalen|Help:Vertalen]].
|-
|[[File:es.gif]]
|La FlightGear wiki todavía necesita ayuda para traducirla a varios lenguajes. Si estás interesado en hacer la FlightGear wiki multilingüe, entonces comienza en [[:es:Help:Traducir|Help:Traducir]].
|}

== Nasal for newbies ==

== New software tools and projects ==
=== FlightGearMap update ===
[[File:FlightGearMap Cessna 172 panel.png|400px]]
[[File:Deployment flightgearmap 3devices.jpg|x250px|A tablet instrument panel, mobile phone comm panel and another mobile phone showing the map.]]

[[FlightGearMap]], an Android application bringing live FlightGear data to your phone, has received an extensive update. Several new instruments were added, including an altitude radar, HSI and RMI. Besides that some basic switches like the magnetos and starter have been implemented. And finally two all new panels come with this release: a [[Cessna 337G Skymaster|Cessna 337 Skymaster]] panel and a communications panel where you can adjust your radio settings.

The app is avialable from [https://play.google.com/store/apps/details?id=com.juanvvc.flightgear Google Play].

== FlightGear addons and mods ==

== In the hangar ==

=== New aircraft ===

=== Updated aircraft ===

=== Liveries ===

== Scenery corner ==

=== Airports ===
[[File:CCSDPM1.png|400px|Overview of a Caribbean city from the radar station]]
[[File:CCSDPM2.png|x195px|Flying over another Caribbean town]]

DutchPilotMitchell has been working on making the scenery around the Caribbean more interesting. It is fictional, none of the placed models is actually there in real life. The reason why he made this was just about making a nice looking and fun area to fly (or drive!!).

You can make up your own 'missions'. For example, the people who work at the radar station are injured and need a medevac with a helicopter to bring them to the hospital quickly. Or there is a party in a small town, but they have nothing to drink. Fly to the scotch distillery and bring them drinks. As you can see there are countless things you can do on these islands. Especially after more islands get updated. The only limit is just your imagination. It is really nice flying around with detailled scenery beneath you. There are lots of places to explore. Here are a few features: there is are a few naval ships around, roads with cars on them, railways with trains and train stations, lots of small villages to explore, a WWII airport with F6F Hellcats and B17 bombers, harbours and industrial areas, radar stations and more!

It is worth downloading and flying around the place, especially with friends! Imagine doing a helicopter mission with other pilots or a sightseeing tour. On the forums you'll find more pictures of all this and also you'll find a regularly updated download link.

*[http://www.flightgear.org/forums/viewtopic.php?f=5&t=20007&p=184072#p184072 Forum topic]

=== Pittsburgh Development ===

Pittsburgh, Pennsylvania is one of the most iconic places in American history. Rick Ace has started modeling parts of city, and Pittsburgh International Airport. The Frick Building has almost been completed too. You can watch his progress in the [http://www.flightgear.org/forums/viewtopic.php?f=5&t=19994 flightgear forums].

== Aircraft of the month ==
== Airport of the month ==
== Screenshot of the month ==

== Suggested flights ==
== Aircraft reviews ==

== Wiki updates ==
===New articles===
<DynamicArticleList>
type=new
count=10
</DynamicArticleList>
===New aircraft articles===
<DynamicArticleList>
type=new
count=10
categoryRoot=Aircraft
</DynamicArticleList>
===Most popular newsletters===
<DynamicArticleList>
type=hot
count=5
categoryRoot=FlightGear Newsletter
</DynamicArticleList>
== Community news ==
=== FlightGear on YouTube ===

=== New tutorials and screencasts ===
=== Forum news ===
=== Multiplayer ===
=== Virtual airlines ===
FlightGear Virtual Aviation Organization - www.flightgearvao.org - We are an organization that has multiplayer events, ATC service and training for both pilots and ATC alike! We are currently seeking staff members and pilots, so join today!

=== FlightGear events ===

=== Web tools for ATC sessions in Europe ===
Some new web tools help planning ATC events are in development. They was initiated by lenny64 who [http://www.flightgear.org/forums/viewtopic.php?f=10&t=19810 announced on the official forum on Apr 27, 2013] that he had the first version of a web site, [http://lenny64.free.fr/ lenny64.free.fr], that made it possible to see and plan ATC sessions at some of the airports in Europe. Since then it have become possible too file flights to some of them.

He later [http://www.flightgear.org/forums/viewtopic.php?p=183688#p183688 announced] that similar functionality was added by evilslut to his tracker and mpserver, [http://mpserver12.flightgear.org/tracker/ mpserver12].

These services makes it possible:
* To see planned and current ATC sessions at various airports
* To plan ATC sessions for those airports
* To file flightplans to at least some of those airports
* For ATCs to see what flightplans are filed to and from his airport

The airports currently supported by those services are (airports with asterisk are only supported by lenny64):
* [[Frankfurt am Main Airport]] (EDDF)
* [[Leipzig/Halle Airport]] (EDDP)
* [[Flughafen Stuttgart]] (EDDS) *
* [[London Gatwick Airport]] (EGGK)
* Luxembourg Findel Airport (ELLX)
* Marseille Provence Airport (LFML)
* Paris Orly Airport (LFPO) *

== Useful links ==
== And finally ... ==
=== Contributing ===
One of the regular thoughts expressed on the FlightGear forums is "I'd like to contribute but I don't know how to program, and I don't have the time". Unfortunately, there is a common mis-conception that contributing requires programming and lots of free time. In fact, there are a huge range of ways to contribute to the project without needing to write code or spending days working on something.

For ideas on starting to contribute to FlightGear, you may want to check out: [[Volunteer]].

To learn more about how the project works, please see [http://flightgear.org/forums/viewtopic.php?f=42&t=15267#p149971 this short essay] written by Thorsten, for a more detailed article see [[How the FlightGear project works]].

=== Call for volunteers ===
* The [[Flightgear On Android]] team is looking for testers
* The [[Target4Today]] team is looking for volunteers to help improving FlightGear's combat support
* The [[FGFSPM]] (FlightGear Package Manager) is looking for a new maintainer.

=== Did you know ===

[[Category:FlightGear Newsletter]]
[[Category:Changes after 2.10]]

ATC tutorial

2010-06-06T20:48:02Z

Rickace: - Removed the part that says " (but most boring)", because that is an opinion which does not reflect everyones' views. It should not be in a wiki.

{{ATC-navbar}}
{{Main article|Air Traffic Control}}

[[Air Traffic Control]] is an agreed procedure and process which keeps the [[aircraft]] separated to ensure that they don't crash into each other or are affected by turbulence when passing through the same air space. The separation of planes taking off or landing at airports is three minutes. This allows the air to settle again. Pilots have used an analogy of calling the atmosphere soup as air and liquid has similar properties.

In order to be able to effectively and reliably communicate, ATC and pilots agree on a set of keywords and jargon. This may vary between regions and the like. English is the agreed language for internaltional flights. 

==Lesson 1==
{| class="prettytable"
! align="center" bgcolor="#EFEFEF" | Position Suffix
! align="center" bgcolor="#EFEFEF" | Name
! align="center" bgcolor="#EFEFEF" | Description
|-
| xxxx_GND
|Ground Controller
|Controls the movement of aircraft on the ground at an airport, however only the taxiways and bays... not the active runways. Whenever a plane needs to cross an active runway, it has to call the tower.
|-
! bgcolor="#EFEFEF" align="left" |xxxx_TWR
! bgcolor="#EFEFEF" align="left" |Tower Controller
! bgcolor="#EFEFEF" align="left" |'Owns' the runways and the airspace up to 10 NM (nautical miles) from the airport. Clears planes for takeoff and landing.
|-
|xxxx_APP
|Approach Controller
|Controls the airspace up to 30NM away from the airport, up to 18,000 ft (usually). Handles all aircraft leaving or arriving at an airport, until they are established on the ILS (then gives the plane to TWR) or are leaving their airspace to continue flight (then hands off to CTR)
|-
! bgcolor="#EFEFEF" align="left" |xxxx_DEP
! bgcolor="#EFEFEF" align="left" |Departure Controller
! bgcolor="#EFEFEF" align="left" |An position rarely used except at busy airports in the real world which relieves the work-load of the approach controller by handling all the departures, and getting them away from arrivals as quickly as possible, leaving the approach controller free to handle arrivals (the hard bit).
|-
|xxxx_CTR
|(ARTCC) Center Controller
|Centers own all airspace not controlled by APP or TWR. They control the plane while en route, and get it from X to Y safely, until it can be descended and given to the approach controller.
|-
! bgcolor="#EFEFEF" align="left" |xxxx_FSS
! bgcolor="#EFEFEF" align="left" |Flight Service Station
! bgcolor="#EFEFEF" align="left" |Flight Service Stations cover large areas (e.g.: France) and provide support to pilots and controllers. They can advise pilots of weather and frequencies for other controllers. They do not provide Air Traffic Control.
|-
|xxxx_DEL
|Clearance Delivery
|Clearance Delivery is rarely used in FlightSims. In the real world, a controller would give a clearance (which explains where the plane is allowed to fly) to all planes, but the ease of giving a clearance in the virtual world, means the Tower can normally give the clearance.
|}

The 'xxxx' in the table replace a code used to identify the area that controller is using. These are known as [[ICAO]] codes, and can be found on the [http://www.airport-technology.com/icao-codes/ ICAO web-site]. For example, Heathrow is 'EGLL' so a Heathrow Tower Controller would log-in as EGLL_TWR.

Centers and flight service stations also have ICAO identifiers, but they are not for one airport, but for a larger area. For example, LFFF_CTR is France Center, and LFFF_FSS is the France Flight Service Station.

You may also see the callsigns xxxx_SUP and xxxx_OBS. These are used only in the virtual world and represent, respectively, a supervisor and an observer (someone who isn't controlling).

So now you can choose your position, but beware: if you are the approach controller at an airport which doesn't have a ground / tower controller, planes will expect you to offer them all those facilities, but if you are a London Center controller, you are not expected to offer center facilities to airplanes in an adjacent sector, but could be expected to offer very basic facilities of GND / TWR / APP to airports in your sector...

==Lesson 2==
Now, we'll have a look at each of the positions in details:

===_GND (Ground)===
Ground is possibly the easiest position available to controllers. The basic responsibility is to get planes to and from the runway and terminal buildings as quickly as possible (to save fuel and time) and to avoid planes colliding with each other. For this, you'll need a GROUND SECTOR FILE. These are very detailed maps of a particular airport (can be downloaded from the Sector System on IVAO) which hold all the taxiways as geographic data (press F5 to view).

Depending on the airport, the taxiways may have letters, or descriptions (e.g.: Inner Taxiway) or each section of the airport may have a number (called blocks). At Heathrow, the last two are used, so a statement like 'taxi to block 76 via the outer taxi-way' would be valid.

===_TWR (Tower)===
Tower has responsibility for all planes coming into or out of the airport, and the planes wishing to enter or cross the active runways. For Tower you can use any sector file with the airport shown, and center on your airport and zoom in to give your short (10NM) range. The first responsibility is to choose which runways to use (there's always at least 2 - one runway being used either direction) according to the weather (more later). You will also be expected to give IFR clearances, but this is very simple.

The biggest responsibility the tower has is to ensure that planes can take-off and land as quickly as possible, without any two colliding. Your approach controller should make sure that all planes arriving are well spaced and already heading directly for the runway. When a plane you've given permission to take-off to has left the ground, they are given straight to APP (Approach). Normally, there will not be a ground controller, so you may have to also give basic ground instructions (just ask a plane to get to the runway - not giving them directions - but warn them of any other traffic).

===_APP (Approach)===
Approach is the most complicated position. Approach controllers deal with all traffic arriving and leaving (unless there is a departures controller - unusual). The main aim, as always, is to keep the aircraft arriving and leaving separated. For departing traffic, the aim is to get them going in the right direction and give them to center as soon as possible; for arriving traffic, the aim is to get them onto the approach (the correct height and heading) so that they can follow an electronic system (the ILS) which gives them exact guidance onto the runway, and then you can hand them off to the tower, who will clear them to land and try and get planes taking off in between the landings.

The difficulty is, of course, dealing with the high volumes of traffic around an airport. In Lesson 3, SIDs and STARs are introduced which are standard ways of leaving from or arriving at an airport which ensure that planes maintain separation.

===_DEP (Departures)===
An unusual position in the virtual world, the departure controller controls all planes leaving an airport; normally _APP will handle these but sometimes traffic means that there is just too much for a single controller to do. It is the aim of the departures controller to get the departing aircraft away from the airport as soon as possible without interfering with approach's planes. Later, you will see that departures are kept below a certain altitude until they're a distance away so that any arrivals can fly over them without any mid-air collisions.

In this position you absolutely must co-ordinate very closely with the approach controller.

===_CTR (ARTCC - Center)===
Center handles all airplanes in a specific area which are en route and not getting ready to land or having just departed. They navigate the plane from place to place as quickly as possible whilst ensuring that planes stay separated from each other. A plane may deal with many centers as it passes over many countries in a flight.

Notice how I've mentioned separation in every description? SEPARATION is the first key to controlling. It does not matter how far out its way a plane has to go if you keep everybody on board alive. A pilot may well want to have landed five minutes earlier, but it's your job as the controller to keep them separated. Of course, having said that, the second key to controlling is expedite flow - that is keep traffic moving quickly and get it where it wants to go by the most direct route.

==Lesson 3==
Let's look at a plane taxiing to the runway and taking off now. So, to do this, we'll consider two controllers:
''ground control (_GND) and the tower (_TWR).''

First, we have to know which runway is being used so that ground can get the plane to the right place. The rule is 'planes always like to be heading into the wind for takeoff or landing'. The winds are given in the METAR like 'xxxyy'. The direction of the wind is given first in 3 digits, and the speed after that in 2 digits; so 11007 indicates winds of 7kts with a direction of 110 (magnetic heading). Winds under 5 kts can be considered 'calm' and can be ignored. Thus, the basic idea is to match the heading of the wind, and the runway heading (add a '0' to the runway number - 17L is 170) as closely as possible. Runways are numbered by knocking the '0' off the heading, and appending 'L' for left or 'R' for right if there are parallel runways.

At Heathrow, there are runways 9L and 9R, and the same runways (used in opposite directions) 27R and 27L. If the wind is 110º @ 15 kts then runways 9L and 9R are most suitable, as 90 and 110 are only 20 degrees away, but 270 and 110 are 160º away! At Heathrow, where there are parallel runways, one runway can be used for landing and the other for taking off - so a plane can be leaving on 9L while another is almost landing on 9R. Where there is only one runway, the same runway can be used to landing and taking off. It is important to notice that if an aircraft is taking off on runway 7, and another lands shortly after on runway 7, they are travelling in the same direction, so they are not approaching each other, and a collision is impossible.

Knowing about your ATIS which can be read by all planes to avoid you repeating information, you would want to put the active runways in your ATIS so that other controllers know which runways you have chosen, and so planes have an idea of what they will be expected to do. Always keep your ATIS short (as it is hard for the pilots to read a long ATIS), and delete any blank lines at the end. The other component of your ATIS should be the current weather, so a good ATIS for a tower or ground controller would be:

''London Heathrow Ground/Tower Information <alpha/bravo/charlie/delta/echo...>. Active runways are 9R for departures, and 9L for arrivals. Weather is'' '''(copy from METAR)''' ''110@15 FEW030 OVC090 Q1015 NOSIG. On initial contact report you have <alpha/bravo/charlie/delta/echo...>'' ; the only detail to note here is the use of alpha/bravo, etc. Each time you update your ATIS change the identifier up by one, so start with alpha, then use bravo, then charlie. This is used so that when a plane calls you and says 'information alpha' you know if he has current information or an old version.

Now that the active runway has been established and the ATIS set-up, you can go about controlling. First, though, you need to know some basic guidelines about contact. Usually, expect a plane to call you first. They should give their current location, callsign (used to identify each plane) and which ATIS they have, so:

'''B-ELIO: Ground, this is B-ELIO at the terminal, Information Alpha. Request clearance to Paris Orly.'''

B-ELIO, a plane, has called you telling you where he is, what information he has, and what he wants. To reply, you need to tell him whether the information is current ('Alpha is current') or new information ('New active runway is 23') and reply to his request.

First, we earlier mentioned IFR clearance. This allows the controller to know where the plane is going, and to plan ahead for the aircraft. If you remember looking at a Flight Strip in lesson 1, you will recall it allows a controller to see the destination of the aircraft, the route the aircraft will follow and the requested altitude. The aim of the clearance is just to confirm these details with the pilot, especially in the real-world where they may be altered due to traffic levels, to make sure there aren't any mistakes and everyone knows what's going to happen. The clearance is as follows:

'''<Callsign> is cleared to <destination> as filed''' (give any changes to the flight plan here). '''After takeoff c/m''' (climb and maintain) '''<altitude> on runway heading / and turn <left/right> to <heading>, expect <requested flight level> after 10 minutes. Squawk <transponder code>.'''

Here's an example clearance:

'''You: B-ELIO is cleared to Paris Orly as filed. After takeoff c/m 6,000 and turn left to heading 180 (south) expect FL310 after 10 minutes. Squawk 5201.'''

The clearance can be given whilst on the ground, and is given by Clearance Delivery (_DEL) if one is online, else the GROUND (_GND), or TOWER (_TWR) controller. The pilot must read-back the whole clearance, to which you confirm by saying 'readback correct'. The Squawk code is a number used to identify the plane. It can be seen on the flight plan (will default to 1200) and means - in the real world - a controller can tell the dots apart as each one has a number. Just assign an available number in the 5000 or 6000 range (eg: 6001, 6002, 6003, etc.).

'''B-ELIO: B-ELIO cleared to Orly as filed. c/m 6000 left 180 - expect FL310 after 10, and squawk 5201.''' 
'''You: B-ELIO, readback correct, call when ready to push-back and start-up.''' 
'''B-ELIO: B-ELIO requests start-up and push-back.'''

Here a push-back and start-up means he wants a vehicle to pull the plane away from the buildings so he can start his engines... this is a real-world call, and is not used in the virtual world, so just approve it. He might skip this entirely and just ask if he can taxi, otherwise say:

'''You: Cleared to push-back and start engines. Call when ready to taxi'''

B-ELIO will then call you when he's ready to taxi. Note you don't have to type B-ELIO, just click on his icon on the screen and ProController automatically inserts it for you. You can often just respond with 'roger' or 'rgr' which means you've heard what the other person has said, or 'wilco' which means you have heard and will obey. When he calls to taxi:

'''B-ELIO: rgr (to the push-back and start-up clearance). Ready to taxi to the active runway.''' 
'''You: B-ELIO, Taxi to runway 9 (or whatever Tower has chosen) and hold short, altimeter 1009.''' 
'''B-ELIO: to runway 9 and h/s, alt 1009, B-ELIO (h/s is short for hold short)'''

Hold short asks the plane to get close to the point given (here, the runway) without actually getting on to the point. Each runway has a line painted on the ground (the holding line) at which a plane waiting to take-off will wait until he is cleared onto the runway (tower's duty). If you put the plane on the runway, tower might be landing a plane and this plane might well land on top of it! The altimeter is given now so that you are sure that the plane has the correct altimeter setting, and is just good practice. Even with it in your ATIS, and their take-off checks, it never hurts to be safe. Your aim as ground is just to get a queue ready for takeoff so that tower has aircraft ready to takeoff when there's a gap in arrivals.

If the pilot needs to cross a runway, he'll stop before the runway and ask for clearance. You just direct him to ask the tower for this information. Imagine for a second that there's another plane taxiing to the runway as well... tell the plane to give way:

'''You: B-ELIO, Taxi to runway 9 and hold short. Give way to the American Airlines 747 taxiing from left to right.'''

Now the pilot will have to give way to the 747 moving in front of him from his left to his right. If B-ELIO was also an American Airlines, you can use the word 'Company' to mean 'of the same company' so 'Give way to company 747...' would be legal. As a ground controller, with a detailed map, you might like to give full details of the way you want him to go, but normally the controller can just give a simple statement like the ones above:

'''You: B-ELIO, taxi via Inner Taxiway to block 53, then left onto taxi-way B to runway 9, and hold short.'''

Now the plane is ready to get onto the runway and takeoff, you hand him off to TWR, using the method you learnt in Lesson 1 by right-clicking on the plane, selecting 'aircraft >' and then 'request handoff' and select the appropriate controller. This will ask the controller for a hand-off and, when they accept, the circles around the plane will change colour, you can now go through the same menu and choose hand-off which will give B-ELIO the following message. In the real world, you'd actually say it, and in IVAO, you can just type it without using the automated system:

'''You: B-ELIO, contact the tower frequency 119.7 (you'd have to look up the frequency in who is on-line)'''

So now, it's Tower's turn to get this plane off into the sky...

If you were awaiting a plane to land, you could just leave the plane queuing, but if you are ready to have him on the runway tell him to get into position on the runway. Remember, it is your job to get aircraft onto and off the runways as quickly as possible, so that planes can land and take-off quickly:

'''You: B-ELIO, taxi into position and hold.''' 
'''B-ELIO: Position and hold, B-ELIO.'''

One thing to note, Europeans may use the terminology 'line up and wait' in stead of 'position and hold' - it means exactly the same. You may also use a conditional clearance, to make your job easier:

'''You: B-ELIO, taxi into position and hold [after the arriving B747 / following the departing B757]'''

The plane may give a call back when he's ready like 'ready to go' or 'on the numbers' or 'in position'. If not, just wait until his icon stops moving and give him his takeoff clearance:

'''You: B-ELIO, winds calm/110@15, runway 9, cleared to takeoff''' 
'''B-ELIO: Cleared to takeoff.'''

The plane will commence his take-off roll, and - as soon as he is airborne - you want to get rid of him and get onto your next plane. You initiate the hand-off to approach, and handoff as soon as (s)he accepts. So now, onto approaches dealings...

==Lesson 4==
''(In this section the approach controller is presumed to be handling departures, as there are very, very rarely departure controllers. If there were a departure controller, (s)he would deal with a departing plane, and the approach controller would deal with any planes arriving)''

So approach now has a plane that wants to get on with its flight. The first thing to notice was the clearance:
''climb and maintain 6,000...''

It wasn't explained last page, but the reason for this low height is to ensure that planes arriving at the airport - also at low heights - that are arriving from the takeoff end of the airfield are kept above the departing planes. If arriving planes are only cleared down to 8,000 ft. then - even if they have to fly over the airport and turn around - they cannot conflict with departing planes. For this reason, departing planes are usually cleared to 6,000 and arriving planes to 8,000 until they are on the 'safe' (non-departure) side of the runway.

Let's look at how the hand-off occurs this time:
'''EGLL_TWR: B-ELIO, contact EGLL_APP on 119.72, good-day.''' 
'''B-ELIO (to you): Heathrow Approach, good-day, this is B-ELIO out of 1,700 for 6,000 on runway heading'''

This time, because the plane is in the air, you want to acknowledge you can see him on the radar:
'''You: B-ELIO, Radar Contact, continue to 6,000... (and right to 120)'''

The aim now is to get the plane heading in the right direction (that is, towards the first VOR or NDB - remember how they're shown on the display - listed in the Flight Strip, or just in the general direction of the country he's heading to. When the planes far enough away from the airport, or there's no other traffic, climb him up to 12,000 - 18,000ft and hand him off to center. Now, a few words about giving the plane vectors (headings), remember:

* Don't expect the plane to respond instantly... think ahead. By the time he's got your message and started to turn he might be 1 NM further on that you expected.
* If he's heading directly to a 'fix' (any VOR, NDB or Intersection) give them a 'direct <place>' order like 'B-ELIO, turn left direct BIG' - don't bother trying to figure out headings when you've been given an easy way.
* Consider your heading -- are you sure you mean 90 and not 270? If the aircraft is heading to the left of the screen, he's flying a heading of 270 and not 90!! This may seem obvious, but is one of the biggest problems for new controllers.

Now the plane's in the sky, a big, bold few words about separation:
'''Keep your planes at least 3NM from each other, or at least 1,000 ft vertically between them. If you think the planes will eventually come too close, don't wait -- turn or descend one immediately! In order to make collisions between planes traveling in opposite directions less likely, use this rule:'''

{| class="prettytable"
! align="center" bgcolor="#EFEFEF" |
! align="center" bgcolor="#EFEFEF" |
|-
|Plane flying headings 0-179
|Fly at ODD FLIGHT LEVELS
|-
|Plane flying headings 180 - 359
|Fly at EVEN FLIGHT LEVELS
|}

What are Flight Levels? Flight Levels are used to shorten heights -- you should recognize them from the plane's blip -- you simply remove the two last digits from the height, for example 32,000ft --> FL320. Also, when you talk about Flight Levels, the pilot uses a standard altimeter setting (instead of the local altimeter setting found after the Q in the METAR weather report in the bottom right of your screen); while at low altitudes the plane will use the local barometric pressure. This means that all planes cruising will think 32,000 ft is at the same place, and not vary slightly depending on the local pressure.

Your aim is to get the planes in the right direction at a height ready for hand-off to an ARTCC (_CTR) and away from the airport. Once you've done it pass your plane onto the centre controller. It is a good idea to use the .chat <callsign of controller> function to ensure that you and your center agree on what places and heights you'll hand off at.

Now the planes with Centre. The same hand-off procedure as above applies... wait for the first contact. When you've got it, identify the plane, and report 'radar contact'. If a plane is in your airspace and won't contact you try asking on your frequency, then try a quick switch to 121.50 to send a 'Contact EGTT_CTR on 132.600' to get the plane's attention. Using 121.50 (the Guard Frequency) is used when you can't contact a plane -- all planes within a few hundred miles will hear your broadcast, irrespective of who it was intended for! Remember to switch back to your frequency -- you don't want everyone to hear your broadcasts for the rest of eternity (or perhaps you do; I certainly don't).

Centers job is pretty easy until its busy. Read the planes intended route and just get the plane to fly it. If there are other planes, make sure they don't collide. Since opposite traveling planes will have a 1,000 ft separation (using the table above) you shouldn't need to worry that much. Other than that, listen to the pilot's requests and help him where you can. When you get to your ARTCC boundary hand-off to the next centre, or - if there isn't one - give the order:

'''You: B-ELIO, no control available in France, resume own navigation to Belgium, radar service terminated'''

This statement removes all your requirements to control the plane, as it now knows that your not watching on radar, and you're not going to help him navigate. When you are navigating as centre - if the flight plan doesn't include a route - find the start and end points, and plan a quick route (either direct - give one heading - or by 'hopping' from VOR to VOR).

These terms are used often while controlling to confirm or deny requests and answer any questions:

{| class="prettytable"
! align="center" bgcolor="#EFEFEF" |
! align="center" bgcolor="#EFEFEF" |
|-
|Affirmative (sometimes affirm or aff)
|Yes or correct
|-
|Negative (sometimes neg)
|No or incorrect
|-
|Confirm...
|Is it correct that...
|-
|Unable...
|Sorry, I cannot accept your request for...
|-
|Roger (almost always rgr)
|I've heard and understood your last transmission
|-
|Wilco
|I will comply with your orders (implies Roger)
|-
|Standby (sometimes stby)
|Please wait, I will call you back when I am free.
|}

'''Some examples of these:'''
* '''You: Confirm current altitude is FL310. '''
**'''B-ELIO: Negative, FL290'''
* '''B-ELIO: Request descent to FL290 '''
**'''You: Unable FL290 (there is already traffic at FL290?)'''

When the plane is nearing its final destination, make sure it has descended to between 18,000 and 22,000 ft. This means that the approach controller can take the plane and descend it quickly -- it's no good trying to descend a plane 35,000 ft in 20 NM and still get it to land. Notice that the plane should remain above 18,000 ft (in your airspace) until you've handed off. Approach might decide not to take the plane and have you make it fly circles in the sky for 20 minutes until he has some room; otherwise arrivals and departures might crash while they're being handed over! So:

'''You: B-ELIO, d/m (descend and maintain) 18,000 on QNH 1221, right to 270 and expect hand-off to approach in five minutes.''' 
'''B-ELIO: down to 18,000 on 1221, will expect approach in five, B-ELIO.'''

What is the QNH? This is an altimeter setting. As the plane will shortly be moving back to local pressure, and not the flight level standard pressure, the pilot must know the local pressure. This ensures that his diagrams which give him the height of the airfield above sea level are correct -- if everyone used a standard altimeter setting at low altitudes the airport's height would seem to fluctuate over a period of hours by a few hundred feet! And finally:

'''You: B-ELIO, contact EGLL_APP on 192.72'''

I'm not sure how we ended up at Heathrow, but that's another story!

==Lesson 5==
Our plane, B-ELIO, is now about 40NM east-south-east of Heathrow ready to start the approach to runway 9L - as tower has chosen runway 9R for departures, with the winds of 87@22 - the plane is at 18,000 ft and is heading at 270 (towards the left of our screen...).

Did you remember that the landing direction would be towards the right of the screen? I hope so... Anyway, planes need to be at 2,500 ft about 8NM away from the airport heading in the correct direction to intercept the magical [[ILS]] device that will guide them perfectly onto the runway. We know we need to keep the plane at 8,000 ft until its past OCK, and then get it down to 2,500 and onto the grey dotted line leading to the left runway (9L) for the ILS and tower to take the passengers safely to the ground. Formulate a plan: accept the hand-off, descend the plane to 8,000 and send it directly towards OCK VOR, at OCK descend it to 2,500 and fly it past OCK on 270, then turn it to 360 (north, easier to read than '0') up the grey dotted line pointing north, then turn it to 45 so that is cuts the grey-dotted line at 90 to runway 9L... when the plane is on a course taking it through extended center-line (an imaginary line representing a line extending from the runway) it is said to be intercepting the localizer. The plane can then be told to get itself onto this extended center-line as the ILS will warn the plane when it needs to turn to establish itself on the line.

Since the airplane is on the wrong side of the airport, we fly three sides of a rectangle, the first is known as the down-wind (since you land heading up-wind), then the next 'leg' is known as the base, and the red-line shows the final. If the plane was coming from the west, he could just fly a 'straight-in' approach, also known as an extended final - as the plane only flies a very long final.

The orange line shows the 'intercepting the localizer' as the plane will continue to fly this heading until the ILS tells it to turn right onto the center-line of the runway. As soon as the plane reports it's established on the localizer (it has direction signals), it can be cleared for the approach and told to descend with the glideslope which gives the plane height signals. The glideslope and localizer give precision approach information and are known - together - as the ILS (Instrument Landing System). Then get the plane to the tower, because - remember - you may well be dealing with planes taking off which you need to get out of your air-space, and other planes trying to get established on the ILS, as the tower wants a steady stream of well-separated planes on the ILS. You hopefully now know what you're supposed to be doing, but how do we do it. We'll look at each stage in turn.

'''B-ELIO: B-ELIO with you at 18,000 for Heathrow. Information Alpha. (Your ATIS - might contain weather, voice IP?)''' 
'''You: B-ELIO, Radar Contact, alpha is current. d/m 8,000 and direct OCK please.''' 
'''B-ELIO: rgr, down to 8,000 to OCK.'''

Great... B-ELIO will now get to OCK and be at 8,000. Just before he gets to OCK, you need to issue the next instructions so that he can be ready for them:

'''You: B-ELIO, d/m 2,500 continue present heading and expect ILS approach to runway 9L at Heathrow.''' 
'''B-ELIO: rgr, 2,500 on my heading for 9L, B-ELIO.'''

OK so far? Now let's head him towards the airport. This is the base leg:

'''You: B-ELIO, turn right heading 360 (for base) the for base is for information and is usually left out.''' 
'''B-ELIO: t/r (turn right) 360, B-ELIO'''

This is where judgment and cunning use of the feature for monitoring heading and distance come into play. It is also your duty to give the plane the frequency for the ILS (in the form xxx.xx) which can be found at www.ivao.aero/db/ss (or from database, sector system) using the search facility. The plane just hit the extended center-line at least 8NM away from the airport, so make sure you issue the turn to 45 at the correct time, otherwise B-ELIO will miss the ILS. Right place, so...

'''You: Turn right heading 45 to intercept the localizer on 119.21 to 9L and report established.''' 
'''B-ELIO: right to 45 for LLZ to 9L, will report established'''

B-ELIO will now get himself onto the localizer and call:

'''B-ELIO: established'''

This is your cue to clear him for the approach and allow him to descend (otherwise he'll fly perfectly over the runway at 2,500ft). This is done with the following command:

'''You: B-ELIO, rgr (I heard the 'established') cleared the ILS approach to 9L, descend with the g/s. 
B-ELIO: Cleared ILS approach.''' 
'''You: B-ELIO, contact the tower on 118.52 (if there is a tower, else you'll have to do the job... and look up the tower frequency in who's on-line)''' 
'''B-ELIO: Over to the tower, thanks for your help.'''

That's your job done! As the approach controller you have the most work, so don't be afraid to give planes holds. A hold is a request for a plane to circle around a given fix (e.g.: a VOR) at a given height until you can do something with them. In fact, if you have lots of planes all circling a VOR, it's known as a 'stack' because the plane's are stacked there. So, we could get three planes holding at the OCK VOR (while we waited for traffic to decrease) at 6,000 ft, 8,000 ft and 10,000 ft and add new planes to the top and take planes ready for the approach from the bottom. To give a hold, the basic command is:

''Hold at <vor name> VOR at <current altitude/10,000 etc. / FL120 etc.>, expect further clearance in <time> minutes.''

Which requests the pilot flies around the <vor name> VOR at the assigned altitude until you give him a new clearance. The expect further clearance (e.g.: expect further clearance in 10 minutes) just gives the pilot some idea of the delay and does not give the pilot the right to start flying away after that time is over! The full clearance for holding is as follows, but usually you can just use the one above unless you specifically need to avoid a plane coming to a certain side of the VOR:

'''Hold <north/east/south/west> of the <vor name> VOR on the <approach heading> radial, expect further clearance in <time> minutes.'''

The approach heading is the heading at which you want the plane to approach the VOR. So, hold north of the OCK VOR on the 270 radial would ask the pilot to fly to OCK on a hdg of 270 and then to hold so he's always north of the fix. A hold is a racing track shaped rectangle.

The key to remember as the approach controller is to, wherever the planes coming from, remember its height is just as important as its direction when it comes to landing - 2,500 ft (above ground level) for the ILS.

Disaster! You've got a propeller aircraft doing an approach and you've started a 747 on the same approach behind it. There's nothing to hold it at, and there getting very close -- what do you do? You could take the plane away and start the approach again, but using an orbit -- a circle to the left or right and then on the original heading -- will increase your time, just give:

'''You: B-ELIO, one orbit to the left please for spacing.''' 
'''B-ELIO: wilco'''

Also, sometimes as approach you will want to slow a plane down to ensure that it isn't conflicting with a plane already on approach in front... if they are too close, the second plane will end up missing his approach because the plane in front will still be on the runway.

'''You: B-ELIO, slow to 210kts''' 
'''You: B-ELIO, slow to minimum feasible speed please''' 
'''You: B-ELIO, maintain minimum 190kts ''etc.'''''

Anyway, back to our imaginary flight in which B-ELIO is flying the approach and is back with the tower...

==Lesson 6==
Tower now has B-ELIO who is now cleared for the ILS approach, so can descend to the decision height. The decision minimum height is the height above the airport to which the plane can descend before being cleared to land. The plane cannot pass the decision height until he has visual contact (that is, he can see) the runway he wants to land on. If he cannot see the runway he will execute a missed approach and go around for another approach.

The pilot will report to the tower:

'''B-ELIO: B-ELIO with you to land 9L.''' 
'''You: B-ELIO, Rgr. (you do not need to give radar contact, as the pilot no longer needs a radar service. He is using ILS)'''

You can then give the landing clearance, or - more likely - you can delay the clearance until he is 8NM from the airport and so are more certain that he will be able to land. The 8NM point of the approach is marked by a special device that causes a tone and light in the plane's cockpit. This device is known as the outer marker (O/M or OM). You can ask the pilot to tell you at this point for his clearance:

'''You: B-ELIO, report the O/M for landing clearance''' 
'''B-ELIO: rgr 
'''B-ELIO: at O/M'''

'''You: B-ELIO, winds 109@17, runway 9L, cleared to land.''' 
'''B-ELIO: 9L, cleared to land, B-ELIO.'''

Your aim as the tower is to clear the plane to land to avoid it having to miss its approach, and get other planes taking off between the landing planes, whilst maintaining separation between the planes. You must remember to account for the fact that a plane trying to land may miss its approach, and have to fly past the airport -- so make sure you turn slower planes away from the airport quickly in case a jet needs to continue past the runway.

After B-ELIO has landed, while he's still on the runway, you still control him. You want him off your runway as soon as possible, so you can land the next plane (otherwise, if he's still anywhere on the runway, you'd have to give a landing plane a missed approach), so:

'''You: B-ELIO take first taxi-way to <left/right> then contact ground on 121.65 (look up frequency in who's on-line)''' 
'''B-ELIO: Thanks for your help, switching to ground.'''

And your job is done... let's look at a worse scenario. You landed a plane before B-ELIO and for some reason it hasn't been able to get off the runway yet. You must not let B-ELIO land whilst any other plane is on the runway, so you order B-ELIO to miss his approach:

'''You: B-ELIO initiate missed approach immediately, c/m 6000 on runway heading, and contact approach on 192.72 (again, use who's on-line) 
B-ELIO: Missed approach, and will contact approach.'''

Approach will then climb the plane back to 6,000 ft (as it is almost a departure now) and complete the down-wind and base legs again (possibly on the other side of the airfield, depending on traffic). The plane can then be vectored back onto approach by the approach controller, and then given back to tower to try again. Of course a plane can initiate their own missed approach.

'''B-ELIO:''' No visual on runway, going around (same as missed approach), B-ELIO. 
You: Rgr, c/m 6000 left to 60 (perhaps there's traffic straight ahead?) and contact approach on 192.72.'''

Once, B-ELIO is back with the ground controller, having taxied just off the runway, he will be given instructions to taxi to the terminal building. If there is no ground, the tower controller can just give a 'taxi to parking' order without specialized instructions.

That concludes the average flight in ProController, but the next (and last) page of this lesson contains some information that you may want to know, for example: the words used to represent single letter (e.g.: alpha for A in ATIS, and lima for L as in 'taxi-way lima' as opposed to 'taxi-way L').

[[Category:Air Traffic Control]]

User:Ac001/Airport Tutorial

2010-06-06T20:43:43Z

Rickace: - Added that Heathrow will expand. - Added that 27LR will be used soon.

{{Ac001-tutorial-navbar}}
=Airport Tutorial=
* The map below shows the two parallel [[runway]]s '''09L/27R''' and '''09R/27L''' at [[EGLL]] London Heathrow, a busy international airport. [[EGLL]] is the [[ICAO]] code for the airport.
** The runways are not actually parallel, but are aligned 89.67/269.67 and 89.89/269.69, a 0.02 degree difference.
** The north runway is 3,901m (12,799ft) long and the southern runway is 3,660m (12,008ft) in length.
** The yellow squares are the location of the [[DME]] transmitters, around halfway down the runway and used for ILS landings from both ends.
* The '''LON''' [[VOR]]/[[DME]] transmitter is located around 1km north of the airport, in a field and well away from interference by high rise buildings, large metal objects, large glass panels and "radio reflective" objects.
* The orange denotes the "noise abatment" area that are to be avoided.
* The wind is blowing from the SW (blue arrows).
* There would be three ATC controllers for arrival, departure and ground control, coordinating the event sequence and utilising both runways often to max capacity.
* The current configuration is:
** '''27R''' preferred for landing - the northen runway with white arrival path lines
** '''27L''' preferred for takeoff - the southern runway with green departure path lines

[[File:Ac001 egll airport map.jpeg]]
===Departures===
* '''27L''' is the designated and preferred runway for take off (green trails) and [[SID]]s
* '''27R''' is avoided as Cranford is a small village and an [http://en.wikipedia.org/wiki/Cranford_Agreement unwritten rule (Cranford Agreement)]. (However, on 15 January 2009, the Government announced that it was ending the Cranford Agreement as part of the controversial [http://en.wikipedia.org/wiki/Expansion_of_London_Heathrow_Airport expansion of London Heathrow Airport.])
* 27L is preference for heavy aircraft, lighter aircraft would take off earlier on 27R and climb higher over Cranford and less noise.
* The purple line is a position roughly 1-2nm from LON VOR. An aircraft is expected climb straight and above 500ft before commencing a turn at this point.
* A red H denotes taxi/runway holding points, waiting to position on '''27L''' ready for take-off.
* A purple H denotes taxi/runway holding points, waiting to position on '''27R''' ready for take-off and are further away from the runway so as not to interfere with the [[ILS]] signal for landing aircraft.

===Arrivals===
* '''27R''' is designated and preferred runway for landing and [[STARS]]
* There is a noise abatement area to the north (orange) and a public picnic park.
* The yellow circles at left end of runways represent the ILS transmitters at the end of the runway
* The yellow lines extending to the right of the runways are the approx extend of ILS "beam".
* The red '''T''' is the runway threshold and the aircraft needs to touch down at or after this point.
* Aircraft waiting to take-off on 27R need to hold hold further away (purple H) so as not to interfere the ILS beam.
* The purple lines show the "missed approach" point, around 2nm from the runway threshold.
** The trail in red shows an aircraft that has executed a missed approach to 27R. It reached decision point and executed a Go Around by flying down the runway centre line (to the left slightly) climbing to 3000ft and turning right around 1 LON dme.