Amateur hour at US Airways

Just went for a jog and thought of another thing.

How about a green-on-green crew situation, or something similar?

i.e. captain recently came to the Airbus from the right seat of the 757, and the first officer just came back from 2 years of military deployment. Each has only been back to work for a month or two and they are paired together. Would it not be prudent to make sure both are on the same page when the trip starts as far as just taking it slow and making sure everything is done just right?

Just another example of what could have been going on up there, and that's not the type of thing I'd want to include in the PA either.

Thats entirely possible. Not being a 121 guy myself, I don't know the going ideas on how truthful, or not, that PA announcements should or shouldn't be to pax. Guess it depends.
 
Thats entirely possible. Not being a 121 guy myself, I don't know the going ideas on how truthful, or not, that PA announcements should or shouldn't be to pax. Guess it depends.

Sure, I know what you mean.

I just think that something else was going on here that they did not mention. What I just typed is a good example -- a perfectly reasonable explanation as to why they are taking their time in the name of safety yet not something most passengers would prefer to hear, that their crew is split between new to the airplane and first week back and work in a couple years.
 
Wow. Talk about dooshbags coming out of the woodwork.

"How do you know the pilots didn't lie about the situation?"
"How do you know it wasn't their fault?"
"What if it was mechanical and they lied about it?"
"Why are you complaining?"
"Why didn't you drive?"
"Anybody else can b*tch about a flight except you, MikeD."
"Your armchair quarterbacking something that they told you happened."
"Nobody has to agree with you."
:rolleyes:

I'll try not to take that too personnally, it would give you waaaay too much importance :rolleyes:
 
Sure, I know what you mean.

I just think that something else was going on here that they did not mention. What I just typed is a good example -- a perfectly reasonable explanation as to why they are taking their time in the name of safety yet not something most passengers would prefer to hear, that their crew is split between new to the airplane and first week back and work in a couple years.

Anything is possible I agree. As I said, just the sound of being so surprised that missing one's release time could actually mean missing one's takeoff time, in the long time that they'd been in the business, struck me as very odd to feel much less to say over the PA.

But there very well could be any number of alternate explanations, weird as they may have been handled.
 
Delays usually start before the plane even starts getting loaded in my limited experience.

Most of the time. Not all the time.

Unless we're physically in the jumpseat and plugged in, we're not in a position to question the professionalism of the crew in the completion of their tasks. A 15 minute window for release can run out in a hurry when the tug driver is new, the engines need to be run for a specific number of minutes before takeoff, ATC changes the departure runway or departure procedure, etc. There can be a lot to accomplish, and I'd rather the crew take their time in getting everything squared away.

Racing to the end to meet a release time and forgetting something like setting takeoff trim is indicative of an "amateur" crew. Completing what needs to be done in however long it takes to do properly is not.
 
Most of the time. Not all the time.

Unless we're physically in the jumpseat and plugged in, we're not in a position to question the professionalism of the crew in the completion of their tasks. A 15 minute window for release can run out in a hurry when the tug driver is new, the engines need to be run for a specific number of minutes before takeoff, ATC changes the departure runway or departure procedure, etc. There can be a lot to accomplish, and I'd rather the crew take their time in getting everything squared away.

Racing to the end to meet a release time and forgetting something like setting takeoff trim is indicative of an "amateur" crew. Completing what needs to be done in however long it takes to do properly is not.

Absolutely.
 
Most of the time. Not all the time.

Unless we're physically in the jumpseat and plugged in, we're not in a position to question the professionalism of the crew in the completion of their tasks. A 15 minute window for release can run out in a hurry when the tug driver is new, the engines need to be run for a specific number of minutes before takeoff, ATC changes the departure runway or departure procedure, etc. There can be a lot to accomplish, and I'd rather the crew take their time in getting everything squared away.

Racing to the end to meet a release time and forgetting something like setting takeoff trim is indicative of an "amateur" crew. Completing what needs to be done in however long it takes to do properly is not.

Of course. Again, I can only go by what the crew was saying. Sounding completely surprised that a delay had the effect it did.....you had to hear how the announcement was made and what it specifically said, as well as the comments afterwards......made it seem that the crew was shocked that missing an ATC release time due to needing to get stuff done, could cause a delay as it did. Again, only going by what was said, as I was there to hear it.
 
Gotcha...next time we're at the gate I'm gonna go ahead and knock out the before takeoff checklist...you know, flap verifications, telling the flight attendant to be seated, etc. How silly of me to not have that taken care of at the gate.

