HomecplNavigationCh.30 — Notes
30
NAVIGATION — CHAPTER 30 · NOTES

CX-3: Wind Finding and Flight Planning

by Ghost Aviator

LECTURE PARTS
STUDY AID — PENDING INDEPENDENT AUDIT These notes are study aids for DGCA examination preparation. They are PENDING INDEPENDENT AUDIT and must not be used for operational flight planning. Always verify procedures against current AIPs, NOTAMs, and your operator's manuals.
General Navigation · The Navigation Computer

Chapter 8B
The Flight Plan and Wind Finding

Every chapter of this module has been one operation at a time. This is where they all run in a single row of a table — and where the computer stops being a calculator and becomes a flight planning tool.

A completed paper flight plan log on a table under a low warm light, its columns of
       figures running down the page, a pencil resting across it.
Opening plate — One row per leg, and every column earned by a separate skill. By the end of this chapter you will be able to fill one from the left edge to the right without stopping.
Sixty seconds before start-up

The chart is marked, the legs are measured, the forecast is in your hand. In front of you is a table with fourteen columns and seven rows, and every cell is empty except the ones you were given.

Nothing in that table is new to you. Column by column it is Chapter 6 (a calibrated airspeed and a temperature become a true airspeed), then Chapter 8A (a track and a wind become a heading and a ground speed), then this chapter (a true heading becomes the number you will actually steer by), then Chapter 5 (a distance and a ground speed become minutes).

The skill being tested is not any one of those. It is doing all four in order without losing your place. That is why the exercises at the end of this chapter are worked across the rows and never down the columns.

1 · What a flight plan actually is

Strip the printing away and a flight plan row is a chain of five conversions. Each one hands its answer to the next, which is exactly why a mistake in the third column is invisible until the last one is wrong.

StepYou haveYou wantWhat does itChapter
1 CAS, pressure altitude, OAT TAS FLT → Airspeed → Planned TAS 6
2 Track, TAS, W/V Heading (T), GS PLAN → Leg 8A
3 Heading (T), variation Heading (M) arithmetic, or the Var field this one
4 Heading (M), deviation Heading (C) arithmetic, or the Dev field this one
5 Distance, GS Time FLT → Ground Speed, or ETE 5
Why the whole module has been building to this

A student who can do steps 1, 2 and 5 in isolation and cannot fill in a flight plan row has not learned navigation. They have learned three party tricks.

The examination knows this, which is why the flight plan questions are worth disproportionate marks and why they are where candidates run out of time.

2 · Variation and deviation — and the sign trap that will get you

Steps 3 and 4 are the only genuinely new arithmetic in this chapter, and they are two lines. The danger is not the arithmetic. It is the sign.

The rule, and the mnemonic that has never let anyone down

Variation west, magnetic best.
Variation east, magnetic least.

So going from true to magnetic:

Magnetic = True + West variation
Magnetic = True − East variation

And deviation behaves identically, one step further along: Compass = Magnetic + West deviation.

Worked: true 095°, variation 5°W → magnetic 100°. Then deviation 1°W → compass 101°. West both times, so you add twice.

The trap: the book's plus sign and the CX-3's plus sign mean opposite things

Most rows in the exercises write variation in words — 5°W, 3°E — and there is no ambiguity. But some rows write it as a signed number, and there the two conventions you will meet are exact mirrors of each other.

+ means− means
The exercises in this chapter EastWest
The CX-3's Var field WestEast

Type the book's sign straight into the machine and you do not get the variation slightly wrong. You get it wrong by twice the variation — once for applying it backwards, once for the correction you needed and did not get. On a 34° variation, which appears in these exercises, that is 68°.

The CX-3's own words, from the User's Guide V1.3: "east is least, west is best: enter a positive number for a westerly variation and a negative number for an easterly variation." Its own worked example enters 17° East as 1 7 +/− → −17.

Read the machine's convention as the mnemonic made mechanical, not as a contradiction of it. It computes Magnetic = True + Var, so entering east as negative produces the subtraction the mnemonic describes. The arithmetic is the same rule you already know. What changes is only which key you press first.

The safe habit, and it costs two seconds: never type a variation as a bare signed number. Say the word to yourself — "five west" — decide from the mnemonic whether the magnetic heading gets bigger or smaller, and only then decide what to press.

Deviation is smaller, which is exactly why it is missed

