My airport 9A1 has been waiting ~forever for an LPV approach. We got it on Thursday. However, those of us who tried it got no glideslope, and the 430/530 screen only showed LNAV. What's up with that? we wondered.
Well last night I discovered deep in the bowels of garmin.com Service Alert 0825 which advised that on ALL their in-panel, certified WAAS units airports with only 3 letter/number designators could not get vertical guidance on any approaches with an LPV. To quote Garmin in this July 22, 2008 report "Garmin has identified an issue, whereby all LPV approaches at airports with three-character identifiers will function as an LNAV-only approach."
Garmin's so called Resolution states "The ability to fly LPV and LNAV/VNAV approaches to airports with three character identifiers will be added in later software versions."
Does that stink or what? The FAA (your tax dollars) spent plenty to get this LPV approach certified and now 99% of the WAAS equipped aircraft likely to use my airport can't use the approach as intended. I sure hope that Garmin's monopoly in this market ends soon.
Rant off.
Well last night I discovered deep in the bowels of garmin.com Service Alert 0825 which advised that on ALL their in-panel, certified WAAS units airports with only 3 letter/number designators could not get vertical guidance on any approaches with an LPV. To quote Garmin in this July 22, 2008 report "Garmin has identified an issue, whereby all LPV approaches at airports with three-character identifiers will function as an LNAV-only approach."
Garmin's so called Resolution states "The ability to fly LPV and LNAV/VNAV approaches to airports with three character identifiers will be added in later software versions."
Does that stink or what? The FAA (your tax dollars) spent plenty to get this LPV approach certified and now 99% of the WAAS equipped aircraft likely to use my airport can't use the approach as intended. I sure hope that Garmin's monopoly in this market ends soon.
Rant off.