User Tools

Site Tools


airfieldmanual:f._moray_cta_radio_procedures

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
airfieldmanual:f._moray_cta_radio_procedures [2022/05/21 08:22]
sallyw [F.1.3 They will reply with]
airfieldmanual:f._moray_cta_radio_procedures [2022/06/03 15:08] (current)
173.208.130.202 ↷ Links adapted because of a move operation
Line 1: Line 1:
-====== F. Moray CTA Radio Procedures ======+====== -"F" MORAY CTA Radio Procedures ======
  
-===== F.1 Introduction =====+===== 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:+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.
  
-==== F.1.1 Think First! ==== +Engage brain before opening mouth. Use the mnemonic **<color #FF0000>CAPACER</color>** as the guide for the “message”. The example message exchange is shown below:
-Engaging brain before opening your mouth will make it easier for all!+
  
 +|  **<color #FF0000>C/A</color>**   | **Callsign / Aircraft**     | Glider SC       | Gliders don’t need to use the G-XXXX aircraft registration call sign, the comp number or trigraph is ok.  \\ \\ If in a two-seat glider say “Scottish Control 2 seat Glider T3”. After the initial call you can omit “2 seat” from the callsign. |
 +|  **<color #FF0000>P</color>**    | **Position** | 15 nautical miles North West of ERSON  | Erson is an ATC reporting point. Better to use what they know, e.g., FOYLE, ERSON, GUSSI or INBAS reporting points  |
 +|  **<color #FF0000>A</color>**    | **Altitude**     | Currently Flight Level 140 |Reminds them you are a glider. \\ \\ ATC usually prefers FL’s above 6000’, otherwise altitude. | 
 +|  **<color #FF0000>C</color>**    | **Condition**    | VMC | Can be left out but it makes ATC aware of your actual conditions |
 +|  **<color #FF0000>E/R</color>**  | **Estimates / Requests** | For Information Glider SC intends to cross Moray CTA West to East Not above FL160 close to ERSON. No service required | |
  
-==== F.1.2 Initial contact with ATC ====+===== - Example =====
  
-Initial contact with **Scottish Control** on, for example, 127.275+Initial contact with **Scottish Control** on, (for example)radio frequency 127.275
  
-//Sant: //**“Scottish Control, Glider SC”** //(Sierra Charlie)//  (Refer [[https://en.wikipedia.org/wiki/NATO_phonetic_alphabet|phonetic alphabet]])+<html> 
 +<p class="pmkquote scquote"> 
 +“Scottish Control, Glider SC” (Sierra Charlie) 
 +</p> 
 +</html>
  
-(Noteif in a two-seat glider say **“Scottish Control 2 seat Glider T3”.** After the initial call you can omit “2 seat” from the callsign)+ATC will reply with:
  
-Gliders don’t need to use the G-XXXX aircraft registration call signthe comp number or trigraph is ok.+<html> 
 +<p class="pmkquote atcquote"> 
 +“Glider SCScottish (Control), pass your message” 
 +</p> 
 +</html>
  
-==== F.1.3 ATC's reply ==== +Use the mnemonic (CAPACER)
- +
-They will reply with +
- +
-//ATC: //**“Glider SC, Scottish (Control), pass your message”** +
- +
-==== F.1.4 CAPACER Mnemonic ==== +
- +
- Use the mnemonic CAPACER as the guide for the “message” +
- +
-| **C/A** | **Callsign/Aircraft** | **Glider SC** | **Notes**   | +
-| **P** | **Position:** | is 15 nautical miles North West of ERSON… | better to use what they know, e.g. FOYLE, ERSON, GUSSI or INBAS reporting points | +
-| **A** | **Altitude:** | Currently Flight Level 140 … | (reminds them you are a glider) | +
-| **C** | **Conditions:** | VMC… | can be left out but it makes ATC aware of your actual conditions | +
-| **E/R** | **Estimates/Requests**: | For Information Glider SC intends to cross November 560 West to East Not above FL160 close to ERSON. No service required || +
- +
-e.g. (CAPACER)+
  
 +<html>
 +<p class="pmkquote scquote">
 “Glider SC is 15 nautical miles North West of ERSON, Currently FL140 VMC.   “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."+For information Glider SC intends to cross MORAY CTA West to East not above FL160 close to ERSON. No service required." 
 +</p> 
 +</html>
  
