A Part 107 Preflight Is a Release Decision, Not a Checklist Signature

Commercial drone work often treats preflight as the first line on a job sheet. That framing is too small. Under the Federal Aviation Administration's Part 107 overview, the person responsible for a small UAS must ensure the drone is safe before flight, and the preflight inspection includes checking the communications link between the control station and the aircraft. Those two points make preflight a release decision: the moment when a crew decides whether the planned aircraft, control setup, payload, people, and operating conditions are fit for the proposed flight.

That decision deserves more than a completed form. A form can show that someone touched the process. A release decision shows that someone compared the actual condition of a particular operation with the limits that make it lawful and manageable. The difference becomes important when a client schedule is tight, a crew is at a remote site, or the mission is routine enough that people begin to assume the same answer every time.

The FAA's Part 107 summary supplies a useful boundary. It describes rules for commercial and government small UAS uses involving drones under 55 pounds. It requires registration for each drone flown under Part 107, a remote pilot certificate with a small UAS rating for the person operating the controls or direct supervision by someone who has one, and a preflight review that includes the control link. It also sets operating limits. A release process should bring those requirements together before the propellers turn.

Start with the proposed flight, not the generic checklist

A generic checklist has value, but it cannot make the final decision on its own. The crew first needs a concise description of the flight it is about to conduct. What aircraft and attached equipment will be used? Who is the remote pilot in command? What is the intended flight area, altitude, speed, and time window? Is the operation expected to occur in daylight or during civil twilight? Will it carry an external load or property for compensation or hire?

Those questions are not an attempt to create new FAA requirements. They are a way to connect the FAA's published limits to the flight in front of the crew. The FAA says that a Part 107 drone may operate during daylight, defined there as 30 minutes before official sunrise through 30 minutes after official sunset, or during twilight if it has anti-collision lighting. It says the maximum allowable altitude is 400 feet above ground, with a higher altitude possible when the aircraft remains within 400 feet of a structure. It also states a maximum speed of 100 mph, or 87 knots.

A release record should therefore state the planned operating window and the planned limits for that job rather than simply carrying forward yesterday's defaults. If the mission moves from a field to a structure, the crew can evaluate the applicable altitude condition before launch. If the schedule slips toward twilight, the crew can confirm the lighting condition rather than treating the clock as a minor administrative detail. If the mission plan changes, the release decision can change with it.

Treat the aircraft configuration as the aircraft that will actually fly

The FAA's overview allows an external load when it is securely attached and does not adversely affect the aircraft's flight characteristics or controllability. It also says property may be transported for compensation or hire within state boundaries if the drone, attached systems, payload, and cargo together weigh less than 55 pounds and the other flight rules are followed.

For operations staff, those statements make configuration control part of preflight. The relevant aircraft is not just a model name. It is the aircraft with its specific battery, controller, attached system, payload, cargo, and mounting arrangement. A release record can identify those elements plainly enough that the remote pilot and a later reviewer know what was evaluated.

That matters because an operation can be appropriate for one configuration and unsuitable for another. The crew does not need to create a laboratory report at the launch point. It does need to make an informed decision about the actual configuration, confirm that the load is secured where one is used, and recognize that the total system weight is part of the FAA's property-transport condition. If an attached system, payload, or cargo has changed since planning, that change should trigger another look at the intended operation.

Make the communications-link check a real gate

The FAA specifically includes checking the communications link between the control station and the drone in its preflight inspection example. That gives the link a different status from a box checked after the system is already being relied upon. It is a condition to evaluate before flight.

A useful release process identifies the control station that will be used, the aircraft it will control, and the result of the link check. It also gives the remote pilot authority to stop the mission if the link is not satisfactory for the operation. The point is not to prescribe a particular manufacturer procedure beyond the FAA source. The point is to preserve the FAA's basic expectation that the aircraft is safe before flight and that the communications link is checked as part of that assessment.

The same discipline helps the crew separate a known-good setup from an assumed-good setup. A controller that worked on a prior job, a battery charged at the shop, or an aircraft that flew earlier in the day may be useful context. None of those facts eliminates the need to check the setup that will be used now. The release decision is about this flight, not the memory of a previous one.

Put accountable people and records in the same frame

The FAA says a person operating the controls under Part 107 needs a remote pilot certificate with a small UAS rating, unless that person is under the direct supervision of someone who holds one. It also says the operator must make the drone available to the FAA for inspection or testing on request and provide associated records required under the rule.

A field release can make those responsibilities visible without becoming a long administrative exercise. Record who is acting as remote pilot in command, who is operating the controls if that is a different person, and who has authority to halt the flight. Keep the registration information associated with the aircraft that will fly. Retain the job-specific release with the information that explains what was decided and why.

The goal is not to turn every mission into a compliance performance. It is to ensure that the people conducting the work can identify the responsible role, the aircraft involved, and the basis for proceeding. When a question arises later, a crew should be able to show more than a signature. It should be able to show the specific operation that was released.

Build a stop decision into the normal workflow

Preflight has real value only if it can result in a no-go or a pause. A useful form therefore includes an unambiguous outcome: released, released with a documented change to the plan, or not released. The crew should not have to invent a reason to pause when the aircraft, link, planned time, configuration, certification, registration, or operating limit does not line up with the proposed mission.

This is especially useful for seemingly small changes. A client may request one more pass after the original plan. A payload may be substituted. The mission may move later in the day. A new person may take the controls. Instead of treating each change as an informal exception, the remote pilot can return to the release questions: Is the aircraft safe before flight? Has the control link been checked? Does the configuration fit the FAA's stated conditions? Are the operating time, altitude, and speed consistent with the rule? Is the required certified supervision in place?

That is not bureaucracy for its own sake. It is a disciplined method for turning a published rule into a decision that can be made consistently under field pressure.

A short release record can be enough

A practical release record does not need to repeat a full operations manual. It can capture the mission identifier and location, the aircraft registration and configuration, the remote pilot in command, the planned time window, relevant operating limits, the communications-link check, any external load or property-carrying condition, and the final go or no-go decision. If the plan changes, record the change and repeat the decision.

The FAA also says that a report is required within 10 days for an operation that results in serious injury, loss of consciousness, or property damage of at least $500. That reporting obligation is a reminder that the record of a flight may matter after the aircraft has landed. A release record will not decide whether an event is reportable, but it can preserve the basic facts of the operation for the people who must assess what happened.

The operational takeaway

Part 107 preflight is not simply a sequence of checks performed to start a mission quickly. The FAA frames it as part of the responsibility to ensure that the drone is safe before flight, including a check of the communications link. Combined with the published requirements for registration, pilot certification, configuration, timing, altitude, speed, and property transport, that makes preflight the right place to make a deliberate release decision.

For a commercial crew, the durable habit is simple: describe the actual flight, evaluate the actual aircraft and control setup against the applicable Part 107 conditions, name the accountable person, and make a clear go or no-go decision. A checklist supports that work. It should not replace it.