2015 Wootton Bassett rail incident

Charter train passed a signal at danger

Wootton Bassett rail incident

34067 Tangmere was the locomotive hauling the charter train

Location of Wootton Bassett Jn in Wiltshire

Details
Date| 7 March 2015
17:25 UTC
Location| Wootton Bassett Junction, Wiltshire
Coordinates| 51°32′07″N 1°54′20″W﻿ / ﻿51.53528°N 1.90556°W﻿ / 51.53528; -1.90556
Country| United Kingdom
Line| Great Western Main Line
and South Wales Main Line
Operator| West Coast Railway Company
First Great Western
Incident type| SPAD
Cause| Traincrew error: mishandling of AWS and braking system on train.
Statistics
Trains| Two
Passengers| 717
Crew| ~45
grid reference SU 066 818

On 7 March 2015, a steam-hauled charter train passed a signal at danger and subsequently came to a stand across a high-speed mainline junction near Wootton Bassett Junction, Wiltshire, England. Another train, which had right of way, had passed through the junction 44 seconds earlier and no collision occurred nor was any damage done.

As a result of this signal passed at danger (SPAD), Network Rail banned the train's operator, West Coast Railway Company (WCRC), from operating trains anywhere on the British railway network. The Rail Accident Investigation Branch (RAIB) opened an investigation into the incident, which it called a "dangerous occurrence". The incident was rated the most serious SPAD in the United Kingdom since December 2010. Following improvements made by WCRC, the ban was lifted. A subsequent incident led to a further ban, which was later lifted.

In December 2015, the Office of Rail and Road initiated a prosecution against the driver of the train and WCRC for offences under the Health and Safety at Work Act 1974. The case was heard in June 2016. Both WCRC and the driver of the train pleaded guilty. WCRC was fined £200,000 plus costs. The driver received a sentence of four months' imprisonment, suspended for eighteen months.

In May 2016, the RAIB published a report on the incident, which largely blamed the incident on the train crew tampering with a safety system that would otherwise have safely brought the train to a halt.

## Incident[edit]

* v
* t
* e

2015 Wootton Bassett SPAD

Legend

|  |  |

|  |

| Great Western Main Line

to Bristol Temple Meads

|  |

|  |

SN43

|  |

|  | Temporary speed restriction
|  |

|  |

SN45

|  |

|  |

Stone terminal siding

|  |

|  |
|  |

|  |

| South Wales Main Line

to Bristol Parkway

|  |

|  |
|  |

|  |
|  |

|  | Wootton Bassett Junction
|  |

|  |
|  |

|  |
|  |

|  |

| Great Western Main Line

to London Paddington

|  |  |  |  |  |

Key

|  |  |

|  |

Path of WCRC charter train

|
|
|
|

|  |

|  |

Path of FGW passenger train

|  |

|  |

Other lines

|  |

|  |

Signals

|  |  |  |  |  |

At 17:25 GMT on 7 March 2015, a charter train approached Wootton Bassett Junction, where the Great Western Main Line and South Wales Main Line diverge at Royal Wootton Bassett, Wiltshire. In the approach to signal SN43, an Automatic Warning System (AWS) magnet was present in the trackbed, warning of a temporary speed restriction ahead.[1] The line speed was 125 miles per hour (201 km/h). The temporary restriction of 85 miles per hour (137 km/h) then in force[2] did not apply to the train as steam locomotives are restricted to a maximum of 75 miles per hour (121 km/h) on Network Rail (NR) tracks in any event.[3] An emergency brake application occurred on the train after it had passed over the magnet because the driver failed to press the AWS cancelling button within 2.7 seconds.

The driver should have allowed the train to come to a stand and contacted the signalman,[4] but he did not. Instead the AWS isolating cock was operated, releasing the brake after the train's speed had been reduced from 59 miles per hour (95 km/h) to about 51 miles per hour (82 km/h). This had the effect of isolating both the AWS and the Train Protection & Warning System (TPWS), rendering them unable to apply the brakes. Although the driver was permitted to operate the isolating cock under certain fault conditions, he did not follow the British Railway Rule Book protocol or inform the signaller that he had done so.[5]

The next signal, SN45, was displaying a red (danger) aspect. By the time the driver saw this, there was insufficient distance available to stop the train,[1] which eventually came to a stand on the junction some 700 yards (640 m) past the signal. The service train that was being protected by the red signal had already passed through the junction and no collision occurred.[6] As the points had already moved for the passage of the charter train, no damage was done to the trackwork at Wootton Bassett Jn.[3] The line speed approaching the junction was 70 miles per hour (110 km/h) for the service train.[7] Before he was relieved from driving duties, the driver of the charter train claimed that signal SN43 had displayed a green (proceed) aspect. NR investigations showed that a single yellow (caution) aspect was displayed.[7]

