The easiest way to understand Aerlattice is to follow a request through the application. This walkthrough follows the planning workflow, from the first route to its acceptance and reservation.
Prepare the request
Start with the proposed route and the times and heights assigned to its waypoints. Add the aircraft’s limits, the mission window, priority and radio-channel needs.
Those details give the application something specific to check. They also give the reviewer a way to understand what the planner is trying to achieve and which parts of the request can change.
Run the checks and examine alternatives
Aerlattice checks the request against the other flights, restricted areas, weather and radio use represented in the exercise. Findings show where and when a conflict occurs.
Open the findings in the context of the route. If a change is needed, consider whether it involves the path, the departure time or the channel assignment. Required waypoints and locked times remain constraints when alternatives are generated.
Check the revised route and examine its findings. Acceptance runs a final check against the current project before reserving the corridor.
Record the decision
Accepting a flight runs fresh checks and, when they pass, records the decision and reserves its corridor. A conflicting route stays a draft for further review.
Accepted revisions stay fixed until an explicit replacement decision. Keep proposed replacements as drafts while they are being considered, so the accepted plan remains identifiable.
Explore it on the exercise timeline
Run an exercise or replay recorded observations to examine the plan over time. The application can show deviations, feed loss and projected collision alerts. Suggested replacement routes still go through review.
The local workspace keeps the plans, checks, decisions and recordings together. Reopening that record lets someone follow the sequence from request to decision.
