OAK72DVW28

NTSB accident investigation · Beech 3NM · Coso Junctn, CA · April 17, 1972

Accident · Minor injuriesClosed
Date
April 17, 1972
Place
Coso Junctn, CA · COSO JUNCTN, CA
Injuries
2 minor
Damage
Substantial damage
Phase of flight
Landing
Aircraft
N16144Beech 3NM
Status
Completed · report February 3, 1973
Report
Brief approved by the director
Case key
166355

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-1470  72/4/17    COSO JUNCTN,CALIF   BEECH 3NM           CR-  0  0  1  NONCOMMERCIAL             COMMERCIAL, AGE 43, 250
        TIME - 1000                    N16144              PX-  0  0  1  PLEASURE/PERSONAL TRANSP  TOTAL HOURS, 39 IN TYPE,
                                       DAMAGE-SUBSTANTIAL  OT-  0  0  0                            NOT INSTRUMENT RATED.
        NAME OF AIRPORT - GILL STRIP
        DEPARTURE POINT             INTENDED DESTINATION
          TRONA,CALIF                 COSO JUNCTN,CALIF
        TYPE OF ACCIDENT                                         PHASE OF OPERATION
           NOSE OVER/DOWN                                           LANDING: ROLL
        PROBABLE CAUSE(S)
           PILOT IN COMMAND - IMPROPER OPERATION OF BRAKES AND/OR FLIGHT CONTROLS

Aircraft

Registration
N16144
Reported as
Beech 3NM
Category
Airplane
Engine
reciprocating
Damage
Substantial damage
Airport
Gill Strip

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.