Heathrow Airtrack

From Infogalactic: the planetary knowledge core
Jump to: navigation, search

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

Heathrow Airtrack (proposed)
Heathrow airtrack logo.png
Heathrow T5 station AB.JPG
The current Terminal 5 station which would have formed part of Airtrack
Overview
Type Urban rail / Airport rail link proposal
System National Rail
Status Proposal only
Locale London, England, UK
Termini Heathrow Terminal 5
London Waterloo
Reading
Woking
Guildford
Stations 13
Operation
Opened 2015 (projected)
Owner Heathrow Airport Holdings (railway tracks around Heathrow Airport)
Network Rail (remainder of the network)
Technical
Track gauge 1,435 mm (4 ft 8 12 in)
Heathrow Airtrack
Waterloo National Rail London Underground London River Services
Clapham Junction National Rail London Overground
Vine Lane
Langley
Sheen Lane
North Sheen (Manor Road)
Richmond National Rail London Underground London Overground
Richmond Railway Bridge
over River Thames
Twickenham
Feltham Depot
Feltham
Bedfont Lane
Staines
Heathrow Terminal 5 National Rail London Underground
Chertsey
UK-Motorway-M25.svg M25 motorway
Woking National Rail
Guildford National Rail
Staines Railway Bridge
over River Thames
Thorpe Lane
Pooley Green
UK-Motorway-M25.svg M25 motorway
Rusham
London Road
Bracknell
Waterloo Road
Star Lane
Wokingham level crossing
Wokingham
UK-Motorway-M4.svg M4 motorway
River Loddon
River Kennet
Reading Crossrail National Rail

Heathrow Airtrack was a proposed railway link in west London, England, UK. The line as proposed by BAA, would have run from Heathrow Terminal 5 into central London and across the suburbs of south-west London. BAA announced that it was abandoning the project in April 2011. In October 2011 Wandsworth Council announced a revised plan called Airtrack-Lite.[1]

The BAA proposal would have provided direct rail services from the airport to London Waterloo, Reading and Guildford, and offered an alternative route to the existing rail routes to Heathrow (namely Heathrow Express, Heathrow Connect and the Piccadilly line). The scheme, estimated to cost around £673 million,[2] was controversial mainly because of the projected impact on local road traffic due to the high number of level crossings on the route.[citation needed] In April 2011, BAA announced that it was abandoning the project,[3] citing the unavailability of government subsidy and other priorities for Heathrow,[4] such as linking to Crossrail and HS2.

Both proposals involve reopening a section of the former West Drayton to Staines railway line, roughly following the southern route of the line to a junction with the Staines to Windsor Line and a reinstatement of the Staines West chord.[1][5]

Plans

Heathrow Terminal 5 has two safeguarded heavy rail platforms for use by a west-facing connection to the National Rail network, which would have been utilised by Airtrack. The original proposal for the AirTrack link[6] included a new station, called Staines High Street railway station, built near the site of the former station of the same name, but that plan was omitted from the revised proposals in the second public consultation, published on 20 October 2008.[7]

A new rolling stock depot on the site of the former marshalling yards at Feltham was included in the proposal.

BAA indicated that they wished to extend the Heathrow Express service from terminal 5 to a new terminal platform at Staines.[7]

Proposal and cancellation

The principle of a rail connection to Heathrow from the south had been the subject of considerable discussion and study for 50 years. Since 1960, there have been more than 10 studies or proposals that considered how to improve surface access to Heathrow by means of an additional fixed rail link and in 1984 studies confirmed the viability of the link.[8]

Following a period of public consultation in 1998, BAA submitted plans on 24 July 2009 to the Secretary of State for Transport seeking authorisation under the Transport and Works Act to acquire the necessary land and begin constructing the rail link.

Work had been forecast to begin in 2011, with rail services operating by 2015.[9] However, on 30 July 2010 the Department of Transport wrote to all parties involved in the public inquiry, informing them that this had been delayed indefinitely. The reason cited was that "the Government has confirmed that its most urgent priority is to tackle the UK's budget deficit and that there will be a spending review in the Autumn. The review may have implications for the proposed funding of the Airtrack Scheme and until the position becomes clearer, we do not consider it appropriate to take matters forward..."[10]

