Wireless messages dent SIT claim on Modi

April 18, 2013
New Delhi, Apr18: In its closure report submitted to the trial court, the Special Investigation Team that probed Zakia Jafri’s complaint against Narendra Modi and 58 others said there was no evidence to prove that the Chief Minister had sent the bodies of the 2002 Godhra victims to Ahmedabad with a view to parading them before the public.

modi1
The SIT quoted Ahmedabad Police Commissioner P.C. Pande to back its claim that there was no parading of the bodies.

Not just this. Anyone reading the report would conclude that peace had prevailed through the time the bodies were transported from Godhra to the Sola Civil Hospital on the outskirts of Ahmedabad, and later too, when the bodies were handed over to the next of kin. There is no mention in the closure report of the charged atmosphere in the hospital prior to the arrival of the bodies in the early hours of February 28, 2002. Nor does the report indicate anywhere that huge, violent crowds accompanied the funeral processions of the victims; indeed that the processions became the trigger for the anti-Muslim violence that rocked the city and State in the Godhra aftermath.

The real story emerges in a series of desperate wireless messages sent out by police and intelligence field staff positioned at the Sola Civil Hospital and other locations on February 27 and 28, 2002. The wireless extracts, annexed to a protest petition filed against the SIT’s closure report by Ms. Jafri in a local court, show the following. One, there was a lot of anxiety over the Modi administration’s decision to send the bodies to Ahmedabad. Two, there were repeated pleas for bandobast at the hospital where crowds had gathered in anticipation of the arrival of the bodies. Three, there were attacks on Muslims by crowds accompanying the funeral processions which set the stage for the large-scale violence that followed.

At 12.30 p.m. on February 27, that is just hours after the Godhra train carnage, a State Intelligence Bureau (SIB) officer sent a fax communication to his headquarters saying there were reports that bodies of the kar sevaks were going to be sent to Ahmedabad. He alerted: “So communal violence will occur in the city of Ahmedabad; so take preventive action.”

The warning was repeated in another message which added that kar sevaks were threatening retaliatory violence in explosive interviews given to a TV station in Godhra. In the early hours of February 28, there were two messages (1.51 a.m. and 1.59 a.m.) from a police van stationed at the Sola Civil Hospital, urging “immediate protection from Special Reserve Police platoons and the presence of DCP Zone 1.”

At 2.44 a.m., a message said the motorcade carrying the bodies had reached the hospital. Another message at 4 a.m. said a mob comprising 3,000 swayamsevaks (Rashtriya Swayamsevak Sangh volunteers) had gathered at the hospital. At 7.14 a.m., the police van again relayed the message that a large mob had assembled at the hospital. Three minutes later, a message said a mob of 500 was holding up the traffic.

At 11.55 a.m., there was a message saying “the hindu mob” had become violent and had set a vehicle on fire and was “indulging in arson on the highway.” Another message at the same time said, “Sayyed Saheb, the Protocol Officer” had informed that riots had started in the hospital. A further message said mobs had surrounded the hospital staff.

There were specific messages from the field about crowds of 5,000-6,000 taking the bodies out in funeral processions. A message at 11. 58 a.m. said: “Amrajwadi-1 informed that 10 dead bodies have been taken for cremation ceremony from Ramol Janatanagar to Hatkeshwar Cremation Centre with crowd of 5 to 6 thousand.” Another message said: “Funeral procession allowed at Khedbrahma town in Sabarkantha district. Situation tense, 2 Muslims stabbed at Khedbrahma.”

There was also a message about 150 Bajrang Dal members from Ayodhya reaching Khedbrahma.

The SIT’s closure report acknowledged that the bodies of kar sevaks had been handed over to the VHP’s Jaydeep Patel but it placed the blame for the decision on M.L. Nalvaya, the local executive magistrate, and said he had issued a letter to Mr. Patel where he mentioned that 54 bodies were being sent with him on five trucks.

The SIT said the five trucks carrying the bodies reached the Sola Civil Hospital between 3.30 a.m. and 4 a.m. on February 28, and that Mr. Patel handed over the letter from the executive magistrate to the Deputy Collector who was waiting at the hospital with the Collector and other officials.

