Shield AI Inc

08/17/2026 | Press release | Distributed by Public on 08/17/2026 12:16

How V-BAT Earns Operational Trust

Two V-BATs sat on the deck aboard the Italian Coast Guard patrol vessel Dattilo, ready for a maritime surveillance mission run by Frontex, the European Border and Coast Guard Agency.

Long before the aircraft reached Dattilo, Shield AI and Global Sat Tech, the operator, began working with the Italian Civil Aviation Authority (ENAC) to secure authorization for the mission. That authorization depended on more than the aircraft itself. ENAC evaluated the specific aircraft configuration, the crews, the operating procedures, and the mission plan. That process ultimately resulted in a Specific Assurance and Integrity Level III (SAIL III) authorization, the highest authorization to date in Europe for unmanned maritime operations.

V-BAT brought an established operating record to the mission. It had already deployed aboard U.S. Navy and U.S. Coast Guard vessels, flown in the Aegean, and operated daily in Ukraine against heavy electronic jamming. It was also in service with the Royal Netherlands Navy and under contract in Poland. Japan selected V-BAT as a maritime-based ISR platform, while India selected it for operations with the Indian Army.

That operational record did not automatically authorize the mission aboard Dattilo. Before the mission could begin, the team had to demonstrate three things:

  • Airworthiness: the aircraft matched a tested and documented configuration and was safe to fly
  • Mission readiness: the aircraft, crews, and support system could sustain the mission
  • Operational authorization: the specific operation met ENAC's requirements for safe flight

Those three requirements are a big part of how V-BAT earns operational trust. The Dattilo mission shows how they come together in practice.

What Does Airworthiness Actually Mean?

Airworthiness is often described as whether an aircraft is safe to fly.

This is accurate, but it also means something more specific: the aircraft operating in the field must be the same aircraft engineers designed, tested, and documented.

The work starts before anything ships. Every V-BAT completes acceptance testing defined by our flight-test and engineering teams before delivery. Ground checks come first, followed by five flight-test cards with clear pass-or-fail criteria. No V-BAT leaves the factory until it completes all of them.

The same discipline applies when the aircraft changes. Aircraft evolve throughout their service life. A customer may add a sensor that affects weight, power demand, or flight behavior. At our test ranges spanning the environmental envelope, our teams evaluate the modified aircraft, confirm that it performs as expected, and update the supporting manuals, procedures, training materials, and technical evidence before it reaches the customer.

Documentation is not the end product or the goal. It is the record linking the aircraft in the field to the aircraft that engineers tested and validated. If the aircraft changes but its documentation does not, crews may follow procedures written for a different configuration, creating both a compliance gap and a safety risk.

Airworthiness therefore does not end with a factory test or a single approval. It is the ongoing work of keeping the aircraft, its configuration, and the way crews operate it aligned throughout its service life.

V-BAT Is Ready Any Day, Any Time

Mission readiness answers a different question: will it be ready when operators need it? Reliability is one of the main drivers of that readiness. It begins with aircraft design, continues through production, and improves through operational experience.

Design decisions can simplify maintenance, reduce failure points, and make it easier for crews to keep the aircraft flying over years of service. As an example, for the V-BAT Heavy Fuel Variant, we redesigned the electrical architecture and wiring harnesses, reducing the number of electrical connections on the aircraft. That means fewer potential failure points and fewer connections for maintainers to troubleshoot at 2 a.m. on a pitching deck.

Those improvements add up. Across its operating life, V-BAT has maintained a mission-readiness rate above 98 percent. That level of readiness depends on more than engineering. It also takes people. Our field service representatives deploy alongside customers worldwide, working directly with operators and maintainers to troubleshoot issues, return aircraft to service, and bring lessons from the field back to our engineering and production teams in Texas.

When crews identify an issue, it enters our safety management system, where it is assigned an owner and tracked through resolution. We like to think that the next crew inherits the fix, not the problem.

Operational Authorization is Mission-Specific

An aircraft can be airworthy and mission-ready without being approved for every operation. Operational authorization applies to a specific operator, aircraft configuration, mission, and operating area - not simply to an aircraft model.

That distinction is important because every mission presents different risks. An operation over open water differs from one near populated land. Launching from a moving patrol vessel introduces conditions that do not exist at a remote ground site. A different payload, flight path, or operating area can all change what an aviation authority needs to evaluate.

The Dattilo mission illustrates how that process works. Shield AI worked closely with Global Sat Tech, Frontex, and the Italian Coast Guard throughout mission planning. Together, the teams documented the exact aircraft configuration, developed the concept of operations, and trained crews for normal, contingency, and emergency situations.

Operational trust is built one mission at a time. Dattilo was one example. Shield AI has supported operators through mission approvals across North America, Europe, and the Indo-Pacific, working with military organizations and civil aviation authorities in a range of regulatory and operational environments. That experience helps us anticipate what different authorities require and prepare the documentation customers need to obtain authorization for their specific mission.

ENAC assessed the proposed operation under the Specific Operations Risk Assessment (SORA) framework used by the European Union Aviation Safety Agency, or EASA. Its review evaluated the operation as a whole: where and how V-BAT would fly, the risks to people, property, and other airspace users, and the procedures the operator would use to manage those risks.

That process resulted in SAIL III authorization, the highest authorization level to date in Europe. The authorization showed that V-BAT's safety case, operational procedures, and technical documentation met the requirements of an EASA Member State authority for beyond visual line of sight (BVLOS) maritime UAS operations.

From SAIL III to 150 Flight Hours

Then came the real test.

Over 19 days, the two V-BATs flew day and night as a fully integrated part of the patrol vessel, logging 150 flight hours. At peak tempo, both aircraft were airborne simultaneously for a combined 20 hours a day and operated as far as 150 kilometers from the ship.

They were also the largest unmanned aircraft in the 50-to-100-kilogram class that Frontex had flown from a On July 8, senior Frontex and Italian Coast Guard representatives watched a live search and rescue simulation in which one V-BAT located a small inflatable boat and helped coordinate the rescue.

The aircraft matched the approved configuration, the crews followed the documented procedures, and the support team kept both V-BATs ready at the tempo the mission demanded.

That preparation is what turned an authorization into 150 hours of operations at sea. It is the same work that helps customers and partners keep V-BAT flying critical missions around the world.

Photo from Frontex

Shield AI Inc published this content on August 17, 2026, and is solely responsible for the information contained herein. Distributed via Public Technologies (PUBT), unedited and unaltered, on August 17, 2026 at 18:16 UTC. If you believe the information included in the content is inaccurate or outdated and requires editing or removal, please contact us at [email protected]