In the event, Airtrack was not mentioned in the spending review and, as a result, in November 2010 BAA announced that the 'public inquiry remains deferred'.[11]

On 23 December 2010, two radio stations, County Sound and Eagle, ran news stories on the 'end of the line' for Airtrack.[12] However, it is not clear whether these stories were based on industry rumour or official sources. The same report had BAA insisting that its commitment to the project was still there and promising a new 'public consultation in the New Year'. However, on 26 January 2011 the DfT again wrote to objectors informing them the Transport and Works Act process remained suspended indefinitely, citing 'continuing uncertainty'.

Meanwhile, an alternative proposal has emerged, called the Windsor Link Railway. According to the promoting company, this has the advantage of potentially not requiring any public subsidy whilst providing more public benefit, not only connecting Heathrow to the north west (via the Thames Valley) but also to the south and linking the historic Great Western and Southern Railway regions. The proposal has been welcomed by the Minister for Transport, Theresa Villiers. [13]

Support and opposition

The AirTrack Forum, is a 'group of organisations with a common interest in seeing Airtrack built', formed at the initiative of British Airways, according to its website.[14] It has commissioned consultants to study the economic benefits of the scheme funded by the (now defunct) SE Regional Assembly.[15] Some groups within the Airtrack Forum do not support the current proposals.

BAA has claimed support for the scheme from Transport for London, the Mayor of London, nine London Boroughs and local borough councils of Runnymede, Reading, Woking, Guildford, Bracknell Forest and Wokingham, as well as by Surrey and Hampshire County Councils.[16] However, this is contradicted by objections made by some of these authorities to the final plans. Surrey County Council, for example, is an official objector to the scheme, as is Wokingham.[17] Additionally, "Strong concerns" have been raised by the Royal Borough of Windsor and Maidenhead,[18] including a worries that the busy Windsor Riverside service would have been downgraded as a result and, again, level crossings.

It has been reported that Surrey may 'drop its opposition' after BAA offered to fund £11 million of transport improvements[19] and a vote to provisionally drop their opposition was passed by the county's cabinet on 28 September 2010.[20] This decision was due to be finalised by the full council in December 2010[20] but was deferred. The move was the subject of an 'extraordinary outburst' from Philip Hammond, the local MP, who at the time happened to be the Secretary of State for Transport.[21] Hammond criticised the council for 'grabbing a bribe', a payment of £11 million towards mitigating some traffic problems in Egham entirely unconnected to[citation needed] Airtrack and went on to demand a more comprehensive solution, saying 'no solution, no scheme' and urging BAA to 'get back to the drawing board'.[22] BAA had made a significant compromise in offering this payment as it had previously been consistent in arguing that traffic problems caused by Airtrack were not its responsibility, using the fact that Network Rail has no legal obligation to open level crossings at all or to consult on changes.[23]

Construction

The economic case was heavily dependent on the fact that Airtrack should be a low-cost option[24] as only 4 kilometres (2.5 mi) of new line would be required, mostly within Spelthorne. The remaining new infrastructure would consist of station improvements and associated facilities.

The key elements of construction work would involve:[5]

  • Tunnelling from Heathrow Terminal 5 to Stanwell Moor
  • Construction of a new rail line across Stanwell Moor and Staines Moor
  • Construction of a new section of track in Staines-upon-Thames town centre
  • The remodelling of Staines station
  • Building a train depot at Feltham

The scheme was estimated to cost about £673 million,[2] of which about £150 million is expected to come from an operating surplus and the remainder from a government subsidy.

In the Airtrack project some stations used by its trains would be upgraded. It was intended that from Staines-upon-Thames the trains would use existing Network Rail tracks

Services

The passenger services proposed for the Airtrack service were generally to offer a half-hourly service to each destination:[7]

London Waterloo - Heathrow: two trains per hour stopping at:

  • Clapham Junction
  • Richmond
  • Twickenham
  • Feltham
  • Staines

