{"id":17975,"date":"2022-04-19T08:38:43","date_gmt":"2022-04-19T12:38:43","guid":{"rendered":"https:\/\/ops.group\/blog\/?p=17975"},"modified":"2022-04-21T06:45:05","modified_gmt":"2022-04-21T10:45:05","slug":"alphabet-soup-faa-new-flight-planning-codes","status":"publish","type":"post","link":"https:\/\/ops.group\/blog\/alphabet-soup-faa-new-flight-planning-codes\/","title":{"rendered":"Alphabet Soup: FAA New Flight Planning Codes"},"content":{"rendered":"

The FAA are changing up some flight planning codes, and they\u2019ve published their plans in a handy little guide entitled \u2018Filing for advanced capabilities using the ICAO flight plan (FPL)\u2019.<\/p>\n

We thought we’d take a look at what these new things coming into the FAA flight plan filing code world might be. When we say take a look, we mean literally type up the presentation and add some thoughts of your own.<\/p>\n

This just applies to FAA flight plans, right?<\/h4>\n

Yes. No. Maybe…<\/p>\n

We think it is a yes<\/strong> because the\u00a0US is implementing a lot of RNP1 SIDs and STARs (basically stuff that requires advanced Nav capabilities) and for reasons we’ll mention below, they need new codes.<\/p>\n

You can expect to see a load of new items which relate to NAV\/ and also DAT\/, SUR\/ and COM\/. ICAO has \u201cfrozen\u201d Items 10 and 18 for PBN\/ unless it is a safety critical thing.<\/p>\n

What’s more, in the FAA presentation there is a lot of talk about the STAYY SID into KSNA\/Orange County<\/strong> (guessing because it will be the first RNP 1 SID published?). So, from Septemberish to Novemberish, if you\u2019re flying there and are planning on flying this approach then you\u2019ll need to be filing these.<\/p>\n

So it’s all about RNP1?<\/h4>\n

Mostly, yes. RNP 1 SIDs and STARs require Radius to Fix (RF) capability. There is some mention of RNP2, which is used in the UK and Australia. The FAA are working with them to clarify this because there are actually two different RNP2 standards so it is currently a bit ambiguous.<\/p>\n

What are these codes?<\/h4>\n

We are seeing a \u2018Z\u2019 which will go into Item 10a and a Z1 which will go into NAV\/<\/p>\n

What else?<\/h4>\n

Here is a table. Lots of new letters with a 1 after them (or a 2) confirming your various RNP capabilities.<\/p>\n

\"\"<\/b>What do we use at the moment?<\/h4>\n

Let\u2019s take a quick jump back and talk about \u2018Relevant Flight Plan Fields\u2019.<\/b><\/p>\n

If you\u2019ve ever filed a flight plan, you are probably fairly familiar with Item 10 – Equipment and Capability<\/strong> (with 10a for your Nav, Comms and Approach Aids and 10b for your Surveillence). Then there is Item 18 – Other Information<\/strong>, and this is where you enter your PBN, NAV, DAT, SUR and COM stuff.<\/p>\n

So, depending on the type of routing or what-have-you that you plan on doing, you need to add info in item 10 and item 18 to confirm you\u2019re capable of doing it.<\/p>\n

Here is a handy table for you. Basically, if the plan is to fly a \u2019T-Route\u2019 for example, then your airplane needs to be capable of RNAV 2, which means you\u2019ll want to whack a \u2018GR\u2019 into Item 10a and a \u2018C2\u2019 into Item 18.<\/p>\n

\"\"

Current AIM instructions<\/p><\/div>\n

GR of course means GNSS and R means PBN approved. C2 means RNAV 2 GNSS specifications.<\/p>\n

If any of this is totally new to you\u2026<\/h4>\n

Maybe take a read of FAA Appendix A. FAA Form 7233-4 ‘International Flight Plan’<\/a> which covers all the boxes and their respective what\u2019s<\/em> and why\u2019s<\/em>.<\/p>\n

PBN\/ is limited.<\/h4>\n

Something else mentioned in the presentation is the limited number of PBN\/ entries<\/strong> that you can make on your flight plan. This limit means the automation which \u201creads\u201d your plan might make some assumptions. For example, if you enter a D1, D2, D4, O1 or O2 code, it is going to assume you are RNAV 2 capable.<\/p>\n

There are also certain PBN\/descriptions which don\u2019t align with any OpSpec authorisations.<\/p>\n

C3, D3, O3 \u2013 DME\/DME is not adequate for RNAV 2, RNAV 1, RNP 1 and O4\u2013 DME\/DME\/IRU alone is not adequate for RNP 1.<\/p>\n

All of which means changes are needed!<\/b><\/p>\n

A reminder on using NAV\/RNV to suppress a PBN segment<\/h4>\n

The automation (and this is a direct quote from the presentation) \u2018bases route eligibility on PBN information but overrides that with the NAV\/ information when provided\u2019.<\/em><\/p>\n

Right now, putting RNV means RNAV, so if you file NAV\/RNV the automation won\u2019t think you\u2019re eligible for an RNP routing.\u00a0In fact, 50% of flight plans which include RNP1 capability are only seen as RNAV 1 eligible. If this has happened to you, stop putting RNV in the NAV\/ string.<\/p>\n

The main point here is that the majority of users should be using PBN\/ only.<\/strong><\/p>\n

There is more.<\/h4>\n

There is more, but it might be easier to read it in the FAA presentation itself.\u00a0<\/a><\/p>\n

When all the FAA documents are changed and updated to include the new stuff, then this is what to look out for:<\/p>\n