The SIT blandly recorded that “the relatives of the persons who had died at the Godhra carnage were also present in the hospital. Accordingly, 35 persons were identified and their bodies handed over to their relatives …”

The SIT denied that there had been any parading of bodies, and quoted Mr. Pande to back its claim: “Shri P.C. Pande, the then CP, Ahmedabad city has stated that there had been no parading of dead bodies inasmuch as the trucks carrying the dead bodies under police escort reached Ahmedabad city between 0330 hrs to 0400 hrs on 28.02.2002 which means they had started from Godhra at least three hrs earlier and as such there was no one to see them on the highway at dead of night. Shri Pande has also stated that in Ahmedabad city, the dead bodies were kept in Sola Civil Hospital situated on the outskirts of the city and that most of the dead bodies were handed over to their relations after proper documentation by 28.02.2008 morning.”

As for the funeral processions, the SIT said: “… the dead bodies were moved in vehicles and not by foot as the same would have escalated the tension … R.J. Savani (Deputy Commissioner of Police, Zone V) succeeded in persuading the relatives and well-wishers of the deceased to take each body in a vehicle and the funeral procession was guarded by the police up to Hatkeshwar cremation ground … The funeral was over by 1400hrs and the crowd which had gathered on the highway dispersed thereafter.”

No mention of the unrest in the hospital. No mention of arson by protestors. And no mention of the huge crowds that accompanied the funeral processions.

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

indigocrisis.jpg

Angry outbursts, long queues, and desperate appeals filled airports across India today as IndiGo grappled with a severe operational breakdown. Hundreds of flights have been cancelled or delayed, leaving thousands of passengers stranded through the night and forcing many to spend long hours at helpdesks.

Social media was flooded with videos of fliers pleading for assistance, accusing the airline of misleading updates, and demanding accommodation after being stuck for 10 to 12 hours at airports such as Hyderabad and Bengaluru.

What Triggered the Meltdown?

IndiGo has attributed the widespread disruption to “a multitude of unforeseen operational challenges.” These include:

•    Minor technology glitches
•    Winter-season schedule adjustments
•    Bad weather
•    Congestion in the aviation network
•    New crew rostering rules (Flight Duty Time Limitations or FDTL)

Among these, the most disruptive has been the implementation of the updated FDTL norms introduced by the Directorate General of Civil Aviation (DGCA) in January 2024.

These rules were designed to reduce pilot fatigue and improve passenger safety. Key changes include:

•    Longer weekly rest periods for flight crew
•    A revised definition of “night,” extending it by an extra hour
•    Tighter caps on flight duty timing and night landings
•    Cutting night shifts for pilots and crew from six per roster cycle to just two

Once these norms became fully enforceable, airlines were required to overhaul rosters well in advance. For IndiGo, this triggered a sudden shortage of crew available for duty, leading to cascading delays and cancellations.

Why IndiGo Was Hit the Hardest

IndiGo is India’s largest airline by a wide margin, operating over 2,200 flights daily. That’s roughly double the number operated by Air India.

When an airline of this size experiences even a 10–20% disruption, it translates to 200–400 flights being delayed or grounded — producing massive spillover effects across the country.

IndiGo also relies heavily on high-frequency overnight operations, a model typical of low-cost carriers that aim to maximise aircraft utilisation and reduce downtime. The stricter FDTL norms clash with these overnight-heavy schedules, forcing the airline to pull back services.

Aviation bodies have also criticised IndiGo’s preparedness. The Airline Pilots' Association of India (ALPA) said airlines were given a two-year window to plan for the new rules but “started preparing rather late.” IndiGo, it said, failed to rebuild crew rosters 15 days in advance as required.

The Federation of Indian Pilots (FIP) went further, calling the crisis the result of IndiGo’s “prolonged and unorthodox lean manpower strategy,” and alleging that the airline adopted a hiring freeze even as it knew the new rules would require more careful staffing.

How Many Flights Are Affected?

