FTW66F0095

NTSB accident investigation · Piper PA-22 · Corpuschristi, TX · June 9, 1965

Accident · Serious injuriesClosed
Date
June 9, 1965
Place
Corpuschristi, TX · CORPUSCHRISTI, TX
Injuries
1 serious, 1 uninjured
Damage
No damage
Phase of flight
Standing
Aircraft
N6037DPiper PA-22
Status
Completed · report August 12, 1965
Report
Brief approved by the director
Case key
178046

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
----------------------------------------------------------------------------------------------------------------------------
2-0293   65/6/9    CORPUSCHRISTI TEX   PIPER PA-22         CR-  0  0  1  NONCOMMERCIAL             COMMERCIAL, AGE 42, 2050
        TIME - 2200                    N6037D              PX-  0  1  0  BUSINESS                  TOTAL HOURS, 25 IN TYPE,
                                       DAMAGE-NONE         OT-  0  0  0                            NOT INSTRUMENT RATED.
        NAME OF AIRPORT - CUDDIHY FIELD
        TYPE OF ACCIDENT                                         PHASE OF OPERATION
           PROPELLER/ROTOR ACCIDENT TO PERSON                       STATIC: IDLING ENGINE(S)
        PROBABLE CAUSE(S)
           PERSONNEL - MISCELLANEOUS-PERSONNEL: PASSENGER
        REMARKS- PAX DEPLANED TO DIRECT PLT TO TIE-DOWN AREA.PILOT DID NOT USE AIRCRAFT LIGHTS TOILLUME DARK AREA

Aircraft

Registration
N6037D
Reported as
Piper PA-22
Category
Airplane
Engine
reciprocating
Damage
No damage
Airport
Cuddihy Field

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.