SEA66F0085

NTSB accident investigation · Luscombe 8A · Deer Park, WA · August 7, 1965

Accident · Minor injuriesClosed
Date
August 7, 1965
Place
Deer Park, WA · DEER PARK, WA
Injuries
1 minor
Damage
Substantial damage
Phase of flight
Landing
Aircraft
N25229Luscombe 8A
Status
Completed · report October 19, 1965
Report
Brief approved by the director
Case key
176700

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-2541   65/8/7    DEER PARK WASH      LUSCOMBE 8A         CR-  0  0  1  NONCOMMERCIAL             STUDENT, AGE 25, 27 TOTAL
        TIME - 0715                    N25229              PX-  0  0  0  PLEASURE/PERSONAL TRANSP  HOURS, ALL IN TYPE, NOT
                                       DAMAGE-SUBSTANTIAL  OT-  0  0  0                            INSTRUMENT RATED.
        TYPE OF ACCIDENT                                         PHASE OF OPERATION
           OVERSHOOT                                                LANDING: ROLL
           NOSE OVER/DOWN                                           LANDING: ROLL
        PROBABLE CAUSE(S)
           PILOT IN COMMAND - MISJUDGED DISTANCE AND SPEED
           PILOT IN COMMAND - FAILED TO INITIATE GO-AROUND
        FACTOR(S)
           MISCELLANEOUS ACTS,CONDITIONS - DOWNWIND
        REMARKS- OFF AIRPORT OPERATION

Aircraft

Registration
N25229
Reported as
Luscombe 8A
Category
Airplane
Engine
reciprocating
Damage
Substantial damage

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.