A Reactor Blast at Shift Change: The Liability Stack a Small Pharma Unit and Its Principal Both Need

Late on Friday night, a reactor exploded at a pharmaceutical unit in Pochampally mandal of Telangana's Yadadri Bhuvanagiri district. Two workers were killed and nine were injured, two of them with burns over more than 50 percent of the body, according to The Tribune of 22 August 2026. India TV reported the same day that the unit belonged to Hazelo Lab Private Limited and that the blast triggered a fire, later extinguished by the fire department. Police registered a case and an investigation is ongoing.

The timing is the detail an underwriter should notice first. The explosion happened during a shift change, the window in which headcount inside a block is at its highest, handover of process state is verbal, and the person who charged the last reagent may already have left the floor. The investigation has not reported a cause, but shift-change concentration is the mechanism that turns a single vessel failure at a small unit into eleven casualties.

The second detail is the size of the operator. India's Active Pharmaceutical Ingredient (API) and intermediate base carries a long tail of private limited companies running one or two synthesis blocks, often on contract for a larger branded pharma company through a loan-licence arrangement or a Contract Development and Manufacturing Organisation (CDMO) agreement. The typical programme at that scale is a Standard Fire and Special Perils policy on the shed and plant, an Employees' Compensation policy because a factory inspector asks for one, and nothing else. The principal that contracted the batch assumes the exposure sits entirely with its manufacturing partner. Both assumptions fail at the same moment.

Deaths and injuries to the unit's own workers are the first and most certain liability. They do not sit under public liability, and they do not sit under a general liability policy, both of which exclude injury to the insured's employees. They sit under the Employee's Compensation Act, 1923, or under the Employees' State Insurance Act, 1948, and which one applies changes the answer entirely.

Where a factory is covered under ESI, employment injury is dealt with by the ESI Corporation, and the employer's separate liability under the 1923 Act is barred for those employees. Where the unit or the specific worker sits outside ESI coverage, the employer carries direct statutory liability, and that is what an Employees' Compensation (EC) policy indemnifies.

The EC computation for a fatal accident is 50 percent of the deceased worker's monthly wages multiplied by an age-based relevant factor set out in Schedule IV, subject to the wage ceiling notified for the purpose, plus the funeral expenses payable under the Act. Permanent total disablement is computed at 60 percent on the same basis. The mechanics matter because they produce two predictable failures on small-unit slips:

• Wage declarations that no longer match the payroll. EC premium is rated on declared wages. A unit that hired ten more operators mid-year and never endorsed the policy is under-declared, and the insurer will apply the shortfall at claim stage.
• Contract labour and trainees left off the schedule. Night-shift manning at small API units frequently includes contractor-supplied helpers. If the principal employer's EC policy does not extend to contractors' employees, and the contractor holds no policy of its own, the liability lands on the principal employer under the Act with no cover behind it.

Burns of the severity reported here expose a further gap. The 1923 Act compensates for death and disablement; it does not oblige the employer to fund the hospital bill. Treating burns over 50 percent of body surface means weeks in a burns unit and repeated grafting. A medical extension on the EC policy, and a group personal accident cover with a medical-expenses section, are the instruments that meet that cost. Neither is standard, and both are cheap relative to what they pay.

Any unit handling hazardous substances above the quantities notified under the rules made pursuant to the Public Liability Insurance Act, 1991 is legally required to hold a Public Liability (Act) Policy. An API or intermediate synthesis block running flammable solvents and reactive chemistry ordinarily crosses that threshold. The Act creates no-fault liability: a third party injured by an accident involving a hazardous substance receives relief on a statutory scale without proving negligence, and the collector administers the claim.

The Act sits alongside an Environment Relief Fund (ERF), to which the owner contributes when the policy is taken, and relief above the insurer's liability is drawn from that fund. Three limits of the Act policy are worth stating plainly, because small units routinely treat it as their liability cover:

1. The relief scale is statutory and modest. It is fixed relief for death, injury and property damage on a defined scale, not the measure of damages a civil court or the National Green Tribunal would award.
2. It responds to third parties, not employees. Workers inside the gate are an EC or ESI matter.
3. It is triggered by an accident involving a notified hazardous substance, so a fire or machinery failure that does not involve one may fall outside it even though the same event injured third parties.

A compulsory Act policy plus a fire policy therefore leaves the operator's real third-party exposure almost entirely uncovered. See our detailed treatment of no-fault claims under the PLI Act and the Environment Relief Fund for how those claims are actually processed at collector level.

An explosion followed by fire does not respect the fence line. Blast overpressure cracks masonry and glazing next door. Firewater and solvent run-off enters an adjoining plot. A neighbouring unit shuts for two days because the fire service closes the access road. Each is a third-party claim, and none is covered by the fire policy on the insured's own assets.

The cover that responds is a Commercial General Liability (CGL) or broad-form public liability policy for third-party bodily injury and property damage arising out of the insured's premises and operations. For a small pharma unit, four wording points decide whether it is worth the premium it costs:

• Sudden and accidental pollution. Standard liability wordings exclude pollution, then buy back sudden and accidental release, usually with a short discovery and notification window. Firewater run-off carrying solvent into a neighbouring plot is the classic test of that buy-back. Gradual seepage stays excluded and needs a separate environmental impairment policy.
• Limit structure. Any-one-accident and any-one-year limits set too close together mean a single event exhausts the annual aggregate, leaving the unit bare for the rest of the period, precisely when regulators and neighbours are most active.
• Defence costs in addition to or within the limit. With police having registered a case, legal spend starts immediately and can consume a small limit before any award.
• Territorial and jurisdiction clauses, which matter once export customers are in the picture.

