A cup that brought DEATH: RCB victory parade turns into chaos in Bengaluru; 11 dead

News Network
June 4, 2025

stampede1.jpg

Bengaluru, June 4: The Royal Challengers Bengaluru’s (RCB) maiden victory celebration turned tragic on Wednesday when a stampede outside the M Chinnaswamy Stadium left at least 11 dead and 47 injured, according to officials and eyewitness accounts. 

The stampede — Bengaluru’s first in decades — broke out between 4 pm and 5:30 pm at the stadium’s three entry gates (17, 18 and 21), as thousands pushed their way to witness the invite-only historic event. 

Most of the deceased were young men and women, with the youngest being a 13-year-old girl. Many victims are believed to have died from suffocation after being trampled. 

Thirty-three injured victims are still in hospital. At least one is critical. 

Reliable sources said that RCB, the Karnataka State Cricket Association (KSCA) and the state government ignored police advice to postpone the celebrations. 

“We tried to discourage them but there was a mad frenzy. The celebrations had continued into the early hours, and our personnel were exhausted. Though we managed to cancel the victory procession, our request to either confine the celebrations to a single venue or postpone it to Sunday — when emotions would have settled — was ignored,” said a senior police officer. “We simply had no time to prepare. It was a case of ‘damned if you do, damned if you don’t’.” 

There were heart-wrenching scenes at hospitals. “Yelu, chinna? Appa banddidare, baa maga (Wake up, son. Father has come),” cried the mother of 20-year-old Bhumik. 

His father, Lakshman, was equally inconsolable. “God gave me everything. Now what am I supposed to do without my son? How can I go back home,” he said. 

A traffic policeman deployed at the stadium flagged the “poor coordination” among the police, the fire force and the KSCA. At the time of the stampede, a large number of police personnel were deployed near the Vidhana Soudha, where the state government was felicitating the RCB players. “We didn’t even have clarity on the event’s agenda,” he said. 

After the Vidhana Soudha event ended, large crowds travelled through Cubbon Park to reach the stadium. Despite the huge crowd — estimated at 3 lakh — there was no public address system. 

Shockingly, even after the stampede, another gate near Queen’s Road was opened, and many people streamed in. 

One eyewitness said the security was so overwhelmed that people were allowed in without their entry passes being checked. 

Many were perched on trees. Barricades were broken down and hundreds of discarded footwear lay scattered outside the entry gates. 

A DH journalist at the stadium saw ambulances streaming in and out, their sirens drowned by cries of cheering fans. Many victims had to be taken out in autos. Some ambulances carrying the victims got stuck in the crowd-packed roads around the stadium. 

“I shifted two people barely breathing into an auto,” the officer said. “There was no mercy. Everyone just wanted to get in, no matter what. Everyone was busy making videos.” 

Namma Metro shut five stations and reopened them only when crowds cleared out. 
Deputy Chief Minister D K Shivakumar defended the police, saying they did their best. “You saw the crowd. We can’t hit them with sticks.” 

The RCB issued a statement, saying it was “deeply anguished by the unfortunate incidents” and “mourns the tragic loss of lives”. 

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

Udupi: A 40-year-old NRI from Udupi has reportedly lost more than Rs 12.25 lakh in an online investment scam operated through Telegram.

According to a complaint filed at the CEN police station, Leo Jerome Mendonsa, who has been working in Dubai for the past 15 years in computer accessories sales, maintains NRI accounts in Karkala and Nitte.

On November 12, 2025, Mendonsa was added to a Telegram group called Instaflow Earnings by unknown individuals. Users identified as Priya and Dipannita persuaded him to invest in “Revenue Tasks.” Initially, Mendonsa transferred Rs 1,100 multiple times and received the promised returns, encouraging him to continue.

On November 14, another user, Nishmitha Shetty, directed him to register on a website, digitvisionuoce.cc, and invest Rs 4 lakh in various shares. Over the next few days, he made multiple transfers totaling Rs 12,25,000, including Rs 50,000 via Google Pay, believing the scheme was legitimate.

