Delta Air Lines Flight 565
Boeing B757-232 · Accident: dragged wing, rotor, pod, float or tail/skid during landing
From Hartsfield Jackson Atlanta International Airport (ATL) to Luis Munoz Marin International Airport (SJU)
Event
- NTSB case
- DCA06FA068
- 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
- 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
Boeing B757-232
- Aircraft type
- Boeing 757
- 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
- N622DL
- Operator
- Delta Air Lines
- Onboard fatalities
- Unknown
- Route
- From Hartsfield Jackson Atlanta International Airport (ATL), Atlanta, GATo Luis Munoz Marin International Airport (SJU), San Juan, PR
- 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
- Dragged wing, rotor, pod, float or tail/skid
- 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
- Copilot/second pilot › Flare, excessive
- Copilot/second pilot › Stabilator trim, inadvertent activation
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The crew elected to conduct a practice autoland approach during a scheduled airline flight in order to recertify the airplane for category 3 (CAT III) autoland procedures. Airline procedures permit crews to conduct such approaches when weather is at category 1 (CAT I) minimums or better. Weather at the time of the accident included good visual conditions, and was not a factor in the accident. Additionally, wake turbulence was not a factor in the accident. The airline's flight operations manual stated: "Except for facilities that have a restrictive note, autoland approaches are permissible to all [instrument landing system (ILS)] facilities. When a restrictive note regarding the localizer or glide slope appears on [an approach chart], autoland is not authorized." The ILS runway 8 approach chart was notated "unusable from 0.8 nm to threshold." The crew reported, and the flight data recorder (FDR) confirmed, that the airplane began to drift off the centerline of the approach at about three-quarters of a mile from the runway threshold. The drift was consistent with the direction of the wind and the ILS chart notation. Additionally, both Federal Aviation Administration (FAA) advisory material, and the airline's flight operations manual direct pilots to advise air traffic control (ATC) when conducting an autoland approach, to allow ATC to ensure that appropriate areas are clear of vehicles or other obstructions which may affect the localizer signals. The flight crew did not advise ATC of the autoland approach. After the airplane drifted off the centerline, the first officer disconnected the autopilot and hand-flew the airplane back to the center of the runway, thereby prolonging the flare. Airline training material noted that a prolonged flare is a risk factor for tailstrikes. The airplane did not touch down until approximately 4,000 feet from the landing threshold. Recovering from the drift off-centerline led to the first officer prolonging the flare, and landing long, at a lower speed than nominal. FDR information indicated that during the landing flare, the horizontal stabilizer moved to a position that would command full nose up trim. During the landing, the tail struck the ground, and the airplane received substantial damage. An assessment of the Boeing 757 horizontal stabilizer trim control system indicated that the rate of trim change seen during the flare could only be achieved by operating the control yoke stabilizer trim switch, or by using the stabilizer trim control levers on the center pedestal. Post-accident tests of the trim system revealed no anomalies. During a post-accident training session, the first officer was noted to handle the yoke such that he inadvertently activated the trim switch to the nose-up position. Airline training material noted that use of nose-up trim during the flare is a risk factor for tailstrikes. Analysis of the evidence indicates it is likely that during the flare, the first officer inadvertently activated full nose up trim, resulting in abnormal control forces on the yoke and a higher than normal pitch attitude, leading to the tailstrike.
Probable cause
the first officer's inadvertent application of full nose-up trim during a prolonged flare, resulting in an excessive pitch angle during landing and subsequent tailstrike. Contributing to the accident was the flight crew's failure to correct the airplane's drift from the centerline approach course during short final approach, leading to the prolonged flare, and their improper decision to perform a practice autoland approach using a restricted procedure.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record DCA06FA068
- Event ID
- 20060908X01318
- Case number
- DCA06FA068
- 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. 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: 85bc944a50d55a975cc7a85337e701fa3d59d906fd1dc4e78bc7ac57c758692f; retrieved 2026-09-18T14:50:36.843Z.