It is hard to believe that people are saying that NOTAM is difficult to read. Shocking. This is the state of the airline industry. Very clear NOTAMS cannot be read and pilots cannot talk on the radio properly…..
It seems like the pilot was “maybe aware” of when the runway was to open and knowingly knew that he was cutting it down to the very exact minute of opening relying on everyone’s time being synchronized to the minute and no problems happening with the runway work crew. Or else the pilot was just oblivious and just trying to CYA, both could lead to something very bad happening.
I work on this airfield. Unfortunately it is a regular occurrence at PWM to see airliners depart and arrive without a single CTAF call. Seeing landing lights approaching while you’re working on and near runways is very unsettling. We are diligent about making CTAF calls but not all professional pilots see it as necessary. This is very dangerous.
If it was 5:45 when he took off then he should have takeoff clearance from tower. If it was before 5:45 the runway was closed. He knew what he was doing.
Indeed. It isn't a coincidence that the closure ends at the same time the tower opens. They did that precisely to avoid problems, but Southwest had other ideas...
Yeah, they're liars. Flying SWA is basically the modern equivalent of getting in a cab with a driver who's mixing a wild turkey and lime while he's taking you to the --- WHOAH I DIDNT EVEN KNOW WE WERE ON A BRIDGE. GERONIMO, AMIRITE!???!!!
My home airport and I was listening on my ICOM. Southwest was not on CTAF, they were communicating on Boston Center 128.2, the frequency who gave them their IFR clearance and hold for release instructions. They did not communicate any ground movements on CTAF 120.9
Did or can you check 121.9 at that time too? It’s really strange not to make traffic calls. It’s a busy airport during the early morning push. And the sun is up.
That Boeing should be capable of four different frequencies. And of recieving 3 of those 4. BOS CTR, airport local/UNICOM freq, ATIS. And it can transmit on 2 of them. 1 pilot talk to bos, one talk to airport local.
For clarity for a few commenters who are confused: when an airport like this is "uncontrolled' that means there is not an Air Traffic Controller (ATC) actively managing the runways. The Southwest pilot communicated their intention to take off on runway 29 to "center" which is not responsible for verifying or controlling runways; Center controls the airspace and tells the pilot what altitude to go to, etc. The pilots had a responsibility to announce their ground movements and takeoff intentions to everyone on 120.9, and didn't. This is 100% pilot error, there was no ATC mistake. They also apparently took off before the scheduled opening of the runway, although the pilot claimed after the fact that they didn't, but even if *were* on time, they still had a responsibility to announce their intentions. Just because a runway is scheduled to be open does not mean it's automatically clear. There's also a crossing runway in active use! What if another pilot is taking off on the crossing runway? What if someone's trying to land?
Just to add onto this… That’s why the controller said “you are released for departure” instead of saying “cleared for takeoff.” The controller is in a different location, most likely in Boston.
@VASAviation BTW, if you look at the previous 2 weeks flight tracking, this SWA flight number departed the 29 runway before the 0945 opening 3 other times.
And that's complacency for you folks. Got a truck running up and down the runway checking for debris left over from construction, etc....gets ran over by a plane while turning off to clear the runway. When you wonder "how does this kind of thing happen?" this is how.
@@rdbchase Actually, that is a regional thing. People in the western part of the states tend to use “was” instead of “were”. It can be kinda cute sometimes too.
@@CaptSugman And the Vehicle Driver? Good Situational Awareness and Good Luck that he just had left the Runway. But that was not the Merit of the Southwest Pilots!
@@JimNortonsAlcoholism we want him to stay as bad of a pilot as he is to put more people in danger, fuck protocols or erros, why improve from them when u can just dismiss them....is that better for you?
As a pilot who is meticulous in ensuring I do my job properly to protect myself, my employer, paying customers, and other users of the national airspace system, this event grinds my gears more than any other I can think of.
It was in the NOTAM. It was in the ATIS. He’s driving an aircraft full of passengers around an airport not communicating on CTAF. Technically legal but certainly not it prudent. Then, he takes off on 29. 1. He could have had a tragic collision at the intersection with 36 if the departing aircraft departed a few moments earlier. 2. He could have collided with the ops vehicle further down 29 if they hadn’t been alert and left the runway in time. That needs to be handled as a “possible pilot deviation”.
Republic pilot here who’s landed at PWM many times, a lot of construction at this airport, if the weather was poor, this was an absolute recipe for disaster
An IFR departure release is not takeoff clearance. Center does not issue takeoff clearances. You either get takeoff clearance from Tower, or you listen and talk on CTAF. I'm not a huge fan of the 1500-hour rule, because hundreds of hours of pattern work in a Cessna 172 is not especially relevant training for airline pilots, but one thing you do typically learn via this career path is the use of CTAF at untowered fields. Whereas the flood of military aviators fleeing for high-paying airline jobs ASAP (for example) may not have that experience.
Military aviators are well versed in the use of CTAF. It's taught all through undergraduate pilot training. In my current aircraft type, we go to uncontrolled fields all the time. "We didn't raise him like that." Pure laziness on the SWA crew's part.
Your concern for the competency of military aviators is at level of comedy that you simply cannot fathom. The irony is immeasurably thick and beyond your comprehension.
The captain claimed he took off right at 5:45 when the runway opened, however he didn’t communicate with the tower, which also opened at 5:45. If I was the departure controller I would’ve asked him “if you took off at 5:45 Why didn’t you talk to the tower?”
Sounds like the pilot in the Southwest was quick on his feet with responding that it was just a clock issue. His clock is apparently 3 minutes faster than the airport. So either it was or he was trying to cover his ass. I believe, however, you have to wait for the tower controller to declare that the runway was open, which she did by announcing that arrivals and departures were on Rwy 29.
I agree ATIS said runway is closed, until a newer ATIS version or the tower opens this runway, it remains closed, regardless of their faulty clock. Not much to cover there 😂
He should have been talking to either CTAF (< 0545) or Tower (> 0545) and he was on neither. Clock issue or no clock issue, he didn't follow departure procedure.
Lots wrong with SWA. Never used CTAF even knowing supposedly about closed runway possibly with people on it and hopefully saw Brickyard moving around. Never confirmed time or runway status with Boston claiming to believe he had a whole 3 minute window since runway planned to reopen. The tower opened at 05:45 after SWA departed. Had the crew the believed the time was 05:48 then they should called the tower controlling airport. Busted.
Ok folks, Southwest's number of at-fault pilot incidents is now unacceptable. As a 30 year airline pilot, I now don't want to fly Southwest. What on earth is going on there in operational management?
A SWA flight recently was set up to do a visual landing on a state highway… only realizing their error when ATC issued a low altitude alert, 11 miles away from the airfield… Yikes…
Thank you very much for picking this Incident up!👍 I was really waiting for it. It indeed clarifies what had happened. Openly said: So far as I can see it was Cowboy manner by the Southwest Pilots, not a misunderstanding: If he would have had a wrong clock showing .45 he should have contacted the Tower and pleased for a Takeoff-Clearance. - Fortunately nobody was hurt, but anyway: This shouldn´t happen.
Yeup, if they thought the runway was open, then they would have been talking to tower, and if they thought tower wasn't up yet, then the Runway wasn't open yet either.
The blame is on the SWA crew entirely for not adhering to ATIS as far as runway status goes. If you know that traffic is on a certain frequency while tower is closed, USE IT!
@@ThatCodeBlue It is simply an automated weather station that broadcasts the weather over a frequency. At a tower airport the ATIS is taken down when the tower is closed and the AWOS is broadcast over the ATIS frequency. When the controller leaves for the night they can add a recording to play at the end of it if they so desire. In this case they did and they noted the opening time for the tower and the closure of 11-29.
As a former airport ops guy, runways remain closed until handed back to the controlling authority or changed on NOTAMs. ATC and pilots use the pavement but ops vehicles own it and can close and reopen at their discretion. Shame on the southwest pilot for putting his own ego ahead of the vehicles on the runway and his passengers.
Another class act example of Southworst airlines. Not monitoring CTAF and providing traffic calls, and the total lack of situational awareness of airport environment, is very troubling. Hey the other traffic is taking off 36 maybe we need to think about that. Followed by the lack of concern from the detached sounding pilot after he was made aware of the mistake makes this a must for investigation by the FAA.
Southwest owns about 75% of responsibility with this one. They werent on the CTAF. They obviously listened to NOTAM/ATIS. KPWM should own some responsibility that the closure markers should be absolutely last thing off. Also: MAGICAL
This pilot was setting records, needed that Runway 29 departure for best route to Baltimore. Average flight time is 1:09 but this guy got it done in 1:04 . 6:47 AM arrival is legendary.
At both Portland and Bangor, my local airports, they are doing runway rehabilitation which means you have to be extra vigilant when the runway is closed/ which parts of it are closed and when. Not knowing that information or not communicating on the CTAF is disastrous. Close call.
I’ll bet 5 bucks they showed departing right at :45 on their computer. I’ll only bet $5 though. He said “that’s not what we’re showing” which makes me believe that they’re showing a takeoff time of :45 or after on their computerized aircraft log.
@@Spyke-lz2hl the computer is irrelevant though, their ACTUAL roll time was :42, ADSB confirms that. on top of that, SW literally said Runway 29, they missed that and cleared them anyways, then did a ooopsie and came to realize they cleared them onto a closed runway. however, SW is significantly at fault here for not listening to CTAF and seeing, looking for the vehicles on the runway.
The tower cleared them and did nothing to stop them. Pilots are ultimately responsible, but this was a total failure at multiple stages. ATIS ignored, pilots messed up, tower allowed error, ground vehicle report ignored.
Just a hunch, but I'm thinking the crew made CTAF announcements on the incorrect frequency. This would account for the nocomms. As to using a time machine to account for the 3 minute difference between actual takeoff time and the end of the runway closure, that might become a career limiting event for the crew unless they have something *really* good to back it up.
Didn't ZBW16 give them clearance? Not a pilot here, I don't understand every detail, but seemed to me like that is who Southwest asked, and they gave them a clearance for something at least.
@@autarchprincepsThat was Center giving them an IFR release. The airport was uncontrolled at that time since the Tower was closed, so there are no take off clearances issued or needed. The Center guy is just responsible for the airspace around the airport, and has nothing to do with runways, etc. He’s likely in a room miles away. At an uncontrolled airport, pilots are meant to coordinate with each other on the CTAF or common traffic advisory frequency. Southwest here failed to do so, which is a definite no no.
Not convinced he ignored the radio calls and did what he wanted anyways based on the attitude he gave on the radio. Should be reported to FAA. What a moron.
So they never used the CTAF, departed a closed runway, then didn’t accept responsibility. If they knew they departed at :45, then they would have departed without talking to the tower, which is pretty much just as bad.
FAA should look into this as part of safety training for commercial pilots and Southwest should really look into this as part of operational and overall process improvements. Southwest wasn't paying any attention, assumed things, and didn't communicate or clarify.
Amazing audio and plane synchronization on the graphics as usual! Keep up the great work! Hopefully these will be used for some better training and discipline. Bravo!
I don’t get it: EITHER it was post 5.45, in which case SW would have been talking to the tower for clearance, OR it was pre 5.45, in which case they would not have been talking to the tower. Surely they can’t have it both ways: they weren’t trying to communicate with the tower, so they must have know it wasn’t yet 5.45.
ATIS is only up when the tower is active. Though, presumably a runway closure may be broadcast on an overnight recording, but it’s not guaranteed. It depends how long the closure was for, if it was scheduled ahead of time, etc.
SWA has an ASAP Program, therefore they will net get violated in the way a GA pilot would get violated. Was a mistake made yes. There could be many reasons how this happened. They had the incorrect CTAF freq in the radio and thought they were talking on CTAF. The FMC's could have had the incorrect time loaded. Which made them think they were good with the 0945z time. Just a thought.
Still has to respect the runway closure as stated in the ATIS, right? The release from Center is only in regards to the climbout, not the takeoff clearance?
I thought they gave clearance for take off in more than three and less than five minutes? And they don't explicitly specify that the runway is closed on the call, especially since they apparently gave clearance to be on that runway. Idk the whole comms is throwing me off. @@r.b.4009
My question as someone who knows jack about airport procedures is why would you start taking off with an obstruction on the runway even if you have permission?
I've been watching this and all other air-related channels over the last decade. And I have to say since 2023 we have so many "closed calls" that beats what I have watched for the last 10 years. What's going on with aviation?
I used to fly in and out of Portland all the time, I could have sworn it used to be a 24Hr operation. That being said, the fact that ATIS said the runway was closed and they just assumed it was open and then use center for clearance to depart and never announced their depature is a major deviation.
Most airliners have GPS synchronized clock on board, and if the crew has EFBs those usually too have clocks synchronized to some reliable source. Nowadays, kitchen devices and wrist watches are basically the only not automatically synced clocks. So the pilot could read the time from his wrist watch, which could be off. But imo it's at the very least unwise to rely on wrist watch in safety-critical decision making when you have GPS clock on-board.
@@VASAviation Of course they do. But I would not be surprised when in an old design like the 737 there is a very accurate GPS clock on the 7th display page of the FMC, while in addition there is a free-running clock prominently in view on the instrument panel...
@@VASAviation Why would the pilot challenge Boston control about time? I don't get it. Talk about the variance in time, if there really was a variance... I don't know but that seemingly weak answer by the pilot upsets me on top of the other mistakes the crew made
That's also the airport's fault. It's never a good idea to have a surface opening coincide with the TWR reopening. They're should be at LEAST a 10-15 minute overlap between the resumption of controlled airspace and the opening of the closed surface. The yellow X's would still have been deployed and all access to 29 would still have been barricaded. Fifteen minutes is plenty of time for pre-opening clean up at an airport like PWM.
"Not what we're showing." You're telling me in a multi-million dollar machine with GPS uplinks that provide time accurate to somewhere between milliseconds and microseconds, you have a clock that's off my THREE MINUTES? Are you running your aircraft off a mechanical watch? Also, radio seems to work just fine before and after telling you there was a vehicle on the runway and it was closed, what happened in between? Was it the flight deck not paying attention?
I’m not surprised at the pilots response. SMH. When he was planning to take off on a runway that was just opened yet he never made any calls to confirm that the opening was on time nor to confirm that it was open at the time of break release.
There are errors across the board here. Pilots claim the dispatch report did not include the NOTAMS, which should be included with airline dispatches. Pilots failed to check NOTAM's themselves and to ensure runway was open. Pilots failed to monitor CTAF (which is insane), where they would've been notified it was still closed and there was a vehicle on the runway. Pilots failed to look down the runway to ensure any vehicles were clear of the runway. Boston Center, who should've also been aware of the runway NOTAM, gave a confusing instruction that they were clear to depart from the runway. Southwest pilots told Boston which runway they were taking. This is a lot of errors.... Thank god nobody got hurt.
Controller here. Boston did not give a departure clearance from a runway. They gave them their IFR release from an uncontrolled field meaning they could depart any runway they wanted or heck even take off vertically. It's not a takeoff clearance like a tower issues. Center controllers do not (and do not have time to) check NOTAMs for departures (we're required to for arrivals since things could have changed while the aircraft is in the air) but it is on the pilot's to obtain all pertinent weather and NOTAMs prior to their departure.
Boston Center controls 165,000 square miles of airspace that includes Connecticut, Vermont, Massachuisetts, Rhode Island, Maine, New Hampshire, New York and PA. Do you know how many airports there are in that area? Hhey do not have the ability or time to check every NOTAM for every airport for every ifr departure in their area.
METAR KPWM 250951Z 29005KT 10SM FEW100 16/14 A2972 RMK AO2 SLP063 T01610139=
PWM 06/168 PWM RWY 11/29 CLSD EXC XNG AND TAX THU FRI MON TUE WED 0230-0945 2406200230-2407310945
So how big a deal is this? At least an interview by FAA and his company?
I like your funny words, magic man
@@goutvols103 Southwest has ASAP. They're going to get talked to and possibly taken offline and retrained. They will not get violated.
It is hard to believe that people are saying that NOTAM is difficult to read. Shocking. This is the state of the airline industry. Very clear NOTAMS cannot be read and pilots cannot talk on the radio properly…..
Is this the ATIS?
Them not monitoring CTAF is almost as dangerous as taking off on the closed runway
Worse than that, he was supposed to be broadcasting on Tower frequency as a Unicom until the tower opens.
Right and then when they said they departed at :45, if that was even the case, that would mean they didn’t talk to tower.
It seems like the pilot was “maybe aware” of when the runway was to open and knowingly knew that he was cutting it down to the very exact minute of opening relying on everyone’s time being synchronized to the minute and no problems happening with the runway work crew. Or else the pilot was just oblivious and just trying to CYA, both could lead to something very bad happening.
@@Mentaculus42 He also clearly communicated runway 29 to ATC and ATC did not correct him.
Shared blame.
@@jonathanbott87it isn’t centers job to check notams for local airport for the pilot
"Did he just take off from a closed runway?"
"Yes"
AFP95 confirmed. Welcome to Steam Edition.
I just lol’d hearing his voice say that. “Can confirm” 😂
The peanut gallery
shuttle status engage
"Let me run the numbers on that one Sauce Boss and I'll get back to you."
apparently all the people on steam edition got their commercial licenses?
"That's not what we're showing, but ok" boy, that's how you end up with the FAA holding a pair of scissors and asking to see you pilots license
Time to get a new Timex.
"I just want to talk to em.."
this attitude comes up more and more often, doubt it has any repercussions at all
I used to set my watch five minutes fast too.
@don7294 ... the GPS in the flight computers has the proper zulu time.
Swa: Well obviously the runway wasn’t closed if we took off from it.
Anything can be a runway at least once, right?
Something like that, yes.
I work on this airfield. Unfortunately it is a regular occurrence at PWM to see airliners depart and arrive without a single CTAF call. Seeing landing lights approaching while you’re working on and near runways is very unsettling. We are diligent about making CTAF calls but not all professional pilots see it as necessary. This is very dangerous.
It’s required . Not their call to make
@@deanward7789 it's not required by FAA regs. Maybe company policy (it should be), but not a legal requirement.
@@deanward7789 Its actually not....but it SHOULD
@@FlightX101 wow . Didn’t know there wasnt a reg on this .
@@madrockxvx That's insane. What are they waiting for? Someone to get killed? Not all rules _need_ to be written in blood.
"You risked people's lives"
"Meh..that's not what we were showing."
Lol. Exactly.
Except they didn’t
Great job once again putting this all together Victor! It adds a LOT of clarity to the situation.
Agreed Juan. Victor does a great job as always. Also enjoyed your post about it. Thank you both for your excellent content!
So what's the outcome Juan? SWA wasn't on the correct frequency and took off without T-O clearance?
Glad to help, Juan!
Thank you very much for your Debriefing of this Incident, too!
@@VASAviation good job creating content for JB, going to bring in a nice penny.
If it was 5:45 when he took off then he should have takeoff clearance from tower. If it was before 5:45 the runway was closed. He knew what he was doing.
Indeed. It isn't a coincidence that the closure ends at the same time the tower opens. They did that precisely to avoid problems, but Southwest had other ideas...
Indeed, exactly.
Yes my thoughts too. He painted himself into a corner on that one.
just complete reckless stupidiy all around
Yeah, they're liars. Flying SWA is basically the modern equivalent of getting in a cab with a driver who's mixing a wild turkey and lime while he's taking you to the --- WHOAH I DIDNT EVEN KNOW WE WERE ON A BRIDGE. GERONIMO, AMIRITE!???!!!
Brickyard 5760 was so surprised that they were just vanished.
It's a new teleport capability. On-time metrics are guaranteed to hit 100% every time!
I wouldn’t want to hang around either. 😂
He decided he didn’t want to share airspace with them so he disconnected from Vatsim.
He disconnected since he was looking for realism and that server turned out to be keyboard and mouse steam edition
My home airport and I was listening on my ICOM. Southwest was not on CTAF, they were communicating on Boston Center 128.2, the frequency who gave them their IFR clearance and hold for release instructions. They did not communicate any ground movements on CTAF 120.9
I did not hear any comms at all
Did or can you check 121.9 at that time too? It’s really strange not to make traffic calls. It’s a busy airport during the early morning push. And the sun is up.
That Boeing should be capable of four different frequencies. And of recieving 3 of those 4.
BOS CTR,
airport local/UNICOM freq,
ATIS.
And it can transmit on 2 of them. 1 pilot talk to bos, one talk to airport local.
For clarity for a few commenters who are confused: when an airport like this is "uncontrolled' that means there is not an Air Traffic Controller (ATC) actively managing the runways. The Southwest pilot communicated their intention to take off on runway 29 to "center" which is not responsible for verifying or controlling runways; Center controls the airspace and tells the pilot what altitude to go to, etc.
The pilots had a responsibility to announce their ground movements and takeoff intentions to everyone on 120.9, and didn't. This is 100% pilot error, there was no ATC mistake. They also apparently took off before the scheduled opening of the runway, although the pilot claimed after the fact that they didn't, but even if *were* on time, they still had a responsibility to announce their intentions. Just because a runway is scheduled to be open does not mean it's automatically clear. There's also a crossing runway in active use! What if another pilot is taking off on the crossing runway? What if someone's trying to land?
Just to add onto this… That’s why the controller said “you are released for departure” instead of saying “cleared for takeoff.” The controller is in a different location, most likely in Boston.
@VASAviation BTW, if you look at the previous 2 weeks flight tracking, this SWA flight number departed the 29 runway before the 0945 opening 3 other times.
Oh the FAA is gonna love that.
If no one else is using it, why can't he have his own personal runway?
@@MeerkatADV yeah, and they probably did not file safety reports for the previous deps… i dont wanna fly with them.
And that's complacency for you folks. Got a truck running up and down the runway checking for debris left over from construction, etc....gets ran over by a plane while turning off to clear the runway. When you wonder "how does this kind of thing happen?" this is how.
Doesn’t mean the runway was notam’d closed the other times
Very lucky ops in the vehicle was paying attention.
"were"
@@rdbchase Actually, that is a regional thing. People in the western part of the states tend to use “was” instead of “were”. It can be kinda cute sometimes too.
@@rdbchase Don't come on here being the gRamMaR police you woke.Nobody cares so go and carry on watching the channel on religion and get brainwashed.
@@jamie-hb8gy No such word.
@@TitaniumTurbine "were"
Love the little service vehicle graphic bookin out of the way.
hello, Zaphod Beeblebrox!
The ops guy was very professional about clearing the runway.
This is your daily dose of another close call
Calling this a close call is a massive stretch.Nobody was in any actual sort of danger at any point.
Vehicle driver on runway was awake unlike the Southwest pilot .
@@CaptSugmanwe found the SWA crew
@@CaptSugman And the Vehicle Driver? Good Situational Awareness and Good Luck that he just had left the Runway. But that was not the Merit of the Southwest Pilots!
And if they did hit the truck, or make some sudden input to avoid it, or encounter FOD, then the SWA flight was in danger too.
The pilot was awfully flip about taking off from a closed runway.
An attitude that’s going to get people hurt or worse. It’s only a matter of time.
I have zero respect for the attitude displayed by CA. Staggering.
Did you want him to cry?
@@JimNortonsAlcoholism No, I wanted him to show some humility cuz he f’d up. It’s not difficult.
@@JimNortonsAlcoholism we want him to stay as bad of a pilot as he is to put more people in danger, fuck protocols or erros, why improve from them when u can just dismiss them....is that better for you?
3:51 Brickyard 3516 would be a nice radio host 😂
😄
That pilot in 3516 is such a dork I love it lmao.
MAGICAL.
"It's an early morning" same bro, same
As a pilot who is meticulous in ensuring I do my job properly to protect myself, my employer, paying customers, and other users of the national airspace system, this event grinds my gears more than any other I can think of.
I can almost forgive missing the NOTAM in their paperwork, but they should have heard it on the AWOS, and been tuned to the CTAF before takeoff.
Southwest pilot just sounds like an ass
I could imagine.!
It was in the NOTAM. It was in the ATIS. He’s driving an aircraft full of passengers around an airport not communicating on CTAF. Technically legal but certainly not it prudent.
Then, he takes off on 29.
1. He could have had a tragic collision at the intersection with 36 if the departing aircraft departed a few moments earlier.
2. He could have collided with the ops vehicle further down 29 if they hadn’t been alert and left the runway in time.
That needs to be handled as a “possible pilot deviation”.
Republic pilot here who’s landed at PWM many times, a lot of construction at this airport, if the weather was poor, this was an absolute recipe for disaster
The taxiway alpha project has been happening for months at this point. It’s the same thing every night until 5:45. 11/29 closed
Southwest is going to Tenerife somebody eventually.
How ironic. 4805 is the same flight number as the KLM 747 in the Tenerife airport disaster.
Don't tell me that jerkwad got reincarnated 😮
Aviation is a team sport. Keep your head on a swivel, and double check your radio frequencies. We make it safer by working together.
"Magical!" Lmao
An IFR departure release is not takeoff clearance. Center does not issue takeoff clearances. You either get takeoff clearance from Tower, or you listen and talk on CTAF. I'm not a huge fan of the 1500-hour rule, because hundreds of hours of pattern work in a Cessna 172 is not especially relevant training for airline pilots, but one thing you do typically learn via this career path is the use of CTAF at untowered fields. Whereas the flood of military aviators fleeing for high-paying airline jobs ASAP (for example) may not have that experience.
Military aviators are well versed in the use of CTAF. It's taught all through undergraduate pilot training. In my current aircraft type, we go to uncontrolled fields all the time. "We didn't raise him like that." Pure laziness on the SWA crew's part.
Your concern for the competency of military aviators is at level of comedy that you simply cannot fathom. The irony is immeasurably thick and beyond your comprehension.
The captain claimed he took off right at 5:45 when the runway opened, however he didn’t communicate with the tower, which also opened at 5:45. If I was the departure controller I would’ve asked him “if you took off at 5:45 Why didn’t you talk to the tower?”
Captain Ron: Don’t worry. They’ll get out of the way. I learned that driving the Saratoga.”
Including the ATIS and the previous Brickyard CTAF calls.... that was savage!!
It was an AWOS/ASOS, not an ATIS.
Sounds like the pilot in the Southwest was quick on his feet with responding that it was just a clock issue. His clock is apparently 3 minutes faster than the airport. So either it was or he was trying to cover his ass. I believe, however, you have to wait for the tower controller to declare that the runway was open, which she did by announcing that arrivals and departures were on Rwy 29.
Well he was tuned to Center and not on CTAF or Tower apparently.
Regardless, they should have been on CTAF.
I agree ATIS said runway is closed, until a newer ATIS version or the tower opens this runway, it remains closed, regardless of their faulty clock. Not much to cover there 😂
Clocks are calibrated with GPS signal. Unless he looked at his wrist watch, the airplane clock should be giving the correct GPS hour.
He should have been talking to either CTAF (< 0545) or Tower (> 0545) and he was on neither. Clock issue or no clock issue, he didn't follow departure procedure.
Lots wrong with SWA. Never used CTAF even knowing supposedly about closed runway possibly with people on it and hopefully saw Brickyard moving around. Never confirmed time or runway status with Boston claiming to believe he had a whole 3 minute window since runway planned to reopen. The tower opened at 05:45 after SWA departed. Had the crew the believed the time was 05:48 then they should called the tower controlling airport. Busted.
Boston center has nothing to do with the runway, checking with them about it makes no sense.
Was this guy literally just monitoring Boston Center? The vehicle warned him, the TOWER warned him......I mean sheesh
Tower didn't warn him. Tower wasn't open yet.
@@N1120A Tower wasn't open yet, but the controllers were there and they did warn WN @ 3:04.
Ok folks, Southwest's number of at-fault pilot incidents is now unacceptable. As a 30 year airline pilot, I now don't want to fly Southwest. What on earth is going on there in operational management?
DEI hires, woke agenda being pushed, management more concerned with putting feelings over everything else ?
apparently a lot of bloody marys...
A SWA flight recently was set up to do a visual landing on a state highway… only realizing their error when ATC issued a low altitude alert, 11 miles away from the airfield…
Yikes…
Seeing the same attitudes on the GA side...rules are for other people to follow. Hell, the roads too for that matter.
Fly Southwest on a Boeing plane. What's the worst that could happen?
Thank you very much for picking this Incident up!👍 I was really waiting for it. It indeed clarifies what had happened. Openly said: So far as I can see it was Cowboy manner by the Southwest Pilots, not a misunderstanding: If he would have had a wrong clock showing .45 he should have contacted the Tower and pleased for a Takeoff-Clearance. - Fortunately nobody was hurt, but anyway: This shouldn´t happen.
They weren’t talking to the tower, they knew exactly what time it was, they weren’t making CTAF calls, that’s a deliberate foul.
Yeup, if they thought the runway was open, then they would have been talking to tower, and if they thought tower wasn't up yet, then the Runway wasn't open yet either.
The blame is on the SWA crew entirely for not adhering to ATIS as far as runway status goes. If you know that traffic is on a certain frequency while tower is closed, USE IT!
There was no ATIS. That was an AWOS/ASOS.
@@johnaclark1 I stand corrected. Does the AWOS/ASOS carry more weight or not?
@@ThatCodeBlue It is simply an automated weather station that broadcasts the weather over a frequency. At a tower airport the ATIS is taken down when the tower is closed and the AWOS is broadcast over the ATIS frequency. When the controller leaves for the night they can add a recording to play at the end of it if they so desire. In this case they did and they noted the opening time for the tower and the closure of 11-29.
As a former airport ops guy, runways remain closed until handed back to the controlling authority or changed on NOTAMs. ATC and pilots use the pavement but ops vehicles own it and can close and reopen at their discretion. Shame on the southwest pilot for putting his own ego ahead of the vehicles on the runway and his passengers.
Another class act example of Southworst airlines. Not monitoring CTAF and providing traffic calls, and the total lack of situational awareness of airport environment, is very troubling. Hey the other traffic is taking off 36 maybe we need to think about that. Followed by the lack of concern from the detached sounding pilot after he was made aware of the mistake makes this a must for investigation by the FAA.
Southwest owns about 75% of responsibility with this one.
They werent on the CTAF. They obviously listened to NOTAM/ATIS.
KPWM should own some responsibility that the closure markers should be absolutely last thing off.
Also: MAGICAL
I'd think if they want to make the timing, pull the marking at that end at :40 or so, then stay there till :44 ... hard to miss a vehicle right there!
Maybe even 100 percent. YIKES!
i mean, remove markers, drive on the runway to the other end (basically doing an inspection), remove markers there, that is about 5 minutes easily....
@@boahneelassmal For that matter, reverse the order and remove the departure end (based on current winds) markings first.
@@chrisschack9716 fair point
This pilot was setting records, needed that Runway 29 departure for best route to Baltimore. Average flight time is 1:09 but this guy got it done in 1:04 . 6:47 AM arrival is legendary.
At both Portland and Bangor, my local airports, they are doing runway rehabilitation which means you have to be extra vigilant when the runway is closed/ which parts of it are closed and when. Not knowing that information or not communicating on the CTAF is disastrous. Close call.
That SWA picked a baaaaad flight number for this sort of thing.
"That's not what we're showing" - that's not what I wrote down to comply with myself 😆
We MUST know how Brickyard 3516's magical climb turned out!
Republic has good crews, I fly with them as much as possible. 3516’s departure was by the book. Southwest didn’t bother to go get the book.
Southwest didn't even bother to read the CliffsNotes.
Even though they didn't announce it until :45, I guarantee you all the controllers in that Tower saw and heard this whole thing happen. 😂
That SWA crew is a potential danger. They are incompetent and or liars.
Truth, and should be reprimanded.
I’ll bet 5 bucks they showed departing right at :45 on their computer. I’ll only bet $5 though. He said “that’s not what we’re showing” which makes me believe that they’re showing a takeoff time of :45 or after on their computerized aircraft log.
@@Spyke-lz2hl the computer is irrelevant though, their ACTUAL roll time was :42, ADSB confirms that.
on top of that, SW literally said Runway 29, they missed that and cleared them anyways, then did a ooopsie and came to realize they cleared them onto a closed runway.
however, SW is significantly at fault here for not listening to CTAF and seeing, looking for the vehicles on the runway.
@CapStar362 it's not centers job
The tower cleared them and did nothing to stop them. Pilots are ultimately responsible, but this was a total failure at multiple stages. ATIS ignored, pilots messed up, tower allowed error, ground vehicle report ignored.
Just a hunch, but I'm thinking the crew made CTAF announcements on the incorrect frequency. This would account for the nocomms.
As to using a time machine to account for the 3 minute difference between actual takeoff time and the end of the runway closure, that might become a career limiting event for the crew unless they have something *really* good to back it up.
Surprised that the takeoff clearance wasn't cancelled. Then realized that there was no takeoff clearance ...
Didn't ZBW16 give them clearance? Not a pilot here, I don't understand every detail, but seemed to me like that is who Southwest asked, and they gave them a clearance for something at least.
@@autarchprincepsThat was Center giving them an IFR release. The airport was uncontrolled at that time since the Tower was closed, so there are no take off clearances issued or needed. The Center guy is just responsible for the airspace around the airport, and has nothing to do with runways, etc. He’s likely in a room miles away. At an uncontrolled airport, pilots are meant to coordinate with each other on the CTAF or common traffic advisory frequency. Southwest here failed to do so, which is a definite no no.
@@MikeGranby Thx
@@MikeGranbytrue you are most definitely right about him being in a room miles away, Boston center is in Nashua NH if I recall correctly
How did the flight crew "miss" this? If the tower and runway both open at the same time (5:45), why are you talking to Boston but no one at Portland?
Something tells me 3516 knew he'd be on VAS.
Information Victor, indeed.
It’s wild to me that an airport that big with so many commercial flights is uncontrolled
Babe wake up, weekly US close call just dropped
I was waiting for the "possible pilot deviation, advise when ready to copy a phone number" ...did that happen later or not at all?
Thank you for the video🙏
Not convinced he ignored the radio calls and did what he wanted anyways based on the attitude he gave on the radio. Should be reported to FAA. What a moron.
I'm sure he will be a call from his friends at the FAA
The FAA is already aware of it, note the FAA quote at 5:09
So they never used the CTAF, departed a closed runway, then didn’t accept responsibility. If they knew they departed at :45, then they would have departed without talking to the tower, which is pretty much just as bad.
Indeed, exactly.
FAA should look into this as part of safety training for commercial pilots and Southwest should really look into this as part of operational and overall process improvements. Southwest wasn't paying any attention, assumed things, and didn't communicate or clarify.
This would require SWA to want to improve.
The flight management computer can display GPS time.
For the first time in forever, Portland in question is Portland, ME. Not Portland, OR.
FIRED!
Was that Brickyard whispering? 😂
"..........but... ok..."
Great response!
Remind me never to fly out so early that the airport is uncontrolled.
I am not even doing these kind of things in Microsoft Flight Simulator.
Seems like any airport operating multiple large airlines should have tower controllers there for those arrivals and departures.
Not necessary if the professionals actually adhere to procedures; this crew did not think it applied to them.
Me flying MSFS when people take off whatever direction they want on the runway..
Talk about an uncontrolled airport.
Amazing audio and plane synchronization on the graphics as usual! Keep up the great work! Hopefully these will be used for some better training and discipline. Bravo!
I don’t get it: EITHER it was post 5.45, in which case SW would have been talking to the tower for clearance, OR it was pre 5.45, in which case they would not have been talking to the tower. Surely they can’t have it both ways: they weren’t trying to communicate with the tower, so they must have know it wasn’t yet 5.45.
@@gustafpeyron It opened at 5:45 - as you can hear in the Video.
Indeed, exactly!
Hubris makes the plane go boom
SWA sounds like a cowboy, hope he gets investigated
indeed.
Ever since Southwest softened up their pilot requirements, they’ve been having too many close calls.
If I have information Romeo why wasn't a closed runway on that prerecorded announcement and why didn't Romeo tell me!?
Romeo, Romeo, whereforth art thou runway closure info Romeo?
ATIS is only up when the tower is active.
Though, presumably a runway closure may be broadcast on an overnight recording, but it’s not guaranteed. It depends how long the closure was for, if it was scheduled ahead of time, etc.
Magical 🪄🪄✨✨✨✨
Exactly why i dont fly SWA or United...too many problems with the workers.
SWA has an ASAP Program, therefore they will net get violated in the way a GA pilot would get violated. Was a mistake made yes. There could be many reasons how this happened. They had the incorrect CTAF freq in the radio and thought they were talking on CTAF. The FMC's could have had the incorrect time loaded. Which made them think they were good with the 0945z time. Just a thought.
the magic happened here 2:33-2:43
Still has to respect the runway closure as stated in the ATIS, right? The release from Center is only in regards to the climbout, not the takeoff clearance?
I thought they gave clearance for take off in more than three and less than five minutes? And they don't explicitly specify that the runway is closed on the call, especially since they apparently gave clearance to be on that runway. Idk the whole comms is throwing me off.
@@r.b.4009
And then the pilot is reading back wrong thing, am I understanding this correctly?
My question as someone who knows jack about airport procedures is why would you start taking off with an obstruction on the runway even if you have permission?
I've been watching this and all other air-related channels over the last decade. And I have to say since 2023 we have so many "closed calls" that beats what I have watched for the last 10 years. What's going on with aviation?
Vax brain
Probably about the same thing going on before but now if you fart someone puts it on TH-cam.
I've heard reduced staffing--not enough qualified hires stepping up to replace experienced retirees, for whatever reason.
Layman question: should the runway be marked or flagged as closed somehow while work is in progress?
It is probable that the Vehicle Driver had just removed the Closed Signs - it was three minutes before opening.
Pilot really didnt care.🤔😳
I’m going to start saying “magical” just like that now
Magical!
guys it's southwest, as long as there is a form of asphalt it'll take off naturally due to taxi speeds :x
Immediately apply for immunity!!🤣🤣🤣
I used to fly in and out of Portland all the time, I could have sworn it used to be a 24Hr operation. That being said, the fact that ATIS said the runway was closed and they just assumed it was open and then use center for clearance to depart and never announced their depature is a major deviation.
Bad airmanship on Southwest’s part
ATIS says the CTAF
ATIS says rwy closed
SWA: "meh, ATIS says a lotta stuff"
Yeehaww, ten gallon hats all round again 😂
It's all fun and games until you have to depend on aluminum's tensile strength versus a truck or another plane's wing.
Sounds like a fine from the FAA for *each occurrence* is really gonna add up
Not a pilot of a 737 but is there an "official" clock in that plane or is it that informal at that level to go by the pilots watch?
Airplanes have a clock based on GPS signal.
Most airliners have GPS synchronized clock on board, and if the crew has EFBs those usually too have clocks synchronized to some reliable source. Nowadays, kitchen devices and wrist watches are basically the only not automatically synced clocks. So the pilot could read the time from his wrist watch, which could be off. But imo it's at the very least unwise to rely on wrist watch in safety-critical decision making when you have GPS clock on-board.
@@VASAviation Of course they do. But I would not be surprised when in an old design like the 737 there is a very accurate GPS clock on the 7th display page of the FMC, while in addition there is a free-running clock prominently in view on the instrument panel...
@@VASAviation Why would the pilot challenge Boston control about time? I don't get it. Talk about the variance in time, if there really was a variance... I don't know but that seemingly weak answer by the pilot upsets me on top of the other mistakes the crew made
@@VASAviation Is towers clock GPS based too?
That's also the airport's fault. It's never a good idea to have a surface opening coincide with the TWR reopening. They're should be at LEAST a 10-15 minute overlap between the resumption of controlled airspace and the opening of the closed surface. The yellow X's would still have been deployed and all access to 29 would still have been barricaded. Fifteen minutes is plenty of time for pre-opening clean up at an airport like PWM.
"Not what we're showing." You're telling me in a multi-million dollar machine with GPS uplinks that provide time accurate to somewhere between milliseconds and microseconds, you have a clock that's off my THREE MINUTES? Are you running your aircraft off a mechanical watch? Also, radio seems to work just fine before and after telling you there was a vehicle on the runway and it was closed, what happened in between? Was it the flight deck not paying attention?
I’m not surprised at the pilots response. SMH. When he was planning to take off on a runway that was just opened yet he never made any calls to confirm that the opening was on time nor to confirm that it was open at the time of break release.
Cpt Leroy Jenkins going in on 28
Amazing!! These guys actually got their private pilots license somehow 😑
There are errors across the board here. Pilots claim the dispatch report did not include the NOTAMS, which should be included with airline dispatches. Pilots failed to check NOTAM's themselves and to ensure runway was open. Pilots failed to monitor CTAF (which is insane), where they would've been notified it was still closed and there was a vehicle on the runway. Pilots failed to look down the runway to ensure any vehicles were clear of the runway. Boston Center, who should've also been aware of the runway NOTAM, gave a confusing instruction that they were clear to depart from the runway. Southwest pilots told Boston which runway they were taking. This is a lot of errors.... Thank god nobody got hurt.
Controller here. Boston did not give a departure clearance from a runway. They gave them their IFR release from an uncontrolled field meaning they could depart any runway they wanted or heck even take off vertically. It's not a takeoff clearance like a tower issues. Center controllers do not (and do not have time to) check NOTAMs for departures (we're required to for arrivals since things could have changed while the aircraft is in the air) but it is on the pilot's to obtain all pertinent weather and NOTAMs prior to their departure.
@@DannyfromMPLSeven so, that’s still one of the holes in the Swiss cheese my man
Boston Center controls 165,000 square miles of airspace that includes Connecticut, Vermont, Massachuisetts, Rhode Island, Maine, New Hampshire, New York and PA. Do you know how many airports there are in that area? Hhey do not have the ability or time to check every NOTAM for every airport for every ifr departure in their area.
I heard that as well. Its not like Southwest took off from a different runway they said they were going from.
He must be claiming that he took off AFTER the runway opened at 0545, but before he would need a takeoff clearance which also happened at 0545.