# Operations guide

## Daily workflow

1. Review active alerts, schedule conflicts, unassigned flights, aircraft availability, crew placeholders/assignments, airport limitations, and expiring aircraft documents.
2. Generate dated flights from approved templates and confirm UTC/local times, route, aircraft type, turnaround, and operating date.
3. Resolve server-detected overlaps, turnaround, maintenance, grounding, range, airport-hours, duplicate-flight, and document conflicts.
4. Complete dispatch planning, payload, fuel placeholders/plans, weather notes, alternate, attachments, and every mandatory checklist item.
5. Release dispatch only after aircraft and required confirmations are valid.
6. Record estimated and actual off-block, takeoff, landing, on-block, arrival, delay, diversion, or cancellation data.
7. Complete the flight only after actuals are correct. Completion moves the aircraft to the final arrival airport and records location history.

Flight statuses must follow the operational workflow. Completed, diverted, cancelled, departed, and in-flight records cannot be reset through schedule editing. Corrections must use an approved controlled process and retain audit/history records.

## Irregular operations

For delays, record category, reason, duration, responsible department, and notes. For cancellations, record category, reason, approval, and UTC timestamp. For diversion, record original/final destination, diversion airport, time, reason, and recovery action.

PowerAMS contains no GPS or ADS-B tracking. Aircraft location is manually selected or derived from completed flights. It is not a passenger booking, ticketing, check-in, or boarding system.