About Knowledge Hub Troubleshooting SOP Library Components Contact Get in Touch
Home/ Troubleshooting Atlas/ Division 21 — Operational & Maintenance Problems
Safety-critical technical reference — read before use. Independent educational guidance for qualified AGL personnel. It is not an approved procedure or regulatory instruction and does not replace your aerodrome’s permit-to-work, isolation/LOTO and maintenance procedures or the manufacturer’s instructions. Series-circuit AGL equipment can carry lethal voltages. Read the full disclaimer ↓
Division 21 of 30

Operational & Maintenance Problems

Operational and maintenance fault diagnosis across the AGL system — from recurring lamp, LED, transformer, connector, and cable failure patterns through excessive maintenance burden, repeated circuit/earth-fault/CCR/sign faults, high energy consumption, unexpected shutdowns, performance degradation, false alarms, and seasonal, rain, heat, cold, flood, and dust-related failure patterns. Each topic follows the full engineering diagnostic record: symptom → observation → measurement → decision → fault location → root cause → verification → corrective action → preventive action.

20 / 20
Topics Published
01
of 1 Subsection Complete
11
Fields per Topic
01 · Operational & Maintenance Problems (20)

01 · Operational & Maintenance Problems

20 of 20 topics published
OPM-506 Frequent Lamp Failure

Symptom — A fixture, group, or circuit shows a lamp replacement frequency well above the expected service life, identified through maintenance records rather than a single failure event.

Equipment / System

Incandescent/halogen lamp population across a fixture, circuit, or zone, assessed collectively via maintenance and replacement history rather than as an individual bulb fault.

Possible Causes
HighSustained overvoltage at the CCR output driving lamps beyond their rated operating voltage, shortening filament life across the whole circuit
HighVibration from ground/aircraft traffic at that specific location accelerating filament fatigue
MedIncorrect lamp wattage/voltage rating stocked and used at replacement, mismatched to the fixture's isolation transformer
MedFrequent power cycling (on/off) at that location compared to others, accelerating thermal filament stress
LowA batch of lamps from a specific supplier/lot with a systemic quality defect
LowPoor fixture ventilation/heat dissipation at that specific location shortening lamp life
Required Tools
CCR output voltage/current trend logTrue-RMS multimeter (CAT III)Lamp replacement history/work order recordsSample lamps from suspect batch for bench comparison
Safety Precautions
  • LOTO the circuit before lamp replacement or fixture inspection.
  • Coordinate airside access through ATC/apron control before approaching fixtures on an active surface.
Diagnostic Procedure
  1. ObservationPull the lamp replacement history for the affected fixture/circuit/zone and compare the failure rate against the expected service life and against comparable circuits.
  2. MeasurementWith the circuit isolated, verify CCR output voltage/current against design at the affected circuit, and compare to a circuit with normal lamp life.
  3. MeasurementConfirm the lamp wattage/voltage rating in use matches the fixture/transformer specification.
  4. DecisionVoltage/current confirmed elevated → investigate CCR calibration or transformer tap setting. Rating or vibration/location factor identified → address at the fixture level.
  5. Fault LocationDetermine whether the elevated failure rate is circuit-wide (pointing to CCR output) or localised to specific fixtures (pointing to vibration, ventilation, or a batch defect).
  6. Root CauseConfirm the corrective action reduces the failure rate over the following several operating cycles rather than relying on a single replacement.
Test Points
CCR output voltage/current vs. design
Lamp rating in stock vs. fixture specification
Comparative failure rate across circuits
Failure rate trend after correction
Root Cause Verification

Track the lamp replacement rate at the affected location over the following several months to confirm it has returned to the expected baseline.

Corrective Action
  • Correct CCR output voltage/current if confirmed elevated.
  • Replace lamps with the correctly rated stock where a mismatch is found.
  • Address vibration or ventilation issues at chronically affected fixture locations.
  • Quarantine and stop using a confirmed defective lamp batch.
Preventive Action
  • Trend lamp replacement rates by circuit/zone to catch an emerging pattern before it becomes a chronic maintenance burden.
  • Verify CCR output calibration on a defined schedule.
  • Track lamp batch/lot numbers to enable early detection of a systemic quality issue.
Related References

SOP: SOP-OPM-01 (Recurring Failure Rate Trending Procedure)

Standards: FAA AC 150/5340-30, manufacturer lamp specification sheets

Diagram: Lamp Replacement History Log Template

Case Study: Division 01 — CCR Troubleshooting

Rev 0 — Initial issue
OPM-507 Frequent LED Failure

Symptom — A fixture, group, or circuit fitted with LED modules shows a module or driver failure rate well above the expected service life, identified through maintenance records.

Equipment / System

LED module and driver population across a fixture, circuit, or zone, assessed collectively via maintenance and replacement history.

Possible Causes
HighDriver overheating from inadequate heat sinking or ventilation at that fixture type/location, accelerating electronic component degradation
HighVoltage/current transients at the CCR output or a specific circuit segment stressing driver electronics beyond design tolerance
MedA batch of LED modules or drivers from a specific supplier/lot with a systemic quality defect
MedIncorrect driver current setting for the LED module installed, causing accelerated LED degradation
LowMoisture ingress at a specific location repeatedly damaging driver electronics
LowThermal cycling extremes at a particular location (e.g. high solar gain) accelerating solder joint fatigue in the driver
Required Tools
Thermal imaging cameraTrue-RMS multimeter (CAT III) with waveform/transient captureLED module/driver replacement history recordsSample modules from suspect batch for bench comparison
Safety Precautions
  • LOTO the circuit before module/driver replacement or inspection.
  • Coordinate airside access through ATC/apron control before approaching fixtures on an active surface.
Diagnostic Procedure
  1. ObservationPull the LED module/driver replacement history for the affected fixture/circuit/zone and compare the failure rate against expected service life and comparable circuits.
  2. MeasurementWith the circuit isolated, thermally image the driver during a live operating period to check for overheating relative to a known-good fixture.
  3. MeasurementCheck CCR output for voltage/current transients or instability on the affected circuit.
  4. DecisionThermal reading elevated → investigate heat sinking/ventilation at that fixture type/location. CCR output shows transients → route to Division 01 for source-side investigation.
  5. Fault LocationDetermine whether the elevated failure rate is circuit-wide (pointing to CCR/source) or localised (pointing to thermal or moisture factors at specific fixtures).
  6. Root CauseConfirm the corrective action reduces the failure rate over subsequent operating cycles.
Test Points
Driver thermal signature vs. known-good fixture
CCR output stability on the affected circuit
Comparative failure rate across circuits
Failure rate trend after correction
Root Cause Verification

Track the LED module/driver replacement rate at the affected location over the following several months to confirm it has returned to baseline.

Corrective Action
  • Improve heat sinking/ventilation at chronically affected fixture locations.
  • Investigate and correct CCR output instability if confirmed.
  • Quarantine and stop using a confirmed defective module/driver batch.
  • Correct driver current setting to match the installed LED module.
Preventive Action
  • Trend LED module/driver replacement rates by circuit/zone to catch an emerging pattern early.
  • Include thermal imaging of drivers in the periodic PM cycle for fixture types with a history of failures.
  • Track LED module/driver batch/lot numbers to enable early detection of a systemic quality issue.
Related References

SOP: SOP-OPM-01 (Recurring Failure Rate Trending Procedure)

Standards: FAA AC 150/5345-46, manufacturer LED module/driver specification sheets

Diagram: LED Module/Driver Replacement History Log Template

Case Study: Division 01 — CCR Troubleshooting

Rev 0 — Initial issue
OPM-508 Frequent Transformer Failure

Symptom — A specific circuit, zone, or fixture type shows an isolation transformer failure rate well above the expected service life, identified through maintenance records rather than a single failed unit.

Equipment / System

Isolation transformer population across a fixture, circuit, or zone, assessed collectively via maintenance and replacement history.

Possible Causes
HighSustained overvoltage or current transients at the CCR output stressing transformer insulation and windings across the circuit
HighChronic moisture exposure at that location's base cans repeatedly degrading transformer insulation
MedA batch of transformers from a specific supplier/lot with a systemic quality defect
MedTransformers under-rated for the actual fixture load at that location, running consistently overloaded
LowRepeated mechanical stress (e.g. from unsupported installation per Division 17) fatiguing internal connections over time
LowAmbient temperature extremes at a particular location accelerating insulation ageing
Required Tools
CCR output voltage/current trend log1000V insulation resistance tester (megger)Transformer replacement history recordsSample transformers from suspect batch for bench comparison
Safety Precautions
  • LOTO the circuit before transformer replacement or inspection.
  • Coordinate airside access through ATC/apron control before approaching base cans on an active surface.
Diagnostic Procedure
  1. ObservationPull the transformer replacement history for the affected fixture/circuit/zone and compare the failure rate against expected service life and comparable circuits.
  2. MeasurementWith the circuit isolated, verify CCR output voltage/current against design, and check insulation resistance trend for the affected circuit.
  3. MeasurementInspect base cans at the affected location for chronic moisture or mechanical stress consistent with Division 14/17 fault patterns.
  4. DecisionCCR output confirmed elevated → investigate source-side calibration. Moisture or mechanical stress identified → address at the base-can/installation level.
  5. Fault LocationDetermine whether the elevated failure rate is circuit-wide (source-side) or localised (installation/environmental).
  6. Root CauseConfirm the corrective action reduces the failure rate over subsequent operating cycles and re-check insulation resistance trend.