Following the incident, the driver was relieved at Swindon. There a new driver was supplied by West Coast Railway Company (WCRC) who drove the train to Southall, where the train was terminated.[8]

The incident was rated the most serious SPAD since December 2010, rating 25 out of 28 on Network Rail's scale. Any SPAD rated at 20 or more leads to a mandatory investigation by the Office of Rail and Road (ORR).[9] The scale is logarithmic, with each increment rated twice as serious as the previous;[9] thus the incident was rated as nominally over thirty times more serious than this threshold. The December 2010 SPAD was rated at 26, and was at Uphill Junction, Somerset, on the Bristol to Exeter line when a passenger train overran a signal by 180 yards (160 m). The month before that incident, a passenger train overran a signal at Tamworth, Staffordshire, in an incident rated at 25.[10]

### RAIB investigation findings[edit]

The RAIB investigation into the accident reported that the outward working, reporting number 1Z21, the 07:22 from Southend East to Bristol Temple Meads, had been fitted with a numbered plastic tie on the handle of the Automatic Warning System (AWS) isolating cock. The train was driven to Bristol without incident, although some misting of the driver's window was reported. The driver of that train was not the driver later involved in the SPAD at Wootton Bassett. During an empty coaching stock movement to St Philip's Marsh depot, the emergency brake applied because the driver did not cancel an AWS warning in the allotted time. The AWS isolating cock was opened, breaking the seal. On leaving St Philip's Marsh, a similar incident occurred, and the AWS isolating cock was opened again. There was a change of traincrew on arrival at Bristol Temple Meads, where the return working was designated 1Z67. According to the rulebook, the driver of the train should have reported the missing seal on the AWS isolating cock. The train should not have been allowed to depart until the cock had been sealed. The driver did not do this, and set off with an unsealed cock.[11]

Due to misting and exhaust obstructing the driver's view through the window, the driver drove leaning out of the cab for much of the time. This made hearing the AWS sounder and observing the AWS reminder light harder. Approaching signal SN43, there was a temporary speed restriction of 85 miles per hour (137 km/h), which was warned of by a temporary AWS magnet in advance of the restriction, and indicated by a sign at the start of the temporary speed restriction.[11] The train approached signal SN43 at 59 miles per hour (95 km/h) and passed over the temporary AWS magnet. The driver failed to react to the warning given within the time allowed and the brakes were applied. Because the AWS isolating cock was out of reach of the driver, he instructed the fireman to open it for him. The train's speed had reduced by about 8 miles per hour (13 km/h) when the brakes were released. The rules require that the train is brought to a stand and the signaller contacted in the event of an AWS brake application.[11] Additionally the driver must inform the signaller whenever the AWS is isolated;[5]

> "Driver: If it becomes necessary to isolate the AWS, you must:

>   * stop your train immediately
>   * tell the signaller
>   * not move the train until instructed to do so
>   * carry out the instructions given."

The train then passed signal SN43, which was displaying a single yellow (caution) aspect. The driver acknowledged the AWS warning, but did not reduce speed.[1]

In the twelve seconds between brake application and brake release, the train passed over the fixed AWS magnet for signal SN43, which was displaying a single yellow (caution) aspect. This warning was cancelled in time. The train then passed over the TPWS+ overspeed sensor for signal SN45, which was displaying a red (danger) aspect. As the train was travelling more slowly than the trigger speed, no brake action was demanded from the train. The train then passed over the second TPWS overspeed sensor for signal SN45, this time at 53 miles per hour (85 km/h), which was in excess of the 45 miles per hour (72 km/h) trigger speed. Consequently, a TPWS intervention occurred, but as the AWS isolating cock was open the brakes did not apply. When the driver saw that signal SN45 was at danger, he applied the brakes on the train. Due to there being insufficient distance to stop, the train overran the signal by 600 yards (550 m) and came to a stand across Wootton Basset Junction.[11]

