Delay code "CPT slow closing door"

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.
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.
 
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.

As someone who has delayed flights both as a gate agent and pilot, I've never gotten in trouble for delaying a flight. I get what you're saying, and I've definitely seen the us vs them mentality, however I think it's more of a nobody really likes being wrong kind of mentality and so if I can blame the other person, I will feel better. And yes, station's on time performance (at least to the company) is based off of D-0 for conditions they can control. That kind of stuff is what helps push people to make sure the flight gets out. Also, flight attendants are definitely treated the worst when it comes to delays. At my old shop they were threatened with firing if they received more than 5 delays in a rolling year, when I was a gate agent, so long as I had a halfway good reason, I could delay 5 flights a week (or day) and not have problems. Thankfully it didn't happen that often, but hey, it happens.

I just wish people would realize that having a delay coded against you isn't really a big deal. Like most people have said, the CPO will call, hear what happened and say OK, sounds good. Remember,ultimately the goal is to identify trends in order to rectify problems, and improve operational performance.

Last thing, there was a huge section of delay codes at my previous shops for dispatchers. Like you said, most of them are safety related, but dispatchers are people, too and make mistakes. I remember once (and I mean only once, dispatchers are generally good eggs), I had to code a delay on a dispatcher because they hadn't worked the release up in time.
 
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.
 
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.
 
One super early morning there were two flights leaving at the same time. The other flight started their engines and sat there for a while, which delayed our boarding and caused a delay. I tried to get ops, jokingly, to put our delay on the other guy. Not sure if she ever did. But we like to give the other pilots a hard time.
 
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
This, always free texted with D-0 time line. Never heard anything.
 
I've had this conversation more than once:

"We'll go when everything is done, and done right (no pun intended). Code it however you want. "

Never got a call...
 
One time a gate agent was being completely unreasonable for whatever reason, and it's the only time I did this.

I tore off a sheet of printer paper and wrote my full name and cell phone number on it and handed it to them and said, put this delay in an "Other" category and write this in as the remarks.

I still didn't get a phone call.

Outsourcing is entertainment-value-only sometimes.
 
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.

Richmond is absolutely horrendous.

And that is an understatement.


Sent from my iPhone using Tapatalk
 
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 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.

It's competitive. Everyone wants to be the "on time airline" and knock the leader off the top spot.
 
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."
 
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."
"MST unrealistic" has appeared more than once. Major disconnect between doing this in testing and doing this in reality.
 
Back
Top