OSH/WHS Law Tracker — Week 35, 2026 (24–30 August): A Narrowed Absence Claim as Half the Regulator Portals Went Unreachable; the Cachar Metal-Plant Deaths Enter This Tracker Five Weeks Late and Expose Two Opposite Accountability Architectures Six Days Apart; and the 40-Plus Health Check-Up Closes at D-8

This week (2026-08-24 to 2026-08-30) in India, no new central occupational-safety instrument was traced — but Veritect can only make that claim for two authorities, not for the sector. The DGOSH notifications page was verifiably last updated 21 August 2026, three days before the week opened; the National Green Tribunal record ran from 20 August straight to 3 September. Every other regulator portal was unreachable or returned a navigation template. The week's real content is a disclosure: the Cachar metal-plant deaths have never appeared in this tracker, and read against Sikkim they expose two opposite accountability architectures.

Top Developments This Week

1. Four Deaths in Assam That This Tracker Never Recorded

What is verified. The National Human Rights Commission took suo motu cognisance on 29 July 2026 of the death of four workers and severe injuries to two others in an explosion at a metal-processing factory in Cachar district, Assam. Those figures, that characterisation of the plant, and that date are taken from the NHRC's own press-release record at nhrc.nic.in — not from reporting about it.

What is reported but NOT verified. Reporting places the incident on 26 July 2026 at a unit at Pangram, in the Udharband constituency; describes the mechanism as a molten-metal spill across the factory floor with more than one hundred people inside the unit; and records arrests including the plant's owner, alongside a magisterial inquiry, a police investigation and a separate Labour Department probe. Veritect has not verified any of that against a Tier 1 record. It is set out here as reported, marked as reported, and the verification path is named: the Cachar district administration and the Assam Labour Department.

The disclosure. This event was not covered in any Veritect OSH tracker at the time it occurred, and has not been covered since. That is the second consecutive week in which a mass-fatality event has had to be disclosed late — Week 34 corrected the same failure for the 25 deaths at Samardung, Sikkim. Two misses in two weeks on the two deadliest Indian occupational events of the period is a sourcing failure in the discovery layer, not an isolated slip, and it is recorded here rather than backfilled quietly.

Why it earns a place in Week 35 rather than a footnote. Because its analytical value is only visible now, alongside Sikkim — and that comparison is the most useful thing in this week's tracker.

Links. National Human Rights Commission: https://nhrc.nic.in/media/press-release | Assam Labour Department: https://labour.assam.gov.in/

2. Two Mass-Fatality Events, Six Days Apart, Opposite Accountability Architectures

Read this even if you have no plant in Assam or Sikkim. A workplace fatality in India does not trigger one inquiry. It triggers a five-track statutory architecture, and the tracks run on independent timetables with independent respondents:

Now compare the two events.

Cachar, 26 July 2026 — four deaths. The NHRC took cognisance within three days. Criminal and labour-inspectorate tracks were reported as running in parallel from day one, with arrests reported the following day. On the reported facts, Tracks 1, 3 and 4 all activated, plus a human-rights commission layer that sits outside the five tracks entirely.

Samardung, Sikkim, 20 July 2026 — twenty-five deaths. Six days earlier, and six times the death toll. The only live public proceeding is the National Green Tribunal suo motu application, and its notices run to the Namchi District Collector, the CPCB, the Sikkim Pollution Control Board and the MoEF and CC regional office. No labour department. No factory inspectorate. No DGOSH. No DGMS. That is Track 5 alone.

