Date: 201502
Local time of day: 0601-1200
Location: MMMX.Airport, FO
Flight conditions: VMC
Light: Daylight
Aircraft: A320
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Initial Approach
ATC / advisory: TRACON MMMX
Aircraft component: FMS/FMC
Component problem: Improperly Operated
Reporter organization: Air Carrier
Reporter function: First Officer; Pilot Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Human factors: Training / Qualification; Human-Machine Interface; Confusion; Workload
Anomaly: ATC Issue All Types; Aircraft Equipment Problem Less Severe; Deviation - Altitude Overshoot; Deviation - Track / Heading All Types; Deviation / Discrepancy - Procedural Published Material / Policy; Deviation / Discrepancy - Procedural Clearance
Detector: Person Air Traffic Control; Person Flight Crew
When detected: In-flight
Result: Air Traffic Control Issued New Clearance; Air Traffic Control Issued Advisory / Alert; Flight Crew Became Reoriented; Flight Crew Returned To Clearance
Contributing factors: Human Factors; Aircraft
Primary problem: Human Factors

Narrative: On the DATUL2A Arrival landing 05R we programmed the FMS with STAR DATU2A; ILS 05R. The database did not allow or show any transitions or vias. I briefed the ILS DME 5R; plate 11-2. This approach tracks outbound from SMO then joins the localizer. The FMS database did not show this track outbound and showed a discontinuity between SMO [and] CI05R. We deleted the discontinuity to connect SMO to CI05R (Incorrectly). We verified the track in the FMS agreed with the Jeppesen Chart. When we passed SLM; Approach Control gave us direct to MAVEK and cleared for the RNAV ILS 05R. I had never heard of an RNAV ILS so I thought it just language/accent issue and continued with the ILS plan we had made. I confirmed with the Captain (CA) that we were cleared for the approach. At this point MAVEK is not programmed in the FMS because we were expecting to go over SMO. The CA said he saw MAVEK on the other Jeppesen Chart for the GPS approach and that SMO [and] MAVEK are the same spot. He programmed direct to MAVEK; which put in a discontinuity; so I then connected it to CI05R. It was still looking good to both of us at this point. We started to slow to 160 KIAS and get configured per the 10-7 pages but ATC requested 200 KIAS until MAVEK which we accepted. Just before MAVEK I reselected 160 KIAS. For an unknown reason; reaching MAVEK; the aircraft reverted to heading mode flying straight ahead on our current heading and did not turn left as we expected. The CA quickly said that it was in heading mode and we need to turn left. At this time ATC also called us and asked if we were going to turn left. We replied yes. I intervened by pressing the heading button to arm the NAV which it captured right away with a hard left turn to re-intercept the course. Before MAVEK we were at 12;000 FT and had set 9;200 FT in the ALT Select for the next step descent at CI05R (Incorrectly). ATC must have seen our sharp turn to re-intercept our course and gave us a vector for the 05R localizer. I think it was around a 160 degree heading to join. We took the heading and continued our descent to 9;200 FT. Reaching 9;200 FT ATC called us and said we were supposed to be at 9;700 FT. We replied and did an open climb back up to 9;700 FT. We received one more vector; about 10 degrees right of the previous heading to join. We joined the localizer and intercepted the glideslope. We were handed off to Tower; cleared to land; and landed without further incident.We knew that MMMX was considered an enhanced threat airport and I prepared by completing a MMMX PowerPoint presentation in Learning on Line. We had also thoroughly reviewed all the Company Charts in the Jeppesen app. The first contributing factor was the fact that although MMMX is shown to have D-ATIS we were unable to retrieve ATIS through our ACARS. All we could receive was TERM WX which was helpful but did not print approaches in use and landing runways. The CA had to listen to the ATIS over the normal frequency and write it down. It was broadcast in Spanish and English. The parts I heard were hard to understand but ILS 05R was clear enough.The next factor was the FMS database and Jeppesen Charts. The only FMS choices are for the ILS05R; VOR05R; or the basic 05R. There is no RNAV/GPS 05R or ILS DME 05R. Additionally; once we selected ILS 05R with the DATU2A; there were no options to select a Transition or Via. With this combination of DATU2A [and] ILS05R it displays a discontinuity between SMO [and] CI05R and omits outer waypoints. Now I know that to display the entire ILS 05R you have to select NO STAR but this is cumbersome because you are flying the STAR up until you get cleared for the approach. As to the Jeppesen Charts; plate 11-1 RNAV (GPS) OR ILS Rwy 05R [and] plate 11-2 ILS DME 05R; are too similar and easily confused. Both plates have the word ILS in them. Also the first plate 11-1; the one we actually should've used; starts with RNAV/GPS so I think we instantly overlooked it and didn't further readthe 'OR ILS 05R' part of it. I would suggest that this plate should split into each of its respective functions instead of a combo plate. I would also suggest that the FMS database be able to accept DATU2A; ILS 05R via MAVEK. Another problem with the DATU2A is that it has you fly to SLM then track SLM R-219 to SMO and expect approach authorization from there (it's even labeled IAF on the STAR Plate). SMO happens to be the IAF for plate 11-2 ILS DME 05R. I feel like it leads you to that approach. 1. Split Jeppesen Chart 11-1 into two separate procedures. 2. Update FMS Database to allow approach vias. Update FMS to include ILS DME 05R. 3. Include info in the MMMX training PowerPoint about putting in NO STAR to activate all fixes. Include a warning not to confuse the ILS 05R with the ILS DME 05R.




Synopsis: A320 First Officer experiences confusion after Approach Control gave him direct to MAVEK and cleared for the RNAV ILS 05R at MMMX. The plain ILS 05R is selected from the FMGC database but no transition from SMO is available and is created manually. Heading and altitude deviations occur and ATC eventually takes over with vectors and altitude assignments.