Two incidents bring traffic to standstill on M25 in Essex
Summarised from 3 outlets · 9 reports · Updated 20 Nov, 11:28 · Archive
Two separate incidents have caused traffic to be held on different sections of the M25 motorway in Essex.
Two separate incidents on the M25 in Essex have caused significant disruption to traffic on the busy motorway. All traffic was temporarily held on the anticlockwise carriageway between Junction 28 for the A12 at Brentwood and Junction 27 for the M11, with the incident reported to be around two miles after Junction 28.
A second incident also affected the clockwise carriageway at the QE2 Bridge. Traffic was temporarily stopped following a crash involving a lorry and a car between Junction 31 for the A1306 at Lakeside and Junction 1a for the A206 at Dartford.
Congestion from the second incident stretched back to around a mile before Junction 30 for the A13 at Lakeside. Delays were reportedly worsened by motorists slowing down to look at the scene of the incident.
The two incidents affected important sections of the M25 used by motorists travelling through south and west Essex, including routes around Brentwood, Thurrock and the Dartford Crossing. The combined effect of both incidents caused major disruption across the motorway network in the area.
Drivers were advised to allow additional time for their journeys while the incidents were being dealt with. Motorists were also urged to consider exiting the motorway to avoid the congestion on these key routes.
How it is being reported
- Live updates as M25 traffic grinds to a halt in places after two incidentsAll traffic has been held on two key stretches of the M25; the anticlockwise from Junction 28 Brentwood and the clockwise at the Dartford Crossing QE2 Bridge.Brentwood Guardian · 20 Nov, 11:13
- Live updates as M25 traffic grinds to a halt in places after two incidentsAll traffic has been held on two key stretches of the M25; the anticlockwise from Junction 28 Brentwood and the clockwise at the Dartford Crossing QE2 Bridge.Echo (Basildon) · 20 Nov, 11:13
- Live updates as M25 traffic grinds to a halt in places after two incidentsAll traffic has been held on two key stretches of the M25; the anticlockwise from Junction 28 Brentwood and the clockwise at the Dartford Crossing QE2 Bridge.Colchester Gazette · 20 Nov, 11:13
- Major Essex route facing CHAOS as two incidents bring all traffic to a stopM25 traffic chaos as crashes halt both carriageways near Brentwood, M11 and QE2 Bridge, causing delays around Thurrock and Dartford Crossing; drivers warned.Echo (Basildon) · 20 Nov, 11:11
- Major Essex route facing CHAOS as two incidents bring all traffic to a stopM25 traffic chaos as crashes halt both carriageways near Brentwood, M11 and QE2 Bridge, causing delays around Thurrock and Dartford Crossing; drivers warned.Colchester Gazette · 20 Nov, 11:11
- Major Essex route facing CHAOS as two incidents bring all traffic to a stopM25 traffic chaos as crashes halt both carriageways near Brentwood, M11 and QE2 Bridge, causing delays around Thurrock and Dartford Crossing; drivers warned.Brentwood Guardian · 20 Nov, 11:11
- Key stretch of the M25 CLOSED with delays buildingM25 closure: clockwise carriageway shut between Junction 24, Potters Bar, and Junction 25, Waltham Cross, on Essex border, causing delays and 15mph speeds.Colchester Gazette · 20 Nov, 08:31
- Key stretch of the M25 CLOSED with delays buildingM25 closure: clockwise carriageway shut between Junction 24, Potters Bar, and Junction 25, Waltham Cross, on Essex border, causing delays and 15mph speeds.Echo (Basildon) · 20 Nov, 08:31
- Key stretch of the M25 CLOSED with delays buildingM25 closure: clockwise carriageway shut between Junction 24, Potters Bar, and Junction 25, Waltham Cross, on Essex border, causing delays and 15mph speeds.Brentwood Guardian · 20 Nov, 08:31
In this story: M25 · Essex · Brentwood · Dartford Crossing · Lakeside · Potters Bar · Waltham Cross · AA
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)