RNAV (GNSS)

[Barronflyer]

Hi there

Can someone please advise that an RNAV (GNSS) approach requires a working GPS in all cases? I.e. with failed GPS receivers the approach cannot be flown with reference to RADIO UPDATING, INERTIAL pos etc. Silly question I know. Just trying to confirm my assumption.

Thanks

[c100driver]

Correct.

What is in the brackets is the basis of your approach. No GPS no RNAV (GNSS) approach. If it was an RNAV (RNP) you could still continue an approach as long as the ANP was within the RNP.

[8che]

Point of order there.
If it says RNAV (RNP) you certainly cannot continue without dual GPS receivers as that's an RNP AR approach or SAAR as our American friends call it and GPS is a required item.

[aterpster]

8che:

Point of order there.
If it says RNAV (RNP) you certainly cannot continue without dual GPS receivers as that's an RNP AR approach...

Absolutely correct. IRU position is for extraction in the event of a loss of GPS.

... or SAAR as our American friends call it...

We stopped using SAAR a couple years ago. They are now RNP AR.

[c100driver]

And this is where all the confusion starts, as in all aviation "it depends" on how ahead or behind your certifying authority are in the PBN world.

RNAV (RNP) is not equal to RNP APCH, it is similar in many respects but it is certainly not SAAAR or RNAV (RNP AR) or RNP AR APCH (three names for the same approach by different states).

RNAV (RNP) is not part of the ICAO PBN structure. It was an attempt to allow such equipped aircraft to operate using the current aircraft navigation capability. As such in some states RNAV (RNP) was able to be flown without GNSS, but required Radar monitoring, however many states decided (quite rightly in my view) that GNSS should be part of the aircraft system requirements. RNAV (RNP) did not have RF legs or an RNP less that 0.3:

RNAV (RNP AR), SAAAR or RNP AR APCH can have RF legs, could be below 0.3 and could be either public or tailored (private) for specific requirements.

The whole PBN debacle of nomenclature, sensor requirements etc was the result of the US and Europe heading for similar outcomes via different pathways and the slow cumbersome nature of ICAO to develop a standard.

As the ICAO contracting states start towards PBN standardisation most of the confusion "should" disappear.:ugh::ugh::ugh:

