- Date
- July 8, 1973
- Place
- Libby, MT · LIBBY, MT
- Injuries
- 2 uninjured
- Damage
- Substantial damage
- Phase of flight
- Enroute
- Aircraft
- N8353XCessna 172
- Status
- Completed · report October 26, 1973
- Report
- Brief approved by the director
- FAA report
- 19730708019849A
- Case key
- 188996
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-2740 73/7/8 LIBBY,MONT CESSNA 172 CR- 0 0 1 NONCOMMERCIAL PRIVATE, AGE 36, 501 TIME - 0810 N8353X PX- 0 0 1 PLEASURE/PERSONAL TRANSP TOTAL HOURS, 25 IN TYPE, DAMAGE-SUBSTANTIAL OT- 0 0 0 NOT INSTRUMENT RATED. NAME OF AIRPORT - ABANDON AIR STRIP DEPARTURE POINT INTENDED DESTINATION LIBBY,MONT LOCAL TYPE OF ACCIDENT PHASE OF OPERATION COLLIDED WITH: WIRES/POLES IN FLIGHT: NORMAL CRUISE GEAR COLLAPSED LANDING: LEVEL OFF/TOUCHDOWN PROBABLE CAUSE(S) PILOT IN COMMAND - DIVERTED ATTENTION FROM OPERATION OF AIRCRAFT PILOT IN COMMAND - FAILED TO SEE AND AVOID OBJECTS OR OBSTRUCTIONS MISCELLANEOUS ACTS,CONDITIONS - UNWARRANTED LOW FLYING MISCELLANEOUS ACTS,CONDITIONS - PREVIOUS DAMAGE FACTOR(S) TERRAIN - HIGH OBSTRUCTIONS AIRPORTS/AIRWAYS/FACILITIES - AIRPORT CONDITIONS: HIGH VEGETATION MISCELLANEOUS ACTS,CONDITIONS - OVERLOAD FAILURE EMERGENCY CIRCUMSTANCES - PRECAUTIONARY LANDING ON AIRPORT SUSPECTED OR KNOWN AIRCRAFT DAMAGE REMARKS- HIT PWR LINES OVR RIVER.NS GR COLLAPSED LDG ON 12IN HIGH GRASS STRIP.
Aircraft
- Registration
- N8353X
- Reported as
- Cessna 172
- Category
- Airplane
- Engine
- reciprocating
- Damage
- Substantial damage
- Airport
- Abandon Air 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.
FAA reports on this event · 1
The FAA’s own accident and incident reports, matched to the aircraft by N-number and date.