1. Choose a mission lane before buying equipment

Agriculture drones solve different problems. Some missions collect information, such as imagery or mapping. Others place material, such as seed or an agricultural product. Start by choosing one customer problem and defining the deliverable, decision it supports, and conditions that make the mission unsuitable.

Information-gathering, seeding, and spraying should not be treated as interchangeable. Their aircraft, workflow, risk, evidence, and regulatory paths differ.

2. Build the flight foundation

For operations conducted under Part 107, earn the FAA Remote Pilot Certificate and learn the responsibilities that continue after the test. Registration, Remote ID, airspace, operating limitations, aircraft condition, crew roles, and recordkeeping may all affect a real mission.

Practice controlled takeoffs, approaches, emergency responses, orientation, mission interruption, and safe landing away from crops and people before adding field complexity. A software-generated route does not transfer responsibility away from the remote pilot in command.

3. Learn the field workflow

Field work begins before propellers turn. A useful intake identifies the field, acreage, crop, requested outcome, timing, access, obstacles, adjacent properties, sensitive areas, and responsible decision-maker. Then the operator determines whether the request fits the available authority, aircraft, conditions, and evidence.

1. Confirm the actual field and permission to access it.
2. Walk or otherwise assess boundaries, wires, trees, structures, roads, people, animals, and launch or refill areas.
3. Review airspace, weather, wind, visibility, and mission-specific constraints.
4. Define stop conditions and communication roles.
5. Capture an operational record appropriate to the mission.

4. Treat application as a separate compliance lane

Part 107 certification by itself is not a complete authorization to dispense agricultural materials. The FAA directs agricultural UAS operators to the Part 137 certification process and explains that exemptions may be needed from rules the aircraft cannot meet. Pesticide application can also involve EPA requirements, state certification or licensing, and mandatory product-label directions.

Do not advertise, quote, or perform application work until the exact operator, aircraft, material, location, and mission have been checked against current requirements. Build a written compliance matrix and keep proof behind every public credential claim.

5. Evaluate equipment against the mission

Payload is only one decision. Evaluate aircraft and support equipment against field size and shape, material compatibility, required application or distribution pattern, refill workflow, battery and charging logistics, transport, weather limits, maintenance, parts, software, data handling, and the authority under which the aircraft can operate.

Ask a manufacturer or dealer for written documentation. Verify claims independently and budget for the complete field system—not only the aircraft. Avoid publishing acreage-per-hour or coverage claims without a defined configuration and field evidence.

6. Build experience that a farmer can evaluate

Start with supervised training and controlled missions whose scope matches your authority. Use checklists, record what changed, and document limitations as carefully as successes. A credible case study identifies the problem, field context, workflow, evidence captured, and what the evidence does not prove.

Build relationships by asking agronomists, farmers, applicators, and other operators about timing, crop sensitivity, access, and how a deliverable changes a decision. The goal is not flight hours alone; it is a repeatable service that helps someone make or execute a field decision responsibly.

Review Wisconsin Aerial's current agriculture mission-intake approach for an example of how requests can be scoped without promising universal fit.