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 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.
News Network
December 4,2025

indigoflight.jpg

Domestic carrier IndiGo has cancelled over 180 flights from three major airports — Mumbai, Delhi and Bengaluru — on Thursday, December 4, as the airline struggles to secure the required crew to operate its flights in the wake of new flight-duty and rest-period norms for pilots.

While the number of cancellations at Mumbai airport stands at 86 (41 arrivals and 45 departures) for the day, at Bengaluru, 73 flights have been cancelled, including 41 arrivals, according to a PTI report that quoted sources.

"IndiGo cancelled over 180 flights on Thursday at three airports-Mumbai, Delhi and Bengaluru," the source told the news agency.

Besides, it had cancelled as many as 33 flights at Delhi airport for Thursday, the source said, adding, "The number of cancellations is expected to be higher by the end of the day."

The Gurugram-based airline's On-Time Performance (OTP) nosedived to 19.7 per cent at six key airports — Delhi, Mumbai, Chennai, Kolkata, Bengaluru and Hyderabad — on December 3, as it struggled to get the required crew to operate its services, down from almost half of December 2, when it was 35 per cent.

"IndiGo has been facing acute crew shortage since the implementation of the second phase of the FDTL (Flight Duty Time Limitations) norms, leading to cancellations and huge delays in its operations across the airports," a source had told PTI on Wednesday.

Chaos continued at several major airports for the third day on Thursday because of the cancellations.

A spokesperson for the Kempegowda International Airport (KIA) in Bengaluru said that 73 IndiGo flights had been cancelled on Thursday.

At least 150 flights were cancelled and dozens of others delayed on Wednesday, airport sources said, leaving thousands of travellers stranded, according to news agency Reuters.

The Directorate General of Civil Aviation (DGCA) has said it is investigating IndiGo flight disruptions and has asked the airline to submit the reasons for the current situation, as well as its plans to reduce flight cancellations and delays.

It may be mentioned here that the pilots' body, Federation of Indian Pilots (FIP), has alleged that IndiGo, despite getting a two-year preparatory window before the full implementation of new flight duty and rest period norms for cockpit crew, "inexplicably" adopted a "hiring freeze".

The FIP said it has urged the safety regulator, the DGCA, not to approve airlines' seasonal flight schedules unless they have adequate staff to operate their services "safely and reliably" in accordance with the New Flight Duty Time Limitations (FDTL) norms.

In a letter to the DGCA late on Wednesday, the FIP urged the DGCA to consider re-evaluating and reallocating slots to other airlines, which have the capacity to operate them without disruption during the peak holiday and fog season if IndiGo continues to "fail in delivering on its commitments to passengers due to its own avoidable staffing 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.
News Network
November 21,2025

Tejas.jpg

An Indian Air Force (IAF) Tejas fighter jet crashed on Friday, November 21, afternoon during its aerial demonstration at the Dubai Air Show, plunging to the ground at around 2:10 pm local time while performing a manoeuvre before thousands of spectators.

The IAF confirmed the incident, stating that a Tejas aircraft participating in the show had crashed and that further details were being gathered. An Air Force spokesperson said more information would be shared after initial assessments.

The crash sent thick black smoke billowing into the sky near the airport, causing panic among visitors, including families and children who had gathered to watch the display. Authorities have not yet confirmed whether the pilot managed to eject before the aircraft went down. Emergency response teams rushed to the scene, and officials have not released information on casualties or damage so far.

The Tejas is a 4.5-generation, multi-role fighter aircraft developed indigenously by Hindustan Aeronautics Limited (HAL). Designed for versatility, it is capable of offensive air support, close combat, ground attack missions and maritime operations. The aircraft family includes single-seat fighters and twin-seat trainers for both the Air Force and Navy.

HAL describes the latest version, the LCA Mk1A, as the most advanced in the series, featuring an AESA radar, an upgraded electronic warfare suite with radar-warning and self-protection jamming, smart multifunction displays, a digital map generator, a combined interrogator–transponder system and a modern radio altimeter. These enhancements significantly improve the aircraft’s combat capability and survivability.

Further updates from IAF and UAE authorities are awaited.

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.