FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

CHI94LA031 · Beech B36TC

3 Nov 1993 · Rockford, IL, United States

Beech B36TC · Accident: total loss of engine power (mechanical failure) during initial climb

From Chicago Rockford International Airport (RFD) to Chicago Rockford International Airport (RFD)

Report a problem

Event

NTSB case
CHI94LA031
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 B36TC

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
N8006R
Operator
Unknown
Onboard fatalities
Unknown
Route
From Chicago Rockford International Airport (RFD)To Chicago Rockford International Airport (RFD)
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
Initial climb
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
Total loss of engine power (mechanical failure)
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
Fuel starvation
DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
Substantial

Cause areas

  • Fluid, fuel › Starvation
  • Fuel system, line fitting › Loose
  • Other maintenance personnel › Maintenance, improper

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

NTSB narrative

THE AIRPLANE WAS FLOWN ON A CHECK FLIGHT AFTER MAINTENANCE FOR AN OIL-AND-FILTER CHANGE AND REPLACEMENT OF LEAKING GASKETS. DURING THE INITIAL CLIMB AFTER TAKEOFF, THE PILOT NOTED A MOMENTARY LOSS OF POWER, PROMPTING A TURN TOWARDS THE AIRPORT. THE ENGINE LOST ALL POWER IN THE TURN. DURING A LANDING SHORT OF THE RUNWAY, THE AIRPLANE HIT A FENCE. THE MAIN FUEL LINE CONNECTION TO THE FUEL PUMP WAS FOUND LOOSE. WHEN THE BOOST PUMP WAS ENERGIZED, THE LOOSE FITTING LEAKED SUBSTANTIALLY.

Probable cause

A LOOSE FUEL LINE FITTING, DUE TO IMPROPER MAINTENANCE, WHICH RESULTED IN AN INTERUPTION OF FUEL TO THE ENGINE.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record CHI94LA031
Event ID
20001211X13718
Case number
CHI94LA031
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: 377436f99bd78cf27047cbc5a114a290669660aff4bed0f3ae13c2bda4e766c8; retrieved 2026-09-23T01:29:46.817Z.