Brunei DCA CPL(A) VFR Communications common mistakes
Brunei DCA CPL(A) VFR Communications · Understand the traps and how to avoid them.
Reading back a clearance by repeating only the tail end (e.g. "...two thousand, cleared") or acknowledging with a bare "roger" instead of full readback of route, level, heading and frequency.
Candidates treat readback as a courtesy acknowledgement rather than a verification loop, and under time pressure they copy the controller's last few words verbatim rather than reconstructing the clearance elements.
What to do instead
Practise a fixed readback skeleton: callsign, clearance limit/route, level, heading, frequency, any special condition - in that order, every time. Before keying the mic, silently tick off the elements you must return; if any is missing, say "say again" rather than half-reading back.
Using the wrong callsign format or dropping the aircraft type/registration suffix, e.g. transmitting "Charlie Papa Lima" alone on first contact, or abbreviating before ATC has done so.
Candidates confuse the abbreviated callsign that ATC has granted with the full callsign required on initial contact, and they mumble the registration because it feels redundant.
What to do instead
Memorise the rule: full callsign (type + registration) on initial contact and whenever requested; abbreviate only after ATC abbreviates first, and revert to full callsign if callsigns are similar or confusion arises. Drill the full callsign aloud until it is automatic.
Failing to state position and altitude/level in position reports, or reporting "overhead the field" without the reporting point name, time and next position with ETA.
Candidates learn position reporting as a memorised script but omit the elements they think the controller already knows from radar or from the flight plan.
What to do instead
Use the standard five-element order: callsign, position (named reporting point), time, level, next position and ETA. Rehearse it as a single rhythmic phrase so no element is dropped, and always name the reporting point rather than describing it.
Transmitting on the wrong frequency or at the wrong time - calling ground on tower frequency, calling tower before being handed off, or transmitting while another station is mid-exchange.
Candidates do not build a frequency-management habit (writing each new frequency and its owner on the flight log) and they listen for a gap rather than for the end of an exchange.
What to do instead
After every handoff, write down frequency and unit before changing over. Before transmitting, listen for a full 5–10 seconds and confirm no ongoing exchange; if in doubt, use the standard "[unit] [callsign], request frequency check" rather than blind-calling on an assumed frequency.
Confusing distress and urgency phraseology - using "PAN PAN" for a situation that is genuinely distress, or declaring "MAYDAY" for a minor problem, and omitting the nature of the problem and intentions.
Candidates remember only the opening words and not the required content sequence, and they hesitate to escalate because declaring an emergency feels disproportionate.
What to do instead
Learn both sequences as complete blocks: MAYDAY/MAYDAY/MAYDAY, callsign, nature of distress, intentions, position, level, persons on board, other information; PAN PAN/PAN PAN/PAN PAN with the same content. Decide the category by asking "is there grave and imminent danger requiring immediate assistance?" - if yes, MAYDAY.
Giving no plan or an incorrect plan after radio failure - e.g. simply stating "radio failure" without stating intended actions, or choosing a procedure that conflicts with the actual meteorological conditions and airspace.
Candidates memorise one radio-failure procedure and apply it regardless of IMC/VMC, controlled versus uncontrolled airspace, or the specific clearance last received, and they forget to state intentions before the failure becomes total.
What to do instead
Build a decision tree: last clearance acknowledged or not, VMC or IMC, controlled or uncontrolled. Practise stating it as a transmission: "[callsign], radio failure, maintaining VMC, proceeding to [aerodrome], will join [direction] for [runway], listening [frequency], transmitting blind." Rehearse each branch aloud.
Misinterpreting conditional or compound ATC instructions - e.g. "after the departing [type], line up and wait" or "cross [runway] behind the landing traffic" - and acting on the first clause only.
Candidates parse instructions sequentially as they hear them rather than holding the whole instruction, and conditional phrases sound like permission when they are actually a constraint.
What to do instead
Treat "after", "behind", "when", "until" as hold points: nothing is authorised until the condition is satisfied. Read back the full condition plus the action, then visually confirm the traffic or condition before moving. If unsure, ask "confirm we are cleared to [action] now?"
Omitting the transponder/SELCAL and frequency elements from readbacks and reports - e.g. not reading back a squawk, not reporting when leaving a frequency, or not confirming a SELCAL check.
Candidates regard squawk and frequency as administrative detail rather than safety-critical clearance content, and they are not practised at reading back four-digit groups.
What to do instead
Treat a squawk as a clearance: read back all four digits individually ("squawk four seven two one"). For SELCAL, respond with the assigned code and confirm the check. When leaving a frequency, state the next frequency. Drill four-digit and letter-group readbacks aloud.
Poor microphone technique and non-standard phraseology - clipped first syllables, "um", "er", non-standard words like "takeoff" outside a clearance, "repeat" instead of "say again", or "over and out".
Candidates are nervous and press the transmit button while still composing the sentence, and they use conversational English because it feels natural.
What to do instead
Compose the whole transmission mentally, then press, pause half a second, speak at moderate pace, release. Learn the standard vocabulary list and use "say again", "standby", "roger", "wilco", "correction", "disregard". Never say "takeoff" except in a takeoff clearance; use "departure" otherwise.
Failing to obtain or interpret VFR-specific information - not requesting airspace status, not reporting meteorological conditions encountered, or not confirming VMC before accepting a clearance that would put the aircraft in IMC.
Candidates treat VFR communications as purely positional and forget that VFR flight carries an obligation to report weather, request clearance into controlled airspace, and refuse clearances that cannot be flown under VFR.
What to do instead
Build a VFR checklist for each phase: airspace boundary and clearance requirement, weather report or request, VMC minima for the altitude and airspace. Practise the phrase "[callsign], request clearance into controlled airspace, [position], [level], VFR" and the report "[callsign], meteorological conditions, [description], [position], [level]" so both are automatic.