Amateur hour at US Airways

MikeD

Administrator
Staff member
Flying on US Airways 444, an A-319, from TUS to PHX yesterday. Get loaded up, push back, start, taxi. Getting to the runway, we're holding short #1 for an unusually long amount of time. Didn't see any traffic on final, so I figure its a release issue or something. Well, it was that and more.

Captain comes on over the PA after about 10-ish minutes at the hold short line. He announces that "ladies and gentlemen this is your captain, ummm, we've ummm, missed our release time from air traffic control for Phoenix, since we weren't finished with checklists up here in the cockpit, and now we can't take off apparently according to the tower. They're telling us it's going to be a 1 hour delay until we can depart for Phoenix in order to fit into the flow. I really apologize for the inconvenience."

Missed their IFR release because their checklists weren't complete?!?!?!

You kidding me!?! I mean, thats something I expect from flight school airplane on a IFR dual cross country, not something I expect from a supposedly "varsity team" mainline crew.

We're talking TUS here, not LGA or LAX or EWR during rush hour.

The Captain came on a few minutes later with "ladies and gentlemen, I really apologize.....if it makes you feel any better, in 15 years of being an airline captain, this has never happened and is the first time I've experienced it. We're very sorry for the delay."

We did a 180, taxiied to the quasi-penalty box, and held for the next 50 minutes, finally launching for PHX.

TUS to PHX is supposed to be a 27 minute flight.....the ground time was 55 minutes! Longer than the damn total flight time. All for some freaking rookie BS.

There were a lot of pissed off pax, and a good few who missed connections at PHX from what I understood. As I was leaving the plane last, since I was sitting in back, I asked the FO and FA who were at the cockpit door what the real story was........was there a minor problem with the jet that they had to work out in the cockpit, but didn't want to rile up the pax over the PA, maybe?

Nope. Took too long with the checklist and "we didn't figure it'd be a problem, until we found out it was. And in any event, we've had a long day anyways." Oh really? No excuse. Seriously. What a bunch of crap for this kind of simple error.

Am curious though, had this happened in an aforementioned "busier airport", what then? These guys should freaking know better.

One funny thing was, that there were two regional guys riding in the back, not exactly sure which airline, but they were quietly chuckling about this embarassing error by a mainline crew.
 
Flying on US Airways 444, an A-319, from TUS to PHX yesterday. Get loaded up, push back, start, taxi. Getting to the runway, we're holding short #1 for an unusually long amount of time. Didn't see any traffic on final, so I figure its a release issue or something. Well, it was that and more.

Captain comes on over the PA after about 10-ish minutes at the hold short line. He announces that "ladies and gentlemen this is your captain, ummm, we've ummm, missed our release time from air traffic control for Phoenix, since we weren't finished with checklists up here in the cockpit, and now we can't take off apparently according to the tower. They're telling us it's going to be a 1 hour delay until we can depart for Phoenix in order to fit into the flow. I really apologize for the inconvenience."

Missed their IFR release because their checklists weren't complete?!?!?!

You kidding me!?! I mean, thats something I expect from flight school airplane on a IFR dual cross country, not something I expect from a supposedly "varsity team" mainline crew.

We're talking TUS here, not LGA or LAX or EWR during rush hour.

The Captain came on a few minutes later with "ladies and gentlemen, I really apologize.....if it makes you feel any better, in 15 years of being an airline captain, this has never happened and is the first time I've experienced it. We're very sorry for the delay."

We did a 180, taxiied to the quasi-penalty box, and held for the next 50 minutes, finally launching for PHX.

TUS to PHX is supposed to be a 27 minute flight.....the ground time was 55 minutes! Longer than the damn total flight time. All for some freaking rookie BS.

There were a lot of pissed off pax, and a good few who missed connections at PHX from what I understood. As I was leaving the plane last, since I was sitting in back, I asked the FO and FA who were at the cockpit door what the real story was........was there a minor problem with the jet that they had to work out in the cockpit, but didn't want to rile up the pax over the PA, maybe?

Nope. Took too long with the checklist and "we didn't figure it'd be a problem, until we found out it was. And in any event, we've had a long day anyways." Oh really? No excuse. Seriously. What a bunch of crap for this kind of simple error.

