M25 crash causes 45‑minute delays for commuters between J16 and J17
Two lanes closed on the clockwise carriageway near Gerrards Cross, with queues reaching Heathrow and knock‑on congestion on the M40.
Trust 30Craft 57Hype 65How this was reported ▾
The central claim is attributed to National Highways, but no named individuals or documents are cited.
How well corroborated and evidenced the reporting is. Higher is better.
The report provides specific details on the incident and its impact, but lacks quotes or a right of reply.
Context, balance and separation of fact from comment. Higher is better.
The headline uses 'LIVE' and 'chaos' which is sensationalised for a traffic incident.
How far presentation runs ahead of substance. Lower is better.
1 source assessed · methodology
National Highways confirmed that a collision on Tuesday morning blocked the clockwise side of the M25 close to the Chalfont Viaduct. The crash forced the closure of two of the four lanes between junction 16 and junction 17. Drivers travelling eastbound towards London encountered a single lane of traffic, while the opposite carriageway continued to operate normally.
Location and extent of the crash
A2 and M25 drivers face four nights of closures
Overnight works will shut sections of the A2 between London and Kent and parts of the M25 orbital route.
The incident occurred near Gerrards Cross, a settlement in Buckinghamshire that lies just north of the M25’s western arc. The crash site sits between junction 16, which serves the A404, and junction 17, which connects to the A404 and A41. National Highways reported that the impact forced the closure of the two inner lanes, leaving only the outer lane for traffic in each direction.
Impact on traffic flow
By 8 am, traffic monitoring showed queues extending back to Heathrow Airport and as far as junction 13 at Staines. Drivers reported waiting times of about 45 minutes before reaching the next open lane. The reduced capacity meant that vehicles were forced to travel at a reduced speed, further lengthening travel times for commuters heading into central London or out towards the west.
M25 Disruption: Two Stretches Affected by Crashes
Motorists face significant delays as multiple incidents cause lane closures on key sections of the orbital route.
Effect on other routes
The blockage on the M25 also produced secondary congestion on the M40, which runs parallel to the M25 for part of its route. National Highways noted that vehicles attempting to avoid the M25 bottleneck were diverting onto the M40, adding to travel times for those heading into the capital from the west. No additional lane closures were reported on the M40 itself.
Next steps and advice for drivers
National Highways said crews were on site working to clear the crash and restore the closed lanes. Drivers were urged to follow live traffic updates, consider alternative routes such as the A41 or the M40, and allow extra travel time. The council did not announce a specific time for full lane reopening, but indicated that progress would be communicated through the National Highways website and local radio bulletins.
Questions this report answers
+What caused the delays on the M25 this morning?
A collision on the clockwise carriageway near Gerrards Cross forced the closure of two of four lanes between junction 16 and junction 17. The reduced capacity created queues that stretched back to Heathrow and junction 13, resulting in delays of about 45 minutes at 8 am.
+How long were drivers waiting on the M25?
National Highways reported that, as of 8 am, the average delay for vehicles on the affected stretch of the M25 was roughly 45 minutes. The delay reflected the time needed to navigate the single open lane while queues extended back to Heathrow and Staines.
+Which lanes were closed and where?
Two inner lanes on the clockwise side of the M25 were closed between junction 16, near the A404, and junction 17, near the A41. Only the outer lane remained open for eastbound traffic, while the opposite carriageway continued to operate with all four lanes.
+Did the crash affect any other roads?
Yes, the incident caused knock‑on delays on the M40 heading towards London. Drivers attempting to avoid the M25 congestion diverted onto the M40, adding travel time for those using that route. No lane closures were reported on the M40 itself.
WE FILE
No invented reporter. No hidden source trail.
The London Travel Desk assembled this report from the outlets listed below. Language-model drafting is reviewed under human editorial supervision, with scoring notes and corrections kept visible.
More Coverage in Roads & Driving