# Those tiny planes have a very large supply chain

Flightradar24 is a reminder that the visible map may be the easy part of a data product.

By AppRill Editorial · Published 2026-09-08
Canonical: https://apprill.app/blog/flightradar24-network-behind-map

The map looks like a collection of tiny moving planes. The service behind it is much less tiny.

[Flightradar24's company page](https://www.flightradar24.com/about) describes a receiver network combined with flight-plan, schedule and aircraft information. It also reports more than 100 million app downloads. That is a company-reported cumulative figure observed on September 8, 2026, not a count of current paying users or an independently verified revenue measure.

The important research question is what a new entrant would need to reproduce to offer a comparable service.

## Draw the system outside the screen

List data collection, coverage, normalization, identity matching, refresh frequency, error correction and distribution rights. Then add uptime and support. A prototype can imitate a map while having almost none of those capabilities.

For a small data business, a narrower scope may be far more realistic: one audience, one recurring decision and a small number of reliable sources. Narrowing is useful only when that audience still has a valuable job to do.

## Find the source of defensibility

A distinctive interface can be copied more readily than a trusted supply of difficult-to-obtain information. Conversely, a large dataset without an understandable workflow can fail to help anyone. A viable product needs the two to meet.

Before choosing an idea, ask what happens if the easiest source disappears. Can you continue serving customers legally and economically? Is there an alternative source, or is the entire business a presentation layer on one fragile dependency?

## Build the smallest complete service

A good early version does not need global coverage. It does need to explain what it covers, when observations were collected and what an absent result means.

The lesson is not that small teams should avoid data products. It is that the first architecture diagram should extend beyond the browser window. The planes are the picture. The supply chain is a large part of the product.


## Sources
- [Flightradar24: About the service](https://www.flightradar24.com/about)