Date: 202002
Local time of day: 1201-1800
Location: CLT.TRACON, NC
Flight conditions: VMC
Aircraft: A320
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Descent
Airspace: Class B CLT
ATC / advisory: TRACON CLT
Reporter organization: Air Carrier
Reporter function: First Officer; Pilot Flying
Reporter qualification: Flight Crew Instrument; Flight Crew Multiengine; Flight Crew Air Transport Pilot (ATP)
Human factors: Distraction; Human-Machine Interface; Time Pressure
Second reporter function: Captain; Pilot Not Flying
Anomaly: Deviation - Altitude Overshoot; Deviation / Discrepancy - Procedural Clearance; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Flight Crew
When detected: In-flight
Result: Air Traffic Control Issued New Clearance
Contributing factors: Chart Or Publication; Human Factors; Procedure; Airspace Structure
Primary problem: Procedure

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.


Second narrative: Aircraft was flying to CLT on the arrival up to land 36R. ATC instructed 'cross KRISS at one-three thousand; then descend via arrival'. Crew set aircraft to comply with instruction. Approximately 2 miles prior to KRISS; Aircraft switched controllers and immediately instructed 'Aircraft; plan Runway 36L.' Upon changing landing runway; FMS deleted '13000 ft.' restriction and went with normal arrival window; thus requiring altitude restriction to be reprogrammed. By the time restriction was put in; aircraft was at 13200 ft. and sequenced to the next fix on the arrival; and began descent. Crew immediately noticed deviation and selected 'Level Off' when apparent the FMS would not honor crossing restriction. Crew immediately corrected and crossed KRISS at 13000 ft. as assigned. Aircraft deviated by altitude not more than a few hundred ft.; and subsequently met all assigned restrictions. Be alert for frequency changes and landing runway assignments while under heavy workloads.


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