In the past 48 hours, over 300 flights have been cancelled. At least 100 more are expected to be cancelled today.

City-wise impact:

•    Hyderabad: 33 expected cancellations; several fliers stranded overnight
•    Bengaluru: over 70 expected cancellations
•    Delhi, Mumbai, Chennai, Kolkata: widespread delays and missed connections

Passengers shared distressing accounts online.

One customer at Hyderabad airport said they waited from 6 PM to 9 AM with “no action taken” regarding their delayed Pune flight. Another said IndiGo repeatedly told them the crew was “arriving soon,” only for the delay to stretch over 12 hours.

IndiGo has apologised for the disruption and promised that operations will stabilise within 48 hours, adding that “calibrated adjustments” are being made to contain the chaos.

What Should Passengers Do Now?

For those flying in the next few days, especially with IndiGo, here are key precautions:

1. Keep Checking Flight Status
Monitor your flight closely before leaving for the airport, as delays may be announced last-minute.

2. Arrive Early
Expect long queues at counters and security due to crowding and rescheduling.

3. Carry Essentials
Pack snacks, water, basic medicines, chargers, and items for children or senior citizens. Extended waiting times should be anticipated.

4. Use Flexible Booking Options
If you booked tickets with a free-date-change or cancellation option, consider using them.
If you haven’t booked yet, prefer refundable or flexible fares, or even consider alternate airlines.

5. Follow IndiGo’s Updates
Keep an eye on IndiGo’s official social media channels and contact customer support for rebooking and refund queries.

What Needs to Change?

Pilot groups have raised concerns not just about staffing but also the planning practices behind it.
The Federation of Indian Pilots accused IndiGo of:

•    Imposing an unexplained hiring freeze despite knowing the FDTL changes were coming
•    Entering non-poaching agreements that limited talent movement
•    Keeping pilot pay frozen
•    Underestimating the need to restructure operations in advance

They have urged DGCA to approve seasonal schedules only after airlines prove they have adequate pilot strength under the new norms.

ALPA also warned that some airlines might be using the delays as an “immature pressure tactic” to push DGCA for relaxations in the new rules — which, if granted, could compromise the very safety standards the norms were meant to protect.

Both pilot bodies stressed that no exemption should dilute safety, and any deviations should be based solely on scientific risk assessment.

Is a Solution in Sight?

While IndiGo says normalcy will return within two days, aviation experts believe that fully stabilising operations could take longer, depending on how quickly the airline can:
•    Re-align rosters
•    Mobilise rested crew
•    Boost staffing
•    Adjust its winter schedule to match regulatory requirements
Passengers are advised to remain prepared for continued delays over the next few days as the airline works through its backlog. 

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

indigoCEO.jpg

New Delhi, Dec 5: IndiGo CEO Pieter Elbers issued a public apology this evening after more than a thousand flights were cancelled today, making it the "most severely impacted day" in terms of cancellations. The biggest airline of the country cancelled "more than half" of its daily number of flights on Friday, said Elbers. He also said that even though the crisis will persist on Saturday, the airline anticipates fewer than 1,000 flight cancellations.

"Full normalisation is expected between December 10 and 15, though IndiGo cautions that recovery will take time due to the scale of operations," the IndiGo CEO said. 

IndiGo operates around 2,300 domestic and international flights daily.

Pieter Elbers, while apologising for the major inconvenience due to delays and cancellations, said the situation is a result of various causes.

The crisis at IndiGo stems from new regulations that boost pilots' weekly rest requirements by 12 hours to 48 and allow only two night-time landings per week, down from six. IndiGo has attributed the mass cancellations to "misjudgment and planning gaps".

Elbers also listed three lines of action that the airline will adopt to address the issue.

"Firstly, customer communication and addressing your needs, for this, messages have been sent on social media. And just now, a more detailed communication with information, refunds, cancellations and other customer support measures was sent," he said.

The airline has also stepped up its call centre capacity.

"Secondly, due to yesterday's situation, we had customers stranded mostly at the nation's largest airports. Our focus was for all of them to be able to travel today itself, which will be achieved. For this, we also ask customers whose flights are cancelled not to come to the airports as notifications are sent," the CEO said.

