18 Feb 2008: McDonnell Douglas MD-88 — DELTA AIR LINES INC

18 Feb 2008: McDonnell Douglas MD-88 (N935DL) — DELTA AIR LINES INC

No fatalities • Austin, TX, United States

Probable cause

The airplane struck a large bird while making a visual approach to the airport.

— NTSB Determination

Accident narrative

On February 18, 2008, at 1430 central standard time, a McDonnell Douglas MD-88, N935DL, operating as Delta Air Lines flight 1877, sustained minor damage when it struck a large bird while on a visual approach to Runway 35R at Austin Bergstrom International Airport (AUS), Austin, Texas. None of the 5 crew members or 135 passengers were injured. A instrument flight rules flight plan was filed for the flight that departed Hartsfield-Jackson Atlanta International Airport (ATL), Atlanta, Georgia, at 1311, and was destined for Austin. Visual meteorological conditions prevailed for the schedule passenger flight conducted under 14 Code of Federal Regulations Part 121.

The captain and first officer provided similar accounts of the incident. According to the captain's statements, the airplane was at an altitude of 1,800 feet above ground level (agl), approximately 4 to 5 miles from the airport, and at an airspeed of 210 knots, when he and the first officer saw two large birds in front of the airplane. Moments later one of the birds struck the bottom right side of the radome. The impact resulted in airframe vibrations; however, both engine indications remained normal. The first officer then declared an emergency and the captain informed the passengers about what had happened since it was "obvious we had collided with something." The airplane landed uneventfully, and once clear of the runway, the captain asked the airport's rescue and fire fighting (ARFF) personnel to assess the damage. They reported the impact area was "quite large with the bird imbedded into the radome."

Federal Aviation Administration (FAA) safety inspectors performed an on-scene examination of the airplane. According to an inspector, the bird struck the lower right hand corner of the radome (as viewed from the cockpit). As a result, the glide slope antenna mount, the lower nose-web, and outer fuselage skin was damaged. In addition, the forward bulkhead (non-pressurized) fuselage rib was torn. Blood was also observed on the right engine's nacelle; however, an inspection of the first and second stage blades revealed no damage.

Austin airport operations personnel sent photographs and feathers of the deceased bird to the Feather Identification Laboratory at the Smithsonian Institution, Museum of Natural History, who identified the bird as a Black Vulture. Airport operations personnel also produced several Airport Noise and Operations Monitoring System (ANOMS) plots, which showed that when the airplane was at a 1,800 agl, it was approximately 9 miles from the airport.

A review of Federal Aviation Regulation (FAR) 139.337(a), titled Wildlife Hazard Management, revealed that a certificate holder is required to conduct an ecological study (Wildlife Hazard Assessment) if an air carrier aircraft experiences a multiple bird strike, an engine ingestion, or a damaging collision with wildlife other than birds. Part 139 also requires that an assessment be conducted if wildlife of a size or in numbers capable of causing one of these events is observed to have access to any airport flight pattern or movement area.

According to a representative of Austin Airport, he said the airport "...does not have an FAA approved Wildlife Management Plan. To date there have been no incidents here at [AUS] that fits the criteria set aside by FAR 139.337(a) or [Advisory Circular 150/5200-33B, titled Hazardous Wildlife Attractants on or Near Airports] requiring such a plan."

Contributing factors

  • cause Animal(s)/bird(s)

Conditions

Weather
VMC, wind 020/09kt, 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.