FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

CHI92LA217 · Piper PA-38-112

10 Nov 1991 · Faribault, MN, United States

Piper PA-38-112 · Accident: propeller/rotor contact to person while standing

From Faribault Municipal Airport-Liz Wall Strohfus Field (FBL) to Faribault Municipal Airport-Liz Wall Strohfus Field (FBL)

Report a problem

Event

NTSB case
CHI92LA217
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-38-112

Aircraft type
Piper PA-38
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
N9296T
Operator
Baron, James H. · private individual
Onboard fatalities
Unknown
Route
From Faribault Municipal Airport-Liz Wall Strohfus Field (FBL)To Faribault Municipal Airport-Liz Wall Strohfus Field (FBL)
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
Standing · engine(s) start-up
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
Propeller/rotor contact to person
DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
None

Cause areas

  • Passenger › Inattentive
  • Pilot in command › Starting procedure, improper

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

NTSB narrative

THE PILOT REPORTED HE AND A FRIEND WERE PREPARING THE PILOT'S AIRPLANE FOR A LOCAL FLIGHT. THE AIRPLANE WAS DUG OUT OF A SNOW DRIFT. THE AIRPLANE'S BATTERY WAS TOO WEAK TO START THE ENGINE, AND THE PILOT ELECTED TO JUMP START THE AIRPLANE USING HIS CAR BATTERY. THE PILOT ENTERED THE COCKPIT TO START THE ENGINE AND THE (INTENDED) PASSENGER WAS SEATED IN THE AUTOMOBILE. ONCE THE AIRPLANE ENGINE WAS STARTED, THE PASSENGER EMERGED FROM THE CAR, AND WAS STRUCK IN THE LEFT ARM BY THE PROPELLER AS HE ATTEMPTED TO REMOVE THE BATTERY CABLES.

Probable cause

THE PILOT'S IMPROPER STARTING PROCEDURES AND THE PASSENGER'S INATTENTIVENESS. A RELATED FACTOR IS THE PILOT'S LACK OF SUPERVISION.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record CHI92LA217
Event ID
20001212X18438
Case number
CHI92LA217
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, damage. 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: 330b9d06a2e13de9ce0fb9387c42f83c8ffd6239212e60aebebac93b23728947; retrieved 2026-09-21T15:14:38.649Z.