CHI94LA026 · Beech F33A
Beech F33A · Accident: loss of engine power en route
From Anoka County-Blaine (Janes Field) Airport (ANE) to Spirit of St Louis Airport (SUS)
Event
- NTSB case
- CHI94LA026
- 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 F33A
- Aircraft type
- Beechcraft 33
- 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
- N6333Y
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Anoka County-Blaine (Janes Field) Airport (ANE), Anoka, MNTo Spirit of St Louis Airport (SUS), SAINT LOUIS, MO
- 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
- Pole
- 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
- Fuel system, line fitting › Undertorqued
- Other maintenance personnel › Maintenance, installation, improper
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
PRIOR TO THE ACCIDENT FLIGHT THE MECHANICAL FUEL PUMP WAS REMOVED AND REPLACED TO COMPLY WITH AN AIRWORTHINESS DIRECTIVE. THE ACCIDENT FLIGHT WAS THE FIRST FLIGHT AFTER THE MAINTENANCE. WHILE IN CRUISE FLIGHT THE PILOT NOTICED A LOSS IN FUEL PRESSURE. THE PRESSURE LOSS CONTINUED UNTIL THE PILOT WAS REQUIRED TO MAKE A FORCED LANDING AT NIGHT. THE AIRPLANE CONTACTED A FENCE AND GUARD RAIL POSTS DURING THE LANDING. SUBSEQUENT EXAMINATION REVEALED THAT A 'B' NUT ATTACHING THE FUEL LINE TO THE MECHANICAL FUEL PUMP HAD BACKED OFF. NO OTHER DISCREPANCIES WERE NOTED.
Probable cause
other maintenance personnel's improper maintenance installation and fuel system line fitting undertorqued. Factors related to the accident were the dark night, along with the fence and posts which were contacted.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CHI94LA026
- Event ID
- 20001211X13547
- Case number
- CHI94LA026
- 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: 8f1840502110f6c9a49344fdcee580c5a731bd674a5fe4a875602254a1772bf1; retrieved 2026-09-21T22:46:15.823Z.