Why MCD’s Legal Framework Never Requires Inspection of Falling Buildings

On 6 September 2026, a five-story building running as a boys’ PG called “Hostel Daze” collapsed in Satya Niketan, near Delhi University’s South Campus. At least seven people died. A senior MCD official later told reporters that the building had no sanctioned plan at all andreinspection that the changes made to its basement were unauthorized. Mayor Pravesh Wahi added something equally telling. He remarked that the building had never been classified as dangerous, even though basement work was going on right up to the day it fell.

Putting those two facts side by side, there is one question that stands out. Delhi’s building law gives the Municipal Corporation of Delhi wide powers to sanction, stop, seal and demolish construction. Why did none of that machinery touch this building before it killed the people inside it? That is the question this piece tries to answer.

What the law actually requires

Chapter XVI of the Delhi Municipal Corporation Act, 1957 sets out the chain that is supposed to run from paper to plot. Section 336 requires the Commissioner to sanction or refuse a building plan. Once sanctioned, construction that deviates from that plan can be stopped under Section 344, altered under Section 345, or sealed under Section 345A. If a structure is “in a ruinous condition, or likely to fall, or in any way dangerous,” the Commissioner can order for it to be demolished, secured or repaired under Section 348, and can order it vacated under Section 349.

On a plain reading, these appear to be very strong powers. But every one of them starts with a trigger, and the trigger is the word “appears.” Section 348 acts only once it “appears to the Commissioner” that a building is dangerous. Section 344 acts only once someone notices work proceeding without or contrary to sanction. Nowhere in Chapter XVI does the Act require MCD to send anyone to a site on its own initiative, at any fixed point after sanction, to check whether the building is still standing the way it was approved to stand.

The bye-laws fill the gap with paperwork rather than people. Under the Unified Building Bye-Laws, 2016, (UBBL) a structural stability certificate has to be filed at only two instances. One, when the plan is sanctioned, and again when the completion-cum-occupancy certificate is sought. The Ministry of Home Affairs told the Lok Sabha in March 2016 what this means in practice, the certificate is signed by the owner, the architect and a structural engineer engaged by the owner, and “the structural safety of building is relied upon the structural engineer engaged by the owner.” MCD does not run its own structural check at either stage. It just checks whether such a piece of paper exists.

Structural safety in Delhi is certified on two occasions, in each case by professionals engaged and paid by the owner. Thereafter, it is presumed to continue until a complaint is made or the Commissioner happens to notice a problem. No third checkpoint exists between these points.

What this meant for Satya Niketan

Where a building has no sanctioned plan, neither certification stage takes place, as there is nothing against which to certify. In the present case, no complaint was made about the basement work, and no municipal officer observed the site and formed a view, so Section 348 was never invoked. The building could therefore remain wholly outside MCD's scrutiny and continue to stand and fill with students, until the afternoon it collapsed.

This is not the only instance. Three months earlier, on 30 May 2026, a five-storey building collapsed in Saidulajab, killing six people. The Supreme Court’s amicus curiae reported that the property had been booked for unauthorised construction since 2015, and that the MCD had “failed to discharge its statutory obligations” under Sections 332, 346 and 348 of the Act and Bye-Laws 1.7.2, 2.7.2 and 2.11 of the UBBL, despite years of documented violation. Saidulajab and Satya Niketan are almost mirror cases. In Saidulajab, the violation was known for a decade and enforcement still did not happen. In Satya Niketan, the violation was never brought to anyone’s notice at all. Both point to the same problem. MCD gets involved with a building only when paperwork or a complaint brings it in. It has no routine of its own for checking on a building once it is standing.

The Delhi High Court noticed something close to this when it ordered a high-level inquiry a day after the collapse, observing that had the authorities been alive to their statutory responsibilities, the incident could have been avoided. A week later, an MCD survey of 2,453 PG properties found sanctioned plans for only 726 of them, and structural stability certificates for just eight. Even the thin, twice-only paper system the law relies on was not being complied with across the very category of building that had just collapsed.

What other cities do differently

Mumbai’s building law does not leave the question of when to recheck a structure to chance. Section 353B of the Mumbai Municipal Corporation Act, 1888, requires every building over 30 years old to undergo a structural audit by a registered engineer, with the report filed to the ward office, and buildings between 15 and 30 years old fall under a similar cycle set by cooperative housing bye-laws. The audit is still conducted by a private engineer, so BMC has not solved the self-certification problem either. What it has done is convert the timing of re-inspection from a matter of luck into a matter of the calendar. The condition of a structure itself puts it in front of the authorities again and again, whether or not anyone complains.

Bengaluru’s BBMP has approached the same problem from the plan-approval end instead. Its online portal runs automated checks that flag setback, foor area ratio and height violations before a human officer even opens the file, and a BBMP engineer is expected to inspect the site in person before an occupancy certificate is issued. This does not cover construction-stage monitoring either. But it closes part of the gap between the plan on paper and the building on the ground.

Neither city has got rid of private certification. Both have simply stopped treating re-inspection as something that happens only when somebody asks for it.

What needs to change?

Delhi requires no new demolition or sealing powers, as the existing framework already confers them in ample measure. What is lacking is a trigger for intervention that does not depend on a complaint reaching the Commissioner. An amendment to the UBBL, or a bye-law modelled on Section 353B, could make a third-party structural audit mandatory for buildings above a prescribed age, and for any building used as a PG, hostel or similar high-occupancy premises above a specified number of residents. The audit would be filed on a fixed cycle and not at the owner's convenience. A public, searchable register of sanctioned plans and audit status for such buildings, which a university or a prospective tenant could consult, would complement this requirement. Together they would change the basis on which safety is treated. Under the present system, a building is presumed safe until shown otherwise. Under the proposed one, the owner would have to establish safety periodically and on record.

The point that matters

Satya Niketan differs from Saidulajab in an important respect. In Saidulajab, MCD had a violation on file and failed to act on it. In Satya Niketan, no file existed, since the law did not require one to be opened until it was too late to matter.

The deficiency therefore lies in the design of the law itself and cannot be attributed to defective implementation alone. Absent a change, the same outcome can be expected in the next building that the commissioner has no occasion to examine.