Then the driver reported to the signaller by radio, claiming that the signals had not sequenced properly (i.e. that SN43 had been green). During the time that he was on the radio, the fireman closed the AWS isolating cock. The signaller initially treated the event as a Technical SPAR (i.e., Signal Passed at Red due to an Irregular Signal Sequence) because there was no SPAD alarm provided for signal SN45[11] and the driver had claimed that the preceding signal was displaying a green aspect. Because this is not a safety-critical event he authorised the driver to take the train forward to Swindon. However, by the time the train arrived at Swindon, it was understood that signal SN45 had been passed at danger without authority and the driver was relieved of his duties. The driver was not tested for the presence of drugs or alcohol in his system, as is required by Railway Group Standards. The investigation found that there was no evidence of alcohol in his system. Prescription drugs that he was taking were assessed as not having an effect on his ability to drive the train. Fatigue was found not to be a factor.[11]

The investigation found that crewing of the train was insufficient. There was no traction inspector on board. WCRC had discontinued the use of traction inspectors by 2012. A traction inspector's duties include assisting the driver with the sighting of signals. Two members of the train support crew were also on the footplate of Tangmere, but they had no responsibility in respect of the operation of the train. No problems were found with the ability to sight signals SN43 and SN45. The locomotive and carriages from the train were tested separately following the incident; no fault was found with either, although some of the sensors were not being recorded by the On Train Data Recorder (OTDR). The RAIB were able to reconstruct the sequence of events from the data that was recorded by the OTDR.[11]

The investigation found that the fixed AWS magnet for signal SN43 was incorrectly positioned. It was located 304 yards (278 m) from the signal, instead of the standard 200 yards (180 m). The actual location of signal SN43 was 13 yards (12 m) closer to the junction than shown on signalling diagrams, which was at 83 miles 54 chains (134.66 km) from London. These errors meant that the placing of the AWS magnet for the temporary speed restriction was also incorrect. Instead of being 244 yards (223 m) from the fixed AWS magnet, the temporary AWS magnet for the speed restriction was only 190 yards (170 m) from it. The installation of signal SN43 was in 1978, and the errors had remained undetected since then. An emergency speed restriction had been introduced in January 2015 due to the condition of the track, and had subsequently been converted to a temporary speed restriction. These errors were found not to have been contributory factors in the incident.[11]

The safety culture at WCRC was found by the investigation to be weak. This was evidenced by a number of factors, including the lack of traction inspectors, failure to test for drugs and alcohol, failure to download data from OTDRs to analyse individual driver performance, failure to maintain OTDR equipment correctly, failure to report missing seals on safety equipment where they were required to be fitted, failure to keep proper records, and failure to improve following the incident at Bell Busk (detailed below).[11]

## Trains[edit]

First Great Western HST, similar to that which passed Wootton Bassett Junction a minute before the charter train came to a halt across the junction.

### Charter train[edit]

The charter train, reporting number 1Z67,[1] was a steam-hauled passenger train, the 16:35 Cathedrals Express charter from Bristol Temple Meads to Southend East, Essex.[8][12] The train was hauled by Battle of Britain-class locomotive 34067 Tangmere (TOPS number 98 767[8]). Tangmere was hauling thirteen carriages,[1] which were a mixture of Mk 1s and Mk 2s.[6] The train was operated by WCRC.[1] There were 477 passengers and 39 staff on board the train.[13]

### Service train[edit]

The service train was the 15:28 Swansea to London Paddington,[12] reporting number 1L76.[8] It was operated by a First Great Western InterCity 125 "High Speed Train",[6] and was carrying about 240 passengers.[14]

## Investigations[edit]

The Rail Accident Investigation Branch opened an investigation into the incident, which it called a "dangerous occurrence".[1] One aspect of the investigation was whether the seals on the TPWS equipment were already broken before the train departed from Bristol, or were not in place at the time.[3] In March 2016, the RAIB published an update on their investigation.[15] The final report was released in May 2016. Five safety recommendations were made and one learning point was identified.[11]

The Rail Safety and Standards Board opened an investigation into the incident.[16] The ORR opened two investigations; one into WCRC's Safety Management System, with the second a criminal investigation.[17] The ORR subsequently charged WCRC and the driver of the train with various offences under the Health and Safety at Work Act 1974.[18] WCRC also opened an internal investigation into the incident.[19]

## Ban[edit]

### Network Rail[edit]

Looking west over Wootton Bassett Junction

Effective midnight on 3 April, NR banned WCRC from operating trains anywhere on the British railway network,[6] stating in the suspension notice that "the operations of WCR are a threat to the safe operation of the railway". Seven areas of deficiencies were identified.[20] WCRC was required to address five of them and show significant progress towards addressing the other two by 15 May. If this could be achieved, the ban would be lifted.[21] During the period that WCRC was banned from the rail network, it was still required to pay Track Access Charges to Network Rail.[20] This was the first time that a train operating company had been banned in the United Kingdom.[16]

