FTW65F0037

NTSB accident investigation · Cessna 170 · Corpus Christi, TX · April 25, 1965

Accident · No injuriesClosed
Date
April 25, 1965
Place
Corpus Christi, TX · CORPUS CHRISTI, TX
Injuries
4 uninjured
Damage
Substantial damage
Phase of flight
Landing
Aircraft
N5567CCessna 170
Status
Completed · report July 21, 1965
Report
Brief approved by the director
Case key
178514

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-1259  65/4/25    CORPUS CHRISTI TX   CESSNA 170          CR-  0  0  1  NONCOMMERCIAL             COMMERCIAL, AGE 41, 4000
        TIME - 1200                    N5567C              PX-  0  0  3  PLEASURE/PERSONAL TRANSP  TOTAL HOURS, 3 IN TYPE,
                                       DAMAGE-SUBSTANTIAL  OT-  0  0  0                            INSTRUMENT RATED.
        NAME OF AIRPORT - CUDIHY FIELD
        TYPE OF ACCIDENT                                         PHASE OF OPERATION
           GROUND-WATER LOOP-SWERVE                                 LANDING: ROLL
           GEAR COLLAPSED                                           LANDING: ROLL
        PROBABLE CAUSE(S)
           PILOT IN COMMAND - IMPROPER OPERATION OF BRAKES AND/OR FLIGHT CONTROLS
        FACTOR(S)
           MISCELLANEOUS ACTS,CONDITIONS - OVERLOAD FAILURE

Aircraft

Registration
N5567C
Reported as
Cessna 170
Category
Airplane
Engine
reciprocating
Damage
Substantial damage
Airport
Cudihy 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.