73 killed as fire breaks out in train in Pakistan

Agencies
October 31, 2019

Oct 31: A massive fire broke out on a moving train in Pakistan's eastern Punjab province on Thursday after two gas cylinders exploded while some passengers were cooking breakfast, killing at least 73 people, mostly Islamic preachers travelling to attend a religious congregation.

The train, Tezgam Express, was on its way to Lahore from Karachi when the fire broke out early morning, gutting three bogies which had over 200 passengers, including women and children, at Liaquatpur near Rahim Yar Khan, some 400 kms from Lahore, authorities said.

District Emergency Officer RYK Baqir Hussain has confirmed that 73 passengers lost their lives in the fire.

Most deaths occurred from people jumping off the train, the authorities said, adding that the toll could rise further as more than 40 passengers have suffered severe burn injuries.

Railway Minister Sheikh Rashid Ahmad said that most of the victims belonged to the Tableeghi Jamaat (Islamic preachers) who were going to Lahore to attend a major annual congregation at Raiwind.

The Railways Minister said two gas stoves carried by some passengers blew up when they were preparing breakfast on the speeding train in violation of rules.

"Some of the passengers started making breakfast on small gas cylinders they brought with them when they exploded and the fire engulfed the three coaches of the train," he said.

The Tableeghi Jamaat office-bearers, however, dismissed the Railway Minister's claim, saying the explosion took place because of "short circuit".

"Some injured passengers said that they had told the train officials late on Wednesday night about the short circuit smell but no attention was paid and on Thursday morning explosion took place," the Jamaat said.

Prime Minister Imran Khan expressed his grief over the incident and directed authorities to provide the best medical treatment to the injured.

The authorities said they were still trying to identify the victims.

Some 10 fire brigade units extinguished the fire after a struggle of several hours. Rescue officials and army helicopters shifted the injured to the hospitals. The condition of most of the injured is stated to be critical.

Liquat Pur Hospital Medical Superintendent Nadeem Zia said most of the bodies brought to the hospital were beyond recognition. He said the dead will be identified through DNA tests.

Eyewitnesses said that they saw several people jumping off the moving train after it caught fire.

"I was travelling along with my mother, a sister and a brother when our bogie caught fire after a sudden explosion at around 6 am. Everyone was crying and looking for saving one's life. I asked my family members to jump off the train before the fire reached us. My brother and I managed to jump off the train, but my mother and sister couldn't," injured Iftikhar Ahmed told reporters at Liaqatpur Hospital.

According to a railways official, the train stopped some two kilometers after it caught the fire.

Prime Minister Khan has ordered an inquiry into the tragedy.

The Railway Minister has admitted his administration's failure for not checking the cylinders the passengers brought with them.

"It was our fault. And we will investigate it," he said and announed Rs 1.5 million compensation for each of the deceased and Rs 500,000 for injured.

Comments

Add new comment

  • Coastaldigest.com reserves the right to delete or block any comments.
  • Coastaldigset.com is not responsible for its readers’ comments.
  • Comments that are abusive, incendiary or irrelevant are strictly prohibited.
  • Please use a genuine email ID and provide your name to avoid reject.
News Network
December 6,2025

pilot.jpg

New Delhi: IndiGo, India’s largest airline, faced major operational turbulence this week after failing to prepare for new pilot-fatigue regulations issued by the Directorate General of Civil Aviation (DGCA). The stricter rules—designed to improve flight safety—took effect in phases through 2024, with the latest implementation on November 1. IndiGo has acknowledged that inadequate roster planning led to widespread cancellations and delays.

Below are the key DGCA rules that affected IndiGo’s operations:

1. Longer Mandatory Weekly Rest

Weekly rest for pilots has been increased from 36 hours to 48 hours.

The government says the extended break is essential to curb cumulative fatigue. This rule remains in force despite the current crisis.

2. Cap on Night Landings

Pilots can now perform only two night landings per week—a steep reduction from the earlier limit of six.

Night hours, defined as midnight to early morning, are considered the least alert period for pilots.

Given the disruptions, this rule has been temporarily relaxed for IndiGo until February 10.

3. Reduced Maximum Night Flight Duty

Flight duty that stretches into the night is now capped at 10 hours.

This measure has also been kept on hold for IndiGo until February 10 to stabilize operations.

4. Weekly Rest Cannot Be Replaced With Personal Leave

Airlines can no longer count a pilot’s personal leave as part of the mandatory 48-hour rest.

Pilots say this closes a loophole that previously reduced actual rest time.

Currently, all airlines are exempt from this rule to normalise travel.

5. Mandatory Fatigue Monitoring

