Premium research interface

The modern interface for aviation safety intelligence.

Search investigations, review source evidence, monitor watched reports, and trace long-term patterns from one calm, data-first workspace.

63k+
Reports indexed
1940-2026
Coverage
Recent
Last data refresh
Featured Report

Loading…

Loading featured report…

Loading…
Open Report

Safety trends by operating rule

Track fatal and non-fatal accident patterns across Part 91, Part 135, and Part 121 operations.

Loading trend charts…

Browse the aviation graph

Move quickly by aircraft, airport, operator, and time with indexes built for research, not wandering.

Last Data Update

By Decade

By Month

Aircraft Manufacturer

More manufacturers

Airports

More airports

Operators

More operators

About

Aviation safety reports, made easier to study

NTSB Reports is an independent research and search tool for public aviation accident and incident records. It brings NTSB aviation reports, structured fields, docket files, extracted figures, photos, videos, and update history into one searchable interface.

The goal is practical safety education: make it faster to find relevant investigations, compare similar events, review factual records, and understand the evidence behind probable-cause and preliminary reports.

The investigative work and source records belong to the National Transportation Safety Board and the published investigation record. This site is not affiliated with or endorsed by the NTSB.

FAQs

NTSB Report

November 20, 2008 · Beech E35 · N3213C

Bloomington, IN

Overview

Report Status
Final with probable cause
Event Type
Accident
Date
November 20, 2008
Injury Outcomes
No injuries (1 uninjured)
Location
Bloomington, IN
Aircraft
Beech E35
Tail Number
N3213C
Operator
Six Four Alpha
Injuries
None
Aircraft Damage
Substantial
NTSB Number
CEN09CA080

The pilot reported that the engine began to run rough during cruise flight at 6,000 feet mean sea level. He noted that the takeoff and climb were uneventful, and that the personal instrument-flight-rules flight had proceeded normally to that point. He advised air traffic control of the situation and elected to divert to an intermediate airport located approximately 10 miles west of his present position. The pilot increased the mixture, switched fuel tanks, and applied carburetor heat in an attempt to address the rough running engine; however, those efforts were not successful. The number one cylinder temperature had dropped and the engine oil pressure subsequently went to zero. He notified the controller that he would be unable to make it to the runway and set up for a forced landing in a pasture about 3.5 miles east of the airport. The terrain consisted of rolling hills. After touchdown, he was unable to stop the airplane before the aircraft impacted a fence or trees. The airplane sustained substantial damage to the leading edges of both wings. A postaccident inspection revealed that the number one cylinder exhaust valve had failed at the base of the valve stem. The intake valve and piston sustained mechanical damage as a result. The secondary mechanical damage precluded a metallurgical examination of the fracture surface of the exhaust valve stem. The engine had accumulated about 1,130 hours since overhaul and the airplane had accumulated about 26 hours of flight time since the most recent annual inspection, which was completed approximately one month prior to the accident.

NTSB Probable Cause

A partial loss of engine power due to a failure of the number one cylinder exhaust valve, and the associated secondary damage to the intake valve and piston.

Full Narrative

The pilot reported that the engine began to run rough during cruise flight at 6,000 feet mean sea level (msl). He noted that the takeoff and climb were uneventful, and the personal instrument flight rules (IFR) flight had proceeded normally to that point. He advised air traffic control of the situation and elected to divert to an intermediate airport located approximately 10 miles west of his present position. The pilot increased the mixture, switched fuel tanks, and applied carburetor heat in an attempt to address the rough running engine; however, those efforts were not successful. The #1 cylinder temperature had dropped and the engine oil pressure subsequently went to zero. He notified the controller that he would be unable to make it to the runway and set up for a forced landing in a pasture about 3.5 miles east of the airport. The terrain consisted of rolling hills. After touch down, he was unable to stop the airplane before it impacted a fence and trees. The airplane sustained substantial damage to the leading edges of both wings. A post accident inspection revealed that the #1 cylinder exhaust valve had failed at the base of the valve stem. The intake valve and piston sustained mechanical damage as a result. The secondary mechanical damage precluded a metallurgical examination of the fracture surface of the exhaust valve stem. The Continental E225-8 engine that powered the airplane had accumulated about 1,130 hours since overhaul. The airplane had accumulated about 26 hours flight time since the most recent annual inspection, which was completed approximately one month prior to the accident.

Flight

Event TypeAccident
Event Time07:30 EST
Nearest AirportMonroe County (4nm)
Flight Plan FiledIFR
Flight Plan ActivatedYes
Aircraft FireNo
Aircraft ExplosionNo

Aircraft

AircraftBeech E35
Tail NumberN3213C
Aircraft CategoryAir
DamageSubstantial
OperatorSix Four Alpha
Operating RulePart 91
Engines1
Engine TypeReciprocating
Engine DetailsCont Motor · E225 SERIES · Reciprocating · 225
Seats4

People & Injuries

Injury SummaryNo injuries (1 uninjured)
Fatal0
Serious0
Minor0
Uninjured1
Total1
Crew 1Age 49 · Third Class · None

Conditions

ConditionsVMC
LightDaylight
Wind320° @ 6 kt
Visibility10 sm
CeilingNone
Temperature / Dew Point32 C / 25 C
Altimeter30.18 inHg
Observation Time12:46
Weather SourceWFAC

Appendix: Source Data