Investigation Archives - Page 5 of 7

Washington, United States: The family of a passenger killed in January’s midair collision near Ronald Reagan Washington National Airport has filed the first federal lawsuit over the disaster, naming American Airlines, its regional affiliate PSA Airlines, the Federal Aviation Administration (FAA), and the U.S. Army as defendants. The complaint, filed Tuesday in U.S. District Court, comes from Rachel Crafton, whose husband, Casey Crafton, was among the 67 people killed when American Eagle Flight 5342 collided with a U.S. Army Black Hawk helicopter on January 29. The crash, which occurred at low altitude just half a mile from the runway, killed all 64 people aboard the Embraer E175 regional jet and all three Army crew members on the helicopter. Crafton’s lawsuit accuses the defendants of negligence and wrongful death, arguing that the tragedy was both predictable and preventable. The 115-page filing cites more than 30 documented near misses in the crowded D.C. airspace that, according to the suit, were ignored by regulators and operators. The National Transportation Safety Board (NTSB) preliminary findings indicate insufficient vertical separation, estimated at just 75 feet, and highlight a history of over 15,000 near-misses between aircraft and helicopters in the area from 2021 to 2024, many occurring at night or above designated altitudes. The NTSB has recommended that the FAA restrict helicopter operations near DCA during active runway use and designate safer routes to prevent future collisions. The full investigation is ongoing, with a final report expected in 2026. “The defendants utterly failed in their responsibilities to protect passengers, crew, and the public,” the complaint alleges. It further faults American and PSA for inadequate pilot training, the FAA for failing to redesign or better monitor congested flight paths into Reagan National, and the Army for not preventing its aircraft from entering civilian approach corridors. The suit also highlights alleged air traffic control failures, including the absence of timely safety alerts that could have helped avoid the collision. This federal filing follows earlier Federal Tort Claims Act notices submitted by Crafton in February, seeking $250 million in damages from the FAA and the Army. Those claims are a legal prerequisite to suing the U.S. government, which typically enjoys sovereign immunity unless exceptions apply. The FAA responded with a statement of condolences, noting that it had “acted decisively” since the crash to improve safety over the capital region and pledged full cooperation with the ongoing National Transportation Safety Board (NTSB) investigation. The Army declined to comment, citing the active investigation, but said it remains focused on supporting victims’ families. American Airlines and PSA signaled they would defend themselves in court, pointing to their overall safety record. The Crafton case is expected to be a bellwether lawsuit, with other families of victims likely to join or file their own claims in the coming months. The NTSB’s final accident report, expected in 2026, will likely shape the scope of liability across all parties.

Widow of Passenger Sues American Airlines, FAA, Army Over Deadly D.C. Collision

Aviation Today News Desk September 25, 2025

Washington, United States: The family of a passenger killed in January’s midair collision near Ronald Reagan Washington National Airport has filed

Kentucky, United States: The National Transportation Safety Board (NTSB) has released its final report into the September 27, 2023, crash of a Piper PA-28-161 that killed a flight instructor and student pilot near Whitesville, Kentucky, concluding that the accident was caused by the instructor’s decision to continue flying into an area of severe thunderstorms. Investigators found the airplane suffered an in-flight breakup after encountering extreme turbulence inside convective weather. The Eagle Flight Academy aircraft departed Bowling Green-Woodhurst Airport at 9:55 p.m. for a night cross-country training mission intended to complete the student’s night-flying requirement. The 22-year-old instructor and 18-year-old student were on their first flight together. According to ADS-B data and air traffic control recordings, the aircraft climbed to 4,500 feet and was warned by controllers at 10:44 p.m. of “heavy to extreme precipitation” to its left. Two minutes later, the instructor requested an instrument flight rules clearance but continued circling in the weather and reported the airplane was “getting blown around like crazy” and in “pretty extreme turbulence.” Moments later, communications ceased. Radar data showed a right descending turn before the plane broke apart. The debris field stretched across 25 acres of wooded terrain. Post-accident examination revealed no mechanical failures. Investigators confirmed the aircraft exceeded its structural limits while penetrating severe weather. The NTSB cited the instructor’s decision-making as the defining factor: “The flight instructor’s improper decision to continue flight into a known area of thunderstorms resulted in an in-flight breakup.” The weather briefing obtained before departure included an active convective SIGMET warning of severe storms with tops to 42,000 feet, hail, and wind gusts up to 50 knots. The NTSB also highlighted the potential latency of weather radar images from cockpit and mobile applications, cautioning pilots that such data may be several minutes old and could under-represent the severity or position of fast-moving storms. Autopsies determined both occupants died of multiple blunt-force injuries. Toxicology tests were negative for the instructor. The student tested positive for cetirizine, an over-the-counter antihistamine, but impairment could not be determined.

