21 May 2009: EMBRAER EMB-135 KL — American Eagle Airlines Inc

21 May 2009: EMBRAER EMB-135 KL (N843AE) — American Eagle Airlines Inc

No fatalities • Los Angeles, CA, United States

Probable cause

The flight crew's failure to adequately monitor and maintain clearance from a parked aircraft while taxiing. Contributing to the accident was an improperly parked airplane that encroached upon the taxiway area.

— NTSB Determination

Accident narrative

On May 21, 2009, about 1625 Pacific daylight time, an Embraer EMB-135KL, N843AE, taxied into a parked and unoccupied Embraer EMB-135KL, N848AE, while leaving the terminal hub at Los Angeles International Airport (LAX), Los Angeles, California. American Eagle operated the airplane under 14 Code of Federal Regulations Part 121 as flight 3085. The captain, first officer, 1 flight attendant, and 44 passengers were not injured. The accident airplane received substantial damage to the left horizontal stabilizer, and the parked airplane received substantial damage to the right horizontal stabilizer. The other Embraer was parked at the gate with no flight crew or passengers onboard. There were no ground injuries. Visual meteorological conditions prevailed for the flight and an instrument flight rules flight plan had been filed. The flight was destined for San Diego International Airport (SAN), San Diego, California.

In the company's submitted report (National Transportation Safety Board (NTSB) Pilot/Operator Aircraft Accident/Incident Report form 6120.1), American Eagle reported that ramp personnel pushed airplane back and instructed the captain to set the parking brake. After setting the parking brake, the tug was disconnected. The first officer contacted LAX ground control and was given a taxi clearance. As the captain started to taxi the airplane, along the taxiway center line, the flight crew felt a "bump." The captain stopped the airplane. The captain set the parking brake and shutdown the engines. Ramp personnel radioed the flight crew stating that their left horizontal stabilizer had struck the right horizontal stabilizer of an airplane parked at the gate. According to a Federal Aviation Administration (FAA) inspector who responded to the accident, the airplane had been pushed back from the gate via ground tow. Once disconnected from the tow bar, the captain started to taxi the airplane to the runway. As the captain was maneuvering around a parked airplane, the left horizontal stabilizer of the taxiing airplane struck the right horizontal stabilizer of the parked airplane.

The FAA inspector further reported that the parked airplane had been improperly parked with the right wing tip and horizontal stabilizer well outside the safety lines. It also appeared that the taxiing airplane may have been pushed back in such a manner that the left main landing gear was to the left of the taxi line placing it closer to the parked airplane.

Both the solid state flight data recorder (SSFDR), and solid state cockpit voice recorder (SSCVR) for the accident airplane were shipped to the NTSB vehicle recorder laboratory, Washington, D.C., for read out.

The SSFDR was a Honeywell SSFDR, model 980-4700, 256 word, serial number 09297. The SSFDR was received at the vehicle recorder division in good condition, and a normal extraction of the data was performed. An FDR group was not convened; the event was recorded on the SSFDR, with no pertinent findings.

The SSCVR was a Honeywell 6022 SSCVR 120, serial number 5550. The SSCVR was received at the vehicle recorder division's audio laboratory in good condition, and the data was extracted normally. A CVR group was not convened; the event was recorded on the SSCVR; however, the information did not add anything to the investigation. As a result of the ground collision, American Eagle had the lead-in lines redrawn to a 45-degree angle. If the flight crew was not able to make the drop off point to the lead-in lines for parking, they would have to taxi the airplane around the building or satellite terminal and rejoin the drop off point.

Contributing factors

  • cause Flight crew
  • factor Incorrect use/operation

Conditions

Weather
VMC, wind 260/13kt, vis 10sm

Loading the flight search…

What you can do on Flight Finder

  • Search flights between any two airports with live fares.
  • By aircraft — pick a plane model (e.g. Boeing 787, Airbus A350) and see every route it flies from your origin.
  • Route map — click any airport worldwide to explore its destinations, or draw a radius to find nearby airports.
  • Global aviation safety — aviation accident database, 5,200+ records since 1980, with map and rankings by aircraft and operator.
  • NTSB safety feed — recent U.S. aviation accidents and incidents from the official NTSB CAROL database, updated daily.

Frequently asked questions

How do I search flights by aircraft type on FlightFinder?

Pick an aircraft model — Boeing 737, Airbus A320, A380, Boeing 787 Dreamliner and more — enter your origin airport, and FlightFinder shows every route that plane flies from there with live fares.

Which aircraft types can I filter by?

We support Boeing 737/747/757/767/777/787, the full Airbus A220/A319/A320/A321/A330/A340/A350/A380 family, Embraer E170/E175/E190/E195, Bombardier CRJ and Dash 8, and the ATR 42/72 turboprops.

Is FlightFinder free to use?

Search and schedules are free. Pro ($4.99/month, $39/year, or $99 one-time lifetime) unlocks the enriched flight card — on-time stats, CO₂ per passenger, amenities, live gate & weather — plus My Trips with push alerts.

Where does the route data come from?

Live schedules come from Amadeus, AeroDataBox and Travelpayouts. Observed routes (which aircraft actually flew a given city pair) are crowdsourced from adsb.lol ADS-B data under the Open Database License.