The first and most fundamental failure category in the AGL Failure Database — capturing failures directly associated with the actual airfield light fixtures and their internal, optical and mechanical components. Runway fixtures, taxiway fixtures and component-level failures, including LED driver failure, lamp burnout, moisture ingress, optical damage, seal failure, corrosion and loose internal connections.
Key principle — This division is not merely a list of failed lights. Every record should answer: what fixture failed → how did it fail → why did it fail → what evidence confirmed the failure → how was it repaired → how can recurrence be prevented? This mirrors the Failure Database's overall philosophy, which distinguishes historical failure intelligence from an active troubleshooting procedure.
Failure of a runway edge-light fixture resulting in loss or degradation of the required runway-edge visual guidance.
Failure of a threshold fixture causing loss of the required threshold-light output.
Threshold lighting failures can have high operational significance, so the failure record should capture the affected threshold location, number of failed fixtures and operational impact.
Record failures affecting runway-end fixtures.
Determine whether the failure is:
This prevents incorrectly classifying a fixture outage when the actual cause is elsewhere.
Record whether the failure is single fixture, repeated at the same location, repeated in the same circuit, repeated for the same manufacturer/model, or repeated for the same batch. This becomes valuable for the later Product & Component Reliability division.
Because TDZ lighting is particularly important to runway visual guidance, the record should capture:
Runway Guard Light (RGL) failures are also recognised separately within the Stop Bar & RGL failure division, including LED, driver, control, cable, connector, intensity, alignment and structural failures. For Division 01, the fixture-level component failure should be captured here.
Where the failure is caused by control system (Division 07), cable (Division 05), structural damage (Division 06) or operational incident (Division 10), the master failure record should cross-reference the relevant division.
Compare the failed fixture against adjacent taxiway fixtures to identify a common failure pattern, age-related failure, environmental pattern, installation issue or product/batch issue.
Because centreline fixtures may experience significant environmental and operational stresses, record fixture location, installation condition, mechanical condition, optical condition, circuit condition, maintenance history and previous failure history.
Failure of a clearance-bar lighting fixture or lighting element.
Failure of taxiway exit-lighting fixtures.
Verify the fixture itself before assigning the failure to the circuit or transformer.
Record whether failures occur repeatedly at the same RET location, same circuit, same fixture model, same installation type or same environmental exposure.
LED light source no longer produces the required output.
Photograph the LED module before replacement wherever practical.
Applicable primarily to conventional lamp-based fixtures.
This is one of the explicitly identified failure categories in the source framework.
Compare visual condition → optical condition → photometric result.
Photograph the damaged prism and record the fixture's photometric condition where applicable.
Therefore, seal failure should be recorded as both a failure mode and a possible root cause.
Determine type/location of corrosion, severity, environmental exposure, moisture involvement, age, previous maintenance, and material compatibility.
A loose connection should not automatically be classified as the final root cause. Investigate why it became loose: incorrect torque, vibration, thermal cycling, poor assembly, ageing, maintenance error, or component defect.
If the actual failure originates outside the fixture, cross-reference Cable & Connector Failures.
Photograph external damage, internal damage, mounting condition, and associated optical/electrical damage.
Frangible-coupling failure is also identified under the Mechanical & Structural failure categories.
Determine whether the failure resulted from vehicle impact, maintenance activity, installation error, mechanical loading, material degradation, or incorrect component.
Fixture misalignment is explicitly included in Division 01 and also appears within the Mechanical & Structural and Base-Can/Civil Interface failure categories.
Standard record structure, classification, RCA linkage, evidence layer and severity scheme that apply across all 24 Division 01 failure topics.
Every Division 01 failure should ideally be converted into a standard failure record with the following fields:
The database distinguishes failure mode from root cause — the same visible symptom (light OFF) can have entirely different causes:
Failure mode: LED driver failure
Root cause: Thermal overstress
Contributing factor: Inadequate heat dissipation
Corrective action: Driver replacement
Preventive action: Review thermal performance
Failure mode: Light outage
Actual root cause: Loose internal connection
Failure mode: LED failure
Root cause: Moisture ingress
Underlying cause: Seal failure
Every fixture failure should eventually become engineering intelligence:
Division 01 links every failure to the Root Cause Analysis Database. The most relevant RCA categories for fixture failures are:
Every failure receives a severity classification, plus operational-impact tagging:
Critical / Safety-Critical — immediate operational or safety risk
Major / Operationally Critical — significant availability impact
Moderate — reduced performance, not yet critical
Minor / Non-Critical — limited or no operational effect
Degradation / Intermittent / Latent — developing or hidden fault
Visual evidence
Technical evidence
The Troubleshooting Atlas answers “I have a fault now — how do I diagnose and fix it?” The Failure Database answers “this failure happened — what happened, why, what evidence proves it, what was done, and how do we stop it recurring?” Kept strictly separate, then linked end-to-end, the two form a genuine AGL Failure Intelligence Engine rather than a simple fault list.
Quick answers about lighting fixture failures in the AGL Failure Database.
Division 01 is the first and most fundamental failure category in the AGL Failure Database. It captures failures directly associated with the actual airfield light fixtures and their internal, optical and mechanical components, across 24 published topics (LTF-01 to LTF-24) covering runway fixtures, taxiway fixtures and component-level failures.
Runway fixtures include edge, threshold, end, centreline, touchdown zone and runway guard lights. Taxiway fixtures include edge and centreline lights, clearance bars, exit lights and rapid-exit taxiway lights.
LED module failure, lamp burnout, LED driver failure, optical lens damage, prism damage, seal failure, moisture ingress, corrosion, loose internal connections, secondary-lead failure, housing damage, frangible-component failure and fixture misalignment.
The database distinguishes the two because the same visible symptom, such as a light being off, can have entirely different causes. For example, an LED failure may be caused by moisture ingress, with seal failure as the underlying cause. Likewise, a light outage may trace back to a loose internal connection rather than the LED itself.
Each failure should ideally become a standard failure record. Fields include failure ID, fixture type and category, manufacturer, model, location, series-circuit ID, date and operating hours, failure mode, symptoms, test results, physical and environmental condition, RCA, corrective and preventive action, retest, evidence, severity, operational impact, repeat-failure flag, related SOP and lessons learned.
Each failure follows a loop from failure ID and initial inspection through electrical, optical and mechanical testing, evidence collection and failure-mode identification to root cause analysis. It continues with corrective action, post-repair test, preventive action, lessons learned and reliability trend.
A fixture outage may have its actual cause elsewhere. For runway-end lights, for example, the investigation should determine whether the failure is fixture-related, transformer-related, cable-related, circuit-related, environmental or maintenance-induced. For exit lights, the fixture itself should be verified before the failure is assigned to the circuit or transformer.
Seal failure is recorded as both a failure mode and a possible root cause. The typical chain runs from environmental exposure to seal failure, moisture ingress, corrosion, electrical failure and finally light outage.
Not automatically. A loose connection should not be classified as the final root cause; the investigation should ask why it became loose, for example incorrect torque, vibration, thermal cycling, poor assembly, ageing, maintenance error or a component defect.
Failures are classed as Critical / Safety-Critical, Major / Operationally Critical, Moderate, Minor / Non-Critical, or Degradation / Intermittent / Latent, with operational-impact tagging. The evidence layer combines visual evidence, such as photos of the fixture, LED module, driver, lens, seal and corrosion, with technical evidence, such as circuit current, insulation resistance, continuity, transformer and driver output, and photometric measurements.
The Troubleshooting Atlas answers how to diagnose and fix a fault happening now. The Failure Database answers what happened, why, what evidence proves it, what was done and how to stop it recurring. Kept separate but linked end to end, they form the AGL Failure Intelligence Engine.
Every AGL failure tells a story. From LED and driver failures to moisture ingress, optical damage, corrosion, loose connections and fixture misalignment, effective troubleshooting depends on understanding the complete system behind the symptom.
Take that knowledge further with Precision AGL Academy.
Learn how to connect:
Develop structured knowledge across AGL fundamentals, components, electrical systems, testing, photometry, troubleshooting, maintenance and commissioning.
Find the failure. Understand the cause. Build the engineering skill.
Please read before relying on any content on this page or on any record downloaded from it.