- Date
- October 3, 1972
- Place
- Salome, AZ · SALOME, AZ
- Injuries
- 1 fatal
- Damage
- Destroyed
- Phase of flight
- Uncontrolled descent
- Aircraft
- N8342UCessna 172F
- Status
- Completed · report March 12, 1973
- Report
- Brief approved by the director
- Case key
- 169047
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-2995 72/10/3 NR.SALOME,ARIZ CESSNA 172F CR- 1 0 0 NONCOMMERCIAL PRIVATE, AGE 45, 124 TIME - 1920 N8342U PX- 0 0 0 PLEASURE/PERSONAL TRANSP TOTAL HOURS, 74 IN TYPE, DAMAGE-DESTROYED OT- 0 0 0 NOT INSTRUMENT RATED. DEPARTURE POINT INTENDED DESTINATION LANCASTER,CALIF PHOENIX,ARIZ TYPE OF ACCIDENT PHASE OF OPERATION COLLISION WITH GROUND/WATER: UNCONTROLLED IN FLIGHT: UNCONTROLLED DESCENT PROBABLE CAUSE(S) PILOT IN COMMAND - CONTINUED VFR FLIGHT INTO ADVERSE WEATHER CONDITIONS PILOT IN COMMAND - SPATIAL DISORIENTATION FACTOR(S) WEATHER - RAIN WEATHER - THUNDERSTORM ACTIVITY WEATHER - TURBULENCE, ASSOCIATED W/CLOUDS AND/OR THUNDERSTORMS WEATHER BRIEFING - BRIEFED BY FLIGHT SERVICE PERSONNEL, BY PHONE WEATHER FORECAST - FORECAST SUBSTANTIALLY CORRECT SKY CONDITION CEILING AT ACCIDENT SITE OVERCAST 6000 VISIBILITY AT ACCIDENT SITE PRECIPITATION AT ACCIDENT SITE 3 MILES OR LESS RAIN SHOWERS, THUNDERSTORM OBSTRUCTIONS TO VISION AT ACCIDENT SITE TYPE OF WEATHER CONDITIONS NONE VFR TYPE OF FLIGHT PLAN VFR REMARKS- FLEW INTO KNOWN TSTM AREA.
Aircraft
- Registration
- N8342U
- Reported as
- Cessna 172F
- 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.