1. Establish the affected operation

Open Fleet and Schedules. Record the registration, actual aircraft airport, maintenance or grounding state, and the first affected departure in UTC. Inspect the Rotation Board and upcoming flights to see which later legs depend on it. Keep a missed flight separate from a timetable that has never become active.

2. Resolve the cause

For maintenance, check the authorised check and completion state. Counters can reset when work is authorised; that does not mean downtime has finished. For grounding, read the reason and resolve it before using the available reactivation action. Wet-lease renters cannot authorise maintenance or grounding as owners.

If the aircraft is at the wrong airport, review the supported transfer workflow and its quote. A home-base edit does not move it. Loaded CargoLife cargo can prevent an ordinary transfer.

3. Protect the next operation

Review the remaining rotation for airport continuity and turnaround. Do not assume a missing leg will replay automatically or that a newly published replacement starts immediately. Follow the schedule replacement guide for future changes, and notify affected pilots through your normal airline channel.

4. Verify recovery

Refresh the aircraft and departure records. Check that the actual status, location and next flight agree, then review the next completed flight. If the state remains inconsistent, report the aircraft ID, flight ID, UTC time and displayed reason using the support guide. Avoid repeated transfers or purchases while the original result is unclear.