 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Emb-170 captain reported experiencing high aileron control forces during the flight. During post-flight inspection; maintenance did not find anything wrong.
| Attributes | |
| ACN | 1634753 |
| Time | |
| Date | 201904 |
| Local Time Of Day | 1201-1800 |
| Place | |
| Locale Reference | ZZZ.ARTCC |
| State Reference | US |
| Environment | |
| Light | Daylight |
| Aircraft 1 | |
| Make Model Name | EMB ERJ 170/175 ER/LR |
| Operating Under FAR Part | Part 121 |
| Flight Phase | Descent |
| Route In Use | Vectors STAR ZZZZZ2 |
| Flight Plan | IFR |
| Component | |
| Aircraft Component | Aileron Control System |
| Person 1 | |
| Function | Captain Pilot Flying |
| Qualification | Flight Crew Multiengine Flight Crew Air Transport Pilot (ATP) Flight Crew Instrument |
| Events | |
| Anomaly | Aircraft Equipment Problem Less Severe |
Narrative:
On [our] flight there was a flight control anomaly. Throughout the flight everything was normal. As we approached the start of the arrival; center issued us a vector. Using heading mode we started turning to that heading. As the aircraft started the turn the autopilot disengaged and we heard the 'autopilot' aural warning.I pressed the ap/trim disconnect button to cancel the aural warning and noticed the control wheel was difficult to move in roll. I asked the first officer (first officer) to fly to see what his opinion was. The consensus was that the control wheel was unusually stiff in roll. After reengaging the autopilot and using FMS nav on the arrival the autopilot disengaged for a second time. I reengaged the autopilot and discussed with the first officer about possible scenarios. I felt like the aircraft was safe to fly and there should be no problem in continuing and landing safely at [the destination] as we had full control of the aircraft albeit with heavy control force on the ailerons. As we descended and after disengaging the autopilot manually; the control force was normal and we had an uneventful landing. I wrote up the anomaly in the logbook and maintenance came out; ran a bunch of tests and couldn't find anything wrong. The logbook was signed off but I refused the aircraft for our next leg.
Original NASA ASRS Text
Title: EMB-170 Captain reported experiencing high aileron control forces during the flight. During post-flight inspection; Maintenance did not find anything wrong.
Narrative: On [our] flight there was a flight control anomaly. Throughout the flight everything was normal. As we approached the start of the arrival; Center issued us a vector. Using heading mode we started turning to that heading. As the aircraft started the turn the autopilot disengaged and we heard the 'autopilot' aural warning.I pressed the AP/TRIM disconnect button to cancel the aural warning and noticed the control wheel was difficult to move in roll. I asked the FO (First Officer) to fly to see what his opinion was. The consensus was that the control wheel was unusually stiff in roll. After reengaging the autopilot and using FMS Nav on the arrival the autopilot disengaged for a second time. I reengaged the autopilot and discussed with the FO about possible scenarios. I felt like the aircraft was safe to fly and there should be no problem in continuing and landing safely at [the destination] as we had full control of the aircraft albeit with heavy control force on the ailerons. As we descended and after disengaging the autopilot manually; the control force was normal and we had an uneventful landing. I wrote up the anomaly in the logbook and Maintenance came out; ran a bunch of tests and couldn't find anything wrong. The logbook was signed off but I refused the aircraft for our next leg.
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.