NTSB Cites Pilot Error In 2010 OSH Accident | Aero-News Network
Aero-News Network
RSS icon RSS feed
podcast icon MP3 podcast
Subscribe Aero-News e-mail Newsletter Subscribe

** AIRBORNE 05.24.13 Aero-TV-- CLICK HERE! ** HD iPad-Friendly Version -- AIRBORNE 05.24.13 **

** AIRBORNE 05.21.13 Aero-TV-- CLICK HERE! ** HD iPad-Friendly Version -- AIRBORNE 05.21.13 **

** AIRBORNE 04.01.13 SPECIAL EDITION of Aero-TV-- CLICK HERE! ** HD iPad-Friendly Version -- AIRBORNE 04.01.13 SPECIAL EDITION **

Tue, Jun 26, 2012

NTSB Cites Pilot Error In 2010 OSH Accident

Racing Team Owner Jack Roush Injured When His Beechjet Went Down On Approach

The NTSB has released its probable cause report for an accident which occurred at Wittman Regional Airport during AirVenture in 2010. The accident injured pilot and racing team owner Jack Roush (pictured in 2009 image), as well as a passenger in his airplane. Roush lost his left eye in the accident. The NTSB cites Roush's actions as pilot in command as the probable cause of the accident.

NTSB Identification: CEN10FA443
14 CFR Part 91: General Aviation
Accident occurred Tuesday, July 27, 2010 in Oshkosh, WI
Probable Cause Approval Date: 06/12/2012
Aircraft: Hawker Beechcraft 390, registration: N6JR
Injuries: 2 Serious.
 
The accident occurred during the EAA’s Airventure 2010 fly-in convention. Because of the high density of aircraft operations during the fly-in, the Federal Aviation Administration implemented special air traffic control procedures to accommodate traffic demand and maximize runway capacity. Arriving aircraft were issued landing instructions and clearances by a tower controller using a specified tower radio frequency. Departing aircraft were handled by another team of controllers operating on a separate radio frequency that was associated with a mobile operations unit located near the runway.
 
Air traffic control data indicated that the accident airplane established contact with the tower controller and entered a left traffic pattern for runway 18R. As the accident airplane was turning from downwind to base leg, the controller handling departures cleared a Piper Cub for an immediate takeoff and angled departure (a procedure used by slower aircraft to clear the runway immediately after liftoff by turning across the runway edge). The accident pilot was not monitoring the departure frequency, and, therefore, he did not hear the radio transmissions indicating that the departing Piper Cub was going to offset to the left of the runway after liftoff. The accident pilot reported that, while on base leg, he became concerned that his descent path to the runway would conflict with the Piper Cub that was on takeoff roll. He stated that he overshot the runway centerline during his turn from base to final, and, when he completed the turn, his airplane was offset to the right of the runway. The pilot stated that, at this point, he decided not to land because of a perceived conflict with the departing Piper Cub that was ahead and to the left of his position. The pilot reported that he initiated a go-around, increasing engine power slightly, but not to takeoff power, as he looked for additional traffic to avoid. He estimated that he advanced the throttle levers “probably a third of the way to the stop,” and, as he looked for traffic, the stall warning stick-shaker and stick-pusher systems activated almost simultaneously as the right wing stalled. The airplane subsequently collided with terrain in a nose down, right wing low attitude.

A post-accident review of available air traffic control communications, amateur video of the accident sequence, controller and witness statements, and position data recovered from the accident airplane indicated that the Piper Cub was already airborne, had turned left, and was clear of runway 18R when the accident airplane turned from base to final.
 
The post-accident examination did not reveal any preimpact mechanical malfunctions or failures that would have precluded normal operation of the airplane. The airplane flight manual states that, in the event of a go-around, the pilot should first advance engine thrust to takeoff power and then establish Vref (reference landing approach speed). The pilot’s decision not to select takeoff power during the go-around directly contributed to the development of the aerodynamic stall at a low altitude.
 
The National Transportation Safety Board determines the probable cause(s) of this accident as follows:
The pilot’s decision not to advance the engines to takeoff power during the go-around, as stipulated by the airplane flight manual, which resulted in an aerodynamic stall at a low altitude.

FMI: www.ntsb.gov

Advertisement

More News

ANN's Daily Aero-Linx (05.24.13)

Stormbirds A confederation of Luftwaffe-related web sites, providing reference-grade coverage of the Messerschmidt 262 and other advanced combat aircraft of the Third Reich.>[...]

ANN's Daily Aero-Term (05.24.13): Terrain/Obstruction Alert

A safety alert issued by ATC to aircraft under their control if ATC is aware the aircraft is at an altitude which, in the controller's judgment, places the aircraft in unsafe proxi>[...]

Aero-News: Quote Of The Day (05.24.13)

"You have a huge job ahead of you. The challenges are many and the solutions are hard." Source: Senate Commerce Committee Chair Jay Rockefeller (D-WV).>[...]

ANN FAQ: ANN's News Portal Syndication Program

Get A Customized ANN News Portal For YOUR Website! As we promised, the ever-so-busy software geeks at ANN have been working overtime on a number of cool new tools and toys... and t>[...]

AF Seven Summits Team Scales Everest

Effort To Raise Funds And Awareness For The Special Operations Warrior Foundation A group of Airmen with the Air Force Seven Summits team reached the highest point of the world, Mo>[...]

blog comments powered by Disqus



Advertisement

Advertisement

Podcasts

Advertisement

© 2007 - 2013 Web Development & Design by Pauli Systems, LC