Premium research interface

The modern interface for aviation safety intelligence.

Search investigations, review source evidence, monitor watched reports, and trace long-term patterns from one calm, data-first workspace.

63k+
Reports indexed
1940-2026
Coverage
Recent
Last data refresh
Featured Report

Loading…

Loading featured report…

Loading…
Open Report

Safety trends by operating rule

Track fatal and non-fatal accident patterns across Part 91, Part 135, and Part 121 operations.

Loading trend charts…

Browse the aviation graph

Move quickly by aircraft, airport, operator, and time with indexes built for research, not wandering.

Last Data Update

By Decade

By Month

Aircraft Manufacturer

More manufacturers

Airports

More airports

Operators

More operators

About

Aviation safety reports, made easier to study

NTSB Reports is an independent research and search tool for public aviation accident and incident records. It brings NTSB aviation reports, structured fields, docket files, extracted figures, photos, videos, and update history into one searchable interface.

The goal is practical safety education: make it faster to find relevant investigations, compare similar events, review factual records, and understand the evidence behind probable-cause and preliminary reports.

The investigative work and source records belong to the National Transportation Safety Board and the published investigation record. This site is not affiliated with or endorsed by the NTSB.

FAQs

NTSB Report

October 19, 2024 · Boeing 737-7H4 NO Series · N250WN

Long Beach, CA

Overview

Report Status
Factual report
Event Type
Incident
Date
October 19, 2024
Location
Long Beach, CA
Aircraft
Boeing 737-7H4 NO Series (2006)
Tail Number
N250WN
Operator
Southwest Airlines
NTSB Number
OPS25LA005

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.

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

Flight

Event TypeIncident
Event Time14:50 PDT
Nearest AirportLong Beach Airport (0nm)
Runway30
Runway Length10000 ft
Runway Width200 ft
Flight Plan FiledIFR
Flight Plan ActivatedYes
Aircraft FireNo
Aircraft ExplosionNo

Aircraft

AircraftBoeing 737-7H4 NO Series
Tail NumberN250WN
Aircraft CategoryAir
OperatorSouthwest Airlines
Operating RulePart 121
Engines2
Seats143

People & Injuries

Fatal0
Serious0
Minor0
Uninjured0
Total0

Conditions

ConditionsVMC
LightDaylight
Wind200° @ 9 kt
Visibility9 sm
CeilingNone
Temperature / Dew Point25 C / 6 C
Altimeter-3001
Weather SourceWFAC

Appendix: Source Data