FTW66D0693

NTSB accident investigation · Piper PA-30 · Ft Stockton, TX · May 12, 1966

Accident · No injuriesClosed
Date
May 12, 1966
Place
Ft Stockton, TX · FT STOCKTON, TX
Injuries
1 uninjured
Damage
Substantial damage
Phase of flight
Landing
Aircraft
N7624YPiper PA-30
Status
Completed · report July 8, 1966
Report
Brief approved by the director
Case key
172310

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-1210  66/5/12    FT STOCKTON TEX     PIPER PA-30         CR-  0  0  1  NONCOMMERCIAL             COMMERCIAL, AGE 44, 6475
        TIME - 1630                    N7624Y              PX-  0  0  0  BUSINESS                  TOTAL HOURS, 15 IN TYPE,
                                       DAMAGE-SUBSTANTIAL  OT-  0  0  0                            INSTRUMENT RATED.
        NAME OF AIRPORT - PECOS COUNTY
        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)
           AIRFRAME - LANDING GEAR: LANDING GEAR WARNING AND INDICATING COMPONENTS
        REMARKS- LANDING GEAR HORN INOPERATIVE.

Aircraft

Registration
N7624Y
Reported as
Piper PA-30
Category
Airplane
Engine
reciprocating
Damage
Substantial damage
Airport
Pecos County

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.