- Date
- November 13, 1971
- Place
- Solvang, CA · SOLVANG, CA
- Injuries
- 4 fatal
- Damage
- Destroyed
- Phase of flight
- Uncontrolled descent
- Aircraft
- N3626RPiper PA-28
- Status
- Completed · report June 27, 1972
- Report
- Brief approved by the director
- Case key
- 164134
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-4104 71/11/13 NR.SOLVANG,CALIF PIPER PA-28 CR- 1 0 0 NONCOMMERCIAL PRIVATE, AGE 39, 869 TIME - 1920 N3626R PX- 3 0 0 PLEASURE/PERSONAL TRANSP TOTAL HOURS, 5 IN TYPE, DAMAGE-DESTROYED OT- 0 0 0 INSTRUMENT RATED. DEPARTURE POINT INTENDED DESTINATION SAN DIEGO,CALIF SAN LUIS OBISPO,CAL TYPE OF ACCIDENT PHASE OF OPERATION COLLISION WITH GROUND/WATER: UNCONTROLLED IN FLIGHT: UNCONTROLLED DESCENT PROBABLE CAUSE(S) PILOT IN COMMAND - CONTINUED FLIGHT INTO KNOWN AREAS OF SEVERE TURBULENCE FACTOR(S) WEATHER - TURBULENCE IN FLIGHT,CLEAR AIR WEATHER - DOWNDRAFT,UPDRAFTS WEATHER BRIEFING - BRIEFED BY FLIGHT SERVICE PERSONNEL, IN PERSON WEATHER FORECAST - FORECAST SUBSTANTIALLY CORRECT MISSING AIRCRAFT - LATER RECOVERED SKY CONDITION CEILING AT ACCIDENT SITE CLEAR UNLIMITED VISIBILITY AT ACCIDENT SITE PRECIPITATION AT ACCIDENT SITE 5 OR OVER(UNLIMITED) NONE OBSTRUCTIONS TO VISION AT ACCIDENT SITE TYPE OF WEATHER CONDITIONS NONE VFR TYPE OF FLIGHT PLAN NONE REMARKS- CONT FLT INTO KNOWN ADVERSE WEA COND. HIT MTN SLOPE. RECOVERY DATE 11/14/71.
Aircraft
- Registration
- N3626R
- Reported as
- Piper PA-28
- 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.