Following improvements made by WCRC, the ban was lifted on 8 May.[22] A review of progress made was scheduled to be made after 3 months.[23]

### Office of Rail and Road[edit]

On 17 April, the ORR took steps to revoke WCRC's Safety Certificate. A process of representation was started, with parties having until 15 May to comment. The ORR's opinion was that WCRC's Safety Management System "is not able to ensure that services are being operated, designed or maintained safely".[24] On 21 May 2015, the ORR issued WCRC an improvement notice under the Railways and Other Guided Transport Systems (Safety) Regulations 2006.[25]

## Previous incident[edit]

On 12 July 2014, a charter train operated by WCRC, reporting number 1Z57,[26] caused a lineside fire at Bell Busk, North Yorkshire,[27] The train was headed by Hall-class locomotive 5972 Olton Hall, which was hauling a charter train from Carnforth, Lancashire to York. The fire was caused by a defect in the locomotive's ash pan which allowed a piece of burning coal to fall from the locomotive and land alongside the track.[2] Following the incident, WCRC was served with a Suspension Notice, which had the effect that WCRC was banned from operating steam locomotives on that route. It raised the issue with the Access Disputes Committee (ADC), calling Network Rail's actions "partial and malicious". The Suspension Notice was later partly lifted, allowing operation on routes where there was deemed not to be an enhanced fire risk.[26]

An investigation found that the crew of the train had not been advised that there was a raised fire risk at the time. WCRC was found not to have co-operated fully with the investigation. The ADC found that WCRC's Safety Management System was deficient due to confusion over whether or not the crew of the train had been informed of the increased fire risk. WCRC failed to inform Network Rail of its plans to try to prevent future incidents of a similar nature. The ADC found that this was in breach of WCRC's Safety Management System. WCRC chairman David Smith instructed his staff that no further correspondence would be gone into over the matter. The ADC found that this instruction was prejudicial to the safe operation of WCRC's Safety Management System.[27] The instruction was later rescinded. WCRC was also found to be in breach of its Track Access Contract.[26]

## Fallout[edit]

At the time of the ban, WCRC operated about 90% of all steam charter operations on Britain's railways.[28] DB Schenker was the only other operator licensed to run steam trains on Network Rail tracks.[29] DB Schenker has a policy of only operating air braked trains, whereas many trains operated by WCRC use vacuum brakes, which meant that DB Schenker was unable to operate those charters in place of WCRC.[30]

Steam Railway editor Howard Johnston said that the aftermath of the SPAD represented "possibly the greatest challenge to our movement".[28] ASLEF General Secretary Mick Whelan called for better regulation of crew driving charter trains.[31] Following the ban, eighteen charters were cancelled and eleven were postponed in the period 4 April – 5 May. DB Schenker and GB Railfreight operated three charters each. Companies affected included Belmond, Compass, NENTA Traintours, PMR Railtours, Railway Touring Company, SRPS Railtours, Statesman Rail, Steam Dreams and Vintage Trains.[32][33]

On 6 May, it was reported that The Jacobite season was likely to start late due to the suspension. The trains, which run on the West Highland Line in Scotland, were due to start running on 11 May for the start of the 2015 season.[34] Following the lifting of the ban on 8 May, it was announced that The Jacobite trains would run as scheduled from 11 May.[35]

In May 2015, Abellio ScotRail announced that as a result of the ban, it was reconsidering its decision to give WCRC preferred bidder status for a contract to run steam trains on the Waverley Line, which was scheduled to reopen between Edinburgh and Tweedbank in September 2015.[36]

In June 2015, it was reported that the ORR was planning to call a "Safety Summit" involving operators of charter trains on NR tracks. It was reported that one proposal to be put forward by the ORR was that all charter trains be limited to a maximum of eleven carriages. This, if enacted, would mean a loss of revenue of up to £5,000 per train for operators.[37][38] Part of the reasoning behind the proposal was that steam locomotives have a lower rate of acceleration than modern traction. As they are limited to 75 miles per hour (121 km/h), they have to be worked harder in order to maintain time. A reduction in train weight would make acceleration rates a little faster and reduce the need to work locomotives so hard.[39]

