|33803 departs Norwich on Tuesday 20th working the 10.30 Lowestoft - Peterborough. Photo : Kieran Smith|
Tuesday 20th saw a very rare breakdown in traffic. 33810 which had arrived in Peterborough on K5-XL11 at 18.44 failed with the oil cooler problem and the King's Lynn rescue van was sent to its aid. It wasn't out of traffic for long though as it resumed work with K19-XL06 on Friday 23rd. On election day, Thursday 22nd Malcolm saw 33806 arrive in Lowestoft 'not in service' before departing on K18-XL04 11.00 to Peterborough. While on the afternoon of Friday 23rd, K14 -XL01 was delayed and Bruce saw it go by eastbound 14 late (due past him at Walpole at 14.46 but passing by on the stroke of 3pm), 33805 was the culprit.
Peter says "I turned up for
the 17.20 departure from Peterborough railway station, but caught the 16.50 with 33813 running 15 minutes late. Very friendly driver called Alan who actually thanked people for travelling with the X1. Top marks from me. We came out of Peterborough via the Passport Office route (pictured left) which is unusual".
A funeral and election duty saw Bruce take command of sightings for a few days, all passing reasonably uneventfully. Tuesday 27th May (after the Bank Holiday) saw minor delays and Y7-XL13 was 14 late into Lowestoft during the afternoon with 33816. Neither Wednesday or Friday last were good on the punctuality front as half term traffic took its toll. 28th saw 33810 arriving in Wisbech 15 late for the 11.55 to Lowestoft (Y9-XL15) and K18-XL05 14.58 Wisbech - Peterborough passed me 15 late with 33807. Peter reports that on Thursday 29th, some X1 services were disrupted by queueing traffic on Bourges Boulevard in Peterborough. The 08.48 from Wisbech was one of the services affected, see Peter's picture :
On the vehicle front there have been few incidents, but 33823 has been off the road since the evening of 24th with a transmission fault and wiring problems. AD staff have been in attendance on more than one occasion as this vehicle seems to have more than its fair share of faults. It managed 4 miles on test runs during the last week, but is still currently unfit. 33811 continues to lead the way on the mileage front with 77,700 miles recorded as of the evening of Saturday May 31st.