Narrative:

I was the relief pilot on a flight. After returning to the flight deck from the preflight walkaround inspection I was told by the captain and first officer that there was an FMC database issue and station maintenance was already notified. Even though the active database was showing current as of [the last update] our expected approach; the ILS approach into our destination was not included. The appropriate STAR was loaded but we could not find the corresponding approach. We cycled to the expired database and back to the current one hoping that this would solve the issue. At about this time tech ops arrived and advised we needed a full system reload on both fmcs which would take about 45 minutes. This was 20 minutes prior to departure. The reload didn't solve the issue but we got a new mrd claiming the database was active and ops check ok. Unsatisfied with this answer and wondering what else might be missing from the database we wrote it up again breaking the mrd. This time an avionics specialist came out and advised it may have been an omission from jeppesen. We discussed as a crew the wisdom of taking an airplane with this FMC anomaly to south america and considered the safety implications of missing data. About this time operations decided to offer passengers an opportunity to deplane as it was nearing 2 hours past departure time. Shortly afterward we were notified by the crew desk that the flight was being delayed and we were released as we were within about 30 minutes of our cco time.

Google
 

Original NASA ASRS Text

Title: B767 Pilot reported the the FMC Database was missing the approaches to their international destination.

Narrative: I was the Relief Pilot on a flight. After returning to the flight deck from the preflight walkaround inspection I was told by the Captain and First Officer that there was an FMC database issue and station maintenance was already notified. Even though the active database was showing current as of [the last update] our expected approach; the ILS Approach into our destination was not included. The appropriate STAR was loaded but we could not find the corresponding approach. We cycled to the expired database and back to the current one hoping that this would solve the issue. At about this time Tech Ops arrived and advised we needed a full system reload on both FMCs which would take about 45 minutes. This was 20 minutes prior to departure. The reload didn't solve the issue but we got a new MRD claiming the Database was active and Ops Check OK. Unsatisfied with this answer and wondering what else might be missing from the database we wrote it up again breaking the MRD. This time an Avionics specialist came out and advised it may have been an omission from Jeppesen. We discussed as a crew the wisdom of taking an airplane with this FMC anomaly to South America and considered the safety implications of missing data. About this time Operations decided to offer passengers an opportunity to deplane as it was nearing 2 hours past departure time. Shortly afterward we were notified by the Crew Desk that the flight was being delayed and we were released as we were within about 30 minutes of our CCO time.

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.