A 78th-Minute Injustice Nobody Reviewed

There is a specific kind of football injustice that hurts more than all the others: the one that never gets looked at. No replay on the big screen. No earpiece crackle. No referee trotting to the pitchside monitor. Just a wave of the hand and the match moves on, carrying an incorrect scoreline with it.

Wondering if the ref got it right?

Upload any clip — X, Reddit, or a file — and get an AI verdict in 60 seconds. Grounded in the IFAB Laws, with frame-by-frame reasoning and a confidence score.

Analyze a play → No card required

That is exactly what happened at 78:40 in England vs Ghana at the 2026 FIFA World Cup. The match was goalless — in the balance, the kind of moment when one decision reshapes everything. Ghana's #25, Prince, drove through the middle of the pitch on a counter-attack, beat England's #2 for position, and pushed the ball ahead into the penalty area. A recovering England defender, already beaten, slid in from behind and to the side. His leg caught the attacker's legs before Prince could reach the ball.

Referee Saíd Martínez waved play on. VAR did not intervene. The score stayed 0-0.


What OURVAR.AI Ruled — and How Certain It Is

OURVAR.AI's AI analysis returned a verdict of WRONG NO-CALL at HIGH confidence. That is the platform's clearest possible finding — not a marginal call, not a 50-50, but a missed penalty that the available evidence resolves firmly in Ghana's favour.

The Laws cited are Laws 12 and 14 — the twin pillars of every penalty decision in football.

Law 12 (Fouls and Misconduct): tripping or attempting to trip an opponent is a direct free-kick offence when committed carelessly. A recovering defender who slides through an attacker's legs rather than playing the ball is committing exactly that offence.

Law 14 (The Penalty Kick): any direct free-kick offence committed by a defending player inside their own penalty area is a penalty kick. The foul was inside the box. The chain is airtight.


Why the AI Got There — In Plain Football Language

Strip away the legal language and this is a case you will recognise from any level of football. Prince beat his man. Not narrowly — he had already won position and pushed the ball ahead. England's #2 was behind him, beaten, and rather than accepting it, slid in. His leg connected with the attacker's legs before Prince could get a touch on the ball.

That sequencing is everything. Defender gets the man before the ball. Inside the box. After the attacker has already won position. That is the scenario the Laws exist specifically to punish, because if recovering defenders could trip attackers from behind with impunity the entire concept of winning a duel would be meaningless.

The goalkeeper muddying the water is worth addressing directly, because it is almost certainly why Martínez hesitated. England's keeper arrived into the tangle — but the broadcast frames and OURVAR.AI's analysis make clear that the goalkeeper's collision was with his own defender, not with Prince. By the time the keeper arrived, the foul had already been committed. The three-way pile-up looked chaotic in real time; in replay, the sequence is straightforward. The #2 trips the attacker. The keeper then runs into the #2. Two separate events, one of which is a foul and one of which is irrelevant.

This is exactly how complex-looking incidents become missed penalties: the visual noise of a crowded box gives a referee a reason — consciously or not — to default to "no call." That default was wrong here.

As for VAR: the platform's analysis is unambiguous that this was a clear and obvious error that should have triggered an On-Field Review recommendation. VAR's silence was a compounded failure, not a vindication of the on-field call.


What the Community Thought

On OURVAR.AI, the case drew 9 upvotes against 3 downvotes — a 75% majority agreeing with the AI's penalty verdict. That is a meaningful margin, particularly given how often contentious decisions split communities closer to 50-50.

The three dissenters likely fell into one of two camps: those who believed the goalkeeper's involvement was the key contact point (the footage suggests otherwise), or those applying the classic "it looked complicated, so it probably wasn't a penalty" reasoning that referees themselves sometimes fall into. Neither holds up to a frame-by-frame read of the incident.

The submitter left no personal rating — which, given the strength of the AI verdict and the community lean, may simply reflect the frustration of submitting a case you already know is a penalty and watching the numbers confirm it.


When Does This Kind of Call Usually Go the Other Way?

Based on general IFAB guidance and the broader body of VAR jurisprudence — not data specific to this case — recovering-defender challenges tend to escape punishment most often in three scenarios.

First, when the contact is minimal and the attacker stays on his feet. If Prince had stumbled slightly but kept running, Martínez's wave-on becomes much harder to challenge. He went to ground, which makes the foul harder to dismiss.

Second, when the defender gets a genuine touch on the ball first. Even a glancing touch can shift a trip into a legitimate challenge. OURVAR.AI's analysis found no such touch here — the legs were caught before the ball was played.

Third — and most relevant here — when multiple players are involved and the "who fouled whom" question becomes genuinely ambiguous. The goalkeeper's arrival created exactly that fog. In a pre-VAR era, Martínez's hesitation might be more understandable. In 2026, with a Video Assistant Referee specifically designed to unpick these tangles, it is indefensible.


The Bottom Line

Ghana were 12 minutes from the end of a goalless World Cup match, with an attacker breaking clear and a clear penalty denied. The referee missed it. VAR compounded it by not acting. England kept a clean sheet they had not fully earned.

This is not a 51-49 call dressed up as controversy for clicks. OURVAR.AI's verdict is HIGH confidence — the AI equivalent of pointing at the replay and saying there is nothing to argue about. The Laws are clear. The position of the contact is clear. The sequence — legs caught before ball reached, defender behind the attacker, inside the box — is clear.

Saíd Martínez had a hard moment in a difficult match. VAR had no such excuse.

Read the full case analysis, including the specific Law 12 and Law 14 breakdown, at https://ourvar.ai/case/131.