MIA69F0387

NTSB accident investigation · Piper PA-24 · Tampa, FL · January 31, 1969

Accident · No injuriesClosed
Date
January 31, 1969
Place
Tampa, FL · TAMPA, FL
Injuries
1 uninjured
Damage
Substantial damage
Phase of flight
Landing
Aircraft
N7984PPiper PA-24
Status
Completed · report May 9, 1969
Report
Brief approved by the director
Case key
191705

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-0329  69/1/31    TAMPA,FLA           PIPER PA-24         CR-  0  0  1  NONCOMMERCIAL             STUDENT, AGE 52, 7560
        TIME - 1410                    N7984P              PX-  0  0  0  BUSINESS                  TOTAL HOURS, 412 IN TYPE,
                                       DAMAGE-SUBSTANTIAL  OT-  0  0  0                            NOT INSTRUMENT RATED.
        NAME OF AIRPORT - TAMPA INTL
        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)
           MISCELLANEOUS ACTS,CONDITIONS - CIRCUIT BREAKER POPPED
        REMARKS- LANDED WITH PARTIALLY EXTENDED GR.

Aircraft

Registration
N7984P
Reported as
Piper PA-24
Category
Airplane
Engine
reciprocating
Damage
Substantial damage
Airport
Tampa Intl

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.