Narrative:

We were on the endee 1 arrival into mdw. The arrival had been properly briefed. The first ATIS we received showed an ILS for [runway] 31C. We were approaching poogy and given a crossing restriction of FL240. Next; we received crossing restriction of nanee at 17;000 ft. Shortly thereafter; we were given 'descend via the endee one arrival.' with the previously two changes from the published arrival; we were almost 4;000 ft high on the profile. I increased the speed to over 300 KTS and caught back up to the path before mmegg. A new ATIS came out and was advertising [runway] 31C circle [runway] 22L. We revised the runway in the box to [runway] 22L with gleam and runts added in. After passing stkny; ATC queried our headed. We then realized that when [runway] 22L was changed in the box the arrival fix sequencing changed too. We were then given a heading 090 and told 'no worries.'I should have noticed the change and rebriefed the approach. Although we should have software available to allow a different landing runway with the ability to fly a different transition; if not; you could potentially be close to the field with a lot of programming required. Mdw had previously been utilizing the RNAV Y and Z approaches for [runway] 22L. Also; due to the changes to the crossing restrictions on the arrival; my full attention was on trying to get back on the path. If we were allowed to 'descend via' the entire arrival I could have caught the error in fix sequencing.

Google
 

Original NASA ASRS Text

Title: Air carrier flight crew learns that the ENDEE 1 transitions into MDW are determined by the runway selection in the FMC. A clearance to fly the Runway 31C transition and circle to land Runway 22L results in a track deviation when Runway 22L is entered prior to passing STKNY.

Narrative: We were on the ENDEE 1 Arrival into MDW. The arrival had been properly briefed. The first ATIS we received showed an ILS for [Runway] 31C. We were approaching POOGY and given a crossing restriction of FL240. Next; we received crossing restriction of NANEE at 17;000 FT. Shortly thereafter; we were given 'descend via the ENDEE One Arrival.' With the previously two changes from the published arrival; we were almost 4;000 FT high on the profile. I increased the speed to over 300 KTS and caught back up to the path before MMEGG. A new ATIS came out and was advertising [Runway] 31C circle [Runway] 22L. We revised the runway in the box to [Runway] 22L with GLEAM and RUNTS added in. After passing STKNY; ATC queried our headed. We then realized that when [Runway] 22L was changed in the box the arrival fix sequencing changed too. We were then given a heading 090 and told 'no worries.'I should have noticed the change and rebriefed the approach. Although we should have software available to allow a different landing runway with the ability to fly a different transition; if not; you could potentially be close to the field with a lot of programming required. MDW had previously been utilizing the RNAV Y and Z approaches for [Runway] 22L. Also; due to the changes to the crossing restrictions on the arrival; my full attention was on trying to get back on the path. If we were allowed to 'descend via' the entire arrival I could have caught the error in fix sequencing.

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.