Cambridgeshire Guided Busway

From Infogalactic: the planetary knowledge core
Jump to: navigation, search
Cambridgeshire Guided Busway
200px
Cambridge Busway Stagecoach Scania N230 Cropped.jpg
Guided busway during trials, 2009
Overview
Owner Cambridgeshire County Council
Locale Cambridgeshire, United Kingdom
Transit type Guided busway
Website www.thebusway.info
Operation
Began operation 7 August 2011
Operator(s) Whippet Coaches
Stagecoach in Huntingdonshire
Technical
System length 16 miles (25 km)

The Cambridgeshire Guided Busway (also Cambridge-Huntingdon Rapid Transit Scheme, locally the Busway or the guided bus) connects Cambridge, Huntingdon and St Ives in the English county of Cambridgeshire. It is the longest guided busway in the world,[1][2] overtaking the O-Bahn Busway in Adelaide, South Australia.[3][4][5]

Two guided sections make up 16 miles (25 km) of the route. The northern section, which uses the course of the Cambridge and Huntingdon railway, runs through the former stations of Oakington, Long Stanton and Histon. The southern section, which uses part of the former Varsity Line to Oxford, links Cambridge railway station, Addenbrooke's Hospital and the park and ride site at Trumpington, via housing on the Clay Farm site.

Services are operated by Stagecoach in Huntingdonshire and Whippet Coaches, which have exclusive use of the route for five years in exchange for providing a minimum service frequency between 07:00 and 19:00 each week day.[6] Specially adapted buses are used: the bus driver does not need to hold the steering wheel on the guided sections of the busway. A total of 2,500,000 trips were made in the first year of operation.

Proposed initially in the 2001 Cambridge-Huntingdon Multi-Modal Study, which recommended widening of the A14 road and construction of a guided busway along the old railway lines, construction began in March 2007 and it was opened on 7 August 2011 after a succession of delays and cost overruns.[2]

The original cost estimate of £64 million rose to £181 million by December 2010.[7] An independent review of the project was announced on 21 September 2010,[8][9] in which the Cambridge MP Julian Huppert at the time described the busway as a "white elephant".[10] A court case with BAM Nuttall, the main contractor, was settled by Cambridgeshire County Council in August 2013.[11]

Overview

The scheme links Cambridge, in East Anglia, with St Ives, Huntingdon and Northstowe (a proposed new town) to the north-west, and with the M11 motorway to the south. The route includes two sections of guided operation, a bus-only road and other places with on-street operation in conventional bus lanes. New park and ride sites have been built at Longstanton and at St Ives, with a tarmac cycle track/bridleway alongside some sections of the route.[6] The final scheme includes bus priority and real-time passenger information system displays at busway bus stops; and subsequent separate funding and works to better link those stops to local businesses for pedestrians and cyclists.[12]

A total of 2,500,000 trips were made in the first year of operation, which Atkins reported was 40% higher than the predicted figure. Bus ridership along the corridor was estimated to have increased by 33% over the same period.[13] Before opening, the contractor had predicted that an estimated 11,500 journeys per day would be made on the busway.[14] The scheme was predicted to cause a direct reduction in traffic on the busy parallel A14 road of 5.6% (rising to 11.1% with the new Park & Ride sites), although as other traffic re-routes to the freed-up road space from other parts of the local road network, the net reduction is predicted to be 2.3%. The overall scheme was "not intended to solve the congestion problems on the A14" by itself, but will rather have an overall effect across the local road network, and be complementary to planned improvements on the A14.[15]

Route

Cambridgeshire Guided Busway
East Coast Main Line
Huntingdon railway station National Rail
Huntingdonstreet running
Somershamstreet running
St Ivesstreet running
St Ivespark and ride
St Ives Viaduct(River Great Ouse)
Fen Drayton Lakes
Swavesey
Longstantonpark and ride
Northstoweproposed development
Oakington
Histon and Impington
A14 road
Orchard Park East
Orchard Park West
Cambridge Regional College
Cambridge Science Park
Cambridgestreet running
to North and East
Cambridge railway station National Rail
Hills Road
Long Road
Addenbrooke's Hospital
Shelford Road
Trumpington Cutting (single track)
Hauxton Road
Trumpingtonpark and ride
to London
Cambridgeshire Guided Busway network between Huntingdon (top-left) and Cambridge (bottom-right)

Starting at Huntingdon railway station and town centre, buses travel on normal roads to St Ives. From here the busway follows the path of the former Cambridge and Huntingdon railway to a new park and ride site south of the town, where it becomes guided. The buses stop at Swavesey, Longstanton, Oakington and Histon, with a request stop for the nature reserve at Fen Drayton. Should a proposed new town at Northstowe be built, further stops would be opened, with the Northstowe developers Gallagher Construction being encouraged to build the busway through the development beforehand.[16]

Upon entering Cambridge the route diverges. One route has stops at Cambridge Regional College and Cambridge Science Park, before it rejoins the road network into central Cambridge. The other joins the road network at Orchard Park (formerly Arbury Park), before continuing to the city centre. The two forks converge at Cambridge bus station for the journey to Cambridge railway station. Beyond Cambridge railway station the buses are guided along the former Cambridge-Oxford railway (The Varsity Line) south to Addenbrooke's Hospital and Trumpington Park and Ride. This section last saw a scheduled passenger train in 1967.[17]

