Manage your drone business with PilotLedger — the all-in-one platform for commercial UAS operators.
Home/Blog/Part 107 Condition for Safe Operation (§107.15)
Federal

Part 107 Condition for Safe Operation (§107.15)

By The DroneLaws.us Team··5 min read

The Part 107 condition for safe operation rule is one of the shortest sections in the small drone regulations, and one of the easiest to underestimate. Section 107.15 puts the responsibility for the aircraft's condition on the people flying it, before the flight and during it. This post quotes §107.15 as published in the eCFR (14 CFR 107.15, checked Nov 16, 2026; eCFR Title 14 up to date as of Nov 12, 2026), explains what each paragraph asks of you, and shows where it stops and other Part 107 sections take over. It is general information, not legal advice.

The text of §107.15

Here is the section in full.

§ 107.15 Condition for safe operation.

(a) No person may operate a civil small unmanned aircraft system unless it is in a condition for safe operation. Prior to each flight, the remote pilot in command must check the small unmanned aircraft system to determine whether it is in a condition for safe operation.

(b) No person may continue flight of the small unmanned aircraft when he or she knows or has reason to know that the small unmanned aircraft system is no longer in a condition for safe operation.

What paragraph (a) requires before flight

Paragraph (a) does two things.

First, it sets a standing condition: a civil small unmanned aircraft system may not be operated unless it is in a condition for safe operation. Note the words "small unmanned aircraft system." That is the whole system, not just the airframe. Section 107.3 defines a small unmanned aircraft system as "a small unmanned aircraft and its associated elements (including communication links and the components that control the small unmanned aircraft) that are required for the safe and efficient operation of the small unmanned aircraft in the national airspace system" (14 CFR 107.3, checked Nov 16, 2026).

Second, it assigns a task to a specific person. Prior to each flight, the remote pilot in command must check the system to determine whether it is in a condition for safe operation. "Each flight" means this is not a once-a-day or once-a-job check. A battery swap and relaunch is another flight.

The rule does not list the items to check. It leaves the judgment to the remote pilot in command. In practice, operators often look at items such as:

  • propellers, motors and arms for cracks, chips or looseness,
  • batteries for damage, swelling or a charge that won't support the planned flight,
  • the controller, display and any control link warnings,
  • firmware or app messages that flag a fault, and
  • anything attached to the aircraft, such as a camera or payload mount.

Those are examples, not a legal checklist. The legal question under §107.15(a) is whether the system is in a condition for safe operation, and the remote pilot in command must check it before each flight to determine that.

What paragraph (b) requires during flight

Paragraph (b) carries the same standard into the air. No person may continue flight when he or she knows, or has reason to know, that the system is no longer in a condition for safe operation.

Two points matter here:

  • "Knows or has reason to know." The rule does not require certainty. A low-battery warning that won't clear, a sudden loss of control response, a motor that sounds wrong or a visible broken propeller can all give someone reason to know something is wrong.
  • "No person." Like paragraph (a)'s first sentence, paragraph (b) is not limited to the remote pilot in command. Anyone operating the aircraft is covered.

The practical result is that a problem discovered mid-flight is not a reason to finish the job. It is a reason to end the flight as safely as the situation allows.

How §107.15 differs from the §107.49 preflight list

Section 107.15 is often confused with §107.49, "Preflight familiarization, inspection, and actions for aircraft operation." They overlap, but they are not the same rule.

Section 107.49 sets out a broader list of things the remote pilot in command must do prior to flight, including assessing the operating environment (local weather, airspace and flight restrictions, people and property on the surface, and other ground hazards), briefing participants, confirming control links work, confirming enough power for the intended operational time, and making sure attached objects are secure (14 CFR 107.49, checked Nov 16, 2026). We cover that list in detail in our post on Part 107 preflight requirements under §107.49.

Section 107.15 is narrower and focused on the system itself, and it continues during flight through paragraph (b). A pilot can satisfy the §107.49 environment assessment and still violate §107.15 by launching a damaged aircraft, or by continuing to fly after the aircraft stops being in a condition for safe operation.

The aircraft's condition, not the pilot's

Section 107.15 is about the condition of the small unmanned aircraft system. The remote pilot's own fitness to fly is a separate rule, §107.17, which we explain in Part 107 medical condition under §107.17. Keep the two apart in your own procedures: one asks whether the equipment is fit to fly, and the other asks whether the person is.

Is §107.15 waivable?

No waiver path is listed for it. Section 107.205 lists the Part 107 regulations that a certificate of waiver may authorize a deviation from, and §107.15 is not on that list (14 CFR 107.205, checked Nov 16, 2026). Our Part 107 waiver basics post explains how waivers work for the sections that are listed.

Keeping a record of the check

Section 107.15 requires the check. It does not, in its text, require a written record of it. Many operators keep one anyway so they can show what was checked, when, and by whom. If you want to move that routine off paper, see how to digitize your commercial drone preflight checklist.

Bottom line

  • Before each flight, the remote pilot in command must check whether the small unmanned aircraft system is in a condition for safe operation.
  • No one may operate the system unless it is in that condition.
  • No one may continue flight after knowing, or having reason to know, that it no longer is.
  • Section 107.15 is separate from the §107.49 preflight list and the §107.17 medical rule, and it is not on the §107.205 waiver list.

Federal aviation rules are separate from landowner permission and from state and local laws, which may also apply where you fly. When in doubt, read the current eCFR text and the FAA's guidance directly.

About The DroneLaws.us Team

›Contact The DroneLaws.us Team

Your message goes to the DroneLaws.us editorial inbox and is passed to The DroneLaws.us Team. We never publish author email addresses.

Only used to reply to you.

Stay compliant. Stay organized.

PilotLedger keeps your flight logs, clients, quotes, invoices, and compliance records in one place.

See PilotLedger plans

This site provides general information about drone laws and is not legal advice. DroneLaws.us is not affiliated with the FAA or any government agency. Consult a qualified attorney for legal advice regarding your specific situation.