A day after the Delhi Metro corridor faced a technical snag, commuters travelling on the Blue Line faced problems Thursday morning as a signalling issue led to a delay in the train services on the entire stretch. Connecting Dwarka to Noida and Vaishali, the Blue Line is one of the busiest segments of the Delhi Metro network. Vaishali section branches off from Yamuna Bank, an intersection station.
According to a senior DMRC official, "There is some signalling issue which is intermittently surfacing on Yamuna Bank to Vaishali section of the Blue Line, affecting punctuality of services on the entire Blue Line.”
Delhi Metro's 18 km-long Shiv Vihar-Trilokpuri section of Pink Line gets safety approval, to open around Diwali
Escorts Mujesar-Ballabgarh section ready for passenger operations; to be flagged off by PM Modi today
'Western Peripheral Expressway should have been completed 9 years ago': PM Modi inaugurates key projects in Haryana
A temporary arrangement for train services has been made till the problem is solved, he said.
"Train services between Dwarka and Noida are running seamless in one go with a frequency of around 4 minutes and 30 seconds on an automatic mode through central control, i.e., Operations Control Centre," the official said.
The regular frequency of trains on Dwarka-Noida line is 2 minutes and 30 seconds, he added.
"...services between Yamuna Bank and Vaishali stations are being run in an independent loop with a frequency of around 5 minutes and 30 seconds through local control (at station level)," he said.
The signalling team is working on the system and as soon as it is rectified, train services on the entire Blue Line will be started as per normal schedule, the official said.
Several commuters took to twitter and complained of delays. Many said that their trains were stuck for as long as 30 minutes.
Train services were affected twice on the line on Wednesday due to signalling issues in different sections of the corridor.
The first technical snag had occurred around 3 pm. The issue was resolved at 4:23 pm and train services were started as per schedule. However, the snag recurred around 7 pm at another section.