FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

American Eagle Airlines Flight 3008

2 Jan 2006 · Santa Maria, CA, United States

Saab-Scania AB (Saab) SF340B+ · Incident: in flight encounter with weather en route

From San Luis County Regional Airport (SBP) to Los Angeles International Airport (LAX)

Report a problem

Event

NTSB case
LAX06IA076
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
Unknown
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
Instrument Meteorological Cond

Saab-Scania AB (Saab) SF340B+

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
N390AE
Onboard fatalities
Unknown
Route
From San Luis County Regional Airport (SBP), San Luis Obispo, CATo Los Angeles International Airport (LAX), Los Angeles, CA
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
In flight encounter with weather
Also codedOther events the NTSB coded in the sequence, such as a wire strike after a loss of power. Flight Findings uses them for its kinds of event. Glossary
Stall
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

  • Other person › Airspeed, not maintained
  • Stall › Encountered

Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.

NTSB narrative

After departure and during the cruise climb phase, the flight encountered airframe ice and departed from controlled flight.

The flight crew encountered light rime icing on the inbound leg while descending from 9,000 to 5,000 feet. Before the incident takeoff, they reviewed the dispatch package weather and noted two AIRMET (airmen's meteorological information) reports for icing in clouds. The captain decided to perform the departure and turn control of the airplane over to the first officer after completing the climb checklist at the acceleration altitude. In accordance with the operator's minimum equipment list (MEL), the airplane was dispatched with the continuous mode of the boot deice system inoperable, which would require the crew to manually operate the deice boots. Company procedures require activation of the deice system at the first sign of ice accretion, and operation of the deice boots continually thereafter while in icing conditions. The departure was into level 2 weather conditions (defined as 10 degree Celsius or colder with visible moisture).

The airline's Airplane Operating manual (AOM) for the airplane calls for computation of a minimum speed (Vcln+15) in icing conditions, which for this flight was 141 KIAS. The limitations section stipulates that Indicated Air Speed (IAS) is the only authorized flight director/autopilot mode while climbing when ice accretion is occurring or with residual ice on the airframe. In IAS mode, the flight control computer gives pitch commands to maintain the selected indicated airspeed as opposed to the Vertical Speed (VS) mode where the autopilot sacrifices airspeed to maintain climb rate. Even though the crew had encountered icing on the inbound leg and the dispatch weather reports predicted an icing encounter during the climb on the outbound leg, the captain engaged the autopilot in the medium (M) climb mode and shortly after taking the controls at 2,500 feet, the first officer changed the autopilot to VS mode.

As the airplane climbed through 11,700 feet, the captain noted light rime ice accumulating on the windshield wiper blades and about a 1/2-inch-wide area of ice on the left wing. During this time, the crew failed to detect a decaying indicated airspeed due to the ice that was accumulating. As he began to activate the manual deice boot system, he felt a heavy vibration in the airframe and the windscreen immediately turned white with ice. The airplane's nose and left wing dropped and the autopilot disconnected. As he was grabbing the yoke, the clacker sounded (indicating an imminent stall), the stick shaker activated, and the ground proximity warning system emitted a "bank angle" aural warning. Digital Flight Data Recorder (DFDR) data showed that the indicated airspeed went from 144 to 130 KIAS over the 26 seconds before the upset, and that the rate of airspeed decay accelerated in the final 10 seconds before the autopilot disconnected. The airplane departed controlled flight at an indicated airspeed of 130 knots, and before the stall warning activated. The data establishes that the airplane went through a series of roll and pitch excursions, reaching maximum values of 86 degrees left wing down, 140 degrees right wing down, 23 degrees nose up, and 40 degrees nose down before the flight crew recovered control. The data also revealed that about 26 seconds before the stall while the airplane was at a speed of 144 KIAS, the airplane began to experience a likely ice-induced slight rolling anomaly that was counter to the direction of the aileron input. Aileron input from the autopilot arrested this slight rolling motion.

The DFDR data also disclosed that 14 seconds after the initial stall, both ailerons simultaneously traveled to the full up position for approximately 14 seconds. The Safety Board believes that the initial stall that occurred prior to stall warning, the upset, and the aileron upward deflections were caused by ice accreted on the wing in supercooled liquid droplets (SLD) conditions. Furthermore, the period of simultaneous upward deflection of the ailerons were caused by airflow separations over the ailerons, and not by opposite control wheel inputs by the captain and first officer (FO). This conclusion was based on the similar nature of past experience in accidents and incidents involving modification of aileron forces by SLD ice accretions, the higher airspeed and dynamic nature of the initiating events, the captain's and FO's statements, and the captain removing one hand from the control wheel to reduce the power. Also contributing to this conclusion was extrapolation of aileron and control wheel force measurements obtained in high speed taxi testing with a simulated ice shape in front of one aileron, and the development of airflow separation over the ailerons into a complete full wing stall.

Recommendations

The Safety Board issued several recommendations as a result of the investigation.

Urgent recommendation A-06-48 asked the FAA to require all operators of Saab SF340 series airplanes to instruct pilots to maintain a minimum operating airspeed of 1.45xVs during icing encounters and before entering known or forecast icing conditions and to exit icing conditions as soon as performance degradations prevent the airplane from maintaining 1.45xVs.

Recommendation A-06-49 and A-06-50 asked the FAA to require the installation of modified stall protection logic in Saab SF340 series airplanes certified for flight into known icing conditions and to require the installation of an icing detection system on Saab SF340 series airplanes.

Recommendation A-06-51 asked the FAA to require all operators of turbo propeller-driven airplanes to instruct pilots, to disengage the autopilot and fly the airplane manually when operating in icing conditions.

The Safety Board also reiterated the following prior recommendations to the FAA.

Recommendation A-03-53 and A-03-54 asked the FAA to convene a panel of airplane design, operations, and aviation human factors specialists to determine whether a requirement for the installation of low-airspeed alert systems in airplanes engaged in commercial operations under 14 Code of Federal Regulations Parts 121 and 135 would be feasible, and if the panel determined that such feasibility exists, establish requirements for low-airspeed alert systems.

Probable cause

An in-flight loss of control due to ice accreted in supercooled liquid droplets (SLD) conditions, and the flight crew's failure to maintain the specified minimum airspeed in icing conditions. Contributing to the accident was the flight crew's decision to climb the airplane in known and forecast icing conditions using an autopilot mode contrary to that specified in the operator's Airplane Operations Manual for climbs during periods of ice accretion or when ice was present on the airframe.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record LAX06IA076
Event ID
20060109X00033
Case number
LAX06IA076
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: investigation status, damage. Values present in the bulk record are kept.
  • The date is the local date, which is the same as the UTC date the NTSB stores.
  • API snapshot SHA-256: cb0ae35aff67ff5d1b986cb1901d379f03d3dd4e7b82ca1a0d074ab1676219d8; retrieved 2026-09-18T14:56:18.606Z.