The Senate Standing Committee on Railways has raised concerns over encroachments on railway land, the growing burden of pension payments, delays in the revival of the Karachi Circular Railway (KCR), and challenges surrounding the ML-1 project, in a meeting chaired by Senator Jam Saifullah Dharejo. Committee members including Senator Nasir Mehmood, Senator Asad Qasim, and Senator Dost Mohammad Khan were also in attendance.
The committee visited the Divisional Superintendent (DS) office of Pakistan Railways, at the City Station where DS Mehmoodur Rehman Lakho gave a briefing on the operational, financial, and land-related challenges facing the department. Railway officials noted that the organisation is grappling with outdated infrastructure, limited financial resources, and declining revenues, with these issues not only affecting day-to-day services but also hampering progress on expansion projects. Further, they noted that a significant portion of the budget is being consumed by rising pension obligations, impacting development.
The committee was informed that a strategy is being formulated to enhance the security of railway operations nationwide, with particular focus on the Karachi to Hyderabad section. Steps are also being taken to modernise surveillance systems, strengthen coordination with law enforcement, and reinforce the security framework, ensuring the safe movement of passengers and freight. Speaking to the media, Dharejo described the encroachment of railway land and the prolonged delay in the KCR revival as major challenges, but noted that discussions are ongoing with the government to reintegrate the KCR project, along with its inclusion in the China-Pakistan Economic Corridor (CPEC).
The committee chairman also provided updates on recent consultations with Chinese companies regarding the ML-1 project, the country's largest and most expensive rail infrastructure initiative.
COMMENTS
Comments are moderated and generally will be posted if they are on-topic and not abusive.
For more information, please see our Comments FAQ