Malaysia helicopter crash aircraft identified as BO-105, investigation ongoing
The helicopter that crashed in Long Lellang, Malaysia, killing five, has been identified as a BO-105, according to Free Malaysia Today.
2 reports on this incident · first at Sep 8, 2026, 9:44 p.m. ET
This report went out within minutes of the first account of it. Early reports are provisional and are frequently revised; where sources disagree, both readings are given.
We last searched for new coverage of this at Sep 8, 2026, 10:09 p.m. ET — checked 1h ago.
Earlier reports
Sep 8, 2026, 9:44 p.m. ETFirst report
Helicopter crash in Malaysia kills five, investigation ongoing
A BO-105 helicopter crashed in Long Lellang, Malaysia, on September 8, 2026, killing all five people on board, according to Free Malaysia Today. The cause of the crash has not been determined, and the investigation is ongoing.
The helicopter, registered 9M-LLF, was built in Germany in 1991 and had serial number S-867. Production of the BO-105 model ceased in 2001, the outlet reported. The operator was the Flying Doctor Service.
The crash occurred near the settlement of Long Lellang, which is located in the Miri district of Sarawak, according to geographic reference data. The settlement's terrain elevation is 1,542 feet, and Long Lellang Airport is 137 feet southeast of the settlement.
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
- Senator calls for BO-105 helicopters to be groundedfreemalaysiatoday.com
Revision history
- Version 19 Sept 2026, 01:52current
First published.
- Version 19 Sept 2026, 01:44current
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.