- Date
- February 13, 1972
- Place
- Morrison, TN · MORRISON, TN
- Injuries
- 2 fatal
- Damage
- Destroyed
- Phase of flight
- Uncontrolled descent
- Aircraft
- N9044XCessna 182D
- Status
- Completed · report September 11, 1972
- Report
- Brief approved by the director
- Case key
- 164710
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-0053 72/2/13 MORRISON,TENN CESSNA 182D CR- 1 0 0 NONCOMMERCIAL PRIVATE, AGE 37, 270 TIME - 0830 N9044X PX- 1 0 0 BUSINESS TOTAL HOURS, ALL IN TYPE, DAMAGE-DESTROYED OT- 0 0 0 INSTRUMENT RATED. DEPARTURE POINT INTENDED DESTINATION NASHVILLE,TENN ALBANY,GA TYPE OF ACCIDENT PHASE OF OPERATION COLLISION WITH GROUND/WATER: UNCONTROLLED IN FLIGHT: UNCONTROLLED DESCENT PROBABLE CAUSE(S) PILOT IN COMMAND - ATTEMPTED OPERATION W/KNOWN DEFICIENCIES IN EQUIPMENT WEATHER - ICING CONDITIONS-INCLUDES SLEET,FREEZING RAIN,ETC. MISCELLANEOUS ACTS,CONDITIONS - AIRFRAME ICE WEATHER BRIEFING - BRIEFED BY FLIGHT SERVICE PERSONNEL, BY PHONE WEATHER FORECAST - FORECAST SUBSTANTIALLY CORRECT SKY CONDITION CEILING AT ACCIDENT SITE OVERCAST 800 VISIBILITY AT ACCIDENT SITE PRECIPITATION AT ACCIDENT SITE 2 MILES OR LESS RAIN OBSTRUCTIONS TO VISION AT ACCIDENT SITE TYPE OF WEATHER CONDITIONS FOG IFR TYPE OF FLIGHT PLAN IFR FIRE AFTER IMPACT REMARKS- FILED INTO KNOWN ICING CONDITIONS.PLT RPRTD RIME ICG AT 7000FT,CLRD TO 4000FT,CONTACT LOST.
Aircraft
- Registration
- N9044X
- Reported as
- Cessna 182D
- Category
- Airplane
- Engine
- reciprocating
- Damage
- Destroyed
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.