PCAA Navigation common mistakes
PCAA Navigation · Understand the traps and how to avoid them.
Treating the ICAO Annex provisions as if they were identical to the national AIP/regulatory text, and answering from memory of local practice rather than from the standard the question names.
Candidates learn procedures operationally from their own state's AIP and assume the wording is universal; ICAO Annexes, PANS, and regional supplementary procedures differ in detail (e.g., who may deviate from a rule, notification timelines, and unit conventions), so recall of local practice produces plausible but wrong options.
What to do instead
For each regulatory item, memorise the hierarchy explicitly: Convention/Annex standards, PANS procedures, regional supplementary procedures, then national regulation and AIP. Practise stating which layer a given requirement lives in and who is responsible for filing differences. When a question cites a specific document, answer only from that document's scope.
Confusing the roles and outputs of the flight plan, the operational flight plan, and the ATS flight plan, and mixing up which one carries fuel, alternate, and performance data.
The three documents overlap in content and are often produced by the same dispatch system, so candidates collapse them into one concept and then misanswer questions about who files, who approves, and what each contains.
What to do instead
Build a three-column comparison table: ATS flight plan (filed with ATS, contains route, level, endurance, alternates, aircraft identification), operational flight plan (operator's document, fuel policy, performance, loading, signatures), and flight log/journey log (actuals). Attach one worked example for a short-haul flight to each column so the boundaries are concrete.
Selecting a navigation aid or sensor based only on range or accuracy figures without checking the associated integrity, availability, or coverage limitations (e.g., using a GNSS-based approach without confirming SBAS/ABAS coverage or RAIM prediction).
Candidates memorise headline performance numbers (accuracy in metres, range in nautical miles) but not the failure modes of each system, so they pick the option with the best number and ignore whether the signal is usable, monitored, or approved for that phase of flight.
What to do instead
For each aid (VOR, DME, ILS, GNSS, SBAS, GBAS, radar, ADS-B), write a one-line profile covering: what it measures, what it does not provide, coverage limits, integrity monitoring method, and approved phases of flight. Practise questions by first identifying the phase of flight and required performance, then eliminating aids that cannot meet the integrity requirement.
Applying a single separation standard everywhere, for example quoting 5 NM radar separation in a terminal area where 3 NM applies, or applying lateral separation minima without checking the required navigation performance or surveillance coverage.
Separation minima are taught as numbers rather than as conditional rules, and candidates do not systematically check the conditions (airspace class, surveillance type, RNP/RNAV specification, wake turbulence category, runway/approach type) before choosing a value.
What to do instead
Create a decision checklist to run before every separation question: airspace class, surveillance service available, aircraft navigation specification, wake category of the leader, and phase of flight. For each combination, record the applicable minimum and the document that sets it. Practise by writing the conditions next to each option before selecting.
Mixing up the services and message sets of different CNS links, such as attributing CPDLC clearance delivery to VHF voice, confusing ACARS with ADS-C, or assuming ADS-B reports carry the same content as secondary radar replies.
The acronyms cluster around the same operational workflow (surveillance, communication, clearance), and study material often presents them together, so candidates learn the labels without learning which system carries which data and who uses it.
What to do instead
Draw a matrix of system versus function: communication (VHF/HF voice, CPDLC, ACARS, SATCOM), surveillance (PSR, SSR mode A/C, mode S, ADS-B, ADS-C, multilateration), navigation (GNSS, DME/DME, VOR/DME, INS). For each cell note the data carried, the update rate, and whether it is controller-, pilot-, or automation-initiated. Use it to answer by function first, then system.
Reading a METAR, TAF, or significant weather chart literally without converting units or interpreting change groups, and thereby misjudging crosswind, cloud base, or the validity period of a trend.
Reports use compact codes (e.g., BECMG, TEMPO, PROB30, RVR groups, QNH in hPa, wind in degrees/kt) and mixed units, and candidates skim the code groups, missing that a TEMPO condition is temporary or that a wind group is gusting, which changes the operational conclusion.
What to do instead
Decode reports group by group using a fixed template: wind (mean and gust, crosswind component), visibility/RVR, weather, cloud (base and amount), temperature/dewpoint, pressure, then change groups with their timing. Rehearse crosswind and cloud-base calculations from raw coded values until decoding is automatic, and always state the validity period before answering.
Using an out-of-date chart edition or treating chart symbols and scales as interchangeable, e.g., reading an approach chart minimum without checking the chart's effective date, or confusing chart scale with the scale of the underlying data.
Charts are revised on AIRAC cycles, and candidates rely on the version they studied rather than checking the effective date, chart index, and amendment status embedded in the question or the current AIRAC cycle.
What to do instead
Before answering any chart question, identify the chart type, its effective date/AIRAC cycle, the projection and scale, and the units used on that chart. Learn the standard symbology for aerodrome, en-route, and approach charts separately, and practise converting chart scale to real distance and to time at a given groundspeed.
Answering human factors and safety management questions from intuition or personal experience rather than from the defined concepts (e.g., calling any error 'violation', or describing a just culture as 'no blame').
Safety management terminology is precise (hazard, risk, occurrence, error versus violation, safety assurance versus safety promotion), and everyday language uses these words loosely, so intuitive answers are subtly wrong.
What to do instead
Memorise the SMS components and the error/violation taxonomy with one concrete aviation example each. For just culture, be able to state precisely what is and is not tolerated. When a question uses a safety term, define it in one sentence before evaluating the options, and eliminate any option that redefines the term.
Ignoring the 'except', 'most likely', 'initially', or 'not' in the stem and selecting the first technically true statement.
Exam stems are written to test discrimination, and under time pressure candidates pattern-match to a familiar phrase and stop reading, so a true but non-responsive option is chosen.
What to do instead
Adopt a two-pass method: first underline the qualifier and the requested object in the stem, then evaluate options against that qualifier only. Practise with question sets where every option is factually true but only one answers the specific stem, and time yourself to keep the discipline under pressure.
Failing to convert units and reference frames consistently (feet versus metres, knots versus km/h, magnetic versus true, hPa versus inHg, UTC versus local time) before computing a flight-planning or navigation answer.
Questions deliberately mix units and reference frames, and candidates compute with the first numbers they see, producing answers that are off by the conversion factor or by magnetic variation and therefore match a distractor.
What to do instead
Write the conversion and reference frame explicitly at the start of every calculation: state the unit of each given value, the target unit, and whether headings/bearings are true or magnetic. Use a standard conversion sheet (1 NM = 1.852 km, 1 ft = 0.3048 m, 1 kt = 1.852 km/h, 1 hPa ≈ 30 ft pressure altitude) and check the answer's order of magnitude before selecting.