Narrative:

Aircraft was flying on the arrival to runway 36R. ATC instructed 'cross kriss at 13000 ft.; then descend via kriss arrival'. Crew set aircraft to comply with instruction. Approximately 2 miles prior to kriss; aircraft switched controllers and immediately instructed 'aircraft; plan runway 36L.' pilot flying changed landing runway in FMS. Upon changing landing runway; FMS deleted '13000 ft.' restriction and inserted published arrival restriction at kriss of 'at or above 11000 ft.'; requiring altitude restriction to be reprogrammed. By the time pilot flying put the 13000 ft. Restriction at kriss; aircraft was nearing 13000 ft. And sequenced to the next fix on the arrival (early turn) and began descent. Prior to going below restriction; crew noticed impending deviation and selected 'level off'. Crew immediately and pro-actively corrected and crossed kriss at 13000 ft. As assigned but dipped momentarily below. Aircraft deviated by altitude not more than a few hundred ft.; and subsequently met all assigned restrictions.when inserted new arrival (36L vs 36R); FMS re-strung the approach and automatically set back to the database crossing restriction; eliminating programmed and assigned ATC crossing restriction. Was a 'swiss cheese' moment where change occurred all within a short period of time. Had the change been entered 20 seconds earlier or later; it wouldn't have been an issue. Wait until crossing restrictions aren't imminent; and be more proactive with confirming the FMS honors entered crossing restrictions.

Google
 

Original NASA ASRS Text

Title: A Flight Crew reported after reprogramming the FMS to a different runway than planned they descended below a crossing restriction on the RNAV Arrival.

Narrative: Aircraft was flying on the arrival to Runway 36R. ATC instructed 'cross KRISS at 13000 ft.; then descend via KRISS arrival'. Crew set aircraft to comply with instruction. Approximately 2 miles prior to KRISS; Aircraft switched controllers and immediately instructed 'Aircraft; plan Runway 36L.' Pilot Flying changed landing runway in FMS. Upon changing landing runway; FMS deleted '13000 ft.' restriction and inserted published arrival restriction at KRISS of 'at or above 11000 ft.'; requiring altitude restriction to be reprogrammed. By the time Pilot Flying put the 13000 ft. restriction at KRISS; aircraft was nearing 13000 ft. and sequenced to the next fix on the arrival (early turn) and began descent. Prior to going below restriction; crew noticed impending deviation and selected 'Level Off'. Crew immediately and pro-actively corrected and crossed KRISS at 13000 ft. as assigned but dipped momentarily below. Aircraft deviated by altitude not more than a few hundred ft.; and subsequently met all assigned restrictions.When inserted new arrival (36L vs 36R); FMS re-strung the approach and automatically set back to the database crossing restriction; eliminating programmed and assigned ATC crossing restriction. Was a 'Swiss cheese' moment where change occurred all within a short period of time. Had the change been entered 20 seconds earlier or later; it wouldn't have been an issue. Wait until crossing restrictions aren't imminent; and be more proactive with confirming the FMS honors entered crossing restrictions.

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.