Amateur hour at US Airways

Cripes, I wouldn't be surprised if something like this happened with a regional, but USAirways is supposed to be a "real" airline. And how long is an Airbus checklist? I can't imagine it being that long, with all the automation and whatnot.

Oh well, like with bad TSA experiences, its just more job security for the frax/corporate sector.
 
sorry MikeD, people make mistakes, and sometimes it comes at your expense. Welcome to life. We should all bow to you for never making a mistake that affected anyone else.
 
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.

If that was the issue, they didn't mention anything or mention that it was due to any changes (which I assume they'd want to lay blame on IF that was the issue, rather than make it sound like it was totally their fault and they were surprised, as the PA announcement did). Runway was the duty runway it was all day, no changes there. Again, you had to hear the PA announcements that sounded shocked and surprised that even though they got to the runway late and not ready to go, that they just couldn't takeoff and now were forced to wait.
 
I'm not sure how their checklists are structured, but it's my opinion that I was and elbows between starting the second engine and putting the flaps up on departure, especially if you're not going to stop between starting that engine and getting on the runway.

Who knows if they were in the same situation, but for some operators there are simply too many items to be accomplished when you're just about to depart. They could have been in that position, and it's better to not rush if that's the case.
 
sorry MikeD, people make mistakes, and sometimes it comes at your expense. Welcome to life. We should all bow to you for never making a mistake that affected anyone else.

Nice personal attack, but no dice there punchy. Try again.

Yes, we all make mistakes, but ones like this that have far-reaching effects and are avoidable, aren't the kind that I would would try and write off. I hope these guys at least learned something from this.
 
I'm not sure how their checklists are structured, but it's my opinion that I was and elbows between starting the second engine and putting the flaps up on departure, especially if you're not going to stop between starting that engine and getting on the runway.

Who knows if they were in the same situation, but for some operators there are simply too many items to be accomplished when you're just about to depart. They could have been in that position, and it's better to not rush if that's the case.

Which brings up an interesting safety issue. Is being "holes and elbows" in that time between starting the second engine and getting cleaned up on departure a function of not having enough time from push back to takeoff, in a scheduling sense? Should crews be having to rush that fast and does that widen the arena for mistakes to be made and not caught until its too late?
 
yea, chose your words carefully when making passenger announcements.

Thats the thing. They didn't blame the situation on anything other than their not having the checklist complete. No problem there...again, they were very honest on that item.

They were just seemingly shocked and surprised that missing their release time equated to not being able to takeoff. Funny how that works. I mean, I know this is slow-ass TUS and we were the only jet taxiing out.....this wasn't EWR or LAX or anything, but guess what guys, don't be shocked and surprised that this happens when you take a seemingly cavalier attitude towards making your assigned release time.
 
something missing in this story. Almost without fail, I have always been given an 'if not airborne by ___' if there was a hard release time. Without being advised of a tight and closing window for release, I would fall back to my normal pacing for tasks. And what would give me a clue that TUS was going to have a hard release time? Like you said, it ain't 'zackly EWR in the winter.
 
Do they get leg by leg block or better at USAirways? If so, there's your answer :D

Also, I've never seen an EDCT time get pushed back 55 minutes just because you missed your original void time by a minute or two. That seems pretty outrageous. Usually you're waiting another 15 minutes at worst. Then again, LA/PHX seem to be a little less flexible than their east coast counterparts in my limited experience. That's not a knock, they may very well have a good reason for it.
 
Do they get leg by leg block or better at USAirways? If so, there's your answer :D

Also, I've never seen an EDCT time get pushed back 55 minutes just because you missed your original void time by a minute or two. That seems pretty outrageous. Usually you're waiting another 15 minutes at worst. Then again, LA/PHX seem to be a little less flexible than their east coast counterparts in my limited experience. That's not a knock, they may very well have a good reason for it.

East coast is used to it. I mean, sarcastically speaking, when PHX starts getting a couple of cumulus clouds here and there, they cancel visuals and start vectoring for ILSs. :)

something missing in this story. Almost without fail, I have always been given an 'if not airborne by ___' if there was a hard release time. Without being advised of a tight and closing window for release, I would fall back to my normal pacing for tasks. And what would give me a clue that TUS was going to have a hard release time? Like you said, it ain't 'zackly EWR in the winter.

Dunno. Wasn't privy to that part and they made no mention of it. I too would think if there was a void time, they'd know about it. Then again, Ive never tried to push a release time either if only for fear of not being able to launch.
 
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.
Flying public is not on our side. They never will be. No better evidence of that than after Colgan's crash and people were actually talking about pay.

Safe transport for quite a while actually goes to prove that the longer the traveling public receives seamless, safe, professional flying, the more they will take it for granted. My reference, which was might have served better as a parenthetical reference, may have been misleading. Your flight crew was safe, they may not have been professional. Maybe we should be saying that safety is non-negotiable but professionalism is. :)

Anyway, I don't work for Airways, they have their own business model. My regional business can be summed up by the taste of the coffee.
 
I'd personally be more upset at PHX TRACON for giving the guys such a narrow window. Sometimes those things are impossibly hard to deal with. And it may just be another feather in the cap for ATC to say, "See, SEE SEE! We need a new ATC system!!!!! OMGZ, those people could have been killed!"
 
No personal attack, but why on earth would anyone bother with TSA screening, wait, board, wait, taxi, take off (or not !), climb, descend, approach and land for a 27 minutes flight ? Is the drive THAT long ?
 
Flying public is not on our side. They never will be. No better evidence of that than after Colgan's crash and people were actually talking about pay.

Safe transport for quite a while actually goes to prove that the longer the traveling public receives seamless, safe, professional flying, the more they will take it for granted. My reference, which was might have served better as a parenthetical reference, may have been misleading. Your flight crew was safe, they may not have been professional. Maybe we should be saying that safety is non-negotiable but professionalism is. :)

Preaching to the choir, my friend. I know exactly what you mean and where you're coming from. What I'm saying is that this public perception is the unfortunate enemy you have to fight against, whether deserved or not. Sucks, but it is.
 
Which brings up an interesting safety issue. Is being "holes and elbows" in that time between starting the second engine and getting cleaned up on departure a function of not having enough time from push back to takeoff, in a scheduling sense? Should crews be having to rush that fast and does that widen the arena for mistakes to be made and not caught until its too late?

Well, there is certainly more time pressure in these scenarios now in light of the whole "passenger bill of rights". As we all know, ground stops, delay programs, and EDCT times can be very fluid. However airline management now pressures you not to board until the last possible second to mitigate the possibility of an "extended tarmac delay" which would result in a gate return or substantial fines. Ironically this can sometimes have the opposite effect (It happened to me on a CMH-EWR a few months back, ground stop lifted, cmh says "you can go when your ready", but we're not boarded yet....in the middle of boarding, they come back with a 90 minute EDCT.....had we already been boarded we could've blasted off when the ground stop got cx'd)

It's hard to say if any of that played a role in what happened, but I've certainly been getting a the stink eye from operations people lately if I dare suggest we start boarding more than 25-30 minutes prior to an existing EDCT.
 
No personal attack, but why on earth would anyone bother with TSA screening, wait, board, wait, taxi, take off (or not !), climb, descend, approach and land for a 27 minutes flight ? Is the drive THAT long ?

I didn't want to have to, but due to hub and spoke....thats the way it goes in order to catch a connection. Unless on SWA.
 
Back
Top