 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
On short final for runway 20R at sna the flight crew of a challenger was surprised by a raas announcement of 'approaching 19R.' the runway number had been altered and; apparently; the raas database had not yet been updated.
| Attributes | |
| ACN | 1238291 |
| Time | |
| Date | 201502 |
| Local Time Of Day | 1201-1800 |
| Place | |
| Locale Reference | SNA.Airport |
| State Reference | CA |
| Environment | |
| Flight Conditions | VMC |
| Light | Daylight |
| Aircraft 1 | |
| Make Model Name | Challenger 300 |
| Operating Under FAR Part | Part 135 |
| Flight Phase | Initial Approach |
| Route In Use | Visual Approach |
| Flight Plan | IFR |
| Component | |
| Aircraft Component | Navigation Database |
| Person 1 | |
| Function | First Officer Pilot Not Flying |
| Qualification | Flight Crew Air Transport Pilot (ATP) |
| Events | |
| Anomaly | Aircraft Equipment Problem Less Severe |
Narrative:
We had previously planned and briefed a visual approach to runway 20R at sna. The ILS was set for a backup to the visual approach. We visually identified the airport; reported that to socal approach and were cleared for a visual approach to runway 20R. On final approach; the runway awareness advisory system (raas) announced 'approaching runway 19R'. We confirmed that we were properly established for the correct airport/runway and continued to a normal landing.apparently the runways were renumbered sometime during the second half of 2014. Either the raas database is not up to date or the latest database is not installed in the aircraft.the announcement of the incorrect runway presented a distraction during a critical phase of flight in busy airspace.1) add an ops note for raas equipped aircraft that the database may not be correct for runway 20L/right at sna.2) find out if the raas database has the correct runway numbering for sna.3) see of the airplane has the correct raas database in it.
Original NASA ASRS Text
Title: On short final for Runway 20R at SNA the flight crew of a Challenger was surprised by a RAAS announcement of 'approaching 19R.' The runway number had been altered and; apparently; the RAAS database had not yet been updated.
Narrative: We had previously planned and briefed a visual approach to runway 20R at SNA. The ILS was set for a backup to the visual approach. We visually identified the airport; reported that to Socal approach and were cleared for a visual approach to runway 20R. On final approach; the Runway Awareness Advisory System (RAAS) announced 'Approaching runway 19R'. We confirmed that we were properly established for the correct airport/runway and continued to a normal landing.Apparently the runways were renumbered sometime during the second half of 2014. Either the RAAS database is not up to date or the latest database is not installed in the aircraft.The announcement of the incorrect runway presented a distraction during a critical phase of flight in busy airspace.1) Add an ops note for RAAS equipped aircraft that the database may not be correct for runway 20L/R at SNA.2) Find out if the RAAS database has the correct runway numbering for SNA.3) See of the airplane has the correct RAAS database in it.
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.