Variation runs to tens of degrees and demands attention. Deviation is usually one, two, three degrees, and a student who has fought through the variation quietly forgets it.

It is the last column before the number you actually fly. An unapplied 3° deviation is 3° of track error for the whole leg — five miles at the end of a hundred.


3 · One leg, end to end

Here is a single row of Flight Plan 1, worked from the left edge to the right, with nothing skipped. Once you can do this one you can do all thirty.

  • Pressure altitude — 2000 ft
  • OAT — −10°C
  • CAS — 160 kt
  • Track required — 100°(T)
  • W/V — 330/17
  • Variation — 5°W · Deviation — 1°W
  • Distance — 50 NM

Worked example 8B.1. Fill the row. Find TAS, heading true, heading magnetic, heading compass, ground speed and time.

Method 1 — the arithmetic
five steps, in order, never skipping

1. TAS. Density ratio at 2000 ft and −10°C is 1.018, so
TAS = 160 ÷ √1.018 = 158.6 → 159 kt

2. Heading and GS. Wind from 330 points toward 150. θ = 150 − 100 = 50°
WCA = sin⁻¹(17·sin50 ÷ 159) = 4.7°
HDG = 100 − 4.7 = 95.3 → 095°(T)
GS = 159·cos4.7 + 17·cos50 = 169.4 → 169 kt

3. Magnetic. Variation 5°West, so magnetic is best — bigger.
095 + 5 = 100°(M)

4. Compass. Deviation 1°West, same direction again.
100 + 1 = 101°(C)

5. Time. 50 ÷ 169.4 × 60 = 17.7 → 18 min

159 kt · 095(T) · 100(M) · 101(C) · 169 kt · 18 min

Method 2 — the CX-3
two menus, and the second one keeps the answer
  1. FLT → Airspeed → Planned TAS. Enter CAS 160, OAT −10, PAlt 2000. Read TAS.
  2. PLAN → open leg 1.
  3. TCrs 100 · TAS from step 1 · WDir 330 · WSpd 17.
  4. Var — 5° West, and west is positive on this machine, so enter 5, no sign key.
  5. Dev — 1° West, same again: 1.
  6. Dist 50, and Rate if you want the fuel.
  7. Read GS, CHdg and ETE straight off the leg.

CHdg 101 · GS 169 · ETE 18 min

Look at what the machine did there. Method 1 needed four separate calculations and two sign decisions. The PLAN leg took the same inputs and returned the compass heading directly — variation and deviation already inside it. That is the first time in this module the electronic computer has saved you real work rather than just time, and it is why this chapter exists.

Sanity check. The wind is from 330 on a track of 100 — behind your left shoulder. Behind, so ground speed beats TAS: 169 against 159, yes. On the left, so it drifts you right and you aim left: 095 is left of 100, yes. Both variation and deviation are west, so both headings climb: 095 → 100 → 101, yes.
If your compass heading had come out lower than your true heading with two westerly corrections, you applied them backwards.

4 · The PLAN menu — where it stops being a calculator

One leg is a fair fight between the formula and the machine. Seven legs is not.

A stylised route across a chart broken into numbered legs between turning points, each
       leg carrying its own short data strip, with a summary panel at the end of the route.
Figure 8.12 — A trip is legs, and legs share almost everything. The aircraft does not change TAS between turning points; the variation barely moves; the fuel flow is a property of the engine, not of the leg. The machine knows this.
Global values — the feature that does the actual work

Four of the PLAN inputs are marked with a blue circle icon: TAS, Var, Dev and Rate. A blue circle means this value repeats across every leg. Enter it once and every leg has it.

So a seven-leg plan is not seven times the work. It is one aircraft set-up, then seven pairs of numbers — track and distance — and a wind for each.

Per-leg inputs are Dist, TCrs, TAS, WDir, WSpd, Var, Dev, Rate, Dep; per-leg outputs are GS, CHdg, ETE, Fuel. The Total Trip line returns total Dist, ETE, ETA and Fuel.

Total Trip — the number nobody calculates by hand twice

At the foot of the plan the machine totals the distance, the elapsed time, the fuel, and — given a departure time — the ETA.

Add a leg, change a wind, or accept a re-route, and every one of those totals moves on its own. Doing that by hand means re-adding four columns and it is exactly where a tired pilot makes an arithmetic error at one in the morning.

