Final Approach Runway Occupancy Signal (FAROS)
An advanced airfield safety system that alerts pilots on final approach when the runway ahead is occupied. Rather than adding a new light fixture, FAROS drives the airport's existing Precision Approach Path Indicator (PAPI) into a flashing mode when a surface-surveillance system detects a conflict, giving pilots a direct visual go-around cue without waiting on an ATC radio call.
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 Final Approach Runway Occupancy Signal (FAROS) is an advanced airfield safety capability that provides visual alerts to pilots on final approach when a runway is occupied. Rather than being a standalone light fixture, FAROS is an add-on control function for the existing Precision Approach Path Indicator (PAPI): when surface surveillance detects that the runway's protected zone is occupied, the FAROS controller commands the PAPI light units to flash instead of burning steady, giving the approaching pilot a clear, unambiguous "runway not clear" cue without requiring any additional cockpit equipment or waiting on an ATC radio call.
Purpose & Function
FAROS exists to close a specific, dangerous gap in runway safety: a pilot on short final has no reliable way to see for themselves whether the runway ahead is actually clear, since another aircraft, vehicle, or obstruction on the far end of a long runway may not be visible from the approach path, and radio communication about runway status can be delayed, missed, or misunderstood. By switching the PAPI — a light array the pilot is already looking at for glide-path guidance — into a flashing state exactly when the runway is occupied, the system gives a go-around decision cue that doesn't depend on air traffic control instruction or the pilot's own visual judgement of a runway they may not be able to fully see. Its purpose, in short, is to convert a hidden runway-occupancy hazard into a direct, self-evident visual warning at the single moment — final approach — when a wrong decision has the least time to be corrected.
Where Is It Used?
FAROS systems are installed at busy airports with high traffic volumes and complex runway configurations where approach conflicts are a significant risk. They are typically used on:
- Precision approach runways (CAT II and III) where safety margins are critical
- Major international airports with intersecting runways and complex approach paths
- Runways with high traffic density where incursion risk is significant
- Airports implementing advanced safety management systems
- Runways with limited visibility operations where visual cues are essential
Installation & Location
FAROS is retrofitted onto the runway's existing PAPI installation — typically a 4-box L-880 (or 2-box L-881) array sited beside the runway roughly 300 m (1,000 ft) from the threshold, on the same low, frangible-mounted ground stands used for standard PAPI. No new elevated light fixture or dedicated FAROS bar is required; the FAROS driver is added inline between the PAPI's own power/lamp-control unit and its light heads so it can switch the units into a flashing state without disturbing their aiming or glide-path calibration. The system is tied into the airport's surface surveillance source (ASDE-X, ASSC, or ADS-B-based tracking) via a FAROS controller that evaluates occupancy status for the defined activation zones and issues the flash command on detection of a conflict. The controller, its power supply, and its monitoring unit are usually housed in an equipment shelter near the PAPI site, and installation is coordinated closely with the surveillance system's own commissioning to validate accurate occupancy detection before activation is enabled.
How Does It Work?
The FAROS system operates through an integrated surveillance and alert mechanism:
- Surveillance: Surface surveillance data (ASDE-X, ASSC, or ADS-B-based tracking) tracks aircraft and vehicle positions on the airfield.
- Detection: The FAROS processing system evaluates whether a defined runway activation zone is occupied by an aircraft or vehicle.
- Activation: When an activation zone is occupied, the FAROS controller switches the runway's existing PAPI light units from steady-burning to a flashing state.
- Alert: The flashing PAPI gives the approaching pilot a clear, unambiguous indication that the runway is not clear for landing.
- Deactivation: When the activation zone is clear, the PAPI reverts to its normal steady glide-path indication and the pilot proceeds with the approach.
System Architecture & Control Logic
Unlike a series-circuit AGL fixture, FAROS is not commanded by the tower or an ALCMS brightness step — it is a self-contained, sensor-driven system that decides its own state in real time and acts on the PAPI it is attached to, rather than on a fixture of its own. Surface surveillance feeds (ASDE-X, ASSC, or ADS-B-based tracking) are continuously ingested by the FAROS occupancy processor, which evaluates whether the protected runway segment is occupied and, on detecting a conflict, drives the PAPI's existing light heads into a flashing mode independent of any ATC action. Because a missed occupied-runway call is far more dangerous than an unnecessary flash, the logic is fail-safe by design: any loss of confidence in the surveillance feed, a processor fault, or a communications dropout defaults the system to the conservative "occupied" (flashing) state rather than reverting silently to steady-burning, and the fault is separately reported to the ALCMS/tower for maintenance action.
Surveillance Feed → Occupancy Processor → FAROS Driver → PAPI Light Heads Flash (fail-safe to "occupied")
Detection-to-Alert Cycle
Both outcomes feed back into continuous surveillance — the system re-evaluates runway status in real time for every approach, not just once per landing.
Physical Construction
FAROS does not introduce a new optical fixture: the light-emitting hardware remains the runway's existing PAPI light units (typically a sealed LED or halogen luminaire in a die-cast aluminium enclosure, anodised or powder-coated, with a red/white split beam behind a toughened glass lens), mounted low to the ground on frangible couplings beside the runway per standard PAPI siting. What FAROS adds is a driver/interface module — usually a card or unit built into or wired alongside the PAPI's power and control unit (PCU) — that can override the PAPI's normal steady output and switch the light units into a flashing pattern on command. This driver electronics package is potted or conformal-coated for moisture protection and connected via sealed, direct-burial-rated cable glands to a dedicated mains feed and UPS backup circuit, since the FAROS function must remain available even through a brief power interruption. A weatherproof junction box near the PAPI site houses the interface to the surface-surveillance/RWSL, A-SMGCS, or ALCMS control link, with corrosion-resistant fasteners and hardware used throughout given the fixture's exposed, low-lying siting near the runway environment.
Technical Parameters
| Parameter | Typical Value |
|---|---|
| Light Source | Existing PAPI light units (LED or halogen; the runway's own L-880/L-881 array — FAROS adds no new luminaire) |
| Colour | Standard PAPI red/white split beam; flashes rather than burns steady when activated |
| Flash Rate | Approx. 60 flashes per minute (adjustable at the FAROS driver) |
| Intensity | Same as the PAPI unit's normal steady-burning beam (no separate intensity spec) |
| Beam Pattern | Unchanged from PAPI — narrow vertical fan beam directed along the approach path |
| Mounting Type | Ground-level, on the PAPI's own frangible-mounted stands beside the runway (not elevated) |
| Power Supply | FAROS driver on dedicated mains with UPS backup; PAPI light units powered as normal |
| Integration | Surface surveillance (ASDE-X/ASSC/ADS-B), reported to RWSL, A-SMGCS, and ALCMS |
| Protection Class | IP65 / IP67 (weatherproof), matching standard PAPI enclosure ratings |
Electrical Requirements
| Requirement | Typical Value |
|---|---|
| Circuit Type | Dedicated mains branch circuit for the FAROS driver (not a series/CCR loop); PAPI light units remain on their own normal supply |
| Supply Voltage | 120V / 240V AC single-phase (regional variants available) |
| Backup Power | UPS backup circuit, sized for continued operation through a mains interruption |
| FAROS Driver | Potted / conformal-coated interface module that overrides the PAPI's steady-burning output and regulates flash rate |
| Cable Type | Direct-burial-rated cable via sealed, weatherproof cable glands |
| Control Interface | Low-voltage data link to RWSL, A-SMGCS, or ALCMS via weatherproof junction box |
| Earthing/Grounding | PAPI light unit housings, driver enclosure, and junction box bonded to the airfield earth grid |
| Fault Protection | Driver-level fault detection with UPS transfer and mains-loss monitoring |
| Power Source | Dedicated mains feed with UPS backup, status monitored by the host control system |
Photometric Requirements
| Parameter | Typical Value |
|---|---|
| Peak Beam Intensity | Unchanged from the underlying PAPI unit's certified steady-burning intensity (per FAA AC 150/5345-28H / ICAO Annex 14) |
| Flash Rate | Approx. 60 flashes per minute, adjustable at the FAROS driver/controller |
| Vertical Beam Spread | Unchanged from PAPI — narrow vertical fan beam split between the white (above glide path) and red (below glide path) sectors |
| Horizontal Beam Spread | Unchanged from PAPI — directed along the final approach path |
| Chromaticity | Standard PAPI red/white boundaries per ICAO Annex 14 (CIE coordinates); FAROS does not alter colour, only cadence |
| Directionality | Uni-directional, aimed at approaching aircraft on final (as for the underlying PAPI) |
| Activation Behaviour | PAPI switches from steady to flashing when the surveillance system reports the activation zone occupied; reverts to steady when clear |
| Effective Intensity | Governed by the PAPI unit's own certified photometrics; FAROS activation does not require a separate effective-intensity calculation |
| Aiming Tolerance | Set by the underlying PAPI's own aiming/calibration procedure; FAROS retrofit must not disturb glide-path aim |
| Test Method | Photometric verification that flashing mode preserves the PAPI's certified intensity and aim, plus flash-rate and activation-logic checks during commissioning and periodic checks |
Applicable Standards
ICAO Annex 14
Aerodrome visual aids requirements, including PAPI systems FAROS is built on
FAA AC 150/5345-28H
Precision Approach Path Indicator (PAPI) Systems — the underlying light units FAROS drives
FAA Order JO 6850.2C
Visual Guidance Lighting Systems (current edition) — siting/integration guidance for FAROS with ALS and RWSL
FAA AC 150/5345-53
Airport Lighting Equipment Certification Program — qualification listing for certified equipment
Installation Requirements
Driver Module Retrofit
MechanicalFit the FAROS driver module inline with the existing PAPI power and control unit (PCU) per the manufacturer's retrofit kit, without disturbing the PAPI light units' mounting or aim.
Verify PAPI Aim Undisturbed
MechanicalConfirm the underlying PAPI units remain within their certified glide-path aiming tolerance after the retrofit — FAROS must not require re-aiming the light heads.
Power Cable Route & Termination
ElectricalRun the dedicated mains feed to the driver module through sealed, direct-burial-rated cable glands, keeping the run separate from the PAPI's own PCU wiring.
UPS Backup Installation
ElectricalInstall and wire the UPS backup near the driver module or equipment shelter, sized to carry the FAROS function through the required outage duration before mains power is restored.
Surveillance/Communication Interface Wiring
SystemsTerminate the RWSL, A-SMGCS, or ALCMS communication link at the weatherproof junction box per the system integration specification, keeping runs separated from power cabling.
Junction Box Weatherproofing
MechanicalSeal the junction box near the PAPI site against wind-driven rain and dust, confirming cable glands and gaskets are fully seated before closing.
Controller Configuration Upload
SystemsLoad the design flash rate and activation logic parameters into the FAROS controller before any pre-activation testing begins.
Pre-Activation Sign-off
DocumentationRecord the PAPI's post-retrofit aiming check, cable/connector terminations, and driver configuration as-built before the system is energised for testing.
Testing & Commissioning
Surveillance Interface Validation
Pre-ActivationConfirm the system correctly receives runway occupancy data from the airport's surveillance source before enabling automated activation.
Activation Logic Test
Pre-ActivationRun scripted occupancy scenarios and confirm the flashing signal activates and deactivates correctly in each case.
Flash Rate & Intensity Verification
Final AcceptanceMeasure flash rate and intensity with a calibrated photometer against applicable thresholds before handover.
Communication Link Verification
Pre-ActivationConfirm the link between the FAROS controller and the surveillance/communication source remains 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-ActivationConfirm the controller's occupancy-to-activation logic matches the design specification across all tested scenarios.
Mounting & Visibility Verification
Final AcceptanceConfirm the unit is correctly mounted and visible to pilots on final approach at the design decision point.
Documentation & As-Built Sign-off
Final AcceptanceRecord activation logic, communication, and photometric test results in the commissioning dossier for handover.
Inspection & Maintenance
Flash Intensity & Rate Check
AnnualVerify peak candela output and flash rate against the design specification using a calibrated photometer, since dimming or an off-tempo flash pattern reduces conspicuity to arriving crews.
PAPI Lens & Optics Cleaning
QuarterlyClean the PAPI light units' lenses of dust, insects, and weather film so the red/white split beam stays within its intended cone toward final approach — routine PAPI upkeep that also protects FAROS conspicuity.
Surveillance Interface Validation
Semi-annualConfirm the data link from RWSL, A-SMGCS, or ALCMS surveillance sources is current and correctly triggering activation, since a stale feed causes late or missed alerts rather than a hardware fault.
Activation Logic Test
AnnualRun a simulated runway-occupancy scenario end-to-end to confirm the system activates and deactivates within its designed response window.
UPS & Power Supply Check
Semi-annualTest the dedicated mains supply and UPS backup under simulated outage conditions to ensure uninterrupted operation during a mains failure.
Communication Link Inspection
AnnualInspect network cabling, switches, and redundant communication paths between sensors, processing units, and light heads for degradation or single points of failure.
Housing & Mounting Structure Inspection
AnnualCheck the PAPI ground stand, weatherproof housing seals, and fasteners for corrosion, looseness, or ingress that could compromise IP rating.
Software & Firmware Update Review
AnnualConfirm processing unit firmware and control software are on the manufacturer's supported version to close known calibration and false-alarm issues.
Common Field Issues
Surveillance Data Latency
Delays in surveillance data processing can cause the FAROS system to react slowly, potentially failing to alert pilots in time. Regular system performance monitoring and network optimization are essential.
False Alarms
The FAROS system can trigger false alarms due to surveillance errors or system faults. False alarms can desensitize pilots and reduce the effectiveness of the system. Regular calibration and system validation are critical.
Communication Infrastructure Failure
FAROS 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 essential.
Troubleshooting Guide
System Fails to Activate on Runway Occupancy
Frequent False Alarms / Nuisance Activations
Delayed Activation / Slow Response
System-Wide Loss of Function
Single Light Head Dark or Dim
System Drops Out on Mains Failure
Failure Modes & Root Causes
Surveillance Feed Loss or Staleness
Calibration Drift / Firmware Fault Causing False Alarms
Communication Path / Network Switch Failure
UPS Battery Degradation / Transfer-Switch Failure
Individual Light Head LED/Driver Failure
Safety & Operational Notes
Mains Circuit, Not a Series Loop
Electrical SafetyThe FAROS driver runs on a dedicated mains branch circuit rather than the runway's CCR series loop; isolate and lock out at the FAROS driver's own supply point, and don't assume the PAPI is dead just because the FAROS circuit is isolated — the PAPI light units keep their own supply (mains for Style A, CCR series loop for Style B).
Surveillance Integration Dependency
OperationalThe flashing indication is driven entirely by the surface surveillance feed (ASDE-X, ASSC, or ADS-B-based tracking); any work on the FAROS driver or the PAPI light units must be followed by an integration check confirming occupancy detection still correctly triggers flashing before returning the system to service.
PAPI Site Work Coordination
OperationalBecause FAROS is retrofitted onto the PAPI's own hardware, work here follows the PAPI's own access, frangibility, and aiming-preservation procedures rather than a separate approach-lighting-structure procedure, coordinated with ATC and covered by a NOTAM for the affected runway.
Equipment Shelter Access
Electrical SafetyThe FAROS controller, power supply, and monitoring unit are typically housed in an equipment shelter; follow standard electrical lockout procedure at the shelter's own supply before servicing the controller, independent of the field circuit isolation.
Verify Before Re-Energisation
Electrical SafetyAfter any field wiring or controller work, test the affected lights and confirm the surveillance interface still reports correctly before restoring the system to active monitoring.
Restore to Compliant State
ComplianceDo not return FAROS to service with an unverified occupancy trigger; confirm detection accuracy and flash synchronisation against the parent ALS system before closing out and cancelling the associated NOTAM.
Engineering & Expert Notes
Aiming Drift Is a PAPI Calibration Issue, Not a FAROS One
MechanicalBecause FAROS rides on the existing PAPI hardware rather than a fixture of its own, any azimuth/elevation drift is a PAPI aiming and pad-settlement issue — ground movement, frost heave, or a knocked stand — not something introduced by the FAROS retrofit. Re-verify PAPI aim against the extended runway centreline on the PAPI's own periodic schedule, and don't chase a "FAROS aiming" problem that is really a PAPI calibration problem.
Test the UPS as a Real Load Transfer, Not a Status Light
Electrical SafetyThe safety case for FAROS depends on the mains-to-UPS backup circuit actually switching over correctly under a genuine mains loss. A healthy standby indicator doesn't confirm that — schedule an actual load-transfer test on the UPS circuit rather than relying on its status LED alone.
A Driver Swap Can Silently Change Cadence Without Touching Intensity
RetrofitThe FAROS driver only overrides the PAPI's steady/flashing state — it doesn't regulate beam intensity, which stays governed by the PAPI's own power and control unit. After swapping a FAROS driver module, confirm flash rate and duty cycle match spec; don't assume the retrofit affects intensity, and don't skip re-checking the PAPI's own photometrics if the PCU was touched during the same visit.
Validate Through the Real Control Interface
System DesignA FAROS fixture that flashes correctly on a manual bench test can still fail its intended function if the interface to RWSL, A-SMGCS, or ALCMS doesn't correctly trigger on actual runway occupancy. Validate through the live control interface, not just the fixture in isolation.
Frangible-Stand Vibration Loosens Fasteners Before It Damages Housings
MechanicalPAPI/FAROS units sit on ground-level frangible stands exposed to jet-blast and continuous low-level vibration, which loosens fastener torque well before it produces any visible housing damage. Check fastener torque on a defined interval rather than waiting for a visual sign of movement to prompt a check.
Wind-Driven Rain at Ground Level Still Isn't a Bench Test
DurabilityThe IP65/67 rating on the PAPI/FAROS enclosure reflects rain driven horizontally by wind across open airfield terrain — angles a static bench seal-check never replicates. A gasket that seals fine on the bench can still leak in service, so don't treat a bench check as representative of in-service performance.
Frequently Asked Questions
Short answers about FAROS (Final Approach Runway Occupancy Signal): what it is, how it works, specifications, standards, maintenance and common faults.
Q1What is FAROS?
The Final Approach Runway Occupancy Signal (FAROS) is an airfield safety capability that gives pilots on final approach a visual alert when the runway is occupied. It is an add-on control function for the existing PAPI rather than a standalone light fixture.
Q2How does FAROS alert pilots?
When surface surveillance detects that the runway's protected zone is occupied, the FAROS controller commands the PAPI light units to flash instead of burning steady. This gives the approaching pilot a clear runway-not-clear cue without extra cockpit equipment or waiting for an ATC radio call.
Q3What is the sequence of operation?
Surface surveillance (ASDE-X, ASSC or ADS-B-based tracking) tracks aircraft and vehicles, and the FAROS processing system checks whether a defined runway activation zone is occupied. If it is, the controller switches the PAPI from steady to flashing, and when the zone is clear the PAPI reverts to steady.
Q4Does FAROS add new lights?
No. It adds no new luminaire. It drives the runway's existing PAPI light units (the L-880/L-881 array), which keep their normal colour, beam pattern and intensity. Only the cadence changes, at about 60 flashes per minute adjustable at the FAROS driver.
Q5Where is FAROS installed?
At busy airports with high traffic and complex runway configurations where approach conflicts are a significant risk: precision approach runways (CAT II and III), major international airports with intersecting runways, and runways with high incursion risk.
Q6How is FAROS powered?
The FAROS driver runs on a dedicated mains branch circuit (120/240 V AC single-phase, regional variants available) with UPS backup, not a series CCR loop. The PAPI units stay on their own normal supply, and the driver has fault detection with UPS transfer and mains-loss monitoring.
Q7How does FAROS connect to other systems?
Through a low-voltage data link via a weatherproof junction box to RWSL, A-SMGCS or ALCMS, with the driver as a potted or conformal-coated interface module that overrides the PAPI's steady output and regulates flash rate. Enclosures are IP65 or IP67.
Q8Which standards apply?
The main references are ICAO Annex 14, FAA AC 150/5345-28H (PAPI systems), FAA Order JO 6850.2C (visual guidance lighting systems, including FAROS siting and integration) and FAA AC 150/5345-53 (equipment certification). Always verify the current edition and your aerodrome's approved requirements.
Q9How often should FAROS be maintained?
Typical intervals are quarterly for PAPI lens and optics cleaning, semi-annual for surveillance interface validation and UPS and power supply checks, and annual for flash intensity and rate, activation logic test, communication link inspection, housing and mounting inspection and software and firmware update review. Your airport's approved maintenance programme takes precedence.
Q10What are the common problems with FAROS?
Common problems are surveillance data latency or feed loss, false alarms from calibration drift or firmware faults, communication path failure, UPS battery degradation or transfer-switch failure, and individual light head LED or driver failure. Failure to activate on runway occupancy, frequent nuisance activations and delayed activation are the typical symptoms.
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 FAROS system selection or installation?
Precision AGL Academy provides advice on system integration, surveillance optimization, and field testing of FAROS 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 Final Approach Runway Occupancy Signal (FAROS) 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.