SEA71DTI39

NTSB accident investigation · Luscombe T-8F · Chinook, MT · June 13, 1971

Accident · No injuriesClosed
Date
June 13, 1971
Place
Chinook, MT · CHINOOK, MT
Injuries
1 uninjured
Damage
Substantial damage
Phase of flight
Landing
Aircraft
N2216BLuscombe T-8F
Status
Completed · report February 9, 1972
Report
Brief approved by the director
Case key
161986

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-2009  71/6/13    CHINOOK,MONT        LUSCOMBE T-8F       CR-  0  0  1  NONCOMMERCIAL             COMMERCIAL, AGE 45, 1250
        TIME - 0500                    N2216B              PX-  0  0  0  BUSINESS                  TOTAL HOURS, 300 IN TYPE,
                                       DAMAGE-SUBSTANTIAL  OT-  0  0  0                            NOT INSTRUMENT RATED.
        NAME OF AIRPORT - CHINOOK
        DEPARTURE POINT             INTENDED DESTINATION
          CHINOOK,MONT                LOCAL
        TYPE OF ACCIDENT                                         PHASE OF OPERATION
           NOSE OVER/DOWN                                           LANDING: ROLL
        PROBABLE CAUSE(S)
           PILOT IN COMMAND - SELECTED UNSUITABLE TERRAIN
        FACTOR(S)
           TERRAIN - WET,SOFT GROUND
        REMARKS- LANDED ON SOFT FLD ADJ TO RANCH.

Aircraft

Registration
N2216B
Reported as
Luscombe T-8F
Category
Airplane
Engine
reciprocating
Damage
Substantial damage
Airport
Chinook

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.