FlightGear wiki - User contributions [en]

User talk:Kai Burghardt

2022-12-01T16:39:05Z

Kai Burghardt: Redirected page to wikipedia:User talk: Kai Burghardt

#REDIRECT [[Wikipedia: User talk: Kai Burghardt]]

User:Kai Burghardt

2022-12-01T16:36:54Z

Kai Burghardt: update, use {{user}}

{{user
| name = Kays
| location = Milkyway
| age = {{#expr:{{CURRENTYEAR}} - 1992}} years
| job =
| interests =
| callsign = D‑9654
| favourite =
* Schempp‑Hirth Duo Discus
| website = [https://ttt.KaiBurghardt.de/ ttt.KaiBurghardt.de]
}}

Hi, I’m {{PAGENAME}}!

2007 to 2012 I used to be a sailplane student pilot at my home [http://LSV-Solling.de/ airfield of Uslar], located at the heart of Germany.
Although I did my first solo flight in 2010, I don’t have a {{abbr|GPL|glider pilot license}} (since 2012 {{abbr|SPL|sailplane pilot license}}) yet, but wish to eventually finish that.

Because lights at airfields use color coding (e. g. to distinguish between active runways), my protanopia (red-green color perception impairment) bars me from flying at night.
The {{abbr|FGFS|FlightGear flight simulator}} (or in fact any {{abbr|FS|flight simulator}}) allows me to do flights nevertheless.

{{#tag:h2|external links|style="clear: both;"}}
* {{Wikipedia|User: Kai Burghardt|Wikipedia user page}}

Talk:Blender and BTG

2012-12-12T23:36:46Z

Kai Burghardt: /* Download links */ no change

== Download links ==
The download links are pointing to nirvana. Can someone update nor upload 'em somewhere else? That'd be genial! --[[User:Kai Burghardt|Kays]] 08:56, 20 October 2012 (EDT)
: Hi Kai,
: I've contacted the author of the scripts. He will re-upload (an updated version of) the scripts next week. ;-) Thanks for notifying!
: [[User:Gijs|Gijs]] 05:21, 22 October 2012 (EDT)
:: Hm, unfortunately in a week is some weeks ago, and the links are still the same. --[[User:Kai Burghardt|Kays]] 18:36, 12 December 2012 (EST)

TerraGear

2012-10-21T01:24:47Z

Kai Burghardt: /* Dependencies */ libnewmat10-dev

<div style="padding-left:20px;">''Not to be confused with [[TerraSync]], a tool to download scenery on-the-fly.''</div>

[[File:TerraGear The Hague wireframe.png|thumb|270px|A wireframe view of detailed [[CORINE]] and [[OSM]] scenery, generated by TerraGear.]]
'''TerraGear''' is a collection of open-source tools and rendering libraries which can transform publically available GIS data in 3D representations (i.e. 3D models or 3D maps) of the earth for use in real time rendering projects. TerraGear can import 3D data sets such as DEM terrain grids, 2D polygon data sets such as coastlines, city outlines, lake outlines, and 2D raster data sets such as the 1 km NAOO land use/land cover data. It also has tools for generating realistic [[airport]]s, runways, and lighting based on available FAA data.

TerraGear is the primary tool used to generate the [[scenery]] for the [[FlightGear]] project.

== Introduction ==
For a variety of reasons you might want to build terrain yourself, rather than downloading it from the available scenery on FlightGear. For instance, if you use [[TaxiDraw]] to create or modify an airport layout, you might wish to see how that modified airport would look in the Scenery before deciding you're happy with the results. And normally, to see and use the airport in the scenery, it's necessary to submit the modifications to the FlighGear scenery staff and then wait untill the next update of the scenery of that area is available via [[TerraSync]] or in the [http://www.flightgear.org/download/scenery/ official FlightGear Scenery] build. If you can build terrain yourself, you can start using it right away.

Maybe the official scenery is too detailed for your slow machine, and you'd like to build terrain using a digital elevation model (DEM) with poorer resolution, to decrease the number of polygons and thus improve your framerates. Or maybe you've got a fantastically fast machine, and you want to build your own terrain using higher resolution vector data (vmap1, Tiger) to get better roads/rivers. For all these reasons learning how to use TerraGear is a good idea.

== Getting TerraGear ==
=== Pre-compiled builds ===
* [http://flightgear.simpits.org:8080/job/TerraGear-Win-Cmake/lastSuccessfulBuild/artifact/*zip*/archive.zip Latest Windows build], built by the [[FlightGear Build Server]].
* [ftp://ftp.ihg.uni-duisburg.de/FlightGear/Win32 Windows builds] (old)

=== Source ===
The source is hold in a [[git]] repository at Gitorious.
git clone git://git.gitorious.org/fg/terragear.git

== Compilation ==
=== Dependencies ===
* TerraGear
** [[SimGear]] - '''Not''' simgear-cs! (simgear-dev package)
*** SimGear can be compiled without OSG support thus eliminating many deps, like OSG. Use "-DSIMGEAR_HEADLESS=YES" for a minimal build.
** libnewmat - at least version newmat11 (which is beta at the time of writing) See [http://mapserver.flightgear.org/git/?p=terragear;a=blob;f=README.newmat;h=95570b6b279d3d00bd7664cd4f00d6c4802aed1b;hb=HEAD README.newmat] for info on how to obtain and install it. Nor use the package libnewmat10-dev.
** gpc - See [http://mapserver.flightgear.org/git/?p=terragear;a=blob;f=README.gpc;h=226e185b1ce1d1578006b48bb426e35848cce93b;hb=HEAD README.gpc] for info on how to obtain and install it.
** [http://pocoproject.org/ POCO] - For multicore support
** [http://www.gdal.org/ libgdal]
** [http://trac.osgeo.org/proj/ libproj]
** [http://ogdi.sourceforge.net/ libogdi]
** [http://epsilon-project.sourceforge.net/ libepsilon] - for ogr-decode
** libexpat
** libplib-dev
** Feel free to add more required libs here!

=== Building ===
Please, have a look at [http://mapserver.flightgear.org/git/?p=terragear;a=blob;f=README;h=7dae654283ca0b1447aeb3aa398287219f4b57df;hb=HEAD README] and/or [http://mapserver.flightgear.org/git/?p=terragear;a=blob;f=README.cygwin;h=d0436ec0371dd9fa255a8a560a388818432600d6;hb=HEAD README.cygwin] of the TerraGear sources.
./autogen.sh
./configure [options]
sed s/-O2// -i src/Lib/TriangleJRS/Makefile
make install
<tt>./configure</tt> options:
--prefix=/path/to/install-dir
I am missing reliable data here. Please, revise/complete the list if you have more info!
--with-gdal=/path/to/gdal-config
--with-gpc=/path/to/libgenpolyclip.a
--with-newmat=/path/to/libnewmat.a
--with-plib=/path/to/libplib*.a
--with-simgear=/path/to/libsg*.a
--with-osg=/path/to/OSGinstallation

=== Platform specific ===
* Debian: [[Building FlightGear - Debian#TerraGear]]
* Gentoo: <tt>emerge -av terragear</tt> See [[Building Flightgear - Gentoo]].
* Ubuntu: [[Building terragear-cs in Ubuntu 64]]

== GUI Tool ==
A [[TerraGear GUI]] is available for those that would like to use TerraGear without knowing/using the command line options.

== Related content ==
* [[Using Terragear]]
* [[TerraGear CORINE]]
* [[TerraGear Documentation]]

{{Terra}}
{{Building}}

[[Category:Scenery enhancement]]

[[es:TerraGear]]
[[fr:TerraGear]]

TerraGear

2012-10-21T01:22:11Z

Kai Burghardt: /* Dependencies */ simgear

<div style="padding-left:20px;">''Not to be confused with [[TerraSync]], a tool to download scenery on-the-fly.''</div>

[[File:TerraGear The Hague wireframe.png|thumb|270px|A wireframe view of detailed [[CORINE]] and [[OSM]] scenery, generated by TerraGear.]]
'''TerraGear''' is a collection of open-source tools and rendering libraries which can transform publically available GIS data in 3D representations (i.e. 3D models or 3D maps) of the earth for use in real time rendering projects. TerraGear can import 3D data sets such as DEM terrain grids, 2D polygon data sets such as coastlines, city outlines, lake outlines, and 2D raster data sets such as the 1 km NAOO land use/land cover data. It also has tools for generating realistic [[airport]]s, runways, and lighting based on available FAA data.

TerraGear is the primary tool used to generate the [[scenery]] for the [[FlightGear]] project.

== Introduction ==
For a variety of reasons you might want to build terrain yourself, rather than downloading it from the available scenery on FlightGear. For instance, if you use [[TaxiDraw]] to create or modify an airport layout, you might wish to see how that modified airport would look in the Scenery before deciding you're happy with the results. And normally, to see and use the airport in the scenery, it's necessary to submit the modifications to the FlighGear scenery staff and then wait untill the next update of the scenery of that area is available via [[TerraSync]] or in the [http://www.flightgear.org/download/scenery/ official FlightGear Scenery] build. If you can build terrain yourself, you can start using it right away.

Maybe the official scenery is too detailed for your slow machine, and you'd like to build terrain using a digital elevation model (DEM) with poorer resolution, to decrease the number of polygons and thus improve your framerates. Or maybe you've got a fantastically fast machine, and you want to build your own terrain using higher resolution vector data (vmap1, Tiger) to get better roads/rivers. For all these reasons learning how to use TerraGear is a good idea.

== Getting TerraGear ==
=== Pre-compiled builds ===
* [http://flightgear.simpits.org:8080/job/TerraGear-Win-Cmake/lastSuccessfulBuild/artifact/*zip*/archive.zip Latest Windows build], built by the [[FlightGear Build Server]].
* [ftp://ftp.ihg.uni-duisburg.de/FlightGear/Win32 Windows builds] (old)

=== Source ===
The source is hold in a [[git]] repository at Gitorious.
git clone git://git.gitorious.org/fg/terragear.git

== Compilation ==
=== Dependencies ===
* TerraGear
** [[SimGear]] - '''Not''' simgear-cs! (simgear-dev package)
*** SimGear can be compiled without OSG support thus eliminating many deps, like OSG. Use "-DSIMGEAR_HEADLESS=YES" for a minimal build.
** libnewmat - at least version newmat11 (which is beta at the time of writing) See [http://mapserver.flightgear.org/git/?p=terragear;a=blob;f=README.newmat;h=95570b6b279d3d00bd7664cd4f00d6c4802aed1b;hb=HEAD README.newmat] for info on how to obtain and install it.
** gpc - See [http://mapserver.flightgear.org/git/?p=terragear;a=blob;f=README.gpc;h=226e185b1ce1d1578006b48bb426e35848cce93b;hb=HEAD README.gpc] for info on how to obtain and install it.
** [http://pocoproject.org/ POCO] - For multicore support
** [http://www.gdal.org/ libgdal]
** [http://trac.osgeo.org/proj/ libproj]
** [http://ogdi.sourceforge.net/ libogdi]
** [http://epsilon-project.sourceforge.net/ libepsilon] - for ogr-decode
** libexpat
** libplib-dev
** Feel free to add more required libs here!

=== Building ===
Please, have a look at [http://mapserver.flightgear.org/git/?p=terragear;a=blob;f=README;h=7dae654283ca0b1447aeb3aa398287219f4b57df;hb=HEAD README] and/or [http://mapserver.flightgear.org/git/?p=terragear;a=blob;f=README.cygwin;h=d0436ec0371dd9fa255a8a560a388818432600d6;hb=HEAD README.cygwin] of the TerraGear sources.
./autogen.sh
./configure [options]
sed s/-O2// -i src/Lib/TriangleJRS/Makefile
make install
<tt>./configure</tt> options:
--prefix=/path/to/install-dir
I am missing reliable data here. Please, revise/complete the list if you have more info!
--with-gdal=/path/to/gdal-config
--with-gpc=/path/to/libgenpolyclip.a
--with-newmat=/path/to/libnewmat.a
--with-plib=/path/to/libplib*.a
--with-simgear=/path/to/libsg*.a
--with-osg=/path/to/OSGinstallation

=== Platform specific ===
* Debian: [[Building FlightGear - Debian#TerraGear]]
* Gentoo: <tt>emerge -av terragear</tt> See [[Building Flightgear - Gentoo]].
* Ubuntu: [[Building terragear-cs in Ubuntu 64]]

== GUI Tool ==
A [[TerraGear GUI]] is available for those that would like to use TerraGear without knowing/using the command line options.

== Related content ==
* [[Using Terragear]]
* [[TerraGear CORINE]]
* [[TerraGear Documentation]]

{{Terra}}
{{Building}}

[[Category:Scenery enhancement]]

[[es:TerraGear]]
[[fr:TerraGear]]

TerraGear

2012-10-21T01:09:32Z

Kai Burghardt: /* Dependencies */ plib

<div style="padding-left:20px;">''Not to be confused with [[TerraSync]], a tool to download scenery on-the-fly.''</div>

[[File:TerraGear The Hague wireframe.png|thumb|270px|A wireframe view of detailed [[CORINE]] and [[OSM]] scenery, generated by TerraGear.]]
'''TerraGear''' is a collection of open-source tools and rendering libraries which can transform publically available GIS data in 3D representations (i.e. 3D models or 3D maps) of the earth for use in real time rendering projects. TerraGear can import 3D data sets such as DEM terrain grids, 2D polygon data sets such as coastlines, city outlines, lake outlines, and 2D raster data sets such as the 1 km NAOO land use/land cover data. It also has tools for generating realistic [[airport]]s, runways, and lighting based on available FAA data.

TerraGear is the primary tool used to generate the [[scenery]] for the [[FlightGear]] project.

== Introduction ==
For a variety of reasons you might want to build terrain yourself, rather than downloading it from the available scenery on FlightGear. For instance, if you use [[TaxiDraw]] to create or modify an airport layout, you might wish to see how that modified airport would look in the Scenery before deciding you're happy with the results. And normally, to see and use the airport in the scenery, it's necessary to submit the modifications to the FlighGear scenery staff and then wait untill the next update of the scenery of that area is available via [[TerraSync]] or in the [http://www.flightgear.org/download/scenery/ official FlightGear Scenery] build. If you can build terrain yourself, you can start using it right away.

Maybe the official scenery is too detailed for your slow machine, and you'd like to build terrain using a digital elevation model (DEM) with poorer resolution, to decrease the number of polygons and thus improve your framerates. Or maybe you've got a fantastically fast machine, and you want to build your own terrain using higher resolution vector data (vmap1, Tiger) to get better roads/rivers. For all these reasons learning how to use TerraGear is a good idea.

== Getting TerraGear ==
=== Pre-compiled builds ===
* [http://flightgear.simpits.org:8080/job/TerraGear-Win-Cmake/lastSuccessfulBuild/artifact/*zip*/archive.zip Latest Windows build], built by the [[FlightGear Build Server]].
* [ftp://ftp.ihg.uni-duisburg.de/FlightGear/Win32 Windows builds] (old)

=== Source ===
The source is hold in a [[git]] repository at Gitorious.
git clone git://git.gitorious.org/fg/terragear.git

== Compilation ==
=== Dependencies ===
* TerraGear
** [[SimGear]] - '''Not''' simgear-cs!
*** SimGear can be compiled without OSG support thus eliminating many deps, like OSG. Use "-DSIMGEAR_HEADLESS=YES" for a minimal build.
** libnewmat - at least version newmat11 (which is beta at the time of writing) See [http://mapserver.flightgear.org/git/?p=terragear;a=blob;f=README.newmat;h=95570b6b279d3d00bd7664cd4f00d6c4802aed1b;hb=HEAD README.newmat] for info on how to obtain and install it.
** gpc - See [http://mapserver.flightgear.org/git/?p=terragear;a=blob;f=README.gpc;h=226e185b1ce1d1578006b48bb426e35848cce93b;hb=HEAD README.gpc] for info on how to obtain and install it.
** [http://pocoproject.org/ POCO] - For multicore support
** [http://www.gdal.org/ libgdal]
** [http://trac.osgeo.org/proj/ libproj]
** [http://ogdi.sourceforge.net/ libogdi]
** [http://epsilon-project.sourceforge.net/ libepsilon] - for ogr-decode
** libexpat
** libplib-dev
** Feel free to add more required libs here!

=== Building ===
Please, have a look at [http://mapserver.flightgear.org/git/?p=terragear;a=blob;f=README;h=7dae654283ca0b1447aeb3aa398287219f4b57df;hb=HEAD README] and/or [http://mapserver.flightgear.org/git/?p=terragear;a=blob;f=README.cygwin;h=d0436ec0371dd9fa255a8a560a388818432600d6;hb=HEAD README.cygwin] of the TerraGear sources.
./autogen.sh
./configure [options]
sed s/-O2// -i src/Lib/TriangleJRS/Makefile
make install
<tt>./configure</tt> options:
--prefix=/path/to/install-dir
I am missing reliable data here. Please, revise/complete the list if you have more info!
--with-gdal=/path/to/gdal-config
--with-gpc=/path/to/libgenpolyclip.a
--with-newmat=/path/to/libnewmat.a
--with-plib=/path/to/libplib*.a
--with-simgear=/path/to/libsg*.a
--with-osg=/path/to/OSGinstallation

=== Platform specific ===
* Debian: [[Building FlightGear - Debian#TerraGear]]
* Gentoo: <tt>emerge -av terragear</tt> See [[Building Flightgear - Gentoo]].
* Ubuntu: [[Building terragear-cs in Ubuntu 64]]

== GUI Tool ==
A [[TerraGear GUI]] is available for those that would like to use TerraGear without knowing/using the command line options.

== Related content ==
* [[Using Terragear]]
* [[TerraGear CORINE]]
* [[TerraGear Documentation]]

{{Terra}}
{{Building}}

[[Category:Scenery enhancement]]

[[es:TerraGear]]
[[fr:TerraGear]]

Talk:Blender and BTG

2012-10-20T12:56:29Z

Kai Burghardt: +

==download-links==
The download links are pointing to nirvana. Can someone update nor upload 'em somewhere else? That'd be genial! --[[User:Kai Burghardt|Kays]] 08:56, 20 October 2012 (EDT)

User talk:Kai Burghardt

2012-06-25T19:06:46Z

Kai Burghardt: babel

Babel: German-3, English-2

User:Kai Burghardt

2012-06-25T19:05:48Z

Kai Burghardt: airfield info page is even better

Hello,

I'm Kai Burghardt, a gliding-flight-learner at [http://www.segelflug.de/vereine/uslar/flugplatz.html airfield Uslar] (mid Germany).

User:Kai Burghardt

2012-06-25T19:04:17Z

Kai Burghardt: Created page with "Hello, I'm Kai Burghardt, a gliding-flight-learner at [http://lsv-solling.de airfield Uslar] (mid Germany)."

Hello,

I'm Kai Burghardt, a gliding-flight-learner at [http://lsv-solling.de airfield Uslar] (mid Germany).

ATC tutorial

2012-06-25T18:30:20Z

Kai Burghardt: typo

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

[[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 international 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 might need a GROUND SECTOR FILE. This is optional as a very detailed map 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, runway 9, line up and wait.''' 
'''B-ELIO: Runway 9, line up and wait, B-ELIO.'''

One thing to note, the phrase 'position and hold' is no longer used, since the FAA adopted the ICAO standard "line up and wait" (since September 30, 2010).

You may also use a conditional clearance, to make your job easier:

'''You: B-ELIO, runway 9, line up and wait [after the arriving B747 / following the departing B757]'''

The plane may give a call back when he's ready like 'ready for departure' or 'on the numbers'. 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 for takeoff''' 
'''B-ELIO: Cleared for 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 [[Instrument Landing System|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]]

ATC phraseology

2012-06-25T18:29:04Z

Kai Burghardt: +-

{{ATC-navbar}}
This page lists some common phraseologies used in the communication between pilots and [[Air traffic control|ATC]].

For a detailed tutorial in ATCing, please take a look at the [[ATC Tutorial]].

=== Affirmative ===
* Abbreviation: aff
Yes.

=== Call ===
Contact me. Usually ATC asks you to make contact after you've done something or you are ready to do something.

=== Cleared for takeoff runway two-eight-left ===
You are cleared for takeoff from runway 28L. Only this sentence (and really nothing else) gives you clearence for takeoff from the said runway.

If the word immediate is added (eg. Cleared for immediate takeoff runway 28L), you are only cleared for takeoff if you are able to do so within a very short time. Usually traffic is coming in on the same runway, so do not enter the runway if you are not ready for takeoff in this case.

=== Cleared to land runway two-eight-center ===
You are cleared to land at runway 28C. Only this sentence (and really nothing else) gives you clearence to land at the said runway. Always make a visual check to see if the runway is really clear!

=== Climb and maintain eight-thousand feet ===
* Abbreviation: c/m.
Climb to 8000 ft and hold that altitude until further instructions are given.

=== Descend and maintain eight-thousand feet ===
* Abbreviation: d/m.
Descend to 8000 ft and hold that altitude until further instructions are given.

=== Hold short ===
* Abbreviation: h/s.
You are cleared to taxi to a certain location, but you should wait at the designated point. This can be a runway entrance, or a taxiway crossing. As soon as you reached the designated point, you inform the ATC that you are "Holding short".

=== Initiate missed approach ===
For some reason ATC wants you to abort the landing; there might be traffic on the runway. Immediately abort your landing and follow the missed approach procedure appropriate to your aircraft. Usually the ATC will give some instructions like altitude and heading. As you have to redo your approach, you are requested to contact approach again.

=== Line up and wait ===
Enter the runway, position yourself in the center and await further clearance.

Note: The phrase "(taxi into) position and hold" is no longer used.

=== Negative ===
* Abbreviation: neg
No.

=== One orbit to the left ===
Make a circle to the left and then continue on the original heading. ATC may tell you to do so if a little more spacing between you and the aircraft in front of you is required.

=== Report established ===
Tell the ATC once you are established.

=== Roger ===
* Abbreviation: rgr
I received your information.

=== Say again ===
Repeat your last message.

=== Will Comply ===
* Abbreviation: wilco
__NOTOC__
__NOEDITSECTION__

[[Category:Air Traffic Control]]

Understanding FlightGear Scenery

2012-01-05T22:21:24Z

Kai Burghardt: refs broken

If you want to develop scenery for FlightGear, great! FlightGear needs as much help as possible with modeling the world. This article is designed for someone who is interested in creating FlightGear scenery for the first time and this is meant to explain how FlightGear manages scenery and what quirks or nuances you need to know in order to best contribute.

== How Scenery is Generated ==
There are three main types of data which make up FlightGear scenery - airports, objects and terrain.

All Airports and Terrain are generated using the [[TerraGear]] software. The vast majority of objects can be placed dynamically, using either the UFO aircraft model, or by finding the latitude and longitude of the object and placing it manually through text files.

All scenery which is included in the main FlightGear database should be derived from either license-free data or data which there is implicit permission to use. For instance, using USGS imagery, LANDSAT satellite imagery, or even Yahoo! Maps is okay for placing models or checking coordinates of airport runways. However, the FlightGear scenery project is copyright aware and typically does not accept objects or terrain created from copyrighted data, including, unfortunately, Google. (Yahoo! Maps has told OpenStreetMap deriving coordinates from their map data is not a copyright issue.) If you have a question about your source, do not hesitate to [http://flightgear.org/forums ask on the forum].

== How Scenery is Stored ==
FlightGear manages scenery through a folder hierarchy representing square degrees for both Objects and Terrain. The purpose of separating scenery tiles by degree is to allow easy internet distribution and to provide boundaries for the generation of terrain, so polygons do not just go on for miles.

This means you need to know where your scenery project is in longitude and latitude. For instance, San Francisco's airport can be found under the folder w123n37.

== The Basic Format ==
The /Scenery folder for FlightGear contains three subfolders - Airports, Objects and Terrain.

=== Airports ===
This folder contains various .xml files for the airports you have downloaded. You do not need to edit these!

If you are interested in contributing airport data, you will want to use [[TaxiDraw]]. Unfortunately TaxiDraw is not very robust at the moment, but it works. As of January 2010, FlightGear uses an older version of the X-Plane airport data. The kind people over at [http://scenemodels.flightgear.org the Scenery Model Database] accept updated airports in the X-Plane 8.10 format.

Because of the FlightGear feature which allows airports to undulate, or change elevation, all airports must be regenerated using [[TerraGear]] once [[TaxiDraw]] has been used.

=== Objects ===
Objects are possibly the easiest sceneries to create for FlightGear. All you need is to create an .ac model and place it using the ufo or manually using co-ordinates. You can also create an .xml file to create animations.

Objects are stored in a global database, the [http://scenemodels.flightgear.org/ FlightGear Scenery Model Database]. Once you have modeled your building, please make sure to send it into the database, as this is how your work gets distributed! Your work will be available to [[TerraSync]] users shortly after it is added.

Please note there is a difference between SHARED and STATIC objects. SHARED objects are objects which are included within the whole scenery, regardless of where you are. STATIC objects are specific objects, which appear a limited number of times (usually once) in the scenery. For instance, a house created to be auto-generated scenery would be a SHARED model, while the model of the tallest skyscraper in the country would be a STATIC model. SHARED models are typically to be avoided unless you know what you are doing, as they are loaded into memory when FlightGear starts up.

* [[Howto: Place 3D objects with the UFO]]
* [[Howto: Add shared models manually]]

=== Terrain ===

[[Category:Scenery]]

FlightGear wiki:Community portal

2007-12-17T16:36:44Z

Kai Burghardt: /* Latest news */ RC

==New at FlightGear==
There are many Tutorials for you.
*[[New to FlightGear]]
*[[Joystick]]
*[[Flying the Helicopter]]

==Latest news==
[[Current events]] - [[special:Recentchanges|Recent changes]]

FlightGear wiki:Community portal

2007-12-17T16:35:32Z

Kai Burghardt:

==New at FlightGear==
There are many Tutorials for you.
*[[New to FlightGear]]
*[[Joystick]]
*[[Flying the Helicopter]]

==Latest news==
[[Current events]] - [[special:Recentchanges]]

FlightGear wiki:Community portal

2007-12-17T16:09:01Z

Kai Burghardt:

==New at FlightGear==
There are many Tutorials for you.
[[Flying the Helicopter]]