Infrastructure

Wheel-on-kerb method: on the guideway, small wheels touching the kerbs keep the buses in the centre and the bus driver lets go of the steering wheel.

The busway is designed for buses travelling at Lua error in Module:Convert at line 1851: attempt to index local 'en_value' (a nil value)., slowing to Lua error in Module:Convert at line 1851: attempt to index local 'en_value' (a nil value). where it crosses public highways.[18] Bus drivers are asked to drive as they would do on a normal road.[19] Guidance is achieved using the guidewheel-on-concrete-kerb method, with the busway constructed from pre-cast concrete sections that are 15 metres (49 ft) long and 2.6 metres (8.5 ft) wide.[20] Additionally, the guide wheels will aid close positioning at slightly modified bus stops within the on-street sections.[21]

The busway is 6 metres (20 ft) wide, consisting of two 2.6-metre wide tracks separated by a central reservation of 80 centimetres (31 in). Between Cambridge and St Ives there is also a 4-metre (13 ft) wide (maximum) bridleway/maintenance track to one side and a 70-centimetre (28 in) evacuation strip to the other creating a total width of 10.7 metres (35 ft). Where necessary it is narrower; for example through the Trumpington cutting where there is a single busway with a narrower maintenance-only track giving a total width of approximately 6.3 metres (21 ft).[18] In 2010, proposals were made to reduce the width of the bridleway, narrowing it to 3 metres and increasing the height in order to combat flooding.[22] Elevated sections have two evacuation strips at busway level with the bridleway/maintenance track at the base of the embankment.[citation needed] The bridleway is useable by people on foot, bicycle and horse.

The 6-metre (20 ft) width of the busway is narrower than the 9.3-metre (31 ft) width of a single-carriageway rural all-purpose road built to 2009 standards (excluding attendant verges and footpaths/cyclepaths in both cases).[23] A conventional road would have been too wide to fit on top of existing railway embankments and across the under-bridges along parts of the route.[24] The maintenance track is either adjacent to the busway on flat land, or to one side at the foot of the former railway embankments—the combined width of the maintenance track and the busway being considerably wider than that of the railway it had replaced. To negotiate Trumpington Cutting on the southern section, a narrower maintenance track was required, along with the use of a bi-directional single track busway in order to fit within the width of the former double-track railway line.[25] The southern section will be restricted to single-decker buses.[25] In May 2012 the County Council received a petition calling for better night-time lighting for the bridleway alongside the southern section, and the need for this was subsequently acknowledged by the Council.[26] Work on lighting was completed in autumn 2015.[27]

Services

Stagecoach Route B bus travelling from Cambridge on the first full day of service on the busway, 7 August 2011.

Two operators, Stagecoach[28] and Whippet Coaches, committed to buying new buses and running commercial services on the scheme. The council had previously held talks with Cavalier (Huntingdon and District) and another operator.[29] As with all other UK busway schemes, the Council owns the infrastructure, allowing bus operators to use it on their registered services, subject to quality contracts specifying vehicle and service standards (Euro IV and low-floor buses).[30] During peak hours of 07:00–19:00 Monday–Saturday operators are charged for using the busway.[6][30]

Originally seven buses per hour ran between St Ives and Cambridge Science Park during the day, reducing to hourly in the evenings and on Sundays. Figures published during 2004 by Cambridgeshire County Council proposed that it would begin operation with six buses per hour and build up to 20 buses per hour into Cambridge during peak periods by 2016.[31]

In January 2012, a report to Cambridgeshire County Council suggested opening up the operation of the five Park & Ride sites to companies in addition to just Stagecoach Cambridgeshire in a bid to recover some of the £617,000 annual cost.[32]

Routes A and B
Interior of a single-decker Cambridgeshire Guided Busway route A bus approaching Addenbrooke's Hospital.

Stagecoach controls 86% of Cambridgeshire's bus services[32] and runs Routes A and B between St Ives and Cambridge along the busway, with extensions to Huntingdon railway station. The journey time from St Ives bus station to the Cambridge Science Park is 23 minutes plus 15 minutes into Cambridge city centre, roughly 38 minutes in total.[33] Stagecoach's previous three-times per hour Service 55 between Cambridge and St Ives had been timetabled at 30–37 minutes.[34] The promoters of the scheme predicted that journey times via the busway might be more consistent and reliable, due to buses avoiding the busy A14 road.[31]

To operate their services, Stagecoach ordered ten Eclipse/B7RLE single-decker buses, to be manufactured by Wrightbus and Volvo, and ten Alexander Dennis Enviro400/Scania N230UD double deckers. All the specially-branded vehicles are equipped with leather seats, air chill or air conditioning, real time information, and free Wi-Fi.[28] The new buses were deployed on Stagecoach's other services prior to the opening of the busway, having cost the operator a total of £3 million[35] plus £1 million in staffing and training costs.[36]

