FAA’s ICE NOTAM Gets Teeth: Change 13 Is the Enforcement Escalation Drone Pilots Should Fear

We covered FAA NOTAM FDC 6/4375 on January 23. We covered it again on February 2 and February 3. So when Vic Moss of the Drone Service Providers Alliance published his breakdown on March 11, the fair question is: what’s new? The answer is FAA Order 2150.3C Change 13 — and it changes everything about how dangerous this invisible restriction actually is.

• The NOTAM: FDC 6/4375, issued January 16, 2026, bans all drones within 3,000 feet laterally and 1,000 feet vertically of any DOD, DOE, or DHS facility or mobile asset — including ICE convoys that never announce their location.
• The New Layer: FAA Order 2150.3C Change 13, issued in late January, eliminates enforcement discretion for airspace violations. Investigators must now refer qualifying cases directly to the FAA Chief Counsel for legal action — no warnings, no administrative slaps.
• The Combined Problem: A restriction pilots cannot see, paired with enforcement that leaves investigators no room to exercise judgment. That’s a trap, not a compliance framework.
• The Source: Vic Moss’s full analysis is at the Drone Service Providers Alliance. DroneXL’s original January 23 coverage is here.

Change 13 Turns an Invisible Restriction Into a Career-Ending One

FAA Order 2150.3C Change 13 is a compliance and enforcement bulletin issued in late January 2026 that eliminates investigator discretion for drone airspace violations — requiring FAA field personnel to refer any qualifying case directly to the Office of the Chief Counsel for legal enforcement action, bypassing the warning letters and administrative actions that previously gave pilots a path to correction before consequences escalated.

This is what Vic flags in his DSPA piece that we hadn’t directly connected to FDC 6/4375 before. The NOTAM problem was always real — a restriction that moves with undisclosed federal convoys and can’t appear on any flight planning app. But the enforcement posture before Change 13 still carried some implicit mercy. An investigator could look at a case, see a pilot who checked everything and got caught in an invisible moving zone, and exercise judgment.

Change 13 removes that judgment. Violate established airspace restrictions, and the case goes to the Chief Counsel. The consequences on the table: criminal charges under 49 USC Section 46307, civil penalties, certificate revocation, and the FAA’s term “mitigation” — which means seizure, disabling, or destruction of your aircraft. A Part 107 pilot who did everything right, who emailed the SOSC before the flight and got no useful answer, who checked B4UFLY and the FAA TFR map and found nothing — still faces that pipeline the moment a DHS convoy enters their airspace.

I’ve been checking the SOSC email process since we first reported on this restriction in late January. What comes back is an acknowledgment. Sometimes boilerplate guidance that refers you back to the same tools that don’t show the restriction. Nothing actionable. Vic is right to call it a workaround that doesn’t work — and with Change 13 now in place, that non-answer carries a much heavier cost.

The Restriction Still Has No Visible Boundaries

Nothing about FDC 6/4375’s core structure has changed since January. The restriction bans all unmanned aircraft within 3,000 feet laterally and 1,000 feet vertically of any active DOD, DOE, or DHS asset, including mobile ground convoys and their escorts. It has no fixed coordinates, no activation times, and no end date. The FAA classifies this as “National Defense Airspace” under 49 U.S.C. Section 40103(b)(3), which is the same authority used for moving naval vessels — except naval vessels are large, operate in waterways, and are generally visible. An unmarked ICE vehicle in a Chicago neighborhood is not.

No flight planning tool shows this restriction in real time. Not B4UFLY, not AirControl, not LAANC, not the FAA TFR map. Showing it would require the FAA to broadcast the real-time location of federal agents in the field. That’s never going to happen. The restriction exists. The tools to find it do not.

The FAA’s UAS Support Center guidance — reproduced in Vic’s piece — tells pilots to check those exact tools before flying, then land if they “have reason to believe” a covered operation is nearby. That guidance is written for a TFR with a known location. Applied to a moving, invisible restriction, it asks pilots to act on information the system is specifically designed to withhold.

A Revised NOTAM Is Ready — DHS Is Reportedly Blocking It

Vic reports — and this is the other piece of genuinely new information in his March 11 analysis — that industry sources say a revised version of the NOTAM has already been drafted by the FAA, but a separate federal agency is holding up its release. That agency is widely believed to be the Department of Homeland Security. DroneXL has not independently confirmed this, but it aligns with the pattern we’ve reported since February.

If accurate, the situation is straightforward: the FAA knows the restriction is broken and has written a fix. DHS won’t let them publish it. The pressure, then, doesn’t belong on the FAA. It belongs on DHS — and on the congressional members who oversee it. Vic’s suggestion to email the SOSC remains the best documentation play for individual pilots. But the policy fix requires a different audience.

DroneXL’s Take

Vic Moss has been doing exactly what the drone industry needs more of — connecting the regulatory dots that most people cover in isolation. The NOTAM story has been out there since January. The Change 13 story broke in late January too. What Vic did is put them in the same frame, which is the right frame. An invisible airspace restriction paired with zero-tolerance enforcement is not a compliance challenge. It’s a structural trap.

We’ve now been tracking this for nearly two months. The ACLU published its analysis. The National Press Photographers Association and the Freedom of the Press Foundation both issued statements. The Commercial Drone Alliance flagged it publicly. None of that has moved DHS. That should tell you something about how committed the current administration is to preserving this restriction as written.

My prediction, revised from February: I no longer expect a meaningful NOTAM revision by early summer. The DHS hold-up, if accurate, reflects deliberate policy preference — not paperwork delay. What’s more likely is that a legal challenge forces the revision. The ACLU has been preparing one. When it lands, watch what the revised language actually says. A narrow fix that addresses the “impossible compliance” language while preserving the effective scope of the restriction would be worse than nothing — it would insulate the policy from further legal challenge while keeping the operational problem intact.

In the meantime: if you’re flying commercially anywhere near any area that could plausibly have federal activity, email 9-ATOR-HQ-SOSC@faa.gov before every flight. Keep the record. If you’ve already done this and gotten a non-answer, that documentation matters — bring it to your congressional representative and explain what Change 13 means for your license and your livelihood.

Editorial Note: AI tools were used to assist with research and archive retrieval for this article. All reporting, analysis, and editorial perspectives are by Haye Kesteloo.