HK PPL Radiotelephony common mistakes
HK PPL Radiotelephony · Understand the traps and how to avoid them.
Reading back the clearance you expected instead of the one actually transmitted - for example, reading back a climb to 4,000 ft when ATC cleared 5,000 ft, or omitting an intermediate level-off in a stepped descent.
Candidates rehearse typical clearance shapes during preparation and then pattern-match the first few words of the transmission, filling in the rest from memory. Under exam pressure the working-memory load of holding a clearance while formulating the readback makes this substitution more likely.
What to do instead
Train a strict sequence: write the clearance down (or hold each element in a numbered list) before keying the microphone, then read back from the written record element by element - level, heading, speed, frequency, squawk, and any condition attached. Practise with a partner who deliberately issues clearances that differ from the expected template, including conditional clearances, so that copying rather than predicting becomes the habit.
Using non-standard or colloquial phraseology in place of the prescribed phrase - for example 'taking off', 'cleared to land' on a ground frequency, 'with you', 'any traffic in the area please advise', or 'roger' where an explicit readback is required.
Candidates absorb phrasing from online videos, flight-simulator communities and informal cockpit chat rather than from the standard phraseology tables, and they underestimate how strictly examiners mark deviations from the prescribed wording.
What to do instead
Build a personal phraseology sheet organised by phase of flight with the exact prescribed phrases (for example 'line up and wait', 'cleared for take-off', 'standby', 'say again', 'wilco', 'roger', 'affirm', 'negative') and their correct uses. Say each one aloud until it is automatic, and record yourself on a simulated frequency, marking every departure from the standard wording.
Giving an incomplete readback of a taxi clearance, omitting the holding point designator, the intermediate taxiways, or the runway in use, and failing to read back a 'hold short' instruction in full.
Taxi clearances are long and contain several proper nouns in sequence; candidates treat them as routine and read back only the first and last elements. The safety-critical nature of hold-short instructions is often not appreciated until it is explained in terms of runway incursion.
What to do instead
Adopt a fixed readback template: callsign, 'taxi to holding point' plus designator, via each taxiway named, runway in use, and any hold-short instruction repeated verbatim including the reason if given. Practise with progressively longer routes and insist on reading back every named element, not a summary.
Failing to read back safety-related items in full - runway-in-use, SSR code, heading, altitude, speed, frequency - or acknowledging them with only 'roger' or 'wilco'.
Candidates confuse the general acknowledgement words with a valid readback, and they truncate readbacks under time pressure because the frequency sounds busy.
What to do instead
Memorise the readback-required list as a checklist (route clearances, runway-in-use, hold-short, level, heading, speed, frequency, squawk, altimeter setting, conditional clearances) and apply it mechanically. In practice, deliberately read back the full item even when it feels verbose, and have a partner flag any item acknowledged with 'roger' alone.
Using the wrong callsign form - dropping the aircraft type or the last two characters, using the abbreviated form before ATC has used it, or failing to distinguish similar-sounding callsigns on a busy frequency.
Candidates imitate the abbreviated callsigns they hear on recordings without knowing the rule that the full callsign is used on initial contact and that abbreviation is at ATC's initiative. Similar-sounding registrations are also hard to separate by ear.
What to do instead
Learn the rule explicitly: full callsign on initial contact, abbreviated form only after ATC has abbreviated it, and revert to the full callsign whenever there is any possibility of confusion. Practise discriminating pairs of similar callsigns by ear and always begin a transmission with your own callsign so the controller can identify the caller.
Making initial contact without the required elements - omitting position, altitude or level, or the ATIS identifier - or calling the wrong unit because the boundary between aerodrome and approach frequencies was not understood.
Candidates memorise a single 'initial call' script and apply it to every unit, and they have not thought through which agency owns which airspace and when the handover should occur.
What to do instead
Write out the required initial-call content for each unit type (ground, tower, approach, area) and for each phase, including position, level, and ATIS letter where applicable. Study the local AIP or aerodrome chart so that the sequence of frequencies and the transfer-of-control points are known before the flight, and rehearse the handover calls as a scripted sequence.
Mishandling a conditional clearance - reading back the clearance but not the condition, or acting on the clearance before the condition is satisfied (for example lining up or crossing behind traffic that has not yet vacated).
Conditional clearances have a two-part structure and candidates focus on the clearance itself because it is the part that authorises action. The condition is often short and easy to drop from the readback.
What to do instead
Learn the structure as a fixed formula: condition first, then clearance, then the condition repeated in the readback. Never accept a conditional clearance that is not clearly understood - ask for it to be repeated. In practice, verbalise the condition aloud as a gate ('only after the landing aircraft has passed') before taking any action.
Fumbling distress and urgency procedures - using 'PAN PAN' when the situation is a distress, failing to include the required elements (nature of emergency, intentions, position, level, persons on board), or cancelling a distress call prematurely.
These procedures are rarely used in normal flying, so candidates learn them as text and never rehearse them aloud. The distinction between distress and urgency is understood in principle but not applied quickly under pressure.
What to do instead
Drill the two formats aloud until they are automatic: MAYDAY three times for distress, PAN PAN three times for urgency, each followed by callsign, nature of problem, intentions, position and level, and any other useful information. Rehearse scenarios (engine failure, smoke in cockpit, passenger medical emergency) and practise the cancellation or downgrade call as a separate step.
Handling a communication failure incorrectly - continuing to transmit on a failed radio, failing to follow the prescribed lost-communication actions (squawk 7600, attempt contact on other frequencies, follow the notified procedure), or misreading a request to 'standby' or 'say again' as a failure.
Candidates confuse a receiver failure with a transmitter failure and do not know the decision sequence for the loss of two-way communication, so they either give up or keep transmitting blindly.
What to do instead
Learn the lost-communication sequence as an ordered checklist: attempt contact on the assigned frequency, then on other frequencies, then squawk 7600, then comply with the published lost-communication procedure for the airspace and land as soon as practicable. Practise distinguishing 'say again' and 'standby' from a genuine failure, and rehearse transmitting blind with position and intentions.
Poor microphone discipline and listening technique - transmitting before the previous exchange has finished, blocking the frequency with long transmissions, missing a call because the volume or squelch was not set, or not using 'say again' with the correct phrase when part of a message was lost.
Candidates focus on what they will say rather than on receiving, and they are embarrassed to ask for a repeat, so they guess at the missing content. Long, unstructured transmissions come from composing the message while keying the microphone.
What to do instead
Practise a receive-first habit: listen to the full exchange, note the callsign addressed, and only then key the microphone with the message already formed. Learn the standard recovery phrases ('say again', 'say again all after', 'say again all before', 'I say again') and use them without hesitation. Keep transmissions short and structured, and check radio volume and squelch before every simulated exercise.