What Part 108 Permits and Certificates Could Require From Drone Operators

If Part 108 takes effect substantially as proposed, the operating permit and certificate paths will matter for a simple reason: they would turn scalable BVLOS operations into an organization-level trust problem. The FAA would not be watching every flight. It would be trusting that the operator has the people, aircraft, procedures, training, safety controls, and records needed to conduct the operation safely.

That is why the evidence requirements are so important. The point is not that operators will need nicer reports. The point is that the operator would need a standing record that can answer basic questions at any moment: what aircraft flew, what condition it was in, who was assigned, whether those people were trained and current, what route was intended, what area was approved, what safety issues were open, and what actually happened.

What proposed Section 108.40 tells us

The proposed recordkeeping section is the clearest signal. The NPRM describes aircraft records such as unmanned aircraft used in the operation, total time in service, and life-limited part status. It also describes flight records such as date, time, duration, registration number, operation type, flight path, assigned operations personnel, and landing locations. It also points to training records and, for certificate holders, duty and rest records for required operations personnel.

That mix is not accidental. Aircraft state, flight state, people state, and training state are not separate compliance chores. They are pieces of one proof: this specific flight was allowed to happen. If those records live in disconnected spreadsheets, cloud drives, and vendor portals, the operator can still assemble a packet eventually. What they cannot easily do is prove that the flight was authorized before it launched.

Certificates raise the standard

The permit path may work for simpler operations. The certificate path is different. It is aimed at operations that need more scale, more complexity, and more oversight. The NPRM table of contents alone shows the shape of that burden: training program, validation tests, cybersecurity, risk assessments, inoperative equipment, safety management system, and operation-specific requirements.

For the operator, the practical question becomes: can the organization demonstrate its own control system? Not just that a pilot was qualified. Not just that a drone flew. The organization needs to show that its system knew enough to release the flight and preserve enough to defend that release later.

What operators can do now

• Connect aircraft, configuration, mission, route, crew, training, findings, and evidence records before BVLOS scale arrives.
• Freeze mission-time configuration snapshots instead of relying on current aircraft state.
• Track training, currency, duty, rest, and role assignments as operational facts, not HR notes.
• Treat every dispatch decision as a record that should be understandable to an auditor months later.
• Label proposed Part 108 checks clearly so teams can rehearse against the NPRM without pretending it is final.

The strongest version of a Part 108-ready operation is not a team that can scramble quickly. It is a team where evidence is created through normal work. That is the thesis: compliance should be a byproduct of how the operation runs, because under a Part 108 authorization, the operation itself becomes the thing being evaluated.