SEA79FTA01

NTSB accident investigation · Piper J-3 · Belfry, MT · September 28, 1978

Accident · No injuriesClosed
Date
September 28, 1978
Place
Belfry, MT · BELFRY, MT
Injuries
1 uninjured
Damage
Substantial damage
Phase of flight
Landing
Aircraft
N33160Piper J-3
Status
Completed · report November 1, 1978
Report
Brief approved by the director
FAA report
19780928029589A
Case key
138999

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-2637  78/9/28  NR.BELFRY,MT          PIPER J-3           CR-  0  0  1  NONCOMMERCIAL             PRIVATE, AGE 37, 2380
        TIME - 1630                    N33160              PX-  0  0  0  PLEASURE/PERSONAL TRANSP  TOTAL HOURS, 20 IN TYPE,
                                       DAMAGE-SUBSTANTIAL  OT-  0  0  0                            INSTRUMENT RATED.
        DEPARTURE POINT
          RED LODGE,MT
        TYPE OF ACCIDENT                                         PHASE OF OPERATION
           GEAR COLLAPSED                                           LANDING: ROLL
        PROBABLE CAUSE(S)
           PILOT IN COMMAND - SELECTED UNSUITABLE TERRAIN
        FACTOR(S)
           TERRAIN - ROUGH/UNEVEN
           MISCELLANEOUS ACTS,CONDITIONS - OVERLOAD FAILURE
        REMARKS- LND ON RANCH ROAD.

Aircraft

Registration
N33160
Reported as
Piper J-3
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.

FAA reports on this event · 1

The FAA’s own accident and incident reports, matched to the aircraft by N-number and date.