Kent moped crash that killed teenager had no police pursuit
Summarised from 2 outlets · Updated 6 Nov, 15:43 · Archive
An 18-year-old died and a 16-year-old was left with life-threatening injuries in a moped crash on the Isle of Sheppey; the IOPC confirms no police pursuit occurred.
An 18-year-old man died and a 16-year-old boy suffered life-threatening injuries when a moped crashed near the Sheppey Leisure Complex on the Isle of Sheppey on 31 October. The Independent Office for Police Conduct is investigating the incident.
Kent Police officers on foot saw the moped and attempted to approach it before the rider drove off. Officers arrived at the crash scene, provided emergency first aid and called for an ambulance. The IOPC confirmed that no police pursuit was initiated before the collision occurred.
A post-mortem examination was carried out on 4 November, and an inquest date has not yet been set. Emily Barry, IOPC director of engagement, said the investigation was in its early stages and urged witnesses to come forward. The watchdog said it had reviewed council and leisure centre CCTV footage and welcomed additional footage from members of the public.
How it is being reported
- No police pursuit before fatal moped crash that killed Kent teen, watchdog confirmsA fatal moped crash is under investigation by the Independent Office for Police Conduct (IOPC) after an 18-year-old man died and a 16-year-old was left with life-threatening injuries.News Shopper · 6 Nov, 15:03
- No police pursuit before fatal moped crash that killed Kent teen, watchdog confirmsA fatal moped crash is under investigation by the Independent Office for Police Conduct (IOPC) after an 18-year-old man died and a 16-year-old was left with life-threatening injuries.This Is Local London · 6 Nov, 15:03
In this story: Isle of Sheppey · Kent · Independent Office for Police Conduct · Kent Police · Emily Barry
This summary was written by AI from the headlines and standfirsts above, and states as fact only what at least two outlets report. How we use AI · Report a problem · Corrections log
Comments (0)