37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 980424 |
Time | |
Date | 201111 |
Local Time Of Day | 1201-1800 |
Place | |
Locale Reference | ZSE.ARTCC |
State Reference | WA |
Environment | |
Flight Conditions | VMC |
Light | Daylight |
Aircraft 1 | |
Make Model Name | Commercial Fixed Wing |
Operating Under FAR Part | Part 121 |
Flight Phase | Descent |
Route In Use | Direct |
Flight Plan | IFR |
Component | |
Aircraft Component | FMS/FMC |
Person 1 | |
Function | Captain Pilot Not Flying |
Qualification | Flight Crew Air Transport Pilot (ATP) |
Experience | Flight Crew Last 90 Days 185 Flight Crew Total 9170 Flight Crew Type 3620 |
Events | |
Anomaly | Deviation - Procedural Published Material / Policy |
Narrative:
Incorrect database selected. [We were] unable to accept RNAV arrival. The FMS database that expired mid november was 'enabled' in the FMS. This database did not contain the arrival airport's RNAV arrival. Although we were not filed via the RNAV arrival; sea center assigned an RNAV. I had checked earlier to see if the RNAV was in the database; anticipating the RNAV arrival assignment. I informed sea center that we were 'unable' as the FMS did not contain the RNAV arrival. I checked to see if the database was current. This is when I discovered the 'selected' database had expired. Accordingly; it is critical to verify that the FMS database is current and will not expire during flight during preflight preparations. I attempted to 'swap' the expired database with the current database; but this is not possible in flight. Center inquired if we had the paper chart for the RNAV arrival and what the effective date was. I informed sea center that the commercial chart was dated early 2011. Center stated that there was a new version available with a more recent revision date. I believe center was looking at the NOAA RNAV arrival. Center asked if we could proceed direct to the intersection. After verifying the FMS contained the intersection; center cleared us to the intersection and told us to expect to cross at 10;000 ft MSL at 250 KTS. The rest of the flight was uneventful.
Original NASA ASRS Text
Title: A pilot discovered in flight that the aircraft's FMS database was out of date; did not contain the RNAV arrival and the current database could not be selected in flight.
Narrative: Incorrect Database Selected. [We were] unable to accept RNAV Arrival. The FMS database that expired mid November was 'enabled' in the FMS. This database did not contain the arrival airport's RNAV Arrival. Although we were not filed via the RNAV arrival; SEA Center assigned an RNAV. I had checked earlier to see if the RNAV was in the database; anticipating the RNAV Arrival assignment. I informed SEA Center that we were 'unable' as the FMS did not contain the RNAV Arrival. I checked to see if the database was current. This is when I discovered the 'selected' database had expired. Accordingly; it is critical to verify that the FMS Database is current and will not expire during flight during preflight preparations. I attempted to 'swap' the expired database with the current database; but this is not possible in flight. Center inquired if we had the paper chart for the RNAV Arrival and what the effective date was. I informed SEA Center that the Commercial Chart was dated early 2011. Center stated that there was a new version available with a more recent revision date. I believe Center was looking at the NOAA RNAV Arrival. Center asked if we could proceed direct to the intersection. After verifying the FMS contained the intersection; Center cleared us to the intersection and told us to expect to cross at 10;000 FT MSL at 250 KTS. The rest of the flight was uneventful.
Data retrieved from NASA's ASRS site as of April 2012 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.