10.1 Navigation Definitions, Variation & UTC

10.1 Navigation Definitions, Variation & UTC

Quick Answer: Latitude and longitude fix position. Variation converts between true and magnetic directions. Track is the ground path; heading is where the nose points; drift is the wind-caused difference. Airspeed is through the air; groundspeed includes wind. Use the 24-hour clock and UTC (Zulu) for aviation times, convert correctly to Canadian zones (AST through PST and daylight variants), and treat sunrise/sunset as gates for night lighting and night-operation rules.

TP 15263 Section 5 navigation is not about airline oceanic plotting—it is about speaking the same geometric language as charts, CFS entries, NOTAMs, and ATC so Advanced RPAS pilots can plan, brief, and deconflict in shared airspace. Master the definitions cold; almost every later nav skill (chart reading, energy planning, GNSS awareness) rests on them.

Latitude and longitude

Earth position is described with a spherical grid:

Parallels of latitude never meet; meridians of longitude converge at the poles. One degree of latitude is roughly constant (~60 NM); one degree of longitude shrinks toward the poles. For RPAS site work you usually need accuracy to minutes (or better with GNSS), not “somewhere near the city.”

Practical uses for Advanced pilots:

1. Plot or verify a launch site on a VNC/VTA chart or digital planning tool.
2. Confirm distance from aerodrome centres and airspace boundaries.
3. Enter home points, geofences, and authorization polygons consistently (same datum—typically WGS-84 for GNSS).
4. Read NOTAM and CFS geographic references without guessing.

Exam trap: swapping lat/long order, or treating “northing” on a local grid as if it were geographic latitude without conversion.

Direction vocabulary: track, heading, bearing, course

These words are not interchangeable:

In wind, heading ≠ track. If wind blows from the left, you must point the nose somewhat into wind (crab) so the track stays on the planned line. Multirotor autopilots often hide the crab by yawing or translating; fixed-wing and hybrid RPA make the difference more visible. On the exam, pick the definition that matches the word used—do not assume “heading” always means the line on the map.

Airspeed, groundspeed, and wind velocity

Wind is always stated as the direction from which it blows (meteorological convention). A wind of 270°/15 kt is from the west at 15 knots. Headwind reduces groundspeed and can shrink range for a given energy budget; tailwind increases groundspeed outbound but may cost you on the return. Crosswind produces drift and forces continuous correction to hold track—raising power demand on multirotors that must translate sideways or crab while fighting gusts.

For small RPAS without classic ASI hardware, firmware still estimates air-relative vs ground-relative motion using GNSS and inertial data. Conceptually you still need: wind changes endurance, range, and the path back to the landing zone.

True vs magnetic: variation (and deviation)

Directions can be measured relative to:

• True north — geographic North Pole (meridians on most charts).
• Magnetic north — direction a magnetic compass needle seeks (magnetic pole).

Magnetic variation (also called magnetic declination) is the angle between true north and magnetic north at a location. It is labelled on charts with isogonic lines and often a variation note near the chart legend or aerodrome data.

Teaching rule of thumb (Eastern vs Western variation wording varies by training text; lock the algebra to your exam materials):

• Variation east: magnetic directions are less than true for the same line (classic “east is least”).
• Variation west: magnetic directions are greater than true (classic “west is best”).

In formula form many Canadian texts use:

• Magnetic = True − East variation (or True + West variation), depending on sign convention taught.
• Always apply the chart’s stated variation for that area and epoch—variation changes slowly over years as the magnetic field moves.

Deviation is the additional error of a particular magnetic compass caused by local magnetism in the aircraft (motors, wiring, steel). Manned aircraft use a compass correction card. Small RPA more often rely on electronic magnetometers with calibration routines; the Advanced idea remains: onboard magnetic sensing can be wrong near metal, vehicles, and power lines even when variation is applied correctly.

Exam focus: If a question gives a true track and a variation, compute the magnetic track/heading correctly; if it asks definitions, do not confuse variation (Earth’s field) with drift (wind) or deviation (aircraft magnetism).

Time systems: 24-hour clock and UTC

Aviation rejects ambiguous a.m./p.m. labels. Use the 24-hour clock: 0000 is midnight start of day, 1200 is noon, 1800 is 6 p.m., 2359 is one minute before next midnight. Times in flight plans, NOTAMs, METARs, and authorizations are routinely in UTC.

UTC / Zulu

UTC (Coordinated Universal Time) is the world civil time standard used in aviation. In radio and logs it is often called Zulu and written with a Z suffix (e.g., 1430Z). UTC does not observe daylight saving; local zones do. That mismatch is a classic error source every spring and fall.

Canadian zone examples (standard / daylight)

Offsets are hours to add to local to get UTC, or equivalently hours to subtract from UTC to get local. Confirm the current offset for the province/territory and whether daylight saving is in effect—Yukon and some regions have special rules, and Saskatchewan often stays on Central Standard-style observation patterns; use official time references operationally.

Worked conversions (examples):

1. NOTAM valid 1800–2200Z, pilot in Toronto on EDT (UTC−4): local window is 1400–1800 local (subtract 4 hours).
2. Briefing at 09:00 MST in Calgary in winter (MST = UTC−7): UTC = 1600Z same calendar day.
3. Pacific PDT afternoon 1600 local = 2300Z (PDT = UTC−7 → add 7).
4. Crossing into a new province mid-mission: the UTC log stays continuous; only the local wall clock jumps.

Exam traps: using standard offset during daylight saving; adding when you should subtract; forgetting Newfoundland’s half-hour; assuming all of Canada shifts to daylight saving the same way.

Sunrise, sunset, and night lighting relevance

Civil night for lighting and night-operation rules is tied to sunset and sunrise (and official definitions in the CARs/air law materials you study alongside this chapter). For Advanced RPAS:

• Night operations require the aircraft to be equipped and lit as required (position/anti-collision style lighting themes under Part IX night rules), and the pilot must meet night privileges/equipment conditions—not merely “fly until it’s dark.”
• Sunrise/sunset tables (CFS, NAV CANADA products, reputable astronomical sources for the site lat/long) tell you when lighting obligations and night rules engage.
• Twilight can trick vision: the sky may still look bright while the regulatory clock has crossed into night, or vice versa under heavy cloud.
• Mission planning must include battery + lighting power and VLOS contrast at dusk—telemetry alone is not a substitute for seeing the aircraft.

Link to human factors: reduced contrast at dusk increases loss-of-orientation risk; link to air law: lighting and night equipment are compliance items, not optional aesthetics.

Integrated definition checklist for the exam

1. Plot position with lat/long; know which is which.
2. Distinguish track / heading / bearing / course.
3. Apply wind → drift, groundspeed, energy.
4. Convert true ↔ magnetic with variation; remember deviation as aircraft-specific compass error.
5. Log and interpret times in UTC/Zulu with correct Canadian zone math.
6. Use sunrise/sunset for night lighting and night-ops go/no-go.

Bottom line: Navigation definitions are the grammar of flight planning. If you mix track with heading, true with magnetic, or EDT with EST against a Zulu NOTAM, every later chart and energy decision inherits the error. Drill the vocabulary and time conversions until they are automatic under the 60-minute Advanced exam clock.