MKC69F0457

NTSB accident investigation · Mooney M-20C · Lake Andes, SD · May 5, 1969

Accident · No injuriesClosed
Date
May 5, 1969
Place
Lake Andes, SD · LAKE ANDES, SD
Injuries
2 uninjured
Damage
Substantial damage
Phase of flight
Initial climb
Aircraft
N7820VMooney M-20C
Status
Completed · report July 9, 1969
Report
Brief approved by the director
Case key
183353

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-1327   69/5/5    LAKE ANDES,S DAK    MOONEY M-20C        CR-  0  0  1  NONCOMMERCIAL             PRIVATE, AGE 38, 1805
        TIME - 1400                    N7820V              PX-  0  0  1  PLEASURE/PERSONAL TRANSP  TOTAL HOURS, 480 IN TYPE,
                                       DAMAGE-SUBSTANTIAL  OT-  0  0  0                            NOT INSTRUMENT RATED.
        NAME OF AIRPORT - LAKE ANDES
        TYPE OF ACCIDENT                                         PHASE OF OPERATION
           STALL: MUSH                                              TAKEOFF: INITIAL CLIMB
        PROBABLE CAUSE(S)
           PILOT IN COMMAND - FAILED TO OBTAIN/MAINTAIN FLYING SPEED
        FACTOR(S)
           PILOT IN COMMAND - SELECTED WRONG RUNWAY RELATIVE TO EXISTING WIND
           MISCELLANEOUS ACTS,CONDITIONS - DOWNWIND
        REMARKS- WIND 4K.

Aircraft

Registration
N7820V
Reported as
Mooney M-20C
Category
Airplane
Engine
reciprocating
Damage
Substantial damage
Airport
Lake Andes

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.