It has been out recently but I can find out more tomorrow.
4055 is out all day on Airport - South Hylton services. As there is a lack of spare sets it is just about guaranteed to be out tomorrow.
4055 is out all day on Airport - South Hylton services. As there is a lack of spare sets it is just about guaranteed to be out tomorrow.
More units are out of service long term I guess then?
It appears from reading on here 4083 is due to return to service sometime soon, any timeframe on this?
4055 is out all day on Airport - South Hylton services. As there is a lack of spare sets it is just about guaranteed to be out tomorrow.
although normally at least job per day is cancelled off the depot.
I don't have too much knowledge of the Metro but assume there are only two routes - Airport - South Hylton and South Shields - St James. I assume there may be some shorter workings in the peaks.
I'm pushing my luck now I knowbut if anyone is in a position to confirm what route 4055 will be working tomorrow it would be a great help. I don't know whether it is likely to replicate today or swap to South Shields, not sure how it works.
Cheers
I don't have too much knowledge of the Metro but assume there are only two routes - Airport - South Hylton and South Shields - St James. I assume there may be some shorter workings in the peaks.
I'm pushing my luck now I knowbut if anyone is in a position to confirm what route 4055 will be working tomorrow it would be a great help. I don't know whether it is likely to replicate today or swap to South Shields, not sure how it works.
Cheers
Out of curiosity, how many sets are out of service and is there any likelihood of the backlog being cleared shortly?
I was reading a NECA report into the faults per KM for the MetroCar, and the reliability was described as very poor for EMUs; decreasing by more than half comparing the 2nd year of the concession to now.
Sets are allocated in the morning to their services. I'd take a punt that it will be on Airport-South Hylton but that can change at any time during the day should a train fail or other disruption (highly likely to happen too). If it's on South Hylton-Airport it will be on that all day though, it won't become a St James/South Shields train at all, and it's unlikely it will become a Pelaw/Monkseaton/Benton/Regent Centre short service unless there is disruption. Best option that I'd suggest may be if you have Twitter, send Metro a tweet in the morning at around 7am asking if they can find out for you. I believe the social media staff are based in the depot and so will likely be able to access that easier.
IIRC, there's around 6 units out of use on a more long term basis, with quite a lot of units being given quick and basic repairs just to keep some level of service available. The backlog will continue, once some of the longer term issues are fixed and those units are back out, other units will need to go in for heavy work and it will just keep coming back around. This isn't going to go away, and will only get progressively worse. It's not DB/Metro's fault, unfortunately though they've been given the bad end of the stick and are getting the blame. A lot of the blame for me should lie with Nexus. And we're going to be stuck with these trains past their use by date with a half assed refurbishment that looks like corners were cut all over the place.
Who specified the refurbishment spec? Nexus or?? And who would have altered the spec? Would that be Nexus too?
55 is working 121 St James to South Shieldd today, unless things change with disruption
At the end of the day there is a lot of criticism of DB Regio, especially on Facebook, but anyone who thinks that things will improve overnight if Nexus take back the concession is sadly deluded. There will be the same rolling stock, same members of staff to fix cars and the same issues with procuring spare parts. I wouldn't be a bit surprised if Nexus do take it back in house that the timetable will be changed a great deal, with less peak hour trains and possibly trains less frequent on a night time (e.g. every 20-30 minutes after 9pm).
I am trying to find timetables from before DB took over to see what the difference is to the current timetable, and also to see how much higher the total mileage is per day for the fleet. I'm just about sure that there were less peak hour services, and possibly none of these ever went to Monkseaton (Benton was used a lot at the time instead).
With the refurbishment, Nexus specified what work was to be done to the fleet. As part of the concession, it was DB who had to manage the refurbishment, as just about all the engineering staff with knowledge of the rolling stock transferred over to DB. The contract was awarded to Wabtec, so DB then had to project manage the work down in Doncaster. After the first 13 cars came back (these were the ones which had the roof air con for the driver's cabs), the spec was changed by Nexus as the first 13 had gone over budget. As a result there are a lot of differences between the first 13 and the rest of the fleet, but most are not seen by the passenger.
The vast majority of faults are due to the mechanical systems underneath the trains which were not touched during refurbisment. There is an increasing number being withdrawn from service due to cab faults, mainly as the B ends were not refurbished and are not particularly fit for service.
Slightly away from refurbishment but maybe on topic if they have changed the ability to see the monitors easily...tonight was a major farce. The driver of a Shields train refused to either close the doors or leave Haymarket because he couldn't see clearly down the side of the train to be safe to pull away. I assume because of an earlier problem there was a backlog of passengers therefore I can see his problem. When I got there the platform was being policed by several Metro staff and the relevant distance had been cleared, in fact the distance was much larger. The driver still refused to move. It must have been a good 10 minutes before he considered closing the doors and a further 5 before he moved off, oh and at this point the lady with the dispatch flags wasn't there, she arrived on the following train.
I have no idea what his problem was after the relevant distance had been established but he caused a heck of a lot of delay and upset a lot of people.
Apparently photographic evidence of his refusal to move even when the clearance distance had been complied with has been submitted to Nexus.
Strange times on the Metro....
Dave
Why were they using flags? Was there a signalling fault? If the flags were required it suggests that there may have also been a signal failure? One cannot simply pass a signal at danger without a green flag or contacting control; that could be why the event escalated. There is a very good training vide on YouTube of a SPAD a due to passing a signal just on word of mouth and not the flags. However, I was not present and have a limited knowledge of tonight's events and the railway.
This month seems to have been a bit of a disaster for Metro, another 60ish% on the OTP and more trouble on the horizon for our scapegoat DB?
Because platform dispatch as appose to driver dispatch requires a fully qualified signal, i.e. a green flag. Nothing to do with the signaling system itself. Not all metro staff are qualified to do this.....
Today I noticed 'asbestos free' or something along the lines on a piece of the equipment underneath the metrocar; does anyone know what pieces of equipment do/did have asbestos within them? Many thanks in advance!