Hmmm you verify flaps on the before takeoff check? Little late, isn't it? :D
 
Anything is possible I agree.

But there very well could be any number of alternate explanations, weird as they may have been handled.


I always just blame TSA or CBP for any delays. They're nice big faceless agencies to absorb the blame.






:D
 
I remember coming in on a Southwest flight into MCI. We were cranking and banking at a much lower altitude than seemed normal in most airline flights. As we turned final, we flew it for a short time and the engines spooled up and we went missed. Either the CA or FO came on a blamed it on traffic on the runway....YEAH RIGHT!
 
I'm just surprised they gave the PAX all the unnecessary information.... It seems like "There's an air traffic control delay" would've sufficed....
 
Either the CA or FO came on a blamed it on traffic on the runway....YEAH RIGHT!


How do you know it wasnt? I just hate this monday quarterbacking stuff we all do... I remember a few months back I did an AGS-CLT morning flight. Left early and all was going well. Come to short final on 18C into CLT and ATC puts a DC9 in DAL colors into position and hold as we're on a 2 mile final.... Needless to say the spacing didnt work out and we executed a go around. On the go around it was executed perfectly. I made the PA saying what happen and we come back around to land. The CA lands it, not a great smooth landing but perfectly acceptable.... And we taxi in...

Old man at the end says as he's on his way out, " Did you two young punks get your liscense yesterday." "Worst flipping flight I've ever been on." I of course just smiled and blew it off as my FA (senior lady) goes, "I guess you didnt see that plane on the ground, we could have hit it and killed all 50 on here plus the 100 plus on there." "Which would you have preferred sir?" :)

Anyways.... I'm just saying, even if we fly the plane and work for the same company, we havent a clue unless we're up there..... Until then if everything goes fine and you land and walk away, I dont think there's much room to talk.... That's just me..
 
Hmmm you verify flaps on the before takeoff check? Little late, isn't it? :D

Not really. We just recently had some checklist changes that have us check them on the after start and again on the before takeoff (done while taxiing out). We're supposed to make sure we have them selected to the same setting dictated by our performance data to avoid doing what PSA did in HVQ.
 
#1: You flew to PHX from TUS. 'Nuff said.
#2: Someone with a mind like yours should be properly sedated before flying commercially so that you wouldn't notice any delay, or even a crash for that matter.
#3: This whole situation could be avoided in the future if they build that high-speed train from TUS to PHX. :D
 
#1: You flew to PHX from TUS. 'Nuff said.
#2: Someone with a mind like yours should be properly sedated before flying commercially so that you wouldn't notice any delay, or even a crash for that matter.
#3: This whole situation could be avoided in the future if they build that high-speed train from TUS to PHX. :D

#4: Should've gone VFR! :rotfl:

:popcorn:
 
How do you know it wasnt? I just hate this monday quarterbacking stuff we all do... I remember a few months back I did an AGS-CLT morning flight. Left early and all was going well. Come to short final on 18C into CLT and ATC puts a DC9 in DAL colors into position and hold as we're on a 2 mile final.... Needless to say the spacing didnt work out and we executed a go around. On the go around it was executed perfectly. I made the PA saying what happen and we come back around to land. The CA lands it, not a great smooth landing but perfectly acceptable.... And we taxi in...

Old man at the end says as he's on his way out, " Did you two young punks get your liscense yesterday." "Worst flipping flight I've ever been on." I of course just smiled and blew it off as my FA (senior lady) goes, "I guess you didnt see that plane on the ground, we could have hit it and killed all 50 on here plus the 100 plus on there." "Which would you have preferred sir?" :)

Anyways.... I'm just saying, even if we fly the plane and work for the same company, we havent a clue unless we're up there..... Until then if everything goes fine and you land and walk away, I dont think there's much room to talk.... That's just me..

I guess it's acceptable to monday morning quarterback from someone else's personal experience and interpretation of an event. ;)

It very well could have been traffic. But from my limited experience and our rollout from a 90 degree bank at 5' AGL for a quarter-second, I would have put money on a bad approach. Could have very well been traffic or a poor vector, but they were dodging small buildups(thank you) and it was far from busy at the airport at that 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.

Runway 25L/7R in PHX is closed right now so they are down to 2 runways. They are having all kinds of delays there...I did the TUS-PHX flight a week or so ago, missed my window by a couple minutes, tried to get in VFR and had to spin in circles for almost 90 minutes...
 
Back
Top