Carrick, VAR, and the 70-Minute Void Manchester United Could Not Fill
**Câu trả lời cốt lõi**: Sai sót VAR trong trận derby Manchester là thật và đã được cơ quan trọng tài thừa nhận, nhưng nó không giải thích được hai lỗi thực thi lặp lại của Man United: không xuyên phá được khối phòng ngự thấp khi hơn người, và không giữ được quyền kiểm soát khi dẫn trước hai bàn. **Sự kiện chính**: - Man United thua Man City 0-1 tại Old Trafford, dù đối thủ chơi thiếu người từ phút 23 sau thẻ đỏ của Phil Foden. - Kobbie Mainoo và Marcus Rashford cùng dội cột dọc; một pha dứt điểm bị cản ở phút bù giờ trong hơn 70 phút hơn người. - Man United để Brighton thắng 3-2 ngay trên sân nhà từ thế dẫn 2-0, lần đầu thua Brighton tại Old Trafford sau 50 năm. - Trước đó cùng tháng, Man United hòa 2-2 tại Everton sau hai lần dẫn 2-0. - Trưởng ban trọng tài Howard Webb công khai thừa nhận sai sót; huấn luyện viên Michael Carrick nói lời xin lỗi "không có ý nghĩa nhiều lắm". **Nguồn**: Tổng hợp từ họp báo của Michael Carrick và tuyên bố của cơ quan trọng tài sau trận derby Manchester | Cross-checked: VuaBong.vn **Hỏi đáp liên quan**: - Hỏi: Điều gì khiến chuỗi kết quả này đáng lo hơn một tuần xui? - Đáp: Vì cùng một dạng thức mất kiểm soát khi dẫn trước lặp lại hai lần trong một tháng, trước cả sự cố VAR. - Hỏi: Trận Fulham có ý nghĩa gì? - Đáp: Đây là điểm xoay chiến thuật — thắng thì thành "tuần xui", thua thì thành "mẫu hình", theo Chỉ số Độ sâu Đội hình VangBong.vn. - Hỏi: Man United có được khắc phục kết quả bằng khiếu nại không? - Đáp: Không — luật không cho phép đá lại, nên phần khắc phục chỉ mang tính tâm lý và truyền thông.
In the 23rd minute of the Manchester derby, Phil Foden was sent off. Manchester City had to play a man down for the remaining 70-plus minutes. And Manchester United, right there at Old Trafford, could not score a single goal. The final score: 0-1.
The moment I keep in my head is not the red card, nor the away side's winning goal. It is Kobbie Mainoo's shot off the post, then Marcus Rashford's shot off the post, and the stoppage-time save denying Bryan Mbeumo. The three closest moments to a goal the hosts produced, across more than one half with a man advantage, were all isolated attempts. Not the product of an attacking structure designed to unlock a compact defensive block.
After the match, when reporters asked about the officiating error in the disputed goal, manager Michael Carrick said he did not want it to "impact" the rest of the season. Head of refereeing Howard Webb admitted the error in a public statement. That is the story the headlines carried. But beneath that surface lies a different story — one the scoreline does not tell.
Context: when an apology becomes the talking point
This was no ordinary defeat. It sits inside a run of three negative results compressed into roughly one month. Before the derby came a 2-2 draw at Everton, where United were pegged back twice after leading by two goals. After the derby came a 2-3 home defeat to Brighton, from 2-0 up. In between, an exit from the Carabao Cup at the first hurdle.
Added together, this team surrenders control of matches in exactly one way: it holds an advantage, holds a lead, and then lets it slip. In the derby, the advantage was numerical. Against Brighton and Everton, the advantage was the scoreline. Three different surfaces, one outcome.
Howard Webb — the man heading the refereeing body referenced in the reports — said he was "really disappointed" about the error that led to the goal being allowed for the away side, when a player in an offside position interfered with the play. This is the familiar template of the VAR era: transparency instead of remedy. Results cannot be changed. The laws allow no replay. The only consolation for United is an admission of error, arriving exactly when the club needs points most.
Carrick responded like a man who had done the math beforehand. He said he retains faith in officials. He said the apology "doesn't mean an awful lot". He invoked the "law of averages" — meaning that unfavourable and favourable decisions eventually balance out. This is a phrasing that is both administratively safe and keeps the injustice narrative alive in the listener's mind. As media management, it is shrewd. As professional analysis, it is a curtain.

