Can You Track Celebrity Private Jets? What the Data Shows

Celebrity jet tracking has gotten complicated with all the legal threats, platform bans, and PR spin flying around. As someone who spent years digging through aviation datasets, pulling ADS-B feeds, and building flight history tools from scratch, I learned everything there is to know about how this infrastructure actually works — and it’s a lot more interesting than any gossip site’s list of tail numbers. The system that makes celebrity tracking possible is the same system powering every serious flight application on the planet. It’s public. It’s real-time. And it wasn’t built with Taylor Swift’s publicist in mind.

What follows isn’t a celebrity jet registry. It’s a breakdown of the actual data layer underneath all of this — how signals travel from an aircraft to your browser, where the real gaps are, and why “blocking” your flight data is messier than most celebrity PR teams want to admit.

How Anyone Can Track a Private Jet

But what is ADS-B? In essence, it’s a broadcast system — every modern commercial and private aircraft equipped with ADS-B Out hardware continuously transmits its position, altitude, speed, and identifier on 1090 MHz. But it’s much more than that. That frequency isn’t encrypted. It isn’t locked behind a government login or a paid subscription. Anyone with a $20 RTL-SDR dongle — I started with a NooElec NESDR Smart, roughly $24 off Amazon — can pick up these signals from aircraft within 200 to 250 miles, depending on how high your antenna is sitting.

Each broadcast includes a squawk code and an ICAO 24-bit address — a unique hexadecimal identifier permanently assigned to that aircraft. That address maps to a tail number. The tail number maps to an FAA registry record, which is also public. The registry lists the registered owner, aircraft type, and state of registration. So the chain from “plane in the sky” to “who owns it” is, technically speaking, pretty short.

The Tools Most People Actually Use

Almost nobody decodes raw 1090 MHz signals by hand. The practical workflow looks like this:

1. Visit FlightAware, Flightradar24, or ADS-B Exchange
2. Search the tail number — called an N-number for US-registered aircraft
3. Cross-reference with the FAA Aircraft Registry at registry.faa.gov
4. Pull historical flight logs to build trip patterns over time

ADS-B Exchange deserves a specific callout here. Unlike FlightAware or Flightradar24, it’s a community-run aggregator that has historically refused to honor blocking requests from aircraft owners. Their position — that ADS-B signals are public radio transmissions and scrubbing them from a database is censorship of public data — has real technical backing. The signal doesn’t stop broadcasting just because one website removes the record. That’s what makes ADS-B Exchange endearing to us aviation data people.

The FAA registry lookup is where the celebrity angle kicks in. Search a tail number and you’ll often find it registered to an LLC or a trust rather than an actual person’s name. That’s intentional — and I’ll get to why it doesn’t actually solve the problem.

Step-by-Step — Finding a Specific Aircraft’s History

Frustrated by how scattered and contradictory the documentation on this was, I eventually built my own lookup workflow after piecing together about a dozen different sources over several months. Here’s the condensed version:

• Start at registry.faa.gov/aircraftinquiry — search by name, city, or aircraft model to find associated tail numbers
• Pull the ICAO hex code using a free converter at airframes.org
• Search that hex code on ADS-B Exchange for unfiltered historical data
• Use FlightAware for more structured trip logs if the aircraft isn’t LADD-blocked
• Cross-reference with OpenSky Network for academic-level historical datasets going back several years

The whole process takes about ten minutes once you know the aircraft identifier. Honestly, that’s the uncomfortable reality for anyone trying to maintain jet privacy in 2026.

The LADD Program and How Celebrities Block Tracking

The FAA runs a program called LADD — Limiting Aircraft Data Displayed. It was formerly called the PIA program, Privacy ICAO Address, and before that the Block Aircraft Registry Request program. The name has changed multiple times — which tells you something about how reactive this entire system has been to public pressure.

Under LADD, an aircraft owner requests that their tail number and ownership information be removed from the data feed the FAA provides to commercial tracking services. If approved, platforms like FlightAware and Flightradar24 display the flight as a generic blocked aircraft — a dot moving across the map with no registration attached.

Taylor Swift’s team filed a LADD request for her Dassault Falcon 7X, registration N898TS — since sold and re-registered — after significant public attention around her flight patterns in 2022. Elon Musk’s Gulfstream G650ER, registered under Falcon Landing LLC, also carries LADD protections on certain tracking platforms.

The Technical Gap in LADD

Here’s what most celebrity PR advisors apparently don’t understand — or understand and choose not to publicize. LADD only works on platforms that voluntarily honor it. The FAA has no technical mechanism to suppress an ADS-B broadcast. The aircraft is still transmitting. Ground stations run by hobbyists and community networks are still receiving those signals. ADS-B Exchange does not honor LADD requests — full stop.

So when Taylor Swift’s team blocked her tail number on FlightAware, it disappeared from FlightAware. It did not disappear from ADS-B Exchange. It did not disappear from anyone running their own SDR receiver near an airport she used. The blocking is a visibility restriction on one data intermediary — not signal suppression.

