- Date
- May 31, 1976
- Place
- Ashland, OR · ASHLAND, OR
- Injuries
- 2 serious
- Damage
- Destroyed
- Phase of flight
- Enroute
- Aircraft
- N6156LAmer Avco AA1
- Status
- Completed · report July 7, 1976
- Report
- Brief approved by the director
- FAA report
- 19760531014699A
- Case key
- 154697
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-2336 76/5/31 NR. ASHLAND,OR AMER AVCO AA1 CR- 0 1 0 NONCOMMERCIAL PRIVATE, AGE 47, 547 TIME - 1300 N6156L PX- 0 1 0 PLEASURE/PERSONAL TRANSP TOTAL HOURS, 182 IN TYPE, DAMAGE-DESTROYED OT- 0 0 0 NOT INSTRUMENT RATED. DEPARTURE POINT INTENDED DESTINATION LAST ENROUTE STOP MEOFORD,OR KLAMATH FALLS,OR REDMOND,OR TYPE OF ACCIDENT PHASE OF OPERATION TURBULENCE IN FLIGHT: NORMAL CRUISE PROBABLE CAUSE(S) PILOT IN COMMAND - CONTINUED VFR FLIGHT INTO ADVERSE WEATHER CONDITIONS FACTOR(S) WEATHER - TURBULENCE, ASSOCIATED W/CLOUDS AND/OR THUNDERSTORMS WEATHER - DOWNDRAFT,UPDRAFTS WEATHER - THUNDERSTORM ACTIVITY WEATHER BRIEFING - BRIEFED BY FLIGHT SERVICE PERSONNEL, IN PERSON WEATHER FORECAST - UNKNOWN/NOT REPORTED SKY CONDITION CEILING AT ACCIDENT SITE UNKNOWN/NOT REPORTED 5000 VISIBILITY AT ACCIDENT SITE PRECIPITATION AT ACCIDENT SITE 5 OR OVER(UNLIMITED) RAIN, THUNDERSTORM OBSTRUCTIONS TO VISION AT ACCIDENT SITE TEMPERATURE-F NONE 60 TYPE OF WEATHER CONDITIONS TYPE OF FLIGHT PLAN VFR VFR FIRE AFTER IMPACT REMARKS- TSTMS IN AREA.
Aircraft
- Registration
- N6156L
- Reported as
- Amer Avco AA1
- 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.
FAA reports on this event · 1
The FAA’s own accident and incident reports, matched to the aircraft by N-number and date.