A B737 air crew discovered that they were unable to bring up the required STAR and approaches in FMC...

Narrative:

I was copilot on flight ZZZ [mainland] to kona. During preflight; the FMC routing was datalink loaded. The flight pub bag and FMC database were checked to be current. After uploading the winds; the runway and departure were loaded along with the runway in kona. I did not load the arrival into kona as I was taught adding the arrival will likely add distance to the flight and could potentially create fuel issues at the critical point. After passing the critical point I attempted to load the arrival and approach for kona. However; we noticed that there were no arrivals or approaches available to load; only the runway. Further investigation found that there were no departures; arrivals; or approaches in the FMC for any hawaii airport. We continued raw data on arrival and flew an uneventful ILS approach into kona. We wrote a maintenance discrepancy in the logbook; notified maintenance via ACARS; and debriefed the mechanic upon arrival into kona.today (18 days later); the captain was informed that the aircraft was loaded with an airbus navigation database and that is what accounted for the lack of coverage for hawaii. I don't know how I would have caught this on preflight; or how long this plane had been flying with the wrong database.FYI; I had the same experience on airport ZZZ2 to ZZZ3 [also hawaii] (8 days ago). Again we flew raw data on the arrival and ILS approach for an uneventful landing. We wrote up the discrepancy and thoroughly debriefed maintenance upon arrival into ZZZ3. I never found out what the problem was but I suspect it was the same issue. I remember looking in the logbook of this plane and noted that it had not been out to hawaii for at least a couple weeks.

Original NASA ASRS Text

Title: A B737 air crew discovered that they were unable to bring up the required STAR and approaches in FMC. They were later notified that incorrect Airbus data had been loaded in the aircraft by mistake.

Narrative: I was copilot on flight ZZZ [mainland] to Kona. During preflight; the FMC routing was datalink loaded. The flight pub bag and FMC database were checked to be current. After uploading the winds; the runway and departure were loaded along with the runway in Kona. I did not load the arrival into Kona as I was taught adding the arrival will likely add distance to the flight and could potentially create fuel issues at the critical point. After passing the critical point I attempted to load the arrival and approach for Kona. However; we noticed that there were no arrivals or approaches available to load; only the runway. Further investigation found that there were no departures; arrivals; or approaches in the FMC for any Hawaii airport. We continued raw data on arrival and flew an uneventful ILS approach into Kona. We wrote a maintenance discrepancy in the logbook; notified maintenance via ACARS; and debriefed the mechanic upon arrival into Kona.Today (18 days later); the captain was informed that the aircraft was loaded with an Airbus navigation database and that is what accounted for the lack of coverage for Hawaii. I don't know how I would have caught this on preflight; or how long this plane had been flying with the wrong database.FYI; I had the same experience on Airport ZZZ2 to ZZZ3 [also Hawaii] (8 days ago). Again we flew raw data on the arrival and ILS approach for an uneventful landing. We wrote up the discrepancy and thoroughly debriefed maintenance upon arrival into ZZZ3. I never found out what the problem was but I suspect it was the same issue. I remember looking in the logbook of this plane and noted that it had not been out to Hawaii for at least a couple weeks.

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.

Attributes
ACN	1241022
Time
Date	201502
Local Time Of Day	1201-1800
Place
Locale Reference	ZHN.ARTCC
State Reference	HI
Environment
Flight Conditions	VMC
Aircraft 1
Make Model Name	B737 Undifferentiated or Other Model
Operating Under FAR Part	Part 121
Flight Phase	Cruise
Route In Use	Oceanic
Flight Plan	IFR
Component
Aircraft Component	Navigation Database
Person 1
Function	Pilot Not Flying First Officer
Qualification	Flight Crew Air Transport Pilot (ATP)
Experience	Flight Crew Last 90 Days 150 Flight Crew Total 6000 Flight Crew Type 400
Person 2
Function	Pilot Flying Captain
Experience	Flight Crew Last 90 Days 161 Flight Crew Type 161
Events
Anomaly	ATC Issue All Types Aircraft Equipment Problem Less Severe Deviation - Procedural FAR Deviation - Procedural Maintenance Deviation - Procedural Published Material / Policy

A B737 air crew discovered that they were unable to bring up the required STAR and approaches in FMC. They were later notified that incorrect airbus data had been loaded in the aircraft by mistake.