Accident Piper PA-23-250 Aztec C N6521Y,
ASN logo
ASN Wikibase Occurrence # 235627
 
This information is added by users of ASN. Neither ASN nor the Flight Safety Foundation are responsible for the completeness or correctness of this information. If you feel this information is incomplete or incorrect, you can submit corrected information.

Date:Thursday 30 April 2020
Time:12:20
Type:Silhouette image of generic PA27 model; specific model in this crash may look slightly different    
Piper PA-23-250 Aztec C
Owner/operator:Landcare Aviation Inc
Registration: N6521Y
MSN: 27-3812
Year of manufacture:1967
Total airframe hrs:9154 hours
Engine model:Lycoming IO-540-C4B5
Fatalities:Fatalities: 1 / Occupants: 1
Aircraft damage: Destroyed
Category:Accident
Location:SE of Hemet-Ryan Airport (HMT/KHMT), Hemet, CA -   United States of America
Phase: Approach
Nature:Survey
Departure airport:Chino Airport, CA (CNO/KCNO)
Destination airport:Hemet-Ryan Field, CA (HMT/KHMT)
Investigating agency: NTSB
Confidence Rating: Accident investigation report completed and information captured
Narrative:
The accident pilot and a second company pilot were flying in the same general area to photograph parcels of land. As the pilots were beginning their photography passes, the company pilot heard the accident pilot make distress calls on the radio. The accident pilot did not respond when asked to clarify the radio calls.

ADS-B data revealed the airplane approached the area to be photographed from the west, made a turn north to enter the area, then made a turn back to the southwest. The airplane then started a right descending turn about the time it intercepted its inbound course to the area. The last data captured the airplane, about 1,000 ft above the ground, about 177 knots groundspeed, in a 2,000 ft-per-minute descent, and about 950 ft northwest of the accident site. The camera system mounted in the airplane recorded the airplane, at that time, in a 31° nose-down attitude, and a 79° right roll.

The airplane struck steep mountainous terrain at a high speed, and the fuselage sustained substantial damage throughout. The wings, the vertical stabilizer, and the right side of the stabilator separated from the airplane.

Examination of the aileron control by the NTSB materials laboratory revealed that a cable had broken under fatigue in a location near the aileron control bellcrank, likely resulting in a loss of control of the airplane. The airplane was maintained in accordance with the operator’s annual maintenance schedule; however, postaccident examination of the aileron control cable revealed that in addition to the fatigue break, multiple individual broken wires were discovered protruding from the strands, which would have required replacement of the cable upon discovery during required checks of the cable.

The toxicology report for the pilot identified positive results for a cannabis metabolite; however, amounts discovered were unlikely to have been impairing. Given the circumstances of the accident, it is unlikely that the pilot’s use of cannabis contributed to the accident and that the pilot lost control of the airplane due to the fatigue failure of the aileron cable.

Probable Cause: Maintenance personnel’s failure to properly inspect and replace damaged aileron control cables, which resulted in fatigue separation of the aileron control cable and loss of control of the aircraft.

Accident investigation:
cover
  
Investigating agency: NTSB
Report number: WPR20LA135
Status: Investigation completed
Duration: 1 year and 10 months
Download report: Final report

Sources:

NTSB
https://www.google.com/amp/s/ktla.com/news/local-news/airplane-crashes-near-hemet/amp/
https://www.pe.com/2020/04/30/plane-crashes-in-southwest-riverside-county/

https://flightaware.com/live/flight/N6521Y/history/20200430/1832Z/KCNO/L%2033.65587%20-116.83960/tracklog

https://cdn.jetphotos.com/full/5/72956_1540952978.jpg (photo)

Location

Images:







Photos(c): NTSB

Revision history:

Date/timeContributorUpdates
30-Apr-2020 22:51 Captain Adam Added
30-Apr-2020 22:54 Captain Adam Updated [Aircraft type]
30-Apr-2020 23:12 Geno Updated [Time, Total fatalities, Total occupants, Location, Source]
01-May-2020 07:11 Anon. Updated [Date]
01-May-2020 09:35 Anonymous Updated [Registration, Source]
01-May-2020 09:37 harro Updated [Aircraft type, Cn, Departure airport, Destination airport, Source, Damage]
01-May-2020 10:25 RobertMB Updated [Aircraft type, Operator, Phase, Nature, Narrative]
01-May-2020 12:23 RobertMB Updated [Operator, Narrative]
01-May-2020 16:34 RobertMB Updated [Nature, Source, Narrative]
02-May-2020 08:08 Captain Adam Updated [Nature, Narrative]
01-Mar-2021 19:39 harro Updated [Nature, Narrative]
16-Mar-2022 18:43 Captain Adam Updated [Source, Narrative, Category, Accident report, Photo]
16-Mar-2022 18:46 Captain Adam Updated [Photo]
16-Mar-2022 18:46 Captain Adam Updated [Photo]
16-Mar-2022 18:46 Captain Adam Updated [Photo]
16-Mar-2022 18:47 Captain Adam Updated [Photo]
16-Mar-2022 18:47 Captain Adam Updated [Photo]

Corrections or additions? ... Edit this accident description

The Aviation Safety Network is an exclusive service provided by:
Quick Links:

CONNECT WITH US: FSF on social media FSF Facebook FSF Twitter FSF Youtube FSF LinkedIn FSF Instagram

©2024 Flight Safety Foundation

1920 Ballenger Av, 4th Fl.
Alexandria, Virginia 22314
www.FlightSafety.org