- Date
- July 21, 1971
- Place
- Alamosa, CO · ALAMOSA, CO
- Injuries
- 5 fatal
- Damage
- Destroyed
- Phase of flight
- Enroute
- Aircraft
- N6302YPiper PA-23
- Status
- Completed · report January 3, 1972
- Report
- Brief approved by the director
- Case key
- 162074
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-1361 71/7/21 NR.ALAMOSA,COLO PIPER PA-23 CR- 1 0 0 NONCOMMERCIAL PRIVATE, AGE 52, 1173 TIME - 1600 N6302Y PX- 4 0 0 BUSINESS TOTAL HOURS, 109 IN TYPE, DAMAGE-DESTROYED OT- 0 0 0 NOT INSTRUMENT RATED. DEPARTURE POINT INTENDED DESTINATION LAST ENROUTE STOP PHOENIX,ARIZ DENVER,COLO FARMINGTON,N MEX TYPE OF ACCIDENT PHASE OF OPERATION COLLIDED WITH: WIRES/POLES IN FLIGHT: NORMAL CRUISE PROBABLE CAUSE(S) PILOT IN COMMAND - CONTINUED VFR FLIGHT INTO ADVERSE WEATHER CONDITIONS FACTOR(S) WEATHER - LOW CEILING WEATHER - RAIN WEATHER - TURBULENCE, ASSOCIATED W/CLOUDS AND/OR THUNDERSTORMS WEATHER - THUNDERSTORM ACTIVITY WEATHER BRIEFING - BRIEFED BY FLIGHT SERVICE PERSONNEL, BY PHONE WEATHER FORECAST - UNKNOWN/NOT REPORTED MISSING AIRCRAFT - LATER RECOVERED SKY CONDITION CEILING AT ACCIDENT SITE OBSCURATION UNKNOWN/NOT REPORTED VISIBILITY AT ACCIDENT SITE PRECIPITATION AT ACCIDENT SITE UNKNOWN/NOT REPORTED RAIN OBSTRUCTIONS TO VISION AT ACCIDENT SITE TYPE OF WEATHER CONDITIONS UNKNOWN/NOT REPORTED IFR TYPE OF FLIGHT PLAN VFR FIRE AFTER IMPACT REMARKS- RECOVERY DATE 7/24/71
Aircraft
- Registration
- N6302Y
- Reported as
- Piper PA-23
- 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.