Am curious though, had this happened in an aforementioned "busier airport", what then? These guys should freaking know better.

One funny thing was, that there were two regional guys riding in the back, not exactly sure which airline, but they were quietly chuckling about this embarassing error by a mainline crew.

Probably too busy looking down on "regional guys".

Nah, honestly, 15 years and all they screw up is a checklist? At least everyone is safe. Had a 20 year guy do something similar, there wasn't any 50 minute delay but 10 minutes for his/our goofup.
 
Probably too busy looking down on "regional guys".

Nah, honestly, 15 years and all they screw up is a checklist? At least everyone is safe. Had a 20 year guy do something similar, there wasn't any 50 minute delay but 10 minutes for his/our goofup.

10 minutes here and there, oh well. This one was just out there.......originally the departure wasn't going to be for 90 minutes. I almost could've deplaned, rented a car and driven to PHX quicker.
 
10 minutes here and there, oh well. This one was just out there.......originally the departure wasn't going to be for 90 minutes. I almost could've deplaned, rented a car and driven to PHX quicker.
Ya know, I was thinking, these guys could have canceled before reaching the gate. :)
 
Meh...at least they did the checklists. I've missed wheels up times before for a number of reasons. Late pulling the jetway off the plane, late closing all the doors, ground crew forgets to connect nosewheel steering scissors, runway change and ACARS is slow getting the new performance data, etc. Never has it turned into an hour wait.

I do know that when delays are issued they usually start with the closer airports. Or planes with MikeD aboard as they figure he probably has nowhere to be.
 
Ah yeah, rush through checklists...

Thats what I want my flight crew to do.

Wah-bulance.

Thanks to that new Passenger Bill of Rights, all you had to do was ask one of the crew members that you wanted to deplane and they would have been obligated to do just that. You could have rented your car and driven.
 
Ah yeah, rush through checklists...

Thats what I want my flight crew to do.

Wah-bulance.

Thanks to that new Passenger Bill of Rights, all you had to do was ask one of the crew members that you wanted to deplane and they would have been obligated to do just that. You could have rented your car and driven.

Considering that the crew was socializing with one of the FAs as they were still at the gate, there's no excuse.

Remember, you have paying pax, or have you forgotten what your responsibility is there in the midst of whining and complaining about everything pay/QOL related?

No need to rush through the checklist, but having this happen and being somehow surprised that they couldn't take off for an hour and is inexcusable. IFR release is IFR release.

Wah-bulance nothing. Doing one's job as a professional and not taking unnecessary delays for a BS reason is simply expected standard for a professional at the job. Not making excuses for it.
 
Flying on US Airways 444, an A-319, from TUS to PHX yesterday. Get loaded up, push back, start, taxi. Getting to the runway, we're holding short #1 for an unusually long amount of time. Didn't see any traffic on final, so I figure its a release issue or something. Well, it was that and more.

Captain comes on over the PA after about 10-ish minutes at the hold short line. He announces that "ladies and gentlemen this is your captain, ummm, we've ummm, missed our release time from air traffic control for Phoenix, since we weren't finished with checklists up here in the cockpit, and now we can't take off apparently according to the tower. They're telling us it's going to be a 1 hour delay until we can depart for Phoenix in order to fit into the flow. I really apologize for the inconvenience."

Missed their IFR release because their checklists weren't complete?!?!?!

You kidding me!?! I mean, thats something I expect from flight school airplane on a IFR dual cross country, not something I expect from a supposedly "varsity team" mainline crew.

We're talking TUS here, not LGA or LAX or EWR during rush hour.

The Captain came on a few minutes later with "ladies and gentlemen, I really apologize.....if it makes you feel any better, in 15 years of being an airline captain, this has never happened and is the first time I've experienced it. We're very sorry for the delay."

We did a 180, taxiied to the quasi-penalty box, and held for the next 50 minutes, finally launching for PHX.

TUS to PHX is supposed to be a 27 minute flight.....the ground time was 55 minutes! Longer than the damn total flight time. All for some freaking rookie BS.

