193
edits
User:F-WTSS/Brouillon Fr/Tutoriel CTA: Difference between revisions
Jump to navigation
Jump to search
User:F-WTSS/Brouillon Fr/Tutoriel CTA (view source)
Revision as of 16:43, 13 February 2016
, 13 February 2016Traduc § "Phraséologie", début et remise en page plus cohérente.
(Retouches.) |
(Traduc § "Phraséologie", début et remise en page plus cohérente.) |
||
| Line 98: | Line 98: | ||
|} | |} | ||
== Phraséologie | == Phraséologie, exemple de vol IFR == | ||
La phraséologie se présente au travers d'un exemple de vol IFR depuis LEBL (aéroport de Barcelone, en Espagne) à EDDF (Frankfort sur le Main, en Allemagne). Pour simplifier, on suppose que tous les postes de contrôleurs (autorisations, sol, tour, départ, centre et approche) sont occupés. On suppose que l'immatriculation de l'appareil est ''BAW1542'' (épelé ''Speedbird un cinq quatre deux''). | |||
La phraséologie est présentée dans l'ordre des étapes successives d'un vol dont le lecteur est le pilote. | |||
=== Planification du vol === | |||
Lien vers l'article principal (en anglais) : [[Flight planning]]<!-- à remplacer par [[[FR/Plan de vol|Plan de vol]] après traduc.--> | Lien vers l'article principal (en anglais) : [[Flight planning]]<!-- à remplacer par [[[FR/Plan de vol|Plan de vol]] après traduc.--> | ||
| Line 108: | Line 110: | ||
Follow the instructions on the [[Flight planning]] article to file a flightplan from LEBL to EDDF with a cruising altitude of FL250. | Follow the instructions on the [[Flight planning]] article to file a flightplan from LEBL to EDDF with a cruising altitude of FL250. | ||
=== Obtenir l'autorisation de départ === | |||
We start on the airport apron at terminal T1, stand 221. | We start on the airport apron at terminal T1, stand 221. | ||
| Line 145: | Line 147: | ||
We also set the transponder code and switch the transponder to Ground mode (if the aircraft we're using supports this functionality). | We also set the transponder code and switch the transponder to Ground mode (if the aircraft we're using supports this functionality). | ||
=== Remorquage et démarrage === | |||
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. | 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. | ||
| Line 162: | Line 164: | ||
After that, we start our engines and complete our checklists as quickly as possible. | After that, we start our engines and complete our checklists as quickly as possible. | ||
=== Roulage jusqu'à la piste de décollage === | |||
We ask for clearance to taxi to the departure runway. | We ask for clearance to taxi to the departure runway. | ||
* '''BAW1542:''' Speedbird one five four two is ready to taxi. | * '''BAW1542:''' Speedbird one five four two is ready to taxi. | ||
| Line 194: | Line 196: | ||
* '''BAW1542:''' Contact El Prat Tower on one one eight decimal three two zero, Speedbird one five four two, bye! | * '''BAW1542:''' Contact El Prat Tower on one one eight decimal three two zero, Speedbird one five four two, bye! | ||
=== Alignement et décollage === | |||
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: | 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; | # the wind direction and speed; | ||
| Line 223: | Line 225: | ||
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'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> | ||
=== | === Approche de l'aéroport de destination === | ||
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: | 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.'' | * '''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.'' | ||
| Line 251: | Line 253: | ||
* '''BAW1542:''' Contact Frankfurt Tower on one one niner decimal niner zero, Speedbird one five four two. | * '''BAW1542:''' Contact Frankfurt Tower on one one niner decimal niner zero, Speedbird one five four two. | ||
=== Atterrissage === | |||
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: | 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; | # the wind direction and speed; | ||
| Line 272: | Line 274: | ||
* '''BAW1542:''' Contact Frankfurt Ground on one two one decimal eight zero, Speedbird one five four two. | * '''BAW1542:''' Contact Frankfurt Ground on one two one decimal eight zero, Speedbird one five four two. | ||
=== Roulage jusqu'au bloc et arrêt === | |||
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: | 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. | * '''BAW1542:''' Frankfurt Ground, Speedbird one five four two on Mike one five, runway zero seven right vacated. | ||
| Line 301: | Line 303: | ||
We taxi to the stand and shut down, also switching the transponder off – there's no need to ask a clearance for that. Our flight is now finished. | We taxi to the stand and shut down, also switching the transponder off – there's no need to ask a clearance for that. Our flight is now finished. | ||
=== Tutoriel en video === | |||
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. | 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. | ||
| Line 307: | Line 309: | ||
{{#ev:youtube|E3yfeWjlyic|400}} | {{#ev:youtube|E3yfeWjlyic|400}} | ||
== Exemple de vol VFR == | |||
[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]. | [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]. | ||