With flight planning turned on, flight time calculations will consider ATC optimized routes on domestic and international flight legs and real-time or historical wind data. To have the module enabled in your account, email Opsupport@avianis.com. Once the integration has been enabled, follow the steps below to complete the configuration.
Enable Module and Customize Cruise Profiles
Access the aircraft profile to turn on the "Calculate with Flight Planning" option.
When turned on, it will default using the standard type template profile and display like so:
Operations have the ability to customize default settings on each distance profile if needed. To do so, set use template to no. Click Edit by the distance profile to set a default cruise profile. Select from various settings: Custom Mach, Great Circle, Long Range Cruise, Various Mach Settings, Max Cruise, Standard or enter a Custom Mach value (if the aircraft type supports it).
Note: The copy template option allows the operation to pull in the current flight time configuration template Avianis offers.
Customize Aircraft Payload
Access the aircraft profile > Flight Planning tab to define when calculating the flight time, should the application consider a min or max payload value.
Note: The payload option is considered when not tail specific.
Flight Planning Settings
Once enhanced flight time calculation is enabled on the aircraft, access Operations > Settings > Configurations > ATC Flight Time Configurations. These settings allow the operation to set a default for when the calculations should run for the quote and the trip level independently.
When a quote and/or trip is created, it will automatically utilize the global flight planning engine based on the rules setup in the global settings. If defaults are set on the aircraft profile in the flight time configuration the cruise profile will auto-select but they can be overridden by leg as well.
Q: Does the performance data for the aircraft consider step climbs when planning routes?
A: Yes, they do. This is worth knowing as it is a concern for aircrews when flight planning and step climbs are pretty common. The flight planning engine attempts to find the best fuel burn scenario. Some of this is dependent on takeoff weight and ISA temperature/wind conditions. However, aircraft engines tend to operate more efficiently at higher altitudes so as the aircraft burns off fuel and looses weight the crew will often choose to climb to a higher altitude to achieve a more efficient fuel burn.
Q: How is the route selected?
A: It is based on the MTT Route (Minimum Time Tracked). The MTT Route is the shortest route based on burn and time.
Q: Does it consider recent routes flown?
A: Not at this time. It considers frequently cleared ATC routing and published airspace data (airways, NAVIADS, SIDS, STARS).
Q: What wind data does the application use when the enhanced option is enabled?
A: When the quote/trip dates are more than 24 hours from the time of creation, the system uses historical winds. When the quote/trip is within 24 hours the system will use real-time data from WSI.
Q: Why are the short position legs coming up with only 6 minutes?
A: At this time we do not take into account traffic volume and in a very limited way we take into account ATC routing. Our provider looks at frequently cleared routes from ATC however this data is limited for re-positioning flights between airports that are relatively close together. Most of the frequently cleared ATC routes would be between major city pairs such as LAX- SFO. Even though these are taken into account the system puts you on an optimized route that takes into account weather, aircraft performance, SIDs, STARs,NAVAIDs, and airways. All of this information is taken into account to calculate a route. For short routes though, say SJC - OAK, the system will often default to a direct route or send you out to one NAVAID and then back in. Although this is unlikely to be what the crew is cleared on the system defaults to that due to the difficulty of calculating a route between those two airports that takes into account all the factors previously stated. This is a limitation caused by the relatively short distance between these airports. In reality, the aircraft is unlikely to be put on an airway between those two airports by ATC anyways.