LAX66F0247

NTSB accident investigation · Cessna 172 · Chiriaco Sut, CA · February 2, 1966

Accident · Minor injuriesClosed
Date
February 2, 1966
Place
Chiriaco Sut, CA · CHIRIACO SUT, CA
Injuries
1 minor, 1 uninjured
Damage
Substantial damage
Phase of flight
Approach
Aircraft
N5660TCessna 172
Status
Completed · report April 1, 1966
Report
Brief approved by the director
Case key
173794

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-0254   66/2/2    CHIRIACO SUT CALI   CESSNA 172          CR-  0  0  1  NONCOMMERCIAL             PRIVATE, AGE 43, 223
        TIME - 1320                    N5660T              PX-  0  0  1  BUSINESS                  TOTAL HOURS, 63 IN TYPE,
                                       DAMAGE-SUBSTANTIAL  OT-  0  0  0                            NOT INSTRUMENT RATED.
        TYPE OF ACCIDENT                                         PHASE OF OPERATION
           OVERSHOOT                                                LANDING: FINAL APPROACH
           COLLIDED WITH: TREES                                     LANDING: GO-AROUND
        PROBABLE CAUSE(S)
           PILOT IN COMMAND - MISJUDGED DISTANCE AND SPEED
           PILOT IN COMMAND - DELAYED IN INITIATING GO-AROUND
        REMARKS- OFF AIRPORT OPERATION

Aircraft

Registration
N5660T
Reported as
Cessna 172
Category
Airplane
Engine
reciprocating
Damage
Substantial damage

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.