Follow along with the video below to see how to install our site as a web app on your home screen.
Note: This feature may not be available in some browsers.
WW24dude said:Another great discussion (one of few on this board!!). RNAV A and B is not just a problem at the big airports. Take a look at Rifle, CO, a primary divert for Aspen when the weather goes down cause they have an ILS, 7000' runway and it's an easy drive to ASE. EVERY DP is now an RNAV Type B DP!
Look at the back of the Jepps 10-9. You have an Obstacle Departure proceedure for RW 8, but what about RW26? It says to fly the RNAV SID??? WTFO? If you have greater than 10 knots down RW 26 I don't see how you can leagally get out of RIL unless you have a box that can fly these Type A and B DPs? (if it's IFR of course) OBTW field elev is 5500' and ATC (DEN Center) has radar coverage down to about 9000' MSL. So you can't take radar vectors.
I'm frustrated that on any obstacle DP they would tell you to fly an RNAV proceedure. It's like the FAA is not talking to ATC and they aren't talking to us....
Am I wrong? Hopefully this will get us a new box!
ww24dude
Capthuff said:501261,Great explanation,Thanks
Lead Sled said:I agree, excellent post.'Sled
Why thank you, I must have stayed at a Holiday Inn Express last night .SabreFlyR said:That's the best explaination I've seen yet.
GravityHater said:The whole thing is really messed up, and they do not realize it.
Have a look at the Lisse6 into hobby. Not listed as an Rnav arrival at all, BUT you accept it then read the fine print... PART of the route is only for use by RNP2.0 equipped aircraft ONLY. (see the note)
AND many have said the GNS XLS should not do an rnav A or B arrival --- well ours has them! But no where does it give an RNP value and the company's head tech tells me in an email that the GNS XLS is not an RNP-capable navigator... so we can't legally do them.... even if they are right there in the box. &$##&$ Ours navigates them just fine, what the H is up with that?
http://www.naco.faa.gov/d-tpp/0511/00198LISSE.PDFGravityHater said:The whole thing is really messed up, and they do not realize it.
Have a look at the Lisse6 into hobby. Not listed as an Rnav arrival at all, BUT you accept it then read the fine print... PART of the route is only for use by RNP2.0 equipped aircraft ONLY. (see the note)
AND many have said the GNS XLS should not do an rnav A or B arrival --- well ours has them! But no where does it give an RNP value and the company's head tech tells me in an email that the GNS XLS is not an RNP-capable navigator... so we can't legally do them.... even if they are right there in the box. &$##&$ Ours navigates them just fine, what the H is up with that?
You must have INS/DME FMS(/E), DME/GPS FMS(/F), GPS(/G) or be /R, which is RNP and able to fly the Required Navigation Performance of 2.0 nm. If you are not opspec or AFM approved RNP, you don't have to worry about the RNP 2.0 thing. If you want to be safe though, you may want to make sure your GPS or FMS scales the CDI sensitivity down from enroute (5.0 nm fullscale) to terminal (1.0 nm). I'm not sure if there are FMSes or GPSes that have a 2.0 nm sensitivity setting, but you may be able to do that manually. I would be willing to bet that if your FMS has this procedure in the database, it will go automatically to terminal sensitivity, just like it will go to approach sensitivity (0.3 nm) at 2 nm outside the FAF on an RNAV approach.Note: Route (SAT-SACGY) for use by E/F/G/R (RNP 2.0) equipped aircraft only.