B777-200
Confusion
Aircraft Equipment Problem Less Severe; Deviation - Track / Heading All Types; Deviation / Discrepancy - Procedural Clearance; Deviation / Discrepancy - Procedural Published Material / Policy
Air Traffic Control Separated Traffic; Air Traffic Control Issued New Clearance; Flight Crew Executed Go Around / Missed Approach
Procedure; Human Factors; Chart Or Publication; Airport; Aircraft
[Flying the ANSUG 1A STAR/Rwy 09R ILS approach to SBGR the FMS turned us] from MARPU toward fix CI09R when [ATC cleared us to climb to 7;000 FT heading 090 for vectors for another approach]. When set up for the next approach the FMS now showed UTKET then CI09R. One must select the MARPU transition in order to get UTKET. CI09R is only in the B777 data base. It is not depicted on the 09R approach plates. It is very confusing. A second problem also occurred. The charts show the transition altitude is 8;000 FT. When we tried to level at 7;000 FT the B777 data base wanted FL070. It does not recognize feet until cleared below FL070. Very confusing.Our chart provider needs to sync up the plates with the B777 data base.
This time when we inserted the ILS 9R in the FMC in showed UTKET then CI09R. Seems one must select the MARPU transition for UTKET to show up.
When a B777-200 flight crew; arriving SBGR via the ANSUG 1A STAR; Runway 09R ILS; turned inside the charted track between westbound at MARPU (an IAF) on the STAR and eastbound at UTKET (a straight in IF on the approach) ATC directed a go-around. A mysterious fix CI09R inside of UTKET and prior to the LOM played a role. The aircraft's database also failed to utilize the published 8;000 MSL transition altitude.