The inference practitioners should draw. The number of deaths does not determine which tracks activate. The framing of the first proceeding does. Once a mass-fatality event is characterised as environmental, the respondent set, the reliefs and the evidentiary questions all follow that characterisation — and the occupational-safety questions (gas monitoring, ventilation design, permit-to-work, whether two contractors' workforces were inducted to a single ventilation regime) never get asked, because no party before the tribunal is charged with asking them.

The operational consequence for your client. Two things follow. First, an appearance in one forum discharges nothing in the others — a client treating an NGT appearance as its safety-accountability response has misread the map, and a client treating a police FIR as the end of the matter has ignored the §88 notice and the §92 exposure. Second, and less obvious: if the tracks that ought to run are not running, that is a fact about your file too. Where the occupational track is dormant, the limitation clocks, the inspector's power to enter, and the §114 compounding position are all in an unresolved state that can reactivate later. Do not treat regulatory silence as closure.

💡 Staying current on workplace-fatality response compliance? The Veritect Legal AI platform tracks every gazette notification, regulator circular, and amendment across India's compliance landscape in real time — so in-house counsel never miss a trigger. From research to drafting, one AI-native platform. Explore Veritect Legal AI →

OSH Code transition note. The accident-notice duty currently sits in two places at once. §88 of the Factories Act 1948 obliges the manager to notify the state-prescribed authority of any accident causing death or 48-hour-disabling injury, with §88A extending it to dangerous occurrences regardless of injury; §10 of the OSH Code 2020 carries the equivalent duty forward, with §103 (death or serious bodily injury) and §109 (offences by companies) supplying the penal frame. The OSH Code is in force from 21 November 2025 and the OSH (Central) Rules 2026 were notified by G.S.R. 345(E) on 8 May 2026, but Chapters III and XI have not completed state-by-state commencement — so the Factories Act 1948 remains operative in most state-sphere factories today. In the interim, notify under the state Factories Rules form and treat the OSH Code section as the citation that will replace it, not as the citation to use now.

Links. India Code — Factories Act 1948: https://www.indiacode.nic.in/handle/123456789/2385 | National Green Tribunal: https://www.greentribunal.gov.in/

3. What Veritect Could and Could Not Verify This Week — and Why That Is Published

The narrow claim Veritect will make. Two authorities produced usable records for 24–30 August 2026. The DGOSH (formerly DGFASLI) notifications page carried a last-update stamp of 21 August 2026 — three days before the week opened — and held only Regional Labour Institute course-admission notices (PDIS Kanpur, ADIS Kolkata and CLI Mumbai, DIS Chennai) and procurement tenders. A page whose own stamp predates the window cannot have published inside it. The National Green Tribunal record moved from a server-maintenance notice of 20 August 2026 directly to filings of 3 and 5 September 2026.

The claim Veritect will NOT make. For every other authority the listing page could not be read for this batch:

So Veritect makes no absence claim for the Ministry, ESIC, DGMS, PESO, CEA, MoEF and CC, or any state directorate for this week. A portal outage tells you nothing about whether an instrument exists. This is a narrower statement than Week 34's, and the narrowing is deliberate: last week's phrasing rested on a wider portal sweep than this week's evidence supports, and stretching it to match would have been the exact error this tracker exists to avoid.

A date-provenance caution worth more than any of the above. A commercial compliance listing carries a cluster of OSH Code 2020 notifications — S.O. 2503(E) (Appellate Authority for the Chief Labour Commissioner), S.O. 2505(E) (Registering Officer), S.O. 2517(E) (hours of work) and G.S.R. 604(E) (under Rule 111(4) of the OSH (Central) Rules 2026) — against a date of 31 August 2026. Veritect could not corroborate any late-August gazette date from a Tier 1 source; the available indication places S.O. 2517(E) at 13 May 2026, fixing not more than five hours of continuous work with an interval of at least half an hour under §25(1)(b) of the Code. Treat the cluster as May-2026 material until the Gazette copy is read. The transferable rule: a compliance tracker's listing date is not the instrument's gazette date. Diarising from the former is how a three-and-a-half-month-old obligation gets recorded as new — or how a live one gets recorded as future.

Links. DGOSH: https://dgfasli.gov.in/view-notification | e-Gazette of India: https://egazette.gov.in/ | MoLE Labour Codes: https://labour.gov.in/en/labour-codes

Regulatory Action Log

• 40-plus health check-up at D-8. Delivery is due 7 September 2026 under the OSH (Central) Rules 2026 (G.S.R. 345(E), 8 May 2026). Week 35 was the last working week in which a booked provider schedule could still be converted into a dated compliance artefact. A signed, dated provider engagement is worth more evidentially than an undocumented completed check-up.

• ERF affidavit — eighteen days past expiry, still unconfirmed. The four-week window fixed by the Supreme Court's order of 21 July 2026 for the Union and the CPCB to account for the Environment Relief Fund under §7A, Public Liability Insurance Act 1991 expired on or about 18 August 2026. No affidavit, compliance record or subsequent listing was retrievable as at 5 September 2026. Unconfirmed — not "not filed". Owners handling hazardous substances above threshold should keep the §4(2A) PLI adequacy, Rule 11 parity and insurer-remittance file live while the proceeding is undetermined.

• Sikkim high-level committee — five weeks past its own deadline. Home Department notification No. 73/Home/2026 of 22 July 2026 gave a four-member committee fifteen days to report on cause, safety-regulation compliance and gas-detection and ventilation adequacy. That placed submission on or about 6 August 2026. No report, summary or extension order had entered the public record as at 5 September 2026. The NGT Eastern Zonal Bench, Kolkata hears the suo motu matter on 3 September 2026 — four days after this week closed.

• No ESIC deadline fell inside the week. The July-wages deposit landed 17 August 2026 (Week 34); the August-wages deposit falls 15 September 2026, a Tuesday requiring no shift. The draft ESI (General) Regulations 2026 could not be traced to any final gazette, and the ESIC circulars page was unreachable this batch — so no status change is asserted. Continue citing the ESI (General) Regulations 1950: Regulation 31 for contribution timing, Regulation 31A for 12 per cent per annum interest, Regulation 68 for the 48-hour Form 12 accident notice.

• Fireworks — the pre-festival ramp is the live sectoral risk. The 13 August 2026 Sivakasi commissioning-test fatalities (covered in Week 33) sit inside an August cluster of firecracker-unit explosions. A further blast at a firecracker unit in Kaushambi district, Uttar Pradesh occurred on Monday 31 August 2026 — day 1 of Week 36, outside this window. The village within the district is not established by any Tier 1 record traced as at 8 September 2026, and is therefore not asserted here. Reporting divides between Manori (attributed to the District Magistrate, under Pipri police station), Chilla Shahbazi on the Prayagraj–Kaushambi border and Mehmadpur, with a further reference to Manauri Bazar — a landmark on the Prayagraj side rather than a revenue village in Kaushambi. The unit is reported to have been used for manufacture and storage; that too is reported, not verified, and the distinction is not cosmetic, because manufacture engages the PESO / Chief Controller of Explosives licence under the Explosives Act 1884 while possession and sale engage the District Magistrate. It is flagged forward, not counted here, and is assessed on Tier 1 material in the Week 36 tracker. (Corrected 8 September 2026 — this edition originally named the village as "Manauri/Manori"; see Corrections at the end of this edition.)

• Boilers — unchanged and not re-verified. No final gazette for draft IBR 2026 (G.S.R. 31(E)) has been traced. IBR 1950 remains the operative delegated regulation under the Boilers Act 2025 (Act 12 of 2025, in force 1 May 2025 by S.O. 1943(E)), and the Boiler Attendants Rules 2011 two-class competency regime is unchanged. The DPIIT boilers page was not re-verified in this batch.

State Variations

Assam. The week's centre of gravity, and a state that has not previously featured in this tracker. The Cachar position is set out above. For metal-processing, foundry and smelting operations anywhere in the state, the immediate action is to confirm that the §88 / §88A notification route and the 48-hour ESIC Form 12 route are both mapped to named individuals with named backups — the two most common failures after a molten-metal event are a notice sent to the wrong authority and a Form 12 whose cause-field attributes fault. Keep the cause-field factual; §27 of the Bharatiya Sakshya Adhiniyam 2023 makes such statements admissible against the maker in every parallel forum.

Sikkim. For hydro, tunnelling and Himalayan infrastructure exposure, the standing action is unchanged from Week 34: confirm in writing, per works package, whether the works are classified under the Mines Act 1952 (DGMS — a §5.2 carve-out, not repealed) or as building and other construction work (BOCW Act 1996 / OSH Code Chapter XI), and identify the correct accident-notice addressee before an event.

Andhra Pradesh. The OSH (Andhra Pradesh) Rules, 2026 (G.O.Rt.No. 146, 7 August 2026) remain the operative basis for AP sites. The date discrepancy flagged in Week 33 — one compliance tracker records 6 August rather than 7 August — is still unresolved against the AP Gazette copy and should be verified before any advisory relies on the commencement date. This is the same class of error as the S.O. cluster above.

Rajasthan. In force since S.O. 23 of 30 June 2026, with electronic registration, licensing and returns and deemed-approval mechanics where departmental timelines lapse. The portal acknowledgement is the primary evidence — retain it.

Gujarat. Complete across all four Labour Codes. The DISH portal could not be reached this batch, so no change is asserted. The monsoon inspection window is closing; field-visit reports upload to the DISHA portal within two days of visit. Chemical-manufacturing occupiers should treat the PLI / ERF file as live while the Supreme Court proceeding is undetermined.

Maharashtra. Still draft. The draft Maharashtra OSH (Factories and Other Ports) Rules, 2026 and Maharashtra OSH (Labour) Rules, 2026 were published 6 May 2026; no final State Gazette notification has been traced, and the DISH notifications page returned 404 this batch. DISH continues under the Factories Act 1948 + Maharashtra Factories Rules 1963, the MSIHC Rules 1989, the Chemical Accidents (EPPR) Rules 1996 and the Maharashtra Factories (Control of Industrial Major Accident Hazards) Rules, 2003 — the last has no Central analogue and is routinely missed.

Karnataka. Still draft. The Draft Karnataka OSHWC Rules 2026 of 23 January 2026 (notification LD 245 LET 2021) have no confirmable final State Gazette notification. Continue on the Karnataka Factories Act 1 of 2003 + Karnataka Factories Rules 1969. Draft Rule 21(1)(b) would raise the non-hazardous-factory Safety Committee threshold from 200 to 500 workers. Karnataka requires electronic §88 filing within 24 hours via eSuraksha — a shorter window than the central model.

Tamil Nadu. Draft stage; the Factories Act 1948 + Tamil Nadu Factories Rules continue to govern. The Tamil Nadu Factories Rules 1950 carry a notably longer dangerous-occurrence list than the central model, which matters for §88A. With the pre-festival fireworks ramp under way in the Virudhunagar–Sattur belt after the 13 August Sivakasi fatalities, quantity-on-floor discipline, drying-yard segregation and commissioning permits remain the priority audit items — the Sivakasi deaths occurred during the testing of a newly installed chemical-mixing machine, which is a permit-to-work failure mode, not a housekeeping one.

Delhi-NCR. No Delhi-specific OSH gazette notification traced; the Delhi labour portal was not reached this batch. Post-monsoon structural-integrity checks and scaffolding-tie inspection remain the operative site duty across Bawana, Narela and Okhla.

Practitioner Watch-List

1. Map all five tracks for every site, before an event. Named owner and named backup for the §88 / §88A notice, the ESIC Form 12, the criminal-counsel call, the compensation computation and the MSIHC Rule 7 notification. The Cachar–Sikkim contrast shows the tracks do not activate automatically or symmetrically.

2. Never diarise from a compliance-tracker listing date. Recompute from the gazette copy. The S.O. 2503(E) / 2505(E) / 2517(E) cluster is listed at 31 August 2026 and the available indication is 13 May 2026 — a three-and-a-half-month error waiting to be inherited.

3. Close the 40-plus health check-up file before 7 September. Eight days from week close. The dated provider schedule is the artefact.

4. Do not read regulatory silence as closure. Where the occupational track is dormant after an incident, limitation, entry powers and the §114 compounding position remain unresolved and can reactivate.

5. Keep the ESI citation on the 1950 Regulations. No final gazette for the draft 2026 Regulations has been traced. Re-citing to an un-notified draft is invisible until challenged.

FAQ

Q1: Was any new central occupational-safety notification issued in India between 24 and 30 August 2026?

None was traced, but the scope of that statement is deliberately narrow. Veritect can say with confidence that the DGOSH published nothing during the week: its notifications page carried a last-update stamp of 21 August 2026, three days before the week opened, and held only Regional Labour Institute course-admission notices and procurement tenders. The National Green Tribunal record likewise moved from 20 August straight to 3 September 2026. For every other authority the listing page could not be retrieved for this batch — the Ministry of Labour and Employment gazette, What's New and press-release pages returned navigation templates with no items; the ESIC circulars and press-release pages returned HTTP 422 and refused connections; and the DGMS, PESO, CEA, MoEF and CC and state DISH pages returned 404 or were unreachable. Veritect therefore makes no absence claim for the Ministry, ESIC, DGMS, PESO, CEA or any state directorate for this week. A portal outage is a research gap, not a finding.

Q2: What happened at the Cachar metal-processing plant in Assam, and why is it in a Week 35 tracker?

Four workers were killed and two severely injured in an explosion at a metal-processing factory at Pangram in Cachar district, Assam. The National Human Rights Commission took suo motu cognisance on 29 July 2026, recording those casualty figures in its own press release. Reporting places the incident on 26 July 2026, describes a molten-metal spill across the factory floor with more than a hundred people inside the unit, and records arrests including the plant's owner together with magisterial, police and Labour Department inquiries — none of which Veritect has verified against a Tier 1 record. It appears in Week 35 because it has never appeared in any Veritect OSH tracker at all. That is a second consecutive editorial miss on a mass-fatality event, disclosed rather than quietly backfilled, and its analytical value is highest now precisely because it can be read against the Sikkim tunnel deaths six days earlier.

Q3: Why does Veritect say Cachar and Sikkim show opposite accountability architectures?

Because they engaged different tracks of the same five-track statutory architecture that a workplace fatality triggers in India. In Cachar, the NHRC took cognisance within three days, and criminal and labour-inspectorate tracks were reported as running — Track 1 (factory inspectorate notice under Section 88 of the Factories Act 1948 and Section 10 of the OSH Code 2020), Track 3 (criminal, Section 106(1) of the Bharatiya Nyaya Sanhita 2023, up to five years) and Track 4 (compensation). In Sikkim, twenty-five deaths produced one live public proceeding — an NGT suo motu application whose notices run to the Namchi District Collector, the CPCB, the Sikkim Pollution Control Board and the MoEF and CC regional office, with no labour, factories or mines-safety authority on the list. That is Track 5 alone. The practitioner point is that the number of deaths does not determine which tracks activate; the framing of the first proceeding does, and a client that treats one track as discharging the others has misread the map.

Q4: What is the next hard OSH compliance deadline after 30 August 2026?

The 40-plus annual health check-up on 7 September 2026 under the OSH (Central) Rules, 2026 (G.S.R. 345(E), 8 May 2026) — eight days from Week 35 close. Week 35 was the last working week in which a booked provider schedule could still be converted into a dated compliance artefact. Before that, the NGT Eastern Zonal Bench at Kolkata hears the Sikkim Teesta-VI suo motu matter on 3 September 2026. The ESIC and provident-fund deposit on August 2026 wages falls due 15 September 2026, a Tuesday requiring no shift. The Shram Suvidha establishment-record update is due 7 November 2026. CEA Chapter XA battery-energy-storage obligations bind from 1 April 2027.

Q5: Should I diarise the S.O. 2503(E), 2505(E) and 2517(E) notifications as late-August 2026 instruments?

No. A commercial compliance listing carries this cluster of OSH Code 2020 notifications — Appellate Authority for the Chief Labour Commissioner, Registering Officer, and hours of work for establishments — against a date of 31 August 2026, which would place them just outside this week. Veritect could not corroborate any late-August gazette date from a Tier 1 source, and the available indication is that S.O. 2517(E), fixing not more than five hours of continuous work with an interval of at least half an hour under Section 25(1)(b) of the Code, dates to 13 May 2026. Treat the cluster as May-2026 material until the Gazette copy is read. The general rule this illustrates is the one that matters: a compliance tracker's listing or release date is not the instrument's gazette date, and diarising from the former is how a deadline gets missed by three and a half months.

Compliance Deadlines — W35 and Beyond

Research Gaps Declared This Week

Per Veritect's research-honesty standard, the following are recorded as unretrievable, not as findings:

• MoLE gazette / What's New / press-release pages — returned navigation templates with no items rendered. No absence claim made for the Ministry this week.
• ESIC circulars and press releases — HTTP 422 via reader, refused connection direct. No absence claim made for ESIC.
• DGMS, PESO, CEA, MoEF and CC, DISH Gujarat, Maharashtra DISH — 404 or unreachable. No absence claim made for any of them.
• Cachar incident particulars — the 26 July 2026 date, the molten-metal-spill mechanism, the arrests and the reported magisterial / police / Labour Department triple probe are reported, not verified. Only the four deaths, two severe injuries, the plant's characterisation as metal-processing, the Cachar location and the 29 July 2026 NHRC cognisance rest on a Tier 1 record.
• Kaushambi (Uttar Pradesh) firecracker-unit blast of 31 August 2026 — every particular, including the village. The location within the district, the manufacture-and-storage characterisation, the casualty figures and the licence chronology are reported, not verified. Six Tier 1 surfaces were checked on 8 September 2026 — the Kaushambi district site, its press-release category (404), the UP Information and Public Relations Department, PIB, the National Green Tribunal and the UP Pollution Control Board (422) — and none carried an item on the incident. This is not a finding that the incident did not occur, nor that the village is unknown to government; only that no traced Tier 1 record establishes it. Reporting itself divides between Manori, Chilla Shahbazi and Mehmadpur.
• S.O. 2503(E) / 2505(E) / 2517(E) and G.S.R. 604(E) — no Tier 1 gazette date obtained. The 31 August 2026 date comes from a commercial listing and is not treated as the instrument date. Not "not issued".
• ERF affidavit — no filing, compliance record or subsequent listing retrievable as at 5 September 2026. Not "not filed".
• Sikkim high-level committee report — no report, summary or extension order in the public record as at 5 September 2026. Not "no report exists".
• ESI (General) Regulations 2026 and draft IBR 2026 (G.S.R. 31(E)) — no final gazette traced. Not "rejected" or "abandoned".
• Karnataka / Maharashtra / Tamil Nadu final OSH Rules — no confirmable final State Gazette notification. Treat as draft until the state gazette copy is read.

Primary Sources This Week

• National Human Rights Commission — press releases: https://nhrc.nic.in/media/press-release
• Directorate General Occupational Safety and Health (DGOSH, formerly DGFASLI): https://dgfasli.gov.in/view-notification
• National Green Tribunal: https://www.greentribunal.gov.in/
• Supreme Court of India — latest orders: https://www.sci.gov.in/latest-orders/
• Central Pollution Control Board: https://cpcb.nic.in/
• Directorate General of Mines Safety: https://www.dgms.gov.in/
• ESIC — circulars: https://esic.gov.in/circulars
• ESIC — employer page: https://www.esic.gov.in/employer-page
• Ministry of Labour & Employment — Gazette Notifications: https://labour.gov.in/gazette-notification
• Ministry of Labour & Employment — Labour Codes: https://labour.gov.in/en/labour-codes
• Ministry of Environment, Forest & Climate Change: https://moef.gov.in/
• Central Electricity Authority: https://cea.nic.in/
• Petroleum and Explosives Safety Organisation: https://peso.gov.in/
• DPIIT — Boilers / Central Boilers Board: https://www.dpiit.gov.in/boilers
• India Code — Factories Act, 1948: https://www.indiacode.nic.in/handle/123456789/2385
• India Code — Boilers Act, 2025 (Act 12 of 2025): https://www.indiacode.nic.in/handle/123456789/21395?view_type=browse
• Assam Labour Department: https://labour.assam.gov.in/
• Government of Sikkim: https://sikkim.gov.in/
• Andhra Pradesh Labour Department: https://labour.ap.gov.in/
• Rajasthan Labour Department: https://labour.rajasthan.gov.in/
• Karnataka Labour Commissionerate (Karmika Spandana): https://karmikaspandana.karnataka.gov.in/english
• Maharashtra DISH — notifications: https://mahakamgar.maharashtra.gov.in/dish-notifications.htm
• DISH Gujarat: https://dish.gujarat.gov.in/
• DISH Tamil Nadu: https://dish.tn.gov.in/
• e-Gazette of India: https://egazette.gov.in/

Corrections

8 September 2026 — Kaushambi firecracker-unit blast of 31 August 2026: the village, and the manufacture-versus-storage characterisation. This edition carried a forward-reference to the blast and located it at "Manauri/Manori, Kaushambi district". That named a particular which no Tier 1 record establishes. Reporting is not merely split two ways but divergent four ways: Manori (attributed in reporting to the District Magistrate, under Pipri police station), Chilla Shahbazi village on the Prayagraj–Kaushambi border, Mehmadpur, and a further reference to Manauri Bazar — which is a landmark on the Prayagraj side, not a revenue village in Kaushambi, and so may not be a competing candidate at all but a navigational reference that has been read as one. The village is therefore no longer asserted anywhere in this file. The unit's characterisation as a manufacturing and storage unit is corrected on the same evidentiary standard — reported, not verified — and the distinction is reader-actionable rather than descriptive: manufacture engages the PESO / Chief Controller of Explosives licence under the Explosives Act 1884, while possession and sale engage the District Magistrate, so the two characterisations point at different licensing authorities and different failure narratives.

What was checked, on 8 September 2026. The Kaushambi district administration site (reachable; no item on the incident); its press-release category (HTTP 404); the Uttar Pradesh Information and Public Relations Department listing (reachable; carried only 4–6 September 2026 items, none on the incident); PIB's release listing (rendered zero releases) together with a PIB-domain-restricted search returning no release — noting that PIB does publish district-level ex gratia releases for comparable firecracker-unit incidents, Banaskantha 2025 and Virudhunagar 2021 among them; the National Green Tribunal (no 2026 Kaushambi matter traced — the pending OA No. 391 of 2024 concerns the separate February 2024 blast at Maheva village, Kokhraj police station, which killed seven); and the Uttar Pradesh Pollution Control Board (HTTP 422).

Two things this correction deliberately does not say. It does not say the incident did not occur, and it does not say the village is unknown to government. A portal outage and an empty listing are research gaps, not findings. What is stated is only what those listings showed on the date checked.

On method. This correction was verified against the issuing authorities' own surfaces — not against any Veritect corpus file or sibling tracker. That constraint is deliberate and is the lesson of an earlier failure on this platform, in which a correction pass checked a date against our own derivative, and thereby confirmed a fabricated reference code while fixing the date. A derivative cannot falsify its own source. Recorded here rather than silently amended, because a named location attached to a fatal incident is exactly the kind of particular a reader — or an AI engine lifting the sentence — would treat as established.

Beyond this brief Preview — access the full Veritect Legal AI platform

Veritect Legal AI is India's comprehensive AI-native legal workspace — complete compliance frameworks, live legislative-change tracking, operational SOPs, state-by-state nuances, landmark-judgment research, and drafting assistance for every major statutory regime. Start with legal research and finish with a client-ready draft — all in one workflow.

What Veritect Legal AI covers for this topic:

• Full operational SOP depth (10–15 step playbooks vs. this brief preview)
• Every state-specific notification + amendment in real time
• Verbatim rule + Schedule + form text with AI-native retrieval
• Cross-referenced case law with subsequent-treatment trees
• Drafting templates (pleadings / notices / compliance memos)

Access Veritect Legal AI →