229
edits
Spoken ATC: Difference between revisions
Jump to navigation
Jump to search
no edit summary
No edit summary |
No edit summary |
||
| Line 1: | Line 1: | ||
'''Spoken ATC''' allows the pilot to listen to the directives of the ''Air Traffic Controller''. | '''Spoken ATC''' allows the pilot to listen to the directives of the ''Air Traffic Controller''. | ||
[[ Page under construction ]] | [[ ---- Page under construction ----]] | ||
= Preface = | |||
'''Typically''', you should tune the ATC-station frequency and make a request by pressing "'''<'''" key. You may hear something like:<br /> | '''Typically''', you should tune the ATC-station frequency and make a request by pressing "'''<'''" key. You may hear something like:<br /> | ||
<small> | <small> | ||
| Line 16: | Line 16: | ||
</small> | </small> | ||
That is only an example of standard '''VFR Phraseology''' that you can expect from '''Spoken ATC'''.<br /> | That is only an example of standard '''VFR Phraseology''' that you can expect from '''Spoken ATC'''.<br /> | ||
= How to install = | |||
#- Download the [https://drive.google.com/file/d/0BzzojFuPdeyMTGNDYmZDcEljQkU/view?usp=sharing spoken_atc.zip]. There you will find a "''spoken_atc''" directory with 6 files inside. | |||
#- Extract that directory (not only the files!) into the ''$FGFS_ROOT/Nasal'' directory. | |||
#- Edit the ''$FGFS_ROOT/keyboard.xml'' file and include the following lines in order to bind the "'''<'''" key: | |||
<key n="60"> | |||
<name>less-than</name> | |||
<desc>Spoken ATC</desc> | |||
<binding> | |||
<command>nasal</command> | |||
<script>spoken_atc.speak(15)</script> | |||
</binding> | |||
</key> | |||
And that's all !<br /> | |||
If you prefer, you can bind an unused joystick button too.<br /> | |||
= How to use it = | |||
Launch FlighGear (or re-start it) and tune Comm1 to an available ATC frequency (you can find them at ''Menu/Location/Airfield information''), | |||
and press the "'''>'''" key to transmit your request.<br /> | |||
You will hear the ATC's answer according the standard VFR phraseology, depending on your current position, weather and previous messages: | |||
* If you are on ground => | |||
** The code interprets it's a taxi request (if you are far from the runway or you've just landed), | |||
** or a take-off request (if you are on the correct Runway or at his holding point). | |||
* If you are flying => | |||
** The code interprets it's an approach request (if you tunned an APP station), | |||
** or a landing request (if you tunned a TWR station), | |||
** or a departure request (if you tunned a DEP station. and you are climbing after a take-off).<br /> | |||
Note that only TWR stations can deliver landing or take-off clearances, and only GND or TWR stations can deliver taxiing ones.<br /> | |||
Where there is not a specific GND or APP-DEP freq., TOWER can take their tasks.<br /> | |||
If they do exist, TWR will redirect to the specific frequency.<br /> | |||
Only at initial contact, the ATC message includes his station name & type, and the current QNH.<br /> | |||
APP stations will give a vector to the runway threshold in use (if you are far from there) or order to contact TWR (if you are inside the CTR).<br /> | |||
TWR stations will give instructions to join pattern or make direct final (depending on your position).<br /> | |||