A planned route and the last reported position of an aircraft answer different questions. One describes an intention, while the other describes an observation made at a particular time.
That distinction matters when information is delayed or stops arriving. The application needs to keep the plan visible without making an old observation appear current.
Keep the timing of information explicit
An observation can have a measurement time and a later time when it becomes available to the planning workspace. Replaying the earlier situation should respect what was known then, rather than using information that arrived afterwards.
This is part of the model in Aerlattice. Exercises and recordings let us examine how delayed information, route deviations and feed loss affect the picture available to a reviewer.
Give a proposed response its own review
A change in the available information may lead to a proposed replacement route. The reviewer needs to understand the basis of that proposal and compare it with the accepted plan.
Keeping the candidate separate allows the original allocation to stay in place while another route is checked. The response can then be considered through the same planning and approval process as another change to the flight.
