Hereford train terminated at Reading due to train crew being unavailable

[whole diary]

[Chris from Nailsea]

From FGW^▸ (First Great Western) JourneyCheck:

19:22 London Paddington to Hereford due 22:54
This train has been delayed at Reading and is now 19 minutes late.
This train will be terminated at Reading at 20:10.
This train will no longer call at Oxford, Hanborough, Charlbury, Kingham, Moreton-In-Marsh, Honeybourne, Evesham, Pershore, Worcester Shrub Hill, Worcester Foregate Street, Malvern Link, Great Malvern, Colwall, Ledbury and Hereford.
This is due to a member of train crew being unavailable.

Customers should now travel on the next service which calls as follows:
            Arrival Departure
READNG 20:50 20:52
OXFORD 21:19 21:21
HANBOROUGH 21:30 21:31
CHARLBURY 21:38 21:39
KINGHAM 21:47 21:49
MORTON-IN-MARSH 21:56 21:57
HONEYBOURNE 22:07 22:09
EVESHAM 22:15 22:17
PERSHORE 22:23 22:25
WORCESTER SHRUB HILL 22:39 22:41
WORCESTER FORGATE STREET 22:43 22:45

Customers for Colwall, Ledbury and Hereford will be provided with replacement road transport from Worcester Shrub Hill.

Message Received:10/04/2012 20:42

[IndustryInsider]

Hmmm, bit of a strange one that.  Both driver and TM^‡(resolve) are Bristol crew who work the train throughout, so it seems odd that they ran it to Reading if there was some reason it could not continue beyond?

[Chris from Nailsea]

Yes, I wondered that, too: that's why I thought it was worth posting. However, you're the Insider! 

[Btline]

You should have titled the thread "Tired commuters DUMPED at Reading". What a missed opportunity.

[Chris from Nailsea]

Hmm. I prefer to give my posts the greater gravitas of factual accuracy, rather than overblown hyperbole, Btline. 

[JayMac]

Hmmm, bit of a strange one that.  Both driver and TM^‡(resolve) are Bristol crew who work the train throughout, so it seems odd that they ran it to Reading if there was some reason it could not continue beyond?

Crew out of hours?

[bobm]

 Or taken ill?