• Our new ticketing site is now live! Using either this or the original site (both powered by TrainSplit) helps support the running of the forum with every ticket purchase! Find out more and ask any questions/give us feedback in this thread!

2340 London Euston to Northampton cancelled (16/09)

Status
Not open for further replies.

Ken_Ilworth

Member
Joined
10 Feb 2010
Messages
95
Many pax on concourse tonight at Euston awaiting 2340. At 2331 changed to cancelled 'due to operational incident'. Swiftly removed from board at 2337. Most able to get 0015, assuming it runs. No announcement and no staff around (a few BTP, but obviously there with other priorities). What does ' operational incident' mean?
(0015 currently expected 0022)
 
Sponsor Post - registered members do not see these adverts; click here to register, or click here to log in
R

RailUK Forums

Ken_Ilworth

Member
Joined
10 Feb 2010
Messages
95
Many thanks. 'operational incident' was a new one on me. In my experience they've always stated ' shortage of train crew' in the past.
Thanks for the links..
 

tsr

Established Member
Joined
15 Nov 2011
Messages
7,400
Location
Between the parallel lines
The stock for the service ran empty along its booked route, albeit a few minutes late from Euston (time which it quickly made up).

My guess is that either:
- Realtime Trains has the wrong reason, and it was the guard who was unavailable.
- As above, but that it was the train which had a problem.
- The driver was unfit to drive the train in passenger service for some reason.
- The stock and / or crew were needed back at Northampton a lot earlier than planned, perhaps due to avoid implications with the service the next day.
or
- We just don't know...
 

BestWestern

Established Member
Joined
6 Feb 2011
Messages
6,736
'Operational incident' generally means something has gone wrong somewhere, either human error or technological failure, resulting in the train and/or crew needing to come out of service. Could be a Spad, station overrun, Guard door release or dispatch issue, etc. Alternatively, it could well have been that somebody decided to tell a porkie and not admit that there was a lack of crew for it!
 

CC 72100

Established Member
Joined
23 Jan 2012
Messages
3,852
TG is the attribution code for the delay being attributed to drivers - but that can mean anything related to drivers, including driver operational incident or driver shortage.

tsr is probably the closest - it's far from unknown for traincrew incidents (Driver = TG, Guard = TH) to be mis-coded, although most common for miscoding when it is a staff shortage.
 
Status
Not open for further replies.

Top