Southwest Airlines Boeing 737-7H4 incident
Boeing 737-7H4 and Meng Ye Diamond Aircraft IND Inc DA 40 · Incident: air traffic event during landing
Event
- NTSB case
- OPS25LA005
- 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
- Incident
- InvestigationHow far the investigation had got when the record was published: preliminary, ongoing, final or completed. Unknown where the source does not say. Glossary
- Ongoing
- Event fatalities
- Unknown
- 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
Aircraft 1 · 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
- N250WN
- Operator
- Southwest Airlines
- Onboard fatalities
- Unknown
- Route
- From Oakland San Francisco Bay Airport (OAK), Oakland, CATo Long Beach International Airport (LGB), Long Beach, CA
- Aircraft age
- About 18 years (built 2006)
- 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
- Landing · landing roll
- 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
- Air traffic event
- DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
- None
Aircraft 2 · Diamond Aircraft IND Inc DA 40
- Aircraft type
- Diamond DA-40
- 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
- N895AM
- Operator
- Meng Ye
- Onboard fatalities
- Unknown
- Route
- From Camarillo International Airport (CMA), Camarillo, CATo Long Beach International Airport (LGB), Long Beach, CA
- Aircraft age
- About 16 years (built 2008)
- 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 91: General Aviation
- 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
- Landing · landing roll
- 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
- Air traffic event
- 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
No findings designated as a cause are recorded in the NTSB data yet.
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
On October 19, 2024, at 1450 pacific daylight time (PDT), a Diamond DA40, N895AM, and a Boeing 737-7H4, N250WN, operated as SWA1671, were involved in a runway incursion in Long Beach, CA. There were no injuries reported and none of the aircraft were damaged. N895AM was operated as a Title 14 Code of Federal Regulations (CFR) Part 91 personal flight and had departed Camarillo Airport (CMA) with a destination of Long Beach Airport, Daugherty Field (LGB). SWA1671 was operated as a Title 14 CFR Part 121 passenger flight and had departed San Francisco Bay Oakland International Airport (OAK) with a destination of LGB.
A review of Federal Aviation Administration (FAA) air traffic control (ATC) audio recordings indicated that at 1442:36 PDT, the crew of N895AM established communication with the local control one (LC1) controller and reported inbound on the Area Navigation (RNAV) Runway 30 Zulu approach. The LC1 controller cleared N895AM to land on runway 30 and instructed the crew to hold short of runway 26 right for traffic. The crew of N895AM then requested to circle to land on runway 26 right which the LC1 controller verbally confirmed with the crew.
At 1444:38, the LC1 controller denied the circling request and again cleared N895AM to land on runway 30 and hold short of runway 26 right for traffic. The crew acknowledged with an accurate read back.
At 1446:46, the crew of SWA1671 established communication with the LC1 controller and reported inbound for landing on runway 30. At 1447:20 the LC1 controller cleared SWA1671 to land on runway 30 and provided a traffic advisory to the crew reference an uninvolved aircraft in the pattern. The crew acknowledged with an accurate readback.
At 1448:27, the LC1 controller provided a traffic advisory to the crew of SWA1671 reference a Cessna that was landing runway 26 left.
At 1449:50, the crew of N895AM advised the LC1 controller they were holding short of runway 26 right on runway 30.
At 1450:05, as SWA1671 was completing their landing roll out on runway 30, the crew of SWA1671 advised the LC1 controller that there was an aircraft on runway 30.
Following the runway incursion, both aircraft taxied to their requested parking areas without further incident.
Figure 1 shows the ground tracks of N895AM (indicated by the blue track) and SWA1671 (indicated by the yellow track) overlaid on satellite imagery in Google Earth. The illustration depicts the direction of travel for each airplane as well as their closest estimated proximity.
Figure 1. Overhead view of the flight tracks of N895AM and SWA1671 with the area of closest proximity.
Upon notification, an NTSB Air Traffic Control (ATC) working group was formed. Parties to the investigation include the FAA and the National Air Traffic Controllers Association (NATCA).
Certified Automatic Dependent Surveillance – Broadcast (ADS-B) data and audio recordings were provided by the FAA and were used in constructing this preliminary report. The NTSB is currently analyzing this data.
During the week of October 28th, 2024, the ATC working group convened at Long Beach Airport Traffic Control Tower (LGB ATCT), the facility that was providing services to both airplanes at the time of the incident, and conducted interviews with the LC1 and LC2 controllers, and operations supervisor who were working at the time of the incident, as well as the NATCA Vice Facility Representative and Air Traffic Manager.
Verbatim NTSB factual narrative from the NTSB dataset
Sources
NTSB record OPS25LA005
- Event ID
- 20241021195355
- Case number
- OPS25LA005
- 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, coordinates, damage. Values present in the bulk record are kept.
- The date is the UTC date the NTSB stores; the local time zone is not recorded, so the local date may differ by a day.
- API snapshot SHA-256: f1be8e13d7c5bb87779e85ed4ec1f468621e64ef0f6613d324f248e76891a7ca; retrieved 2026-09-13T18:47:13.164Z.