MIA71FKQ34

NTSB accident investigation · Piper J3C · Minter City, MS · May 14, 1971

Accident · Minor injuriesClosed
Date
May 14, 1971
Place
Minter City, MS · MINTER CITY, MS
Injuries
1 minor
Damage
Substantial damage
Phase of flight
Approach
Aircraft
N33598Piper J3C
Status
Completed · report January 11, 1972
Report
Brief approved by the director
Case key
161563

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-1609  71/5/14    MINTER CITY,MISS    PIPER J3C           CR-  0  0  1  NONCOMMERCIAL             STUDENT, AGE 37, 50 TOTAL
        TIME - 1930                    N33598              PX-  0  0  0  PLEASURE/PERSONAL TRANSP  HOURS, 47 IN TYPE, NOT
                                       DAMAGE-SUBSTANTIAL  OT-  0  0  0                            INSTRUMENT RATED.
        NAME OF AIRPORT - PVT STRIP
        DEPARTURE POINT             INTENDED DESTINATION
          MINTER CITY,MISS            LOCAL
        TYPE OF ACCIDENT                                         PHASE OF OPERATION
           COLLIDED WITH: WIRES/POLES                               LANDING: FINAL APPROACH
        PROBABLE CAUSE(S)
           PILOT IN COMMAND - FAILED TO SEE AND AVOID OBJECTS OR OBSTRUCTIONS
           TERRAIN - HIGH OBSTRUCTIONS

Aircraft

Registration
N33598
Reported as
Piper J3C
Category
Airplane
Engine
reciprocating
Damage
Substantial damage
Airport
Pvt Strip

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.