2012 India blackouts

From Infogalactic: the planetary knowledge core
Jump to: navigation, search
July 2012 blackouts
File:Indian states affected by July 2012 power cuts.svg
Indian states
  Affected 2 days by the power outages (on 30 and 31 July)
  Affected 1 day by the power outages (on 31 July)
Date 02:48, 30 July 2012 (+05:30) (2012-07-30T02:48+05:30)-
20:30, 31 July 2012 (+05:30) (2012-07-31T20:30+05:30)
Location Northern India

Two severe power blackouts affected most of northern and eastern India on 30 and 31 July 2012. The 30 July 2012 blackout affected over 300 million people and was briefly the largest power outage in history, counting number of people affected, beating the January 2001 blackout in Northern India. (230 million affected)[1] The blackout on 31 July is the largest power outage in history. The outage affected over 620 million people, about 9% of the world population,[2][3][4] or half of India's population, spread across 22 states[5] in Northern, Eastern, and Northeast India. An estimated 32 gigawatts of generating capacity was taken offline.[6] An article in The Wall Street Journal stated that of the affected population, 320 million initially had power, while the rest of the affected population lacked direct access.[7] Electric service was restored in the affected locations between 31 July and 1 August 2012.[8][9]

Background

India is the world's third largest electricity producer and consumer of electricity after the United States and China; however, the electrical infrastructure is generally considered unreliable.[10][11] The northern electrical grid had previously collapsed in 2001.[6] An estimated 27% of energy generated is lost in transmission or stolen,[12] while peak supply falls short of demand by an average of 9%.[12] The nation suffers from frequent power outages that last as long as 10 hours.[12] Further, about 25% of the population, about 300 million people, have no electricity at all.[12] Efforts are underway to reduce transmission and distribution losses and increase production further.[13]

In the summer of 2012, leading up to the failure, extreme heat had caused power use to reach record levels in New Delhi. Due to the late arrival of monsoons, agricultural areas in Punjab and Haryana drew increased power from the grid for running pumps irrigating paddy fields.[14] The late monsoon also meant that hydropower plants were generating less than their usual production.[15]

Sequence of events

30 July

At 02:35 IST (21:05 UTC on 29 July), circuit breakers on the 400 kV Bina-Gwalior line tripped. As this line fed into the Agra-Bareilly transmission section, breakers at the station also tripped, and power failures cascaded through the grid. All major power stations were shut down in the affected states, causing an estimated shortage of 32 GW.[6] Officials described the failure as "the worst in a decade".[16]

On the day of the collapse, Power Minister Sushilkumar Shinde stated that the exact cause of the failure was unknown, but that at the time of the failure, electricity use was "above normal". He speculated that some states had attempted to draw more power than permitted due to the higher consumption. Spokesperson for PowerGrid Corporation of India Limited (PGCIL) and the Northern Regional Load Dispatch Centre (NRLDC) stated that Uttar Pradesh, Punjab and Haryana were the states responsible for the overdraw. PGCIL's chairman also stated that electrical service was restored "at a record time".[6]

A senior director for an Indian power company described the outage as "a fairly large breakdown that exposed major technical faults in India's grid system. Something went terribly wrong which caused the backup safety systems to fail."[17]

More than 300 million people, about 25% of India's population, were without power. Railways and some airports were shut down until 08:00.[18] The busiest airport in South Asia, Delhi Airport, continued functioning because it switched to back-up power in 15 seconds.[17][19] The outage caused "chaos" for Monday morning rush hour, as passenger trains were shut down and traffic signals were non-operational.[6] Trains stalled for three to five hours.[18] Several hospitals reported interruptions in health services,[6] while others relied on back-up generators.[16] Water treatment plants were shut down for several hours,[18] and millions were unable to draw water from wells powered by electric pumps.[14]