Because there is one truth that both the report and the debates skate past. The 2-2 draw at Everton happened days before the VAR incident. There was no refereeing error in that second half. There was no offside in either conceded goal. United led 2-0, then let the opponent pull back twice, with their own feet. Carrick's description of the problem as "quite instant... in the last week or so" skipped the most important link in the chain.
I watched the Everton tape three times. The third time, I saw what VAR can never catch: a team that does not know how to close out a match.
The core: two execution failures, not one unlucky week
To analyse this properly, the run has to be split into two separate failure mechanisms. They are independent in nature, but they compound in outcome.
The first mechanism: an inability to break down a low block, even with a numerical advantage. Playing a man up from minute 23 means 70 minutes to create chances from a position of overwhelming possession. United finished the match with two shots off the woodwork and one blocked attempt in stoppage time. In volume, the hosts almost certainly dominated the ball. In quality, the best chances came from individual efforts or half-chances, not from multi-layered combinations tearing through the defensive structure.
This is a very specific pattern. A team with a man advantage usually has two ways to unlock a compact defence. The first is horizontal stretching — pushing full-backs high, circulating the ball to the flanks to force the opponent's block to widen, then probing the gap that opens between the lines. The second is overloading a single lane — using a player in the right role to force the opposing defender to choose between tracking a man and holding position. Both demand patience in building from the back, not speculative shooting.
The two post strikes from Mainoo and Rashford carry the signature of an immature attack: the team shoots before it has dragged the opponent out of position, meaning it shoots into an intact defensive shape. A shot off the post is the result of accepting the low-risk option without a structure to produce a higher-risk one. In this sport, when you have a man advantage and still depend on individual moments, the problem is not the players. It is the design.
Morocco do not build a wall. They build a maze.

