DEN69F0124

NTSB accident investigation · Luscombe 8A · Anapra, NM · October 19, 1968

Accident · No injuriesClosed
Date
October 19, 1968
Place
Anapra, NM · ANAPRA, NM
Injuries
2 uninjured
Damage
Substantial damage
Phase of flight
Landing
Aircraft
N71363Luscombe 8A
Status
Completed · report November 21, 1968
Report
Brief approved by the director
Case key
107753

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-3351  68/10/19   ANAPRA,N MEX        LUSCOMBE 8A         CR-  0  0  1  NONCOMMERCIAL             PRIVATE, AGE 37, 80 TOTAL
        TIME - 0730                    N71363              PX-  0  0  1  PLEASURE/PERSONAL TRANSP  HOURS, 21 IN TYPE, NOT
                                       DAMAGE-SUBSTANTIAL  OT-  0  0  0                            INSTRUMENT RATED.
        NAME OF AIRPORT - SUNLAND
        TYPE OF ACCIDENT                                         PHASE OF OPERATION
           GROUND-WATER LOOP-SWERVE                                 LANDING: ROLL
           NOSE OVER/DOWN                                           LANDING: ROLL
        PROBABLE CAUSE(S)
           PILOT IN COMMAND - FAILED TO MAINTAIN DIRECTIONAL CONTROL
        FACTOR(S)
           AIRPORTS/AIRWAYS/FACILITIES - AIRPORT CONDITIONS: SOFT SHOULDERS

Aircraft

Registration
N71363
Reported as
Luscombe 8A
Category
Airplane
Engine
reciprocating
Damage
Substantial damage
Airport
Sunland

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.