Portmoak Pilot's Information and Airfield Manual

This page is read only. You can view the source, but not change it. Ask your administrator if you think this is wrong.
====== -"F" MORAY CTA Radio Procedures ======

===== - 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 #FF0000>CAPACER</color>** as the guide for the “message”. The example message exchange is shown below:

|  **<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 | |

===== - Example 1 =====

Initial contact with **Scottish Control** on, (for example), radio frequency 127.275

<html>
<p class="pmkquote scquote">
“Scottish Control, Glider SC” (Sierra Charlie)
</p>
</html>

ATC will reply with:

<html>
<p class="pmkquote atcquote">
“Glider SC, Scottish (Control), pass your message”
</p>
</html>

Use the mnemonic (CAPACER)

<html>
<p class="pmkquote scquote">
“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>
</html>

ATC’s likely response (in most cases):

<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:

<html>
<p class="pmkquote scquote">
“Scottish, Will call entering and leaving MORAY CTA not above FL160 and maintain VMC, Glider SC."
</p>
</html>

Once clear of the appropriate airspace and no longer needing to talk to ATC:

<html>
<p class="pmkquote scquote">
“Scottish, Glider SC is clear of MORAY CTA East of ERSON, returning to gliding frequencies"
</p>
</html>

<html>
<p class="pmkquote atcquote">
“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.

===== - 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, calls:

<html>
<p class="pmkquote scquote">
“Scottish Control, Glider SC”
</p>
</html>

<html>
<p class="pmkquote atcquote">
“Glider SC, Scottish (Control), pass your message”
</p>
</html>

<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>

<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...

<html>
<p class="pmkquote scquote">
 “Scottish, Glider SC entering MORAY CTA, currently climbing through Flight Level 115.”
</p>
</html>

<html>
<p class="pmkquote atcquote">
“Roger, Glider SC.”
</p>
</html>

A few more minutes later, maybe:

<html>
<p class="pmkquote atcquote">
“Glider SC, Scottish”
</p>
</html>

<html>
<p class="pmkquote scquote">
“Go ahead, Glider SC”
</p>
</html>

<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>

<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>

<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>

<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>

<html>
<p class="pmkquote atcquote">
“Glider SC, roger, traffic now clear behind you, have a nice day.”
</p>
</html>

<html>
<p class="pmkquote scquote">
“Scottish, roger, I will call again later on the return trip.”
</p>
</html>

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:start#contents|Contents]] | [[g._reporting_defects_in_club_gliders|G. Reporting Defects in Club Gliders]]
Portmoak Pilot's Information and Airfield Manual

User Tools

Site Tools

Page Tools
