Division 11 · INS · Inspection-to-Maintenance Bridge

Inspection-Driven Maintenance

The operational bridge between the AGL Inspection Handbook and the AGL Maintenance Handbook. Division 11 does not describe what maintenance is performed on an asset — it describes how an inspection finding becomes a maintenance action: identified, classified, prioritized, triggered, repaired, verified, closed, and trended.

Core principle: Inspect → Identify Defect → Classify → Prioritize → Trigger Maintenance → Repair → Verify → Close → Trend. No significant inspection finding should be lost between inspection and maintenance closure — this is what makes Division 11 a closed-loop control system rather than a records log.

30
Topics in Division
04
Topic Groups (A–D)
05
Defect Classifications
11
Step Closed-Loop Workflow

Closed-Loop Workflow

Every inspection finding in this division moves through the same eleven-step sequence, regardless of asset type, and is graded against the same four classification levels.

Inspect
Identify
Classify
Prioritize
Trigger
Work Order
Maintain
Test
Post-Inspect
Close
Trend
Critical Major Minor Observation Repeat Defect

Defect Priority Matrix

Classification determines response. Categories should ultimately be aligned with the airport's approved operational and safety criteria.

ClassificationTypical ResponseMaintenance Action
CriticalImmediate / urgentEmergency or priority corrective maintenance
MajorPrioritizedCorrective maintenance
MinorScheduledRoutine corrective maintenance
ObservationMonitorFollow-up inspection
Repeat defectEngineering reviewRoot-cause / condition assessment

Defect Description Standard

A finding is only as useful as the description behind it. The description must be specific enough to act as a maintenance trigger without repeating the inspection.

Weak vs. Usable Description

  • Weak: "Light problem."
  • Better: "Runway edge light at identified location has damaged lens and visible contamination."
  • The second version identifies asset, defect, and condition — giving the maintenance team a usable trigger.

Minimum Finding Record

  • Date, time, location
  • Asset, Asset ID, circuit
  • Inspection type
  • Defect description
  • Photograph / evidence where applicable
  • Inspector and initial condition

The 30 Topics

Grouped by stage of the inspection-to-maintenance chain — click any topic to expand.

A

Inspection Finding to Maintenance

8 topics
MNT-INS-001Defect Identification
Record
  • Date, time, location
  • Asset and Asset ID
  • Circuit
  • Inspection type
  • Defect description
  • Photograph / evidence where applicable
  • Inspector
  • Initial condition
Acceptance / Record

Standard: the description must be specific enough to serve as a usable maintenance trigger, not a generic statement.

MNT-INS-002Defect Classification
Classification Levels
  • Critical — immediate/urgent action, safety or electrical significance
  • Major — significant defect, prioritized maintenance
  • Minor — requires maintenance, not immediate
  • Observation — monitor / follow-up, no work order yet
Acceptance / Record

Use: the exact classification criteria established by the airport's approved inspection/maintenance system.

MNT-INS-003Critical-Defect Response
Response Sequence
  • Notify responsible personnel
  • Assess operational impact
  • Coordinate with airport/ATC functions where required
  • Establish safe electrical condition
  • Initiate emergency/corrective maintenance
  • Record the incident/finding
  • Verify restoration
  • Complete post-maintenance inspection
Acceptance / Record

Connects to: Division 05 — Emergency Maintenance.

MNT-INS-004Major-Defect Response
Workflow
  • Finding
  • Classification
  • Priority
  • Work order
  • Repair
  • Verification
  • Closure
Acceptance / Record

Planner responsibility: ensure major defects do not remain indefinitely on the observation list.

MNT-INS-005Minor-Defect Response
Sequence
  • Recorded
  • Assigned
  • Scheduled
  • Corrected within the applicable maintenance cycle
  • Verified
  • Closed
Acceptance / Record

Note: minor does not mean "no action required" — it means the required response is less urgent.

MNT-INS-006Observation Follow-Up
Typical Examples
  • Early corrosion
  • Minor deterioration
  • Slight contamination
  • Early mechanical wear
  • Developing moisture issue
Acceptance / Record

Every observation needs: owner, follow-up date, condition criterion, escalation trigger.

MNT-INS-007Maintenance-Trigger Definition
Example Triggers
  • Damaged lens → Fixture maintenance trigger
  • Corroded connector → Connector maintenance trigger
  • Water in transformer pit → Transformer/pit trigger
  • Abnormal CCR condition → CCR maintenance trigger
  • Cable deterioration → Cable maintenance trigger
Acceptance / Record

Definition: the point at which an inspection finding becomes a maintenance action.

MNT-INS-008Work-Order Generation
Recommended Fields
  • Work-order number
  • Asset ID / location / circuit
  • Defect and classification
  • Priority
  • Required action
  • Inspection reference
  • Assigned person/team
  • Target and completion date
  • Test requirement
  • Closure evidence
Acceptance / Record

Standard: a work order should contain enough information to act without repeating the inspection unnecessarily.

B

Inspection-Based Maintenance

