FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

CHI93LA030 · Piper PA-28-180

11 Nov 1992 · Mankato, MN, United States

Northstar Aviation Piper PA-28-180 · Accident: total loss of engine power (non-mechanical) on approach

From Omar N Bradley Airport (MBY) to an unrecorded destination

Report a problem

Event

NTSB case
CHI93LA030
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

Piper PA-28-180

Aircraft type
Piper PA-28
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
N15609
Onboard fatalities
Unknown
Route
From Omar N Bradley Airport (MBY), Moberly, MOTo not recorded
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
Approach · VFR pattern downwind
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 (non-mechanical)
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; Wire, transmission
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

  • Pilot in command › Fuel tank selector position, improper

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

NTSB narrative

THE PILOT STATED THAT WHILE IN AN EXTENDED TRAFFIC PATTERN TO LAND AT THE CONCLUSION OF A CROSS COUNTRY FLIGHT, THE ENGINE COUGHED AND BEGAN WINDMILLING. A FORCED LANDING WAS MADE DURING WHICH THE AIRPLANE CONTACTED POWER LINES. POST ACCIDENT INSPECTION REVEALED THE FUEL SELECTOR WAS FOUND POSITIONED ON THE LEFT TANK WHICH CONTAINED 12 GALLONS OF FUEL. THE RIGHT TANK WAS SEVERED BY THE POWER LINES AND FOUND EMPTY. A DEPUTY WHO ARRIVED AT THE SCENE JUST AFTER THE ACCIDENT STATED IT DID NOT APPEAR AS THOUGH ANY FUEL HAD DRAINED FROM THE RIGHT TANK. THE PILOT STATED HE TOOK OFF ON THE LEFT TANK, SWITCHED TO THE RIGHT AFTER APRX 1 HOUR, THEN SWITCHED BACK TO THE LEFT APRX 8 MILES FROM LANDING. THE PASSENGER SITTING IN THE LEFT FRONT SEAT, NEXT TO THE SELECTOR, STATED THE PILOT ONLY SWITCHED TANKS ONCE DURING THE FLIGHT. THE LOCATION OF BLOOD SPLATTERS AND A PUNCTURE MARK ON THE FUEL SELECTOR SUGGEST THE SELECTOR WAS POSITIONED ON THE RIGHT TANK WHEN THE ACCIDENT OCCURRED.

Probable cause

THE PILOT'S FAILURE TO SELECT A PROPER FUEL SELECTOR POSITION.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record CHI93LA030
Event ID
20001211X16014
Case number
CHI93LA030
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: local date, investigation status. Values present in the bulk record are kept.
  • The date is the local date; the NTSB stores the UTC date 1992-11-12.
  • API snapshot SHA-256: 2c1849e895678acc8c02ee1107af1c6841fc8eeaf4af53f5dcf9af1df313588a; retrieved 2026-09-21T23:05:15.350Z.