Despite many requests from Rail, WCRC chairman David Smith refused to comment on the incident.[7] In an interview with Steam Railway, he stated that the company was working to satisfy the seven demands made by Network Rail, and was only cancelling trains about a week in advance, in the hope that WCRC would be able to run trains again in the future.[40] Responding to a comment by Smith that "We are co-operating with the ORR in its enquiries, but from what we can see, all it is doing is keeping a watchful eye on what is going on", Rail editor Nigel Harris expressed astonishment at the "jaw-dropping" comments as criminal charges could lead to imprisonment following a guilty verdict. The reputational damage to WCRC was described as "possibly commercially fatal".[7] Rail contributor Pip Dunn said that WCRC refused to talk to journalists when negative stories concerning the company were being reported, yet was happy to when publicising a charter it was running.[3] On 28 May, WCRC issued a press release apologising for the distress, disappointment and inconvenience caused by the incident and events arising from it. It also thanked the ORR and others for assistance and support given. It stated that it was giving full assistance to the RAIB in respect of its investigation into the SPAD.[41]

In April 2015, the ORR was considering whether or not to prosecute WCRC, and subsequently decided to prosecute both WCRC and the driver of the train.[18] Although the suspension had been lifted by NR, the ORR could still have revoked WCRC's Safety Certificate at the end of the 28-day consultation period.[31][42] The lifting of the suspension by NR was subject to a review after three months.[43]

### Great Britain VIII[edit]

Great Britain VIII was a nine-day railtour, one of an annual series, from London to Cornwall, then to Scotland, and back to London. Various steam locomotives were scheduled to haul the train on each day of the tour, which was to have been entirely steam-hauled.[44] Participants paid between £1,995 and £2,895 per person for the nine-day tour,[17] which ran from 28 April to 6 May 2015.[45] Despite fears that the tour would be cancelled, it was run although with changes to the locomotives hauling it. DB Schenker agreed to operate the first two days of the tour.[46] The tour suffered a number of issues including steam locomotives being replaced by diesels, and a lack of train heating; these resulted in a significant number of passengers leaving the tour early.[17][44][46][47][48]

## Subsequent incident and further ban[edit]

On 2 October 2015, Black 5 steam locomotive 45231 Sherwood Forester was working a WCRC special through Doncaster when it was noticed that its TPWS had been isolated by the fireman.[49] As a result, in November 2015 a further prohibition notice was issued to WCRC by the ORR, suspending further steam services operated by them. It was reported that locomotives would need to have their TPWS modified to prevent the crew from being able to isolate it, before this suspension could be lifted.[50][51]

On 17 February 2016, the ORR served a Prohibition Notice on WCRC, citing a further seven incidents which had occurred since the SPAD at Wootton Bassett. The prohibition was to become effective from 18 February 2016 meaning that WCRC would "no longer be able to operate trains on the mainline network until such a time as [WCRC] can satisfy [the ORR] that its governance and operations meet industry practice and are fit for the scale of its operations". In addition the ORR found that the conditions for the revocation of WCRC's safety certificate had been met, which could have implications for WCRC's European train operator's licence.[49] This second prohibition was lifted on 23 March 2016.[52]

## Prosecution[edit]

On 9 December 2015, the ORR announced that WCRC and the driver of the train were to be prosecuted for offences contrary to the Health and Safety at Work Act 1974. An initial hearing was scheduled to be heard at Swindon Magistrates Court on 11 January 2016,[18] but postponed until 20 January.[53] When the case opened, neither the driver Melvyn Cox nor WCRC entered pleas. The case was committed to Swindon Crown Court, where it was scheduled to be heard on 19 February; unconditional bail was granted to Cox.[54] The case was subsequently postponed until 18 March,[55] and then further postponed to an undisclosed date in May 2016.[52] In late May, it was announced that the trial would begin on 27 June 2016.[56]

At the trial, both WCRC and Cox pleaded guilty. WCRC were fined £200,000 plus costs of £64,000. The fine imposed was half of the maximum that could have been imposed. This was decided by Judge Peter Blair QC after he took mitigating circumstances into account.[13] Cox was sentenced to four months imprisonment, suspended for eighteen months.[57] He was also ordered to do 80 hours unpaid work.[58] Cox's counsel stated in court that "he would never drive trains again".[13]

## References[edit]

