EU drone operator registration: operator IDs vs pilot competency

EU drone operator registration is one of two things a person or company has to sort out before flying under European rules, and it is easy to mix up with the other. Registering as an operator identifies who is responsible for the aircraft and produces the operator ID that goes on every drone you fly. Proving pilot competency is a separate obligation that shows the person at the controls has the right training. Under Regulation (EU) 2019/947, an organisation registers once as the operator, while each of its pilots has to hold the competency their operations require.

This guide separates the two: what operator registration is and who has to do it, how it differs from the pilot competency certificates, where the A1/A3 test and A2 certificate fit, and how an organisation with several pilots keeps operator and competency records straight. Getting the distinction right matters because a valid operator ID does nothing for a pilot who has not passed the required training, and a trained pilot still needs a registered operator behind the flight.

What operator registration is

An operator, in EU terms, is the person or organisation responsible for the drone operation, which is a different role from the remote pilot who physically controls the aircraft. For a private individual the two are usually the same person, but for a business the company is the operator and its staff are the pilots. You register as an operator with the national aviation authority of the Member State where you live, or where your business has its principal place of business, and you can only register in one Member State even if you fly across several.

Registration is required once the drone has a maximum take-off mass of 250 grams or more, or carries a sensor able to capture personal data and is not a toy, which covers nearly every camera drone. Once registered, you receive a single operator registration number. That number has to be displayed on every drone you operate and uploaded into the drone's remote identification system where the aircraft supports it. Because the registration identifies the operator rather than the aircraft, one number covers your whole fleet, and it is valid across the entire EU.

Why pilot competency is a separate step

Registration answers who is accountable; it says nothing about whether the person flying knows how to fly safely. That is what remote pilot competency covers, and it is a distinct requirement that attaches to the individual, not the operator. EASA's explainer on the difference between drone operators and pilots is a useful reference here, because the two roles are constantly confused. A pilot must hold proof of competency before the first flight whenever the drone is 250 grams or more, whether or not that pilot is also the registered operator.

The competency required depends on the subcategory of the Open category the operation falls under. The A1/A3 route is a free online training course and theory exam run through the national authority, valid for five years, and it covers flying over some people or well away from everyone. The A2 subcategory, which allows flying closer to uninvolved people, needs an additional certificate of remote pilot competency: the online training plus self-declared practical training and a further, proctored theory exam. Certificates issued in one Member State are recognised across all of them.

Managing operator and pilot records across a team

For a solo pilot, the operator ID and the competency certificate belong to the same person and rarely cause confusion. For an organisation, the two pull apart: the company holds one operator registration, while every pilot carries their own competency certificate with its own five-year expiry, and different pilots may be qualified for different subcategories. Keeping track of who is cleared for A2 work, who is limited to A1 or A3, and which certificates are approaching renewal becomes a real administrative job as the roster grows.

Access to those records is part of the same problem. A pilot assigned to one project has no need to see the operator files, client details, or flight records for jobs across the business, and software that can partition each pilot's view to only the jobs they were assigned keeps a growing team organised. Pair that with a clear register of every pilot's competency and its expiry, filed against the one operator registration the business holds, and the operation can show at any moment who is accountable and who is qualified.

Turning operator and competency status into a record

During an inspection or a client review, the questions are who the registered operator is, whether the operator ID is displayed and uploaded to remote ID, and whether the specific pilot who flew held the right competency for that subcategory. Answering all three from memory, or from a folder of certificate photos, is slow and easy to get wrong when several pilots and several subcategories are in play.

A record that keeps the operator registration in one place, and every pilot's competency certificate tracked with its expiry and the subcategories it covers, turns those questions into quick lookups. Tie each certificate to the pilot who holds it and each flight to the pilot who flew it, and the operation can show that a given operation had a registered operator behind it and a qualified pilot at the controls. The registration and the certificate are the permissions, and the record is what proves both were in order on the day.

Common mistakes with EU drone operator registration

Treating operator registration as pilot qualification. Registering as an operator produces an ID and identifies who is responsible, but it proves nothing about flying skill. Every pilot still needs the A1/A3 or A2 competency for the operation, and the two requirements never substitute for each other.

Registering the drone instead of the operator. The EU registers the operator, not each aircraft, so one operator number covers a whole fleet. Expecting a separate registration per drone, as some other countries require, leads people to look for a step that does not exist here.

Registering in more than one Member State. You register once, in your country of residence or principal place of business, and that registration is valid across the EU. Registering again in another Member State is unnecessary and not permitted, though local rules like insurance can still differ.

Skipping the A2 certificate for close-to-people work. The free A1/A3 online test does not cover the A2 subcategory. Flying closer to uninvolved people needs the additional certificate of remote pilot competency, and using an A2-class drone near people without it puts the operation outside the rules.

Forgetting the operator ID has to be shown and broadcast. The number is not just held on file; it has to be displayed on every drone and uploaded into the remote identification system where supported. An unmarked aircraft, or one missing from remote ID, is a gap even when the operator is properly registered.

FAQ

Is EU drone operator registration the same as a pilot licence?

No. Operator registration identifies the person or company responsible for the drone and gives you an operator ID for the aircraft. A pilot licence, in the form of the A1/A3 or A2 competency certificate, is a separate requirement that proves the person flying has been trained.

Do I register once or in every EU country I fly in?

Once. You register with the national aviation authority of your country of residence or principal place of business, and that single operator registration is valid across the whole EU. You cannot hold registrations in more than one Member State at the same time.

What is the difference between the A1/A3 test and the A2 certificate?

The A1/A3 test is a free online theory exam covering flight over some people or far from everyone. The A2 certificate adds self-practical training and a proctored exam, and it is what allows flying closer to uninvolved people in the A2 subcategory.

Does my operator ID go on the drone or stay on file?

Both. You keep the registration on record, and the operator number also has to be displayed on every drone you fly and uploaded into the aircraft's remote identification system where it supports that function, so the operator is identifiable in the air.

Closing thought

EU drone operator registration and pilot competency answer two different questions: who is responsible for the operation, and whether the person flying is trained. An organisation registers once as the operator and displays that ID on every aircraft, while each pilot separately holds the A1/A3 or A2 competency their work requires. Confusing the two leaves a real gap in either accountability or qualification.

If you are running an EU drone operation and separating operator registration from pilot competency across your team, FlybyOps was built for the operational record problem at the center of regulated drone work. Role-based access control, a pilot registry with certification and currency tracking, a document vault with expiration tracking, and an append-only audit log are all part of how the platform keeps each operator ID and pilot competency record scoped to the people who need to see it.