Part 107 Mission Release Cards: Turn FAA Operating Limits Into a Field Check

The useful document is the one a crew can use at the launch point

Commercial drone teams often have the ingredients of compliance scattered across several places. A pilot has a certificate. The aircraft has a registration number. A planner has checked a map. A client has supplied a location. A crew has a checklist. Those are valuable pieces, but they do not automatically become a single decision to fly.

The Federal Aviation Administration's July 6, 2026 overview of Part 107 provides a compact way to reconnect them. It describes rules for small unmanned aircraft systems used in a broad range of commercial and government operations, for aircraft weighing less than 55 pounds. It also identifies the operating limits, registration, pilot qualifications, preflight responsibility, airspace authorization, and reporting obligations that apply to the work.

The practical challenge is not memorizing a web page. It is making sure the facts that matter to a particular mission are visible to the person who can stop the flight. A short mission release card can do that. It is not a new FAA form and it does not replace a manual, authorization, waiver, or the judgment of the remote pilot in command. It is an internal prompt that turns a general rule set into a specific question: does this planned flight fit the conditions under which the crew is prepared to operate today?

That focus matters because a field operation changes from job to job. The aircraft, payload, site, people nearby, airspace, light, weather, crew, and client schedule can all differ. A release card should make the crew compare those mission facts with the limits that govern the operation rather than relying on the comfort of having flown a similar job before.

Start with the operation, not with a generic checklist

The FAA says that a Part 107 operation must avoid manned aircraft and must not be careless or reckless. Those are not boxes that can be completed once for an entire season. They set the context for each launch decision.

A good release card therefore begins with a plain description of the flight. Record the site, the purpose, the aircraft configuration, the intended launch and recovery area, the proposed maximum altitude, the time window, and the people assigned to the operation. Keep the wording specific enough that another qualified person could understand what the crew intends to do without needing a verbal explanation.

This initial description is useful because it exposes the assumptions that are otherwise easy to leave unstated. Is the aircraft expected to fly near a structure? Is an external load attached? Will the crew be operating in daylight or twilight? Is the planned location in Class G airspace, or does it require air traffic control authorization? Is there a reason a person could be under the intended flight path? The card does not answer these questions by itself. It requires the team to answer them before launch.

The FAA's overview says a drone must be kept within sight. If a crew uses first person view or similar technology, a visual observer must always keep the drone within unaided sight. It also says a person cannot serve as pilot or visual observer for more than one drone operation at a time. These points belong next to the crew assignment, not in a separate training binder. The release decision should identify who is acting as the remote pilot, who is acting as visual observer if one is used, and whether the planned method keeps the aircraft within the required sight condition.

A role name is not enough. The crew should be able to state who is watching the aircraft, who is monitoring the conditions around the operation, and who has the authority to call for a pause. A short spoken briefing can make the written card real: confirm the flight objective, identify the relevant limit, name the stop condition, and make sure every assigned person understands it.

Make airspace a visible release item

The FAA states that operations in Class G airspace are allowed without air traffic control permission. Operations in Class B, C, D, and E airspace need air traffic control authorization. That distinction should not be buried in a planning note that never reaches the launch site.

Put airspace on the release card in a form that makes the decision traceable. Identify the airspace determination, the authorization if one is required, any applicable authorization details, and the person who confirmed them. The point is not to make every field record long. It is to avoid a vague statement such as “airspace checked” when a future reviewer needs to know what was checked and what the crew relied upon.

The FAA explains that the Low Altitude Authorization and Notification Capability, known as LAANC, uses desktop and mobile apps to support a high volume of drone operations with almost real-time airspace authorizations. It says that many authorizations are granted within seconds after submission. The agency also says that LAANC applies only to FAA air traffic control facilities and does not yet include contract or Department of Defense air traffic control facilities. Authorizations for those facilities need the manual process through FAADroneZone.

For a field team, the implication is straightforward: a fast authorization route is not a reason to defer airspace work to the last minute. The release card should distinguish the authorization path that applies to the site. It should also show whether the evidence is available to the remote pilot before takeoff. If the team cannot show which airspace process applies, it has not completed the release decision.

Airspace is also connected to the planned height. The FAA describes a maximum allowable altitude of 400 feet above ground level, with a higher altitude available when the drone remains within 400 feet of a structure. A release card can ask for the proposed maximum altitude and, where relevant, the structure basis the crew is using. That turns a familiar number into a documented mission constraint rather than a rule remembered in the abstract.

Put operating limits beside the planned flight profile

The FAA lists several core operating requirements that can be translated into direct prompts. The operation must avoid manned aircraft. It cannot be careless or reckless. The aircraft must remain within sight under the conditions the FAA describes. The rule also restricts operations over people who are not directly participating in the operation, operations from a moving aircraft, and operations from a moving vehicle except in the specific sparsely populated circumstances identified by the FAA.

