Illinois DOT Just Changed UAS Rules for Federally Funded Projects (BlueUAS)

On March 18, 2026, the Illinois Department of Transportation Division of Aeronautics issued a directive that removed any remaining uncertainty around foreign manufactured drone use on federally connected projects.

Effective immediately, platforms from DJI, Autel Robotics, and other FASC prohibited manufacturers are not allowed on projects with a federal funding connection. 

This requirement is not limited to future work. It applies to active contracts, early phase studies, and any consultant or subcontractor supporting delivery. If federal funding can touch the project at any stage, the restriction applies, which makes this an immediate operational concern rather than a future policy discussion.

What Changed and Why It Matters

The significance of this decision lies in how it translates federal policy into real world execution. Illinois did not introduce a new rule. It took existing federal direction and made it actionable at the state level, which is often the step that drives industry change. State transportation agencies ultimately determine how policy is enforced in the field, and once one agency defines expectations clearly, others tend to follow with similar approaches.

This trend is already visible.

• Missouri DOT restricted the use of federal funds for covered drones on federally supported projects starting in late 2025.
• Michigan DOT directed teams to stop procurement, operations, maintenance, and data processing tied to restricted platforms on federally funded work.
• New Jersey DOT issued guidance warning agencies about how federal restrictions impact drone use.
• Texas has taken a related but broader approach by requiring all drone operations conducted by or on behalf of TxDOT to comply with the Texas Model Security Plan for Prohibited Technologies, which restricts the use of certain manufacturers and systems unless a formal exemption is granted.

Illinois is not acting alone. It is reinforcing a direction that is already forming across multiple states.

The Compliance Burden Has Shifted

Responsibility now sits with the operator and the organization managing the work. Teams that continue using non-compliant platforms must be prepared to justify that decision:

Detail would include:

• supply chain transparency, 
• data security practices,
• NDAA alignment, and
• overall risk mitigation posture.

That level of validation is difficult for most project teams, which are structured to execute work rather than defend compliance positions. As more states formalize similar guidance, this burden will become more pronounced, especially for firms operating across multiple jurisdictions.

Why BlueUAS is Becoming the Default Path

Although Illinois did not mandate Blue UAS platforms by name, the practical path forward is becoming clear. The Blue UAS Cleared List, now managed by the Defense Contract Management Agency, offers the most direct route to compliance. Platforms on this list have already been evaluated for cybersecurity, supply chain integrity, and NDAA requirements, which removes a significant amount of uncertainty for operators. These systems are also exempt from FCC Covered List restrictions through January 1, 2027, which further simplifies procurement and operational decisions. Instead of proving that a platform is acceptable, organizations can select one that has already been vetted at a high level.

This Is Not Just a Hardware Change

Treating this transition as a simple equipment replacement introduces risk. Changing platforms affects mission planning, data collection, processing workflows, and overall operational consistency. It also impacts how comfortable and effective operators are in the field. Platform selection must be approached as part of a complete system design, where the aircraft, payload, software, and workflow are aligned to the mission requirements.

Training Is Critical to Maintaining Capability

Training is the factor that determines whether a compliant transition is successful. A team may meet regulatory requirements on paper and still struggle operationally if training is not addressed. Each platform introduces differences in control systems, automation features, sensor performance, and data handling processes. Operators must adapt to those differences to maintain efficiency and accuracy in the field. Without structured training, teams often experience slower operations, increased error rates, and reduced confidence. We have already identified cross platform training as a key challenge as organizations move between systems, which makes it a critical component of any transition plan.

Why Other States Are Likely to Follow

Several factors suggest that more states will adopt similar positions. Federal restrictions are already in place, and state agencies are determining how to enforce them within their own programs. Transportation agencies rely heavily on drones for inspection, mapping, and documentation, which increases their exposure to compliance risk. Once a few states publish clear guidance, others gain a practical model they can follow.

For organizations working across multiple states, maintaining different compliance standards becomes difficult, which often leads to adopting a unified and defensible approach across all operations.