NTSB CAROL · Event
Event DCA14CA034
Registry · N8327A
FAA Aircraft Registry record.
Make / Model
BOEING 737-8H4
Year of manufacture
2012 · 2 years old at event
TCDS
A16WE · THE BOEING CO
Engine
CFM INTL CFM56-7B27E
Seats / Engines
143 seats · 2 engines
Last airworthiness date
20121210
ADS-B equipped
Yes — Mode-S AB6316
Registrant of record
UMB BANK NA TRUSTEE
Source: FAA Aircraft Registry (releasable master file).
Aircraft involved
Probable cause & findings
the captain's over rotation during the bounced landing.
Factual narrative
On January 3, 2014, at approximately 1930 pacific standard time, Southwest Airlines flight 2516, a Boeing 737-800, N8327A, experienced a tail strike during landing at McCarran International Airport (KLAS), Las Vegas, Nevada. There were no injuries to the 180 passengers and crew onboard and the airplane was substantially damaged. The flight was operating as a regularly scheduled passenger flight and originated from Orlando International Airport (KMCO), Orlando, Florida. According to the operator, the captain was the pilot flying and the first officer (FO) was the pilot monitoring. The accident flight was the first and only scheduled flight for the day for both crew members. Both pilots indicated that takeoff through the initial descent was uneventful. The aircraft was configured for a flaps 30 landing. During the ILS approach to runway 25L, the captain used the Heads-up Guidance System (HGS) in the IMC mode. During the decent below 100 feet, the FO indicated that the runway environment was dark and sensed the runway was "coming close fast". He noted a slightly increased descent rate and before he could make a callout, the captain had begun to take corrective action. During the descent, the captain stated he was hand flying the airplane (autopilot and autothrottles were off) and used the localizer, glideslope and flare cues from the HGS. At approximately 30 feet, he transitioned from the HGS to the runway environment, noting it appeared "pitch black." He then noticed the runway edge lights and what appeared to be an increased sink rate. Both pilots indicated the airplane touched down firm, then bounced, and the second touch down was harder than the first. Neither were aware that they had struck the tail. The captain did not recall seeing a tail strike warning indication from the HGS. Post flight inspection revealed that the tail strike indicator was compressed and deep scrapes and wear damage to the lower aft fuselage skin. Further investigation revealed multiple fractured frames and buckled stringers, shear ties and straps. On January 3, 2014, at approximately 1930 pacific standard time, Southwest Airlines flight 2516, a Boeing 737-800, N8327A, experienced a tail strike during landing at McCarran International Airport (KLAS), Las Vegas, Nevada. There were no injuries to the 180 passengers and crew onboard and the airplane was substantially damaged. The flight was operating as a regularly scheduled passenger flight and originated from Orlando International Airport (KMCO), Orlando, Florida. According to the operator, the captain was the pilot flying and the first officer (FO) was the pilot monitoring. The accident flight was the first and only scheduled flight for the day for both crew members. Both pilots indicated that takeoff through the initial descent was uneventful. The aircraft was configured for a flaps 30 landing. During the ILS approach to runway 25L, the captain used the Heads-up Guidance System (HGS) in the IMC mode. During the decent below 100 feet, the FO indicated that the runway environment was dark and sensed the runway was "coming close fast". He noted a slightly increased descent rate and before he could make a callout, the captain had begun to take corrective action. During the descent, the captain stated he was hand flying the airplane (autopilot and autothrottles were off) and used the localizer, glideslope and flare cues from the HGS. At approximately 30 feet, he transitioned from the HGS to the runway environment, noting it appeared "pitch black." He then noticed the runway edge lights and what appeared to be an increased sink rate. Both pilots indicated the airplane touched down firm, then bounced, and the second touch down was harder than the first. Neither were aware that they had struck the tail. The captain did not recall seeing a tail strike warning indication from the HGS. Post flight inspection revealed that the tail strike indicator was compressed and deep scrapes and wear damage to the lower aft fuselage skin. Further investigation revealed multiple fractured frames and buckled stringers, shear ties and straps. 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).
- C Personnel issues-Action/decision-Action-Incorrect action performance-Pilot - C
Verbatim from NTSB's published report. Source file
NTSB_2014_DCA14CA034.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.
Related research
What the literature says.
Academic papers and agency reports matching this event's aircraft type or causal vocabulary (imc, autopilot). Sourced from NASA NTRS, NTSB Safety Studies, FAA CAMI, AOPA Air Safety Institute, Embry-Riddle Scholarly Commons, arXiv, and the Semantic Scholar academic graph.
- NASA NTRS 2019 · Technical Memorandum (TM)
A preliminary study of a wake vortex encounter hazard boundary for a B737-100 airplane
A preliminary batch simulation study was conducted to define the wake decay required for a Boeing 737-100 airplane to safely encounter a Boeing 727 wake and land.
- NASA NTRS 2018 · Other
A Numerical Simulation Study to Develop an Acceptable Wake Encounter Boundary for a B737-100 Airplane
The National Aeronautics and Space Administration (NASA) is conducting research with the goal of enabling safe improvements in the capacity of the nation's air transportation system.
- arXiv 2025 · arXiv preprint
ROSflight 2.0: Lean ROS 2-Based Autopilot for Unmanned Aerial Vehicles
ROSflight is a lean, open-source autopilot ecosystem for unmanned aerial vehicles (UAVs). Designed by researchers for researchers, it is built to lower the barrier to entry to UAV research and acceler…
- arXiv 2025 · arXiv preprint
ROSplane 2.0: A Fixed-Wing Autopilot for Research
Unmanned aerial vehicle (UAV) research requires the integration of cutting-edge technology into existing autopilot frameworks.
- arXiv 2024 · arXiv preprint
A Data-Driven Autopilot for Fixed-Wing Aircraft Based on Model Predictive Control
Autopilots for fixed-wing aircraft are typically designed based on linearized aerodynamic models consisting of stability and control derivatives obtained from wind-tunnel testing.
- arXiv 2022 · arXiv preprint
Experimental Flight Testing of a Fault-Tolerant Adaptive Autopilot for Fixed-Wing Aircraft
This paper presents an adaptive autopilot for fixed-wing aircraft and compares its performance with a fixed-gain autopilot.
Browse the full corpus — academia portal ↗