A2 Traffic Today: Car and Motorbike Crash Closes London-Bound Road in Gravesend
CREDIT-KENTONLINE.CO.UK

A2 Traffic Today: Car and Motorbike Crash Closes London-Bound Road in Gravesend

GRAVESEND, Kent — Drivers faced major disruption on the A2 on Wednesday morning after a crash involving a car and a motorbike closed the London-bound carriageway near Gravesend and prompted an air ambulance response.

The collision was reported shortly after 7am on September 16, 2026, close to the A227 Wrotham Road junction and Tollgate Services. The London-bound side was reported shut from around 7.20am as emergency crews worked at the scene, while queues quickly built across the surrounding road network.

The incident also affected motorists travelling coast-bound. Traffic on the opposite carriageway was temporarily stopped so an air ambulance could land safely, causing additional congestion towards Northfleet and Bluewater.

A2 London-bound closed near Gravesend

The main disruption affected the London-bound A2 around the A227 junction serving Gravesend. Early traffic information referred to restrictions between the A227 Gravesend area and the B262 Southfleet section, with the route also described as blocked towards Pepper Hill.

The location is important for both local and longer-distance traffic because the A2 links north Kent with routes towards London and connects with roads serving Gravesend, Strood, Northfleet and surrounding communities.

With the carriageway closed during the morning travel period, vehicles approaching from the M2 direction were caught in substantial queues before reaching the crash scene.

Air ambulance response affected both directions

Although the collision happened on the London-bound carriageway, coast-bound traffic was also stopped for around 20 minutes to allow the air ambulance to operate at the scene.

Traffic information indicated that the coast-bound side was moving again by around 8.15am, although queues remained after the temporary stoppage.

The presence of an air ambulance should not be treated as confirmation of a fatality or a specific level of injury. The initial reports did not provide officially confirmed details about the condition of the motorcyclist or anyone else involved.

There was also no confirmed information establishing the cause of the collision or reporting an arrest during the early response.

Queues stretched towards Strood and Bluewater

The effects of the crash extended well beyond the immediate scene. London-bound congestion was reported stretching back towards M2 Junction 1 at Strood.

On the opposite side, queues developed towards Northfleet and Bluewater while traffic was held for the air ambulance operation.

National Highways information cited during the incident indicated delays of about 60 minutes westbound and 35 minutes eastbound while emergency services were dealing with the collision.

Those figures reflected conditions during the response and could change as restrictions were altered and traffic began to clear.

A2 Gravesend crash timeline

Shortly after 7am: A car and motorbike were involved in a collision on the London-bound A2 near the A227 Wrotham Road junction.

Around 7.20am: The London-bound carriageway was reported closed while emergency crews dealt with the incident.

During the morning response: Both directions were temporarily stopped as the air ambulance attended.

By around 8.15am: Coast-bound traffic was reported moving again after being held for roughly 20 minutes, although congestion continued in the area.

The London-bound carriageway remained the main focus because the collision itself had occurred on that side of the road.

Crash Disrupts Traffic Across Surrounding Roads

The A2 is a major route through north Kent, carrying commuter and regional traffic towards London as well as vehicles travelling between Gravesend, Dartford, Strood and the wider road network.

When traffic is stopped during the morning travel period, queues can quickly spread beyond the immediate closure and place additional pressure on nearby roads.

A similar traffic pattern was seen when an M61 crash caused long delays between Chorley and Horwich, where an initial traffic hold continued to affect journeys after vehicles began moving again.

Drivers have also recently faced disruption after an M3 closure near Winchester caused four-mile queues following a diesel spill. The incidents are unrelated, but both show how quickly traffic can build when a major route is restricted.

Drivers should check the latest A2 conditions

Anyone travelling through Gravesend should check the newest road information before setting out, because closure status and queue lengths can change quickly during emergency and recovery work.

National Highways live travel updates provide current information about incidents, disruptions and delays across England’s motorways and major A roads.

Drivers approaching from Strood or the M2 should allow extra journey time if congestion remains and follow overhead signs, traffic management and instructions from emergency services.

Cause and casualty details remain unconfirmed

The confirmed information from the initial response is that a car and motorbike were involved, emergency services attended, an air ambulance was called and significant traffic disruption followed on the A2 near Gravesend.

However, the cause of the collision had not been officially established in the early reports, and verified details about the identities or medical condition of those involved had not been released.

Until police, ambulance services or another responsible authority publishes further information, claims about serious injuries, a death, arrests or responsibility for the crash should not be treated as confirmed.

Add Swikblog as a preferred source on Google

Make Swikblog your go-to source on Google for reliable updates, smart insights, and daily trends.

Get the Swikblog App
Stay updated with breaking news, trending stories and the latest updates—all in one place.
Get the Swikblog app on Google Play
Free download for Android devices

Comments

No comments yet. Why don’t you start the discussion?

Leave a Reply

Your email address will not be published. Required fields are marked *