Skywest in KASE

To be fair- I'm 100% sure the kid that did the deicing was new and they fired him after that. The usual guys are pretty good.

It's always about payload reduction and they feel like they have to tell the passengers who's fault it is and rather than saying the weather they say "the pilots."
 
bLizZuE said:
To be fair- I'm 100% sure the kid that did the deicing was new and they fired him after that. The usual guys are pretty good.

It's always about payload reduction and they feel like they have to tell the passengers who's fault it is and rather than saying the weather they say "the pilots."
Click to expand...

Yeah, been there done that! A few months ago was the worst example I've seen in awhile... We were ended up having a min rest issue the night before, which moved our show time an hour later. We told the station (COS) the night before about the delay as well.

The next morning as we walk into the gate area, the pax all looked super pissed. We thought it strange that all of them looked angry, but didn't think too much more of it. After the pax boarded, several told the FAs that the gate agent made an announcement (before we got there) that the crew was late that morning since the Captain slept in!
 
I ALWAYS check my delay codes and dispute those that are incorrect. Probably at least 50% of the time I see stations trying to put delays on crews that are not our fault.
 
Blackhawk said:
I ALWAYS check my delay codes and dispute those that are incorrect. Probably at least 50% of the time I see stations trying to put delays on crews that are not our fault.
Click to expand...
We now get biffed by company e-mail for delays coded to us. Links you right to the inquiry page where you likely copy-paste the ACARS summary of 'CARGO DOORS NOT CLOSED AT D-ZERO' into the comments field.
 
Autothrust Blue said:
We now get biffed by company e-mail for delays coded to us. Links you right to the inquiry page where you likely copy-paste the ACARS summary of 'CARGO DOORS NOT CLOSED AT D-ZERO' into the comments field.
Click to expand...

I've never understood the delay code fights. It's all just a game...Put it on someone else and they'll just shift the blame. There are only 4 codes that get attributed properly, 1)ATC, 2)WX, 3)MX, 4)Security.
 
Luigi said:
I've never understood the delay code fights. It's all just a game...Put it on someone else and they'll just shift the blame. There are only 4 codes that get attributed properly, 1)ATC, 2)WX, 3)MX, 4)Security.
Click to expand...
Eh, I think I'm pretty honest in holding up my end (i.e. being at the airplane on time when the schedule permits...I mean really, that's 90% of being on time) and properly coding things as "DST" (station) or "DPX" (passengers/slow em/deplaning/extra handling).
 
Autothrust Blue said:
Eh, I think I'm pretty honest in holding up my end (i.e. being at the airplane on time when the schedule permits...I mean really, that's 90% of being on time) and properly coding things as "DST" (station) or "DPX" (passengers/slow em/deplaning/extra handling).
Click to expand...

Fair enough, my only point is that you say what happened and can back it up with a ACARS log, but the station gets the delay back and just gets to recode it again. It really matters very little. Delay coding should exist to pinpoint issues and prevent future mistakes; which means it should be completely non-punitive.
 
Blackhawk said:
I ALWAYS check my delay codes and dispute those that are incorrect. Probably at least 50% of the time I see stations trying to put delays on crews that are not our fault.
Click to expand...

Last week we pushed 9 minutes late because the rampers allowed the belt loader to run out of gas. Apparently that is somehow an excuse to blame the delay on flight crew!
 
adk said:
Last week we pushed 9 minutes late because the rampers allowed the belt loader to run out of gas. Apparently that is somehow an excuse to blame the delay on flight crew!
Click to expand...

If you'd pushed sooner, the belt loader wouldn't have run out of gas!

4a65fac217cbb981cefde54ab4bdd4b119bcb40d0a08cf3ffe10acd345275c60.jpg
 
Luigi said:
Fair enough, my only point is that you say what happened and can back it up with a ACARS log, but the station gets the delay back and just gets to recode it again. It really matters very little. Delay coding should exist to pinpoint issues and prevent future mistakes; which means it should be completely non-punitive.
Click to expand...
Yes, except in such cases where it's "flight crew straight up no-showed, no-called." Wait, we have a code for that ("unavailable crew").

adk said:
Last week we pushed 9 minutes late because the rampers allowed the belt loader to run out of gas. Apparently that is somehow an excuse to blame the delay on flight crew!
Click to expand...
Code: 
DFC UA LTFN: FLT OPS CREW PREDEPARTURE NORM CHECKLIST
 
Autothrust Blue said:
Yes, except in such cases where it's "flight crew straight up no-showed, no-called." Wait, we have a code for that ("unavailable crew").


Code: 
DFC UA LTFN: FLT OPS CREW PREDEPARTURE NORM CHECKLIST
Click to expand...

That's such a stupid code. I love it when stations pin it on "pre departure norm checklist" when you're running 1.5 hrs late. "Yep, sorry it took us an hour and a half to run a couple checklists guys."
 
