Your Pilot InterviewATPL EASA

The forward wind triangle

Find a heading and groundspeed that actually produce the required track.

Why does pointing at the destination not hold the track?

The wind carries the air mass while the aircraft moves within it.

Reverse wind-from before adding vectors

Wind is reported as the direction it comes from; its velocity points toward the reciprocal. In east/north coordinates, an air vector is (TAS sin H, TAS cos H), while wind from D at speed W is (−W sin D, −W cos D). Their sum is ground velocity. All angles must use the same north reference.

For required track 000°, TAS 120 kt and wind from 090° at 30 kt, the aircraft needs a 30 kt eastward air component to cancel the westward wind. WCA = asin(30/120) = +14.48°, so heading is 014.48°. The remaining northward airspeed and GS are √(120² − 30²) = 116.19 kt. Heading 000° would drift west.

Solve cross-track before along-track motion

Let δ be wind-from direction minus required track. The required WCA is asin[(W/TAS) sin δ]; heading equals track plus WCA, normalised. Along-track GS is TAS cos WCA − W cos δ. The crosswind equation needs |W sin δ| ≤ TAS, and the final GS must be positive to reach the next fix.

A real arcsine is not sufficient. A direct headwind stronger than TAS can leave WCA at zero while GS is negative. The laboratory explicitly rejects an unusable forward solution rather than clamping a physically impossible ratio into a plausible-looking heading.

Transfer the triangle to a different track

Retain TAS 120 kt and wind 090°/30 kt, then change desired track to 090°. The same wind is now a direct headwind: WCA is zero and GS is 90 kt. On track 270° it becomes a tailwind and GS is 150 kt. This explains why a wind has no universal headwind or crosswind component: its components depend on the desired track. Before reading a numeric answer, predict the crab direction and whether GS should rise or fall.

How can you test whether the wind solution is usable?

A numeric answer is valid only inside the physical domain.

Test lateral control and forward progress separately

At TAS 100 kt, desired track 000° and wind 090°/120 kt, the crosswind exceeds TAS. No possible air vector has enough eastward component to cancel the westward wind. The required sine magnitude is 1.2, outside its physical range. There is no real track-holding heading under the stated assumptions.

At TAS 100 kt and wind 000°/120 kt, the crosswind is zero, so an arcsine-only method returns WCA 0°. However, GS is 100 − 120 = −20 kt. The aircraft would move backward relative to the desired ground direction. A forward navigation solution requires both a possible lateral balance and positive along-track motion.

Recognise sensitivity near the boundary

For fixed crosswind, reducing TAS increases required crab and reduces the along-track air component. Near 90° WCA, small wind changes can produce very large changes in heading and GS. A barely positive GS may be a valid number but a poor planning margin, because a small wind underestimate changes the result materially.

Wind changes with height, time and position. The triangle gives an initial steady-state plan. After establishment, compare actual track and GS with the prediction and update from reliable observations. An airspeed increase or route change must also remain within aircraft and operational constraints.

Compare two near-limit cases

At TAS 100 kt with a pure 99 kt crosswind, the model gives WCA about 81.89° and only 14.11 kt along-track GS. Increasing crosswind by 1 kt reaches zero GS; increasing it further removes the solution. A display that rounded both winds to 100 kt could conceal this difference. Use the controls to identify the boundary and explain why blindly reporting a rounded 90° heading correction would be misleading. The domain check is part of the answer, not a cosmetic software guard.

Can you explain and apply the mechanism?

Four original questions. Work from the stated facts, then compare your reasoning with the explanation.

Your learning

Progress saved in this browser. Log in to sync across devices.

Learning overview