Originally Posted by
ERJ Jay
Actually,
The Howgozit recalculates each additional fix at the original SABRE flight planned speed and altitudes.
So you can ask for another HOWGOZIT after each fix, and it will recalculate based on the filed SABRE flight plan speed AND altitude.
If you are planning to go .80 (example), or at another altitude (rides), you need to manually send dispatch a message for them to rerun the flight plan and send you a .80/FL360 howgozit - when they do, that will update the SABRE flight plan in the system and it will THEN give you a valid howgozit.
But you are incorrect - it does NOT update what you've changed in the FMC (speed or altitude) - but simply "recomputes".
Have you ever noticed an excessively high number UAL app flight updates updating the arrival time so much on an inbound flight?
The reason for that is that the flight plan was .76 (example), but the guys are going .81 to be on time (A:00). After each fix or two, when the arrival time is updated (fix X distance remaining X SABRE speed of .76), the app "updates" the arrival time - based on flying the remaining flight at .76.
This "can" be incredibly annoying for our customers who's family is waiting for them and the app keeps updating the arrival time (getting there different than when they looked 5 hours ago). As the aircraft gets closer and closer, the distance remaining is so small that even when you go .81 the times eventually become the "estimated" arrival time.
As a result, if they don't recheck the arrival time on the app, the may not leave for the airport in time.
As a "technique", most L-UAL guys figure out what speed they want for the tracks, get the clearance from Gander/Shanwick - and then have dispatch rerun a new howgozit prior to coast out.
That way (five +/- hours from touch down), the UAL SABRE automated position reports can keep customers/opps/SONIC up to date with a very accurate estimated arrival time.
Nice technique IMHO - but it can increase the work load on an already overloaded dispatcher.
That's what I said.... Admittedly not very clearly. I'm well aware that it plans the REST of your flight with your Sabre plan, which is why I said if you want the new actual numbers you need to call dispatch and have then re-run. However, if you pull the numbers 1/3 of the way through the flight and compare the the original Howgozit, you can get a good idea of how much extra fuel your .81 has burned and how many minutes it's saved. Then you extrapolate. It takes about 10 seconds.
As far as bothering dispatch, if you're flying .81 on a .765 plan you really should get them involved anyway. You're going to be getting close to an time change large enough to require a report to them anyway per the FOM. And you're going to have quite a bit less fuel than they were expecting. If they don't have time, they will ignore you based on my experience.
If you don't like the Howgozit, that's fine. But I've found it to be a fantastic and easy tool over the years. Especially since it's tough to keep a fuel score without a paper FP (assuming non international leg). With the Howgozit, a quick glance will tell you everything. FWIW, keeping a fuel score manually on the Sabre plan is going to be just as worthless once you blow off the plan. And you introduce the possibility of math errors.
Pulling a Howgozit isn't going to change what the app says. So if you're worried about being "incredibly annoying" to the people coming to pick someone up, fly the plan... Or call dispatch. That's their job.