An extension of the Heathrow Express service to Staines-upon-Thames would have provided an additional 2tph between the airport and Staines-upon-Thames. Journey time from Waterloo to Heathrow would have been approximately 40 minutes.[25]

Guildford - Heathrow (via Egham and Virginia Water): two trains per hour (one per hour at peak times) stopping at:

  • Chertsey
  • Woking

Journey time from Guildford to Heathrow would have been approximately 36 minutes.[25]

Reading - Heathrow (via Egham and Virginia Water) two trains per hour stopping at:

  • Wokingham
  • Bracknell

Journey time from Reading to Heathrow would have been approximately 45 minutes.[25]

Impact

Concerns about the impact of Airtrack construction work and operation had been raised by local residents, campaigners and politicians.

Environment

Stanwell Moor

Staines Moor

Most of the construction work would have affected Staines Moor and Stanwell Moor, which include a Site of Special Scientific Interest (SSSI), and extensive consultations took place in Spelthorne resulting in major modifications of the scheme.[5]

Feltham depot

Building a train depot in Feltham was part of the scheme. Residents of Feltham had expressed opposition to this mainly as the depot may have encroached on a natural conservation area and that the depot may give rise to noise pollution.[26]

In response to these concerns, BAA had published assurances in their consulation literature that the Feltham depot would have been designed to limit noise and light pollution and with landscape screening.[5]

Level crossings

Mortlake level crossing

A number of major problems concerned level crossings. The proposed Airtrack route would have run on lines which have fifteen level crossings, and local campaigners along those routes have pointed out that more frequent trains would increase waiting times at closed barriers and exacerbate traffic congestion problems. For example, between Richmond and Barnes as many as five trains may pass before the road barriers are lifted.[5] BAA investigated the possibility of constructing road bridges or tunnels at these locations but concluded that such construction was "not feasible or justifiable".[7]

BAA had acknowledged these problems and noted that eight crossings would have been slightly impacted, with barrier closure times increasing by up to 13%. Three level crossing more would have been moderately affected, with increases of between 13% and 25% to the amount of time that the barriers are closed to road traffic. Four crossings would have been "severely" affected, with barrier downtimes increasing by between 25% and 36%.[27] As no independent time and motion study had been conducted, the closure times of level crossings and impact to the surrounding area had yet to be assessed at the time of the project's cancellation.[17]

Three of the four severely affected crossings are located in Egham, which lies between Staines-upon-Thames, where the Airtrack spur would have met the main line, and Virginia Water, where the Reading and Guildford lines diverge.

Airtrack originally envisaged that by investing in new signalling technology, they could keep level crossings down-times to a manageable level. This was accepted as a reasonable proposition by the local authority, Runnymede Borough Council, and by the Highways Authority for the area, Surrey County Council, both of which actively supported the Airtrack scheme.[16] However, in September 2009 Runnymede Borough Council responded to the TWA application with an objection.[citation needed]

Egham

Egham Hythe Thorpe Road level crossing

Immediately after Staines-upon-Thames the westward line goes through the town of Egham. Local campaigners in Egham had voiced their opposition to Airtrack mainly due to the foreseen traffic congestion problems caused by level crossing closures.[28] Opponents noted that the railway bisects the town, and it can only be crossed via four level crossings (Thorpe Road, Egham Hythe; Vicarage Road; Station Road; and Prune Hill) as there are no alternative bridges or tunnels in the locality.

Concerns were also raised about the scheme's effect on the town by Egham Chamber of Commerce,[29] Runnymede Council, Richmond Council,[30] and bus operators. The local MP for Runnymede and Weybridge, Philip Hammond, first raised his concerns about lack of alternatives to level crossings in Egham in the House of Commons;[31] in 2002. In 2009 he arranged for the Chamber of Commerce to deliver a petition to 10 Downing Street appealing to the then Labour Government to not allow Airtrack to be built without a tunnel or bridge in Egham. Hammond became Secretary of State for Transport in May 2010.[32]

