Your closure report a bid to shield Modi, Bhatt tells Raghavan

May 17, 2012

Bhatt_1085550f

Ahmedabad, May 17: The suspended IPS officer Sanjiv Bhatt says the closure report submitted by the Supreme Court-appointed Special Investigation Team (SIT) only confirmed his long-standing apprehension that it was only working to “shield” Chief Minister Narendra Modi and other “powerful persons” from legal punishment for their involvement in the 2002 Gujarat pogrom.

In a letter to SIT Chairman R. K. Raghavan on Wednesday, Mr. Bhatt said it was “outrageously shocking” that even after his repeated requests the SIT did not issue any timely direction to the State government for preservation and production of vital contemporaneous documents, and allowed it to selectively destroy the potentially incriminating documents “with the tacit blessings of the SIT.”

Claiming that the closure report made it apparently clear that the SIT was carrying out “further investigation” even after the September 12, 2011 Supreme Court order to submit its final report to a competent metropolitan magistrate's court in Ahmedabad, Mr. Bhatt said it was done “with the sole purpose and motive of shielding Mr. Modi and other powerful accused persons from legal punishment.”

Mr. Bhatt said the SIT was not required to investigate the observations made by amicus curiae Raju Ramachandran but it deliberately did so to find loopholes in his report and demolish his remark that criminal cases could be framed against Mr. Modi for allegedly creating communal disharmony under Sections of the Indian Penal Code.

Referring to a confidential letter — quoted by Mr. Ramachandran in his report — allegedly sent by the Under Secretary of the State Home Department to the SIT Chairman four days after Mr. Bhatt had met the amicus curiae in Gandhinagar, the suspended IPS officer said the “Janus-faced policies, as well as the collaborative machinations of the state of Gujarat and the SIT under your stewardship, once again stand exposed in this overt attempt at influencing the ongoing investigation against the Chief Minister and other powerful persons.”

The June 26, 2011 letter, in which the State government claimed to have “retrieved” several e-mails of Mr. Bhatt, said: “It leaves no room for doubt that it is a systematic and larger conspiracy, through Mr. Sanjiv Bhatt, involving top leaders of the Congress party in Gujarat, vested interests groups surviving on [an] anti-Gujarat campaign and electronic and print media reporters all of whom have started final efforts to keep the Godhra riot issue [a]live based on concocted facts and Mr. Bhatt, through all of them, is trying to build up a story at a stage when after almost 10 long years the honourable Supreme Court has virtually concluded the judicial proceedings after undertaking tremendous judicial exercise and [as] elaborately pointed out in the affidavit of the State government.”

The letter, Mr. Bhatt claimed, was clear proof of the State government, which should be the prosecutor, trying to influence the ongoing investigation and shielding Mr. Modi and the other accused.

Mr. Bhatt took strong exception to the SIT demolishing his two fax messages dated February 27 and 28, 2002, as “concocted and unreliable.” He gave long explanations to justify his claim that the messages he sent as Deputy Commissioner of the intelligence branch then were real and established that Mr. Modi was continuously informed of the developing serious situation outside Gulberg Society but the Chief Minister refused to take any action to pre-empt the strike, and that the then Ahmedabad Police Commissioner P. C. Pande was guilty of dereliction despite being cautioned about the possible repercussions of the “Chief Minister's decision” to bring the bodies of the train carnage victims to Ahmedabad on the Gujarat Bandh day.

Mr. Bhatt said Mr. Raghavan, as a retired senior IPS officer, should have realised that the grounds the SIT had shown for calling copies of his fax messages concocted were not justified. He said the reasons that the messages did not bear any security classification, that they carried serial numbers different from the number allocated to the intelligence agency on these days or that the serial numbers were typed, instead of being handwritten as was the usual practice, were inadequate to declare his claims unreliable.

‘Nothing secret'

Attaching copies of some other fax messages, Mr. Bhatt claimed that all fax messages need not carry security classification by default as it was decided on the contents. The messages he sent did not contain any information of a confidential or secret nature warranting their bearing the security classification. It was a common practice in the Gujarat police to assign serial number 100 for urgently numbering out-of-sequence communications in emergency situations whenever it was inexpedient to obtain the specific number of the dispatch sequencing. His messages shown as carrying the serial number 100 and other weak grounds adduced did not mean these were created later. But the SIT was making “overzealous efforts to undermine the credibility of the messages.”

‘Outrageously shocking'

Mr. Bhatt said the fact that the originals of the fax messages could not be traced in the official records only strengthened his long-standing apprehension that the State government had been selectively destroying the potentially incriminating documents, and despite his repeatedly cautioning the SIT about such possibilities, it allowed the government to carry on with its destructive action. It was “outrageously shocking” that the SIT in its final report dispensed with the issue of “non-preservation or destruction of material documents and records” in just one insignificant sentence that the “efforts were made to locate the dispatch register and [the] fax register of state IB control room, but the same had been reportedly destroyed.”

‘Bid to destroy evidence'

Mr. Bhatt said: “It is now become increasingly clear that agencies and offices working under the control of the State government of Gujarat have conspired to selectively destroy potentially incriminating documents and records pertaining to the Gujarat carnage 2002. It is also apparent that despite repeated requests, the SIT did not make any fruitful efforts for the production and/or preservation of crucial and relevant records and thereby indirectly facilitated the process of destruction of very vital evidence. The SIT under your stewardship has conveniently chosen to ignore the fact that such acts on the part of the State government or its agents would amount to offences under Sections 120-B (conspiracy), 201 and 204 of the Indian Penal Code.”

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.
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 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.