airfieldmanual:f._moray_cta_radio_procedures
Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
| airfieldmanual:f._moray_cta_radio_procedures [2026/03/10 16:28] – [1. Example 1] kateb | airfieldmanual:f._moray_cta_radio_procedures [2026/03/10 16:28] (current) – [1. Notes] kateb | ||
|---|---|---|---|
| Line 46: | Line 46: | ||
| - | ===== - Example 2 ===== | + | ===== F.3 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, | 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=" | + | |
| - | “Report entering and leaving MORAY CTA not above FL160 and maintain VMC, glider SC.” | + | |
| - | </p> | + | |
| - | </ | + | |
| - | A few minutes later... | + | A few minutes later… |
| - | < | + | < |
| - | <p class=" | + | |
| - | “Scottish, | + | |
| - | </p> | + | |
| - | </ | + | |
| - | < | + | < |
| - | <p class=" | + | |
| - | “Roger, Glider SC.” | + | |
| - | </p> | + | |
| - | </ | + | |
| A few more minutes later, maybe: | 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. | So, not exactly proper RT – but in our experience pretty typical. | ||
| Line 148: | Line 88: | ||
| 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. | 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 ===== | + | |
| + | ===== F.4 Reporting Points ===== | ||
| If you want to put the reporting points in your nav kit, going Northbound: | If you want to put the reporting points in your nav kit, going Northbound: | ||
| - | | **FOYLE** | 560834N | 0042256W | | + | |**FOYLE** |560834N|0042256W| |
| - | | **ERSON** | 562748N | 0041824W | | + | |**ERSON** |562748N|0041824W| |
| - | | **INBAS** | 564200N | 0041459W | | + | |**INBAS** |564200N|0041459W| |
| - | | **GUSSI** | 571247N | 0040727W | | + | |**GUSSI** |571247N|0040727W| |
| - | ===== - Notes ===== | ||
| + | ===== F.5 Notes ===== | ||
| * Sometimes if they are busy, they may ask for a time for airspace penetration. | * Sometimes if they are busy, they may ask for a time for airspace penetration. | ||
| Line 166: | Line 107: | ||
| * 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. | * 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.1773160082.txt.gz · Last modified: by kateb
