LAX67F0310

NTSB accident investigation · Cessna 150F · Hawthorne, CA · February 26, 1967

Accident · No injuriesClosed
Date
February 26, 1967
Place
Hawthorne, CA · HAWTHORNE, CA
Injuries
2 uninjured
Damage
Substantial damage
Phase of flight
Landing
Aircraft
N6687FCessna 150F
Status
Completed · report August 14, 1967
Report
Brief approved by the director
Case key
118419

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-0611  67/2/26    HAWTHORNE,CALIF     CESSNA 150F         CR-  0  0  1  NONCOMMERCIAL             PRIVATE, AGE 36, 48 TOTAL
        TIME - 1228                    N6687F              PX-  0  0  1  PLEASURE/PERSONAL TRANSP  HOURS, ALL IN TYPE, NOT
                                       DAMAGE-SUBSTANTIAL  OT-  0  0  0                            INSTRUMENT RATED.
        NAME OF AIRPORT - HAWTHORNE
        TYPE OF ACCIDENT                                         PHASE OF OPERATION
           HARD LANDING                                             LANDING: LEVEL OFF/TOUCHDOWN
           GEAR COLLAPSED                                           LANDING: LEVEL OFF/TOUCHDOWN
        PROBABLE CAUSE(S)
           PILOT IN COMMAND - IMPROPER LEVEL OFF
        FACTOR(S)
           MISCELLANEOUS ACTS,CONDITIONS - OVERLOAD FAILURE

Aircraft

Registration
N6687F
Reported as
Cessna 150F
Category
Airplane
Engine
reciprocating
Damage
Substantial damage
Airport
Hawthorne

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.