Two Killed After Boeing 757 Wake Turbulence Causes Bonanza Crash

Advertisement
Timeline
Event 1 —
The Bonanza was sequenced into the traffic pattern at Reno-Tahoe behind Boeing 757 traffic.
1.
Event 2 —
Two FedEx 757s were operating on the parallel runway.
2.
Event 3 —
The Bonanza was cleared to land while remaining exposed to the wake-turbulence environment.
3.
Event 4 —
The light aircraft encountered the 757 wake vortices during the approach.
4.
Event 5 —
The Bonanza rolled sharply at low altitude and lost controlled flight.
5.
Event 6 —
The aircraft crashed and both occupants were killed.
6.

The Flight

On the afternoon of 30 August 2016, a Beechcraft Bonanza was sequenced into the traffic pattern at Reno-Tahoe International Airport behind Boeing 757 traffic. Two FedEx 757s were operating on the parallel runway. The Bonanza pilot was cleared to land on a runway whose approach path was vulnerable to wake turbulence translating across from the heavier jets. Moments later the light airplane encountered the wake vortices, rolled inverted or nearly so at low altitude, and crashed. Both occupants were killed.

Wake turbulence from a Boeing 757 has long been recognized as particularly hazardous to light aircraft. The vortices generated by the 757’s wingtip can remain strong enough to roll a small airplane long after the jet has passed. Separation standards exist precisely to prevent this scenario, yet the geometry of parallel runway operations, pilot identification of traffic, and controller instructions can still place a light airplane in the path of the invisible rotating air.

What Went Wrong

Investigation showed that the Bonanza pilot had been instructed regarding the 757 traffic and had reported the airliner in sight. However, the geometry of the approach and the presence of two sequential 757s created ambiguity about which aircraft the pilot was actually looking at. The controller’s instructions and the pilot’s subsequent path placed the Bonanza close enough to the wake that recovery at the altitude available became impossible. Post-accident modeling confirmed that the flight path intersected the residual vortices from one of the 757s just prior to impact.

The NTSB examined both the pilot’s decision-making and the air traffic control handling. Parallel runway operations with less than 2,500 feet of separation are treated, for wake purposes, as a single runway in some guidance. Additional separation is required when a small airplane follows a 757. Those margins were not maintained in this instance.

NTSB Probable Cause

The National Transportation Safety Board determined that the accident resulted from the pilot’s selection of a landing runway susceptible to high crosswinds and the translation of wake turbulence across its approach path, together with the failure of both the controller and the pilot to ensure adequate separation from the B757 and its wake. The low-altitude encounter with the vortices left the pilot unable to recover.

Accident Facts

Accident
WPR16FA172
Date
August 30, 2016
Location
Reno-Tahoe International Airport, Nevada
Aircraft
Beechcraft Bonanza
Preceding traffic
Boeing 757 (FedEx)
Operation
Part 91 personal flight
Defining event
Wake turbulence encounter / loss of control
Fatalities
2

Primary Source / Investigation Record

Investigation reference: WPR16FA172

Closing Reflection

Wake turbulence remains one of the most unforgiving hazards for light aircraft operating near heavy jets. The vortices are invisible, they drift with the wind, and they can retain lethal energy for minutes. Pilots must treat every 757, and every heavy, as a potential trap and must be prepared to refuse a clearance or request additional spacing when the geometry looks marginal. Controllers share the responsibility to protect the smaller airplane. When either party relaxes the margin, the result can be catastrophic within seconds of the encounter. This accident is a reminder that “I have the traffic in sight” is not always enough.

Sources

Audio from the original air traffic control recording, sourced from public recordings and released investigation records. The reconstruction, animation and written account are our own.
Advertisement

Primary Investigation Reference

NTSB accident number: WPR16FA172

The weekly incident