One dead, 15 injured as Dashain bus overturns in Udayapur, cause unknown

Why it ran today

• ranking judge 1: ranked #3 with 68/100. A Dashain homecoming bus crash on Thursday, October 15, with one dead. It is confirmed by Nagarik, The Rising Nepal, Kantipur and others, so it meets the breaking and season brief. Attribute the injured count by outlet, because Radio Nepal says 14, Nagarik and Kantipur 15, and Himalpress and Khabarhub 16. State that police gave no cause, and name none of the injured, two of whom are minors. Weakest dimension is the buried angle.
• ranking judge 2: ranked #3 with 66/100. Kept at 3, with one amendment to the reason. The crash happened Thursday, October 15, so it is fresh but outside the 12-hour breaking window. It earns its place on the season brief and on corroboration from Nagarik, The Rising Nepal and Kantipur. Attribute the injured count by outlet: 14 per Radio Nepal, 15 per Nagarik and Kantipur, 16 per Himalpress and Khabarhub. Say police gave no cause, and name none of the injured, two of whom are minors. Weakest dimension is the buried angle.

What the desk dug up

• The pattern. The Madan Bhandari Highway through Udayapur district is a recognized hazard corridor: at least four other serious bus or truck crashes have hit this same stretch in the past 14 months, independent of Thursday's Surke crash, none of which same-day coverage of this story mentions. [Ratopati English] [Khabarhub English]
• Left out. No report on Thursday's crash states a cause, yet the most recent comparable bus crash on this same highway in this same district, in February 2026, was attributed by police to brake failure — a mechanical-failure pattern on this corridor that no outlet has raised in connection with this crash. [Ratopati English] [The Rising Nepal]
• Left out. Nagarik News reports driver Suman Khattri was taken into custody with 'further investigation' ongoing, but no outlet — including the ones in today's coverage set — reports his legal status, whether he has been charged, or whether the bus's fitness and permit record has been checked. [Nagarik News]

Validation

1 red team round, 2 revisions. Decision: approved.

• accuracy88
• relevance74
• defensibility88
• reach52

Judge 1: The core event is solid and well sourced in the two fetched reports. The piece names no injured child, as the ranking orders require. It carries several accuracy faults: a place name credited to the wrong outlet, a claim that both outlets reported police gave no cause, a 2025 truck crash presented as 'this year', and an injury count dispute built on unfetched pages that may not be a real disagreement. The card also breaks the length rules. All of these are precise fixes, so the piece goes back for one editing pass.

Judge 2: All four edits ordered in the last round were made, even though the log marks them as still missed. The injured passenger's name is gone from the body and from the sources list. The 5:30 pm time of death is credited to Nagarik. The trigger is replaced, and the repeated line about the other 14 injured is deleted. On a full reread, every fact traces to The Rising Nepal, Nagarik or myRepublica, no injured person or child is named, the driver's status is the plain action, and all dates check out. The two remaining loose spots are minor: the take's 'died hours after' covers a gap of about 95 minutes, and the headline says 'cause unknown' where the body says police have not said. Virality is still below target, but no revisions are left.

The complete record, including the advocate, skeptic, red team and defence arguments, is kept by the newsroom.