British Rail Class 700

From Infogalactic: the planetary knowledge core
(Redirected from Class 700)
Jump to: navigation, search
British Rail Class 700 Desiro City
700110 - London Blackfriars 3T13.JPG
700110 at London Blackfriars on a training run
275px
Class 700 mock-up interior
In service Due to enter service in 2016–2018[1]
Manufacturer Siemens Mobility[2]
Built at Krefeld, Germany[2]
Family name Desiro City[2]
Replaced
Constructed 2014–
Number under construction 55 twelve-car units (660 vehicles)[3]
60 eight-car units (480 vehicles)[3]
25 six-car units (150 vehicles)[4]
140 units in total (1290 vehicles)
Formation 8 or 12 carriages per unit
Fleet numbers 700001 to 700060 (8 car)[3]
700101 to 700155 (12 car)[3]
Capacity 427 seats, 719 standing (8-car)[3]
666 seats, 1,088 standing (12-car)[3]
Operator(s) Thameslink
Depot(s) Hornsey, Three Bridges[2]
Specifications
Train length 162.0 m (531.5 ft) (8-car)
242.6 m (796 ft) (12-car)
Car length 20.2 m
Width 2.80 m (9 ft 2 in)
Floor height 1.10 m (3 ft 7 in)
Wheel diameter 820 to 760 mm (32 to 30 in) (new/worn)
Maximum speed Lua error in Module:Convert at line 272: attempt to index local 'cat' (a nil value).
Weight 278 t (274 long tons; 306 short tons) (8-car)
410 t (400 long tons; 450 short tons) (12-car)
Power output 3.3 MW (4,400 hp) (8-car, at wheel)
5.0 MW (6,700 hp) (12-car, at wheel)
Electric system(s) 25 kV AC Catenary
750 V DC Third rail
UIC classification 8 car: Bo'Bo'+2'2'+Bo'Bo'+2'2'+2'2'+Bo'Bo'+2'2'+Bo'Bo'

12 car: Bo'Bo'+2'2'+Bo'Bo'+Bo'Bo'+2'2'+2'2'+
2'2'+2'2'+Bo'Bo'+Bo'Bo'+2'2'+Bo'Bo'
Track gauge 1,435 mm (4 ft 8 12 in) (Standard gauge)
Notes
Sources : Desiro City data sheet
Except where noted

The British Rail Class 700 is a class of electric multiple-unit passenger train built for Thameslink as part of the Thameslink Programme in the United Kingdom.

A fleet of 60 eight- and 55 twelve- car trains are expected to enter service between spring 2016 and 2018. Associated rolling stock depots are being built at Hornsey and Three Bridges. The first train was delivered in late July 2015.

In 2011 the consortium Cross London Trains (XLT) consisting of Siemens Project Ventures, 3i Infrastructure and Innisfree was announced as preferred bidder with Siemens to manufacture the trains. The decision was politically controversial as the trains are to be built overseas, while the competing consortium led by Bombardier Transportation had a train factory in the UK. Both the procurement process and final close of contract were significantly delayed, resulting in the expected first delivery date moving from 2012 to 2016. The £1.6 billion contract to manufacture and provide service depots for the trains was finalised in June 2013.

The first unit is planned to be introduced by the end of Spring 2016.[5]

History

The Department for Transport began its procurement process (Thameslink Rolling Stock Project, or Thameslink Rolling stock Programme) on 9 April 2008, with the aim of introducing more passenger capacity on Thameslink lines to match expected demand. In addition, the bidders were to provide depots for vehicle maintenance and storage, and finance for the rolling-stock project whereby revenues would be generated from the long-term leasing of rolling stock to the operating Train Operating Company and associated maintenance payments.[6]

