Investigation Archives - Page 2 of 9

Paringa, New Zealand: A loose maintenance bolt that detached during flight caused an Airbus AS350BA helicopter to become increasingly difficult to control before it crashed near the Paringa River mouth on New Zealand's West Coast, according to final findings released by the Transport Accident Investigation Commission (TAIC). The accident occurred on July 20, 2024, while an Amuri Helicopters Airbus AS350BA, registration ZK-HJM, was being flown from Queenstown to Franz Josef following maintenance work performed at Queenstown Aerodrome. The helicopter was carrying a pilot and one passenger. Both occupants sustained minor injuries and were transported to hospital, while the aircraft suffered substantial damage. According to the investigation, engineers from Salus Aviation had swapped the helicopter's left and right hydraulic servo actuators during scheduled maintenance. However, a critical securing bolt on the lower attachment point of the left-hand hydraulic servo actuator was not properly secured before the aircraft was returned to service. Investigators determined that the associated nut had not been tightened to the required torque and that a locking pin was either missing or incorrectly installed. Although the work was subject to a mandatory duplicate inspection by a second engineer, the defect went undetected. Approximately 52 minutes into the flight, the pilot felt a sudden jolt and observed abnormal main rotor blade tracking. Seven minutes later, concerned by the abnormal indications, the pilot initiated a precautionary landing. During the descent, cyclic control forces increased significantly, particularly when attempting left control inputs. As the helicopter descended to between three and seven metres above the ground, it rolled and collided with terrain before coming to rest on its left side. TAIC found that the securing bolt eventually detached completely during the flight, significantly limiting the pilot's control of the helicopter. The investigation identified several human-factor issues that contributed to the maintenance error. The engineer responsible for the task was reportedly distracted by both a customer interaction and a hydraulic fluid spill while performing the work. Investigators also found the engineer was working under time pressure ahead of a planned holiday and did not sufficiently verify the maintenance task before completion. The second engineer responsible for the duplicate safety inspection also failed to identify the improperly secured hardware. The engineer told investigators they could not explain why the defect was missed but acknowledged experiencing broken sleep at the time, which may have affected performance. Following the accident, Salus Aviation conducted an internal investigation and implemented a series of corrective actions. The company temporarily removed the involved engineers from release-to-service inspection duties, introduced additional training, strengthened inspection and documentation procedures, implemented independent post-maintenance inspections, and established regular assurance audits. Measures aimed at reducing workplace distractions and improving engineering oversight were also introduced. TAIC concluded that the maintenance provider had adequately addressed the safety deficiencies identified during the investigation. As a result, the Commission did not issue any formal safety recommendations.

Loose Bolt Left Undetected During Inspection Caused New Zealand Airbus AS350 Crash

Aviation Today News Desk June 19, 2026

Paringa, New Zealand: A loose maintenance bolt that detached during flight caused an Airbus AS350BA helicopter to become increasingly difficult to

