# CIFP

FAA Coded Instrument Flight Procedures (ARINC 424) — SIDs, STARs, approaches, enroute airways, waypoints, controlled and restrictive airspace.

**Version:** `239462ba9c35`
  
**Effective:** 2026-04-16
  
**Upstream:** https://aeronav.faa.gov/Upload_313-d/cifp/CIFP_260416.zip

> **Disclaimer**
>
> United States Department of Transportation
> Federal Aviation Administration
> Aeronautical Information Services
> Coded Instrument Flight Procedures
> DISCLAIMER
> 
> 1. The Coded Instrument Flight Procedures (CIFP) is a product of the United States
> Department of Transportation (DOT), Federal Aviation Administration (FAA).
> The CIFP is not copyrighted under Title 17 U.S.C.
> 
> 2. The CIFP is in the Aeronautical Radio, Incorporated (ARINC), Airlines Electronic
> Engineering Committee (AEEC), Navigation System Data Base format, ARINC
> Specification 424 version 18.
> 
> 3. Aeronautical data supporting the CIFP is acquired from two United States
> government source:
> a. Department of Transportation (DOT), Federal Aviation Administration
> (FAA)
> b. Department of Defense (DOD), National Geospatial-Intelligence Agency
> (NGA)
> 
> 4. The FAA is responsible for the accuracy of the FAA-originated data included in
> the CIFP. The FAA is not responsible for the accuracy of NGA Digital
> Aeronautical Flight Information File (DAFIF) data.
> 
> 5. The FAA is responsible for the compilation of the CIFP into the industry standard
> ARINC Navigation Systems Data Base, ARINC Specification 424 format.
> 
> 6. The FAA is not responsible for products derived from the CIFP.
> 
> 7. The FAA requires that product developers and manufactures include warranty
> disclaimers as follows:
> a. Under 10 U.S.C. 456, no civil action may be brought against the United States
> on the basis of the content of a navigational aid prepared or disseminated by
> the FAA.
> b. The CIFP product is provided “as is” and no warranty, express or implied,
> including, but not limited to the implied warranties of merchantability and
> fitness for particular purpose or arising by statue or otherwise in law or from a
> course of dealing or usage in trade, is made by the FAA as to the accuracy and
> functioning of the product.
> c. Neither the FAA nor its personnel will be
>  liable for any claims, losses, ordamages arising from or connected with the use of this product. The useragrees to hold harmless the United States Federal Aviation Administration.
> The user’s sole and exclusive remedy is to stop using the CIFP product.
> Question regarding the Coded Instrument Flight Procedures (CIFP) should be
> directed to:
> Department of Transportation
> Federal Aviation Administration
> Aeronautical Information Services
> 1305 East West Highway
> Silver Spring, Maryland
> 20910-3281 Telephone:
> 800-638-8972
> E-mail: 9-AMC-Aerochart@faa.gov
> NOTE: The Disclaimer below is provided as a frame of reference since the NGA/DAFIF
> is a similar navigation database used by the United States military. It will not be included
> with the FAA CIFP Disclaimer.
> Department of Defense
> National Geospatial-Intelligence Agency
> Digital Aeronautical Fight Information File
> DISCLAIMER
> 
> 1. The DAFIF®, or the Digital Aeronautical Fight Information File, is a product ofthe National Geospatial-Intelligence Agency (NGA) of the United States
> Department of Defense (‘DOD’). Although NGA makes no copyright claim under
> Title 17 U.S.C., NGA claims copyrights under other legal regimes. NGA herebygrants to each user of DAFIF a license to use and distribute the product, anddevelop derivative works.
> 
> 2. The product name - -DAFIF®- -is a registered trademark of the National
> Geospatial- Intelligence Agency, and may only be used to refer to the source ofthe data.
> 
> 3. NGA requests that products developed using DAFIF®, acknowledge the sourceof the data with the following statement:
> “This product was developed using DAFIF®, a product of the
> National Geospatial-Intelligence Agency.”
> 
> 4. When product developers and other customers acknowledge DAFIF® as thesource of the data, please be aware that under the United States Code, 10 U.S.C.
> 425, the names of the National Geospatial-Intelligence Agency or the former
> Defense Mapping Agency, their respective initials, or seals cannot be used toimply that a product is approved, endorsed, or authorized by the Secretary of
> Defense.
> Fortunately, a simple disclaimer to the effect that, “This product has not
> been endorsed or otherwise approved by the National Geospatial-Intelligence
> Agency, or the United States Department of Defense (10 U.S.C   425), “is
> sufficient to resolve any ambiguity.
> 
> 5. NGA and its personnel are not required to provide technical support or generalassistance with respect to DAFIF®.
> 
> 6. Finally, NGA requires that products developers and manufacturers includewarranty disclaimers as follows:
> a. Under 10 U.S.C.   456, no civil action may be brought against the United
> States on the basis of the content of a navigational aid prepared ordisseminated by either the former Defense Mapping Agency (DMA) or the
> National Geospatial-Intelligence Agency (NGA).
> b. The DAFIF® product is provided “as is,” and no warranty, express orimplied, including, but not limited to the implied warranties ofmerchantability and fitness for particular purpose or arising by statute orotherwise in law or from a course of dealing or usage in trade, is made by
> NGA as to the accuracy and functioning of the product.
> c. Neither NGA nor its personnel will be liable for any claims, losses, ordamages arising from or connected with the use of this product. The useragrees to hold harmless the Untied States National Geospatial-Intelligence
> Agency. The user’s sole and exclusive remedy is to stop using the
> DAFIF® product.

