NTSB CAROL · Event
Event WPR10LA134
Registry · N221WN
FAA Aircraft Registry record.
Make / Model
BOEING 737-7H4
Year of manufacture
2005 · 5 years old at event
TCDS
A16WE · THE BOEING CO
Engine
GE CFM56 SERIES
Seats / Engines
143 seats · 2 engines
Last airworthiness date
20051031
ADS-B equipped
Yes — Mode-S A1E6B9
Registrant of record
SOUTHWEST AIRLINES CO
Source: FAA Aircraft Registry (releasable master file).
Aircraft involved
Probable cause & findings
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.
Factual narrative
On February 13, 2010, about 1445, Pacific standard time, a Boeing 737-7H4, N221WN, abruptly maneuvered during radar vectors for initial approach to the Bob Hope Airport, Burbank, California. At the time, the airplane was about 20 miles northwest of Burbank. The 2 pilots, 80 passengers and 1 of the 3 flight attendants were not injured. The remaining 2 flight attendants sustained a minor and a serious injury. The airplane was not damaged. The airplane was registered and operated by Southwest Airlines as Flight #2534, under the provisions of Title 14 Code of Federal Regulations Part 121. Visual meteorological conditions prevailed for the flight which was operated on an instrument flight rules flight plan. The scheduled domestic passenger flight originated from Las Vegas, Nevada, at 1354. The Airline Transport Pilot (ATP) captain stated that he was the pilot flying and the ATP First Officer was the pilot monitoring, as they descended for landing. The Approach Air Traffic Controller (ATC) issued the flight a clearance to fly a 190-degree heading and descend to and maintain 6,000 feet. The captain stated that he set a 190 degree heading in the heading window and selected 6,000 feet in the altitude window of the airplane's mode control panel (MCP) used to set autopilot functions and was subsequently verified by the first officer. The captain stated that as the flight continued, the controller issued a traffic information alert for traffic at their 11 o'clock position and roughly 4 miles away. The captain said that the flight crew began scanning for the traffic and received a Traffic Collision Avoidance System (TCAS) traffic advisory (TA), which identified that the traffic was about 500 feet below their airplane's altitude. The captain stated that he began to shallow the airplane's rate of descent to its assigned altitude of 6,000 feet to avoid the traffic. Subsequently, the controller advised the flight crew to check the airplane's heading. The captain said that he noticed that he had inadvertently allowed the airplane to turn to a 163-degree heading and immediately initiated a turn back to the assigned heading of 190 degrees. During the turn, the crew received a TCAS resolution alert (RA) to descend at 1,500 to 2,000 feet per minute (fpm), followed by a command to climb at 2,000 fpm. The captain further reported that the RA commands were followed and that during the climb portion, they observed traffic ahead of their position about 2 miles away and slightly higher in altitude. The captain stated that he responded by making a shallow turn to the right to avoid the traffic. At the time of the accident, all of the passengers were seated with their seatbelts fastened. The flight attendants stated that all three of them were standing in the aft galley and were making their final preparations for landing. One flight attendant sustained a fractured left scapula. 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. 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 Aircraft-Aircraft oper/perf/capability-Performance/control parameters-Pitch control-Incorrect use/operation - C
- C Personnel issues-Task performance-Use of equip/info-Aircraft control-Pilot - C
- F Environmental issues-Operating environment-Air traffic/operating proc-(general)-Compliance w/ procedure - F
Verbatim from NTSB's published report. Source file
NTSB_2010_WPR10LA134.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 (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.
- 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.
- arXiv 2021 · arXiv preprint
An Adaptive Digital Autopilot for Fixed-Wing Aircraft with Actuator Faults
This paper develops an adaptive digital autopilot for a fixed-wing aircraft and compares its performance with a fixed-gain autopilot.
- arXiv 2020 · arXiv preprint
Reinforcement Learning for Robust Missile Autopilot Design
Designing missiles' autopilot controllers has been a complex task, given the extensive flight envelope and the nonlinear flight dynamics.
Browse the full corpus — academia portal ↗