Less than a month after opening, Stagecoach announced that the Sunday service would be increased to three buses per hour to St Ives, up from one per hour. One Sunday service per hour would continue to Huntingdon.[37] From the summer of 2012 both Route A and B will increase to every 15 mins, with all buses extended to St Ives town centre. Andy Campbell, Stagecoach Cambridgeshire’s managing director, said: "I think 1 million customers in four-and-a-half months showed there was a desire to use the busway. This is a positive step which will hopefully increase patronage even further."[38]

Route C
A Go Whippet Route C bus leaving St Ives on 7 August 2011.

Whippet Coaches operate Route C from Somersham to Cambridge centre using a mixture of rural roads, Cambridge city centre roads and the northern busway between the St Ives park and ride site and the outskirts of Cambridge. Journey time from Somersham to Cambridge city centre is scheduled at 57 minutes, with no Sunday service.[39] Whippet spent a total of £420,000 on three buses (£140,000 each).[35] Less than a month after opening Whippet announced that they would adjust their sporadic Sunday service between Cambridge and Somersham, increasing it to one service per hour.[37]

Ticketing

On the busway passengers are required to purchase their tickets before boarding[40] from one of seventeen ticket issuing machines compatible with ITSO smartcards.[41] Cambridgeshire Country Council stated that multi-operator ticketing would be supported, allowing passengers to board the first bus that arrived, stating that such a ticket would be a first, but would take a while to perfect. Single tickets from one operator will not be valid on another operator's bus, but a multi-operator smartcard can be purchased.[42]

History

Planning

In 2001 the Cambridge-Huntingdon Multi-Modal Study (CHUMMS) recommended widening of the A14 road and building a guided busway along the old Cambridge and Huntingdon railway,[43] which had been closed to passengers since 1970 and to all traffic since 1993.[44] Since closure there had been proposals to reinstate the rail service, and for a light railway network, a bus lane, a road with limited access, a bus-way, a cycle path and a nature walk.[44] A local group, CAST.IRON, was set up in July 2003 after being inspired by the Wensleydale Railway to promote and undertake reinstatement of the route for trains and to resist other proposals, referring to the guided bus as the 'misguided bus'.[45] A private consortium that had proposed a guided bus scheme, SuperCAM, abandoned their plans in 2003.[46] Arup prepared the Transport and Works Act (TWA) application presented in late 2003.[47][48]

A public inquiry was held in September–October 2004. The scheme was supported by five bus and coach operators, and 20 other organisations and individuals.[49] A total of 2,735 objections were received:[18] from local councils, public bodies, transport interests, local pressure groups and individuals who criticised the Environmental Impact Assessment, supported the rail alternative or objected to the scheme in principle.[50] The scheme was approved by the Government in December 2005.[51][52]

Construction

In March 2007, the then Transport Secretary Douglas Alexander officially opened a manufacturing plant at Longstanton that would produce the 6,000–7,000 concrete beams for the busway.[53][54] Each beam was 350 millimetres thick with a further 180-millimetre lip for the glide wheels to press against.[54] A total of 50,000 tonnes of concrete was cast to a precision of plus or minus one millimetre.[54] Supports below the beams were under-pinned by 2,150 piles along a 2.5 miles (4 km) length of the busway.[55]

In the same year a viaduct of maintenance-free steel was built over the River Great Ouse as a replacement for the 200-tonne wrought-iron railway viaduct removed in 2007.[56][57] There would later be a dispute between the Conservative-controlled County Council and opposition Liberal Democrat councillors as to whether the structure was structurally sound,[58] with a claim that water draining off the track over the viaduct could lead to crumbling.[59]

Construction work under way near Histon, Cambridgeshire in 2008.

In March 2008 existing guided vehicles were trialled along a section near Oakington.[60][61] The vehicles tested included a Wrightbus-bodied single decker owned by FirstGroup, a Plaxton President-bodied Dennis Trident 2 double decker from Lothian Buses, and a white Alexander Dennis Enviro500 triple-axled double decker. The test vehicles were fitted with sensors to assess vibration levels and ride quality. Hot weather testing of the track took place during May/June 2010.[62][63] In addition to the bus fleet, Cambridgeshire County Council trialled and purchased a specially adapted "guided gritter" lorry for use during periods of cold weather, which will spray salt water rather than rock salt.[64][65][66][67][68][69][70] In November 2011 this was augmented with a customised "Multihog" gritter/snowplough vehicle from Ireland designed for clearing the accompanying maintenance track and cycleway.[69][70][71][72][73] The Multihog is powered by 90-horsepower engine allowing it to travel at up to 40 km/h and features a brine tank, rather than solid grit.[71][74][75]

By August 2008 approximately 6 miles (10 km) of the busway had been constructed, between Longstanton and Milton Road (Science Park).[citation needed] On 30 November 2009, road signs directing traffic from the A14 towards the future busway park and ride sites started to be installed.[76] Other signage related to the busway had required subsequent height adjustments,[77] and spelling corrections.[78][79][80][81][82] Trees had also blown over, blocking the busway route near Swavesey.[83] The twelve junctions on the route fitted with bus priority traffic signals were tested on 16 December 2010 and worked as expected.[84][85][86]

Delays

