Equipment Codes non WAAS GPS

Ryan Harris

Filing Flight Plan
Joined
Jul 19, 2017
Messages
18
Display Name

Display name:
rcharris
Just bought a 182P with a pretty basic IFR setup. Aircraft has two nav/comms (KX-155 / Narco MX-12) with dual G/S, and a working KLN-90A with the IFR paperwork. Transponder is KT-76A w/ Mode C. I'm a new IFR pilot and trying to figure out what the appropriate equipment code is (AIM table 5-1-3). Since it's a non-WAAS GPS, but approved for enroute, assuming that /G is not appropriate? Perhaps RNAV with no GNSS? (/I?)

Thanks.
 
If it's approved enroute and you have a Mode C transponder, /G is still the appropriate filing code. It doesn't have to be WAAS to file /G. Is it approved for LNAV approaches? That wouldn't change the filing code either.

If you think this is confusing, wait until the FAA switches to ICAO filing. It's more descriptive, but very confusing when you set the plane up the first time on Foreflight or Garmin Pilot or FltPlan.com
 
/G is "No RVSM" + "GNSS" + "Transponder with Mode C" which says nothing about WAAS. You have GNSS so /G is the thing to use.
 
If you think this is confusing, wait until the FAA switches to ICAO filing. It's more descriptive, but very confusing when you set the plane up the first time on Foreflight or Garmin Pilot or FltPlan.com

Yep, you then get two sets of codes, navigation and surveillance. I THINK I am SBG (WAAS GPS and VOR/ILS) and EB2 (ADSB 1090 in+out mode S). When you install ADSB the mfg usually tells you what ICAO code your install will be.
 
If it's approved enroute and you have a Mode C transponder, /G is still the appropriate filing code. It doesn't have to be WAAS to file /G. Is it approved for LNAV approaches? That wouldn't change the filing code either.

If you think this is confusing, wait until the FAA switches to ICAO filing. It's more descriptive, but very confusing when you set the plane up the first time on Foreflight or Garmin Pilot or FltPlan.com
KLN89-90-94, Garmin 150(XL), GNC300XL, 430/530non-W's, 480/CNX80, 430/530Ws, 650/750, IFD440/550 and a few more are all are /G. GNSS is simply the Global Navigation Satellite System (satellite chain) that GPS systems (430, etc.) use for position fixing. All airplanes that have a GPS that uses a GNSS (ours, GLONASS, etc.) are /G.
 
Last edited:
/G is for enroute navigation, not approach capability. Most GPS approaches, even when they have LPV capability, can be operated with non-WAAS on non-LPV minimums anyway. One of the only ones I know of that isn't available is the RNAV Z at KCMA.
 
My Cirrus is WAAS and I still use /G, there is nothing else, I figure controllers care less if I am WAAS or not, the distinction WAAS or not means little to them.


Sent from my iPad using Tapatalk Pro
 
Yep, they only really care if you can take an enroute (or perhaps) terminal direct route. The pre-ICAO codes aren't good enough to determine what sort of approach you can fly even notwithstanding GPS.
 
Any panel-mount IFR GPS is /G for the FAA flight plan.

Now, when you decide to figure out the codes for an ICAO plan... Good freaking luck. There's a billion different codes, you really need to ask the manufacturer what you should have, and even after all that, I had a pair of codes that apparently conflict in the ATC computers, thus denying me the RNAV SID I filed. ForeFlight support figured that one out for me.

So, I used to be M20P/G. Now I'm M20P/L -BGRS PBN/B2C2D2 SUR/B2E. I think.
 
Wut!? I give up already. Game over man.

Yeah. ICAO codes are NOT user friendly. I used to have a NAV/ tag in there, but I guess something that was in there conflicted with something in the PBN/ tag. It's also better to use the S equipment code than "spelling out" the LOV codes, from what I was told. I think I had -BGLORV instead of -BGRS, and that was half of the conflict.
 
Back
Top