CPL Navigation common mistakes
CPL Navigation · Understand the traps and how to avoid them.
Adding or subtracting the magnetic variation in the wrong direction when converting between true and magnetic headings.
Candidates memorise 'variation east, magnetic least' as a slogan but cannot apply it to a sketch, so they reverse it under exam pressure, especially when the question gives easterly variation in a westbound scenario.
What to do instead
Before calculating, draw a three-line compass rose with true north, magnetic north and the aircraft heading; place variation between the two norths and read the correction off the diagram. State the rule in words ('east variation: magnetic heading is smaller than true heading') and check the answer is plausible: variation in Australia is a few degrees, so a 12-degree error signals a reversed sign.
Computing track-made-good and drift by using groundspeed or heading instead of resolving the wind triangle with the correct vectors.
Candidates treat the wind triangle as an arithmetic formula to memorise rather than a vector diagram, so they add wind speed to true airspeed directly or apply drift to the wrong leg.
What to do instead
Always sketch the triangle: true heading and true airspeed from the origin, wind vector from the end of that line, and the resultant closing back to the origin as track and groundspeed. Solve with the sine rule for drift and the cosine rule for groundspeed, then verify that a tailwind increases groundspeed and a crosswind produces drift toward the downwind side.
Calculating a heading to steer using only the wind correction angle without converting the resulting true heading to compass heading via variation and deviation.
The wind triangle naturally produces a true heading, and candidates stop there because the calculation feels complete, forgetting that the pilot flies a compass heading.
What to do instead
Adopt a fixed output sequence: true track, apply wind to get true heading, apply variation to get magnetic heading, apply deviation to get compass heading. Write the four labels as column headings on the working sheet and fill each one, so no conversion is skipped and the final answer is the compass heading the question asks for.
Treating a chart's stated scale as valid for measuring distance without checking for projection distortion or using the correct latitude scale on a Mercator chart.
Candidates measure with a ruler against the scale bar at the bottom of the chart, not realising that on a Mercator projection scale varies with latitude and the bar applies only at its reference latitude.
What to do instead
On Mercator charts, measure distance by comparing the interval against the latitude graduations on the same horizontal level as the route, using one minute of latitude equals one nautical mile. Use the scale bar only for small distances near its stated latitude, and state in the answer which method was used.
Plotting a position from a bearing and distance by measuring the bearing from the wrong reference or applying the distance along the bearing line in the reciprocal direction.
Candidates confuse the bearing 'from' and 'to' a point, and protractor placement errors of 180 degrees are easy to make when the origin is not clearly marked.
What to do instead
Mark the origin with a distinct dot, draw a north line through it, measure the bearing clockwise from that north line, then step the distance along the ray away from the origin. Sanity-check the plotted point against the expected quadrant (for example, a bearing of 045 degrees must plot up and to the right) before committing.
Planning a route by joining waypoints with straight lines on a chart without checking controlled airspace, restricted areas, or terrain along each leg.
Candidates focus on the mathematical track and distance and treat airspace as a separate topic, so the navigation plan is geometrically correct but operationally illegal.
What to do instead
After drawing each leg, run a structured corridor check: note every airspace boundary, restricted or danger area, and minimum safe altitude within a defined distance either side of track, and record the clearance or avoidance action in the plan. Build this as a checklist column in the flight plan table so it cannot be skipped.
Filing or using a flight plan with fuel, endurance, or alternate figures that were computed once and not updated after the route or wind changed.
Candidates treat the flight plan as a document to complete rather than a live calculation, so a late route amendment leaves fuel and endurance figures inconsistent with the final track and distance.
What to do instead
Recalculate endurance last, from the final leg-by-leg time and fuel figures, and cross-check that total fuel covers trip fuel plus reserve plus contingency with a stated margin. If any leg changes, mark the whole plan as superseded and redo the dependent figures rather than patching one number.
Misreading or omitting the validity, units, and reference data when extracting information from navigation documentation such as AIP entries, NOTAMs, or chart legends.
Candidates skim for the headline fact (a frequency or an elevation) and ignore the effective dates, units, and footnotes that determine whether the information applies to the planned flight.
What to do instead
Read each document with a fixed extraction template: what, where, when effective, units, and source. Record the effective period against the planned date of flight before using any value, and note explicitly when a NOTAM supersedes a published charted value.
Converting between units (nautical miles, statute miles, kilometres, feet, metres, knots) inconsistently within a single calculation.
Candidates mix units because charts, documents, and performance data use different conventions, and the arithmetic still produces a number, so the error goes unnoticed.
What to do instead
Write the unit beside every number in the working, and convert to a single working unit (normally nautical miles, knots, and feet) before calculating. At the end, convert back to the unit the question requests and check the magnitude is sensible, for example that a distance in kilometres is larger than the same distance in nautical miles.
Answering a time, fuel, or ETA question by using groundspeed for one leg and true airspeed for another, or forgetting the time zone offset when giving an ETA.
Multi-leg questions reward consistent method, but candidates recompute from scratch on each leg and drift between airspeed and groundspeed, and they convert UTC to local time in the wrong direction.
What to do instead
Build a leg table with columns for distance, wind, groundspeed, time, and cumulative time, and carry groundspeed forward for every time calculation. Convert all times to UTC for the calculation, then apply the local offset once at the end, checking that the local time differs from UTC by the expected whole or half hours for that region.