- Date
- August 1, 1972
- Place
- Tallahassee, FL · TALLAHASSEE, FL
- Injuries
- 2 uninjured
- Damage
- Substantial damage
- Phase of flight
- Landing
- Aircraft
- N7732PPiper PA-24
- Status
- Completed · report April 11, 1973
- Report
- Brief approved by the director
- Case key
- 168789
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-4037 72/8/1 TALLAHASSEE,FLA PIPER PA-24 CR- 0 0 1 NONCOMMERCIAL PRIVATE, AGE 49, UNK/NR TIME - 0845 N7732P PX- 0 0 1 PLEASURE/PERSONAL TRANSP TOTAL HOURS, 1250 IN DAMAGE-SUBSTANTIAL OT- 0 0 0 TYPE, NOT INSTRUMENT RATED. NAME OF AIRPORT - TALLAHASSEE MUNI DEPARTURE POINT INTENDED DESTINATION JACKSONVILLE,FLA TALLAHASSEE,FLA TYPE OF ACCIDENT PHASE OF OPERATION WHEELS-UP LANDING: LEVEL OFF/TOUCHDOWN PROBABLE CAUSE(S) PILOT IN COMMAND - FAILED TO ASSURE THE GEAR WAS DOWN AND LOCKED FACTOR(S) PERSONNEL - MAINTENANCE,SERVICING,INSPECTION: INADEQUATE MAINTENANCE AND INSPECTION AIRFRAME - LANDING GEAR: NORMAL RETRACTION/EXTENSION ASSEMBLY MISCELLANEOUS ACTS,CONDITIONS - LACK OF LUBRICATION-SPECIFIC PART,NOT SYSTEM MISCELLANEOUS ACTS,CONDITIONS - CIRCUIT BREAKER POPPED REMARKS- LACK OF LUBRICATION CAUSED GR MOTOR TO OVRLOAD 30 AMP CIRCUIT BREAKER-LDG GR BECAME INOP.
Aircraft
- Registration
- N7732P
- Reported as
- Piper PA-24
- Category
- Airplane
- Engine
- reciprocating
- Damage
- Substantial damage
- Airport
- Tallahassee Muni
N7732PRegistered now · Piper PA-24-250Airframe modelPiper PA-24-250Engine 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.