Smoke erupts from Jansadharan Express power car at Simri Bakhtiyarpur station

Share:
Audio Loading voice…
Smoke erupts from Jansadharan Express power car at Simri Bakhtiyarpur station

Synopsis

A suspected brake-binding fault sent smoke billowing from the power car of the Jansadharan Express at Simri Bakhtiyarpur station in Bihar, triggering passenger panic and an emergency chain pull. The fire brigade was called in, the situation was contained, and the train resumed after a 25-minute delay — with no injuries but a formal railway investigation now under way.

Key Takeaways

Smoke erupted from the power car of train No.
14603 Jansadharan Express at Simri Bakhtiyarpur Railway Station , Bihar, on Friday evening, 2 May 2025 .
Preliminary indications point to brake binding as the cause; a formal railway investigation has been launched.
Passengers pulled the emergency chain, halting the train near an overbridge; the local fire brigade was called to assist.
The situation was brought under control after sustained efforts by railway staff and fire brigade personnel.
No casualties or injuries were reported; the train was delayed by approximately 25 minutes before resuming its journey to Amritsar .

Smoke billowed from the power car of train No. 14603 (Up) Jansadharan Express at Simri Bakhtiyarpur Railway Station in Bihar on Friday, 2 May 2025 evening, triggering panic among passengers aboard the Saharsa–Amritsar service. No casualties or injuries were reported, and the train resumed its journey after a delay of approximately 25 minutes.

How the Incident Unfolded

According to eyewitnesses, thick smoke rose from beneath the power car, with preliminary indications pointing to brake binding as the likely cause. Alarmed passengers immediately pulled the emergency chain, bringing the train to a halt near an overbridge close to Simri Bakhtiyarpur station.

As the train stopped, panic spread rapidly. Several passengers rushed to deboard as a precaution, while others remained on board attempting to assess the situation. The train's driver and guard responded promptly, and onboard railway staff deployed fire extinguishers in an effort to contain the smoke.

Fire Brigade Called to the Spot

Despite the initial efforts of railway personnel, the smoke persisted for some time, making the situation appear serious. Railway authorities quickly alerted the local fire department, and a fire brigade team reached the spot shortly thereafter.

Working in coordination with railway personnel, the fire brigade launched a containment operation. After sustained efforts, the situation was brought under control, averting what could have turned into a major accident. The train was then moved cautiously to Platform No. 1 at Simri Bakhtiyarpur Railway Station before being cleared to resume its journey.

Investigation Under Way

Railway authorities have initiated a formal investigation to ascertain the exact cause of the smoke. While preliminary indications point to a technical fault linked to brake binding, officials stated they are examining all possibilities and have not ruled out other mechanical factors.

This is not the first time a technical snag on a passenger express has caused passenger panic on the busy Bihar–Punjab corridor. The Jansadharan Express is one of the key inter-state services connecting Bihar with Punjab and Haryana, making its reliable operation critical for thousands of daily commuters.

Passengers Left Shaken, No Injuries Reported

Fortunately, no casualties or injuries were reported in the incident. However, the sudden development left several passengers visibly shaken. The train recorded a delay of approximately 25 minutes before it was cleared to continue towards Amritsar.

As railway authorities complete their technical inquiry, the incident has once again drawn attention to the importance of routine maintenance checks on power cars of long-distance express trains.

Point of View

But the Simri Bakhtiyarpur incident raises a harder question: how routinely are power cars on long-distance Bihar corridor expresses inspected for brake and mechanical faults? Brake binding generating enough smoke to trigger a passenger panic and a fire brigade call-out is not a minor snag — it is a systemic maintenance signal. The Jansadharan Express connects some of Bihar's most migration-heavy districts to Punjab and Haryana, meaning its passenger load is consistently high and the consequences of a more serious failure would be severe. Railway authorities owe commuters a transparent inquiry outcome, not just an internal note.
NationPress
8 Jul 2026

Frequently Asked Questions

What happened to the Jansadharan Express at Simri Bakhtiyarpur station?
Smoke began billowing from the power car of train No. 14603 Jansadharan Express at Simri Bakhtiyarpur Railway Station in Bihar on Friday evening. Passengers pulled the emergency chain, halting the train, and the fire brigade was called in to assist railway staff in containing the smoke.
Was anyone injured in the Jansadharan Express smoke incident?
No casualties or injuries were reported. While several passengers panicked and rushed to deboard, the situation was brought under control before any harm occurred.
What caused the smoke from the Jansadharan Express power car?
Preliminary indications suggest brake binding as the likely cause of the smoke. However, railway authorities have initiated a formal investigation and are examining all technical possibilities.
How long was the Jansadharan Express delayed?
The train was delayed by approximately 25 minutes. After the situation was brought under control, it was moved to Platform No. 1 at Simri Bakhtiyarpur station and then cleared to resume its journey towards Amritsar.
Which route does the Jansadharan Express operate on?
The Jansadharan Express (train No. 14603) runs from Saharsa in Bihar to Amritsar in Punjab, serving as one of the key inter-state rail links connecting Bihar with Punjab and Haryana.
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. 8 months ago
  4. 8 months ago
  5. 11 months ago
  6. 1 year ago
  7. 1 year ago
  8. 1 year ago
Google Prefer NP
On Google