Quick summary
Under federal aviation rules, the pilot-in-command retains final responsibility for wake turbulence separation even after air traffic control applies mandatory minimum spacing.
But no current FAA guidance gives pilots a concrete, instrument-based method to confirm that spacing is actually safe. The fallback is visual judgment, course adjustments, and requests to ATC for more information. That gap between legal duty and practical verification tool is real, and it applies unevenly across aircraft types.
Ask most pilots who’s responsible for keeping their aircraft clear of wake turbulence, and they’ll point to the controller who just assigned them a standard spacing interval behind a heavy jet. Ask an FAA inspector the same question, and the answer changes.
The legal duty is unambiguous. Under the FAA’s pilot-in-command authority rule, the pilot-in-command is the final authority for the safe operation of the aircraft — full stop, no carve-out for wake turbulence, no transfer of that duty to a radar scope in a tower somewhere. Once a pilot accepts an ATC instruction to follow another aircraft, that acceptance functions as an acknowledgment: the pilot has agreed to take on wake separation as part of the deal.
What’s less discussed is what that acknowledgment actually asks a pilot to do. Controllers apply mandatory minimum distances tied to weight class. Pilots retain the final word on safety.
Somewhere between those two facts sits a question nobody in the regulatory chain answers cleanly: confirm it how?
What ATC actually guarantees — and what it doesn’t
Air traffic control’s job under both IFR and radar-sequenced VFR procedures is to apply minimum mandatory wake-separation distances between aircraft, keyed to weight class — originally Super, Heavy, Large, and Small. That system has moved on from a simple four-tier weight chart.
The FAA and NASA now describe a recategorization framework, or RECAT, that expands the old weight buckets into a six-category system, labeled A through F, applied to both departures and arrivals — a distinction confirmed in Federal Aviation Administration (FAA) order material. The U.S. rollout began at Memphis in November 2012, according to Skybrary’s implementation history, with the European version, RECAT-EU, arriving first at Paris Charles de Gaulle in 2016.
None of that changes the basic arrangement, though. The controller’s minimum is a floor, not a certification that a specific encounter won’t happen. It assumes standard conditions — average wind, average performance, average everything.
Real flights aren’t average. That’s precisely the gap the pilot-in-command is legally on the hook for closing, even though the controller did their job exactly right.
How a pilot is actually supposed to confirm wake separation
Here’s the practical question that current FAA guidance answers only partially: given ATC’s spacing, what does a pilot actually do in the cockpit to confirm it’s safe?
The closest operative document, AC 90-23G, hosted by Skybrary, frames the task as avoidance rather than measurement: picture where the vortices are, adjust the flight path to stay above or upwind of the traffic ahead or wait, and, if the picture looks wrong, ask ATC how far apart the aircraft are, what the lead aircraft’s groundspeed is, and at what altitude it’s flying. That circular has since been cancelled and replaced by AC 90-23H. The substance carried forward largely unchanged: visual judgment, avoidance maneuvers, and a phone call to the controller if something feels wrong.
What’s missing is any cockpit calculation or instrument reading that proves the spacing is actually adequate. There’s no wake-safety gauge. There’s no threshold number a pilot can check against a display and get a green light.
The guidance is advisory, built around avoidance behavior, not verification.
On a visual approach specifically, a pilot does hold one concrete lever: the authority to ask controllers for the groundspeed and separation of any heavier aircraft ahead. That’s real, and it matters. It’s also a request for information, not a measurement a pilot performs independently.
Flight deals
most people never see
Our AI monitors 150+ airlines for pricing anomalies that traditional search engines miss. Air Traveler Club members save $650 per trip per person on average: see how it works.
Each deal saves 40–80% vs. regular fares:
Confirmation looks completely different depending on what you’re flying
This is where the regulation’s uniformity breaks down against cockpit reality. The same pilot-in-command duty applies to a student pilot in a light piston trainer and a captain flying a widebody into a major international airport. Their tools for meeting it aren’t remotely the same.
| Aircraft class | Traffic display available | Wake-specific detection or alerting | Realistic in-cockpit confirmation method |
|---|---|---|---|
| Light GA piston | Often none unless equipped with aftermarket traffic display equipment; FAA guidance assumes visual scanning and operational judgment | No standard wake-specific detector in routine GA operation | Visually estimate spacing, stay above or upwind of the lead aircraft’s path, and request more separation if needed |
| Turboprop or light jet | Commonly available on equipped aircraft, but not universal | No routine certified wake-specific alerting system identified in FAA guidance | Use traffic display plus visual separation and ATC spacing updates; treat it as a procedural judgment, not a measured wake proof |
| Regional jet | Common in modern avionics suites | No operationally standard wake-specific detection or cockpit alerting system identified | Confirm by ATC spacing, own visual acquisition, and runway/approach geometry; no dedicated wake verifier is documented |
| Narrowbody | Integrated traffic awareness is common on airline aircraft | No certified production wake-specific detection system identified in the retrieved FAA/NASA material | Use ATC spacing, visual cues, aircraft performance margins, and operational procedure; the cockpit still lacks a direct wake-safety sensor |
| Widebody or heavy | Typical in transport-category cockpits | No certified production wake-specific detection system identified in the retrieved material | Cross-check ATC spacing, flight-path geometry, and lead-aircraft position; the available guidance remains procedural rather than instrument-based |
The pattern across every row is the same absence. A widebody crew has a richer traffic display and more time to process what’s ahead.
Neither one gets a wake-specific sensor. The duty is identical; the equipment gap between a piston single and a heavy transport aircraft is enormous, and the regulation doesn’t acknowledge that difference at all.
The mechanism nobody built — and why the research never left the lab
NASA actually tried to close this gap.
Under its AVOSS program, researchers fed weather data and wake-sensor readings into prediction software, then ran a Dallas/Fort Worth test that combined a ground-based vortex sensor with continuous-wave and pulsed lidar. Later work went further, testing pulsed coherent lidar and an onboard study that tracked live wake movement while flying in formation.
None of it became a certified production system a working airline crew can switch on today. These were research prototypes, and the documentation is explicit about that limit. So the regulatory duty to confirm safe separation stands exactly where it stood decades ago — resting on eyesight, judgment, and a radio call, not on measurement.
That’s why American Airlines Flight 587 keeps surfacing in this conversation, even though it doesn’t resolve the accountability question cleanly. The jet, accelerating through about 255 knots during initial climb, flew into the wake vortices of a Japan Air Lines 747 that had just departed. But the NTSB‘s probable cause centered on the first officer’s rudder movements, which investigators found were unnecessary and excessive — not on a spacing failure.
The wake encounter happened. The finding that followed it was about what the crew did next, not what the separation minimum failed to prevent.
What this means for you
FAA wake guidance does get more specific by phase of flight, even without a measurement tool behind it. Depending on aircraft class, the advice covers where to lift off and where to touch down: get airborne before the aircraft ahead does, stay above the larger aircraft’s final approach path, note exactly where that aircraft’s wheels touched, and aim to land beyond that point.
None of that is a proof of safety. It’s tailored avoidance behavior, and it’s the most concrete thing current guidance offers.
