Part 108 is the FAA’s proposed framework for routine beyond-visual-line-of-sight, or BVLOS, civil operations. Today, a civil operator that wants to fly BVLOS generally needs FAA relief such as a Part 107 waiver. Qualifying government agencies may also conduct public aircraft operations under Part 91 and a Certificate of Authorization, or COA. Under the current proposal, routine civil BVLOS operations would move into Part 108 instead of being handled through Part 107 waivers. Public aircraft operations would remain a separate option for qualifying government agencies.

Under the proposal, operators would hold one of two authorizations.

• Operating Permit, for lower-risk, more limited operations.
• Operating Certificate, for higher-risk or larger-scale operations, requiring a documented Safety Management System.

For a drone-as-first-responder program, this is the part that matters most. DFR depends on flying beyond the operator’s line of sight to get a drone airborne before officers arrive on scene. Right now that capability runs on a waiver your agency had to justify and maintain. Part 108 would make it a standing operating category instead, with its own compliance requirements attached.

For public safety, proposed §§ 108.455 and 108.585 define civic-interest operations as civil operations performed by an entity contracted to a Federal, State, local, Tribal, or territorial government for specified conservation and public-safety support missions.

That contractor language matters. As written, an in-house police, fire, or emergency-management program does not appear to fit the civic-interest category simply because it is a government agency. Qualifying agencies could still continue public-aircraft operations under Part 91 and a COA, and the final Part 108 text could change. Agencies should not assume the proposed civic-interest category is a direct replacement for their existing public-aircraft authority.

The proposed risk tiers matter too. Under § 108.455, a civic-interest permit would be limited to fewer than 25 active aircraft, aircraft at or below 110 pounds, and Category 3 population-density areas or lower, unless otherwise authorized. Under § 108.185, Category 4 operations generally require an Operating Certificate. For civic-interest certificate operations, § 108.585 does not set a specific fleet-size cap; aircraft over 110 pounds are limited to Category 4 or lower unless otherwise authorized, while aircraft at or below 110 pounds may operate in any population-density category if the applicable Part 108 requirements are met. Both the permit and certificate provisions also include a narrow imminent-threat exception allowing operations over any population density to safeguard lives. The FAA would use LandScan USA data to determine the category.

Part 146 is the companion rule. It does not primarily govern the aircraft or individual pilot qualifications. It governs providers of automated data services that BVLOS operations may depend on, such as traffic deconfliction and airspace conformance monitoring. The FAA refers to these entities as Automated Data Service Providers, or ADSPs.

Most public safety agencies are likely to consume these services rather than become ADSPs themselves. In that case, Part 146 matters indirectly through the vendors and platforms supporting the agency’s BVLOS operation. But the proposal also contemplates automated data services that are self-provided, so an agency or vertically integrated operator that provides a regulated service for its own operation could have direct Part 146 obligations. If a vendor says it is “Part 146 ready,” ask what specific proposed requirement that claim addresses and how the vendor would adapt if the final rule changes.

One budget implication is that if an agency relies on an external ADSP rather than self-providing the required service, provider fees should be planned as an operating-cost line item, not treated as part of the one-time aircraft purchase. The NPRM does not prescribe a vendor pricing model, so agencies should ask how pricing scales with their actual operating concept.

You cannot demonstrate compliance with a final rule that has not been published, and no vendor can guarantee what the final requirements will be. Here is what you can do now.

1. Know which category your operations would likely fall under. Start by distinguishing a civil BVLOS operation seeking Part 108 authority from a qualifying public-aircraft operation under Part 91 and a COA. Under the proposal, a single-site civil program may also face a different Part 108 authorization path than a larger regional operation.
2. Look at your governance now, not later. Under the proposal, the Operating Certificate track includes formal safety-management requirements. Agencies that already have documented approval paths, incident records, and audit trails are better positioned to adapt without building those systems from scratch.
3. Ask vendors what “108-ready” or “146-ready” actually means. Treat these as marketing claims, not regulatory status. Ask what specific proposed requirement the claim addresses, what evidence supports it, and what happens if the final rule changes.
4. Build the operating system around the aircraft, not just the aircraft. This is true regardless of what Part 108 ends up saying. Aircraft capability alone does not create an operational program. Policy, training, workflows, data handling, accountability, and documentation still have to work together.

This is the operating discipline Echo Two brings to DFR and autonomous public-safety program design. If Part 108 changes what is required, a documented governance foundation gives an agency a clearer basis for adapting without rebuilding the program around the aircraft.