Test Points
CCR output voltage/current vs. design
Insulation resistance trend for the circuit
Base-can moisture/mechanical condition at affected locations
Failure rate trend after correction
Root Cause Verification

Track the transformer replacement rate at the affected location over the following several months and re-check insulation resistance trend to confirm improvement.

Corrective Action
  • Correct CCR output voltage/current if confirmed elevated.
  • Address chronic base-can moisture or mechanical stress at affected locations.
  • Quarantine and stop using a confirmed defective transformer batch.
  • Replace under-rated transformers with the correctly specified rating.
Preventive Action
  • Trend transformer replacement rates by circuit/zone to catch an emerging pattern early.
  • Verify CCR output calibration on a defined schedule.
  • Track transformer batch/lot numbers to enable early detection of a systemic quality issue.
Related References

SOP: SOP-OPM-01 (Recurring Failure Rate Trending Procedure)

Standards: FAA AC 150/5345-46

Diagram: Transformer Replacement History Log Template

Case Study: Division 08 — Taxiway Centreline / Guidance Lighting Troubleshooting (insulation faults)

Rev 0 — Initial issue
OPM-509 Frequent Connector Failure

Symptom — A specific circuit, zone, or fixture type shows an L-823 connector failure rate well above the expected service life, identified through maintenance records rather than a single connector event.

Equipment / System

L-823 connector population across a fixture, circuit, or zone, assessed collectively via maintenance and replacement history.

Possible Causes
HighChronic base-can flooding or drainage issues at that location repeatedly causing water/moisture-related connector failures
HighGround/aircraft traffic vibration at that specific location repeatedly loosening or damaging connectors
MedA batch of connectors from a specific supplier/lot with a systemic quality defect
MedConsistent installation-practice errors (sealing, support, torque) at that location per Division 17 findings
LowConnector type under-rated for the circuit's actual current at that location
LowRepeated mishandling during frequent maintenance access at a high-traffic-fault location
Required Tools
Connector replacement/failure history records1000V insulation resistance tester (megger)Base-can drainage inspection kitSample connectors from suspect batch for bench comparison
Safety Precautions
  • LOTO the circuit before connector replacement or inspection.
  • Coordinate airside access through ATC/apron control before approaching base cans on an active surface.
Diagnostic Procedure
  1. ObservationPull the connector replacement/failure history for the affected fixture/circuit/zone and characterise the pattern — same failure mode each time, or a mix.
  2. MeasurementWith the circuit isolated, inspect base-can drainage and mechanical condition at the affected location per Division 14 procedures.
  3. MeasurementIf a batch defect is suspected, bench-test sample connectors from the same lot against a known-good reference.
  4. DecisionPattern points to a location-specific drainage/mechanical condition → correct the underlying condition rather than continuing like-for-like swaps. Pattern points to a batch defect → proactively replace other connectors from that lot.
  5. Fault LocationDistinguish between a location-specific systemic cause and a component-batch-specific cause before deciding the scope of corrective action.
  6. Root CauseConfirm the corrective action addresses the systemic driver identified, and monitor the failure rate at that location afterward.
Test Points
Historical failure mode pattern from records
Base-can drainage/mechanical condition
Comparative bench test of suspect batch connectors
Failure rate trend after correction
Root Cause Verification

Place the affected location on a shortened monitoring interval for several cycles and confirm the failure pattern does not recur before returning to standard PM.

Corrective Action
  • Correct chronic base-can drainage or mechanical stress at the affected location.
  • Replace connectors with an upgraded or better-suited type if the standard part is inadequate for that location's conditions.
  • Quarantine and stop using a confirmed defective connector batch.
Preventive Action
  • Flag locations with two or more repeat connector failures for root-cause review rather than routine like-for-like replacement.
  • Track connector batch/lot numbers to enable early detection of systemic quality issues.
  • Feed recurring-failure locations into the design/engineering review process for a permanent fix.
Related References

SOP: SOP-CON-14 (Repeat Failure Root Cause Investigation Procedure), SOP-OPM-01 (Recurring Failure Rate Trending Procedure)

Standards: FAA AC 150/5345-26

Diagram: Connector Failure History Log Template

Case Study: Division 14 — L-823 / Connector Troubleshooting (repeated connector failure)

Rev 0 — Initial issue
OPM-510 Frequent Cable Failure

Symptom — A specific circuit segment or zone shows a cable fault (insulation breakdown, open, or short) rate well above the expected service life, identified through maintenance and fault-location records.

Equipment / System

Primary series cable population across a circuit segment or zone, assessed collectively via maintenance and fault history rather than a single cable event.

Possible Causes
HighChronic mechanical stress at that location — heavy traffic loading, repeated excavation nearby, or pavement movement — repeatedly damaging cable insulation
HighCable of that age/batch nearing end of service life across the whole segment
MedChronic moisture exposure at low-lying sections of the route repeatedly degrading insulation
MedInadequate burial depth or protection at that segment per Division 17 findings, leaving it exposed to repeated damage
LowA manufacturing batch defect in the cable insulation
LowFrequent third-party excavation activity in the area repeatedly nicking or stressing the cable
Required Tools
Cable fault/failure history records1000V/2500V insulation resistance tester (megger) with trend logTDR / fault locatorRoute/burial as-built drawing for the affected segment
Safety Precautions
  • LOTO the circuit before fault-locating or excavating.
  • Coordinate with other utility owners before excavating near the cable route.
Diagnostic Procedure
  1. ObservationPull the fault/failure history for the affected segment and characterise the pattern — clustered at one point, distributed along the run, or associated with specific events (excavation, weather).
  2. MeasurementWith the circuit isolated, megger the segment and use a TDR/fault locator to identify the specific fault points from this and prior events.
  3. MeasurementReview burial depth, protection, and drainage conditions along the segment per the as-built record.
  4. DecisionFaults clustered at a specific point with a mechanical/environmental cause → correct the local condition (protection, drainage, re-route). Faults distributed and age-related → plan proactive replacement of the segment.
  5. Fault LocationMap all historical fault points along the segment to identify whether they cluster or distribute.
  6. Root CauseConfirm the corrective action reduces the fault rate on that segment over subsequent seasons/cycles.
Test Points
Historical fault location pattern along the segment
Insulation resistance trend for the segment
Burial depth/protection condition vs. specification
Fault rate trend after correction
Root Cause Verification

Trend the segment's fault rate over the following operating seasons and re-megger periodically to confirm the corrective action has been effective.

Corrective Action
  • Add or repair cable protection at a clustered fault location.
  • Correct chronic drainage issues along the affected segment.
  • Plan proactive cable replacement for a segment showing distributed, age-related fault clustering.
  • Coordinate with utility owners to prevent repeated third-party excavation damage.
Preventive Action
  • Trend cable fault rates by segment to catch an emerging pattern before a hard failure occurs.
  • Prioritise ageing or previously-faulted segments for proactive replacement in capital planning.
  • Maintain accurate as-built burial and protection records to speed future fault investigation.
Related References

SOP: SOP-OPM-01 (Recurring Failure Rate Trending Procedure), SOP-TCL-11 (Guidance Circuit Fault Location Procedure)

Standards: IEC 60364, FAA AC 150/5340-30

Diagram: Segment Fault History Log Template

Case Study: Division 08 — Taxiway Centreline / Guidance Lighting Troubleshooting (cable insulation faults)

Rev 0 — Initial issue
OPM-511 Excessive Maintenance Requirement

Symptom — A specific fixture, circuit, or zone consistently consumes a disproportionate share of maintenance labour/work orders compared to the rest of the system, without any single dominant failure mode standing out.

Equipment / System

The maintenance workload profile for a specific fixture, circuit, or zone, assessed via aggregated work order records across all fault types rather than a single component.

Possible Causes
HighMultiple minor, individually-unremarkable faults (loose hardware, minor moisture, minor drift) recurring at the same location, none severe enough to trigger a dedicated root-cause investigation on its own
HighAn underlying environmental stressor at that location (traffic loading, drainage, exposure) affecting several component types simultaneously
MedOriginal design or installation at that location marginal in a way that manifests as generalised extra wear rather than one specific fault
MedThat location simply receiving disproportionate reporting/inspection attention rather than actually failing more, skewing the record
LowStaffing or procedural factors causing repeat visits for the same underlying issue rather than a single thorough repair
LowA recently changed operational pattern (e.g. new taxiway routing) increasing traffic loading at that location beyond original design assumptions
Required Tools
Aggregated work order/maintenance history report for the locationEnvironmental/traffic loading data for the location if availableDesign and installation records for the locationCross-division troubleshooting atlas reference for individual fault types found
Safety Precautions
  • LOTO the circuit before any on-site investigation.
  • Coordinate airside access through ATC/apron control for the investigation visit.