This is a genuine infrastructure point, not just a gotcha. ADS-B was designed for air traffic safety and collision avoidance. Privacy was never a design goal. Retrofitting privacy onto a broadcast-by-design system through voluntary database suppression is technically fragile — always has been.

The Jack Sweeney Story — When Flight Data Became Political

Probably should have opened with this section, honestly, because it’s what most people searching celebrity jet tracking actually want to understand. But the technical foundation matters for making sense of what happened.

In 2020, Jack Sweeney was a college student at the University of Central Florida. Using publicly available ADS-B data, FAA registry lookups, and a Python script pulling from the ADS-B Exchange API, he built a Twitter bot — @ElonJet — that automatically posted Elon Musk’s flight departures and arrivals in near real-time. The bot pulled position data, matched it to a known tail number, and tweeted whenever the aircraft moved. Simple setup. Massive consequences.

The timeline after that escalated fast:

• 2021 — Musk offered Sweeney $5,000 to take the account down. Sweeney declined and countered with $50,000 or an internship. Musk stopped responding.
• Late 2022 — Musk acquired Twitter. Within weeks, @ElonJet was suspended. Sweeney moved the bot to Mastodon, Bluesky, and other platforms.
• Early 2023 — Meta banned Sweeney’s jet-tracking accounts across Instagram and Facebook, citing policy violations. Sweeney argued the data was entirely public-source.
• 2023–2024 — Legal threats from Musk’s team. Sweeney kept operating on platforms willing to host him, expanding to track politicians and executives.
• 2025 — Platform-level suppression increased. The underlying signals never changed.

What Sweeney’s case demonstrated — from a pure data perspective — is that the bottleneck was never the data itself. It was the distribution layer. Musk could pressure Twitter because he owned it. Meta has its own liability math around harassment claims. But no platform owns the 1090 MHz frequency. No terms of service applies to radio waves.

Dozens of similar accounts launched in Sweeney’s wake, tracking jets belonging to politicians, executives, and entertainment figures. The pattern spread wide enough that several European countries began discussing regulatory frameworks — not to block the signals, but to establish legal boundaries around publishing derived location data. That’s a meaningful distinction. The raw signal is one thing. The curated, named, publicly-posted dataset is another.

What Data You Can and Cannot See

Let me be specific about what’s actually visible versus what can be obscured — because the answer varies more than the headlines suggest.

What Remains Visible Even With LADD Blocking

Even a fully LADD-blocked aircraft, on a platform that honors the block, still shows up as a moving object on the map. You can see:

• Real-time position — latitude and longitude
• Altitude in feet
• Ground speed in knots
• Track heading
• Departure and arrival airports in most cases
• Aircraft type in some implementations

What you lose is the registration number and the ownership link. A knowledgeable analyst can sometimes re-identify a blocked aircraft by correlating its flight patterns, performance characteristics, and airport usage against known registrations from non-blocking platforms. Manual work — but not impossible work.

Shell Companies and Trust Registrations

The more sophisticated privacy play happens at the registration level rather than the data display level. Registering an aircraft under an LLC or a Delaware statutory trust severs the obvious name-to-tail-number connection in the FAA registry. Instead of finding a person’s name, you find “Falcon Landing LLC” or a trust with an opaque, deliberately unremarkable name.

Don’t make my mistake. Early in my work with aviation data, I assumed registry name matches were comprehensive. They’re not — beneficial ownership, who actually controls the LLC, isn’t disclosed in FAA records. That’s a real privacy layer, not a cosmetic one.

The workaround researchers use involves correlating known aircraft to individuals through other channels — historical photos taken at known-use airports, FBO fuel records obtained through FOIA requests, and the simple fact that an aircraft is often photographed publicly before its owner decides to obscure the ownership. Once a tail number gets publicly linked to a person through any source, the shell company stops helping retroactively.

The Practical State of Jet Privacy in 2026

Complete flight privacy for a US-registered aircraft operating under ADS-B Out requirements is not achievable through currently legal means. The FCC mandates the broadcast. The FAA mandates the transponder. LADD blocks one visibility layer on compliant platforms. That’s the ceiling of what’s available.

Some ultra-high-net-worth individuals operate aircraft registered in foreign jurisdictions — Cayman Islands, Isle of Man, Aruba — where different registry rules apply and ICAO hex codes may not resolve cleanly against public databases. That adds friction. It doesn’t add real privacy, because the signal still broadcasts regardless of where the paperwork lives.

Military aircraft and certain government operations do run with suppressed or spoofed transponder data. That capability is not available to private citizens or celebrities — regardless of net worth. The gap between what a government can do for signal privacy and what a billionaire can do is wide, and it isn’t narrowing.

The data infrastructure was never built with celebrity privacy in mind. It was built to keep planes from hitting each other. The fact that the same system surfaces enough detail to track a pop star’s weekend travel is a side effect of designing a transparent, redundant, publicly-receivable safety broadcast — and no amount of platform-level blocking changes the underlying physics of what 1090 MHz does.