Currently, it seems the additive always defaults to “autothrottle on” without the possibility to default to another computation method (manually switching in case of large winds is easily forgotten).
The Airbus FMGS does apply the wind-based correction automatically, and I imagine performance calculators would do something similar by default?
In addition, the computation done by the drop-down seems to only account for METAR winds-- when manually entering winds (e.g. METAR not available or simply overriding the METAR data for testing) the computation seems to ignore the manually-specified wind component, which is unfortunate.
Regards,
Tim
Hi Tim,
Probably there should be default additives for different aircraft types, but that’s maybe a little ways off right now.
This is the bigger issue IMO. I actually noticed it as well the other day, will try to fix in the next version.
Best regards,
Perhaps there should be a save button for the additive in the meantime?
Regards,
Tim
Inflight and dispatch performance are 2 different animals. Under dispatch, what is my max allowable weight given these conditions; the runway is either dry or wet, everything working or not in accordance with the MEL. This flap configuration and done. A/T additives do not figure into dispatch landing performance.
What I’d like to see in the dispatching phase, is I determine my desired runway for takeoff (and landing) and the performance calculator will calculate the highest MTOW I can lift, or the highest MLDW I can land with given the weather conditions. When I am DX’ing, that is all I really care about. Inflight landing performance can reflect crew procedures (additives and the like), but dispatch takeoff (and landing performance), need not reflect crew procedures, for they are different animals.
In my DX tool at work, I enter my takeoff weather conditions (and applicable MEL/CDLs), and it will calculate the MTOW for all the runways (and intersections) at the airport (it’ll ignore those where the tailwind limit exceeds the max); I then select my desired departure runway once I know my MTOW off that strip of concrete.
Our landing tool works the same way.
I’d also like to be able to run a dispatch landing performance analysis for the planned alternate that is in the fuel ladder, for that is also technically a requirement at least for 121 ops.