Set the departure in UTC and read the ETA in UTC. Mixing local and UTC inside one flight plan is a classic and expensive mistake, and the machine will not catch it for you — it has no idea which one you typed.

Set the aircraft up once, before the first leg

Under SET the CX-3 carries an Aircraft Profile. Put your TAS and your fuel flow in it and they are waiting for you every time.

The same menu carries K, the instrument calibration factor used to convert OAT to TAT and back, defaulting to 1.0. That is the electronic replacement for the E6B's blue scale, and unless your operator tells you otherwise, 1.0 is what you leave it at.

And the housekeeping one: clear the memory before an examination. The requirement is written into the Guide for FAA knowledge exams. Whether DGCA imposes the same is not something I can show you in writing, so treat clearing it as good practice rather than as a rule I have proved.


5 · Wind finding — the third job

Back to the table at the start of Chapter 8A. Row one was finding track. Row two was finding heading. Row three is finding the wind, and it is the only one where the answer is something nobody gave you.

Why bother, when the forecast is right there

A forecast wind covers a large area and is valid for several hours. It is an average of a region over a period, and it was written before you took off.

The wind you find in flight is the wind at your level, in your part of the sky, over the last twenty minutes. It is more recent and more local than anything you were handed on the ground, and every remaining leg of your plan is better for having it.

The situation

You are heading 060°(T) at a TAS of 140 knots, flying some planned track.

A single air vector drawn from an origin, pointing north east, with no wind and no
       ground vector yet — the only thing known at the start of the problem.
Figure 8.13 — This is all you have at the start: one vector, whose direction is your heading and whose length is your TAS. Everything else has to come from looking out of the window.
heading 060°(T), TAS 140 kt

You pass a known landmark at A. Twenty minutes later you get a fix at B. On the chart you measure the line from A to B: it runs 065°(T) and it is 40 nautical miles long.

Forty miles in twenty minutes is 120 knots over the ground. And now you have four numbers, which is one more than you need:

  • Heading — 060°(T)
  • TAS — 140 kt
  • Track made good — 065°(T)
  • Ground speed — 120 kt
Two vectors from a common origin — a longer gold air vector and a shorter white ground
       vector lying a few degrees clockwise of it — with the gap between their tips still open.
Figure 8.14 — Two sides of the triangle, measured rather than forecast. The gap between the two arrowheads is the wind, and it has been there all along.
air vector — heading 060, 140 kt ground vector — track 065, 120 kt
The whole of wind finding, in one sentence

The wind is the vector that joins the tip of the air vector to the tip of the ground vector.

Nothing else. Draw where you were pointing, draw where you actually went, and the line closing the gap between the two arrowheads is the wind — pointing the way it blows, with a length equal to its speed.

The same two vectors with a cyan arrow now drawn from the tip of the air vector to the
       tip of the ground vector, completing the triangle.
Figure 8.15 — The triangle closes, and the closing side is the answer. Note where it starts and where it ends: from the air vector's tip, to the ground vector's tip. Draw it the other way round and you have the reciprocal, which is the single commonest error in this operation.
air vector — one arrowhead ground vector — two arrowheads the wind — three arrowheads, and it was the unknown

Worked example 8B.2. Heading 060°(T), TAS 140 kt, track made good 065°(T), ground speed 120 kt. Find the W/V.

Method 1 — the arithmetic
subtract one vector from the other

1. Break the air vector into east and north parts:
E = 140·sin060 = 121.24
N = 140·cos060 = 70.00

2. Same for the ground vector:
E = 120·sin065 = 108.76
N = 120·cos065 = 50.71

3. Subtract, ground minus air. This is the step whose order decides everything:
E = 108.76 − 121.24 = −12.48
N = 50.71 − 70.00 = −19.29

4. Wind speed is the hypotenuse:
√(12.48² + 19.29²) = 22.98

5. That vector points toward atan2(−12.48, −19.29) = 213°. A wind is named for where it comes from, so add 180.

W/V 033° / 23 kt

Method 2 — the CX-3
and this time the function name is honest
  1. FLT → Wind Correction.
  2. THdg 060 · TAS 140 · TCrs 065 · GS 120.
  3. Read WDir, WSpd and WCA.
  4. Four inputs, three outputs, no sign decisions and nothing to draw. This is the one wind job the CX-3 does better than you do.