Bhiwani, India: India’s Aircraft Accident Investigation Bureau (AAIB) has released its final investigation report into the accident involving Tecnam P2006T aircraft VT-VDB operated by FSTC Flying School at Bhiwani Airfield, Haryana, on May 12, 2022, concluding that fuel vapor lock in the left engine, combined with crew handling deficiencies and limited experience on type, led to the crash during a training flight. The twin-engine Tecnam P2006T was conducting a routine training sortie at Chaudhary Bansi Lal Airport, Bhiwani, with a flight instructor and a student pilot on board. The exercise involved six circuit-and-landing maneuvers and was the second training sortie of the day. According to the investigation, the aircraft completed its first circuit and performed a normal touch-and-go landing on Runway 30. Shortly after becoming airborne again, the crew experienced rough running and a loss of power in the left engine. The instructor took control and initiated asymmetric-flight procedures to maintain directional control. While the aircraft was still climbing at approximately 100 feet above ground level, the crew reported roughness and a reduction in power from the right engine as well. As the aircraft’s airspeed decayed, it was unable to sustain the climb. The crew elected to conduct a forced landing within the airfield boundary. The aircraft touched down heavily, sustaining substantial damage before coming to rest near the perimeter wall. Both occupants evacuated safely. No fatalities, serious injuries, fire, or damage to third parties were reported. The accident aircraft was a 2019-built Tecnam P2006T, serial number 269, powered by two Rotax 912 S3 engines. Records examined by investigators showed the aircraft held valid airworthiness documentation and had been maintained in accordance with DGCA-approved maintenance programs. The 34-year-old flight instructor held a valid Commercial Pilot Licence and had accumulated approximately 1,589 flight hours. However, he had only around 28 hours of experience on the Tecnam P2006T type. The 20-year-old student pilot had logged approximately 182 flight hours, most of them on Cessna 172 aircraft. Prior to the accident, he had accumulated only about 1 hour and 15 minutes on the Tecnam P2006T. Investigators found both crew members were properly licensed, medically fit, adequately rested, and had not consumed alcohol. A central focus of the investigation was determining whether an engine malfunction had caused the accident. AAIB investigators conducted extensive examinations and operational testing of both Rotax engines and associated fuel, ignition, and electrical systems. The report concluded that neither engine suffered a technical malfunction and both were capable of producing power. Investigators also noted that the aircraft’s Garmin avionics system had the capability to record engine and flight parameters. However, no SD card had been installed in the data-logging slot, meaning no flight data was recorded. Subsequent attempts by the U.S. The National Transportation Safety Board (NTSB) to recover information from the units' internal memory was unsuccessful. Weather conditions at Bhiwani played a significant role in the occurrence. Meteorological data recorded temperatures of approximately 44°C at the time of the flight, while a weather station measured 46°C immediately after the accident. The aircraft type is approved for operations up to 50°C. Investigators determined that the combination of extreme ambient temperatures, elevated runway surface temperatures, and the use of automotive gasoline (MOGAS) created conditions favorable for vapor lock formation. Vapor lock occurs when fuel vaporizes within fuel lines, disrupting the continuous supply of liquid fuel to the engine. The report noted that FSTC operated its Tecnam fleet on MOGAS containing 10% ethanol. Although the fuel met all approved specifications and manufacturer requirements, investigators found that its volatility increased the likelihood of vapor formation under very hot operating conditions. According to the report, the student pilot switched off the aircraft’s electric fuel pumps after leveling at circuit altitude, following normal procedures. As the aircraft entered the circuit pattern and later prepared for the touch-and-go maneuver, engine power settings were reduced, resulting in lower fuel flow and reduced cooling airflow through the engine compartments. Following touchdown and the subsequent takeoff, investigators believe heat accumulated within the engine cowling area, allowing fuel vapor to form in the fuel lines supplying the left engine. The resulting vapor lock interrupted fuel flow, causing rough running and loss of power in the left engine. The right engine later experienced a reduction in performance under similar environmental conditions, though investigators found evidence indicating it continued producing power throughout the forced landing sequence. While acknowledging the instructor initially applied correct asymmetric-flight techniques after the left-engine power loss, the report found several critical procedures outlined in the Aircraft Flight Manual (AFM) were not followed. Investigators determined that the failed left-engine propeller was not feathered, creating additional aerodynamic drag. The landing gear also remained extended, further degrading aircraft performance. The report additionally concluded that the instructor did not lower the aircraft’s pitch attitude sufficiently to preserve airspeed after the initial engine failure. As a result, airspeed decayed below the aircraft’s minimum control speed (VMCA), reducing controllability and climb capability. AAIB stated that the crew likely interpreted the right engine’s reduced performance as a complete engine failure, although evidence suggested the engine was still producing power. The investigation further noted that neither a left-engine failure call nor a Mayday transmission was made to air traffic personnel. AAIB also identified several organizational shortcomings at the flying school. Investigators found that FSTC had reduced local circuit altitude from the DGCA-approved 1,500 feet to 700 feet without formally amending its Training and Procedures Manual or obtaining regulatory approval. The investigation additionally criticized the emergency checklist carried onboard, describing it as a small single-page document that did not clearly describe actions required during various emergency situations. Another finding noted that the school did not utilize the aircraft’s built-in Garmin data-recording capability, despite the system being available. The report concluded that the aircraft was airworthy, properly maintained, loaded within limits, and carrying sufficient fuel. AAIB determined that the ambient temperature was close to the aircraft’s operational limit and conducive to vapor lock formation. Investigators also found that both crew members had comparatively limited experience on the Tecnam P2006T and that emergency procedures were not followed precisely after the initial engine power loss. The final probable cause stated that the accident occurred when the left engine encountered vapor lock and the right engine suffered a slight loss of power while operating in temperatures near the aircraft’s operational limit. The aircraft subsequently impacted the ground during a forced landing. Contributing factors identified by AAIB included non-adherence to Aircraft Flight Manual procedures and the pairing of two crew members with limited experience handling emergency situations on the aircraft type.