"Thirdly, cancellations were made for today to align our crew and planes to be where they need to start tomorrow morning afresh. Earlier measures of the last few days, regrettable, have proven not to be enough, but we have decided today to reboot all our systems and schedules, resulting in the highest numbers of cancellations so far, but imperative for progressive improvements starting from tomorrow," he added.

As airports witnessed chaotic scenes, the Directorate General of Civil Aviation (DGCA) stepped in to grant IndiGo a temporary exemption from stricter night duty rules for pilots. It also allowed substitution of leaves with a weekly rest period. 

Civil Aviation Minister Ram Mohan Naidu has said a high-level inquiry will be ordered and accountability will be fixed.

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

indigo.jpg

IndiGo, India’s largest airline, is battling one of its worst operational disruptions in recent years, with hundreds of delays and cancellations throwing domestic travel into chaos.

Government data on Tuesday showed its on-time performance plunging to 35%, an unusual dip for a carrier long associated with punctuality.

By Wednesday afternoon, airports in Delhi, Mumbai, Bengaluru and Hyderabad had collectively reported close to 200 cancellations, stranding travellers across the country.

Crew Shortage After New Duty Norms

A major trigger behind the meltdown is a severe crew shortage, especially among pilots, following the rollout of revised Flight Duty Time Limitation (FDTL) norms last month.

The rules mandate longer rest hours and more humane rosters — a shift IndiGo has struggled to incorporate across its vast network.

Sources said several flights were grounded due to lack of cabin crew, while some delays stretched upwards of eight hours.

With IndiGo controlling over 60% of India’s domestic aviation market, the ripple effect has impacted airports nationwide.

IndiGo Issues Apology, Lists “Compounding Factors”

In a statement, IndiGo acknowledged the large-scale disruption:

“We sincerely apologise to customers. A series of unforeseen operational challenges — technology glitches, winter schedule changes, adverse weather, system congestion and updated FDTL norms — created a compounding impact that could not have been anticipated.”

To stabilise operations, the airline has begun calibrated schedule adjustments for the next 48 hours, aiming to restore punctuality. Affected passengers are being offered refunds or alternate travel arrangements, IndiGo said.

What the FDTL Rules Require

The FDTL norms, designed to reduce pilot fatigue, cap duty and flying hours as follows:
•    Maximum 8 hours of flying per day
•    35 hours per week
•    125 hours per month
•    1,000 hours per year

Crew must also receive rest equalling twice the flight duration, with a minimum 10-hour rest period in any 24-hour window.

The DGCA introduced these limits to enhance flight safety.

Hyderabad: 33 Flights Cancelled, Long Queues Reported

Hyderabad’s Rajiv Gandhi International Airport saw heavy early-morning crowds as 33 IndiGo flights (arrivals and departures) were cancelled.

The airport clarified on X that operations were normal, advising passengers to contact IndiGo directly for latest flight status.

Cancellations included flights to and from Visakhapatnam, Goa, Ahmedabad, Delhi, Bengaluru, Chennai, Madurai, Hubli, Bhopal and Bhubaneswar.

Bengaluru: 42 Flights Disrupted

Bengaluru’s Kempegowda International Airport recorded 42 cancellations — 22 arrivals and 20 departures — affecting routes to Delhi, Mumbai, Chennai, Hyderabad, Goa, Kolkata and Lucknow.

Passengers Vent on Social Media

Irate travellers took to X to share their experiences. One passenger stranded in Hyderabad wrote: “I have been here since 3 a.m. and missed an important meeting.”

Another said: “My flight was pushed from 1:55 PM to 2:55 PM and now 4:35 PM. I was informed only three minutes before entering the airport.”

Delhi Airport Hit by Tech Glitch

At Delhi Airport, the disruption deepened due to a slowdown in the Amadeus system — used for reservations, check-ins and departure control.

The technical issue led to longer queues and sluggish processing, adding to delays already worsened by staff shortages.

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.