CFI’s Choice to Fly in Severe Weather Caused Crash that Killed Student and Self: NTSB

Aviation Today News Desk September 11, 2025

Kentucky, United States: The National Transportation Safety Board (NTSB) has released its final report into the September 27, 2023, crash of

Mumbai, India: The Aircraft Accident Investigation Bureau (AAIB) has issued its preliminary report on July 21, 2025 runway excursion involving an Air India Airbus A320-neo at Chhatrapati Shivaji Maharaj International Airport, offering the first official account of what caused the aircraft to veer off course upon landing. According to the report, Air India flight AI 2744 was operating from Kochi to Mumbai with 182 people on board including two pilots and five cabin crew when it touched down during heavy rainfall but failed to stay on the runway centerline. Investigators said the aircraft’s right-hand main wheels and nose gear entered the grassy area adjacent to the runway before the crew was able to steer it back onto the paved surface. Despite the excursion, the aircraft maintained control and continued taxiing under its own power to parking bay K5L, where passengers disembarked safely. No injuries were reported among passengers or crew. The AAIB report detailed significant damage to the aircraft’s undercarriage and engine cowling. Three main tyres numbers 2, 3, and 4 were found deflated with cut marks, likely caused by contact with uneven ground. The right engine fan cowl showed cuts on both sides, while investigators also noted grass ingestion in both main landing gear assemblies and the nose landing gear. The report highlights adverse weather conditions as a contributing factor. Mumbai was experiencing intense monsoon rainfall at the time of landing, which likely reduced runway friction. Airport officials briefly suspended operations following the incident to conduct runway inspections, after which flight movements resumed. Air India deployed maintenance teams to tow the aircraft to its hangar for detailed inspection and repairs. The final investigation report is yet to be released.

AAIB Preliminary Report Notes Adverse Weather in Air India Mumbai Runway Excursion

Aviation Today News Desk September 9, 2025

Mumbai, India: The Aircraft Accident Investigation Bureau (AAIB) has issued its preliminary report on July 21, 2025 runway excursion involving an

$Detroit, United States: A Detroit-based flight attendant has filed a $75 million lawsuit against Delta Air Lines and its regional carrier Endeavor Air, alleging negligence and “human error” in connection with a February crash landing at Toronto Pearson International Airport that left her severely injured. According to court documents filed in the U.S. District Court for the Eastern District of Michigan, Vanessa Miles, 39, claims she sustained life-altering injuries when Delta Connection Flight 4819 operated by Endeavor Air landed hard, flipped over, and briefly caught fire on February 17, 2025. She was traveling as a “deadheading” crew member, repositioning to another assignment, when the accident occurred. The Bombardier CRJ-900 regional jet was arriving from Detroit Metropolitan Wayne County Airport with 80 people on board, including four crew members and 76 passengers. Preliminary findings from the Transportation Safety Board of Canada indicate the aircraft descended too rapidly during final approach, causing a landing gear collapse that led to the jet overturning on the runway. Twenty-one people were injured, there were no fatalities. In its initial report, the TSB noted that the aircraft’s emergency locator beacon failed to activate and that evacuation slides did not function as intended. Passengers and crew evacuated through damaged exits while the aircraft emitted smoke. Miles alleges Delta and Endeavor Air engaged in gross negligence by assigning an inexperienced captain to the flight and rushing pilot training to cut costs. The lawsuit claims both airlines failed to provide adequate safety equipment, citing the non-deployment of evacuation slides and poor in-cabin communication during the emergency. Court filings state that Delta and Endeavor “chose profit over safety” and ignored critical safety protocols, putting crew and passengers at “unnecessary and extreme risk.” Miles says she suffered a traumatic brain injury, a fractured shoulder, spinal and knee injuries, chemical burns, post-traumatic stress disorder, and ongoing anxiety and depression. She claims these injuries have ended her career in aviation. Delta Air Lines has declined to comment on the lawsuit, citing pending litigation, but stated it is cooperating fully with the TSB investigation. The airline has defended the training and certification of both the captain and first officer, saying that safety is its top priority. Endeavor Air has not issued a public statement. The TSB’s full investigation is expected to take several more months and is examining flight data recorders, crew training logs, and maintenance history to determine the exact sequence of events that led to the hard landing and runway overturn.$