A release card does not need to repeat every rule in full prose. It should put the relevant decision near the mission plan. For example, a section headed “people and movement” could require the crew to identify whether nonparticipants may be below or near the intended operation, whether the launch and recovery areas are controlled, and whether the operation involves any vehicle-based activity. If the answer does not fit the planned method, the correct outcome is a pause and a review, not an optimistic checkbox.

The FAA also gives measurable boundaries that are easy to overlook when a job runs late. Flights may occur during daylight, which the FAA describes as 30 minutes before official sunrise to 30 minutes after official sunset local time. Twilight operations are permitted if the drone has anti-collision lighting. The minimum weather visibility is three miles from the control station, and the maximum speed is 100 mph, or 87 knots.

A useful release card converts these into a time, equipment, and condition check. Record the planned time window. If the work may enter twilight, identify the anti-collision lighting condition before launch. Record the crew's visibility assessment from the control station and compare it with the FAA minimum. Confirm the proposed flight profile remains within the speed and altitude limits relevant to the mission. These are not ceremonial entries. They make it easier for a crew to recognize when a delayed setup, changing light, or deteriorating conditions have changed the operation it originally approved.

Treat aircraft configuration as part of the decision

The FAA says that a drone may carry an external load when it is securely attached and does not adversely affect the flight characteristics or controllability of the aircraft. It also says that property may be transported for compensation or hire within state boundaries if the aircraft, attached systems, payload, and cargo together weigh less than 55 pounds and the other flight rules are followed, subject to the exceptions the FAA notes for Hawaii and the District of Columbia.

Those statements give an internal release card a clear purpose for capturing configuration. Identify the aircraft, attached systems, payload, cargo if any, and the total operating configuration the crew intends to fly. Note how the crew confirmed the attachment and whether the planned configuration remains controllable for the intended work. The card should not turn a field crew into an engineering department. It should make sure a configuration change is recognized as a change that deserves a deliberate check.

The FAA also says that the operator is responsible for ensuring a drone is safe before flight. It does not require small drones to meet current agency airworthiness standards or obtain aircraft certification. The FAA gives a preflight inspection that includes checking the communications link between the control station and the drone as an example.

This is a strong reason to connect the release card to the team's existing preflight process rather than create a competing form. The release record can state that the preflight inspection was completed, identify the aircraft configuration, and include any finding that changes the plan. A crew should not be asked to certify that everything is perfect. It should be asked to identify whether the aircraft and link are ready for the specific operation or whether a discrepancy requires maintenance, a different configuration, or no flight.

Confirm the people, registration, and records behind the flight

Under the FAA's overview, anyone flying under Part 107 must register each drone they intend to operate. The FAA says the registration number must be placed on the drone and that the operator should carry the registration when operating. The release card should make the registration reference available at the job, especially when several aircraft or similar airframes are in use. It is a simple way to confirm that the machine in the case is the machine the crew intends to fly.

The FAA says a person operating the controls under Part 107 needs a remote pilot certificate with a small UAS rating, or must be under the direct supervision of someone who holds that certificate. Capture the remote pilot's identity and certification status in the release record. If another person is operating controls under supervision, identify the supervising certificate holder and the planned arrangement. This is not paperwork for its own sake. It makes the responsibility structure visible before the work starts.

The FAA also says the pilot in command must make the drone available to the FAA for inspection or testing on request and must provide associated records that the rule requires. That is a reminder to design a release record that can be retrieved later. The useful file is not a photograph of a paper checklist trapped on one phone. It is a clearly named record tied to the date, site, aircraft, pilot, and mission.

The same principle applies to events. The FAA requires reporting within 10 days for an operation resulting in serious injury, loss of consciousness, or property damage of at least $500. A mission release card cannot determine whether an event is reportable, but it can direct the crew to preserve the operational record and notify the responsible internal contact when something abnormal happens. That preserves the facts needed for the organization to evaluate its obligation without relying on recollection after the site has been cleared.

A release card should make stopping easier

The best test of a mission release card is not whether it creates a complete-looking record on an ordinary day. It is whether it gives a crew permission to stop when the operation no longer matches the plan.

A simple card can have five sections: mission description, crew and visual-line-of-sight arrangement, airspace and altitude, operating conditions and people nearby, and aircraft readiness and records. Each section should end in a direct decision: confirmed, changed, or stop for review. Avoid a design that pressures the crew to reach “confirmed” simply because the client, truck, or schedule is waiting.

The FAA provides a waiver path for some regulations listed in section 107.205 when an applicant can show an equivalent level of safety. Its overview notes that beyond visual line of sight, above-400-foot, and operations-over-people waivers are among the most requested. That is a separate planning path, not a field workaround. If a release card reveals that the planned operation depends on a limitation the crew cannot meet, the team should identify the mismatch and use the appropriate process rather than redefining the mission at the launch point.

The durable lesson from the FAA's July overview is that Part 107 is not a collection of facts to recall after an incident. It is a set of operating boundaries that should shape the go or no-go decision before takeoff. A concise mission release card gives commercial teams a practical bridge between the regulation, the flight plan, and the people standing at the control station. When that bridge is clear, the crew has a better chance of recognizing both when a mission is ready and when it is not.