PUBLIC RECORD MATCH NO BEHAVIOR CLAIM
Federal fleet & front companies.
Newsrooms have published the fictitious corporate names federal agencies use to register surveillance aircraft. We take those names, match them against the FAA Civil Aircraft Registry, and then join the result against detections our own receivers recorded. Presence in this table means one thing only: that aircraft flew through our footprint. It is not a claim that any specific flight targeted anyone.
- Registered aircraft matched
- …
- Detected in our footprint
- …
- Named registrants tracked
- …
Registrant directory
Fleet size is the number of aircraft in the FAA registry under that exact registrant name. Detected is how many of those aircraft appear in our own detection profiles.
| Registrant | Attribution | Fleet size | Detected here |
|---|---|---|---|
| Loading registry… | |||
Aircraft we actually detected
Every row below is one tail we recorded ourselves. Lowest altitude is the minimum recorded for that tail across its whole profile — a single low pass, not an average behavior.
| Aircraft | Registrant | Type | Detections | Lowest alt. | Primary county | Last seen |
|---|---|---|---|---|---|---|
| Joining registry against detections… | ||||||
How to read this honestly
- Front-company names come from published journalism, not from our machine layer. They are labelled as reported.
- The FAA match is an exact registrant-name match against the public registry. Common words are excluded to avoid false hits.
- Detection counts are raw ADS-B/MLAT pings, not sorties. A single orbit produces thousands of pings.
- Nothing on this page asserts a purpose, target, or unlawful act. Purpose requires records, not telemetry.
All data referenced here is drawn from public sources — FAA ADS-B broadcasts, the FAA Civil Aircraft Registry, and published reporting — and is independently verifiable by any member of the public. Cross-check any tail on Aircraft Dossiers, Verify, or Methodology.