PM admits he cleared coal block allocation to Hindalco

October 20, 2013

PM_Hindalco
New Delhi, Oct 20: The Prime Minister's Office on Saturday ended its silence on the latest and possibly most explosive development in Coalgate by acknowledging that Manmohan Singh put his stamp of approval (on October 1, 2005) on the allocation of a coal block to top industrialist Kumar Birla's Hindalco. At the same time, it vigorously rebutted the Central Bureau of Investigation's claim of illegality, saying the PM stood by the decision as no wrong had been committed.

Taking what is being seen in political and bureaucratic circles as an uncharacteristically strong stand, the PMO said, "The PM is satisfied that the final decision in this regard was entirely appropriate and based on merits of the case placed before him."

The PMO statement comes after retired coal secretary P C Parakh — booked along with Birla for alleged criminal conspiracy and misconduct, and corruption - said that if CBI thought there were irregularities, then the PM ought to be "accused No 1" for giving his approval.

With the opposition baying for his resignation, Singh's move to forthrightly own up to having sought a reassessment of Hindalco's case after a representation by Odisha chief minister Naveen Patnaik appears intended to cap a politically debilitating controversy.

But by doing so, Singh, who at the time held charge of the coal ministry, accepted he was the "competent authority" who signed off on the coal allocations in the 2006-09 period - under CBI's lens — when he held charge of the portfolio. On whether the PM would be ready to be questioned in any Coalgate case, as suggested by senior minister Kamal Nath, a PMO spokesperson declined comment, saying CBI was yet to make such a request.

The PMO said it didn't wish to impede the CBI's investigation, but justified altering the screening committee's earlier decision to award the coal block in question to public sector companies Neyveli Lignite Corp (NLC) and Mahanadi Coalfields Ltd (MCL) by relying heavily on Patnaik's backing to Hindalco.

In accommodating Hindalco as the third partner in a joint venture, PM also waived a violation in guidelines to enhance the firm's share by arguing that NLC and Mahanadi were "sister PSUs" and Neyveli's share could be made good from Mahanadi's 70% allocation.

It invoked the "federal framework" to say Patnaik's views had to be accommodated, and claimed that public sector claimants had not been disadvantaged.

Countering criticism that private sector Hindalco had been favoured, PMO said the coal requirements of the two PSUs, who also sought the blocks, were protected in a separate arrangement.

Neyveli Lignite was originally allotted Talabira II coal blocks in Sambhalpur by the screening committee headed by then coal secretary P C Parakh as the panel held that Hindalco had failed to utilize a previously allocated block. The committee also said Hindalco had been provided adequate coal linkages from MLC, which it had failed to utilize. It was felt NLC and Mahanadi could together develop Talabira II and III to extract an additional 30 million tonnes of coal.

The coal ministry altered the screening committee's decision and gave Hindalco a 15% stake in a joint venture with NLC and Mahanadi, said the PMO, after considering representations from Birla and Patnaik, which were referred to it by the PM.

PMO said while the original recommendation was being processed by it, the PM received a letter dated 17.8.2005 from the Odisha CM saying that the state government assigned "topmost priority" to allocating Talabira II to Hindalco. Singh noted "please get a report from the coal ministry" on the letter.

Birla in his letter also sought the linkage and officials said he explained that Hindalco had not been able to use its previous allocation as a bauxite lease for its aluminium plant had not materialized.

Coal ministry resubmitted the file on 16.9.2005 proposing that Talabira II and III be mined as a single entity by the JV. Mahanadi's holdings would be proportionate to the extractable reserves in Talabira III or 70% of annual production.

The coal ministry told the PM that the total requirement of coal from the blocks by the main contenders was 503 million tons. The ministry said the claim of Orissa Sponge Iron Ltd would be accommodated elsewhere and Mahanadi was made a partner along with Hindalco and NLC.

Neyveli could not be dropped as it was a central PSU backed by the screening committee. In its account, PMO has leaned on the Odisha CM's "clear preference" for Hindalco in the "interest of creating more employment and growth of the state's manufacturing sector."

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.