Crash on A12 near Feering causes severe delays for drivers
Summarised from 3 outlets · 5 reports · Updated 30 Oct, 21:51 · Archive
A crash on the A12 London-bound near Feering at junction 22 is causing severe delays, with queues stretching back around eight miles.
A crash on the A12 London-bound carriageway has caused severe delays for drivers. The incident happened at junction 22, Witham north, near Feering.
Queues are stretching back towards junction 24, Feering, with delays extending for around eight miles on the London-bound carriageway following the collision.
The incident is also affecting the M11 northbound, where all traffic is being held between junction 8 for the A120 and Stansted Airport and junction 9 for the A11 at Saffron Walden.
The emergency services have been contacted for more information regarding the crash and when normal traffic flow might resume.
How it is being reported
- Crash on busy stretch of A12 causing miles of queuesA crash on the A12 near Feering is causing severe delays for drivers heading Londonbound.Echo (Basildon) · 30 Oct, 15:16
- Crash on busy stretch of A12 causing miles of queuesA crash on the A12 near Feering is causing severe delays for drivers heading Londonbound.Colchester Gazette · 30 Oct, 15:16
- Crash on busy stretch of A12 causing miles of queuesA crash on the A12 near Feering is causing severe delays for drivers heading Londonbound.Brentwood Guardian · 30 Oct, 15:16
- A12 partially blocked with delays building before rush hourThe A12 London-bound is partially blocked after reports of the incident just after Boreham Interchange.Colchester Gazette · 28 Oct, 16:44
- A12 partially blocked with delays building before rush hourThe A12 London-bound is partially blocked after reports of the incident just after Boreham Interchange.Echo (Basildon) · 28 Oct, 16:44
In this story: A12 · Feering · Witham · M11 · Stansted Airport · Saffron Walden
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)