Dangerous 'mishap' near Hadnall
175 113, forming the 22:36 Manchester Piccadilly - Shrewsbury of 16 January, had left Manchester a few minutes late and was still a few minutes 'down' when it departed from Wem at 23:49, with (it is reported) just one passenger still on board. However, before reaching its final destination it ran into a track workers' trolley, whose operatives had run clear when they saw the train approaching.
A Police spokesman wrote: 'British Transport Police were called on Friday following a report that a rail trolley had been struck by a train near Station Road in Hadnall, Shrewsbury. BTP officers attended the incident, which was reported at 12.25am, alongside colleagues from West Mercia Police and West Midlands Ambulance service. The train ... is understood to have struck the rail trolley which contained engineering equipment that was being used by rail staff working on the tracks in the location. One passenger was on board at the time and there are no reports of any injuries to them or the driver of the service, who was treated for shock. Three men, who were working on the tracks at the time, managed to move out of the way and were uninjured but have been left extremely shaken. The train remained upright but has been badly damaged by the trolley, which was lodged underneath it. Officers will now be working to establish the circumstances surrounding the collision.'
The person in charge of entering 'delay attributions' to the railway's information systems chose to use code 'IY' which is officially described as 'Mishap - Network Rail causes' which seems to be something of an understatement of a potentially fatal event. How the 'mishap' was allowed to occur we cannot say: clearly there was a big misunderstanding at some point; the Rail Accident Investigation Board has been informed, but has not made any public statement at the time of writing. Last year the intermediate signalboxes on the Crewe - Shrewsbury line were closed and control of the signalling transferred to Cardiff signalling centre. It will be interesting to see whether this change turns out to have had any bearing on the incident.