Narrative:

Upon inputting flight plan FMS would not recognize rst; checked data base date and was up to date. Swapped data base still no rst; swapped back to current database and called maintenance. FMS maintenance looked at it and notified database personnel that is was not in there and said it would have to be fixed in next update and they could not do anything at that time. I checked the fom which states: do not write up nav data errors; report errors to ....etc. I checked our charts in efb which were up to date; both ILS approaches were available and rst VOR was in database and wx was good. Talked about having to manually tune ILS and no LNAV for missed approach. First officer said he was ok but I feel I may have not opened up the conversation enough to his full thought. After landing in rst notified maintenance. After arriving at hotel; I started to email nav data base personnel about error and researched the fom a little more and realized I had not checked the aircraft specific data base which is where the error was; which I confirmed with write up by maintenance in aml [wrong aircraft type database loaded]. In hindsight I should have taken more time in researching problem and used better CRM by giving the first officer more opportunity to get his thoughts. My failure to thoroughly research the problem and to make aml write up.

Related reports:

Google
 

Original NASA ASRS Text

Title: Air Carrier Captain reported discovering that the FMC database does not contain approaches for the destination airport; although the database appears to be current. The EFB contains the necessary approaches and the flight departs without a logbook write-up in compliance with FOM procedures for database errors. Maintenance discovers that the database loaded was for a different fleet type that does not operate into this airport.

Narrative: Upon inputting flight plan FMS would not recognize RST; checked data base date and was up to date. Swapped data base still no RST; swapped back to current database and called maintenance. FMS Maintenance looked at it and notified database personnel that is was not in there and said it would have to be fixed in next update and they could not do anything at that time. I checked the FOM which states: do not write up nav data errors; report errors to ....etc. I checked our charts in EFB which were up to date; both ILS approaches were available and RST VOR was in database and Wx was good. Talked about having to manually tune ILS and no LNAV for missed approach. FO said he was OK but I feel I may have not opened up the conversation enough to his full thought. After landing in RST notified maintenance. After arriving at hotel; I started to email nav data base personnel about error and researched the FOM a little more and realized I had not checked the aircraft specific data base which is where the error was; which I confirmed with write up by maintenance in AML [wrong aircraft type database loaded]. In hindsight I should have taken more time in researching problem and used better CRM by giving the FO more opportunity to get his thoughts. My failure to thoroughly research the problem and to make AML write up.

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.