The HoverAir Versa loophole: when a drone is legally a camera

The HoverAir Versa FCC loophole is the sharpest bit of regulatory engineering I've read about this year, and the drone part is almost incidental. Zero Zero Robotics looked at a US ban its name was never written into, cut its product in half, and put only the half containing a radio in front of the regulator.

The Verge read the actual FCC orders and landed on a careful verdict: the loophole looks real, and it could also be dead inside 30 days. Both things at once. That tension is the useful part.

---

🔍 The trick, stated plainly

HoverAir did not argue that its drone should be allowed. It argued that the thing it was certifying is not a drone.

What the FCC was asked to certify	What a customer actually receives
A handheld pocket steadycam with a wireless radio	The same camera, plus a snap-on Flight Kit
Sold standalone (a real SKU)	Propellers that clip on via copper contacts
Made by a company not on the Covered List	A flying camera

The propellers are the clever bit. FCC equipment authorisation covers gadgets containing a wireless radio. The Flight Kit connects through physical copper contacts and almost certainly has no radio of its own, so on a literal reading it never needs to be submitted at all.

The company's own framing, from global marketing director Anita Facundo:

"The Flight Kit is an accessory that extends VERSA's capabilities. Therefore, HOVERAir is in full compliance with the applicable regulatory requirements for the full product configuration offered to US customers."

---

⚖️ Why the ban had a hole to find

Two separate things happened, and conflating them is where most coverage goes wrong.

1. The 2025 NDAA named DJI and Autel Robotics specifically. That is the Covered List. HoverAir is not on it.
2. In December 2025, the US removed automatic FCC approval for all new foreign-made drones. Every foreign manufacturer now has to make a case: built in America, or not a national security threat.

So HoverAir faces friction, not a wall. Its position reduces to: we are not on the Covered List, and for cameras nobody has ever said we couldn't be certified. Both statements are true.

The counter-argument is that the December ban covers "UAS critical components" as well as drones, and the FCC has already indicated cameras count as one of those components. The Versa camera holds the radios, the brains, and the flight logic. Remove the camera and the propellers are plastic.

Key takeaway: Regulatory scope is set by definitions, not by intent. If your product's definition sits outside a category, the rule genuinely does not reach you — right up until someone re-reads the definition with you in mind.

---

⏳ The 30-day clock is the real story

The FCC granted authorisation on August 9th. It also has a rarely-used power to reverse a certification within 30 days. That window has not closed.

The original sign-off came from a Telecommunications Certification Body, a private company the FCC outsources routine approvals to. A TCB asking "has this applicant been barred from certifying cameras?" gets a clean no. That is a narrower question than the FCC itself would ask.

Here's who is actually exposed:

Party	Downside if the FCC reverses
Zero Zero Robotics	Lost certification, refunds, bad press
Indiegogo backers	Money committed to hardware that may never legally ship
US retailers	Stranded inventory
The FCC	A precedent it has to either defend or kill

To its credit, HoverAir did issue refunds when its Aqua drone turned out to be unshippable in the US. That precedent cuts both ways: it shows the company behaves reasonably, and it shows this exact failure has already happened to them once.

One number tells you how the market reads it: as The Verge was writing, only 12 backers had opted for the camera-only version. Nearly everyone is buying the configuration that carries the regulatory risk.

---

🇱🇰 What this means if you're buying or building from Sri Lanka

Three practical consequences.

• A crowdfunding pledge is not a purchase. It's an unsecured bet on a company clearing obstacles it hasn't cleared yet. When the obstacle is a regulator with a live reversal window, that bet is worse than it looks. Cross-border refunds from Sri Lanka are slow and sometimes partial.
• Certification is the moat, not the technology. DJI being pushed out of the US looks like an opening for smaller manufacturers. It isn't. The barrier that removed DJI is paperwork and political classification, and neither gets cheaper for a small team.
• Landed cost is not sticker price. If you're importing a drone or a camera rig here, duty and registration matter more than the exchange rate. We built calculators for exactly this: Sri Lanka drone import tax and drone registration fees.

If the device's legal status in its home market is unsettled, assume support, firmware updates, and warranty service for an imported unit are unsettled too.

---

🛠️ Stress-testing your own "that rule doesn't apply to us"

Sri Lankan software teams hit this pattern constantly. Not a payment institution, just a wallet. Not a medical device, just a wellness tracker. Not a lender, just a deferred payment plan. The HoverAir play is the hardware version of the same move, and the same four questions apply:

1. Who decided you're outside the category — you, or the regulator? A TCB's approval and the FCC's approval are not the same event.
2. Does the rule name products, or does it name functions? "UAS critical components" is function language. Function language is much harder to unbundle your way out of.
3. Can the decision be reversed, and how fast? A 30-day reversal window is a completely different risk profile from a decision that requires a hearing.
4. If it reverses, who is holding the loss? If the answer is "our customers," the strategy has a problem no legal opinion fixes.

Question 2 is where I'd put my money on this one failing. If the camera is the flight controller, calling the propellers an accessory describes the packaging, not the machine.

---

💡 What this means for you

I don't think HoverAir is being dishonest. Every statement it has made appears literally accurate, and the standalone camera is a real SKU, not a fictional one.

But there's a difference between a claim that is true and a claim that is durable. This one currently depends on a regulator not looking closely at a device it has 30 days to reconsider, in a policy area where the political direction is one-way.

If you're a builder, take the technique and drop the timing. Unbundling a regulated component is a legitimate design pattern when the split is real and the regulator has confirmed it in writing. It is not a strategy when the split exists mainly in the marketing copy and the confirmation came from a contractor answering a narrower question.

And if you're a buyer: wait for the 30 days to run out. That costs you a month. Being wrong costs you the whole amount.