Five teenagers hospitalised after Peak District car crash
Summarised from 3 outlets · Updated 9 Nov, 11:28 · Archive
Five teenagers were taken to hospital with serious injuries after a one-car collision in the Peak District.
Five teenagers have been taken to hospital with serious injuries after a one-car collision on the A5270 Old Coalpit Lane near the A515 junction in the Peak District. Police were called to reports of the collision at 2.10am on Saturday, November 7. The blue Suzuki Swift was carrying three teenage girls and two teenage boys.
All five have been hospitalised with what police describe as serious injuries, which are not believed to be life-threatening at this time. All parents of those involved have been contacted.
As of 3pm on November 7, Old Coalpit Lane remained closed from the junction of the A515 to The Ditch in Chelmorton. Police are appealing for anyone who was driving in the area at the time and saw the Suzuki prior to the collision to come forward, particularly anyone with dashcam footage.
Anyone with information has been asked to contact Derbyshire Constabulary via their website, the Derbyshire Constabulary Facebook page or by calling 101, quoting reference 26000688247. CrimeStoppers can also be contacted anonymously on 0800 555 111.

How it is being reported
- Five teenagers seriously hurt in Peak District crashThree teenage girls and two teenage boys were taken to hospital with serious injuriesBuxton Advertiser · 9 Nov, 10:59
- Five teenagers seriously hurt in Peak District crashThree teenage girls and two teenage boys were taken to hospital with serious injuriesDerbyshire Times · 9 Nov, 10:59
- 5 teenagers in hospital with serious injuries after Peak District crashThe teenagers were all travelling in a blue Suzuki SwiftDerbyshire Live · 7 Nov, 15:45
In this story: Peak District · Derbyshire · A5270 Old Coalpit Lane · Derbyshire Constabulary
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)