- Date
- May 20, 1970
- Place
- Bird City, KS · BIRD CITY, KS
- Injuries
- 1 uninjured
- Damage
- Substantial damage
- Phase of flight
- Initial climb
- Aircraft
- N9331DPiper PA-22
- Status
- Completed · report March 3, 1971
- Report
- Brief approved by the director
- Case key
- 122934
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-2176 70/5/20 BIRD CITY,KANS PIPER PA-22 CR- 0 0 1 NONCOMMERCIAL PRIVATE, AGE 31, 234 TIME - 1030 N9331D PX- 0 0 0 PLEASURE/PERSONAL TRANSP TOTAL HOURS, 28 IN TYPE, DAMAGE-SUBSTANTIAL OT- 0 0 0 NOT INSTRUMENT RATED. NAME OF AIRPORT - BIRD CITY DEPARTURE POINT INTENDED DESTINATION FIELD STRIP MCDONALD,KANS TYPE OF ACCIDENT PHASE OF OPERATION ENGINE FAILURE OR MALFUNCTION TAKEOFF: INITIAL CLIMB NOSE OVER/DOWN LANDING: ROLL PROBABLE CAUSE(S) PILOT IN COMMAND - INADEQUATE PREFLIGHT PREPARATION AND/OR PLANNING MISCELLANEOUS ACTS,CONDITIONS - FUEL STARVATION MISCELLANEOUS ACTS,CONDITIONS - WATER IN FUEL MISCELLANEOUS ACTS,CONDITIONS - FUEL CONTAMINATION-EXCLUSIVE OF WATER IN FUEL COMPLETE POWER LOSS - COMPLETE ENGINE FAILURE/FLAMEOUT-1 ENGINE EMERGENCY CIRCUMSTANCES - FORCED LANDING OFF AIRPORT ON LAND REMARKS- FUEL SYS NOT DRAIN CKD BFR T/O.HAY CHAFF FOUND IN FUEL SAMPLE.7GALS FUEL L TANK.
Aircraft
- Registration
- N9331D
- Reported as
- Piper PA-22
- Category
- Airplane
- Engine
- reciprocating
- Damage
- Substantial damage
- Airport
- Bird City
N9331DRegistration cancelled May 10, 2013 · Piper PA-22-160Airframe modelPiper PA-22-160Engine modelLycoming 0-290 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.