Real Philippine structural failures, engineered breakdowns of what went wrong and what the code requires. No speculation — just the mechanics, the red flags, and the NSCP 2015 provisions meant to prevent them.
The failure modes behind almost every Philippine structural-collapse story we've covered.
5 dead, DOLE flagged this site 8 months before it fell — the pancake-collapse mechanics and the red flags every developer must check.
Read the analysis →
DPWH's own words confirm years of creek erosion brought down the bridge — what "scour" means and why it's invisible until it isn't.
Read the analysis →The Cotabato Trench mechanism, the failure modes behind collapsed buildings, and what NSCP 2015 §208 actually protects against.
Read the analysis →One week on: the full damage picture, aftershock data, and what the numbers mean for rebuilding safely to code.
Read the analysis →A negligent collapse and a M7.8 earthquake, 15 days apart, exposing the same engineering gaps — plus a practical resilience checklist.
Read the analysis →
We fact-check the "Ring of Fire" claim and explain what a cluster of global quakes means for Philippine buildings.
Read the analysis →
Where each active trench sits, who's nearest, and a self-check for whether your building is ready.
Read the analysis →A licensed engineer can check soft-storey risk, column sizing, and foundation condition in a single site visit.
This is a standing series — every verified Philippine structural failure we analyze gets added here. Each case is broken down the same way: what failed, why it failed, and which NSCP 2015 provision exists to prevent it from happening again.
We publish a full engineering breakdown within 24–48 hours of a verified structural failure. Join the alert channel and get notified the moment a new case goes live — no email, no spam, just the analysis.
Request a structural inspection from a PRC-licensed engineer — site visit plus a written report.