Flight Attendant Sues Delta and Endeavor for $75 Million Over Toronto Runway Crash

Aviation Today News Desk August 9, 2025

Detroit, United States: A Detroit-based flight attendant has filed a $75 million lawsuit against Delta Air Lines and its regional carrier

Washington, United States: Investigators probing the January 29 mid‑air collision between U.S. Army Black Hawk helicopter and American Airlines Flight 5342 over the Potomac River revealed a combination of faulty altitude data, communication failures, and ignored safety warnings as contributing factors to the disaster that killed all 67 people aboard the commercial aircraft. During three days of public hearings held this week, the National Transportation Safety Board (NTSB) disclosed evidence that the Black Hawk was operating as much as 100 feet higher than its altimeter indicated, breaching the restricted ceiling for helicopters transiting the congested Reagan National Airport corridor. Officials said the helicopter’s barometric altitude sensors were incorrectly calibrated, a condition also found in similar Army aircraft. “Altitude deviations of that magnitude are unacceptable in such tightly controlled airspace,” said NTSB Chair Jennifer Homendy, noting that the military’s existing tolerance for up to 100 feet of variance was now under review. The hearing also detailed a communication breakdown moments before the collision. A radio transmission from the Black Hawk reportedly “stepped on” the tower controller’s instructions, obscuring critical clearance information. Compounding the error, a single controller was managing both local helicopter and fixed‑wing operations, an arrangement the NTSB described as “operationally unsound for high‑density traffic periods.” The Federal Aviation Administration faced sharp criticism for not acting on repeated warnings from controllers and internal safety analysts. Between 2021 and 2024, more than 15,000 near‑miss events were recorded nationwide, including 84 in the Washington National airspace region. Despite internal proposals to chart helicopter “hot spots” and segregate their routes, no permanent changes were implemented prior to the crash. According to Reuters, Transportation Secretary Sean Duffy told lawmakers that, “This accident reflects systemic failures that cannot be excused by procedural norms or military exemptions.” On Tuesday, Senator Ted Cruz introduced bipartisan legislation requiring all military and training helicopters operating near commercial corridors to activate ADS‑B Out tracking, which broadcasts precise position and altitude to air traffic control and other aircraft. The bill also calls for a comprehensive review of flight routing in mixed‑use airspace and a federal audit of aviation oversight practices. The Army confirmed that ADS‑B tracking had been disabled during the helicopter’s test mission, a common practice for certain military flights but one that reduced situational awareness in an already crowded corridor. Families of victims, along with aviation safety advocates, have welcomed the proposed reforms, though the NTSB cautioned that a final report is not expected until 2026.

NTSB Blames Faulty Altitude Data, ATC Gaps in Deadly Potomac Mid-Air Collision

Aviation Today News Desk August 5, 2025

Image: NTSB Washington, United States: Investigators probing the January 29 mid‑air collision between U.S. Army Black Hawk helicopter and American Airlines