There were a lot of pissed off pax, and a good few who missed connections at PHX from what I understood. As I was leaving the plane last, since I was sitting in back, I asked the FO and FA who were at the cockpit door what the real story was........was there a minor problem with the jet that they had to work out in the cockpit, but didn't want to rile up the pax over the PA, maybe?

Nope. Took too long with the checklist and "we didn't figure it'd be a problem, until we found out it was. And in any event, we've had a long day anyways." Oh really? No excuse. Seriously. What a bunch of crap for this kind of simple error.

Am curious though, had this happened in an aforementioned "busier airport", what then? These guys should freaking know better.

One funny thing was, that there were two regional guys riding in the back, not exactly sure which airline, but they were quietly chuckling about this embarassing error by a mainline crew.

I don't know, man. They got to the end of the runway and for one reason or another, couldn't be accommodated by ATC. I'm betting if they knew it would result in an hour delay, they would have made sure that they got out before that delay. From what you're saying it sounds like maybe they got to the end of the runway and the tower had them release and center wanted them airborne pronto. They may have had some more boxes to check and center probably said "forget it, then". It happens from time to time. 95% of the time, you have a general idea about those delays and that's about it. I'm sure they were doing the best they could. I would've probably explained it a little different on the PA.
 
Flying on US Airways 444, an A-319, from TUS to PHX yesterday. Get loaded up, push back, start, taxi. Getting to the runway, we're holding short #1 for an unusually long amount of time. Didn't see any traffic on final, so I figure its a release issue or something. Well, it was that and more.

Captain comes on over the PA after about 10-ish minutes at the hold short line. He announces that "ladies and gentlemen this is your captain, ummm, we've ummm, missed our release time from air traffic control for Phoenix, since we weren't finished with checklists up here in the cockpit, and now we can't take off apparently according to the tower. They're telling us it's going to be a 1 hour delay until we can depart for Phoenix in order to fit into the flow. I really apologize for the inconvenience."

Missed their IFR release because their checklists weren't complete?!?!?!

You kidding me!?! I mean, thats something I expect from flight school airplane on a IFR dual cross country, not something I expect from a supposedly "varsity team" mainline crew.

We're talking TUS here, not LGA or LAX or EWR during rush hour.

The Captain came on a few minutes later with "ladies and gentlemen, I really apologize.....if it makes you feel any better, in 15 years of being an airline captain, this has never happened and is the first time I've experienced it. We're very sorry for the delay."

We did a 180, taxiied to the quasi-penalty box, and held for the next 50 minutes, finally launching for PHX.

TUS to PHX is supposed to be a 27 minute flight.....the ground time was 55 minutes! Longer than the damn total flight time. All for some freaking rookie BS.

There were a lot of pissed off pax, and a good few who missed connections at PHX from what I understood. As I was leaving the plane last, since I was sitting in back, I asked the FO and FA who were at the cockpit door what the real story was........was there a minor problem with the jet that they had to work out in the cockpit, but didn't want to rile up the pax over the PA, maybe?

Nope. Took too long with the checklist and "we didn't figure it'd be a problem, until we found out it was. And in any event, we've had a long day anyways." Oh really? No excuse. Seriously. What a bunch of crap for this kind of simple error.

Am curious though, had this happened in an aforementioned "busier airport", what then? These guys should freaking know better.

One funny thing was, that there were two regional guys riding in the back, not exactly sure which airline, but they were quietly chuckling about this embarassing error by a mainline crew.

I don't know, man. They got to the end of the runway and for one reason or another, couldn't be accommodated by ATC. I'm betting if they knew it would result in an hour delay, they would have made sure that they got out before that delay. From what you're saying it sounds like maybe they got to the end of the runway and the tower had them released and center wanted them airborne pronto. They may have had some more boxes to check and center probably said "forget it, then". It happens from time to time. 95% of the time, you have a general idea about those delays and that's about it. I'm sure they were doing the best they could. I would've probably explained it a little different on the PA.
 
Like I said, passengers have this handy passenger bill of rights thing now...suppose you could have used it.

Nice attitude.

No need to use a bill of rights. You're dancing around the issue. Which is, do your freaking job and do it right, and maybe the general public will see the profession as more than just the aerial bus driver gig its become. Delays like this kind aren't things paying pax should have to deal with.

