CHI68F0258

NTSB accident investigation · Sparks D · Marion, OH · September 17, 1967

Accident · No injuriesClosed
Date
September 17, 1967
Place
Marion, OH · MARION, OH
Injuries
1 uninjured
Damage
Substantial damage
Phase of flight
Landing
Aircraft
N832ZSparks D
Status
Completed · report December 13, 1967
Report
Brief approved by the director
Case key
114295

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-3333  67/9/17    MARION,OHIO         SPARKS D            CR-  0  0  1  NONCOMMERCIAL             PRIVATE, AGE 35, 152
        TIME - 1000                    N832Z               PX-  0  0  0  PLEASURE/PERSONAL TRANSP  TOTAL HOURS, 41 IN TYPE,
                                       DAMAGE-SUBSTANTIAL  OT-  0  0  0                            NOT INSTRUMENT RATED.
        NAME OF AIRPORT - MARION
        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
N832Z
Reported as
Sparks D
Category
Airplane
Engine
reciprocating
Damage
Substantial damage
Airport
Marion

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.