By Angelissa Savino, Autonomy Global Ambassador – Homeland Security
On April 15, 2026, the FAA replaced its embattled roving Temporary Flight Restriction (TFR) , NOTAM 6/4375, with an updated version, NOTAM 6/2824. The move came on the heels of mounting industry backlash and a formal legal challenge filed in the U.S. Court of Appeals for the District of Columbia. For anyone tracking this closely, the outcome was hardly a surprise. The FAA had already acknowledged in its own communications that the original NOTAM was “ambiguous” and that “any [UAS] flight carries the risk of inadvertent violation.” The real question now is whether the updated NOTAM actually solves anything, or simply papers over a deeper, unresolved conflict between drone operator rights, press freedom and federal enforcement authority.
Roving TFRs: Not a New Concept
Roving TFRs have existed in aviation for years. The FAA has long applied them to naval vessels, where operators receive clear, practical notice. Ships are large, visible, and confined to waterways (see NOTAM 5/6379). They are also used for VIP motorcades involving Presidential and Vice-Presidential movement, which are published prior to execution, sometimes with little advance warning. The Department of Energy (DoE) can also request a roving TFR to protect the movement of nuclear material, though it rarely invokes this authority.
What made NOTAM 6/4375, issued on January 16, 2026, categorically different was its subject, non-Secret Service Department of Homeland Security (DHS) mobile assets. These are vehicles that operators cannot readily identify, that are not tracked in any flight planning tool, and that include, notably, unmarked vehicles. Combined with a TFR footprint of 3,000 feet laterally and up to 1,000 feet vertically, this created a compliance nightmare. Drone pilots had no meaningful way to know when a planned flight might violate an undetectable, moving no-fly zone.
The Original NOTAM 6/4375: High Stakes, High Risk
NOTAM 6/4375 replaced an October 2025 NOTAM 5/6378 that had prohibited drone operations within 3,000 feet laterally and 1,000 feet vertically of covered DoD and DoE facilities, mobile assets, vessels, and “ground vehicle convoys.” The January 2026 expansion added DHS facilities and mobile assets, while also referencing DOJ missions in Part 3. The stakes were severe. The NOTAM was classified as “National Defense Airspace” under 49 U.S.C. § 40103(b)(3) and threatened criminal prosecution, civil penalties, certificate revocation, and potential seizure or destruction of any drone found in violation. It had no listed end date.
Two days after the NOTAM’s release, the FAA issued Change 13 to FAA Order 2150.3C, mandating that all known TFR violations be referred to the Chief Counsel for legal enforcement action. This explicitly prohibited administrative or compliance-based resolution. In practice, this meant drone operators could face federal prosecution for violating a TFR they had no way to detect.
The need to protect mobile federal operations from drone threats is legitimate and also not new. The Department of Justice has flagged this gap in congressional testimony dating back to July 2022, with additional testimony in December 2024 and as recently as June 2025. U.S. Marshals regularly transport high-risk detainees, including cartel leaders, where drone-based interference or attacks are a documented threat. But the mechanism for protecting those missions must be workable for lawful operators. NOTAM 6/4375 was not.
Immediate Fallout: Industry and Press Pushback
The drone industry and news media moved quickly. The News Media Coalition, representing the Electronic Frontier Foundation, the New York Times, the Washington Post, and eighteen other organizations, sent a letter to the FAA Chief Counsel on January 28, 2026, demanding the TFR be immediately rescinded on constitutional grounds. Reporting from the ACLU, the Drone Service Providers Alliance, Autonomy Global News, and others was overwhelmingly critical. The consensus was that the NOTAM was not a workable solution.
The Legal Challenge: Levine v. FAA
On March 16, 2026, Minneapolis-based photojournalist Robert Levine, represented by The Reporters Committee for Freedom of the Press (RCFP), filed a petition for review in the U.S. Court of Appeals for the D.C. Circuit. Levine argued the TFR prevented him from using his drones to photograph DHS operations or events where DHS vehicles might be present, including in his own Minneapolis neighborhood, where DHS vehicles routinely operate. On April 8, the FAA’s only response to Levine’s direct inquiry was that the agency was “still considering this matter, including whether or not to enforce the current NOTAM.”
That ambiguity crystallized on April 10, when Levine filed a motion for interim relief, asserting the NOTAM violated the Administrative Procedure Act, was void for vagueness, and violated the First Amendment as applied to journalistic drone use. The filing included internal FAA communications stating: “What we have is an ambiguous TFR. We are working to resolve this” and “The NOTAM is ambiguous. Therefore, any flight carries the risk of inadvertent violation.”
Under settled due process doctrine, a restriction is unconstitutionally vague if it “fails to provide a person of ordinary intelligence fair notice of what is prohibited, or is so standardless that it authorizes or encourages seriously discriminatory enforcement.” The FAA’s own words had made the legal outcome almost inevitable.
NOTAM 6/2824: What Changed And What Didn’t
Rather than formally responding to the Levine petition, the FAA released NOTAM 6/2824 on April 15, 2026. Key changes included:
- Language shifted from “prohibited” to “avoid flying in proximity”
- The Department of Justice was added to the list of covered agencies
- The explicit 3,000-foot lateral and 1,000-foot vertical distance was replaced with the vague phrase “in proximity to” a covered mission
- Threats of criminal prosecution, civil penalties and FAA certificate revocation were removed
- The “National Defense Airspace” classification was removed
- “Department of Defense” was updated to “Department of War”
RCFP posted a statement on their website noting that Levine called the development “a big win,” adding, “It was heartbreaking to have my drones grounded at a time of such importance to my community, but I’m looking forward to getting back up there and getting back to my journalism as soon as possible.”
However, the structural problem persists. Replacing “prohibited within 3,000 feet” with “avoid flying in proximity” does not solve the core compliance gap. Drone operators still have no way to know, in real time, whether they are near a mobile TFR that is not publicly broadcast. Every flight in an area with potential DHS, DOJ or DoW mobile activity still carries legal risk.
What Comes Next
On April 16, 2026, Levine withdrew his motion for interim relief but explicitly stated that “To the extent Respondent believes that the withdrawal of the challenged TFR also moots the Petition, Petitioner intends to oppose any such suggestion of mootness.” Practitioners should track this case as it continues to move forward. A ruling would establish critical precedent on roving TFRs and the boundaries of federal airspace authority over mobile operations, a precedent that currently does not exist. Even as the litigation plays out, the FAA will continue to face pushback from both operators and press organizations on the practical compliance issues the NOTAM leaves unresolved.
The likelihood of future challenges will depend on two variables: how often the federal government invokes these undetectable TFRs, and how aggressively it enforces them. Frequent use paired with severe enforcement, picture mitigation efforts that destroy multiple drones, would almost certainly invite litigation mirroring the arguments in Levine’s motion. By contrast, sparing use coupled with restrained enforcement may leave operators with too little at stake to justify the cost of suit. A measured posture toward these TFRs is therefore not only easier for the FAA to defend, but more likely to survive judicial scrutiny.
Either way, the federal government should consider other workable solutions:
- A real-time verification mechanism that allows credentialed drone operators to confirm they will not violate an active mobile TFR
- A safe harbor framework for operators who pre-coordinate flights with a designated FAA point of contact or a tiered-transparency model tied to the sensitivity of the protected operation.
- Any of these approaches could bridge the gap between legitimate security needs and lawful drone operations.
Until a practical solution is implemented, drone operators across the country will continue flying in legal limbo, uncertain whether any given flight over their own communities puts them on the wrong side of what still remains an undetectable, moving federal no-fly zone.