Week 48 | November 2026

On 27 October the NTSB published its report on a 16-foot NOAA research drone that a 45-foot cruiser collided with on Lake Erie in August 2024. I covered the collision itself on LinkedIn last Wednesday. This piece is about what Washington did afterwards.

Sixteen months after that collision, Congress passed a law that lets one category of uncrewed vessel step outside US vessel rules. That category is NOAA craft of 35 feet or less doing survey or research work. The SeaTrac SP-48 that ended up fouled in the cruiser’s propeller pod fits that definition exactly.

There’s a condition, and it’s the whole story. The rules only fall away when one NOAA official decides they’re in the way, and only for one specific reason.

❝

Help shape OTI. Almost 700 of you now read the Brief, from navies and defence departments to primes, autonomy companies and investors. I’d like to know your role and what you use OTI for, so the next six months cover what matters to your work. Six quick questions that shouldn’t take you more than a minute. Responses will not be shared. Take the survey

The only real exemption

Section 7331 of the FY2026 NDAA (Pub. L. 119-60, enacted 18 December 2025) opens with “notwithstanding any other provision of law”. Small uncrewed maritime systems owned, operated or chartered by NOAA “shall not be subject to any vessel inspection, design, operations, navigation, credentialing, or training requirement, law, or regulation” that the Assistant Administrator of NOAA’s Office of Marine and Aviation Operations “determines will harm real-time operational extreme weather oceanographic and atmospheric data collection and predictions.”

Read that last sentence again. The power sits inside NOAA. The text asks for no Coast Guard sign-off and no published determination. The Coast Guard keeps one lever, action on an “immediate safety or security concern”, which is the authority it would reach for anyway.

Even the NTSB’s report quotes the section with an ellipsis that drops the official, so it reads like an automatic exemption. In the statute, someone has to decide first.

The section also reaches companies “performing specified oceanographic surveys on behalf of and pursuant to a contract or other written agreement” with NOAA. That clause does more work than it looks. NOAA’s own craft are public vessels, so most of the inspection and manning law in Title 46 already doesn’t apply to them. The navigation rules still do, and that’s where §7331 bites for NOAA’s own fleet. For contractors, it’s the only carve-out on the books. Eligibility follows the paperwork.

Then there’s the part I find hardest to explain. Congress called this a pilot program. It’s right there in the section heading. Then it gave the pilot nothing to be measured against: no reporting duty, and no requirement to publish a determination. The nearest thing to oversight sits four sections later. Section 7335 has the Coast Guard, with NOAA, the Office of Naval Research, the National Science Foundation and the White House science office, brief Congress each year for three years on “the future operation and governance of small uncrewed maritime systems.” The first briefing is due by 18 December this year. The exemption itself expires a year after that.

Has the Assistant Administrator ever made a determination? I can’t find one on the public record. Either none has been needed, or nobody is required to say. The statute doesn’t let you tell which.

Outside the guidance, still under the rules

The Coast Guard’s current guidance on uncrewed operations is Work Instruction 5P-WI-002(1), issued on 1 June. Its applicability clause excludes two groups: NOAA’s small craft, and public vessels.

Under 46 U.S.C. 2101, a public vessel must be owned or demise-chartered by the government and operated by it, outside commercial service. That takes in the Navy’s four medium USVs, plus the 30 more it ordered on 29 September from Galliano Marine Services, HII and Saronic at an average of about US$40 million each.

Being excluded from the guidance is a long way from being exempt from the rules. The instruction says so itself: nothing in it “relieves owners and operators of their responsibility to comply with applicable regulations, including navigation rules.” INDOPACOM’s legal guidance is blunter. The COLREGS “apply to all vessels and do not include a military exemption.”

Now the odd part. Contractor-run fleets sit inside the guidance. The six Saildrone Voyagers working the Great Lakes for the Coast Guard this year, part of a US$15.5 million contract covering 16 craft, are piloted by Saildrone. In the Coast Guard’s own words to the Detroit News, they are “not owned or operated by the agency.” They aren’t public vessels, so the work instruction applies to them. Now take the 23-foot Saildrone Explorers that chase hurricanes for NOAA each season. Saildrone runs those too. They’re under 35 feet, they collect exactly the extreme-weather data §7331 was written to protect, and the work instruction’s own footnote puts NOAA-contracted craft outside its scope. (Whether they pass the statute’s “exclusively” test is a craft-by-craft question.) Same company, same pilots. Which regime applies depends on who signed the purchase order.

The rule nobody has written

Here’s the gap the NTSB actually found. No US instrument sets a perceptibility standard written for uncrewed vessels. The Inland Rules ask a 16-foot drone for the same lights as a 16-foot runabout, and the SP-48 had them. The statute adds nothing, and neither does the work instruction. The instruction mentions a “COLREGS Compliance Statement” covering lookout, manoeuvrability, navigation and lighting, but only as one of the details that “may be discussed” with the Captain of the Port. The nearest thing to a marking list is a 2024 Marine Safety Information Bulletin, which is advisory. The best-practice circular meant to sort all this out has been in draft since September 2020.

Over in Britain, they’ve gone another way. Edition 3 of the MCA’s Workboat Code added Annex 2 for remotely operated unmanned vessels, and Lloyd’s Register certified ACUA Ocean’s PIONEER under it in August 2025. A certificated code for commercial craft, with navigation lights and signals written in.

So for anyone building or buying USVs for US waters: when standards come, perceptibility will be the first chapter, because that’s where the NTSB has pointed the Coast Guard. It runs straight into a market that footnote 47 of the report put on the record. SeaTrac’s radar reflector kit is optional because some customers “do not want the vessel to be visible due to the nature of their operations.” Builders selling to science agencies and defence buyers will be asked to make the same hull easier to see and harder to see. The military already has a narrow way around this. The Navy can certify that a warship’s lights can’t fully comply, and it publishes each certification in the Federal Register. §7331 is broad and publishes nothing. I struggle to see one perceptibility standard settling all of this without another carve-out.

This one isn’t finished. The first §7335 briefing is due by 18 December, and the Coast Guard and NOAA both owe the NTSB answers by around late January. NOAA’s answer is on perceptibility testing for its own drones. At the same time, it’s the agency that decides when §7331 switches the rules off. 

❝

Got a question about anything here, or a suggestion for a thread I should be watching? Reply to this email or connect on LinkedIn.

Since you have been, thanks for reading.

Cheers,

Mick

Ocean Tech Intelligence provides informational analysis only. Nothing in this publication constitutes financial, investment, legal, or strategic advice. Readers act on this content at their own risk. For full details see our Disclaimer.