W/V 033° / 23 kt

Now the trap from Chapter 8A, seen from the other side. The function called Wind Correction was the wrong tool for finding a heading. Here it is exactly right. Its name has always described what it takes, not what it gives you — and reading it that way makes the whole menu obvious.

Sanity check. You drifted from 060 to 065 — five degrees right — so the wind must be pushing from your left, somewhere north-westerly to northerly. 033 is north-north-east, which is on your left on a heading of 060. Yes.
And your ground speed dropped from 140 to 120, so it must have a head component. A wind from 033 against a heading of 060 is 27° off the nose. Yes.
If you had computed 213° instead, you would have subtracted the vectors the wrong way round — and 213 is exactly the reciprocal of 033, which is how that error always announces itself.

The completed triangle with the cyan wind vector detached and redrawn from the origin
       so its direction and length can be read directly against a bearing scale.
Figure 8.16 — On a rotating computer the wind vector is swung down to the six o'clock position before it is read. That step has no mathematics in it at all — it exists only so the number can be read accurately off a scale.
the wind, moved only to be measured
The finished triangle with all three vectors labelled and the wind vector emphasised,
       drawn cleanly and at rest.
Figure 8.17 — W/V 033/23. This is the wind that has been acting on you for the last twenty minutes — not an area forecast, not an average, but the actual air you are flying in. Put it into the remaining legs of your plan.
heading 060 · 140 kt track 065 · 120 kt wind 033 · 23 kt
A one-degree difference you will meet in the answers

The arithmetic above gives 32.9°, which rounds to 033. The published answer for this example is 034 — read off a rotating disc to the nearest degree.

Neither is wrong to any degree that matters here. But when you are choosing between exam options that sit a degree or two apart, trust the arithmetic. It is exact and it is reproducible, and the next section explains when even the arithmetic cannot help you.


6 · When the wind direction barely means anything

Here is something the source book does not tell you, and it will save you an argument with an answer key one day.

The wind is the small difference between two large vectors. When the wind is light and the aeroplane is fast, that difference is a short line joining the tips of two long ones — and the direction of a short line between two long ones is extremely sensitive to any error in either.

The rough size of it, and it is an upper bound not a law

Get your measured track wrong by one degree, and the wind direction you compute can move by up to roughly

TAS ÷ wind speed degrees.

Often it moves much less — it depends on the geometry — but that ratio is the worst case and it is worth carrying in your head.

A worked instance from the question set below. Row 29: heading 274, track 275, TAS 290, GS 270. The wind works out at about 21 knots, so TAS ÷ W is roughly 14. And measured directly: one degree of track error swings the computed wind direction by 13.2°.

And the opposite extreme. Row 37: TAS 460, GS 505, and a wind of about 149 knots. TAS ÷ W is 3, and the measured swing is 1.5°. A big wind pins its own direction down.

What to do with this, practically

Trust a found wind's SPEED more than its DIRECTION when the wind is light relative to your TAS. The speed comes out of a length, which is robust; the direction comes out of an angle between two nearly-parallel lines, which is not.

Do not chase a few degrees. If your answer and the key differ by three or four degrees on a light wind at high speed, neither of you is wrong — the data does not contain the answer to that precision.

Fly for longer before you fix. The fix at B is what sets your track accuracy. Twenty minutes gives a better wind than five, because the same half-mile of fix error is a smaller angle over a longer line. This is the practical reason wind finding is done over a decent run and not opportunistically.


Questions — the flight plans

How to work these, and it is not optional advice

Work across the rows. One row at a time, left to right, finishing each before you start the next.

Doing it column by column — all the TAS values, then all the headings — is faster and it is worthless. It turns the exercise into typing, and it hides the one thing being trained: holding a five-step chain in your head without dropping a link.

The blank cells are TAS, HDG(T), HDG(M), HDG(C), GS and Time. Everything else is given.

Flight Plan 1

#PA
ft
OAT
°C
CASTASTrack
°(T)
W/VHDG
°(T)
VarHDG
°(M)
DevHDG
°(C)
GSDist
NM
Time
min
12000-10160100330/175°W1°W50
24700-2170227300/103°E2°E112
34000-10175134262/173°W1°E30
42000+2170157110/126°W2°W38.5
56000-3154100320/184°E1°W60
65000-15150050110/458°W2°E13
710000-8173320181/273°E3°W44