Airlines must submit quarterly fatigue reports along with corrective actions to DGCA.

This system aims to create a transparent fatigue-tracking framework across the industry.

The DGCA has stressed that these rules were crafted to strengthen flight safety and align India with global fatigue-management standards. The temporary relaxations are expected to remain until February 2025, giving IndiGo time to stabilise its schedules and restore normal air travel.

Comments

Add new comment

  • Coastaldigest.com reserves the right to delete or block any comments.
  • Coastaldigset.com is not responsible for its readers’ comments.
  • Comments that are abusive, incendiary or irrelevant are strictly prohibited.
  • Please use a genuine email ID and provide your name to avoid reject.
News Network
December 7,2025

SHRIMP.jpg

Mangaluru, Dec 7: A rare bamboo shrimp has been rediscovered on mainland India more than 70 years after it was last reported, confirming for the first time the presence of Atyopsis spinipes in the country. The find was made by researchers from the Centre for Climate Change Studies at Sathyabama Institute of Science and Technology, Chennai, during surveys in Karnataka and Odisha.

The team — shrimp expert Dr S Prakash, PhD scholar K Kunjulakshmi, and Mangaluru-based researcher Maclean Antony Santos — combined field surveys, ecological assessments and DNA analysis to identify the elusive species. Their findings, published in Zootaxa, resolve decades of taxonomic confusion stemming from a 1951 report that misidentified the species as Atyopsis moluccensis without strong evidence.

The shrimp has now been confirmed at two locations: the Mulki–Pavanje estuary near Mangaluru and the Kuakhai River in Bhubaneswar. Historical specimens from the Andaman Islands, previously labelled as A. moluccensis, were also found to be misidentified and actually belong to A. spinipes.

The rediscovery began after an aquarium hobbyist in Odisha spotted a shrimp in 2022, prompting systematic surveys across Udupi, Karwar and Mangaluru. Four female specimens were collected in Mulki and one in Odisha, all genetically matching.

Researchers warn the species may exist in very small, vulnerable populations as freshwater habitats face increasing pressure from pollution, sand mining and infrastructure development. All verified specimens have been deposited with the Zoological Survey of India for future reference.

Comments

Add new comment

  • Coastaldigest.com reserves the right to delete or block any comments.
  • Coastaldigset.com is not responsible for its readers’ comments.
  • Comments that are abusive, incendiary or irrelevant are strictly prohibited.
  • Please use a genuine email ID and provide your name to avoid reject.
News Network
December 2,2025

DKSsiddu.jpg

Bengaluru: 'Nati koli saaru' (country chicken curry) considered one of Chief Minister Siddaramaiah’s favourites along with steaming hot idlis was on the breakfast menu at Deputy CM D K Shivakumar’s residence on Tuesday, according to official sources.

The spread also included 'nati koli' fry, vada and pongal, among other items, they said.

In an apparent show of unity, Siddaramaiah visited Shivakumar’s residence for breakfast, just days after the two leaders shared a meal amid a simmering power tussle in the state Congress.

Siddaramaiah drove to the Deputy CM’s residence in Sadashivanagar, where he was received by Shivakumar and his brother D K Suresh, who is a former Congress MP.

Suresh and Kunigal MLA H D Ranganath, a relative of Shivakumar, joined them for breakfast, which featured a mix of vegetarian and non-vegetarian dishes.

Speaking to reporters later, Siddaramaiah said Shivakumar had invited him during his visit to the CM’s residence for breakfast on Saturday.

Asked about the difference between the two meals, the chief minister said, "At his (Shivakumar’s) house it was non-veg, while at my house it was veg. He is a vegetarian, I am a non-vegetarian. I had not prepared non-veg. I told DK to get chicken from the village as you won’t get the original in Bengaluru."

Shivakumar said he had initially invited Siddaramaiah to his residence, but the CM had suggested visiting his place first and reciprocating later. "It was a vegetarian breakfast at the CM’s house on Saturday," he noted.

"Today, I invited him (the CM) to my house. He enjoyed the breakfast, which had his Mysuru taste," Shivakumar added. At this point, Siddaramaiah remarked that Shivakumar’s wife is also from Mysuru.

Saturday’s breakfast at Siddaramaiah’s official residence, held as part of efforts by the Congress high command to ease tensions in the leadership dispute between the two, reportedly included idlis and sambar, according to official sources.

Comments

Add new comment

  • Coastaldigest.com reserves the right to delete or block any comments.
  • Coastaldigset.com is not responsible for its readers’ comments.
  • Comments that are abusive, incendiary or irrelevant are strictly prohibited.
  • Please use a genuine email ID and provide your name to avoid reject.