MIA72FKW28

NTSB accident investigation · Piper J3C-65 · Elizabethton, TN · May 23, 1972

Accident · No injuriesClosed
Date
May 23, 1972
Place
Elizabethton, TN · ELIZABETHTON, TN
Injuries
1 uninjured
Damage
Substantial damage
Phase of flight
Approach
Aircraft
N98429Piper J3C-65
Status
Completed · report February 16, 1973
Report
Brief approved by the director
Case key
167407

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-2225  72/5/23    ELIZABETHTON,TENN   PIPER J3C-65        CR-  0  0  1  INSTRUCTIONAL             COMMERCIAL, AGE 30, 376
        TIME - 1045                    N98429              PX-  0  0  0  TRAINING                  TOTAL HOURS, 72 IN TYPE,
                                       DAMAGE-SUBSTANTIAL  OT-  0  0  0                            INSTRUMENT RATED.
        NAME OF AIRPORT - ELIZABETHTON
        DEPARTURE POINT             INTENDED DESTINATION
          ELIZABETHTON,TENN           LOCAL
        TYPE OF ACCIDENT                                         PHASE OF OPERATION
           STALL                                                    LANDING: GO-AROUND
        PROBABLE CAUSE(S)
           PILOT IN COMMAND - FAILED TO OBTAIN/MAINTAIN FLYING SPEED
        REMARKS- PRACT SHORT FLD GO-AROUNDS.

Aircraft

Registration
N98429
Reported as
Piper J3C-65
Category
Airplane
Engine
reciprocating
Damage
Substantial damage
Airport
Elizabethton

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.