Date: 201502
Local time of day: 1201-1800
Location: ZHN.ARTCC, HI
Flight conditions: VMC
Aircraft: B737 Undifferentiated or Other Model
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Cruise
Airspace: Class A ZHN
ATC / advisory: Center ZHN
Aircraft component: Navigation Database
Component problem: Improperly Operated
Reporter organization: Air Carrier
Reporter function: Pilot Not Flying; First Officer
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Human factors: Troubleshooting; Human-Machine Interface; Confusion
Second reporter function: Pilot Flying; Captain
Anomaly: ATC Issue All Types; Aircraft Equipment Problem Less Severe; Deviation / Discrepancy - Procedural FAR; Deviation / Discrepancy - Procedural Maintenance; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Flight Crew
When detected: In-flight
Result: Air Traffic Control Provided Assistance; Flight Crew Became Reoriented; Flight Crew FLC Overrode Automation
Contributing factors: Incorrect / Not Installed / Unavailable Part; Procedure; Aircraft
Primary problem: Incorrect / Not Installed / Unavailable Part

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.


Second narrative: Attempts to load arrival STAR and approach in FMC unsuccessful. No data for any Hawaii airport; except runway threshold; available for selection. Flew arrival procedures to Airport Kona using raw data only. Made logbook entry upon arrival and briefed maintenance. ACARS info message sent to company maintenance prior to landing. Notified next day that Airbus Navigation Data was loaded in aircraft by mistake by maintenance.


Synopsis: 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.