10 topics
MNT-INS-009Runway Fixture Maintenance Trigger
Possible Triggers
  • Failed fixture
  • Damaged lens
  • Damaged prism
  • Contamination
  • Misalignment
  • Loose mounting
  • Damaged housing
  • Frangible-component damage
  • Secondary-lead/connector problem
Acceptance / Record

Trigger: runway inspection finding → fixture maintenance work order.

MNT-INS-010Taxiway Fixture Maintenance Trigger
Possible Triggers
  • Failed light
  • Misalignment
  • Damaged housing
  • Contamination
  • Loose mounting
  • Damaged optical component
  • Cable/connector defect
Acceptance / Record

Standard: the finding should identify the specific fixture and location.

MNT-INS-011PAPI Maintenance Trigger
Possible Triggers
  • Unit failure
  • Incorrect alignment
  • Optical contamination
  • Physical damage
  • Intensity/performance abnormality
  • Structural deterioration
Acceptance / Record

Action: convert the finding into the appropriate PAPI maintenance activity.

MNT-INS-012Sign Maintenance Trigger
Possible Triggers
  • Sign failure
  • LED-module failure
  • Uneven illumination
  • Physical damage
  • Damaged legend/panel
  • Driver fault
  • Mounting problem
  • Electrical fault
MNT-INS-013CCR Maintenance Trigger
Possible Triggers
  • Output abnormality
  • Alarm
  • Cooling problem
  • Fan failure
  • Display/control problem
  • Wiring abnormality
  • Protection-system issue
  • Communication/control failure
Acceptance / Record

Reference: Division 07 — CCR Maintenance procedure.

MNT-INS-014Transformer Maintenance Trigger
Possible Triggers
  • Physical damage
  • Connector defect
  • Cable-lead damage
  • Water ingress
  • Corrosion
  • Insulation concern
  • Mechanical displacement
  • Repeated circuit failure
Acceptance / Record

Reference: Division 08 — Isolation Transformer Maintenance.

MNT-INS-015Cable Maintenance Trigger
Possible Triggers
  • Cable damage
  • Exposed cable
  • Damaged route
  • Water ingress
  • Joint defect
  • Termination defect
  • Insulation deterioration
  • Abnormal test result
  • Repeated cable fault
Acceptance / Record

Reference: Division 09 — Cable Maintenance.

MNT-INS-016Connector Maintenance Trigger
Possible Triggers
  • Corrosion
  • Moisture
  • Damaged seal
  • Damaged contact
  • Loose connection
  • Locking failure
  • Overheating
  • Intermittent operation
  • Cable-lead damage
Acceptance / Record

Reference: Division 10 — Connector Maintenance.

MNT-INS-017Earthing Maintenance Trigger
Possible Triggers
  • Damaged earth connection
  • Corrosion
  • Loose connection
  • Broken conductor
  • Abnormal earth-resistance result
  • Missing bonding connection
MNT-INS-018ALCMS Maintenance Trigger
Possible Triggers
  • Communication failure
  • Incorrect status indication
  • Control-command failure
  • Monitoring failure
  • Alarm failure
  • Interface problem
  • Remote-control problem
Acceptance / Record

Preserve the distinction: AGL field-equipment fault vs. ALCMS monitoring/control fault.

C

Closure

6 topics
MNT-INS-019Maintenance Completion Verification
Verify
  • Correct component repaired/replaced
  • Defect addressed
  • Installation restored
  • Electrical condition satisfactory
  • Functional condition satisfactory
  • Work area restored
Acceptance / Record

Not enough: completion should never be based solely on "work completed."

MNT-INS-020Post-Maintenance Inspection
Evidence-Chain Example
  • Original finding — runway fixture misaligned
  • Maintenance — fixture alignment corrected
  • Post-maintenance inspection — alignment verified satisfactory
Acceptance / Record

Purpose: confirm the original defect has actually been corrected.

MNT-INS-021Defect Closure
Close Only When
  • Maintenance is complete
  • Required testing is complete
  • Functional condition is verified
  • Evidence is available
  • Responsible person approves closure
MNT-INS-022Corrective-Action Evidence
May Include
  • Before photograph
  • After photograph
  • Test result
  • Measurement
  • Replacement record
  • Maintenance report
  • Inspection checklist
  • Work-order completion record
Acceptance / Record

Standard: evidence requirements should be proportional to the significance of the defect.

MNT-INS-023Maintenance-History Update
Record Should Include
  • Defect and cause where known
  • Maintenance performed
  • Component replaced
  • Test result
  • Date and technician
  • Cost where tracked
  • Downtime where tracked
  • Closure date
MNT-INS-024Repeat-Defect Identification
Track Recurrence By
  • Asset
  • Location
  • Component
  • Circuit
  • Failure mode
Acceptance / Record

Standard: repeated defects should trigger engineering review rather than endless repetition of the same repair.

D

Condition Escalation

6 topics
MNT-INS-025Minor-to-Major Defect Escalation
A Minor Defect May Escalate When
  • Condition deteriorates
  • Defect remains uncorrected
  • Failure frequency increases
  • Operational significance increases
  • Environmental exposure worsens
  • Similar assets begin failing