Diagnostic Procedure
  1. ObservationPull the full aggregated work order history for the location across all fault types and categorise each entry by division/fault type.
  2. MeasurementWith the circuit isolated where applicable, conduct a thorough on-site inspection covering mounting, connectors, transformer, cable, and earthing rather than only the most recently reported symptom.
  3. MeasurementCompare the location's traffic loading, drainage, and environmental exposure against comparable, lower-maintenance locations.
  4. DecisionA common environmental or design factor identified across multiple fault types → address that root driver rather than each symptom individually. No common factor found → continue standard component-level troubleshooting for each new fault as it arises, but flag the location for closer monitoring.
  5. Fault LocationIdentify whether the excess maintenance burden is genuinely component failures or partly a reporting/procedural artefact.
  6. Root CauseConfirm whether addressing the identified common factor reduces the overall work order rate for that location over subsequent months.
Test Points
Work order count and categorisation by fault type over a defined period
Traffic loading/environmental exposure vs. comparable locations
Design/installation record review findings
Work order rate trend after intervention
Root Cause Verification

Track the total work order rate for the location over the following several months and compare against the historical baseline and comparable locations to confirm improvement.

Corrective Action
  • Address the identified common environmental or design factor (traffic loading, drainage, marginal installation) rather than treating each fault individually.
  • Escalate for a design/engineering review if the location's conditions exceed original design assumptions.
  • Correct any procedural gap causing repeat visits for the same underlying issue.
Preventive Action
  • Review aggregated work order data by location on a regular interval to catch an emerging high-maintenance pattern early, not just individual fault trends.
  • Feed chronic high-maintenance locations into the capital renewal/design review process.
  • Ensure work orders are closed out with full root-cause documentation to avoid masking a systemic pattern behind many small tickets.
Related References

SOP: SOP-OPM-01 (Recurring Failure Rate Trending Procedure)

Standards: FAA AC 150/5340-30, internal reliability/RCA guidance

Diagram: Location Maintenance Workload Report Template

Case Study: Division 25 — Field Case Study Troubleshooting

Rev 0 — Initial issue
OPM-512 Repeated Circuit Trips

Symptom — A specific series circuit trips its CCR protection repeatedly over a period, with each individual trip investigated and seemingly resolved, yet the circuit continues to trip again within a short interval.

Equipment / System

CCR overcurrent/protection function and the series circuit it protects, assessed across a pattern of repeated trip events rather than a single trip.

Possible Causes
HighA marginal or intermittent fault on the circuit that clears itself enough to pass a post-trip test but reappears under specific operating conditions (thermal, vibration, moisture)
HighCCR protection settings are marginal for the circuit's normal inrush or operating characteristics, tripping on conditions that are not actually faults
MedMultiple independent minor faults on the circuit, each individually minor, cumulatively pushing the circuit to the trip threshold
MedA repair from a previous trip investigation addressed a symptom but not the actual root cause
LowCCR itself has a marginal or drifting protection relay/sensor giving false trips
LowAn external factor (e.g. a nearby lightning-prone area, or a specific weather pattern) coinciding with each trip event
Required Tools
CCR trip/event log with timestamps and trip type1000V/2500V insulation resistance tester (megger)Series circuit fault locator / TDRCCR protection settings and calibration record
Safety Precautions
  • LOTO the circuit before investigation or testing.
  • Treat a circuit with a repeated-trip history as higher priority for thorough investigation rather than another quick reset-and-monitor cycle.
Diagnostic Procedure
  1. ObservationPull the full trip history for the circuit, including timestamps, and look for a pattern correlated with time of day, weather, or operating condition.
  2. MeasurementWith the circuit isolated, megger the full circuit and compare against previous test values to check for a genuine, if marginal, insulation trend.
  3. MeasurementReview the CCR's protection settings and calibration against the circuit's normal operating characteristics.
  4. DecisionInsulation trend confirms a genuine marginal fault → proceed to full segment-by-segment fault location per Division 08/14 procedures. No insulation trend found and settings are marginal → review and adjust CCR protection settings.
  5. Fault LocationUse the trip-history pattern (time correlation, weather correlation) to help narrow which segment or condition to focus fault-location effort on.
  6. Root CauseConfirm the corrective action results in no further trips over an extended monitoring period covering the conditions previously associated with trips.
Test Points
Trip event timestamps and correlation with operating conditions
Full-circuit insulation resistance vs. historical trend
CCR protection settings vs. circuit characteristics
Trip-free interval after correction
Root Cause Verification

Monitor the circuit's trip log over an extended period, ideally covering the range of conditions (weather, time of day) previously associated with trips, before closing out as resolved.

Corrective Action
  • Complete full segment-by-segment fault location and repair for a confirmed marginal insulation fault.
  • Adjust CCR protection settings if found to be marginal for the circuit's normal characteristics.
  • Recalibrate or replace a CCR protection relay/sensor found to be drifting.
Preventive Action
  • Treat any second trip on the same circuit within a defined interval as a repeated-trip investigation trigger rather than a routine reset.
  • Trend insulation resistance for chronically tripping circuits rather than relying on a single pass/fail test after each event.
  • Review CCR protection settings periodically against actual circuit operating characteristics.
Related References

SOP: SOP-CCR-05 (Repeated Trip Investigation Procedure)

Standards: FAA AC 150/5340-30, IEC 60364

Diagram: Circuit Trip Event Log Template

Case Study: Division 01 — CCR Troubleshooting

Rev 0 — Initial issue
OPM-513 Repeated Earth Fault

Symptom — A circuit's earth-fault/ground-fault protection trips repeatedly over a period, with insulation resistance appearing to recover between events, yet the fault recurs.

Equipment / System

Circuit earth-fault/ground-fault protection function at the CCR and the insulation system of the circuit it protects, assessed across a pattern of repeated events.

Possible Causes
HighMoisture intrusion at a specific point that dries out between rain events, temporarily restoring insulation resistance until the next wet cycle
HighA cable or connector insulation defect that only manifests as a leakage path under specific thermal or mechanical conditions
MedCumulative ageing across the circuit reducing overall insulation margin, so the circuit trips under any additional minor stress
MedEarth-fault protection threshold set marginally, tripping on borderline-acceptable readings rather than a genuine developing fault
LowA shared earthing/bonding issue elsewhere in the vault affecting the reference used for the earth-fault measurement
LowSeasonal water-table changes affecting insulation resistance at specific points along the route
Required Tools
CCR earth-fault trend log with timestamps1000V/2500V insulation resistance tester (megger)Moisture detection meterWeather/rainfall correlation data for the site
Safety Precautions
  • LOTO the circuit before investigation or testing.
  • Treat a circuit with a repeated earth-fault history as a developing hazard warranting thorough investigation rather than repeated resets.
Diagnostic Procedure
  1. ObservationPull the earth-fault trip history with timestamps and correlate against weather/rainfall data to check for a moisture-related pattern.
  2. MeasurementWith the circuit isolated, megger the full circuit segment-by-segment, ideally during or shortly after a period similar to when trips have occurred, to catch the fault in its active state.
  3. MeasurementInspect base cans and connectors along the circuit for moisture at points identified as lowest-reading in the segment test.
  4. DecisionSegment testing isolates a specific low-reading point correlated with the trip pattern → proceed to targeted repair at that point. No clear segment isolation despite testing → consider the earth-fault protection threshold itself as marginal and review CCR settings.
  5. Fault LocationUse weather/timing correlation to decide when to conduct segment testing, since a dried-out fault may not show up in a test performed long after the last trip.
  6. Root CauseConfirm the corrective action results in no further earth-fault trips through at least one full wet-weather cycle before closing out.
Test Points
Earth-fault trip timestamps correlated with weather
Segment insulation resistance tested during/after a relevant weather event
Moisture presence at the lowest-reading point
Trip-free interval through a subsequent wet-weather cycle
Root Cause Verification

Monitor the circuit's earth-fault trend through at least one full wet-weather cycle after correction before closing out as resolved.

Corrective Action
  • Repair or reseal the identified moisture entry point.
  • Replace the cable segment or connector confirmed as the source of the intermittent leakage path.
  • Review and adjust CCR earth-fault protection threshold if found to be marginal rather than reflecting a genuine fault.
Preventive Action
  • Test insulation resistance during or shortly after wet weather for circuits with a history of earth-fault trips, rather than only during dry conditions.
  • Trend earth-fault readings over time rather than treating each trip as an isolated event.
  • Prioritise circuits with a repeated earth-fault pattern for proactive moisture-point sealing during PM.
Related References

SOP: SOP-CON-05 (Water Ingress Inspection and Remediation Procedure), SOP-CCR-05 (Repeated Trip Investigation Procedure)

Standards: IEC 60364, FAA AC 150/5340-30

Diagram: Circuit Earth-Fault Trend Log Template

Case Study: Division 08 — Taxiway Centreline / Guidance Lighting Troubleshooting (insulation faults)

Rev 0 — Initial issue
OPM-514 Repeated CCR Fault

Symptom — A specific Constant Current Regulator unit experiences repeated internal faults (output instability, protection nuisance trips, control card errors) over a period, despite individual repairs, distinct from faults isolated to the circuit it feeds.

