NTSB CAROL · Event
Event DCA23LA278
Registry · N921US
FAA Aircraft Registry record.
Make / Model
AIRBUS A321-231
Year of manufacture
2015 · 8 years old at event
TCDS
A28NM · AIRBUS SAS
Engine
IAE V2533-A5
Seats / Engines
379 seats · 2 engines
Last airworthiness date
20150418
ADS-B equipped
Yes — Mode-S ACC3B4
Registrant of record
AMERICAN AIRLINES INC
Source: FAA Aircraft Registry (releasable master file).
Aircraft involved
Probable cause & findings
The captain’s failure to maintain the appropriate airspeed and pitch attitude during landing which resulted in a tailstrike.
Factual narrative
American Airlines flight 1753 sustained a tailstrike while landing at Charlotte Douglas International Airport (CLT), Charlotte, NC. The flight was a regularly scheduled domestic passenger flight from Fort Lauderdale, FL to CLT. According to the flight crew, the captain was the pilot flying, and the first officer (FO) was the pilot monitoring when they were cleared to land on runway 18L at CLT. The airplane was in the landing configuration and on a stabilized approach at 1,000 ft. above ground level (AGL). While crossing the runway’s threshold the wind shifted from a 6 -7 knot headwind component to a 6–7 knot tailwind component, the airspeed began to decay, and the airplane’s sink rate increased. In an effort to correct for the sink rate the captain applied back sidestick. The airplane touched down firmly and bounced, coincidentally the ground spoilers deployed which resulted in a nose high attitude. The airplane touched down a second time decelerated and taxied uneventfully to the gate. The captain stated that the ground spoiler deployment coinciding with the bounced touchdown resulted in an airplane nose-up pitch attitude. As a result, the pitch attitude increased until the tail struck the runway. After the tailstrike, and subsequent touchdown the remainder of the landing and landing rollout were normal with no risk of runway overrun or excursion. The tailstrike resulted in abrasion damage along the aft lower fuselage, over an area of about 14 feet long by 2 feet wide. An inspection revealed substantial damage to several frames. Source: NTSB Aviation Accident Database Retrieved: 2026-02-12
NTSB Findings
Hierarchical cause / factor breakdown from the FAA bulk avdata database. Each finding tagged C (Cause) or F (Factor).
- — Aircraft-Aircraft oper/perf/capability-Performance/control parameters-Pitch control-Not attained/maintained
- — Aircraft-Aircraft oper/perf/capability-Performance/control parameters-Airspeed-Not attained/maintained
- — Personnel issues-Task performance-Use of equip/info-Aircraft control-Pilot
Verbatim from NTSB's published report. Source file
NTSB_2023_DCA23LA278.txt.
Findings + structured fields enriched from FAA avall.mdb.
Full investigation docket on
data.ntsb.gov ↗.
Beyond the agency record
Search this event elsewhere.
Pre-filled searches into the sources where news + community discussion of aviation events lives. External sources are reported, not agency. Treat them as signal that something happened, not as fact about what happened.
Entity-clustered aviation events in the press — last 24 hr + 30-day archive.
Official agency record + docket.
Investigative docket: factual reports, photos, transcripts.
Long-running aviation incident database (Flight Safety Foundation).
Community NTSB synthesis blog — often has photos and witness reports.
Gold-standard aviation incident blog.
Aviation industry news search.
GA pilot forum — informed but rumor-prone.
GA pilot subreddit search.
Tail-number page — flight history (free tier limited).
AOPA Air Safety Institute search.
Mainstream press coverage. Recent events only.
Privacy-preserving news search.
External links open in a new tab. We don't ingest their content; we deep-link search queries.