Part 108 Is Changing UAS Integration: A 2026 Playbook for Defense Contractors

For defense contractors, 2026 is becoming a planning year for the next phase of unmanned aviation.

The Federal Aviation Administration’s proposed Part 108 rule: formally titled “Normalizing Unmanned Aircraft Systems Beyond Visual Line of Sight Operations” and identified as RIN 2120-AL82: could move many beyond visual line of sight (BVLOS) missions away from case-by-case waivers and toward a more repeatable, performance-based operating framework.

But Part 108 is not final.

As of September 18, 2026, the rule is at the last desk: the White House Office of Information and Regulatory Affairs (OIRA) received it on July 10, 2026, and it remains under Executive Order 12866 review. The nominal 90-day review window runs through approximately October 8. A published final rule is therefore most likely in late 2026 or early 2027, although no publication date is guaranteed. Reginfo.gov lists the rule as a final rule pending review.

That uncertainty should not produce inaction. Defense contractors should use this period to prepare their systems, people, supply chains, and proposals for a more scalable UAS operating environment.

What Part 108 could change

Today, many BVLOS operations depend on waivers, exemptions, or other special authorizations. That process can be slow, mission-specific, and difficult to scale across multiple customers, locations, and aircraft configurations.

The proposed Part 108 framework would establish a more rules-based approach centered on:

• Performance-based BVLOS operating requirements
• UAS certification or airworthiness acceptance
• Operational approvals appropriate to mission risk
• Command-and-control link performance
• Detect-and-avoid capabilities
• Right-of-way and encounter responsibilities
• Remote identification and operational oversight

The important shift is not simply “drones can fly farther.” The larger change is that UAS integration would become a systems-engineering and enterprise-readiness challenge.

A contractor seeking approval for a persistent surveillance mission, logistics route, training range, or distributed maintenance operation may need to demonstrate more than aircraft capability. The operator may also need to show that its airspace procedures, communications architecture, crew qualifications, maintenance program, data systems, and contingency plans work together as an integrated safety case.

The FAA’s BVLOS NPRM provides the foundation for understanding the agency’s proposed approach. However, contractors should treat the final regulation: not the NPRM: as the controlling document once it is published.

The critical gap: detect, avoid, and communicate

One of the most important planning signals comes from the Government Accountability Office.

In GAO-26-107648, issued in February 2026, GAO found that the FAA still lacked a detailed technical and implementation plan for how drones will communicate with and avoid other aircraft. The report identified missing actions, unclear federal and non-federal roles, and a lack of technical milestones for achieving two-way communication.

That finding matters because ADS-B alone does not solve the BVLOS integration problem.

ADS-B can provide valuable traffic awareness, but drones are generally not intended to use ADS-B Out in the same way as crewed aircraft because of concerns about system saturation. A UAS may receive information from cooperative traffic while still lacking a universal way to communicate its own position and intent directly to every nearby aircraft.

This creates a practical distinction between:

• Strategic deconfliction: planning routes and airspace use in advance
• Tactical separation: detecting and responding to nearby traffic in real time
• Electronic communication: sharing position, intent, or other information with airspace users

Defense contractors should plan for all three. A flight plan and geofence may reduce risk, but they do not replace tactical detect-and-avoid performance when an unexpected aircraft enters the operating area.

The GAO recommended that the FAA define specific actions, responsibilities, and technical milestones for drone communication and avoidance. Read the GAO report here.

Section 2209 adds another airspace layer

Part 108 will not operate in isolation.

The FAA’s Section 2209 framework addresses facility-based restrictions around eligible critical infrastructure. Under the proposed approach, qualifying facilities could request defined UAS Flight Restriction Areas, or UAFRs. The framework distinguishes between:

• Standard UAFRs, which would impose defined restrictions while allowing certain vetted, compliant operations under specified conditions
• Special UAFRs, which would apply heightened restrictions to more sensitive defense, intelligence, or national-security-related facilities

For contractors, this means airspace planning must account for more than altitude and geographic boundaries. A mission may also involve:

• Facility-specific restrictions
• Remote ID requirements
• Advance notification or coordination
• Site-owner permissions
• FAA approvals
• Security assessments
• Special handling near defense or critical infrastructure facilities

The FAA describes the Section 2209 critical-infrastructure framework and its proposed restrictions in greater detail. Contractors should monitor the relationship between these requirements and the final Part 108 rule rather than assuming that a future BVLOS authorization automatically permits operations over or near restricted facilities.

A 2026 readiness playbook for defense contractors

The most effective response is to build capabilities that remain valuable under multiple regulatory outcomes.

1. Build an airspace and waiver strategy now

Do not wait for Part 108 to be published before documenting current operating concepts.

For each mission set, identify:

• Current Part 107 waiver or exemption requirements
• Airspace classifications and special-use airspace
• Critical infrastructure and facility-based restrictions
• Takeoff, landing, recovery, and contingency areas
• Crew, escort, and observer requirements
• Likely Part 108 approval pathway
• Customer-specific security and reporting obligations