Equipment / System

CCR unit internals — control card, output stage, protection relays, and cooling — assessed across a pattern of repeated fault events rather than the circuit-side faults it protects.

Possible Causes
HighA marginal or ageing internal component (control card, output SCR/transistor stage) causing intermittent faults that each individual repair only partially addresses
HighInadequate cooling/ventilation for the CCR's operating environment causing repeated thermal-stress-related faults
MedInput power quality issues (voltage sags, harmonics) at that specific vault stressing the CCR repeatedly
MedA previous repair used an incorrect or non-genuine replacement part, itself prone to failure
LowFirmware/software issue on a digital CCR causing recurring control faults not resolved by a hardware-focused repair
LowThe CCR is simply approaching end of service life with generalised increasing fault frequency across multiple subsystems
Required Tools
CCR fault/event log with timestamps and fault codesThermal imaging camera for CCR cabinetInput power quality loggerManufacturer CCR service/repair history for the unit
Safety Precautions
  • LOTO and de-energise the CCR from both input and output sides before internal investigation.
  • Follow manufacturer safety procedures for capacitor discharge and internal component access.
Diagnostic Procedure
  1. ObservationPull the full fault/event log for the CCR, including fault codes, and look for a pattern (same subsystem repeatedly, or a spread across different subsystems).
  2. MeasurementWith the unit isolated, thermally image the cabinet during a subsequent live period to check for a chronic hot spot.
  3. MeasurementCheck input power quality at the vault for sags, surges, or harmonics that could be stressing the CCR repeatedly.
  4. DecisionPattern points to one subsystem repeatedly → replace that subsystem/card rather than repairing again. Pattern is generalised across multiple subsystems → consider the unit approaching end of service life and evaluate replacement.
  5. Fault LocationConfirm whether the repeated fault is genuinely internal to the CCR or is a symptom of an external input power quality issue.
  6. Root CauseConfirm the corrective action results in a fault-free interval consistent with normal CCR reliability expectations before closing out.
Test Points
Fault code pattern across the event log
Thermal signature of the CCR cabinet under load
Input power quality at the vault
Fault-free interval after correction
Root Cause Verification

Monitor the CCR's fault log over an extended period after correction and confirm no further recurrence of the same fault pattern before closing out.

Corrective Action
  • Replace the specific subsystem/card responsible for a repeatedly recurring fault.
  • Improve cooling/ventilation for the CCR's operating environment.
  • Address input power quality issues at the vault if identified as the driver.
  • Evaluate full CCR replacement if the unit shows generalised end-of-life fault frequency.
Preventive Action
  • Track CCR fault codes and frequency by unit to identify an emerging repeated-fault pattern early.
  • Use only manufacturer-approved genuine replacement parts for CCR repairs.
  • Include input power quality monitoring in vaults with a history of CCR faults.
Related References

SOP: SOP-CCR-05 (Repeated Trip Investigation Procedure), SOP-CCR-06 (CCR Internal Fault Diagnosis Procedure)

Standards: Manufacturer CCR service manual, FAA AC 150/5345-10

Diagram: CCR Fault/Event Log Template

Case Study: Division 01 — CCR Troubleshooting

Rev 0 — Initial issue
OPM-515 Repeated Sign Failure

Symptom — A specific lighted airfield sign experiences repeated failures (dark, dim, wrong colour, or flickering) over a period, despite individual repairs, indicating a systemic rather than isolated cause at that sign location.

Equipment / System

Lighted airfield guidance sign and its internal LED modules, driver, and connections, assessed across a pattern of repeated fault events at a specific location.

Possible Causes
HighChronic moisture ingress into the sign housing at that location, repeatedly damaging internal electronics
HighRepeated impact or vibration exposure at that location (e.g. proximity to a high-traffic taxiway junction) stressing internal connections
MedA batch of LED modules or drivers from a specific supplier/lot with a systemic quality defect installed in that sign
MedInadequate ventilation/heat dissipation in that sign's housing design or installation, accelerating electronic degradation
LowPower supply instability specific to the circuit feeding that sign
LowA previous repair addressed the symptom without correcting an underlying housing seal or mounting issue
Required Tools
Sign fault/failure history recordsMoisture detection meterThermal imaging cameraTrue-RMS multimeter (CAT III)
Safety Precautions
  • LOTO the circuit before internal sign inspection or repair.
  • Coordinate airside access and any required closure through ATC before working on or near an active surface.
Diagnostic Procedure
  1. ObservationPull the full fault/failure history for the sign and characterise the pattern — same failure mode each time, or a mix of different fault types.
  2. MeasurementWith the circuit isolated, inspect the sign housing seal, drainage, and mounting for chronic moisture or mechanical stress.
  3. MeasurementThermally image the internal driver/LED modules during a live period to check for chronic overheating.
  4. DecisionPattern points to a housing seal or mounting condition → correct the underlying condition rather than repeating like-for-like module swaps. Pattern points to a batch defect → proactively replace other sign modules from that lot.
  5. Fault LocationDistinguish between a location-specific systemic cause (moisture, vibration, heat) and a component-batch cause before deciding the scope of corrective action.
  6. Root CauseConfirm the corrective action addresses the systemic driver identified and monitor the sign's fault rate afterward.
Test Points
Historical fault pattern from records
Housing seal/drainage condition
Internal thermal signature under load
Fault rate trend after correction
Root Cause Verification

Place the affected sign on a shortened monitoring interval for several cycles and confirm the failure pattern does not recur before returning to standard PM.

Corrective Action
  • Correct the sign housing seal or mounting condition causing chronic moisture or vibration exposure.
  • Improve ventilation/heat dissipation in the sign housing where inadequate.
  • Quarantine and stop using a confirmed defective module/driver batch.
  • Address power supply instability on the feeding circuit if identified.
Preventive Action
  • Flag signs with two or more repeat failures for root-cause review rather than routine like-for-like module replacement.
  • Include sign housing seal and mounting condition in the periodic PM checklist.
  • Track sign module/driver batch/lot numbers to enable early detection of systemic quality issues.
Related References

SOP: SOP-OPM-01 (Recurring Failure Rate Trending Procedure), SOP-INST-13 (Sign Installation Verification Procedure)

Standards: ICAO Annex 14 Vol I, FAA AC 150/5340-18

Diagram: Sign Failure History Log Template

Case Study: Division 17 — Installation & Commissioning Faults (incorrect sign installation)

Rev 0 — Initial issue
OPM-516 High Energy Consumption

Symptom — A circuit, zone, or the overall AGL system shows energy consumption significantly higher than the expected baseline for its configuration and operating schedule, identified through utility billing or CCR/energy monitoring records.

Equipment / System

Overall AGL system or a specific circuit/zone's energy consumption profile, assessed against its expected baseline given configuration, intensity step usage, and operating schedule.

Possible Causes
HighOne or more circuits left running at a higher intensity step than operationally required for extended periods
HighCCR output voltage/current running higher than design due to a calibration drift, increasing consumption across the whole circuit without a corresponding operational need
MedLamp/fixture population shifted toward less efficient technology (e.g. incandescent) in an area intended to have been converted to LED, without the energy model being updated
MedCircuits scheduled to run during periods when they are not operationally required (e.g. inconsistent with actual traffic patterns)
LowPower factor degradation across the system increasing apparent power draw without a corresponding increase in useful light output
LowMetering or billing discrepancy rather than an actual consumption increase
Required Tools
CCR/energy monitoring system historical dataUtility billing records for comparisonPower quality/power factor meterCircuit intensity-step operating schedule and logs
Safety Precautions
  • LOTO the circuit before any on-site electrical investigation.
  • Coordinate airside access through ATC/apron control for the investigation visit.
Diagnostic Procedure
  1. ObservationCompare current energy consumption against the historical baseline and against an expected model based on configuration and schedule, to quantify the excess.
  2. MeasurementWith circuits isolated as needed, verify CCR output voltage/current calibration against design for the affected circuits.
  3. MeasurementReview intensity-step operating logs against actual operational requirement (e.g. traffic volume, visibility conditions) to check for unnecessary high-intensity operation.
  4. DecisionConsumption traced to CCR calibration drift → recalibrate. Consumption traced to unnecessary intensity-step operation or scheduling → review and adjust the operating schedule/step selection.
  5. Fault LocationIsolate whether the excess consumption is system-wide, zone-specific, or circuit-specific before targeting corrective action.
  6. Root CauseConfirm the corrective action reduces consumption toward the expected baseline over the following billing/monitoring period.
Test Points
Energy consumption vs. expected baseline
CCR output voltage/current calibration
Intensity-step operating logs vs. operational requirement
Power factor across the system
Root Cause Verification

Track energy consumption over the following billing/monitoring period after correction and confirm it has returned toward the expected baseline.

Corrective Action
  • Recalibrate CCR output voltage/current to design.
  • Adjust intensity-step operating schedule to match actual operational requirement.
  • Complete or update an LED conversion where the energy model assumed a conversion that did not occur.
  • Correct a metering/billing discrepancy if identified as the cause.
