Oyster card (pay as you go) on National Rail

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

The acceptance of Oyster card pay as you go (PAYG) on National Rail in London, England, was limited to a restricted number of National Rail services[1] at the introduction of the stored-value product on London Underground in January 2004.[2] In response to an offer from Transport for London of funding to the train operating companies that have services within Greater London, plans were made to expand its acceptance across the rail network in London,[3] and it was expected that by February 2009 TFL would announce plans for all suburban trains to accept the card.[4] In May 2009 London TravelWatch indicated it had discovered that the works were unlikely to be completed until 2010.[5] On 23 November 2009 the GLA announced that from 2 January 2010 the vast majority of rail services in Greater London would accept Oyster PAYG.[6]

Background

The Oyster card was launched in 2003 with the facility to hold season-ticket Travelcards, accepted on both London Underground and National Rail services. In January 2004, a PAYG product was launched for use on London Underground and DLR, but only a limited number of National Rail operators accepted the product on parts of their routes, usually because their tickets were interchangeable with London Underground ticketing under long-standing agreements. Transport for London (TfL) and National Rail publish lists and maps of routes and stations where PAYG is valid.[1][7]

In May 2006 TfL and the Department for Transport agreed a £20 million funding package for train operators to install the equipment necessary to accept PAYG at all London stations.[8] The package was not taken up by any train operating companies and in September 2006, the South West Trains franchise was renewed by the Department for Transport with the condition that smartcard ticketing must be in place by 2009.[9] In November 2007 the metro routes operated by Silverlink were brought under the control of TfL and operated under the brand name London Overground, accepting Oyster PAYG.[10]

A necessary precursor of the acceptance of Oyster PAYG was the introduction of zonal single fares on the National Rail network in London; this was implemented in January 2007.[11] Also in January, the then Mayor of London Ken Livingstone announced that he required operators to sign up by 31 January 2007 in order to receive the funding package offer.[12] c2c and Chiltern Railways accepted the deal and on 31 January 2007, a commitment was made by ATOC, in principle, that all other operators would eventually accept the PAYG product.[3] According to ATOC, roll-out plans were subject to the installation of suitable ticket gates and back office equipment at all 330 stations. A 2009 date was set out for this to be finished by.[13]

Current acceptance and future schedule

The acceptance of Oyster PAYG on National Rail has now been implemented across the Travelcard area (Zones 1-9), and at additional stations including Watford Junction, some Abellio Greater Anglia stations and c2c stations at Purfleet, Ockendon, Chafford Hundred and Grays. Oyster PAYG is not valid on Heathrow Connect between Hayes and Harlington and Heathrow Airport, Heathrow Express. Oyster PAYG is now available on Southeastern highspeed between St Pancras International and Stratford International stations only.

TfL and BAA studied acceptance of Oyster PAYG on BAA's Gatwick Express and Heathrow Express in 2006, but BAA decided not to go ahead. [14]

In October 2007, it was agreed by all National Rail Operators who operate services in London to implement the scheme by 2009 at the latest, as a result of both pressure from passengers and TfL. An agreement was reached with TfL to accept Oyster PAYG at all National Rail stations in Greater London. As a result of this implementation, ticket barriers with readers have been installed at some National Rail stations to prevent fare evasion, for example, London Waterloo from 2008.[15]

It was announced in late 2009 that all London National Rail services would accept Oyster PAYG from 2 January 2010, although fares may not be the same as for a comparable Tube journey.[16]

In the Chancellor's Autumn Statement in November 2011, expansion of the Oyster system was reported covering towns such as Guildford.[17] This appears to have been mistaken reporting, the Chancellor only referred explicitly to 'smart ticketing' being introduced, presumably the ITSO scheme being driven by DfT.

As of 2 January 2013, the current arrangement and planned implementation schedule will be as follows:

Operator 2004 implementation[2] Expansion implemented[1] Zones 1—6 completed Expansion planned
Abellio Greater Anglia Liverpool Street to Walthamstow Central, Seven Sisters and Tottenham Hale (not at intermediate stations)
Liverpool Street to Stratford
2006: Stratford to Tottenham Hale and Seven Sisters
Jan 2008: intermediate stations[18]
2 January 2010: all remaining stations
2 January 2013: Turkey Street and Enfield Lock to Broxbourne; Harold Wood to Shenfield
19 October 2015 Rye House, St. Margarets, Ware and Hertford East[19]
YesY
c2c Fenchurch Street to Upminster
Liverpool Street to Barking via Stratford (not at Forest Gate or Maryland)
Jan 2008: Barking to Rainham[20]
2 January 2010: Upminster/Rainham to Grays
YesY None.[21]
Chiltern Railways Marylebone to Amersham
Marylebone to West Ruislip (South Ruislip only intermediately)
Jan 2008: intermediate stations [22][23]
April 2008: London Paddington to South Ruislip[24]
YesY
Thameslink and Great Northern Kentish Town to London Bridge, Elephant & Castle or Moorgate
Finsbury Park to Moorgate or King's Cross
2007: Kentish Town to West Hampstead Thameslink[25]
2 January 2010: all remaining stations
YesY By 2016: East Croydon to Gatwick Airport
: Elstree & Borehamwood to Luton Airport; Crews Hill to Hertford North and Hadley Wood to Welwyn Garden City[26]
First Great Western Jan 2008: Ealing Broadway to Greenford (not at intermediate stations)
April 2008: London Paddington to Ealing Broadway (not at Acton Main Line)
Sept 2008: remaining stations[27]
YesY TBC: Heathrow Connect services between Hayes & Harlington and Heathrow [28]
2018: West Drayton to Reading [29]
London Midland Euston to Harrow & Wealdstone 2007: Watford Junction to Harrow & Wealdstone[30] YesY
London Overground Euston to Harrow & Wealdstone
(not at Kilburn High Road or South Hampstead)
Gunnersbury to Richmond
Stratford to Canning Town (closed 2006)[1]
2007: all remaining stations
YesY Any future lines that become part of London Overground.
Southeastern Elephant & Castle to City Thameslink [31] 2 January 2010: all remaining stations
31 July 2015: St Pancras International to Stratford International on HS1.[32]
6 September 2015: Dartford.[33]
YesY TBC: Barnehurst, Slade Green, Crayford.
Swanley by 31 December 2016.[34]
Southern 2007: Clapham Junction to Watford Junction
November 2009: London Victoria to Balham [35]
2 January 2010: all remaining stations
YesY By 2016: Purley to Gatwick Airport (& TBC: Reigate)
South West Trains 2 January 2010: all stations YesY TBC: Hampton to Shepperton [29] According to SWT, rollout is on hold for unknown reasons.

See also

References

  1. 1.0 1.1 1.2 1.3 Lua error in package.lua at line 80: module 'strict' not found.[dead link]
  2. 2.0 2.1 Transport for London, Your Guide to Oyster, (2004)
  3. 3.0 3.1 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. Lua error in package.lua at line 80: module 'strict' not found.
  7. Lua error in package.lua at line 80: module 'strict' not found.[dead link]
  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. 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. 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.[dead link]
  25. Lua error in package.lua at line 80: module 'strict' not found.[dead link]
  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. Lua error in package.lua at line 80: module 'strict' not found.
  29. 29.0 29.1 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.[dead link]