Pre-processed snapshot of airport data from the 2026-05-14 FAA NASR cycle. Data only - no query logic, no dependency on @squawk/airports.

Documentation

Part of the @squawk aviation library suite. See all packages on npm.

Coverage

• All open aviation facilities the FAA publishes: US airports, heliports, seaplane bases, gliderports, ultralight, and balloonports, plus selected Canadian, Mexican, Caribbean, and Pacific facilities that participate in US operations
• Runway dimensions, surface, condition, lighting, and weight limits
• Per-runway-end details: heading, displaced thresholds, declared distances (TORA/TODA/ASDA/LDA), approach lighting, VGSI, LAHSO
• Structured ILS data: system type, identifier, category, localizer frequency and course, glide slope angle and type, DME channel
• Communication frequencies with usage and sectorization
• IANA time zone identifier resolved from the facility lat/lon (e.g. America/New_York), ready for direct use with Intl.DateTimeFormat and other standard date/time APIs

Installation

npm install @squawk/airport-data

Usage

import { usBundledAirports } from '@squawk/airport-data';

// Inspect metadata
console.log(usBundledAirports.properties.nasrCycleDate); // YYYY-MM-DD
console.log(usBundledAirports.properties.recordCount);

// Use with @squawk/airports for zero-config airport queries
import { createAirportResolver } from '@squawk/airports';

const resolver = createAirportResolver({ data: usBundledAirports.records });

Consumers who have their own data pipeline can use @squawk/airports alone and pass any compatible Airport array at initialization.

Browser / SPA usage

For browsers, edge runtimes (Cloudflare Workers, Deno Deploy), and any other environment without node:fs, import the async loader from the /browser subpath. It fetches and decompresses the bundled .gz using Web Streams (DecompressionStream) and the global fetch.

import { loadUsBundledAirports } from '@squawk/airport-data/browser';
import { createAirportResolver } from '@squawk/airports/browser';

const dataset = await loadUsBundledAirports();
const resolver = createAirportResolver({ data: dataset.records });

The default URL is resolved relative to this module's import.meta.url, which works under any modern ESM bundler when the package is installed normally.

To host the asset on your own CDN, to use a bundler-resolved (hashed) asset URL, or to override the URL for any other reason, pass an explicit url:

import { loadUsBundledAirports } from '@squawk/airport-data/browser';

const dataset = await loadUsBundledAirports({
  url: 'https://your-cdn.example/airports.json.gz',
});

The loader also accepts a custom fetch implementation, which is useful in tests or in edge environments that need a configured fetcher.

Data format

Each record is a full Airport object from @squawk/types. Key fields:

| Property | Type | Description | | ---------------------- | ------------------- | ----------------------------------------------------- | | faaId | string | FAA location identifier (e.g. "JFK", "LAX", "3N6") | | icao | string or undefined | ICAO code when assigned (e.g. "KJFK") | | name | string | Official facility name | | facilityType | FacilityType | AIRPORT, HELIPORT, SEAPLANE_BASE, etc. | | ownershipType | OwnershipType | PUBLIC or PRIVATE | | useType | FacilityUseType | PUBLIC or PRIVATE | | status | FacilityStatus | Always OPEN (closed facilities are excluded) | | city, country | string | Location identifiers | | state | string or undefined | Two-letter code for US facilities, absent for foreign | | lat, lon | number | Decimal degrees | | timezone | string | IANA time zone identifier (e.g. "America/New_York") | | elevationFt | number or undefined | Field elevation in feet MSL | | magneticVariationDeg | number or undefined | Magnetic variation in degrees | | towerType | string or undefined | e.g. "ATCT", "NON-ATCT" | | fuelTypes | string or undefined | e.g. "100LL,A" | | runways | Runway[] | Runway details (see below) | | frequencies | AirportFrequency[] | Communication frequencies (see below) |

Runway

| Property | Type | Description | | ------------- | ------------------- | ------------------------------------ | | id | string | Designator (e.g. "04L/22R") | | lengthFt | number or undefined | Length in feet | | widthFt | number or undefined | Width in feet | | surfaceType | string or undefined | e.g. "CONC", "ASPH", "TURF" | | condition | SurfaceCondition | EXCELLENT, GOOD, FAIR, POOR, FAILED | | lighting | RunwayLighting | HIGH, MEDIUM, LOW, NONSTANDARD, NONE | | ends | RunwayEnd[] | Per-end details (typically two) |

RunwayEnd

| Property | Type | Description | | ------------------------------------- | ---------------------- | ------------------------------------ | | id | string | Designator (e.g. "04L", "22R") | | trueHeadingDeg | number or undefined | True heading in degrees | | ils | IlsSystem or undefined | Structured ILS data (see below) | | toraFt, todaFt, asdaFt, ldaFt | number or undefined | Declared distances in feet | | displacedThresholdFt | number or undefined | Displaced threshold distance in feet | | vgsiType | VgsiType | e.g. PAPI-4L, VASI-2L | | approachLights | string or undefined | Approach lighting system code |

IlsSystem

| Property | Type | Description | | ---------------------------- | ------------------------ | -------------------------------------------------------------------- | | systemType | IlsSystemType | ILS, ILS/DME, LOCALIZER, LOC/DME, LOC/GS, LDA, LDA/DME, SDF, SDF/DME | | identifier | string or undefined | Facility identifier (e.g. "I-JFK") | | category | IlsCategory or undefined | Approach category (I, II, III, IIIA, IIIB, IIIC) | | localizerFrequencyMhz | number or undefined | Localizer frequency in MHz (108-112) | | localizerMagneticCourseDeg | number or undefined | Front course bearing in magnetic degrees | | glideSlopeAngleDeg | number or undefined | Glide slope angle in degrees (typically ~3.0) | | glideSlopeType | string or undefined | Glide slope class (GLIDE SLOPE, GLIDE SLOPE/DME) | | dmeChannel | string or undefined | DME channel (e.g. "032X", "046X") |

AirportFrequency

| Property | Type | Description | | --------------- | ------------------- | --------------------------------------- | | frequencyMhz | number | Frequency in MHz (e.g. 119.1) | | use | string | Purpose (e.g. "LCL/P", "GND/P", "ATIS") | | sectorization | string or undefined | Applicability (e.g. "RWY 04L/22R") |

Data source

All data is derived from the FAA National Airspace System Resource (NASR) 28-day subscription, which is public domain. Airport base data comes from APT_BASE.csv, runway data from APT_RWY.csv and APT_RWY_END.csv, frequencies from FRQ.csv, and ILS data from ILS_BASE.csv, ILS_GS.csv, and ILS_DME.csv. The build pipeline that produces this dataset lives in tools/build-airport-data.