Met Police facial recognition wrongly matched youth worker Shaun Thompson
In February 2024 Shaun Thompson, a youth advocacy worker, was stopped and questioned after the Metropolitan Police's live facial‑recognition system matched him to a watchlist entry. The encounter lasted around 30 minutes and ended when Thompson produced ID; he subsequently brought a High Court challenge to the Met's use of LFR, which was dismissed on 2026-04-21. Reporting on the case is documented by multiple independent outlets including the BBC and The Independent.
A live facial‑recognition match generated a false positive that prompted officers to stop and detain a youth worker.
Key facts
- What
- In February 2024 Shaun Thompson, a youth advocacy worker, was stopped and questioned after the Metropolitan Police's live facial‑recognition system matched him to a watchlist entry.
- Incident date
- Feb 1, 2024
- Who
- Metropolitan Police Service (Met Police)
- Failure mode
- Hallucination
- AI surface
- Computer Vision
- Severity
- Medium
What happened
Shaun Thompson, a youth worker, was stopped by Met officers in February 2024 outside London Bridge after LFR matched his image to a watchlist entry; officers told him he was a wanted man and detained him for about 30 minutes. He refused to provide fingerprints and was released after showing a passport photo. Thompson later mounted a legal challenge to the Met’s use of LFR; the High Court dismissed that challenge on 2026-04-21.
What broke inside the model
- 01 · TriggerA user asks for a fact, a citation, or a figure.
- 02 · Model stepThe model writes a fluent, confident answer.
- 03 · Control gapNothing ties the claim back to a real source.
- 04 · FailureA fabricated fact ships as if it were verified.
- 05 · ConsequenceThe false claim reaches a customer, a court, or the public.
Confidence holds, and even spikes, as the claim detaches from any source.
A live facial‑recognition (LFR) deployment produced a false‑positive match between a passerby and an entry on a police watchlist. The matching algorithm flagged the individual and issued an alert to officers, which triggered a stop and questioning. The system’s alerting/human‑review chain did not prevent the wrongful detention.
What it cost
Sources
- Press'Facial recognition tech mistook me for wanted man' - BBCbbc.com
- PressPair lose High Court challenge against Metropolitan Police over use of live facial recognition technology | The Independentindependent.co.uk
- PressAIAAIC - Youth advocacy worker misidentified by Met Police facial recognition systemaiaaic.org
Cite this entry
https://failureindex.ai/failures/met-police-facial-recognition-wrongly-matchedAI Failure Index. "Met Police facial recognition wrongly matched youth worker Shaun Thompson" (FI-0488). Realm Labs. https://failureindex.ai/failures/met-police-facial-recognition-wrongly-matched (indexed Jun 10, 2026).Data fields CC-BY 4.0, prose citation permitted. Incident ID FI-0488. Full dataset at /data.
Note from Realm Labs, the Index steward
How Realm fits
- Prism
- OmniGuard
- AI Detection & Response (AIDR)
This entry sits in the index's predictive wing: a system that scores, ranks, perceives, or steers rather than generates. Realm's runtime layer is built for the generative and agentic systems now moving into these same decision seats, where it watches a model's internal state and holds an unsupported claim or an unchecked action before it commits. The control gap on this record, an automated decision that reached people with no runtime check in front of it, is the same gap. The index keeps predictive failures on the record because the pattern carries straight into the systems shipping today.