Better information for your journey
The National Traffic Control Centre collects real-time information on road conditions.
How We Manage Our Roads
In this section you can find out more about how we manage and maintain these roads and plan for the future
The Project Control Framework
On 1st April 2008 we launched the Project Control Framework. The Framework sets out how we, together with the Department for Transport, manage and deliver major improvement projects.
Traffic news on your desktop
Helpful ways to access the latest traffic information when you need it.
Existing Conditions
2.1 General
This section of the report describes the existing A2 within the limits of Phase 1 of the Scheme. The extent of Phase 1 and the location of existing features are shown on Figure A1.2 in Appendix 1. This figure includes chainages at 500m intervals. The chainage value (CH) is a system for referencing specific points along the route and will be used throughout this report. Phase 1 starts at CH200 and ends at CH4300.
2.1 General
Between the junction with the M25/A282 and the junction with the M2, the A2 is predominantly a dual three lane all-purpose carriageway with hardshoulders. A 2.1km section of the coast bound carriageway between the Bean Junction coast bound entry slip road and Pepperhill Junction (CH1800 to CH3900) was widened to four lanes, in 1998, under a Section 278 Agreement (Highways Act) as part of the Bluewater development scheme.
At the western end of Phase 1, the Bean Junction connects the B255 to the A2. This junction serves the Bluewater development to the north and Bean village to the south. Access to the A2 in the coast bound direction from Bean junction is via the A296 which joins the A2 at the Swanscombe Footbridge where the coast bound carriageway becomes four lanes wide. At the eastern end of Phase 1, the Pepperhill Junction serves the B262 to the south and the A2260 to the north.