Preventive Action
  • Trend energy consumption by circuit/zone against an expected baseline model on a regular interval.
  • Review intensity-step operating logs periodically against actual traffic/visibility conditions to identify unnecessary high-intensity operation.
  • Verify CCR calibration on a defined schedule as part of the energy management programme.
Related References

SOP: SOP-OPM-02 (Energy Consumption Trending and Investigation Procedure)

Standards: FAA AC 150/5340-30, applicable energy management standards

Diagram: Circuit Energy Consumption Baseline Model

Case Study: Division 01 — CCR Troubleshooting

Rev 0 — Initial issue
OPM-517 Unexpected Shutdown

Symptom — A circuit, zone, or the CCR itself shuts down without an operator command or an identifiable protection trip, reported via ALCMS status change, pilot/vehicle report, or a night inspection finding a section dark with no logged fault.

Equipment / System

CCR control system, ALCMS command/status interface, and the power supply feeding the CCR, assessed for an unexplained shutdown event.

Possible Causes
HighAn ALCMS command was issued (intentionally or in error) that was not adequately logged or communicated to the operations team investigating the shutdown
HighA brief upstream power interruption or sag caused the CCR to shut down and it did not automatically restart, without logging a distinct fault code
MedA control system software/firmware fault caused the CCR to shut down without triggering a standard protection trip log entry
MedA protection trip did occur but was not correctly logged due to a data-logging fault, making it appear as an unexplained shutdown
LowA manual local shutdown was performed by a technician on-site without properly logging or communicating it
LowA cyber/network issue on the ALCMS communication link caused a false or unintended shutdown command
Required Tools
ALCMS command and status logCCR internal event logUpstream power quality/interruption logManufacturer CCR control system documentation
Safety Precautions
  • LOTO the circuit before any internal investigation.
  • Treat the circuit as potentially still live at some point in its control chain until isolation is fully confirmed, given the shutdown cause is not yet understood.
Diagnostic Procedure
  1. ObservationCross-reference the ALCMS command log, the CCR's internal event log, and the upstream power quality log for the exact time of the shutdown.
  2. MeasurementWith the circuit isolated, review the CCR's internal fault/event log in detail for any entry that did not surface as an obvious ALCMS alarm.
  3. MeasurementCheck with on-site staff and shift logs for any manual local action around the time of the shutdown.
  4. DecisionAn ALCMS command, power interruption, or manual action is confirmed as the cause → close out with the confirmed explanation and address any logging/communication gap. No cause can be confirmed → treat as an unexplained control system fault and escalate for deeper investigation.
  5. Fault LocationDetermine whether the shutdown originated at the ALCMS command level, the CCR control system, or the upstream power supply.
  6. Root CauseConfirm the circuit restarts and operates normally, and that the logging/communication gap (if found) is corrected so a future event is not similarly unexplained.
Test Points
ALCMS command log at time of shutdown
CCR internal event log detail
Upstream power quality log at time of shutdown
Circuit operation after restart
Root Cause Verification

After restart, monitor the circuit over subsequent operating cycles and confirm the logging/communication gap identified has been corrected so any future event would be traceable.

Corrective Action
  • Correct the logging or communication gap identified between ALCMS, the CCR, and on-site staff.
  • Address an upstream power interruption source if identified as the cause.
  • Escalate to the CCR manufacturer for firmware/software investigation if no other cause can be confirmed.
  • Reinforce local shutdown logging/communication procedures if a manual action was the cause.
Preventive Action
  • Ensure all manual local shutdowns are logged and communicated per procedure, without exception.
  • Verify ALCMS-to-CCR command and status logging integrity on a defined schedule.
  • Include upstream power quality monitoring at vaults with a history of unexplained shutdowns.
Related References

SOP: SOP-CCR-07 (Unexplained Shutdown Investigation Procedure)

Standards: FAA AC 150/5340-30, ALCMS/CCR manufacturer documentation

Diagram: CCR/ALCMS Event Log Cross-Reference Template

Case Study: Division 01 — CCR Troubleshooting

Rev 0 — Initial issue
OPM-518 Performance Degradation

Symptom — A fixture, circuit, or the overall system shows a gradual decline in measured performance — light output, colour consistency, or response time — over an extended period, without a discrete failure event triggering the observation.

Equipment / System

Photometric and functional performance of a fixture, circuit, or system, assessed via trend comparison against baseline commissioning or previous periodic measurements.

Possible Causes
HighCumulative lens/optic contamination or wear across the affected fixtures reducing output gradually rather than through a single dirty-lens event
HighGradual LED lumen depreciation consistent with normal end-of-life ageing across a fixture population installed around the same time
MedGradual CCR output drift reducing circuit current slightly below design over time
MedCumulative insulation ageing across a circuit segment beginning to affect performance before reaching a hard-fault threshold
LowEnvironmental change (new nearby structure, vegetation growth) gradually affecting visibility/photometric readings rather than a genuine fixture-side decline
LowMeasurement equipment or method drift making a real, stable performance appear to be declining
Required Tools
Photometric field measurement equipmentHistorical photometric/performance trend recordsCCR output trend logLens/optic cleaning and inspection kit
Safety Precautions
  • LOTO the circuit before any on-site measurement requiring fixture access.
  • Coordinate airside access through ATC/apron control for measurement work.
Diagnostic Procedure
  1. ObservationCompare the current photometric/performance measurement against the baseline commissioning value and the trend of previous periodic measurements.
  2. MeasurementWith the circuit isolated where needed, verify CCR output current against design to rule out a source-side drift as the cause.
  3. MeasurementInspect lens/optic condition and confirm measurement equipment calibration to rule out a measurement artefact.
  4. DecisionDecline traced to CCR output drift → recalibrate the CCR. Decline traced to lens contamination or LED ageing → clean or plan proactive replacement accordingly.
  5. Fault LocationDetermine whether the degradation is system-wide (source-side), zone-specific (environmental), or fixture-specific (ageing/contamination).
  6. Root CauseConfirm the corrective action restores performance toward the baseline or, for genuine end-of-life ageing, confirm the decline rate is consistent with expected lumen depreciation and plan replacement accordingly.
Test Points
Photometric measurement vs. baseline and trend
CCR output current vs. design
Lens/optic condition
Measurement equipment calibration status
Root Cause Verification

Re-measure photometric/performance values after correction and compare against the baseline to confirm improvement, or document the confirmed ageing trend for replacement planning.

Corrective Action
  • Clean or replace contaminated/worn lenses and optics.
  • Recalibrate CCR output if drift is confirmed as the cause.
  • Plan proactive replacement of fixtures showing confirmed end-of-life LED lumen depreciation.
  • Correct environmental factors affecting readings where identified as the cause.
Preventive Action
  • Conduct periodic photometric trending, not just pass/fail testing at commissioning, to catch gradual decline early.
  • Verify measurement equipment calibration before each trending campaign.
  • Plan proactive fixture replacement based on expected lumen-depreciation curves rather than waiting for a hard failure.
Related References

SOP: SOP-OPM-03 (Performance Trending Procedure)

Standards: ICAO Annex 14 Vol I (photometric requirements), FAA AC 150/5340-30

Diagram: Fixture/Circuit Performance Trend Log Template

Case Study: Division 26 — Photometric & Intensity Compliance

Rev 0 — Initial issue
OPM-519 False Alarms

Symptom — An ALCMS or CCR alarm indicates a fault condition that, upon investigation, is not confirmed — the circuit or fixture is found operating normally with no measurable fault present, and this pattern recurs.

Equipment / System

ALCMS/CCR monitoring and alarm-generation system, assessed for alarm accuracy against confirmed field conditions across a pattern of investigated alarms.

Possible Causes
HighA monitoring sensor or status input (current sensor, lamp-out detection circuit) drifting or marginal, triggering alarms on normal operating variation
HighAlarm threshold set too tight for the normal variation in that circuit's operating characteristics
MedA communication or data-logging fault between the field sensor and the ALCMS causing a false status report
MedSoftware/firmware issue in the monitoring system generating spurious alarms
LowEnvironmental interference (electrical noise, temperature) affecting a specific sensor's readings
LowA genuine intermittent fault that clears before the investigating technician arrives, making it appear falsely alarmed when it is in fact a real but transient issue
Required Tools
ALCMS/CCR alarm log with timestamps and alarm typeField verification equipment matched to the alarm type (multimeter, photometric meter, etc.)Sensor calibration recordsCommunication/data-logging diagnostic tools
Safety Precautions
  • LOTO the circuit before any field verification requiring direct access.
  • Do not dismiss a repeated alarm as false without field verification each time — confirm the absence of a fault rather than assuming it based on pattern alone.
Diagnostic Procedure
  1. ObservationPull the alarm log for the pattern of alerts and note the specific sensor/parameter each alarm relates to.
  2. MeasurementWith the circuit isolated, field-verify the actual condition using appropriate test equipment matched to what the alarm reported (e.g. current, lamp status, insulation).
  3. MeasurementCheck the relevant sensor's calibration and the communication path between the sensor and the ALCMS.
  4. DecisionField condition confirmed normal and sensor/threshold identified as the cause → recalibrate the sensor or adjust the alarm threshold. Field condition intermittently shows a real but transient fault → treat as a genuine intermittent fault per the relevant division rather than a false alarm.
  5. Fault LocationIsolate whether the false alarm originates at the sensor, the communication path, or the ALCMS software/threshold configuration.
  6. Root CauseConfirm the corrected sensor/threshold no longer generates alarms under normal operating variation over a subsequent monitoring period.
