SEA70F0027

NTSB accident investigation · Cessna 180 · Birney, MT · July 22, 1969

Accident · No injuriesClosed
Date
July 22, 1969
Place
Birney, MT · BIRNEY, MT
Injuries
1 uninjured
Damage
Substantial damage
Phase of flight
Landing
Aircraft
N5194ECessna 180
Status
Completed · report September 16, 1969
Report
Brief approved by the director
Case key
169680

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-2311  69/7/22    BIRNEY,MONT         CESSNA 180          CR-  0  0  1  NONCOMMERCIAL             PRIVATE, AGE 66, 2300
        TIME - 1615                    N5194E              PX-  0  0  0  BUSINESS                  TOTAL HOURS, 700 IN TYPE,
                                       DAMAGE-SUBSTANTIAL  OT-  0  0  0                            NOT INSTRUMENT RATED.
        NAME OF AIRPORT - QUARTER CIRCLE
        TYPE OF ACCIDENT                                         PHASE OF OPERATION
           HARD LANDING                                             LANDING: LEVEL OFF/TOUCHDOWN
           GEAR COLLAPSED                                           LANDING: LEVEL OFF/TOUCHDOWN
        PROBABLE CAUSE(S)
           PILOT IN COMMAND - IMPROPER LEVEL OFF
        FACTOR(S)
           MISCELLANEOUS ACTS,CONDITIONS - OVERLOAD FAILURE

Aircraft

Registration
N5194E
Reported as
Cessna 180
Category
Airplane
Engine
reciprocating
Damage
Substantial damage
Airport
Quarter Circle

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.