San Francisco, California: A Delta Air Lines co-pilot was arrested on Saturday night at San Francisco International Airport (SFO) moments after his aircraft landed, following a months-long investigation into serious allegations of child sexual abuse. According to official statements, federal agents from Homeland Security Investigations (HSI) and officers from the Contra Costa County Sheriff’s Office boarded Delta Flight 2809, arriving from Minneapolis, shortly after its arrival at SFO at approximately 9:35 p.m. on July 26. The co-pilot was taken into custody directly from the cockpit in the presence of passengers and crew members. The suspect has been identified as Rustom Bhagwagar, a 34-year-old Florida resident. Authorities confirmed that Bhagwagar faces five felony counts of oral copulation with a child under the age of 10. The Contra Costa County Sheriff’s Office stated that the arrest followed an investigation that began in April 2025, when reports of alleged child sexual abuse involving the suspect were first received. Detectives from the Sheriff’s Office, working in coordination with federal law enforcement, determined Bhagwagar’s work and travel schedule in order to facilitate the arrest without incident. The operation was executed as the aircraft reached the gate at SFO, ensuring that the suspect was apprehended immediately upon arrival. Passengers onboard reported that a team of approximately ten officers entered the aircraft in tactical gear and removed the pilot from the cockpit. No disruption to airport operations or other flights was reported during the incident. In an official statement, Delta Air Lines confirmed the pilot’s immediate suspension, stating: “Delta has zero tolerance for unlawful conduct and is cooperating fully with law enforcement in their investigation.” Bhagwagar is currently being held at the Martinez Detention Facility in Contra Costa County. His bail has been set at $5 million, according to county officials. No information has been released regarding court proceedings or legal representation at this time. While Homeland Security Investigations assisted with the arrest due to its location at an international airport, officials confirmed that the criminal case remains under the jurisdiction of the Contra Costa County Sheriff’s Office. Authorities have not disclosed further details regarding the ongoing investigation, and no additional charges have been announced. As of now, there is no indication that any other Delta personnel were involved or aware of the allegations. The airline has not issued further comment beyond its initial statement.

Delta Co‑Pilot Arrested After Flight Lands at San Francisco in Child Sex Abuse Case

Aviation Today News Desk July 29, 2025

San Francisco, United States: A Delta Air Lines co-pilot was arrested on Saturday night at San Francisco International Airport (SFO) moments

