Fire guts Jaynagar-Udhna Express coach at Madhubani station; no casualties

Share:
Audio Loading voice…
Fire guts Jaynagar-Udhna Express coach at Madhubani station; no casualties

Synopsis

A general coach of the Jaynagar-Udhna Express was completely gutted by fire at Madhubani station on 28 May — the second coach fire on the Samastipur Division in just ten days. No one was hurt, but the repeat incidents have prompted the DRM to order a high-level inquiry, putting railway maintenance safety protocols under scrutiny.

Key Takeaways

A fire broke out in a general coach of the Jaynagar-Udhna Express at Madhubani railway station on 28 May 2025 , completely gutting the compartment.
No passengers or railway staff were injured; the train had been parked for maintenance for two days prior to the incident.
The coach was stationed on Platform No.
3 when flames and thick black smoke suddenly emerged.
DRM Jyoti Prakash Mishra of the Samastipur Railway Division visited the site and ordered a high-level inquiry committee .
Preliminary cause is suspected to be a short circuit ; final findings await the inquiry report.
A similar coach fire occurred on 18 May aboard the Sasaram-Patna Fast Passenger train (53212) , also attributed to a short circuit.

A fire broke out in a general coach of the Jaynagar-Udhna Express at Madhubani railway station in Bihar on Thursday, 28 May, completely gutting the compartment, according to railway officials. No passengers or staff were injured, as the train had been stationed for maintenance for the past two days.

How the Fire Broke Out

The affected coach was parked on Platform No. 3 for scheduled maintenance work when thick black smoke and flames suddenly began emerging from it. The blaze spread rapidly through the general compartment before bystanders could intervene. People present at the station immediately alerted the Station Master upon noticing the fire.

Fire brigade teams were rushed to the spot, but a substantial portion of the coach had already been damaged by the time they arrived. After extensive firefighting efforts, the blaze was brought under control and prevented from spreading to adjacent coaches.

DRM Rushes to Spot, Inquiry Ordered

Jyoti Prakash Mishra, the Divisional Railway Manager (DRM) of the Samastipur Railway Division, travelled to Madhubani on a special train to personally inspect the site. During the visit, he reviewed the extent of the damage and sought detailed reports from railway officials on the circumstances leading to the fire.

Acknowledging the seriousness of the incident, Mishra announced the formation of a high-level inquiry committee to determine the exact cause and assess any lapses in safety protocols. Railway authorities have preliminarily attributed the fire to a short circuit, though the final cause will be confirmed only after the inquiry report is submitted.

A Pattern of Coach Fires This Month

This is the second such incident on the same railway network within ten days. On 18 May, a fire broke out in a general coach of the Sasaram-Patna Fast Passenger train (53212) while it was stationed at Platform No. 6 ahead of its scheduled 6:45 am departure. That fire was also reportedly triggered by a short circuit, in the fifth coach from the engine.

The recurrence raises questions about the adequacy of routine fire-safety inspections on coaches undergoing maintenance at station platforms — a concern that the inquiry committee will likely be expected to address.

Impact and Immediate Response

The incident briefly triggered panic among passengers and staff present at the station premises. Fortunately, the absence of passengers aboard the stationary coach averted what could have been a far more serious tragedy. The Samastipur Division has been put on heightened alert as authorities await the inquiry findings.

With the high-level committee now in place, the focus shifts to whether the preliminary short-circuit theory holds and whether systemic safety gaps in coach maintenance procedures need to be addressed across the division.

Point of View

Which points to a gap in pre-departure and in-maintenance electrical inspections rather than an operational anomaly. The DRM's personal visit and high-level inquiry signal institutional seriousness, but the real test is whether the committee's findings translate into enforceable changes to maintenance protocols. Indian Railways has a long history of post-incident committees whose recommendations gather dust; this case, coming in quick succession, offers an opportunity to break that cycle.
NationPress
13 Jul 2026

Frequently Asked Questions

What happened at Madhubani railway station on 28 May?
A fire broke out in a general coach of the Jaynagar-Udhna Express at Madhubani railway station on 28 May, completely gutting the compartment. The coach was parked on Platform No. 3 for maintenance work when flames and thick black smoke suddenly emerged.
Were any passengers or staff injured in the Madhubani train fire?
No passengers or railway staff were injured. The train had been stationed at the platform for maintenance for two days, so no passengers were on board at the time of the incident.
What is the suspected cause of the Jaynagar-Udhna Express fire?
Railway authorities have preliminarily attributed the fire to a short circuit. However, the exact cause will be confirmed only after the high-level inquiry committee submits its report.
Who is investigating the Madhubani railway fire?
DRM Jyoti Prakash Mishra of the Samastipur Railway Division visited the site and announced the formation of a high-level inquiry committee to determine the cause and assess safety lapses.
Has a similar train fire occurred recently in Bihar?
Yes. On 18 May, a fire broke out in a general coach of the Sasaram-Patna Fast Passenger train (53212) at Platform No. 6, also reportedly triggered by a short circuit in the fifth coach from the engine. This makes the Madhubani incident the second such fire on the division within ten days.
Nation Press
The Trail

Connected Dots

Tracing the thread behind this story — newest first.

8 Dots
  1. Latest 1 month ago
  2. 1 month ago
  3. 2 months ago
  4. 2 months ago
  5. 8 months ago
  6. 1 year ago
  7. 1 year ago
  8. 1 year ago
Google Prefer NP
On Google