B767 said:
That's such a stupid code. I love it when stations pin it on "pre departure norm checklist" when you're running 1.5 hrs late. "Yep, sorry it took us an hour and a half to run a couple checklists guys."
Click to expand...
It's such a "nothing" or "copout" code. Your situation is accurately described as "Late arriving aircraft MST fail: (reason, which might be flight crew safety checklists, and probably isn't)." There is actually a sub-code for that on the UA side too.

I can't run the last part of the "pre departure normal checklist" (I don't even know what that means, I have Safety and Power Up, Originating, and Before Start) until the CLR is done, the manifest is sent and our takeoff performance is set. But hey, keep coding it to me, when you hand me the paperwork 2 minutes before D0 and stomp off...
 
I can only control what is in my lane. I dispute delay codes that are not accurate then let the company deal with it. In almost every case it is changed to the correct code.
 
I'm slightly relieved to know that my airline isn't the only one that tries to play the delay-blame-game. Ours is pretty bad. They love to throw things on the flight attendants, even when it's clearly not their fault.
 
GypsyPilot said:
I'm a SKW ASE pilot. The key is using "instantaneous" winds. Nobody here is stupid enough to bust limitations, and I've never seen it happen. No reason for it either...

We cancel all the time for weather, and are pay protected. It's just part of the job. If you think we don't cancel and divert all the time too, you are very mistaken.

I'm assuming you do the special LOC DME 15? Or just the LOC DME?
Click to expand...

Like GypsyPilot, I did Aspen this winter too. Including flying one month with him!

Contrary to what your ops folks say we do our fair share of diverts with Aspen. This last week I did a 4 day trip with an Aspen turn each day in the early afternoon. The WX was clear and perfect all week, but every stinking time the tail winds picked up when we got there; as did the little down drafts on short final. Only once did we have to use the "instantaneous" winds and they stayed right around 8 or 9 knots on the tail and the tower called them out all the way down the approach. If they had exceeded 10 knots on the tail before we got too close, our plan was to bug out to Grand Junction. On several of those days, not long after we departed the winds picked up just enough that aircraft, including SkyWest aircraft were diverting.
 
bLizZuE said:
I'm slightly relieved to know that my airline isn't the only one that tries to play the delay-blame-game. Ours is pretty bad. They love to throw things on the flight attendants, even when it's clearly not their fault.
Click to expand...

One thing I have found is that if there is a delay it is normally thrown on the first "contributor" to that delay. For example, if FAs are suppose to be on board and ready 30 prior to departure and one shows up 29 prior to departure ANY delay will be coded as a crew delay due to the late FA.
 
:bounce::bounce::bounce::bounce:

I can't stop laughing at these comments. I am a ramper and also a gate agent. I can tell you right now that the delay game is and always will be blamed on the crew. For my station, our manager wants us to delay codes on crew as much as possible, regardless of the true story, because it affects our scorecard...which in return affects bonuses. Me and a few supervisors actually follow the rules and will code a delay on us, if it's our faults....but I've received many many calls from Delta asking to change a morning crews delay code. Seen some of my colleagues that are working the gate delay weather issues, waiting for passengers, belts stop working in -30 degree temps, etc....etc.....

I find it thoroughly amusing when we take a delay and watching my gate agents decide "how can we get this coded to not hit our station"....and I guarantee it's like that in all your other stations too. We are preached to live, eat, and breath the scorecard x2. Needless to say...I agree with you all!! I can't wait to be in your seat in a couple years laughing at what I'm blamed for next. Thankfully I'll have a built tolerance and patience knowing how some ramp agents are...:aghast:
 
Yeah so landing in the citation X at ASE. There is a 12 knot tailwind. We are not authorized to use RWY 15. So the captain lets the tower know our ops requires less than a 10 knot tailwind. The tower says winds are 9 knots at 150.

Thanks bro...

Thanks.
 
BEEF SUPREME said:
Yeah so landing in the citation X at ASE. There is a 12 knot tailwind. We are not authorized to use RWY 15. So the captain lets the tower know our ops requires less than a 10 knot tailwind. The tower says winds are 9 knots at 150.

Thanks bro...

Thanks.
Click to expand...

Well, in ASE the weather is always changing, so your captain asking for the current winds is the right thing to do. They aren't going to lie to you, if that's what you're getting at. ASE knows exactly what our limitations are, and countless times we've asked about wind and been given an answer that exceeds our limitations. It's the mountains... Things are constantly and quickly changing at any time, any season.

Also, you have your runways mixed up. You were landing 15, and a direct tailwind is 330.

I'm assuming you did monitor your TAS and GS to make sure you were in compliance with your limitations?
 
You must log in or register to reply here.
Back
Top