Test Points
Field-verified condition vs. alarm report
Sensor calibration status
Communication path integrity between sensor and ALCMS
Alarm frequency after correction
Root Cause Verification

Monitor the alarm log for that circuit/sensor over a subsequent period after correction and confirm the false-alarm pattern has stopped, or that any remaining alarms correspond to genuine, verified conditions.

Corrective Action
  • Recalibrate the drifting or marginal sensor.
  • Adjust the alarm threshold to reflect normal operating variation for that circuit.
  • Correct the communication/data-logging fault between the sensor and the ALCMS.
  • Escalate to the ALCMS manufacturer for a software/firmware fix if the cause is confirmed as a system issue.
Preventive Action
  • Periodically verify sensor calibration for monitoring points with a history of alarm activity.
  • Review and tune alarm thresholds against real operating variation rather than a generic default setting.
  • Require field verification and documented outcome for every alarm, to build an accurate false-alarm-rate record rather than relying on technician assumption.
Related References

SOP: SOP-OPM-04 (Alarm Verification and False-Alarm Investigation Procedure)

Standards: FAA AC 150/5340-30, ALCMS manufacturer documentation

Diagram: ALCMS Alarm Verification Log Template

Case Study: Division 01 — CCR Troubleshooting

Rev 0 — Initial issue
OPM-520 Seasonal Fault Pattern

Symptom — Fault rates across the system or a specific zone show a clear correlation with season — elevated in a particular time of year — identified through longer-term maintenance trend analysis rather than any single event.

Equipment / System

System-wide or zone-specific fault trend, assessed across multiple seasons/years to identify a recurring seasonal correlation rather than a single weather event.

Possible Causes
HighSeasonal moisture/water-table changes affecting insulation resistance across affected circuits
HighSeasonal temperature extremes (heat or cold) affecting component performance consistent with the pattern
MedSeasonal operational changes (e.g. increased traffic during a peak season) increasing mechanical stress on fixtures and connectors
MedSeasonal maintenance activity itself (e.g. a specific PM campaign timed annually) coinciding with and partly explaining the fault-detection pattern
LowSeasonal wildlife or vegetation activity affecting specific components (e.g. nesting near base cans)
LowA seasonal power-quality pattern from the utility supply correlating with the fault trend
Required Tools
Multi-year fault trend records by month/seasonWeather/climate data for the site over the same periodCCR output and insulation trend logs across seasonsTraffic/operational schedule data by season
Safety Precautions
  • LOTO the circuit before any on-site investigation.
  • Coordinate airside access through ATC/apron control for investigation visits during the affected season.
Diagnostic Procedure
  1. ObservationPlot the fault trend by month/season across multiple years to confirm a genuine recurring pattern rather than a single anomalous period.
  2. MeasurementWith circuits isolated as needed, correlate the fault trend against weather/climate data, traffic schedules, and internal PM campaign timing for the same period.
  3. MeasurementWhere the pattern points to a specific mechanism (moisture, heat, cold, traffic), conduct targeted testing consistent with that mechanism during the next occurrence of that season.
  4. DecisionA specific environmental or operational driver is confirmed → target preventive action ahead of the next occurrence of that season. No clear driver identified beyond the PM campaign timing itself → adjust the PM/reporting schedule assumption rather than treating it as a genuine seasonal fault pattern.
  5. Fault LocationIdentify whether the seasonal pattern is system-wide or concentrated in specific zones/circuit types.
  6. Root CauseConfirm whether targeted preventive action ahead of the next occurrence of that season measurably reduces the fault spike compared to previous years.
Test Points
Multi-year fault trend by month/season
Correlation with weather/climate data
Correlation with traffic/operational schedule
Fault rate during the next occurrence of the season, post-intervention
Root Cause Verification

Track the fault rate during the next occurrence of the identified season after implementing targeted preventive action, and compare against the historical seasonal spike to confirm improvement.

Corrective Action
  • Schedule targeted preventive maintenance (e.g. drainage checks, connector re-sealing) ahead of the identified seasonal onset.
  • Adjust CCR or protection settings if a seasonal power-quality or thermal pattern is confirmed.
  • Correct the underlying mechanism identified (moisture, heat, traffic loading) at affected locations.
Preventive Action
  • Maintain multi-year fault trend records by month/season to enable this kind of pattern analysis.
  • Schedule seasonal preventive maintenance campaigns ahead of a confirmed historical fault spike rather than on a purely calendar-fixed basis.
  • Correlate fault trends with weather/climate data as a standard part of periodic reliability review.
Related References

SOP: SOP-OPM-01 (Recurring Failure Rate Trending Procedure)

Standards: FAA AC 150/5340-30, internal reliability/RCA guidance

Diagram: Multi-Year Seasonal Fault Trend Report Template

Case Study: Division 25 — Field Case Study Troubleshooting

Rev 0 — Initial issue
OPM-521 Rain-Related Failure Pattern

Symptom — Fault reports, particularly earth-faults, flicker, and connector-related issues, show a clear correlation with rainfall events, identified through cross-referencing fault timestamps against weather records.

Equipment / System

System-wide or zone-specific fault trend specifically correlated against rainfall events, distinct from a broader seasonal pattern.

Possible Causes
HighBase-can and connector seals degraded across multiple locations, each individually passing a dry-condition test but leaking under active rainfall/saturation
HighCable insulation defects that only present a measurable leakage path when saturated, drying out and appearing normal between rain events
MedSurface water pooling at specific low-lying locations during heavy rainfall, temporarily flooding base cans
MedLightning/electrical storm activity accompanying rain events causing transient-related faults distinct from water ingress itself
LowDrainage system capacity exceeded only during heavy rainfall intensity, not during lighter/more common rain events
LowIncreased ground/vehicle traffic disturbance during storm response operations coinciding with and contributing to the fault pattern
Required Tools
Fault/alarm log with timestamps cross-referenced against rainfall records1000V insulation resistance tester (megger)Moisture detection meterSite drainage capacity assessment
Safety Precautions
  • LOTO all affected circuits before any investigation.
  • Exercise extra caution working in or near water-affected base cans and equipment, treating them as live until isolation is confirmed.
Diagnostic Procedure
  1. ObservationCross-reference the fault/alarm log timestamps against rainfall intensity and duration records to confirm and characterise the correlation.
  2. MeasurementWith circuits isolated, test insulation resistance at affected locations during or immediately after a rainfall event to catch the fault in its active state, since it may recover once dry.
  3. MeasurementInspect base-can drainage, seals, and connector condition at the specific locations correlated with the fault pattern.
  4. MeasurementAssess drainage system capacity against the rainfall intensity that correlates with the fault spikes.
  5. DecisionTesting during/after rainfall isolates specific seal or drainage defects → proceed with targeted repair at those points. Pattern correlates with high-intensity events exceeding drainage design capacity → escalate for a drainage capacity review.
  6. Fault LocationUse the rainfall-correlated timing to schedule testing during or immediately after the next rain event for the best chance of capturing the fault in its active state.
  7. Root CauseConfirm the corrective action results in no further rain-correlated faults through at least one subsequent significant rainfall event.
Test Points
Fault timestamps correlated with rainfall intensity/duration
Insulation resistance tested during/after rainfall
Drainage and seal condition at correlated locations
Fault-free status through a subsequent rainfall event
Root Cause Verification

Monitor the fault log through the next significant rainfall event after correction and confirm the previously observed rain-correlated pattern does not recur.

Corrective Action
  • Repair or replace degraded base-can and connector seals at correlated locations.
  • Correct drainage deficiencies at locations where capacity is exceeded during heavy rainfall.
  • Replace cable segments confirmed to leak only under saturated conditions.
Preventive Action
  • Schedule proactive seal and drainage inspections ahead of the wet season based on the historical rain-correlated fault pattern.
  • Test insulation resistance during or shortly after rainfall for circuits with a history of rain-correlated faults, rather than only in dry conditions.
  • Review drainage system capacity against actual regional rainfall intensity data.
Related References

SOP: SOP-CON-05 (Water Ingress Inspection and Remediation Procedure), SOP-OPM-01 (Recurring Failure Rate Trending Procedure)

Standards: IEC 60364, FAA AC 150/5340-30

Diagram: Rainfall-Correlated Fault Log Template

Case Study: Division 17 — Installation & Commissioning Faults (poor drainage)

Rev 0 — Initial issue
OPM-522 Heat-Related Failure Pattern

Symptom — Fault reports, particularly LED/driver failures, transformer faults, and CCR nuisance trips, show a clear correlation with high-temperature periods, identified through cross-referencing fault timestamps against temperature records.

Equipment / System

System-wide or zone-specific fault trend specifically correlated against ambient/surface temperature extremes.

