Delta Air Lines Flight 800
Airbus A321 211 · Accident: tailstrike during landing
From Boston Logan International Airport (BOS) to Hartsfield Jackson Atlanta International Airport (ATL)
Event
- NTSB case
- DCA17LA145
- 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
Airbus A321 211
- Aircraft type
- Airbus A321
- 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
- N315DN
- Operator
- Delta Air Lines
- Onboard fatalities
- Unknown
- Route
- From Boston Logan International Airport (BOS), Boston, MATo Hartsfield Jackson Atlanta International Airport (ATL), Atlanta, GA
- Aircraft age
- About 1 year (built 2016)
- 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
- 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
- Tailstrike
- 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
- Personnel issues › Task performance
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The first officer was on her third day of initial operating experience training and was the pilot flying for the flight; the captain, a check airman, was the pilot monitoring. The first officer reported that this was her fourth landing in an A320-series airplane and her first landing in an A321 model. According to the captain and first officer, the flight was cleared for the visual approach, the approach was stable, and wind was out of the southwest at 12 kts with gusts up to 20 kts. The first officer recalled that the captain instructed her to "pull back pull back" before touchdown. Both pilots reported that the landing was “firm.” The first officer stated that after landing, the captain provided feedback that she flared a little low (near 20 ft above ground level [agl] instead of 30 ft agl) and did not provide enough pitch back on the side stick. Both crewmembers reported that the first officer was late to flare on previous landings. A company pilot who was seated in the cockpit jumpseat reported the captain was providing instruction to the first officer during the flight about the nuances of the A321. He stated that the descent and arrival were uneventful up until the flare and that the first officer “never really performed any type of flare maneuver even as the captain repeatedly called for the F/O to perform one." Subsequent preflight inspection of the airplane by the next flight crew revealed an area of abrasion damage to the aft fuselage about 13 ft long by 2 ft wide affecting two skin panels. The fuselage skin was abraded through in several areas with damage to the underlying stringers and frames. Several frames, stringers, and shear clips were also bent and/or fractured.
Probable cause
The first officer's improper landing flare, which resulted in a hard, bounced landing, and the flight crew’s improper bounced landing recovery procedures.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record DCA17LA145
- Event ID
- 20170625X04604
- Case number
- DCA17LA145
- 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. 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: af47a0f7a13ed3d00c5b5c126ebcc123b5e8cec3dfa3d704e9b4e1ff7392ae52; retrieved 2026-09-16T05:27:21.662Z.