FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

American Airlines Flight 2065

21 Mar 2006 · Denver, CO, United States

McDonnell Douglas DC-9-82 · Incident: on ground/water collision with terrain/water during landing

From Dallas Fort Worth International Airport (DFW) to Denver International Airport (DEN)

Report a problem

Event

NTSB case
DEN06IA051
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 DC-9-82

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
N574AA
Onboard fatalities
Unknown
Route
From Dallas Fort Worth International Airport (DFW), DALLAS-FORT WOR, TXTo Denver International Airport (DEN), Denver, CO
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 · flare/touchdown
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
On ground/water collision with terrain/water
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

  • Pilot in command › Flare, improper
  • Pilot in command › Procedures/directives, not followed

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

NTSB narrative

According to the flight crew, the departure, en route, and initial approach phases were reported to be without incident. During the approach, the crew selected gear down and flaps 28 [degrees] for landing and the landing weight was 127,000 pounds. The air traffic control tower reported the winds at 100 degree and 6 knots. The airplane broke out of a thin cloud layer with the base at approximately 1,000 feet above ground level. At 100 feet above the runway, the captain detected a "sinker" and then applied thrust to arrest the sink. The aircraft continued to sink in the flare and made a "very firm landing with no bounce." A review of the DFDR data revealed that a few seconds prior to touchdown, the airspeed decreased 6 knots below Vref, and the pitch attitude changed from 2.1 degrees to 5.3 degrees. A vertical acceleration of 2.032 Gs was recorded at an airspeed of 129.2 knots. Vref was calculated at 135 knots. The pilot reported applying thrust when the sink rate was detected; however, the DFDR data revealed that the engine EPR's did not increase until 7 seconds after touchdown. According to company procedures, "A stabilized approach means the airplane must be: at approach speed (VREF + additives); on the proper flight path at the proper sink rate, and at stabilized thrust. These requirements must be maintained throughout the rest of the approach for it to be considered a stabilized approach. If the stabilized approach requirements cannot be satisfied by the minimum stabilized approach heights or maintained throughout the rest of the approach, a go-around is required." The CVR recording consisted of four channels of audio information; however, none of the audio was pertinent to the incident investigation. The audio was consistent with the CVR being overwritten or recorded over by subsequent events.

**This narrative was modified on May 22, 2007.**

Probable cause

the captain's failure to follow existing company procedures for stabilized approach.

**This report was modified on May 23, 2007.**

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record DEN06IA051
Event ID
20060330X00368
Case number
DEN06IA051
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, 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: 7dbd20894a331c08f87befcf7674cbf61ef4dc33c8317687faea79ad8d11938a; retrieved 2026-09-18T14:54:32.218Z.