The general specifications included: high reliability, short station dwell times, integrated information technology including passenger information and information for vehicle maintenance, a top speed of 100 miles per hour (160 km/h) and high acceleration and deceleration performance in line with a high-frequency timetable.[note 1] The trains were to be designed for low weight, low track forces and high energy efficiency. A standard-length train was to be about 240 metres (790 ft) long, with some services using trains limited to 162 metres (531 ft).[6]

The passenger accommodation was to include versions for both "metro" and "commuter" trains,[note 2] based around a 2+2 seating arrangement, with fold-up seats and designed for high levels of standing passengers.[6] Ride quality and noise levels were expected to equal or be better than those of current vehicles. Climate control (air-conditioning) was to be fitted.[8] The vehicles were to be fitted for Driver-only operation, and to include GSM-R communications radio, as well as AWS, TPWS and ERTMS level 2 safety systems. The ability to be used in a "driverless" mode automatic train operation was also specified.[8]

Vehicles were to operate on 750 V DC and 25 kV AC electrification systems, with regenerative brakes. Maintenance time was to be reduced by the use of modular components, remote diagnostics, and the avoidance of over-complicated systems.[8] The Department for Transport gave a target of 384 tonnes (378 long tons; 423 short tons) when empty for a 243 m (797 ft) train.[8]

Bids

In July 2008 the Department for Transport shortlisted consortia including Alstom, Bombardier, Hitachi and Siemens as train builders.[9] The Invitations to Tender were issued to the four bidders in November 2008.[7]

Hitachi exited the bidding process in April 2009.[10]

In July 2009 Siemens unveiled the Desiro City, a development of design and technology used in its British Desiro range and the Desiro Mainline range.[11] Development of the design began in 2007, with an investment of about £45 million.[2][12]

In September 2009 Alstom unveiled the "X'trapolis UK, unusually an articulated vehicle, using 15.6 metres (51 ft) cars, with individual carriages proposed to be supported at one end by a bogie, and at the opposite end by a linkage to the next carriage. The shorter vehicle allowed a slightly wider design; the smaller number of bogies was to have resulted in a train approximately 40 tonnes lighter than a conventional design.[13] However, the design would have resulted in a higher axleload. The bid was rejected in October 2009.[14]

Bombardier Transportation offered the Aventra, a design incorporating a development of the FLEXX Eco inside frame bogie with bogie-mounted traction motors.[15]

Both Bombardier's and Siemens' rolling-stock designs were conventional EMUs incorporating inside frame bogies and modern passenger and rolling stock information systems.[2][11][12][15]

Contract decision and financial close

Full size mock-up of the class 700 at ExCeL

The contract for the order was originally planned to be signed in summer 2009, with the first vehicles in service by February 2012, and squadron service by 2015.[6] The award of the contract was delayed by the 2010 general election,[16] and the subsequent spending review, following which the procurement was announced to be proceeding in late 2010.[17]

On 16 June 2011, Cross London Trains Ltd, a consortium formed by Siemens Project Ventures GmbH, Innisfree Ltd., and 3i Infrastructure Ltd., was named preferred bidder for the PFI contract, and the targeted entry of trains into service was rescheduled to 2015–2018. The vehicles would be manufactured at Siemens' plant in Krefeld, Germany, and maintenance depots were to be built at Hornsey (London) and Three Bridges (Sussex).[2] Because the trains were to be built outside the UK, the decision to award the contract to Siemens proved controversial: there was widespread criticism of the UK government's bidding process and perceived lack of support for British manufacturing,[18][19] which in turn led to a review of governmental procurement mechanisms.[20][21][22][23]

The contract was significantly delayed: initially Siemens had hoped to reach agreement in early 2012;[24] by late 2011 commercial close was hoped for by the end of the year, and financial close in early 2013.[25] Key aspects of the commercial contract were reported to have been finalised by December 2012.[26]

As a result of the delays to the procurement, in late 2012 train operating company Southern began procurement of 116 new dual-voltage EMUs from Bombardier that would be used temporarily on the Thameslink route until 2015; the order contract was finalised in July 2013[26][27][28][29] In mid-2013 the National Audit Office reported that the contract delay could negatively impact the delivery of the entire Thameslink Programme.[30]

