Beech B36TC accident near Dayton, Ohio, April 1, 2010
On April 1, 2010 at about 4:53 pm local time, a Beech B36TC, registered N4BA, was destroyed in an accident during initial climb near Dayton, Ohio (Dayton-Wright Brothers airport). It was a personal flight under general aviation rules (Part 91). 2 people were killed. The weather was visual conditions (good weather).
The NTSB's probable cause their words, unchanged
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.
Source: NTSB aviation accident database, copy made November 2, 2026. Docket and reports at the NTSB.
What the record shows
- Date
- April 1, 2010 · about 4:53 pm local time · cases in 2010
- Place
- Dayton, Ohio · Dayton-Wright Brothers · cases near this airport · map
- Type
- Accident
- Injuries
- 2 people were killed.
- Weather
- visual conditions (good weather)
- Aircraft
- Beech B36TC · all B36TCs on the register
- Registration
- N4BA · registry record · serial EA-356
- Damage
- Destroyed
- Flight
- Personal flight · general aviation rules (Part 91)
The NTSB's narrative final · quoted from the NTSB record
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.
The complete narrative as the NTSB published it. The NTSB's docket holds the report as a PDF and any photographs, statements and other documents from the investigation.
The factual record from the NTSB's investigation tables, in plain English
What happened, in order
- Loss of engine power (total) during initial climb defining event
- Off-field or emergency landing during emergency descent
- Landing area undershoot during landing
- Collision with terrain or object (not controlled flight into terrain) during landing
The NTSB's findings
- cause Aircraft › Aircraft power plant › Engine (reciprocating) › Recip eng rear section › Failure other cases naming the engine
- factor Personnel issues › Action/decision › Info processing/decision › Decision making/judgment › Pilot
Pilot
- Certificate: private
- Ratings: single-engine land; instrument: airplane
- Flight time: 182 hours in all; 93 in this make and model
- Last flight review: August 31, 2009
- Medical certificate: Class 3 (with waivers/limitations)
- Seat: left
- Injury: fatal
The aircraft
- Airframe total time: 2,284 hours
- Last inspection: annual inspection, March 11, 2010
- Maximum gross weight: 3,850 lb
- Seats: 6
- Landing gear: retractable
- Engine: Cont Motor TSIO-520 SER (piston); 0 hours total
- Fire on the ground
- Operator: Poelking Air LLC
The flight
- Departed from: MGY Dayton OH at 4:50 pm
- Destination: DPA West Chicago IL
- Flight plan: IFR
- Runway 20, 5,000 ft by 100 ft
Weather at the time
- Light: daylight
- Wind: from 210° at 9 knots, gusting 22
- Visibility: 10 statute miles
- Sky: clear
- Temperature: 72°F (22°C), dew point 48°F (9°C)
- Altimeter: 29.97 inHg
- Observation at 4:53 pm from MGY, 1 miles away
Injuries
| Fatal | Serious | Minor | None | |
|---|---|---|---|---|
| Flight crew | 1 | |||
| Passengers | 1 |
Documents from the investigation the NTSB's docket: the evidence folder behind the report
15 documents, released by the NTSB on May 9, 2011. View them here, or download them; the NTSB redacts some personal details before release, and this site shows the NTSB's own titles rather than its file names.
The same docket at the NTSB · documents without a copy here are fetched from the NTSB when you open them.
Other NTSB records under N4BA the same tail number, which may have belonged to a different aircraft at the time
Connections how this case links to the rest of the register
- N4BA on the register today · the tail number may have moved to another aircraft since
- Beechcraft B36 Bonanza 308 registered today · the model family and its accident history
- Beechcraft 6 aircraft on the register
- Engine: Cont Motor TSIO-520 SER 4,109 aircraft carry this series today · as the NTSB recorded it
- Dayton/Wright Brothers Airport · nearest airport
- Dupage Airport · bound for
- Accidents and incidents in Ohio 1,884 since 1982 · 253 in the last ten years
- Ohio 8,535 aircraft registered
- Other NTSB records under N4BA 1 records · the number may have belonged to another aircraft at the time
The whole map of how records connect · these connections as data: /graph/accident/CEN10FA180.json.
The bigger picture in Aviation Analytics: accidents over time since 1982, by model, by phase of flight and conditions, by place and on the map.
Everything on this page comes from the NTSB's public records. The narrative, probable cause and findings are the NTSB's own words; the coded tables behind the report are written out in plain English, with pilots' ages, home towns and medical details left out. The documents and photographs are the NTSB's docket, shown as the NTSB released them. This site's own text does not name anyone involved, its policy at this time. A preliminary report can change; the final report usually follows one to two years later, and the page is refreshed when it does.