Narrative:

We were flight planned to end up in iah on the gushr arrival. Halfway to iah the weather had moved east and we were given a quicker route to swb for the ZEEKK2 arrival. In ft. Worth airspace and approaching swb we were assigned the GESNR1 arrival which did not match current ATIS for landing runways. Inside of swb we were told to descend via the ZEEKK2 arrival. My first officer (first officer) asked for confirmation because we had been given the gesnr arrival just a few minutes earlier. The controller said we should be on the zeekk arrival and the gesnr was assigned in error. We heard him discuss this same problem with an aircraft behind us who was also assigned the gesnr in error. The controller realized this and cleared us direct to zeekk and descend via the zeekk arrival. We were leading the pack and he said to delete speed restrictions. We entered direct zeekk in the FMC and were in a managed descent. We then reprogrammed the FMC with the zeekk arrival. Everything looked on track for the zeekk crossing restriction. After passing zeekk the FMC immediately showed us 5000 ft. High for next crossing restriction. I selected full speed brakes; disconnected the autopilot and nosed over to meet next restriction which we barely made. We couldn't get a word in due to radio saturation. We wondered why this had happened and thought it was due to multiple arrival assignments with the last one being dropped on us at the last minute while already descending. In retrospect; I realize what happened. We were descending and approaching zeekk on the gesnr arrival when changed once again to the zeekk arrival at the last minute. We immediately selected direct zeekk in the FMC and loaded the zeekk arrival. This locked the FMC on the crossing restriction for zeekk on the gesnr arrival which is different than the zeekk restriction on the zeekk arrival. That's why the FMC showed on profile up to zeekk. As a result; we crossed zeekk at the gesnr restriction instead of the zeekk arrival restriction which is different. The controller didn't say anything as we were leading the pack and he just wanted us to go fast. At that point we still hadn't figured out why this happened. The rest of the arrival was uneventful.

Related reports:

Google
 

Original NASA ASRS Text

Title: A319 Captain reported being high at intersection on arrival into IAH.

Narrative: We were flight planned to end up in IAH on the GUSHR arrival. Halfway to IAH the weather had moved east and we were given a quicker route to SWB for the ZEEKK2 arrival. In Ft. Worth airspace and approaching SWB we were assigned the GESNR1 arrival which did not match current ATIS for landing runways. Inside of SWB we were told to descend via the ZEEKK2 arrival. My FO (First Officer) asked for confirmation because we had been given the GESNR arrival just a few minutes earlier. The Controller said we should be on the ZEEKK arrival and the GESNR was assigned in error. We heard him discuss this same problem with an aircraft behind us who was also assigned the GESNR in error. The Controller realized this and cleared us direct to ZEEKK and descend via the ZEEKK arrival. We were leading the pack and he said to delete speed restrictions. We entered direct ZEEKK in the FMC and were in a managed descent. We then reprogrammed the FMC with the ZEEKK arrival. Everything looked on track for the ZEEKK crossing restriction. After passing ZEEKK the FMC immediately showed us 5000 ft. high for next crossing restriction. I selected full speed brakes; disconnected the autopilot and nosed over to meet next restriction which we barely made. We couldn't get a word in due to radio saturation. We wondered why this had happened and thought it was due to multiple arrival assignments with the last one being dropped on us at the last minute while already descending. In retrospect; I realize what happened. We were descending and approaching ZEEKK on the GESNR arrival when changed once again to the ZEEKK arrival at the last minute. We immediately selected direct ZEEKK in the FMC and loaded the ZEEKK arrival. This locked the FMC on the crossing restriction for ZEEKK on the GESNR arrival which is different than the ZEEKK restriction on the ZEEKK arrival. That's why the FMC showed on profile up to ZEEKK. As a result; we crossed ZEEKK at the GESNR restriction instead of the ZEEKK arrival restriction which is different. The Controller didn't say anything as we were leading the pack and he just wanted us to go fast. At that point we still hadn't figured out why this happened. The rest of the arrival was uneventful.

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.