How To SurviveLife-Safety Intelligence for India
Language
Automatic translation
Case Study · Building & Structural

Kudasan construction collapse: rescue updates and why scene clearance still matters

A review of the Gandhinagar rescue with dated official statements and an explicit distinction between reported rescue totals and a cleared site.

Date2026-09-09LocationKudasan, Gandhinagar, Gujarat, IndiaLast checked15 Sep 2026
ShareWhatsApp
01
Case Study

What happened here

ResponseGandhinagar and Ahmedabad teams reported
EvidenceOfficial statements relayed by established newsrooms
Site statusContinued debris search described

A review of the Gandhinagar rescue with dated official statements and an explicit distinction between reported rescue totals and a cleared site.

Quick answers

What happened in the Kudasan construction collapse in Gandhinagar?

On the night of 9 September 2026, part of a construction project collapsed in Kudasan, Gandhinagar, Gujarat. Gujarat's Deputy Chief Minister was reported as saying 15 people had been rescued and 12 were injured, none considered critical at that time.

What caused the Kudasan construction site collapse?

No technical cause has been assigned. A possible crane impact was mentioned in reporting as an allegation, not an engineering conclusion, and early coverage described the collapsed element differently.

Does a rescue headcount mean a collapse site is safe?

No. Even though the site manager believed nobody remained trapped, responders said they would continue until debris was cleared. A headcount and the decision that a scene is safe answer different questions.

What to do if someone may be missing after a building collapse?

Report the concern to the rescue team with the last reliable information about where the person was. Do not send an untrained person into a damaged structure, stay outside restricted areas and call 112 from safety.

The rescue update

A portion of a construction project collapsed in Kudasan, Gandhinagar, on the night of 9 September 2026. In ANI’s 01:30 IST report on 10 September, Gujarat Deputy Chief Minister Harsh Sanghavi said 15 people had been rescued, three discharged and 12 injured. He said doctors did not consider the injured critical at that time. These are attributed statements, not a later medical assessment. ANI via Asianet News, 10 September, 01:30 IST.

Table of the Kudasan construction collapse of 9 September 2026: ANI at 01:30 IST reported 15 rescued, three discharged and 12 injured; The Indian Express at 00:39 IST reported 13 rescued and at least five hospital transfers.
The ANI and Indian Express rescue figures for the Kudasan construction collapse of 9 September 2026, drawn by HowToSurvive.in from the facts on this page. It is not a photograph of the incident.

Why earlier figures differ

The Indian Express’s 00:39 IST update preserved an earlier statement that 13 people had been rescued and reported at least five hospital transfers. Reports were published during an evolving response; the numbers should not be added together. The Indian Express, updated 10 September, 00:39 IST.

Early coverage also used different descriptions of the collapsed element. A possible crane impact was an allegation in reporting, not an engineering conclusion. This case therefore describes a construction collapse without assigning a technical cause.

Rescue count does not mean the scene is cleared

ANI’s report quoted Sanghavi saying that, although the site manager believed nobody remained trapped, responders would continue until debris was cleared. This is a useful distinction: a headcount statement and an operational decision to finish searching answer different questions.

Editorially, an incident review should retain the source, time and scope of each update. “Rescued”, “taken to hospital” and “remaining at the site” are different categories. An early estimate of people feared trapped is not a confirmed death toll.

Infographic from the Kudasan collapse case study: rescued, taken to hospital and remaining at the site are separate categories, a headcount is not a cleared site, and four workplace preparedness points.
Three categories of rescue reporting and four workplace preparedness points, from the Kudasan collapse case study, drawn by HowToSurvive.in from the facts on this page. It is not a photograph of the incident.

Learning without guessing blame

For workplace preparedness, identify how staff or visitors report their location after an alarm and who passes information to responders. Do not send an untrained person back into a damaged structure to check a name. A missing-person concern belongs with the rescue team, together with the last reliable information available.

The cover is a conceptual AI scene, not the actual site. Related learning videos are labelled separately from news coverage. Early newsroom video pages are recorded among the sources, but their footage has not been verified for the site’s embedded player.

More on Ahmedabad: see our Ahmedabad fire and emergency safety guide for fire brigade numbers, every fire station and the local risks to know.

  1. Construction collapse reported
  2. Indian Express update
  3. ANI report carrying Deputy CM statement

Why consequences escalated

  • Editorial lesson: do not combine rescue counts from different reporting snapshots.
  • A reported headcount is not an authorisation to approach a damaged site.

Failures and risk multipliers

  • No confirmed engineering failure mechanism or finding of individual fault reviewed.

Actions that reduce risk

  1. Follow the cordon and responder directions.
  2. Report missing-person concerns with last-known information.
  3. Keep source and time attached to updates.
Share

Share the lesson, not the grief.

Send it to neighbours, shop owners or your housing society group so it is not repeated.

Only the title and the link are sent. Nothing is tracked.
02
Watch & learn

Video reports & learning

Incident news / follow-up

Gandhinagar Slab Collapse: Slab Collapses in Kudasan, 10-15 Feared Trapped — TV9Gujarati

TV9 Gujarati · English

Newsroom coverage of this case. Early numbers and allegations reflect the original report, not a final finding.

What to do

  1. Stay outside the cordon and away from the damaged or unstable structure.
  2. Call 112 from a safe place and give the exact location of the collapse.
  3. Tell the rescue team who may be missing and where each person was last seen.
  4. Follow the directions of the responders and keep access routes clear.
  5. Share only confirmed information with the rescue team, not guesses.

Emergency numbers: In India: fire 101, ambulance 108, police 100, or 112 from any phone.

Do not go back into a damaged structure or send an untrained person in to look for someone; report the missing person to the rescue team.

03
Incident data

The broader evidence

Survival sequence

  1. Stay outside restricted areas and away from unstable structures. Call 112 from safety for immediate emergency help.
15People reported rescuedDeputy CM via ANI, 10 Sep 01:30 IST
12Injured in that statementA dated account, not final clinical outcomes

Limitations

  • No final engineering report, final medical outcomes or subsequent scene-clearance confirmation reviewed. Counts are not a trend chart. No precise map location inferred.
Location mapGandhinagar area context — approximate area only; exact incident site not marked

23 other case studies within 150 km

  • This case
  • Fire
  • Road
  • Building
  • Other
Open the full incident map
Nearby cases (6)
Map data © OpenStreetMap contributors

Immediate actions

  • Check how your workplace would account for staff and visitors after an alarm.
Community discussion

Questions, experience and constructive safety discussion

Comments publish immediately unless security controls identify spam. Please do not post private information, unsupported allegations or unsafe instructions.

Leave a comment

* Name and email are required. Your email address will not be published.


The reCAPTCHA verification period has expired. Please reload the page.