Look - there are about 10 work groups that work to get the flight out. When there is a mx problem the pilots call mx control and mx control dispatches the mechanics. There is no interaction between the pilots and mechanics until they arrive at the airplane. How in the world does anyone expect the pilots to be able to pinpoint with swiss timing, the amount of minutes it will take to deal with a mx problem? When you take your car in for repairs, they give you an estimated time. There is no difference here. Mechanics get a BASIC idea of the problem when dispatched by mx control. It isn't until they arrive at an airplane and do their job, that the whole picture is discovered. THAT is why most delays are "rolling." We're also required to update every 15 minutes, with or without news, so that you're all kept in the loop, which is where your dreaded creeping 15 minute announcements come from. Sometimes we don't have the whole story or an accurate story to tell you. Passengers just have to have patience and flexibility when something irregular occurs.
I had patience, I had flexibility. But if pilots don't talk with mechanics and they can't pinpoint timing, then don't say it will only be a few minutes. Just say mechanics are coming and we will keep you apprised of the situation. I don't have a problem them telling me what they know, I have a problem saying one thing when they either don't know, or it is going to change. Again, I fault mostly the NWA ops folks.
Rolling delays are what frustrates/angers pax. Perhaps those that subscribe to such should consider better transparency and honesty.
Originally Posted by
dmitzel
Methinks the OP (and others) should be happy they got to their destination that night at all in any case. I faced a similar "plane swap" situation in FNT a few years ago, back when XJ was flying Avros. We were waiting at Gate 1 DTW-bound when the Gate 2 MSP-bound flight went MX. Ops swapped gates and we found out when all the MSP pax marched into the boarding area; looking up at the monitor I could see that it now read MSP with their flight monitor. When I walked over to 2, our flight was listed as CX.
Since these were the last flights of the day, I hustled down to the counter, only to be told it would be a couple of days until NW could get me to WAS (high loads). I ended up staying home that week after declaring "trip in vain" and getting a full refund on a "non-refundable" Y fare. The work suffered a slight bit, but I didn't feel it good stewardship of the Company's money to fly down there for only a day's work (Thu).
So, again, be glad everyone made it that day.
For the record I was happy to get to my destination. While I wasn't ecstatic about the delay, I think I have made it clear that I understand things happen when you travel and one should expect it. My postings here have been more or less to evoke a good discussion on how NWA handled it and to inquire into the "thrust" issue.
I usually do not book last flights of the day, in this case I had to make a change to it because of a work conf.