Narrative:

Preflight from lax-ZZZ. First officer was entering the winds and noticed the fixes on UJ9 from pvr-col are different on the FMC legs page than what is shown on the flight plan. The FMC shows UJ9 as tevek; igrot and tidek while the flight plan shows tevek; tukon and siksa. The jeppesen paper chart shows tevek; tukon; siksa. The efb chart also shows tevek; igrot and tidek. We verified the navigation database as current for the date.so the same airway was showing igrot/tidek in the FMC/efb and tukon/siksa on the flight plan/jeppesen paper chart. We called dispatch and got patched through to the superintendent of dispatch and chief pilot on call. Neither could understand the discrepancy; so we were refiled via direct routing off of UJ9. It took about a 25 minute delay at the gate to work through this problem. All other routes in the FMC database were correct for this leg; not sure if this had to do with the next update being one day away and the new database had somehow been entered in error when loaded by maintenance.

Google
 

Original NASA ASRS Text

Title: Captain reported finding during preflight that the flight plan waypoints on UJ9 between PVR and COL were different from those displayed on their FMC and EFB. Dispatch refiled to resolve the discrepancy.

Narrative: Preflight from LAX-ZZZ. First Officer was entering the winds and noticed the fixes on UJ9 from PVR-COL are different on the FMC LEGS page than what is shown on the flight plan. The FMC shows UJ9 as TEVEK; IGROT and TIDEK while the flight plan shows TEVEK; TUKON and SIKSA. The Jeppesen paper chart shows TEVEK; TUKON; SIKSA. The EFB chart also shows TEVEK; IGROT and TIDEK. We verified the NAV database as current for the date.So the same airway was showing IGROT/TIDEK in the FMC/EFB and TUKON/SIKSA on the Flight Plan/Jeppesen paper chart. We called Dispatch and got patched through to the Superintendent of Dispatch and Chief Pilot on Call. Neither could understand the discrepancy; so we were refiled via direct routing off of UJ9. It took about a 25 minute delay at the gate to work through this problem. All other routes in the FMC database were correct for this leg; not sure if this had to do with the next update being one day away and the new database had somehow been entered in error when loaded by Maintenance.

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.