Air India flight 171 crashed immediately after take-off from Ahmedabad on 12 June, and today, two weeks later, with no news about causes, the system is beginning to leak.

This is what happens naturally when information which people know is available to the authorities is withheld from the media and the public.

It’s easy for authorities like the Indian Directorate General of Civil Aviation to believe they can justify withholding information on the grounds that it’s very complicated, and they intend to release it quite soon anyway. Unfortunately for the DGCA, today’s media environment does not have that kind of patience any longer, especially in a case like this.

This fatal accident, a first for the Boeing 787 of any marque, killed 241 people on board and many on the ground. Whatever the cause was, it was highly unusual – maybe unique. For that reason, the industry and its regulators are desperate to know if there might be an unknown latent failure in the 787, so they can stop it happening again.

This pressure is what causes the system to leak. The Air India 171 flight data recorder has been downloaded by the National Transportation Safety Board for the DGCA at the Air Accident Investigation Bureau in Delhi, so some outstanding data will already be clear, even if not fully analysed yet.

Meanwhile the NTSB is sworn to secrecy according to the International Civil Aviation Organisation protocol which states that the nation in which the accident occured is responsible for the investigation. So in this case, the NTSB provides all its data to the DGCA, but as an agency of the nation in which the accident aircraft was designed, built and certificated, the NTSB has a particular responsibility to ensure that all operators of Boeing 787s throughout the world – there are about 1,000 of the type flying today – learn as fast as possible what, if anything, they should do.

That NTSB responsibility is a heavy one, but at the same time they want, if possible, to stick to the protocols to ensure the investigation proceeds calmly.

The NTSB obviously has to tell Boeing any details that are emerging. Then Boeing has an urgent duty to provide advice to 787 operators, particularly if any system failure detected might possibly repeat. This information will be received at Boeing by many engineers and technicians who must act rapidly to frame a plan for inspections and corrective action, then communicate with the operators, where an even larger group of airline technicians must carry out the Boeing advisories, or any directives that the Federal Aviation Administration may see fit to issue.

The pressure on the DGCA is of a different kind, and arguably less urgent. It is, after all, a regulator, a bureaucracy, with the responsibility to oversee the investigation and ensure it is conducted properly and according to law. It does, however, face the reality that a lot of highly relevant information is being shared right now by hundreds of experts all over the world, and the media knows it. So if the DGCA delays release of established facts, it will face increasing censure, especially if it delays release beyond one calendar month from the date of the accident.

A month is now firmly established as the time it should take for an air accident investigator to establish the basic facts of the case, and release a “preliminary factual report”. The final report can take more than a year.

Meanwhile, what of all those FDR facts whizzing around the world between experts at the manufacturer, the investigator, the world’s civil aviation authorities, and all the airlines that operate 787s? Well, they leak, of course, because they are important and everyone knows it. But most of the time the precise source of emerging information isn’t obvious, because individuals discussing them do not want to be recognised, so responsible journalists have to be careful what we do with what we hear.

What happens, however, is that it gradually becomes clear, among the plethora of opinions and guesswork always out there, which facts are beginning to establish themselves.

Some are simple, almost obvious. For example, the one emergency radio call made by the AI 171 crew said they had lost power, and an observation of the flight path almost immediately after unstick corroborates that puzzling fact.

But double engine failure immediately after take-off is almost unheard of, so what caused it? That is less obvious.

The DGCA has issued a list of checks it required Indian 787 operators to carry out. Unfortunately it lists checks that – mostly – are routine and would be carried out anyway.

The exception to that is the requirement to test the Electronic Engine Control System. These are computers called Full-Authority Digital Engine Controls (FADEC) that monitor the engines’ performance and react to demands by the pilots via the power levers or the flight control panel (autopilot input). These are vital, but have been established since the 1980s as highly dependable devices, and more reliable by far than the old mechanical connections.

So if both FADECs failed that would be extraordinary. In fact it makes more sense that something else failed or malfunctioned and disabled both FADECs. There is a lot of credible information gathering that backs this up, but since its precise source is not certain, I will not run it here.

Suffice to say we will soon learn what the problem was, because the DGCA knows it would look very bad to sit on it beyond 12 July 2025.