Runway Status Light (RWSL)
An advanced automated airfield safety system that provides real-time visual indications of runway status to pilots and vehicle operators. The RWSL system uses surveillance data to detect runway occupancy and activates Runway Entrance Lights, Runway Intersection Lights, and Take-Off Hold Lights — all red, in-pavement fixtures — to prevent runway incursions.
Image disclaimer: For identification and illustration only. It may show a product by another manufacturer and may not depict the exact item described; it is not a statement of any product’s quality, approval or performance. Third-party image and trademark rights belong to their owners. See full notice.
What Is It?
The Runway Status Light (RWSL) system is an automated safety system that provides direct, real-time visual indications of runway status to pilots and vehicle operators. The system uses surveillance data (radar, ADS-B, surface movement radar) to detect the presence and movement of aircraft and vehicles on the runway. When the system determines that a runway is occupied or that a conflict is imminent, it illuminates its own dedicated field elements — steady-burning red, in-pavement Runway Entrance Lights (REL) at taxiway/runway intersections, Runway Intersection Lights (RIL) at runway/runway crossings, and Take-Off Hold Lights (THL) on the runway centreline at the departure position — to alert pilots and vehicle operators to stop or remain clear. RWSL is a distinct system from Runway Guard Lights (RGL), the separate elevated amber flashing fixtures at holding positions that are switched independently, typically by ATC or local control logic rather than by RWSL's surveillance algorithms.
Purpose & Function
RWSL exists to add a fully automated layer of runway incursion protection that operates independently of, and in parallel with, air traffic control instructions and pilot situational awareness — both of which can be compromised by workload, communication breakdowns, or a surveillance gap that a controller cannot instantly perceive. By continuously fusing surveillance data on every aircraft and vehicle near the runway, the system can detect a developing conflict and illuminate the relevant lights (Runway Entrance, Runway Intersection, and Take-Off Hold Lights) automatically and immediately, without waiting for a human to notice the hazard and issue an instruction. Its purpose is best understood as a safety backstop: it does not replace ATC clearances or a pilot's own vigilance, but catches the specific failure mode where a conflict exists and neither party has yet recognized it in time to act.
Where Is It Used?
RWSL systems are installed at busy airports with high traffic volumes where runway incursion risk is elevated. They are typically used on:
- Precision approach runways (CAT II and III) where safety margins are critical
- Major international airports with complex taxiway layouts
- Intersecting runways where crossing traffic needs to be managed
- Runways with high traffic density where incursion risk is significant
- Airports implementing advanced surface movement control
Installation & Location
RWSL is a system installation rather than a single fixture: the field elements are in-pavement Runway Entrance Light, Runway Intersection Light, and Take-Off Hold Light fixtures (distinct from the elevated Runway Guard Lights described elsewhere in this library), so ground-side installation follows those fixtures' own base can, cabling, and frangibility requirements. What is specific to RWSL is the addition of an airport surface surveillance processing unit — typically housed in the airport's ATC facility or a dedicated equipment room — that ingests ASDE-X, ADS-B, or surface movement radar data, runs the occupancy and conflict-detection logic, and sends activation commands over a dedicated fibre or copper network to the field lighting controllers at each holding position and take-off position. Installation therefore centres on running this control network between the surveillance processing unit and each affected location, together with extensive integration testing to confirm the detection logic activates the correct lights within the required response time before the system is commissioned for live operational use.
How Does It Work?
The RWSL system operates through a sophisticated integration of surveillance data, processing algorithms, and visual output devices:
- Surveillance: Radar, ADS-B, and surface movement radar data continuously track all aircraft and vehicles on the airfield.
- Processing: The RWSL processing system analyzes this data to determine runway occupancy status and predict potential conflicts.
- Activation: When a runway is occupied, the system illuminates the affected Runway Entrance Lights and/or Runway Intersection Lights (steady red, in-pavement, at the intersection) and, for departing traffic, the Take-Off Hold Lights (steady red, on the runway centreline).
- Indication: When the runway is clear, the system extinguishes the lights, allowing safe entry or crossing.
System Architecture & Control Logic
RWSL is a fully automated, non-cooperative safety layer that sits on top of existing surface surveillance rather than depending on any controller action. Surveillance feeds — typically ASDE-X or ASSC surface radar/multilateration, supplemented by ADS-B where available — stream target position and velocity continuously into the RWSL processing system, which runs independent algorithm sets for each light function: Runway Entrance Light and Runway Intersection Light logic for the in-pavement fixtures at taxiway/runway and runway/runway intersections, and the Takeoff Hold Lights logic for the in-pavement lights at the departure end. Each algorithm evaluates occupancy and closing-speed predictions against the runway in question and issues an illuminate/extinguish command directly to the light control and monitoring subsystem, which drives the field circuits for that light group. Because the logic is deterministic and reaction time is sub-second, RWSL lights change state ahead of or in step with the conflict itself, with no controller-in-the-loop delay. The tower retains an ATC display showing overall system and light-group health, and the light control and monitoring subsystem reports back circuit status and individual light-group faults for maintenance dispatch, but tower personnel cannot directly command individual lights — the algorithms are the sole source of illumination commands.
Surveillance Sensors → RWSL Processing System (Algorithms) → Light Control & Monitoring → Fixture Group (with health feedback to ATC display)
Detection-to-Activation Logic
RWSL Processing System
Fuses surveillance data in real time to determine runway occupancy and predict potential conflicts — reaction time under 1 second, fully automated with no controller input.
Physical Construction
RWSL has no dedicated luminaire of its own — the field elements are in-pavement Runway Entrance Light, Runway Intersection Light, and Take-Off Hold Light fixtures, so their housings, optics, and base-can construction follow the standard in-pavement fixture designs described elsewhere in this library. What is specific to RWSL is the processing and control hardware: the surveillance processing system is typically built as a redundant server pair mounted in a 19-inch rack, housed in an environmentally controlled equipment room within the ATC facility or an airfield electrical building, with dual power feeds and UPS backup to keep detection logic running through a mains interruption. Field-side light control and monitoring units sit in weatherproof cabinets at or near each holding position and take-off position, sealed to at least IP65 to protect the switching electronics from the outdoor environment, and connected back to the processing racks over a dedicated fibre-optic or hardened copper network rather than the general airport LAN, keeping activation latency low and deterministic. Cabling between the processing system, field cabinets, and the tower ATC display follows the same duct and trench routes as other airfield electrical services, with fibre runs typically diverse-routed so a single cable cut cannot take down surveillance-to-light communication across the whole system.
Technical Parameters
| Parameter | Typical Value |
|---|---|
| System Type | Automated runway status indication system |
| Surveillance Inputs | Radar, ADS-B, surface movement radar, multilateration |
| Output Devices | Runway Entrance Lights (REL), Runway Intersection Lights (RIL), Take-Off Hold Lights (THL) — all steady red, in-pavement |
| Activation Criteria | Runway occupancy detected or conflict predicted |
| Deactivation Criteria | Runway clear and conflict resolved |
| Reaction Time | < 1 second from detection to activation |
| Power Supply | Dedicated mains supply with UPS backup |
| Communication | Networked (Ethernet, fiber optic, or wireless) |
| Integration | ALCMS, A-SMGCS, and other airfield systems |
Electrical Requirements
| Requirement | Typical Value |
|---|---|
| Processing Rack Supply | Dual redundant mains feeds, 100–240VAC, with UPS backup |
| Field Light Circuits | Series circuit, CCR fed, per underlying REL (L-852S) / THL / RIL (L-850T) fixture spec |
| Field Cabinet Supply | Dedicated low-voltage feed for switching and monitoring electronics |
| UPS Autonomy | Sized to ride through mains interruption without loss of detection logic |
| Network Medium | Dedicated fibre-optic or hardened copper, diverse-routed |
| Cable Type | L-824 series cable for light circuits; armoured fibre/copper for control links |
| Earthing/Grounding | Processing racks, field cabinets, and fixtures bonded to airfield earth grid |
| Fault Protection | Redundant server failover; CCR-level ground fault and open-circuit detection on light circuits |
| Surge Protection | Surge suppression at rack, cabinet, and field cable entry points |
Photometric Requirements
| Parameter | Typical Value |
|---|---|
| REL Intensity | ≥ 2,000 cd (red), steady-burning per L-852S in-pavement fixture spec |
| THL / RIL Intensity | ≥ 2,000 cd (red), steady-burning per L-850T in-pavement fixture spec |
| Vertical Beam Spread | Main beam 2°–15° above horizontal (peak ~3°–4°) for both device types |
| Horizontal Beam Spread | ± 5° to ± 7.5° either side of runway/taxiway centreline plane |
| Chromaticity (Red) | Within ICAO Annex 14 / FAA aviation red boundary (CIE coordinates) |
| Operating Mode | Steady-burning (not flashing) — illuminated or extinguished by the RWSL algorithm, no intermediate state |
| Isocandela Distribution | Per L-850T / L-852S in-pavement fixture photometric specification |
| Maintenance Factor | ≥ 50% of new-fixture intensity before replacement/cleaning is due, checked per field device |
| Test Method | Per-fixture photometric testing plus end-to-end system verification of detection-to-illumination response |
Applicable Standards
FAA Engineering Brief No. 64D
Runway Status Lights system specification — the core U.S. RWSL design/functional standard
FAA AC 150/5345-46
Specifies the L-850T and L-852S in-pavement fixtures used for the THL, REL, and RIL functions
FAA JO 7110.65, §3-4-20
Air traffic control procedures governing RWSL operation, override, and reporting
ICAO Annex 14, Vol I
General aerodrome design/lighting provisions; RWSL-type systems fall under ICAO's Autonomous Runway Incursion Warning System (ARIWS) guidance
Installation Requirements
Processing Rack Siting & Environmental Control
CivilInstall the redundant surveillance processing servers in a 19-inch rack within an environmentally controlled equipment room, confirming HVAC capacity and dual power feeds are in place before hardware installation.
Field Cabinet Placement
CivilPosition light control and monitoring cabinets at each holding position and take-off position per the design layout, confirming the enclosure meets at least IP65 before field wiring begins.
Diverse Fibre/Copper Route Installation
ElectricalLay dedicated fibre-optic or hardened copper links between the processing racks, field cabinets, and tower ATC display on diverse routes, so a single cable cut cannot break surveillance-to-light communication.
Surveillance Feed Interconnection
ElectricalConnect and configure the radar, ADS-B, and multilateration feeds into the processing system, verifying each source is live and correctly mapped before any logic testing begins.
Dedicated Supply & UPS Installation
ElectricalInstall the dedicated mains supply and UPS backup for the processing racks and field cabinets, sizing runtime to bridge a mains interruption without a loss of detection logic.
Field Circuit Termination to Existing Fixtures
ElectricalTerminate light control and monitoring outputs to the REL, RIL, and THL series circuits, confirming polarity and circuit assignment match the design drawings.
ALCMS / A-SMGCS Interface Configuration
SoftwareConfigure the network interface and data mapping between the RWSL processing system and the airport's ALCMS/A-SMGCS, confirming status reporting reaches the tower ATC display before activation.
Pre-Activation Sign-off
DocumentationRecord rack and cabinet locations, cable routing, surveillance source mapping, and circuit terminations as-built before the system proceeds to logic and reaction-time testing.
Testing & Commissioning
Sensor Fusion & Track Accuracy Verification
Pre-ActivationConfirm surface-movement radar/ADS-B tracks correlate accurately with actual aircraft and vehicle positions before enabling automated light control.
End-to-End Reaction Time Test
Pre-ActivationMeasure elapsed time from a qualifying conflict detection to REL/THL illumination, confirming it meets the mandated response window.
Output Device Activation Test
CommissioningIndividually verify every REL and THL fixture on the runway/taxiway network illuminates correctly on command from the controller.
Network & Communication Link Verification
Pre-ActivationConfirm controller-to-fixture and controller-to-ALCMS/A-SMGCS communication links remain stable under load.
UPS Backup & Failover Test
CommissioningSimulate a primary power loss and confirm the system continues operating without interruption on backup power.
Software & Logic Validation
Pre-ActivationRun scripted conflict scenarios and confirm the system's activation and deactivation logic responds correctly in each case.
ALCMS / A-SMGCS Integration Test
Final AcceptanceConfirm the system correctly reports status and accepts control handoffs from the airport's surface management system.
Live Traffic Shadow-Mode Trial
Final AcceptanceRun the system in shadow/observation mode against live traffic before operational activation, validating performance without affecting operations.
Inspection & Maintenance
Reaction Time Verification
QuarterlyTime the interval from simulated runway occupancy detection to light activation and confirm it stays under the sub-one-second threshold; drift here points to surveillance data latency.
Sensor Fusion & Track Accuracy Check
Semi-annualCross-check radar, ADS-B, surface movement radar, and multilateration tracks against known aircraft/vehicle positions to confirm the fused track feeding the logic engine stays accurate.
UPS Backup & Failover Test
Semi-annualSimulate a mains loss and confirm the UPS carries the system without a gap in coverage, and that failover paths bring the system back cleanly.
Network & Communication Link Audit
QuarterlyTest Ethernet, fibre, or wireless links between the RWSL controller and its output devices for latency or packet loss that could delay light activation.
Output Device Activation Test
MonthlyTrigger a controlled test activation of connected REL, RIL, and THL fixtures to confirm the RWSL logic engine correctly commands every downstream fixture.
Software & Firmware Review
AnnualCheck controller and logic-engine software against the latest vendor release and apply patches, since outdated firmware is a recurring source of false activations or missed conflicts.
ALCMS / A-SMGCS Integration Check
AnnualConfirm data exchange with the airfield lighting control and surface guidance systems remains synchronised, since a mismatch here can desync status indications across systems.
Controller & Server Hardware Inspection
AnnualInspect server racks, controller cabinets, and cooling for dust, thermal stress, or failing components that could degrade system reliability.
Common Field Issues
Surveillance Data Latency
Delays in surveillance data processing can cause the RWSL system to react slowly, potentially failing to activate lights in time. Regular system performance monitoring and network optimization are essential.
Communication Infrastructure Failure
RWSL systems rely on network communication between surveillance sensors, processing units, and output devices. Network failures can result in system-wide loss of functionality. Redundant communication paths are critical.
False Alarms
The RWSL system can trigger false alarms due to surveillance errors, wildlife detection, or system faults. False alarms can desensitize pilots and vehicle operators, reducing the effectiveness of the system.
Troubleshooting Guide
Lights Fail to Activate for an Occupied Runway
Lights Activate with No Traffic Present (False Alarm)
Slow or Delayed Response to a Genuine Conflict
System-Wide Loss of Function
Single Light Group Reports Fault but Others Operate Normally
Failure Modes & Root Causes
Surveillance Sensor Feed Loss or Degradation
Processing Server / Software Fault
Field Light Control Cabinet Failure
Communication Network Link Failure
Sensor Miscalibration / Clutter False Alarms
Fixture / Lamp Failure Within a Light Group
UPS / Backup Power Failure
Response-Time Degradation Under Load
Safety & Operational Notes
System, Not a Single Fixture
OperationalRWSL is a surveillance-driven system commanding dedicated REL, RIL, and THL fixtures; before working on any element, confirm whether you're isolating the field fixture's own series circuit, the control network link, or the central processing unit, since each has its own isolation point.
Processing Unit Redundant Supply
Electrical SafetyThe surveillance processing rack runs on dual redundant mains feeds with UPS backup; isolating one feed does not de-energise the rack, so confirm both feeds and the UPS are addressed per the manufacturer's lockout procedure before servicing it.
Field Circuit Isolation
Electrical SafetyField lights remain series circuits fed by their own CCR per the underlying REL, RIL, or THL specification; de-energise and lock out the correct CCR, then verify zero energy at the fixture before opening a base can or handling connectors.
Do Not Disable the Automated Function Unannounced
ComplianceRWSL provides automated, real-time runway occupancy alerting relied on by both pilots and vehicle operators; never take the system, or an individual light it drives, out of service without prior ATC coordination and a NOTAM covering the affected function.
Integration Testing After Any Change
ComplianceAfter any change to field wiring, the control network, or the processing unit, run the full detection-to-activation test sequence to confirm the correct lights still activate within the required response time before returning the system to live operational use.
Confirm Fail-Safe Behaviour Before Closing Out
ComplianceVerify the system reverts to a safe, conservative state (rather than a false-clear indication) in the event of a sensor or network fault before closing out and cancelling the associated NOTAM.
Engineering & Expert Notes
Surveillance Latency Is the Real Spec, Not Just Flash State
System IntegrationRWSL activation depends on the surface surveillance feed detecting a conflict and commanding the lights in near real time; benchmark end-to-end latency from actual aircraft/vehicle position to light activation after any surveillance sensor or software update, not just confirm that the lights illuminate on command.
A Correct-Looking Test Doesn't Confirm the Live Detection Logic
TestingA manual lamp test or forced activation confirms the fixture and wiring but says nothing about whether the underlying detection algorithm still correctly interprets real traffic patterns; schedule periodic live-traffic validation against actual surveillance data in addition to fixture-level testing.
Treat Software and Sensor Updates as Full-System Changes
Change ManagementAn update to the surface surveillance radar, ADS-B feed, or RWSL control software can change detection behaviour even when no fixture or cabling changes; run a full functional revalidation after any such update rather than treating it as a fixture-level maintenance item.
Distinguish a False Activation From a Genuine Conflict
TroubleshootingA pattern of unexplained light activations is more often a surveillance data quality issue — ghost tracks, multipath, or a misconfigured detection zone — than a fixture fault; correlate activation logs against actual traffic before assuming the problem is at the light itself.
Log and Trend Activation Response Times
ReliabilityRWSL response time can degrade gradually as sensor coverage or processing load changes, well before it fails outright; trend activation-to-illumination timing over successive test cycles rather than relying on a single pass/fail check at commissioning.
Fixture-Level Redundancy Doesn't Cover a Central Software Fault
DesignBecause many RWSL fixtures share a common detection and control backbone, redundant fixture wiring protects against a local failure but not a fault in the shared surveillance or processing chain; understand where the actual single points of failure sit in the system architecture, not just at the light fixtures.
Frequently Asked Questions
Short answers about Runway Status Lights (RWSL): what they do, light types, surveillance inputs, response time, standards, maintenance and common faults.
Q1What is the Runway Status Light (RWSL) system?
RWSL is an automated safety system that gives pilots and vehicle operators direct, real-time visual indications of runway status. It uses surveillance data to detect aircraft and vehicles on the runway, and lights dedicated in-pavement red lights when the runway is occupied or a conflict is imminent.
Q2What lights does RWSL use?
Steady-burning red in-pavement lights: Runway Entrance Lights (REL) at taxiway/runway intersections, Runway Intersection Lights (RIL) at runway/runway crossings and Take-Off Hold Lights (THL) on the runway centreline at the departure position.
Q3Why add RWSL when air traffic control already gives instructions?
RWSL adds an automated layer of runway incursion protection that operates independently of, and in parallel with, ATC instructions and pilot awareness. Workload, communication breakdowns or a surveillance gap can compromise those, while the system continuously fuses surveillance on every aircraft and vehicle near the runway.
Q4What surveillance data does RWSL use?
Radar, ADS-B, surface movement radar and multilateration. A processing system analyses the data to determine runway occupancy and predict conflicts.
Q5How fast does RWSL react?
Under 1 second from detection to light activation. Reaction time is verified regularly, and drift usually points to surveillance data latency.
Q6Do RWSL lights flash?
No. They are steady-burning and are either illuminated or extinguished by the algorithm, with no intermediate state. The lights are at least 2,000 cd (red).
Q7Where is RWSL used?
Busy airports with high traffic volumes and elevated incursion risk, including precision approach runways (CAT II and III), major international airports with complex taxiway layouts, intersecting runways and airports implementing advanced surface movement control.
Q8What does an RWSL installation involve?
It is a system installation rather than a single fixture. Field elements are in-pavement REL, RIL and THL fixtures (distinct from elevated Runway Guard Lights), on series circuits fed by CCRs, plus an airport surface surveillance processing system with dual redundant mains and UPS backup, integrated with ALCMS and A-SMGCS.
Q9Which standards apply to RWSL?
The main references are FAA Engineering Brief No. 64D (RWSL system specification), FAA AC 150/5345-46 (L-850T and L-852S in-pavement fixtures), FAA JO 7110.65 §3-4-20 (ATC procedures) and ICAO Annex 14 Vol I, where RWSL-type systems fall under ICAO's ARIWS guidance. Always verify the current edition and your approved requirements.
Q10How often should an RWSL system be tested?
Typical intervals are monthly for output device activation tests, quarterly for reaction time verification and network and communication link audits, and semi-annual for sensor fusion and track accuracy checks and UPS backup and failover tests. Your approved maintenance programme takes precedence.
Q11Why do the lights fail to activate for an occupied runway?
Loss or degradation of a surveillance feed (radar, ADS-B or multilateration), or a fault in the light control and monitoring subsystem at that light group. Check ATC display health alerts, confirm sensor feeds report valid tracks and test the field cabinet and circuit independently of the algorithm.
Q12Why do the lights activate with no traffic present?
Spurious or ghost targets from a surveillance sensor, such as radar clutter or multilateration multipath, are the likely cause. Investigate the sensor source and re-run response testing before returning the light group to live service.
Related Components
Go Beyond the Component. Understand the Complete AGL System.
You have explored the component. Now understand how it works within the complete Airfield Ground Lighting system.
Learn AGL from fundamentals to design, installation, testing, photometry, commissioning, maintenance and troubleshooting through structured technical training at Precision AGL Academy.
Build practical knowledge. Understand the circuit. Read the standards. Troubleshoot with confidence.
Your next step in AGL starts here.
Need expert guidance on RWSL system selection or installation?
Precision AGL Academy provides advice on system integration, surveillance optimization, and field testing of RWSL systems.
Follow the Academy
Important Notice, Disclaimer & Limitation of Liability
Please read before relying on any content on this page.
- Purpose and intended users. This page on Runway Status Light (RWSL) is an independent educational and informational reference for competent, suitably trained and authorised airfield ground lighting (AGL) and aerodrome electrical personnel. It is not professional engineering, legal or regulatory advice, and using it does not create any professional or client relationship.
- Safety. Work on series circuits, constant current regulators (CCRs), isolating transformers, cables, connectors and lighting equipment can be fatal. Always apply the aerodrome’s permit-to-work and isolation/LOTO procedures, prove dead, use correctly rated instruments and PPE, and follow the manufacturer’s instructions. Nothing here authorises work on live equipment or the bypassing of any safety device or interlock.
- Aviation operations. Nothing here authorises installation, modification, energisation, adjustment, return to service, a change of operating category (CAT I/II/III), a NOTAM or any aerodrome certification or approval decision. These rest with the aerodrome operator, the air navigation service provider and the competent regulator.
- Specifications, ratings and typical values. Descriptions, parameters, ratings, dimensions, photometric values, wattages, service lives, maintenance tasks and intervals, failure modes, certifications (for example CE, FCC, UL or IEC marks) and part or type designations are general, typical and indicative. They may not match any particular product, make, model or version, and they are not a datasheet, design, specification, selection, sizing, procurement or acceptance criterion. The manufacturer’s current documents, the approved design and the project specification prevail.
- Standards and regulations. References to ICAO, FAA, IEC, IEEE, ISO, BIS, DGCA and other standards are paraphrased summaries for orientation only. They may be incomplete or out of date, and standards are revised from time to time. Consult the current official editions. Following this content does not guarantee compliance with any law, standard or regulatory approval, and the regulator’s requirements always prevail.
- No warranty. Content is provided “as is” and “as available”, without warranty of any kind, express or implied, including accuracy, completeness, currency or fitness for a particular purpose. Real installations differ in design, equipment make and model, age and condition.
- Limitation of liability. To the fullest extent permitted by applicable law, Precision AGL Academy, Precision AGL Solutions and their owners, authors and contributors are not liable for any injury, death, loss, damage, downtime, penalty or regulatory consequence, whether direct or indirect, arising from the use of, reliance on, or inability to use this content. Nothing in this notice excludes or limits any liability that cannot lawfully be excluded or limited.
- Independence, brands and no endorsement. This is an independent publication. It is not affiliated with, sponsored by or endorsed by ICAO, the FAA, the IEC, DGCA, AAI, any airport, regulator, supplier or equipment manufacturer. Third-party names, product designations, standard designations and trademarks (including Megger®, Siemens, Eaton, Crouse-Hinds, ADB SAFEGATE, Fluke, ABB and Honeywell) belong to their respective owners and are used only for identification and description. Mention of a brand, product or supplier is not a recommendation, and we do not sell, supply or quote for any component described.
- Images and third-party content. Images and illustrations are shown to help identify the type of component. They may show products of various manufacturers, may not depict the exact item described, and are not a statement about any product’s quality, approval or performance. Copyright and trademarks in third-party images, logos and photographs belong to their respective owners and are not claimed as ours. If you are a rights holder and want an image removed, replaced or credited, email precisionaglsolutions@gmail.com with the page address and we will act promptly.
- Training and services. Mentions of training, courses, consultation, advice, selection, installation, calibration or other support, including the “Learn…Certify” pathway, describe learning stages and are not an offer, quotation, tender or promise of any result. Contacting us or our replying creates no engagement or duty of care; an engagement exists only under a written agreement. We are not a regulator or certification body, and completing any course or reading this content is not a certification, accreditation or authorisation to work on any aerodrome.
- Copyright, privacy and corrections. © 2026 Precision AGL Academy. All rights reserved. Text, structure, compilations and diagrams may be viewed for personal reference and internal training only; any other copying, republication or commercial use needs our written permission. If you email, telephone or message us, we use your details only to respond and handle your matter, in line with applicable Indian law including the Digital Personal Data Protection Act, 2023; please do not send confidential or security-sensitive information. To display this page your browser requests fonts, icons and images from third-party servers, which receive your IP address and browser details under their own policies. Content is reviewed periodically with no obligation to update. To report an error, safety concern or rights issue, write to precisionaglsolutions@gmail.com.