I’d like to suggest a change to how SimBrief calculates enroute landing performance, specifically the landing weight and resulting VREF.
To better mimic real-world operations and ACARS/FMS workflows, I think the calculation could be based on two values that are commonly entered or available to the flight crew:
-
Zero Fuel Weight (ZFW)
-
Estimated Arrival Fuel (EFOB / estimated fuel remaining at destination)
The backend could then calculate the estimated landing weight as:
Estimated Landing Weight = ZFW + Estimated Arrival Fuel
That landing weight could subsequently be used to calculate the appropriate VREF (and any other landing-performance parameters).
This seems more representative of how the information is handled operationally. Rather than relying on a predetermined landing weight, the crew typically has their actual/updated ZFW and an estimated fuel-on-arrival value, which can be used to determine the expected landing weight and corresponding approach speeds.
It would also make the enroute performance calculation more dynamic and better reflect what a pilot would actually see when updating performance information during a flight, particularly when fuel burn or payload differs from the original dispatch assumptions.
Just a suggestion for consideration — I think using ZFW + estimated arrival fuel would make the enroute landing-performance functionality feel more authentic to real-world airline/ACARS operations.