Out and Back: Accelint's MV-20 Completes Multi-Day Endurance Run in Gulf of America

On February 18, 2026, Accelint launched the MV-20 small unmanned surface vehicle from its integration facility in Panama City Beach, Florida, into the Gulf of America for a multiday endurance run conducted in support of the Office of the Under Secretary of Defense for Research and Engineering's rapid prototyping and assessment for joint experimentation. The MV-20 completed the mission, and what the team learned along the way is shaping what comes next.

Before the Run: Months of Preparation

Turning a platform into a multi-mission-capable system takes time. The Accelint team spent months at the Panama City facility installing electronic LRUs, edge compute capabilities, routing cable harnesses, outfitting the sensor tower, and completing a rigorous engine break-in process before the vessel was ready for open-water testing.

The team also completed extensive on-water testing and lessons learned ahead of the endurance run, including shakeout runs to validate autonomy behaviors, stress C2 links, and verify propulsion and sensor performance in operational conditions. By February 18, the MV-20 had already accumulated meaningful hours on the water. The endurance run was a milestone, not a first attempt.

"This wasn't a lab test — it was a real-world, operational, checkout. We launched the MV-20 into the Gulf, handed it off to autonomous control, and it went. No hand-holding, no continuous intervention. That's what we built it to do." — Ben Pinx, Sensors & Autonomous Solutions, Accelint

The Run: 300+ Miles of Autonomous Operations

The MV-20 launched from various docks around the Panama City Beach area and transited to the Gulf under its own power - arriving on station ready to execute. From there, it transitioned from manual control to remote operation to sustained autonomous operations during the full run. Sea states reached three to four — conditions the vessel is designed to handle — and the platform performed as designed throughout.

Every C2 handoff went according to plan. Engine health, temperature, and system telemetry all behaved within expected parameters. Once launched and tasked, the MV-20 maintained its mission — no continuous course correction, no intervention required to keep it on task.

Operating in Contested Environments: What the Data Revealed

Defense acquisition requirements consistently ask how systems perform when GPS is degraded, communications are jammed, and the environment is actively working against the mission. The endurance run generated real data against those requirements.

The team evaluated line-of-sight performance of the SILVUS radio suite and assessed assured PNT behavior throughout the run. The results are now informing how the MV-20's PACE (Primary, Alternate, Contingent, Emergent) communication plan is structured for future missions.

Sensor data collected during the run is also feeding the broader partner ecosystem. Maritime imagery gathered across varying sea states is being used to improve Striveworks' aided target recognition (ATR) models — data that improves detection accuracy whether the sensor is on a USV, a helicopter, or a ground platform. The endurance run generated training data that will make the whole system sharper.

Finding Problems Before They Find You

The team conducted UMAA (Unmanned Maritime Autonomy Architecture) compliance testing during the run, validating that the MV-20's open systems architecture integrates with third-party C2 systems — a requirement explicitly called out in government RFPs, and one where the MV-20's design approach is paying dividends and warfighter life-cycle cost savings.

When an issue surfaced during a planned off-water period in the test sequence, the team traced it to a vendor specification deviation, corrected it, and updated their processes to prevent recurrence. The vessel was back on schedule.

"This is why the Army takes ISR ground robotics out and leaves them on station for five or six days before a mission. You're collecting data. You're hardening systems. You're building the troubleshooting guide a sailor will rely on when something goes wrong in the field." — Ben Pinx, Sensors & Autonomous Solutions, Accelint

Multi-Mission Capability: Built In, Not Bolted On

The endurance run used a block-zero payload configuration: radar, cameras, FLIR, Starlink, and SILVUS radios. The payload bay carried surrogate weight in lieu of mission-specific packages - a deliberate choice to validate baseline platform performance before layering in operational payloads.

The payload architecture is already designed and ready. Standardized interfaces for power, communications, and data mean that ISR, EW, kinetic, and other mission packages can be integrated rapidly and swapped between tasking. The MV-20 was built to be an open systems architecture, rapidly reconfigurable, not purpose-locked to a single mission.

"The MV-20 wasn't built for one job. You can show up with a fleet of these and configure each one for a different mission — ISR, EW, CLASS I-X resupply, CASEVAC, kinetics — and re-task them dynamically while they're underway. That flexibility is what makes this platform relevant across the threat environment, not just in one scenario." — Ben Pinx, Sensors & Autonomous Solutions, Accelint

Consider what that enables operationally for multi-mission needs: a CASEVAC pickup in a littoral environment, with ISR running simultaneously, an EW effector denying enemy detection during the approach, and targeting data flowing back to a command element throughout. Multiple missions, one hull.

The Government Team That Made It Happen

The endurance run was a team effort. The Honorable Emil Michael (Under Secretary of War for Research and Engineering and Chief Technology Officer for the Department of War), Dan Cabel (Director of Joint Maritime Next Capabilities at OUSW R&E) and the team at Naval Surface Warfare Center Panama City — led by Holly Van Camp and Erica Davis — coordinated across organizations to execute a complex, multi-week independent test event with genuine rigor.

“The OUSW R&E NSWC PC teams were outstanding — patient, rigorous, and genuinely invested in proving the capability. The challenges they put in front of us made the platform better. You couldn’t ask for a better customer to work with.” — Ben Pinx, Sensors & Autonomous Solutions, Accelint

The government team is now developing an assessment memo documenting the results — a validated record that will allow other Maritime programs and DoD organizations to treat the MV-20 as a proven multi-mission maritime platform and rapidly providing warfighter joint operational problem solutions.

What Comes Next

The MV-20 program continues into a full schedule of 2026 demonstration events, each designed to validate new mission threads, stress the platform in new environments, and push the capability further. Every run generates data, and every data point makes the system sharper.

The work of building a truly autonomous, truly multi-mission maritime platform is iterative by nature — and Accelint team with warfighter collaboration is moving fast. The MV-20 was awarded under a competitive OUSW R&E contract, and the Gulf endurance run is the proof point that moves it toward programs of record.

‍