Stop Bar Sensor
A precision detection device that monitors aircraft and vehicle presence at runway holding positions. Stop Bar Sensors are a critical component of Runway Status Light (RWSL) systems, providing real‑time occupancy data to prevent runway incursions and enhance surface safety.
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 Stop Bar Sensor is a compact, high‑reliability detection device installed at runway holding positions (stop bars) to detect the presence of aircraft or vehicles that are approaching, crossing, or occupying the stop bar area. The sensor is a key component of the Runway Status Light (RWSL) system, providing the real‑time occupancy data needed to activate runway entrance lights (RELs), take‑off hold lights (THLs), and runway guard lights. Stop Bar Sensors typically use radar, infrared, or inductive loop technology to detect metallic targets with high accuracy and reliability, even in adverse weather conditions. They are designed for harsh airfield environments, with rugged housings, wide temperature tolerance, and lightning protection. The sensor's output (typically a dry contact or digital signal) is fed to the RWSL processing unit, which uses it to determine runway status and control the associated warning lights. By providing precise occupancy detection, Stop Bar Sensors help prevent runway incursions and support safe, efficient ground operations.
Purpose & Function
Where a runway occupancy sensor watches an entire runway segment, the stop bar sensor's purpose is narrower and more precise: to detect the exact moment an aircraft or vehicle crosses a specific holding position, the one line on the airfield where a runway incursion actually begins. That point-detection role is what makes it suitable for triggering RELs and THLs at the specific location where entry onto the runway occurs, rather than reporting on runway status more broadly. Its rugged construction and lightning protection reflect the fact that it sits at one of the highest-consequence locations on the airfield, where a missed or false detection has a direct bearing on runway incursion risk rather than being a general monitoring inconvenience.
Where Is It Used?
Stop Bar Sensors are deployed at all runway holding positions where stop bars are installed, and in other critical areas where occupancy detection is required:
- Runway Holding Positions: At taxiway/runway intersections, sensors detect aircraft waiting to enter the runway, triggering RELs and warning lights.
- Runway Entrance Lights (REL) Systems: Sensors provide the detection input that activates the RELs when an aircraft crosses the stop bar.
- Take‑Off Hold Lights (THL) Systems: Sensors detect aircraft at the take‑off position on the runway, activating the THLs to warn other traffic.
- Runway Guard Light Systems: Sensors trigger flashing amber warning lights when a vehicle or aircraft approaches a runway holding position.
- RWSL (Runway Status Light) Systems: As a primary input sensor, providing accurate occupancy data to the RWSL logic processor.
- A‑SMGCS (Advanced Surface Movement Guidance and Control Systems): Integrating with A‑SMGCS for enhanced surface surveillance and conflict detection.
- Apron and Gate Areas: Detecting aircraft or vehicles at gate positions for ground handling coordination.
- Vehicle Access Points: Monitoring vehicle crossings of taxiways or runways to ensure safety.
Installation & Location
Sensors are set into or beside the pavement at the runway holding position, either as an inductive loop cut into a saw-cut slot in the taxiway surface or as a surface-mounted microwave/infrared head on a short frangible post clear of wingtip clearance. Loop sensors are sealed into their slot with a bitumen or epoxy compound and home-run in duct back to the local field cabinet, while surface-mounted heads are aligned so their detection zone covers the full stop bar width without triggering on adjacent lanes. Detector output cabling is kept on its own screened pair back to the REL/THL controller or Remote I/O rather than sharing conduit with lighting series-circuit cable, since a nuisance trip on this input directly drives a runway safety light.
How Does It Work?
The Stop Bar Sensor uses a combination of detection technologies to provide reliable target presence indication. Key functional aspects include:
- Detection Technologies: Sensors typically use one or a combination of:
- Radar (FMCW or pulsed): Detects moving targets and provides range and velocity information, immune to weather conditions.
- Infrared (active or passive): Uses thermal or reflected IR to detect targets, effective in darkness and fog.
- Inductive Loop: Buried wire loops detect changes in inductance when a metallic target passes over; simple and reliable.
- Target Classification: Advanced sensors can differentiate between aircraft and vehicles, or ignore small objects (birds, debris) to reduce false alarms.
- Coverage Zone: The sensor is positioned to cover the stop bar area, typically a zone 5‑10 metres wide and 1‑3 metres deep, ensuring that any aircraft or vehicle crossing the stop bar is detected.
- Output Signal: The sensor provides a clean, isolated output—typically a dry contact (relay) or transistor output—that changes state when a target is detected. The output is connected to the RWSL logic processor or PLC.
- Self‑Diagnostics: The sensor monitors its own health (e.g., power supply, signal quality, internal faults) and provides a diagnostic output (or fault indicator) to alert maintenance staff.
- Environmental Protection: The sensor is housed in a rugged, IP65/67 enclosure, with weatherproof connectors and surge protection for lightning‑prone airfield environments.
The sensor is typically mounted on a small pole (0.5‑1.5 m high) adjacent to the stop bar, or embedded in the pavement (inductive loops). Its position and orientation are carefully calibrated to ensure it only detects targets that are actually within the stop bar zone, avoiding false triggers from adjacent taxiways or apron areas.
System Architecture & Control Logic
The Stop Bar Sensor is a detection input at the edge of the control system rather than a controller itself — it reports a target's presence to the RWSL logic or ALCMS server, typically via a Remote I/O unit or directly wired into the local PLC, and takes no action on the stop bar or runway status lights on its own. That upstream logic combines the sensor's detection with the current runway/taxiway occupancy state and traffic clearances to decide whether the stop bar should be illuminated, and issues the corresponding command back down to the CCR controlling that circuit. Because the sensor's output is only ever an input to that decision, a sensor fault is treated as a loss of detection at that specific location — the system typically fails toward the conservative state (stop bar lit) rather than assuming clear, and the fault is reported to the ALCMS as a sensor-level alarm distinct from a lighting-circuit fault.
Stop Bar Sensor
Detects target presence — reports only, does not decide
Remote I/O / PLC
Passes detection state to the RWSL logic / ALCMS server
RWSL Logic / ALCMS Server
Combines detection with occupancy & clearance state, issues command
CCR → Stop Bar Lights
Illuminates or extinguishes per the logic's decision
Detection & Output Path
Physical Construction
The sensor is built into a compact, sealed housing — die-cast aluminium or glass-reinforced polymer — rated IP65/IP67, small enough to mount on a short pole beside the stop bar or flush into the pavement where inductive loop technology is used instead. A radome or optical window covers the radar or IR aperture, transparent to the sensing wavelength while shedding rain, dust, and de-icing fluid, and pole-mounted units include an adjustable bracket for setting detection angle during commissioning. Internal electronics are conformally coated and connected through sealed M12 or similar circular connectors rather than open terminals, keeping moisture out of the detection and output circuitry. Built-in transient voltage suppression is mounted near the cable entry to protect against lightning-induced surges, and the compact housing dimensions keep the unit unobtrusive at the holding position while still meeting the IP and temperature ratings needed for continuous outdoor exposure.
Technical Parameters
| Parameter | Typical Value |
|---|---|
| Detection Technology | FMCW Radar (24 GHz) or IR (active/passive) or Inductive Loop |
| Detection Range | 2‑15 metres (radar/IR), 1‑3 metres (inductive loop) |
| Field of View (radar/IR) | Typically 10°‑30° horizontal, 5°‑15° vertical |
| Target Detection Speed | 0.5‑50 km/h (walking to taxi speed) |
| Output Type | Dry contact (relay, NO/NC) or opto‑isolated transistor (PNP/NPN), 24 VDC |
| Response Time | ≤ 100 ms (from detection to output change) |
| Power Supply | 24 VDC (nominal, 18‑32 VDC) or 12 VDC |
| Power Consumption | 2‑10 W (radar/IR), < 1 W (inductive loop) |
| Operating Temperature | -30°C to +70°C |
| 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) or flush‑mount (inductive loop) |
| Dimensions (radar/IR) | Typical: 100 × 80 × 60 mm (housing) |
| Diagnostics | Status LED, fault output (optional), communication (RS‑485/Modbus) |
| Certifications | CE, FCC Part 15, EN 61000‑6‑2 / EN 61000‑6‑4 (industrial EMC immunity/emission) |
Electrical Requirements
| Requirement | Typical Value |
|---|---|
| Supply Voltage | 24 VDC (nominal, 18–32 VDC) or 12 VDC, from the local field distribution/control cabinet |
| Power Consumption | 2–10 W (radar/IR), < 1 W (inductive loop) |
| Cabling | Screened, direct-burial rated cable from the sensor to the local junction box/control cabinet |
| Circuit Protection | Regulated supply with dedicated fuse/breaker at the distribution point |
| Surge Protection | Built-in transient voltage suppression (TVS), up to 6 kV, supplemented by an external SPD on long cable runs |
| Insulation Resistance | ≥ 50 MΩ (megger test, cable-to-ground, at commissioning) |
| Earthing/Grounding | Sensor housing and cable screen bonded to the local earth grid |
| Fault Protection | Fault output/status LED, with annual power supply check per maintenance schedule |
Applicable Standards
ICAO Annex 14
Runway holding position requirements and safety systems
FAA AC 150/5340‑30
Runway Status Light System (RWSL) specifications
FAA AC 150/5345‑56
Specification for L‑890 Airport Lighting Control and Monitoring System (ALCMS)
EUROCAE ED‑87
MASPS for Advanced Surface Movement Guidance and Control Systems (A‑SMGCS)
Installation Requirements
Loop Slot Cutting & Sealing
CivilSaw-cut the slot for inductive loop sensors into the taxiway surface at the holding position, sealing the loop with a bitumen or epoxy compound once installed.
Post Mounting & Detection Alignment
MechanicalMount surface-mounted microwave/infrared heads on a short frangible post clear of wingtip clearance, aligning the detection zone to cover the full stop bar width without triggering on adjacent lanes.
Screened Cable Route
ElectricalHome-run detector output cabling on its own screened pair back to the REL/THL controller or Remote I/O, kept separate from lighting series-circuit cable.
Field Cabinet Termination
ElectricalTerminate the sealed M12 or similar circular connector at the field cabinet end per manufacturer procedure before the sensor is energised.
Pre-Commissioning Sign-off
DocumentationRecord sensor position, alignment, and cable route as-built before commissioning testing begins, given that a nuisance trip on this input directly drives a runway safety light.
Testing & Commissioning
Coverage Zone Calibration
Pre-EnergisationSet and lock detection angle and range so the coverage zone is confined to the stop bar area, avoiding false triggers from adjacent taxiways.
Power & Output Signal Check
EnergisationConfirm supply voltage at the sensor and verify the dry contact or transistor output changes state correctly on a test target.
Fail-Safe State Verification
Final AcceptanceSimulate a sensor fault and confirm the system defaults to the conservative (stop bar lit) state rather than assuming clear.
Target Classification Test
Final AcceptanceConfirm the sensor correctly detects aircraft/vehicle targets while filtering birds and debris to reduce false alarms.
RWSL Logic / PLC Interface Test
Final AcceptanceVerify detection state reaches the RWSL logic processor or PLC correctly via the Remote I/O or direct wiring path.
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, coverage zone settings, and fail-safe test results in the commissioning dossier for handover.
Inspection & Maintenance
Detection Accuracy Check
Semi-annualTest detection performance against known vehicle movements to catch false detections or missed calls early.
Sensor Lens / Aperture Cleaning
QuarterlyClean the sensor lens or radome 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 Detections from Adjacent Traffic
Radar and IR sensors may detect aircraft or vehicles on adjacent taxiways if the field of view is too wide. Careful alignment and, where possible, use of narrow beamwidth and range‑gating can mitigate this. Regular calibration is essential.
Sensor Obscuration (Radar/IR)
Snow, ice, heavy rain, or dirt accumulation on the sensor window can reduce detection performance. Regular cleaning and the use of heated housings or wipers can prevent obscuration.
Inductive Loop Damage
Buried inductive loops can be damaged by pavement resurfacing, ground movement, or heavy aircraft loads. Periodic loop testing (using a loop tester) is required to detect open or short circuits.
Interference from RF Sources
Radar sensors operating at 24 GHz can experience interference from other nearby radar systems (e.g., SMR, weather radar) or communication transmitters. Frequency coordination and filtering are necessary.
Power Supply Instability
Voltage fluctuations or spikes can cause sensor resets or damage. Use a regulated power supply and surge protection devices to ensure reliable operation.
Alignment Drift
Over time, sensor mounts can shift due to vibration or thermal expansion, altering the detection zone. Regular site surveys and alignment checks are recommended.
Troubleshooting Guide
False Detections from Adjacent Taxiway or Vehicle Traffic
Missed Detection in Adverse Weather (Sensor Obscuration)
Loop Detector Not Registering / Stuck Output
Erratic Readings Near Other Radar Systems
Detection Zone Drifted from Design Boundary
Failure Modes & Root Causes
Sensor Lens / Aperture Contamination
Sensor Obscuration in Adverse Weather
Inductive Loop Damage (Loop Variant)
Interference from RF Sources
Alignment Drift
Power Supply Instability
Safety & Operational Notes
Electrical Isolation Before Servicing
Electrical SafetyDe-energise the sensor's 24VDC (or 12VDC) supply from the local field distribution/control cabinet and verify zero energy before opening the housing or disconnecting cable.
Safety-Critical Function — Coordinate Before Isolating
OperationalThe sensor feeds real-time occupancy data to the RWSL system that activates runway entrance and take-off hold lights; taking it out of service removes that protection, so coordinate with ATC and raise a NOTAM before isolation, and confirm an interim procedure is in place for the affected stop bar.
Pavement/Embedment Work Coordination
OperationalExcavating or re-setting an embedded or inductive-loop sensor requires ATC/airside coordination, a NOTAM, and pavement closure, with the surrounding surface reinstated to the required load rating before reopening.
FOD Control
OperationalKeep tools, fasteners, and excavated material accounted for at all times when the sensor or its housing is open, and clear the area of debris before reinstating the surface.
Insulation Test Before Re-Energisation
Electrical SafetyTest the signal and power cabling for insulation integrity after any cable or connector work before restoring power, since a residual fault can produce a false occupancy indication rather than an obvious failure.
Restore to Compliant State
ComplianceVerify correct detection and a clean occupancy signal to the RWSL logic before closing out the work and cancelling the associated NOTAM.
Engineering & Expert Notes
A False-Clear Is More Dangerous Than a False-Occupied
DesignA sensor that fails to a "no occupancy" state on fault is a much worse outcome for RWSL logic than one that fails to "occupied," since the latter simply keeps hold lights on unnecessarily while the former can suppress a genuine warning; confirm the fail-safe direction of a replacement sensor matches the original before commissioning it.
Nuisance Trips Often Trace to Ground Loop Interference
TroubleshootingIntermittent false detections on an inductive-loop sensor are frequently caused by electrical noise coupling from adjacent series circuits rather than a fault in the sensor itself; check loop screening and separation from AGL power cabling before replacing hardware on a recurring nuisance-trip complaint.
Pavement Overlay Work Changes Loop Depth
MaintenanceA resurfacing or overlay project that adds pavement thickness above an embedded inductive loop can change its detection sensitivity even though the loop itself wasn't touched; re-verify detection performance after any pavement work in the vicinity, not just after work that directly disturbs the sensor.
Verify Against Real Traffic, Not Just a Bench Test
VerificationA sensor can pass a static bench or simulated-target test while still under-detecting a specific aircraft type's gear geometry or approach speed in service; where practical, confirm detection against actual traffic during commissioning rather than relying solely on a synthetic test signal.
Response Latency Matters as Much as Detection Accuracy
VerificationA sensor that correctly detects occupancy but reports it to the RWSL logic with excessive latency can still leave a hold light illuminating too late relative to the actual hazard; verify end-to-end response time during commissioning, not just detection accuracy in isolation.
Log Every Interim Procedure Used During Isolation
OperationalWhen a sensor is taken out of service and an interim manual procedure covers the affected stop bar, document exactly what that interim procedure was and confirm it was formally stood down when the sensor was restored; an interim procedure that quietly persists after restoration is a latent operational risk.
Frequently Asked Questions
Short answers about stop bar sensors: detection technology, placement, electrical requirements, standards and troubleshooting.
Q1What is a stop bar sensor?
A stop bar sensor is a compact detection device installed at runway holding positions to detect aircraft or vehicles approaching, crossing or occupying the stop bar area. It feeds the runway safety and stop bar control chain.
Q2How is it different from a runway occupancy sensor?
A runway occupancy sensor watches an entire runway segment. A stop bar sensor is narrower and more precise: it detects the exact moment a target crosses one specific holding position.
Q3Where are stop bar sensors installed?
At runway holding positions where stop bars are installed, such as taxiway and runway intersections, and in other critical areas where occupancy detection is required.
Q4What detection technologies do they use?
FMCW radar (typically 24 GHz), active or passive infrared, or inductive loops, alone or in combination.
Q5What are the typical specifications?
Radar or IR range of 2-15 m (1-3 m for inductive loops), detection speed 0.5-50 km/h, response time of 100 ms or less, dry-contact or opto-isolated 24 VDC output, IP65/IP67 protection and -30°C to +70°C operating temperature.
Q6How is a stop bar sensor powered and protected?
It runs on 24 VDC (18-32 VDC) or 12 VDC from the local cabinet, drawing 2-10 W for radar or IR. Screened cable, built-in transient suppression up to 6 kV, an external SPD on long runs, and earth bonding of the housing and cable screen are typical.
Q7Which standards apply?
ICAO Annex 14 (runway holding position and safety system requirements), FAA AC 150/5345-56 (L-890 ALCMS) and EUROCAE ED-87 (MASPS for A-SMGCS).
Q8How often should a stop bar sensor be maintained?
Quarterly lens or radome cleaning; semi-annual detection accuracy and alignment checks; and annual power supply stability checks and, for inductive loops, loop continuity and resistance tests.
Q9Why is a stop bar sensor giving false detections?
A common cause is a field of view too wide for the stop bar zone, picking up adjacent taxiway or vehicle traffic. Review alarm logs against known movements and check the beamwidth and range-gate settings.
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 Stop Bar Sensor selection, installation, or integration for your RWSL system?
Precision AGL Academy provides advice on sensor technology selection, placement, alignment, and field commissioning.
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 Stop Bar 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.