FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

CHI84IA404 · Beech A36TC

24 Sept 1984 · Lafayette, IN, United States

Beech A36TC · Incident: loss of engine power en route

From Chicago Midway International Airport (MDW) to Purdue University Airport (LAF)

Report a problem

Event

NTSB case
CHI84IA404
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
Incident
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
Instrument Meteorological Cond

Beech A36TC

Aircraft type
Beechcraft 36
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
N305MM
Operator
Unknown
Onboard fatalities
Unknown
Route
From Chicago Midway International Airport (MDW), Chicago, ILTo Purdue University Airport (LAF), Lafayette, 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 · descent
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
DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
Minor

Cause areas

  • Reason for occurrence undetermined

Approximate · Estimated position: the centre of Lafayette, IN, the place the record names. Not the accident site.

NTSB narrative

THE PLT REPORTED THAT WHEN HE LEVELED OFF AT 3000 FT MSL, THE AUX FUEL BOOST SWITCH WAS STILL ON, SO HE SWITCHED IT 'OFF.' WHEN THE SWITCH WAS TURNED OFF, THE ENG BEGAN TO RUN WITH A BIT OF VIBRATION, SO HE RETURNED THE SWITCH TO 'ON' & LEFT IT IN THAT POSITION FOR THE REMAINDER OF THE FLT. THE EN ROUTE PORTION OF THE FLT WAS UNEVENTFUL. DURING A DESCENT THRU 2300 FT, IN IFR CONDITIONS NEAR THE DESTINATION, THE ENG STOPPED RUNNING. THE PLT WAS UNABLE TO RESTART THE ENG. HE REPORTED THAT THE ACFT BROKE OUT OF THE OVERCAST AT A LOW ALT. THE PLT SAW A SUITABLE FIELD & LANDED, BUT THE ACFT RECEIVED MINOR DAMAGE. THE ENG OPERATED NORMALLY DURING A RUN-UP. NO REASON FOR THE LOSS OF POWER WAS IDENTIFIED.

Verbatim NTSB analysis from the NTSB dataset

Sources

NTSB record CHI84IA404
Event ID
20001214X40992
Case number
CHI84IA404
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: 4a1a45848722f21cd8c4d71f79bd1a12c3afa8326a58adf37e783b1a223861f9; retrieved 2026-09-23T19:05:06.976Z.