1. ^ a b c d e f g "Dangerous occurrence at Wootton Bassett junction, Wiltshire". Rail Accident Investigation Branch. 27 March 2015. Retrieved 14 April 2015.
2. ^ a b Browne, Stefanie (15 April 2015). "Tension between NR and West Coast Railways escalates". RAIL. Peterborough: Bauer Media (477): 32–33. ISSN 0953-4563.
3. ^ a b c d Wolmar, Christian (29 April 2015). "Tangmere SPAD highlights the need for extra vigilance". Rail. Peterborough: Bauer Media (478): 38–39. ISSN 0953-4563.
4. ^ "Online Rulebook: Module TW1 - Section 1 (Abnormal brake applications)" (PDF). RSSB. Archived from the original (PDF) on 5 December 2016. Retrieved 29 June 2016.
5. ^ a b "Online Rulebook: Module TW5 - Section 4.4 (Isolating the AWS when in service)" (PDF). RSSB. Archived from the original (PDF) on 5 December 2016. Retrieved 29 June 2016.
6. ^ a b c d Brown, Stefanie (2 April 2015). "West Coast Railways track access suspended". RAIL. 46 (2): 168. doi:10.2979/reseafrilite.46.2.168. Retrieved 14 April 2015.
7. ^ a b c d Harris, Nigel (29 April 2015). "WCR is a major test for ORR". Rail. Peterborough: Bauer Media (478): 3. ISSN 0953-4563.
8. ^ a b c d Johns, Cedric (8 April 2015). "SPAD stops Tangmere at Wootton Bassett". Heritage Railway. Horncastle: Mortons Media Ltd (201): 59. ISSN 1466-3562.
9. ^ a b Streeter, Tony (24 April 2015). "Most serious SPAD since December 2010?". Steam Railway. Peterborough l: Bauer (440): 73. ISSN 0143-7232.
10. ^ Browne, Stefanie (29 April 2015). "SPAD rankings". Rail. Peterborough: Bauer Media (478): 8. ISSN 0953-4563.
11. ^ a b c d e f g h i j "Signal passed at danger on approach to Wootton Basset Junction, Wiltshire 7 March 2015" (PDF). Rail Accident Investigation Branch. Retrieved 8 May 2016.
12. ^ a b Browne, Stefanie (15 April 2015). "WCR "a threat to safe operation of the railway" – NR". Rail. Peterborough: Bauer Media (477): 6–7. ISSN 0953-4563.
13. ^ a b c Jones, Robin. "West Coast fined 200K for Wootton Bassett SPAD". Heritage Railway. Horncastle: Mortons Media Ltd: 16–17. ISSN 1466-3562.
14. ^ "Railway company's £264k bill as steam train driver blamed for 'near miss'". Swindon Advertiser. High Wycombe: Newsquest (Oxfordshire & Wiltshire) Ltd. 28 June 2016. Retrieved 29 June 2016.
15. ^ "Dangerous occurrence at Wootton Bassett junction - web site update and supplementary information" (PDF). Rail Accident Investigation Branch. Retrieved 9 March 2015.
16. ^ a b Quine, Adrian (12 April 2015). "Off the rails. Future in doubt for West Coast steam trains 'run like private toy'". The Daily Telegraph. Retrieved 15 April 2015.
17. ^ a b c Browne, Stephanie (13 May 2015). "Network Rail refuses to lift West Coast Railways suspension". Rail. Bauer Media (774): 14–15.
18. ^ a b c "ORR prosecutes West Coast Railway Company and train driver over signal incident" (Press release). Office of Rail and Road. Retrieved 9 December 2015.
19. ^ "(open letter)" (PDF). West Coast Railways. Archived from the original (PDF) on 10 April 2015. Retrieved 30 April 2015.
20. ^ a b "Suspension Notice 1 April 2015" (PDF). Network Rail. 1 April 2015. Retrieved 15 April 2015.
21. ^ "Steam train company suspended after running red light in Wiltshire". Independent Television News. 3 April 2015. Retrieved 14 April 2015.
22. ^ "STATEMENT – Network Rail revoke West Coast Railways suspension notice". Network Rail. 8 May 2015. Retrieved 9 May 2015.
23. ^ McMahon, Paul (7 May 2015). "Revocation of Suspension Notice". Network Rail, republished by Steam Railway via its Facebook page. Retrieved 8 May 2015.
24. ^ Browne, Stefanie. "ORR takes next step to revoke WCR safety certificate". Rail. Retrieved 22 April 2015.
25. ^ "Improvement Notice" (PDF). Office of Rail and Road. 21 May 2015.
26. ^ a b c "Determination in respect of ADA 20" (PDF). Access Disputes Committee. 24 October 2014. Archived from the original (PDF) on 16 April 2015. Retrieved 16 April 2015.
27. ^ a b Haigh, Philip (15 April 2015). "Comment". RAIL. Peterborough: Bauer Media (477): 8. ISSN 0953-4563.
28. ^ a b Johnston, Howard (24 April 2015). "We're all on the losing side". Steam Railway. Peterborough: Bauer (440): 3. ISSN 0143-7232.
29. ^ Wilcox, David (24 April 2015). "'Thomas' owner pulls out of Waterloo '70th' party". Steam Railway. Peterborough: Bauer (440): 15. ISSN 0143-7232.
30. ^ Streeter, Tony (24 April 2015). "What's the damage? It's too early to say". Steam Railway. Peterborough: Bauer (440): 72–75. ISSN 0143-7232.
31. ^ a b Westcott, Richard (11 May 2015). "Minute from disaster: What caused near catastrophe on the railway?". BBC News. Retrieved 12 May 2015.
32. ^ "West Coast sidelined due to 'safety weaknesses'". Steam Railway. Peterborough: Bauer (440): 8–10. 24 April 2015. ISSN 0143-7232.
33. ^ Browne, Stefanie (13 May 2015). "West Coast suspension casts uncertainty on charter timetable". Rail. Peterborough: Bauer Media (774): 26–27. ISSN 0953-4563.
34. ^ Newton, Alastair (6 May 2015). "Harry Potter line steam train service hits buffers". The Scotsman. Edinburgh. Retrieved 7 May 2015.
35. ^ "Harry Potter steam train suspension revoked". The Herald. Glasgow. 8 May 2015.
36. ^ Johns, Cedric (7 May 2015). "Abellio may seek new steam operator". Heritage Railway. Horncastle: Mortons Media Ltd (202): 58. ISSN 1466-3562.
37. ^ Johnston, Howard (19 June 2015). "Short trains: a new body blow?". Steam Railway. Peterborough: Bauer (442): 3. ISSN 0143-7232.
38. ^ Streeter, Tony (19 June 2015). "Steam Bosses are called to Safety Summit". Steam Railway. Peterborough: Bauer (442): 6–7. ISSN 0143-7232.
39. ^ "Short sharp shock". Steam Railway. Peterborough: Bauer (442): 74–75. 19 June 2015. ISSN 0143-7232.
40. ^ Smith, David (24 April 2015). "We want the issues resolved quickly". Steam Railway. Peterborough: Bauer (440): 9. ISSN 0143-7232.
41. ^ Pitts, David (19 June 2015). "Press Release - West Coast Railways". Steam Railway. Peterborough: Bauer (442): 75. ISSN 0143-7232.
42. ^ Johns, Cedric (7 May 2015). "Main line crisis: how the story unfolded". Heritage Railway. Horncastle: Mortons Media Ltd (202): 56. ISSN 1466-3562.
43. ^ Jones, Robin (4 June 2015). "West Coast back in business – but 'on probation' by ORR". Heritage Railway. Horncastle: Mortons Media Ltd (203): 6–7. ISSN 1466-3562.
44. ^ a b "Tours". Heritage Railway. Horncastle: Mortons Media (201): 66. 8 April 2015. ISSN 1466-3562.
45. ^ "MAINLINE STEAM TOUR PROGRAMME 2015". UK Steam info. Retrieved 26 January 2018.
46. ^ a b Jones, Robin; Johns, Cedric (7 May 2015). "'Great Britain VIII' sets off as West Coast waits". Heritage Railway. Horncastle: Mortons Media (202): 6. ISSN 1466-3562.
47. ^ "'GBVIII' gamble". Steam Railway. Peterborough: Bauer (441): 70–74. 22 May 2015. ISSN 0143-7232.
48. ^ Johns, Cedric (4 June 2015). "'Great Britain IX' doubtful after tour failure". Heritage Railway. Horncastle: Mortons Media (203): 60–61. ISSN 1466-3562.
49. ^ a b "Decision letter following end of notice period - Revocation of Safety Certificate - Parts A & B" (PDF). Office of Rail and Road. 17 February 2016.
50. ^ "ORR Issues Prohibition Notice On WCR". Railway Herald. 24 November 2015.
51. ^ Stefanie Browne (24 November 2015). "West Coast Railways steam prohibited on main line network". Rail.
52. ^ a b "West Coast Railway Company prohibition lifted". Rail. Peterborough: Bauer Consumer Media. 23 March 2016. Retrieved 6 April 2016.
53. ^ Milner, Chris. "West Coast Railway court date deferred". The Railway Magazine. Horncastle: Mortons Media Group Ltd. Archived from the original on 14 January 2016. Retrieved 11 January 2015.
54. ^ Davy-Osbourne, Stephen. "'750 lives put at risk' when steam train ran red light at Royal Wootton Bassett". Swindon Advertiser. Newsquest. Retrieved 20 January 2015.
55. ^ "Heritage train operator prohibited from running rail services". Office of Rail and Road. 17 February 2016. Retrieved 8 March 2016.
56. ^ Restan, Sue (28 May 2016). "Date set for trial of Harry Potter steam train operator". Press & Journal. Aberdeen Journals Ltd. Retrieved 28 May 2016.
57. ^ Browne, Stephanie. "WCR fined £200k for safety failings". Rail. Bauer Consumer Media Ltd. Retrieved 27 June 2016.
58. ^ "West Coast steam train 'near miss' firm fined £200k". BBC News. 27 June 2016. Retrieved 27 June 2016.