Concrete beam construction of the main busway route. An estimated 6,000 to 7,000 concrete beams were made for the busway.

In January 2009 it was announced that the scheduled opening of the scheme had been delayed until late summer 2009 owing to bad weather and flooding in the Fen Drayton area. As a result of complications with a bridge at Hills Road in Cambridge, traffic restrictions there continued throughout the summer of 2009.[87] Flooding and drainage issues affected the limestone-covered cycleway during late 2009[88] and early 2010.[89]

In August 2009 a further delay until late November 2009 was announced for the opening of the northern section, with no date given for the southern section.[90][91][92]

On 16 November 2009 the project was delayed for the third time when Cambridgeshire County Council announced that the northern section would not open on the previously advertised date of 29 November 2009.[93] An opening date of "the end of the year" 2009 for the northern section was announced later in the same month,[94] followed four days later by "hopefully in the new year [2010]".[77] Initial busway services would only reach Huntingdon railway station and not serve Hinchingbrooke Hospital as had originally been promoted during the public inquiry;[95] neither would they continue southwards to Cambridge railway station.

In January 2010, the contractors and Cambridgeshire County Council were still in discussions about what required finishing.[96] During February 2010 the directors of both the signed-up bus operators—Andy Campbell of Stagecoach in Cambridge, and Peter Lee of Whippet coaches—expressed their companies' frustrations at the busway not being usable by the new buses they had bought to run on it.[35] Shortly afterwards Stagecoach altered the slogan displayed on their fleet of buses for the busway, changing it from reading "I'll be on the busway soon, will you?" to a new slogan of "Will I be on the busway soon?".[97][98][99] In the same month, South Cambridgeshire District Council demanded of Cambridgeshire County Council a comprehensive public statement giving clarity over rising costs.[100] In mid-June 2010, none of the listed outstanding issues had been fixed[101] and a public review was announced.[102]

At the start of July 2010, it was reported that that neither section would open before 2011;[103] the bus operators reacted to the news angrily, suggesting that they might seek to reduce the minimum level of service that had been previously committed to.[36] At a council meeting on 9 July 2010, a decision was taken to concentrate on completion of the southern section in order to get the whole route opened, rather than aiming for a phased introduction.[104] During late September 2010 BAM Nuttall missed deadlines for providing construction certificates needed by the Council, forcing it to begin its own inspections.[105]

Trials

A Stagecoach Route B bus prepares to depart from St Ives to Cambridge on the launch day 7 August 2011.

On 21 April 2011 the busway was officially handed over to Cambridgeshire County Council, triggering a 28-day period for any remedial works be undertaken by BAM Nuttall.[106] This period expired without BAM Nuttall having completed any of the required work. The County Council contracted Jackson Civil Engineering to finish the busway, at BAM Nuttall's expense, with a view to opening the busway in August 2011.[107] The County Council served a legal notice on BAM Nuttall that they were not willing to pay for the budget overrun.[108]

A number of preview trials of the busway were held, during which some problems were encountered, particularly with cyclists using the busway.[109] In one incident a cyclist cycling on the guide beams, rather than the cycle path next to the busway, was struck by a bus coming in the opposite direction.[110] Trials of recovery procedures should a bus break down were also held, with the test finding that a stranded bus could be connected up and removed within five to ten minutes of a specially-adapted breakdown vehicle reaching the scene.[111] During one preview journey held for journalists on 28 July 2011, Hugh Morris of the Cambridge First newspaper staged a race between the guided bus and a car travelling from Cambridge to St Ives to see which was quickest to reach the end of the track. The car beat the bus by ten minutes, although he noted that the trip had not been held during rush hour, during which the A14 road is noted for congestion.[112] A journey from St Ives to the Cambridge Science Park was found to take 20 minutes.[1]

Operation

Car traps

The busway and cycle track officially opened to the public on 7 August 2011.[1][113] The first guided bus left St Ives at 09:00 after the busway had been opened by Andrew Lansley MP.[113] In the first seven days, 55,895 trips were made,[114] leading to the operators providing additional buses on their services.[115] Over the first four weeks the average was 52,227 journeys (224,054 total).[116][117][118] Footfall and trade at businesses in the villages increased as a result,[119] with the same increase reported by market traders and shopkeepers in St Ives[120] As a bridleway, horse riders can also use the maintenance track adjacent to the northern guided section providing a traffic-free route between the villages.[121]

Work began at the end of July 2011 on improving the park and ride facilities at Longstanton. Construction work included a £430,000 passenger waiting room and exhibition centre, for the adjacent Northstowe development.[122] The co-building subsequently won an award at the 2012 Green Apple Built Environment and Architectural Heritage Awards.[123][124] On 12 January 2012, the busway celebrated its one millionth passenger.[125][126]

The intersections of the busway with the regular roads are equipped with prominently signed "car traps" to prevent motorists driving onto the guide beams and interfering with the bus traffic.

Construction costs

Construction of the bridge over the railway line near Addenbrooke's Hospital, September 2008.