Ahmedabad, India: The Aircraft Accident Investigation Bureau (AAIB) has released the preliminary report into the crash of Air India’s Boeing 787-8 Dreamliner, registration VT-ANB, which occurred on 12 June 2025 shortly after takeoff from Ahmedabad’s Sardar Vallabhbhai Patel International Airport. The scheduled flight, operating as AI171, was bound for London Gatwick Airport with 230 passengers, 10 cabin crew, and 2 flight crew on board. All 241 persons on board perished in the accident. Additionally, 19 fatalities were reported on the ground. Aircraft and Crew Information The aircraft involved was a Boeing 787-8 with serial number 36279, manufactured in 2013, and operated by Air India. Both engines were General Electric GEnx-1B series units, installed in March and May 2025 respectively. The aircraft had a valid Certificate of Airworthiness and had undergone its last Airworthiness Review on 22 May 2025. The Pilot-in-Command held an ATPL with over 15,638 hours of total flying experience, including 8,596 hours on type. The First Officer held a CPL with 3,403 hours of total flying experience, of which 1,128 hours were on type. Both pilots were based in Mumbai, had arrived in Ahmedabad the previous day, and had met required rest periods. The First Officer was the Pilot Flying for the accident flight. Sequence of Events On 12 June 2025, VT-ANB had earlier operated AI423 from Delhi and landed at Ahmedabad at 05:47 UTC. A post-flight defect regarding “STAB POS XDCR” was logged and addressed by on-duty maintenance personnel before the aircraft was released for its next flight. Flight AI171 was scheduled for departure at 07:40 UTC. The aircraft pushed back from Bay 34 at 07:48 UTC, taxied to Runway 23, and received takeoff clearance at 08:07:33 UTC. The aircraft began its takeoff roll at 08:07:37 UTC. According to data recovered from the Enhanced Airborne Flight Recorder (EAFR), the aircraft reached V1 at 08:08:33 UTC and rotation speed (Vr) at 08:08:35 UTC. It lifted off at 08:08:39 UTC and reached a maximum recorded indicated airspeed of 180 knots at 08:08:42 UTC. At that moment, both engine fuel control switches, first for Engine 1 and then for Engine 2, with a one-second interval transitioned from the “RUN” to the “CUTOFF” position. The data indicated an immediate decrease in N1 and N2 engine speeds, consistent with fuel supply being cut off. Cockpit voice recordings captured a pilot questioning the action, with one asking, “Why did you cut off?” and the other responding that he had not. No further verbal conflict or distress was recorded before the power loss. Power Loss and Emergency Response The sudden loss of thrust from both engines triggered the deployment of the Ram Air Turbine (RAT), visible on CCTV footage from the airport. The RAT began supplying hydraulic power by 08:08:47 UTC, confirming the engines were no longer providing power. At 08:08:52 UTC, the Engine 1 fuel control switch was moved back to “RUN,” followed by Engine 2 at 08:08:56 UTC. The Auxiliary Power Unit (APU) inlet door also began to open at this time, indicating an automatic start sequence. Both engines attempted relight: Engine 1 showed signs of core recovery, while Engine 2 relit but could not stabilize its core speed. At 08:09:05 UTC, a MAYDAY call was transmitted by one of the pilots. No further communication was received. The aircraft lost altitude rapidly and crashed into the BJ Medical College hostel complex approximately 0.9 nautical miles from the end of Runway 23. The impact caused destruction of five buildings and extensive fire damage. All occupants of the aircraft were fatally injured. According to the report, the Emergency Locator Transmitter (ELT) was not activated during the sequence. Recovery and Wreckage The wreckage was spread across an area of approximately 1000 feet by 400 feet. The vertical stabilizer, main landing gear, fuselage components, both engines, and nose gear were found at various distances from the initial impact point. The thrust levers were discovered near the idle position, though flight data indicated they were forward (takeoff thrust) until impact. The fuel control switches were found in the “RUN” position post-crash. The forward EAFR was successfully recovered and downloaded using equipment supplied by the U.S. National Transportation Safety Board (NTSB). It contained approximately 49 hours of flight data and two hours of audio, including the accident flight. The aft EAFR was too severely damaged to retrieve data. Ongoing Investigation The investigation team comprises AAIB India officers, subject matter experts, and international participants from NTSB (USA), Boeing, General Electric, the FAA, and authorities representing nations whose citizens were onboard. As of the preliminary report, there are no recommendations issued to operators or manufacturers of the B787-8 aircraft or GEnx-1B engines. Fuel samples tested from the bowsers and tanks used to refuel the aircraft were found satisfactory. Additional trace samples collected from the APU and refuel/jettison systems are being sent for further testing. Statements from witnesses and the sole surviving passenger have been recorded. Post-mortem analyses are underway to determine any relevant aeromedical findings. The AAIB emphasized that the investigation remains ongoing, and all evidence, including maintenance records, crew history, and system components, will continue to be evaluated.

Cockpit Voice Captures Fuel Cutoff Confusion in Air India AI171 Crash Preliminary Report

Aviation Today News Desk July 12, 2025

Gujarat, India: The Aircraft Accident Investigation Bureau (AAIB) has released the preliminary report into the crash of Air India’s Boeing 787-8