AAIB Final Report: Vapor Lock And Crew Actions Led To FSTC Tecnam P2006T Crash In 2022

Aviation Today News Desk June 7, 2026

Bhiwani, India: India’s Aircraft Accident Investigation Bureau (AAIB) has released its final investigation report into the accident involving Tecnam P2006T aircraft

New Delhi, India: India's Aircraft Accident Investigation Bureau (AAIB) has released its preliminary findings into the serious incident involving a Swiss International Air Lines Airbus A330-343 that suffered a left-engine failure during takeoff at Delhi's Indira Gandhi International Airport, forcing the crew to reject takeoff and conduct an emergency evacuation. The incident occurred shortly after 1:27 a.m. local time on April 26, 2026, when Swiss flight LX147 was preparing to depart Delhi for Zurich with 245 people onboard, including 232 passengers and 13 crew members. According to the AAIB report, the aircraft involved was a 2012-built Airbus A330-343, registered HB-JHK, powered by Rolls-Royce Trent 772B-60 engines. The aircraft had arrived in Delhi earlier that day, operating flight LX146 from Zurich. Investigators noted that the inbound Zurich–Delhi flight was uneventful. While seven maintenance complaints were logged after arrival, all were described as routine and unrelated to the aircraft's engines, flight controls, serviceability, or controllability. The reported issues were addressed before the aircraft was cleared for the return flight to Switzerland. No abnormalities were detected during pre-flight inspections before LX147's departure from Delhi. The aircraft, parked at Stand A14, received pushback and startup clearance before taxiing to Runway 28 via taxiway J6. At 01:25:56 IST, air traffic control cleared the flight for takeoff with light winds reported from 210 degrees at one knot. Moments later, during the takeoff roll, the aircraft accelerated to approximately 106 knots. According to cockpit reports cited by investigators, the crew heard a loud bang as the No. 1 engine experienced a failure. Pilots reported seeing a large flame projecting forward from the left engine and observed the aircraft veering left. The crew immediately rejected the takeoff and brought the aircraft to a stop on Runway 28 between taxiways G1 and G2. After stopping, the flight crew informed air traffic controllers of the engine failure and requested emergency services. Communications recorded by investigators show that airport vehicles and crash fire tenders responded rapidly. Initially, responders observed smoke around the aircraft. As emergency personnel continued assessing the situation, reports indicated smoke near the left landing gear and subsequently fire near the right landing gear area. Fire crews began firefighting operations while coordinating with air traffic controllers and the flight crew. At approximately 01:35 IST, a full airport emergency was declared. Following confirmation of smoke and fire indications, both engines were shut down. Emergency evacuation procedures were initiated directly on the runway. Seven of the aircraft's eight evacuation slides were deployed and used to evacuate passengers and crew. All occupants successfully exited the aircraft. Four passengers sustained injuries during the evacuation and were transported for medical treatment. Airport responders reported that the fire had been completely extinguished by approximately 01:50 IST. The aircraft was later towed from the runway and parked at a remote stand. The airport terminated the full emergency status at 04:50 IST. Data obtained from the aircraft's post-flight report showed the first recorded warning was an "ENG 1 Stall" message at 01:27 IST during the takeoff roll. This was followed by multiple system messages including "ENG 1 FAIL," "AIR PACK 1+2 FAULT," "F/CTL RUD TRIM 1 FAULT," and "ENG 1 REV UNLOCKED." An "ENG 1 SHUTDOWN" message was subsequently recorded after the aircraft came to a stop. Investigators conducted an external inspection of the aircraft and found metallic debris near the exhaust section of the left engine along with soot and burn marks on the engine pylon behind the exhaust area. Notably, no damage was observed on the engine fan blades, and investigators reported no significant structural damage to the aircraft apart from minor dents likely caused during emergency slide deployment. A borescope inspection of the failed engine revealed extensive internal damage. Investigators discovered broken bolts and spacers from the high-pressure/intermediate-pressure bearing support assembly within the thrust reverser ducts. High-pressure bleed valves were also partially blocked by debris. Further examination identified significant damage to components within the engine core, including the High Pressure Turbine, Intermediate Pressure Turbine, Low Pressure Turbine, and High Pressure Compressor sections. Both the high-pressure and intermediate-pressure shafts were seized, preventing complete inspection. The AAIB stated that although severe internal engine damage was identified, investigators were unable to determine the precise cause of the engine failure during the initial borescope examination because the engine's rotating assemblies could not be fully inspected. Importantly, investigators found no evidence of an uncontained engine failure. The failed Rolls-Royce Trent 772B-60 engine was manufactured in 2009 and had accumulated more than 75,500 operating hours and 11,369 flight cycles. Records show the engine's last overhaul occurred in May 2016. Since that overhaul, it had accumulated nearly 40,000 additional flight hours before the incident. Both cockpit crew members were appropriately licensed and qualified on the Airbus A330. The captain had more than 18,600 total flight hours, while the first officer had accumulated more than 2,170 hours. AAIB investigators have removed and downloaded data from both the cockpit voice recorder and flight data recorder. Analysis of the recorded information is ongoing. The bureau said the damaged engine will be removed from the aircraft for a detailed examination aimed at identifying the root cause of the failure. Investigators are also reviewing maintenance records, operational documentation, air traffic control recordings, and witness statements. The investigation includes participation from international authorities and technical experts. France's Bureau d'Enquêtes et d'Analyses (BEA), Airbus, the European Union Aviation Safety Agency (EASA), Germany's BFU, the United Kingdom's AAIB, and Rolls-Royce representatives are assisting the Indian investigation under the provisions of ICAO Annex 13. The AAIB emphasized that the findings released so far are preliminary and subject to change as the investigation progresses. No interim safety recommendations have been issued at this stage.

