4 Jan 2014: BOEING 737 8H4 — SOUTHWEST AIRLINES CO

4 Jan 2014: BOEING 737 8H4 (N8327A) — SOUTHWEST AIRLINES CO

No fatalities • Las Vegas, NV, United States

Probable cause

the captain's over rotation during the bounced landing.

— NTSB Determination

Accident 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.

Contributing factors

  • cause Pilot

Conditions

Weather
VMC, wind 190/07kt, vis 10sm

Loading the flight search…

What you can do on Flight Finder

  • Search flights between any two airports with live fares.
  • By aircraft — pick a plane model (e.g. Boeing 787, Airbus A350) and see every route it flies from your origin.
  • Route map — click any airport worldwide to explore its destinations, or draw a radius to find nearby airports.
  • Global aviation safety — aviation accident database, 5,200+ records since 1980, with map and rankings by aircraft and operator.
  • NTSB safety feed — recent U.S. aviation accidents and incidents from the official NTSB CAROL database, updated daily.

Frequently asked questions

How do I search flights by aircraft type on FlightFinder?

Pick an aircraft model — Boeing 737, Airbus A320, A380, Boeing 787 Dreamliner and more — enter your origin airport, and FlightFinder shows every route that plane flies from there with live fares.

Which aircraft types can I filter by?

We support Boeing 737/747/757/767/777/787, the full Airbus A220/A319/A320/A321/A330/A340/A350/A380 family, Embraer E170/E175/E190/E195, Bombardier CRJ and Dash 8, and the ATR 42/72 turboprops.

Is FlightFinder free to use?

Search and schedules are free. Pro ($4.99/month, $39/year, or $99 one-time lifetime) unlocks the enriched flight card — on-time stats, CO₂ per passenger, amenities, live gate & weather — plus My Trips with push alerts.

Where does the route data come from?

Live schedules come from Amadeus, AeroDataBox and Travelpayouts. Observed routes (which aircraft actually flew a given city pair) are crowdsourced from adsb.lol ADS-B data under the Open Database License.