OAK68F0074

NTSB accident investigation · Cessna 140 · San Carlos, CA · July 8, 1967

Accident · Serious injuriesClosed
Date
July 8, 1967
Place
San Carlos, CA · SAN CARLOS, CA
Injuries
1 serious, 1 uninjured
Damage
Substantial damage
Phase of flight
Initial climb
Aircraft
N81043Cessna 140
Status
Completed · report October 9, 1967
Report
Brief approved by the director
Case key
118562

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-0503   67/7/8    SAN CARLOS,CALIF    CESSNA 140          CR-  0  1  0  MISCELLANEOUS             PRIVATE, AGE 68, 1000
        TIME - 0905                    N81043              PX-  0  0  1  DEMONSTRATION             TOTAL HOURS, 150 IN TYPE,
                                       DAMAGE-SUBSTANTIAL  OT-  0  0  0                            NOT INSTRUMENT RATED.
        NAME OF AIRPORT - SAN CARLOS
        TYPE OF ACCIDENT                                         PHASE OF OPERATION
           STALL: SPIN                                              TAKEOFF: INITIAL CLIMB
        PROBABLE CAUSE(S)
           PILOT IN COMMAND - FAILED TO OBTAIN/MAINTAIN FLYING SPEED
        REMARKS- PX A PROSPECTIVE BUYER MADE ERRATIC TAKEOFF RUN.PLT AT FLT CONTROLS WHEN ACFT AIRBORNE UNDETERMINE

Aircraft

Registration
N81043
Reported as
Cessna 140
Category
Airplane
Engine
reciprocating
Damage
Substantial damage
Airport
San Carlos

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.