Layang Layang Aerospace Grounds BO-105 Fleet After Fatal Sarawak Crash
The operator voluntarily grounded its BO-105 helicopters and other Rolls-Royce 250-equipped aircraft after a Flying Doctor Service flight crashed near Long Lellang on September 8, killing five.
2 reports on this incident · first at Sep 9, 2026, 7:26 a.m. ET
Earlier reports
Sep 9, 2026, 7:26 a.m. ETFirst report
Helicopter crash in Sarawak kills five, says Malaysian report
A helicopter operating a Flying Doctor Service (FDS) flight crashed near Long Lellang, Sarawak, Malaysia, on September 8, 2026, killing all five people on board, according to The Star. The dead include the pilot and four Health Ministry personnel, the outlet reported.
The helicopter, registered 9M-LLF, was operated by Layang Layang Aerospace Sdn Bhd (LLA), a subsidiary of Hubline, The Star reported. The Air Accident Investigation Bureau is investigating the crash, according to the same report.
The cause of the crash has not been determined.
Was this report accurate and useful?
Reference data
From aircraft and geographic registries, not from the news sources. Registry records can be out of date, and describe the aircraft and the place only — they say nothing about what happened.
- Terrain elevation
- 1,542 ft
- Nearest aerodrome
- 137 ft SE of Long Lellang Airport (WBGF/LGL)
Sources
- Helicopter operator grounds fleet following Sarawak crashfreemalaysiatoday.com
- Hubline confirms subsidiary operated helicopter in fatal Sarawak crashthestar.com.my
Revision history
- Version 210 Sept 2026, 06:17current
Added operator's voluntary grounding of BO-105 and Rolls-Royce 250-equipped aircraft, CAAM statements on the precautionary nature of the grounding and against speculation, certificate validity dates, and AAIB investigation details.
- Version 19 Sept 2026, 11:52
First published.
- Version 19 Sept 2026, 11:26current
First published.
How we work
This site models an investigative reporter rather than a wire desk. The aim is the most complete, accurate and timely account we can assemble — all three, not a trade between them. Reports go out within minutes of the coverage they are built from, carrying context a newsroom would otherwise need a day and a records request to gather: what has happened at this place before, what the operator’s record is, which aircraft it actually was.
Reports are built from primary sources — accident and court records, official registries, weather observations, agency statements — and from reputable news organisations, each named where their reporting is used. Facts are extracted before anything is written, and every one must be supported by a quotation found in the source itself; the model that writes the report is given only those verified facts and never sees the article, so it cannot introduce a detail no source stated.
Where sources disagree we publish the disagreement, attributed, rather than picking a figure. Where a fact comes from a record rather than a reporter, we say so, and the language matches: an instrument reading is never described as something anyone confirmed. Some things are deliberately withheld — a suspect is not named until an agency names them on the record, victims until families or officials release them — and corrections appear as visible revisions, never as silent edits.
None of that makes a report true. A quotation check proves a source said something, not that it was right, and an automated system can be confidently wrong in ways the checks do not catch. If something here is wrong, the feedback above is how it gets found. The full methodology, including what we refuse to publish.