The U.S. aircraft register, updated daily
Accidents · NTSB DCA13FA131 · Final report

Boeing 737 7H4 accident near Flushing, New York, July 22, 2013

On July 22, 2013 at about 9:00 pm local time, a 1999 Boeing 737 7H4, registered N753SW, was substantially damaged in an accident during landing (flare/touchdown) near Flushing, New York (La Guardia airport). It was flown under scheduled airline rules (Part 121). 8 people had minor injuries; 142 others were unhurt. The weather was visual conditions (good weather).

The NTSB's probable cause their words, unchanged

The captain's attempt to recover from an unstabilized approach by transferring airplane control at low altitude instead of performing a go-around. Contributing to the accident was the captain's failure to comply with standard operating procedures.

Source: NTSB aviation accident database, copy made October 5, 2026. Docket and reports at the NTSB.

What the record shows

Date
July 22, 2013 · about 9:00 pm local time
Place
Flushing, New York · La Guardia · map
Type
Accident
Injuries
8 people had minor injuries; 142 others were unhurt.
Weather
visual conditions (good weather)
Aircraft
Boeing 737 7H4 7H4, built 1999 · all 737 7H4s on the register
Registration
N753SW · no longer on the register · serial 29848
Damage
Substantial damage
Flight
Flight · scheduled airline rules (Part 121)

The NTSB's narrative final · quoted from the NTSB record

As the airplane was on final approach, the captain, who was the pilot monitoring (PM), realized that the flaps were not configured as had been briefed, with a setting of 40 degrees for the landing. Data from the flight data recorder (FDR) indicate that the captain set the flaps to 40 degrees as the airplane was descending through about 500 ft altitude, which was about 51 seconds from touchdown. When the airplane was between 100 to 200 ft altitude, it was above the glideslope. Concerned that the airplane was too high, the captain exclaimed repeatedly "get down" to the first officer about 9 seconds from touchdown. About 3 seconds from touchdown when the airplane was about 27 ft altitude, the captain announced "I got it," indicating that she was taking control of the airplane, and the first officer replied, "ok, you got it." According to FDR data, after the captain took control, the control column was relaxed to a neutral position and the throttles were not advanced until about 1 second before touchdown. The airplane touched down at a descent rate of 960 ft per minute and a nose-down pitch attitude of -3.1 degrees, resulting in the nose gear contacting the runway first and a hard landing. The airplane came to a stop on the right side of the runway centerline about 2,500 ft from its initial touchdown. The operator's stabilized approach criteria require an immediate go-around if the airplane flaps or landing gear were not in the final landing configuration by 1,000 ft above the touchdown zone; in this case, the flaps were not correctly configured until the airplane was passing through 500 ft. Further, the airplane's deviation about the glideslope at 100 to 200 ft would have been another opportunity for the captain, as the PM at this point during the flight, to call for a go-around, as indicated in the Southwest Airlines Flight Operations Manual (FOM). Accident data suggest that pilots often fail to perform a go-around or missed approach when stabilized approach criteria are not met. A review of NTSB-investigated accidents by human factors researchers found that about 75% of accidents were the result of plan continuation errors in which the crew continued an approach despite cues that suggested it should not be continued. Additionally, line operations safety audit data presented at the International Air Safety Summit in 2011 suggested that 97% of unstabilized approaches were continued to landing even though doing so was in violation of companies' standard operating procedures (SOPs). The Southwest FOM also states that the captain can take control of the airplane for safety reasons; however, the captain's decision to take control of the airplane at 27 ft above the ground did not allow her adequate time to correct the airplane's deteriorating energy state and prevent the nose landing gear from striking the runway. The late transfer of control resulted in neither pilot being able to effectively monitor the airplane's altitude and attitude. The first officer reported that, after the captain took control of the airplane, he scanned the altimeter and airspeed to gain situational awareness but that he became distracted by the runway "rushing" up to them and "there was no time to say anything." The captain should have called for a go-around when it was apparent that the approach was unstabilized well before the point that she attempted to salvage the landing by taking control of the airplane at a very low altitude. In addition, the captain did not follow SOPs at several points during the flight. As PM, she should have made the standard callout per the Southwest FOM when the airplane was above glideslope, stating "glideslope" and adding a descriptive word or words to the callout (for example, "one dot high"). Rather than make this callout, however, the captain repeatedly said "get down" to the first officer before stating "I got it." The way she handled the transfer of airplane control was also contrary to the FOM, which indicates that the PM should say "I have the aircraft." The flight crew's performance was indicative of poor crew resource management.

