Operational workflows and troubleshooting

Published 7 October 2026, Updated 7 October 2026

22. Recommended operational workflows

22.1 Start-of-day maintenance control review

1. Refresh Resources.
2. Review missing-next-due icons, grounded/warning states, wrench, AMO, expected return, last position, and next schedule.
3. Open Status board and work each exception section from the top.
4. Review the first ten next-due resources.
5. Check open tasks by registration.
6. Review Risk Heatmap or Dashboard only after immediate release blockers are understood.
7. Record ownership and due dates for follow-up.

[SCREENSHOT: maintenance-start-of-day | Capture: Resources and Status board prepared for the start-of-day review, with key exceptions highlighted.]

22.2 New pilot snag to maintenance visit

1. Confirm the pilot snag and supporting file in Squawk Manager.
2. Review whether it grounds the resource or has an approved postponement.
3. Confirm aircraft position and next schedule.
4. Send the resource to maintenance, selecting AMO and expected return when known.
5. Add a task for coordination if ownership or a due date is needed.
6. Add a temporary Scheduler block if a specific time window must be protected.
7. Verify Resources and Status board.

[SCREENSHOT: maintenance-snag-to-visit | Capture: Pilot snag, Send to maintenance dialog, resulting resource row, and linked task.]

22.3 Maintenance completion and return to service review

1. Confirm approved maintenance documentation outside this page.
2. Enter correct closing date and explanation on each resolved squawk.
3. Renew any item that remains controlled; do not conceal it in a closed record.
4. Establish the next required TTSN item when applicable.
5. Update data-sheet values only when reconciled.
6. Remove obsolete temporary Scheduler blocks.
7. Return the resource from maintenance.
8. Refresh Status board and confirm no release blockers remain.
9. Check the live Scheduler and Flight Record status.
10. Close or update related tasks and add a History note when useful.

[SCREENSHOT: maintenance-return-to-service-check | Capture: Closed squawk, valid next due, cleared maintenance visit, clean Status board, and updated task.]

22.4 Weekly manager review

1. Review Dashboard availability and lost-activity context.
2. Review AMO turnaround and utilization with deliberate date ranges.
3. Review pilot-squawk tags and Risk Heatmap trends.
4. Review the AI report and its limitations when available.
5. Open underlying squawks for every high-priority finding.
6. Assign tasks for inspections, data corrections, or monitoring.
7. Review OpenAviation Needs sync and failed Transfer History entries.

[SCREENSHOT: maintenance-weekly-review | Capture: Dashboard, Risk Heatmap, AI priorities, OpenAviation history, and Task tab as a weekly review sequence.]

23. Common questions and troubleshooting

Situation	What to check
A resource is missing	Clear filters, reset selector filters, expand groups, enable Show inactives, and confirm restricted-view access.
The resource looks available but cannot ramp out	Check maintenance/AMO state, mandatory next due, grounded squawks, Scheduler unavailability, weekday/day-night restrictions, and Status board.
Send/return maintenance is disabled	Refresh and check the last position or in-flight state, current maintenance state, and your access.
A task disappeared	The resource shortcut filters to open tasks. Change the Closed/status filters or clear the registration filter.
Delete became inactive instead	The resource or AMO has history and is intentionally preserved.
Resource deletion is blocked	Existing schedules may need to be moved or deleted first.
A squawk is unexpectedly grounded	Check whether it has a valid approved date/TTSN limit and whether the earliest limit has expired.
A date-postponed squawk changed after the listed day	The date is inclusive; it expires after that calendar day.
A closed squawk still appears	Hide inactives/closed items, or keep them visible for historical review.
Cannot edit a pilot snag description	The original report is preserved. Use follow-up/closing text for clarification.
Pilot snag label does nothing	Select an eligible pilot snag row first.
Public/private upload did not appear	Confirm the rename prompt was completed, wait for upload, refresh the file list, and verify the correct registration/tab.
Scheduler block is absent	Refresh, navigate to the correct date, and confirm From/To.
Status board says No items found	That section currently has no exception; continue reviewing the remaining sections.
Heatmap shows a dash	No comparable tag result is available for that aircraft/period.
AI result conflicts with current knowledge	Check period, limitations, flight hours, original squawks, inspection findings, and current operational context.
OpenAviation says Needs sync	Double-click the row, inspect awaiting flights, review Daily records, then synchronize the narrowest appropriate range.
OpenAviation says Up to date but no flights occurred	This is expected: no eligible completed flight is waiting in the selected range.
OpenAviation says no eligible records	Check inclusive dates, completion, cancellation, and positive air time.
OpenAviation status did not change	Refresh, inspect Transfer History/details, and verify the transfer result before resubmitting.
A chart seems misleading	Confirm date range, units, hidden legend series, utilization, inactive-resource setting, and whether open visits are included.

[SCREENSHOT: maintenance-troubleshooting | Capture: Composite target showing Reset filters, Show inactives, Status board blocker, closed-squawk toggle, Heatmap dash, and OpenAviation Transfer History.]

24. Final maintenance-control checklist

Before treating a resource as operationally available:

1. Verify the registration and current aircraft position.
2. Confirm there is no open grounding condition.
3. Confirm every postponement has an approved, unexpired limit and adequate warning period.
4. Confirm mandatory next-due control is present and valid.
5. Confirm the aircraft is not still marked in maintenance or at an AMO.
6. Confirm no temporary Scheduler unavailability covers the intended operation.
7. Confirm day/night, weekday, restricted-view, and Scheduler display settings are appropriate.
8. Refresh Status board and resolve every applicable No release entry.
9. Confirm the official technical release and required records outside this page.
10. Update or close tasks and record any continuing follow-up.

[SCREENSHOT: maintenance-final-release-checklist | Capture: One resource with a valid next due, no grounding squawk, no maintenance/AMO state, no Scheduler block, clean Status board, and no overdue open task.]