FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

American Eagle Airlines Flight 230

27 Dec 2000 · Chicago, IL, United States

Embraer EMB-135LR · Incident: airframe, component or system failure en route

From Chicago O'Hare International Airport (ORD) to La Crosse Regional Airport (LSE)

Report a problem

Event

NTSB case
CHI01IA055
Event typeAccident: someone killed or seriously injured, or the aircraft substantially damaged (NTSB definition). Incident: an occurrence that affected or could have affected safety, short of that. Glossary
Incident
InvestigationHow far the investigation had got when the record was published: preliminary, ongoing, final or completed. Unknown where the source does not say. Glossary
Completed
API-reported fatalities
0 · all aircraft and ground
Ground fatalities
0
OperationWhat kind of flying it was, grouped by the rules it flew under: airline (US Part 121), air taxi and commuter (Part 135), general aviation (Part 91 and similar), military or government. Glossary
Airline
WeatherVisual meteorological conditions (VMC): good enough to fly by looking outside. Instrument conditions (IMC): cloud or low visibility, flying by instruments. Glossary
Visual Meteorological Cond

Embraer EMB-135LR

Aircraft type
Embraer EMB-135
Category
Airplane
RegistrationThe aircraft's tail number, such as N12345 or G-ABCD. Registrations are reissued, so the same one years apart can be a different aircraft. Glossary
N721HS
Onboard fatalities
Unknown
Route
From Chicago O'Hare International Airport (ORD), ILTo La Crosse Regional Airport (LSE), LACROSSE, WI
Aircraft age
Not recorded
Flight rulesThe regulations the flight operated under: in the US, Part 91 (general aviation), Part 121 (airlines), Part 135 (air taxi and commuter) and others; for flights abroad, the NTSB's coarser commercial or non-commercial code. Glossary
Part 121: Air Carrier
Phase of flightThe stage of the flight when things started to go wrong: standing, taxi, takeoff, initial climb, en route, maneuvering, approach or landing. Glossary
En route · climb to cruise
First occurrenceThe single coded event the NTSB judges best describes what happened (records from 2008 on). Older records name the first occurrence in the sequence instead. Glossary
Airframe, component or system failure
DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
None

Cause areas

  • Flt control syst, stabilator trim › Jammed

Approximate · Estimated position: the centre of Chicago, IL, the place the record names. Not the accident site.

NTSB narrative

The captain said that during takeoff from O'Hare International Airport (ORD) the airplane accelerated normally, rotated, and "jumped into the air". At 800 feet agl, the captain called for the climb checklist. It was about this time that the captain noticed that he could not trim nose down. The captain had the first officer check his trim switch and the backup system. They did not respond. The captain elected to bring the airplane back to ORD. The captain said that both he and the first officer had their control yokes pushed forward to the stop and were still climbing. The captain said he was finally able to stop the climb and level the airplane at approximately 8,000 feet. The captain said they declared an emergency and referred to the Pitch Trim 1 and 2 Failure checklists. The checklist directed they lower flaps to 9 degrees. "When we brought in the flaps, the aircraft pitched way nose high. We were out of control." The captain regained control of the airplane and had the first officer retract the flaps. The captain said they lowered the landing gear. It improved the airplane's stability slightly. They pulled and reset the trim circuit breakers twice. These actions did nothing. The captain said he lined up for an approach to runway 9R. The captain determined he was too high to land, so he executed a 360-degree descending turn. On completion of the turn, the captain said they needed to slow down so they deployed the spoilers. The captain said the airplane abruptly pitched way up. The captain said he and the first officer pushed both yokes forward. The captain advanced the throttles, and retracted the spoilers. "That second, I banked hard left, 50 to 60 degrees as I recall, and chopped the power. It took all our abilities to get the nose down." After they got the airplane back under control, the captain said approach control informed them that runway 4R was straight ahead. The captain elected to land on runway 4R. The captain said he left the airplane configured as it was (landing gear down, flaps and spoilers retracted) and flew a long shallow approach. "I said to myself, God please let me land this airplane. Over the runway, I chopped the power and let it settle on the runway." A post-incident examination of the airplane's spoiler control unit revealed that when the spoilers were given the command to retract, the unit was not sending an input to the horizontal stab control unit (HSCU) to put in 1 unit of nose down stabilizer trim. Examinations of the trim system components and the other airplane systems revealed no anomalies. Following the incident, the airplane's manufacturer revealed that the horizontal stab actuator was determined to be inadequate to move the horizontal stabilizer in all flight conditions. "The incidents are most likely caused when the flight crew fails to trim the airplane after takeoff before reaching a certain airspeed where the air loads on the stabilizer may overpower the trim actuator, resulting in the horizontal stabilizer not responding to the pitch trim command from the flight crew." The manufacturer issued an alert service bulletin mandating the installation of a cockpit placard and revisions to the airplane flight manual establishing a maximum speed of 160 knots to pitch-trim after takeoff. The FAA issued an emergency AD mandating the installation of the cockpit placard and revisions to the airplane flight manual. The FAA has also tasked the manufacturer to make design changes that will enable the trim actuator to handle increased load limits. The FAA has also mandated changes that will provide improved pitch trim failure indications and ergonomic improvements of the yoke trim switches.

Probable cause

The jammed horizontal stabilizer trim that occurred during the airplane's initial climb after takeoff. Factors relating to the incident were the inadequate capability of the horizontal stabilizer trim actuator to move the stabilizer during all flight phases, and the inadequate design of the system by the manufacturer.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record CHI01IA055
Event ID
20010105X00017
Case number
CHI01IA055
Dataset
historical-pre2008
Source SHA-256
89e2df6d848e7ab3b42e7d7c7a03ff403303057a26ca04c95b3ea67201c3ce74
Source notes (4)
  • Unreviewed is an editorial label, not an investigation status. API-sourced is not report-checked or human-reviewed. Explicit event totals are used without summing aircraft injury tables; onboard allocation is withheld. Unknown values remain unknown. The operation category is mapped from the NTSB-reported FAR part and has not been reviewed.
  • Filled from the NTSB case API where the bulk record had no value: local date, investigation status, damage. Values present in the bulk record are kept.
  • The date is the local date; the NTSB stores the UTC date 2000-12-28.
  • API snapshot SHA-256: f09100560d987b2d08ff2768d89698f0634b6af274404f0cbcf413e2c3126bef; retrieved 2026-09-18T16:18:32.831Z.