**GraphQL endpoint:** `https://api.nav.sortie.co/graphql`

## Types

### Other

| Type | Description |
|---|---|
| [`CifpAirport`](./types/CifpAirport.md) | Airport reference data including location, elevation, runway, and operational characteristics per ARINC 424 Section PA r |
| [`CifpApproach`](./types/CifpApproach.md) | ARINC 424 Section 4.1 instrument approach procedure records defining all legs, fixes, and constraints for published appr |
| [`CifpControlledAirspace`](./types/CifpControlledAirspace.md) | Defines the boundaries and properties of controlled airspace (Class B, C, D, etc.) as sequences of boundary-defining poi |
| [`CifpEnrouteAirway`](./types/CifpEnrouteAirway.md) | Enroute airway route segments defining the fixes, courses, distances, and altitudes along named airways in ARINC 424 Sec |
| [`CifpEnrouteWaypoint`](./types/CifpEnrouteWaypoint.md) | Enroute waypoints (named fixes) used in the en route structure, corresponding to ARINC 424 Section EA records |
| [`CifpGridMora`](./types/CifpGridMora.md) | Grid Minimum Off-Route Altitudes (MORA) providing terrain and obstacle clearance altitudes for 1-degree latitude by 1-de |
| [`CifpHeliport`](./types/CifpHeliport.md) | Heliport and helipad reference records containing location, elevation, and operational data for civil and military helip |
| [`CifpHeliportApproach`](./types/CifpHeliportApproach.md) | ARINC 424 heliport instrument approach procedure records defining the sequence of legs, fixes, and constraints for helic |
| [`CifpHeliportMsa`](./types/CifpHeliportMsa.md) | Minimum Safe Altitude (MSA) sectors associated with heliports, defining safe altitudes within specified radii and bearin |
| [`CifpHeliportSid`](./types/CifpHeliportSid.md) | Standard Instrument Departure (SID) procedure records for heliports, encoded per ARINC 424 section HD |
| [`CifpHeliportWaypoint`](./types/CifpHeliportWaypoint.md) | Terminal waypoints associated with specific heliports, defining named fixes used in heliport instrument procedures (ARIN |
| [`CifpLocalizer`](./types/CifpLocalizer.md) | ILS/LOC localizer and glide slope facility records for airports, containing frequency, position, bearing, and approach c |
| [`CifpMsa`](./types/CifpMsa.md) | Minimum Sector Altitude (MSA) records defining obstacle clearance altitudes within defined sectors around a reference na |
| [`CifpNdbNavaid`](./types/CifpNdbNavaid.md) | NDB (Non-Directional Beacon) navaid records defining the location, frequency, and characteristics of NDB ground stations |
| [`CifpPathPoint`](./types/CifpPathPoint.md) | SBAS (WAAS/LPV) Final Approach Segment (FAS) path point data for RNAV/GPS approaches, defining the precision glide path  |
| [`CifpRestrictiveAirspace`](./types/CifpRestrictiveAirspace.md) | Defines the boundaries and attributes of restrictive airspace areas (MOAs, Restricted, Prohibited, Warning, Alert, and M |
| [`CifpRunway`](./types/CifpRunway.md) | Runway records containing physical and navigational characteristics of individual runway ends at airports |
| [`CifpSid`](./types/CifpSid.md) | Standard Instrument Departure (SID) procedure records parsed from FAA CIFP (Coded Instrument Flight Procedures) in ARINC |
| [`CifpStar`](./types/CifpStar.md) | Standard Terminal Arrival Route (STAR) procedure records defining waypoints, paths, and constraints for arriving aircraf |
| [`CifpTerminalNdb`](./types/CifpTerminalNdb.md) | Terminal NDB (Non-Directional Beacon) navaids associated with specific airports, as defined in ARINC 424 Section PN reco |
| [`CifpTerminalWaypoint`](./types/CifpTerminalWaypoint.md) | Terminal area waypoints (named fixes) associated with specific airports or terminal regions, used in instrument flight p |
| [`CifpVhfNavaid`](./types/CifpVhfNavaid.md) | VHF Navaid records (VOR, VORTAC, VOR/DME, DME, TACAN) from ARINC 424 Section D, containing frequency, position, and oper |