# Incident 20051210030649I: Emb ERJ170100SE, Lincoln, NE, December 10, 2005

- Type: FAA incident report (Accident/Incident Data System), as reported
- Date: December 10, 2005, 10:33 local time
- Place: Lincoln, NE
- Airport: Lincoln Municipal
- Phase of flight: Normal Cruise
- Operating rules: Air carrier (Part 121)
- Operator: UHLA
- Location: 40.8509° N, 96.7591° W: Placed by OpenAirDocs at LINCOLN (LNK), within about a mile (OpenAirDocs)
- Nearby events: https://openairdocs.org/map.md?lat=40.8509&lon=-96.7591&mi=10
- Aircraft: N641RW, registered now (https://openairdocs.org/aircraft/N641RW) (OpenAirDocs)
- Registry model: Embraer ERJ 170-100 SE (registry code 3260406, https://openairdocs.org/model/embraer-erj-170-100-se) (OpenAirDocs)
- Registry engine: GE CF34 series (registry code 30015, https://openairdocs.org/engine/ge-cf34-series) (OpenAirDocs)
- Reported make and model: EMB ERJ170100SE
- People aboard: 58
- Fatal injuries: 0
- Pilot flight hours: 0 total, 0 in this make and model, 0 in the last 90 days
- FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/)
- Page: https://openairdocs.org/incident/20051210030649I

## Narrative

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

(-23) N641RW, EMBRAER EMJ-170-100SE, OPERATED BY SHUTTLE AMERICA AS UNITED EXPRESS FLIGHT 7655, WAS ENROUTE FROM COLUMBUS, OH, TO DENVER, CO. EIGHTY MILES WEST OF LINCOLN, NE., THE CREW DECLARED AN EMERGENCY DUE TO AN AILERON PROBLEM, AND DIVERTED TO LINCOLN, NE, WHERE THEY LANDED SAFELY. COMPANY MECHANICS REPLACED THE AUTOPILOT SERVO, WHICH HAD CAUSED THE AUTOPILOT SYSTEM TO FAIL.

## Other reports on N641RW (1)

Matched to the same aircraft by N-number and date.

- [Incident 20250309001509I](https://openairdocs.org/incident/20250309001509I), Mar 9, 2025: Embraer ERJ 170-100 SE (N641RW), Dulles, VA, Minor damage. Flight [privacy data omitted] (bdl-iad) struck a bird at 2000FT while on approach to rwy 19L. Landed and taxied to the gate. A bird strike inspection revealed…

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.