Traffic stopped on M6 due to lorry fire caused by crash

Crews working at the scene following the serious incident. Photo: National Highways
Crews working at the scene following the serious incident. Photo: National Highways

The lorry caught fire following a collision. Photo: National Highways

The lorry caught fire following a collision. Photo: National Highways

The Midlands Air Ambulance and all other emergency services are at the scene between Junction 12 for Cannock and Junction 13 for Stafford.

Traffic was held in both directions but the southbound carriageway has now been released.

The northbound carriageway will remain closed for extensive recovery work.

As of 1pm, traffic caught within the closure was being turned around from the rear of the queue. Some traffic near to the crash will soon be moved past the incident.

Long delays of over an hour have been building since the crash.

The lorry caught fire following a collision. Photo: National Highways
The lorry caught fire following a collision. Photo: National Highways
Crews working at the scene following the serious incident. Photo: National Highways
Crews working at the scene following the serious incident. Photo: National Highways
Crews working at the scene following the serious incident. Photo: National Highways
Crews working at the scene following the serious incident. Photo: National Highways

Traffic caught within the closure of the #M6[1] northbound between J12 (#Cannock[2]) and J13 (#Stafford[3]) continues to be turned around from the rear of the queue.

Please await instruction from Police or our Traffic Officers before turning.

This process will take some time. pic.twitter.com/rpZfxJxGef[4]

— National Highways: West Midlands (@HighwaysWMIDS) April 16, 2023[5]

The lorry caught fire following a collision. Photo: National Highways

The lorry caught fire following a collision. Photo: National Highways

More to follow.

References

  1. ^ #M6 (twitter.com)
  2. ^ #Cannock (twitter.com)
  3. ^ #Stafford (twitter.com)
  4. ^ pic.twitter.com/rpZfxJxGef (t.co)
  5. ^ April 16, 2023 (twitter.com)