# Incident 20121216027299I: Embraer ERJ 170-100 SE, Windsor Locks, CT, December 16, 2012

- Type: FAA incident report (Accident/Incident Data System), as reported
- Date: December 16, 2012, 15:00 local time
- Place: Windsor Locks, CT
- Damage: No damage
- Phase of flight: Descent
- Operating rules: Air carrier (Part 121)
- Operator: UHLA
- Location: 41.9298° N, 72.6580° W: Placed by OpenAirDocs: center of Windsor Locks, CT, within about 6 miles (OpenAirDocs)
- Nearby events: https://openairdocs.org/map.md?lat=41.9298&lon=-72.6580&mi=10
- Aircraft: N652RW (not matched to a registry record)
- Reported make and model: EMBRAER ERJ 170-100 SE
- Reported engine: GE CF34 SERIES
- People aboard: 49
- Fatal injuries: 0
- Other injuries: 0
- FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/)
- Page: https://openairdocs.org/incident/20121216027299I

## Narrative

As the FAA filed it, in capitals; the FAA replaces private details with ^PRIVACY DATA OMITTED^.

ON 1/2/2013, I SPOKE WITH CAPTAIN ^PRIVACY DATA OMITTED^ IN REFERENCE TO TCF 3448. CAPTAIN ^PRIVACY DATA OMITTED^ STATED THAT ON 12/16/2012, HE WAS PILOT IN COMMAND OF TCF 3448, AIRCRAFT N652RW. THE FLIGHT BEGAN IN ORD. HE STATED THE FLIGHT BEGAN NORMAL WITH ALL CHECKLISTS COMPLETED SUCCESSFULLY INCLUDING THE FLIGHT CONTROL CHECK. HE STATED THAT WHILE AT CRUISE, WITH AUTOPILOT ON, THE RUDDER TRIM WAS DISPLACED APPROXIMATELY 50% LEFT AND THE YOKE WAS DISPLACED SLIGHTLY RIGHT WING LOW. HE BROUGHT THIS TO THE ATTENTION OF THE FIRST OFFICER. BEGINNING THEIR DESCENT, CAPTAIN ^PRIVACY DATA OMITTED^ STATED THAT THE AUTOPILOT DISCONNECTED AND ROLLED SLIGHTLY RIGHT BUT NOT ABRUPTLY. WHEN HE TRIED TO ROLL BACK LEFT, THE CAPTAINS YOKE WOULD NOT ROLL LEFT. HE TRANSFERRED CONTROL TO THE FIRST OFFICER AND DECLARED AN EMERGENCY. HE ASKED AIR TRAFFIC CONTROL FOR RIGHT TURNS ONLY. THE FIRST OFFICER APPLIED EXTRA FORCE ON THE YOKE TO STOP THE ROLL AND AT THIS POINT, THE YOKE BROKE FREE AND THE AIRCRAFT RESPONDED NORMALLY THRU OUT THE REST OF THE FLIGHT. THEY LANDED NORMALLY IN BDL, THEIR PLANNED DESTINATION. MAINTENANCE WAS NOTIFIED AND SPENT OVER 32 MAN HOURS TROUBLE SHOOTING THE PROBLEM. THEY COULD FIND NO PROBLEM WITH THE FLIGHT CONTROLS AND NO ONBOARD FLIGHT RECORDERS SHOWED ANY ABNORMALITIES. THE AIRCRAFT WAS TEST FLOWN AND THEN FERRIED TO IND WHERE MAINTENANCE PERSONNEL AND FAA AIRWORTHINESS PERSONNEL AGAIN PERFORMED OPERATIONAL CHECKS WITH NO FINDINGS. THE AIRCRAFT WAS THEN RELEASED FOR REVENUE SERVICE.

From the FAA Accident/Incident Data System. Reports are matched to registry aircraft by N-number and event date, checked against the reported make and model; the registry's history has gaps, so older matches can be wrong. Compare the reported make and model. For accidents, the NTSB's own investigation is the fuller record.

---
OpenAirDocs.org is an independent research project of [Contrail Labs](https://contraillabs.com/). It is not affiliated with the FAA or the NTSB. Source documents are U.S. government works in the public domain.