Commercial drone survey operations under Part 107 are not complicated to document when the process is established from the start. The regulatory requirements are defined in 14 CFR Part 107, the Remote ID requirements are in 14 CFR Part 89, and the airspace authorization process runs through the FAA's DroneZone portal and the LAANC system. What creates documentation gaps is not the complexity of the requirements. It is the absence of a consistent process for capturing and associating the required information with each flight record.
This post walks through the documentation items a civil drone survey operator needs to address, organized by when in the operational cycle they occur. This is not an exhaustive regulatory reference. It is a practical checklist built around what FAA auditors typically ask for when reviewing a Part 107 commercial survey operation, and what operators who have been through audits consistently wish they had organized better beforehand.
Before the Season Starts: Permanent Records
Some documentation is not per-mission. It is maintained at the operator and aircraft level and needs to be current before any operations begin. These are the foundational records that an auditor checks first, because they determine whether the operation was legally authorized at all.
Remote Pilot Certificate for each RPIC. Every person serving as remote pilot in command must hold a current Part 107 Remote Pilot Certificate. Current means the certificate was issued or renewed within the preceding 24 calendar months. Certificates expire on the last day of the 24th calendar month after the month in which the knowledge test was passed. Track expiration dates for every active pilot in your operation, not just your own. A pilot whose certificate lapsed during a campaign creates a retroactive compliance problem for every flight they conducted after the expiration date.
FAA UAS Registration for each aircraft. Any UAS weighing between 0.55 and 55 pounds must be registered with the FAA before any outdoor flight. Small UAS registration through the FAA DroneZone portal produces a registration number in the format FA-XXXXXXXX. This number must be marked on the aircraft and must be included in the flight record. Registration is valid for three years. If your registration expires mid-season, any flight after the expiration date is unregistered operation, which is a violation regardless of how good the rest of your documentation is.
Remote ID compliance. Under 14 CFR Part 89, most commercial UAS must either be equipped with standard Remote ID broadcast capability, or operate within an FAA-recognized identification area (FRIA). For most survey operations away from a permanent base, Remote ID broadcasting is required. This means the aircraft must broadcast the required message elements (UAS ID, takeoff location, current position, velocity, and control station location where applicable) during the entire flight. Remote ID compliance documentation includes the UAS ID registered in DroneZone and, for DJI aircraft, confirmation that the Remote ID module is enabled and broadcasting. Remote ID compliance is not self-certifying. The operator needs to be able to demonstrate that the aircraft was configured to broadcast during each flight period.
Before Each Mission: Pre-Flight Documentation
Several documentation items must be addressed before each flight, and the record of having addressed them is part of the mission file.
Airspace authorization. Every flight occurs in a specific class of airspace. Uncontrolled airspace below 400 feet AGL in Class G requires no authorization under standard Part 107 conditions. Controlled airspace (Class B, C, D, or E surface areas) requires authorization before flight. For most survey operations at or below 400 feet, the primary authorization mechanism is LAANC, the Low Altitude Authorization and Notification Capability. LAANC provides near-real-time authorizations through approved UAS Service Suppliers (USS). The authorization is time-specific: it covers a defined ceiling in a defined geographic area for a defined time window. The authorization number, the ceiling granted, and the time window must be recorded as part of the mission file for each flight in controlled airspace.
Flights in special use airspace (restricted areas, prohibited areas, temporary flight restrictions) require different authorization processes and may not be authorizable through LAANC. A survey operation that requires flying near a TFR or within a restricted area needs either a specific authorization from the controlling authority or a waiver from the FAA. The documentation for these situations must be in place before the flight, not assembled after the fact.
Pre-flight airworthiness check. Part 107 requires the RPIC to assess the UAS and ensure it is in a condition for safe operation before each flight. This assessment includes, at minimum: visual inspection of propellers for chips, cracks, or deformation; battery charge state and condition; airframe structural integrity; sensor and communication system function; and for aircraft with multiple configuration options, confirmation that the current configuration is correct for the planned mission. The record of this check does not need to be elaborate, but it needs to exist. A dated, timestamped note that the pre-flight inspection was conducted and the aircraft was deemed airworthy is the minimum. For operations with repeat clients who may review your quality management system, a structured pre-flight form serves better.
Weather assessment. The RPIC must not operate the aircraft in weather conditions that would affect safety. Part 107 sets a minimum flight visibility of 3 statute miles from the control station, and requires cloud clearance of 500 feet below, 1,000 feet above, and 2,000 feet horizontally. The pre-flight weather assessment record should document the weather source consulted, the conditions at the time of the assessment, and the RPIC's determination that conditions were within limits. Aviation weather products from aviationweather.gov are the standard reference for this, not consumer weather apps.
During the Mission: Real-Time Records
During the flight, the primary record is the aircraft's flight log. For DJI aircraft, the DAT or TXT file captures GPS position, altitude, and system state throughout the flight. The flight log is not a document you create. It is a file the aircraft creates automatically. The documentation responsibility during the mission is ensuring that the log is being captured (verify that logging is enabled if the aircraft has configurable logging settings), and that after each flight the log file is associated with the correct mission in your records system.
If the mission involves multiple flights and multiple batteries on the same day at the same site, each battery/flight session produces a separate log file. All of them belong to the same mission record. The association between sessions and the mission needs to be explicit, because a log file named with a timestamp and serial number does not inherently communicate which survey contract it belongs to.
Waivers, if applicable. Part 107 allows the FAA to issue waivers for certain standard operating limitations: night operations, operations over people, operations beyond visual line of sight, and others. If any waiver applies to a given mission, the waiver reference number and the specific conditions it authorizes must be part of the mission file. A waiver is not a blanket authorization. It applies to specific conditions, and operations outside those conditions are not covered by the waiver.
After the Mission: Post-Flight Documentation
The mission file is not complete until the post-flight documentation is assembled. For routine survey operations that went as planned, this is quick. For missions with incidents or anomalies, it requires more attention.
Flight log retrieval and association. The log files from the mission need to be transferred from the aircraft (if using USB retrieval) or confirmed in the cloud platform (if using FlightHub or a similar system) and associated with the mission record. This step is often skipped when the next mission is scheduled for the following morning. The consequence is a log archive that is organized by date but not by mission, which makes it very difficult to retrieve a complete mission record when an audit request arrives three months later.
Incident or accident reporting. Under 14 CFR 107.9, the RPIC must report to the FAA within 10 days any operation that results in at least a serious injury to any person, or property damage of at least $500 (excluding the UAS itself). The threshold for mandatory reporting is specific. Document any event that might meet the threshold immediately after the mission, even if you are not certain whether a report is required. The decision about whether to file can be made with legal counsel, but the underlying facts need to be captured before they fade.
Retention and Retrieval
Part 107 does not specify a minimum records retention period for flight records explicitly, but the prudent standard is three years minimum, which aligns with the civil statute of limitations for most incidents. Operational context: if a dispute arises about the conduct of a survey mission, flight records are the primary evidence of what the aircraft actually did. Records that cannot be produced are treated as records that do not exist.
The retrieval side is as important as the retention side. Being able to produce a complete mission file for a specific date and aircraft within 24 hours of an audit request is the operational standard. If your records are organized by date folder with unmarked log files, that retrieval takes hours of manual work. If your records associate each log file with a mission identifier, the aircraft serial, the pilot, and the authorization records at ingestion time, the retrieval is a query.