- Date
- September 9, 1972
- Place
- Jamul, CA · JAMUL, CA
- Injuries
- 3 fatal
- Damage
- Destroyed
- Phase of flight
- Enroute
- Aircraft
- N9731DPiper PA-22
- Status
- Completed · report January 15, 1973
- Report
- Brief approved by the director
- Case key
- 167688
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-1135 72/9/9 NR.JAMUL,CALIF PIPER PA-22 CR- 2 0 0 NONCOMMERCIAL COMMERCIAL, AGE 35, 800 TIME - 1251 N9731D PX- 1 0 0 PLEASURE/PERSONAL TRANSP TOTAL HOURS, UNK/NR IN DAMAGE-DESTROYED OT- 0 0 0 TYPE, NOT INSTRUMENT RATED. DEPARTURE POINT INTENDED DESTINATION IMPERIAL,CALIF SANTEE,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) MISCELLANEOUS ACTS,CONDITIONS - FLEW INTO BLIND CANYON WEATHER - LOW CEILING WEATHER - RAIN WEATHER - FOG WEATHER BRIEFING - BRIEFED BY FLIGHT SERVICE PERSONNEL, BY PHONE WEATHER FORECAST - FORECAST SUBSTANTIALLY CORRECT SKY CONDITION CEILING AT ACCIDENT SITE OBSCURATION 0 VISIBILITY AT ACCIDENT SITE PRECIPITATION AT ACCIDENT SITE ZERO DRIZZLE OBSTRUCTIONS TO VISION AT ACCIDENT SITE TYPE OF WEATHER CONDITIONS FOG IFR TYPE OF FLIGHT PLAN NONE FIRE AFTER IMPACT REMARKS- FSS WEA TOLD PLT VFR FLT ENROUTE AND DEST NOT POSSIBLE. FLEW INTO STEEP OBSCURED CANYON SLOPE.
Aircraft
- Registration
- N9731D
- Reported as
- Piper PA-22
- 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.