Air carrier pilots reported discrepancies between the FMC database and SID Chart for the XUDED crossing restriction of FL220 on the XUDED1B SID from PVR.
Synopsis
Air carrier pilots reported discrepancies between the FMC database and SID Chart for the XUDED crossing restriction of FL220 on the XUDED1B SID from PVR.
Narrative
During predeparture we were cleared the XUDED1B Departure from Runway 22 in PVR. In the initial clearance we were cleared to climb to FL320. We read that back to the Clearance Delivery Person. We briefed and set FL320 in the Altitude Selector on the mode select panel. From that point forward nobody in ATC ever altered that vertical clearance. We departed and were handed off to Departure. Upon initial contact with Departure; we reported out altitude crossing and climbing to 32000 ft. Just prior to PR552 we were cleared direct XUDED and normal speed. We again said 'direct XUDED; normal speed climbing to FL320.' At no time were we ever cleared to climb via the SID. A few minutes later ATC cleared us to stop climb at 25000 ft. We reset the modes select panel; confirmed the setting and complied. Shortly after that the Controller voice changed to an American. He asked us who cleared us above 22000 ft.. We explained the clearance we received and who gave it to us. He said there was an altitude limit of 22000 ft. out of PVR but also said 'no problem.' He left the frequency; and we continued without incident.In reviewing the event in the cockpit; we noticed a FL220 under XUDED on the SID plate. It does not have the standard line above and below to denote a mandatory crossing. We also checked the FMC procedure in the aircraft database that was loaded and that we used to fly. The procedure loaded in the database has XUDED coded as at or above FL220. There is a discrepancy between ATC expectation; the chart and the FMC database. We were also cleared off the SID direct to XUDED without any issued vertical profile except the previously issued climb to 32000 ft. from pre departure and our read backs.We could have done a better job comparing the plate to the FMC loading. We did confirm in the briefing; but it was rushed; and we missed the ambiguity. PVR Controllers could do a better job managing clearance limits in pre departure clearance. Perhaps they should not issue initial clearance above FL220 if that is what they expect.
Second reporter narrative
With clearance on ground; we were cleared to climb to FL320. On departure; we made sure to check in with both our current altitude and the altitude we were climbing to FL320. Passing through FL235; Departure stopped us at FL250. We stopped at FL250; and then were switched to Center. Center climbed us higher; and then asked who cleared us to climb higher originally. We told them that was our original clearance on ground; and no one had changed it. They told us that there was a PVR altitude restriction on FL220; and that he would talk to Ground.
Source: NASA Aviation Safety Reporting System (public domain). Reports are voluntary submissions and are not verified by NASA.