Narrative:

We were scheduled to fly a flight from osan air base (ab). Initially; the first error we discovered with our FMC database and jeppesen charts was that the osan ab runways were not marked correctly with the airbase. Osan ab is constructing a new; parallel runway to their existing runway 09/27. The construction has progressed to the point that osan ab is now marking the existing runway as 09R/27L; and giving taxi; takeoff; and landing clearances as such. The FMC database and the paper jeppesen do not reflect this. The jeppesen charts are dated end of 2014 or earlier. Ironically; the performance data provided via ACARS does reflect the following choices: runway 09; runway 09R; runway 27; and runway 27L. With this as a background; the second issue (or error with our equipment) occurred.our flight plan indicated that we were to pick up a jet route just north of the osan ab; at the egoba intersection. Our clearance was for the draggin 7 departure to 6;000 feet; expect radar vectors to noru and flight plan route. You will note that noru is only a 4 letter navigation fix; locally described and identified; as the sot 025/015. Noru was certainly in our FMC database. We were initially reluctant to accept the draggin 7 departure because of the caveat that it required TACAN for transitions; but since the identified transitions were not on our flight plan; we accepted this clearance. Our jeppesen charts for the draggin 7 departure are dated xx/XXXX. It identifies a fix north east of the airport as enkas; after the drggn fix. We discovered; after takeoff and during our initial radio contact with osan departure; that the fix enkas was renamed egoba! Now we had accepted a clearance with a transition that required a TACAN. After osan departure explained the distinction between enkas and egoba; we entered egoba in our FMC and proceeded on our flight plan. There was no deviation of any flight path; no disruption of air traffic or radio traffic during this time at all.osan ab ground control also instructed us to back taxi on runway 09R due to local fighter aircraft at the end of the taxiway. Runway 09R/27L is only 150 feet wide; and we cannot make a 180 turn within that width. Fortunately; the fighters had moved and we were able to continue down the taxiway to the end of the runway.the crews need more information; as referenced on jeppesen chart 31-1 as a note: 'refer to DOD/nga supplementary publications for additional information.' we; the aircrew; did not have access to this information.

Related reports:

Google
 

Original NASA ASRS Text

Title: The First Officer reported discrepancies between the FMC database and the Jeppesen charts for RKSO.

Narrative: We were scheduled to fly a flight from Osan Air Base (AB). Initially; the first error we discovered with our FMC database and Jeppesen charts was that the Osan AB runways were not marked correctly with the airbase. Osan AB is constructing a new; parallel runway to their existing Runway 09/27. The construction has progressed to the point that Osan AB is now marking the existing runway as 09R/27L; and giving taxi; takeoff; and landing clearances as such. The FMC database and the paper Jeppesen do not reflect this. The Jeppesen charts are dated end of 2014 or earlier. Ironically; the performance data provided via ACARS does reflect the following choices: Runway 09; Runway 09R; Runway 27; and Runway 27L. With this as a background; the second issue (or error with our equipment) occurred.Our flight plan indicated that we were to pick up a jet route just north of the Osan AB; at the EGOBA intersection. Our clearance was for the DRAGGIN 7 Departure to 6;000 feet; expect radar vectors to NORU and flight plan route. You will note that NORU is only a 4 letter navigation fix; locally described and identified; as the SOT 025/015. NORU was certainly in our FMC database. We were initially reluctant to accept the DRAGGIN 7 departure because of the caveat that it required TACAN for transitions; but since the identified transitions were not on our flight plan; we accepted this clearance. Our Jeppesen charts for the DRAGGIN 7 Departure are dated XX/XXXX. It identifies a fix north east of the airport as ENKAS; after the DRGGN fix. We discovered; after takeoff and during our initial radio contact with Osan Departure; that the fix ENKAS was renamed EGOBA! Now we had accepted a clearance with a transition that required a TACAN. After Osan Departure explained the distinction between ENKAS and EGOBA; we entered EGOBA in our FMC and proceeded on our flight plan. There was no deviation of any flight path; no disruption of air traffic or radio traffic during this time at all.Osan AB Ground Control also instructed us to back taxi on Runway 09R due to local fighter aircraft at the end of the taxiway. Runway 09R/27L is only 150 feet wide; and we cannot make a 180 turn within that width. Fortunately; the fighters had moved and we were able to continue down the taxiway to the end of the runway.The crews need more information; as referenced on Jeppesen chart 31-1 as a note: 'refer to DOD/NGA supplementary publications for additional information.' We; the aircrew; did not have access to this information.

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.