The project was budgeted to cost £116.2 million,[127] with central government providing £92.5 million.[128] Cost-benefit analysis of the scheme had variously assessed the expected ratio as 4.84,[129] 2.28 (1998 prices)[18] and 1.968,[129] (a higher ratio is better), with the cost rising from an initial estimate of £54 million.[129] In December 2008, the County Council assessed the financial risks of the project as "high"; None of the £12.7 million funding—out of £23.7 million—due to come from property developers had been received by the promoters.[130] In November 2009 the backers of the "cb1" redevelopment scheme around Cambridge railway station frontage, Ashwell Property Group, had been due to make their £927,000 contribution towards the busway scheme, but were given permission to defer, and entered administration in December 2009.[131] The taxpayer was expected to have to make up any funding shortfall.[130] Cambridgeshire County Council announced it was budgeting £1 million per year to cover potential ongoing costs associated with the busway,[132][133] through the reorganisation of other transport related budgets.[134]

Repayments for the loans and associated interest would then be recovered from the contractors and future housing developers after the scheme had been completed.[135] Contributions from developers were also used to pay for artworks and time capsules along the route.[136][137]

BAM Nuttall dispute

The busway between Oakington and Longstanton. The cycle path is visible on the left of the image.

In 2008, BAM Nuttall claimed that it would cost more than the original budgeted amount to finish the work,[138] perhaps £6 million more.[139] Another report[140] suggests that the overrun could be £30 million on a construction cost of £90 million. Cambridgeshire County Council stated that it had been confident that the scheme would come in on budget because of the terms of its contract with BAM Nuttall.[141] By December 2009, the project had been forecasted to be £1.3 million over budget,[132][133][136] the Council's extra liabilities being limited to £5 million over the originally agreed price[142]—with the right to impose penalties upon the contractors for late delivery;[143] since February 2009, the contractors had been amassing a fine of £14,000 per day for late delivery,[35][144] amounting to £6 million by June 2010[145] and estimated in December 2010 to be £9 million.[146] On 29 January 2010, Cambridgeshire County Council's head of audit and risk management stated that uncertainty over the final construction price had been causing cash flow issues for the council.[147]

The County Council's performance bond with BAM Nuttall was limited to £7.5 million, plus a further "unlimited guarantee" from Koninklijke BAM Groep, BAM Nuttall's parent company based in The Netherlands.[148]

The original price for the engineering works conducted by BAM Nuttall had been £88 million, and estimates in mid-February 2010 projected costs to have increased to £120 to 140 million.[149] The main issue was structural repairs necessary to the new Great Ouse Viaduct to prevent water ingress.[149] Later that month, Cambridgeshire County Council stated that the council was due to borrow £41 million during 2010 and then £10.2 million the year after, payable to BAM Nuttall in order to complete the project.[135]

Cambridgeshire County Council brought in Atkins as consultants to manage the project. Following the delivery delays, Atkins' bill increased from an expected £2.9 million to £9.6 million.[150][151][152][153] The cost of this would be offset by the £10.8-million fine imposed on BAM Nuttall over the same time-period.[153]

A court date of January 2014 was scheduled for proceedings to begin at the Technology and Construction Court in London. Cambridgeshire County Council stated that it had set aside £6.5 million for legal costs for pursuing the £60 million claim against BAM Nuttall.[154] In May 2012 BAM Nuttall launched a £43-million counterclaim.[155][156] On 30 August 2013, Cambridgeshire County Council announced that it had reached an out of court settlement with BAM Nuttall.,[157] paying them £84.7 million, up from the £83.9 million original fee. Legal costs and other charges would set the total cost at £152 million, £26 million of which would have to come from the Council budget.[11]

Future proposals

As of February 2012 suggestions had been made for its expansion.

Cambridge Science Park railway station

<templatestyles src="Module:Hatnote/styles.css"></templatestyles>

The construction of Cambridge Science Park railway station in the Chesterton district of Cambridge had been scheduled to begin in 2014.[158] As part of the plans the busway is to be extended from Milton Road to the station.[158] The authority already had the necessary powers to build the extension.[30]

Southern extensions

By June 2010, BAM Nuttall was predicting that it hoped to have the southern sections to Trumpington and Addenbrooke's Hospital opened by December 2010.[159] Cambridgeshire County Council has proposed extending the busway beyond each of the Addenbrooke's Hospital and Trumpington Park and Ride termini. Funding would be part of the same Transport Innovation Fund proposals.[160]

Newmarket Road

During May 2012 proposals were published by the council to provide segregated bus lanes or an extended bus guideway down the central reservation of Newmarket Road, Cambridge, between Cambridge United Football Club's Abbey Stadium and East Road, Cambridge.[161]

Other proposals

In connection with the Chesterton diversion, the CamLink consortium have proposed a busway from the centre of Cambridge, past the future Science Park station to Waterbeach.[162] CamLink is a proposal developed by RLW Estates which is a consortium of The Royal London Group, Turnstone Estates and St John's College.[163]

