Cousin of Air India crash victim wants recordings released
Under International Civil Aviation Organization (ICAO) rules, investigating states are obliged to file a preliminary report within 30 days of a crash, detailing any initial findings.One of the findings in the report by India's Aircraft Accident Investigation Bureau outlines how a pilot could be heard asking the other pilot, "why did you cut off?", in a voice recording of the cockpit in the moments before the crash.It is not specified which voice is which. At the time the aircraft took off, the co-pilot was flying the plane, while the captain was monitoring.The report says the switches were moved back into their normal inflight position, something which would automatically start the process of relighting the engines.One engine, according to the report, was in the process of regaining thrust at the time the aircraft crashed. The other was relit but was not yet regaining thrust.The report says both engine fuel cut-off switches were turned to "cut-off" with a time delay.Mr Rafik said he would fly to India "straight away" if the recordings were released to family members."The Indian Government should release the cockpit audio for the families who lost loved ones," said Mr Rafik."After we listen to the cockpit recording, we will then know what happened."If they want to release the audio to family members only, I will be more than happy to fly to India and listen to it, I will go straight way."I lost my loved one. I know what my family are feeling and no one will understand my pain."
The investigation - led by Indian authorities with experts from Boeing, General Electric, Air India, Indian regulators, and participants from the US and UK - raises several questions.Investigators say the lever-lock fuel switches are designed to prevent accidental activation - they must be pulled up to unlock before flipping, a safety feature dating back to the 1950s. Built to exacting standards, they're highly reliable. Protective guard brackets further shield them from accidental bumps.The report does not draw any conclusions, and points out that the investigation into the crash - which just one passenger, Vishwashkumar Ramesh, from Leicester, survived - is continuing.In a statement following the release of the report, an Air India spokesperson said the airline "stands in solidarity with the families and those affected" and is cooperating fully with authorities investigating the crash.It did not address specific findings in the report.
Hashtags
Try Our AI Features
Explore what Daily8 AI can do for you:
Comments
No comments yet...
Related Articles
The Independent
13 hours ago
- The Independent
Day 2 of federal investigation into fatal midair crash of Army chopper, commercial plane opens
The National Transportation Safety Board enters a second day of public hearings Thursday on the January midair collision between an Army Black Hawk helicopter and a passenger plane that killed all 67 people aboard the aircrafts. On the first day, investigators highlighted a number of factors that may have contributed to the crash and the warnings about helicopter traffic that FAA received years before the tragedy over the Potomac River. It's too early for the board to identify what exactly caused the crash. The board's final report won't be released until sometime next year. But it became clear Wednesday how small a margin of error there was for helicopters flying the route the Black Hawk took the night of the nation's deadliest plane crash since November 2001. The January incident was the first in a string of crashes and near misses this year that have alarmed officials and the traveling public, despite statistics that still show flying remains the safest form of transportation. FAA didn't add warning to helicopter charts, official says NTSB Chairwoman Jennifer Homendy said an FAA working group raised concerns about all the helicopter traffic around Reagan airport and the risk of a collision in 2022, but the FAA refused to add a warning to helicopter charts urging pilots to use caution when this runway was in use. 'This is the very event that this would have been the cautionary note for,' she said. Video and animation presented during the proceeding's first day showed the helicopter flying above the 200 feet (61 meters) altitude limit before colliding with the plane. Investigators said Wednesday the flight data recorder showed the helicopter was actually 80 feet to 100 feet (24 to 30 meters) higher than the barometric altimeter the pilots relied upon showed they were flying. So the NTSB conducted tests on three other helicopters from the same unit in a flight over the same area and found similar discrepancies in their altimeters. Dan Cooper with Sikorsky helicopters said that when the Black Hawk helicopter involved in the crash was designed in the 1970s, it used a style of altimeter that was common at the time. Newer helicopters have air data computers that didn't exist back then that help provide more accurate altitude readings. Chief Warrant Officer Kylene Lewis told the board that she wouldn't find an 80 to 100 foot discrepancy between the different altimeters on a helicopter alarming because at lower altitudes she would be relying more on the radar altimeter than the barometric altimeter. Below 500 feet (152 meters), Lewis said she would be checking both instruments and cross referencing them. Army officials said a discrepancy of 70 to 100 feet (21 to 30 meters) between the Black Hawk's altimeters is within the acceptable range because pilots are expected to maintain their altitude plus or minus 100 feet. Concern about distances between planes and helicopters The greater concern is that the FAA approved routes around Reagan airport that included such small separation distances between helicopters and planes when planes are landing. 'The fact that we have less than 500 foot separation is a concern for me,' said Scott Rosengren, who is chief engineer in the office that manages the Army's utility helicopters. During the two minutes before the crash, one air traffic controller was directing airport traffic and helicopters in the area, a task that involved speaking to or receiving communications from several different aircraft, according to the NTSB's History of Flight Performance Study. The air traffic controller had spoken to or received communications from the Black Hawk helicopter, an airplane that was taking off, an Air Force helicopter, an airplane on the ground, a medical helicopter and an inbound flight that was not the American Airlines plane that would crash. 'All aircraft could hear the controller, but helicopters could only hear other helicopters on their frequency and airplanes only other airplanes,' the report stated. 'This resulted in a number of stepped on transmissions as helicopters and airplanes were not aware when the other was communicating.' Stepped on transmissions are those that are unheard or blocked because of other transmissions. The NTSB report provides a list of 29 separate communications between the airport tower and other aircraft during approximately the 1 minute and 57 seconds before the collision. Previously disclosed air traffic control audio had the helicopter pilot telling the controller twice that they saw the airplane and would avoid it. The animation ended with surveillance video showing the helicopter colliding with the plane in a fiery crash. Investigations have already shown the FAA failed to recognize a troubling history of 85 near misses around Ronald Reagan National Airport in the years before the collision, and that the Army's helicopters routinely flew around the nation's capital with a key piece of locating equipment, known as ADS-B Out, turned off. ___ Associated Press writers Leah Askarinam, Ben Finley and Rio Yamat contributed to this story.
Metro
a day ago
- Metro
Boeing 787 Dreamliner narrowly avoided crash after engine failure
A Boeing 787 Dreamliner crash nearly crashed just moments after taking off because of an engine failure. The United Airlines plane took off from Washington Dulles Airport bound for Munich on Friday but was forced to turn around just minutes into the flight. A 'Mayday' was declared by the crew at around 5,000 feet after a malfunction was reported in the aircraft's left engine. The crew on the plane were directed by air traffic control to a holding pattern northwest of Washington so that they could dump fuel. They asked the pilots: 'How long do you expect to hold, fuel, or just get set up there?' The pilot responded: 'We'll have to climb six [thousand feet] and adjust fuel.' The Dreamliner remained at around 6,000 feet for several minutes while it dumped the fuel. The pilot told air traffic control: 'We're dumping fuel at six thousand. We'll let you know when complete.' Luckily, the crew managed to land the plane safely back at Dulles Airport, and no injuries were reported, and all passengers disembarked safely. Because of engine failure, the plane had to be towed off the runway by the ground crew. Flight data shows that the aircraft's left engine failed while it was climbing after it departed. The aircraft is still grounded at the airport while engineers inspect the engine and the damage. Aviation authorities, including the Federal Aviation Administration (FAA), are expected to investigate the incident. A United Airlines spokesperson told Metro: 'United flight 108 to Munich returned to Washington Dulles shortly after takeoff to address a mechanical issue. 'The plane landed safely, and all passengers deplaned normally at the gate. 'The flight was subsequently cancelled and we arranged alternate travel arrangements to take customers to their destination as soon as possible.' Boeing has been approached for comment. The safety model of the Boeing 787 Dreamliner is currently under scrutiny because of the Air India crash last month. That incident involved both engines failing shortly after take-off from Ahmedabad airport. More Trending The tragic crash killed more than 260 people and the circumstances around it are still under investigation. Other problems with Boeing 787s have been reported this year, including an Ethiopian Airlines Boeing 787 en route from Addis Ababa to Mumbai. It experienced a mid-air depressurisation event, prompting an emergency descent. Oxygen masks were deployed, and seven passengers needed medical attention when they landed in Mumbai. Get in touch with our news team by emailing us at webnews@ For more stories like this, check our news page. MORE: Wizz Air launches 5 new Spanish routes from the UK – but not everyone is happy MORE: One of the world's highest volcanos erupts after 8.8-magnitude quake MORE: New York City skyscraper shooting victims identified: Everything we know
Daily Mail
a day ago
- Daily Mail
United plane forced to land minutes after takeoff over engine failure
A transatlantic United Airlines Boeing 787-8 Dreamliner was forced to return to the airport just moments after taking off after suffering a mid-air engine failure . Flight UA108, carrying 219 passengers and 11 crew members, departed Washington Dulles Airport at 5:40 p.m. on Friday, July 25, bound for Munich in Germany . But as the jet climbed through 5,000 feet, the left engine failed, prompting the pilots to declare a 'MAYDAY' and alert air traffic controllers. What followed was nearly three hours of tense aerial maneuvering. The crew entered a holding pattern northwest of Dulles, circling at 6,000 feet while dumping fuel to reduce the aircraft's landing weight. Throughout the emergency, the pilots worked closely with air traffic control to maintain safe separation from other aircraft and prepare for the return. Once the fuel dump was complete, the plane was cleared to land using an Instrument Landing System approach to Runway 19 Center. In a statement to the Independent , United Airlines confirmed the emergency, saying the aircraft returned to Dulles 'to address a mechanical issue.' A spokesperson added: 'The flight was subsequently cancelled, and we arranged alternate travel arrangements to take customers to their destination as soon as possible.' The airline declined to provide further details about the engine malfunction or confirm whether an investigation is underway. The Metropolitan Washington Airports Authority also confirmed the emergency landing, noting that the aircraft was met by fire and rescue crews and towed to a gate for inspection.
