BCA to start independent investigations into Tanjong Katong sinkhole incident
'The investigation will examine the circumstances leading to the formation of the sinkhole, identify the root causes, and take the necessary actions against any non-compliance under the Building Control Act and Regulations,' BCA said in a media statement.
The agency said investigations could take several months, given the complexity of the incident.
'It will include detailed geotechnical analysis and other validation tests by BCA and its appointed consultants,' BCA added.
The sinkhole appeared along Tanjong Katong Road South on Saturday evening, causing a car to fall in. The female driver was rescued by workers and taken conscious to Raffles Hospital.
BCA said that since the incident, its engineers have been conducting round-the-clock site monitoring to ensure that surrounding buildings, roads and infrastructure remain structurally safe.
'As a precautionary measure, BCA had recommended that PUB implement a safety time-out for similar sewer construction projects across Singapore, and conduct a thorough review of current practices and safeguards at these worksites,' it added.
PUB said on Sunday that it called for a safety timeout to review similar sewer works.
It said works near the sinkhole involved the construction of a 16m-deep shaft connecting three existing sewer lines.
Providing a timeline of what happened, PUB said that a concrete component in the shaft failed at around 5.50pm on Saturday.
At around the same time, a sinkhole formed on the adjacent road.
PUB said it was still not clear what contributed to the failure of the component. "The shaft has been backfilled to stabilise the surrounding ground," it said on Sunday.
Hashtags
Try Our AI Features
Explore what Daily8 AI can do for you:
Comments
No comments yet...
Related Articles
Business Times
10 hours ago
- Business Times
Carro targets US IPO with over US$3 billion valuation: sources
[SINGAPORE] Singapore-based Carro, South-east Asia's largest used-car online marketplace, is preparing for a US initial public offering as early as 2026 that could raise up to US$500 million, according to sources familiar with the matter. The company is aiming for a valuation of more than US$3 billion, according to the sources, who could not be named discussing confidential information. If successful, Carro's listing would be the largest South-east Asian IPO in the US since Sea's US$989.3 million listing in 2017 and the third biggest South-east Asian high-tech IPO in the US, according to LSEG. It would also be the first major automotive tech and artificial intelligence or AI-driven commerce startup from Singapore to go public in the US. Carro is on track to deliver US$100 million in annual earnings before interest, taxes, depreciation, and amortisation by its fiscal year ending March 2026, one of the sources said. The IPO size is still under discussion and may change depending on market conditions, the sources added. BT in your inbox Start and end each day with the latest news stories and analyses delivered straight to your inbox. Sign Up Sign Up Carro did not immediately respond to an email request seeking comment on Wednesday. Founded in 2015, Carro operates a digital platform that enables consumers and dealers to buy and sell vehicles, while also offering insurance, financing and after-sales services. Besides Singapore, it has a presence in markets across the Asia-Pacific region including Malaysia, Indonesia, Thailand, Japan, Taiwan and Hong Kong, its websites show. With over 4,500 employees across Asia-Pacific, Carro has raised more than US$1 billion in debt and equity from investors including Temasek, SoftBank and several other sovereign funds, according to its websites. A successful listing could pave the way for other regional unicorns such as Carsome, Traveloka and Xendit to follow suit. Beyond South-east Asia, a growing number of Chinese companies are also eyeing US listings, drawn by the potential for higher valuations despite ongoing geopolitical tensions. REUTERS
CNA
10 hours ago
- CNA
CNA938 Rewind - Are AI enhancements behind BlueSG's 'strategic pause' and suspension of services?
Electric car-sharing firm Blue SG will suspend operations from this Friday, 11.59 p.m. It will return next year though. Is this move due to market competition or infrastructure? Daniel Martin finds out more from Keith Kee, CEO, Blue SG.
Independent Singapore
11 hours ago
- Independent Singapore
SBS Transit apologises, reveals 2 passengers were hospitalised after double-decker buses collided
SINGAPORE: SBS Transit has apologised for the crash involving two of its double-decker buses on Tuesday (Aug 5). The company has also revealed that two out of the 12 passengers who were sent to the hospital have been warded. The accident involving the two buses and a private-hire car occurred along Tampines Ave 7, around 10 a.m. All three vehicles were travelling in the same direction, towards Tampines Ave 12, when the crash occurred. A video uploaded by TikTok user @143mindie shows the aftermath of the accident, with one of the buses having a smashed window. The other sustained more significant front-end damage. The front door of the rear bus appeared badly crumpled from the impact. A car was seen wedged in front of the bus at the front. A total of 13 individuals were taken to the hospital, including the 69-year-old driver of one of the buses and 12 passengers aged between 30 and 69. All were reported to be conscious at the time of transport. See also Apologise for speaking in Parliament? A spokesperson for SBS Transit has since apologized for the accident and said that the welfare of the affected passengers is the company's top priority. The representative revealed that an SBS team had earlier gone to the hospital to provide care, support, and assistance. The driver and 10 passengers received outpatient treatment, while the other two passengers needed to be hospitalized. SBS Transit promised to continue to support the injured passengers. The company is also assisting the police in ongoing investigations. () => { const trigger = if ('IntersectionObserver' in window && trigger) { const observer = new IntersectionObserver((entries, observer) => { => { if ( { lazyLoader(); // You should define lazyLoader() elsewhere or inline here // Run once } }); }, { rootMargin: '800px', threshold: 0.1 }); } else { // Fallback setTimeout(lazyLoader, 3000); } });
