MKC68D0364

NTSB accident investigation · Piper J3C-65 · Curtis, NE · November 19, 1967

Accident · No injuriesClosed
Date
November 19, 1967
Place
Curtis, NE · CURTIS, NE
Injuries
1 uninjured
Damage
Substantial damage
Phase of flight
Landing
Aircraft
N35210Piper J3C-65
Status
Completed · report January 18, 1968
Report
Brief approved by the director
Case key
112871

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-4129  67/11/19   CURTIS,NEBR         PIPER J3C-65        CR-  0  0  1  NONCOMMERCIAL             COMMERCIAL, AGE 28, 316
        TIME - 1220                    N35210              PX-  0  0  0  PLEASURE/PERSONAL TRANSP  TOTAL HOURS, 25 IN TYPE,
                                       DAMAGE-SUBSTANTIAL  OT-  0  0  0                            NOT INSTRUMENT RATED.
        NAME OF AIRPORT - CURTIS
        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
N35210
Reported as
Piper J3C-65
Category
Airplane
Engine
reciprocating
Damage
Substantial damage
Airport
Curtis

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.