Ashley Childress 9ec3c2ca48 fix: publish every per-source registry CSV, not just the joined one
Each source accumulates by reading its own previous release asset, but only the joined
registry and the FAA CSV were published. Transport Canada could therefore never find a
prior asset and would have rebuilt from a single day on every run, permanently.

- stage the joined CSV and every per-source asset into one flat directory before upload,
  so the artifact has a single root and nothing is lost to the least-common-ancestor rule
- carry the per-source CSVs into the release by glob, so a new source needs no edit here

Generated-by: Claude Opus 5 <noreply@anthropic.com>
2026-09-11 11:06:51 -04:00
2026-03-18 14:29:13 -04:00
2026-03-10 05:08:19 -04:00
2026-02-13 11:37:31 -05:00
2026-02-13 11:37:31 -05:00

OpenAirframes.org

OpenAirframes.org is an open-source, community-driven airframes database.

The data includes:

  • Registration information from Civil Aviation Authorities (FAA)
  • Airline data (e.g., Air France)
  • Community contributions such as ownership details, military aircraft info, photos, and more

For Users

A daily release is created at 06:00 UTC and includes:

  • openairframes_community.csv
    All community submissions

  • openairframes_adsb.csv
    Airframes dataset derived from ADSB.lol network data. For each UTC day, a row is created for every icao observed in that days ADS-B messages, using registration data from tar1090-db (ADSBExchange & Mictronics). Example Usage:

import pandas as pd
url = "https://github.com/PlaneQuery/OpenAirframes/releases/download/openairframes-2026-03-18-main/openairframes_adsb_2024-01-01_2026-03-17.csv.gz" # 1GB
df = pd.read_csv(url)
df

  • openairframes_registry.csv
    Every national registry in one table, one row per registration record, with a source column naming the registry it came from. Currently the FAA (United States) and Transport Canada. Identifier columns (transponder_code_hex, registration_number, openairframes_id) lead the table and are populated for every source.

  • openairframes_faa.csv
    All FAA registration data from 2023-08-16 to present (~275 MB). Superseded by openairframes_registry.csv; still published so existing consumers keep working.

  • ReleasableAircraft_{date}.zip
    A daily snapshot of the FAA database, which updates at 05:30 UTC

  • basic-ac-db.json.gz
    ADS-B Exchange basic aircraft database, republished unmodified.

  • mictronics-db.zip
    Mictronics aircraft database, republished unmodified. Best effort — the release ships without it when the source is unavailable.

Redistribution terms for the underlying sources travel with the release in NOTICE. Some registries permit redistribution only on condition that specific notices reach you with the data.


For Contributors

Submit data via a GitHub Issue with your preferred attribution. Once approved, it will appear in the daily release. A leaderboard will be available in the future. All data is valuable. Examples include:

  • Celebrity ownership (with citations)
  • Photos
  • Internet capability
  • Military aircraft information
  • Unique facts (e.g., an airframe that crashed, performs aerobatics, etc.)

Please try to follow the submission formatting guidelines. If you are struggling with them, that is fine—submit your data anyway and it will be formatted for you.


For Developers

All code, compute (GitHub Actions), and storage (releases) are in this GitHub repository Improvements are welcome. Potential features include:

  • Web UI for data
  • Web UI for contributors
  • Additional export formats in the daily release
  • Data fusion from multiple sources in the daily release
  • Automated airframe data connectors, including (but not limited to) civil aviation authorities and airline APIs
S
Description
No description provided
Readme MIT
903 KiB
Languages
Python 80.1%
JavaScript 19.2%
Shell 0.7%