OAK68D0027

NTSB accident investigation · Waco SRE · Merced, CA · June 4, 1967

Accident · No injuriesClosed
Date
June 4, 1967
Place
Merced, CA · MERCED, CA
Injuries
2 uninjured
Damage
Substantial damage
Phase of flight
Approach
Aircraft
N20967Waco SRE
Status
Completed · report September 22, 1967
Report
Brief approved by the director
Case key
116662

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-1898   67/6/4    MERCED,CALIF        WACO SRE            CR-  0  0  1  NONCOMMERCIAL             COMMERCIAL, AGE 43, 1500
        TIME - 1200                    N20967              PX-  0  0  1  PLEASURE/PERSONAL TRANSP  TOTAL HOURS, 100 IN TYPE,
                                       DAMAGE-SUBSTANTIAL  OT-  0  0  0                            NOT INSTRUMENT RATED.
        NAME OF AIRPORT - MERCED MUNICIPAL
        TYPE OF ACCIDENT                                         PHASE OF OPERATION
           UNDERSHOOT                                               LANDING: FINAL APPROACH
           COLLIDED WITH: RUNWAY OR APPROACH LIGHTS                 LANDING: FINAL APPROACH
        PROBABLE CAUSE(S)
           PILOT IN COMMAND - MISJUDGED DISTANCE AND ALTITUDE
        REMARKS- RT GEAR KNOCKED OFF.FURTHER DAMAGE ON LANDING.

Aircraft

Registration
N20967
Reported as
Waco SRE
Category
Airplane
Engine
reciprocating
Damage
Substantial damage
Airport
Merced Municipal

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.