If I read this correctly, because this gauge is capable of 1 feature, regardless how bad or good the others are, it is then supposed to be “the most complex avionics in any sim”.
In taking the comparaison with the NXi and PMDG/FSLabs/Tolis, the above is like saying:
“Compared to the space shuttle [PMDG+FSLabs+Tolis], Tesla [NXi] is the most sophisticated vehicle [Avionics] man can ever pilot [in any sim], only because it has an autopilot for hands free driving on the road, which is something the space shuttle doesn’t have”
Notwithstanding the RNP/AR capabilities of the NXi:
- What is the accuracy of its GPWS?
- Is the TCAS passing the industry standard 250 TSIM tests like the RXP? (Which is RXP code and not Garmin just to make this clear)
- Is it capable of RAIM checks?
- Does it also has the authentic Garmin navigation bugs and other navigation and flight plan sequencing specifics capabilities? (1)
I might be wrong of course, but I’m lacking the words to explain what I think about the claim that a single NXi gauge, even if it has a fully working 1:1 RNP/AR feature, is the most sophisticated piece of avionics when comparing with a complete and highly authentic simulation of an entire Boeing or Airbus computer systems and avionics, like they are implemented by PMDG, FSLabs and Tolis to name a few.
And on the RNP/AR specifically, you might want to read this too (2):
https://www.avsim.com/forums/topic/570395-kpsp-no-rnav-approaches/
RNAV (GPS) approaches can use the curved path RF leg type, but you won’t find any of these in the existing WAAS GPS databases as none of the Garmin panel mount GPS units support the RF leg in their AFMS. They have the software to perform the RF leg type, but until the FAA approves the use these legs with the GPS for part 91 operations, Garmin can’t include them in the database. At that point, Garmin would have to update the software to enable the RF leg to be used and issue a new AFMS to go with the ability.
The poster child is the RNAV (GPS) X RWY 24 at KCRQ. You can find the RNAV (GPS) Y RWY 24 in the database, but not the X. At one point, the Y included the RF leg, but this prevented the procedure from being in the database, so the X was added that just has the RF leg feeder route and it was removed from the Y so it could be put back in the database.
Garmin did a white paper on the subject of flying the RF leg and demonstrated that with a minimum of training that it could be flown by pilots with all levels of experience.
Those procedures are RNAV (RNP) AR or authorization required approaches. Unless the aircraft is certificated for RNP AR, which the GTN alone would not be, the approaches are required to be excluded from the database. Further, RNP AR approaches are subjected to additional database scrutiny and validation testing. That usually requires a separate, RNP AR qualified database with all the RNP AR approaches included for the coverage area.
If you want to know more, Google “FAA AC 90-101A”.
Rich Boll
Wichita KS
(1) yes there are also bugs and actually, thanks to the RXP solution, and astute customers, we’ve helped Garmin identifying a real bug affecting the real Garmin GTN with potential hazardous outcome in the real world…
(2) you can enable support for RF legs in the Reality XP GTN in the AFMS settings, like you’d do at the FBO with the real unit… It just needs the approach to be in the database.