Division 24 establishes the planning and scheduling control system for the entire handbook. It connects the maintenance strategies of Divisions 01–23 with actual field execution — turning asset condition, risk and requirement into a resourced, coordinated, and tracked work window.
Philosophy: maintenance frequency and timing are controlled by the approved maintenance strategy and adjusted where justified by asset condition, risk, operational requirements, and maintenance history — not scheduled on a calendar alone.
needs maintenance?
does it need maintenance?
should it be performed?
should it be prepared & controlled?
Every maintenance activity in the handbook moves through the same nine-stage planning cycle before it reaches the field.
Planning is not calendar-only — it weighs asset, resource, and operational factors together before a work window is set.
A practical priority framework ranks activities by urgency and consequence. Actual priority definitions should follow the airport's approved system.
Immediate or urgent action required.
Action required within a controlled short-term window.
Planned maintenance required.
Can be incorporated into routine planned work.
Grouped by planning function — click any topic to expand its scope and key considerations.
Role: provides the high-level maintenance roadmap for the year and identifies major resource requirements.
Role: converts the annual plan into executable monthly activities.
Role: establishes the specific work expected during the coming week.
Role: confirms planned work can actually be executed safely and operationally.
Link: should be linked to the applicable preventive-maintenance SOP/checklist.
Escalation: critical failures should be escalated through the emergency-maintenance process where appropriate.
Goal: convert a predictive warning into an actionable maintenance activity before failure where practicable.
Record: the maintenance plan should record why the activity was initiated.
Note: emergency maintenance cannot always be scheduled in advance, but the organization maintains preparedness.
Outcome: critical assets receive appropriate planning priority.
Note: actual priority definitions should follow the airport's approved system.
Formula: Risk = Consequence × Likelihood. Higher-risk assets receive greater planning attention.
Note: age alone should not automatically determine replacement.
Note: repeated failures should trigger engineering review rather than simply repeated repair.
Basis: actual airport conditions and historical experience.
Requirement: every planned maintenance activity should have an appropriate work order or equivalent controlled instruction.
Confirm: required instruments are available and appropriately calibrated where applicable.
Timing: permit requirements should be established before the work window.
Coordination: LOTO planning should be coordinated with the applicable safety procedures.
Note: the exact coordination route should follow airport procedures.
Rule: do not plan only for the repair itself — testing, inspection, restoration, and contingency time are part of the window.
Final window: agreed through the airport's established operational coordination process.
Purpose: provides basic maintenance-plan performance visibility.
Rule: deferred maintenance is formally controlled and should not simply disappear from the schedule.
Rule: emergency activities are separately identified from normal planned work.
Trigger: a growing backlog should trigger management review.
Purpose: identifies resource constraints before they affect maintenance performance.
Objective: is the maintenance schedule realistically delivering the required maintenance at the required time — not merely measuring completion.
A practical close-out checklist spanning planning, resources, safety, operations, execution, and closure.
A practical master schedule connects every planned activity to its resources, authorization, and status.
| Field | Description |
|---|---|
| Work Order | Unique reference |
| Asset ID | Equipment identification |
| Location | Physical location |
| Maintenance Type | PM / CM / PdM / CBM / Emergency |
| Activity | Work description |
| Priority | Critical / High / Medium / Low |
| Due Date | Required completion |
| Planned Date | Scheduled date |
| Work Window | Planned operational window |
| Manpower | Required personnel |
| Spare Status | Available / Required |
| Test Equipment | Required equipment |
| Permit | Required authorization |
| LOTO | Yes / No |
| Status | Planned / In Progress / Completed / Deferred |
| Completion Date | Actual completion |
| Delay Reason | If applicable |
| Remarks | Additional information |
A simple monthly review can classify every activity into one of five statuses.
Completed within the planned window.
Not completed as originally planned but controlled and rescheduled.
Due date exceeded without acceptable closure.
Formally deferred with documented justification and risk control.
Unplanned work arising from failure or abnormal condition.
Backlog is not simply a list of unfinished jobs — each item carries its own risk profile and should be periodically reviewed and reduced accordingly.
These indicators exist to improve the planning system, not merely for reporting.
The recommended end-to-end Division 24 workflow, from asset register through to schedule update.
"AGL MAINTENANCE SHALL BE PLANNED AND SCHEDULED BASED ON ASSET CRITICALITY, CONDITION, RISK, MAINTENANCE REQUIREMENTS AND OPERATIONAL CONSTRAINTS, WITH THE NECESSARY PERSONNEL, SPARES, TOOLS, TEST EQUIPMENT, PERMITS AND WORK WINDOWS CONFIRMED BEFORE EXECUTION."
Quick answers about maintenance planning & scheduling, based on the topics in this division.
It is the planning and scheduling control system for the entire handbook. It connects the maintenance strategies of Divisions 01 to 23 with actual field execution, turning asset condition, risk and operational constraints into planned work.
Division 24 (Maintenance Planning & Scheduling) contains 35 topics in four groups: Group A Maintenance Planning (9 topics), Group B Asset-Based Planning (8 topics), Group C Work Planning (11 topics) and Group D Schedule Control (7 topics).
What needs maintenance, why it needs maintenance, when it should be performed, and how it should be prepared and controlled.
Every activity moves through nine stages before reaching the field: asset condition, maintenance requirement, priority, resources, work window, schedule, execution, completion and review.
No. Frequency and timing are controlled by the approved maintenance strategy and adjusted where justified by asset condition, risk, operational requirements and maintenance history. Planning weighs asset factors (criticality, condition, findings, failure history), resource factors (spares, manpower, test equipment) and operational factors (airside restrictions, aircraft operations, permits, LOTO and shutdowns) together.
Priority 1 Critical needs immediate or urgent action, Priority 2 High needs action within a controlled short-term window, Priority 3 Medium is planned maintenance, and Priority 4 Low can be folded into routine planned work. Actual priority definitions should follow the airport's approved system.
It connects every planned activity to its resources, authorization and status: work order, asset ID, location, maintenance type (PM, CM, PdM, CBM or Emergency), activity, priority, due and planned dates, work window, manpower, spare status, test equipment, permit, LOTO, status, completion date, delay reason and remarks.
A monthly review classifies every activity as Green (completed within the planned window), Amber (not completed as planned but controlled and rescheduled), Red (due date exceeded without acceptable closure), Deferred (formally deferred with documented justification and risk control) or Emergency (unplanned work from a failure or abnormal condition).
Backlog is not simply a list of unfinished jobs. Each item carries its own risk profile, so it is reviewed by age, priority, risk, asset criticality, reason for delay, required resources, target completion and responsible person, and reduced accordingly.
Maintenance planning and scheduling is more than assigning dates to a task list.
Build the technical knowledge to understand risk-based prioritization, resource allocation, outage coordination, and how a well-built schedule keeps the airfield compliant without disrupting operations.
Plan with intent. Schedule with discipline. Protect operations.
Please read before relying on any content on this page or on any record downloaded from it.