Beechcraft 390 N6JR
27 July 2010 · Oshkosh, Wisconsin, United States · Serious injuries
Summary
On 27 July 2010 at about 23:16 local time, a Beechcraft 390 registered N6JR, operated by Roush Fenway Racing, LLC., was involved in an accident near Oshkosh, Wisconsin, United States. 2 people were on board and 2 were seriously injured. The aircraft was substantially damaged. The NTSB has published a probable cause for this accident; it is quoted in full below.
The record
- Date
- at 23:16
- Classification
- Accident
- Location
- Oshkosh, Wisconsin, United States
- Nearest airport
- Wittman Regional Airport (OSH)
- Coordinates
- 43.9753, -88.5581
- Aircraft
- Beechcraft 390
- Registration
- N6JR
- Category
- Airplane
- Engines
- 2
- Operator
- Roush Fenway Racing, LLC.
- Operating rule
- Part 91: General Aviation
- Purpose of flight
- Business
- Phase of flight
- Not recorded
- Route
- Ypsilanti → Oshkosh
- Aircraft damage
- Substantial
- Weather
- VMC
- Light
- Day
- NTSB number
- CEN10FA443
People
2 people were seriously injured.
| On board | Died | Serious | Minor | Uninjured |
|---|---|---|---|---|
| 2 | 0 | 2 | 0 | 0 |
Probable cause
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.
Quoted verbatim from the NTSB record. This site does not paraphrase or interpret it.
Read the full NTSB narrative
The accident occurred during the Experimental Aircraft Association'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 postaccident 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 postaccident 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.
Quoted verbatim from the NTSB record.
Other Beechcraft 390 accidents
| Date | Aircraft | Location | Operator | Outcome | Died |
|---|---|---|---|---|---|
| 19 Dec 2010 | Beechcraft 390 | Bever, Switzerland | Windrose Air Jetcharter GmbH | Fatal | 2 |
| 23 Dec 2008 | Beechcraft 390 | Lewistown, Missouri, United States | CNS Corporation | No injuries | - |
| 13 Feb 2008 | Beechcraft 390 | Leesburg, Virginia, United States | DEKA Research & Development Corp | No injuries | - |
| 21 Feb 2013 | Beechcraft 390 | Thomson, Georgia, United States | Richard Z. Trammell | Fatal | 5 |
| 4 Mar 2013 | Beechcraft 390 | Cranves-Sales, France | Global Jet Luxembourg | Fatal | 2 |
| 17 Mar 2013 | Beechcraft 390 | South Bend, Indiana, United States | Digicut Systems | Fatal | 2 |
Other accidents in this area
| Date | Aircraft | Location | Operator | Outcome | Died |
|---|---|---|---|---|---|
| 19 Jul 2010 | Nord 3202 | Oshkosh, Wisconsin, United States | Schommer David L | No injuries | - |
| 6 Mar 2010 | Beechcraft A36 | Milwaukee, Wisconsin, United States | - | No injuries | - |
| 25 Jul 2010 | Beechcraft H35 | Green Lake, Wisconsin, United States | Michael A. Lella | No injuries | - |
| 21 Dec 2010 | Cessna 340A | Madison, Wisconsin, United States | Wisconsin Aviation Inc | No injuries | - |
| 15 Mar 2010 | Cessna 172M | Waupaca, Wisconsin, United States | Riverside Aviation Inc | No injuries | - |
| 25 Dec 2010 | Cessna 305A | Spooner, Wisconsin, United States | Kronlund Kevin | No injuries | - |