M1 delays: lanes re-opened after two-hour delay and nine-mile tailbacks due to collision near Leicester

A collision between a van and a trailer has caused a spillage on the roads, leading to lanes being closed during the early-morning rush hour
Heather Carrick
By Heather Carrick
12th Feb 2024, 8:49am
Drivers are facing nine-mile tailbacks and delays of up to two-hours after a multi-vehicle collision in the M1 near Leicester. (Credit: motorwaycameras.co.uk)Drivers are facing nine-mile tailbacks and delays of up to two-hours after a multi-vehicle collision in the M1 near Leicester. (Credit: motorwaycameras.co.uk)
Drivers are facing nine-mile tailbacks and delays of up to two-hours after a multi-vehicle collision in the M1 near Leicester. (Credit: motorwaycameras.co.uk)

Drivers on the M1 near Leicester were facing massive delays this morning following a multi-vehicle collision.

Those travelling were facing delays of up to two hours and tailbacks stretching nine miles after a van and a trailer collided northbound between J21A (Leicestershire) and J22 Leicester earlier this morning. Teams worked to help with recovery, with all lanes bar one closed due to a spillage which occurred as a result of the collision.

Hide Ad
Hide Ad

All lanes have since re-opened to traffic, with the incident now clear. However there are still warnings of some residual delays with normal traffic conditions expected to resumes around 11am.

National Highways: East Midlands said in an update on X (formerly Twitter): "This incident is now clear, and all lanes have re-opened on the #M1 northbound in #Leicestershire between J21 (#Leicester) and J22 (#Markfield) following a collision. "A 45 minute delay remains in the area but should now start to ease. Thanks for your patience this morning."

Related topics:LeicesterLeicestershireDriversTrafficNational Highways

Comment Guidelines

National World encourages reader discussion on our stories. User feedback, insights and back-and-forth exchanges add a rich layer of context to reporting. Please review our Community Guidelines before commenting.