Part 107 Preflight Requirements: What §107.49 Actually Says

Most Part 107 pilots can recite altitude and visual-line-of-sight. Fewer can walk through the regulation that turns “I looked around” into a list of required preflight actions. 14 CFR § 107.49 — titled Preflight familiarization, inspection, and actions for aircraft operation — tells the remote pilot in command what must happen prior to flight. This DroneLaws.us explainer covers Part 107 preflight requirements under § 107.49 only. Regulatory text was verified against the Cornell LII / eCFR compilation on 16 Oct 2026. This is a statute explainer, not legal advice. Confirm the current Code of Federal Regulations before you rely on any summary—including this one.

For related operating-limitations context on this site, see Part 107 visibility and cloud clearance (§ 107.51). For a shop-floor checklist approach (separate from the regulatory text), see digital drone pre-flight checklist.

What § 107.49 actually says

Under 14 CFR § 107.49 (pull date 16 Oct 2026), prior to flight, the remote pilot in command must:

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

1. Local weather conditions;
2. Local airspace and any flight restrictions;
3. The location of persons and property on the surface; and
4. Other ground hazards.

(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;

(c) Ensure that all control links between ground control station and the small unmanned aircraft are working properly;

(d) If the small unmanned aircraft is powered, ensure that there is enough available power for the small unmanned aircraft system to operate for the intended operational time;

(e) Ensure that any object attached or carried by the small unmanned aircraft is secure and does not adversely affect the flight characteristics or controllability of the aircraft; and

(f) If the operation will be conducted over human beings under subpart D of this part, ensure that the aircraft meets the requirements of § 107.110, § 107.120(a), § 107.130(a), or § 107.140, as applicable.

That is the structure of the text we pulled (including the later amendment note on the LII page). Do not invent extra paragraphs, dollar fines, or “automatic certificate action” language that is not in § 107.49.

Paragraph (a): assess the operating environment

Paragraph (a) is not a vibe check. It requires an assessment that considers risks to persons and property nearby—on the surface and in the air—and it lists four mandatory ingredients: local weather, local airspace and flight restrictions, location of persons and property on the surface, and other ground hazards.

In practice, shops treat this as the “walk the site and check the apps” step: METARs and trends, LAANC or authorization status, NOTAMs and TFRs, who is standing where, vehicles, power lines, and trip hazards. The regulation does not prescribe a branded weather app. It does require the assessment.

Paragraph (b): brief the people on the operation

Anyone directly participating in the operation must be informed about operating conditions, emergency procedures, contingency procedures, roles and responsibilities, and potential hazards. That is a briefing duty, not a shrug toward a bystander. If you have a visual observer, a second crew member, or a client standing inside the operation, treat the brief as part of compliance—not optional customer service.

Paragraphs (c)–(e): links, power, and payloads

(c) Control links between the ground control station and the aircraft must be working properly before flight—not “probably fine after takeoff.”

(d) If the aircraft is powered, there must be enough available power for the intended operational time. The text does not invent a percentage reserve for you; it requires enough power for the operation you intend to fly.

(e) Anything attached or carried must be secure and must not adversely affect flight characteristics or controllability. That covers cameras, beacons, and improvised mounts that seemed like a good idea in the parking lot.

Paragraph (f): operations over human beings (subpart D)

If you will operate over human beings under subpart D, § 107.49(f) requires the aircraft to meet the applicable requirements of § 107.110, § 107.120(a), § 107.130(a), or § 107.140. This explainer does not expand those category rules; it flags that (f) is part of the preflight gate when subpart D applies. Read the category text before you treat a social-media crowd shot as routine.

What § 107.49 does not decide for you

§ 107.49 answers a narrow question: what must the remote PIC do prior to flight? It does not, by itself:

• Replace your company’s longer SOP checklist
• Set visibility or cloud-clearance numbers (see § 107.51 on this site)
• Invent civil-penalty dollar amounts for a missed brief
• Authorize flight in airspace you have not arranged legally

This article does not invent fines. § 107.49 states preflight duties; treat enforcement and penalty questions as separate research against current FAA materials and counsel when needed.

How pilots operationalize the rule without theater

A workable preflight habit maps to the regulation without padding it:

1. Weather + airspace + people/property + ground hazards (a)
2. Crew / participant brief (b)
3. Link check (c)
4. Power for the intended time (d)
5. Payload secure and controllable (e)
6. Subpart D aircraft requirements when applicable (f)

Digitizing that list so the same steps happen on every job is an ops choice. Pilot Ledger’s digital drone pre-flight checklist is practical process reading—not a substitute for the CFR. Pilot Ledger offers a 14-day trial with no card for its software stack; this article does not call that “free” as a marketing dodge for regulated advice.

Weather and airspace inside paragraph (a)

Paragraph (a)(1) and (a)(2) are where many rushed flights fail the spirit of the rule even when the aircraft leaves the ground. “Local weather conditions” means more than glancing at a phone icon. Wind at altitude, gusts in a canyon, precipitation that ends the job early, and temperature effects on batteries all belong in the assessment. “Local airspace and any flight restrictions” means class of airspace, authorizations, temporary flight restrictions, and other limits that apply to this site at this time—not the airspace you flew last Tuesday across town.

None of that language invents a checklist brand. It is how commercial shops translate (a) into behavior that survives an interview after an incident.

Persons, property, and other ground hazards

Paragraph (a)(3) and (a)(4) force you to notice who and what shares the immediate vicinity. A parking lot that was empty at sunrise may have a school pickup line at 3 p.m. A “vacant” lot may have buried utilities marked for another crew. Ground hazards include uneven terrain, wires, fences, and equipment that becomes an obstacle the moment you lose attitude reference. The regulation lists these categories; your site walk fills them in.

Crew resource habits that match paragraph (b)

Paragraph (b) is easy to skip when you fly alone and treat every bystander as “not part of the operation.” The text reaches persons directly participating. If someone is assigned a role—observer, payload tech, client spotter inside the ops plan—they need the conditions, emergencies, contingencies, roles, and hazards. A thirty-second mumbled “watch out” is not the same as covering emergency and contingency procedures. Write the brief once for your shop, then deliver it out loud when the people change.

Control links and power without superstition

Paragraphs (c) and (d) are mechanical. Confirm the control link before flight. Confirm power for the intended operational time. Shops often add a personal reserve policy on top of (d); that is an ops manual choice, not something this article invents as federal text. If your intended flight is twenty minutes of mapping plus a reposition, “enough available power” is measured against that plan—not against a full battery icon that ignores wind and payload draw.

Payloads and subpart D as preflight gates

Paragraph (e) catches loose cameras, dangling antennas, and mounts that change CG after a “quick zip-tie.” Paragraph (f) only fires when the operation will be conducted over human beings under subpart D; when it does, the aircraft must meet the cited category requirements. If your marketing team wants a crowd shot, stop and read subpart D before you treat § 107.49(f) as a checkbox you can skip.

Documentation culture (ops, not invented law)

§ 107.49 does not, in the text we pulled, require you to file a PDF with the FAA before every flight. Many operators still keep a signed or digital preflight record because clients, insurers, and internal audits ask what was checked. That documentation habit supports accountability; it is not a substitute for the duties in (a)–(f), and it is not a fine schedule. Pair the regulation with a practical digital drone pre-flight checklist if you want process tooling—then keep the CFR as the legal baseline.

Related reading

• Part 107 visibility and cloud clearance (§ 107.51)
• Digital drone pre-flight checklist
• Federal landing context on DroneLaws.us: federal drone laws

Re-read 14 CFR § 107.49 on the day it matters. Blog summaries age; the Code is the source.