About
NHL Flights shows where each team's charter aircraft is: expected, airborne, or landed. The schedule tells us when a team must move between cities. Community ADS-B receivers tell us where the aircraft are. A matcher pairs the two and keeps a history of every flight it identifies. Matches are automatic and sometimes wrong; a "likely" tag means the match is not certain yet.
Get the app: App Store · Google Play (closed testing)
What the statuses mean
- Expected
- The schedule says the team should fly in this window: after a road game, the day before the next one, or the morning of. No flight has been seen yet.
- Filed
- A flight plan is on file for one of the known charter aircraft, from FlightAware when a key is configured.
- Boarding soon
- Within 45 minutes of the planned departure. The aircraft has not moved yet; this is read from the plan, not seen.
- Airborne
- The aircraft is in the air and the matcher believes the team is aboard. "Last seen N min ago" means the community receivers lost it, which happens over water and in thin coverage.
- Landed
- Arrived. "Estimated" means the landing airport was inferred from where the aircraft disappeared low and slow rather than seen on the ground.
- Corrected
- Reviewers confirm, reject or move matches when they turn out to be wrong, and the bots take their posts down. Every such decision is listed on the corrections page.
- Likely
- The flight fits the route and the timing but nothing identifies the team: no known tail, operator or charter flight number. Likely flights count toward the team's history but are shown with this tag until a reviewer confirms them.
- Unknown
- The travel window closed with no flight identified. For a trip under about 160 km the team may have gone by road.
- Positioning
- An aircraft from a charter fleet flying with no team matched to it. It may be empty on its way to or from a pickup, or it may be carrying another customer: these aircraft fly for other clients too, and the site cannot tell. Shown in grey on the map and never counted against a team.
Data sources
- Live aircraft positions: airplanes.live and adsb.lol, with adsb.fi as a backup when both are unavailable. Historical traces from adsb.lol, available under the Open Database License.
- Schedule and game state: the NHL's public API.
- Airport reference data: OurAirports, public domain.
- Map tiles: OpenFreeMap.
How a flight gets matched to a team
- The schedule sets the expectations. For every game the worker works out when each team has to move and between which airports: home after a road game, on to the next city, in the day before or the morning of a game, and a trip home when a road break runs four days or more. Each expected movement gets a time window and a prior based on how teams usually travel. Neutral-site games put both teams on the road.
- Community receivers show the aircraft. The worker follows the known charter fleets on airplanes.live and adsb.lol, turns their position streams into flights with a takeoff and a landing airport, and fills gaps from the adsb.lol trace archive. An airport is "observed" when the aircraft was seen on the ground there and "inferred" when it vanished low and slow nearby. A flight that reappears within eight hours at a plausible speed is joined to its earlier part, and a technical stop is treated as one trip.
- Each flight is scored against each expected movement. Six parts add up to one: origin (0.25), destination (0.25), timing inside the window (0.2), the aircraft's history with the team (0.15), the flight number (0.1) and the aircraft type (0.05). Some things end a comparison outright: a reviewer rejected the pair, an observed airport contradicts the movement, the aircraft is not registered in the US or Canada, or the timing is impossible for the distance.
- Only identified flights publish on their own. A score of 0.8 or more becomes an automatic match and 0.6 or more a "likely" one, but only when something identifies the team: a tail number the team has used, a charter operator's flight number, or a registration flown as its own callsign. A scheduled airline flight number or a known positioning pattern sends the flight to review instead, and an aircraft that is not an airliner is never more than likely. When two movements fit the same flight within 0.2 of each other, the matcher leaves it for a reviewer rather than guess.
- People check the edges. Reviewers confirm, reject or move matches from a queue that shows the evidence and every visitor report. Their decisions adjust the priors for exactly the aircraft and team involved, nothing else, and each one is listed on the corrections page. The bots delete their posts when a match is withdrawn and post a correction when another team takes the flight over.
The site cannot see who is on board. "Matched" means the aircraft, the route and the timing fit the schedule, nothing more. Flights the receivers never saw are missing, so every total here is a floor.
Fuel and CO2 estimates
Each flight shows an estimate of the jet fuel burned and the CO2 released. The estimate multiplies the time in the air, plus a short taxi allowance, by a typical block-average burn rate for the aircraft type (about 2,500 kg per hour for an Airbus A320 or Boeing 737-800). Burning one kilogram of jet fuel releases about 3.16 kg of CO2. Team charters carry far fewer people than an airline cabin, so the aircraft is lighter and the real burn is usually a little lower than the figure shown. Treat the numbers as rounded estimates, not measurements.
Follow along
A bot posts every identified departure and arrival to Mastodon at @[email protected] and to Bluesky at @nhlflights.ca. Follow either account to get the updates in your timeline, or follow one team's hashtag there. Mastodon works from any Fediverse account. Every team page also has an RSS feed and a JSON feed of its flights (for example /team/SEA/feed.xml), and /feed.xml carries the whole league. Feeds list tracked flights only, never filed plans. Each team page also offers a calendar subscription (for example /team/SEA/travel.ics) with one event per expected movement spanning its travel window, updated as flights are tracked; paste the address into any calendar app that subscribes to a URL. Developers and researchers can take every tracked flight as JSON or CSV from the API, under the Open Database License.
Support the site
NHL Flights is free to use and costs a little to run. If it is useful to you, buy me a coffee.
This site is a hobby project. It is not affiliated with the NHL, any team, or any airline. Aircraft are identified by their public ADS-B transponder broadcasts; no private information is collected.