The £1.6 billion contract to finance, supply and maintain a 1,140-carriage fleet of passenger rolling stock was finalised between the DfT, the supplier Siemens and the Cross London Trains consortium on 14 June 2013.[31][32][33]

To finance the work, loans were arranged with 19 banks, with Lloyds, Sumitomo Mitsui Banking Corporation, KfW and BTMU acting as mandated lead arrangers; the European Investment Bank also provided a debt facility. Loans for the construction of the rolling-stock depots were through Siemens Financial Services.[34]

In 2014 the National Audit Office reported on the handling of Intercity Express and Thameslink rolling-stock procurement projects by the Department for Transport. The report questioned the DfT's attempt to take leadership in the project, contrary to general policy, without any prior experience of large-scale rolling stock procurement; the NAO also said the DfT had handled communications with bidders poorly, increasing the likelihood of a legal challenge to its decisions.[35][36]

Additional orders

In addition to the Thameslink fleet, Govia Thameslink Railway (GTR) announced upon winning the franchise that it would seek to replace the existing Class 313 units in use on services to and from London Moorgate, with up to 25 six-car units intended to be procured.[37][38] In December 2015, GTR announced that it had selected Siemens to provide this new fleet as a follow-on order from the main Class 700 run, with entry into service expected from 2018.[39][40] The order was finalised in February 2016.[4] No evidence so far what class these will be designated, these are referred to as new Moorgate Trains rather than Class 700.[41]

Manufacture, design and introduction

Design

SF7000 bogie

Development of a new bogie type began in 2007; the design was intended specifically for the UK market as a replacement for the SF5000 bogie. To reduce energy consumption and track access charges, a key feature of the design was reduced weight: weight-saving design elements included short wheelbase, inboard frames, a bolsterless bogie design, and hollow axles. Total bogie weight is 6.3 tonnes (powered) and 4.4 tonnes (trailer), a reduction of around one third from the SF5000 design.[42][43] The decision to procure a train with a new bogie design untested in the UK was challenged by several observers at a parliamentary investigation into the train procurement; rival bidder Bombardier already had a proven low-weight bogie.[44]

The primary suspension system uses layered rubber, with pneumatic secondary suspension. The bogie wheel base is 2,200 mm (87 in) (motor bogie) with 820 mm (32 in) wheels. Braking is by tread brakes, and regenerative braking on power bogies, and by two axle-mounted disc brakes per axle on trailer bogies.[42][45]

Prototypes of the new SF-7000 bogie were completed at Siemens' bogie plant in Graz, Austria in late 2011.[46]

Manufacture and introduction

Manufacture of pre-series production trainsets began before formal financial close of the project in mid-2013.[47]

A mockup of the train was unveiled at the ExCel centre in January 2014, and then displayed at various stations in London and the surrounding area;[48][49] and testing of a 12-car unit at the Test and validation centre, Wegberg-Wildenrath began in March 2014;[47] a completed unit was presented by Siemens in Krefeld, Germany in April 2015.[50]

The first delivered train arrived in the UK by the end of July 2015, and was delivered to the Three Bridges depot.[51] The first test run on the Brighton Main Line took place in December 2015.[52]

The first train is expected to enter service during Spring 2016, with full deployment by 2018.[1][53]

Fleet details

The new rolling stock was given the TOPS code 'Class 700' in 2013.[3] This was divided into Class 700/0 for eight-car units, and Class 700/1 for twelve-car units.[26][54]

In July 2013 Eversholt Rail entered into an agreement with Cross London Trains to provide long-term (22-year) asset management for the fleet of trains.[55]

There will be 60 eight-car units, and 55 twelve-car units.[56] Each set is to be a fixed length continuously gangwayed vehicle.[3] The initial livery will be "light grey with pastel blue doors and a white diagonal flash at the carriage ends".[3]

