Hello,
for me, this makes sense at least for the part where planning is concerned. Even at the first leg, the plan brought from home needs to be cross verified with the real world on the apron and in case of differences the plan needs to be updated or the real world refueled. PICs checking their past flights and comparing their fuel remaining can raise or lower their contingency percentage to adapt to their actual values.
I like the approach from FlorianK where for every "land here" event the options of estimated takeoff time and estimated remaining fuel are defined. However, i see some Challenges in solving that request:
- Should this be a one time calculation when "land here" is pressed and the next leg is created? The values are set but not re-calculated if leg 1 has been updated afterwards. Danger of having calculated values not being accurate anymore (e.g. by prolonging the first leg)
- Should the calculation be linked and continuously recalculated and prohibit a change in values unless the link between previous leg and next leg is deactivated? I guess that needs a significant redesing of the data model on SD-side if they concider the individual legs as individual flights.