Vehicle Detection Sensor
A specialised detection system that monitors the presence and movement of ground vehicles on the airfield surface. Providing critical input to runway incursion prevention systems, A‑SMGCS, and ATC surveillance, these sensors enhance safety by alerting controllers to unauthorised vehicle movements on runways and taxiways.
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?
A Vehicle Detection Sensor is a specialised surveillance device designed to detect and track ground vehicles operating on the airfield surface—including runway sweeper trucks, maintenance vehicles, fuel trucks, baggage tugs, and other support vehicles. These sensors provide real‑time vehicle presence and movement data to Air Traffic Control, Airport Operations Centres, and runway incursion prevention systems. Unlike aircraft detection sensors that are optimised for larger targets, vehicle detection sensors are engineered to reliably detect smaller, slower-moving targets (typically 1‑5 tonnes) with high sensitivity and low false‑alarm rates. They are deployed at critical locations such as runway crossings, taxiway intersections, vehicle access points, and runway ends. The sensor data is integrated with A‑SMGCS (Advanced Surface Movement Guidance and Control Systems), RWSL (Runway Status Light) systems, and ATC displays to provide comprehensive surface surveillance, enabling controllers to manage both aircraft and vehicle movements safely and efficiently, particularly during low‑visibility operations and complex ground movements.
Purpose & Function
The vehicle detection sensor exists to close a specific blind spot in surface surveillance: aircraft detection systems are tuned for large, predictable targets, while service vehicles are smaller, move less predictably, and are exactly the kind of traffic a controller can lose track of during a busy ground movement sequence, particularly in low visibility. By giving ATC and A-SMGCS the same real-time presence and movement data for vehicles that they already have for aircraft, the sensor lets vehicle and aircraft movements be managed within a single coherent picture rather than the vehicle side being managed by memory, radio position reports, or visual observation from the tower alone. This matters most at the exact locations, runway crossings and taxiway intersections, where an undetected vehicle would otherwise pose the greatest incursion risk.
Where Is It Used?
Vehicle Detection Sensors are deployed at critical locations across the airfield where ground vehicle movements pose a potential conflict with aircraft operations:
- Runway Crossings: Detecting vehicles approaching or crossing active runways to prevent incursions and trigger warning systems.
- Taxiway Intersections: Monitoring vehicle movements at busy taxiway intersections to enhance situational awareness.
- Vehicle Access Points: Detecting vehicles entering the airside from landside access gates.
- Runway Ends (Threshold Areas): Monitoring vehicle activity near runway thresholds during maintenance or inspection operations.
- Apron Areas: Tracking ground support vehicles (fuel trucks, baggage tugs, catering vehicles) for improved apron management.
- Runway Status Light (RWSL) Systems: Providing vehicle detection input for Runway Entrance Lights (REL) and Takeoff Hold Lights (THL).
- A‑SMGCS (Advanced Surface Movement Guidance and Control Systems): Integrating with A‑SMGCS for comprehensive surface surveillance and conflict detection.
- ATC Towers: Providing controllers with real‑time vehicle location and tracking data, enhancing situational awareness.
- Airport Operations Centers: Monitoring fleet vehicle movements for operational planning and resource allocation.
Installation & Location
Sensors are positioned at the runway crossing, taxiway intersection, or access gate they monitor, mounted either as an in-pavement inductive loop (cut and sealed into the surface) or as a pole-mounted microwave/infrared unit set back clear of vehicle and aircraft clearance envelopes. Mounting height and detection-zone aim are set out so the zone covers the full width of the crossing or gate without extending into an adjacent lane where it would generate false triggers. Detector cabling runs on its own screened pair back to the local controller or Remote I/O rather than sharing conduit with unrelated lighting circuits, since the output typically drives a warning light or gate interlock directly.
How Does It Work?
The Vehicle Detection Sensor uses advanced detection technologies optimised for smaller, slower targets. Key functional aspects include:
- Detection Technologies: Sensors typically use one or a combination of:
- FMCW Radar (24 GHz or 77 GHz): Detects moving vehicles with high sensitivity, providing range, speed, and position information, immune to weather and lighting.
- Infrared (active or passive): Uses thermal signatures or reflected IR to detect vehicles, effective in darkness, fog, and smoke.
- Inductive Loops: Buried loops detect metallic vehicles passing over; simple and reliable, but limited to fixed points.
- Video Analytics (AI/CCTV): Uses camera footage with machine learning algorithms to detect and classify vehicles, providing visual confirmation.
- Fusion Sensors: Combine multiple technologies (e.g., radar + IR + video) for improved detection reliability and false‑alarm rejection.
- Target Classification: Advanced sensors can differentiate between vehicles and aircraft, or between different vehicle types (e.g., fuel truck vs. baggage tug), to provide more meaningful data to controllers.
- Coverage Zone: The sensor is positioned to cover a specific area—typically 50‑300 metres for radar/IR, or a precise detection point for inductive loops.
- Speed and Direction Detection: Radar sensors can determine vehicle speed and direction of travel, providing valuable information for conflict prediction.
- Output Signal: The sensor provides a clean, isolated output—typically a dry contact, transistor output, or digital message (Ethernet/Modbus)—that indicates vehicle presence, speed, and direction. The output is connected to the RWSL processor or A‑SMGCS.
- Self‑Diagnostics: The sensor continuously monitors its own health (power, communication, signal quality) and provides diagnostic outputs for proactive maintenance.
Vehicle detection sensors are typically mounted on poles adjacent to the monitored area, on overhead gantries, or integrated into existing airfield infrastructure. Their position and sensitivity are carefully calibrated to detect vehicles while ignoring small objects (birds, debris) and reducing false alarms.
System Architecture & Control Logic
Like the Stop Bar Sensor it is closely related to, the Vehicle Detection Sensor is a detection input rather than a decision-maker — it reports the presence of a smaller, slower-moving target (a service vehicle or piece of ground equipment) to a Remote I/O unit or local PLC, and the access-control or ALCMS logic upstream decides what to do with that information: hold a gate or barrier, trigger a warning light, or log the crossing. It does not itself energise any actuator or lighting circuit. Because it is tuned to detect targets smaller and slower than the aircraft the Stop Bar Sensor is designed around, it is typically deployed at vehicle crossing points and service road junctions rather than on the runway itself, and a fault is reported and handled the same conservative way — as a loss of detection at that location, not as an assumption that the crossing is clear.
Vehicle Detection Sensor
Tuned for smaller, slower targets — reports presence only
Remote I/O / PLC
Passes detection state upstream
Access Control / ALCMS Logic
Decides gate, barrier or warning-light action
Gate / Barrier / Warning Light
Actuated only on the upstream decision
How the Sensor Detects & Reports a Vehicle
Target Enters Coverage Zone
50‑300 m detection area, depending on technology
Detection Technology Senses Target
Radar, IR, video analytics, or inductive loop — often fused
Target Classification
Distinguishes vehicle from aircraft, bird, or debris
Speed & Direction Determined
Clean output signal sent to RWSL processor / A‑SMGCS
Filtered Out
Bird, debris, or noise rejected — no output triggered
Physical Construction
The sensor head is housed in a sealed, weatherproof enclosure — die-cast aluminium or glass-reinforced polymer — rated IP65/IP67, with a radome or optical window covering the radar, IR, or camera aperture to protect it from rain, dust, and de-icing overspray while remaining transparent to the sensing wavelength. Pole-mounted units bolt to an adjustable bracket that allows azimuth and elevation to be set and locked during commissioning, and where video analytics are used, the camera module is a separate sealed unit connected to the processing electronics by a short weatherproof cable run. Internal electronics are conformally coated and connected through sealed M12 or similar circular connectors rather than open terminal strips, keeping moisture out of the detection and output circuitry. Built-in transient voltage suppression is mounted near the cable entry point to protect against lightning-induced surges, and the enclosure includes a grounding lug for bonding to the site's lightning protection system.
Technical Parameters
| Parameter | Typical Value |
|---|---|
| Detection Technology | FMCW Radar (24/77 GHz) or IR (thermal) or Video Analytics or Inductive Loop |
| Coverage Range | 50‑300 m (radar), 50‑150 m (IR), 5‑20 m (inductive loop), 50‑100 m (video) |
| Azimuth Coverage | 5°‑20° (radar), 10°‑30° (IR), up to 180° (video with wide‑angle lens) |
| Minimum Target Size | 0.5 m² (radar), 1 m² (IR) — typical vehicle detection |
| Target Detection Speed | 0‑50 km/h (parked to vehicle speed) |
| Speed Accuracy | ± 2 km/h (radar) |
| False Alarm Rate | ≤ 1 per 24 hours (with proper calibration) |
| Output Type | Dry contact (relay, NO/NC), opto‑isolated transistor (PNP/NPN), Ethernet (Modbus TCP), serial (RS‑485), video stream (IP) |
| Response Time | ≤ 150 ms (radar), ≤ 200 ms (IR), ≤ 500 ms (video analytics) |
| Power Supply | 24 VDC (nominal, 18‑32 VDC) or 120/230 VAC (video cameras) |
| Power Consumption | 5‑25 W (radar/IR), 10‑50 W (video analytics with processing) |
| Operating Temperature | -30°C to +70°C (outdoor electronics) |
| Storage Temperature | -40°C to +85°C |
| Protection Class | IP65 / IP67 (weatherproof) |
| Surge Protection | Built‑in transient voltage suppression (TVS), up to 6 kV |
| Mounting | Pole‑mount (radar/IR/camera) or flush‑mount (inductive loop) |
| Diagnostics | Status LEDs, fault output, communication (RS‑485/Modbus), web interface (optional) |
| Certifications | CE, FCC (electronic emissions/immunity); designed to ICAO Annex 14 and EUROCAE ED‑87E/ED‑116 A‑SMGCS provisions |
Electrical Requirements
| Requirement | Typical Value |
|---|---|
| Circuit Position | Standalone powered sensor; output interfaces to control system (relay/serial/Ethernet) |
| Power Supply | 24 VDC (18–32 VDC nominal) or 120/230 VAC (video units) |
| Power Consumption | 5 – 50 W, depending on sensor type |
| Isolation | Output relay/opto-isolated interface keeps the sensor circuit separate from controlled loads |
| Surge Protection | Built-in transient voltage suppression (TVS), up to 6 kV |
| Earthing | Enclosure/mount bonded to local earth |
| Fault Protection | Internal overcurrent/surge protection; faults reported via diagnostic output |
Applicable Standards
ICAO Annex 14, Vol I
Aerodrome design and operations, including vehicle control on the movement area
FAA AC 150/5345‑46
Specification for Runway and Taxiway Light Fixtures, covering the REL and THL in‑pavement fixtures that RWSL drives
EUROCAE ED‑87E
MASPS for A‑SMGCS (current edition, Apr 2022) — defines the surveillance performance the sensor's output feeds into
EUROCAE ED‑116
MOPS for Surface Movement Radar sensor systems used in A‑SMGCS
Installation Requirements
Pole/Bracket Mounting
MechanicalBolt the sensor head to its adjustable mounting bracket at the design height, leaving azimuth and elevation free to adjust before final locking during commissioning.
Cable Route & Connector Termination
ElectricalRun cable to the sensor via sealed M12 or similar circular connectors rather than open terminal strips, keeping moisture out of the detection and output circuitry.
Grounding & Surge Protection
ElectricalBond the enclosure's grounding lug to the site's lightning protection system and confirm the built-in transient voltage suppression is correctly connected near the cable entry.
Camera Module Cabling (Video Analytics Variant)
ElectricalWhere video analytics are used, run the short weatherproof cable between the separate camera module and the processing electronics, keeping the run fully sealed.
Inductive Loop Installation (Loop Variant)
CivilFor inductive loop installations, saw-cut and install the loop conductor at the correct depth before the pavement is finally sealed.
Coverage Zone Setout
MechanicalMark out the intended detection area on the ground before final aim, confirming the sensor's mounting position and height can achieve the required coverage zone.
Pre-Energisation Sign-off
DocumentationRecord sensor position, mounting bracket settings, and cable terminations as-built before the sensor is energised for alignment and commissioning testing.
Testing & Commissioning
Alignment & Aim Verification
Pre-EnergisationSet and lock azimuth/elevation on the mounting bracket so the coverage zone matches the design detection area before power-up.
Power & Output Signal Check
EnergisationConfirm supply voltage at the sensor and verify the dry contact, transistor, or Ethernet output changes state correctly on a test target.
Detection Range & Speed Test
Final AcceptanceDrive a test vehicle through the coverage zone at varying speeds to confirm detection range, response time, and speed accuracy meet spec.
Target Classification Test
Final AcceptanceConfirm the sensor correctly distinguishes a vehicle from birds, debris, or other false targets without triggering a nuisance output.
False Alarm Rate Verification
Final AcceptanceMonitor the sensor over a settling period to confirm the false alarm rate is within the specified limit before operational handover.
Loop Continuity Test (Inductive Loop Variant)
Pre-EnergisationFor inductive loop installations, test loop continuity and resistance before the pavement is finally sealed.
Documentation & As-Built Sign-off
Final AcceptanceRecord sensor position, aim settings, and detection/false-alarm test results in the commissioning dossier for handover.
Inspection & Maintenance
Detection Accuracy Check
Semi-annualTest detection performance against known vehicle movements to catch false alarms or missed detections early.
Lens / Sensor Cleaning
QuarterlyClean the sensor lens or housing window to prevent obscuration from dust, dirt, or de-icing fluid residue.
Loop Continuity Test
AnnualFor inductive loop installations, test loop continuity and resistance to catch pavement-related damage.
Alignment Verification
Semi-annualConfirm sensor aim hasn't drifted, since misalignment leads to missed or false detections.
Power Supply Check
AnnualVerify power input stability at the sensor, a common source of intermittent detection faults.
Common Field Issues
False Alarms from Non‑Vehicle Targets
Radar and IR sensors may detect pedestrians, animals, or debris, causing false alarms. Advanced filtering and target classification algorithms are required to differentiate vehicles from other objects. Regular calibration and software updates are essential.
Sensor Obscuration (Radar/IR/Camera)
Snow, ice, heavy rain, dirt, or bird droppings on the sensor window or camera lens can significantly reduce detection performance. Regular cleaning and the use of heated housings, wipers, or air purges can prevent obscuration.
Inductive Loop Damage
Buried inductive loops can be damaged by pavement resurfacing, ground movement, or heavy vehicle loads. Periodic loop testing (using a loop tester) is required to detect open or short circuits.
Video Analytics Performance in Low Light
Camera‑based detection systems may struggle in low‑light conditions (night, fog, heavy rain) without specialised low‑light cameras or IR illumination. Use thermal cameras or integrated IR illuminators for reliable performance.
Alignment Drift
Over time, sensor mounts can shift due to vibration, thermal expansion, or ground movement, altering the detection zone. Regular site surveys and alignment checks using calibration targets are recommended.
Power Supply Instability
Voltage fluctuations or spikes can cause sensor resets or damage. Use a regulated power supply with surge protection and UPS backup to ensure reliable operation.
Troubleshooting Guide
False Alarms from Non-Vehicle Targets
Missed Detection in Adverse Weather (Sensor Obscuration)
Loop-Based Detection Not Registering
Unreliable Detection at Night or in Fog (Camera-Based)
Detection Zone Drifted from Design Boundary
Failure Modes & Root Causes
Lens / Sensor Contamination
Sensor Obscuration in Adverse Weather
Inductive Loop Damage (Loop Variant)
Video Analytics Performance in Low Light
Alignment Drift
Power Supply Instability
Safety & Operational Notes
Movement Area Coordination
OperationalCoordinate with ATC/airside operations and raise a NOTAM before any work that takes the sensor offline, since the data feeds A-SMGCS, RWSL, and ATC surface-surveillance displays used for runway incursion prevention.
Electrical Isolation
Electrical SafetyLock out the sensor's power and communications supply and verify zero energy before opening the housing or servicing internal electronics.
Calibration/Alignment Verification
ComplianceVerify detection accuracy and coverage zone against a known reference after any sensor mounting or aim adjustment; a mis-aimed or drifted sensor can create a blind spot or false-alarm zone that degrades incursion-prevention reliability.
Active Ground Traffic Awareness
OperationalSensors are deployed at runway crossings and taxiway intersections with live vehicle movement; barricade and mark the work area and stay alert to vehicles that the sensor itself would normally be detecting.
FOD Control
OperationalAccount for tools and fasteners at all times when the housing is open on or near the movement area, and secure loose material before leaving the site.
PPE
Personnel SafetyWear high-visibility clothing and standard airside PPE, and use insulated tools for electrical work.
Restore to Compliant State
ComplianceConfirm the sensor's data is correctly received by ATC and A-SMGCS/RWSL systems before closing out the work and cancelling the associated NOTAM.
Engineering & Expert Notes
False-Alarm Tuning Trades Directly Against Missed-Detection Risk
DesignTightening sensitivity to cut nuisance false alarms on a busy movement area inevitably raises the risk of missing a genuine slow-moving vehicle at the detection threshold; tune sensor sensitivity against the specific traffic mix and false-alarm tolerance at that location rather than applying one blanket setting airfield-wide.
Low-Visibility Performance Needs Separate Verification From Clear-Day Testing
VerificationA sensor that reliably detects vehicles in clear daylight can behave differently in fog, heavy rain, or snow depending on its underlying technology. Verify detection performance under degraded-visibility conditions specifically, since that's when the system matters most operationally.
Integration Latency With A-SMGCS/RWSL Matters as Much as Detection Accuracy
DesignA sensor can detect a vehicle correctly and still contribute to a near-miss if the data takes too long to propagate through to the A-SMGCS display or RWSL logic; verify end-to-end latency from detection to displayed or actuated response, not just standalone sensor accuracy.
Coverage Overlap at Intersections Should Be Deliberate, Not Assumed
DesignRunway crossings and taxiway intersections often sit at the edge of two adjacent sensors' coverage zones; confirm there's deliberate overlap covering the full intersection rather than assuming adjacent sensor footprints meet cleanly, since a coverage gap at exactly the highest-risk point defeats the system's purpose.
Alignment Drift Is Gradual and Easy to Miss Between Scheduled Calibrations
MaintenanceSmall mounting or aiming drift from wind, thermal cycling, or incidental contact can shift a sensor's detection zone gradually without triggering an obvious fault. Include a target-based alignment check in routine maintenance rather than relying solely on the sensor's own self-reported status.
Treat Detection Data as Safety-Critical for Change Control
OperationalBecause vehicle detection feeds directly into runway incursion prevention logic, any change to sensor configuration, firmware, or mounting should go through the same change-control rigor as a change to the lighting or signage it protects, not be treated as a routine IT update.
Related Components
Frequently Asked Questions
Short answers about vehicle detection sensors: technologies, coverage, outputs, standards and common problems.
Q1What is a vehicle detection sensor in AGL?
A vehicle detection sensor is a surveillance device that detects and tracks ground vehicles on the airfield surface, such as sweeper trucks, maintenance vehicles, fuel trucks and baggage tugs. It gives real-time presence and movement data to ATC, airport operations centres and runway incursion prevention systems.
Q2Why are dedicated vehicle sensors needed?
Aircraft detection systems are tuned for large, predictable targets. Service vehicles are smaller (typically 1 to 5 tonnes), move less predictably and are easy to lose track of during busy ground movements or low visibility. Vehicle sensors give ATC and A-SMGCS the same data for vehicles as for aircraft.
Q3What detection technologies are used?
FMCW radar (24 GHz or 77 GHz), infrared (active or passive), inductive loops, video analytics (AI/CCTV), and fusion sensors that combine several technologies for better reliability and false-alarm rejection. Radar is immune to weather and lighting, infrared works in darkness, fog and smoke, and loops are simple but limited to fixed points.
Q4What is the detection range?
Typically 50 to 300 m for radar, 50 to 150 m for infrared, 50 to 100 m for video, and 5 to 20 m for inductive loops. Radar sensors can also measure vehicle speed (typically ±2 km/h) and direction of travel.
Q5Where are vehicle detection sensors installed?
At runway crossings, taxiway intersections, vehicle access points from landside gates, runway thresholds during maintenance operations and apron areas. They also feed Runway Status Light (RWSL) systems, A-SMGCS, ATC towers and airport operations centres.
Q6How does the sensor connect to other systems?
It has a clean, isolated output: typically a dry contact relay, opto-isolated transistor output, Ethernet (Modbus TCP), RS-485 serial or an IP video stream. Output indicates presence, speed and direction and connects to the RWSL processor or A-SMGCS. Response time is typically 150 ms or less for radar.
Q7What are the typical electrical and environmental ratings?
Power is 24 VDC nominal (18 to 32 VDC) or 120/230 VAC for video units, with 5 to 50 W consumption depending on type. Protection class is IP65/IP67, operating temperature is -30°C to +70°C, and built-in TVS surge protection is rated up to 6 kV.
Q8Which standards apply to vehicle detection sensors?
The main references are ICAO Annex 14 Vol I, FAA AC 150/5345-46 (covering the REL and THL in-pavement fixtures that RWSL drives), EUROCAE ED-87E (A-SMGCS MASPS) and EUROCAE ED-116 (MOPS for surface movement radar sensor systems). Always verify the current edition.
Q9How can false alarms be reduced?
Radar and IR sensors may detect pedestrians, animals or debris, so advanced filtering and target classification algorithms are needed. Position and sensitivity are calibrated to detect vehicles while ignoring small objects such as birds and debris, and the typical false alarm rate target is no more than 1 per 24 hours with proper calibration.
Q10What are the common vehicle detection sensor problems?
The common issues are false alarms from non-vehicle targets, obscuration of the sensor window or lens by snow, ice, rain, dirt or bird droppings, inductive loop damage from resurfacing or ground movement, poor video analytics performance in low light, alignment drift, and power supply instability.
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 Vehicle Detection Sensor selection, installation, or integration for your airfield?
Precision AGL Academy provides advice on sensor technology selection, placement, calibration, and integration with RWSL and A‑SMGCS 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 Vehicle Detection Sensor 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.