-==== F.1.5 ATC’s likely response (in most cases) ====+ATC’s likely response (in most cases):
  
-//ATC://** “Glider SC, that’s approved. Call entering and leaving MORAY CTA not above FL160 and maintain VMC.**+<html> 
 +<p class="pmkquote atcquote"> 
 +“Glider SC, that’s approved. Call entering and leaving MORAY CTA not above FL160 and     maintain VMC.” 
 +</p> 
 +</html>
  
-Note: **READ BACK**Always read back a clearance exactly as it is given.  In this case (whilst not exactly an ATC clearance) the reply is:+Note: **READ BACK**Always read back a clearance exactly as it is given.  In this case (whilst not exactly an ATC clearance) the reply is:
  
-//Sant://** “Scottish, Will call entering and leaving MORAY CTA not above FL160 and maintain VMC, glider SC.”**+<html> 
 +<p class="pmkquote scquote"> 
 +“Scottish, Will call entering and leaving MORAY CTA not above FL160 and maintain VMC, Glider SC.
 +</p> 
 +</html>
  
-==== F.1.6 Once clear of the airspace ====+Once clear of the appropriate airspace and no longer needing to talk to ATC:
  
-Once clear of the appropriate airspace and no longer needing to talk to ATC +<html> 
-//Sant://** “Scottish, Glider SC is clear of MORAY CTA East of ERSON, returning to gliding frequencies”**+<p class="pmkquote scquote"> 
 +“Scottish, Glider SC is clear of MORAY CTA East of ERSON, returning to gliding frequencies
 +</p> 
 +</html>
  
-//ATC://** “Glider SC, roger, have a good flight.”** +<html> 
- +<p class="pmkquote atcquote"> 
-==== F.1.7 Don't gabble! ====+“Glider SC, roger, have a good flight.” 
 +</p> 
 +</html>
  
 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. 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.
  
-Here’s an attempt at a full example. SC is heading SW from Ballinluig to turn Lochgoilhead. At about Kenmore he changes from 130.105 to 127.275 and after a pause to avoid interrupting any ongoing conversation, calls:-+===== Example 2 =====
  
-//Sant: //**“Scottish ControlGlider SC”**+Here’s another full examplefor 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 conversationcalls:
  
-//ATC://** “Glider SC, pass your message**+<html> 
 +<p class="pmkquote scquote"> 
 +Scottish Control, Glider SC” 
 +</p> 
 +</html>
  
-//Sant://** “Scottish, for information, Glider SC is approximately 10 miles South of INBAS currently at Flight Level 120 and intending to track SW across MORAY CTA not above FL160. No service required.**+<html> 
 +<p class="pmkquote atcquote"> 
 +Glider SC, Scottish (Control)pass your message 
 +</p> 
 +</html>
  
-//ATC://** “Glider SC that’s approved. Report entering and leaving MORAY CTAnot above FL160 and maintain VMC**+<html> 
 +<p class="pmkquote scquote"> 
 +Scottish, for information, Glider SC is approximately 10 miles South of INBAS currently at Flight Level 120 and intending to track SW across MORAY CTA not above FL160. No service required." 
 +</p> 
 +</html>
  
-//Sant://** "Report entering and leaving N560, not above FL160 and maintain VMC, glider SC”**+<html> 
 +<p class="pmkquote atcquote"> 
 +“Glider SC that’s approved. Report entering and leaving MORAY CTA, not above FL160 and maintain VMC." 
 +</p> 
 +</html> 
 + 
 +<html> 
 +<p class="pmkquote scquote"> 
 + “Report entering and leaving MORAY CTA not above FL160 and maintain VMC, glider SC. 
 +</p> 
 +</html>
  
 A few minutes later... A few minutes later...
  
-//Sant://** “Scottish, Glider SC entering MORAY CTA, currently climbing through Flight Level 115.”**+<html> 
 +<p class="pmkquote scquote"> 
 + “Scottish, Glider SC entering MORAY CTA, currently climbing through Flight Level 115.” 
 +</p> 
 +</html>
  
