- Date
- February 19, 1971
- Place
- Jamul, CA · JAMUL, CA
- Injuries
- 2 fatal
- Damage
- Destroyed
- Phase of flight
- Enroute
- Aircraft
- N7378PPiper PA-24
- Status
- Completed · report September 21, 1971
- Report
- Brief approved by the director
- Case key
- 132934
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-0090 71/2/19 JAMUL,CALIF PIPER PA-24 CR- 1 0 0 NONCOMMERCIAL PRIVATE, AGE 45, 505 TIME - 1500 N7378P PX- 1 0 0 PLEASURE/PERSONAL TRANSP TOTAL HOURS, 96 IN TYPE, DAMAGE-DESTROYED OT- 0 0 0 NOT INSTRUMENT RATED. DEPARTURE POINT INTENDED DESTINATION SAN DIEGO,CALIF PHOENIX,ARIZ TYPE OF ACCIDENT PHASE OF OPERATION COLLISION WITH GROUND/WATER: CONTROLLED IN FLIGHT: OTHER PROBABLE CAUSE(S) PILOT IN COMMAND - CONTINUED VFR FLIGHT INTO ADVERSE WEATHER CONDITIONS PILOT IN COMMAND - MISJUDGED ALTITUDE FACTOR(S) WEATHER - LOW CEILING WEATHER BRIEFING - BRIEFED BY FLIGHT SERVICE PERSONNEL, BY PHONE WEATHER FORECAST - UNKNOWN/NOT REPORTED MISSING AIRCRAFT - LATER RECOVERED SKY CONDITION CEILING AT ACCIDENT SITE OVERCAST 2000 VISIBILITY AT ACCIDENT SITE PRECIPITATION AT ACCIDENT SITE 5 OR OVER(UNLIMITED) NONE OBSTRUCTIONS TO VISION AT ACCIDENT SITE TEMPERATURE-F NONE 55 WIND DIRECTION-DEGREES WIND VELOCITY-KNOTS 190 6 TYPE OF WEATHER CONDITIONS TYPE OF FLIGHT PLAN VFR NONE REMARKS- RCVRY DATE 2/21/71.HIT MTN APRX 2000FT MSL.EST CIG 200FT VIS 1/2MI,LT RAIN.ACFT HEARD BUT NOT SEEN
Aircraft
- Registration
- N7378P
- Reported as
- Piper PA-24
- 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.