BVLOS operations: the records regulators expect

Beyond visual line of sight is among the most operationally complex authorizations a commercial drone program can hold. Under current FAA Part 107 regulation, BVLOS operations require a waiver of Section 107.31 (the visual line of sight requirement), and waivers are granted with operation-specific conditions that determine what the program is allowed to do, under what circumstances, and with what equipment. Reference material on the framework lives at the FAA's Beyond Visual Line of Sight page. Compliance with each waiver's conditions is required for every flight, and demonstrating compliance requires records.

The recordkeeping load for BVLOS is substantially heavier than for routine Part 107 operations. The waiver imposes specific obligations beyond the rule. The conditions usually require records the rule does not, including performance data from the command and control link, detect-and-avoid system function, observer protocols, and operating area constraints. Programs that hold BVLOS waivers and treat the recordkeeping as a check-box exercise end up with the records they need for day-to-day surveillance and not the records they need when something happens.

What a BVLOS waiver typically requires

Waivers come with conditions specific to the proposed concept of operations, but several elements appear consistently across BVLOS approvals issued to commercial operators.

Operating area definition. The geographic envelope the operation is approved within, often defined by GPS coordinates or referenced to specific assets (a corridor along a pipeline, a defined area around a facility).

Altitude and airspace constraints. Maximum altitude, airspace class restrictions, and any controlled airspace authorizations required, typically obtained separately.

Equipment requirements. Specific airframes, payloads, command and control equipment, detect-and-avoid systems, and communication links. The waiver often names equipment by manufacturer and model.

Personnel requirements. Remote PIC qualifications, observer roles, ground crew, and communications staffing. The waiver may require specific training beyond Part 107 currency.

Operational procedures. Pre-flight briefings, weather minimums, contingency procedures, communication protocols, and observer station configurations. Often referenced to the operator's SOPs which the FAA reviewed during the waiver application.

Reporting and review obligations. Periodic operational reports to the FAA, immediate notification for specific event types, and annual reviews of the operation against the conditions.

Each of these elements creates a recordkeeping obligation because the operator needs to demonstrate compliance for every flight conducted under the waiver.

Records demonstrating BVLOS compliance

The core flight records for a BVLOS operation include all of the documentation expected for Part 107, plus the conditions specific to the waiver.

Flight records with route information. The actual flight path against the approved operating area, recorded with sufficient detail to demonstrate the flight stayed within the envelope. GPS tracking with timestamps is the baseline; some waivers require detailed telemetry retention.

Equipment configuration per flight. The airframe used, the payload configuration, any detect-and-avoid or communications equipment, and confirmation the equipment matched waiver requirements for that operation.

Personnel assignments. The remote PIC, any visual observers, ground crew, and communications staff. Each role assigned per flight, with confirmation the assigned personnel were qualified for the role.

Weather observations. The observed weather at the time of operation, including any specific minimums the waiver imposes (visibility, ceiling, wind). Some waivers require independent verification of the observations.

Pre-flight briefing and risk assessment. Documentation that the briefing occurred, what was covered, and the operational decision to proceed. For high-risk operations, the risk assessment record may need to show what the operator considered.

Post-flight debrief and incident notation. Any operational deviations, equipment anomalies, or near-events identified during or after the flight.

Detect-and-avoid and observer records

BVLOS waivers typically require one of two strategic approaches for managing collision risk: detect-and-avoid systems, visual observers, or both. Each creates specific recordkeeping demands.

For detect-and-avoid (DAA) systems, records should include the manufacturer and version of the system in use, performance data during each operation, any alerts generated and how they were resolved, and the maintenance and calibration history of the equipment. DAA systems that are part of the approval depend on continued correct function; loss of the system mid-flight is typically a contingency event.

For visual observers, records should include the observer's location during the operation, the observer's qualifications, the communication record between observer and remote PIC, and any traffic or hazard sightings reported. Observer station positioning is often part of the waiver, and the record should show the observer was positioned as approved.

For operations using both DAA and observers, the records of each should be maintained and linked to the same flight record so the integrated picture is recoverable on request.

Communications, equipment, and integration