Possible Causes
HighDriver or transformer components operating at or near their thermal design limit under normal load, pushed over threshold by high ambient temperature
HighInadequate ventilation/heat dissipation in fixture or CCR cabinet design becoming a limiting factor only during peak heat
MedPavement/surface heat radiating into in-pavement fixtures during hot periods, compounding ambient air temperature effects
MedCCR protection thresholds not accounting for legitimate thermal derating, causing nuisance trips during hot weather
LowIncreased cooling/HVAC load in the equipment vault during hot periods affecting available power quality
LowSolar gain on above-ground equipment (signs, elevated fixtures) not accounted for in original thermal design
Required Tools
Fault/alarm log with timestamps cross-referenced against temperature recordsThermal imaging cameraCCR protection threshold and thermal derating specificationSite pavement/surface temperature data if available
Safety Precautions
  • LOTO the circuit before any thermal investigation requiring direct access.
  • Exercise caution working on hot pavement/fixture surfaces during peak heat periods, using appropriate PPE.
Diagnostic Procedure
  1. ObservationCross-reference the fault/alarm log timestamps against ambient and, where available, pavement surface temperature records to confirm and characterise the correlation.
  2. MeasurementWith circuits isolated as appropriate, thermally image affected components during a subsequent high-temperature period to identify which specific components run closest to their design limit.
  3. MeasurementReview CCR protection thresholds against the manufacturer's specified thermal derating curve.
  4. DecisionThermal imaging confirms specific components running near their limit → improve ventilation/heat dissipation or address load at those locations. Pattern traced to CCR protection thresholds not accounting for legitimate derating → review and adjust thresholds per manufacturer guidance.
  5. Fault LocationIdentify whether the heat-related pattern is concentrated in specific fixture/component types or is system-wide.
  6. Root CauseConfirm the corrective action results in no further heat-correlated faults through the next comparable high-temperature period.
Test Points
Fault timestamps correlated with temperature records
Thermal imaging results during a high-temperature period
CCR protection thresholds vs. manufacturer thermal derating guidance
Fault-free status through a subsequent high-temperature period
Root Cause Verification

Monitor the fault log through the next comparable high-temperature period after correction and confirm the previously observed heat-correlated pattern does not recur.

Corrective Action
  • Improve ventilation/heat dissipation at fixture or CCR locations confirmed to run near thermal limits.
  • Adjust CCR protection thresholds per manufacturer thermal derating guidance where nuisance trips were the issue.
  • Address solar gain on above-ground equipment where identified as a contributing factor.
Preventive Action
  • Schedule proactive thermal imaging surveys ahead of the hot season based on the historical heat-correlated fault pattern.
  • Design new installations with manufacturer-specified thermal derating and ventilation margins for the site's climate.
  • Review CCR protection thresholds against actual seasonal temperature extremes for the site.
Related References

SOP: SOP-OPM-01 (Recurring Failure Rate Trending Procedure)

Standards: Manufacturer thermal derating specifications, FAA AC 150/5340-30

Diagram: Temperature-Correlated Fault Log Template

Case Study: Division 14 — L-823 / Connector Troubleshooting (overheated contact)

Rev 0 — Initial issue
OPM-523 Cold-Weather Failure Pattern

Symptom — Fault reports, particularly cracked housings, connector seal failures, and reduced insulation resistance readings, show a clear correlation with cold-weather periods, identified through cross-referencing fault timestamps against temperature records.

Equipment / System

System-wide or zone-specific fault trend specifically correlated against sub-freezing or cold-extreme temperature periods.

Possible Causes
HighConnector or fixture housing materials becoming brittle at low temperature, cracking under normal handling or minor impact that would not cause damage in warmer conditions
HighFreeze-thaw cycling of moisture already present in base cans or conduits causing mechanical damage to seals and connectors
MedFrost heave affecting base-can position/level, gradually working connectors loose or misaligning fixtures during the cold season
MedDe-icing chemical exposure during cold-weather operations accelerating corrosion or seal degradation at affected locations
LowCCR or cabling insulation resistance genuinely reads lower at very low temperatures without indicating an actual developing fault, if the acceptance threshold does not account for temperature
LowSnow removal equipment contact causing physical damage to elevated fixtures or signs during winter operations
Required Tools
Fault/alarm log with timestamps cross-referenced against temperature recordsMoisture detection meter for freeze-thaw affected locationsFrost heave/settlement survey equipmentManufacturer cold-weather material/temperature rating specifications
Safety Precautions
  • LOTO the circuit before any cold-weather investigation requiring direct access.
  • Use appropriate cold-weather PPE and follow airside snow/ice safety procedures during investigation.
Diagnostic Procedure
  1. ObservationCross-reference the fault/alarm log timestamps against temperature records to confirm and characterise the cold-weather correlation.
  2. MeasurementWith circuits isolated, inspect affected connectors and housings for brittleness-related cracking, and check base-can level for frost heave.
  3. MeasurementTest insulation resistance and compare against the temperature at time of test, referencing manufacturer guidance on temperature-adjusted acceptance thresholds.
  4. DecisionDamage traced to material brittleness or freeze-thaw cycling → replace with cold-rated components at affected locations. Reduced insulation readings explained by temperature effect rather than a genuine fault → adjust acceptance criteria to a temperature-corrected threshold rather than treating as a fault.
  5. Fault LocationDetermine whether the cold-weather pattern reflects genuine component damage or a measurement/threshold interpretation issue.
  6. Root CauseConfirm the corrective action results in no further cold-correlated faults through the next comparable cold-weather period.
Test Points
Fault timestamps correlated with temperature records
Housing/connector material condition after cold exposure
Base-can level/frost heave survey
Insulation resistance vs. temperature-corrected threshold
Root Cause Verification

Monitor the fault log through the next comparable cold-weather period after correction and confirm the previously observed cold-correlated pattern does not recur.

Corrective Action
  • Replace affected connectors/housings with components rated for the site's actual cold-weather extremes.
  • Correct base-can level/position where frost heave has caused misalignment.
  • Address de-icing chemical exposure at affected locations where identified as a contributing factor.
  • Adopt a temperature-corrected insulation resistance acceptance threshold where appropriate.
Preventive Action
  • Specify cold-weather-rated materials for connectors and housings in climates with significant sub-freezing periods.
  • Schedule proactive frost heave/base-can level surveys ahead of and during the cold season.
  • Reference manufacturer temperature-adjusted thresholds when interpreting insulation resistance readings taken in cold conditions.
Related References

SOP: SOP-OPM-01 (Recurring Failure Rate Trending Procedure)

Standards: Manufacturer cold-weather material specifications, IEC 60364

Diagram: Cold-Weather Correlated Fault Log Template

Case Study: Division 14 — L-823 / Connector Troubleshooting (connector mechanical damage)

Rev 0 — Initial issue
OPM-524 Flood-Related Failure Pattern

Symptom — A cluster of faults — multiple base cans flooded, widespread earth-fault trips, or multiple circuits affected simultaneously — occurs following a flood or extreme rainfall event, distinct from the more gradual rain-related pattern and requiring a coordinated system-wide response.

Equipment / System

Multiple base cans, circuit segments, and potentially the equipment vault itself, assessed collectively following a confirmed flood event rather than an isolated rainfall correlation.

Possible Causes
HighFlood water directly inundating multiple base cans and pull boxes across a low-lying section of the field simultaneously
HighFlood water reaching the equipment vault/CCR room itself, posing a system-wide risk beyond individual circuits
MedDrainage and pumping systems overwhelmed beyond their design capacity by the flood event's volume/intensity
MedDebris carried by flood water causing additional mechanical damage to fixtures, base cans, or exposed cable
LowFlood water receding but leaving residual saturation that causes a secondary wave of faults over subsequent days as insulation continues to be affected
LowEmergency response activity itself (heavy equipment, temporary pumps) causing incidental additional damage during recovery
Required Tools
Wet/dry vacuum and pumping equipment for large-scale water removal1000V insulation resistance tester (megger) for post-flood circuit assessmentFlood extent survey/mappingEmergency response coordination with airport operations and civil/utility teams
Safety Precautions
  • Treat all affected circuits and equipment as energised hazards until isolation is confirmed at the CCR/vault level, given the scale of a flood event.
  • Coordinate with airport emergency response and follow flood-specific safety procedures, including electrical hazard assessment before any personnel enter affected areas.
Diagnostic Procedure
  1. ObservationMap the full extent of flood-affected base cans, circuits, and equipment before beginning individual fault investigation.
  2. MeasurementWith all affected circuits confirmed isolated, systematically megger each affected circuit segment before attempting to re-energise anything.
  3. MeasurementAssess whether flood water reached the equipment vault/CCR room and inspect that equipment separately and thoroughly before considering system-wide re-energisation.
  4. DecisionCircuit-level flooding only, vault unaffected → proceed with systematic circuit-by-circuit pump-out, drying, and insulation verification. Vault/CCR affected → treat as a higher-priority, system-wide event requiring full equipment assessment before any re-energisation.
  5. Fault LocationPrioritise fault investigation by criticality (e.g. runway circuits before secondary taxiway circuits) given the scale of a flood event.
  6. Root CauseConfirm every affected circuit passes insulation testing before re-energising, and monitor for the secondary fault wave that can follow as residual saturation continues to affect components over subsequent days.