## Further reading[edit]

* Brodrick, Nick; Milner, Chris (May 2015). Pigott, Nick (ed.). "Disastrous Collision Averted by Less Than a Minute: Main Line Steam Devastated by Ban". Headline News. The Railway Magazine. Horncastle: Morton's Media Group. 161 (1370): 8–9. ISSN 0033-8923.
* Rail Accident Investigation Branch (16 October 2015). Dangerous occurrence at Wootton Bassett junction - web site update and supplementary information (PDF) (Report). Gov.uk. Retrieved 19 October 2015.
* Rail Accident Investigation Branch (19 October 2015). "Dangerous occurrence at Wootton Bassett junction, Wiltshire - Update". Gov.uk. Retrieved 19 October 2015.

* v
* t
* e

Railway accidents and incidents in 2015 (2015)

* Feb 3 Valhalla train crash, United States
* Feb 13 Anekal derailment, India
* Feb 16 Mount Carbon derailment, United States
* Feb 20 Rafz train crash, Switzerland
* Feb 24 Oxnard train derailment, United States
* Mar 7 Wootton Bassett incident, United Kingdom
* Mar 9 Halifax train crash, United States
* Mar 10 Dien Sanh train crash, Vietnam
* Mar 20 Bachhrawan train accident, India
* Mar 26 Phachi collision, Thailand
* Apr 28 Johannesburg train crash, South Africa
* May 12 Philadelphia train derailment, United States
* May 16 Ibbenbüren train collision, Germany
* Jun 16 El Fahs train accident, Tunisia
* Jul 2 Gujranwala derailment, Pakistan
* Jul 2 Maryville train derailment, United States
* Jul 22 Studénka train crash, Czech Republic
* Aug 4 Harda train derailment, India
* Aug 21 Thalys train attack, France
* Nov 14 Eckwersheim derailment, France
* Nov 17 Aab-e-Gum derailment, Pakistan

