Scribd
Upload
68 views

Case Study RNAV PBN MDW Database 1 1

1) A pilot was using an RNAV (GPS) approach in an aircraft equipped with Universal FMS units that had WAAS capability. However, the LP approach did not show up on the FMS navigation page and could not be armed, even though it was loaded correctly. 2) The FMS manufacturer did not recertify the units for LP approaches, which came out after certification, but still included them in the database. These were labeled with an (a) to designate them as "advisory." 3) Pilots may have no way of knowing the operational limitations of approaches in their FMS database until attempting to arm one for flight. This could lead to issues in low visibility conditions.

Uploaded by

Tony Nicholas
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
68 views

Case Study RNAV PBN MDW Database 1 1

1) A pilot was using an RNAV (GPS) approach in an aircraft equipped with Universal FMS units that had WAAS capability. However, the LP approach did not show up on the FMS navigation page and could not be armed, even though it was loaded correctly. 2) The FMS manufacturer did not recertify the units for LP approaches, which came out after certification, but still included them in the database. These were labeled with an (a) to designate them as "advisory." 3) Pilots may have no way of knowing the operational limitations of approaches in their FMS database until attempting to arm one for flight. This could lead to issues in low visibility conditions.

Uploaded by

Tony Nicholas
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 2

Case Study

FMS DATABASE TRAP

M
DW was using one of the new RNAV GPS
approaches, RNAV (GPS) Z RWY 22L, an LP
[Localizer Performance (without Vertical
Guidance)] non-precision approach to an
MDA. As our aircraft has a pair of relatively new
Universal 1FW FMSs with WAAS, we loaded up the
approach and verified its presence on the FLTPLAN
page.
The problem was that, although correctly loaded, the
approach did not show up in the FMS on the NAV page
1. We were not able to arm or activate it! Lucky for us,
it was Day VFR and we ended up being assigned traffic
Author’s Conclusions
to follow and it became a non-event.
It is the ASRS author’s understanding that the decision
Working to figure out what happened, we discovered
to not recertify FMS systems to provide LP capability is
that even though our FMS is WAAS certified, LP
not unique to the manufacturer of the system in his
approaches began to be published after it was certified.
aircraft. He has become aware of at least one other
Universal did not want to do the paperwork to recertify it
manufacturer with the same issue.
for these approaches, but included them in the database
anyway, although they could not be armed and flown.
Additionally, he observed that he received no
They excused this by labeling them with an (a) notification or training from his company, the FMS
[appended to the left of the approach designator in the manufacturer, or the FAA alerting him to the
FMS "list of approaches"]. This (a) designated them as dysfunctional nature of data available to him and, most
an “advisory or advanced” approach. This status allows likely, other users.
selection and display of LP approaches even though the
crew is unable to arm and activate them. Our FMS is not He further concludes that, unless pilots are very familiar
certified for these LP approaches although it is WAAS with the operating limitations and performance of their
certified for LPV approaches. specific FMS and related avionics, they would have no
obvious means of determining their performance
Note: This narrative is an edited version of a filed
capability shortfall until attempting to arm the approach
ASRS from April, 2014.
mode to fly a similar approach and, only then late in the
arrival, discovering approach mode functions not
available.
..............................................................
Notes:
________________________________________________________________________________________
________________________________________________________________________________________
________________________________________________________________________________________
http://asrs.arc.nasa.gov/docs/rpsts/rnav_arrival.pdf
FMS Database Trap  

1
 

Questions for Reflection

1 Imagine that you were the PIC of this flight, and the
same situation happened to you except that you are
IMC with a ceiling just above the published MDA
for this approach. What actions would you take?

2 Could this situation happen to you at your current


company in the equipment you are flying now? If
No, why not? If Yes, what should be done to change
that?

Notes:
________________________________________________________________________________________
________________________________________________________________________________________
________________________________________________________________________________________
http://asrs.arc.nasa.gov/docs/rpsts/rnav_arrival.pdf
FMS Database Trap  

2
 

You might also like