airfieldmanual:f._moray_cta_radio_procedures
no way to compare when less than two revisions
Differences
This shows you the differences between two versions of the page.
— | airfieldmanual:f._moray_cta_radio_procedures [2025/02/21 09:09] (current) – created - external edit 127.0.0.1 | ||
---|---|---|---|
Line 1: | Line 1: | ||
+ | ====== -" | ||
+ | ===== - Introduction ===== | ||
+ | |||
+ | 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 # | ||
+ | |||
+ | | **<color # | ||
+ | | **<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: | ||
+ | |||
+ | < | ||
+ | <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 cross 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.” | ||
+ | </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: | ||
+ | |||
+ | | **FOYLE** | 560834N | 0042256W | | ||
+ | | **ERSON** | 562748N | 0041824W | | ||
+ | | **INBAS** | 564200N | 0041459W | | ||
+ | | **GUSSI** | 571247N | 0040727W | | ||
+ | |||
+ | ===== - Notes ===== | ||
+ | |||
+ | |||
+ | * Sometimes if they are busy, they may ask for a time for airspace penetration. | ||
+ | * What does “no service required” mean? Exactly what it says; ATC will not have to (though they will likely try – it’s ingrained) give you any service, e.g., basic service, traffic service, etc. and that way they will not bug you unless they have to. | ||
+ | * Remember that distances, flight levels, bearings, and times are read as separate digits e.g., “GUSSI radial 120° at 20nm, FL140 is spoken as “GUSSI radial one two zero degrees, two zero nautical miles at Flight Level one four zero”. | ||
+ | * When giving a distance and bearing it’s from a waypoint, not to the waypoint. It’s possibly easier to say for example, North West of GUSSI (for example). Also, it’s best to work in nautical miles. | ||
+ | * The reason for telling ATC the maximum level you expect to cross the airway is that ATC must sterilize a defined airspace box to protect other IFR or VFR traffic. Giving ATC a maximum FL makes it easier for them. | ||
+ | |||
+ | [[E. Letters of Agreement]] | [[airfieldmanual: |
airfieldmanual/f._moray_cta_radio_procedures.txt · Last modified: 2025/02/21 09:09 by 127.0.0.1