How to handle unscheduled maintenance (defects)
Not all maintenance can be planned. Use this workflow to manage unexpected defects, resolve issues quickly, and maintain safe operations.
Overview
Unscheduled maintenance typically follows this flow:
Defect identified → Logged → Work order created → Work performed → Defect resolved
This ensures issues are handled in a structured and traceable way.
Step 1: Identify the defect
A defect can be identified during:
-
Inspections
-
Daily operations
-
Pilot or technician reports
Any issue affecting the aircraft should be recorded immediately.
Step 2: Log the defect
Once identified, log the defect in MaintSpace:
1. Go to Maintenance Planning → Defects
2. Click “New Defect”
3. Select the aircraft
4. Describe the issue clearly
5. Set priority if needed
This ensures the issue is visible and tracked.
Step 3: Assess and prioritize
After logging the defect:
-
Determine severity and urgency
-
Decide if the aircraft can continue operating
-
Plan corrective action
Clear prioritization helps you respond appropriately.
Step 4: Create a work order
To resolve the defect:
-
Create a work order linked to the defect
-
Define the required actions
-
Assign responsibility
This ensures the defect is actively addressed.
Step 5: Prepare parts and tools
Before starting the repair:
-
Check Inventory for required parts
-
Reserve parts or order missing items
-
Ensure tools are available
Preparation reduces downtime.
Step 6: Perform the repair
Execute the work in Production:
-
Open the work order
-
Perform the required maintenance
-
Log time and actions
-
Record findings
All work should be documented as it happens.
Step 7: Close the defect
Once the issue is resolved:
-
Confirm the defect has been fixed
-
Update the defect status
-
Close the related work order
This ensures the issue is fully resolved and documented.
Tips
-
Log defects immediately when identified
-
Use clear and detailed descriptions
-
Link all defects to work orders
-
Review open defects regularly
Avoid these common mistakes
-
Delaying defect logging
-
Using unclear descriptions
-
Not linking defects to work orders
-
Leaving defects open after resolution