AAIB Preliminary Report Finds No Evidence Of Uncontained Failure In Swiss A330 Engine Incident

Aviation Today News Desk June 1, 2026

New Delhi, India: India’s Aircraft Accident Investigation Bureau (AAIB) has released its preliminary findings into the serious incident involving a Swiss

New Delhi, India: Indian investigators are preparing an interim report into last year’s fatal Air India Boeing 787 Dreamliner crash instead of a final report, as authorities continue examining one of the deadliest aviation disasters. According to Reuters, the Aircraft Accident Investigation Bureau (AAIB) is expected to issue the interim findings ahead of the first anniversary of the June 12, 2025 crash involving Air India Flight AI171, which was operating from Ahmedabad to London Gatwick. The accident killed 260 people after the Boeing 787-8 lost thrust moments after takeoff and crashed into a medical college hostel near the airport. The interim document will be “more comprehensive” than the 15-page preliminary report released in July 2025 and is expected to examine possible primary causes and contributing factors behind the crash. However, investigators said the final report is still not ready because of the complexity of the inquiry and the time required for additional analysis. The preliminary AAIB report found that the aircraft’s engine fuel control switches moved almost simultaneously from the “RUN” to “CUTOFF” position shortly after takeoff, starving both engines of fuel. Cockpit recordings reviewed during the investigation indicated confusion between the pilots over the movement of the switches. The early assessment by U.S. officials reviewing cockpit voice recordings supported the view that the captain may have cut fuel flow to the engines. Indian investigators, however, said at the time that it was “too early to reach any definite conclusions.” The ongoing investigation involves multiple international agencies because the aircraft was designed and manufactured in the United States. The U.S. National Transportation Safety Board (NTSB) is participating in the probe, while Boeing is assisting as a technical adviser. By issuing an interim report instead of a final one, Indian authorities will not be required to circulate draft findings in advance to the NTSB for review and comment. Under International Civil Aviation Organization (ICAO) rules, draft final reports are generally shared with participating states for consultation before publication. The investigation has gained renewed attention following a separate Air India Boeing 787 incident earlier this year involving fuel control switches. In February 2026, pilots operating a Dreamliner flight from London to Bengaluru reported that the fuel switches did not remain fixed in the “RUN” position during engine start attempts before stabilizing on a third attempt. Indian aviation regulator Directorate General of Civil Aviation (DGCA) officials are expected to travel to Boeing facilities in Seattle in June to observe testing of the fuel switch panel from that aircraft. Under international aviation standards, a final accident report is generally expected within one year of a crash. If the investigation remains incomplete, authorities are required to issue an interim statement outlining progress in the inquiry. Investigators said work on the final report is continuing and no timeline has been confirmed for its release.

