User:F-WTSS/Brouillon Fr/Tutoriel CTA: Difference between revisions

Cet aticle, plutôt destiné aux pilotes, illustre ces procédures. Il devrait aider à apprécier les zones contrôlées et celles des aéroports sur les [[serveurs multijoueurs de FlighGear]].

The roles a controller can assume mirror the ones that a pilot can encounter in "real life" aviation:

{| class="wikitable"

* At large airports, multiple controllers may man the same positions.

Since there are not many ATCs in FlightGear, often a single controller fills more than one position. Generally speaking:

* a controller filling a particular position also fills the positions below him/her (the one listed before in the table above) if no one else is covering it; for example, if ''EGKK_TW'' (a Gatwick Tower Controller) is online, but there is no ''EGKK_GN'', the Tower controller acts also as Ground controller;

* as an exception to the rule above, Tower controllers often act also as Approach controllers for the respective airports.

If more than one controller is manning an area, the first controller should tell the pilot to contact the second controller when the airplane is about to enter the airspace of the latter. This is usually done with the phrase: "callsign, ''contact'' station ''on'' frequency".

{{Main article|Flight rules}}

A distinction you should know for flying in controlled areas is the one between IFR and VFR flights, as flight planning and some phraseology are different.

* IFR (Instrument Flight Rules) apply in all other cases.

{{Main article|Getting aeronautical charts}}

You should [[Getting aeronautical charts|get aeronautical charts]] for the airports you intend to fly from/to, specifically:

|}

We will teach the phraseology through an IFR sample flight from LEBL (Barcelona) to EDDF (Frankfurt am Main). For simplicity, we assume that all controller positions (delivery, ground, tower, approach/departure and center) are manned; also, we assume our callsign is ''BAW1542'' (to be read as ''Speedbird one five four two'').

{{Main article|Flight planning}}

It's a good practice to file a flight plan on [http://flightgear-atc.alwaysdata.net/ Lenny's website] so that the controllers will be able to know your departure/destination airports, cruising altitude and route without asking you about that every time.

Follow the instructions on the [[Flight planning]] article to file a flightplan from LEBL to EDDF with a cruising altitude of FL250.

We start on the airport apron at terminal T1, stand 221.

We also set the transponder code and switch the transponder to Ground mode (if the aircraft we're using supports this functionality).

Before pushing back (being pushed away from the stand with a tug) and starting up, we need to get appropriate clearances from the Ground controller. This ensures we won't block taxiways unnecessarily.

After that, we start our engines and complete our checklists as quickly as possible.

We ask for clearance to taxi to the departure runway.

* '''BAW1542:''' Speedbird one five four two is ready to taxi.

* '''BAW1542:''' Contact El Prat Tower on one one eight decimal three two zero, Speedbird one five four two, bye!

We contact Tower on text chat, FGCom or Mumble (depending on the tools the controller is using) to get our takeoff clearance. It will include, in that order:

# the wind direction and speed;

We're now free to follow our flightplan - it's a good practice to keep an eye on the multiplayer map to check for traffic and to announce altitude changes/turns on text chat if other pilots are nearby.<ref>In real world flying, we would be handed off to center controllers and we would report our position over special points, marked as black triangles in the charts. Since center controllers are not common in FlightGear, this is not usually done.</ref>

We start descending on our own so as to reach FL150 approximately 100 NM from the destination airport. When we're about 80 NM from EDDF we check the ATIS for the destination airport, just like we did at LEBL - in this case the frequency is 118.02. We tune in the COM1 radio to that frequency and listen:

* '''EDDF ATIS:''' ''This is Frankfurt information Echo. Landing runway zero seven right. Departure runway zero seven center. Transition level five zero. Wind zero two zero degrees, four knots. Visibility one zero km or more, few four thousand eight hundred feet. Temperature one niner<ref>"Niner" is used instead of "nine" to avoid confusion between the similarly sounding "nine" and "five".</ref>, dewpoint zero seven. QNH one zero one eight. No significant change. On initial contact advise controller you have information Echo.''  

* '''BAW1542:''' Contact Frankfurt Tower on one one niner decimal niner zero, Speedbird one five four two.

We switch to 119.90 MHz and/or join the Frankfurt Tower channel on Mumble, then contact the tower controller to get the landing clearance. It will include:

# the wind direction and speed;

* '''BAW1542:''' Contact Frankfurt Ground on one two one decimal eight zero, Speedbird one five four two.

We switch the transponder to ground mode and check the ground chart to get the name of the taxiway we are on; in our case, we have vacated the runway on taxiway M15. We then contact the ground controller:

* '''BAW1542:''' Frankfurt Ground, Speedbird one five four two on Mike one five, runway zero seven right vacated.

We taxi to the stand and shut down, also switching the transponder off &ndash; there's no need to ask a clearance for that. Our flight is now finished.

The departure and arrival presented in this tutorial have also been recorded. Some interactions were simplified, the result should however be more close to what you usually experience on the multiplayer network. Closed captions are available.

{{#ev:youtube|E3yfeWjlyic|400}}

[http://forum.flightgear.org/memberlist.php?mode=viewprofile&u=12953 de profundis] has written a VFR tutorial that takes you for a sample flight from KRNO (Reno Tahoe) to KBIH (Eastern Sierra Regional) and covers VFR flight planning, phraseology and tips in great detail. You can get his ''Cross Country Tutorial'' from the [http://forum.flightgear.org/viewtopic.php?f=72&t=19600 dedicated forum thread].

* This tutorial, for the sake of simplicity and brevity, assumed no other aircraft was present. On multiplayer servers you might be instructed to hold your position, give way to other aircraft or hold (make circles) over a point to remain separate from other aircraft; check the [[ATC phraseology]] page for the specific phraseology used in those situations.

* Follow the guidelines detailed in [[ATC best practices]] to make the experience enjoyable for everyone.