A well-maintained airspace strategy gives program managers a baseline for transition. It also helps proposal teams explain how the contractor will operate legally and safely during the period between today’s waiver environment and a future Part 108 framework.

2. Plan detect-and-avoid as a portfolio, not a single product

The FAA’s performance-based direction means contractors should avoid locking their entire strategy to one sensor or vendor.

Evaluate combinations of:

• Airborne radar
• Electro-optical and infrared sensors
• Cooperative traffic data
• Ground-based surveillance
• Electronic conspicuity inputs
• UTM or operations-management services
• Human-in-the-loop decision support
• Automated alerting and maneuver logic

The goal is not simply to purchase a sensor. It is to develop a validated detect-and-avoid architecture that performs across terrain, weather, electromagnetic conditions, traffic density, and mission profiles.

3. Design resilient data and telemetry architecture

BVLOS operations generate data that must move reliably between the aircraft, control station, customer, maintenance organization, and command structure.

Contractors should assess:

• Primary and backup command-and-control links
• Lost-link behavior and recovery logic
• Data prioritization during degraded bandwidth
• Secure telemetry and identity management
• Time synchronization and event logging
• Remote ID and airspace data integration
• Cybersecurity and supply-chain protections
• Interfaces with customer and government systems

This is where UAS integration becomes inseparable from digital transformation. A capable aircraft cannot compensate for weak data governance or an operations center that cannot distinguish a sensor fault from a communications failure.

4. Treat crew training and currency as an operational system

Military aviation training principles are highly relevant to BVLOS operations. Crews need more than initial qualification; they need recurrent practice in the situations most likely to expose weaknesses in the concept of operations.

Training programs should address:

• Abnormal and emergency procedures
• Lost-link scenarios
• Detect-and-avoid alerts
• Conflicting traffic and right-of-way decisions
• Weather and sensor degradation
• Airspace coordination
• Cyber or navigation disruptions
• Recovery at alternate locations
• Crew resource management

Contractors should also map currency requirements to contract performance. If a proposal promises persistent or distributed UAS operations, the staffing model must account for shift coverage, instructor capacity, simulator access, and replacement crews.

5. Prepare the sustainment and logistics enterprise

More BVLOS activity will increase demand for reliable UAS sustainment.

That includes:

• Configuration management
• Repair and overhaul processes
• Battery and power-system management
• Sensor calibration
• Software and firmware control
• Spares forecasting
• Obsolescence planning
• Depot and field-level maintenance
• Transportation and hazardous-material procedures

A distributed UAS fleet may require a hybrid logistics model combining local technicians, regional hubs, national suppliers, and secure transportation. This is where 3PL defense logistics and 3PL aerospace supply chain, using our partners at Traincroft, their expertise, can directly support readiness.

The contractor that can connect aircraft availability to parts forecasting, maintenance data, transportation, and customer reporting will be better positioned than one that treats sustainment as an afterthought.

What this means for proposals and contracts

Part 108 readiness should begin appearing in capture plans and technical volumes now.

Defense contractors should be prepared to explain:

• How the proposed UAS will transition from waiver-based operations to future rule-based approvals
• What detect-and-avoid capabilities are available today and planned next
• How the system will operate when traffic is non-cooperative
• How command-and-control redundancy will be demonstrated
• How crews will be trained and kept current
• How maintenance, spares, and software updates will be managed
• How airspace restrictions and facility coordination will be handled
• What data will be retained for safety, performance, and auditability

These details help customers assess execution risk. They also protect contractors from making promises that depend on an unsettled regulatory assumption.

The CS3 EGS advantage

CS3 EGS approaches UAS integration as an operational ecosystem: not an isolated aircraft program.

Working with our partners, Vigilant Aerospace and Ready 3. CS3 EGS brings a team with more than 450 years of combined expertise across aerospace support, program management, logistics, training, engineering, and digital transformation. The company is also multi-certified, including AS9100 and ISO 9001:2015.

That combination supports the full readiness picture:

• UAS integration and operational planning
• UAS sustainment, MRO, and supply support
• Military aviation training
• Program and acquisition management
• 3PL defense logistics
• 3PL aerospace supply chain planning
• Data, IT infrastructure, and digital transformation
• Process improvement and performance management

Explore CS3 EGS services or learn more about the company.

Conclusion: prepare for the rule without waiting for the rule

Part 108 may be months away from publication, and its final language may differ from the proposal. But the direction is clear: BVLOS operations are moving toward greater standardization, stronger performance expectations, and deeper integration with the national airspace system.

The contractors best positioned for that future will not wait for a final rule to begin. They will establish their airspace strategy, invest in adaptable detect-and-avoid architectures, strengthen communications and data systems, train their crews, and build sustainment models that can scale.

For more CS3 EGS insights on aerospace, defense contracting, and operational readiness, visit the CS3 EGS Blog.