- Date
- March 25, 1972
- Place
- Livermore, CA · LIVERMORE, CA
- Injuries
- 1 serious, 1 minor
- Damage
- Substantial damage
- Phase of flight
- Enroute
- Aircraft
- N7213TCessna 172A
- Status
- Completed · report January 18, 1972
- Report
- Brief approved by the director
- Case key
- 165612
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-1198 72/3/25 LIVERMORE,CALIF CESSNA 172A CR- 0 1 0 NONCOMMERCIAL PRIVATE, AGE 22, 268 TIME - 0237 N7213T PX- 0 0 1 PLEASURE/PERSONAL TRANSP TOTAL HOURS, 45 IN TYPE, DAMAGE-SUBSTANTIAL OT- 0 0 0 NOT INSTRUMENT RATED. NAME OF AIRPORT - HUMMINGBIRD HAVEN DEPARTURE POINT INTENDED DESTINATION LAST ENROUTE STOP CHICO,CALIF FLAGSTAFF,ARIZ NEEDLES,CALIF TYPE OF ACCIDENT PHASE OF OPERATION COLLISION WITH GROUND/WATER: CONTROLLED IN FLIGHT: NORMAL CRUISE PROBABLE CAUSE(S) PILOT IN COMMAND - CONTINUED VFR FLIGHT INTO ADVERSE WEATHER CONDITIONS FACTOR(S) WEATHER - RAIN WEATHER - FOG WEATHER BRIEFING - BRIEFED BY FLIGHT SERVICE PERSONNEL, IN PERSON WEATHER FORECAST - FORECAST SUBSTANTIALLY CORRECT SKY CONDITION CEILING AT ACCIDENT SITE UNKNOWN/NOT REPORTED UNKNOWN/NOT REPORTED VISIBILITY AT ACCIDENT SITE PRECIPITATION AT ACCIDENT SITE UNKNOWN/NOT REPORTED RAIN OBSTRUCTIONS TO VISION AT ACCIDENT SITE TYPE OF WEATHER CONDITIONS FOG VFR TYPE OF FLIGHT PLAN VFR REMARKS- PLT FOLLOWED WRONG HIGHWAY.
Aircraft
- Registration
- N7213T
- Reported as
- Cessna 172A
- Category
- Airplane
- Engine
- reciprocating
- Damage
- Substantial damage
- Airport
- Hummingbird Haven
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.