CamToo, a transport scheme developed by a separate set of local interest groups,[164] has also offered proposals for further expansion of the guided busway network including:[165]

  • Extending the service to operate to Peterborough[166][167]
  • Extension beyond the Milton Road junction, crossing Milton Road to Barnwell Bridge, continuing along the railway alignment already used
  • New access routes to and from the A14 road to enable buses from Bar Hill and Cambourne to access the northern section of the busway and its bridge under the A14 road.
  • A new bridge under the A14 dual carriageway to enable buses serving Milton, including a new Park and Ride site, to avoid the busy Milton Road / A14 roundabout.
  • Conversion of bus lanes on Newmarket Road to "tramway" style (bus lanes moved into the centre of the road with right turns across the bus lanes prohibited for normal traffic).
  • Extension beyond Addenbrooke's Hospital, connecting to the A1303 Babraham Road
  • Extension beyond Trumpington Park and Ride along the course of the old Bedford railway line to the B1046 between Barton and Comberton.

In February 2012 a proposal was reported from the Campaign for Better Transport to construct an additional Park & Ride facility at Brampton Racecourse to the north-west of Huntingdon.[168]

Incidents

On 20 November 2012 a driver misjudged the entrance when joining the guideway at Longstanton heading towards St Ives. The double-decker bus was left straddling both sides of the guideway and a temporary speed-restriction was introduced. On investigation no defects were found with the bus.[169][170]

On 15 February 2013 a single-decker bus travelling towards St Ives had to brake hard owing to horses obstructing the guideway just after the Swavesey Crossing. This resulted in a following double-decker bus crashing into it.[171][172][173]

On 5 April 2013, a lorry driver accidentally drove along the busway after following directions given by satellite navigation. A spokesperson for the truck operator concluded that the driver had "relied too heavily on his sat-nav". No damage was caused to the busway and no one was injured. The council warned that the company could be fined if it happened again.[174]

In the 6 months until January 2013, a total of 20 cars had attempted to drive onto the busway, 18 of these happened at the start of the busway in St Ives at the junction with Harrison Way and the other incidents occurred at various junctions in Cambridge.[175] Car traps exist at many points where the busway crosses normal roads, to stop cars from travelling on the busway.

On 17 November 2015, a pedestrian was struck and killed on the busway near Swavesey.[176]

On 22 February 2016 a bus derailed on the Trumpington section, crossed the cycle path, mounted an embankment and crashed into the Trumpington Community Orchard, ripping out a section of the traditional hedgerow. Five passengers were injured.[177] CCTV images showed that the bus struck the left side guide rail (instead of engaging gradually on the right) causing it run out of control. It was travelling at excessive speed and the driver was not looking forward at the time. The driver was dismissed by the operator, Stagecoach Cambridgeshire.[178]

See also

