- Date
- October 29, 1970
- Place
- Hayfork, CA · HAYFORK, CA
- Injuries
- 1 uninjured
- Damage
- Substantial damage
- Phase of flight
- Landing
- Aircraft
- N1591KLuscombe 8A
- Status
- Completed · report July 26, 1971
- Report
- Brief approved by the director
- Case key
- 158999
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-4057 70/10/29 HAYFORK,CALIF LUSCOMBE 8A CR- 0 0 1 NONCOMMERCIAL PRIVATE, AGE 46, 179 TIME - 1400 N1591K PX- 0 0 0 PLEASURE/PERSONAL TRANSP TOTAL HOURS, 160 IN TYPE, DAMAGE-SUBSTANTIAL OT- 0 0 0 NOT INSTRUMENT RATED. NAME OF AIRPORT - HAYFORK DEPARTURE POINT INTENDED DESTINATION RED BLUFF,CALIF HAYFORK,CALIF TYPE OF ACCIDENT PHASE OF OPERATION GROUND-WATER LOOP-SWERVE LANDING: ROLL COLLIDED WITH: OBJECT LANDING: ROLL PROBABLE CAUSE(S) PILOT IN COMMAND - FAILED TO MAINTAIN DIRECTIONAL CONTROL WEATHER - UNFAVORABLE WIND CONDITIONS WEATHER BRIEFING - NO RECORD OF BRIEFING RECEIVED WEATHER FORECAST - UNKNOWN/NOT REPORTED 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 RELATIVE BEARING OF WIND NONE RIGHT QUARTERING HEAD WIND 023-067 DEGREES TEMPERATURE-F WIND DIRECTION-DEGREES 65 315 WIND VELOCITY-KNOTS TYPE OF WEATHER CONDITIONS 20 VFR TYPE OF FLIGHT PLAN NONE REMARKS- ROLLED OFF RWY INTO ROCKS.
Aircraft
- Registration
- N1591K
- Reported as
- Luscombe 8A
- Category
- Airplane
- Engine
- reciprocating
- Damage
- Substantial damage
- Airport
- Hayfork
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.