- Date
- June 15, 1976
- Place
- Dyersburg, TN · DYERSBURG, TN
- Injuries
- 2 serious, 3 minor
- Damage
- Substantial damage
- Phase of flight
- Enroute
- Aircraft
- N222GEPiper PA-32
- Status
- Completed · report June 30, 1976
- Report
- Brief approved by the director
- FAA report
- 19760615013889A
- Case key
- 153388
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-1106 76/6/15 DYERSBURG,TN PIPER PA-32 CR- 0 0 1 NONCOMMERCIAL PRIVATE, AGE 29, 227 TIME - 1041 N222GE PX- 0 2 2 PLEASURE/PERSONAL TRANSP TOTAL HOURS, 7 IN TYPE, DAMAGE-SUBSTANTIAL OT- 0 0 0 NOT INSTRUMENT RATED. NAME OF AIRPORT - DYERSBURG DEPARTURE POINT INTENDED DESTINATION LAST ENROUTE STOP INDIANAPOLIS,IN HOUSTON,TX MEMPHIS,TN TYPE OF ACCIDENT PHASE OF OPERATION ENGINE FAILURE OR MALFUNCTION IN FLIGHT: NORMAL CRUISE HARD LANDING LANDING: LEVEL OFF/TOUCHDOWN PROBABLE CAUSE(S) PILOT IN COMMAND - INADEQUATE PREFLIGHT PREPARATION AND/OR PLANNING PILOT IN COMMAND - MISMANAGEMENT OF FUEL MISCELLANEOUS ACTS,CONDITIONS - FUEL EXHAUSTION PILOT IN COMMAND - IMPROPER LEVEL OFF FACTOR(S) MISCELLANEOUS ACTS,CONDITIONS - INATTENTIVE TO FUEL SUPPLY COMPLETE POWER LOSS - COMPLETE ENGINE FAILURE/FLAMEOUT-1 ENGINE EMERGENCY CIRCUMSTANCES - FORCED LANDING OFF AIRPORT ON LAND
Aircraft
- Registration
- N222GE
- Reported as
- Piper PA-32
- Category
- Airplane
- Engine
- reciprocating
- Damage
- Substantial damage
- Airport
- Dyersburg
N222GERegistered now · Piper PA-32-260Airframe modelPiper PA-32-260Engine modelLycoming 0-540 series
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.
FAA reports on this event · 1
The FAA’s own accident and incident reports, matched to the aircraft by N-number and date.