Report: India Preparing Interim Report On Fatal Air India Boeing 787 Crash Investigation

Aviation Today News Desk May 28, 2026

New Delhi, India: Indian investigators are preparing an interim report into last year’s fatal Air India Boeing 787 Dreamliner crash instead

AAIB Flags Civil-Military ATC Coordination Lapses In Air India-Navy Helicopter Near Miss

Aviation Today News Desk May 24, 2026

Port Blair, India: India’s Aircraft Accident Investigation Bureau (AAIB) has released its final investigation report into a serious midair proximity incident

Paris, France: A Paris appeals court has found Air France and Airbus guilty of corporate manslaughter over the 2009 crash of Air France Flight 447, overturning a previous acquittal and marking a major turning point in one of the aviation industry’s longest-running criminal cases. The ruling, delivered on May 21, 2026, comes nearly 17 years after the Airbus A330 operating the Rio de Janeiro-Paris service crashed into the Atlantic Ocean, killing all 228 people onboard. The tragedy remains the deadliest accident in Air France’s history and the worst crash involving an Airbus A330 aircraft. The appeals court imposed the maximum corporate manslaughter fine permitted under French law €225,000 each on both companies. Although financially minor for two global aviation giants, the verdict carries significant symbolic and legal weight after years of investigations, trials, appeals, and pressure from victims’ families. Flight AF447 departed Rio de Janeiro on June 1, 2009, bound for Paris Charles de Gaulle Airport with 216 passengers and 12 crew members onboard. During cruise over the Atlantic Ocean, the aircraft encountered severe weather and icing conditions at high altitude. Investigators later determined that ice crystals blocked the aircraft’s pitot tube sensors responsible for measuring airspeed causing inconsistent speed readings and forcing the autopilot to disconnect. According to the final investigation, the pilots reacted incorrectly after the sensor failure. The aircraft entered a high-altitude aerodynamic stall from which the crew failed to recover before the Airbus plunged into the ocean. Cockpit recordings later revealed confusion inside the flight deck as the pilots struggled to understand the aircraft’s condition during the final minutes of the flight. The court concluded that both Air France and Airbus bore criminal responsibility for the disaster. Judges ruled that Airbus had prior knowledge of recurring pitot tube icing issues affecting A330 aircraft but failed to respond quickly enough to eliminate the risk. Prosecutors argued that the manufacturer underestimated the seriousness of the known defect despite earlier incidents involving unreliable airspeed indications. Air France, meanwhile, was criticized for inadequate pilot training regarding high-altitude manual handling, stall recovery procedures, and unreliable airspeed scenarios. The court found that pilots had not received sufficient preparation to manage the type of emergency that unfolded aboard AF447. The judgment reverses a 2023 lower-court acquittal in which both companies had escaped criminal liability despite widespread criticism from victims’ families and aviation experts. Under the French legal system, the appeals process allowed the entire case to be retried from the beginning. Families of victims welcomed the ruling as long-overdue recognition of corporate accountability, though many described the fines as merely symbolic. Several relatives said the decision represented moral justice after years of legal frustration, while others argued true accountability would require criminal action against individual executives rather than corporations alone. Brazilian victims’ association leader Nelson Faria Marinho said justice was still incomplete, arguing that no senior officials had personally faced criminal consequences despite the scale of the disaster. The case also reignited debate within the aviation industry over the balance between pilot error and systemic corporate responsibility. During proceedings, lawyers representing Airbus and Air France repeatedly emphasized that the immediate cause of the crash was the crew’s inability to recover the aircraft from stall conditions. Prosecutors, however, maintained that the pilots were placed in an avoidable situation because of failures in design risk management and operational training. The wreckage of AF447 was not fully located until 2011 after an extensive deep-sea search operation nearly 4,000 meters below the Atlantic Ocean surface. Recovery of the flight data recorder and cockpit voice recorder proved crucial in reconstructing the sequence of events that led to the crash. The disaster triggered major changes across the global aviation industry. Airlines and regulators revised pilot training programs to place greater emphasis on manual flying skills, high-altitude stall recovery, and automation management. Manufacturers also introduced modifications to pitot tube systems and operational procedures following the accident. Both Airbus and Air France are expected to challenge the verdict before France’s highest appeals court, potentially extending legal proceedings even further. Airbus has already confirmed plans to appeal, while Air France had not publicly commented immediately after the judgment.