The complete narrative as the NTSB published it. The NTSB's docket holds the report as a PDF and any photographs, statements and other documents from the investigation.

The factual record from the NTSB's investigation tables, in plain English

What happened, in order

  1. Hard landing during landing (flare/touchdown) defining event
  2. Landing gear collapse during landing (flare/touchdown)

The NTSB's findings

  • Aircraft › Aircraft oper/perf/capability › Performance/control parameters › Descent/approach/glide path › Not attained/maintained
  • cause Personnel issues › Action/decision › Action › Lack of action › Pilot
  • factor Personnel issues › Task performance › Use of equip/info › Use of policy/procedure › Pilot

Pilot

  • Certificate: airline transport pilot
  • Ratings: multi-engine land; single-engine land; instructor: airplane multi-engine; instructor: airplane single-engine; instructor: instrument airplane; instrument: airplane
  • Flight time: 12,522 hours in all; 7,909 in this make and model; 181 in the last 90 days; 64 in the last 30 days; 7,205 as pilot in command; 2,024 on instruments
  • Last flight review: July 8, 2013
  • Medical certificate: Class 1 (with waivers/limitations)
  • Seat: left
  • Injury: no injuries

Co-pilot

  • Certificate: airline transport pilot
  • Ratings: multi-engine land; single-engine land; instructor: instrument airplane; instrument: airplane
  • Flight time: 5,200 hours in all; 1,100 in this make and model; 200 in the last 90 days; 70 in the last 30 days; 4,000 as pilot in command; 1,000 on instruments
  • Last flight review: December 1, 2012
  • Medical certificate: Class 1 (without waivers/limitations)
  • Seat: rgt
  • Injury: minor injuries

The aircraft

  • Maximum gross weight: 154,500 lb
  • Landing gear: retractable
  • Engine 1: Cfm Intl. CFM56 SERIES (turbofan); 0 hours total
  • Engine 2: Cfm Intl. CFM56 SERIES (turbofan); 0 hours total
  • Operator: Southwest Airlines CO

The flight

  • Departed from: BNA Nashville TN at 7:33 pm
  • Destination: LGA Flushing NY
  • Flight plan: IFR
  • Runway 04, 7,001 ft by 150 ft
  • A second pilot was aboard

Weather at the time

  • Light: daylight
  • Wind: from 040° at 8 knots
  • Visibility: 7 statute miles
  • Sky: broken clouds at 7,500 ft; scat at 3,000 ft
  • Temperature: 77°F (25°C), dew point 72°F (22°C)
  • Altimeter: 29.85 inHg
  • Observation at 9:51 pm from KLGA

Injuries

FatalSeriousMinorNone
Cabi3
Flight crew2
LapC1
Passengers3141

Documents from the investigation the NTSB's docket: the evidence folder behind the report

The docket, the folder of records gathered during an investigation (maintenance records, photographs, witness statements, examinations), has not been read from the NTSB for this case yet; the list appears here once it has. Open the docket at the NTSB.

Everything on this page comes from the NTSB's public records. The narrative, probable cause and findings are the NTSB's own words; the coded tables behind the report are written out in plain English, with pilots' ages, home towns and medical details left out. The documents and photographs are the NTSB's docket, shown as the NTSB released them. This site's own text never names anyone involved. A preliminary report can change; the final report usually follows one to two years later, and the page is refreshed when it does.