An Unusual Takeoff on a Closed Runway

On June 25, 2024, a Southwest Airlines Boeing 737-700, registered as N7861J, took off from an inactive runway at Portland International Jetport (PDX). This event occurred under unusual circumstances where the designated runway was not only closed but also had an airport operations vehicle present, conducting a runway inspection. The flight, numbered WN4805, was scheduled to fly from Portland to Baltimore-Washington Airport (BWI).

The incident took place at 05:43 AM, just two minutes before the official opening time of both the runway and the air traffic control tower, which were set to commence operations at 05:45 AM. The night prior, runway 29/11 had been closed for a taxiway construction project, a routine that had been in effect for several months.

According to audio records from liveatc.net, an airport operations vehicle communicated on the tower frequency, notifying the opening of the runway shortly after the Southwest aircraft had already departed. The crew of the operations vehicle expressed their surprise and attempted to contact the tower regarding the Southwest aircraft that had just flown overhead. However, the tower frequency was not active at that moment, leading to a lack of communication with the departing aircraft.

Further complicating the communication breakdown, the Southwest pilots were tuned into a different frequency, communicating with regional air traffic controllers near Boston instead of the local tower. It was later confirmed by the Boston air traffic controller that the aircraft had departed three minutes before the runway was officially reopened. This miscommunication was evident when the controller mentioned the closure, and the pilot responded with confusion about the exact reopening time of the runway.

Interestingly, another runway, 18/36, was open and available at the time, which raises questions about the decision-making process that led to the use of a closed runway. This incident highlights significant concerns about procedural adherence and communication within airport operations.

Regulatory Response and Investigation

Following the incident, the Federal Aviation Administration (FAA) issued a statement on June 29, 2024, acknowledging the occurrence and confirming that an airport vehicle had exited the runway prior to the aircraft’s takeoff roll. The FAA, along with the National Transportation Safety Board (NTSB), has launched a full-scale investigation into the event to understand the lapses in protocol and to enhance future safety measures.

Southwest Airlines has cooperated fully with the investigating authorities and has begun an internal review to prevent such incidents in the future. The airline emphasized its commitment to safety and adherence to regulatory requirements.

The aircraft involved in the incident managed to land safely in Baltimore without any further complications, averting a potential disaster. This incident serves as a crucial reminder of the importance of strict compliance with flight operation procedures and effective communication between all parties involved in air traffic management.

Leave a Reply

Your email address will not be published. Required fields are marked *