{"id":119434,"date":"2025-11-03T03:15:00","date_gmt":"2025-11-02T21:45:00","guid":{"rendered":"https:\/\/aviationa2z.com\/?p=119434"},"modified":"2025-11-03T01:48:00","modified_gmt":"2025-11-02T20:18:00","slug":"ntsb-probes-close-between-southwest-airlines-and-helicopter","status":"publish","type":"post","link":"https:\/\/aviationa2z.com\/index.php\/2025\/11\/03\/ntsb-probes-close-between-southwest-airlines-and-helicopter\/","title":{"rendered":"NTSB Probes Close Call Between Southwest Airlines and Helicopter Near Cleveland"},"content":{"rendered":"\n

CLEVELAND-<\/strong> The U.S. National Transportation Safety Board (NTSB) has launched an investigation into a near-miss involving a Southwest Airlines (WN)<\/a> Boeing 737 and a medical helicopter near Cleveland Hopkins International Airport (CLE)<\/strong> on October 29.<\/p>\n\n\n\n

According to officials, Southwest Flight 1333 was approaching from Baltimore\/Washington International Thurgood Marshall Airport (BWI)<\/strong> when the two aircraft came dangerously close, prompting the pilot to abort the landing.<\/p>\n\n\n\n

\"NTSB
Photo: Cl\u00e9ment Alloing<\/figcaption><\/figure>\n\n\n\n

Southwest Airlines Jets and Helicopter Close Call<\/h2>\n\n\n\n

The NTSB confirmed the incident involved a loss of separation<\/strong>, meaning the aircraft violated the minimum safe distance required in controlled airspace.<\/p>\n\n\n\n

The Southwest jet and the medical helicopter reportedly came within 0.56 miles (0.9 km)<\/strong> at an altitude of 2,075 feet (632 meters)<\/strong>, according to data from Flightradar24.<\/p>\n\n\n\n

The flight tracking site also revealed that the air traffic controller had advised the helicopter to stay behind the incoming aircraft. However, the helicopter pilot requested to pass above and in front, a decision the controller approved.<\/p>\n\n\n\n

This led to the Southwest pilot\u2019s<\/a> immediate decision to go around for another landing attempt, ensuring passenger safety. The Boeing 737 later landed safely without injuries.<\/p>\n\n\n\n

Southwest Airlines commended its crew\u2019s quick response and confirmed full cooperation with the NTSB investigation. The medical transport company involved has not issued a statement.<\/p>\n\n\n\n

\"Southwest
Photo: By Eric Salard – N559WN LAX, CC BY-SA 2.0, https:\/\/commons.wikimedia.org\/w\/index.php?curid=44649799<\/figcaption><\/figure>\n\n\n\n

ATC and Southwest Pilot Comms<\/h4>\n\n\n\n

Here’s a detailed transcription between ATC and the Southwest Airlines pilot as flagged by You Can See ATC<\/a>:<\/p>\n\n\n\n

{ts:15}<\/strong>
ATC:<\/strong> Wi-Fi tower 301, 30123.<\/p>\n\n\n\n

{ts:33}<\/strong>
[Music]<\/em>
ATC\/Pilot:<\/strong> Contact airport clear of space.<\/p>\n\n\n\n

{ts:39}<\/strong>
ATC:<\/strong> Clear to Bravo left if you can, maintain that 2,000, head.
Pilot:<\/strong> We’ll maintain 2,000.<\/p>\n\n\n\n

{ts:50}<\/strong>
ATC\/Pilot:<\/strong> Contact… [Music]… flight traffic 8:00 about 2 miles.<\/p>\n\n\n\n

{ts:69}<\/strong>
ATC:<\/strong> Southwest 73 at 4,000, setting three for the final flight.<\/p>\n\n\n\n

{ts:76}<\/strong>
ATC:<\/strong> Traffic tower, Southwest 1333, right for 633.
ATC:<\/strong> Clean tire traffic 3:00, about 3 miles.<\/p>\n\n\n\n

{ts:87}<\/strong>
ATC:<\/strong> Helicopter low 2,000, northbound, searching only six left, clear to land 633.<\/p>\n\n\n\n

{ts:97}<\/strong>
ATC:<\/strong> Only six, take off.
Pilot:<\/strong> All right.
ATC:<\/strong> 53, traffic about 9:00 now.<\/p>\n\n\n\n

{ts:116}<\/strong>
ATC:<\/strong> 737, maintain the separation. Traffic, maintain separation.<\/p>\n\n\n\n

{ts:132}<\/strong>
ATC:<\/strong> 133, helicopter now 2:00, 2 miles. They have you in sight; maintain separation.
Pilot:<\/strong> Copy, thanks. We’re still searching.<\/p>\n\n\n\n

{ts:138}<\/strong>
ATC:<\/strong> Southwest 1333, traffic.
Pilot (SW 1333):<\/strong> It’ll be better if we go above it and in front of it if we can. We’re deviating right for the traffic.
ATC:<\/strong> Roger. Would you like…
Pilot:<\/strong> Negative, we can come back. Yeah, we’re going to execute a go-around. We got an RA (resolution advisory) right there.<\/p>\n\n\n\n

{ts:196}<\/strong>
ATC:<\/strong> Roger. When able, heading 060.
Pilot:<\/strong> Heading 060, Southwest 1333.<\/p>\n\n\n\n

{ts:210}<\/strong>
ATC:<\/strong> Maintain 3,000.
Pilot:<\/strong> Climb, maintain 30,000, Southwest 1333.<\/p>\n\n\n\n

{ts:223}<\/strong>
ATC:<\/strong> 1333, climb 4,000, turn left 320.
Pilot:<\/strong> 4,000 and left turn 320, Southwest 1333.
ATC:<\/strong> Contact 26.55, 1333.<\/p>\n\n\n\n

\"American
Photo: Alan Wilson | Flickr<\/figcaption><\/figure>\n\n\n\n

Previous Airspace Safety Concerns<\/h2>\n\n\n\n

The Cleveland incident follows heightened scrutiny of airspace safety in the United States.<\/p>\n\n\n\n

On January 29<\/strong>, a mid-air collision between an American Airlines (AA)<\/a><\/strong> regional jet and a U.S. Army<\/strong> helicopter near Ronald Reagan Washington National Airport (DCA)<\/strong> killed 67 people<\/strong>, intensifying concern about close encounters between commercial and military or medical aircraft.<\/p>\n\n\n\n

Following that tragedy, the Federal Aviation Administration (FAA)<\/strong> introduced revised helicopter routes around BWI<\/strong>, DCA<\/strong>, and Washington Dulles International Airport (IAD)<\/strong> to improve separation buffers.<\/p>\n\n\n\n

Despite these changes, the NTSB noted a continuing trend: since 2021, there have been over 15,200 air separation losses<\/strong> near Reagan, with 85 classified as close-call events<\/strong>.<\/p>\n\n\n\n

Recent Near-Miss Events<\/h4>\n\n\n\n

The Aviation Herald also reported a recent close call involving a Delta Air Lines (DL)<\/a> Airbus arriving from Paris.<\/p>\n\n\n\n

Adverse weather diverted the flight from John F. Kennedy International Airport (JFK)<\/strong> to Boston Logan International Airport (BOS)<\/strong>, where it narrowly avoided a Cape Air (9K)<\/strong> Cessna departing the same runway.<\/p>\n\n\n\n

These recurring incidents highlight ongoing airspace congestion and the critical need for improved coordination between commercial, private, and emergency flight operations.<\/p>\n\n\n\n

\"NTSB
Photo: Jeffrey S.S | Pexels<\/figcaption><\/figure>\n\n\n\n

Broader Impact and Air Traffic Control Challenges<\/h2>\n\n\n\n

The recent government shutdown<\/strong> has worsened staffing shortages among air traffic controllers, particularly in critical control centers.<\/p>\n\n\n\n

Reports from Cleveland.com indicated that 44% of flight delays<\/strong> last Sunday were linked to inadequate staffing, compared to an annual average of 5%<\/strong>. Air traffic controllers, considered essential personnel, are required to work without pay during shutdowns, heightening operational strain.<\/p>\n\n\n\n

The FAA has faced mounting criticism for delayed policy responses to previous near-miss incidents, including a May 1 close call<\/strong> near the Pentagon that led to the Army being barred from operating helicopters in that area.<\/p>\n\n\n\n

Stay tuned with us. Further, follow us on social media for the latest updates.<\/p>\n\n\n\n

Join us on\u00a0Telegram Group\u00a0<\/a>for the Latest Aviation Updates. Subsequently, follow us on\u00a0Google News<\/a><\/p>\n\n\n\n

\n
Southwest Airlines Pilot Arrested for Being Drunk Before Flight | New Update<\/a><\/blockquote>