One certified calculation serves the dispatch desk and the flight deck, revalidated against live conditions from the first flight plan to on blocks, with every signature and acknowledgement on the record.
Dispatch events sit above the line and flight deck events below it. The two filled markers are the points where responsibility is signed.
The release, the flight deck, the FMC and the retained record are served by one engine against one dataset. Every consumer reads the same result.
Every input capable of moving the answer is watched through to arrival. A release that is no longer current is flagged to both parties.
Inputs, results, amendments and acknowledgements are kept together, so a decision can be looked up rather than reassembled.
What the platform does at each point of the flight, and what the desk and the flight deck hold while it happens.
The operational flight plan triggers performance automatically. Airport, obstacle and meteorological data are resolved fresh at calculation time.
Numbers ready ahead of the crew
Usable runways and intersections at departure, destination and alternates, computed for the registration in its current configuration.
The same result will meet the crew
The dispatcher signs against a package assembled from source data, with every figure traceable to its origin.
Release waiting on the EFB
The desk sees the same calculation
The commander opens the EFB to the dispatcher’s calculation: the same engine, the same dataset, the same result.
Final weights arrive and the platform works out whether they actually move the answer. A release is reissued when the numbers require it.
Any revision surfaces on the EFB
Acceptance visible at the desk
Runway change, wind shift, a fresh surface report. Requested from the EFB or from the flight deck over datalink, and answered into the FMC.
Conditions move after pushback. Amendments are issued, delivered and acknowledged, and the record shows when each of those happened.
Amendments arrive on the EFB
In-flight calculations sync to the desk
The crew runs performance in the air as the picture changes: landing data for the destination, an en route alternate, a diversion. Each one comes from the engine the desk uses.
The desk holds the same result
Landing performance is computed on the conditions reported at the time of arrival and returned while the aircraft is on descent.
Every calculation is retained with the inputs that produced it, ready to answer why the flight departed on those figures.
Every release runs inside a closed loop from the moment it is issued until the aircraft is on blocks.
Every input that bounds the active release is under live subscription.
A change is tested against the release it would affect and classified by materiality.
Only a material change raises a new calculation, on the engine that produced the first.
The result reaches the desk, the flight deck and, where required, the aircraft.
Delivery and crew acknowledgement are tracked as separate, timestamped states.
The superseded version is preserved with its inputs and the reason it was replaced.
One calculation serving the release, the flight deck, the aircraft and the record.
Both parties always resolve to one current version, and what each of them has seen and accepted is written to the record.
Talk to our engineers about how dispatch and the flight deck hold one set of numbers in your operation, with your flight planning system, your load planning and your datalink.