Brokers should test the product liability position separately. Batches already shipped from the same line can be pulled by the principal or by a regulator once a process-safety investigation opens, and recall is a distinct cover from liability insurance on premises and operations.

This is the layer most often missing, and it belongs to the branded pharma company rather than the unit that exploded.

When a loan-licence or CDMO partner loses a reactor block, the principal loses supply of a product it sells under its own name and its own marketing authorisation. There is no damage to any asset the principal owns, so its own property and business-interruption policy does not respond. The instrument that does is contingent business interruption (CBI), which covers loss of gross profit at the insured's business caused by physical damage at a named supplier's premises.

CBI is bought badly more often than it is bought well. The recurring failures are specific:

1. Unnamed suppliers. Many wordings respond only to suppliers listed by name and address in the schedule. A CDMO partner that took over a product line mid-year and was never added to the schedule is not a covered dependency.
2. Indemnity periods sized to the wrong recovery. For a regulated dosage form, recovery is rebuild plus re-qualification, plus regulatory re-inspection of the site, plus, for export product, re-audit by the destination regulator. Twelve months is routinely too short.
3. Alternative-supplier clauses read as an escape hatch. Wordings often reduce the claim to the extent loss could have been mitigated by sourcing elsewhere. For a regulated product tied to an approved site, alternative sourcing is not a switch that can be flipped, and the file needs to show why.

Our separate guide to contingent business interruption cover works through schedule construction and indemnity-period sizing in more detail.

The principal's second exposure is legal rather than financial. Where its own technical staff specified the process, supplied the batch record, or ran the audit that cleared the block for manufacture, its position as a mere purchaser weakens. Investigators and claimants look at who controlled the operation, not only at whose name is on the factory licence.

Process-safety underwriting at small API units tends to focus on hardware: relief systems, nitrogen blanketing, dyked tank farms, vapour detection. The Pochampally timing points at the organisational half of the same question, which is cheaper to survey.

Handover controls

The questions that separate a well-run block from a poorly run one at 10 pm are simple to ask:

• Is there a written shift-handover record per reactor, capturing charge state, temperature trend, and any deviation open at handover, signed by both operators?
• Are exothermic steps (nitration, hydrogenation, Grignard, diazotisation and similar) prohibited from starting within a defined window either side of shift change?
• Who holds authority to stop a batch on the night shift, and is that person physically present or reachable by phone?
• Is night-shift manning, including contractor-supplied helpers, recorded and reconciled against the wage declaration on the EC policy?

Headcount as an exposure variable

Most casualty estimates for a process unit are built from normal manning. Shift change raises the population in a block for a period every day, and visiting contractors and maintenance crews add to it. An Estimated Maximum Loss built on average headcount understates the casualty tail of a vessel failure, and that tail drives EC, group personal accident and employer-side litigation.

Our companion piece on process-safety underwriting for dust and explosion exposure in pharma covers the hardware side of the same survey.

Set against an event of this shape, the allocation is straightforward once the layers are named.

The manufacturing unit buys:

1. A Standard Fire and Special Perils policy with correct reinstatement value on reactors, utilities and the block, plus a fire loss of profits section with an indemnity period sized to re-qualification, not to rebuild.
2. An Employees' Compensation policy with wages declared accurately, contractors' employees expressly included, and a medical extension, backed by group personal accident with a medical-expenses section.
3. The compulsory Public Liability (Act) Policy where hazardous-substance thresholds are crossed.
4. A Commercial General Liability policy with a sudden-and-accidental pollution buy-back, defence costs treated deliberately, and separate any-one-accident and annual aggregate limits.
5. Product liability and recall cover reflecting the material it ships and the markets it ships to.

The principal or brand owner buys:

1. Contingent business interruption naming each loan-licence and CDMO site in the schedule, refreshed every renewal as the manufacturing footprint changes.
2. Its own product liability and recall programme, because the product carries the principal's marketing authorisation regardless of which factory made it.
3. Contractual risk transfer that is actually verified: a minimum liability limit specified in the manufacturing agreement, the principal named as additional insured where the wording permits it, and a certificate of insurance collected and checked at each renewal rather than filed once at contract signature.

The third item is where most programmes leak. Manufacturing agreements routinely require the partner to hold liability cover, and almost as routinely no one collects the certificate, checks the limit against the agreed minimum, or notices when the policy lapses. That check is the difference between a contractual indemnity backed by an insurer and one backed by a private limited company with a damaged reactor block and a police case open against it.

Every layer described here turns on wording detail rather than on the headline product name. Whether the EC policy's medical extension is present. Whether the CGL pollution buy-back has a discovery window short enough to defeat a firewater run-off claim. Whether the CBI schedule names the CDMO site that took the product line over in March. Those clauses sit deep inside individual insurer wordings and rarely line up section for section across the market.

Sarvada makes insurer wordings searchable so brokers and risk managers can compare them clause by clause. For a small API unit with a branded principal behind it, that means placing the unit's casualty stack and the principal's contingent exposure against wordings that genuinely respond, instead of against a template built for a formulation plant with no contract-manufacturing footprint.

If you place pharma manufacturing or advise a brand owner with loan-licence and CDMO partners, Request Access to Sarvada to compare insurer wordings on these clauses side by side.