Probable cause
The complete loss of engine power due to failure of the No. 1 main bearing, and the secondary failure of a crankcase through-bolt and the fuel pump drive coupling. Contributing to the accident was the pilot's decision to attempt a return to the airport for a downwind forced landing, despite having an interstate highway and an open grass area short of the runway as available emergency landing sites.
NTSB analysis
Approximately 1 minute after takeoff, as the airplane was about 1 mile southwest of the airport, the pilot reported an engine failure to air traffic controllers and initiated a return to the airport. One witness, located about 1 mile west of the airport, reported that the sound of the engine changed abruptly; noting that the engine seemed to lose power completely. Another witness, located near the airport, observed the airplane approach from the west and turn to align with the downwind runway. During the turn, the left wingtip struck the ground and the airplane impacted short of the runway. A postimpact fire ensued. Although the pilot initiated a return to the airport, an interstate highway and an open grass area short of the runway were both potentially available for an emergency landing. A postaccident examination of the engine revealed that the No. 1 (aft) main crankshaft bearing failed due to unknown circumstances. The progressive failure of the bearing likely precipitated secondary failures of the crankcase through-bolt and the fuel pump coupling, which resulted in a complete loss of engine power.
Text from the NTSB. Open the NTSB docket for CEN10FA180 for the full record.
Event
- Date
- Apr 1, 2010
- Type
- Accident
- Place
- Dayton, Ohio
- Nearest airport
- Dayton-Wright Brothers (MGY)
- Highest injury
- Fatal
- Fatal injuries
- 2
- Weather
- Visual (VMC)
- Light
- Day
Beech B36TC
- N-number
- N4BA
- Category
- Airplane
- Damage
- Destroyed
- Operating rule
- Part 91 (general aviation)
- Purpose of flight
- Personal
From the NTSB aviation accident database: N-registered aircraft, events since 2008, data through Oct 28, 2026. The file is published monthly, so the latest weeks are incomplete and recent records can change. The official source is the NTSB aviation investigation search. CheckAero is independent and not affiliated with the NTSB.