Terror accused Indresh participates at key RSS meet in Puttur

March 13, 2011

Mangalore, March 13: The terror accused Indresh Kumar is currently participating at the Akhil Bharatiya Pratinidhi Sabha (ABPS) of RSS which is going on at Puttur near here.

While addressing the media persons, All India Executive Member of RSS Ram Madhav spilled the beans that Indresh Kumar, who is accused of Mecca-Malegaon bomb blasts, is attending the ABPS.

This was revealed when media persons asked whether anyone who is on CBI's target list attending the ABPS. “Since Indresh Kumar is an active functionary of National Executive of the RSS, he had taken part in the ABPS” Mr Madhav said.

He also said that it was due to political conspiracy Indresh Kumar had been named in the charge-sheet and added that Indresh Kumar was surely not a terrorist.

The ABPS, which is the highest decision making body of RSS adopted a resolution expressing concern over growing multi-dimensional threat from China and lacklustre response of the Union Government to its aggressive intimidatory tactics. Casual attitude and perpetual denial by Indian government in describing gross border violations by the Chinese People's Liberation Army (PLA) as a case of 'lack of common perception on the Latin American and Caribbean (LAC) countries'.

Rubbishing the allegation that Somashekara Committee's report on church attack was one sided, Mr Madhav said in fact, the report which was prepared by a Justice of High Court of Karnataka is constitutional and MF Saldanha is falsely projecting it as unconstitutional.

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.

Flight cancellations strand passengers overnight at Mangaluru Airport

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