Narrative:

Departing from lax late there was some confusion regarding the FMC database vs the jeppesen. According to the aircraft operating manual (aom) the FMC database is good until the morning after the expiration date of the database. The problem is the electronic flight bag (efb) jeppfd-pro application automatically changes to the new update at the time of the FMC expiration date. We were cleared via controller pilot data link communications (cpdlc) for the OSHNN6 SID but the efbs had already swapped over to the OSHNN7. I recognize this problem every time it happens because of past experience related to this. As soon as I see the FMC expiration on the preflight I brief the captain about the issue. Most don't realize there is a problem until I tell them. I usually have to review the aom to ensure the correct solution; don't swap the FMC database. The solution to the updated efb is to select the airport in the upper left and select the caution icon. This opens a window asking 'which lax charts do you want to use?' you can select the previous day's charts from there. We did not have a problem but apparently others did. We got asked multiple times if we were on the correct departure. Apparently several prior to us were not. The oshnn 7 is very different from the oshnn 6.the oshnn 7 now ends at misen versus hec for the oshnn 6. I agree we have procedures to trap the inconsistencies but guessing from ATC's questions and responses they didn't work very well. My big question is why we can't get the efb and FMC databases aligned on changeovers.have the efb jeppfd-pro application announce a required update at the next day when we are required to update the FMC. It then can act as a backup/reminder to the pilot for a manual operation.

Related reports:

Google
 

Original NASA ASRS Text

Title: Air Carrier First Officer reported that the Jeppesen Electronic Flight Bag and the FMC database have different update times.

Narrative: Departing from LAX late there was some confusion regarding the FMC database vs the Jeppesen. According to the Aircraft Operating Manual (AOM) the FMC database is good until the morning after the expiration date of the database. The problem is the Electronic Flight Bag (EFB) JeppFD-Pro application automatically changes to the new update at the time of the FMC expiration date. We were cleared via Controller Pilot Data Link Communications (CPDLC) for the OSHNN6 SID but the EFBs had already swapped over to the OSHNN7. I recognize this problem every time it happens because of past experience related to this. As soon as I see the FMC expiration on the preflight I brief the Captain about the issue. Most don't realize there is a problem until I tell them. I usually have to review the AOM to ensure the correct solution; don't swap the FMC database. The solution to the updated EFB is to select the airport in the upper left and select the CAUTION icon. This opens a window asking 'Which LAX charts do you want to use?' You can select the previous day's charts from there. We did not have a problem but apparently others did. We got asked multiple times if we were on the correct departure. Apparently several prior to us were not. The OSHNN 7 is very different from the OSHNN 6.The OSHNN 7 now ends at MISEN versus HEC for the OSHNN 6. I agree we have procedures to trap the inconsistencies but guessing from ATC's questions and responses they didn't work very well. My big question is why we can't get the EFB and FMC databases aligned on changeovers.Have the EFB JeppFD-Pro application announce a required update at the next day when we are required to update the FMC. It then can act as a backup/reminder to the Pilot for a manual operation.

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.