FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

Flight 1877 · McDonnell Douglas MD-88

18 Feb 2008 · Austin, TX, United States

McDonnell Douglas MD-88 · Incident: collision with terrain/object (non-CFIT) on approach

From Hartsfield Jackson Atlanta International Airport (ATL) to Austin Bergstrom International Airport (AUS)

Report a problem

Event

NTSB case
DFW08IA073
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
Visual Meteorological Cond

McDonnell Douglas MD-88

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
N935DL
Operator
Unknown
Onboard fatalities
Unknown
Route
From Hartsfield Jackson Atlanta International Airport (ATL), Atlanta, GATo Austin Bergstrom International Airport (AUS), Austin, TX
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
Approach
Defining eventThe 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
Collision with terrain/object (non-CFIT)
DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
Minor

Cause areas

  • Environmental issues › Physical environment

Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.

NTSB narrative

A commercial air carrier was on a visual approach to a FAR Part 139 airport when it struck a bird (Black Vulture) approximately 9 miles from the airport at an altitude of 1,800 feet above ground level. The impact resulted in airframe vibrations; however, both of the turbofan engine indications remained normal. The airplane landed uneventfully, and further examination revealed that the vulture struck the lower right hand corner of the radome. The impact resulted in damage to the glide slope antenna mount, the lower nose-web, and outer fuselage skin. 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. 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 the airport, they do not have an FAA approved Wildlife Management Plan since there had been no previous incidents that fit the criteria set aside by FAR 139.337(a) or Advisory Circular 150/5200-33B, titled Hazardous Wildlife Attractants on or Near Airports that required such a plan.

Probable cause

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

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record DFW08IA073
Event ID
20080228X00243
Case number
DFW08IA073
Dataset
full-current
Source SHA-256
5cf380f0061817c0331a6b2d8cc7e0ee3a79bea469a1001dc5c10e56f35f5ab3
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, coordinates. 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: 5fde88b03eaaeabfec4a59cee1556b59f327f6283c0b21e4a4397421e8311ace; retrieved 2026-09-15T09:23:30.884Z.