Remote Pilot in Command Under Part 107: What §107.19 Makes You Responsible For

Every Part 107 flight has one person the regulations hold responsible for it: the remote pilot in command, or RPIC. On a one-person job that's obviously you. On a crew with two certificated pilots, a visual observer, a client watching over your shoulder and a trainee who wants stick time, it can get less obvious fast. 14 CFR § 107.19 is the section that settles it and sets out the remote pilot in command responsibilities.

This post sets out the full text of § 107.19, walks through each paragraph with practical examples, and shows how it connects to the certificate rule in § 107.12 and the preflight duties in § 107.49. It is general information, not legal advice. All regulatory quotations are from the Electronic Code of Federal Regulations (checked Oct 30, 2026; Title 14 shown as up to date as of Oct 28, 2026).

The full text of § 107.19

14 CFR § 107.19 is titled "Remote pilot in command." It has five paragraphs:

(a) A remote pilot in command must be designated before or during the flight of the small unmanned aircraft.

(b) The remote pilot in command is directly responsible for and is the final authority as to the operation of the small unmanned aircraft system.

(c) The remote pilot in command must ensure that the small unmanned aircraft will pose no undue hazard to other people, other aircraft, or other property in the event of a loss of control of the small unmanned aircraft for any reason.

(d) The remote pilot in command must ensure that the small UAS operation complies with all applicable regulations of this chapter.

(e) The remote pilot in command must have the ability to direct the small unmanned aircraft to ensure compliance with the applicable provisions of this chapter.

Who can be the RPIC? Start with § 107.12

Section 107.19 says an RPIC must exist. Section 107.12 says who is allowed to fill the role. 14 CFR § 107.12(b) reads:

Except as provided in paragraph (c) of this section, no person may act as a remote pilot in command unless that person has a remote pilot certificate with a small UAS rating issued pursuant to Subpart C of this part and satisfies the requirements of § 107.65.

(Paragraph (c) covers foreign-registered aircraft operated with the Administrator's authorization.) So whoever is designated under § 107.19(a) needs a remote pilot certificate with a small UAS rating and must meet § 107.65.

The person on the sticks doesn't have to be the RPIC, though. Section 107.12(a) allows someone without a certificate to manipulate the flight controls if:

(2) That person is under the direct supervision of a remote pilot in command and the remote pilot in command has the ability to immediately take direct control of the flight of the small unmanned aircraft.

That's the rule that lets a trainee or a client fly under supervision. The RPIC title and its responsibilities stay with the certificated pilot the whole time.

Paragraph (a): designation "before or during the flight"

The rule requires that an RPIC be designated "before or during the flight" but doesn't say how. In practice, the safest habit is to name the RPIC out loud at the crew briefing and write it down, especially when more than one certificated pilot is on site.

The phrase "or during" matters on longer jobs. If two certificated pilots trade off on a long mapping day, the role can change hands. When it does, both people should know exactly when the handoff happened, and your records should show who was RPIC for each flight. Companies that put several pilots on one account face the same question at a larger scale; tracking assignments is part of managing 1099 pilots and team seats.

Paragraph (b): "the final authority"

Paragraph (b) makes the RPIC "directly responsible for and ... the final authority as to the operation" of the system. Two practical consequences follow:

• Clients and supervisors don't outrank the RPIC on flight decisions. A project manager can ask for another pass, but whether the flight happens, and how, is the RPIC's call.
• Responsibility doesn't transfer to the person holding the controller. If a supervised trainee is flying under § 107.12(a)(2), the RPIC is still directly responsible for the operation.

On a multi-pilot crew, (b) is also why there should be exactly one RPIC at a time.

Paragraph (c): planning for a loss of control

Paragraph (c) requires the RPIC to "ensure that the small unmanned aircraft will pose no undue hazard to other people, other aircraft, or other property in the event of a loss of control of the small unmanned aircraft for any reason."

Note the last three words: "for any reason." The duty isn't limited to likely failures. It's a planning duty that applies before anything goes wrong. In practice that means thinking through where the aircraft could end up after a lost link, flyaway or power problem, and where people and property sit relative to that.

Paragraph (d): compliance with the whole chapter

Paragraph (d) makes the RPIC responsible for ensuring "the small UAS operation complies with all applicable regulations of this chapter." That reaches well beyond Part 107's own operating rules. The RPIC is the person accountable for airspace, visibility, operations over people, and the alcohol and drug rules in § 107.27, which we cover in our post on Part 107 alcohol and drug rules.

Paragraph (e): the ability to direct the aircraft

Paragraph (e) requires the RPIC to "have the ability to direct the small unmanned aircraft to ensure compliance with the applicable provisions of this chapter." Whatever the crew setup, the RPIC has to be in a position to change what the aircraft is doing when the rules require it, whether that's descending, holding, returning or landing.

That's closely related to the supervision condition in § 107.12(a)(2), which requires the RPIC to have "the ability to immediately take direct control" when someone else is on the controls.

How § 107.49 puts the RPIC to work before takeoff

The preflight section assigns its tasks directly to the RPIC. 14 CFR § 107.49 opens: "Prior to flight, the remote pilot in command must:" and then lists the duties. Paragraph (a) begins:

(a) Assess the operating environment, considering risks to persons and property in the immediate vicinity both on the surface and in the air.

and paragraph (b) reaches the whole crew:

(b) Ensure that all persons directly participating in the small unmanned aircraft operation are informed about the operating conditions, emergency procedures, contingency procedures, roles and responsibilities, and potential hazards;

The phrase "roles and responsibilities" is where the RPIC designation naturally gets communicated. Our post on Part 107 preflight requirements under § 107.49 covers the full checklist. If your crew uses a visual observer, our Part 107 visual observer guide explains how that role fits alongside the RPIC.

Common scenarios

• Two certificated pilots, one aircraft. Pick one RPIC per flight, say it out loud, and log any handoff.
• Client or trainee on the controls. Allowed under § 107.12(a)(2) only with direct supervision and the RPIC able to take control immediately. The RPIC's duties don't move.
• Company crews. The company can assign pilots, but each flight still needs a designated RPIC who is the final authority under § 107.19(b).

Summary

• One designated RPIC per flight, named before or during the flight. (§ 107.19(a))
• The RPIC has final authority and direct responsibility. (§ 107.19(b))
• Loss-of-control planning is the RPIC's duty, "for any reason." (§ 107.19(c))
• The RPIC is accountable for compliance with all applicable rules. (§ 107.19(d))
• The RPIC must be able to direct the aircraft. (§ 107.19(e))
• The RPIC needs a remote pilot certificate with a small UAS rating. (§ 107.12(b))

For the rest of the federal rules that apply to small drones, see our federal drone law overview.