Tackley railway station

From Infogalactic: the planetary knowledge core
Jump to: navigation, search
Tackley National Rail
265px
Location
Place Tackley
Local authority West Oxfordshire
Coordinates Lua error in package.lua at line 80: module 'strict' not found.
Grid reference SP484205
Operations
Station code TAC
Managed by Great Western Railway (train operating company)
Number of platforms 2
DfT category F2
Live arrivals/departures, station information and onward connections
from National Rail Enquiries
Annual rail passenger usage*
2002/03 Decrease 18,195
2004/05 Increase 20,382
2005/06 Decrease 18,811
2006/07 Decrease 18,300
2007/08 Increase 19,294
2008/09 Increase 19,610
2009/10 Increase 20,250
2010/11 Increase 20,896
2011/12 Increase 34,372
2012/13 Decrease 20,934
2013/14 Increase 20,996
History
Key dates Opened 6 April 1931 (6 April 1931)
Original company Great Western Railway
Post-grouping Great Western Railway
National RailUK railway stations

A B C D E F G H I J K L M N O P Q R S T U V W X Y Z

* Annual estimated passenger usage based on sales of tickets in stated financial year(s) which end or originate at Tackley from Office of Rail and Road statistics. Methodology may vary year on year.
UK Railways portal

Tackley railway station is on the Cherwell Valley Line in Oxfordshire, England. serves the village of Tackley and its surrounding area. First Great Western operates the station and all but one of the trains serving it. The exception is a weekday late night service at 0048 to Banbury operated by Chiltern Railways.

History

When the Oxford – Banbury section of the Oxford and Rugby Railway opened in 1850 the nearest station was Woodstock Road, which was at Enslow 1.5 miles (2.4 km) south of Tackley. In the 1930s, in response to increasing competition from bus services, the Great Western Railway opened a number of new halts. One of these was Tackley, which was opened on 6 April 1931.[1]

Level crossing

File:Tackley Crossing FromEast.JPG
Tackley crossing no longer has gates for motor vehicles; only pedestrians, equestrians and cyclists can use it
File:Tackley Crossing SignsEast.JPG
Some of the signs on the east side of Tackley crossing

The GWR sited Tackley halt just north of a level crossing on the road linking Tackley with the village of Kirtlington.[1] This had a crossing keeper on duty 24 hours a day and the gates were interlocked with the railway signalling system.[1] However, the route later ceased to be a through road between the two villages, so the railway company withdrew the crossing keeper and redesignated the crossing to be operated by its users.[1]

It was then made an occupation crossing and the only vehicles allowed to use it were those authorised to have access to Tackley Estate.[2] It had large gates for vehicles and small ones for pedestrians.[2] This was still the case in 2009,[2] but by 2012 the large gates had been replaced by fences and the surface for vehicles to cross the tracks had been removed (see photo).

The crossing is used by a bridleway linking Tackley and Kirtlington, which is now also part of National Cycle Route 51.[2] The crossing is also the only passenger access to and from the "up" platform (i.e. for trains from Banbury or to Oxford, Reading and London).[2] As of 2009 Network Rail had 165 unprotected level crossings related to its stations, 26 of which were defined as "user-worked" or "footpath crossings".[1] However, Tackley crossing is the only one that combines station access with a public bridleway.[1]

Bridge and subway proposals

File:Tackley 165104-2.jpg
A First Great Western Class 165 train from Oxford to Banbury passing through the crossing into Tackley station

In 1999 Railtrack plc launched its Reading – Birmingham Cross Country Route Modernisation Project, which was to increase maximum speeds from 90 miles per hour (140 km/h) to 110 miles per hour (180 km/h) ready for Virgin CrossCountry's plan to introduce its new Voyager trains in 2002 (Operation Princess).[3] Higher train speeds would increase the risk of a train colliding with someone on a user-worked level crossing, so in 2000 Railtrack asked West Oxfordshire District Council (WODC) for planning permission to build a footbridge.[4] The bridge would serve passengers and other pedestrians but not vehicles, so the level crossing would have to remain.[4]

In 2001 WODC refused planning permission for a footbridge purely because of its appearance.[4] The council declared "that the proposed footbridge will, by reason of its size, design and use of materials represent an alien, incongruous and overtly urban feature in this rural location".[4] In 2002 Railtrack responded by requesting planning permission for a subway under the railway for pedestrians, equestrians and cyclists.[4] Railtrack and the Tackley Estate agreed an alternative route for vehicluar access,[4] and thus it would be possible to close the crossing completely. Because of the topography of the site, the subway would have to be 90 metres (300 ft) south of Tackley station.[4] WODC again refused planning permission, this time asserting "the design's failure to make safe and convenient provision for horses, their riders, pedestrians, cyclists, the elderly and disabled people; and that the subway would appear as an unduly prominent and intrusive feature in the rural scene".[5] Oxfordshire County Council supported WODC's refusal.[5]