Flight Plan 2

#PA
ft
OAT
°C
CASTASTrack
°(T)
W/VHDG
°(T)
VarHDG
°(M)
DevHDG
°(C)
GSDist
NM
Time
min
15000+5170070230/255°W1°E86
26500-2170234210/303°W2°E71
36000+2174240210/224°W1°E57
47500+2175166110/306°W3°E89
58000-2174190245/364°E1°W60
69000-5180050110/4511°W2°E13
712000-11184324190/473°E2°E50

Flight Plan 3

Sixteen legs, and the altitudes climb. Watch legs 9 and 10 — there is a reason they are up there, and it is explained in the answers.

#PA
ft
OAT
°C
CASTASTrack
°(T)
W/VHDG
°(T)
VarHDG
°(M)
DevHDG
°(C)
GSDist
NM
Time
min
13000+15190315045/337°W2°E88
29000-10205324335/216°E1°W105
314000+5142071030/5511°W1°W80
44000-10132300190/258°E3°E332
53500-17130019300/289°W2°E110
67500+0160342130/403°E1°W92
79500+0180262010/3834°E2°W145
87000+15159021265/3216°W4°W112
922500-30202033310/507°W2°E46
1028000-55194162210/2014°W3°E1312
112000+4148228280/2010°W2°E84
123000+16123351060/3012°W2°W95
135000-5166043123/469°E1°W62
142500+0123032120/304°E1°E49
153500+896162140/409°W1°W130
164000-5111343220/3011°E1°W82

Questions — wind finding

What you are given, and what you are finding

Each row gives you a heading, a TAS, the track you actually made good and your ground speed. One column is blank: the W/V.

All directions are degrees TRUE. Remember the direction of the subtraction — ground vector minus air vector — and remember that a wind is named for where it comes from, so the answer is the reciprocal of the vector you just computed.

#HDG°(T)W/VTrack made good°(T)TASGS
1209219150134
2270266180202
3223224206246
4069079138124
5299293125120
6167162202190
72132318580
8014005200218
93303489090
10179168196226
11098100310338
12091080440435
13050055398415
14351340393405
15288292434462
16276281335316
17280275430435
18291292330360
19097095343322
#HDG°(T)W/VTrack made good°(T)TASGS
20056055287320
21108109480530
22176171428438
23270265335308
24248243406332
25247252380352
26200202435403
27198202340325
28275275435395
29274275290270
30321326338280
31045061285305
32196205210245
33311295482435
34011358198211
35355008248270
36111115120114
37228245460505
38175168121114

Answers — the flight plans

Flight Plan 1

#PA
ft
OAT
°C
CASTASTrack
°(T)
W/VHDG
°(T)
VarHDG
°(M)
DevHDG
°(C)
GSDist
NM
Time
min
12000-10160158100330/170955°W1001°W1011695018
24700-2170180227300/102303°E2272°E22517611238
34000-10175180134262/171383°W1411°E140190309
42000+2170172157110/121546°W1602°W16216438.514
56000-3154166100320/180964°E0921°W0931806020
65000-15150155050110/450658°W0732°E071128136
710000-8173199320181/273153°E3123°W3152194412

Flight Plan 2

#PA
ft
OAT
°C
CASTASTrack
°(T)
W/VHDG
°(T)
VarHDG
°(M)
DevHDG
°(C)
GSDist
NM
Time
min
15000+5170183070230/250735°W0781°E0772068625
26500-2170186234210/302303°W2332°E2311587127
36000+2174190240210/222374°W2411°E2401705720
47500+2175196166110/301596°W1653°E1621788930
58000-2174195190245/361994°E1951°W1961726021
69000-5180205050110/4506111°W0722°E070178134
712000-11184219324190/473153°E3122°E3102495012
CORRECTED — Flight Plan 2, leg 5. The published answer is wrong.

The leg: PA 8000 ft, OAT −2°C, CAS 174, track 190°(T), W/V 245/36, variation 4°E, deviation 1°W, distance 60 NM.

The TAS is not the problem. It works out at 195 by the compressible relation and 196 by the simple one, and the published 196 is perfectly defensible. Use either value and the heading still comes out at 199°(T) and the ground speed at 172–173 knots. The published heading and ground speed are wrong on their own terms, whichever TAS you feed them.

