EASA CRT application impact on farm drone compliance
Learn what EASA CRT comment records change for farm drone planning, including clearer category fit, system-level files, and privacy checks.
The EASA CRT application is best read as a record of regulatory comment, not as an approval route for a farm flight. In this context, CRT means EASA’s Comment Response Tool. The supplied record contains UK CAA comments on EASA’s proposed framework for drone operations.
That distinction matters. A CRT comment can show where regulators see gaps, unclear wording or weak enforcement. It does not, by itself, prove that an operator’s duties have changed.
For farm businesses, the practical lesson is about change control. Compliance files should describe the whole operation, assign clear roles and show why each mission fits its chosen category. They should also make it easy to record later changes in rules or guidance.
The CRT record signals direction, not a new operator approval
EASA’s proposal set out a risk- and performance-based framework centred on the type of operation. The UK CAA supported that broad approach in its CRT comments. This means the regulatory focus is not limited to the aircraft as a product.
The mission matters: where it takes place, who may be exposed, how the aircraft is controlled and what safeguards apply. A farm operator should therefore avoid treating an aircraft specification sheet as a compliance plan.
The CRT record also shows how consultation feeds into rule development. The EASA proposal listed national aviation authorities, drone operators, manufacturers, airspace users, the general public and other groups among the affected stakeholders. Its drivers included safety, legal needs, proportionality, the environment and a level playing field.
That context gives the CRT material a clear but limited role:
- It records comments on proposed policy.
- It shows which parts of a proposal drew concern.
- It helps operators understand the thinking behind the framework.
- It does not replace the applicable regulation or guidance.
The UK CAA’s comments are useful because they stress clarity and practical enforcement. It warned that detailed requirements in the Open category could be hard to enforce in a proportionate way. It also agreed that overburdening low-risk work could harm safety by encouraging indifference or unlawful flights.
For an operator, the answer is not thinner records. It is clearer records. A short statement showing how a mission meets the relevant limits is more useful than a large file that never reaches a conclusion.
The type of operation should lead the compliance plan
EASA’s framework divides operations by risk rather than simply by commercial purpose. Farm work is not placed in a category merely because it involves crops, livestock, mapping or spraying. The planned operation and its risks decide the route.
The proposal described the categories as follows:
| Category | Risk framing | Core approach described by EASA | What the farm file should explain |
|---|---|---|---|
| Open | Low risk | Operational limits, industry standards, set technical features and basic operating rules | Why the mission stays within the category assumptions and limits |
| Specific | Medium risk | Authorisation after an operator risk assessment, with risk controls in an operations manual | The assessed risks, chosen controls and evidence that crews follow them |
| Certified | Higher risk | Controls comparable with manned aviation | Why the operation falls within this higher-risk framework and what approvals apply |
This table is a planning prompt, not a category decision for a specific flight. The supplied material does not support placing every farm mission in the same category.
The operator should begin with a plain mission description. State the task, operating area, control method, people who may be present and the data or material involved. Then state the category basis and the safeguards used.
A crop survey, livestock check and spraying task are not the same operation. Their routes, payloads, ground risks and data flows may differ. Our guides to precision agriculture mapping with drones and how agricultural drone spraying systems work show why the working setup changes with the job.
Do not start with “this is a farm drone”. Start with “this is the work we plan to carry out”.
A UAS file must cover the system and the people
EASA uses “unmanned aircraft system” to mean more than the flying aircraft. A UAS includes the drone, its system and the other equipment used to control and operate it. The command unit is part of that view.
Farm records should match this system-level scope. A file that names only the aircraft leaves out how the operation is controlled. It may also miss the link between the sensor, flight plan, crew and data handling.
A useful system record should cover:
| Record area | What to capture |
|---|---|
| Mission | Task, site, route and intended result |
| UAS setup | Aircraft, control equipment and other operating equipment |
| Payload | Sensor or working payload used for the mission |
| People | Operator, remote pilot and operational management roles |
| Risk controls | The measures tied to the chosen category and site |
| Data | What the system captures, why it is needed and how it is handled |
| Change record | New guidance, the affected procedure and the evidence revised |
EASA defines the drone operator as the person or organisation that owns or rents the drone. The operator may also be the remote pilot, but those roles can be separate. A pilot working for a service company may fly the aircraft while the company remains the operator.
Farm paperwork should reflect that split. Naming “the pilot” is not enough when a farm, contractor or service company owns or rents the system. The file should show who controls the operation, who flies and who checks that the planned safeguards are in place.
Payload choice also belongs in this system record. Agricultural drone sensors explained provides useful technical context, but the compliance file must tie the chosen sensor to the actual mission and data plan.
Privacy must be set before the aircraft flies
EASA’s farm-related privacy case study warns that a drone may capture people living or moving near dwellings and farms. The privacy risk therefore does not vanish because the main subject is a crop, field or fence.
EASA’s Privacy by Design guide is aimed at manufacturers, yet it also speaks directly to pilots and operators that process personal data. It says data protection and privacy should shape technology, processes and flight plans from the start. As little personal data as possible should be processed by default.
For an operator, that turns privacy into a mission-planning task. The team should decide what data it needs before setting the route or sensor. It should also record what happens to unwanted images of workers, neighbours or other people around the site.
EASA sets out seven Privacy by Design principles. They can form a compact checklist in a farm operations file.
| Privacy principle | Question for the mission file |
|---|---|
| Proactive, not reactive | Has the team identified privacy risks before flight? |
| Privacy as the default setting | Does the planned setup limit personal data by default? |
| Privacy embedded into design | Is privacy built into the route, payload choice and data process? |
| Full functionality | Can the task be completed without treating privacy as a barrier to be removed? |
| End-to-end security | How is captured data protected through its full life? |
| Visibility and transparency | Can the operator explain what is being captured and why? |
| Respect for people and a user-centric approach | Does the plan account for people who may be seen or affected? |
The guide says the data controller is the person or entity that decides the purpose and means of processing personal data. In drone work, that may be the operator, client or pilot, depending on the contract and facts.
The compliance file should therefore name the party making those choices. It should not assume that aircraft ownership alone settles control of the data.
Regulatory updates need a controlled path into farm records
EASA describes the European drone framework as a set of regulations, standards, guidelines and good practice. Together, these cover design, operations, administration, safety and data protection.
The framework supports common rules across participating states. EASA also notes that states retain scope over matters such as geographic zones, insurance needs, fines and the minimum age of remote pilots. A common framework does not remove every local check.
A sound farm workflow separates source monitoring from document revision:
- Record the source and its status: proposal, comment, guidance or applicable rule.
- Identify the mission types that the change could affect.
- Compare the new text with the current farm procedure.
- Record what changed and why.
- Revise the linked form, checklist or operations manual.
- Keep evidence that affected staff received the new process.
- Close the change only after the revised process is in use.
This is where CRT material fits. It can alert an operator to a concern under debate, such as whether a rule is clear or enforceable. The operator should not present that comment as though it were an enacted duty.
The same rule applies in reverse. A later decision or updated EASA guide should not sit in an inbox while crews keep using an old checklist. The change log should link the new source to the exact record or procedure it alters.
Traceability is the goal. A reviewer should be able to move from the source, to the change decision, to the revised evidence without guessing.
Farm operators should make the next review mission-based
The next compliance review should begin with the operation, not the aircraft list. Check that each farm mission has a clear task, category basis, system description, role assignment and privacy plan.
Then test whether the documents agree with each other. The named operator should match the owner or renter arrangement. The remote pilot’s role should be distinct where another person or organisation acts as operator.
Add the Privacy by Design principles to the flight-planning pack. Use them when setting routes, choosing payloads and deciding how much data to retain. For image-led work, turning drone imagery into decisions can help teams separate useful crop data from material they do not need.
Finally, create a change log for EASA and national guidance. Record the source, its status, the affected mission and the evidence revised.
The CRT record does not create a stand-alone farm approval process. Its value is that it shows the regulatory method: focus on operational risk, seek practical rules and keep the evidence tied to the work being done.