The command and control (C2) link is the operational lifeline of a BVLOS operation. Records of C2 performance, link integrity, and any anomalies are core to the recordkeeping practice.

Link performance per flight. Many BVLOS operations require continuous logging of C2 link signal strength, latency, and any dropouts. The data demonstrates the link operated within performance bounds during the flight.

Equipment maintenance and inspection. The airframe and any specialty BVLOS equipment carry maintenance and inspection records aligned with manufacturer recommendations and waiver requirements. Some waivers require inspection intervals beyond manufacturer guidance.

Firmware and software versions. The version of flight control firmware, ground control software, and any DAA or other safety system. Changes to these versions can affect waiver compliance and should be tracked deliberately.

Contingency events. Any C2 link interruption, equipment anomaly, or emergency procedure execution. Even when the contingency procedure works as designed, the event is typically reportable under the waiver.

BVLOS records do not stand apart from the broader operational record. They sit on top of it, with BVLOS-specific records linked to the Part 107 baseline. Pilot certification and currency, aircraft registration and history, project and mission records, and surveillance response all need to come together when the FAA asks. Programs that maintain these in separate systems end up reconstructing the linkage during a request.

Common mistakes in BVLOS recordkeeping

Treating the waiver as the end of the compliance work. The waiver authorizes operations under specific conditions. The recordkeeping demonstrates compliance with those conditions for each flight. Programs that file the waiver and stop documenting end up unable to prove they operated within the approval.

Maintaining BVLOS records separately from the broader operational record. Separate systems for BVLOS records and routine flight records produce reconstruction work during any surveillance request. Integration belongs in the operational platform, not in a post-hoc assembly process.

Skipping the C2 link performance data. The link is the operational lifeline, and the records of its performance are how the operator demonstrates the operation was conducted safely. Programs that fly BVLOS without retaining link telemetry are operating without the evidence the waiver typically requires.

Underdocumenting visual observer activity. Observer records often get treated as informal. The waiver typically requires more: position records, communication logs, sighting reports. Treat the observer role with the same documentation rigor as the remote PIC.

Failing to update records when the waiver is amended. Waivers get amended over the life of an operation. The records should reflect the conditions that applied to each flight, which means the operator needs to know which version of the waiver was in effect at the time.

FAQ

How long should BVLOS records be retained? For the duration of the waiver plus several years after expiration is the operating principle. Some operators retain BVLOS records indefinitely because the operations often involve sensitive assets and the records may be needed for incident investigation or legal action years later.

Are BVLOS records required to be stored differently from routine Part 107 records? No specific storage requirement applies, but the volume and operational sensitivity of BVLOS records often justifies a more rigorous storage approach: tamper-evidence, role-based access, and tested backup. The recordkeeping rigor should match the operational risk.

Who should have access to BVLOS records inside a program? Access should be scoped to the people who need to see the records, with broader access reserved for surveillance response and incident review. Programs flying BVLOS for sensitive assets typically apply tighter access controls than they would for routine Part 107 work.

How do we handle BVLOS records when the waiver is renewed? Renewed waivers typically include conditions similar to the prior version but may add or modify specific requirements. Records from the prior waiver period remain valuable; new records should reflect the conditions of the renewed waiver. The transition deserves explicit documentation in the operational platform.

Closing thought

BVLOS recordkeeping is the most demanding documentation any commercial drone program is likely to maintain. The waiver imposes conditions specific to the operation, the equipment, and the personnel; the records prove compliance for every flight conducted under the approval. Programs that build the records into the operational rhythm, with C2 telemetry, observer logs, equipment configuration, and personnel assignments captured per flight, can demonstrate the operation was conducted as approved. Programs that treat the waiver as a one-time authorization and the records as paperwork end up reconstructing the story when surveillance asks.

If you are managing BVLOS records for a commercial drone program, FlybyOps was built for the operational record problem at the center of regulated drone work. An equipment registry that tracks airframes, payloads, and BVLOS-specific equipment per flight, a pilot registry with role-specific qualification records, a document vault for waivers and amendments, and an append-only audit log are all part of how the platform supports the documentation a BVLOS approval requires.