After receiving the money, the alleged handlers stopped responding, and neither the invested amount nor the promised profits were returned.

The CEN police have registered a case under Sections 66(C) and 66(D) of the IT Act and Section 318(4) of the Bharatiya Nyaya Sanhita (BNS), and investigations are ongoing.

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

Mangaluru: Chaos erupted at Mangaluru International Airport (MIA) after IndiGo flight 6E 5150, bound for Mumbai, was repeatedly delayed and ultimately cancelled, leaving around 100 passengers stranded overnight. The incident highlights the ongoing country-wide operational disruptions affecting the airline, largely due to the implementation of new Flight Duty Time Limitations (FDTL) norms for crew.

The flight was initially scheduled for 9:25 PM on Tuesday but was first postponed to 11:40 PM, then midnight, before being cancelled around 3:00 AM. Passengers expressed frustration over last-minute communication and the lack of clarity, with elderly and ailing travellers particularly affected. “Though the airline arranged food, there was no proper communication, leaving us confused,” said one family member.

An IndiGo executive at MIA cited the FDTL rules, designed to prevent pilot fatigue by limiting crew working hours, as the cause of the cancellation. While alternative arrangements, including hotel stays, were offered, about 100 passengers chose to remain at the airport, creating tension. A replacement flight was arranged but also faced delays due to the same constraints, finally departing for Mumbai around 1:45 PM on Wednesday. Passengers either flew, requested refunds, or postponed their travel.

The Mangaluru delay is part of a broader crisis for IndiGo. The airline has been forced to make “calibrated schedule adjustments”—a euphemism for widespread cancellations and delays—after stricter FDTL norms came into effect on November 1.

While an IndiGo spokesperson acknowledged unavoidable flight disruptions due to technology issues, operational requirements, and the updated crew rostering rules, the DGCA has intervened, summoning senior airline officials to explain the chaos and outline corrective measures.

The ripple effect has been felt across the country, with major hubs like Bengaluru and Mumbai reporting numerous cancellations. The Mangaluru incident underscores the systemic operational strain currently confronting India’s largest carrier, leaving passengers nationwide grappling with uncertainty and delays.

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

Mangaluru: Chaos erupted at Mangaluru International Airport (MIA) after IndiGo flight 6E 5150, bound for Mumbai, was repeatedly delayed and ultimately cancelled, leaving around 100 passengers stranded overnight. The incident highlights the ongoing country-wide operational disruptions affecting the airline, largely due to the implementation of new Flight Duty Time Limitations (FDTL) norms for crew.

The flight was initially scheduled for 9:25 PM on Tuesday but was first postponed to 11:40 PM, then midnight, before being cancelled around 3:00 AM. Passengers expressed frustration over last-minute communication and the lack of clarity, with elderly and ailing travellers particularly affected. “Though the airline arranged food, there was no proper communication, leaving us confused,” said one family member.

An IndiGo executive at MIA cited the FDTL rules, designed to prevent pilot fatigue by limiting crew working hours, as the cause of the cancellation. While alternative arrangements, including hotel stays, were offered, about 100 passengers chose to remain at the airport, creating tension. A replacement flight was arranged but also faced delays due to the same constraints, finally departing for Mumbai around 1:45 PM on Wednesday. Passengers either flew, requested refunds, or postponed their travel.

The Mangaluru delay is part of a broader crisis for IndiGo. The airline has been forced to make “calibrated schedule adjustments”—a euphemism for widespread cancellations and delays—after stricter FDTL norms came into effect on November 1.

While an IndiGo spokesperson acknowledged unavoidable flight disruptions due to technology issues, operational requirements, and the updated crew rostering rules, the DGCA has intervened, summoning senior airline officials to explain the chaos and outline corrective measures.

The ripple effect has been felt across the country, with major hubs like Bengaluru and Mumbai reporting numerous cancellations. The Mangaluru incident underscores the systemic operational strain currently confronting India’s largest carrier, leaving passengers nationwide grappling with uncertainty and delays.

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.