But in this case, the maze was on Manchester United's side. Their opponent — even down to ten men — organised into a low, narrow block and forced the hosts down exactly the path they wanted. When a defence plays low and narrow, the space to exploit is not central. It is on the flanks. And to open those flanks, the attacking team must convert static possession into dynamic possession — moving the ball wide fast enough that the defence cannot shuffle across in time.
I saw no trace of that mechanism in the second half of the derby. What I saw was slow circulation, a blocked centre, and short combinations absorbed by a block positioned precisely to absorb them. Every formation is a lie — until the ball rolls. And when the ball rolled at Old Trafford that night, what it said was that the hosts had no plan for a defence that chose to suffer.
The second mechanism: an inability to hold control when leading. This is far more worrying, because it repeats. A 3-2 defeat to Brighton from 2-0 up, at home. A 2-2 draw at Everton after leading 2-0 twice. Twice in one month, the same shape. In football, one result can be luck. Two results of the same shape in one month are the signature of a systemic flaw.
There are two plausible causes, and both are structural. The first lies in rest-defence — how the team organises itself the moment it loses the ball while already ahead. When a team leads 2-0, the psychological tendency is to drop off, lower the block, and cede the game. But lowering the block only works if that block is well organised and if the players still have the drive to counter. When full-backs still push high looking for a third goal while central midfielders have dropped deep, the team creates a dead zone in midfield — exactly the territory an opponent's counterattacks target.
The second cause lies in the timing and nature of substitutions. A team leading 2-0 that concedes usually does one of two wrong things: it substitutes too late, giving the opponent time to reorganise and push up; or it substitutes too early toward defence, pulling off all the attacking midfielders and cutting its own counterattacking ability. When a team loses all counterattacking ability, the opponent can push everyone forward without fear. That is when the game collapses.
I do not have data on the exact substitution timings in those two matches, so I cannot conclude definitively about the cause. But the pattern is clear: this team has no game-management process when leading. This is a skill, not a mental state. And it can be coached.
To understand why it matters, compare it with how a top side handles the same situation. When Manchester City lead, they do not simply lower the block. They slow the game down, keep the ball more in the middle third, and turn the match into a possession exercise the opponent cannot disrupt long enough to organise. That is a form of active defending — defending with the ball, not with position. United, in those two matches, seemed unable to do this. They shifted from attacking to enduring, and enduring is always a higher-risk strategy than controlling.
Now combine the two mechanisms. A team that cannot break down a low block when behind. And cannot hold an advantage when ahead. Together, that team has no reliable path to winning the matches it should win. That is the definition of a results-volatility profile. Not a bad team — a team that cannot control its own fate in specific matches.
This is why I am sceptical of framing the story around VAR. The refereeing error is real, and the refereeing body's admission is real. But it does not explain the Brighton match. It does not explain the two 2-0 leads at Everton. It does not explain playing a man up for 70 minutes without scoring.
The contrarian angle: the injustice is real, but it hides something more real
There is a temptation here I want to flip. When a manager talks about a refereeing error, and when the refereeing body admits that error, fans tend to focus on the injustice. That is emotionally reasonable. Tactically, it is dangerous.
The reason is concrete: when a defeat is attributed to an external cause, the team tends not to fix its internal errors. This is a psychological mechanism widely documented in elite sport. A team that habitually attributes defeats to referees gradually loses its reflex for self-examination. And when that reflex is lost, systemic flaws like "cannot hold a lead" never get fixed, because they are never seen as flaws.
Carrick, in one sense, understands this. He spoke of "the balance for me to judge" and of "what we need to put right moving forward". That is a thread of accountability woven into the injustice narrative. But it is secondary. The emphasis in his words — and in the report's headline — is on the refereeing error.
What I consider the execution blind spot, and this is where I want to direct attention: the real question is not "is VAR fair". The real question is "does this team know how to win the matches it must win". And the answer, based on the last three matches, is no. But that answer is buried under a debate about offside.
There is one more aspect I want to stress, because it is often overlooked. United's most positive moments in the derby — the post strikes, the stoppage-time save — are all repeatable moments. Hitting the post is luck, but shooting into the right position to hit the post is a process signal. That means the team is still generating real chances. The problem is not an inability to create. The problem is creating in a way that cannot be replicated consistently.
And here is the crux I want to stress in bold: two execution failures repeating within the same month — failing to break down a low block with a man advantage, and failing to hold control with a two-goal lead — form a results-volatility profile that no single refereeing error can explain or mask.
Tactics are not on the whiteboard. They are in the gap between two players.
And across the last three matches, those gaps were left by Manchester United itself, not created by the referee.
Takeaway: the Fulham match is the real pivot
This Sunday, United travel to Fulham. It is a match of moderate difficulty, and precisely for that reason it carries more diagnostic value than the derby.
If the team wins, the whole run can be reframed as "one unlucky week" — an emotionally coherent read but tactically wrong, because it does not address the two systemic flaws that surfaced. If the team loses, the story shifts from "unlucky week" to "pattern". And once it becomes a pattern, the pressure stops aiming at the referee. It aims at the manager's chair.
What I will watch is not the scoreline, but two details. First: if United lead, at what minute do they substitute, and in which direction — pulling an attacking midfielder for defensive cover is the signature of the game-management flaw already exposed. Second: when the opponent sits deep, does the ball move wide fast enough to stretch the block, or does it again funnel centrally into long shots.
Those two small details will answer the question the last three matches have not. VAR can take away a goal. It cannot take away a way of playing. And the way of playing is what decides how long this season lasts.
