Inspection Schedule

Create inspection schedules per aircraft, set hour/cycle/calendar intervals, bulk-create via the onboarding wizard, mark inspections as done, and track due status with the configurable horizon selector.

Module: Flight Ops · 8 steps · camo_engineer admin

Browse Inspections
1 Open the Inspection Matrix

Navigate to Flight Ops → Inspections. The matrix at /flight-ops/inspections shows all scheduled inspections per aircraft with their type, interval, last-done values, next-due values, and due status (OK, Coming Due, Overdue).

Inspection matrix showing aircraft, type, intervals, due status with color coding
2 Filter & Sort

Use the Aircraft and Type filters to narrow results. Toggle Overdue Only to see just overdue inspections. Click Sort by Urgency to prioritise the most urgent items first.

The configurable horizon selector on the Due Report page lets you adjust the “coming due” thresholds for hours, cycles, and days.
Create an Inspection
3 Open the New Inspection Form

Click + New Inspection or navigate to /flight-ops/inspections/new.

4 Fill Inspection Details
FieldRequiredNotes
Aircraft *YesSelect the aircraft this inspection applies to.
ATA ChapterNoATA system chapter for categorisation.
Inspection Type *YesA-Check, C-Check, Engine Overhaul, Landing Gear, etc.
DescriptionNoWhat the inspection covers.
Interval — HoursNoFlight-hour interval between inspections.
Interval — CyclesNoFlight-cycle interval.
Interval — DaysNoCalendar-day interval.
Last Done — DateNoWhen the inspection was last performed.
Last Done — HoursNoAircraft hours at last performance.
Last Done — CyclesNoAircraft cycles at last performance.
Performed ByNoEngineer who performed the last inspection.
RemarksNoAdditional notes.
New inspection form with aircraft, type, intervals, last-done baseline, and submit
At least one interval (hours, cycles, or days) must be set. The system calculates the next-due values by adding the interval to the last-done baseline.
5 Submit

Click Create to save. The inspection appears in the matrix with its calculated due status.

Mark as Done
6 Record Completion

Click an inspection row to open the detail page. Fill in the Mark as Done form with:

FieldNotes
Done DateDate the inspection was completed.
Done HoursAircraft total hours at completion.
Done CyclesAircraft total cycles at completion.
Performed ByEngineer who performed the inspection.

Click Mark as Done. The system updates the last-done baseline and recalculates the next-due values automatically.

Inspection detail with mark-as-done form and history
After marking done, check the Task History page to see the full performance log for this inspection type.
Admin Actions
7 Edit Baseline & Deactivate

admin Admins can edit the last-done baseline fields on any inspection (to correct data entry errors) and deactivate inspections that are no longer applicable.

Deactivated inspections are hidden from the matrix by default but remain in the database for audit trail purposes.

Editing last-done fields changes the next-due calculation. Only admins can perform this action, and all changes are logged in the audit trail.
8 Bulk Create via Onboarding Wizard

For new aircraft, use the Onboarding Wizard to create all inspections at once. The wizard lets you copy from an existing aircraft or build from scratch, apply baseline values in bulk, and confirm before creating.