IN Brief:
- Aeronix has introduced a flight-tested Platform Interface Module implementing the US Army’s Picatinny Common Lethality Integration Kit standard.
- The module provides a common electrical interface for power, communications and safety functions between unmanned platforms and compatible payloads.
- Aeronix reports multiple flight tests, dozens of inert payload releases and initial integration onto a test aircraft in less than five minutes.
Aeronix has launched a Platform Interface Module designed to simplify the integration of mission payloads with uncrewed aircraft and other unmanned platforms. The flight-tested device implements the Picatinny Common Lethality Integration Kit (CLIK) standard developed by the US Army’s DEVCOM Armaments Center, providing a common electrical interface between an existing platform and compatible equipment. Aeronix says the module has completed multiple flight tests, including dozens of releases involving inert payloads, and is available for integration and further demonstrations with platform and payload manufacturers.
A payload supplied for one uncrewed aircraft may need different power, communications and control interfaces on another, increasing the integration work for manufacturers. Aeronix’s approach places an interface component between the host platform and the payload, allowing the existing systems to communicate through an implementation of the common CLIK specification.
Picatinny CLIK was developed in response to the growing number of unmanned aircraft and modular payloads entering military development programmes. The standard establishes requirements covering attachment, electrical power, communications, control and safety functions. Its purpose is to provide a defined boundary between the vehicle and the equipment it carries, reducing the number of separate interfaces that manufacturers must engineer. The Armaments Center has also drawn on earlier modular payload architectures, including the Small Universal Payload Interface, in developing the specification.
Within the CLIK architecture, Aeronix’s module bridges the electrical and data interfaces between an existing host vehicle and compatible payload equipment. Power from the aircraft must be made available in a form compatible with the connected payload, while command and status information must be exchanged between the relevant control systems. The module therefore performs a bridging function between equipment developed around different arrangements. Individual platforms will still require mechanical, electrical and software integration checks before the module can be accepted for service.
Where a payload has functions requiring dedicated safety controls, the interface must preserve the necessary command, status and authorisation signals. Commands issued from a ground control station need to travel through the platform’s communications and control systems before reaching the connected equipment, while the status of that equipment must be represented accurately to the operator. Picatinny CLIK includes provisions for safety-critical signals as part of its defined interface architecture. Aeronix has drawn on its existing experience in launcher control electronics and weapons integration when developing the module.
The new component uses a software-reconfigurable architecture, allowing its interface functions to be adapted to different requirements without automatically replacing the underlying hardware. That flexibility can reduce the amount of redesign associated with a changed payload or a revised host platform, although it also creates requirements for configuration control and software verification. An interface that has been tested successfully with one arrangement still needs to be assessed against the characteristics of the equipment connected to it during subsequent integration work.
Aeronix reports that its Platform Interface Module was installed on the test platform in less than five minutes during initial integration, with power and communications established through the new arrangement. The company subsequently completed multiple flight tests and dozens of releases using inert payloads. These demonstrations provide evidence of the module operating in flight rather than remaining a laboratory prototype, but Aeronix has not disclosed a complete test matrix, independent certification results or a catalogue of qualified aircraft and payload combinations.
The module has been designed with a low size, weight and power requirement, reflecting the restrictions encountered when adding equipment to smaller unmanned platforms. Every additional component consumes space and electrical capacity, while its mass can influence the available payload allowance and the vehicle’s operating characteristics. An interface intended to support multiple equipment types must therefore balance functional flexibility with the physical resources available on the host platform. Aeronix has not published the new module’s complete dimensions, mass, electrical consumption or environmental qualification limits.
Although the CLIK specification covers physical attachment, electrical compatibility alone cannot establish that an airframe can safely carry a particular payload. Payload mass, mounting loads, centre of gravity and the manufacturer’s approved operating limits continue to influence integration decisions. The ability to reuse a standardised electrical arrangement therefore reduces one part of the engineering workload without removing all requirements for mechanical assessment, testing and system safety approval.
Aeronix began developing CLIK-compatible solutions through collaboration with unmanned aircraft specialists, including a January 2026 agreement with SafeSky Systems USA. That relationship brought together Aeronix’s communications and interface expertise with SafeSky’s work on unmanned aircraft and payload deployment equipment. The commercial launch represents a further development beyond the earlier collaboration, making a specific flight-tested module available for evaluation by other equipment manufacturers. However, no production quantity, customer purchase contract or delivery programme has been disclosed with the launch.
As manufacturers adopt common interfaces, interoperability will depend on the consistency with which individual products implement the standard and the way changes are managed over their working lives. Standardised communications and power arrangements can reduce repeated design work, but compatible hardware still requires appropriate configuration, qualification and testing before it enters a particular service application. Aeronix’s Platform Interface Module provides an implemented component for that process, with wider adoption dependent on subsequent integrations and the acceptance requirements of customers using Picatinny CLIK equipment.