MNT-INS-026Major-to-Critical Escalation
A Major Defect May Escalate When
  • The asset fails completely
  • Operational impact increases
  • Safety significance increases
  • Multiple related assets fail
  • Electrical safety is compromised
  • The defect affects a critical AGL function
Acceptance / Record

Standard: the escalation should be documented.

MNT-INS-027Temporary Repair Decision
A Temporary Repair Must Have
  • Identification
  • Responsible person
  • Time limit / review date
  • Permanent repair plan
  • Follow-up inspection
Acceptance / Record

Never: let a temporary repair disappear into the maintenance system as if it were a permanent closure.

MNT-INS-028Permanent Repair Decision
Consider
  • Root cause
  • Asset condition
  • Reliability
  • Repair history
  • Failure recurrence
  • Component availability
  • Operational importance
  • Life-cycle considerations
MNT-INS-029Asset Replacement Recommendation
Consider Replacement When
  • Repair is no longer reliable
  • Failure recurrence is high
  • Asset deterioration is advanced
  • Parts are unavailable
  • Condition is beyond practical repair
  • Life-cycle cost supports replacement
  • Reliability risk remains high after repair
Acceptance / Record

Standard: the replacement recommendation should be linked to the asset history.

MNT-INS-030Inspection Frequency Adjustment
Review Frequency When
  • Increased risk → consider increased inspection frequency
  • Repeated failures → consider targeted inspection
  • Stable condition → maintain or review per approved strategy
  • Significant deterioration → increase monitoring
  • Major modification/replacement → review inspection requirements
Acceptance / Record

Standard: frequency changes must be documented and approved through the applicable maintenance/asset-management process.

Repeat-Defect Escalation Ladder

Repeat repair is not necessarily successful maintenance. The objective is to eliminate the underlying failure mechanism, not to keep repeating the same fix.

1
First Occurrence

Normal corrective maintenance.

2
Second Occurrence

Monitor recurrence.

3
Repeated Occurrence

Engineering review.

4
Persistent Recurrence

Root-cause investigation.

5
Continued Recurrence

Condition / replacement assessment.

Frequently Asked Questions

Quick answers about inspection-driven maintenance, based on the topics in this division.

8 QUESTIONS
Q1What is Inspection-Driven Maintenance?

It is the operational bridge between the AGL Inspection Handbook and the AGL Maintenance Handbook. It does not describe what maintenance is done on an asset; it describes how an inspection finding becomes a maintenance action.

Q2What does Division 11 of the AGL Maintenance Handbook cover?

Division 11 (Inspection-Driven Maintenance) contains 30 topics in four groups: Group A Inspection Finding to Maintenance (8 topics), Group B Inspection-Based Maintenance (10 topics), Group C Closure (6 topics) and Group D Condition Escalation (6 topics).

Q3What is the core principle of Inspection-Driven Maintenance?

Inspect, identify the defect, classify, prioritize, trigger maintenance, repair, verify, close and trend. No significant inspection finding should be lost between inspection and maintenance closure.

Q4What is the closed-loop workflow?

Every finding moves through eleven steps: Inspect, Identify, Classify, Prioritize, Trigger, Work Order, Maintain, Test, Post-Inspect, Close and Trend.

Q5How does defect classification drive the maintenance response?

Critical findings get an immediate or urgent response through emergency or priority corrective maintenance; Major findings are prioritized for corrective maintenance; Minor findings are scheduled for routine corrective maintenance; Observations are monitored with follow-up inspection; and a repeat defect goes to engineering review and root-cause or condition assessment. Categories should ultimately align with the airport's approved operational and safety criteria.

Q6What makes a defect description usable as a maintenance trigger?

It must identify the asset, the defect and the condition. 'Light problem' is weak, whereas 'Runway edge light at identified location has damaged lens and visible contamination' gives the maintenance team a usable trigger without repeating the inspection.

Q7What must a minimum finding record include?

Date, time and location; asset, asset ID and circuit; inspection type; defect description; a photograph or other evidence where applicable; and the inspector and initial condition.

Q8What is the repeat-defect escalation ladder?

A first occurrence gets normal corrective maintenance, a second occurrence is monitored for recurrence, a repeated occurrence goes to engineering review, persistent recurrence to root-cause investigation, and continued recurrence to condition or replacement assessment. Repeat repair is not necessarily successful maintenance; the aim is to eliminate the underlying failure mechanism.

Go Further

Don't Just Log the Defect. Act on It.

Inspection-driven maintenance is more than recording what an inspection finds.

Build the technical knowledge to translate inspection findings into prioritized maintenance action, close the loop between defect and correction, and keep the asset register accurate.

Inspect with purpose. Act on findings. Close the loop.

Build Practical AGL Inspection-Driven Maintenance Capability
AGL Fundamentals Components Electrical Systems Preventive Maintenance Inspection Testing Photometry Troubleshooting Commissioning

Talk to Precision AGL Academy

Follow the Academy