-//ATC://** “Roger, Glider SC.”**+<html> 
 +<p class="pmkquote atcquote"> 
 +“Roger, Glider SC.” 
 +</p> 
 +</html>
  
-A few minutes later and maybe;+A few more minutes latermaybe:
  
-//ATC://** “Glider SC, Scottish”**+<html> 
 +<p class="pmkquote atcquote"> 
 +“Glider SC, Scottish” 
 +</p> 
 +</html>
  
-//Sant://** “Go ahead, Glider SC”**+<html> 
 +<p class="pmkquote scquote"> 
 +“Go ahead, Glider SC” 
 +</p> 
 +</html>
  
-//ATC://** “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)+<html> 
 +<p class="pmkquote atcquote"> 
 +“We have an air ambulance in your area tracking S at Flight Level 130, report your Flight Level.” 
 +</p> 
 +</html>
  
-//Sant://** “Scottish, SC is currently at Flight Level 90 – if it helps, I can stay below Flight Level 120 unless I call you.**+<html> 
 +<p class="pmkquote scquote"> 
 +“Scottish, SC is currently at Flight Level 90 – if it helps, I can stay below Flight Level 120 unless I call you” 
 +</p> 
 +</html>
  
-//ATC://** “Glider SC that is helpful, not above Flight Level 120 unless approved – traffic should be clear in about 10 minutes”**+<html> 
 +<p class="pmkquote atcquote"> 
 +“Glider SC that is helpful, not above Flight Level 120 unless approved – traffic should be clear in about 10 minutes” 
 +</p> 
 +</html>
  
-Five minutes later...+<html> 
 +<p class="pmkquote scquote"> 
 +“Scottish, Glider SC is now clear of MORAY CTA West of ERSON and intends to return to gliding frequencies” 
 +</p> 
 +</html>
  
-//Sant:// **Scottish, Glider SC is now clear of MORAY CTA West of ERSON and intends to return to gliding frequencies.”**+<html> 
 +<p class="pmkquote atcquote"> 
 +“Glider SC, roger, traffic now clear behind you, have a nice day.” 
 +</p> 
 +</html>
  
-//ATC://** Glider SC, roger, traffic now clear behind you, have a nice day.”**+<html> 
 +<p class="pmkquote scquote"> 
 +Scottish, roger, I will call again later on the return trip.” 
 +</p> 
 +</html>
  
-//Sant: //**“Scottishroger, I will call again later on the return trip.”**+Sonot exactly proper RT – but in our experience pretty typical.
  
-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.
- +
-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. +
- +
-==== F.1.8 Reporting Points ====+
  
 +===== - 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:
  
-FOYNE | 560834N | 0042256W | +**FOYLE** | 560834N | 0042256W | 
-| ERSON | 562748N | 0041824W | +**ERSON** | 562748N | 0041824W | 
-| INBAS | 564200N | 0041459W | +**INBAS** | 564200N | 0041459W | 
-| GUSSI | 571247N | 0040727W |+**GUSSI** | 571247N | 0040727W |
  
-So, there we are, good luck and enjoy your soaring.+===== - Notes =====
  
-**//Sant Cervantes//** 
  
-===== F.2 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. 
-  * Sometimes if they are busy, they may ask for a time for airspace penetration.  +  * 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 degreestwo zero nautical miles at Flight Level one four zero”. 
-  * 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.  +  * 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.
-  * Remember that distances, flight levels, bearings, and times are read as separate digits e.g. N560 is spoken as “November five six zeroFL120 is “Flight level one two 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.   * 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]] | [[:airfield_manual#contents|Contents]] | [[g._reporting_defects_in_club_gliders|G. Reporting Defects in Club Gliders]] +[[E. Letters of Agreement]] | [[airfieldmanual:start#contents|Contents]] | [[g._reporting_defects_in_club_gliders|G. Reporting Defects in Club Gliders]]
- +
airfieldmanual/f._moray_cta_radio_procedures.1653121337.txt.gz · Last modified: 2022/05/21 08:22 by sallyw