References

  1. 1.0 1.1 1.2 Lua error in package.lua at line 80: module 'strict' not found.
  2. 2.0 2.1 Lua error in package.lua at line 80: module 'strict' not found.
  3. Lua error in package.lua at line 80: module 'strict' not found.
  4. Lua error in package.lua at line 80: module 'strict' not found.
  5. Lua error in package.lua at line 80: module 'strict' not found.
  6. 6.0 6.1 6.2 Lua error in package.lua at line 80: module 'strict' not found.
  7. http://www.cambridge-news.co.uk/Cost-guided-busway-climbs-to181-million/story-22352322-detail/story.html
  8. Lua error in package.lua at line 80: module 'strict' not found.
  9. Lua error in package.lua at line 80: module 'strict' not found.
  10. Lua error in package.lua at line 80: module 'strict' not found.
  11. 11.0 11.1 http://www.cambridge-news.co.uk/News/Guided-busway-legal-battle-with-BAM-Nuttall-settled-by-Cambridgeshire-County-Council-20130830105405.htm
  12. Lua error in package.lua at line 80: module 'strict' not found.
  13. Lua error in package.lua at line 80: module 'strict' not found.
  14. Lua error in package.lua at line 80: module 'strict' not found.
  15. Lua error in package.lua at line 80: module 'strict' not found.
  16. Lua error in package.lua at line 80: module 'strict' not found.
  17. Lua error in package.lua at line 80: module 'strict' not found.
  18. 18.0 18.1 18.2 18.3 Lua error in package.lua at line 80: module 'strict' not found.
  19. Lua error in package.lua at line 80: module 'strict' not found.
  20. Lua error in package.lua at line 80: module 'strict' not found.
  21. Lua error in package.lua at line 80: module 'strict' not found.
  22. Lua error in package.lua at line 80: module 'strict' not found.
  23. Lua error in package.lua at line 80: module 'strict' not found.
  24. Lua error in package.lua at line 80: module 'strict' not found.
  25. 25.0 25.1 Lua error in package.lua at line 80: module 'strict' not found.
  26. Lua error in package.lua at line 80: module 'strict' not found.
  27. Lua error in package.lua at line 80: module 'strict' not found.
  28. 28.0 28.1 Lua error in package.lua at line 80: module 'strict' not found.
  29. Lua error in package.lua at line 80: module 'strict' not found.
  30. 30.0 30.1 30.2 Lua error in package.lua at line 80: module 'strict' not found.
  31. 31.0 31.1 Lua error in package.lua at line 80: module 'strict' not found.
  32. 32.0 32.1 Lua error in package.lua at line 80: module 'strict' not found.
  33. Lua error in package.lua at line 80: module 'strict' not found.
  34. Lua error in package.lua at line 80: module 'strict' not found.
  35. 35.0 35.1 35.2 35.3 Lua error in package.lua at line 80: module 'strict' not found.
  36. 36.0 36.1 Lua error in package.lua at line 80: module 'strict' not found.
  37. 37.0 37.1 Lua error in package.lua at line 80: module 'strict' not found.
  38. http://andysbusblog.blogspot.com/2012/02/cambridgeshire-busway-service.html
  39. Lua error in package.lua at line 80: module 'strict' not found.
  40. Lua error in package.lua at line 80: module 'strict' not found.
  41. Lua error in package.lua at line 80: module 'strict' not found.
  42. Lua error in package.lua at line 80: module 'strict' not found.
  43. Lua error in package.lua at line 80: module 'strict' not found.
  44. 44.0 44.1 Lua error in package.lua at line 80: module 'strict' not found.
  45. Lua error in package.lua at line 80: module 'strict' not found.
  46. Lua error in package.lua at line 80: module 'strict' not found.
  47. Lua error in package.lua at line 80: module 'strict' not found.
  48. Lua error in package.lua at line 80: module 'strict' not found.
  49. Lua error in package.lua at line 80: module 'strict' not found.
  50. Lua error in package.lua at line 80: module 'strict' not found.
  51. Lua error in package.lua at line 80: module 'strict' not found.
  52. Lua error in package.lua at line 80: module 'strict' not found.
  53. Lua error in package.lua at line 80: module 'strict' not found.
  54. 54.0 54.1 54.2 Lua error in package.lua at line 80: module 'strict' not found.
  55. Lua error in package.lua at line 80: module 'strict' not found.
  56. Lua error in package.lua at line 80: module 'strict' not found.
  57. Lua error in package.lua at line 80: module 'strict' not found.
  58. Lua error in package.lua at line 80: module 'strict' not found.
  59. Lua error in package.lua at line 80: module 'strict' not found.
  60. Lua error in package.lua at line 80: module 'strict' not found.
  61. Lua error in package.lua at line 80: module 'strict' not found.
  62. Lua error in package.lua at line 80: module 'strict' not found.
  63. Lua error in package.lua at line 80: module 'strict' not found.
  64. Lua error in package.lua at line 80: module 'strict' not found.
  65. Lua error in package.lua at line 80: module 'strict' not found.
  66. Lua error in package.lua at line 80: module 'strict' not found.
  67. Lua error in package.lua at line 80: module 'strict' not found.
  68. Lua error in package.lua at line 80: module 'strict' not found.
  69. 69.0 69.1 Lua error in package.lua at line 80: module 'strict' not found.
  70. 70.0 70.1 Lua error in package.lua at line 80: module 'strict' not found.
  71. 71.0 71.1 Lua error in package.lua at line 80: module 'strict' not found.
  72. Lua error in package.lua at line 80: module 'strict' not found.
  73. Lua error in package.lua at line 80: module 'strict' not found.
  74. Lua error in package.lua at line 80: module 'strict' not found.
  75. Lua error in package.lua at line 80: module 'strict' not found.
  76. Lua error in package.lua at line 80: module 'strict' not found.
  77. 77.0 77.1 Lua error in package.lua at line 80: module 'strict' not found.
  78. Lua error in package.lua at line 80: module 'strict' not found.
  79. Lua error in package.lua at line 80: module 'strict' not found.
  80. Lua error in package.lua at line 80: module 'strict' not found.
  81. Lua error in package.lua at line 80: module 'strict' not found.
  82. Lua error in package.lua at line 80: module 'strict' not found.
  83. Lua error in package.lua at line 80: module 'strict' not found.
  84. Lua error in package.lua at line 80: module 'strict' not found.
  85. Lua error in package.lua at line 80: module 'strict' not found.
  86. Lua error in package.lua at line 80: module 'strict' not found.
  87. Lua error in package.lua at line 80: module 'strict' not found.
  88. Lua error in package.lua at line 80: module 'strict' not found.
  89. Lua error in package.lua at line 80: module 'strict' not found.
  90. Lua error in package.lua at line 80: module 'strict' not found.
  91. Lua error in package.lua at line 80: module 'strict' not found.
  92. Lua error in package.lua at line 80: module 'strict' not found.
  93. Lua error in package.lua at line 80: module 'strict' not found.
  94. Lua error in package.lua at line 80: module 'strict' not found.
  95. Lua error in package.lua at line 80: module 'strict' not found.
  96. Lua error in package.lua at line 80: module 'strict' not found.
  97. Lua error in package.lua at line 80: module 'strict' not found.
  98. Lua error in package.lua at line 80: module 'strict' not found.
  99. Lua error in package.lua at line 80: module 'strict' not found.
  100. Lua error in package.lua at line 80: module 'strict' not found.
  101. Lua error in package.lua at line 80: module 'strict' not found.
  102. Lua error in package.lua at line 80: module 'strict' not found.
  103. Lua error in package.lua at line 80: module 'strict' not found.
  104. Lua error in package.lua at line 80: module 'strict' not found.
  105. Lua error in package.lua at line 80: module 'strict' not found.
  106. Lua error in package.lua at line 80: module 'strict' not found.
  107. Lua error in package.lua at line 80: module 'strict' not found.
  108. Lua error in package.lua at line 80: module 'strict' not found.
  109. Lua error in package.lua at line 80: module 'strict' not found.
  110. A cyclist hit by a guided bus suffered serious injuries
  111. Lua error in package.lua at line 80: module 'strict' not found.
  112. Lua error in package.lua at line 80: module 'strict' not found.
  113. 113.0 113.1 Lua error in package.lua at line 80: module 'strict' not found.
  114. Lua error in package.lua at line 80: module 'strict' not found.
  115. Lua error in package.lua at line 80: module 'strict' not found.
  116. Lua error in package.lua at line 80: module 'strict' not found.
  117. Lua error in package.lua at line 80: module 'strict' not found.
  118. Lua error in package.lua at line 80: module 'strict' not found.
  119. Lua error in package.lua at line 80: module 'strict' not found.
  120. Lua error in package.lua at line 80: module 'strict' not found.
  121. Lua error in package.lua at line 80: module 'strict' not found.
  122. Lua error in package.lua at line 80: module 'strict' not found.
  123. Lua error in package.lua at line 80: module 'strict' not found.
  124. Lua error in package.lua at line 80: module 'strict' not found.
  125. Lua error in package.lua at line 80: module 'strict' not found.
  126. Lua error in package.lua at line 80: module 'strict' not found.
  127. Lua error in package.lua at line 80: module 'strict' not found.
  128. Lua error in package.lua at line 80: module 'strict' not found.
  129. 129.0 129.1 129.2 Lua error in package.lua at line 80: module 'strict' not found.
  130. 130.0 130.1 Lua error in package.lua at line 80: module 'strict' not found.
  131. Lua error in package.lua at line 80: module 'strict' not found.
  132. 132.0 132.1 Lua error in package.lua at line 80: module 'strict' not found.
  133. 133.0 133.1 Lua error in package.lua at line 80: module 'strict' not found.
  134. Lua error in package.lua at line 80: module 'strict' not found.
  135. 135.0 135.1 Lua error in package.lua at line 80: module 'strict' not found.
  136. 136.0 136.1 Lua error in package.lua at line 80: module 'strict' not found.
  137. Lua error in package.lua at line 80: module 'strict' not found.
  138. Lua error in package.lua at line 80: module 'strict' not found.
  139. Lua error in package.lua at line 80: module 'strict' not found.
  140. Lua error in package.lua at line 80: module 'strict' not found.
  141. Lua error in package.lua at line 80: module 'strict' not found.
  142. Lua error in package.lua at line 80: module 'strict' not found.
  143. Lua error in package.lua at line 80: module 'strict' not found.
  144. Lua error in package.lua at line 80: module 'strict' not found.
  145. Lua error in package.lua at line 80: module 'strict' not found.
  146. Lua error in package.lua at line 80: module 'strict' not found.
  147. Lua error in package.lua at line 80: module 'strict' not found.
  148. Lua error in package.lua at line 80: module 'strict' not found.
  149. 149.0 149.1 Lua error in package.lua at line 80: module 'strict' not found.
  150. Lua error in package.lua at line 80: module 'strict' not found.
  151. Lua error in package.lua at line 80: module 'strict' not found.
  152. Lua error in package.lua at line 80: module 'strict' not found.
  153. 153.0 153.1 Lua error in package.lua at line 80: module 'strict' not found.
  154. Lua error in package.lua at line 80: module 'strict' not found.
  155. Lua error in package.lua at line 80: module 'strict' not found.
  156. Lua error in package.lua at line 80: module 'strict' not found.
  157. Lua error in package.lua at line 80: module 'strict' not found.
  158. 158.0 158.1 Lua error in package.lua at line 80: module 'strict' not found.
  159. Lua error in package.lua at line 80: module 'strict' not found.
  160. Lua error in package.lua at line 80: module 'strict' not found.
  161. Lua error in package.lua at line 80: module 'strict' not found.
  162. Lua error in package.lua at line 80: module 'strict' not found.
  163. Lua error in package.lua at line 80: module 'strict' not found.
  164. Lua error in package.lua at line 80: module 'strict' not found.
  165. Lua error in package.lua at line 80: module 'strict' not found.
  166. Lua error in package.lua at line 80: module 'strict' not found.
  167. Lua error in package.lua at line 80: module 'strict' not found.
  168. Lua error in package.lua at line 80: module 'strict' not found.
  169. Lua error in package.lua at line 80: module 'strict' not found.
  170. Lua error in package.lua at line 80: module 'strict' not found.
  171. Lua error in package.lua at line 80: module 'strict' not found.
  172. Lua error in package.lua at line 80: module 'strict' not found.
  173. Lua error in package.lua at line 80: module 'strict' not found.
  174. Lua error in package.lua at line 80: module 'strict' not found.
  175. Lua error in package.lua at line 80: module 'strict' not found.
  176. Lua error in package.lua at line 80: module 'strict' not found.
  177. Lua error in package.lua at line 80: module 'strict' not found.
  178. Lua error in package.lua at line 80: module 'strict' not found.

External links