M1 Yorkshire RECAP: Motorway closed after vehicle fire with standstill traffic

A major UK motorway was hit with disruption this morning following a vehicle fire[1]. Three lanes of the M1 were closed following the incident, which unfolded just after 8am and caused delays between junction 33 for Sheffield and junction 34 for Meadowhall. Traffic monitoring system Inrix warned of delays caused by a large vehicle fire in an update posted just after 8.10am.

11:07Joe Smith

Fire service statement on 'HGV' fire

A spokesperson for South Yorkshire Fire and Rescue Service said: "We were called at 7:58am to a HGV on fire on the M1, J33-J34 northbound.

Three fire crews from Parkway, Aston and Rotherham stations attended the incident. There were no reports of any casualties. "Crews left the scene at 9:27am.

"The fire is believed to have started accidentally."

10:10Joe Smith

Traffic 'moving slowly'

An update from the Inrix traffic monitoring system said: "One lane closed and slow traffic due to vehicle fire on M1 Northbound from J33 A630 (Catcliffe / Sheffield / Rotherham) to J34 A6102 Shepcote Lane (Meadowhall)."

09:59Joe Smith

Traffic cameras show tailbacks

Earlier images from traffic cameras near the affected area show lengthy traffic queues. Despite three of four lanes now being open again, National Highways has still warned drivers to expect delays.

A vehicle fire on the M1 Northbound from J33 A630 has caused long delays and closed three lanes (TrafficCameras.com)09:55KEY EVENT

Drivers told to allow extra time

Drivers have been warned to allow extra time for their journeys today as recovery crews work at the scene of an earlier vehicle fire which briefly saw three lanes shit while crews tackled the blaze.

There's now 1 (of 4) lanes closed on the #M1[2] in #SouthYorkshire[3] northbound between J33 (#Rotherham[4]) and J34 (#Sheffield[5]) following a HGV fire. Recovery services and service providers in attendance.

Delays on approach, please allow extra time for your journey. pic.twitter.com/qleHGFtanC[6]

-- National Highways: Yorkshire (@HighwaysYORKS) March 10, 2026[7]09:48Joe Smith

Latest from Inrix

The latest from traffic reporting system, Inrix, reads: "Long delays and one lane closed due to vehicle fire on M1 Northbound from J33 A630 (Catcliffe / Sheffield / Rotherham) to J34 A6102 Shepcote Lane (Meadowhall). Congestion to J32 M18 (M18 interchange). Lanes two, three and four are open now."

09:38Joe Smith

Traffic map shows congestion

Traffic maps from Google show the state of the roads around the site of the incident, near the Meadowhall junction of the M1 as fire crews attend reports of a large vehicle fire in the area.

(Google Maps)09:34KEY EVENT

Three lanes now open

One lane remains closed and three lanes are open on the M1 northbound between junctions J33 and J34 according to the latest update from National Highways.

There are currently delays of around 20 minutes against expected traffic with latest estimates saying it could be 1pm before the tailbacks start to clear.

09:29Joe Smith

Emergency services contacted

South Yorkshire Fire and Rescue Service has been contacted for more information. We will bring you an update as soon as we hear more.

09:29Joe Smith

Traffic cameras show fire engine

Images from motorway traffic cameras show fire crews racing to the scene after three lanes of the M1 have been closed as the result of a vehicle fire this morning, according to reports.

Motorway traffic camera still (TrafficCameras.com)09:29KEY EVENT

Fire crews race to the scene

Fire crews have been spotted on traffic cameras racing to the scene. The latest update from traffic reporting system, Inrix, says: "Long delays and three lanes closed due to vehicle fire on M1 Northbound from J33 A630 (Catcliffe / Sheffield / Rotherham) to J34 A6102 Shepcote Lane (Meadowhall).

Congestion to J32 M18 (M18 interchange).

One lane has been re-opened."

References

1. ^ fire (www.mirror.co.uk)
2. ^ #M1 (twitter.com)
3. ^ #SouthYorkshire (twitter.com)
4. ^ #Rotherham (twitter.com)
5. ^ #Sheffield (twitter.com)
6. ^ pic.twitter.com/qleHGFtanC (t.co)
7. ^ March 10, 2026 (twitter.com)