ASN Wikibase Occurrence # 236880
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: | Tuesday 9 June 2020 |
Time: | 08:46 |
Type: | Van's RV-4 |
Owner/operator: | Private |
Registration: | N173CW |
MSN: | 95-1736 |
Year of manufacture: | 1997 |
Total airframe hrs: | 1406 hours |
Engine model: | Lycoming O-320 |
Fatalities: | Fatalities: 1 / Occupants: 1 |
Aircraft damage: | Destroyed |
Category: | Accident |
Location: | near Safford Regional Airport (KSAD/SAD), AZ -
United States of America
|
Phase: | Approach |
Nature: | Private |
Departure airport: | Tucson International Airport, AZ (KTUS/TUS) |
Destination airport: | Safford Regional Airport, AZ (KSAD/SAD) |
Investigating agency: | NTSB |
Confidence Rating: | Accident investigation report completed and information captured |
Narrative:On June 9, 2020, about 0846 mountain standard time, an experimental, amateur-built RV4, N173CW, was substantially damaged when it was involved in an accident near Safford, Arizona. The pilot was fatally injured. The airplane was operated as a Title 14 Code of Federal Regulations Part 91 personal flight.
The pilot was performing a routine flight over mountainous desert terrain to a destination he had flown to multiple times before. Visual meteorological conditions prevailed, with light winds and no turbulence.
ADS-B flight track information indicated that the airplane entered a nominal descent profile toward the destination airport; however, about 1 mile from the end of the presumed landing runway, the airplane began a rapid descent into rising terrain. After colliding with the ground, the airplane continued uphill 300 ft until coming to rest about 1/2 mile short and 40 ft below the approach end of the runway. The considerable distance travelled uphill after striking terrain indicated a relatively flat impact attitude and engine power at impact.
The rapid descent rate suggests that the pilot may have encountered pitch control difficulties; however, examination of the airframe did not reveal any evidence of primary flight control anomalies or a bird strike. The pitch trim system in the rear of the airplane was intact and functional; however, impact damage sustained to the front of the airplane precluded a complete determination of the pitch trim system state.
The airplane’s flaps were found fully extended, but flight track information indicated that the airplane did not slow to its flap deployment speed at any point during the approach. Damage to the flap electrical system prevented an accurate assessment of its operational status; therefore, an unintended deployment of the flaps could not be ruled out. However, under a runaway flap condition, the actuator motor would have deployed the flaps slowly, and flight testing revealed that any pitch-down forces caused by the flap deployment both with and without full nosedown trim would have been easily overcome by the pilot with the application of aft control stick forces. Further, at full extension, the flaps tended to act as air brakes. It is possible that he deployed the flaps intentionally to slow the airplane while struggling with a pitch anomaly.
During the examination, a foreign object (position light socket) that had previously been removed from the airplane was found in the lower underfloor bay of the aft seat, in an area that would have been occupied by the rear control column assembly. Although the forward control stick was fitted with a boot, the aft stick was not, leaving an open area into the control stick assembly. It is possible that either the socket or another unidentified object dropped into the open area and interfered with the free movement of the control stick, resulting in a pitch control jam and a rapid descent.
Probable Cause: A loss of pitch control during the landing approach due to a jammed elevator control system.
Accident investigation:
|
| |
Investigating agency: | NTSB |
Report number: | WPR20LA176 |
Status: | Investigation completed |
Duration: | 2 years and 3 months |
Download report: | Final report |
|
Sources:
https://www.eacourier.com/news/plane-crash-kills-pilot/article_8a9dafc0-aa9e-11ea-b161-5754ef21337a.html NTSB
https://flightaware.com/live/flight/N173CW/history https://www.airport-data.com/aircraft/photo/000217670.html (photo)
Location
Images:
Photos: NTSB
Media:
Revision history:
Date/time | Contributor | Updates |
10-Jun-2020 08:31 |
Captain Adam |
Added |
10-Jun-2020 11:34 |
Abieross |
Updated [Embed code] |
24-Jun-2021 07:26 |
aaronwk |
Updated [Time, Narrative] |
05-Oct-2022 21:46 |
Captain Adam |
Updated [Time, Source, Narrative, Accident report, Photo] |
05-Oct-2022 21:46 |
Captain Adam |
Updated [Photo] |
The Aviation Safety Network is an exclusive service provided by:
CONNECT WITH US:
©2024 Flight Safety Foundation