@squawk/airway-data

  @squawk/airway-data

Pre-processed snapshot of US airway data from the 2026-04-16 FAA NASR cycle. Data only - no query logic, no dependency on @squawk/airways.

Documentation

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

Coverage

• Victor airways (V1, V16, etc.) - VOR-based low-altitude routes
• Jet routes (J1, J60, etc.) - high-altitude IFR routes
• RNAV Q-routes (Q1, Q102, etc.) - GPS-based high-altitude routes
• RNAV T-routes (T238, T270, etc.) - GPS-based low-altitude routes
• Colored airways (Green, Red, Amber, Blue) - Alaska and other regions
• Oceanic routes (Atlantic, Bahama, Pacific, Puerto Rico)
• Full waypoint sequences with ordered fix/navaid references
• MEA, MOCA, MAA, MCA, and GNSS MEA altitude restrictions per segment
• Distance to next waypoint in nautical miles
• Magnetic course and changeover point data
• Signal gap and US airspace-only indicators

Installation

npm install @squawk/airway-data

Usage

import { usBundledAirways } from '@squawk/airway-data';

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

// Use with @squawk/airways for zero-config airway queries
import { createAirwayResolver } from '@squawk/airways';

const resolver = createAirwayResolver({ data: usBundledAirways.records });

Consumers who have their own data pipeline can use @squawk/airways alone and pass any compatible Airway 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 { loadUsBundledAirways } from '@squawk/airway-data/browser';
import { createAirwayResolver } from '@squawk/airways/browser';

const dataset = await loadUsBundledAirways();
const resolver = createAirwayResolver({ 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 { loadUsBundledAirways } from '@squawk/airway-data/browser';

const dataset = await loadUsBundledAirways({
  url: 'https://your-cdn.example/airways.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 Airway object from @squawk/types. Key fields:

Property	Type	Description
designation	string	Airway designation (e.g. "V16", "J60", "Q1", "ATA315")
type	AirwayType	VICTOR, JET, RNAV_Q, RNAV_T, GREEN, RED, ATLANTIC, etc.
region	AirwayRegion	US, ALASKA, or HAWAII
waypoints	AirwayWaypoint[]	Ordered waypoint sequence (west-to-east / south-to-north)

Each AirwayWaypoint contains:

Property	Type	Description
name	string	Waypoint name
identifier	string or undefined	Short identifier (e.g. "BOS", "MERIT")
waypointType	AirwayWaypointType	NAVAID, FIX, WAYPOINT, BORDER, or OTHER
lat, lon	number	Decimal degrees
minimumEnrouteAltitudeFt	number or undefined	Minimum Enroute Altitude in feet
maximumAuthorizedAltitudeFt	number or undefined	Maximum Authorized Altitude in feet
minimumObstructionClearanceAltitudeFt	number or undefined	Minimum Obstruction Clearance Altitude
distanceToNextNm	number or undefined	Distance to next waypoint in NM
magneticCourseDeg	number or undefined	Magnetic course to next waypoint

Data source

All data is derived from the FAA National Airspace System Resource (NASR) 28-day subscription, which is public domain. Airway data comes from AWY.txt (Victor, Jet, RNAV Q/T, colored airways) and ATS.txt (Atlantic, Bahama, Pacific, Puerto Rico oceanic routes). The build pipeline that produces this dataset lives in tools/build-airway-data.