PublishedCorrect
HDG°(T)196199
HDG°(M)192195
HDG°(C)193196
GS180172
Time2021

How I know it is wrong rather than merely different. Take the published heading of 196°(T), fly it at TAS 196 in a wind of 245/36, and the track you make good is 187° — not the 190° the question requires. The published answer does not solve its own question.

Its ground speed fails the same test: with this wind, no heading that achieves a track of 190° produces 180 knots. The correct pair is 199°(T) and 172 knots, and those do reproduce track 190 exactly.

What it looks like it was. The row prints TAS 196 and HDG(T) 196 — the same number twice, in adjacent columns. The magnetic heading, the compass heading and the time are then all derived correctly from that wrong heading and that wrong ground speed: 196 − 4°E gives 192, 192 + 1°W gives 193, and 60 NM at 180 knots gives 20 minutes. Every one of those steps is right. That is the signature of a copied cell rather than an arithmetic mistake, and it is why the error survived proofreading: every check you could run within the row passes.

Flight Plan 3

#PA
ft
OAT
°C
CASTASTrack
°(T)
W/VHDG
°(T)
VarHDG
°(M)
DevHDG
°(C)
GSDist
NM
Time
min
13000+15190200315045/333247°W3312°E3291988827
29000-10205231324335/213256°E3191°W32021010530
314000+5142181071030/5506011°W0711°W0721368035
44000-10132136300190/252908°E2823°E279142332140
53500-17130131019300/280079°W0162°E01412211054
67500+0160179342130/403493°E3461°W3472119226
79500+0180208262010/3827234°E2382°W24021714540
87000+15159181021265/3201216°W0284°W03219211235
922500-30202284033310/500237°W0302°E0282744610
1028000-55194290162210/2016514°W1793°E1762761312285
112000+4148150228280/2023410°W2442°E2421378437
123000+16123130351060/3000312°W0152°W0171169549
135000-5166175043123/460589°E0491°W0501616223
142500+0123125032120/300464°E0421°E0411214924
153500+896101162140/401539°W1621°W16363130124
164000-5111115343220/3033011°E3191°W3201298238
Legs 9 and 10 — and an error of mine, not the book's

Leg 9 is 22,500 ft at −30°C, CAS 202. Leg 10 is 28,000 ft at −55°C, CAS 194. Everywhere else in these plans the simple density-ratio formula — TAS = CAS ÷ √σ — reproduces the published TAS to within a knot.

On these two it does not. It gives 289 and 296 against the published 284 and 291 — about five knots high on both. My first reaction was that the book was wrong. It is not. I was.

Those two legs run at Mach 0.47 and Mach 0.50. The simple formula ignores compressibility, and above roughly Mach 0.45 that is no longer a rounding error. Work them through the compressible relation instead — dynamic pressure to Mach number to true airspeed — and you get 284.1 and 290.0. The book is right to a knot.

This is Chapter 6 arriving in the middle of a flight plan, which is exactly why it was taught there. Every other leg in these three plans is below Mach 0.37, and there the two methods agree to within about a knot, which is the other half of the lesson: the correction is real, and it is only real where it is real.

The CX-3 handles this internally. Its Airspeed function solves the compressible relation and there is no separate correction step to apply — the words "compressibility" and "EAS" do not appear anywhere in its 24-page Guide, because on that machine there is nothing for you to do.


Answers — wind finding

#HDG°(T)W/VTrack made good°(T)TASGS
1209157/29219150134
2270057/26266180202
3223049/40224206246
4069015/27079138124
5299005/14293125120
6167219/21162202190
7213143/262318580
8014128/37005200218
9330249/283489090
10179300/50168196226
11098301/30100310338
12091172/84080440435
13050297/39055398415
14351084/77340393405
15288158/42292434462
16276222/34281335316
17280015/38275430435
18291123/31292330360
19097125/24095343322
#HDG°(T)W/VTrack made good°(T)TASGS
20056226/33055287320
21108298/51109480530
22176278/39171428438
23270314/39265335308
24248269/81243406332
25247201/42252380352
26200176/35202435403
27198143/28202340325
28275275/40275435395
29274261/21275290270
30321299/64326338280
31045309/84061285305
32196066/50205210245
33311013/136295482435
34011110/48358198211
35355251/63008248270
36111059/10115120114
37228129/149245460505
38175236/16168121114
CORRECTED — wind finding, row 35. One mistyped digit.

