MIA69F0197

NTSB accident investigation · Piper J3C-65 · Headland, AL · October 20, 1968

Accident · Serious injuriesClosed
Date
October 20, 1968
Place
Headland, AL · HEADLAND, AL
Injuries
1 serious
Damage
Substantial damage
Phase of flight
Approach
Aircraft
N92043Piper J3C-65
Status
Completed · report December 26, 1968
Report
Brief approved by the director
Case key
107991

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-3744  68/10/20   HEADLAND,ALA        PIPER J3C-65        CR-  0  1  0  INSTRUCTIONAL             NO CERTIFICATE, AGE 46,
        TIME - 1600                    N92043              PX-  0  0  0  TRAINING                  400 TOTAL HOURS, 250 IN
                                       DAMAGE-SUBSTANTIAL  OT-  0  0  0                            TYPE, NOT INSTRUMENT
                                                                                                   RATED.
        TYPE OF ACCIDENT                                         PHASE OF OPERATION
           UNDERSHOOT                                               LANDING: FINAL APPROACH
           COLLIDED WITH: WIRES/POLES                               LANDING: FINAL APPROACH
        PROBABLE CAUSE(S)
           PILOT IN COMMAND - MISJUDGED DISTANCE AND ALTITUDE

Aircraft

Registration
N92043
Reported as
Piper J3C-65
Category
Airplane
Engine
reciprocating
Damage
Substantial damage

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.