B737 captain reports receiving a runway change from 23L to 23R approaching ekeke on the KOLTS1 RNAV ...

Attributes
ACN	1277512
Time
Date	201507
Place
Locale Reference	IND.Airport
State Reference	IL
Environment
Flight Conditions	IMC
Aircraft 1
Make Model Name	B737 Undifferentiated or Other Model
Operating Under FAR Part	Part 121
Flight Phase	Descent
Route In Use	STAR KOLTS1
Flight Plan	IFR
Component
Aircraft Component	FMS/FMC
Person 1
Function	Pilot Not Flying Captain
Experience	Flight Crew Last 90 Days 81 Flight Crew Type 949
Events
Anomaly	Deviation - Altitude Crossing Restriction Not Met Deviation - Altitude Overshoot Deviation - Procedural Published Material / Policy Deviation - Procedural Clearance

Narrative:

We were cleared on and descending via the KOLTS1 RNAV arrival into ind. Just prior to ekeke intersection we were assigned a different runway (I believe we had 23L loaded and we were assigned 23R). I made the runway change in the FMC and the first officer (first officer) verified it prior to executing the change. We had not noticed a discontinuity that had been inserted in the process. When the change was executed; v-nav disengaged. We both recognized the mode reversion. I went 'heads down' to find the error and the first officer manually flew via the MCP. Due to our close proximity to ekeke during the change in clearance and subsequent FMC change; although the first officer recognized the 10000 ft restriction just prior to ekeke he was unable to arrest the descent rate before descending below 10000 just prior to ekeke. I believe we stopped around 9400-9500 ft. Immediately past ekeke we were back on the FMC path; the FMC error had been corrected; and we continued to descend via the arrival.

Original NASA ASRS Text

Title: B737 Captain reports receiving a runway change from 23L to 23R approaching EKEKE on the KOLTS1 RNAV Arrival to IND. When the runway change is executed in the FMC; EKEKE disappears along with its crossing restriction and an altitude deviation occurs.

Narrative: We were cleared on and descending via the KOLTS1 RNAV arrival into IND. Just prior to EKEKE intersection we were assigned a different runway (I believe we had 23L loaded and we were assigned 23R). I made the runway change in the FMC and the First Officer (FO) verified it prior to executing the change. We had not noticed a discontinuity that had been inserted in the process. When the change was executed; V-NAV disengaged. We both recognized the mode reversion. I went 'heads down' to find the error and the FO manually flew via the MCP. Due to our close proximity to EKEKE during the change in clearance and subsequent FMC change; although the FO recognized the 10000 FT restriction just prior to EKEKE he was unable to arrest the descent rate before descending below 10000 just prior to EKEKE. I believe we stopped around 9400-9500 FT. Immediately past EKEKE we were back on the FMC path; the FMC error had been corrected; and we continued to descend via the arrival.

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.

B737 captain reports receiving a runway change from 23L to 23R approaching ekeke on the KOLTS1 RNAV arrival to ind. When the runway change is executed in the FMC; ekeke disappears along with its crossing restriction and an altitude deviation occurs.