DGCA CPL Aviation Meteorology common mistakes
DGCA CPL Aviation Meteorology · Understand the traps and how to avoid them.
Reading the altimeter subscale setting as the aircraft altitude, or mixing up QNH, QFE and QNE when computing true altitude or terrain clearance.
The three pressure references look similar on a question stem, and candidates memorise the definitions without practising the arithmetic that converts indicated altitude to true altitude or height above a datum.
What to do instead
Before answering, write down the definition of each reference (QNH = pressure reduced to MSL giving elevation when set; QFE = pressure at the aerodrome giving height above it; QNE/standard = 1013.25 hPa) and then compute step by step. Practise a set of 'high to low, look out below' problems until the direction of the error is automatic.
Treating the standard atmosphere as fixed rather than as a defined reference, and confusing pressure altitude with density altitude.
Both are 'altitudes' derived from pressure, so candidates assume they are interchangeable and ignore the effect of temperature on density altitude.
What to do instead
State the standard atmosphere values explicitly (MSL 15 C, 1013.25 hPa, lapse 1.98 C/1000 ft to 36,090 ft) and remember that pressure altitude depends only on pressure while density altitude also depends on temperature. Work one example where a hot day raises density altitude above pressure altitude.
Applying the environmental lapse rate and the DALR/SALR without checking which one the question is describing, and mixing up stability with the actual lapse rate sign.
Candidates learn 'lapse rate = 2 C/1000 ft' as a single number and then use it for saturated rising air, giving wrong stability conclusions.
What to do instead
Classify the parcel first: unsaturated air cools at the DALR (~3 C/1000 ft), saturated air at the SALR (~1.5 C/1000 ft). Compare the parcel rate with the environmental lapse rate to decide stability. Draw the two lines on a sketch before choosing an answer.
Assuming relative humidity of 100 percent means it is raining, or that dewpoint equals temperature only when fog is present.
Textbook definitions get memorised as isolated facts, and candidates do not connect saturation to the condensation process that produces cloud, fog or precipitation.
What to do instead
Anchor the chain: dewpoint = temperature means saturation; saturation plus condensation nuclei plus cooling produces cloud; precipitation additionally needs growth of droplets. Test each option against the whole chain rather than a single definition.
Misidentifying cloud types by altitude band, or attributing the wrong precipitation type or hazard to a given cloud.
Cloud names are learned as vocabulary lists, so candidates cannot map a described cloud (e.g. 'low, layered, ragged base') to its family and associated weather.
What to do instead
Build a two-axis table (family: high/middle/low/vertical; form: stratiform/cumuliform) and place each genus in it. Attach one weather signature to each (e.g. cumulonimbus = showers, hail, turbulence, icing; nimbostratus = steady rain).
Confusing the cause of local winds (sea breeze, mountain/valley, katabatic) with the general global circulation, and getting the diurnal timing of the sea/land breeze reversed.
Both are 'winds driven by pressure differences', so candidates answer from a vague sense of 'air moves from high to low' without tracking which surface heats faster and when.
What to do instead
For each local wind, state the driver (differential heating or gravity drainage) and the time of day it peaks. Sea breeze: land heats faster, blows sea to land, afternoon maximum; land breeze: reverse at night. Rehearse the direction and timing together.
Reading a front symbol or a TAF/METAR group incorrectly, such as treating a cold front as warm-sector weather or misreading TEMPO, BECMG, and probability groups as permanent conditions.
Candidates skim the coded groups and assume all forecast conditions in the TAF apply for the whole validity period.
What to do instead
Learn the change-group vocabulary as rules: BECMG = gradual permanent change, TEMPO = temporary fluctuations, PROB30/40 = probability. For fronts, draw the cross-section: cold front = narrow band, sharp slope, squally showers; warm front = wide band, shallow slope, steady rain.
Underestimating icing and turbulence as hazards by choosing 'moderate' answers, or failing to link them to the correct temperature band or cloud type.
Hazard severity is judged by feel rather than by the physical conditions, so candidates miss that clear icing occurs in the 0 to -20 C band in stratiform cloud and that severe turbulence is associated with CBs and mountain waves.
What to do instead
Memorise the hazard-condition map: clear ice = large supercooled drops, 0 to -20 C, stratiform; rime ice = small drops, colder, cumuliform. For turbulence, associate severe with CB, jet stream shear and mountain wave. Match the stem's conditions to the map before choosing severity.
Treating a thunderstorm as a single-stage event and missing the life-cycle stage described, or ignoring the difference between airmass and frontal thunderstorms.
The three-stage model (cumulus, mature, dissipating) is memorised but not applied, so candidates cannot tell which stage produces the hazard named in the stem.
What to do instead
For each stage, list the dominant hazard: cumulus = updrafts, little hazard; mature = hail, lightning, downbursts, severe turbulence; dissipating = downdrafts, anvil. Identify the stage from the described features before answering.
Confusing visibility reported in a METAR (prevailing, minimum, directional) with RVR, or reading a decoded observation without checking units and reference (statute miles versus metres).
Visibility appears in several forms on reports and charts, and candidates assume any number labelled 'visibility' is the same quantity.
What to do instead
Separate the terms: prevailing visibility = the main value, minimum visibility = lowest significant value, RVR = runway-specific range. Always check the unit and the reference point stated in the stem, and convert only after confirming which visibility type is being asked about.