A free check for US addresses near the airports we cover, from the last two weeks of recorded flight tracks.
Checking the address…
First the US Census geocoder finds the address on the map, then our server counts every recorded aircraft track that passed near it in the last two weeks. That usually takes about 15 seconds.
Results for
| Distance from this address | Average track events |
|---|
Each row counts recorded aircraft tracks that came within that distance, so the wider circles include the narrower ones.
FlightPath Home for iPhone goes further for the exact address: a modeled loudness estimate with the method behind it, a map of the recorded flight paths, day-by-day replay, live aircraft nearby, and saved homes you can come back to.
Free to download, with 3 address checks a month, 2 saved homes and live nearby traffic. Replay, unlimited checks and saved homes, and PDF export come with FlightPath Pro, a subscription priced in the App Store.
Traffic levels, by average track events within 1 mile: very frequent 200 or more a day, frequent 50 to 199, occasional 10 to 49, infrequent 1 to 9.9, rare fewer than 1.
When you press Check, our server passes the address to the US Census Bureau's public geocoder, which turns it into map coordinates. The Census Bureau sees our server, not your device, and handles the request under its privacy policy.
We round those coordinates to three decimal places (about 110 m, roughly a city block) and send only that rounded point to our flight-data server. The address itself goes no further, and we don't store it or log it.
The result for each rounded point is cached for up to 12 hours so the next check nearby is quick; the cache holds the point and the counts, never the address. To enforce the 10-checks-an-hour limit, we keep a count for up to an hour under a scrambled identifier derived from your connection, not your IP address itself. Cloudflare, which hosts this site, processes connection information such as your IP address to deliver it. More in our privacy policy.