MIA67D0564

NTSB accident investigation · Stinson 108-3 · Satsuma, FL · May 20, 1967

Accident · Minor injuriesClosed
Date
May 20, 1967
Place
Satsuma, FL · SATSUMA, FL
Injuries
2 minor
Damage
Substantial damage
Phase of flight
Landing
Aircraft
N6964MStinson 108-3
Status
Completed · report September 18, 1967
Report
Brief approved by the director
Case key
116480

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-1719  67/5/20    SATSUMA,FLA         STINSON 108-3       CR-  0  0  1  NONCOMMERCIAL             PRIVATE, AGE 32, 266
        TIME - 1050                    N6964M              PX-  0  0  1  PLEASURE/PERSONAL TRANSP  TOTAL HOURS, 169 IN TYPE,
                                       DAMAGE-SUBSTANTIAL  OT-  0  0  0                            NOT INSTRUMENT RATED.
        NAME OF AIRPORT - M Q RANCH
        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
N6964M
Reported as
Stinson 108-3
Category
Airplane
Engine
reciprocating
Damage
Substantial damage
Airport
M Q Ranch

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.