Time Synchronization / NTP Module
A dedicated precision timekeeping device that provides accurate, synchronized time to all AGL system components — including the ALCMS server, PLCs, workstations, and network equipment. The Time Synchronization / NTP Module ensures consistent timestamps across all system events, alarms, and data logs, enabling precise sequence-of-events (SOE) analysis, forensic investigation, and coordinated system responses.
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 Time Synchronization / NTP Module — also referred to as a network time server, NTP server, or GPS time server — is a dedicated device that distributes highly accurate, synchronized time to all network-connected devices in an AGL system. It acts as the authoritative time source for the ALCMS, PLCs, workstations, communication gateways, and any other equipment that requires accurate timekeeping for event logging, alarm correlation, and coordinated control.
Key characteristics of the Time Synchronization / NTP Module include:
- High-Precision Time Source: Typically synchronizes to an external reference such as GPS, GNSS (GLONASS, Galileo, BeiDou), or a high-accuracy internal oscillator (rubidium or OCXO) for autonomous operation during signal loss.
- Network Time Protocol (NTP) Server: Provides NTP (and optionally PTP — Precision Time Protocol) services to all network clients, ensuring time accuracy typically within 1–10 ms over the network.
- Multiple Output Formats: Supports various time distribution formats including NTP, PTP (IEEE 1588), SNTP, and hardware pulse-per-second (PPS) outputs for high-precision applications.
- Redundant Time Sources: Supports multiple GPS/GNSS inputs, external NTP peers, and internal holdover oscillators to ensure continuous time availability even in the event of a primary reference loss.
- Holdover Accuracy: Maintains accurate time for extended periods (hours to days) when the external reference is lost, using a high-stability oscillator (TCXO, OCXO, or rubidium).
- Web-Based Management: Provides an intuitive web interface for configuration, status monitoring, and diagnostics, including time source status, client statistics, and alarm logging.
- Secure Operation: Supports authentication (NTS — Network Time Security) and access control to prevent unauthorized time manipulation, protecting against cyber threats and ensuring time integrity.
In airfield lighting systems, the Time Synchronization / NTP Module is essential for correlating events across the entire AGL infrastructure. When a fault occurs (e.g., a CCR failure, lamp outage, or communication loss), the precise timestamps from all devices enable operators and maintenance teams to reconstruct the sequence of events accurately, identify root causes, and take corrective action efficiently.
Purpose & Function
The time synchronisation module's purpose is to extend a single accurate time reference out to every device on the network, so that the value of precise timing isn't limited to whichever equipment happens to have its own GPS antenna. A CCR controller, a PLC, an operator workstation, and a network switch all need to agree on the same time down to a few milliseconds if their combined logs are ever going to be read as one coherent story rather than several separately-plausible ones. The redundancy and holdover capability matter for a specific reason: if the network's shared time reference were to silently drift during a brief GPS outage, every downstream device would drift with it without any obvious warning, quietly undermining the very event correlation the whole system depends on — so the module's job is keeping that shared, trustworthy "now" available continuously, not just most of the time.
Where Is It Used?
The Time Synchronization / NTP Module is deployed in all AGL systems where accurate, synchronized time is critical for operations, maintenance, and safety. Key applications include:
- ALCMS Server Time Synchronization: Providing the authoritative time source for the ALCMS server, ensuring that all alarms, events, and operator actions are timestamped consistently.
- PLC and Remote I/O Synchronization: Synchronizing PLCs and remote I/O units to ensure that control actions and status changes are logged with accurate timestamps, enabling precise sequence-of-events (SOE) recording.
- Workstation and Operator Console Time: Ensuring that all operator workstations and control panels display the same, correct time, improving situational awareness and audit traceability.
- CCR Communication Interfaces: Synchronizing CCR communication interfaces to accurately timestamp status changes and alarms from Constant Current Regulators.
- Network Equipment Synchronization: Providing time to Ethernet switches, communication gateways, and fiber converters for accurate network event logging and troubleshooting.
- SCADA Integration: Providing synchronized time to SCADA systems that interface with the AGL system, ensuring that data from multiple sources is time-aligned.
- Sequence-of-Events (SOE) Logging: Enabling precise timestamping of SOE data, which is critical for fault analysis, post-incident investigation, and compliance reporting.
- Approach Lighting Sequencers: Synchronizing sequenced flashing lights and approach lighting systems to ensure precise timing and coordinated operation.
- RWSL (Runway Status Light) Systems: Providing accurate time for RWSL control logic, ensuring that light state changes occur at precisely the right moments during aircraft movements.
Installation & Location
The module is rack-mounted in the main equipment room alongside the ALCMS server and core network switches, positioned so its network connection reaches the core switch or router with the shortest possible hop count to the devices it serves. Its GPS or GNSS antenna is a separate component, mounted outdoors with a clear view of the sky — typically on the equipment shelter roof or a nearby mast — and connected back to the module by a dedicated coaxial or fibre antenna cable run in its own conduit, kept short enough to avoid excessive signal loss and separated from AGL power cabling to limit interference. Where a second GNSS input or external NTP peer is used for redundancy, that reference is fed from a physically independent antenna or network path so that a single antenna fault, cable cut, or lightning strike cannot take down both time sources at once. The module's own power feed is typically drawn from the same UPS-protected circuit as the ALCMS server, so a mains interruption does not itself introduce a gap in the time reference the rest of the system depends on.
How Does It Work?
The Time Synchronization / NTP Module operates as a precision time source and distribution hub, ensuring that all AGL system components are synchronized to a common time reference. Key functional aspects include:
- External Time Reference Reception: The module receives accurate time from an external reference, typically a GPS or GNSS receiver. The GPS/GNSS signal provides Coordinated Universal Time (UTC) with sub-microsecond accuracy. The module decodes the time, date, and position data from the satellite signals.
- Internal Oscillator and Holdover: The module uses a high-stability oscillator (TCXO, OCXO, or rubidium) to maintain accurate time when the external reference is lost. The oscillator is disciplined (slewed) to the external reference during normal operation, ensuring that the holdover accuracy remains within specification (e.g., better than 1 µs per hour).
- Time Processing and Distribution: The module processes the time reference and makes it available to network clients via NTP (Network Time Protocol) and/or PTP (Precision Time Protocol). It responds to client requests with the current time, adjusting for network latency using sophisticated algorithms.
- Hardware Time Stamping: Advanced modules include hardware timestamping capabilities (e.g., on the Ethernet PHY) to achieve sub-microsecond accuracy for PTP and NTP with hardware-assisted synchronization.
- Pulse-Per-Second (PPS) Output: The module provides a hardware pulse-per-second (PPS) output, which can be used by devices that require a precise second-edge synchronization (e.g., PLCs, RTUs, and data acquisition systems).
- Time Zone and Daylight Saving Management: The module applies the configured time zone and daylight saving rules, distributing the local time to clients as required. It also provides UTC time for applications that require a standardized reference.
- Client Monitoring and Authentication: The module logs all NTP/PTP client requests, allowing administrators to monitor which devices are synchronized and at what accuracy. It supports authentication mechanisms (NTS, MD5, or symmetric keys) to prevent unauthorized time manipulation.
- Redundancy and Failover: In critical installations, multiple time servers are deployed in a primary/backup configuration. The module supports peer-to-peer synchronization with other NTP servers, ensuring that a single point of failure does not compromise time accuracy.
The module is typically rack-mounted (19" 1U) and powered from a 120/230 VAC supply with redundant power inputs for high availability. It includes a front-panel display for status indication (time source, synchronization status, alarms) and may include a GPS antenna input (with surge protection) for outdoor antenna installation.
One Clock, Every Device & Control Logic
GPS / GNSS Receiver
UTC from satellites, sub-µs accuracy
Internal Oscillator
OCXO/rubidium — disciplined during lock, holds over on loss
Time Processing & Distribution
Serves NTP, PTP & SNTP; applies time zone / DST rules
ALCMS Server
Alarm & event timestamps
PLCs & Remote I/O
Sequence-of-events logging
CCR Interfaces
Status change timestamps
Network Equipment
Switches & gateways
Physical Construction
The module is built as a rack-mount (typically 1U) or DIN-rail chassis housing the timing electronics, an internal oscillator (often an oven-controlled crystal for holdover stability), and a GPS/GNSS receiver board connected to an external roof- or mast-mounted antenna via a dedicated coaxial feed with surge protection at the entry point. Network connectivity is brought out through standard RJ45 or fibre ports on the rear panel alongside the antenna connector and a power inlet, with the unit designed to sit in the same equipment room or cabinet as the ALCMS servers and PLCs it serves rather than in an outdoor enclosure. A front-panel display or status LEDs indicate GPS lock and synchronisation state, and internal battery backup for the real-time clock maintains reasonable timekeeping accuracy through short power interruptions or antenna signal loss.
Technical Parameters
| Parameter | Typical Value |
|---|---|
| Time Source | GPS / GNSS (GLONASS, Galileo, BeiDou) — multi-constellation receiver |
| Antenna Input | 50 Ω, SMA or TNC connector, with 5 VDC antenna power, surge protected |
| Network Interface | 1–2 x 10/100/1000BASE‑T (RJ‑45) — optional fiber SFP |
| Protocol Support | NTP (RFC 5905), SNTP (RFC 4330), PTP (IEEE 1588), Daytime (RFC 867), Time (RFC 868) |
| NTP Accuracy (LAN) | ±1–10 ms (typical), ±100 µs (with hardware timestamping) |
| PTP Accuracy (LAN) | ±100 ns (with hardware timestamping) |
| Holdover Accuracy | ±1 µs per hour (OCXO), ±1 ms per day (TCXO), ±1 µs per day (rubidium) |
| PPS Output | 1 x BNC (pulse-per-second, TTL level) |
| Time Display | Front-panel OLED or LCD display (time, date, source status, alarms) |
| Number of NTP Clients Supported | Up to 10,000+ (depending on model and network load) |
| Authentication | NTS (Network Time Security), MD5/SHA symmetric keys, access control lists (ACL) |
| Management Interface | Web GUI (HTTPS), SSH, SNMP (v2c/v3), syslog |
| Redundancy | Dual power inputs (hot‑swappable), redundant GPS/GNSS receivers (optional), NTP peer sync |
| Power Supply | 120/230 VAC ±10%, 50/60 Hz (dual redundant, hot‑swappable) |
| Power Consumption | 15‑40 W (depending on model and options) |
| Operating Temperature | -10°C to +55°C (industrial grade), -40°C to +70°C (ruggedized option) |
| Storage Temperature | -40°C to +85°C |
| Protection Class | IP20 (indoor rack‑mount), IP54 (with optional enclosure) |
| Mounting | 19" rack‑mount (1U or 2U), or DIN rail (compact models) |
| Dimensions (1U) | 482.6mm × 44.5mm × 300mm (W × H × D) |
| Certifications | CE, FCC, UL, IEC 61000‑6‑2 (EMC immunity), NIST (time source traceability) |
Electrical Requirements
| Requirement | Typical Value |
|---|---|
| Circuit Type | Equipment-room/control-room low-power supply, independent of the airfield series lighting circuit |
| Supply Voltage | 120/230V AC ±10%, 50/60 Hz, dual redundant hot-swappable inputs |
| Antenna Power | 5V DC supplied over the antenna cable, surge protected at the module input |
| Backup Supply | Dual power inputs allow feed from separate UPS-backed circuits for redundancy |
| Cable Type | Screened antenna coax and network cabling, routed separately from AC power wiring |
| Earthing/Grounding | Chassis and antenna cable shield bonded to the equipment-room earth |
| Fault Protection | Surge protection on antenna and network inputs; loss-of-source and power-input-failure reported via SNMP/alarm output |
Applicable Standards
RFC 5905
Network Time Protocol (NTP) — core specification for time synchronization over IP networks
IEEE 1588
Precision Time Protocol (PTP) — high-precision time synchronization for industrial networks
IEC 61850
Communication networks for power utility automation — includes time synchronization requirements
FAA AC 150/5345‑56
Specification for AGL control and monitoring equipment (time synchronization requirements)
Installation Requirements
Rack Mounting in Equipment Room
CivilRack-mount the module in the main equipment room alongside the ALCMS server and core network switches, positioned for the shortest possible hop count to the devices it serves.
Antenna Siting with Clear Sky View
CivilMount the GPS/GNSS antenna outdoors with a clear view of the sky — typically on the equipment shelter roof or a nearby mast — where it will not be shadowed by structures or vegetation.
Antenna Cable Routing
ElectricalRun the coaxial or fibre antenna cable in its own conduit, kept as short as practical to avoid excessive signal loss and separated from AGL power cabling to limit interference.
Redundant Reference Independence
ElectricalWhere a second GNSS input or external NTP peer provides redundancy, feed it from a physically independent antenna or network path so a single antenna fault, cable cut, or lightning strike cannot take down both time sources at once.
Network Connection to Core Switch
ElectricalConnect the module's network interface to the core switch or router serving the ALCMS and dependent devices.
UPS-Protected Power Feed
ElectricalDraw the module's power feed from the same UPS-protected circuit as the ALCMS server, so a mains interruption does not itself introduce a gap in the time reference.
Lightning Protection Check
MechanicalConfirm the antenna cable run includes appropriate surge/lightning protection at the building entry point, given its outdoor, elevated antenna position.
Pre-Commissioning Sign-off
DocumentationRecord rack position, antenna location and cable route, network connection, and power feed as-built before the installation is closed out.
Testing & Commissioning
Time Source & Accuracy Verification
EnergisationConfirm the module synchronises to its reference time source (GPS, upstream NTP/PTP server) and holds accuracy within the specified tolerance.
Network Connectivity Test
EnergisationVerify the module's network interface reaches all client devices on the AGL monitoring network and responds to time requests.
Failover & Holdover Test
EnergisationDisconnect the primary time reference and confirm the module correctly enters holdover mode and reports the resulting alarm.
Insulation Resistance Test
Pre-EnergisationMegger-test power and network wiring to the module before energisation, confirming insulation resistance clears the acceptable minimum.
Client Synchronisation Check
Final AcceptanceConfirm downstream CCR monitors, panels, and logging systems show correctly synchronised timestamps after commissioning.
Documentation & As-Built Sign-off
Final AcceptanceRecord accuracy, failover, and client synchronisation results in the commissioning dossier for handover.
Inspection & Maintenance
GPS/GNSS Antenna & Feedline Check
AnnualInspect the antenna, feedline, and surge protector for corrosion or moisture ingress, since a degraded feed forces the module into holdover.
Time Accuracy Verification
Semi-annualConfirm NTP/PTP output accuracy against a traceable reference to catch oscillator drift before it affects downstream event timestamps.
Holdover Performance Test
AnnualSimulate a GNSS signal loss to confirm the internal oscillator holds accuracy within spec for the expected outage duration.
Redundant Power & GNSS Receiver Test
Semi-annualRemove each hot-swappable power input in turn, and where fitted, confirm the redundant GNSS receiver takes over cleanly.
Authentication & Access Review
AnnualVerify NTS or symmetric-key authentication and access control lists remain correctly configured to prevent time-source spoofing.
NTP Client Load Review
QuarterlyCheck active client count and query load against the rated capacity so the module doesn't degrade in accuracy under peak demand.
Firmware & Log Review
Semi-annualCheck for validated firmware updates and review syslog and SNMP alarms for recurring synchronisation errors.
Display & Alarm Function Test
QuarterlyConfirm the front-panel display shows correct time, date, and source status, and that alarms trigger correctly on a simulated source failure.
Common Field Issues
GPS/GNSS Signal Loss
GPS signal loss can occur due to antenna obstruction, cable degradation, or atmospheric conditions. When the primary time reference is lost, the module enters holdover mode. Ensure the antenna has a clear view of the sky, use high-quality low-loss coaxial cable, and verify the module's holdover accuracy meets the application's requirements. Consider using redundant GPS/GNSS receivers or a secondary time source (e.g., a cellular network time source).
Network Congestion and NTP Latency
Heavy network traffic can introduce latency and jitter, affecting NTP accuracy. Use dedicated VLANs for time synchronization traffic, prioritize NTP packets using QoS, and ensure that the network infrastructure supports hardware timestamping (e.g., PTP) for high-precision applications. Monitor NTP client offsets and adjust poll intervals to optimize performance.
Time Zone and Daylight Saving Misconfiguration
Incorrect time zone or daylight saving settings can cause timestamps to be off by an hour or more. This can affect event correlation and compliance logging. Always verify the time zone and daylight saving rules during commissioning. Use UTC for internal logging and apply the local time zone only for user display.
Antenna Cable Degradation
GPS antenna cables exposed to weather can degrade over time, leading to signal attenuation and loss of synchronization. Use high-quality, low-loss cable (e.g., LMR-400 or equivalent) with proper weatherproofing. Periodically check the cable for damage and replace it if the signal strength drops below the specified threshold.
Security Vulnerabilities (NTP Amplification)
NTP servers can be used in DDoS amplification attacks if not properly secured. Restrict NTP access to authorized clients using access control lists (ACLs). Enable NTS (Network Time Security) or symmetric key authentication to prevent unauthorized time manipulation. Regularly update the firmware to patch known vulnerabilities.
Holdover Time Exhaustion
If the module operates in holdover mode for an extended period (e.g., days or weeks), the time error may accumulate and exceed the acceptable tolerance. Monitor the holdover duration and accuracy, and consider installing a secondary time source (e.g., a second GPS receiver or a cellular time service) to provide redundancy.
Software Version Incompatibility
Mixing NTP/PTP clients with different software versions or operating systems can cause interoperability issues. Ensure all clients are using a compatible NTP implementation (e.g., ntpd, chrony, or Windows Time Service) and that the firmware version on the NTP module is up to date. Test the system in a staging environment before deployment.
PTP Unicast Negotiation Failures
In PTP unicast mode, the time server may not respond to client requests if the negotiation fails. Verify that both the server and client are configured with the correct unicast negotiation parameters. Use the default multicast mode for simpler deployments and switch to unicast only when required.
Troubleshooting Guide
Module in Extended Holdover Mode
Client Time Offsets Growing or Jittery
Logged Events Off by an Hour or More
Repeated Signal Attenuation from the GPS Antenna
Unexpected Load or Suspicious Traffic on the NTP Service
PTP Clients Fail to Synchronise in Unicast Mode
Failure Modes & Root Causes
GPS Antenna Signal Loss
Internal Oscillator Drift
Time Zone / Leap Second Misconfiguration
Antenna Cable Signal Attenuation
Unauthorised Access / Suspicious Network Traffic
PTP Unicast Negotiation Failure
Safety & Operational Notes
Circuit Isolation Before Internal Work
Electrical SafetyDe-energise and lock out the module's power feed before opening its enclosure or disconnecting internal wiring, and verify zero energy before handling connections.
GPS/GNSS Antenna Work at Height
Personnel SafetyUse appropriate fall protection when accessing a roof- or mast-mounted GPS/GNSS antenna, and confirm the antenna feed is disconnected from the module before disturbing antenna connections.
Confirm Standalone Holdover Before Isolating
OperationalBefore taking the module out of service, confirm downstream systems can tolerate a loss of the authoritative time source, or that a standby time source is available, since alarm correlation and event logging across the ALCMS depend on synchronized time.
Verify Time Distribution After Maintenance
ComplianceAfter maintenance, confirm the module is correctly distributing time to the ALCMS, PLCs, and other connected equipment before closing out the work, not just that the module itself has re-acquired its reference source.
PPE & Grounding
Personnel SafetyUse appropriate PPE and confirm the module chassis and antenna cabling are bonded/grounded and surge-protected per the electrical design before reconnecting.
ESD Precautions
Personnel SafetyUse anti-static handling precautions when removing or inserting cards or modules within the unit, since its internal oscillator and timing electronics can be damaged by electrostatic discharge.
FOD Control at the Enclosure
OperationalKeep tools and fasteners accounted for at all times when the unit or its antenna mount is open, and secure or remove any loose material before closing it.
Restore to Compliant State
ComplianceDo not leave the module reporting an unsynchronised or degraded reference source after maintenance; confirm it has re-acquired a valid time source before closing out the work.
Engineering & Expert Notes
A Degraded GNSS Signal Can Look Like a Healthy Lock
ElectricalA module can report a GPS/GNSS lock while actually tracking a marginal number of satellites or a poor-geometry fix, producing time output that's technically synchronised but with reduced accuracy; check satellite count and fix quality, not just lock status, when investigating a suspected timing discrepancy.
Holdover Accuracy Degrades With the Module's Internal Oscillator Age
ComplianceAn oscillator's holdover performance during a lost reference signal degrades gradually as the oscillator ages, even though the module may have passed its holdover spec when new; factor oscillator age into how much holdover time you can actually rely on for a given unit.
Antenna Feed Surge Protection Is Separate From Power Surge Protection
ElectricalA module can have adequate surge protection on its power input while its GNSS antenna feed, exposed at a roof or mast location, remains vulnerable to induced surges from nearby lightning activity; verify both paths are protected independently.
One Module's Fault Can Desynchronise Alarm Correlation Across the Whole ALCMS
DesignBecause downstream systems rely on this module as their authoritative time source, a subtle drift here doesn't just affect the module's own logs; it can misorder or misalign alarm and event timestamps across every connected system, making incident review confusing well after the module itself is fixed.
ESD Precautions Matter More on Timing Cards Than General Logic Cards
HandlingThe precision oscillator circuitry on a timing module can be more sensitive to electrostatic discharge damage than typical digital logic, with damage sometimes manifesting only as gradually worsening timing accuracy rather than outright failure; treat ESD handling as non-negotiable even for a "quick" card swap.
Verify Time Distribution End-to-End, Not Just at the Source
TroubleshootingConfirming the module itself has reacquired a valid reference doesn't confirm every downstream PLC and ALCMS component is actually receiving and applying the corrected time; check timestamps at a sample of downstream devices before closing out the work.
Frequently Asked Questions
Short answers about time synchronisation / NTP modules in AGL systems: what they do, accuracy, holdover, antenna siting, standards, maintenance and common faults.
Q1What is a time synchronisation / NTP module?
It is a dedicated network time server, also called an NTP server or GPS time server, that distributes accurate, synchronised time to network-connected devices in an AGL system. It is the authoritative time source for the ALCMS, PLCs, workstations, communication gateways and other equipment that needs accurate timekeeping.
Q2Why does an AGL system need synchronised time?
A CCR controller, PLC, operator workstation and network switch must agree on the time to within a few milliseconds if their logs are to be read as one coherent story. Consistent timestamps allow event logging, alarm correlation, sequence-of-events recording and coordinated control.
Q3How does the module get its time?
It receives UTC from a GPS or GNSS receiver (GLONASS, Galileo, BeiDou), which provides sub-microsecond accuracy, then serves that time to the network. A multi-constellation receiver is typical.
Q4What happens if the GPS signal is lost?
The module enters holdover mode and keeps time with its internal oscillator. Typical holdover accuracy is about ±1 µs per hour for an OCXO, ±1 ms per day for a TCXO and ±1 µs per day for rubidium. Extended holdover usually points to an obstructed antenna, degraded cable or atmospheric conditions.
Q5How accurate is NTP compared with PTP?
Typical LAN accuracy is ±1–10 ms for NTP, or about ±100 µs with hardware timestamping. PTP (IEEE 1588) reaches about ±100 ns with hardware timestamping.
Q6Which protocols does the module support?
NTP (RFC 5905), SNTP (RFC 4330), PTP (IEEE 1588), and the Daytime (RFC 867) and Time (RFC 868) protocols. It supports 10,000+ NTP clients depending on model and network load, with a 1 PPS BNC output.
Q7Where should the module and its antenna be installed?
The module is rack-mounted in the main equipment room next to the ALCMS server and core switches, with a short network path to the devices it serves. The GPS/GNSS antenna is mounted outdoors with a clear view of the sky, typically on the shelter roof or a nearby mast, and connected by dedicated coax.
Q8How is the module protected against spoofing?
It supports NTS (Network Time Security), MD5/SHA symmetric keys and access control lists. Authentication and access settings should be reviewed regularly so time-source spoofing is prevented.
Q9Which standards apply to time synchronisation modules?
The main references are RFC 5905 (NTP), IEEE 1588 (PTP), IEC 61850 (communication networks for power utility automation, including time synchronisation) and FAA AC 150/5345-56 (AGL control and monitoring equipment). Always verify the current edition and your approved requirements.
Q10How often should the module be maintained?
Typical intervals are quarterly for NTP client load review, semi-annual for time accuracy verification and redundant power and GNSS receiver tests, and annual for antenna and feedline checks, holdover performance tests and authentication and access review. Your approved maintenance programme takes precedence.
Q11Why are my client time offsets growing or jittery?
Network congestion is usually adding latency and jitter to NTP traffic. Monitor client offsets and round-trip delay, then move time-sync traffic to a dedicated VLAN and apply QoS prioritisation to NTP and PTP packets.
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 Time Synchronization / NTP Module selection, deployment, or integration for your AGL network?
Precision AGL Academy provides advice on time source selection, network design, redundancy planning, and best practices for accurate, reliable time synchronization.
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 Time Synchronization / NTP Module 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.