Date: 201907
Local time of day: 1201-1800
Location: MROC.Airport, FO
Aircraft: A320
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Descent
Aircraft component: Navigation Database
Component problem: Malfunctioning
Reporter organization: Air Carrier
Reporter function: Captain; Pilot Not Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP); Flight Crew Multiengine; Flight Crew Instrument
Second reporter function: Pilot Flying; First Officer
Anomaly: Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew Overcame Equipment Problem
Contributing factors: Aircraft; Chart Or Publication; Procedure
Primary problem: Ambiguous

Narrative: We were required to fly the depicted visual approach to Runway 25. Airport information pages in our EFB direct us to load and fly the Runway 25 RNAV-A Approach. This approach is no longer in the onboard database; leaving crews with minimal guidance for arrival. The approach was accidentally left out of the database when it was recently updated. Someone needs to review the databases for accuracy; prior to issuance.


Second narrative: During cruise; as I was preparing for our arrival into MROC; I noticed that the specified approach was not in the database. MROC was landing west; visual circle to land approaches to RWY 25. The aircraft was not RNP certified; so we were going to be required to fly either the ILS or VOR RWY 07; circle to land RWY 25 using the CYRUS 2 RNAV visual with the RNAV-A selected from the database. The Captain had just been to MROC a week prior and had done this exact approach. We reviewed everything multiple times; and were unable to find the correct database selection to perform this circle to land. RNAV-A as stated in the setup procedures did not exist. I decided that in the interest of safety; it was in our best interest for the Captain to fly the visual since he had just been there the week before. He built a lateral path; using the fixes as specified on the Jepp Chart 19-1; the Visual Approach for RWY 25; as the weather conditions were above the minimums for this visual approach. We landed uneventfully. After shutdown at the gate; we swapped the databases to the old dates to see if the RNAV-A was there. It was; just as specified in the charts. We swapped back to the current database and it was missing. It's very clear; either this database is corrupted; or Jep accidentally deleted the procedure from the database. This is an immediate hazard to crews flying into MROC! Our task loading was severely stressed as we attempted to diagnose why this procedure was not showing up for us when the Captain had just used it a week prior (old database cycle); we were lucky we started preparing so early; which gave us time to work through it; giving ourselves the opportunity to deal with this at altitude prior to descent and approach. A crew that perhaps waited until later in their phase of flight would absolutely be put into a more stressful situation. This is a somewhat complex procedure considering terrain; language and use of the secondary flight plan.


Synopsis: A320 flight crew reported the MROC RNAV-A arrival chart was missing from the aircraft's navigation database.