FAA Drone Operations, Remote Pilots, and Remote ID

Determine whether Part 107 applies

A small unmanned aircraft weighs less than 55 pounds at takeoff, including everything on board or attached. The small UAS includes the aircraft and associated elements needed for safe and efficient operation. A payload can therefore change whether the aircraft remains within the small-aircraft definition. [1, § 107.3]

Part 107 contains express exclusions, including air-carrier operations, operations under the statutory limited-recreational exception, and specified exemption or certificated-aircraft pathways. The distinction is more precise than commercial versus hobby use. A recreational flight qualifies for the statutory exception only if its conditions are met, while package delivery, agricultural dispensing, or heavier aircraft may need an additional or different authorization analysis. [1, § 107.1] [4]

The mission should be classified before equipment is purchased or a customer is promised a flight profile. A remote pilot certificate alone does not authorize an operation outside the rules that apply to it.

Pilot responsibility survives automation

A remote pilot in command must be designated before or during a Part 107 flight. That pilot is the final authority for the small UAS operation, must ensure compliance, and must ensure the aircraft will not pose an undue hazard if control is lost. A flight plan executed by software remains subject to those duties. [1, § 107.19]

Section 107.12 addresses who may manipulate the flight controls. It permits a qualified certificate holder and, under its conditions, a person under direct supervision when the remote pilot can immediately take direct control. Recurrent knowledge or training requirements are addressed in Section 107.65. A business should distinguish its corporate flight authorization process from the individual's FAA qualification. [1]

Preflight responsibilities include assessing the operating environment, ensuring participants understand the operation, checking control links and available power, and verifying that carried objects do not adversely affect controllability. These are legal operational responsibilities, not merely recommended steps in a vendor checklist. [1, § 107.49]

Airspace and ordinary operating limits

Prior air-traffic-control authorization is required under Section 107.41 for the specified Class B, C, D, and airport surface Class E airspace. An authorization addresses its stated airspace and conditions. It does not waive unrelated operating limitations. Sections 107.45 and 107.47 address prohibited or restricted areas and flight restrictions. [1]

The ordinary limits in Section 107.51 include a maximum groundspeed of 87 knots, equivalent to 100 miles per hour; the rule's altitude limitation and structure-related allowance; minimum flight visibility; and cloud-clearance requirements. The usual altitude rule is 400 feet above ground, with a specified allowance when within a 400-foot radius of a structure. Route design must also account for people, other aircraft, property, and the pilot's ability to comply throughout the mission. [1]

Part 107 prohibits careless or reckless operations that endanger another's life or property. An operation within a numeric altitude limit can still violate that prohibition. [1, § 107.23]

Visual contact, night flight, and people

Section 107.31 requires visual line of sight under its stated conditions. A video feed alone does not replace the required unaided visual capability, apart from corrective lenses. Automated navigation, a robust communications link, and a remote operations room do not themselves waive the requirement. An operation outside the baseline must identify an applicable waiver, exemption, or other authority. [1]

Night flight is permitted under Part 107 when the requirements of Section 107.29 are satisfied, including applicable pilot training or testing and anti-collision lighting visible for at least three statute miles. The rule specifies how the pilot may adjust lighting intensity for safety. Night capability in the manufacturer's specifications is not the full legal test. [1]

Operations over people and moving vehicles are governed by the applicable provisions of Section 107.39 and Subpart D. Category eligibility and operating conditions matter. A general airspace authorization does not establish eligibility to fly over an assembly or moving traffic. [1]

Registration and Remote ID

Registration and Remote ID answer different questions. Part 48 addresses registration of qualifying small aircraft, including the conditions for identifying and marking an aircraft. A business should confirm that each aircraft and its registration information fit the chosen operating pathway. [2]

Part 89 generally reaches aircraft registered or required to be registered and foreign civil unmanned aircraft operating in the United States, subject to its exclusions and authorizations. A standard Remote ID aircraft broadcasts required message elements from takeoff to shutdown. Its identification equipment must function and must not be disabled. If the broadcast fails, the rule requires landing as soon as practicable. [3, §§ 89.101, 89.105, 89.110]

The alternative broadcast-module pathway and FAA-recognized identification-area pathway have their own conditions. A broadcast module is not simply a substitute that preserves every capability available to a standard Remote ID aircraft; the applicable visual-line-of-sight and geographic conditions must be checked. Remote ID compliance also does not expand the aircraft's flight authorization. [3, §§ 89.115, 89.120]

Waivers and changed missions

Sections 107.200 and 107.205 identify the waiver process and the provisions that may be waived. The applicant must show that the proposed operation can safely be conducted under the waiver's terms. A waiver is bounded by its actual authorization and conditions, not by a general description such as advanced operations. [1]

A fleet should retain the relevant approvals with the operating instructions and identify who may change the route, aircraft, payload, staffing, or software configuration. This is a recommended method of keeping the approved operation aligned with the deployed system. A changed mission should be compared with every approval that supported the original one.

Event reporting and Texas law

Section 107.9 requires the remote pilot in command to report specified safety events to the FAA within 10 calendar days. The triggers include serious injury, any loss of consciousness, and qualifying property damage other than damage to the small unmanned aircraft. The property-damage exceptions use the rule's $500 repair-cost or total-loss-value criteria. Other reporting regimes may apply to the same event. [1]

Texas Chapter 423 separately addresses drone imagery, protected facilities, sports venues, and local regulation. Compliance with Part 107 does not supply a complete answer to those provisions or to launch-site access. The flight approval and the state-law mission basis should both be documented. [5]

Hypothetical inspection mission

A Texas inspection company schedules an automated night route around a tower. It should verify pilot qualification, airspace authority, altitude and visual-contact compliance, night lighting, Remote ID, and the limits of any waiver. It should separately identify the Texas basis for collecting the planned images. The fact that a software package can execute the route is not evidence that the route fits those permissions. [1] [3] [5]