Udupi: Seers disappointed as PM Modi refuses to visit Krishna Mutt like CM Siddaramaiah

coastaldigest.com news network
May 2, 2018

Udupi, May 2: Bharatiya Janata Party had called chief minister an anti-Hindu for not paying a visit to Sri Krishna Temple during his recent Udupi to Udupi. Ironically, Prime Minister Narendra Modi, who visited the town on May 1 too refused to visit the temple in spite of invitation.

Vidyadheesha Tirtha Swami of Paryaya Palimar Mutt has expressed his disappointment over PM Modi not visiting the historic temple.

“I had expectations that Prime Minister might come. I had invited both Mr Modi and Mr Siddaramaiah to visit the Sri Krishna Mutt/Temple,” he said.

Meanwhile, Vishwesha Tirtha Swami of Pejawar Mutt said that he too had written to Mr. Modi, inviting him to the temple.

In a press release issued here, the district unit of the Congress questioned why Mr. Modi did not visit the temple, especially when the BJP had made a big issue of Mr. Siddaramaiah not visiting it. 

Comments

Ahmed Ali K
 - 
Thursday, 3 May 2018

Our PM is very well aware that he is a liar and his speeches are baseless and fact less.

How can he step in to Hindu sanctiry area in Udupi

Danish
 - 
Wednesday, 2 May 2018

Rahul Gandhi visited Udupi and arranged meeting with seer. even Siddu also

Ganesh
 - 
Wednesday, 2 May 2018

Hope seer wont support Pakoda PM

Kumar
 - 
Wednesday, 2 May 2018

Feku came to Udupi for blabbering not to meet important people

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.