RussR
En-Route
This is going to be a really techie question about RNAV (GPS) approaches and the GPS coding behind the scenes, regarding the advisory glideslope of an LP or LNAV approach when the "Visual Segment - obstacles" note is displayed on the chart.
@John Collins @aterpster , please help if you can.
I flew the 1F0 RNAV (GPS) RWY 17 approach the other day using a Garmin 530W. https://skyvector.com/files/tpp/2009/pdf/05399R17.PDF
It has the note "Visual segment - obstacles" in the profile view (and boy does it ever have such obstacles, trees and big poles just off your wingtip, placed there apparently just to hold red lights for the trees).
It was my understanding that when this note is on the chart, that the glidepath angle would be coded as "0.00" in the ARINC record, and this would cause the advisory glidepath to not be displayed. But when I flew it, I did in fact get an advisory glidepath.
Here is the FAS data record from the IFP Gateway:
Now, this is a sample size of 1, so even if my understanding is correct it could be an error on just this procedure.
John, Wally, anybody else knowledgeable about this type of issue?
@John Collins @aterpster , please help if you can.
I flew the 1F0 RNAV (GPS) RWY 17 approach the other day using a Garmin 530W. https://skyvector.com/files/tpp/2009/pdf/05399R17.PDF
It has the note "Visual segment - obstacles" in the profile view (and boy does it ever have such obstacles, trees and big poles just off your wingtip, placed there apparently just to hold red lights for the trees).
It was my understanding that when this note is on the chart, that the glidepath angle would be coded as "0.00" in the ARINC record, and this would cause the advisory glidepath to not be displayed. But when I flew it, I did in fact get an advisory glidepath.
Here is the FAS data record from the IFP Gateway:
Now, this is a sample size of 1, so even if my understanding is correct it could be an error on just this procedure.
John, Wally, anybody else knowledgeable about this type of issue?