DEN66D0269

NTSB accident investigation · Piper PA-24 · Phoenix, AZ · March 15, 1966

Accident · No injuriesClosed
Date
March 15, 1966
Place
Phoenix, AZ · PHOENIX, AZ
Injuries
2 uninjured
Damage
Substantial damage
Phase of flight
Landing
Aircraft
N7676PPiper PA-24
Status
Completed · report May 11, 1966
Report
Brief approved by the director
Case key
173217

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-0640  66/3/15    PHOENIX ARIZ        PIPER PA-24         CR-  0  0  1  NONCOMMERCIAL             PRIVATE, AGE 39, 250
        TIME - 1500                    N7676P              PX-  0  0  1  PLEASURE/PERSONAL TRANSP  TOTAL HOURS, 150 IN TYPE,
                                       DAMAGE-SUBSTANTIAL  OT-  0  0  0                            NOT INSTRUMENT RATED.
        NAME OF AIRPORT - SKY HARBOR
        TYPE OF ACCIDENT                                         PHASE OF OPERATION
           WHEELS-UP                                                LANDING: LEVEL OFF/TOUCHDOWN
        PROBABLE CAUSE(S)
           AIRFRAME - LANDING GEAR: NORMAL RETRACTION/EXTENSION ASSEMBLY
           MISCELLANEOUS ACTS,CONDITIONS - JAMMED
        REMARKS- LANDING GEAR SYSTEM MALFUNCTION FOR UNDETERMINED REASON

Aircraft

Registration
N7676P
Reported as
Piper PA-24
Category
Airplane
Engine
reciprocating
Damage
Substantial damage
Airport
Sky Harbor

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.