Underground Metro services hit by snag

Mumbai Metro Line 3 services were disrupted for about 40 to 50 minutes on Friday morning after a technical snag delayed trains on both the up and down lines, according to Mumbai Metro Rail Corporation and multiple local reports. The disruption hit the underground Aqua Line during peak commuting hours and left passengers waiting on platforms and inside trains as services slowed or stopped. Commuters told local media they received little information while the delays unfolded. The interruption was the latest service problem on the 33.5-km corridor linking Cuffe Parade in south Mumbai with Aarey JVLR in the northern suburbs. ### Which line was affected, and when did the disruption happen? Metro Line 3, also known as the Aqua Line, was affected on Friday morning, May 22, during office rush hour, local reports said. Mumbai Metro Rail Corporation said train services on both the downline and upline were delayed because of a technical snag before normal operations resumed. (thehindu.com) The 40-50 minute disruption coincided with one of the busiest travel periods of the day, according to The Hindu, Business Standard and other Indian outlets that cited passenger accounts from stations along the route. Reports said crowding built up on station platforms and concourse areas as trains were held. (thehindu.com) ### What did the operator say caused the stoppage? Mumbai Metro Rail Corporation said a “technical snag” delayed services on both routes, but reports said the operator did not immediately spell out the exact nature of the fault. The corporation later said the issue had been rectified and that normal train services had resumed. (thehindu.com) The operator’s public statement, as reported by Indian outlets, focused on restoration rather than the cause or exact timing of the breakdown. That left commuters relying on station announcements, social media posts and media updates for details on when service would normalize. ### What did passengers say they experienced underground? (thehindu.com) Commuters told local media that trains were halted without clear updates and that stations became increasingly crowded as delays stretched on. NDTV reported that some stranded passengers said the experience inside stalled trains was distressing, while other outlets described confusion over whether trains would move or passengers would be asked to disembark. (business-standard.com) The Hindu and other reports said passengers criticized the lack of timely communication from authorities during the disruption. Some commuters posted complaints on social media after being stuck in trains or stations without a clear estimate for when operations would restart. ### Was this an isolated problem on the Aqua Line? (ndtv.com) May 6 was the date of another major disruption on the same corridor, when services were affected by a fire at T2 Airport station, according to Business Standard, The Week and The Economic Times. Several reports described Friday’s incident as the second major disruption on the line this month. (thehindu.com) The Aqua Line is Mumbai’s first fully underground metro corridor and has been watched closely as a key part of the city’s transport network. Friday’s delays drew renewed attention to how quickly faults are communicated to passengers during peak-hour operations, according to commuter accounts cited by local media. (business-standard.com) ### What happens next for commuters? Mumbai Metro Rail Corporation said services were restored after the snag was fixed, and passengers were advised through official updates that normal operations had resumed. Local coverage said trains continued with delays in the aftermath in some parts of the day, even after the immediate stoppage ended. (indianexpress.com) Official service updates from Mumbai Metro Rail Corporation and follow-up local reporting are likely to be the next public source of detail on the fault and any review of operating procedures on Line 3. As of the latest reports available on Saturday, May 23, the operator had confirmed restoration of normal services but had not publicly detailed the exact technical cause. (thehindu.com) (indiatv.in)