![]() |
Originally Posted by buzzpat
(Post 823580)
Nosmo, appreciate the feedback but that doesn't really address the issue of late AWABS. Most of what you're reporting is the same thing I see going through DTW. Its not the load planners but the catering folks who are screwing up. That's a whole 'nother issue. I get the catering deal...I've been there. This issue that Carl raised was not getting the W&B from the company prior to pushing on time. That's a separate issue and one that I've not seen very often in my years at Delta. The catering thing, and the "home boy" approach to blocking in and blocking out jets in Detroit is a different issue and ones that need to be addressed ASAP.
|
Originally Posted by buzzpat
(Post 823580)
Nosmo, appreciate the feedback but that doesn't really address the issue of late AWABS.
Originally Posted by Nosmo King
(Post 823576)
I'll just do the short(ok medium) version on this topic.
A330 ATL-HNL 9/10 departures this year I've been pushed late due to late AWABS numbers. Carl |
Originally Posted by Carl Spackler
(Post 823586)
What do you mean that Nosmo's post doesn't really address the issue of late AWABS? Here is the very first paragraph of Nosmo's post:
I don't know how he could have been any clearer that late AWABS is happening to him too. Carl |
And, as I also recall, northie guys are used to pushing without the AWABS and getting it on the roll. That's been a change, obviously, to how you do business. Southies wait until it comes across before wrapping up the Pushback check and calling the ramp. MB there's a cultural thing there that is being addressed. All I'm saying, and I've been here awhile, is that late AWABS are not, and never have been, a problem. If you guys are having them I suppose its because of the new equipment, training going on in ATL or whatever. Doesn't mean its not happening. Just means I'm not seeing it.
|
Originally Posted by 80ktsClamp
(Post 823393)
Remember, commuting is a choice, and it is on the borderline of even being ethical.
If I were to miss a commute, I would just do the right thing and resign right there. Then give myself 20 lashings for immoral behavior. :) Scoop :) |
Originally Posted by buzzpat
(Post 823588)
Carl, as you often like to post...you're not listening. Read the rest of his response. Quite cherry picking what you like and don't like about a response. Read it again: about 80% is catering, changing catering companies, etc. That's a cultural thing and a contractor thing. I know you get it. The AWABS thing is an internal Delta issue and a completely different issue.
Man it's going to be difficult to affect change if people aren't even reading. Carl |
Originally Posted by buzzpat
(Post 823590)
And, as I also recall, northie guys are used to pushing without the AWABS and getting it on the roll. That's been a change, obviously, to how you do business. Southies wait until it comes across before wrapping up the Pushback check and calling the ramp. MB there's a cultural thing there that is being addressed. All I'm saying, and I've been here awhile, is that late AWABS are not, and never have been, a problem. If you guys are having them I suppose its because of the new equipment, training going on in ATL or whatever. Doesn't mean its not happening. Just means I'm not seeing it.
It would be like if NWA was the surviving management, and we issued the fDAL guys a memo stating that we do not use LNAV. Rather, we put the ND's in VOR mode and keep the needle centered by changing the heading bug. You would probably think that was backward change. Then we could respond, "oh you former DAL guys just don't like change." Carl |
Originally Posted by DAL 88 Driver
(Post 823268)
I can't speak for the other fleets... I've only flown the 88 and the -9 at Delta. But I see absolutely nothing wrong with single-engine taxi being the norm. Obviously, like anything else, you have to use common sense. If you're going to be taxiing up a big hill, then you probably need to start 'em both up before that. On the other hand, there are examples like 26L in ATL. If there's a long lineup for takeoff, then you might need both engines to get up that hill. But, if you can get some speed up prior to engaging the hill, you can coast all the way up at idle power. It just takes a little bit of planning. For example, 29 knots of ground speed was the magic number on the 88 to make it up the 26L hill. In other words, if you hit 29 knots at the bottom (just before going up the hill), you'll make if fine at idle with only one engine. It's a nice smooth taxiway... so no problems with that speed. But my point is (and my experience has been) that you can safely use single-engine taxi a high percentage of the time and it will save fuel in most situations. And that savings really adds up after a while! Even on the 88 and the -9 (which is a very busy seat for the F/O), I've never found it to be too high of a workload during taxi. Like I said before, it just takes a little bit of planning and common sense.
BTW, I agree with you about all the other little areas Delta throws money away. While that is very frustrating, I just don't think it leads to a logical conclusion that we shouldn't care and try to operate efficiently whenever we can do so safely and without compromising our product to our customers. Anyway... just my "2 cents", FWIW. Common sense - you hit the nail squarely on the head. I have been doing S/E taxi at DAL for years and think its a great policy........ with one big exception. I hate being in the middle of a single engine taxi and getting a runway change. If we are single engine and get a rwy change we should stop and set the friggin parking brake. Why is it a such big mystery what rwy we will be using?? Granted, I am not the sharpest tool in the shed but when I am doing the rwy change items while doing a delayed engine start I am totally worthless as a back-up to the CAPT as far as taxiing goes. I am pretty much inside with quick/sporadic looks outside and it bothers me every-time we do it. I can literally feel the hairs stand up on the back of my neck - like I am doing something wrong and should know better. If asked what will be the cause of the next mishap at DAL my vote is for some kind of ground incident/rwy incursion while the FO was doing the delayed start checklist and rwy change items simultaneously. Now I know what you are thinking - just stop if you are uncomfortable. Well this would solve the problem at an individual level but it would not solve the problem for DAL as a whole. This should be an ALPA issue. Yeah I know batteries in the cargo hold are a dire threat but so is overtasked FO's! If S/E taxi is so important to DAL then let them work out a system with ATC where you receive an "expected" runway with your PDC 100% of the time. Rant Over - Scoop :mad: Mad face for emphasis! |
Originally Posted by Carl Spackler
(Post 823601)
Y
It would be like if NWA was the surviving management, and we issued the fDAL guys a memo stating that we do not use LNAV. Rather, we put the ND's in VOR mode and keep the needle centered by changing the heading bug. You would probably think that was backward change. Then we could respond, "oh you former DAL guys just don't like change." Carl |
Originally Posted by Scoop
(Post 823608)
DAL,
Common sense - you hit the nail squarely on the head. I have been doing S/E taxi at DAL for years and think its a great policy........ with one big exception. I hate being in the middle of a single engine taxi and getting a runway change. If we are single engine and get a rwy change we should stop and set the friggin parking brake. Why is it a such big mystery what rwy we will be using?? Granted, I am not the sharpest tool in the shed but when I am doing the rwy change items while doing a delayed engine start I am totally worthless as a back-up to the CAPT as far as taxiing goes. I am pretty much inside with quick/sporadic looks outside and it bothers me every-time we do it. I can literally feel the hairs stand up on the back of my neck - like I am doing something wrong and should know better. If asked what will be the cause of the next mishap at DAL my vote is for some kind of ground incident/rwy incursion while the FO was doing the delayed start checklist and rwy change items simultaneously. Now I know what you are thinking - just stop if you are uncomfortable. Well this would solve the problem at an individual level but it would not solve the problem for DAL as a whole. This should be an ALPA issue. Yeah I know batteries in the cargo hold are a dire threat but so is overtasked FO's! If S/E taxi is so important to DAL then let them work out a system with ATC where you receive an "expected" runway with your PDC 100% of the time. Rant Over - Scoop :mad: Mad face for emphasis! I agree with you. However, my experience has been that the runway change stuff is a pretty low percentage of the time. And whenever it does happen, that's when I slow down the operation to make sure we are getting everything done correctly. I would never recommend that anyone do a delayed engine started while simultaneously accomplishing the runway change items. That's just a setup for a potentially bad mistake. If we have to delay takeoff to make sure we get it all done, then so be it. |
| All times are GMT -8. The time now is 01:03 AM. |
Website Copyright © 2026 MH Sub I, LLC dba Internet Brands