Some Dude said:
The dispatchers do a good job with the tools they have, however most of the info on the flight release is worthless. It's not their fault. It's just wrong. Second Segment climb is a useless number on the flight release.
I am always filed out of SMO with a flaps 10 departure. We never ever use flaps 10 numbers. We have to use flaps 20 out of SMO for noise abatement. Yet the release always show flaps 10. Also the wind data and temp data for takeoff is useless. It's not their fault it's just the program they have to use. We are not even allowed to use the second segment climb number on the release.
Actually I'm glad you brought up the 2nd segment climb issue. Many pilots and even ACP's aren't clear what our role is, was, or will be and it has been poorly communicated over the years - but it HAS been communicated.
A little history - with the exception of one 24 hour day a couple years ago, never in the life of the dispatch department have we been responsible for providing NJA crews with 2nd seg climb performance information. This is the only performance calculation that affects MATOW that the crew is solely responsible. There are two major reasons:
1. Training issues/Standardization. The company has about 12 fleets of a/c from 5 different manufacturers all with different AFM's. There is no standardization from the company on how to compute 2nd segment climb and each fleet seems to want it done slightly different depending on the scenario (The new FOM doesn't come close to resolving the standardization issues). Dispatchers are not fleet specific. I could be dispatching BE-400's one day and the BBJ the next - some times I have them both on the same day. Training dispatchers on each different fleet would be the last straw on an already very weighted back - which brings me to #2.
2. Workload. If we are going to add this "feature" to the release it needs to take less than 30 seconds for us to calculate it or we simply cannot handle the extra workload (Obviously there will be situations where when a problem is identified we will spend several minutes resolving the issue).
So why is it on your release? Excellent question. If it were up to me I would remove it. The data is not valid (with a few exceptions). The reason why it started showing up a couple years ago, and why I said there was one day we actually did it, was because we wanted to include it in Intellijet and provide this information to you - besides the FAA wants us to provide a valid MATOW - something the company has never accurately done on the release. All the dispatchers were trained (one way) and away we went. Well, as soon as we started using it, many software issues were discovered among other things and the next day we stopped using it and told pilots to ignore it. Well, it never got removed from the release and still shows there today. But as you probably know, this doesn't stop compitent dispatchers from taking it upon themselves to make sure there aren't limiting 2nd seg issues for your flight. We still make efforts to at least identify any potential show-stoppers.
That brings us to date. Your comments are very timely because Ops is currently in discussions to address this very issue and sometime this year the issues with standardization will be resolved, dispatchers will be appropriately trained, software issues fixed, and we'll give it another go. But you know how it is, don't hold your breath until you see the final product.
As for the flaps issue, no excuses, but sometimes it's difficult to remember all the different configurations for the different procedures out of the hundreds of airports we come out of in a day. And not all NJA a/c types change the default flap setting for the SMO departure, otherwise it would be much easier to remember. The long term goal for dispatch is to become type specific. I am personally pushing for this.
Your wind/temp data comment is innacurate, not sure what your issue is exactly. Dispatch has always provided T/O and Land numbers with zero winds and current temp after selecting the headwind rwy. If we have to select the downwind rwy then we will factor in the tailwind componant and make a note of it at the top of your 2nd page. We can and do provide you performance with any configuration of different wind/temps using UltraNav and 98% of the time it is dead accurate to the AFM - well, with the exception of a .01% conservative fudge factor.
The only confusing issue about the winds is that you used to see the wind speed from the METAR on your release and perhaps made you believe this was factored into the calculation even though it isn't. The DO recently asked us to start "zeroing out" this number for that reason. But it is still a manual process so you still may see it time to time until it gets automated.