Module @squawk/procedure-data
@squawk/procedure-data
Pre-processed snapshot of US instrument procedure data from the 2026-03-25 FAA CIFP
cycle. Covers Standard Instrument Departures (SIDs), Standard Terminal Arrival Routes
(STARs), and Instrument Approach Procedures (IAPs) in the unified ARINC 424 leg model.
Data only - no query logic, no dependency on @squawk/procedures.
Part of the @squawk aviation library suite. See all packages on npm.
Coverage
- Standard Instrument Departures (SIDs)
- Standard Terminal Arrival Routes (STARs)
- Instrument Approach Procedures (IAPs): ILS, LOC, LOC-BC, RNAV, RNAV (RNP), VOR, VOR/DME, NDB, NDB/DME, TACAN, GLS, IGS, LDA, SDF, GPS, FMS, MLS
- Full ARINC 424 leg model per procedure: path terminators (IF, TF, CF, DF, CA, CI, CR, FA, FC, FD, FM, HA, HF, HM, PI, RF, AF, VA, VD, VI, VM, VR)
- Altitude constraints (at / at-or-above / at-or-below / between / glide-slope / step-down descriptors) with primary and secondary altitudes
- Speed constraints with descriptor
- Recommended navaid, RNP value, turn direction, arc radius, center fix (for RF legs)
- Approach-role flags: IAF, IF (intermediate), FAF, FACF, MAP, fly-over
- Named transitions (approach transitions for IAPs, enroute / runway transitions for SIDs and STARs)
- Missed-approach sequences for IAPs
- Resolved lat/lon for every fix, navaid, airport, and runway reference
Installation
npm install @squawk/procedure-data
Usage
import { usBundledProcedures } from '@squawk/procedure-data';
// Inspect metadata
console.log(usBundledProcedures.properties.cifpCycleDate); // "2026-03-25"
console.log(usBundledProcedures.properties.recordCount);
console.log(usBundledProcedures.properties.sidCount);
console.log(usBundledProcedures.properties.starCount);
console.log(usBundledProcedures.properties.iapCount);
// Use with @squawk/procedures for zero-config procedure queries
import { createProcedureResolver } from '@squawk/procedures';
const resolver = createProcedureResolver({ data: usBundledProcedures.records });
Consumers who have their own data pipeline can use @squawk/procedures alone and
pass any compatible Procedure array at initialization.
Data format
Each record is a full Procedure object from @squawk/types. Key fields:
| Property | Type | Description |
|---|---|---|
name |
string | Human-readable name (e.g. AALLE4, ILS RWY 04L) |
identifier |
string | CIFP procedure identifier (e.g. AALLE4, I04L) |
type |
ProcedureType | SID, STAR, or IAP |
airports |
string[] | Airports served by this procedure |
commonRoutes |
ProcedureCommonRoute[] | Trunk paths with legs and per-route adapted airports |
transitions |
ProcedureTransition[] | Named transitions (approach / enroute / runway depending on type) |
approachType |
ApproachType | undefined | Approach classification (IAPs only) |
runway |
string | undefined | Runway served by the approach (IAPs with a runway-specific approach) |
missedApproach |
MissedApproachSequence | Missed-approach climb-out (IAPs only) |
Each ProcedureLeg carries:
| Property | Type | Description |
|---|---|---|
pathTerminator |
ProcedureLegPathTerminator | ARINC 424 path terminator (e.g. TF, CF, CA) |
fixIdentifier, category, lat, lon, icaoRegionCode |
(see types) | Termination fix (absent on pure heading/altitude legs) |
altitudeConstraint |
AltitudeConstraint | Descriptor + primary/secondary altitudes in feet |
speedConstraint |
SpeedConstraint | Descriptor + speed in knots |
courseDeg, courseIsTrue |
number / boolean | Outbound or intercept course |
distanceNm, holdTimeMin |
number | Distance or hold time (leg-type dependent) |
recommendedNavaid, thetaDeg, rhoNm, rnpNm |
(see types) | Recommended navaid + bearing/distance/RNP reference |
turnDirection |
'L' | 'R' |
Commanded turn direction |
arcRadiusNm, centerFix |
(see types) | Populated on RF constant-radius-arc legs |
isInitialApproachFix, isIntermediateFix, isFinalApproachFix, isFinalApproachCourseFix, isMissedApproachPoint, isFlyover |
boolean | Approach role flags |
Data source
Data is derived from the FAA CIFP (Coded Instrument Flight Procedures) 28-day cycle, which is public domain and published in ARINC 424 v18 format. The build pipeline that produces this dataset lives in tools/build-procedure-data.
A note on Obstacle Departure Procedures (ODPs)
Graphic ODPs are encoded by CIFP as SIDs (PD records) with no distinguishing
field, so they are included in this dataset labelled as SID alongside regular
Standard Instrument Departures. There is no reliable way to distinguish ODPs
from regular SIDs using CIFP data alone - the ODP indicator lives in the d-TPP
(Digital Terminal Procedures Publication) chart titles.
Textual ODPs (plain-English climb instructions published in the d-TPP supplement) are not carried by CIFP at all and are therefore not included in this dataset.