In a consultation between Surrey County Council and the emergency services, the Fire and Ambulance services expressed concerns about increased level crossing down-times.[33]

Airtrack had estimated that if the project proceeded as planned the three significantly affected level crossings in Egham would be closed an average of 34 minutes per hour between 7 am and 7 pm. These figures were based on the assumptions that only timetabled trains would have operated, that they would have operated without delays and that the signalling regime could have been reorganised to allow barriers to be raised if were a 30-second gap between trains.[27]

Wokingham

Waterloo Road level crossing, Wokingham

The Airtrack route was also planned to pass through the town of Wokingham. As with Egham, an opposition campaign was organised to voice local concerns about the foreseen traffic congestion caused by increased rail traffic on level crossings.[34] Wokingham has five crossings (Easthampstead Road, Waterloo Road, Barkham Road, Station Road and Wellington Road) which would have been affected by the project, and campaigners submitted a petition to the Government.[35]

BAA said that Wokingham Borough Council was considering the issue as part of its transport strategy. The council discussed the possibility of building a bridge over the Barkham Road crossing but such a solution was unlikely due to the excessive construction cost. The council also proposed that Wokingham Station would have needed to be moved closer to Reading in order to accommodate the Airtrack proposal.[36]

Airtrack-Lite

In October 2011 Wandsworth Council announced a revised plan called Airtrack-Lite. The idea behind this was to address some of the criticisms of BAA's Airtrack including: costs, level crossing downtime, the use of Feltham depot and the displacement of existing commuters from services which are already overcrowded for shiny but empty trains to Heathrow. Wandsworth thus proposed abandoning the Guildford and Reading branches of Airtrack, which only accounted for 20% of the forecast demand anyway, so stopping any increase in downtime on lines to those destinations, whilst extending existing services from Waterloo to Heathrow, connecting south London to Heathrow without increasing level crossing downtime in places such as Barnes or requiring new rolling stock.

It was proposed that the Waterloo to Windsor service would divide at Staines-upon-Thames, and the Weybridge to London via the Hounslow loop service would be recast as Weybridge to Heathrow and Heathrow to London services.[1]

In March 2013, Wandsworth Council initiated a new £25,000 study into providing a 30-minute rail journey from Clapham Junction to Heathrow.[37]

A variation of Heathrow Airtrack Lite is also used by the Windsor Link Railway, with a new link to T5 from a triangle Wraysbury, providing both a north-west and a south-west rail link to Heathrow, with a bridge over the M25 avoiding the cost of tunneling associated with Airtrack.

Aviation Policy Framework proposal

A new rail link proposal has been included in the governments High Level Output Specification for rail. The proposed line would use a west-facing connection near Slough, which would allow through trains to serve the airport from south Wales and Bristol if a business case could be established.[38]

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. 5.0 5.1 5.2 5.3 5.4 Lua error in package.lua at line 80: module 'strict' not found.
  6. Lua error in package.lua at line 80: module 'strict' not found.
  7. 7.0 7.1 7.2 7.3 Lua error in package.lua at line 80: module 'strict' not found.
  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. Lua error in package.lua at line 80: module 'strict' not found.
  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. 16.0 16.1 Lua error in package.lua at line 80: module 'strict' not found.
  17. 17.0 17.1 Lua error in package.lua at line 80: module 'strict' not found.
  18. 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. 20.0 20.1 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 25.2 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. 27.0 27.1 Lua error in package.lua at line 80: module 'strict' not found.
  28. Lua error in package.lua at line 80: module 'strict' not found. (Egham Airtrack campaigning website)
  29. Lua error in package.lua at line 80: module 'strict' not found.
  30. Lua error in package.lua at line 80: module 'strict' not found.
  31. Lua error in package.lua at line 80: module 'strict' not found.
  32. 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. Lua error in package.lua at line 80: module 'strict' not found.
  36. Lua error in package.lua at line 80: module 'strict' not found.
  37. Lua error in package.lua at line 80: module 'strict' not found.
  38. Lua error in package.lua at line 80: module 'strict' not found.

External links