Changing a departure time is a small edit with consequences elsewhere in a flight plan. A useful interface helps the user follow those consequences without losing the route or the reason for the change.
In Aerlattice, that work takes place around the map. The flight list, route details and findings share the planning context with linked 2D and 3D views.
Keep the next step close to the route
The selected request shows its path through checking, conflict resolution, acceptance and monitoring. Findings identify the affected objects and time intervals, and the reviewer can preview a proposed route in the map before choosing it.
Alternatives are grouped by what they aim to improve, such as arrival time, distance or the amount of change. Their effects remain visible alongside the route, so someone can compare the options without reconstructing them from memory.
Make edits manageable
Direct waypoint editing and departure-time controls let the user explore a change in context. A candidate for an accepted flight stays separate while it is examined, preserving the original allocation through the final check.
The operator and control-centre views arrange the workflow around different tasks. The operator prepares a request, while the control centre reviews and accepts it. These are views within the local application.
Evaluate the experience
The next questions concern how people use these choices: where they lose context, which findings are difficult to interpret and how easily they recover after an edit. Representative user studies will help us decide which changes improve the work.