An additional 25 six car trains were ordered by GTR (2015, confirmed 2016) on winning the Thameslink franchise.[40][4]

Class Operator No. Built Year Built Cars per Set Unit nos.
Class 700/0 Thameslink
Great Northern
60 2014–2019 8 700001-700060
Class 700/1 55 12 700101-700155

Formation details

The formation of Class 700/0 units unit is DMCO-PTSO-MSO-TSO-TSO-MSO-PTSO-DMCO, and that of Class 700/1 units is DMCO-PTSO-MSO-MSO-TSO-TSO-TSO-TSO-MSO-MSO-PTSO-DMCO.[57]

Depots

In 2008 the Department for Transport commissioned a study into the location of depots for the future Thameslink rolling stock: Network Rail preferred two depots based on an expectation that at times the central area of the Thameslink route would be closed for maintenance outside commercial operational hours, with no workable alternative electrified routes available; as a result, depots on either side of the central Thameslink area were required, enabling trains to reach a depot on a nightly basis without passing through central London. A single-depot solution was also investigated, but no suitably large sites were identified for such a facility.[58]

Sites were considered at: Wellingborough (including sidings used by GB Railfreight); Hornsey (adjacent to the existing Hornsey EMU depot then operated by First Capital Connect); Cricklewood (on development land associated with the planned Brent Cross Thameslink railway station); Selhurst (on the site of the existing Selhurst Depot used by Southern); Three Bridges (a split site on either side of the main line), and Tonbridge.[59] By late 2008 the sites had been narrowed to Hornsey, Three Bridges and Tonbridge; finally Hornsey and Three Bridges were selected as a two-depot solution.[60]

In late 2009 the Hornsey depot was refused permission on grounds of its scale damaging a local conservation area.[61] In 2011 revised plans were submitted for both the Hornsey and Three Bridges schemes, with the Hornsey scheme reduced in size, and the Three bridges scheme expanded;[62] the Three Bridges depot was to be located on either side of the London to Brighton main line, with a five-road carriage shed; the Hornsey depot, to be located next to the East Coast main line, was to have a three-road carriage shed; the depots were expected to be opened in 2015 and 2016 respectively.[1]

In mid-2013 Volker Fitzpatrick was awarded the approximately £150 million contract to build the two depots.[63][64]

Three Bridges

Lua error in package.lua at line 80: module 'strict' not found. In 2009 Arup acting on behalf of Network Rail submitted a planning application for a rolling-stock depot south of Three Bridges railway station, with facilities on either side of the Brighton Main Line.[65][note 3] The development was on a 13 ha (32 acres) site owned by Network Rail 1.5 km south of Three Bridges railway station.

The development site was on land historically used for railway use;[note 4] unbuilt on prior to railway developments; by 1910 sidings had been built east of the London, Brighton and South Coast Railway (Brighton Main Line), as well as an engine shed and turntable adjacent west of the site;[68] In 2008 the western development area comprised underutilised sidings and hardstanding with the site east of the mainline including operation sidings, as well as offices; tenants included English Welsh & Scottish Railway, BAM Nuttall, Colas Rail and Balfour Beatty.[69][70] The western side of the proposed development included a single-ended 280 by 23 m (919 by 75 ft) three-road maintenance shed, 13 m (43 ft) high, a wheel lathe, electricity substation, and sidings for eight 12-car trains; the eastern side included stabling for four 12-car trains, and an underframe-cleaning facility; both sides of the development were to have separate 325 m2 (3,500 sq ft) train-washing facilities, waste storage, and controlled emission toilet facilities. Site offices and warehousing were to be in a 2,857 m2 (30,750 sq ft) three-storey building northwest of the main shed.[71][72][73]

