Part 107 · Fleet & flights

Remote ID flag

Each drone carries a Remote ID compliance flag, and the registry surfaces any aircraft that doesn't have it set — so a non-compliant drone is visible rather than assumed. It replaces tracking Remote ID status in your head.

Join the waitlist Request a demo

Launching the first quarter of 2027.

sUAS fleet

Part 107 · registry + flight records

FAA reg #ModelMTOWRemote ID

FA3X8K2M30T1,987 gCompliant

FA9D11QM3E915 gCompliant

FA77B0LEvo II1,250 gMissing

Flight FP-2207 · Class CLAANC # recorded

KPDX 4 nm · altitude cap 200 ft AGL · 107.205 night waiver applied

Remote ID flagged · waivers + LAANC # captured per flight

Illustrative — every screen reflects your own data.

Who it's for

Part 107 operators who need to know a drone's Remote ID compliance posture before assigning it to a job — surfaced on the fleet list rather than carried in someone's head.

What it replaces

Tracking each drone's Remote ID status in your head, where a non-compliant aircraft is assumed fine until it isn't.

What remote id flag gives you

A Remote ID compliance flag per drone
The registry surfaces any drone without it set
A non-compliant drone visible rather than assumed

A compliance flag that surfaces non-compliant drones

As planned, each drone would carry a Remote ID compliance flag on its registry row, and the fleet list would make any aircraft without the flag set stand out. The aim is that a non-compliant drone is something the operator can see before assigning it, and resolve first, rather than something assumed to be fine.

A Remote ID compliance flag per drone
The registry surfaces any drone without it set
A non-compliant drone visible rather than assumed

sUAS fleet

Part 107 · registry + flight records

FAA reg #ModelMTOWRemote ID

FA3X8K2M30T1,987 gCompliant

FA9D11QM3E915 gCompliant

FA77B0LEvo II1,250 gMissing

Flight FP-2207 · Class CLAANC # recorded

KPDX 4 nm · altitude cap 200 ft AGL · 107.205 night waiver applied

Remote ID flagged · waivers + LAANC # captured per flight

A record-keeping aid — not a broadcast monitor

This is built as a flag the operator sets and reads on the record, kept current so the registry reflects the fleet's real Remote ID posture. It is not a live broadcast monitor and not a query against an external Remote ID network. The intent is a record-keeping aid, not a tracking system.

A compliance status you set and maintain on the record
Not a live broadcast monitor or external network query
A record-keeping aid, not a tracking system

Compliance

Part 142 · Part 60 NSP · instructor currency

42 compliant 3 due soon 1 overdue

RequirementDueStatus

14 CFR Part 142 OpSpecsMar 2027Compliant

Part 60 NSP — B737 FFS #1in 11 daysDue soon

CFI currency — Okafor8 days agoOverdue

Aircraft eval renewal — A320in progressIn progress

Facility safety inspectionJan 2027Compliant

Weekly digest to admins · time-limited FAA evaluator access

How an operator uses this

Each drone carries a Remote ID compliance flag on its registry row, and the fleet list makes any aircraft without the flag set stand out — so a non-compliant drone is something the operator can see before assigning it, not something assumed to be fine. It's a flag the operator sets and reads on the record; it isn't a live broadcast monitor or a check against an external Remote ID network.

Illustrative — every screen reflects what's in your own data, nothing more.

How it works

Remote ID flag, step by step

Set the Remote ID compliance flag on each drone's registry row.
Scan the fleet list — aircraft without the flag set are surfaced, not hidden.
Resolve a non-compliant drone before it's assigned to a job.
Keep the flag current so the registry reflects the fleet's real Remote ID posture.

Questions

Remote ID flag — frequently asked

How does the Remote ID flag help?

Every drone has a Remote ID compliance flag, and the registry surfaces any drone without it set, so a non-compliant aircraft is visible on the list rather than assumed compliant in someone's head.

Does it verify Remote ID broadcast in real time?

No. The flag is a compliance status you set and maintain on the record; it isn't a live broadcast monitor or a query against an external Remote ID network. It's a record-keeping aid, not a tracking system.

Keep exploring