IN Brief:
- Gecko Robotics has secured a five-year U.S. Navy IDIQ contract with a $71 million ceiling and an initial award of up to $54 million.
- Work begins on 18 Pacific Fleet ships, using climbing, crawling, and flying robots to inspect hulls, decks, welds, and confined spaces.
- The industrial significance is not only faster inspection, but a shift toward digital, condition-based naval maintenance that could change repair planning and shipyard workload.
The U.S. Navy’s latest deal with Gecko Robotics is nominally an inspection contract, but it lands squarely in the middle of the naval maintenance-industrial problem. Under the five-year IDIQ, worth up to $71 million, Gecko will begin work on 18 ships in the Pacific Fleet, with destroyers, amphibious warships, and littoral combat ships included in the first wave.
The company’s robots climb hulls, crawl through ballast tanks, and fly through confined spaces, collecting structural and material data that feeds its software platform. The promise is straightforward: find defects earlier, prioritise repairs faster, and reduce the maintenance delays that leave ships unavailable when demand is rising.
For naval readers, the most interesting part is not the novelty of the machines. It is the fact that robotic inspection is being scaled from an interesting capability into a programme-level maintenance input. That changes the conversation from technology adoption to industrial workflow.
Gecko says its tools can identify repairs up to 50 times faster and more accurately than manual inspection, and has cited a case in which a robotic evaluation of a flight deck removed more than three months of potential maintenance delay. Even allowing for the usual performance caveats, the direction of travel is clear. The Navy is looking for ways to convert inspection from a labour bottleneck into a repeatable data pipeline.
That fits the wider readiness pressure. The company has linked the contract to the Navy’s target of reaching 80% fleet readiness by 2027, and the work has been structured so other services can access the vehicle as well. Once that kind of contract structure is in place, the technology stops being a one-off experiment and starts competing to become standard practice.
From inspection labour to data pipelines
Traditional inspection still depends heavily on experienced humans entering difficult spaces, documenting condition, and turning observations into maintenance action. That is slow, difficult to standardise, and vulnerable to data loss between inspection, planning, and repair execution. Robotics does not remove skilled labour from the process, but it can shift where that labour is applied.
If robots and fixed sensors can gather repeatable high-resolution condition data, then engineers, planners, and yard teams spend less time hunting for problems and more time defining repair scope. In ship repair, that matters because uncertainty is expensive. Availability slips when defects are discovered late, work packages expand unexpectedly, or yards wait for validated condition data before committing labour and material.
The digital-twin logic behind the Gecko approach therefore has industrial consequences. A vessel with current, structured condition data is easier to plan around than one that arrives with incomplete inspection records and a long list of unknowns. For fleets under pressure, that can matter as much as the inspection hardware itself.
What scaling robotics means for naval maintenance
The contract also says something about production on Gecko’s side. The company has said it currently operates roughly 250 robots across commercial and government customers and plans to build another 50 to 60 this year. That implies an expanding manufacturing and support requirement of its own — more robots, more sensors, more calibration, more data handling, and more field deployment capability.
For the Navy, the harder question is whether yards and maintenance commands are ready to absorb the output. Robotic inspection only improves readiness if the data feeds directly into class-approved repair methods, procurement of replacement material, dock scheduling, and available labour. Otherwise, it risks becoming another layer of information without corresponding action.
Still, the Pacific Fleet award shows the service is willing to treat robotics as part of maintenance infrastructure rather than a side experiment. That matters because warship readiness is increasingly shaped by the industrial system behind the fleet — repair pipelines, inspection quality, and the speed at which condition data becomes executable work.
In that sense, the Gecko contract is less about robots climbing steel than about the Navy trying to industrialise foresight. For fleets that spend too much time waiting for maintenance windows, that is a serious proposition.
