An FAA Agricultural UAS Enforcement Proposal Is a Recordkeeping Lesson

The Federal Aviation Administration announced on August 7, 2026 that it proposes a $289,215 civil penalty against a Washington drone operator for alleged unauthorized unmanned aircraft operations. The FAA alleges that the operator conducted 15 drone flights to dispense fertilizer without an agricultural aircraft operator certificate. The agency also alleges that the aircraft was not registered and did not have an airworthiness certificate. According to the FAA, the alleged violations occurred on various dates between March and April 2025.

Those are allegations in a proposed enforcement action, not findings that an operator should treat as a final adjudication. Even so, the notice offers a useful operational prompt for any team considering agricultural UAS work: a flight plan is not enough. The organization needs a record that ties the mission, aircraft, operating authority, and crew decisions together before the aircraft is dispatched.

For teams that fly near farms, manage contractor work, collect field imagery, or support agricultural application programs, the important lesson is not to speculate about the case. It is to make ordinary compliance evidence easy to locate, review, and use. That discipline is valuable whether an organization performs the flight itself or evaluates a partner before work begins.

Start by describing the mission precisely

A request that says "spray a field" is not an operational description. It leaves too much open: what material is involved, what aircraft will be used, who is responsible for the operation, where the work will occur, and what documentation should accompany the flight. A better intake process turns a broad request into a defined mission package.

The package can begin with the job location, requested work date, field or treatment area, client contact, and the person authorized to change the scope. It should also identify the purpose of the flight in plain language. Is the request for application, mapping, scouting, photography, or another task? Keeping those purposes distinct matters because a team should not assume that the paperwork and operational conditions for one activity automatically cover another.

The FAA notice specifically concerns alleged fertilizer dispensing. That detail is the reason to avoid a generic label such as "ag drone flight." When a mission changes from imagery collection to dispensing, the operator should treat the change as a new compliance review point rather than a minor variation in the same day's work.

Make authority visible before mobilization

The FAA alleges that the operations were conducted without an agricultural aircraft operator certificate. The agency's notice does not provide a complete operational history or every fact that may be considered in the matter. It does, however, make the basic control point clear: authorization should be verified before a team treats the work as ready for dispatch.

In practice, that means assigning an owner for the pre-mobilization review. The owner should be able to answer a simple question: what authority is being relied upon for this exact operation? The answer should not live only in a manager's memory, a sales email, or an informal message thread. It should be available in the job record in a form that a dispatcher, pilot, safety lead, or client contact can understand.

For a recurring program, create a short authority register rather than rebuilding the answer from scratch every time. The register can identify the operation type, the responsible entity, the supporting certificate or approval reference, its effective status, the aircraft configurations it relates to, and the person who owns updates. The goal is not paperwork for its own sake. The goal is to prevent a field crew from being asked to decide, under time pressure, whether an unfamiliar scope is covered.

Treat aircraft identity as a field control

The FAA also alleges that the drone involved was not registered and did not have an airworthiness certificate. Those allegations point to a second operational habit: every aircraft assigned to a mission should be identifiable in the field and traceable in the records.

An aircraft assignment sheet can be simple. It can include the aircraft's internal fleet identifier, registration information where applicable, configuration, assigned pilot or crew, and date of the preflight status review. The key is that the actual aircraft at the launch site matches the aircraft in the mission record. "The sprayer drone" is not a sufficient identifier when several similar aircraft, batteries, or payload systems are in use.

Make the assignment check part of the release process, not an administrative task completed later. Before launch, the responsible person should compare the aircraft identifier on the job record with the aircraft physically present. If the planned aircraft is swapped, the record should show who approved the substitution and whether the new configuration was reviewed for the mission.

Build a stop-work path that crews will use

Documentation has little value if the crew cannot act on it when something does not match. The field process needs an explicit stop-work path. A pilot, observer, dispatcher, or site lead should be able to say that an authority, aircraft identity, or mission detail is unresolved and know who makes the next decision.

The stop-work path should be short. First, stop the launch or pause the mission. Second, record the specific mismatch. Third, contact the named operations owner. Fourth, resume only after the owner documents the resolution or releases an updated mission package. The crew should not be expected to resolve a certificate question, aircraft status issue, or scope change through guesswork.

This approach protects both the crew and the schedule. A pause may be inconvenient, but an undocumented workaround can make later review much harder. When the decision is documented at the time, the organization has a clear account of what was found, who reviewed it, and why the mission did or did not proceed.

Keep one mission file from request through closeout

A scattered collection of emails, photos, text messages, and handwritten notes does not give a team a dependable operational record. A single mission file does. It does not need to be complicated, but it should provide a predictable place for the material that explains the work.

For an agricultural UAS assignment, the file can include the request, mission description, location details, authority review, aircraft assignment, crew names, preflight confirmation, scope changes, any pause or stop-work decision, and closeout notes. The exact format will depend on the organization and the work, but the sequence matters. Someone reviewing the file later should be able to follow the operation from intake to completion without reconstructing it from multiple systems.

Use consistent file names and a clear job identifier. That makes it easier to connect images, maintenance notes, client communications, and any internal review to the same mission. It also limits the risk that a document from one field is mistakenly used to support another operation.

Audit the process on an ordinary day

The best time to find a recordkeeping gap is not after an incident, a client dispute, or an enforcement notice. It is during routine work. Select a completed mission file and ask a few practical questions. Can a reviewer identify the operation? Can they identify the aircraft? Can they see the authority review? Can they tell whether the scope changed? Can they see who approved a decision to proceed?

If any answer is unclear, the solution may be small: a required field, a standard naming convention, a clearer role assignment, or a dispatch checklist. The point of an internal audit is to test whether the system works when a new person needs to use it, not whether the original author remembers what happened.

Separate facts from assumptions

The FAA's August 7 notice is concise. It identifies a proposed civil penalty, the alleged number of fertilizer-dispensing operations, and the agency's allegations about certification, registration, and airworthiness. It does not provide a complete account of the operator's perspective, technical circumstances, or the eventual outcome. Teams should preserve that distinction in their own discussions.

It is reasonable to use the notice as a prompt to examine operational controls. It is not reasonable to infer facts beyond what the FAA published. For example, the notice does not establish what records the company may have kept, why the alleged operations occurred, or how the matter will ultimately be resolved. A calm compliance review should be based on the published facts and on the organization's own procedures, not on speculation.

The practical takeaway

The FAA's proposed action is a reminder that agricultural UAS work needs an operational chain that can be seen and checked: a defined mission, identified responsible party, documented authority review, traceable aircraft assignment, and usable stop-work process. None of those controls requires a large team or a complex software system. They require ownership and consistency.

For organizations involved in agricultural drone work, the next productive step is to open a recent mission file and test it against that chain. If the file does not clearly show what was planned, what aircraft was used, what authority was reviewed, and what happened when conditions changed, improve the workflow before the next launch. A reliable record is not merely evidence of work already completed. It is part of the decision system that keeps the next operation deliberate.

Source: Federal Aviation Administration August 7 notice.