FAA DroneZone: how to set up and manage your operator account

An FAA DroneZone account is the front door to almost every administrative interaction a commercial drone operation has with the FAA. Aircraft registration, Part 107 waiver applications, airspace authorization requests outside LAANC, accident reports, and FAA-Recognized Identification Area applications all run through the same portal. For a solo pilot, the account is a minor errand. For a company running multiple pilots and aircraft, it becomes a piece of operational infrastructure, and the choices made at setup determine who controls registrations and filings for years.

This article walks through creating the account at the current portal, choosing between the recreational and Part 107 paths, structuring an account for a company rather than an individual, and the routine management work the account requires. It also covers what the portal does not do, because several tasks operators expect to find in DroneZone live elsewhere in the FAA's systems.

Creating the account and choosing the right type

The portal lives at faadronezone-access.faa.gov, and setup starts with an email address, a password, and agreement to the government system use notice. The email address matters more than it looks. The FAA sends registration confirmations, renewal reminders, and case correspondence to it, so a company should use a monitored operations address rather than one employee's personal inbox. After the account exists, the portal asks which services you need, and the split between recreational flyer and Part 107 operator determines the dashboard you see.

Commercial operations belong on the Part 107 side. The Part 107 dashboard registers each aircraft individually at five dollars per airframe, while the recreational path issues one number covering all of a flyer's personal aircraft. Choosing the wrong side is a common early mistake, because a recreational number does not cover commercial flying. The two registration types are also separate on the back end, so an aircraft registered recreationally has to be registered again before it flies paid work.

Setting up a company account rather than a personal one

A drone program should hold its registrations under the business, and the portal supports that if the account is built deliberately. The FAA's guidance for new drone businesses on the FAA DroneZone portal recommends building the account around the organization rather than one individual, entering the business name in the Part 107 account name field during profile setup so registrations and waivers issue under the entity rather than a person.

The reason is continuity. Registrations, waiver applications, and their histories live inside the account that filed them, and the portal does not offer a clean way to move a filing history between accounts when an employee leaves. Companies that let a founding pilot register the first aircraft personally often discover the problem two years later, when the renewal notices are going to an inbox nobody checks. Set the authorized representative, keep the credentials in the company password manager, and treat account access as something you grant and revoke like any other system.

What you manage through the account over time

Registration is the recurring workload. Each aircraft entry needs the manufacturer, model, and serial number, and for aircraft with Standard Remote ID, the serial number filed must be the Remote ID serial, which cannot appear on more than one registration at a time. Registrations expire on a three year cycle, and the renewal function appears in the dashboard as each one approaches its date. Sold, destroyed, or exported aircraft get canceled from the same inventory screen, and account details have to be updated within fourteen days when they change.

The account also carries the program's requests to the FAA. Part 107 waiver applications, airspace authorizations for situations LAANC does not cover, accident reports required under Part 107, and FRIA applications for community organizations and schools all file through DroneZone forms. Each submission gets a case entry in the dashboard, which becomes the record of what was asked, when, and what the FAA answered. Exporting or screenshotting those case records into your own files is worth the minute it takes, because access to a portal is not the same as custody of a record.

Where the account ends and the record begins

It is tempting to treat DroneZone as the drone program's filing cabinet, since so much passes through it. The portal is a submission system, though, and it holds only what the FAA needs, organized for the FAA's convenience. It does not know which project an aircraft flew last month, which pilot is assigned to it, or that the insurance certificate tied to that airframe expires in March. The gap between what the regulator tracks and what an operation needs to know about itself is the space where programs get caught.

A mature operation mirrors the portal's contents into its own records. Every registration certificate gets downloaded and filed against the aircraft it covers, with the expiration date tracked somewhere the whole team can see. Every waiver and authorization is stored with the jobs flown under it. When an inspector, a client, or an insurer asks a question, the answer should come from the program's own system in seconds, with the DroneZone account serving as the authoritative backstop rather than the first place anyone looks.

Common mistakes in FAA DroneZone account management

Registering under the wrong type. New commercial operators sometimes create a recreational flyer account because it appears first, then register aircraft under the exception for recreational flyers. That number does not cover paid work, and the aircraft must be registered again on the Part 107 side before commercial flights.

Tying the account to one person. When registrations live in an employee's personal account, the program loses clean access the day that person leaves. Build the account around an organizational email and the DBA field, and store the credentials where the company controls them.

Letting the confirmation email be the only record. Registration certificates should be downloaded, filed against the aircraft, and tracked for expiration. Operators who rely on searching an inbox during an audit lose time they do not have.

Forgetting the fourteen day update rule. Address, email, and representative changes must be updated in the portal within fourteen days. Stale account details mean renewal notices and case correspondence go somewhere nobody is watching.

Assuming every FAA task lives in DroneZone. Pilot certification runs through IACRA and the testing system, and LAANC authorizations come from approved service providers. Teams that hunt for those functions in DroneZone lose afternoons to the wrong portal.

FAQ

Does every pilot in a company need a DroneZone account?

No. The account belongs to the aircraft owner, which for a company operation should be the business itself. One organizational account holds the registrations and filings, while pilot certification is an individual matter handled through separate FAA systems.

How much does it cost to register aircraft through DroneZone?

Registration under Part 107 costs five dollars per aircraft, paid by card through the portal, and each registration lasts three years. The recreational option is five dollars for one certificate covering all of an individual flyer's personal aircraft.

Can one DroneZone account cover recreational and Part 107 flying?

Yes, one login can hold both dashboards, but the registrations stay separate. An aircraft registered under the recreational exception is not registered for commercial work, and moving between the two types means registering the aircraft under the other rule.

What information does the FAA require for each registered aircraft?

The application asks for the owner's name, physical address, email, and phone, plus the aircraft manufacturer, model, and serial number. For Standard Remote ID aircraft, the serial filed must be the Remote ID serial, listed on only one registration at a time.

Closing thought

A DroneZone account looks like a five minute signup, and for a hobbyist it is. For a commercial operation it is the administrative spine of the program's relationship with the FAA, and the decisions made at setup, which email, whose name, which account type, quietly determine how much friction every future registration, renewal, and waiver carries. Build it like infrastructure, then keep your own copies of everything it holds.

If you are setting up the FAA accounts behind a new drone program, FlybyOps was built for the operational record problem at the center of regulated drone work. A pilot registry that tracks certification and currency, an equipment registry with per-airframe history, a document vault with expiration tracking, and an append-only audit log are all part of how the platform keeps every registration, certificate, and account detail behind a program findable when a login is not.