The row: heading 355°(T), TAS 248, track made good 008°(T), GS 270. Published answer 262/62. It should be 251/63 — and the book almost certainly meant to print 252.

The test that settles it. Take the published wind of 262/62 and fly it from the row's own heading of 355 at its own TAS of 248. You get a ground speed of 259 knots. The row states 270. The published answer is eleven knots away from reproducing its own question.

Change the 6 to a 5 — 252/62 — and it gives track 008 and ground speed 269. That is a single transposed digit, and it lands the row back inside normal reading tolerance.

Note what this is not. Two other rows in this set — 26 and 29 — differ from my arithmetic by more than four degrees of wind direction, and neither is an error. They are the ill-conditioning of Section 6: fly their published winds forward from their own headings and they reproduce their own tracks and ground speeds. Row 29 in particular swings 13° of wind direction for one degree of track, which is exactly the case that section was written about. Row 35 is the only row in the set whose published answer fails its own data.

What I checked across this chapter, and what I did not

All 30 flight plan legs and all 38 wind finding rows were recomputed from first principles — compressible airspeed, full vector triangle, signed variation and deviation, and time from distance and ground speed.

Flight plans: 28 of 30 legs reproduce. Headings within a degree, ground speeds within two knots, times within half a minute.

Two legs fall outside that, and they are different in kind. Flight Plan 2 leg 5 is corrected above — it is a genuine error in the source. Flight Plan 3 leg 10 is not an error; it is the compressibility correction arriving in the totals. At Mach 0.50 the compressible TAS is 290 against the published 291, which carries about 3 knots into the ground speed and, over 1,312 nautical miles, four minutes into the elapsed time. Both are defensible — they come from different airspeed methods, and this is the one leg long enough and fast enough for that choice to become visible in the time column.

Wind finding: 35 of 38 rows agree to within four degrees of direction and four knots of speed. Of the three that do not, rows 26 and 29 are not errors — their published winds fly forward and reproduce their own tracks and ground speeds, and the disagreement is the ill-conditioning of Section 6. Row 35 is a genuine source error, corrected above.

What I could not settle. Whether the residual one- and two-knot differences are reading error or typesetting. They are consistent with reading an analogue scale and none of them changes an exam answer, but I have not proved the cause — only that they do not matter.


The chapter in seven lines

Take these into the exam
  1. A flight plan row is five conversions in a chain — CAS to TAS, track to heading, true to magnetic, magnetic to compass, distance to time. Work across the row, never down the column.
  2. Variation west, magnetic best. Variation east, magnetic least. Deviation behaves identically, one step further on.
  3. The CX-3's sign convention is the opposite of the book's. On the machine, + is WEST. Say the word "west" or "east" out loud before you press anything.
  4. The wind is the vector from the air vector's tip to the ground vector's tip. That order, always. Reverse it and you get the exact reciprocal, which is how the error announces itself.
  5. Wind finding is FLT → Wind Correction. Heading and ground speed is PLAN. The names describe what each function takes, not what it gives.
  6. A light wind at high speed has a badly determined direction — up to about TAS ÷ W degrees of swing per degree of track error. Trust its speed more than its direction, and do not argue over three degrees.
  7. Above about Mach 0.45 the simple TAS formula runs high. Two legs in these exercises prove it. Below that, it is exact enough for anything.

Next — Chapter 9: multi-drift winds, where three drift readings on three headings pin down a wind that no single run can; and wind components, which carry the most operationally dangerous trap in this whole module — the CX-3's crosswind function demands a runway number and a magnetic wind, and the forecast in your hand is in true.

Capt. Pankaj Pahil · www.GhostAviator.com
Study Navigation with other student pilots
Join the free Navigation group on Telegram. Stuck on a doubt? Type /q and your question, and get an answer from Ghost Aviator's notes.
Join the Navigation group →
LIVE BATCH
Study General Navigation live with the Captain
Small batch of 10 · live doubt-clearing · 4–6 weeks · ₹12,999 ₹7,999

Reinforce Chapter 30: CX-3: Wind Finding and Flight Planning

Test your knowledge and practice actual exam questions for Air Navigation.

Planning your Pilot Training in 2026?
Calculate exact flying hours, DGCA exam fees, and living costs with our interactive calculator.
CPL Cost Calculator →