FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

American Eagle Airlines Saab 340B accident

21 Mar 2000 · Killeen, TX, United States

Saab 340B · Accident: overrun during landing

From Dallas Fort Worth International Airport (DFW) to Skylark Field (ILE)

Report a problem

Event

NTSB case
FTW00FA101
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
Accident
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
Instrument Meteorological Cond

Saab 340B

Aircraft type
Saab 340
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
N353SB
Onboard fatalities
Unknown
Route
From Dallas Fort Worth International Airport (DFW), DFW AIRPORT, TXTo Skylark Field (ILE), Killeen, 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
Landing · landing roll
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
Overrun
DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
Substantial

Cause areas

  • Pilot in command › Brakes(normal), delayed
  • Pilot in command › Procedures/directives, not followed
  • Pilot in command › Touchdown, delayed

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

NTSB narrative

The captain was the flying pilot for the night landing on runway 01 in instrument meteorological conditions (IMC), with a right cross wind from 110 degrees at 14 gusting 18 knots, drizzle, and a wet runway. Prior to starting the approach, the flightcrew determined that the landing approach speed (Vref) and the approach speed (Vapp) were 122 and 128 knots, respectively. DFDR data showed the airplane flying on autopilot as it passed the middle marker at 200 feet AGL at 130 knots on the ILS approach. Approximately 3 seconds after the first officer called "runway in sight twelve o'clock," the captain disconnected the autopilot, while at a radio altitude of 132 feet and on a heading of approximately 18 degrees. Within approximately 11 seconds after the autopilot disconnect, the glideslope and localizer deviation increased. The first officer called "runway over there." Approximately 5 seconds before touchdown, the airplane rolled right, then left, then right. DFDR data-based performance calculations showed the airplane crossed the threshold at an altitude of 35 feet and 130 knots. The airplane touched down 2,802 feet from the approach end of the 5,495-foot runway (844-foot displaced threshold) at 125 knots on a heading of 10 degrees. The airplane overran the runway and struck a ditch 175 feet beyond the departure end of the runway. Landing roll calculations showed a ground roll of 2,693 feet after touchdown, consisting of 1,016 feet ground roll before braking was initiated and 1,677 feet ground roll after braking was initiated until the airplane exited the pavement. According to Saab, for a wet runway, the aircraft would have needed 1,989 feet from the time of braking initiation to come to a complete stop. The American Eagle Airlines, Inc., FAA approved aircraft operating manual (AOM), states in part: Stabilized approaches are essential when landing on contaminated runways. Landing under adverse weather conditions, the desired touch-down point is still 1,000 feet from the approach end of the runway. Touchdown at the planned point. Cross the threshold at Vapp, then bleed off speed to land approximately Vref -5. Use reverse, if needed. To achieve maximum braking effect on wet runway, apply maximum and steady brake pressure. In 1992, the City of Killeen submitted a proposal that included extending the north end of runway 01 by 194 feet. The FAA originally disapproved the proposal, in part, because the runway extension decreased the length of the runway safety area (RSA) which was already shorter than the recommended 1,000 feet for a 14 CFR Part 139 certificated airport. The proposal was subsequently approved and a drainage ditch was installed in the north RSA, perpendicular to the runway and approximately 175 feet north of the departure end of runway 01. In 1993, the airport received FAA Part 139 certification. The 1998 and 1999, FAA airport certification inspection reports noted the inadequate RSA; however, neither letter of correction, sent from the FAA to the City of Killeen following the inspections, mentioned the RSA. Following this accident, the ILS runway 01 was flight checked by the FAA and all components were found to be operating within prescribed tolerances. Examination of the airplane found no anomalies that would have prevented it from operating per design prior to departing the runway and encountering the ditch.

Probable cause

the captain's failure to follow standard operating procedure for landing on a contaminated ruway in that he touched down long, which combined with his delayed braking resulted in a runway overrun. Contributing factors were the captain's failure to maintain runway alignment following his disconnect of the autopilot, the gusty crosswind and the wet runway. In addition, the following were contributing factors: (1) the airport operator's failure to fill in a ditch in the runway safety area, (2) the FAA's granting of 14 CFR Part 139 approval to the airport when the runway safety area (RSA) did not meet the recommended length for a Part 139 airport, and (3) the FAA's continued lack of acknowledgement to the airport of the inadequate RSA following their annual airport inspection checks.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record FTW00FA101
Event ID
20001212X20624
Case number
FTW00FA101
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, coordinates. Values present in the bulk record are kept.
  • The date is the local date; the NTSB stores the UTC date 2000-03-22.
  • API snapshot SHA-256: 28731d57d415d079362f5959375c715f2cd7c5eb28015f991c0c543674c4b73c; retrieved 2026-09-18T16:43:43.822Z.