ATIS Interface Unit for Airport Weather Data

An ATIS interface unit provides an interface between airport meteorological and operational data systems and the airport’s Automatic Terminal Information Service (ATIS) environment. It collects, formats, transfers or distributes approved data from connected airport systems so the information can be made available to the ATIS application or an associated aerodrome information system.

Depending on the architecture, it can receive data from AWOS, RVR systems and transmissometers, wind sensors, visibility sensors, present weather sensors, atmospheric pressure data such as QNH, weather processors, runway status systems, airport operational databases and other approved data sources. Visibility sensors report meteorological optical range, and RVR is a separate data source.

Depending on the selected configuration, it performs data acquisition, validation, conversion, formatting, routing and communication. It can validate communication integrity, availability, validity and system status, format data for the receiving ATIS application, distribute it, and report communication failures, unavailable sources or equipment faults, depending on the system design.

Possible interfaces are Ethernet and TCP/IP-based communication, serial communication (RS-232, RS-422 and RS-485) and other manufacturer-specific digital interfaces. The actual protocol and physical interface for each connected system should be confirmed before procurement, and for third-party systems the compatibility should be verified using the approved communication protocol, data format, message structure and update-rate requirements.

Configure and test the wind direction reference, because ATIS and local routine reports use degrees magnetic while METAR uses true. Also set the pressure units (hPa or inHg) and the QNH or QFE value required, RVR and visibility reporting conditions with units in metres, and the averaging periods, since local routine and ATIS reports use a 2-minute mean wind and METAR a 10-minute mean (confirm against your Annex 3 edition). Include a time stamp and data age so stale readings are flagged, and a failed sensor should show as missing or invalid, never as zero.

The interface moves and formats data. The content of the broadcast message, and the decision to release it, stay with the air traffic services and the meteorological provider. The ATIS, wind display and ATS displays should be fed from the same validated source so all show matching values.

Define the number of meteorological data sources, RVR inputs, network connections and serial ports, any redundant interfaces, the data update frequency, input and output data formats, alarm and status outputs, the maintenance interface and remote monitoring requirements. This prevents interface limitations from becoming a constraint during system integration.

For network-connected installations the unit may operate within the airport’s secured IT infrastructure, so the design should consider network topology, IP addressing, segmentation, communication ports, data routing, redundancy, access control, remote maintenance, cybersecurity and time synchronization, in coordination with the airport’s IT and communications teams. For power, consider input voltage, AC or DC supply, power consumption, UPS where required, overcurrent and surge protection, earthing, power redundancy and backup power, following the airport electrical design and the manufacturer’s requirements.

Commissioning typically covers an equipment inspection, a power-up test, a communication test with the AWOS, RVR system, weather processor, ATIS application and airport network, and data validation to confirm information is received, validated, formatted and transferred correctly. Where permitted, simulate selected communication or input failures to verify the expected fault indication, and finish with an end-to-end test of the complete data path from the originating sensor or system through the interface unit to the ATIS application.

If no data is received, check the source equipment, cabling and interface status. If ATIS data is unavailable, check the network connection and interface diagnostics. Incorrect data suggests a data-format or configuration mismatch, so verify the protocol and data mapping. Intermittent communication suggests a network, cable or connector problem, a delayed update suggests a source or update-rate issue and a unit that does not start suggests a power supply or hardware fault. Use the approved system documentation and manufacturer procedures.

ATIS is an operationally important airport information service, and provisions may include redundant power supplies, dual network connections, redundant interface units, backup data sources, failover communication paths, health monitoring and automatic fault indication. Redundancy requirements should be established from the airport operational concept and system availability requirements rather than assumed as a standard feature.

Confirm the ATIS and AWOS system manufacturers and models, the RVR interface, the number of data sources, inputs and outputs, communication protocols, data formats and update rates, network architecture, redundancy, power supply, enclosure, installation location, environmental and cybersecurity requirements, remote monitoring, documentation, FAT/SAT requirements and spare parts. References may include ICAO Annex 3, Annex 11, Annex 14 Vol. I and Annex 15, ICAO Doc 9837 and Doc 9328, India Meteorological Department requirements, DGCA CARs and airport-specific ATIS specifications. Confirm the applicable edition during engineering and procurement.