FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

CHI00LA079 · Beech BE-35V

27 Feb 2000 · Bloomington, IN, United States

Beech BE-35V · Accident: loss of engine power en route

From ISZ · Blue Ash to Monroe County Airport (BMG)

Report a problem

Event

NTSB case
CHI00LA079
Event typeAccident: someone killed or seriously injured, or the aircraft substantially damaged (NTSB definition). Incident: an occurrence that affected or could have affected safety, short of that. Glossary
Accident
InvestigationHow far the investigation had got when the record was published: preliminary, ongoing, final or completed. Unknown where the source does not say. Glossary
Completed
API-reported fatalities
0 · all aircraft and ground
Ground fatalities
0
OperationWhat kind of flying it was, grouped by the rules it flew under: airline (US Part 121), air taxi and commuter (Part 135), general aviation (Part 91 and similar), military or government. Glossary
General aviation
WeatherVisual meteorological conditions (VMC): good enough to fly by looking outside. Instrument conditions (IMC): cloud or low visibility, flying by instruments. Glossary
Visual Meteorological Cond

Beech BE-35V

Aircraft type
Beechcraft BE-35
Category
Airplane
RegistrationThe aircraft's tail number, such as N12345 or G-ABCD. Registrations are reissued, so the same one years apart can be a different aircraft. Glossary
N6FN
Operator
Unknown
Onboard fatalities
Unknown
Route
From ISZ · Blue AshTo Monroe County Airport (BMG), IN
Aircraft age
Not recorded
Flight rulesThe regulations the flight operated under: in the US, Part 91 (general aviation), Part 121 (airlines), Part 135 (air taxi and commuter) and others; for flights abroad, the NTSB's coarser commercial or non-commercial code. Glossary
Part 91: General Aviation
Phase of flightThe stage of the flight when things started to go wrong: standing, taxi, takeoff, initial climb, en route, maneuvering, approach or landing. Glossary
En route · cruise
First occurrenceThe single coded event the NTSB judges best describes what happened (records from 2008 on). Older records name the first occurrence in the sequence instead. Glossary
Loss of engine power
Also codedOther events the NTSB coded in the sequence, such as a wire strike after a loss of power. Flight Findings uses them for its kinds of event. Glossary
Tree(s)
DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
Destroyed

Cause areas

  • Company maintenance personnel › Maintenance, overhaul, major, improper

Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.

NTSB narrative

The airplane impacted a wooded area during a forced landing following a total loss of engine power. Examination of the engine revealed sealant was used on the cylinder bases and the cylinder base O-rings of the Teledyne Continental Motors (TCM) engine. A step was present at one of the thru bolt parting surfaces located at the cylinder base. The TCM overhaul manual, service bulletin and service letter do not specify the use of sealant on cylinder bases and cylinder base O-rings. Engine logbook records indicated that Blue Ash Aircraft Services performed a major overhaul of the Teledyne Continental IO-520-BA engine, serial number 249748-R, on March 24, 1998 at a tachometer time of 2,930.0 hours. Engine logbook records also indicated that a 100-hour inspection of the airplane was performed by the same maintenance facility on November 2, 1999 at a tachometer time of 3,668 hours. The tachometer at the accident site indicated 3,766.02 hours. The engine accumulated a total time since major overhaul of 836 hours.

Probable cause

the improper major overhaul of the engine by company maintenance personnel. The tree was a contributing factor.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record CHI00LA079
Event ID
20001212X20465
Case number
CHI00LA079
Dataset
historical-pre2008
Source SHA-256
89e2df6d848e7ab3b42e7d7c7a03ff403303057a26ca04c95b3ea67201c3ce74
Source notes (4)
  • Unreviewed is an editorial label, not an investigation status. API-sourced is not report-checked or human-reviewed. Explicit event totals are used without summing aircraft injury tables; onboard allocation is withheld. Unknown values remain unknown. The operation category is mapped from the NTSB-reported FAR part and has not been reviewed.
  • Filled from the NTSB case API where the bulk record had no value: investigation status. Values present in the bulk record are kept.
  • The date is the local date, which is the same as the UTC date the NTSB stores.
  • API snapshot SHA-256: 11f345605c2687baca9f0d9169e6267965043b8685ec05dfb58e35295eb23628; retrieved 2026-09-21T10:42:19.899Z.