Air France, Airbus Found Guilty Of Manslaughter In 2009 AF447 Crash That Killed 228

Aviation Today News Desk May 22, 2026

Paris, France: A Paris appeals court has found Air France and Airbus guilty of corporate manslaughter over the 2009 crash of

Wuzhou, China: The crash of China Eastern Airlines Flight 5735 crash continues to raise critical questions more than four years after the disaster, as newly surfaced U.S. investigative data points toward deliberate cockpit actions while Chinese authorities maintain silence, citing national security concerns. On March 21, 2022, a Boeing 737-800 operated by China Eastern Airlines plunged from cruising altitude into mountainous terrain in Guangxi, killing all 132 passengers and crew on board. The aircraft, en route from Kunming to Guangzhou, entered a near-vertical descent from approximately 29,000 feet, leaving investigators initially baffled due to the absence of distress calls or clear external triggers. Early findings released by the Civil Aviation Administration of China (CAAC) ruled out conventional causes such as mechanical failure, severe weather, or hazardous cargo. The aircraft was deemed airworthy, the crew qualified and medically fit, and no evidence of explosives was found. Flight data and cockpit voice recorders were recovered and analyzed with assistance from international agencies, including the National Transportation Safety Board (NTSB), yet interim reports issued between 2022 and 2024 stopped short of identifying a definitive cause, describing the event as “very complicated and very rare.” Attention began to shift toward possible human involvement after early assessments indicated that control inputs from the cockpit forced the aircraft into its steep descent. However, no official conclusion was publicly endorsed, and the investigation appeared to stall as updates from Chinese authorities became increasingly limited. A significant breakthrough emerged in 2026 following the release of previously undisclosed materials through a Freedom of Information Act (FOIA) request to the NTSB. According to flight data recorder analysis, both engine fuel control switches were moved to the “cutoff” position approximately 23 seconds before the recording ceased. This action resulted in an immediate loss of engine thrust, followed by autopilot disengagement and aggressive forward control inputs that drove the aircraft into a rapid descent. The loss of electrical power shortly afterward caused the recorder to stop, leaving the final moments of the flight undocumented. The cockpit voice recorder, which continued operating briefly on backup power, was successfully recovered and analyzed. However, its contents have not been made public. The NTSB confirmed that it does not retain copies of the audio, and access remains under the control of Chinese authorities, making it a crucial yet unavailable piece of evidence in determining the sequence of events inside the cockpit. While the available data suggests that the shutdown of both engines was unlikely to be accidental and is consistent with deliberate manual input, investigators have not identified which pilot may have acted or under what circumstances. The data also does not establish motive, leaving open possibilities ranging from intentional action to incapacitation or other in-flight scenarios. Reports speculating about a possible struggle in the cockpit have surfaced in some media outlets but remain unverified and are not part of any confirmed investigative findings. Despite the emergence of these critical details, the CAAC has yet to release a final accident report, well beyond the timeline prescribed under international aviation norms. Officials have indicated that disclosing further information could endanger national security or disrupt social stability, an explanation that has drawn concern from global aviation bodies and safety experts. Under standard practices, accident investigations are expected to produce a final report within one year to ensure that safety lessons are shared across the industry. The continued lack of transparency has left several fundamental questions unanswered. Without access to the cockpit voice recordings and a comprehensive official report, the exact cause of the crash remains unresolved.

NTSB Data Suggests Possible Deliberate Engine Shutdown In MU5735 Crash That Killed 132

