Raghavan critical of Zakia Jafri's charges

May 14, 2012

Raghavan-Zakia

Ahmedabad, May 14: Chairman of the Supreme Court-appointed Special Investigation Team R.K. Raghavan, was highly critical of the petition filed in the Supreme Court by Zakia Jafri levelling sweeping charges against Gujarat Chief Minister Narendra Modi and 62 officials and leaders for their alleged involvement in the 2002 communal riots.

Agreeing with his inquiry officer, A. K. Malhotra, who found most of the allegations baseless and unsubstantiated and gave a clean chit to Mr. Modi and most of his senior police officers in handling the riots, Mr. Raghavan said Ms. Jafri's charges made Mr. Malhotra's task difficult, as the witnesses were not prepared to speak out before the SIT.

Pointing out that Mr. Malhotra had to handle the arduous task almost single-handedly because “associating any Gujarat police officer in such a sensitive inquiry would not have been desirable,” Mr. Raghavan said another factor that caused hurdles for the inquiry officer was the “reluctance of many crucial witnesses to depose frankly and without inhibition, because the complainants had ‘mindlessly and mechanically' referred to these witnesses as ‘accused,' a branding that caused a great offence to many of the witnesses.”

Mr. Raghavan lauded Mr. Malhotra for his “outstanding work,” completing the task of inquiring into 32 allegations levelled by Ms. Jafri against Mr. Modi and 62 others within a year, examining more than 160 witnesses and checking on a large number of documents. For reasons of confidentiality, even the secretarial assistance to him was “modest:” only one person did the “scriptory work.” Besides, most of the witnesses were “non-co-operative” and intentionally delayed appearing before him. The lapse of eight years before the investigation started also caused witnesses problems in recalling the facts correctly, he said.

Mr. Raghavan, a former CBI director, submitted his comments on the findings of the inquiry in the Supreme Court on May 14, 2010, and these have formed part of the closure report the SIT submitted in an Ahmedabad metropolitan court. A copy was given to Ms. Jafri, wife of the slain former Congress MP, Ehsan Jafri, who was among the 69 killed in the Gulberg Society massacre.

Mr. Raghavan agreed with Mr. Malhotra's conclusion that the allegation that Mr. Modi issued a “directive” to police officers to “allow Hindus to vent their anger” had “not been established,” as none of the officers “definitely present” at the crucial meeting held at his residence on the night of February 27, 2002, corroborated the claim made by suspended IPS officer Sanjiv Bhatt. Mr. Bhatt was an “unreliable witness.” There was no proof that the then Minister of State for Revenue, Haren Pandya, was present at the meeting, as he had claimed before the Citizens' Tribunal.

He also agreed with the finding that the decision to bring the bodies of the victims of the Godhra train carnage to Ahmedabad was taken unanimously by all police and administrative officers and the Ministers present in Godhra that day. The then Panchamahals Collector, Jayanti Ravi, also agreed to it.

He disagreed with the complainant that it was Mr. Modi's personal decision meant to inflame the situation by “parading the bodies,” pointing out that the bodies were brought in the dead of night and disposed of in the quickest possible time the next day.

And there was nothing to substantiate the charge that two senior Ministers were “instructed” by the Chief Minister to take charge of the State and city police control rooms on February 28, 2002, when ‘Gujarat Bandh' was observed. It was “conclusively established” that the late Ashok Bhatt, who was Health Minister, and I. K. Jadeja, the then Urban Development Minister, did visit the police control rooms, but there was no evidence that they ever “interfered” with the functioning of the police, or that they were told by Mr. Modi to sit in the control rooms. But as Mr. Modi himself held the Home portfolio, it did “heighten the suspicion that the decision had his blessings.”

Mr. Raghavan disagreed that there was undue delay in summoning and deploying the Army in the riot-hit areas, or Mr. Modi deliberately “ignored” Ehsan Jafri's plea for help when the riotous mob surrounded the Gulberg Society. No records were available to corroborate the allegations, he said, agreeing with the finding that the mobile call records did not show Mr. Modi having received any call from Ehsan Jafri or anyone else in the Gulberg Society, and accepting the Chief Minister's statement that he had never known Ehsan Jafri before the incident.

Mr. Raghavan did not agree that Mr. Modi was issuing “illegal instructions” orally, as alleged by the former Additional Director-General of Police, R. B. Sreekumar, in affidavits filed before the G.T. Nanavati-Akshay Mehta Judicial Inquiry Commission. Mr. Sreekumar's personal diary in which he made entries about such “illegal oral instructions” was an “unofficial document” he was not authorised to maintain, and had no “evidentiary value whatsoever.” Besides, some of the entries in the diary were found factually incorrect. It was significant that Mr. Sreekumar revealed the existence of such a diary three years after he had opened it and only after he was superseded in promotion; he produced only a copy of the diary before the SIT.

But Mr. Raghavan said the transfer of a few police officers amid the raging riots, especially those who were claimed to have done a good job in controlling the violence, were surprising, but none of the police officers was prepared to admit that they were victimised. The Chief Minister himself admitted that he did not visit the riot-hit areas so promptly as he visited Godhra on the day of the train carnage and could not cite any specific reason for the delay. Mr. Modi had not been able to totally deny his alleged statement that private firing by Ehsan Jafri had “provoked” the Gulberg Society massacre, or his reported theory of “action-reaction” to justify the riots, but Mr. Raghavan emphasised that the undertone of all his statements was an “earnest appeal” to the people for peace. He agreed that Mr. Modi failed to give any directive to Hindu organisations against the observance of the bandh in view of the charged atmosphere.

He found that the appointment of some of the special public prosecutors for the trial of the riot-related cases was politically motivated, but said a “transparent procedure” was in place for the appointment, and it was followed by the government.

Mr. Raghavan questioned Mr. Sreekumar's “intentions” in alleging that he was “tutored” by some officials of the Chief Minister's office to give guarded statements on the riots before various probe agencies to protect Mr. Modi and his government. Mr. Sreekumar levelled the allegations not while filling the affidavits before the Nanavati-Mehta Commission, but only when he was superseded, and his junior was promoted as DGP in 2005.

Mr. Raghavan termed “incorrect and motivated” Citizens for Justice and Peace general secretary Teesta Setalvad's charge that Hindu activists conducted two meetings at Lunawada and Borwai, near Godhra, on Fabruary 27 and 28 to hatch plans for a pogrom against minorities, and that the meetings were attended by two members of Mr. Modi's Cabinet. After a thorough probe, the SIT found that the charge was “incorrect and motivated;” there was no evidence for any such meeting having taken place at all, and there was no question of any Minister having attended it.

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.