Can You Track Celebrity Private Jets? What the Data Shows

Yes, you can track celebrity private jets — and it’s easier than most people realize. I’ve spent years working with aviation datasets, pulling ADS-B feeds, and building flight history tools, and the infrastructure that makes celebrity jet tracking possible is the same infrastructure that powers every serious flight tracking application on the planet. It’s public. It’s real-time. And understanding how it actually works is a lot more interesting than a gossip site listing Taylor Swift’s tail number.

What follows isn’t a list of which celebrities own which planes. It’s an explanation of the data layer underneath all of this — how signals move from an aircraft to your browser, where the gaps are, and why “blocking” your flight data is a lot messier than most celebrities’ PR teams understand.

How Anyone Can Track a Private Jet

Every modern commercial and private aircraft equipped with ADS-B Out hardware broadcasts its position, altitude, speed, and identifier continuously on 1090 MHz. That’s a radio frequency. It’s not encrypted. It’s not gated behind a subscription or a government login. Anyone with a $20 RTL-SDR dongle — I started with a NooElec NESDR Smart for about $24 off Amazon — can receive these signals from aircraft within roughly 200 to 250 miles depending on antenna height.

The signal includes what’s called a squawk code and an ICAO 24-bit address, which is a unique hexadecimal identifier assigned to the aircraft. That address maps directly to a tail number, and the tail number maps to an FAA registry record that is also public. The registry lists the registered owner, the aircraft type, and the state of registration. So the chain from “aircraft in the sky” to “who owns it” is technically straightforward.

The Tools Most People Actually Use

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

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

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

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 a person’s name. That’s intentional, and I’ll get to why that doesn’t actually solve the problem in the last section.

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

Frustrated by how scattered the documentation on this was, I built my own lookup workflow after piecing together about a dozen different sources. 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 converter (there are free ones 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 tools like OpenSky Network for academic-level historical datasets going back years

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

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 it was called the Block Aircraft Registry Request program. The name has changed multiple times, which tells you something about how reactive this whole system has been.

Under LADD, an aircraft owner can request that their tail number and ownership information be removed from the data feed that the FAA provides to commercial flight tracking services. If approved, services like FlightAware and Flightradar24 will show the flight as a generic blocked aircraft — you’ll see 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 has LADD protections on certain tracking platforms.

The Technical Gap in LADD

Here’s the thing that most celebrity PR advisors 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 operated by hobbyists and community networks are still receiving those signals. ADS-B Exchange explicitly does not honor LADD requests.

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. It is not signal suppression.

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

The Jack Sweeney Story — When Flight Data Became Political

Probably should have opened with this section, honestly, because it’s what most people googling 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 called @ElonJet that automatically posted Elon Musk’s flight departures and arrivals in near real-time. The bot pulled position data, matched it to the known tail number, and tweeted when the aircraft moved.

The timeline after that escalated quickly:

• 2021 — Musk offered Sweeney $5,000 to take down the account. Sweeney declined, 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 (Instagram and Facebook) banned Sweeney’s jet-tracking accounts, citing policy violations. Sweeney argued the data was entirely public-source.
• 2023–2024 — Legal threats from Musk’s legal team. Sweeney continued operating bots on platforms that would host them, expanding to track other high-profile aircraft including those of politicians and executives.
• 2025 — Platform-level suppression increased, but Sweeney’s data operation remained technically functional because the underlying signals never changed.

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

Inspired by Sweeney’s methodology, dozens of similar accounts launched tracking jets belonging to politicians, executives, and entertainment figures. The pattern is now widespread enough that several European countries have begun discussing regulatory frameworks — not to block the signals, but to establish legal frameworks around the publication of derived location data. That’s a meaningful distinction. The raw signal is one thing. The curated, named, published 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 appears as a moving object on the map. You can see:

• Real-time position (latitude/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 linkage. 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. That’s manual work, but it’s not impossible.

Shell Companies and Trust Registrations

The more sophisticated privacy strategy is 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 “Elon Musk” in the registry, you find “Falcon Landing LLC” or a trust with an opaque name.

Early in my work with aviation data, I made the mistake of assuming registry name matches were comprehensive. They’re not. Beneficial ownership — who actually controls the LLC — is not disclosed in FAA records. That’s a real privacy layer, not a cosmetic one.

The workaround researchers use is correlating known aircraft to individuals through other means — historical photos at known-use airports, FBO fuel records obtained through FOIA, and the fact that a given aircraft will often be photographed before the owner decides to obscure ownership. Once a tail number is publicly associated with a person through any source, the shell company doesn’t retroactively help.

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 on offer.

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.

Military aircraft and certain government operations do operate 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 not 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 information to track a pop star’s weekend travel is a side effect of designing a transparent, redundant, publicly-receivable safety broadcast system — and no amount of platform-level blocking changes the underlying physics of what 1090 MHz does.