A321
Flight Crew Air Transport Pilot (ATP)
Distraction
Deviation / Discrepancy - Procedural Other / Unknown
Flight Crew FLC complied w / Automation / Advisory
Aircraft
Set off ROPS warning system on landing. Turned off at normal exit after moderate braking.
I was the PM (Pilot Monitoring); the captain was flying and this was our second leg of two for the day; and a red-eye flight. Upon landing in Chicago; seconds from touchdown in the touchdown zone; we received a ROPS (Runway Overrun Prevention System) alert that the runway was too short. Although we had briefed the SELs (Special Equipment List) on the aircraft before leaving [the departure airport]; I had forgotten that the aircraft was equipped with ROPS; and for a brief moment I was shocked (maybe a little disbelieving) that I was hearing the alert IN CHICAGO where we operate all the time. (I am new to the aircraft and apart from training slides cannot recall ever hearing the alert in the sim or the aircraft.) In the brief seconds before touchdown; immediately following the alert; these thoughts occurred simultaneously to me: 1) 'What is that? Does it mean if the runway is wet; it's too short to land. NO; that's not true.' 3) The runway is dry 4) We are going to land in the touchdown zone; but are we supposed to go around? 5) [As the airplane touches down in the touch down zone] 'Oh crap; we were supposed to go around.' At that time we got 'Max Braking.' The captain did a great job getting the airplane slowed enough to exit at the 90 degree intersection prior to the end of the runway; and it didn't seem to me that he was overly aggressive in doing so.
An Airbus flight crew reported the activation of the Runway Overrun Prevention System (ROPS) while landing at KORD. They were in compliance with all landing parameters and safely exited the runway after using moderate braking.