Discuss how festival-related emission spikes test the limits of India's air quality management framework, both regulatory and technological.
New · District CollectorCan you hold the district for 72 hours?Floods, a heatwave, an outbreak, a grievance queue. Take the decisions, see the consequences.Play →In this answer
During Deepavali 2026, nearly 70% of the Central Pollution Control Board's (CPCB) 634 Continuous Ambient Air Quality Monitoring Stations (CAAQMS) recorded 'severe' PM2.5 peaks (≥250 µg/m³). At least seven States besides Delhi were affected [1]. Short, intense spikes like these show the limits of both the rules and the instruments behind India's clean-air governance.
Technological limits: monitoring that misses the peak
- Calibration ceiling: the analysers are calibrated only up to 1,000 µg/m³. Automated validation throws away higher values, which then "may appear as a data gap" [1].
- Unexplained blackouts: many stations went silent just before they reached 1,000 µg/m³, which the calibration rule cannot explain [1].
- Network uptime: only 571 of 634 stations were live during the festival [1].
- Understated averages: 24-hour averages are worked out from the cleaner hours that were recorded, so they understate exposure. CSE calls monitoring the "Achilles' heel" of India's fight against air pollution [2].
Regulatory limits: rules built for annual averages
- Wrong pollutant, wrong time-scale: the National Clean Air Programme (NCAP) targets a cut of up to 40% in PM10 by 2025-26, and funds are tied to PM10 performance [3]. A city can meet this target and still choke on festival PM2.5.
- Misdirected spending: 64% of NCAP and 15th Finance Commission funds went to road-dust control. Combustion-based PM2.5, such as firecracker smoke, has been neglected [4].
- Weak capacity: as of May 2024, Delhi and Noida had used less than 40% of their NCAP funds [4].
- Enforcement depends on data: emergency measures such as GRAP in NCR are triggered by AQI readings. Data gaps at peak hours delay action and health alerts for children and the elderly.
Way forward
- Mark readings as "above range" instead of deleting them, and publish station downtime logs [1].
- Add PM2.5 and peak-day metrics to NCAP's funding formula [3][4].
- Use unspent funds for station upkeep and to build State Pollution Control Board capacity.
Festival spikes are therefore a stress test. They reveal a framework tuned to annual PM10 averages that cannot see peak moments. Better instruments, transparent data and an NCAP that counts PM2.5, backed by greener celebrations, would make the Article 21 right to a clean environment and SDG 11.6 real even on the worst night of the year.
Sources
- 1"Across India, 70% of stations reported 'severe' PM2.5 readings", The Hindu, 12 Nov 202670% severe peaks; 634/571 stations; 1,000 µg/m³ calibration limit and data gaps; seven-plus States
- 2CSE, *State of India's Environment* reportmonitoring as the "Achilles' heel" of India's air-pollution fight
- 3PIB, Ministry of Environment, Forest and Climate Change: National Clean Air ProgrammePM10 reduction target of up to 40% by 2025-26; funding tied to PM10 performance
- 4CSE assessment: "NCAP must not get reduced to being just a dust control programme"64% of funds on road dust; neglect of combustion PM2.5; Delhi and Noida using less than 40% of funds