37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 1523800 |
Time | |
Date | 201802 |
Local Time Of Day | 0601-1200 |
Place | |
Locale Reference | ZZZ.Airport |
State Reference | US |
Environment | |
Flight Conditions | Marginal |
Aircraft 1 | |
Make Model Name | Citation X (C750) |
Operating Under FAR Part | Part 135 |
Flight Phase | Final Approach |
Flight Plan | IFR |
Component | |
Aircraft Component | Rudder Control System |
Person 1 | |
Function | Captain Pilot Not Flying |
Qualification | Flight Crew Air Transport Pilot (ATP) Flight Crew Instrument Flight Crew Multiengine |
Events | |
Anomaly | Aircraft Equipment Problem Less Severe Deviation - Procedural Maintenance |
Narrative:
We picked up [the aircraft] in ZZZ at the start of our rotation. During preflight the previous PIC contacted me via phone to inform that they had several repeat issues relating to the upper rudder. After discussing their experience and reviewing the work order and work signed by the mx vendor we were comfortable accepting the aircraft as airworthy.the preflight; including the flight control check before taxi were all satisfactory. We departed without issues; flew approximately 5 minutes to ZZZ2 for a LNAV approach. Due to a single low cloud we went IMC 200 ft above MDA and executed the map (missed approach) after reaching the vdp. During climbout and after flap retraction we received an amber upper yd fail a-b cas message.we informed ATC that we need further delay vectors before attempting another approach to troubleshoot. We followed the checklist and after resetting the upper rudder the cas (crew alerting system) changed into a cyan yaw damp fail upper a before 30 seconds or so later the amber cas for fail a-b returned. It now appeared that the upper rudder was stuck in a slightly deflected position to the left. Based on the recent history with the system we stopped further troubleshooting and contacted maintenance for guidance if they had a preferred airport we divert to. We suggested ZZZ since that was the point of last repair. Maintenance control advised they prefer ZZZ2 to have a factory service center perform troubleshooting. We diverted with no further incident.days later I [received a] message from maintenance control stating that the cause for the failure was due to 'some bolts not installed'. I can only assume the repair work by the vendor in ZZZ was in violation of the maintenance procedures and manufacturer guidelines.I recommend an audit trail of the authorized work and legality of the return to service paperwork in ZZZ.
Original NASA ASRS Text
Title: CE750 Captain reported an UPPER YD FAIL A-B CAS message during a missed approach.
Narrative: We picked up [the aircraft] in ZZZ at the start of our rotation. During preflight the previous PIC contacted me via phone to inform that they had several repeat issues relating to the Upper Rudder. After discussing their experience and reviewing the work order and work signed by the MX vendor we were comfortable accepting the aircraft as airworthy.The preflight; including the flight control check before taxi were all satisfactory. We departed without issues; flew approximately 5 minutes to ZZZ2 for a LNAV approach. Due to a single low cloud we went IMC 200 ft above MDA and executed the MAP (Missed Approach) after reaching the VDP. During climbout and after flap retraction we received an amber UPPER YD FAIL A-B CAS message.We informed ATC that we need further delay vectors before attempting another approach to troubleshoot. We followed the checklist and after resetting the Upper Rudder the CAS (Crew Alerting System) changed into a cyan YAW DAMP FAIL UPPER A before 30 seconds or so later the amber CAS for FAIL A-B returned. It now appeared that the upper rudder was stuck in a slightly deflected position to the left. Based on the recent history with the system we stopped further troubleshooting and contacted Maintenance for guidance if they had a preferred airport we divert to. We suggested ZZZ since that was the point of last repair. Maintenance Control advised they prefer ZZZ2 to have a factory service center perform troubleshooting. We diverted with no further incident.Days later I [received a] message from Maintenance Control stating that the cause for the failure was due to 'some bolts not installed'. I can only assume the repair work by the vendor in ZZZ was in violation of the Maintenance procedures and manufacturer guidelines.I recommend an audit trail of the authorized work and legality of the return to service paperwork in ZZZ.
Data retrieved from NASA's ASRS site and automatically converted to unabbreviated mixed upper/lowercase text. This report is for informational purposes with no guarantee of accuracy. See NASA's ASRS site for official report.