- Date
- November 25, 1970
- Place
- Arlington, CA · ARLINGTON, CA
- Injuries
- 1 fatal
- Damage
- Destroyed
- Phase of flight
- Enroute
- Aircraft
- N6837WPiper PA-28
- Status
- Completed · report June 2, 1971
- Report
- Brief approved by the director
- Case key
- 159270
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-3187 70/11/25 ARLINGTON,CALIF PIPER PA-28 CR- 1 0 0 NONCOMMERCIAL COMMERCIAL, FL.INSTR., TIME - 2011 N6837W PX- 0 0 0 PLEASURE/PERSONAL TRANSP AGE 54, 16000 TOTAL DAMAGE-DESTROYED OT- 0 0 0 HOURS, 7 IN TYPE, NOT INSTRUMENT RATED. DEPARTURE POINT INTENDED DESTINATION BLYTHE,CALIF LONG BEACH,CALIF TYPE OF ACCIDENT PHASE OF OPERATION COLLIDED WITH: WIRES/POLES IN FLIGHT: OTHER PROBABLE CAUSE(S) PILOT IN COMMAND - CONTINUED VFR FLIGHT INTO ADVERSE WEATHER CONDITIONS FACTOR(S) PILOT IN COMMAND - INADEQUATE PREFLIGHT PREPARATION AND/OR PLANNING WEATHER - LOW CEILING WEATHER - RAIN WEATHER - FOG WEATHER BRIEFING - NO RECORD OF BRIEFING RECEIVED WEATHER FORECAST - FORECAST SUBSTANTIALLY CORRECT SKY CONDITION CEILING AT ACCIDENT SITE BROKEN 400 VISIBILITY AT ACCIDENT SITE PRECIPITATION AT ACCIDENT SITE 1 MILE OR LESS DRIZZLE OBSTRUCTIONS TO VISION AT ACCIDENT SITE TYPE OF WEATHER CONDITIONS FOG IFR TYPE OF FLIGHT PLAN NONE REMARKS- HIT PWR POLE 30 FT AGL. PLT HAD PREVIOUSLY REQ SPL VFR CLNC WHEN POS ABOVE OCST. CLNC WAS DENIED.
Aircraft
- Registration
- N6837W
- 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.