M20 lorry crash on coastbound side between Detling Hill and Bearsted near Maidstone sees drivers facing heavy delays

Drivers are facing heavy delays on the M20 after an accident which saw a lorry come off the motorway and crash into trees.

The HGV is believed to have crashed through a barrier on the coastbound side between Junction 7 (Detling Hill[1]) and Junction 8 (Bearsted[2]).

Drivers are facing delays of at least one mile on the carriageway

Drivers are facing delays of at least one mile on the carriageway

Drivers are facing delays of at least one mile on the carriageway
Traffic is building on the M20 coastbound between Junction 7 and 8. Picture: National Highways

Traffic is building on the M20 coastbound between Junction 7 and 8. Picture: National Highways

Traffic is building on the M20 coastbound between Junction 7 and 8. Picture: National Highways

The congestion stretches back to Junction 6 (Blue Bell Hill).

Traffic was temporarily held while the emergency services worked at the scene.

One lane remains blocked with motorists facing queues of at least one mile.

A spokeswoman for South East Coast Ambulance Service (SECAmb) said: “We were called shortly after 12.30pm to reports of a RTC involving a lorry between Junctions 7 and 8 on the M20.

“Crews arrived on scene and provided medical treatment to one individual.”

M20 J7 – J8 Coastbound: 1 lane of 3 blocked due to an RTC on the Coastbound carriageway between J7 (A249 Detling Hill) and J8 (A20 Hollingbourne). Emergency services are in attendance, please use caution on the approach and expect delays: https://t.co/5IY9w2oncN[3]

— KCC Highways (@KentHighways) April 12, 2024[4]

A police spokesman said: “This was reported to us at 12.30pm. A lorry collided with a barrier.

“Police and ambulance crews are in attendance and there are no serious injuries.

“Delays should be expected whilst the scene is cleared of any debris.”

Tune into kmfm for traffic updates

References

  1. ^ Detling Hill (www.kentonline.co.uk)
  2. ^ Bearsted (www.kentonline.co.uk)
  3. ^ https://t.co/5IY9w2oncN (t.co)
  4. ^ April 12, 2024 (twitter.com)