◄ 2014 2016 ►

* v
* t
* e

Railway accidents and incidents in the United Kingdom, 2000–present

2000s|

* Hatfield (Oct 2000)
* Lawrence Hill (Nov 2000)
* Great Heck (Feb 2001) ‡
* Nocton (Feb 2002)
* Potters Bar (May 2002) ‡
* Burmarsh Road (Aug 2003)
* Tebay (Feb 2004)
* Ufton Nervet (Nov 2004) ‡
* 7/7, London (Jul 2005) ‡
* Battery Road (Jul 2005)
* London (Jul 2005)
* Elsenham (Dec 2005)
* Grayrigg (Feb 2007)
* Barrow upon Soar (Feb 2008)
* Channel Tunnel (Sep 2008)

2010s|

* Carrbridge (Jan 2010)
* Falls of Cruachan (Jun 2010)
* Little Cornard (Aug 2010)
* Oxshott (Nov 2010)
* Loch Treig (Jun 2012)
* Norwich (Jul 2013)
* Wootton Bassett (Mar 2015)
* Shalesmoor (Oct 2015)
* Plymouth (Apr 2016)
* Watford Junction (Sep 2016)
* Croydon (Nov 2016) ‡
* Liverpool Lime Street (Feb 2017)
* London Waterloo (Aug 2017)
* Parsons Green (Sep 2017)
* Lewisham (Mar 2018)
* Staniforth Road (Oct 2018)
* Staniforth Road (Nov 2018)

2020s|

* Stonehaven (Aug 2020)
* Llangennech (Aug 2020)
* Kirkby (Mar 2021)
* Salisbury (Oct 2021)

‡ indicates railway accidents and incidents resulting in at least 5 fatalities
1900–1999
*[v]: View this template
*[t]: Discuss this template
*[e]: Edit this template