LAX69D0061

NTSB accident investigation · Boeing A75N1 · Blythe, CA · July 18, 1968

Accident · No injuriesClosed
Date
July 18, 1968
Place
Blythe, CA · BLYTHE, CA
Injuries
1 uninjured
Damage
Substantial damage
Phase of flight
Initial climb
Aircraft
N48788Boeing A75N1
Status
Completed · report September 20, 1968
Report
Brief approved by the director
Case key
109165

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-2328  68/7/18    BLYTHE,CALIF        BOEING A75N1        CR-  0  0  1  COMMERCIAL                COMMERCIAL, AGE 39, 6400
        TIME - 0815                    N48788              PX-  0  0  0  ASSOC CROP CTL ACTIVITY   TOTAL HOURS, 35 IN TYPE,
                                       DAMAGE-SUBSTANTIAL  OT-  0  0  0                            NOT INSTRUMENT RATED.
        NAME OF AIRPORT - HERON
        TYPE OF ACCIDENT                                         PHASE OF OPERATION
           COLLIDED WITH: AUTOMOBILE                                TAKEOFF: INITIAL CLIMB
        PROBABLE CAUSE(S)
           PILOT IN COMMAND - INADEQUATE PREFLIGHT PREPARATION AND/OR PLANNING
        FACTOR(S)
           PERSONNEL - MISCELLANEOUS-PERSONNEL: GROUND SIGNALMAN
        REMARKS- ACFT STRUCK FLAGMANS PICKUP ON T/O FROM ROAD. NO LOAD ABOARD.

Aircraft

Registration
N48788
Reported as
Boeing A75N1
Category
Airplane
Engine
reciprocating
Damage
Substantial damage
Airport
Heron

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.