This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision | ||
testpage [2022/05/26 08:23] sallyw [F.1 Introduction] |
testpage [2022/07/05 16:24] sallyw old revision restored (2022/06/09 20:31) |
||
---|---|---|---|
Line 1: | Line 1: | ||
- | ====== | + | ====== |
- | ===== - Introduction ===== | + | Each link is preceded by the date it was last modified in yyyy-mm-dd format.\\ |
+ | <nspages -tree -r | ||
+ | -exclude | ||
+ | -exclude: | ||
+ | -subns | ||
+ | -pagesInNs | ||
+ | -h1 | ||
+ | -textNs="" | ||
+ | -displayModificationDates | ||
+ | -naturalOrder> | ||
- | Basically, when communicating with air traffic keep it short and sweet. Always remember that the other guy at the end of the line is human and not a god. We should however aspire to maintain good radio discipline as it helps our reputation as responsible pilots. How’s that achieved? Some helpful hints. | ||
- | Engage brain before opening mouth. Use the mnemonic **<color # | + | | {{top|score=true,num=100}} |
- | + | ||
- | | | + | |
- | | **<color # | + | |
- | | **<color # | + | |
- | | **<color # | + | |
- | | **<color # | + | |
- | + | ||
- | ===== - Example 1 ===== | + | |
- | + | ||
- | Initial contact with **Scottish Control** on, (for example), radio frequency 127.275 | + | |
< | < | ||
- | <p class=" | ||
- | “Scottish Control, Glider SC” (Sierra Charlie) | ||
- | </p> | ||
- | </ | ||
- | ATC will reply with: | + | <nspages -tree -r -exclude:testpage -exclude: |
+ | -exclude: | ||
+ | -subns -pagesInNs -h1 -textNs="" | ||
+ | | ||
- | < | ||
- | <p class=" | ||
- | “Glider SC, Scottish (Control), pass your message” | ||
- | </p> | ||
</ | </ | ||
- | Use the mnemonic (CAPACER) | ||
- | |||
- | < | ||
- | <p class=" | ||
- | “Glider SC is 15 nautical miles North West of ERSON, Currently FL140 VMC. | ||
- | For information Glider SC intends to MORAY CTA West to East not above FL160 close to ERSON. No service required." | ||
- | </p> | ||
- | </ | ||
- | |||
- | ATC’s likely response (in most cases): | ||
- | |||
- | < | ||
- | <p class=" | ||
- | “Glider SC, that’s approved. Call entering and leaving MORAY CTA not above FL160 and | ||
- | </p> | ||
- | </ | ||
- | |||
- | Note: **READ BACK**: Always read back a clearance exactly as it is given. | ||
- | |||
- | < | ||
- | <p class=" | ||
- | “Scottish, | ||
- | </p> | ||
- | </ | ||
- | |||
- | Once clear of the appropriate airspace and no longer needing to talk to ATC: | ||
- | |||
- | < | ||
- | <p class=" | ||
- | “Scottish, | ||
- | </p> | ||
- | </ | ||
- | |||
- | < | ||
- | <p class=" | ||
- | “Glider SC, roger, have a good flight.” | ||
- | </p> | ||
- | </ | ||
- | |||
- | When talking to ATC don’t gabble. Make clear and concise statements. The rigid language of CAP 413 is not always followed – it can be quite relaxed. To start with write down on a card CAPACER and run a few scenarios through your head. Lastly and most importantly the thing is to relax. It’s just another guy/gal on the end of the line and they know a lot less about flying and your needs as a glider than you do. | ||
- | |||
- | ===== - Example 2 ===== | ||
- | |||
- | Here’s another full example: for instance, glider SC is heading SW from Ballinluig to turn Lochgoilhead. At about Kenmore he/she changes from 130.105 to 127.275 and after a pause to avoid interrupting any ongoing conversation, | ||
- | |||
- | < | ||
- | <p class=" | ||
- | “Scottish Control, Glider SC” | ||
- | </p> | ||
- | </ | ||
- | |||
- | < | ||
- | <p class=" | ||
- | “Glider SC, Scottish (Control), pass your message” | ||
- | </p> | ||
- | </ | ||
- | |||
- | < | ||
- | <p class=" | ||
- | “Scottish, | ||
- | </p> | ||
- | </ | ||
- | |||
- | < | ||
- | <p class=" | ||
- | “Glider SC that’s approved. Report entering and leaving MORAY CTA, not above FL160 and maintain VMC." | ||
- | </p> | ||
- | </ | ||
- | |||
- | < | ||
- | <p class=" | ||
- | | ||
- | </p> | ||
- | </ | ||
- | |||
- | A few minutes later... | ||
- | |||
- | < | ||
- | <p class=" | ||
- | | ||
- | </p> | ||
- | </ | ||
- | |||
- | < | ||
- | <p class=" | ||
- | “Roger, Glider SC.” | ||
- | </p> | ||
- | </ | ||
- | |||
- | A few more minutes later, maybe: | ||
- | |||
- | < | ||
- | <p class=" | ||
- | “Glider SC, Scottish” | ||
- | </p> | ||
- | </ | ||
- | |||
- | < | ||
- | <p class=" | ||
- | “Go ahead, Glider SC” | ||
- | </p> | ||
- | </ | ||
- | |||
- | < | ||
- | <p class=" | ||
- | “We have an air ambulance in your area tracking S at Flight Level 130, report your Flight Level. (ATC usually prefers FL’s above 6000’, otherwise altitude)” | ||
- | </p> | ||
- | </ | ||
- | |||
- | < | ||
- | <p class=" | ||
- | “Scottish, | ||
- | </p> | ||
- | </ | ||
- | |||
- | < | ||
- | <p class=" | ||
- | “Glider SC that is helpful, not above Flight Level 120 unless approved – traffic should be clear in about 10 minutes” | ||
- | </p> | ||
- | </ | ||
- | |||
- | < | ||
- | <p class=" | ||
- | “Scottish, | ||
- | </p> | ||
- | </ | ||
- | |||
- | < | ||
- | <p class=" | ||
- | “Glider SC, roger, traffic now clear behind you, have a nice day.” | ||
- | </p> | ||
- | </ | ||
- | |||
- | < | ||
- | <p class=" | ||
- | “Scottish, | ||
- | </p> | ||
- | </ | ||
- | |||
- | So, not exactly proper RT – but in our experience pretty typical. | ||
- | |||
- | Lastly and again to repeat, as a way of giving your position in relation to a reporting point one can use Go To (or the non Oudie equivalent) which will give a bearing and distance to a reporting point. You must give the bearing **from** the reporting point i.e., add or subtract 180° to the GO TO bearing. | ||
- | |||
- | ===== - Reporting Points ===== | ||
- | |||
- | If you want to put the reporting points in your nav kit, going Northbound: | ||
- | |||
- | | FOYNE | 560834N | 0042256W | | ||
- | | ERSON | 562748N | 0041824W | | ||
- | | INBAS | 564200N | 0041459W | | ||
- | | GUSSI | 571247N | 0040727W | | ||