CHI68F0414

NTSB accident investigation · Luscombe 8A · Arlington, WI · October 21, 1967

Accident · No injuriesClosed
Date
October 21, 1967
Place
Arlington, WI · ARLINGTON, WI
Injuries
1 uninjured
Damage
Substantial damage
Phase of flight
Enroute
Aircraft
N1343BLuscombe 8A
Status
Completed · report January 4, 1968
Report
Brief approved by the director
Case key
113274

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-3781  67/10/21   ARLINGTON,WIS       LUSCOMBE 8A         CR-  0  0  1  NONCOMMERCIAL             PRIVATE, AGE 39, 201
        TIME - 1630                    N1343B              PX-  0  0  0  PLEASURE/PERSONAL TRANSP  TOTAL HOURS, 177 IN TYPE,
                                       DAMAGE-SUBSTANTIAL  OT-  0  0  0                            NOT INSTRUMENT RATED.
        NAME OF AIRPORT - LODI
        TYPE OF ACCIDENT                                         PHASE OF OPERATION
           STALL: SPIRAL                                            IN FLIGHT: NORMAL CRUISE
        PROBABLE CAUSE(S)
           PILOT IN COMMAND - FAILED TO OBTAIN/MAINTAIN FLYING SPEED
        FACTOR(S)
           MISCELLANEOUS ACTS,CONDITIONS - PILOT FATIGUE
        REMARKS- PLT HAD NO REST THE PREVIOUS NIGHT.

Aircraft

Registration
N1343B
Reported as
Luscombe 8A
Category
Airplane
Engine
reciprocating
Damage
Substantial damage
Airport
Lodi

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.