- Date
- December 16, 1971
- Place
- Evansville, IN · EVANSVILLE, IN
- Injuries
- 1 fatal
- Damage
- Destroyed
- Phase of flight
- Initial climb
- Aircraft
- N8641CPiper PA-22
- Status
- Completed · report June 30, 1972
- Report
- Brief approved by the director
- Safety recommendations
- Yes
- Case key
- 80048
From the NTSB’s public API. By law, NTSB reports can’t be used as evidence in lawsuits over the accident.
On this page
NTSB brief
NTSB’s brief of the accident, as it was printed: the coded facts, with the probable cause and factors.
---------------------------------------------------------------------------------------------------------------------------- FILE DATE LOCATION AIRCRAFT DATA INJURIES FLIGHT PILOT DATA F S M/N PURPOSE ---------------------------------------------------------------------------------------------------------------------------- 3-4220 71/12/16 EVANSVILLE,IND PIPER PA-22 CR- 1 0 0 INSTRUCTIONAL STUDENT, AGE 34, 20 TOTAL TIME - 1421 N8641C PX- 0 0 0 TRAINING HOURS, ALL IN TYPE, NOT DAMAGE-DESTROYED OT- 0 0 0 INSTRUMENT RATED. NAME OF AIRPORT - DRESS REGIONAL DEPARTURE POINT INTENDED DESTINATION EVANSVILLE,IND LOCAL TYPE OF ACCIDENT PHASE OF OPERATION FIRE OR EXPLOSION: IN FLIGHT TAKEOFF: INITIAL CLIMB COLLISION WITH GROUND/WATER: CONTROLLED LANDING: LEVEL OFF/TOUCHDOWN PROBABLE CAUSE(S) POWERPLANT - FUEL SYSTEM: LINES AND FITTINGS MISCELLANEOUS ACTS,CONDITIONS - MATERIAL FAILURE MISCELLANEOUS ACTS,CONDITIONS - FIRE IN CABIN,COCKPIT,BAGGAGE COMPARTMENT MISCELLANEOUS ACTS,CONDITIONS - FIRE IN ENGINE FACTOR(S) PILOT IN COMMAND - INADEQUATE PREFLIGHT PREPARATION AND/OR PLANNING PILOT IN COMMAND - ATTEMPTED OPERATION W/KNOWN DEFICIENCIES IN EQUIPMENT EMERGENCY CIRCUMSTANCES - FORCED LANDING ON AIRPORT/SEAPLANE BASE/HELIPT. REMARKS- MAIN FUEL LINE BETWEEN FILTER AND CARB RUPTURED.SMELL LIKE EXHAUST FUMES REPTD FROM PREVIOUS FLT.
Aircraft
- Registration
- N8641C
- Reported as
- Piper PA-22
- Category
- Airplane
- Engine
- reciprocating
- Damage
- Destroyed
- Airport
- Dress Regional
Matched to the registry by N-number and the event date; the registry’s history has gaps, so older matches can be wrong. Compare the reported make and model.