Southwest B737 at Portland on Jun 25th 2024, took off from closed occupied runway
Last Update: July 12, 2024 / 16:34:34 GMT/Zulu time
Incident Facts
Date of incident
Jun 25, 2024
Classification
Incident
Airline
Southwest Airlines
Flight number
WN-4805
Departure
Portland, United States
Destination
Baltimore, United States
Aircraft Registration
N7861J
Aircraft Type
Boeing 737-700
ICAO Type Designator
B737
Airport ICAO Code
KPWM
Airport Operations can be heard on tower frequency opening the runway about two minutes after Southwest's departure and asking tower whether they could get hold of the Southwest Airplane that had just taken off over them while they were doing a runway inspection. Tower responded they never talked to them, they weren't yet open.
According to NOTAMs only Portland's runway 18/36 would have been available at that time (Tuesday, Jun 25th 2024, 09:43Z).
The FAA released a statement on Jun 29th 2024: "Southwest Airlines Flight 4805 departed from a temporarily closed runway at the Portland International Jetport on Tuesday, June 25. An airport vehicle exited the runway before the plane began its takeoff roll. The FAA and NTSB are investigating the event, which occurred around 5:45 a.m. local time."
On Jul 12th 2024 the NTSB released their preliminary report summarizing the sequence of events:
According to SWA, the incident flight’s dispatch release, titled “release -1,” indicated that the departure time for the flight was 0540. The release also indicated a 12-minute taxi out at PWM and an arrival time at BWI of 0715.
As part of their preflight duties, the flight crew reviewed “Southwest Airlines Briefing” electronic weather packet, which was generated on June 25, 2024, at 0446. The packet contained, in part, the departure and destination weather and, notice to air missions (NOTAMs). There were 32 NOTAMs specifically for PWM, including a NOTAM for runway 11/29 being closed until 0545 on the event date. In addition, part of the weather packet included a content page that included a message that all flights departing from PWM before 0545 must call their dispatcher and receive a briefing from the Chief Pilot who was on call about departing from runway 18/36 which is one of the shortest runways within the SWA system. The flight crew did not see the content page nor did they call for a briefing.
A review of the NOTAMs for PWM revealed that runway 11/29 was closed at the time of the flight’s departure due to construction activities on or near the runway. The runway closure NOTAM was in effect from June 19 to July 24, 2024, and stipulated that the runway would be closed Monday through Friday from 2230 to 0545 and Saturday and Sunday from 0000 to 0545.
The incident flight occurred on a Tuesday.
According to the incident flight crew members, they arrived for the flight on time. The captain, who was the pilot flying, began the preflight duties by reviewing the aircraft logbook for open discrepancies, minimum equipment list items, and a maintenance release. The first officer (FO) conducted the exterior preflight duties and programmed their navigation equipment.
The crew used their respective iPads to set up five flight-related applications, including Jeppesen FlightDeck Pro, WSi, and Comply 365, which provided station-specific information.
The captain accessed the Comply 365 application and noted that the PWM tower was closed until 0545; therefore, Boston Air Route Traffic Control Center would need to be contacted on frequency 128.2 for their instrument flight rules (IFR) clearance and void time. The application also indicated that morning departures should expect to use runway 29. The captain stated that he briefed this information to the FO and then entered the departure, destination, and route into the flight management computer.
The flight crew also reviewed the NOTAMs and noted that runway 29 was closed on Saturdays and Sundays until 0545. The captain incorrectly assumed that any additional days for the runway closure would be in the same NOTAM. The flight crew members did not see the separate NOTAM addressing the runway closure on the other days of the week; the NOTAM was underneath another application.
The FO stated that, before pushback, they received performance weight and balance (PWB) takeoff data via AeroData for runway 29. Normally when a runway is closed, no takeoff data is received, only a message stating it is unavailable due to runway closure. The crew did not brief, nor were they required to, the frequency they would utilize. When the flight was ready to push back, the FO advised on the universal communication frequency (UNICOM) frequency 122.95 that they would be pushing back from gate 4. He also advised on the UNICOM frequency they would be taxing to runway 29 for departure. The flight crew completed all briefings and checklists, and the airplane pushed back from the gate normally.
The captain stated that the FO made “multiple calls to Portland Traffic” in regards to their planned taxi route to runway 29. The FO stated, to investigators, that, while taxiing he utilized the UNICOM frequency to announce their intentions. He then, just before reaching the runway, contacted Boston Center and advised that they were number one for departure from runway 29.
Boston Center gave a clearance void time with instructions to climb on the runway heading to 4,000 feet. The FO stated that he again advised, over the UNICOM, that the airplane would be turning onto runway 29 for departure. Both crewmembers indicated that they saw a truck exit the runway while the flight was holding short of runway 29. Before applying power, they both confirmed that the truck was clear of the runway; it had turned off the runway onto the taxiway and pulled up by the terminal and faced the runway.
The airplane turned onto runway 29, and the FO announced on UNICOM that the airplane would be departing from runway 29. After a visual check of the runway, the flight crew verified the runway and that it was clear of all objects. The flight crew did not observe any equipment, markings, visual closed runway lighted “Xs” designations, or any other sign indicating that the runway was closed, and all equipment and people were clear of the runway. No other traffic or communication was heard on the UNICOM frequency. The flight departed runway 29 and continued to BWI uneventfully.
Relevant NOTAM:
!PWM 06/168 PWM RWY 11/29 CLSD EXC XNG AND TAX THU FRI MON TUE WED 0230-0945
2406200230-2407310945
Metars:
KPWM 251051Z 31008KT 10SM FEW100 18/15 A2973 RMK AO2 SLP067 T01830150=
KPWM 250951Z 29005KT 10SM FEW100 16/14 A2972 RMK AO2 SLP063 T01610139=
KPWM 250851Z 32006KT 10SM FEW100 16/14 A2971 RMK AO2 SLP059 T01610139 53010=
KPWM 250751Z AUTO 30005KT 10SM CLR 17/14 A2969 RMK AO2 SLP053 T01670144=
KPWM 250651Z AUTO 31009KT 10SM FEW080 BKN110 17/15 A2968 RMK AO2 SLP050 T01720150=
KPWM 250551Z AUTO 31005KT 10SM FEW075 OVC100 18/16 A2968 RMK AO2 SLP049 60024 T01780156 10183 20172 53014=
Aircraft Registration Data
Incident Facts
Date of incident
Jun 25, 2024
Classification
Incident
Airline
Southwest Airlines
Flight number
WN-4805
Departure
Portland, United States
Destination
Baltimore, United States
Aircraft Registration
N7861J
Aircraft Type
Boeing 737-700
ICAO Type Designator
B737
Airport ICAO Code
KPWM
This article is published under license from Avherald.com. © of text by Avherald.com.
Article source
You can read 2 more free articles without a subscription.
Subscribe now and continue reading without any limits!
Read unlimited articles and receive our daily update briefing. Gain better insights into what is happening in commercial aviation safety.
Send tip
Support AeroInside by sending a small tip amount.
Related articles
Fleet type match
Southwest B38M at Las Vegas on May 9th 2025, brakes fire
A Southwest Airlines Boeing 737-8 MAX, registration N8765Q performing flight WN-2024 from San Jose,CA to Las Vegas,NV (USA), landed on Las Vegas'…
Fleet type match
Southwest B737 at Houston on Apr 17th 2025, engine shut down in flight
A Southwest Airlines Boeing 737-700, registration N7724A performing flight WN-3006 from Houston Hobby,TX (USA) to San Jose Cabo (Mexico) with 134…
Fleet type match
Southwest B738 at Orlando on Mar 20th 2025, attempted to takeoff from taxiway
A Southwest Airlines Boeing 737-800, registration N8315C performing flight WN-3278 from Orlando,FL to Albany,NY (USA), was cleared for takeoff from…
Fleet type match
Southwest B738 at Chicago on Feb 25th 2025, near collision with business jet on runway
A Southwest Airlines Boeing 737-800, registration N8517F performing flight WN-2504 from Omaha,NE to Chicago Midway,IL (USA), was in the flare to land…
Fleet type match
Southwest B737 at Sacramento on Feb 8th 2025, engine issue
A Southwest Airlines Boeing 737-700, registration N288WN performing flight WN-2301 from Sacramento,CA to Denver,CO (USA), was climbing out of…
Newest articles
Fleet type match
People's E170 at Altenrhein on May 13th 2025, flaps problem
A People's Viennaline Embraer ERJ-170, registration OE-LMK performing flight PE-921 from Lamezia Terme (Italy) to Altenrhein (Switzerland), was on…
Fleet type match
People's E170 at Altenrhein on May 12th 2025, flaps problems
A People's Viennaline Embraer ERJ-170, registration OE-LMK performing flight PE-511 from Palma Mallorca,SP (Spain) to Altenrhein (Switzerland) with…
Subscribe today
Are you researching aviation incidents? Get access to AeroInside Insights, unlimited read access and receive the daily newsletter.
Pick your plan and subscribePartner
ELITE Simulation Solutions is a leading global provider of Flight Simulation Training Devices, IFR training software as well as flight controls and related services. Find out more.
SafetyScan Pro provides streamlined access to thousands of aviation accident reports. Tailored for your safety management efforts. Book your demo today
AeroInside Blog
Popular aircraft
Airbus A320Boeing 737-800
Boeing 737-800 MAX
Popular airlines
American AirlinesUnited
Delta
Air Canada
Lufthansa
British Airways