airportsdata 
Extensive database of location and timezone data for nearly every operational airport, landing strip, and some seaplane bases in the world (no heliports unless IATA coded), with 28,343 entries.
Each entry consists of the following data:
icao: ICAO 4-letter Location Indicator (Doc 7910) or (if none) an internal Pseudo-ICAO Identifier [1] (28,343 entries);
iata: IATA 3-letter Location Code (7,906 entries) or an empty string [2];
name: Official name (diacritized latin script);
city: City (diacritized latin script), ideally using the local language or English;
subd: Subdivision (e.g. state, province, region, etc.; diacritized latin script), ideally in local language or the English names of ISO 3166-2;
country: ISO 3166-1 alpha-2 country code (plus XK for Kosovo);
elevation: MSL elevation of the highest point of the landing area, in feet (warning: it is often wrong);
lat: Latitude (decimal) of the airport reference point (max 5 or 6 decimal digits);
lon: Longitude (decimal) of the airport reference point (max 5 or 6 decimal digits);
tz: Timezone expressed as a tz database name (IANA-compliant);
lid: U.S. FAA Location Identifier (12,625 entries), or an empty string.
Best efforts are placed to review all contributions for accuracy, but accuracy cannot be guaranteed nor should be expected by users.
Important notes:
Timezone was originally sourced from TimeZoneDB;
No historical data (closed airports are removed);
No seaplane bases or heliports unless they have a IATA code;
No surface transportation stations, even if they have an official IATA code;
Airports under construction may be included if they have ICAO and IATA codes and scheduled airline service.
Please report any issues you may find here.
This project is a fork of mwgg/Airports. All new data submitted in this fork have been validated against national Aeronautical Information Publications (AIP) or equivalent, ARINC database, or IATA before publishing.
Raw data
A CSV (comma separated values) file, with headers and encoded in UTF-8, is downloadable from GitHub here.
Python
Install from PyPi using uv (recommended):
uv pip install --update airportsdata
Or, using pip:
pip install --update airportsdata
Once installed, to load the data into a dict:
import airportsdata
icao_airports = airportsdata.load() # key is the ICAO identifier (the default)
print(icao_airports['KJFK'])
or
import airportsdata
iata_airports = airportsdata.load('IATA') # key is the IATA location code
print(iata_airports['JFK'])
or
import airportsdata
lid_airports = airportsdata.load('LID') # key is the FAA LID
print(lid_airports['01AA'])
Older Python versions are supported for 3 years after being obsoleted by a new major release (i.e. about 4 years since their original release).
License 
Released under the MIT License (see license here).
Metadata
Release files for airportsdata 20261030
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| airportsdata-20261030.tar.gz | 945.9 kB | With provenance | Details for airportsdata-20261030.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| airportsdata-20261030-py3-none-any.whl | Python 3 | none | any | Details for airportsdata-20261030-py3-none-any.whl |
Total release size: 1.9 MB
Release files / airportsdata-20261030.tar.gz
| Download URL | airportsdata-20261030.tar.gz |
|---|---|
| Size | 945.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
b02f4a425a3248fc8812b68b0e00896bdc211ed36f8ac2f040c69f864c6fe383
|
|
BLAKE2b-256 checksum How to use checksums |
190f817a8be463f61d632561597ddb9ddc7fb9605d370803aada411e4aaef0a9
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 30, 2026.
Transparency logRelease files / airportsdata-20261030-py3-none-any.whl
| Download URL | airportsdata-20261030-py3-none-any.whl |
|---|---|
| Size | 934.8 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
0b50327f8d026be56cc18e1b83df356d2550f26127e13518883dc0f62533eb87
|
|
BLAKE2b-256 checksum How to use checksums |
be624253350b219e4d1f21121cead8036439292a0a60415422d0a504a12fc2a1
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 30, 2026.
Transparency logSecurity for airportsdata 20261030
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
Full provenance
All 2 files in this release have been uploaded with provenance metadata.
Attestation for airportsdata-20261030.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 30, 2026.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.