Flight Planning

Flight Plan Equipment Codes Explained

What ICAO flight plan equipment codes mean, from Item 10a nav letters to transponder and PBN codes, and how to pick the right ones for VATSIM and sim flights.

On this page
  1. What equipment codes are for
  2. Where the codes go in an ICAO flight plan
  3. Item 10a: communication, navigation and approach codes
  4. Item 10b: surveillance codes
  5. PBN codes in Item 18
  6. The older FAA domestic suffixes
  7. Reading an equipment string: worked examples
  8. Choosing codes for a simulator flight
  9. Real-world note

What equipment codes are for

A flight plan tells air traffic control (ATC) more than where you’re going. It also describes what the aircraft can do: which radios it has, how it navigates, and what kind of transponder it carries. Equipment codes are the short letters and numbers that carry this information.

Controllers use them to decide what they can clear you for. An aircraft filed with GNSS and the right RNAV approval can be given an RNAV departure; one without it may get radar vectors or a conventional procedure instead. On online networks such as VATSIM and IVAO, virtual controllers read the same codes from your filed flight plan, so getting them roughly right makes your flight smoother.

This article is written for simulator pilots. Real-world pilots should file using official guidance from their aviation authority and the aircraft’s documentation.

Where the codes go in an ICAO flight plan

Most of the world uses the ICAO flight plan format. Equipment is described in three places:

  • Item 10a – communication, navigation and approach equipment, written before the slash.
  • Item 10b – surveillance equipment (transponder, ADS-B, ADS-C), written after the slash.
  • Item 18 – extra details, including the PBN/ field that lists specific RNAV and RNP capabilities.

A full equipment entry looks something like SDFGRWY/S, with the Item 10a letters before the slash and the Item 10b letters after it.

Item 10a: communication, navigation and approach codes

The table lists the letters sim pilots meet most often. S is a shorthand for the standard set of equipment, so you won’t usually list those items separately.

Code Meaning
N No COM/NAV/approach equipment, or it’s unserviceable
S Standard equipment: VHF radio, VOR and ILS
B LPV approach capability (SBAS, such as WAAS)
D DME
F ADF
G GNSS (GPS)
H HF radio
I Inertial navigation
L ILS
O VOR
R PBN approved (details go in Item 18 PBN/)
T TACAN
U UHF radio
V VHF radio
W RVSM approved
X Approved for North Atlantic high-level airspace (formerly MNPS)
Y VHF with 8.33 kHz channel spacing
Z Other equipment, explained in Item 18 under COM/, NAV/ or DAT/

Other codes describe datalink and satellite voice, such as E1 to E3 for ACARS services and J1 to J7 for CPDLC. Airliner profiles in planning tools often include them, but they matter less for most sim flying.

Item 10b: surveillance codes

Code Meaning
N No surveillance equipment
A Mode A transponder (no altitude reporting)
C Mode A and Mode C transponder (altitude reporting)
S Mode S transponder with altitude and aircraft identification
E Mode S with altitude, identification and extended squitter (ADS-B)
H Mode S with altitude, identification and enhanced surveillance
L Mode S with altitude, identification, extended squitter and enhanced surveillance
B1 / B2 ADS-B on 1090 MHz: out only / out and in
U1 / U2 ADS-B on UAT: out only / out and in
D1 ADS-C with FANS 1/A

For most sim flights, C (a light aircraft with an altitude-reporting transponder) or S, E or L (modern airliners) will cover it.

PBN codes in Item 18

If you include R in Item 10a, you’re saying the aircraft is approved for performance-based navigation, and Item 18 should spell out which types using PBN/. Common examples:

Code Meaning
A1 RNAV 10 (RNP 10), oceanic
B1 / B2 RNAV 5, all permitted sensors / GNSS
C1 / C2 RNAV 2, all permitted sensors / GNSS
D1 / D2 RNAV 1, all permitted sensors / GNSS
L1 RNP 4, oceanic
O1 / O2 RNP 1, all permitted sensors / GNSS
S1 RNP approach
S2 RNP approach with Baro-VNAV
T1 / T2 RNP AR approach, with / without RF legs

The letters for individual sensors used in a PBN/ code should also appear in Item 10a. For example, a GNSS-based code such as D2 goes with G in Item 10a.

The older FAA domestic suffixes

Before the ICAO format took over, US domestic flight plans used a single letter after the aircraft type, such as C172/G. You’ll still see these in older tutorials and sim tools. The common ones were:

Suffix Meaning
/U Transponder with altitude reporting, no DME or RNAV
/A DME and transponder with altitude reporting
/G GNSS (GPS) with en route and terminal capability, transponder with altitude reporting
/W RVSM, no GNSS or RNAV
/L RVSM with GNSS

The FAA has moved US filers toward the ICAO format, and online networks have largely followed. For new sim flight plans, use ICAO codes.

Reading an equipment string: worked examples

SG/C – a light aircraft with standard VHF radio, VOR and ILS (S), plus GPS (G), and an altitude-reporting transponder (C). This is a reasonable description of a simulated Cessna 172 with a GPS unit.

SBG/C – the same, but the GPS supports LPV approaches (B), as WAAS-capable units do.

SDFGRWY/S with PBN/B2D2 in Item 18 – standard equipment (S), DME (D), ADF (F), GPS (G), PBN approved (R), RVSM approved (W), 8.33 kHz radios (Y), and a Mode S transponder (S). The PBN codes say it can fly RNAV 5 and RNAV 1 using GNSS. That’s the kind of string you might see for a modern airliner.

Choosing codes for a simulator flight

  • Let your planner do it. SimBrief and similar tools fill in equipment codes from the aircraft profile. For airliners, the default profile is usually sensible. Check it if you’ve edited the aircraft or chosen an unusual variant.
  • Match the simulated avionics. File what the aircraft in your sim actually has. If your steam-gauge Cessna has no GPS, don’t file G, because a controller may clear you for an RNAV procedure you can’t fly.
  • Don’t over-claim. Filing W (RVSM) or R with RNP approach codes for an aircraft that can’t do those things invites clearances you can’t follow.
  • Keep it simple for light aircraft. SG/C or S/C covers most GA flights on VATSIM or IVAO.
  • Remember Item 18. If you file R, add the PBN/ codes too; otherwise the string is incomplete.

If you’re building your first plan, our guide on how to create a flight plan shows where equipment fits into the whole process, and our flight planning software overview compares the tools that fill these fields in for you.

Real-world note

Equipment and PBN filing rules vary by country and change over time, and real aircraft must have the relevant approvals, not just the hardware. For real flights, check your aviation authority’s current flight plan guidance and the aircraft’s approved equipment list rather than relying on a summary like this one.

The complete guide to flight planning

Flight Planning Software for Flight Simulators
Read the guide

Keep exploring

Guides from other topics

All topics →