With my FRTOL exam being just over a day away, and really REALLY not wanting to fail (for various reasons but also because the format changes after May and our local examiner won't be licensed to do them any more), I have been doing a bit of revision to try to make sure I have prepared enough. My learning has been based on the Comms book, CAP413, the G-UDRT app, the Safety Sense Radiotelephony leaflet (which is excellent and has a transcript of an example exam at the end!), the SRG1171 form, and of course all of my lessons to date in the air.
I came across the SRG1171 form myself and it says: "Completion of this form is mandatory and is to be declared to the FRTOL Examiner prior to the FRTOL practical test". Is this still a thing that has to be done? Nobody has mentioned it to me yet but I might print one off just in case (maybe the flying school already has filled one out for me in my file somewhere, I don't know...).
In any case, I feel like I can probably muddle through most aspects of aerodrome R/T (startup, radio check, taxi, take-off, etc), circuits, departing, arriving, changing frequency, requesting MATZ penetrations, LARS, and generally "getting around". I've been fortunate to have done my training at a mix of ATC, AFIS and unattended aerodromes plus a couple of landaways at AGCS aerodromes, so I feel reasonably confident about how to make requests and when to follow instructions etc under the various different levels of control / service. I think I will also recognise all the mandatory readback items when they come up. However, things like Mayday, Pan-Pan, relay of emergency calls, VDF (like requesting QDMs), and zone crossings have only been demonstrated and practised once or twice, and I have never requested or seen an SVFR clearance or a DACS or DAAIS so my knowledge of these is limited to the books. As such I will note down the main "cheat sheet" items that I think I need to remember, and if anyone is reading and spots something wrong feel free to call it out!
1) Responses to "Pass your message": ADDPAR
A - Aircraft callsign and type
D - Departure
D - Destination
P - Position
A - Altitude + QNH
R - Request, additional details, intention
Example:
G-ABCD, C152, Cambridge to Cambridge, overhead Waterbeach, altitude 2000 on QNH 1020, squawking 7000, request MATZ penetration
2) Mayday / Pan-Pan structure: CATNIP AHQA (side note: if lost, and not currently receiving a service, can do Pan-Pan to London Centre squawking 0030)
C - Call sign of Station
A - Aircraft callsign
T - Type
N - Nature of issue
I - Intentions
P - Position
A - Altitude
H - Heading
Q - Qualifications
A - Anything else that will be useful info (typically at least the number of POB)
Example:
Mayday Mayday Mayday, London Centre, Student G-ABCD, C152, engine fire, making forced landing in field, 2 miles north Wyton, altitude 2100, heading 180 degrees, student pilot, 1 POB
3) Relaying a Mayday (this is the one I think I find most difficult to remember correctly, and especially to write down all details when listening!)
Mayday Mayday Mayday
(station addressed)
(my callsign)
Have intercepted Mayday from
(their callsign)
I say again
(their callsign followed by all the remaining TNIP AHQA details that have been recorded)
Example:
Mayday Mayday Mayday, London Centre, Student G-ERIC, have intercepted Mayday from G-ABCD, I say again, G-ABCD, C152, engine failure, making forced landing in field, 5 miles south Snetterton, altitude 1100, heading 013, PPL, 2 POB
4) Requesting a QDM, QDR or QTE:
- can use "Homer" as callsign for VDF-equipped stations rather than the usual "Approach / Radar" although probably OK to use either
- Normal request but add your callsign at the end as well as the start
- Expect to read back both a bearing and accuracy (typically Bravo meaning within +/- 5 degrees)
- For QTE, CAP 413 gives a slightly different format of message than the QDM examples. For their QTE example they use "True bearing" and also prefix this twice. I'm not sure why, or if this can be used as standard for e.g. QDM as well and it's just another way to do the same thing and extend the call a bit more to give the VDF equipment more time to "lock on"?
Examples:
Cambridge Homer, G-ABCD, request QDM, G-ABCD
or
True bearing, true bearing, Cambridge Homer, G-ABCD, request true bearing, G-ABCD
5) Position reports: APTAN
A - Aircraft callsign
P - Position
T - Time
A - Altitude
N - Next position and ETA
Example:
G-ABCD overhead Wyton at 25, altitude 2000, Cambridge 34
6) Zone crossing:
Start things off with something like "Luton Radar, G-ABCD, Request zone transit". If not talking to them already: maybe also request a Basic Service at the same time and expect a "Pass your message" too. Include flight rules (VFR) when passing message along with the usual ADDPAR. Then expect lots of things to come back e.g. squawk / QNH, maybe a request for reporting at VRPs, maybe remaining outside, or even a clearance. If a clearance is given, write down all details and limits and read them back. Also expect "Radar control" when in the zone (just reply "Radar control" and follow instructions). Things like "Report field in sight" may be common.
7) DACS / DAAIS: just a normal request describing which danger area it is (Delta + number)
Example:
Someplace Approach, G-ABCD, Request Danger Area Crossing Service for Delta 123
Special VFR: just request it when "passing your message" along with e.g. zone entry / join request when below weather minima
Example:
G-ABCD, C152, Cambridge to Luton, 2 miles southwest Bedford, altitude 1500 on QNH 1010, Request Special VFR zone entry and join
Bonus things I will almost certainly forget:
- Say "hectopascals" after a QNH/QFE below 1000
- Say "degrees" after headings ending with 0
- Don't say "ten miles south Wyton" or whatever - it is "one zero miles south Wyton"
- FL100 is "flight level one hundred" but FL110 is "flight level one one zero". (I won't be going that high anyway though
)
- "Correction" is my friend