Autothrust Blue
“If you jump on my shift, that’s just rude, man.”
just one?This D-0 thing really breeds a toxic culture of finger pointing. I had one coded "check list" when it was actually the rampers running around looking for a headset.
just one?This D-0 thing really breeds a toxic culture of finger pointing. I had one coded "check list" when it was actually the rampers running around looking for a headset.
Where I (and @Luigi) work seem to be the opposite. Flight Operations is the delay sink, mostly because (short of "unavailable crew" or "crewmember late to aircraft"), nobody gets into trouble for it.All I know is that at SJI, when they code it as a pilot delay, the CPO will ask the pilots the real reason, and bounce it back to the appropriate dept. If it truly is a pilot delay, the response is, "Welp, you had a good reason. Have a great day." After a few months of this, pilot delays decreased dramatically once the agents figured out we were rubber and they were glue.
Oh, you are working against people. Certain companies (luckily not the one I work for currently) instill a "us vs them" culture. It certainly was that way at my old carrier. And I can promise you that a gate agent gets in a hell of a lot more trouble for a delay than a pilot would. Now a days I don't give a crap what a delay is coded to because the only way I can create a delay is in the interest of safety. Last time I checked:
(b) The pilot in command and the aircraft dispatcher are jointly responsible for the preflight planning, delay, and dispatch release of a flight in compliance with this chapter and operations specifications.
(c) The aircraft dispatcher is responsible for—
(1) Monitoring the progress of each flight;
(2) Issuing necessary information for the safety of the flight; and
(3) Cancelling or redispatching a flight if, in his opinion or the opinion of the pilot in command, the flight cannot operate or continue to operate safely as planned or released.
Again, not like anyone asked, but I have the delay codes on my tablet. If we're late, I send what it is to OCC and let it fly.
I've only been asked to clarify once because they called it a "crew delay" when, in fact, yeah, it was, but if the plane wasn't cleaned and catered, the crew ain't gonna leave so reassign the delay to what I said it was in the first place.GOOD DAY SIR. GOOD DAY.
At the regional level it's a much more adversarial relationship with all parties involved.
I know.
I didn't know I wasn't invited to participate!Ha!
This, always free texted with D-0 time line. Never heard anything.I usually sent an ACARS message to dispatch 5 prior if it didnt look like D-0 wasn't going to happen.
Just a simple, "called for boarding at 12. Boarding didn't commence until 12:20, it's now 12:25 and it looks like we won't make 12:30 dept."
Never had questions asked after that
What?just one?
No I have had a few but not many as I run a tight shipjust one?
.. Another one that comes to mind was coded to the flight crew because the agent thought I made my welcome aboard announcement too late for her liking and told the A flight attendant so as she was getting off the airplane.I do an IOR every time. The FAs are also writing one this time. They were pretty POed.
I have not done pictures or video in the past, but probably will after several run ins with RIC. In each case the RIC station said it was my fault so it turned into a "he said she said" and I lost.
I never understood the D:0 philosophy. You always have to push on time but you are allowed to have A:14? D:5 makes sense to me. It gives time just in case ramp is a cluster or some other simple reason. I took a delay the other day just because the FMS refused to capture a time during the push.
Sadly my current airline has a thing against technology and giving us information so I can't look up delay codes or anything else that could be helpful.
I know why it exists. The standards set by the DoT just need reworked a bit.It's competitive. Everyone wants to be the "on time airline" and knock the leader off the top spot.
"MST unrealistic" has appeared more than once. Major disconnect between doing this in testing and doing this in reality.If it's my fault, I'll gladly take the blame.
Otherwise, I end up calling it like it is. Which isn't always welcome.
Oh, so we're scheduled for 35 minutes on the ground, and we have an airplane swap, and 3 wheelchairs to deplane, and it's a known fact that the subcontractor that the company uses for wheelchairs never shows up on time? Reported as "Unrealistic expectations."