New Delhi, Sept. 16 -- The Supreme Court on Monday said that its suo motu examination of the ecological and environmental issues plaguing Himachal Pradesh will extend to all Himalayan states as it held that this year nature's fury was at its worst across the high altitude states. The court was dealing with a suo motu case taken up in July where it sought responses from the Centre and Himachal Pradesh government on the action plan to prevent natural disasters, flash floods and cloudbursts, drawing a direct link to high-paced construction of roads, multi-storeyed buildings, chopping of hills, deforestation, mining activities and hydroelectric projects. A bench of justices Vikram Nath and Sandeep Mehta said, "It is extremely sad there is one more incident (of cloudburst) in the state after this matter was taken up on July 28. We will not limit this matter to Himachal Pradesh alone but the entire Himalayan states. This year the effect is very violent." The court was assisted by senior advocate K Parmeshwar as amicus curiae , who told the court that going by the order taking suo motu cognizance, "the canvas is too broad to look into" as the court has expressed concerns over effect of hydroelectric projects, construction of four-lane roads, deforestation for development projects, multi-storeyed buildings constructed illegally, explosive material used for road construction, retreat of glaciers, waste management, and steps taken under disaster management. The state represented by advocate general Anup Kumar Rattan and additional advocate general Vaibhav Srivastava said that the state has been suffering due to global warming due to its unique geographical location. The response of the said admitted "There are shortcomings in the existing measures" and to emphasise the need for their identification and to formulate a comprehensive future action plan to address the disastrous situations witnessed in recent years, the state proposed constituting a "core group" of experts to submit a roadmap. The state on Monday said that the problem is not unique to HP....