Start with one missing departure

Write down its template, aircraft registration, route, direction and expected departure date and time in UTC. Investigating one specific flight is more useful than rebuilding the whole timetable.

1. Check whether the plan is published

Open Schedules and find the template. Saving blocks in the designer saves the plan; it does not by itself publish the operation. Check its publication state and Active from date. A draft with no start date will not operate.

If it is still a draft, open the assigned aircraft's schedule, run Validate, resolve the reported conflicts and save before publishing. Publication needs an aircraft assignment and flight blocks.

2. Check the operating date and weekday

  1. Compare the expected flight date with Active from and any Active to date.
  2. Check the weekday containing the block, including flights crossing midnight.
  3. Read STD in UTC. A local calendar date can differ from the UTC departure date.
  4. Check any effective start date shown for a later aircraft assignment.

New publication requires at least 14 days of lead time. Use the earliest date displayed by the portal. A future plan is not a same-day recovery action. Near the end of a template's date range, confirm the actual departure record instead of assuming the end date includes another full day of flying.

3. Verify the aircraft and route

Confirm the registration is assigned to the intended template and still belongs to the operating company. In Fleet, inspect actual location, grounding, maintenance and availability. Changing a home base does not reposition the aircraft.

If a route is missing from the designer, check that it is active, verified and not archived, and that the aircraft meets its restrictions. One route serves both directions, but each flight block must use the correct direction. Follow the route guide for route setup.

4. Check continuity and timing

Read the designer's conflict details. Each flight needs time to finish and turn around before the next departure, and its arrival airport must make sense for the next departure. Inspect the end of the week as well as adjacent blocks. A transfer prompt needs a real resolution; dismissing it does not move the aircraft.

Use Help and Guide Me in the designer to locate its controls. Fix the specific validation issue before saving again.

5. Find the actual flight record

Open Upcoming flights and the Rotation Board. Distinguish a missing departure record from a visible flight that is pending, delayed or otherwise not complete. Read any status or explanation attached to that record.

Upcoming records are prepared within a limited window; the entire future timetable does not have to appear immediately. If a departure is due and remains missing, record the template details and time of your check. Repeatedly publishing copies can make the investigation harder.

6. Correct the plan or report the operation

For a draft, correct the plan and validate it. For a published plan, use the supported revision or replacement workflow and review its effective dates; do not assume an edit changes already prepared flights immediately. For maintenance, wait for the recorded maintenance state to clear before treating the aircraft as ready.

If the flight still cannot be explained, send support the template ID, registration, route ID, expected UTC departure, actual status and a screenshot of the relevant record. Include what you checked and avoid sending account credentials. Open the support guide.