WDR after pushback procedure (DAL/NWA)
#41
Make sure you get online and fill out LOSA surveys about the new procedure if you don't like it! - It is one of the few ways they will actually hear our opinions. That said, seems like if they are trying to save 2 minutes, why not have the baggage/cargo finalized two minutes earlier! 

I scored checklist and manuals considering the new WDR. I am completely embarrassed that our company would come up with a procedure as ignorant as this.
I hope we all follow it to a T and watch the operation grind to a halt.
We are better than this.
#42
Ramp 2 in ATL is a mess already, this will only make it like Jones town with a bunch of airplanes lying on the ground everywhere not moving.
However, I like that we don't have to have numbers anymore to push. I still think we need the 3 out times and the only way to do that without a technology change is this: Gate agent calls the tower: Cabin Door Closed. Ramp calls the tower: Cargo Door Closed. The airplane is out, we don't flip the beacon on for real until cleared to push. Now they've got 3 out times, 2 called in and 1 for real.
Don't trust the numbers? You've got cameras all over the place, audit people.
However, I like that we don't have to have numbers anymore to push. I still think we need the 3 out times and the only way to do that without a technology change is this: Gate agent calls the tower: Cabin Door Closed. Ramp calls the tower: Cargo Door Closed. The airplane is out, we don't flip the beacon on for real until cleared to push. Now they've got 3 out times, 2 called in and 1 for real.
Don't trust the numbers? You've got cameras all over the place, audit people.
#43
Gets Weekends Off
Joined: Jun 2009
Posts: 5,113
Likes: 0
I just hope my Captains don't decide to go for their merit badges on this one, and FULLY comply with the procedures.
Eagle Scout Candidate:
"OK, call for taxi, and go ahead and put in the numbers"
Procedure-minded F/O:
"I can't: the brakes aren't set"
Awkward silence ensues...
Eagle Scout Candidate:
"OK, call for taxi, and go ahead and put in the numbers"
Procedure-minded F/O:
"I can't: the brakes aren't set"
Awkward silence ensues...
#44
Gets Weekends Off
Joined: Jun 2009
Posts: 5,113
Likes: 0
Another point about the new procedure:
Currently, ACS has two problems that cause it to be penalized for delays:
1) It can't get people and cargo loaded on time for a good portion of the flights, and
2) Flight Ops insists on tying the beacon, and therefore actual pushback time, to the out message. This makes ACS responsible for ramp and ATC delays for a good portion of the flights.
We also have a problem in that Flight Ops is actually shifting ramp and ATC delays onto our wallets, by designing proceure that causes us to sit for free until cleared to push.
By going to the new procedure, ACS is able to get the flights out a little sooner, making them less succeptible to Load Planning issues and AWABS issuance, but it doesn't quite solve the beacon problem. So they're only able to shift the Load Planning portion of the equation off, and maybe will get lucky avoiding ramp and ATC delays, if they get us ready a little early. Their efforts can still be scuttled if we can't push.
Now, by helping with the beacon (theoretically), we would only hide the problems, and give Flight Ops and ACS cover.
By fully complying with new procedures, IF the result is ramp or taxyway congestion, then we're simply leaving the problem exactly where it belongs: Flight Ops' insistance that we use an inappropriate trigger for on-time.
Ergo, failing to enter AWABS fully stopped is not simply a violation of procedure, and an attempt to work for free, but it is also a way of allowing someone else's problem to be shifted to you, your safety, and your certificate.
The reason this could be a dangerous procedure is that someone, somewhere, is potentially going to step on their [...] while trying to "help". I think logic and safety demand that we do NOT try to reinvent the wheel, and we don't pervert the data by trying to shotgun this stuff. This will allow the natural consequences of the procedure to be revealed. Maybe it will be a problem, maybe it won't.
Regardless, the solution to all of this actually is remarkably simple: Delta needs to insist on a procedure that sends the appropriate data at the appropriate times. FTB explained the concept very well.
Currently, ACS has two problems that cause it to be penalized for delays:
1) It can't get people and cargo loaded on time for a good portion of the flights, and
2) Flight Ops insists on tying the beacon, and therefore actual pushback time, to the out message. This makes ACS responsible for ramp and ATC delays for a good portion of the flights.
We also have a problem in that Flight Ops is actually shifting ramp and ATC delays onto our wallets, by designing proceure that causes us to sit for free until cleared to push.
By going to the new procedure, ACS is able to get the flights out a little sooner, making them less succeptible to Load Planning issues and AWABS issuance, but it doesn't quite solve the beacon problem. So they're only able to shift the Load Planning portion of the equation off, and maybe will get lucky avoiding ramp and ATC delays, if they get us ready a little early. Their efforts can still be scuttled if we can't push.
Now, by helping with the beacon (theoretically), we would only hide the problems, and give Flight Ops and ACS cover.
By fully complying with new procedures, IF the result is ramp or taxyway congestion, then we're simply leaving the problem exactly where it belongs: Flight Ops' insistance that we use an inappropriate trigger for on-time.
Ergo, failing to enter AWABS fully stopped is not simply a violation of procedure, and an attempt to work for free, but it is also a way of allowing someone else's problem to be shifted to you, your safety, and your certificate.
The reason this could be a dangerous procedure is that someone, somewhere, is potentially going to step on their [...] while trying to "help". I think logic and safety demand that we do NOT try to reinvent the wheel, and we don't pervert the data by trying to shotgun this stuff. This will allow the natural consequences of the procedure to be revealed. Maybe it will be a problem, maybe it won't.
Regardless, the solution to all of this actually is remarkably simple: Delta needs to insist on a procedure that sends the appropriate data at the appropriate times. FTB explained the concept very well.
#45
Gets Weekends Off
Joined: Feb 2006
Posts: 973
Likes: 0
From: A320 CA
I just hope my Captains don't decide to go for their merit badges on this one, and FULLY comply with the procedures.
Eagle Scout Candidate:
"OK, call for taxi, and go ahead and put in the numbers"
Procedure-minded F/O:
"I can't: the brakes aren't set"
Awkward silence ensues...
Eagle Scout Candidate:
"OK, call for taxi, and go ahead and put in the numbers"
Procedure-minded F/O:
"I can't: the brakes aren't set"
Awkward silence ensues...
Data WILL be reviewed and entered with the brakes set.
No merit badges awarded
#46
I received confirmation from standards that the brakes SET for review of WDR data is how DAL wants it done. There is no big bubble wiggle room out there Captains. Set the brakes review the data, insert the data, call for taxi, or resume taxi.
Data WILL be reviewed and entered with the brakes set.
No merit badges awarded
Data WILL be reviewed and entered with the brakes set.
No merit badges awarded

FO's don't allow this! We need to let the operation grind to a halt while this stupidity works itself out.
#48
Gets Weekends Off
Joined: Jun 2008
Posts: 3,716
Likes: 0
Make sure you get online and fill out LOSA surveys about the new procedure if you don't like it! - It is one of the few ways they will actually hear our opinions. That said, seems like if they are trying to save 2 minutes, why not have the baggage/cargo finalized two minutes earlier! 

Thread
Thread Starter
Forum
Replies
Last Post