Planning permission for the development was granted in November 2009,[74] but in December the associated Hornsey depot application was blocked by the Secretary of State for Communities and Local Government; Network Rail submitted revised plans for both sites in 2011, with a smaller Hornsey scheme and an expanded Three Bridges scheme.[62] In the same period as the new application, Network Rail submitted plans for a large railway operations and signalling centre to be built adjacent to the Three Bridges depot.[75] (see Three Bridges rail operating centre).

The revised plans added additional carriage stabling on the EWS/DB Schenker freight depot to the west of the original site;[76][77][note 5] with stabling for five 8-car trains, and with CET facilities – and total stabling on the western site was increased to eleven 8-car trains. Additional major changes included expansion of the main depot to a 5-road building, 40 m (130 ft) wide; stabling on the eastern site was increased by one to five 8-car trains; and additional office and accommodation space was specified.[79]

The depot was officially opened by Patrick McLoughlin (MP) in October 2015.[80] The completed main facilities building (MFB) was 256 by 40 metres (840 by 131 ft) with five roads, each with full underfloor inspection facilities, and a light (2.5t) crane. One road had two bogie drops, and a road was fitted with 25kV AC electrification for static tests though the main building was unelectrified (third rail). Wheel lathes and carriage washes were outside the MFB.[81]

Hornsey

Lua error in package.lua at line 80: module 'strict' not found.

Network Rail submitted a planning application in August 2009;[82] the development was split across sites east of the main railway line: the main maintenance building was north of Hornsey railway station and the A504 road (High Street/Turnpike Lane); storage sidings were located south-east of Hornsey station, adjacent to the pre-existing Hornsey EMU depot.[83]

The northern site was on rail sidings ('Coronation sidings'/'Hornsey sidings') which had been developed on made embankments from the later 19th century to early 20th century, the southern stabling area was on land that had been extensively developed as railway sidings since the early 20th century.[84][85][86]

The proposed development required bridge widening of the crossing of Turnpike lane, and additional embankment work and extensions.[87] The main maintenance building was a six-road 40 by 280 m (130 by 920 ft), 13.4 m (44 ft) high single-ended train shed, with an adjacent train wash (west) and a two-storey 12 by 117 m (39 by 384 ft) warehouse adjacent to the east.[88] The southern site included sidings for eleven 12-car trains and two 8-car trains, with cleaning and controlled emission toilet facilities.[89]

In 2009 John Denham, Secretary of State for Communities and Local Government blocked the development of the depot – the development had been subject to local and council objections on grounds including negative impact to a conservation area, as well as a potential negative impact to Haringey Council's "Haringey Heartlands" redevelopment project.[61][90]

A revised two-depot plan was produced: the southern (Three Bridges) depot was expanded to a five-road shed, while estimates for total maintenance roads required had been reduced from nine to eight. The northern depot was required to be only a three-road depot; the depot was to be suitable for 12-car trains, with wheel lathe, cleaning, warehousing and stabling facilities. Potential sites for the northern depot were reassessed and possible options reduced to three: a main depot at Coronation Sidings Hornsey; a main depot adjacent to the existing depot at Hornsey; and a site at Chesterton, Cambridge – a depot reduced in size on the site of the original plan was chosen as the best option for Network Rail.[91] The revised plan was submitted in 2011, with the main depot reduced approximately 2 m (6 ft 7 in) in height, and nearly half the area, and with estimated employment figures reduced from 270 to 120 people.[62] Rail union RMT criticised the loss of employment opportunities due to the reduced scale of the plans,[92][93] stating "Without anyone trying, Haringey has lost 150 jobs";[94] the revised scheme continued to produce significant opposition from local residents, with concerns including noise and light pollution during night working, as well as visual impact and traffic.[93][95]

