One Saptakoshi Boat Victim Identified, Police Say Three Still Missing
Police accounts of Sunday's capsize near Triveni blame the engine, overloading or a failed brake, and counts of those aboard run from 14 to 16.

One of the three people killed when a passenger boat capsized in the Saptakoshi River on Sunday, October 25, has been identified, police said. The search for three others was still under way when police last spoke to reporters that day, with no settled count of how many were on board. Nepal Wire found no new police update on the search, the two unidentified dead or the driver as of 9am on Monday, October 26.
If your family travels hill routes by boat or bus at Dashain and Tihar, this is about that trip. DC Nepal reported that vehicles on hill and remote routes carry more people than they should in the festival season, and that accidents like this keep happening. Police found in their first check that 16 people were aboard this boat, more than its capacity, DC Nepal reported.
Nagarik News reported, citing police, on the afternoon of Sunday, October 25, that the dead woman was Lila Rai, about 52, of Baraha Kshetra Municipality-1 in Sunsari district. She was pulled from the river alive but died during treatment at Chatra Hospital. Early Sunday reports by DC Nepal and Setopati, citing Sunsari police, had described the dead woman as 35. The other two bodies, those of a man described as 40 to 50 years old and a girl first reported as 5 by DC Nepal and Setopati and later as about 6 or 7 by Setopati, remain unidentified, Setopati reported, citing police.
The motorboat was travelling from Kopche in Bhojpur district toward Chatra in Sunsari's Baraha Kshetra municipality when it capsized around 2pm on Sunday, October 25, near Triveni, the point where Dhankuta, Udayapur and Bhojpur districts meet on the river, according to DC Nepal, Setopati and Nagarik News, all citing police.
Three people remain missing, Nagarik News and Setopati reported, citing police: Pramila Magar, 21, and Manu Rai, 22, both of Baraha Kshetra-1, and a seven-year-old boy whom Nepal Wire is not naming because he is a child. Nepal Police and a team from the Armed Police Force, a federal police force that also runs rescues, from its No. 6 unit in Dhankuta are searching for them, Setopati reported.
The boat's driver, Suman Magar, swam out, DC Nepal and Setopati reported. Nagarik News gave his age as 24 and his home as Baraha Kshetra-1. Police took him under their control and are investigating, DC Nepal and Setopati reported. No outlet reported a charge.
What the coverage missed
Police themselves have not settled on how many people were on the boat. Nagarik News quoted Superintendent Narayan Ranjitkar, the Dhankuta police chief, saying on Sunday, October 25, that 14 passengers were reported aboard but the figure was not confirmed. Setopati's report on Sunday, October 25, put the figure at 15, including the driver, while a separate Setopati report that day quoted Police Inspector Bikram Bahadur Bhattarai saying 16 were aboard. DC Nepal reported on Sunday, October 25, that police found in their first check 16 people aboard against only 11 tickets sold, with the driver telling police the other five were his own relatives. OnlineKhabar's report on Sunday, October 25, put the ticket count at 12, not 11, for the same 16 people.
The accounts of why the boat went down differ too. Police Inspector Bikram Bahadur Bhattarai of the Baraha Kshetra area police office told Setopati the engine stopped in the Arun river stretch. Superintendent Narayan Ranjitkar, the Dhankuta police chief, told OnlineKhabar the engine failed and the boat drifted. DC Nepal reported overloading and a fast current as the suspected cause, without naming who made that estimate. A later Setopati report the same day said police had first information that the brake failed.
OnlineKhabar reported the jetboat service had been halted since Asar, the monsoon month that began in mid June, and restarted on Kartik 1, which was October 18, one week before the accident. No outlet, including police, has stated the boat's licensed passenger capacity or named who operates or licenses the service.
What we still do not know
- Why the service stopped in Asar and what checks, if any, came before it restarted on October 18.
- The boat's permitted passenger limit and which office licenses the route. No outlet has reported either.
- Which of the three causes police have given is the one they are standing behind. The District Police Offices of Dhankuta and Sunsari could answer.
- The names of the two still unidentified dead. Police or Chatra Hospital could answer.
- Whether the search for the three missing people, including the seven-year-old boy, has found them. Nepal Police and the Armed Police Force's No. 6 unit in Dhankuta could answer.
- Whether driver Suman Magar faces any charge or is only being held while police investigate. Police or the public prosecutor's office could answer.
Get stories like this every morning
One free email with the day's checked stories, each with what the coverage missed.
Sources
- DC Nepal · Initial accident account, ticket vs passenger count (16 aboard, 11 tickets) from police's first check, overloading and fast current cause, driver's statement, festival-season context, driver taken under police control
- Setopati · Police Inspector Bikram Bahadur Bhattarai's account of the engine stopping in the Arun river stretch and 16 people aboard
- Setopati · Corroborating initial victim descriptions, including the 35 year old age for the dead woman and 5 year old age for the dead girl, and driver Suman Magar swimming to safety
- Setopati · Brake failure account, names of three missing people, 15 aboard figure, rescue team deployment including the APF's No. 6 unit in Dhankuta, revised ages for the dead woman and girl
- Nagarik News · Superintendent Narayan Ranjitkar's unverified estimate of 14 passengers and initial unconfirmed victim descriptions
- Nagarik News · Identification of Lila Rai, names of three missing people, survivor list, driver's age and address
- OnlineKhabar · 12 ticket count, engine failure while drifting cause, service suspension since Asar and resumption on Kartik 1 (October 18)
Editorial review record
Why it ran today
- ranking judge 1: ranked #2 with 62/100. We ran this on Oct 25 with up to five missing. The real development is Nagarik's 16:19 update: one of the dead identified, three named people still missing, and the driver in police custody. Setopati adds a brake failure account against earlier engine failure and overloading reports. Every count needs its outlet and timestamp, and the missing child is not named. Weakest dimension is comment friction.
- ranking judge 2: ranked #2 with 62/100. Confirmed as a real development since our Oct 25 piece: Nagarik's 16:19 update identifies one of the dead, names three people still missing instead of up to five, and reports the driver held by police, and Setopati adds a brake failure account. Every count carries its outlet and timestamp, the driver is described as held, not charged, the missing seven-year-old is not named, and the desk rechecks for an Oct 26 police update before publishing. Weakest dimension is comment friction.
What the desk dug up
- The numbers. Police-sourced accounts of how many people were aboard and how many tickets were sold for the boat do not agree even within the same day: DC Nepal/Setopati cite 11 tickets for 16 aboard, OnlineKhabar cites 12 tickets for 16 aboard, Nagarik News cites an unverified estimate of just 14 total, and Setopati's later update puts the total at 15 including the driver. [DC Nepal, citing Sunsari District Police] [OnlineKhabar, citing Dhankuta Police Chief Narayan Ranjitkar]
- The record. One report states the jetboat/motorboat service on this Bhojpur-Chatra route had been suspended since Asar (roughly four months) and had only resumed operation on Kartik 1, about a week before the Kartik 8 accident that killed three people. [OnlineKhabar]
- The record. The officially stated technical cause of the capsizing shifts across four police-attributed accounts published within hours of each other on the same day: sudden engine trouble, engine failure while drifting, overloading plus fast current, and brake failure. [Setopati, citing Baraha Kshetra Police Inspector Bikram Bahadur Bhattarai] [OnlineKhabar, citing Dhankuta Police Chief Narayan Ranjitkar]
- Left out. None of the available reports states the boat's officially certified or rated passenger capacity, nor names the operator, owner or licensing authority of the Bhojpur-Chatra jetboat/motorboat service, despite describing it as a ticketed commercial run. [DC Nepal] [Republica]
Validation
1 red team round, 2 revisions. Decision: approved.
- accuracy87
- relevance78
- defensibility87
- reach61
Judge 1: The core facts trace to fetched pages and two independent newsrooms: three dead, one identified, three missing, the driver held. But the piece ignores the ranking desk's recheck and timestamp orders. It also inflates three police accounts of the cause into four and misattributes DC Nepal's estimate and the driver's status. It drops the 'about' qualifier and the early age conflicts, and the take misstates who is waiting for a name. The card, hook and trigger are weak and repeat themselves, but all of this is fixable in one pass.
Judge 2: All five edits judge 2 ordered are in place: the 'No. 6 unit' bullet, the timed and split lead, DC Nepal's count tied to police's first check in the body and in key_facts[2], the split driver key fact, and the split caption sentence. On a final read against the fetched pages, every death, missing and passenger count, every cause, the October 18 restart and the driver's status trace to their outlets. The missing child is not named and the card is a verified toll. One thing remains that only the desk can confirm: my search tool was unavailable, so I could not check the 9am Monday recheck line myself. Two smaller points are within what the sources support: the take calls Setopati's 15 a police count, and the dek and caption list overloading under 'police accounts'.
The complete record, including the advocate, skeptic, red team and defence arguments, is kept by the newsroom.




Readers' comments
Say what you know. A comment shows once the desk has read it, usually within the hour. A question gets its answer from the story's record.
No comments yet. Be the first.