Aviation Today News Desk May 6, 2026

Wuzhou, China: The crash of China Eastern Airlines Flight 5735 crash continues to raise critical questions more than four years after

El Alto, Bolivia: Bolivian authorities have arrested the pilot and co-pilot of a Bolivian Air Force Lockheed C-130H Hercules following an official investigation that concluded the February 2026 crash near La Paz was preventable and largely linked to operational errors during landing. The aircraft crashed on February 27, 2026, while attempting to land at El Alto International Airport, after completing a domestic flight from Santa Cruz. During landing in adverse weather, the aircraft failed to decelerate on the runway, veered off the surface, breached the airport perimeter, and ploughed into a busy roadway, striking multiple vehicles before breaking apart in a densely populated area. The crash resulted in 24 fatalities and at least 43 injuries, with the majority of victims on the ground. Among the dead were civilians, including passengers in public transport vehicles hit by the aircraft. Several crew members were also injured, making it one of Bolivia’s deadliest aviation disasters in recent decades. Initial reports had indicated a lower death toll, but the number rose significantly as rescue teams recovered victims from the wreckage and surrounding impact zone. The situation on the ground quickly descended into chaos after it emerged that the aircraft was transporting a large consignment of newly printed banknotes for the Central Bank of Bolivia. The impact scattered currency across the crash site, drawing crowds of civilians who rushed to collect the money. Authorities deployed police and military units, including the use of tear gas, to secure the area and allow emergency responders to operate. Officials later declared the banknotes invalid, as they had not yet entered circulation, and subsequently destroyed recovered cash. A formal investigation by the Bolivian Air Force, the findings of which were released on April 30, 2026, identified a chain of operational failures rather than a single-point cause. Investigators determined that adverse weather conditions, including a wet runway and reduced braking efficiency, were contributing factors but not the primary cause. Instead, the report placed significant emphasis on pilot handling during the landing phase. According to the findings, the aircraft executed an improper landing sequence, touching down with the nose gear before the main landing gear, a critical procedural error that compromised braking effectiveness and aircraft stability. This technique reduced aerodynamic drag and delayed the full deployment of braking systems, significantly increasing stopping distance on an already wet runway. The report further highlighted inadequate coordination and communication with air traffic control, which may have affected situational awareness during the final approach and landing rollout. Investigators also pointed to failure to execute a go-around despite unstable landing conditions, a decision that could have prevented the accident altogether. Additionally, the probe noted that standard landing protocols and safety margins were not maintained, particularly given the weather conditions. The combination of these factors resulted in a runway excursion at high speed, leaving the crew unable to regain control before the aircraft exited the airfield boundary. Crucially, investigators concluded that the crash was preventable, stating that proper adherence to established landing procedures and timely decision-making would likely have avoided the accident. Based on these findings, Bolivian prosecutors issued arrest warrants for the pilot and co-pilot on April 30, with both taken into custody on May 1, 2026, following questioning. The two are currently being held in pre-trial detention and face charges of involuntary manslaughter, with authorities alleging that negligent handling of the aircraft and failure to follow standard operating procedures directly contributed to the loss of life.

Pilot & Co-Pilot Arrested After Probe Finds Errors In Bolivian Military Plane Crash

Aviation Today News Desk May 4, 2026

El Alto, Bolivia: Bolivian authorities have arrested the pilot and co-pilot of a Bolivian Air Force Lockheed C-130H Hercules following an