At the same time the Department for Transport removed Railtrack from controlling Britain's rail network. The DfT created a new company, by Network Rail (NR), which revised the subway proposal and lodged a planning appeal against WODC's refusal of planning permission for it. [5] A planning inspector visited the crossing[5] and, unlike WODC, commented that the subway would improve access to and from the "up" platform for passengers with some types of disability.[5] In July 2003 the inspector upheld NR's appeal and granted planning permission for the subway.[6]

However, in September 2002 Virgin CrossCountry had already introduced its accelerated timetable and by July 2003 NR had nearly finished the CrossCountry Route Modernisation,[6] but without increasing train speeds through Tackley station. NR was drawing the project to a close and it did not implement the plan for a subway at Tackley.[6] The planning permission was valid for five years and lapsed, unused, in July 2008.[6]

Fatality and near miss

File:Tackley Crossing SignsWest.JPG
Warning signs and telephone to the signalling control centre on the west side of the crossing

Tackley crossing had a good safety record from at least 1990 (the year when the Rail Safety and Standards Board's records start) until 2008.[7] However, on 31 March 2008 Margaret Evans, an 82-year-old Tackley resident,[8] was struck and killed by a CrossCountry Voyager train while she was crossing to the up platform to catch a local train to Oxford.[9] On 16 February 2009 another CrossCountry Voyager train had a near miss with someone using Tackley crossing.[10]

The Rail Accident Investigation Branch (RAIB) found that the immediate cause of the 2008 fatality was that Mrs Evans stepped into the path of the express train,[11] either because she did not hear it coming or because she hear it and thought it was the local train to Oxford that she intended to catch.[12] However, the RAIB also identified a problem with the "decision point", i.e. the place at which a user would decide where to cross relative to the track, the gates, the warning signs and the limited visibility of trains on the "up" track.[12] It also identified WODC's refusal of planning permission for an alternative, safer crossing as an "underlying factor" in the accident.[12]

The RAIB made a number of additional observations in its report on the fatality.[13] These included that the "whistle boards" telling train drivers where to sound the train horn to warn users were less than the permitted maximum 400 metres (1,300 ft) distance from the crossing,[13] and that this gave users 7.9 seconds' warning of the approach of an "up" train.[14] Lineside vegetation reduced the sighting distance for approaching trains, and communications to NR's maintenance department about the need to control vegetation at this site for this reason were not good enough.[13] When Mrs Evans was killed, the train that hit her was the only one in the vicinity. However, the RAIB noted that when a train is standing at the "down" platform, visibility of trains approaching on the "up" track is reduced to only three seconds.[13]

By the time the RAIB completed its report, NR had reduced the height of a fence on the northwest side of the crossing that had reduced users' ability to see trains approaching on the "up" track.[15] This had reduced the risk at the crossing, but the RAIB stated that the near miss in February 2009 "suggests that there are still issues with sighting at the crossing".[15]

In 2009 RAIB reported that NR was reviewing options to replace Tackley crossing with a bridge for pedestrians, equestrians and cyclists, plus a diversion for vehicular access to the Tackley Estate by a different route.[15] The vehicular diversion was implemented, but as of June 2014 Tackley station still has no bridge so pedestrians, equestrians and cyclists still have to use the level crossing.

Route

Preceding station National Rail National Rail Following station
Heyford   Chiltern Railways
Banbury to Oxford
Limited Service
  Oxford
  First Great Western
Cherwell Valley Line
 
Historical railways
Heyford
Line and station open
  British Railways   Bletchington
Line open, station closed

References

File:Tackley Station UpPlatform.JPG
The "up" platform has a small shelter.
File:Tackley 165104.jpg
The rear of a First Great Western Class 165 train from Oxford to Banbury about to depart from the "down" platform.
  1. 1.0 1.1 1.2 1.3 1.4 1.5 RAIB 2009, p. 13.
  2. 2.0 2.1 2.2 2.3 2.4 RAIB 2009, p. 8.
  3. RAIB 2009, p. 20.
  4. 4.0 4.1 4.2 4.3 4.4 4.5 4.6 RAIB 2009, p. 21.
  5. 5.0 5.1 5.2 5.3 5.4 RAIB 2009, p. 22.
  6. 6.0 6.1 6.2 6.3 RAIB 2009, p. 23.
  7. RAIB 2009, p. 14.
  8. Lua error in package.lua at line 80: module 'strict' not found.
  9. RAIB 2009, p. 6.
  10. RAIB 2009, pp. 31, 32.
  11. RAIB 2009, p. 24.
  12. 12.0 12.1 12.2 RAIB 2009, p. 30.
  13. 13.0 13.1 13.2 13.3 RAIB 2009, p. 31.
  14. RAIB 2009, p. 15.
  15. 15.0 15.1 15.2 RAIB 2009, p. 32.

Sources

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

External links