
In the 73rd minute, Jorgensen received a pass into the penalty area. The Chelsea goalkeeper had enough time and space to control the ball, either by making a long pass or passing it out wide to Reece James. Jorgensen held the ball for almost four seconds, allowing Barcola to close in. And then the crazy thing happened for Chelsea.
Barcola successfully intercepted Jorgensen's pass. The ball bounced to Kvaratskhelia, then passed to Vitinha. The Portuguese midfielder headed the ball forward. Seeing Jorgensen advanced, Vitinha executed a delicate lob to beat the Chelsea goalkeeper.
Jorgensen made a disastrous mistake just as Chelsea had equalized 2-2. James clutched his head. Trevoh Chalobah was furious with Jorgensen. This was the turning point that led to Chelsea's downfall, as in the remainder of the match, "The Blues" conceded two more goals and the game ended 2-5.
For two consecutive days in the Champions League, fans witnessed disastrous mistakes from goalkeepers. The day before, Tottenham goalkeeper Kinski became the focus of football attention when he made two individual errors leading to goals conceded within 17 minutes in Tottenham's humiliating 2-5 defeat against Atletico Madrid.
Kinski was substituted after just 17 minutes. Meanwhile, Jorgensen was luckier as he played the entire match and received encouragement from the manager. After the game, Chelsea manager Liam Rosenior reassured his player: "Every player makes mistakes. Jorgensen is not the first goalkeeper to be in this situation, and it's part of football. Jorgensen admitted his mistake in the dressing room."
Jorgensen is a Swedish goalkeeper, born in 2002. Under manager Rosenior, Robert Sanchez was relegated to the bench due to frequent mistakes. Jorgensen seized the opportunity, playing well in recent Premier League matches when given the chance to start. However, after his mistake against PSG, Jorgensen is at risk of returning to the bench.
Source: https://tienphong.vn/them-pha-xu-ly-tham-hoa-cua-thu-mon-o-knock-out-champions-league-post1826772.tpo







Comment (0)