$Houston, United States: The National Transportation Safety Board (NTSB) has released its final investigation report into a rejected takeoff and emergency evacuation involving a United Airlines Airbus A319 in Houston, concluding that breakdowns in crew coordination and escalating passenger panic significantly increased risk during the incident. The occurrence took place on February 2, 2025, at 08:16 local time at George Bush Intercontinental Airport. United Airlines Flight 1382, bound for New York LaGuardia, was accelerating for departure when a loud bang was heard from the right engine, followed by an “ENG 2 FAIL” indication. The aircraft had not yet reached decision speed when the flight crew rejected the takeoff and brought the jet to a stop on the runway. All 112 occupants, 107 passengers and five crew members remained unharmed. According to the final report, the incident was triggered by a failure within the right engine’s high-pressure compressor. A detailed teardown later confirmed that a third-stage rotor blade fractured due to high cycle fatigue after accumulating more than 40,000 flight hours and over 19,500 cycles. The failure caused internal damage to the engine but remained contained, preventing further structural consequences to the aircraft. What followed inside the cabin, however, became the central focus of the investigation. Despite repeated instructions from both pilots and cabin crew to remain seated, several passengers began shouting that the engine was on fire. Panic quickly spread, particularly in the rear cabin, where passengers stood up, retrieved carry-on baggage, and moved toward the exits. Cabin crew efforts to restore order were increasingly ineffective as congestion built in the aisle and near the aft galley. Faced with escalating pressure and unable to establish communication with the cockpit, a flight attendant initiated an evacuation from the rear left door without direct authorization from the flight crew. Investigators found that the evacuation alarm was not activated, a critical procedural step designed to alert the cockpit and coordinate actions. As a result, the evacuation began while the aircraft’s left engine was still running. The premature opening of the rear left door created a hazardous situation. The evacuation slide deployed into the exhaust airflow of the operating engine, causing it to whip violently and twist for nearly 100 seconds. During this period, three passengers descended the slide before it fully stabilized. The slide subsequently deflated after a structural component failed under stress, rendering the exit unusable. Evacuation was then redirected to the rear right door, where the slide deployed normally and passengers were able to exit safely. The investigation determined that the slide failure was not due to manufacturing defects but was caused by structural overload when exposed to engine exhaust forces beyond its design limits. Safety analysis confirmed that evacuation slides are not certified to operate under such conditions, underscoring the risks of initiating evacuation procedures without full engine shutdown. The NTSB’s final report, published on April 29, 2026, identified the probable cause as the failure of the cabin crew to activate the evacuation alarm and maintain effective communication with the flight crew after deciding to evacuate. This breakdown resulted in passengers evacuating while an engine remained operational. The report also highlighted passenger noncompliance as a major contributing factor, noting that individuals ignored instructions, retrieved baggage, and in some cases forced access to exits, accelerating the breakdown of order in the cabin. The findings align with longstanding safety concerns about passenger behavior during emergencies. The Federal Aviation Administration has repeatedly warned that retrieving carry-on baggage during evacuations can delay egress and increase risk. In response to similar incidents, the agency issued Safety Alert for Operators (SAFO) 25003 in September 2025, urging airlines to strengthen passenger briefings and improve communication strategies to discourage such behavior. No injuries were reported in this incident, investigators emphasized that the outcome could have been far more serious.$

NTSB Finds Crew Lapses, Passenger Panic In United A319 Houston Evacuation Event Probe

Aviation Today News Desk May 1, 2026

Houston, United States: The National Transportation Safety Board (NTSB) has released its final investigation report into a rejected takeoff and emergency

In-Flight Photo Attempt Blamed For South Korean F-15K Jet Collision, Audit Reveals

Aviation Today News Desk April 23, 2026

Daegu, South Korea: A mid-air collision between two Republic of Korea Air Force F-15K fighter jets has been attributed to pilot

Investigation

Loose Bolt Left Undetected During Inspection Caused New Zealand Airbus AS350 Crash

AAIB Final Report: Vapor Lock And Crew Actions Led To FSTC Tecnam P2006T Crash In 2022

AAIB Preliminary Report Finds No Evidence Of Uncontained Failure In Swiss A330 Engine Incident

Report: India Preparing Interim Report On Fatal Air India Boeing 787 Crash Investigation

AAIB Flags Civil-Military ATC Coordination Lapses In Air India-Navy Helicopter Near Miss

Air France, Airbus Found Guilty Of Manslaughter In 2009 AF447 Crash That Killed 228

NTSB Data Suggests Possible Deliberate Engine Shutdown In MU5735 Crash That Killed 132

Pilot & Co-Pilot Arrested After Probe Finds Errors In Bolivian Military Plane Crash

NTSB Finds Crew Lapses, Passenger Panic In United A319 Houston Evacuation Event Probe

In-Flight Photo Attempt Blamed For South Korean F-15K Jet Collision, Audit Reveals

Follow Us

Quick Links

Navigate

General Support

News Desk Support

Follow Us