Public aircraft operations: when government drones fly outside Part 107

Public aircraft operations drone rules occupy a strange corner of aviation law: a government agency's flight can sit largely outside the FAA's civil regulations, including Part 107, provided the operation qualifies under statute, and the price of that freedom is that the agency becomes its own regulator. The authority comes from federal law defining public aircraft and the qualifications for public aircraft status, and it is evaluated flight by flight, not agency by agency. A police department's search flight can be public on Tuesday while the same aircraft's training photos on Wednesday are civil.

This article covers the two legal statuses a single aircraft can hold, who qualifies for public status and what counts as a governmental function, and what public status changes in practice against what it leaves untouched. It closes on the recordkeeping consequence, because an agency that opts out of the FAA's oversight has volunteered to document its own.

Two legal statuses, one aircraft

Every drone flight by a government entity is either a civil operation, conducted under Part 107 or another civil framework like any company's, or a public aircraft operation conducted under the agency's statutory status. The determination is made per flight against the statutory tests, which is the detail that surprises new government programs. There is no public agency badge that covers the fleet; there is a question asked of each mission, and the answer sorts that mission into one rulebook or the other.

Many public safety agencies deliberately run both. Part 107 is well understood, its certificates are portable, and routine flights fit inside it comfortably, so agencies often fly civil by default and invoke public status for the missions that need it. The dual track works only when someone decides, and records, which authority each flight used, because the compliance questions that follow an incident differ completely between the two. A flight nobody classified is a flight the agency will classify retroactively, under pressure, which is the worst available method.

Who qualifies, and what counts as a governmental function

The FAA frames the choice plainly on its page for government and public safety drone programs: agencies either fly under Part 107 like any civil operator, or fly under the statutory requirements for public aircraft at 49 USC 40102(a) and 40125, operating with a Certificate of Waiver or Authorization that lets the agency self certify its aircraft and operators for governmental function flights. The statute supplies the qualification tests behind that second path: a qualifying governmental entity, ownership or an exclusive lease of more than 90 days, a governmental function assessed flight by flight, and no commercial purpose. It also supplies the function list, naming activities such as national defense, intelligence, firefighting, search and rescue, law enforcement, aeronautical research, and biological or geological resource management.

Two clarifications do most of the sorting work. The statutory list illustrates rather than exhausts, but expanding it is the FAA's call, not the agency's, so missions outside the named territory deserve legal review before anyone claims public status. And serving the public good is not the test: plenty of beneficial flying, promotional video, general photography, fails the governmental function requirement, and organizations that feel governmental, including most volunteer fire departments, often are not qualifying entities at all. The status is narrower than its name suggests.

What public status changes, and what it does not

What changes is the source of oversight. A qualifying public aircraft operation is largely outside the FAA's civil certification rules, which means the agency itself takes responsibility for airworthiness standards, pilot qualification, and operational requirements, the oversight work Part 107 would otherwise perform. Airspace is the major exception in practice: public operators still share the national airspace system and typically operate under authorizations obtained from the FAA for access, a topic with its own machinery beyond this article. The freedom is real, and it arrives attached to the regulator's job.

What does not change is the physics or the exposure. A public status flight that injures someone generates the same investigation, the same liability questions, and the same public records requests as a civil one, with a twist: the standards the operation is measured against are the agency's own, because the agency wrote them. Self certification without written standards is indistinguishable from no standards, which is why mature public programs adopt qualification frameworks, often mirroring Part 107 as a floor, and document compliance with their own rules as carefully as any civil operator documents compliance with the FAA's.

Public status changes the rulebook, not the need for records

The paradox of public aircraft operations is that less external regulation demands more internal documentation. A civil operator can point at the FAA's framework and its own compliance with it. A public operator must produce both halves: the standards it set for itself, and the evidence it met them, per flight, because the flight by flight nature of the status means every mission carries its own classification decision. The file for a public status flight should show who declared it public, under which function, flown by whom, qualified how, on which aircraft, maintained to what standard.

Agencies that build this muscle find it pays beyond compliance. City attorneys get clean answers during litigation, councils get real numbers at budget time, and mutual aid partners can verify qualifications before a joint operation instead of during one. Agencies that skip it discover the gap at the worst moment, when an incident review asks which rulebook a flight was under and the honest answer is that nobody wrote it down. Public status is a genuine privilege. The documentation is the rent.

Common mistakes in public aircraft drone operations

Treating public status as an agency wide blanket. Qualification is evaluated flight by flight against the statutory tests. An agency that qualifies in general still flies civil missions whenever a flight fails the function or purpose tests, and each flight's status should be recorded.

Stretching the governmental function list. The statute names functions like firefighting, search and rescue, and law enforcement, and the FAA controls any expansion. Missions that merely benefit the public, promotion, general imagery, belong under civil rules.

Assuming nonprofit means public. The entity test is specific: states, subdivisions, territories, listed tribal governments. Volunteer fire departments and public spirited nonprofits frequently fail it, and their flights are civil operations regardless of mission.

Claiming the freedom without writing the standards. Public status transfers oversight of airworthiness and pilot qualification to the agency. An agency with no written standards has assumed the FAA's role and performed none of it, which reads terribly after an incident.

Leaving flights unclassified. Every mission was public or civil, and the classification drives which rules applied. Deciding at flight time, in the record, costs a checkbox; deciding retroactively under investigation costs credibility.

FAQ

Can any government agency fly drones outside Part 107?

Only qualifying governmental entities, and only flight by flight: the mission must serve a statutory governmental function, use owned or long term exclusively leased aircraft, and involve no commercial purpose. Everything else is a civil operation.

What counts as a governmental function for drone flights?

Federal law lists activities such as national defense, intelligence, firefighting, search and rescue, law enforcement, aeronautical research, and biological or geological resource management. The list can be expanded only by the FAA, not by the operating agency.

Do public aircraft operations escape FAA oversight entirely?

No. The agency takes over airworthiness and pilot qualification oversight for qualifying flights, but public operators still share the national airspace and typically hold FAA authorizations for access, and many fly Part 107 for routine missions anyway.

Why do many agencies fly under Part 107 by choice?

Part 107 is portable, well understood, and sufficient for most routine missions, and its external standards simplify training, mutual aid, and insurance. Agencies often reserve public status for missions that genuinely need what it permits.

Closing thought

Public aircraft status is one of the few places in drone regulation where the government trusts an operator to grade its own work, and the agencies that thrive under it are the ones that act as if the FAA were still watching: written standards, qualified people, classified flights, and files that prove all three. The status removes a regulator. It does not remove the questions.

If you are running drones inside a government agency, FlybyOps was built for the operational record problem at the center of regulated drone work. A pilot registry that tracks certification and currency, a document vault with expiration tracking, a project and job hierarchy that records what each flight was, and an append-only audit log are all part of how the platform keeps an agency's self certifications as findable as any Part 107 file.