Washington, D.C., United States: The National Transportation Safety Board (NTSB) has released its final report into the in-flight depressurization incident involving Alaska Airlines Flight 1282, identifying critical failures by both Boeing and the Federal Aviation Administration (FAA). The incident, which occurred on January 5, 2024, involved the mid-cabin exit door plug separating mid-air from a Boeing 737-9 MAX, leading to an emergency landing in Portland, Oregon. No fatalities occurred, though eight people sustained minor injuries. The NTSB investigation concludes that a series of manufacturing errors, documentation lapses, and oversight failures contributed to the serious safety breach. Incident Summary Alaska Airlines Flight 1282 departed from Portland International Airport at 5:07 p.m. on January 5, 2024. While climbing through approximately 14,830 feet, the aircraft experienced a sudden depressurization due to the separation of the left mid-cabin exit door plug. The cabin pressure rapidly dropped, oxygen masks deployed, and a loud explosive sound was heard. The crew declared an emergency and landed safely back in Portland at 5:27 p.m., 20 minutes after departure. The aircraft was carrying 171 passengers and six crew members. Manufacturing Lapses at Boeing Identified According to the NTSB’s 19-page final report, the door plug had been removed by Boeing personnel at the company’s Renton, Washington facility during fuselage repairs in September 2023. However, no documentation of the removal or reinstallation was found, violating standard production protocols. Furthermore, investigators determined that four critical bolts securing the door plug were never reinstalled. Boeing's internal tracking systems failed to log the maintenance action. The report states, "Boeing did not have procedures to ensure that the required safety documentation or final inspections were completed after door plug reinstallation." The door plug, which is used to cover an optional emergency exit area on high-density seating configurations, is designed to be held in place by 12 fittings and four key retention bolts. The NTSB confirmed that the plug gradually shifted out of position and ultimately detached due to missing fasteners. Inadequate Training and Procedures The NTSB noted that Boeing’s assembly teams lacked adequate training to properly handle door plug installations. The company’s work instructions were described as overly complex and lacking clarity, particularly regarding non-routine work. The investigation found that the work was performed by a team unfamiliar with the procedure. It was further revealed that quality assurance staff failed to verify the bolt installation, allowing the aircraft to proceed through final assembly and delivery without detecting the omission. FAA Oversight Deficiencies In addition to Boeing’s errors, the NTSB cited the FAA’s ineffective compliance and surveillance mechanisms. While the agency had conducted multiple audits at Boeing facilities in prior years, it failed to detect or address systemic lapses in documentation, workforce training, and final assembly inspections. The NTSB concluded that the FAA’s oversight was “inadequate to identify recurring noncompliance” and did not sufficiently mitigate risk associated with critical assembly processes. Probable Cause and Contributing Factors The report states the probable cause of the accident as: "The in-flight separation of the left mid-cabin exit door plug due to the failure of Boeing to ensure that the plug was reinstalled with all required retention hardware during production... Contributing to the accident was the FAA’s ineffective oversight of Boeing’s production processes and safety compliance." Safety Recommendations Issued In total, the NTSB issued 19 safety recommendations, including: A redesign of the 737-9 MAX mid-exit door plug to prevent inadvertent displacement Improved documentation protocols and quality control procedures for component removal and reinstallation Enhanced workforce training for Boeing production and quality assurance personnel Strengthened FAA audit procedures and risk-based surveillance methods Mandated tracking of critical fastener installation for all high-risk components Nine recommendations were directed to Boeing and ten to the FAA. In a statement, Boeing acknowledged the findings and stated that it has implemented "significant corrective actions" in response to the incident and the investigation. The company has committed over $1 billion toward improving safety systems, production oversight, and employee training across its 737 program. The FAA stated that it is reviewing the NTSB’s recommendations and has already implemented a production cap on 737 MAX aircraft pending further compliance improvements. The January 2024 incident raised renewed scrutiny of the Boeing 737 MAX program, which had previously been grounded worldwide following two fatal crashes in 2018 and 2019. Following this event, hundreds of MAX 9 aircraft were temporarily grounded for inspection by the FAA, leading to widespread schedule disruptions for multiple airlines.

NTSB Blames Boeing for Manufacturing Errors for Alaska Airlines Door Plug Incident

Aviation Today News Desk July 11, 2025

Washington, D.C., United States: The National Transportation Safety Board (NTSB) has released its final report into the in-flight depressurization incident involving

