FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

Southwest Airlines Flight 2534

13 Feb 2010 · Santa Clarita, CA, United States

Boeing 737-7H4 · Accident: abrupt maneuver on approach

From Harry Reid International Airport (LAS) to Hollywood Burbank/Bob Hope Airport (BUR)

Report a problem

Event

NTSB case
WPR10LA134
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

Boeing 737-7H4

Aircraft type
Boeing 737
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
N221WN
Onboard fatalities
Unknown
Route
From Harry Reid International Airport (LAS), Las Vegas, NVTo Hollywood Burbank/Bob Hope Airport (BUR), Burbank, CA
Aircraft age
Not recorded
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
Approach · IFR initial approach
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
Abrupt maneuver
DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
None

Cause areas

  • Aircraft › Aircraft oper/perf/capability
  • Personnel issues › Task performance

Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.

NTSB narrative

During descent to landing, the flight crew inadvertently turned about 27 degrees off their air traffic controller-assigned heading. When advised by the controller to check the airplane’s heading, the flight crew noted the heading discrepancy and immediately initiated a turn back to the assigned heading. During the turn, the flight crew received a traffic alert and collision avoidance system resolution advisory (RA). The captain responded to the RA by initiating an estimated 1,500- to 2,000-foot-per-minute rate of descent followed by an approximate 2,000-foot-per-minute climb. During the RA response maneuvers, three flight attendants were standing in the aft galley, one of whom was seriously injured.

Probable cause

The pilot’s abrupt airplane pitch change maneuver. Contributing to the accident was the flight crew’s failure to maintain the heading specified by the air traffic controller, which would have avoided the near collision course with an unidentified airplane that triggered the traffic alert and collision avoidance system resolution advisory.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record WPR10LA134
Event ID
20100216X20235
Case number
WPR10LA134
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, damage. 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: 1b40bd4fb2a2a3611cd7108a604e026961e4d43ea35c197295766efe151eaa6b; retrieved 2026-09-15T13:40:46.808Z.