Or did you forget what the phrase "customer service" means? Remember who's the customer and who's the provider.
 
What proof do you have that this was the pilots fault?

There could be many reasons that would cause a checklist issue.

Joe
 
Nice attitude.

No need to use a bill of rights. You're dancing around the issue. Which is, do your freaking job and do it right, and maybe the general public will see the profession as more than just the aerial bus driver gig its become. Delays like this kind aren't things paying pax should have to deal with.

Or did you forget what the phrase "customer service" means? Remember who's the customer and who's the provider.
While you may be right about the customer service side I disagree with your statement if we do a professional job the traveling public will respect our job more. They've had safe transport for quite a while and the airline pilot gig is less and less respected every day.

Screw up a few more and then people will appreciate it when it all goes seamless. :) WUV YOU!
 
I don't know, man. They got to the end of the runway and for one reason or another, couldn't be accommodated by ATC. I'm betting if they knew it would result in an hour delay, they would have made sure that they got out before that delay. From what you're saying it sounds like maybe they got to the end of the runway and the tower had them released and center wanted them airborne pronto. They may have had some more boxes to check and center probably said "forget it, then". It happens from time to time. 95% of the time, you have a general idea about those delays and that's about it. I'm sure they were doing the best they could. I would've probably explained it a little different on the PA.

I can only go by the PA announcement, which sounded very surprised that anything like this could happen to him.....as if "I'm shocked the National Airspace System and everyone in it who was going to PHX wasn't able to wait on me to get myself airborne."

Im the first one to defend an airline crew against dumb pax complaints, but on this one, they got what they (as they admitted) created for themselves. This was a very avoidable delay, as opposed to times when the delay isn't.
 
While you may be right about the customer service side I disagree with your statement if we do a professional job the traveling public will respect our job more. They've had safe transport for quite a while and the airline pilot gig is less and less respected every day.

Screw up a few more and then people will appreciate it when it all goes seamless. :) WUV YOU!

The point is, that these kind of things aren't going to get the flying public on your side during things like informational picketing campaigns. While one has nothing to really do with the other, you have to look at it from the general pax perspective, whether you like it or not. Thats where your support is going to come from, or not. Unfortunately, the "safe transport for quite a while" is an assumed that comes with paying for a ticket.
 
What proof do you have that this was the pilots fault?

There could be many reasons that would cause a checklist issue.

Joe

Fir turbine aircraft, it is generally assumed that when you get to the runway, you will be ready to go (at least that is what ATC assumes).
 
What proof do you have that this was the pilots fault?

There could be many reasons that would cause a checklist issue.

Joe

did you not read the first post?

Self admitted PA announcement. I appreciate the crews honesty in their announcement but disagree with their surprise. A release time is a release time. It's an error that the pax shouldn't have to pay for in terms of missed connections, time, etc. A completely, avoidable delay, as the crew admitted.
 
What proof do you have that this was the pilots fault?

There could be many reasons that would cause a checklist issue.

Joe

Joe I think you have the right idea.

What if they didn't have the performance numbers for that runway yet? I don't know how US Airways does it but where I fly it's entirely possible that we get to the runway and if it was different from the one we expected back at the gate, we need to request the new data via ACARS. You can't go into position and hold without that stuff in and checked. Continuing with this example, why don't we request all runways while at the gate? Because it takes significantly longer for a second runway on the ACARS, and a third is almost out of the question. So in order to get things moving, we request one and hope it's a good guess.

Another possibility -- the flight was not only assigned a new runway, but perhaps the departure procedure was changed during the taxi out. If it's RNAV, it must be in the FMS because it's the only way to navigate it. Last week I pressed my FPL key and the entire FMS "timed out." Then we had to do the reset for that, and then do what we were going to do after that. About every other time I press the DLK key I get "DATALINK TIMEOUT" and I have to press the top right key rapidly several times and then sometimes helps clear the message.

Just a couple things off the top of my head that I can see adding on time needlessly but there's nothing you can do about it but wait.
 
50 minutes to get into PHX?! That part alone just seems weird... WTH was going on at PHX to necessitate 50 minutes flow control for an inbound?
 
Back
Top