New Delhi, India: Indian authorities are intensifying their investigation into the fatal crash of Air India Flight AI171, with officials confirming that sabotage has not been ruled out as a possible cause. The Boeing 787 Dreamliner, operating on the London-Ahmedabad route, crashed on June 12, resulting in the deaths of all 241 people on board and 19 individuals on the ground. The crash is now considered one of the deadliest aviation disasters in India’s recent history. Black Box Data Under Analysis The Aircraft Accident Investigation Bureau (AAIB) confirmed that the cockpit voice recorder (CVR) and flight data recorder (FDR) were recovered from the wreckage and are currently being analyzed at a newly equipped laboratory in New Delhi. Officials reported that data from both recorders has been successfully downloaded and the process of reconstructing the aircraft’s final moments is underway. The investigation is being carried out with technical assistance from the U.S. National Transportation Safety Board (NTSB), aircraft manufacturer Boeing, and engine maker GE Aerospace. All Possible Causes Being Investigated India’s Minister of State for Civil Aviation, Murlidhar Mohol, stated that no potential cause is being ruled out, including mechanical failure, human error, or sabotage. “The government is committed to a transparent investigation. We are examining every angle, including the possibility of sabotage,” Mohol told reporters. Authorities are scrutinizing CCTV footage from the Ahmedabad airport premises and have questioned several ground-handling personnel. Devices, including mobile phones of certain airport staff, have been seized as part of the probe. Investigators are particularly focusing on any activity near the aircraft in the hours leading up to its departure from London and arrival in Ahmedabad. Sabotage Considered, But Not Confirmed While no conclusive evidence of sabotage has yet been found, the Ministry of Civil Aviation has acknowledged that certain anomalies such as a simultaneous failure of both engines are rare and require thorough examination. Deployment of the aircraft’s emergency Ram Air Turbine (RAT) shortly before impact further supports the theory that the aircraft lost all primary engine power. Officials have not disclosed whether any pre-crash communication indicated a technical or security issue. Domestic Handling of Investigation Contrary to earlier speculation, India has decided not to send the black boxes abroad for analysis. According to government officials, all data extraction and analysis are being handled domestically using newly acquired digital forensics infrastructure. India has also declined a request from the United Nations to allow an ICAO-appointed aviation investigator to participate in the probe. The move has drawn both domestic and international attention, with the government assuring that international best practices under ICAO Annex 13 guidelines are being followed. Fleet Inspections and Safety Measures Following the crash, Air India initiated a precautionary inspection of all 33 Boeing 787s in its fleet. As of June 30, 26 aircraft have cleared safety checks, while the remaining seven continue to undergo technical evaluation. The Directorate General of Civil Aviation (DGCA) has also issued advisories to all Indian carriers to enhance maintenance checks on wide-body aircraft and reinforce pilot training related to engine-out procedures. Preliminary Report Expected by Mid-July Under ICAO standards, a preliminary report is due within 30 days of the crash. Officials have indicated that the report is on schedule and should be published by mid-July. A final report, which will include a detailed causal analysis and safety recommendations, is expected within three to six months. Until then, the AAIB will continue to lead a multi-agency investigation, supported by central aviation authorities, Gujarat Police, counter-terrorism agencies, and technical teams from international aviation partners. Background Air India Flight AI171 was approaching Sardar Vallabhbhai Patel International Airport in Ahmedabad when it experienced a sudden and complete loss of engine power. The aircraft crashed in a residential area approximately 8 km from the airport claiming 241 of 242 lives on board and 1 survivor. This is the first fatal crash involving a Boeing 787 aircraft in Indian aviation history. The incident has prompted widespread scrutiny of Air India’s operational protocols and the broader state of aviation safety oversight in the country.

Air India Crash: Black Boxes Analyzed as India Probes Engine Failure, Sabotage Angle

Aviation Today News Desk July 1, 2025

New Delhi, India: Indian authorities are intensifying their investigation into the fatal crash of Air India Flight AI171, with officials confirming

Emergency System Likely Deployed, Damaged Black Boxes Hinder Probe Into Air India Crash

Aviation Today News Desk June 19, 2025

New Delhi, India: The investigation into the fatal crash of Air India Flight AI171 continues to develop, with new details emerging

Investigation

Widow of Passenger Sues American Airlines, FAA, Army Over Deadly D.C. Collision

AAIB Preliminary Report Notes Adverse Weather in Air India Mumbai Runway Excursion

Flight Attendant Sues Delta and Endeavor for $75 Million Over Toronto Runway Crash

NTSB Blames Faulty Altitude Data, ATC Gaps in Deadly Potomac Mid-Air Collision

Delta Co‑Pilot Arrested After Flight Lands at San Francisco in Child Sex Abuse Case

Cockpit Voice Captures Fuel Cutoff Confusion in Air India AI171 Crash Preliminary Report

NTSB Blames Boeing for Manufacturing Errors for Alaska Airlines Door Plug Incident

Air India Crash: Black Boxes Analyzed as India Probes Engine Failure, Sabotage Angle

Emergency System Likely Deployed, Damaged Black Boxes Hinder Probe Into Air India Crash

Follow Us

Quick Links

Navigate

General Support

News Desk Support

Follow Us