OAK66F0004

NTSB accident investigation · Luscombe 8A · Modesto, CA · June 13, 1965

Accident · No injuriesClosed
Date
June 13, 1965
Place
Modesto, CA · MODESTO, CA
Injuries
1 uninjured
Damage
Destroyed
Phase of flight
Initial climb
Aircraft
N1141BLuscombe 8A
Status
Completed · report August 4, 1965
Report
Brief approved by the director
Case key
177383

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-1433  65/6/13  NR.MODESTO CALIF      LUSCOMBE 8A         CR-  0  0  1  NONCOMMERCIAL             PRIVATE, AGE 39, 300
        TIME - 1400                    N1141B              PX-  0  0  0  PLEASURE/PERSONAL TRANSP  TOTAL HOURS, 171 IN TYPE,
                                       DAMAGE-DESTROYED    OT-  0  0  0                            NOT INSTRUMENT RATED.
        TYPE OF ACCIDENT                                         PHASE OF OPERATION
           ENGINE FAILURE OR MALFUNCTION                            TAKEOFF: INITIAL CLIMB
           COLLIDED WITH: DITCHES                                   LANDING: ROLL
        PROBABLE CAUSE(S)
           POWERPLANT - MISCELLANEOUS: POWERPLANT FAILURE FOR UNDETERMINED REASONS
        COMPLETE POWER LOSS - COMPLETE ENGINE FAILURE/FLAMEOUT-1 ENGINE
        EMERGENCY CIRCUMSTANCES - FORCED LANDING OFF AIRPORT ON LAND

Aircraft

Registration
N1141B
Reported as
Luscombe 8A
Category
Airplane
Engine
reciprocating
Damage
Destroyed

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.