The USA name for RNP AR APCH was SAAAR (three A's) Aircraft, Aircrew Authorisation.

If it says RNAV (RNP) you certainly cannot continue without dual GPS

My regulator: you cannot start an RNP AR APCH approach without Dual GNSS but after the FF you can continue with a single GNSS.

[8che]

Well from our newly updated operations manual :


RNAV (GNSS) APPROACHES


Definition : non-precision approaches with LNAV or LNAV/VNAV minima.


- "RNAV (GNSS) approaches" corresponds to "RNP APCH operations"


- "RNAV (RNP) approaches" corresponds to "RNP AR APCH operations"


RNP AR OPERATIONS


General


Required navigation performance instrument approach procedures with authorisation required (RNP AR) are charted as RNAV (RNP) RWY XX " and contain a special note on the chart to aircrew and operators. These procedures are commonly referred to as "RNP AR" or in the USA "RNP SAAAR".

[aterpster]

8che:

Required navigation performance instrument approach procedures with authorisation required (RNP AR) are charted as RNAV (RNP) RWY XX " and contain a special note on the chart to aircrew and operators. These procedures are commonly referred to as "RNP AR" or in the USA "RNP SAAAR".

Old or incorrect source.

The U.S. changed to RNP AR at least two years ago.

[Bus Driver Man]

Hi there

Can someone please advise that an RNAV (GNSS) approach requires a working GPS in all cases? I.e. with failed GPS receivers the approach cannot be flown with reference to RADIO UPDATING, INERTIAL pos etc. Silly question I know. Just trying to confirm my assumption.

Thanks

There are approaches which are labelled as RNAV (VOR DME) or RNAV (DME DME), although they seem to be very rare.
There are some of them in Egypt like in Sharm El Sheikh (HESH): RNAV (VOR DME) 22L and 22R.
(Other airports that have them are HELX, HEAX, HESN, ...)

This RNAV approach is based on an RNAV system that doesn't need GPS, but only VOR DME position updating. I believe you still need the 0.3 RNP.
However, in the FCOM of my aircraft, it is written that for any RNAV approach which doesn't require a GPS (like the RNAV(VOR DME)), you need to apply the procedures for a RNAV(GPS) approach. Hence you need a working GPS. (However, that might be a company requirement.)

[aterpster]

The HESH 22L/R RNAV IAPs state "VOR/DME or GNSS."

So, the folks with GNSS follow standard procedure.

[aterpster]

c100:

My regulator: you cannot start an RNP AR APCH approach without Dual GNSS but after the FF you can continue with a single GNSS.

That's fine for some circumstances in more conventional instrument flying, but entering the final segment in some RNP AR approaches (say RNP of .2 or less with an RNP required missed approach) is literally going into an area where extraction should be the rule when any significant part of the avionics fails.

[Rocket3837]

I have never come across a confusing topic such as the Rnav & rnp stuff

[c100driver]

That's fine for some circumstances in more conventional instrument flying, but entering the final segment in some RNP AR approaches (say RNP of .2 or less with an RNP required missed approach) is literally going into an area where extraction should be the rule when any significant part of the avionics fails.
A single GPS "unit" failure (in a dual GPS system supporting a dual FMS) should not affect the position solution just the redundancy. As long as ANP is less than RNP and there is no trending of the ANP increasing then risk has not increased appreciably. A single GPS "unit" failure was the only failure that we could continue with after the Final Fix. If it failed prior to the Final Fix the approach could not be continued.

It has been a few years since my airline and the regulator went down the RNP AR journey of discovery but I recall that the extraction was based on, dual GPS sensor loss, FMC failure and Engine failure at missed approach point i.e. Single FMC, IRS updating only.

This was for a RNP of 0.11 for Boeing and 0.10 for Airbus into an airport that the RNP AR approach was really the only option due to the terrain and has multiple RF legs to position into a valley.

[framer]

Our company SOP's have us continue with a single GPS failure or a single. Rad Alt failure if it occurs after the IAF. Prior to that the approach can't be commenced. That is for RNP-AR.
For RNP App LNAV / VNAV you can start the approach with only one GPS and only one Rad Alt but if you lose either you must go around.
Very very confusing evolution of terminology.

[underfire]

RNP-AR with a single GPS.?

[Topper80]

Could you report some examples of airport with RNAV (RNP) and RNAV (AR RNP) ? To see differences in charting, title notes and minima.

[peekay4]

Could you report some examples of airport with RNAV (RNP) and RNAV (AR RNP) ? To see differences in charting, title notes and minima.
RNAV (RNP) implies AR.

To be more precise, in the context of PBN there are two types of approach specifications: RNP APCH, and RNP AR APCH.

1. RNP APCH. Generally charted as RNAV (GPS) in the US or RNAV (GNSS) internationally. This type of approach mainly consists of straight legs. Obstacle clearance and approach minimums do not require specific RNP capabilities. (Instead, minimums depend on approach type being flown, e.g., LPV, LNAV/VNAV, etc.) Example: KSFO RNAV (GPS) Z RWY 28R.

2. RNP AR APCH. Generally charted as RNAV (RNP). This type of approach may include curved (RF) legs. Obstacle clearance and approach minimums developed against specific RNP capabilities (e.g., RNP 0.3 or RNP 0.1). Special authorization is required. Minimums not necessarily lower than RNP APCH (might even be higher). Example: KSFO RNAV (RNP) Y RWY 28R.

[c100driver]

Here is a link to a full tailored type approach for RNP AR APCH even though the landing plate is is called RNAV (RNP) Y RWY 23 at Queenstown NZ

AIP New Zealand (http://www.aip.net.nz/pdf/NZQN_45.1_45.2.pdf)

The second link is a Public RNP AR APCH for Auckland NZ

AIP New Zealand (http://www.aip.net.nz/pdf/NZAA_45.3_45.4.pdf)

The third is for a straight RNAV (GNSS) Z approach at Auckland NZ

AIP New Zealand (http://www.aip.net.nz/pdf/NZAA_45.1_45.2.pdf)

[aterpster]

Here are approaches to Rifle (KRIL), Colorado, Runway 8. For folks with biz jets that can do RNP AR, look at the huge improvement with RNP AR, especially RNP 0.10.

The smart folks with the equipage divert to Rifle when Aspen weather is marginal.

http://i201.photobucket.com/albums/aa214/aterpster/KRILRNAVY8_zps255e96e0.jpg

http://i201.photobucket.com/albums/aa214/aterpster/KRILRNAVZ8_zps2bb039af.jpg

[c100driver]

Nice approach that RNAV (RNP) Z RWY 8. Interesting the difference in GP angle achieved with the RNP by being able to reduce the altitude further out on the approach than the RNAV (GPS)

[Topper80]

RNAV (GPS) Y 08
Minima in only LNAV, not LNAV/VNAV: is consider anyway to be a APV approach?

[aterpster]

No. It is considered to be a NPA. Because the visual segment area does not have significant obstacle penetrations, it does have what the FAA calls a vertical descent angle (VDA). But, the VDA is advisory; does not meet APV criteria. If it were an APV, there would be an LNAV/VNAV line of minimums.

[Topper80]

Thanks, an other question:
RNAV (GPS) do not require a specific RNP (eg. 0.3). On my AOC I' m authorized to operate down to RNP 0.3 but we are not authorized for RNP approaches ( coded RNAV(RNP) ).
Where can I use my RNP 0.3 ?? :ugh:

[aterpster]

Topper80:

Thanks, an other question:
RNAV (GPS) do not require a specific RNP (eg. 0.3). On my AOC I' m authorized to operate down to RNP 0.3 but we are not authorized for RNP approaches ( coded RNAV(RNP) ).
Where can I use my RNP 0.3 ??

I can only speak for the US. LNAV and LNAV/VNAV are RNP 0.3, but the lateral obstacle clearance areas are larger than RNP AR 0.30, and don't require the avionics redundancy required for RNP AR.

Then, we also have LPV and LP, which are predicated on SBAS augmentation. Western Europe is also doing SBAS augmentation.

[Capn Bloggs]

No. It is considered to be a NPA.
The latest ICAO concept that has reached us, 2D and 3D approaches, has NPAs that are flown with an FMS-derived approach path may be classed as a 3D approach. It won't have a DA, so it's up to the operator to not go below the MDA.

[aterpster]

Captain Bloggs:

The latest ICAO concept that has reached us, 2D and 3D approaches, has NPAs that are flown with an FMS-derived approach path may be classed as a 3D ie "precision" approach. It won't have a DA, so it's up to the operator to not go below the MDA.

Be that as it may be, FAA flight inspection is continuing to remove or not accept VDAs on many NPAs in the U.S. If the runway doesn't have an APV there are obstacle issues in the visual segment. If flight inspection judges them significant the VDA is removed (or disapproved on new NPAs, such as LP and LNAV), thus there will be no vertical path such NPAs in the FMS.

[aterpster]

Underfire:

RNP-AR with a single GPS.?

As you know the missed approach segment is often not critical. The only clue the pilot has is when the chart states RNP of less than 1.0 is required for the missed approach.

Since Rifle, Colorado Runway 8 has been an example of low minimums but not a critical missed approach (other than climb performance) here is a more "terpsy" look at RNAV Z Runway 26. The missed approach is critical. By continuing past the FAF with one GPS receiver, the odds of having to conduct an IRU coasting missed approach are certainly increased significantly; probably reducing the target level of safety below the presumed value for this IAP.

I have pasted the missed approach "telescoping" values on the Jepp chart, followed by the actual FAA TERPS map. Not a friendly environment for coasting on IRU(s).

http://i201.photobucket.com/albums/aa214/aterpster/KRILRNAVZRwy26_zps20afa7e1.jpg

http://i201.photobucket.com/albums/aa214/aterpster/RNAVZ26MAP_zps412d9adb.jpg

[peekay4]

RNAV (GPS) Y 08
Minima in only LNAV, not LNAV/VNAV: is consider anyway to be a APV approach?
An APV approach will always list a DA instead of an MDA, so that's an easy way to tell if the approach is considered an APV or an NPA.

Currently the only APV approaches are: LNAV/VNAV, LPV and RNP.

The latest ICAO concept that has reached us, 2D and 3D approaches, has NPAs that are flown with an FMS-derived approach path may be classed as a 3D ie "precision" approach. It won't have a DA, so it's up to the operator to not go below the MDA.

That's not exactly right. Some countries are operating with a special waivers / ops specs / procedures allowing approved operators flying certain NPA approaches using Continuous Descent Final Approach (CDFA) to treat MDA as DA. Under this procedure the operator may actually descend below the published MDA during a missed approach.

However such an approach is still not considered a "precision approach" under ICAO definition. Currently only ILS, MLS and GLS approaches meet the criteria for "precision approach".

[framer]

Under this procedure the operator may actually descend below the published MDA during a missed approach.
This surprises me and I find it hard to believe. Why don't they just add 50ft like they do in NZ and Australia if they are going to treat an MDA as a DA?

[peekay4]

This surprises me and I find it hard to believe. Why don't they just add 50ft like they do in NZ and Australia if they are going to treat an MDA as a DA?

The point is to reduce minimums when safe practices allow it.

Examples:

1. FAA OpSpec C073 VNAV MDA as DA:

"The certificate holder is authorized to use minimum descent altitude (MDA) as a decision altitude (DA)/decision height (DH) with vertical navigation (VNAV) on a Nonprecision Approach (NPA)."

8900.183 - OpSpec/MSpec/LOA C073, Vertical Navigation (VNAV) Instrument Approach Procedure (IAP) Using Minimum Descent Altitude (MDA) as a Decision Altitude DA)/Decision Height (DH) ? Document Information (http://www.faa.gov/regulations_policies/orders_notices/index.cfm/go/document.information/documentID/1019907)

2. Transport Canada Special Exemption from 602.128(2)(b)

"The purpose of this exemption is to permit pilots-in-command of IFR aircraft operated by holders of an air operator certificate or a temporary private operator certificate to descend below the minimum descent altitude (MDA), when conducting a non-precision approach ... following a stabilized constant descent angle (SCDA) non-precision approach."

EXEMPTION FROM PARAGRAPH 602.128(2)(b) OF THE CANADIAN AVIATION REGULATIONS - Transport Canada (http://www.tc.gc.ca/CivilAviation/Regserv/Affairs/exemptions/docs/en/2509.htm)

(SCDA is the Canadian term for CDFA).

[Capn Bloggs]

Interesting stuff, PK. I've amended my earlier post re "precision".

[framer]

Peekay4,
Thanks for posting that.
It's interesting how different regulators around the world view different subjects and what they are willing to provide exemptions for.
I understand that the lower the minima the better commercially but can't ever imagine our regulators " down under" being willing to sign off on certain operators descending below MDA even if it is just 50 feet or so.

[imriozer]

I found that this is in my opinion is the best place to ask the question because it seems that the real experts are here.

Two weeks ago during a ramp check the only complaint they had was on the RNAV subject and the complaint was that we didnt specific which systems (DME, VOR and GPS) affect the navigation and any combination in between. Is this the way your MEL written/deigned ?

[peekay4]

Short answer is "within half-scale deflection" of the CDI.

Generally, to be established on a segment implies all of the below:

1. You've passed the segment's defining fix
2. You are receiving "positive course guidance" (PCG) from the navigation system
3. You are within half-scale deflection on the CDI **
4. You are "stable" in the segment (i.e., with a positive trend to track the centerline)

** The "+/- 5 degrees" is mostly for NDBs (since there's no CDI).

[peekay4]

Have you met all four criteria listed above? (Including #1)

If not, you're not established.

You have to be within half-scale of the centerline defining the segment your are joining, not your route to the segment.

[peekay4]

Hmm, sorry, I have to take back some of I wrote above.

For RNAV and RNP:

1. Instead of "half-scale deflection", the guidance for established is: "An aircraft is considered to be established on-course during RNAV and RNP operations anytime it is within 1 times the required accuracy for the segment being flown." (The scale will depend on your FMS but this seems to imply full-scale deflection).

2. Instead of waiting to "pass" the segment's defining fix, the exact standard is: "(a) Pilots flying FMS equipped aircraft with barometric vertical navigation (Baro-VNAV) may descend when the aircraft is established on-course following FMS leg transition [to the next segment]. Leg transition normally occurs at the turn bisector for a fly-by waypoint [...] (b) Pilots flying TSO-C129 navigation system equipped aircraft without full automation should use normal lead points to begin the turn. Pilots may descend when established on-course on the next segment of the approach."

The italicized quotations are from revised FAA AIM 5-5-16. RNAV and RNP Operations:

https://www.faa.gov/air_traffic/publications/atpubs/aim/aim0505.html

[aterpster]

There is another part of the AIM which discusses passing the bisector of a course change to be considered in the succeeding segment of an IFP.

That's how the avionics work.

[alphacentauri]

Be that as it may be, FAA flight inspection is continuing to remove or not accept VDAs on many NPAs in the U.S. If the runway doesn't have an APV there are obstacle issues in the visual segment. If flight inspection judges them significant the VDA is removed (or disapproved on new NPAs, such as LP and LNAV), thus there will be no vertical path such NPAs in the FMS.

What do they achieve by doing this?

The whole point of providing VDA's is to give those without FMS's a flighting chance of flying a stable approach, and those with FMS's the ability to use vertical guidance...which according to ICAO is more safe.

Have they not just increased the risk of instability on the approach?:confused:

There are other ways to deal with obstacles in the visual segment. Removing the VDA is a poor option.

Alpha

[aterpster]

There are other ways to deal with obstacles in the visual segment. Removing the VDA is a poor option.

I review every FAA IFP as they are posted for public review. It appears that it is flight inspection that removes them, not the initial designers.

The FAA position is that the airport either remove the 20:1 penetration, or mitigation (sometimes) with a VGSI. But, when flight inspection doesn't like what they see for daytime operations the VDAs go.

I feel they are more concerned about FAA liability than safety.

[7478ti]

The KRIL RNP based approach minima at RNP .1 could still safely be even lower, if the present obsolete and unnecessary limitations were removed that are still being placed on RNP procedure design. The fully allocated real VEB could easily provide for DA(H) down to and even somewhat below 200' HAT compared to the higher DA(H) shown for the RNAV(RNP) Z Rwy 8. The present 250' HAT floor limit was only put there for largely political reasons, not due to any technical limitation of engineering or physics. That potential additional advantage for RNP is particularly valid considering that any aircraft with RA available could also use an RA floor to additionally bound improbable to extremely improbable VNAV non-normal events. Unlike with TERPS or PANS-Ops, with [real] RNP, particular non-normal as well as rare-normal events are already suitably addressed and accommodated.

[alphacentauri]

Aterpster, I wasn't criticising you. I was just questioning the FAA logic

It would be interesting to know the logic and what they think they are achieving.

[peekay4]

It would be interesting to know the logic and what they think they are achieving.
VDA only provides advisory obstacle protection until the MDA. Once below the MDA, the VDA is no longer valid -- you are now flying a visual segment and thus must (visually) fly clear of obstacles.

But most pilots don't know this. Most think VDA provides obstacle clearance to the runway. So with the VDA plugged in, pilots tend to "blindly" follow the glideslope all the way down to the runway threshold. This is dangerous if there are obstacles penetrating the 34:1 (1.68 degree) protection surface.

The example commonly cited is KBHM RNAV (GPS) RWY 36 (Birmingham, AL). If you fly the 3.04 degree VDA to the MDA, then transition to land visually, no problems. But if you continue flying the VDA below the MDA, you get perilously close to a house sitting on top of a ridge, 2nm from the runway. The roof of the house penetrates the 34:1 surface, providing just 190ft clearance below the VDA path (picture below):

https://s3.amazonaws.com/org.barkah.longexp/Misc/kbhm-rwy-36.jpg
House penetrating 34:1 surface @ KBHM RWY 36 (from FAA briefing notes)

So the FAA will no longer publish a VDA if there are obstacles penetrating the 34:1 surface.

[alphacentauri]

peekay4, thank you for your response and image. Even after your explanation I still don't know what the FAA are achieving by removing the VDA.

VDA only provides advisory obstacle protection until the MDA. Once below the MDA, the VDA is no longer valid -- you are now flying a visual segment and thus must (visually) fly clear of obstacles.

This is correct, but when the aircraft is visual don't we still expect that the VDA can be maintained to the threshold?. After all as procedure designers don't we build a VDA from the threshold for the aircraft to fly? I would not expect an aircraft to have to change the descent profile to get to the threshold. This is why the VSS was invented. If the VSS is not penetrated then we expect the aircraft can fly a constant profile to the threshold. If it is penetrated then you increase the VDA or remove the straight in minima. (ICAO criteria) Removing the straight in minima forces the aircraft to get visual at a higher altitude and thus have time to visual mitigate the offending VSS penetration.

Question: When the FAA remove the VDA are they also removing the straight in minima?

To try to explain better what I am saying, lets take the Birmingham example, and lets assume that there is no VDA published....

The example commonly cited is KBHM RNAV (GPS) RWY 36 (Birmingham, AL). If you fly the 3.04 degree VDA to the MDA, then transition to land visually, no problems. But if you continue flying the VDA below the MDA, you get perilously close to a house sitting on top of a ridge, 2nm from the runway. The roof of the house penetrates the 34:1 surface, providing just 190ft clearance below the VDA path (picture below):

With no VDA published the pilot still wants to fly as stable approach as possible and now has to guess a suitable descent profile. With no guidance from the approach plate...lets assume he guesses 3 degrees (cause thats a normal profile)...he now has much less than 190ft clearance from the house.

I would suggest the approach profile for this approach is too shallow. So as I see it you have 2 choices. Increase the profile 3.1 or 3.2 should do it...or publish a circling minima only ( I would put an aeronautical light in the roof as well). This forces the aircraft to have to visually mitigate the obstacle.

I just don't see how removing the VDA mitigates this problem..

[aterpster]

Seems like the FAA didn't do their job with those houses. They appear to penetrate Part 77 surfaces for Runway 36 and should have been issued Hazard Determinations.

Also, where was the airport management when those houses were proposed?

[aterpster]

Peekay4:


So the FAA will no longer publish a VDA if there are obstacles penetrating the 34:1 surface.

That is not correct.

Since I couldn't find a Terps Instruction Letter or policy memo on AFS-420's website, I asked the author of Order 8260.19. He advises me it is still somewhat a "hot potato." It is still flight inspection's call. If they feel it should be removed, then in some cases Aero Nav designers first try to raise the angle.

[peekay4]

I asked the author of Order 8260.19. He advises me it is still somewhat a "hot potato." It is still flight inspection's call.

Yes, I shouldn't have been so definitive.

I believe the actual process is as follows:

1. If the 34:1 surface isn't clear, then Flight Inspection will assess the approach
2. During assessment, the VDA guidance will be flown "one dot low"
3. If stable descent can't be maintained at "one dot low", then VDA will not be published
4. Similarly, if a EGPWS warning occurs, then VDA will not be published

Question: When the FAA remove the VDA are they also removing the straight in minima?

VSS is a (relatively new) ICAO concept. FAA uses TERPS to determine if an approach meets the straight-in criteria.

I'm not a TERPS expert but I believe despite the obstacle, KBHM RNAV RWY 36 does meet the straight-in criteria:

- The final approach course is aligned with runway
- The computed VDA at 3.04 degrees is within limits (to MDA)
- Required Obstacle Clearance (ROC) of 250 ft is maintained when approach is flown as designed (leveling off at MDA)
- Height above touchdown (HAT) is < 1000 ft

FAA allows the 34:1 (and 20:1) protection surfaces to be penetrated. However, higher visibility limits will be imposed as a result. E.g., in this case, the minimum visibility was raised to 1 SM (5000 RVR) for Cat A

I do agree that this approach should be revisited; e.g., moving the FAF so a descent angle of 3.2 degrees can be maintained throughout.

[7478ti]

It is a hot potato specifically because both TERPS and PANS-Ops have largely ignored this issue of assuring a safe flight path below DA(H) to the TDZ since the concept of original TERPS and before before CRM was invented (and well before 1975). Hence ONLY [real] RNP protects all the way to the TDZ, and all the way back out, for a balked landing from the TDZ, considering both rare normal and selected non-normal events (e.g., the first nav failure, and the first engine failure on a multi-engine aircraft). Hence NO TERPS or PANS-Ops procedure would ever pass a serious scientifically derived SSA, FMEA, or FHA, at anything other than a largely trivially un-obstructed runway. This was one of the original and continued flaws in both TERPS and PANS-Ops, which led to RNP, and for which (other than the well configured and signed AC120-29A), still has unnecessary, counterproductive, and flawed criteria even being used by FAA in their other RNP references for their version of pseudo RNP [lite] (e.g., AC90-101A and AC90-105). This is why airlines using [real] RNP procedures typically use criteria related back to the criteria of AC120-29A, and not other more recent FAA RNP related criteria.

[alphacentauri]

Peekay4, again thankyou for the information (its interesting to see how the rest of the world deals with this)...and no I am not picking on you. I am really trying to understand the FAA course of action. (I owe you a beer for all the hard questions)

So, after all that,

It appears the example cited to explain the why the FAA are removing VDA's actually meets the criteria and in all likely hood was removed by a flight inspection pilot because he/she got the heeby jeebies about the house on the hill.

I don't know too much about the accident being referred to, but at the end of the day they landed short? Correct? This indicates to me that a whole bunch of things went wrong....not limited to a) following vertical guidance below the MDA b) loss of situational awareness when doing this, which leads to c) poor airmanship.

I am not surprised that they hit the ground whilst following vertical guidance....that's where vertical guidance is supposed to take you. The fact that they didn't hit anything on the way to the ground indicates to me that the other design considerations to protect to the ground are valid as well. If the aircraft had left a smoking hole at the top of the hill and wiped out the house, then we have an argument.

If they missed the house on the hill....which I assume they did....then isn't the house on the hill a bit of a red herring?

3. If stable descent can't be maintained at "one dot low", then VDA will not be published

If stable descent can't be maintained at "one dot low" then the incorrect VDA has been used to design the approach.

Question for everyone. How does removing the VDA make this situation better or safer?

[aterpster]

Tom Imrich:


The KRIL RNP based approach minima at RNP .1 could still safely be even lower, if the present obsolete and unnecessary limitations were removed that are still being placed on RNP procedure design. The fully allocated real VEB could easily provide for DA(H) down to and even somewhat below 200' HAT compared to the higher DA(H) shown for the RNAV(RNP) Z Rwy 8. The present 250' HAT floor limit was only put there for largely political reasons, not due to any technical limitation of engineering or physics. That potential additional advantage for RNP is particularly valid considering that any aircraft with RA available could also use an RA floor to additionally bound improbable to extremely improbable VNAV non-normal events. Unlike with TERPS or PANS-Ops, with [real] RNP, particular non-normal as well as rare-normal events are already suitably addressed and accommodated.

Tom, you are missing the climb gradient limitations on both runway ends at KRIL. That's a fact of RNP AR life, although you may not agree with it.

When you were at the FAA TERPs was in the dark ages compared to today. You know, I was involved then as well.

We have the GQS, which we did not have circa 1975. We have the visual segment, which we did not have back then. And, as tentative as it is on some NPAs, we have the VDA, which we did not have back then.

As you well know, there are runway ends that you can't make a silk purse out of a sow's ear.

Speaking of RNP AR, let's get away from baro in the final segment by having the avionics switch from RNP to LPV for the last 2, or so, miles to the runway end. Or, would Boeing not like that idea?

As we all know, the original model of RNP AR was predicated upon the equipage of Boeing transports at the time.

[peekay4]

If stable descent can't be maintained at "one dot low" then the incorrect VDA has been used to design the approach.
Yes and no.

Non-precision CDFA is also a relatively new concept. There are literally thousands of non-precision approaches in the US alone -- developed long before the CDFA concept -- which have obstructions in the 34:1 and 20:1 protection surfaces.

These old approaches were never designed for continuous descent. What mattered in the past was meeting the required clearance at the MDA floor after a series of step-downs.

So the VDAs for these approaches are constrained by the existing designs. The VDA isn't "selected". By rule, the VDA is simply the angle from the existing FAF to the TCH.

I.e., for these thousands of approaches, the VDA is calculated "after the fact".

This "after the fact" calculation is ok if the VDA is only used to the MDA. Below the MDA, however, there's no obstacle clearance guarantee if the 34:1 surface is penetrated.

Question for everyone. How does removing the VDA make this situation better or safer?

FAA did some tests. With the computed VDA, predictably every approach even when flown perfectly got too close "to the house" (~190 ft) and triggered EGPWS warnings. This is an accident waiting to happen.

Without the VDA, these old approaches get flown "as they were designed" (dive-and-drive). Meaning, pilots would "correctly" level off at the MDA and pass well clear of the house at a protected altitude, before making a visual landing.

So until the approach can be redesigned, we have to do a risk analysis: Which option is worse? a) using CDFA but getting perilously close to obstacles; b) reverting back to dive-and-drive but remaining well clear of obstacles.

FAA picked option b).

[Jet Jockey A4]

I agree with your interpretation as to why the FAA is "taking out" the VDA info off the approach plates on "non precision" approaches.

It seems to be a fact that some pilots think that on a non precision LNAV or LNAV/VNAV approach they are protected from obstacles on that last segment of the approach and the question is why?

There as not been one recurrent ground school I have been too that this is not brought up and explained. It is also brought up in the sim and also during your initial type rating when in the FMS and approach selections are talked about.

Now I believe someone asked about if 1 or 2 GPS are required for an approach.

For non precision approaches like LNAV and LNAV/VNAV, only one GPS is required but for a precision approach like a LPV with their lower minimums, approaching the FAF you need to see dual independant LNAV/GPS sources, in other words 2 GPS are required (like in a CAT II ILS requires 2 ILS receivers) to continue down to LPV minimums.


Now where I'm not sure I agree with you is the descent below MDA statement you brought up.

Again in class this subject was brought up and not for the first time the instructors are clear on this and this is valid for boththe FAA and Transport Canada... Anyone that goes below a MDA altitude on an approach (before being visual) will be busted thus the reason and option (if granted) to add 50 feet to the MDA altitude and to now treat it as a DA.

[peekay4]

Hi Jet Jockey,

For the last part, have you read the Transport Canada exemption cited previously?

EXEMPTION FROM PARAGRAPH 602.128(2)(b) OF THE CANADIAN AVIATION REGULATIONS - Transport Canada (http://www.tc.gc.ca/CivilAviation/Regserv/Affairs/exemptions/docs/en/2509.htm)

This CAR exemption allows descent below MDA during a missed approach incorporating "stabilized constant descent angle" (Canada's term for CDFA) . The exemption is valid for qualified operators until April 30, 2015.

Under this exemption, you don't need to add "50 feet" to the MDA (aka Derived Decision Altitude -- DDA) unless:

- there is a failure of an aircraft system;
- the aircraft is above normal maximum landing weight;
- the aircraft landing weight is limited by aborted landing climb performance; or
- height loss could be expected to be larger than normal.

The main text of the exemption is quoted below:

The purpose of this exemption is to permit pilots-in-command of IFR aircraft operated by holders of an air operator certificate or a temporary private operator certificate to descend below the minimum descent altitude (MDA), when conducting a non-precision approach, even if the required visual reference necessary to continue the approach to land has not been established. This exemption is required in order to accommodate the altitude loss below MDA that will likely occur during a missed approach, following a stabilized constant descent angle (SCDA) non-precision approach.

The FAA has a similar policy as mentioned previously.

[Jet Jockey A4]

Thanks for the clarification... I had missed the point about the CDFA although I don't get its point.

The whole purpose of adding the 50 feet to a MDA approach when flying a "VPATH" or one as to assume a CDFA is to not go below the MDA in the event of a missed approach.

I personally don't understand the FAA and TC on that one.

[peekay4]

Without the exemption in place:

- If you do a "dive-and-drive", you're allowed to descend to the MDA, have a look around, and stay there until the MAP in hopes of seeing the runway environment.

- If you fly CDFA, then you're only allowed to descend to the DDA (MDA + 50ft) before a mandatory missed approach at that point, even if you haven't reached the MAP.

This gives a "disincentive" from flying CDFA. You are essentially being penalized both in terms of minimum altitude and missed approach position for "doing the right thing."

Of course, some ICAO states simply say "tough luck, if you're an air carrier we're going to require you to fly CDFA until a DDA, by regulations".

TC and FAA have taken a different approach by removing the disincentive.

[Jet Jockey A4]

Which is totaly stupid IMHO.

The whole point of the constant descent approach is get to a DA and if you see nothing, get the hell out by doing a missed approach.

For the last 15+ years I have been told by TC that the dive and drive concept is a thing of the past, that constant descent approaches are the thing to do for safety and now they allow this? The only exception to this is a circling approach which is another subject and one that I personally don't think should be allowed for jet operations. I'm glad to see that there is a move to increase the MDAs because of the increase distances per category of aircraft speeds for circlings.

My last airline (a while back) had 1000' and 3 miles as its circling minimums for our jet operation and today with GPS there is no reason not to have some sort of approaches to all runways.

In any case I much prefer the European view which is IMO, is the safer alternative. If an approach to a runway as a higher minimum so be it... A missed approach at its DA, regardless of height above the airport or distance from runway end is a must if the criteria for the approach are such that obstacles require a high MDA/ DA.

[aterpster]

and today with GPS there is no reason not to have some sort of approaches to all runways.

Terrain and obstacles.

[Jet Jockey A4]

Terrain and obstacles are a possibility but IMO this could/would be in a minority of approaches at certain airport and when you look at what is capable with some GNSS approaches like the one in Rifle it is hard to believe some sort of GPS approach couls not be made available to most runways.

Besides if with much higher minimums a circling approach to a runway is available I'm pretty sure a GPS approach to that runway could be designed.

[aterpster]

Terrain and obstacles are a possibility but IMO this could/would be in a minority of approaches at certain airport and when you look at what is capable with some GNSS approaches like the one in Rifle it is hard to believe some sort of GPS approach couls not be made available to most runways.

Those are RNP AR approaches, which require a very high equipage bar. Most airframes simply do not have the equipment.


Besides if with much higher minimums a circling approach to a runway is available I'm pretty sure a GPS approach to that runway could be designed.

Alas, that is simply not the case.

[Topper80]

Sorry guys, I'm referrig back to post #18 relative to RNAV GPS 8 Y:
Is it allow to fly down to LNAV(only) minima using LNAV and VS or is mandatory to use LNAV and VNAV ?

[LNIDA]

LNAV minima will be higher than LNAV/VNAV minima, the latter is for all practical purposes a precision approach and in the case of Jepp's there is no requirement to add 50'

You can fly an LNAV down to LNAV minima in either V/S or VNAV but again in Jepp's case its a non precision approach, it is normally recommended that it is flown in VNAV but may be flown in the alternative method using V/S, but why would you??

If it is a LNAV/VNAV RNP (BARO VNAV) it must be flown in VNAV and for the 737NG VOR update must be switched off and vertical RNP must be changed from 400' to 125'

All of the above not to be confused with an RNP-AR approach

simples.......

[Topper80]

To LNIDA: I agrre with you but in my Boeing FCTM I found:" RNAV approaches require LNAV and VNAV modes to be used regardless of the minima publihed" and this confused me.....

[LNIDA]

LPV (Localiser performance with Vertical guidance) Boeing aircraft are not equipped to utilise LPV minimums.

But i take your point :ok:

[Jet Jockey A4]

The FAA and Transport Canada recognize only the LPV approach as a "precision" approach.

LNAV and LNAV/VNAV are considered "non precision" approaches.

Any approach (LNAV and LNAV/VNAV) that shows its minimum as a MDA minimum must not be flown below that minimum in the event of a missed approach (usually) and that is the reason for some operations adding an increase of 50 feet to that MDA to make it a DA.

[Jet Jockey A4]

That's because they added 77 feet to change it to a DA.

[peekay4]

The FAA and Transport Canada recognize only the LPV approach as a "precision" approach.

LNAV and LNAV/VNAV are considered "non precision" approaches.

No, an LPV is not considered a precision approach.

LPV and LNAV/VNAV are considered Approach with Vertical Guidance (APV). APV minima depict DA(H).

LNAV is considered a Non-Precision approach (NPA). NPA minima depict MDA(H).

One does not "add" anything to an LPV or LNAV/VNAV procedure to "change it" into a DA. The DA is determined by obstruction clearance standards.

For definitions, ref: AIM 5-4-5, FAA Order 8260.3B, Transport Canada AC 700-023, and ICAO Annex 10.

Or see some discussion earlier in the thread.

[Denti]

Guess some of the procedures described here are company procedures.

If it is a LNAV/VNAV RNP (BARO VNAV) it must be flown in VNAV and for the 737NG VOR update must be switched off and vertical RNP must be changed from 400' to 125'.

That is the procedure we use for RNP AR approaches, but for normal LNAV/VNAV RNAV procedures we simply press APProach and go, there is no need for any other switching. On the bus we use a fully managed approach for normal RNAV LNAV/VNAV approaches, however in my opinion the implementation of "fully managed" is better on the boeing than on the bus.

LNAV minima will be higher than LNAV/VNAV minima Again, that depends. Especially to which temperature that LNAV/VNAV minimum can be used. If too low a temperature is chosen the minimum can be substantially higher than the bare LNAV minimum.

[Jet Jockey A4]

My mistake, I did not proof read my comment and you are correct about not adding the 50 feet to the LNAV/VNAV approach. I meant to say all other non precision approaches can be flown to a DA instead of MDA by adding 50 feet if your company is entitled to.

However I would have agreed with you on the LPV "non precision" approach status until a few days ago.

I'm just back from a recurrent training and the instructors at the training facility told us that the FAA just changed the status of the LPV approach (I assume this change happened not too long ago) and without giving us more specifics, that the LPV approach is now considered a "precision approach".

We were told the same thing in the sim by the sim instructor and our check pilot also alluded that he read something lately about LPVs from TC. His comment was that it was in the final stages of being approved by TC as a precision approach... Just passing on what I was told in class and in the sim a few days ago.

Also the aircraft manufacturer of the aircraft I fly as now changed the autopilot limitation to allow us to fly down to 80 feet on a LPV approach just like a CAT I or II approach. All other types of approaches are still restricted to 320 feet AGL with the AP engaged (which in itself means nothing on how it relates to LPV approach status).

[peekay4]

I'm just back from a recurrent training and the instructors at the training facility told us that the FAA just changed and I guess that means not too long ago and without giving us more specifics, that the LPV approach is now considered a "precision approach".

Yes, and no. As of November (last month) the ICAO reclassification scheme went into effect and will eventually be fully incorporated by member states.

The new scheme introduces two types of approach methods (2D and 3D), two types of approach minima (Type 1 and Type 2), in addition to redefining three types of approach procedures (NPA, APV, and PA).

1. Approach methods:

2D: without vertical guidance, flown to an MDA(H)
3D: with vertical guidance, flown to a DA(H)

2. Approach minima:

Type A: minimums 250 ft (75m) or greater
Type B: minimums below 250ft (75m), and further divided into CAT I, II and III

3. Approach procedures:

Non-Precision (NPA): an instrument procedure (IAP) designed for 2D Type A
Approach with Vertical Guidance (APV): an IAP designed for 3D Type A
Precision Approach (PA): an IAP designed for 3D Type B

You can see even in the "new world" there is still a differentiation between APV and PA approach procedures, although they are both considered 3D procedures.

The beauty of all the above is I haven't had to specify any kind of equipment (ground & airborne) are required to fly an approach. The new classification better aligns with the Performance Based Navigation (PBN) concept.

With the new classification, in the future we can better "mix and match" what equipment can be used with which approach procedures (so back to the original question asked in this thread).

So how will existing LPV approaches fit into the new classification? Depends on the particular approach procedure. Many LPV approaches do meet the criteria for a Precision Approach procedure (e.g., at KAPA Rwy 35R), but other LPV approaches only meet the APV criteria (e.g., at KRIL Rwy 26).

[Jet Jockey A4]

Well I guess we just better start making pop corn and see how all of this will play out! :ok:

Why can't they just keep it simple? :ugh:

[peekay4]

2D: without lateral guidance

Haha, thanks for catching that. Fixed.

Life may end up being simpler with the new classification -- in the future. It's just that we're in transition now, so things seem complex since we have to live with the old and the new.

E.g., today we have so many types of approach procedures because they are based on the equipment required (NDB, Lctr, VOR, VOR/DME, ILS, LOC, MLS, GPS, GLS, RNP, etc., etc.) This situation will only get worse as new technologies come online.

In the future, we may end up with just three standardized approach procedures (NPA, APV, PA). That's it. Most aircraft will have GPS/RNAV and most airports will have at least one 3D approach.

From a pilot's perspective, all we care about if we're going to fly 2D or 3D. The FMS can automagically select the most appropriate approach technology & calculate the relevant minimums based on equipment available.

Simple. Maybe? Depends on how the transition goes, I guess.

[underfire]

200' ROC, 50' momentary descent.....until they get over that, you are stuck.

[aterpster]

peekay4:

Most aircraft will have GPS/RNAV and most airports will have at least one 3D approach.

If it were only so. But look at all the LP approaches in FAA-dom now, and they are being added quite rapidly.

[peekay4]

Yeah.

In 2010, ICAO resolution A37-11 set the goal that all instrument runway ends world-wide shall have APV (3D) approach procedures by 2016, with 70% to be completed by this year. Under some exceptions, straight-in 2D LNAV approaches may be substituted.

While this lofty goal will be hard to reach, the transition to RNAV/GNSS/PBN as the primary method for approaches seem inevitable.

Here's the 2012 snapshot of the progress towards that goal, with a number of member states already achieving much, from the ICAO database (http://www.icao.int/safety/pbn/Pages/DB-View.aspx#chartAnchor):

State (% PBN Runways completed, 2012)

Finland -- 96%
United States -- 94%
New Zealand -- 94%
Kenya -- 93%
Australia -- 91%

Austria -- 79%
Canada -- 75%
Egypt -- 71%

Brazil -- 62%
Germany -- 54%
Czech Republic -- 53%
Chile -- 52%

Costa Rica -- 40%
France -- 38%
Denmark -- 37%
Norway -- 36%
Switzerland -- 35%
Singapore -- 33%

Netherlands -- 26%
Thailand -- 24%
Japan -- 23%
Indonesia -- 21%
Russian Federation -- 20%
United Kingdom -- 19%
Spain -- 14%

China -- 9%
Ecuador -- 9%
Italy -- 8%
Sweden -- 5%
Turkey -- 3%

Mexico -- 2%
India -- 1%
Belgium -- 0%
Greece -- 0%
Ireland -- 0%
Israel -- 0%

(*) A number of small states with few instrument runways are either at 100% or 0% completion.
(**) These are 2012 numbers (latest in the published database), many states have made considerable progress since.

[aterpster]

While this lofty goal will be hard to reach, the transition to RNAV/GNSS/PBN as the primary method for approaches seem inevitable.

No doubt about it for IFR airports. (That leaves a whole lot of VFR airports without anything.)

And, the GNSS/GPS/RNAV IAP may be nothing more than LNAV to circling minimums and perhaps at a 90 degree angle to the runway. (example KEMT).

Make no mistake, the FAA didn't pay for WASS unless they wanted LPV to "every runway end." But, that was the high-level movers and shakers. Not those who faced with the hard realities of terrain and close-in runway environment.

Further, ILS at the principal U.S. airline airports will remain primary. As well as in the lofty ICAO world. :)

[peekay4]

Further, ILS at the principal U.S. airline airports will remain primary. As well as in the lofty ICAO world.
Well the intent (both FAA and ICAO) is to eventually replace the majority of ILS installations with WAAS or GBAS approaches (i.e., LPV and GLS). GLS CAT I is already operational in the US, and the FAA is currently testing GLS CAT III prototypes. (Only about 100 of the 1,200 ILS systems in the US are CAT II/III).

The FAA had planned to start phasing out some ILS installations by 2015, however the timing may be under review.

I believe the FAA is still committed to decommission the vast majority of VORs by 2020. A huge number of existing ILS procedures must be revised as a result. I wouldn't be surprised if many of the ILS procedures will be retired along with the VORs.

[aterpster]

Well the intent (both FAA and ICAO) is to eventually replace the majority of ILS installations with WAAS or GBAS approaches (i.e., LPV and GLS). GLS CAT I is already operational in the US, and the FAA is currently testing GLS CAT III prototypes. (Only about 100 of the 1,200 ILS systems in the US are CAT II/III).

Politics and economics always trump the FAA. GLS is slowly progressing because one airline is willing to dabble with it.

But, think if you were a fleet manager at say, DAL or AAL, where Boeing wants a million dollars per airplane in your 150 bird fleet to change out your FMS and related gear to give you WAAS/LAAS and GLS auto-land capability. I don't know the exact count of CAT III ILS's but your number sounds correct. Those 100, or so, CAT III systems are at airports that get weather on a frequent enough basis that fail-active autoland is essential.

I those CAT III ILS's will be around for a lot of years.

As to VORs, the FAA is already pruning them, but rather slowly. They agreed with ICAO to not decommission any VORs that are the end point of oceanic routes. Also, few, if any, in the intermountain west.

If the politics of existing avionics hadn't driven the equipage of RNP AR, that system would transition from LNAV/VNAV to GLS and much lower minimums than we see today with RNP AR.

[peekay4]

But, think if you were a fleet manager at say, DAL or AAL, where Boeing wants a million dollars per airplane in your 150 bird fleet to change out your FMS and related gear to give you WAAS/LAAS and GLS auto-land capability.
Well, DAL just performed their first GLS approach (http://www.fly2houston.com/0/3922179/0/83280D83283/) into Houston a couple of weeks ago (December 1). They already have 34 GLS-capable B737s, out of a total of 112 GLS-capable B737s on order. According to the FAA, DAL is also considering GLS for 45 A321 future deliveries.

AAL will have GLS on all of their B787s on order (GLS is a standard feature on new 787s).

From an economics perspective, these new technologies will allow more fuel-efficient operations at higher traffic densities.

Not to mention, the FAA currently spends $100 million each year for ILS maintenance. It would be a big win if this number can be cut in half through decommissioning. Maybe keep one ILS per airport for backup (as opposed to one per runway end), in addition to the CAT II/III ones.

[Denti]

I do expect to see CAT III ILS around for quite a long time. Regulatory progress is extremely slow. We have done GLS autoland trials five years ago with excellent results, however there is no apparent movement to allow lower than CAT I minima in europe. Even though we have been certified for operational use of GLS since 2009 there was only one airport in my country with an operational GLS until a few months ago, when FRA introduced the second GLS station and GLS approaches to all landing runways.

Getting approval was helped by the fact that boeing essentialy offered us GLS free of charge on all 737s since 2006. Sadly a retrofit on our A320 fleet would cost around a quarter million per aircraft which makes it economically unfeasible. Since we are now phasing out the 737 in favor of A320s we will lose our GLS capability. If we (or our on this site unmentionable major shareholder) orders new Airbii it might be included.

[aterpster]

AAL will have GLS on all of their B787s on order (GLS is a standard feature on new 787s).

Didn't take Boeing very long. :)

[peekay4]

Don't worry...

FAA FY2015 budget: $15 billion.

DoD FY2015 budget: $560 billion. Cost of satellite upgrades amortized over service life: $366 million per year.

I think the DoD can afford it. :E

As a comparison the FAA spends ~ $220 million a year to maintain "legacy" navaids (VOR, NDB, ILS, etc.).

[underfire]

GBAS appears to be a no cost option on both A and B.The benefits are immense, cost is low, I cannot understand why it is not on every ac and installed at virtually every airport.
Something just doesn't make sense here.

[beech35]

I believe the FAA is still committed to decommission the vast majority of VORs by 2020. A huge number of existing ILS procedures must be revised as a result. I wouldn't be surprised if many of the ILS procedures will be retired along with the VORs.

I have sat thru at least four of the MON presentations, the most recent one was this October. They do not plan to eliminate the vast majority of VOR's, at best it will be less than 50% and the Western third of the country, Alaska, and Hawaii will be untouched. There are also several VOR systems that will remain in place because of international agreements. I have asked the question regarding ILS and these systems are not in the plan for removal, but there are changes going to be needed to support them, including using GPS for joining the ILS and installing DME to replace fixes that were once done using locators and VOR radials. A good example is my airport. The ILS was split into two procedures, one which requires GPS and the other which requires DME. The DME is newly installed. See ILS or LOC Y RWY 2 and the Z variation at KUZA.

As part of the MON, the FAA will provide at least one "safe" ILS procedure without any dependency on DME, GPS, or Radar wihtin 100 NM of any place in the NAS where the MON is removing VOR's.

Finally, removing VOR's is going to be a long process and undoubtedly get very political before it is over. Loss of ground based Navaids for approaches will generate a lot of squealing.

[peekay4]

As part of the MON, the FAA will provide at least one "safe" ILS procedure without any dependency on DME, GPS, or Radar wihtin 100 NM of any place in the NAS where the MON is removing VOR's.
Actually I believe the intent is to have a non-GPS approach within 100 NM. This includes not only ILS approaches but also LOC and yes even VOR approaches.

Anyway, think of of VOR MON as "Phase I" in the overall VOR decommissioning process.

MON will reduce the number of VORs by up to 50%, as mentioned. The timing keeps on slipping, but let's say this is completed by 2030 for discussion's sake.

But what happens after MON? VOR decommissioning won't stop!

MON is a required "stepping stone" because we need to provide backup to GPS/GNSS in case of a global or local outage (e.g., interference, jamming, etc.) But MON cannot meet "NextGen" level of performance required for PBN, so the FAA, partners & industry are working on an alternative navigation system (APNT: "Alternate Position, Navigation, Timing").

APNT will likely based on a network of DMEs. That is, improving the tech behind today's DME/DME/IRU RNAV, so even if all GPS signals are lost, enroute RNAV can still be maintained to PBN requirements (e.g., RNP 0.3).

For this to happen, the existing DME network has to be enhanced to provide better accuracy and/or augmented with "pseudo-satellite" signals from ground-based transmitters (GBTs). Think of GPS signals sent via ground antennas instead of from space.

(That is why we never hear of DME decommissioning -- the FAA has big plans for them).

The idea is to have APNT up and running by the end of MON (in our discussion, 2030). Then Phase II can start: most of the remaining VORs, except few critical ones, can then be dismantled in favor of APNT.

(By the way the FAA is currently aiming to have APNT fully operational by 2025).

[hawk37]

The point is to reduce minimums when safe practices allow it.

Examples:

1. FAA OpSpec C073 VNAV MDA as DA:

"The certificate holder is authorized to use minimum descent altitude (MDA) as a decision altitude (DA)/decision height (DH) with vertical navigation (VNAV) on a Nonprecision Approach (NPA)."

8900.183 - OpSpec/MSpec/LOA C073, Vertical Navigation (VNAV) Instrument Approach Procedure (IAP) Using Minimum Descent Altitude (MDA) as a Decision Altitude DA)/Decision Height (DH) ? Document Information (http://www.faa.gov/regulations_policies/orders_notices/index.cfm/go/document.information/documentID/1019907)

2. Transport Canada Special Exemption from 602.128(2)(b)

"The purpose of this exemption is to permit pilots-in-command of IFR aircraft operated by holders of an air operator certificate or a temporary private operator certificate to descend below the minimum descent altitude (MDA), when conducting a non-precision approach ... following a stabilized constant descent angle (SCDA) non-precision approach."

EXEMPTION FROM PARAGRAPH 602.128(2)(b) OF THE CANADIAN AVIATION REGULATIONS - Transport Canada (http://www.tc.gc.ca/CivilAviation/Regserv/Affairs/exemptions/docs/en/2509.htm)

(SCDA is the Canadian term for CDFA).

Peekay, the link says the Transport Canada exemption was over in 2015. I tried to do a search with Transport Canada, to see if it was re issued but came up empty. Do you or anyone else have any further input on exemptions?

thanks,

Hawk

[Jet Jockey A4]

Peekay, the link says the Transport Canada exemption was over in 2015. I tried to do a search with Transport Canada, to see if it was re issued but came up empty. Do you or anyone else have any further input on exemptions?

thanks,

Hawk

This may help you...

I remember seeing the extension to this exemption several years back and I cannot recall at this time if it is on an annual basis that TC renews it.

However, I can definitely tell you it is still in force because it is part of our OPs Manual and SOPs and TC would have advised us if the exemption had ended.

FYI, this exemption is only good while operating in Canada.

[hawk37]

Thanks Jet Jockey, I found the current Canadian exemption here

https://www2.tc.gc.ca/civilaviation/regserv/affairs/exemptions/docs/en/3278.htm

As you say, it appears to be re issued on an annual basis. Some initial and recurrent training required, ground school and in sim/aircraft, and most non prec approaches qualify.

For the USA operations it requires an Ops spec, M spec, or for Part 91 an LOA. C073 is the designation, info is here

https://fsims.faa.gov/PICResults.aspx?mode=EBookContents&restricttocategory=all~menu

And now navigate to Volume 3, Chapter 18, Section 5, Paragraph 3-871, sub-paragraph “OPSPEC/MSPEC/LOA C073.

Note that for US ops, VNAV to a dh vice an MDA is not necessarily permitted for all Non precision approaches, read the requirements closely

Hawk