37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 1519732 |
Time | |
Date | 201802 |
Local Time Of Day | 0601-1200 |
Place | |
Locale Reference | VRB.Airport |
State Reference | FL |
Environment | |
Flight Conditions | VMC |
Light | Daylight |
Aircraft 1 | |
Make Model Name | Citation Excel (C560XL) |
Flight Phase | Initial Approach |
Flight Plan | IFR |
Component | |
Aircraft Component | Data Processing |
Person 1 | |
Function | First Officer Pilot Flying |
Qualification | Flight Crew Air Transport Pilot (ATP) |
Events | |
Anomaly | Aircraft Equipment Problem Critical Deviation - Procedural Clearance Deviation - Procedural Published Material / Policy Deviation - Track / Heading All Types |
Narrative:
The universal FMS 1 database expires on 1 march. GPS 12R approach to vero beach turned the aircraft to line up on a non-existent runway 12 at fort pierce airport (fpr). I had been cleared for a visual approach to runway 12R at vero beach (vrb) in clear weather conditions while approximately 12 miles southwest of vrb and 3 miles southwest of fort pierce (fpr) with both airports in sight. Because I was unfamiliar with vrb; I had briefed a visual backed up with the GPS 12R; and was using the autopilot to intercept the GPS course from an extended right base. I expressed surprise to the pilot monitoring that vrb was actually the closer airport as the autopilot turned us towards that airport (fpr). Simultaneously we realized it couldn't be correct and the ATC controller queried our turn. The pilot monitoring confirmed that the FMS was programmed to fly the GPS 12R to vrb; but it was taking us to the wrong airport. I stopped our descent and was turning back to our original course and ATC canceled our approach clearance and issued a heading correction to the right base at vrb all at approximately the same time. From that point I ignored the navigation information from the FMS and flew an uneventful visual approach to vrb. On short final the FMS navigation corrected itself and provided guidance to the correct airport. Our pilots should be warned that this database might try to align the aircraft with the wrong airport when the vrb GPS12R approach is selected in close proximity to fpr. Consider advising the database provider of the problem. No known satellite outages or raim warnings were in effect.
Original NASA ASRS Text
Title: CE560XL pilot reported encountering a navigational error in the company's FMS database and recommend that the vendor providing FMS database be notified of the problem.
Narrative: The universal FMS 1 database expires on 1 March. GPS 12R approach to Vero Beach turned the aircraft to line up on a non-existent runway 12 at Fort Pierce airport (FPR). I had been cleared for a visual approach to runway 12R at Vero Beach (VRB) in clear weather conditions while approximately 12 miles southwest of VRB and 3 miles southwest of Fort Pierce (FPR) with both airports in sight. Because I was unfamiliar with VRB; I had briefed a visual backed up with the GPS 12R; and was using the autopilot to intercept the GPS course from an extended right base. I expressed surprise to the pilot monitoring that VRB was actually the closer airport as the autopilot turned us towards that airport (FPR). Simultaneously we realized it couldn't be correct and the ATC controller queried our turn. The pilot monitoring confirmed that the FMS was programmed to fly the GPS 12R to VRB; but it was taking us to the wrong airport. I stopped our descent and was turning back to our original course and ATC canceled our approach clearance and issued a heading correction to the right base at VRB all at approximately the same time. From that point I ignored the navigation information from the FMS and flew an uneventful visual approach to VRB. On short final the FMS navigation corrected itself and provided guidance to the correct airport. Our pilots should be warned that this database might try to align the aircraft with the wrong airport when the VRB GPS12R approach is selected in close proximity to FPR. Consider advising the database provider of the problem. No known satellite outages or RAIM warnings were in effect.
Data retrieved from NASA's ASRS site and automatically converted to unabbreviated mixed upper/lowercase text. This report is for informational purposes with no guarantee of accuracy. See NASA's ASRS site for official report.