The main depot was a 278 by 21.6 m (912 by 71 ft) three-road 11.3 m (37 ft) high single-ended shed, with a two-storey 182 by 12 m (597 by 39 ft) warehouse adjacent east, and a 50.6 by 6.5 m (166 by 21 ft) train-washing building adjacent west; facilities at the depot were to include equipment for heavy overhaul, with overhead synchrononsied lift cranes on one road. The southern site, adjacent to the pre-existing First Capital Connect (FCC) EMU depot, would include CET facilities, another 50.6 by 6.5 m (166 by 21 ft) train-washing building, a 260 by 7 m (853 by 23 ft) underfloor cleaning building, and shunter's cabins. Wheel-lathe facilities were to be shared with a pre-existing installation at the FCC depot. Existing sidings adjacent to the FCC depot were to be rebuilt to provide 16 roads – four arrival and departure roads, and 12 storage roads. Civil engineering work included bridge-widening across Turnpike Lane (A51) and a culverted waterway, as well as minor embankment works, and rebuilding of a footbridge at Hornsey station.[96][97][98]

The plan was given permission in late 2011.[99]

See also

Notes

  1. Up to 24 trains per hour in central London.[6]
  2. The 240 m long trains were expected to be of "outer-suburban" or "commuter" type, while the 162 m trains were expected to have both "metro" and "surburban" passenger accommodation types.[7]
  3. The development was a 'permitted development' under Part 11 of the Town and Country Planning (General Permitted Development) Order 1995; the application still required local council approval for certain aspects of the works including the main maintenance building and bridge widening.[66]
  4. The site is located in the 'fork' between the 1841 London and Brighton Railway; the Arun Valley Line (built by the London Brighton and South Coast Railway (LB&SCR) 1848); and the 1855 Tunbridge Wells West Railway (see Three Bridges to Tunbridge Wells Central Line).[67]
  5. The new sidings required the demolition of an existing shed used for stabling of Bombardier Voyager trains.[78]

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 2.2 2.3 2.4 2.5 2.6 Lua error in package.lua at line 80: module 'strict' not found.
  3. 3.0 3.1 3.2 3.3 3.4 3.5 3.6 3.7 3.8 Lua error in package.lua at line 80: module 'strict' not found.
  4. 4.0 4.1 4.2 Lua error in package.lua at line 80: module 'strict' not found.
  5. Our Commitments : Thameslink
  6. 6.0 6.1 6.2 6.3 6.4 Sources:
    • Lua error in package.lua at line 80: module 'strict' not found.
    • Lua error in package.lua at line 80: module 'strict' not found.
    • Lua error in package.lua at line 80: module 'strict' not found.
  7. 7.0 7.1 7.2 Lua error in package.lua at line 80: module 'strict' not found.
  8. 8.0 8.1 8.2 8.3 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 11.2 Lua error in package.lua at line 80: module 'strict' not found.
  12. 12.0 12.1 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. 15.0 15.1 Sources:
    • Lua error in package.lua at line 80: module 'strict' not found.
    • Lua error in package.lua at line 80: module 'strict' not found.
      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. (subscription required)
  17. 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. 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. Lua error in package.lua at line 80: module 'strict' not found.
  26. 26.0 26.1 26.2 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. 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. 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.
  39. Lua error in package.lua at line 80: module 'strict' not found.
  40. 40.0 40.1 Lua error in package.lua at line 80: module 'strict' not found.
  41. http://www.londontravelwatch.org.uk/documents/get_lob?id=3865&age=&field=file
  42. 42.0 42.1 Lua error in package.lua at line 80: module 'strict' not found.
  43. Küter 2012.
  44. 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. 47.0 47.1 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. Pritchard & Hall 2014, pp. 336, 339.
  55. Lua error in package.lua at line 80: module 'strict' not found.
  56. Pritchard & Hall 2014, pp. 336, 339, 341.
  57. Pritchard & Hall 2014, p. 336.
  58. Network Rail & ARUP 2009, Planning Statement, 2.2. pp.5–6.
  59. Network Rail & ARUP 2009, Planning Statement, 2.2.2. pp.5–8.
  60. Network Rail & ARUP 2009, Planning Statement: 2.2.3–2.25, pp.8–10.
  61. 61.0 61.1 Lua error in package.lua at line 80: module 'strict' not found.
  62. 62.0 62.1 62.2 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. Network Rail & ARUP 2009.
  66. Network Rail & ARUP 2009, Planning Statement: 2.3, pp.10–14.
  67. Network Rail & ARUP 2009, Design and Access Statement. 3.1 p.6.
  68. Ordnance Survey. 1:2500. 1873–4, 1897, 1910
  69. Network Rail & ARUP 2009, Planning Statement ,3.1.1–3.1.3. p.14.
  70. Network Rail & ARUP 2009, Environmental Statement (non-technical summary). 3. p.5.
  71. Network Rail & ARUP 2009, Environmental Statement (non-technical summary). 4. p.7, fig.2 p.8.
  72. Network Rail & ARUP 2009, Planning statement 3.2. pp.15–19.
  73. Network Rail & ARUP 2009, 3BR-GX-201 Three Bridges Site Plan.
  74. Network Rail & ARUP 2011, Planning statement. 1. p.3.
  75. Network Rail & ARUP 2011, Planning statement 1.2, pp.4–5.
  76. Network Rail & ARUP 2011, Planning statement 3.1.2 p.16.
  77. Network Rail & ARUP 2011, (3BR-GX-202 07) Revised Scheme Principal Changes.
  78. Network Rail & ARUP 2011, Planning statement. 3.2.1, Table 1, p.19.
  79. Network Rail & ARUP 2011, Planning statement 3.2 pp.18–38.
  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. Network Rail & ARUP 2009a.
  83. Network Rail & ARUP 2009a, Drawing 240809_22 Hornsey Site Plan, 1:1000, 207670-00 HOR-GX-201.
  84. Ordnance Survey. 1:2500. 1863, 1896, 1914, 1935
  85. Network Rail & ARUP 2009a, Cultural Heritage Baseline Information (Appendix D.) D7-D10.
  86. Network Rail & ARUP 2009a, Environmental Statement (REP-PL-HOR-0005). 3.1, p.12.
  87. Network Rail & ARUP 2009a, Environmental Statement (REP-PL-HOR-0005). 4.1, p.15; 4.10, p.17.
  88. Network Rail & ARUP 2009a, Environmental Statement (REP-PL-HOR-0005). 4.2–4.7, pp.15–17.
  89. Network Rail & ARUP 2009a, Environmental Statement (REP-PL-HOR-0005). 4.8–4.9, p.17.
  90. Lua error in package.lua at line 80: module 'strict' not found.
  91. Network Rail & ARUP 2011a, (REP-PL-HOR-001A) Planning Statement (Part C) Northern Depot Site Assessment Study.
  92. Lua error in package.lua at line 80: module 'strict' not found.
  93. 93.0 93.1 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. Network Rail & ARUP 2011a, Planning Statement (REP-PL-HOR-001A) 4-4.2.10 The Proposed Scheme, pp.14–20.
  97. Network Rail & ARUP 2011a, HOR-GX-201 Hornsey Site Plan.
  98. Network Rail & ARUP 2011a, HOR-GX-202 Hornsey Revised Scheme – Principle Changes.
  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.

Sources

  • Lua error in package.lua at line 80: module 'strict' not found.
  • Lua error in package.lua at line 80: module 'strict' not found.
  • Lua error in package.lua at line 80: module 'strict' not found.
  • Lua error in package.lua at line 80: module 'strict' not found.
  • Lua error in package.lua at line 80: module 'strict' not found.
  • Lua error in package.lua at line 80: module 'strict' not found.
  • Lua error in package.lua at line 80: module 'strict' not found.

Further reading

  • Lua error in package.lua at line 80: module 'strict' not found.
  • Lua error in package.lua at line 80: module 'strict' not found.

External links