Test Points
Extent of flood-affected base cans/circuits/vault
Insulation resistance for every affected circuit before re-energising
Vault/CCR equipment condition if affected
Secondary fault trend over the days following the event
Root Cause Verification

Systematically re-verify insulation resistance for every affected circuit before and after re-energising, and continue monitoring for a secondary fault wave over the following days as residual moisture continues to affect components.

Corrective Action
  • Pump out and dry all affected base cans, pull boxes, and vault areas.
  • Replace components (connectors, transformers, control cards) confirmed damaged by flood exposure rather than only drying and re-testing marginal readings.
  • Coordinate with civil/drainage teams on any temporary or permanent drainage improvement needed to prevent recurrence.
  • Prioritise restoration by circuit criticality.
Preventive Action
  • Maintain a flood emergency response procedure specific to the AGL system, including prioritisation criteria and safety steps.
  • Identify flood-prone base cans and vault areas in advance and consider protective measures (raised sills, backup pumping) proactively.
  • Review drainage design capacity against extreme rainfall/flood scenarios, not just routine rainfall.
Related References

SOP: SOP-OPM-05 (Flood Emergency Response and Recovery Procedure), SOP-CON-05 (Water Ingress Inspection and Remediation Procedure)

Standards: FAA AC 150/5340-30, local emergency management coordination requirements

Diagram: Flood-Affected Area Map and Recovery Log Template

Case Study: Division 17 — Installation & Commissioning Faults (base can flooding, poor drainage)

Rev 0 — Initial issue
OPM-525 Dust-Related Failure Pattern

Symptom — Fault reports, particularly reduced photometric output, connector contact issues, and cooling-related faults, show a clear correlation with dry/dusty conditions or specific dust-generating activity nearby, identified through trend analysis.

Equipment / System

Fixture lenses, connector contact surfaces, and CCR/equipment ventilation/cooling paths, assessed for dust accumulation correlated with a fault pattern.

Possible Causes
HighAirborne dust from nearby unpaved areas, construction activity, or seasonal dry conditions accumulating on fixture lenses, reducing measured photometric output
HighDust ingress into connector housings or base cans contributing to contact resistance issues over time
MedDust accumulation in CCR/equipment vault ventilation and cooling paths reducing cooling effectiveness and contributing to heat-related faults
MedNearby construction or ground-disturbance activity generating dust levels well above the site's normal background
LowDust combined with moisture forming a conductive or corrosive film on exposed contacts
LowSeasonal wind patterns concentrating dust exposure on specific zones of the field rather than uniformly across the site
Required Tools
Photometric field measurement equipmentLens/optic and connector cleaning kitThermal imaging camera for vault/cabinet cooling assessmentSite activity log for nearby construction/ground disturbance
Safety Precautions
  • LOTO the circuit before cleaning or inspecting fixtures/connectors.
  • Use appropriate PPE for dust exposure during cleaning and inspection work.
Diagnostic Procedure
  1. ObservationCorrelate the fault/photometric trend against dust-generating events (construction activity, dry-season wind patterns) using site activity logs.
  2. MeasurementWith circuits isolated, measure photometric output before and after lens cleaning at affected fixtures to quantify the dust contribution.
  3. MeasurementInspect connector contacts and CCR/vault cooling paths at affected locations for visible dust accumulation.
  4. DecisionPhotometric output recovers substantially after cleaning → confirm dust as the primary driver and schedule proactive cleaning. Output does not fully recover after cleaning → investigate an additional underlying cause (e.g. LED ageing) rather than attributing the full decline to dust.
  5. Fault LocationIdentify whether the dust-related pattern is site-wide (seasonal) or concentrated near a specific dust-generating activity.
  6. Root CauseConfirm the corrective action (cleaning, source control) results in sustained improvement rather than a temporary recovery that quickly re-declines.
Test Points
Photometric output before/after cleaning
Dust accumulation level on lenses, contacts, and cooling paths
Correlation with nearby dust-generating activity
Sustained output level after a subsequent period
Root Cause Verification

Re-measure photometric output and inspect for dust re-accumulation after a subsequent period to confirm whether a one-time cleaning was sufficient or a more frequent cleaning interval is needed.

Corrective Action
  • Clean affected fixture lenses, connector contacts, and CCR/vault cooling paths.
  • Coordinate with nearby construction/ground-disturbance activities to reduce dust generation where practical (e.g. dust suppression measures).
  • Increase cleaning frequency at chronically dust-affected zones.
Preventive Action
  • Schedule proactive lens/optic and cooling-path cleaning ahead of known dry-season or construction-related dust periods.
  • Track photometric output trends by zone to catch a dust-related decline before it approaches a compliance threshold.
  • Coordinate with any nearby construction activity to require dust suppression measures near the AGL system.
Related References

SOP: SOP-OPM-03 (Performance Trending Procedure)

Standards: ICAO Annex 14 Vol I (photometric requirements), FAA AC 150/5340-30

Diagram: Dust-Correlated Fault and Photometric Trend Log Template

Case Study: Division 26 — Photometric & Intensity Compliance

Rev 0 — Initial issue
No topics match your search. Try a different term.

Frequently Asked Questions

Quick answers about Division 21 — Operational & Maintenance Problems in the AGL Troubleshooting Atlas.

Q1What does Division 21 of the AGL Troubleshooting Atlas cover?

Division 21 is the Operational & Maintenance Problems reference. It publishes 20 diagnostic topics, OPM-506 to OPM-525, in a single subsection.

Q2What information does each topic include?

Every topic follows the same diagnostic record: the symptom, equipment/system, possible causes ranked by likelihood (high, medium or low), required tools, safety precautions, diagnostic procedure, test points, root cause verification, corrective action, preventive action and related references (SOPs, standards, diagrams and case studies).

Q3Which topics are in Division 21?

The 20 topics are OPM-506 to OPM-525: Frequent Lamp Failure; Frequent LED Failure; Frequent Transformer Failure; Frequent Connector Failure; Frequent Cable Failure; Excessive Maintenance Requirement; Repeated Circuit Trips; Repeated Earth Fault; Repeated CCR Fault; Repeated Sign Failure; High Energy Consumption; Unexpected Shutdown; Performance Degradation; False Alarms; Seasonal Fault Pattern; Rain-Related Failure Pattern; Heat-Related Failure Pattern; Cold-Weather Failure Pattern; Flood-Related Failure Pattern; Dust-Related Failure Pattern.

Q4How does a diagnostic procedure begin in Division 21?

Each procedure starts with observation before any intervention. For example, OPM-506 (Frequent Lamp Failure) begins: Pull the lamp replacement history for the affected fixture/circuit/zone and compare the failure rate against the expected service life and against comparable circuits.

Q5What safety precautions apply in Division 21?

Each topic lists its own precautions. For example, OPM-506 (Frequent Lamp Failure) starts with: LOTO the circuit before lamp replacement or fixture inspection.

Q6Which SOPs are referenced in Division 21?

Related references in the topics include SOP-OPM-01 (Recurring Failure Rate Trending Procedure), SOP-CON-14 (Repeat Failure Root Cause Investigation Procedure), SOP-TCL-11 (Guidance Circuit Fault Location Procedure), SOP-CCR-05 (Repeated Trip Investigation Procedure), SOP-CON-05 (Water Ingress Inspection and Remediation Procedure), SOP-CCR-06 (CCR Internal Fault Diagnosis Procedure), SOP-INST-13 (Sign Installation Verification Procedure) and SOP-OPM-02 (Energy Consumption Trending and Investigation Procedure), and 4 more.

Q7Which standards are referenced in Division 21?

Where a standard applies, it appears in the topic's Related References. Those cited in this division include FAA AC 150/5340-30, FAA AC 150/5345-46, FAA AC 150/5345-26, IEC 60364, FAA AC 150/5345-10, ICAO Annex 14 Vol I and FAA AC 150/5340-18.

Q8How can I find a specific topic in Division 21 quickly?

Use the search box at the top of the page to filter the 20 published topics by code, fault name or keyword; matching topics open automatically. Each diagnostic record can also be downloaded as a Word (.doc) file.

Take the Next Step with Precision AGL Academy

Don't Just Patch the Symptom. Understand the Operational Root Cause.

Many AGL faults aren't equipment failures at all — they're the downstream result of an operational or maintenance practice.

Build the technical knowledge to understand how maintenance scheduling gaps, procedural shortcuts, and operational stress show up as recurring 'equipment' faults, and how to fix the practice, not just the part.

Diagnose systematically. Understand the circuit. Build real AGL expertise.

Explore Precision AGL Academy Start AGL Training
Build Practical AGL Troubleshooting Capability
AGL Fundamentals CCR Systems Series Circuits Electrical Testing Fault Diagnosis Photometry Maintenance Commissioning

Talk to Precision AGL Academy

Call+91 98214 96412
Emailprecisionaglacademy@gmail.com

Follow the Academy

YouTube@precisionaglacademy LinkedInPrecision AGL Academy Instagram@PrecisionAGLAcademy Facebook@PrecisionAGLAcademy