The Associated Chambers of Commerce and Industry of India (ASSOCHAM) stated that the blackout had "severely impacted" businesses, leaving many unable to operate.[20] Oil refineries in Panipat, Mathura and Bathinda continued operating because they have their own captive power stations within the refineries and do not depend on the grid.[6]

It took 15 hours to restore 80% of service.[17]

31 July

The system failed again at 13:02 IST (07:32 UTC), due to a relay problem near the Taj Mahal.[21] As a result, power stations across the affected parts of India again went offline. NTPC Ltd. stopped 38% of its generation capacity.[22] Over 600 million people (nearly half of India's population), in 22 out of 28 states in India, were without power.[5]

More than 300 intercity passenger trains and commuter lines were shut down as a result of the power outage.[23][24] The worst affected zones in the wake of the power grid's collapse were Northern, North Central, East Central, and East Coast railway zones, with parts of Eastern, South Eastern and West Central railway zones. The Delhi Metro suspended service on all six lines, and had to evacuate passengers from trains that stopped mid-journey, helped by the Delhi Disaster Management Authority.[22]

About 200 miners were trapped underground in eastern India due to lifts failing, but officials later said they had all been rescued.[25]

The National Disaster Management Authority (NDMA), not normally mandated to investigate blackouts, began to do so because of the threat to basic infrastructure facilities like railways, metro rail system, lifts in multi-storey buildings, and movement of vehicular traffic.[26][27]

The following states were affected by the grid failure:[28]

The following regions were not directly affected by the power outage:[29]

  • Narora, Renukoot and Simbhaoli in Uttar Pradesh
  • parts of Delhi such as Badarpur
  • areas served by Sterlite and Ib Thermal Power Station (most of western Odisha)
  • most of the Kolkata municipal area (CESC system)

As of 2 August, Uttar Pradesh was being supplied about 7 GW power, while the demand was between 9 and 9.7 GW.[30]

Prior disaster-proofing

Before the grid collapse, the private sector spent $29 billion to build their own independent power stations in order to provide reliable power to their factories. The five biggest consumers of electricity in India have private off-grid supplies. Indian companies have 35 GW of private off-grid generation capacity and plan to add another 33 GW to their off-grid capacity.[19]

Some villages that were not connected to the grid were not affected, such as Meerwada, Madhya Pradesh which had a 14 kW solar power station built by a United States-based firm for $125,000.[31]

Reactions

On the day of the collapse, Power Minister Sushilkumar Shinde ordered a three-member panel to determine the reason for the failure and report on it in fifteen days.[32] In response to criticism, he observed that India was not alone in suffering major power outages, as blackouts had also occurred in the United States and Brazil within the previous few years.[15]

The Washington Post described the failure as adding urgency to Indian Prime Minister Dr. Manmohan Singh's plan for a US$400 billion overhaul of India's power grid. His plan calls for a further 76 gigawatts of generation by 2017,[17] produced in part by nuclear power.

Rajiv Kumar, secretary general of the Federation of Indian Chambers of Commerce and Industry (FICCI) said, "One of the major reasons for the collapse of the power grid is the major gap between demand and supply. There is an urgent need to reform the power sector and bring about infrastructural improvements to meet the new challenges of the growing economy."[33]

On 1 August 2012, newly appointed Power Minister Veerappa Moily stated, "First thing is to stabilize the grid and it has to sustain. For that we will work out a proper strategy." He declined to blame specific states, saying, "I don't want to start with the blame game."[34]

Team Anna, the supporters of anti-corruption activist Anna Hazare, charged that this grid failure was a conspiracy to suppress the indefinite fast movement started on 25 July 2012 for the Jan Lokpal Bill and targeting Sharad Pawar.[35][36]

Some technology sources and United States Agency for International Development (USAID) proposed that another widespread outage could be prevented by integrated network of microgrids and distributed generation connected seamlessly with the main grid via a superior smart grid technology, which includes automated fault detection, islanding and self-healing of the network.[37][38][39][40]

Investigation

The three-member investigation committee consisted of S. C. Srivastava, A. Velayutham and A. S. Bakshi, and issued its report on 16 August 2012. It concluded that four factors were responsible for the two days of blackout:[41]

  • Weak inter-regional power transmission corridors due to multiple existing outages (both scheduled and forced);
  • High loading on 400 kV Bina–Gwalior–Agra link;
  • Inadequate response by State Load Dispatch Centers (SLDCs) to the instructions of Regional Load Dispatch Centres (RLDCs) to reduce over-drawal by the Northern Region utilities and under-drawal/excess generation by the Western Region utilities;
  • Loss of 400 kV Bina–Gwalior link due to mis-operation of its protection system.

The committee also offered a number of recommendations to prevent further failures, including an audit of the protection systems.

See also

References

  1. Lua error in package.lua at line 80: module 'strict' not found.
  2. Lua error in package.lua at line 80: module 'strict' not found.
  3. Lua error in package.lua at line 80: module 'strict' not found.
  4. Lua error in package.lua at line 80: module 'strict' not found.
  5. 5.0 5.1 Lua error in package.lua at line 80: module 'strict' not found.
  6. 6.0 6.1 6.2 6.3 6.4 6.5 6.6 Lua error in package.lua at line 80: module 'strict' not found.
  7. Lua error in package.lua at line 80: module 'strict' not found.
  8. Lua error in package.lua at line 80: module 'strict' not found.
  9. Lua error in package.lua at line 80: module 'strict' not found.
  10. Lua error in package.lua at line 80: module 'strict' not found.
  11. Lua error in package.lua at line 80: module 'strict' not found.
  12. 12.0 12.1 12.2 12.3 Lua error in package.lua at line 80: module 'strict' not found.
  13. Lua error in package.lua at line 80: module 'strict' not found.
  14. 14.0 14.1 Lua error in package.lua at line 80: module 'strict' not found.
  15. 15.0 15.1 Lua error in package.lua at line 80: module 'strict' not found.
  16. 16.0 16.1 Lua error in package.lua at line 80: module 'strict' not found.
  17. 17.0 17.1 17.2 17.3 Lua error in package.lua at line 80: module 'strict' not found.
  18. 18.0 18.1 18.2 Lua error in package.lua at line 80: module 'strict' not found.
  19. 19.0 19.1 Lua error in package.lua at line 80: module 'strict' not found.
  20. Lua error in package.lua at line 80: module 'strict' not found.
  21. Lua error in package.lua at line 80: module 'strict' not found.
  22. 22.0 22.1 Lua error in package.lua at line 80: module 'strict' not found.
  23. Lua error in package.lua at line 80: module 'strict' not found.
  24. Lua error in package.lua at line 80: module 'strict' not found.
  25. Lua error in package.lua at line 80: module 'strict' not found.
  26. Lua error in package.lua at line 80: module 'strict' not found.
  27. Lua error in package.lua at line 80: module 'strict' not found.
  28. Lua error in package.lua at line 80: module 'strict' not found.
  29. Lua error in package.lua at line 80: module 'strict' not found.
  30. Lua error in package.lua at line 80: module 'strict' not found.
  31. Lua error in package.lua at line 80: module 'strict' not found.
  32. Lua error in package.lua at line 80: module 'strict' not found.
  33. Lua error in package.lua at line 80: module 'strict' not found.
  34. Lua error in package.lua at line 80: module 'strict' not found.
  35. Lua error in package.lua at line 80: module 'strict' not found.
  36. Lua error in package.lua at line 80: module 'strict' not found.
  37. Lua error in package.lua at line 80: module 'strict' not found.
  38. Lua error in package.lua at line 80: module 'strict' not found.
  39. Lua error in package.lua at line 80: module 'strict' not found.
  40. Lua error in package.lua at line 80: module 'strict' not found.
  41. Lua error in package.lua at line 80: module 'strict' not found.

External links