Asylon Links Air and Ground Robots for USAF Aircraft Inspections
Asylon has received a contract from the Warner Robins Air Logistics Complex to continue development and demonstration of an autonomous aircraft inspection system for U.S. Air Force maintenance operations. The notable engineering point is not simply that a drone will inspect an aircraft. It is that the company is combining aerial mobility, ground mobility, autonomy software, and command-and-control into one inspection workflow aimed at routine maintenance use.
The system is called Multi-modal Autonomous Robotics for Inspection of Aircraft, or MARIA. It combines aerial and ground robots to perform general visual inspections of military aircraft with limited human intervention. Under the contract, Asylon plans to integrate its Guardian small unmanned aerial system, DroneDog quadruped unmanned ground vehicle, Range autonomy software, and the DroneIQ command-and-control platform.
That architecture matters because aircraft inspection is fundamentally a coverage, access, and data-management problem. Upper surfaces, vertical surfaces, landing gear areas, and the space around a parked aircraft do not all suit the same robot equally well. A small aerial system can help with reach and image capture around higher sections of the airframe, while a ground robot adds another mobility mode for areas where persistent close-in positioning and surface-level access are useful. The real systems challenge is coordinating those platforms so maintainers receive one usable inspection package rather than disconnected robot outputs.
MARIA is set up around that integration layer. Inspection results are delivered to maintenance personnel through a single interface. The system collects images, three-dimensional scans of aircraft surfaces, robot position and performance data, and other operational information. Maintainers can review findings through conventional inspection workflows as well as 3D digital models.
For maintenance organizations, that single-interface approach may be as important as the robots themselves. Aircraft inspection remains heavily dependent on trained personnel, and new automation only becomes practical when it fits existing review and sign-off processes. In broader aircraft MRO work, robotics programs have repeatedly shown that the hard part is not just moving a sensor around an airframe. It is tying sensing, localization, repeatable path execution, and data presentation into a workflow that technicians can actually use without creating another disconnected software island.
That is where MARIA appears to be positioning itself. The Guardian drone and DroneDog ground vehicle are only part of the stack. Range provides the autonomy layer for robot operation, while DroneIQ acts as the command-and-control and data environment. In practical terms, that means the program is testing whether multimodal robotics can support a repeatable inspection process instead of a one-off demonstration of mobile sensing hardware.
The Air Force maintenance angle also sharpens the relevance. Routine visual inspections are labor-intensive, and they can involve repetitive tasks and safety risks associated with manual access around large aircraft. The stated aim of the project is to make those inspections faster and more consistent while reducing workload and safety risks. That does not mean maintainers disappear from the loop. It means robotics may handle more of the image capture, scan collection, and positional repeatability, while human personnel review the results through established maintenance workflows.
That distinction is important across the wider aircraft-inspection robotics field. Multimodal systems are often discussed as part of a smart-hangar model, where drones, ground robots, sensors, and digital inspection records are connected rather than used as separate tools. In that model, aerial robots help solve access and viewpoint problems, while ground systems can contribute endurance, payload flexibility, and fewer operating constraints. The bottleneck is usually not whether a robot can move around an aircraft, but whether localization, data consistency, and workflow integration are good enough for real maintenance environments.
If MARIA proves effective in this setting, the contract could become more than a platform demonstration. It would suggest that autonomous inspection is maturing from isolated robotic hardware into a maintenance systems tool, one that links mobility, sensing, software, and review interfaces in a form maintainers can use. That is the more consequential shift for U.S. sustainment operations: not replacing inspectors, but building a robotics stack that can make routine aircraft inspection more repeatable, more digitized, and easier to scale across maintenance organizations.
The contract follows Asylon’s previously announced $24 million Series B funding round, which the company has said is being used to expand engineering, operations, and commercial teams and accelerate deployment of its autonomous robotics technologies. In this case, the more relevant takeaway is where that engineering effort is being applied: aircraft sustainment. For robotics in aviation maintenance, the decisive step is rarely the robot alone. It is whether the full control, sensing, and data chain can fit the discipline of real-world inspection work.
By Jonathan Barrett — Editor for AMI’s future mobility and autonomous systems section, with two decades covering robotics, e-mobility, drone-vehicle convergence, and transport mechanical systems.
