- Date
- March 27, 1972
- Place
- Blountstown, FL · BLOUNTSTOWN, FL
- Injuries
- 2 minor
- Damage
- Substantial damage
- Phase of flight
- Approach
- Aircraft
- N2836ZPiper PA-22
- Status
- Completed · report January 8, 1973
- Report
- Brief approved by the director
- Case key
- 165648
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-1037 72/3/27 BLOUNTSTOWN,FLA PIPER PA-22 CR- 0 0 2 INSTRUCTIONAL COMMERCIAL, FL.INSTR., TIME - 1715 N2836Z PX- 0 0 0 DUAL AGE 53, 1037 TOTAL HOURS, DAMAGE-SUBSTANTIAL OT- 0 0 0 121 IN TYPE, INSTRUMENT RATED. NAME OF AIRPORT - BLOUNTSTOWN DEPARTURE POINT INTENDED DESTINATION BLOUNTSTOWN,FLA LOCAL TYPE OF ACCIDENT PHASE OF OPERATION FIRE OR EXPLOSION: IN FLIGHT LANDING: FINAL APPROACH COLLISION WITH GROUND/WATER: CONTROLLED LANDING: LEVEL OFF/TOUCHDOWN PROBABLE CAUSE(S) MISCELLANEOUS ACTS,CONDITIONS - FIRE IN CABIN,COCKPIT,BAGGAGE COMPARTMENT TERRAIN - WET,SOFT GROUND FACTOR(S) PERSONNEL - MAINTENANCE,SERVICING,INSPECTION: INADEQUATE MAINTENANCE AND INSPECTION POWERPLANT - POWERPLANT-INSTRUMENTS: OTHER MISCELLANEOUS ACTS,CONDITIONS - GROUNDED AIRFRAME - FUSELAGE: OTHER MISCELLANEOUS ACTS,CONDITIONS - DETERIORATED EMERGENCY CIRCUMSTANCES - FORCED LANDING OFF AIRPORT ON LAND SMOKE IN COCKPIT REMARKS- SHORTED NR6 WIRE,AMMETER TO MASTER SWITCH.FIRE FANNED BY RAM AIR THRU HOLE IN RUBBER GROMMET SEAL.
Aircraft
- Registration
- N2836Z
- Reported as
- Piper PA-22
- Category
- Airplane
- Engine
- reciprocating
- Damage
- Substantial damage
- Airport
- Blountstown
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.