MKC68D0556

NTSB accident investigation · Luscombe 8A · David City, NE · April 29, 1968

Accident · No injuriesClosed
Date
April 29, 1968
Place
David City, NE · DAVID CITY, NE
Injuries
1 uninjured
Damage
Substantial damage
Phase of flight
Landing
Aircraft
N71600Luscombe 8A
Status
Completed · report June 28, 1968
Report
Brief approved by the director
Case key
110810

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-1173  68/4/29    DAVID CITY,NEBR     LUSCOMBE 8A         CR-  0  0  1  NONCOMMERCIAL             PRIVATE, AGE 63, 440
        TIME - 1600                    N71600              PX-  0  0  0  PLEASURE/PERSONAL TRANSP  TOTAL HOURS, 7 IN TYPE,
                                       DAMAGE-SUBSTANTIAL  OT-  0  0  0                            NOT INSTRUMENT RATED.
        NAME OF AIRPORT - DAVID CITY
        TYPE OF ACCIDENT                                         PHASE OF OPERATION
           HARD LANDING                                             LANDING: LEVEL OFF/TOUCHDOWN
           NOSE OVER/DOWN                                           LANDING: LEVEL OFF/TOUCHDOWN
        PROBABLE CAUSE(S)
           PILOT IN COMMAND - IMPROPER LEVEL OFF
           PILOT IN COMMAND - IMPROPER RECOVERY FROM BOUNCED LANDING

Aircraft

Registration
N71600
Reported as
Luscombe 8A
Category
Airplane
Engine
reciprocating
Damage
Substantial damage
Airport
David City

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.