What Remote ID actually is (and why it's already being enforced)
Do you need Remote ID for your drone? If your drone requires FAA registration, yes — it must broadcast Remote ID under 14 CFR Part 89, enforced since March 16, 2024. You comply one of three ways: a standard Remote ID drone, an FAA-approved broadcast module, or by flying only within a FRIA.
Remote ID is your drone's digital license plate. Under 14 CFR Part 89, an in-scope drone broadcasts its identity and location — plus the location of its control station or takeoff point — so the FAA, law enforcement, and other airspace users can identify it in flight. The rule left its discretionary-enforcement phase behind on March 16, 2024: Remote ID is now a live compliance requirement, not a future one.
This is a separate axis from your Part 107 currency and from the recreational TRUST test — a current remote pilot flying an unregistered, non-broadcasting drone is still out of compliance.
Does your drone even need Remote ID? Start with registration.
Remote ID follows registration: if your drone requires FAA registration, it must broadcast Remote ID. So the real question is "does my drone need to be registered?" — and the answer depends on how you fly:
- Recreational (49 U.S.C. § 44809): register if your drone weighs 0.55 lb (250 g) or more.
- Part 107 (commercial): register regardless of weight. There is no sub-250 g exemption when you fly for work — a 249 g drone on a paid job still registers, and therefore still broadcasts Remote ID.
This is the single most common Remote ID mistake we see: pilots assume the 250 g line that applies to recreational flying also applies to commercial work. It does not.
The three ways to comply (pick exactly one)
There are three — and only three — Part 89 compliance paths. You need one, per drone:
Path 1 — Standard Remote ID drone (§89.110).The drone broadcasts Remote ID from the factory: it carries a Standard Remote ID serial number, and the manufacturer filed a Declaration of Compliance. Many current consumer and enterprise models ship with standard Remote ID built in — check the manufacturer's spec sheet, or search the FAA's UAS Declaration of Compliance list, to confirm yours does. Nothing to bolt on — you fly and it broadcasts.
Path 2 — Remote ID broadcast module (§89.115(a)). Your drone predates the standard, or doesn't broadcast on its own. Attach an FAA-approved broadcast module (a small add-on device), list its serial number on your FAA registration, and fly the operation within visual line of sight for the entire flight — the VLOS requirement is a limit on how you operate the aircraft, not a property of the module itself.
Path 3 — Fly only at a FRIA (§89.115(b)). No standard broadcast, no module? You may still fly — but only inside an FAA-Recognized Identification Area (FRIA), a specific geographic area (often a club field) where non-broadcasting drones are allowed, as long as the operation stays within visual line of sight of that area.
How to tell which path is yours
If your drone is a recent consumer or enterprise model, check the manufacturer's spec sheet or the FAA's Declaration of Compliance list first — many current models ship standard. Older aircraft and DIY builds more often go the module route. The FRIA path is the fallback for drones that can't do either — useful for legacy fleets and educational programs, but it pins you to a specific field.
Not sure? AeroCopilot's Remote ID Setup asks one plain question and routes you to your single path — and it fails closed: if you answer "not sure," it doesn't guess a default and never marks you compliant on a hunch. It's a routing and record-keeping tool: it does not perform an FAA lookup, does not verify a Declaration of Compliance for you, and does not validate FRIA boundaries — you declare the path, we record it and keep the proof.
Record it once, carry it for every ramp check
Declaring your path is step one; proving it on demand is what keeps you out of trouble. When you pick your path in Remote ID Setup, AeroCopilot records it on that specific drone in Drone Fleet — alongside the manufacturer, model, serial, and FAA registration (FA-number). Your Part 107 compliance dashboard then shows registration and Remote ID next to your certificate, recurrent-training currency, and insurance — one place you can open in front of an inspector.
The AI Copilot — included on every tier, with no per-message token caps, grounded only in official FAA/NWS data — can answer "what does my drone need to be compliant?" without ever inventing a rule. Free comes with a daily chat allowance; paid tiers raise it.
What it costs to fly non-compliant
Remote ID enforcement is real. The FAA can assess civil penalties up to $27,500(49 U.S.C. § 46301) for violations, and a remote pilot can face certificate action on top of the fine. "I didn't know the module needed to be visible" or "I thought sub-250 g was exempt" are not defenses. The two-minute check is cheaper than the first violation.
Remote ID is one requirement — here's the rest
Remote ID compliance is necessary, not sufficient. To fly legally you also need current registration, an airworthy aircraft, the right airspace authorization, and — under Part 107 — a valid remote pilot certificate with current recency. AeroCopilot ties these together: airspace intelligence (address-based "can I fly here?" checks against the FAA UAS Facility Map — 378,000 color-coded grid cells — plus TFR overlays and an automatic "do I need LAANC?" read), the §107.65 recurrent-training clock (current, due soon, or expired), and the compliance record above.
Direct LAANC submission to the FAA is not yet live — today the airspace read is live and automatic; in-app submission is coming, so we say so rather than claim it works.