Why wind shear needs precise language
This article is TELCAP speaking material, not a replacement for aircraft procedures, airport warnings or a pilot's operating manual. Wind shear and microbursts are useful assessment subjects because they combine weather, aircraft performance, decision-making and rapid communication.
Wind shear is a rapid change in wind direction or speed over a short distance. It can occur at many altitudes, but it is particularly hazardous close to the ground during take-off and approach. A microburst is a concentrated downdraft that reaches the surface and spreads outward. An aircraft may first encounter increasing headwind, then a downdraft and later a tailwind. The sequence can rapidly reduce performance when altitude is limited.
Candidates should explain the risk in simple operational language. The goal is not to recite meteorology. It is to show that a crew recognises a hazard, follows approved escape guidance and tells ATC what it needs.
Information before the approach
The crew builds a weather picture from reports, forecasts, radar, airport observations, ATIS, controller reports and information from other aircraft. A thunderstorm near the airport, rapidly changing wind, heavy precipitation or reports of airspeed loss all deserve attention. No single source gives a complete picture.
Airport systems can detect low-level wind shear and microbursts. A controller may issue a wind-shear alert with location, altitude and wind change. The crew should listen to the wording, compare it with its route and decide under the operator's procedures. A warning does not guarantee that every runway or every approach is unsafe, but it is never routine information.
Conditions can change faster than a briefing. A report from an aircraft that landed ten minutes ago may no longer describe the current situation. This is why crews update their plan, retain fuel alternatives and avoid becoming committed to one approach only because it was briefed earlier.
Recognition during flight
Recognition may come from a predictive or reactive warning system, visual weather cues, an unexpected change in ground speed, airspeed trend, vertical speed or flight path. The exact indications and response depend on aircraft type. Pilots should use manufacturer guidance rather than inventing a technique from memory.
The danger is expectation bias. A crew that expects a normal approach may explain away unusual indications as turbulence or instrument error. Cross-checking between pilots and calling out unexpected energy changes can break this pattern. If safety margins are reducing, a prompt go-around is often a stronger decision than continuing to see whether conditions improve.
An aircraft should not attempt to fly through a hazardous event simply because another aircraft reported a smooth approach. Aircraft differ in weight, speed, path and time of arrival. Weather cells also move and develop.
Take-off, approach and go-around
During take-off, the aircraft has little time and altitude. Before the decision speed, a rejected take-off may be considered only under the approved procedures. After that point, the crew follows the aircraft-specific escape or wind-shear guidance. The operational lesson is to fly the aircraft first, use prescribed thrust and attitude guidance, and delay non-essential communication until workload permits.
On approach, an early decision preserves options. If a significant warning is received before the final segment, the crew can hold, divert, choose another runway or wait for conditions to improve. A go-around is not a failed landing; it is a normal safety manoeuvre when the approach is unstable or conditions become unacceptable.
After an encounter, the crew reports what happened as soon as it is safe. The report may help the controller warn following traffic. It should include runway or location, altitude, type of event and significant effect. “Severe wind shear on final, go-around, passing one thousand feet” is more useful than “weather was bad.”
How ATC supports the crew
ATC provides weather information, spacing, runway changes and coordination. Controllers can pass reports from other aircraft and issue wind-shear alerts generated by airport systems. They cannot see the same cockpit displays or determine whether a particular aircraft can safely continue.
When a crew reports a go-around or requests a deviation, the controller needs the aircraft's present situation and intention. If the crew needs to fly a published missed approach before accepting a new clearance, it should state that. If it needs time to assess weather, it should request vectors, holding or an alternative route.
Traffic pressure must not force a rushed decision. Controllers can protect airspace, but the pilot in command decides whether the conditions are acceptable. Clear, short reports help both sides preserve margins.
Planning diversion and recovery
Repeated wind-shear warnings can affect fuel, alternate choice and crew workload. A diversion decision considers current weather, forecast trend, runway orientation, available approaches, fuel, terrain and services. The airport with the shortest flight time may have the same weather system; another airport may offer a wider safety margin.
After landing, the crew records the event under company procedures. A timely report may improve forecasts, airport alerting and training. It should state observed conditions, aircraft response and any warning received without exaggeration.
For a TELCAP answer, organise the story: weather evidence, hazard recognition, immediate response, ATC coordination and subsequent decision. This sequence is clearer than listing every weather term known to the candidate.
Common speaking weaknesses
One mistake is confusing wind shear with any turbulence. Turbulence is irregular air movement; wind shear is a rapid wind change that can produce a sudden performance problem. Another is claiming that weather radar detects every microburst. Detection systems have limits, and a safe answer acknowledges uncertainty.
Candidates also sometimes say they would “land quickly before it gets worse.” This ignores the main risk: the hazardous condition may already be affecting the approach. Better language is: “We would follow the aircraft procedure, discontinue an unstable approach and reassess the safest option.”
Practice asking and answering follow-up questions: What was the reported wind change? Which runway was affected? Is there enough fuel to hold? Would you accept another runway? Such interaction tests comprehension as well as vocabulary.
Key vocabulary
- wind shear — rapid change in wind speed or direction over a short distance
- microburst — concentrated downdraft that spreads outward after reaching the surface
- low-level — close to the ground, especially in terminal operations
- predictive warning — alert based on conditions detected ahead of the aircraft
- reactive warning — alert based on conditions the aircraft is already experiencing
- go-around — discontinued landing approach followed by a climb
- missed approach — published or assigned procedure after an unsuccessful approach
- energy state — relationship between speed, altitude and aircraft performance
- weather trend — expected direction of weather change over time
- safety margin — reserve that keeps an operation away from unsafe limits
Discussion questions
- Why is wind shear more dangerous close to the ground?
- Which sources help a crew build its weather picture?
- What should a useful pilot report after a wind-shear encounter include?
- Why can another aircraft's smooth landing be misleading?
- How can ATC help without deciding whether an approach is safe?
- When should a crew consider holding or diverting instead of repeating an approach?