CAA NZ CPL Meteorology common mistakes
CAA NZ CPL Meteorology · Understand the traps and how to avoid them.
Reading TAF validity and change groups as fixed weather for the whole period, e.g. treating a TEMPO or BECMG group as applying from the start of the TAF, or taking an INTER period as covering the whole forecast.
Candidates learn the TAF layout by memorising the order of groups but never practise mapping each change group onto its own time window. Under exam pressure they read the TAF top-to-bottom as one narrative and assume the first condition listed governs the whole validity period, so they miss that BECMG describes a transition and TEMPO/INTER describe temporary fluctuations within it.
What to do instead
Before answering, draw a timeline of the TAF validity and mark every change group's start and end on it. State explicitly which groups overlap and which succeed each other. Practise with real TAFs where a BECMG to a lower cloud base sits inside a period that also has a TEMPO for showers, and write one sentence per group describing when it applies. Only then answer the question.
Confusing METAR and TAF time conventions and reported phenomena, for example treating a METAR's observation time as the start of a forecast, or reading 'NOSIG' as 'no significant weather now' rather than 'no significant change expected in the trend period'.
METAR and TAF share much of their code, so candidates skim the header and assume the product type from the presence of a trend group. NOSIG and the trend groups (BECMG, TEMPO) belong to the METAR/SPECI trend forecast and describe expected change, not current conditions, and candidates who have only memorised the decode table miss this distinction.
What to do instead
Learn the product structure separately: METAR/SPECI = observation plus optional trend; TAF = forecast. For each product, identify the issue time, observation or validity time, and whether any trend group is present. Write out in plain English what the trend group is forecasting and over what period, and check that your answer distinguishes observed from forecast weather.
Misreading significant weather and cloud codes, particularly CB/TCU, the difference between FEW/SCT/BKN/OVC amounts, and vertical visibility (VV) in an obscured sky, then drawing the wrong operational conclusion about icing, turbulence, or VMC/IMC.
The decode tables are memorised as isolated definitions rather than as operational signals. Candidates know BKN means broken but not that a BKN layer plus CB implies a risk of embedded cumulonimbus and severe turbulence, or that VV002 means the sky is obscured and the reported figure is vertical visibility, not cloud base.
What to do instead
Build a one-page decode sheet and, next to each code, write the operational consequence (CB = icing, turbulence, microburst risk; VV = obscured sky, no cloud base reported; OVC low = likely IMC at approach). Drill decode questions by writing the plain-English meaning and the pilot action before choosing an answer.
Treating area forecasts and advisories (ARFOR, SIGMET, AIRMET, and the graphical/area products) as interchangeable, and applying a SIGMET to the wrong area, level, or validity window.
Candidates learn each product in isolation and never compare their purpose, area of coverage, and issuing triggers. In the exam they pick whichever product name looks familiar rather than reasoning about who issues it, what it covers, and whether it is a warning of hazardous phenomena or a routine area forecast.
What to do instead
Make a comparison table with columns for issuer, area covered, validity, triggering phenomena, and whether it is routine or advisory. For each practice question, first ask 'what phenomenon, where, and over what period?' and only then select the product. Check SIGMET validity and flight level band against the scenario before answering.
Ignoring the flight-level and validity constraints on SIGMETs and AIRMETs, for example accepting a SIGMET for a phenomenon below the levels it covers, or using an expired SIGMET because the issue time looked recent.
Candidates focus on the phenomenon named in the SIGMET and skip the header and footer fields. Validity periods, sequence numbers, and level bands are the parts most often skimmed, so a plausible-sounding but out-of-date or out-of-level advisory is chosen.
What to do instead
Adopt a fixed reading order for every advisory: phenomenon, location, level band, validity start and end, then sequence number. Answer only after confirming the current time in the scenario falls inside the validity and the aircraft's level falls inside the band. Practise with questions that deliberately include an expired or mis-levelled advisory.
Applying New Zealand-specific met regulation and service-provider arrangements from general knowledge or from another country's rules, e.g. assuming the wrong issuer for warnings, the wrong units, or the wrong thresholds for when a SIGMET is required.
Candidates study generic meteorology and then guess the regulatory layer, or transfer FAA/EASA conventions they have seen elsewhere. New Zealand's provider arrangements, unit conventions (e.g. hPa, knots, feet), and advisory thresholds are specific and are tested directly.
What to do instead
Study the NZ-specific regulatory material as a separate topic: who provides what service, which products are mandatory, units and thresholds, and the definitions used in NZ publications. Where you are unsure, mark the item for review rather than guessing. Build a short list of NZ-specific facts and test yourself on issuer, unit, and threshold for each product.
Confusing the roles of the meteorological authority, the air navigation service provider, and the pilot's own responsibility for weather decision-making, and answering regulation questions as if one body does everything.
The regulatory framework splits responsibilities between the authority that sets rules, the provider that issues products, and the pilot in command who makes the go/no-go decision. Candidates collapse these into one and pick answers that sound authoritative but assign the wrong duty.
What to do instead
Write a responsibility map: rule-making, product issuance, dissemination, and operational decision. For each regulation question, identify which role is being asked about before evaluating the options. Remember that no forecast product relieves the pilot in command of the decision, and check answers against that principle.
Reading only the headline of a MET development or product-change item and missing what actually changed, e.g. new product formats, amended thresholds, or changes to dissemination, then applying the old convention.
Development questions are often answered from habit or from older study notes. Candidates recognise a familiar product name and assume the details are unchanged, so they miss the specific amendment the question is testing.
What to do instead
Keep a dated change log of MET product and regulation updates and revise it before the exam. For each development question, ask 'what specifically changed, when, and what does the pilot do differently now?' If your notes predate the change, flag the item for review rather than answering from memory.
Misinterpreting trend and forecast uncertainty language, treating a probability or a TEMPO as a guarantee, or treating a forecast as a fixed observation when making a diversion or alternate decision.
Candidates want a single definitive answer and read probabilistic or temporary conditions as certain. This leads to answers that over-commit (e.g. 'the weather will be IMC') when the product only indicates a chance or a temporary fluctuation.
What to do instead
Annotate every forecast with its confidence language: 'expected', 'temporary', 'probability of'. Answer questions in terms of risk and planning (e.g. carry fuel for the alternate, plan for the TEMPO) rather than certainties. Practise writing the operational decision that each forecast wording supports.
Skipping the units and datum checks on pressure, wind, temperature, and height, and mixing hPa with inches, knots with km/h, or feet with metres when interpreting a product.
Candidates decode the letters correctly but not the numbers, especially under time pressure. A QNH in hPa read as inches, or a wind in knots read as km/h, changes the answer completely, and questions are often built around exactly this slip.
What to do instead
Circle every unit in the question and in your working before calculating. Convert to a single system, write the conversion explicitly, and sanity-check the result against typical values (QNH near 1013 hPa, surface wind in tens of knots). Include unit-conversion drills in your revision rather than assuming the units.