- Date
- September 12, 1981
- Place
- High Springs, FL · HIGH SPRINGS, FL
- Injuries
- 1 minor
- Damage
- Substantial damage
- Phase of flight
- Enroute
- Aircraft
- N3258ZPiper PA-22
- Status
- Completed · report October 19, 1981
- Report
- Brief approved by the director
- FAA report
- 19810912058759A
- Case key
- 123733
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-2143 81/9/12 HIGH SPRINGS,FL PIPER PA-22 CR- 0 0 1 MISCELLANEOUS PRIVATE, AGE 51, 558 TIME - 1700 N3258Z PX- 0 0 0 TOWING GLIDERS TOTAL HOURS, 180 IN TYPE, DAMAGE-SUBSTANTIAL OT- 0 0 0 NOT INSTRUMENT RATED. NAME OF AIRPORT - RUDYS GLIDERPORT DEPARTURE POINT INTENDED DESTINATION HIGH SPRINGS,FL LOCAL TYPE OF ACCIDENT PHASE OF OPERATION ENGINE FAILURE OR MALFUNCTION IN FLIGHT: CLIMB TO 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 STARVATION FACTOR(S) MISCELLANEOUS ACTS,CONDITIONS - OVERLOAD FAILURE COMPLETE POWER LOSS - COMPLETE ENGINE FAILURE/FLAMEOUT-1 ENGINE EMERGENCY CIRCUMSTANCES - FORCED LANDING OFF AIRPORT ON LAND REMARKS- PLT STATED OPERATED ENG ON L TK,R TK 3/4 FULL.L TK FD EMPTY AFT ACCD.
Aircraft
- Registration
- N3258Z
- Reported as
- Piper PA-22
- Category
- Airplane
- Engine
- reciprocating
- Damage
- Substantial damage
- Airport
- Rudys Gliderport
N3258ZRegistration cancelled Nov 5, 2022 · Piper PA-22-160Airframe modelPiper PA-22-160Engine modelLycoming 0-320 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.