MKC68F0250

NTSB accident investigation · Piper PA-18 · Spearfish, SD · October 11, 1967

Accident · No injuriesClosed
Date
October 11, 1967
Place
Spearfish, SD · SPEARFISH, SD
Injuries
1 uninjured
Damage
Substantial damage
Phase of flight
Landing
Aircraft
N1752PPiper PA-18
Status
Completed · report December 26, 1967
Report
Brief approved by the director
Case key
113177

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-3638  67/10/11   SPEARFISH,S DAK     PIPER PA-18         CR-  0  0  1  NONCOMMERCIAL             PRIVATE, AGE 56, 875
        TIME - 0845                    N1752P              PX-  0  0  0  BUSINESS                  TOTAL HOURS, 87 IN TYPE,
                                       DAMAGE-SUBSTANTIAL  OT-  0  0  0                            NOT INSTRUMENT RATED.
        NAME OF AIRPORT - BLACK HILLS
        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
N1752P
Reported as
Piper PA-18
Category
Airplane
Engine
reciprocating
Damage
Substantial damage
Airport
Black Hills

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.