DGCA ATPL Air Navigation common mistakes
DGCA ATPL Air Navigation · Understand the traps and how to avoid them.
When converting between true, magnetic and compass directions, the candidate adds the variation instead of subtracting it (or vice versa), or applies variation to a compass heading in the wrong order, producing answers that are wrong by twice the variation.
The 'variation east, magnetic least' mnemonic is memorised as words but not internalised as a direction of application, and candidates work forward through the conversion chain without a sanity check on whether the magnetic value should be larger or smaller than the true value.
What to do instead
Before computing, state the local variation with its sign and write the conversion as an explicit equation (e.g. True = Magnetic + East variation, or True = Magnetic − West variation). After the calculation, verify that the result lies on the correct side of the true value and that the magnitude of the change equals the variation exactly.
On chart and map-reading questions the candidate measures a track or distance against grid north or the wrong scale, or reads a bearing off a chart whose graticule is not aligned with the chart edges, yielding a track that is off by several degrees or a distance off by a scale factor.
Candidates assume the top of the chart is north and use the nearest printed scale bar without checking whether the chart is a Lambert, Mercator or polar stereographic projection where convergence and scale vary across the sheet, and they skip the step of converting grid to true using convergence.
What to do instead
Always identify the projection and the reference direction of the graticule first. Use the chart's own meridians to establish true north, apply convergence explicitly (True = Grid + convergence, with sign per hemisphere), and measure distance only along the relevant scale (use the scale at the latitude of measurement on a Mercator chart, not a single scale bar).
When computing time problems (ETA, elapsed time, sunrise/sunset, crossing time zones), the candidate mixes LMT, UTC and zone time without a consistent reference, or applies the longitude-to-time conversion with the wrong sign, producing ETAs that are hours out.
The relationship between longitude, LMT and UTC is learned as a formula (15° per hour, 4 minutes per degree) but the sign convention (east positive, west negative) is not fixed in the candidate's mind, and candidates convert to UTC only at the end rather than at the start.
What to do instead
Convert all times to UTC immediately at the start of the calculation, work entirely in UTC, and convert to local time only as the final step. Write the longitude sign explicitly (East +, West −) and check that the answer's local time makes sense relative to the sun's position at that longitude.
On dead-reckoning and flight-planning legs, the candidate computes a heading and groundspeed using the wind triangle but applies drift in the wrong direction (adding drift to track instead of to heading) or uses TAS where groundspeed is required, producing headings and ETAs that are consistently wrong.
The wind triangle is solved by rote formula without a physical picture of which vector is which; candidates confuse the track/drift relationship and forget that heading must be corrected into wind by the drift angle, and they carry TAS through to the ETA calculation.
What to do instead
Draw the wind triangle every time (true track and groundspeed on the ground, heading and TAS in the air, wind vector joining them) and read drift off the diagram rather than from memory. Use groundspeed, never TAS, for ETA and fuel-flow time calculations, and cross-check that the heading is offset from track toward the wind.
On VOR, NDB/ADF and ILS questions the candidate confuses radials with bearings (e.g. treats a VOR radial of 090 as a bearing of 090 from the aircraft, or misidentifies the CDI deflection sense and TO/FROM indication), and on ADF questions confuses relative bearing with magnetic bearing.
The definitions (radial = magnetic bearing from the station; relative bearing = angle between aircraft heading and the bearing to the station) are memorised as sentences but not applied to a spatial picture, so candidates default to treating every displayed number as a bearing to or from the aircraft.
What to do instead
For every radio-navigation question, sketch the station, the aircraft and the relevant vector, then label each number with its definition before answering. Practise the conversions explicitly: Magnetic bearing to station = heading + relative bearing; QDM/QDR relationship; CDI centred with TO/FROM flag interpreted against the selected course.
The candidate answers altimetry questions using indicated altitude or pressure altitude directly as true altitude, ignoring temperature error and the difference between QNH, QFE and standard pressure settings, so terrain clearance and flight-level calculations are wrong in cold or high-elevation conditions.
The altimeter is treated as a direct height-measuring instrument; candidates forget that cold temperatures cause the altimeter to over-read (true altitude lower than indicated) and that the transition between QNH and standard pressure changes the reference datum.
What to do instead
For every altimetry question, state the pressure setting and temperature regime first, then apply the cold-temperature correction rule (true altitude is lower than indicated in cold air; apply the 4% per 10°C ISA-deviation rule of thumb where appropriate). Distinguish clearly between indicated, pressure, density and true altitude and convert explicitly between them.
On mass-and-balance questions the candidate computes total mass and CG but omits zero-fuel mass limits, uses the wrong datum sign convention for arms ahead of the datum, or fails to check that the loaded CG lies within the envelope at both take-off and landing configurations.
Candidates focus on the arithmetic of moments and treat the CG envelope as a single point check, forgetting that fuel burn moves the CG and that ZFM and landing mass have their own limits; negative arms (items ahead of datum) are a frequent sign error.
What to do instead
Set up a tabular moment calculation with every item, its mass, its arm (with explicit sign relative to the datum) and its moment, sum carefully, then plot or check the CG against the envelope at ZFM, take-off and landing. Confirm all three mass limits (MTOM, MLM, MZFM) explicitly rather than only the total.
On performance questions the candidate uses the wrong chart axis or fails to apply the correct corrections (pressure altitude vs density altitude, wind component, slope, temperature, contamination) and reads a take-off or landing distance without checking whether it is ground roll, TODA, ASDA or TORA.
Performance charts are read by finding the nearest line rather than by interpolating between the correct entry conditions, and candidates do not distinguish the declared distances, so they answer with the wrong quantity even when the chart is read correctly.
What to do instead
Before reading any chart, write down the required output (TORA, TODA, ASDA, ground roll, etc.) and the entry conditions in the correct units. Convert QNH and elevation to pressure altitude, then temperature to density altitude if the chart requires it, apply wind and slope corrections in the order the chart specifies, and interpolate rather than rounding to the nearest line.
On GNSS and radar questions the candidate confuses the roles of the segments and error sources (e.g. attributes ionospheric error to the control segment, or assumes RAIM detects all errors), and on radar questions confuses primary and secondary radar returns or misinterprets the display.
GNSS architecture and radar principles are learned as lists without a functional model, so candidates cannot reason about which component causes which effect and default to plausible-sounding but incorrect associations.
What to do instead
Build a one-page functional diagram of GNSS (space, control, user segments; sources of ranging error; what RAIM and SBAS/GBAS actually correct) and of radar (primary skin-paint vs secondary transponder, range vs bearing accuracy). Answer by tracing the question back to the diagram rather than recalling lists.
On operational-procedures and navigation-regulation questions the candidate applies the wrong rule set (e.g. mixes ICAO flight-level semicircular rules for different track bands, or applies VFR minima in IMC, or misstates equipment/airspace requirements) because the rule is recalled generically rather than by its precise condition.
Regulations are studied as isolated facts without the conditional structure (track band, airspace class, flight rules, magnetic vs true track), so candidates pick the rule that 'sounds right' rather than the one matching the stated conditions.
What to do instead
For each regulation question, extract the governing conditions first (track band, airspace class, flight rules, altitude reference) and then apply the specific rule for those conditions. Keep a condensed reference of the semicircular rule, transition altitude/level, airspace equipment requirements and VFR/IMC minima, and practise applying it to worked scenarios rather than re-reading it.