When you file a flight plan under the ICAO format — required for virtually all international and oceanic operations — the equipment and capability codes you enter into Field 10 (and the supplementary Field 18 and Field 19) are far more than administrative checkboxes. They are a precise declaration to air traffic control, departure authorities, and oceanic area control centers (OACCs) about what your aircraft can actually do. Get them wrong and you may receive a route or altitude you cannot legally or safely fly; get them right and ATC can assign you optimum tracks, RVSM altitudes, PBN procedures, and reduced-separation minima with confidence.
The ICAO flight plan format differs substantially from the domestic FAA format, and pilots transitioning to international operations often find Field 10 confusing because it requires two separate sub-fields — 10a for radio communication, navigation, and approach aids, and 10b for surveillance equipment. Field 18 then carries free-text supplementary data such as PBN capabilities and selective calling (SELCAL) codes. This article untangles each component, explains what the codes mean in practice, and highlights the combinations that appear repeatedly on ATP knowledge tests and oral exams.
Structure of the ICAO Equipment Fields
The ICAO flight plan uses a standardized format defined by ICAO Doc 4444 (PANS-ATM) and adopted into U.S. practice as described in AIM 5-1-9. The key fields are:
- Field 10a — Communication, navigation, and approach-aid equipment (a string of letters; if no equipment, enter "N").
- Field 10b — Surveillance equipment (transponder capability; if none, enter "N").
- Field 18 — Other information — contains critical free-text indicators including PBN/, NAV/, COM/, DAT/, SUR/, DEP/, DEST/, REG/, EET/, SEL/, CODE/, RMK/, and others.
- Field 19 — Emergency and survival equipment (ELT type, life jackets, survival gear).
A common error is attempting to combine ICAO Field 10 codes with the FAA domestic equipment suffix (e.g., "/G", "/A") — these are completely different systems. On an ICAO plan you never use the FAA suffix.
Field 10a: Radio, Navigation, and Approach-Aid Codes
Field 10a is a concatenated string of single-letter codes (no spaces, no separators). Each letter represents a specific onboard capability. The most commonly tested and operationally important codes include:
- S — Standard equipment: VHF RTF, VOR, and ILS. When the aircraft has standard equipment and nothing more, enter "S" alone.
- G — GNSS (GPS or other global navigation satellite system).
- R — PBN approved. This is a critical code; it indicates the aircraft and crew are approved for performance-based navigation. The specific PBN levels must then be declared in Field 18 under the PBN/ indicator.
- F — ADF.
- O — VOR.
- I — ILS.
- D — DME.
- T — TACAN.
- K — MLS (microwave landing system).
- L — ILS.
- M — Omega (largely historical).
- N — No COM/NAV/approach equipment, or equipment is unserviceable. Enter "N" alone; do not combine with other letters.
- W — RVSM approved. Indicates the aircraft meets reduced vertical separation minimum (RVSM) standards. Without this code, the aircraft cannot be assigned FL290–FL410 on an ICAO flight plan filed for RVSM airspace.
- X — MNPS approved (minimum navigation performance specifications — required for older NAT track crossings before PBN became the standard).
- Y — VHF with 8.33 kHz channel spacing (required in much of European airspace).
- J1 through J7 — CPDLC and ATN data link capabilities (e.g., J5 = CPDLC FANS 1/A via SATCOM INMARSAT). These are essential for modern oceanic operations and many OACCs will not clear an aircraft onto the NAT tracks without appropriate data link.
An airliner equipped for oceanic operations might therefore show a Field 10a entry such as SDFGRYW/J5, meaning it has standard equipment plus ADF, DME, GNSS, PBN approval, RVSM approval, 8.33 kHz VHF spacing, and CPDLC via INMARSAT.
Field 10b: Surveillance Equipment
Field 10b declares transponder and ADS-B capability. The key codes are:
- N — No surveillance equipment.
- A — Mode A transponder only (4096 codes).
- C — Mode A and Mode C (altitude encoding).
- S — Mode S transponder with pressure-altitude transmission and aircraft identification (this is the baseline for most modern transport-category aircraft).
- E — Mode S with aircraft identification, pressure altitude, and extended squitter (ADS-B out). This is the most common code for ADS-B-equipped airliners.
- H — Mode S with aircraft identification and pressure altitude but without extended squitter.
- I — Mode S with aircraft identification only (no pressure altitude).
- X — Mode S with no identification and no altitude.
- B1 — ADS-B with 1090 MHz extended squitter (ADS-B OUT only).
- B2 — ADS-B with 1090 MHz extended squitter capable of both receiving and transmitting (ADS-B IN and OUT).
- U1 and U2 — ADS-B using UAT (universal access transceiver) out-only or in/out respectively — primarily a GA code for aircraft not flying internationally.
For most ATP-level operations, the surveillance field will read something like SDE3, indicating Mode S with identification and altitude, extended squitter (ADS-B out), and ADS-C capability (the "3" suffix for ADS-C is appended when relevant per ICAO Annex 10 and NAT documentation). Always verify current regional requirements; NAT-specific HLA documentation may require particular ADS-C and CPDLC codes for reduced-separation operations.
Field 18: Performance-Based Navigation (PBN/) and Other Indicators
Field 18 is where modern international flight planning lives. The PBN/ indicator is mandatory whenever Field 10a contains the letter "R". It specifies the exact navigation specifications the aircraft and crew are approved for, using codes such as:
- A1 — RNAV 10 (RNP 10). Required for many oceanic and remote areas, including certain Pacific routes. Requires two independent long-range navigation systems.
- B1 through B6 — RNAV 5 specifications with varying sensor types.
- C1 through C4 — RNAV 2 specifications.
- D1 through D4 — RNAV 1 specifications.
- L1 — RNP 4. Required for some NAT tracks and Pacific operations with lateral separation of 30 NM or less.
- O1 through O4 — RNP 1 specifications.
- S1 — RNP APCH.
- S2 — RNP APCH with baro-VNAV.
- T1 and T2 — RNP AR APCH with and without RF legs.
A typical oceanic-capable airline PBN/ entry might read: PBN/A1B1C1D1L1O1S2, indicating approval for RNAV 10, RNAV 5, RNAV 2, RNAV 1, RNP 4, RNP 1, and RNP APCH (with baro-VNAV). It is the pilot's and dispatcher's responsibility to ensure these codes accurately reflect current, valid approvals — typically evidenced by an Operations Specification (OpSpec) issued under 14 CFR Part 121 or 135.
Why These Codes Matter Operationally
ATC and oceanic area control centers process ICAO flight plans automatically. The capability codes drive which routes and altitudes you can be assigned. Without W in Field 10a, you cannot be assigned a flight level in RVSM airspace (FL290–FL410 over much of the world). Without R and the appropriate PBN/ indicators, you may be denied access to RNAV routes or RNP approaches. On the North Atlantic Tracks (NATs), without appropriate CPDLC (J-codes) and ADS-C capability, the minimum lateral separation applied is larger, effectively pushing you onto less efficient routing. In the Pacific, RNAV 10 (A1) capability is a gateway to certain route structures that simply are not available to aircraft without the approval.
Incorrect codes also carry regulatory consequences. Filing capability you do not actually possess may constitute falsification of an official document and can expose the operator to FAA enforcement action. Conversely, failing to claim capability you do have costs fuel, time, and operational efficiency.
Key Numbers and Rules
- RVSM airspace is FL290 through FL410 inclusive; the W code is required to file at these altitudes.
- RNAV 10 (RNP 10) requires a 10 NM total system error budget 95% of the time, and typically demands at least two independent long-range navigation systems (IRS + FMS, or dual GPS).
- RNP 4 requires a 4 NM accuracy standard and supports 30 NM lateral separation on applicable oceanic tracks.
- CPDLC via FANS 1/A (J5 for INMARSAT) is required by many OACCs for Oceanic Clearance Delivery and controller–pilot data link communications (CPDLC) in lieu of HF voice.
- Field 18 PBN/ is mandatory any time "R" appears in Field 10a; omitting it is a filing error that can cause a flight plan rejection.
- ADS-B 1090ES (B1 in Field 10b) satisfies FAA 14 CFR 91.225/91.227 ADS-B out requirements for domestic U.S. Class A, B, and C airspace.
Common Test Traps
- Confusing ICAO codes with FAA domestic equipment suffixes. The slash-letter suffix (e.g., /G) is domestic only. On an ICAO plan, GPS is indicated by "G" in Field 10a without a slash.
- Forgetting to populate Field 18 PBN/ when "R" is in Field 10a. "R" alone is meaningless without the specific PBN codes in Field 18 — examiners test this frequently.
- Treating "S" in Field 10a as the same as "S" in Field 10b. In Field 10a, S = standard equipment (VHF/VOR/ILS). In Field 10b, S = Mode S transponder. Same letter, completely different meanings.
- Omitting "W" for RVSM. A flight plan filed at FL350 without W in Field 10a should be rejected; if it isn't, the crew is operating outside their authorization.
- Assuming GNSS alone satisfies oceanic long-range navigation requirements. Many oceanic routes require at least two independent navigation systems; a single GPS receiver does not satisfy RNAV 10 (RNP 10) on its own in most operator contexts.