The First Revocation
On August 11, 2026, the Federal Communications Commission's Office of Engineering and Technology and Public Safety and Homeland Security Bureau issued an Order of Revocation — DA 26-839, ET Docket 26-186 — revoking both equipment authorizations held by Odyssey Robot LLC, effective the day the order issued. The devices were a drone and its remote controller, certified on April 20 of this year; the company's name notwithstanding, this is a drone case, not a robotics case. It is also something this regime had not yet produced: the Commission taking back grants it had already issued. Until August 11, revocation of covered equipment was an authority the Commission had asserted. Now it is one the Commission has used.
The file that failed
The order's facts are worth reading slowly, because every one of them is a diligence lesson. In January, Odyssey attested — as every certification applicant must — that its devices were not covered equipment prohibited from authorization. In February it supported that attestation with a declaration that the products were developed, designed, and manufactured by Odyssey in California and assembled by a named company, eTak Worldwide Corporation, in Texas. The test reports in the same application file showed the devices were tested by TÜV Rheinland in Shenzhen. The grants issued in April. In June, a security researcher published allegations — in a public GitHub repository the order itself cites — that the attestations were false and the company was a front for a Covered List entity. The Enforcement Bureau opened its file four days later.
The dispositive step was not forensic. The Bureau wrote to eTak, the assembler Odyssey had named, and asked. eTak answered that it has no affiliation, business relationship, contractual relationship, agency relationship, or ownership interest in Odyssey whatsoever — that it had never assembled anything for them. One letter to the named counterparty and the origin story was finished. Odyssey, for its part, never responded: not to the letter of inquiry in June, not to the deficiency letter that followed, not to the show-cause order in July. From public allegation to revocation took about nine weeks; from show-cause to revocation, three.
Keep the three powers straight
Precision matters here, because the revocation is easy to over-read and easy to under-read. The Commission's rules now hold three distinct powers over equipment already authorized. The first is the limitation on importation and marketing — the clawback track, under § 2.939(e) — in force since June for the legacy Covered List entries, and proposed for named entities (nine on July 17, a tenth on August 10) and for an entire drone category by capability. Those actions expressly do not revoke the underlying authorizations. The second is streamlined revocation under § 2.939(d), for grants whose not-covered attestation or supporting materials contained a false statement — the power exercised against Odyssey. The third is a general authority under § 2.939(a) to review any covered-equipment authorization, asserted in October 2025 and so far unexercised.
Put plainly: an honestly documented grandfathered grant can still lose its market through the clawback track — but not its existence. A grant whose file was false can now lose both, effective the day the order issues.
What a buyer should take from it
The Commission has now shown you its diligence method, and it is the one we have been describing all year: it does not grade the confidence of the claim, it asks the counterparty. A vendor's certificate on file is a representation, and representations are now checked — against the named assembler, against where the test reports say the testing happened, against what public researchers have already published. A vendor-bench review that stops at collecting certificates does less than the agency's own first letter did.
Two further points for anyone holding inventory. The revocation took effect on issuance — equipment that was lawful to market on August 10 was not on August 11, which is what stranding looks like in practice. And the enforcement trigger was not an audit or a tip line; it was a researcher's public repository. Your vendors' origin stories are being read in public, by people with no subpoena and no obligation to warn anyone, and the Commission cited that work by name.
What a manufacturer should take from it
If your production story is true, the lesson is evidentiary. The attestation you sign is only as strong as what the counterparties behind it would say if asked — and the agency now asks. A file built to survive that reading contains the supplier and assembler declarations before anyone requests them, keeps the test venue consistent with the production story, and treats every origin claim as something a stranger will eventually verify. That is the discipline the Gatewell Protocol exists to paper, down to the supplier-confirmation annexes.
One contrast from the same fortnight, offered without adornment. Anzu Robotics — proposed on August 10, on different grounds and in a proceeding still open, for an import and marketing prohibition — answered the Enforcement Bureau's inquiry through counsel, and its matter is today a proposal with a comment period. Odyssey answered nothing, three times, and its matter is a final order. The record now contains a worked example of what silence costs.
Verified against the primary texts on August 14, 2026 — the Order of Revocation (DA 26-839, ET Docket 26-186) and the August 10 public notice (DA 26-832, PS Docket 26-184). This regime moves quickly; verify the current posture before relying on any of it, including this reading.