OAK69D0259

NTSB accident investigation · Cessna 140A · Exeter, CA · March 24, 1969

Accident · No injuriesClosed
Date
March 24, 1969
Place
Exeter, CA · EXETER, CA
Injuries
1 uninjured
Damage
Substantial damage
Phase of flight
Landing
Aircraft
N1136DCessna 140A
Status
Completed · report May 13, 1969
Report
Brief approved by the director
Case key
190681

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-0388  69/3/24    EXETER,CALIF        CESSNA 140A         CR-  0  0  1  INSTRUCTIONAL             STUDENT, AGE 40, 55 TOTAL
        TIME - 1430                    N1136D              PX-  0  0  0  SOLO                      HOURS, ALL IN TYPE, NOT
                                       DAMAGE-SUBSTANTIAL  OT-  0  0  0                            INSTRUMENT RATED.
        NAME OF AIRPORT - PRUNER
        TYPE OF ACCIDENT                                         PHASE OF OPERATION
           GROUND-WATER LOOP-SWERVE                                 LANDING: ROLL
           GEAR COLLAPSED                                           LANDING: ROLL
        PROBABLE CAUSE(S)
           PILOT IN COMMAND - FAILED TO MAINTAIN DIRECTIONAL CONTROL
        FACTOR(S)
           MISCELLANEOUS ACTS,CONDITIONS - OVERLOAD FAILURE

Aircraft

Registration
N1136D
Reported as
Cessna 140A
Category
Airplane
Engine
reciprocating
Damage
Substantial damage
Airport
Pruner

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.