41 feared dead in Russian as burning plane tries emergency landing

Agencies
May 6, 2019

May 6: Forty-one people including at least two children have died after a Russian passenger plane made an emergency landing and erupted in a huge ball of fire and black smoke at Moscow's busiest airport on Sunday, investigators said.

Dramatic footage that went viral on social media showed Aeroflot's Sukhoi Superjet 100 aircraft crash-landing and then speeding along the runway at Sheremetyevo international airport, flames pouring from its fuselage.

Passengers could be seen leaping onto an inflatable slide at the front and running from the blazing plane as huge black columns of smoke billowed into the sky.

"There were 78 people including crew members on board the plane," the Investigative Committee said in a statement, adding that the plane had been flying to the northwestern Russian city of Murmansk.

"According to the updated info which the investigation has as of now, 37 people survived."

A spokeswoman for the investigators confirmed the death toll was 41.

Another 11 people were injured, Dmitry Matveyev, the Moscow region's health minister said earlier in the day.

Witness Alyona Osokina said she was inside the terminal when she suddenly saw a plane on fire rushing along the runway.

"The blaze was devouring the plane," she told Rain TV.

Osokina said that fire engines had arrived quickly but could not immediately put out the blaze.

"This horror and tragedy happened before our eyes," she said, adding that those who managed to flee the plane then walked calmly towards the airport.

"I believe they were in a state of deep shock."

The jet carrying 73 passengers and five crew members had just left Sheremetyevo when the crew issued a distress signal, officials said.

"Flight Su-1492 took off on schedule at 6:02 pm (1502 GMT)," said a statement from the airport.

"After the take-off, the crew reported an anomaly and decided to come back to the departure airport. At 6:30 pm, the aircraft made an emergency landing," it added.

Russia's flagship carrier said the plane had to return to the airport "due to a technical reason" and its engines caught fire upon landing. Previous reports had said the fire broke out in mid-air.

The jet reportedly managed to land on its second attempt, hitting the ground with its landing gear first and then its nose.

The plane's fuel tanks were full and a much bigger death toll could have been a real possibility, aviation experts said.

Investigators said they were looking into various lines of inquiry and it was premature to draw any conclusions about the cause of the accident.

Russian President Vladimir Putin had offered his condolences to the victims' loved ones, the Kremlin said.

He has also said the investigation "should be as thorough as possible," the Kremlin added.

Prime Minister Dmitry Medvedev ordered a special committee to investigate the disaster.

The Murmansk region -- where many of the casualties are believed to be from -- will go into a three-day period of mourning beginning Monday.

Some flights have been diverted to other Moscow airports or Nizhny Novgorod, some 400 kilometres (250 miles) east of the Russian capital.

Numerous Aeroflot flights are expected to be affected in the coming days.

The country's aviation's safety record has been chequered and the latest disaster is seen as a huge blow to its already struggling aviation industry.

The Sukhoi Superjet-100 was the first civilian aircraft developed in the country's post-Soviet era.

At the time of its launch, in 2011, it was a source of national pride and seen as one of Putin's pet projects.

But numerous technical problems with the plane have been reported in recent years and Russia has struggled to convince foreign carriers to purchase it.

The government offered subsidies to encourage Russian airlines to buy the Superjet and Aeroflot has became its main operator.

In September 2018, it announced a record order of 100 Superjet-100s.

After the tragedy some suggested that Russia may be better off abandoning the Sukhoi Superjet altogether.

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
November 24,2025

Mangaluru, Nov 24: The original departure time of 11.10 pm was a distant memory for scores of Dammam-bound passengers at Mangaluru International Airport last Friday night, as their Air India Express flight was abruptly cancelled at the eleventh hour, sparking hours of frustration and chaos.

The flight, IX 885, initially scheduled to depart at 11.10 pm on November 22, was subject to two back-to-back reschedules—first pushed to 11.45 pm and then significantly postponed to 1.40 am—before the final, crushing announcement of cancellation was made. For the travellers, many of whom are likely expatriate workers with tight schedules, the last-minute change marked the beginning of a distressing ordeal.

"There was no drinking water, no food, and absolutely no proper guidance. We were left stranded like refugees," complained a stranded passenger.

According to multiple passenger accounts, the airline's ground staff failed to provide adequate support or essential amenities following the cancellation. Complaints poured in about the total absence of drinking water, food provisions, and any reliable guidance from the carrier's representatives. Travellers alleged they were left stranded for a considerable period, with no immediate arrangements or clear communication offered regarding accommodation or alternative travel to send them back home.

The incident has highlighted serious concerns over the carrier's contingency planning and customer service protocols during flight disruptions at one of India's key international gateways. The airline is yet to issue a comprehensive statement addressing the alleged lapse in passenger care.
 

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 1,2025

hindutvaboy.jpg

Udupi, Dec 1: A horrific case of alleged rape has unfolded in Udupi, where a worker from a Hindutva organisation, previously arrested and released on bail for harassing a young woman, is now accused of waylaying and sexually assaulting her.

The arrested individual has been identified as Pradeep Poojary (26), a member of the Hindu Jagarana Vedike's Nairkode unit in Perdur.

Poojary had allegedly been relentlessly harassing the young woman, pressuring her to marry him. When she bravely stood up to him and refused his demands, she filed a formal complaint at the Hiriyadka police station. He was subsequently arrested in that initial harassment case but was later granted bail.

According to police reports, driven by the same malicious grudge, Poojary allegedly intercepted the woman again on November 29. While she was walking through a deserted area, the accused is claimed to have threatened her by grabbing her neck. When she again refused to marry him, he allegedly proceeded to rape her.

The survivor immediately informed her family about the traumatic assault. Following this, her parents lodged a complaint at the Udupi women’s police station.

Police arrested Poojary again and produced him before the court. He has since been remanded to judicial custody.

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.