AirlineSafety Archives - Aviation Today

New Delhi, India: The Federation of Indian Pilots (FIP) has intensified its challenge to the emerging narrative surrounding the Air India Flight 171 crash investigation, arguing that critical technical questions remain unanswered and urging investigators to conduct additional simulator testing before issuing a final report. Addressing a press conference on June 20, FIP President Captain C. S. Randhawa disputed suggestions that the Boeing 787's fuel control switches were deliberately moved by the flight crew, stating that “the pilots have actually not moved the switches.” The remarks come amid growing scrutiny of the Aircraft Accident Investigation Bureau's (AAIB) preliminary findings into the June 12, 2025 crash of Air India Flight 171, which killed 260 people shortly after departure from Ahmedabad. The AAIB's preliminary report concluded that both engine fuel control switches transitioned from RUN to CUTOFF shortly after takeoff, resulting in the loss of fuel supply to both engines. Cockpit voice recordings reportedly captured one pilot asking the other why the fuel had been cut off, with the second pilot denying responsibility. However, FIP argues that the preliminary findings leave several critical issues unresolved. According to Randhawa, the report failed to include cockpit warning sequences that would normally accompany a significant electrical malfunction. The federation contends that if an electrical disturbance occurred before the engines lost power, the cockpit voice recorder should contain caution messages, warning alerts and associated audio warnings that were not discussed in the preliminary findings. Randhawa also questioned why investigators allegedly did not give sufficient weight to the testimony of the crash's sole survivor, Vishwash Kumar Ramesh. According to Randhawa, Ramesh reported seeing lights flickering inside the cabin shortly after the aircraft became airborne. The FIP president argued that this observation could be a significant clue pointing toward a possible electrical malfunction, noting that cabin lights are normally configured for takeoff and should not have been flickering under normal conditions. He said the survivor's account, when considered alongside technical material submitted by the federation regarding electrical-system anomalies and transmitted fault codes, warranted a deeper examination of a potential electrical-failure scenario rather than an exclusive focus on pilot actions. Randhawa maintained that the survivor's statement could represent an important piece of evidence in understanding the chain of events that led to the crash. FIP further highlighted Aircraft Communications Addressing and Reporting System (ACARS) maintenance messages transmitted around the time of departure. The federation has requested that Air India provide the original ACARS records and that Boeing assist investigators in decoding the data to determine whether any technical abnormalities were present before the accident. Another area of concern involves the Full Authority Digital Engine Control (FADEC) system. FIP has urged investigators to examine whether a malfunction or protective system response within the engine-control architecture could have contributed to the simultaneous loss of power. The federation has additionally questioned the condition of the flight data recorder recovered from the aircraft, arguing that the extent of recorder damage appears inconsistent with reports that much of the tail section remained relatively intact. Randhawa also questioned why Captain Sandhu, who he described as an experienced Boeing 787 pilot, had not been involved in the investigation. FIP has formally written to the Prime Minister's Office, the Ministry of Civil Aviation, the Directorate General of Civil Aviation and the AAIB, requesting fresh simulator testing and a broader technical review before publication of the final accident report. The pilots' organization maintains that technical explanations have not been fully exhausted and warns against attributing blame to the flight crew while several lines of inquiry remain open. The final report into the crash has not yet been released, with investigators continuing engine analysis and other technical examinations. Aviation authorities have repeatedly urged caution against speculation, emphasizing that the investigation remains ongoing.

Indian Pilot’s Body: AI171 Pilots Did Not Move Fuel Switches, Calls For Simulator Tests

Aviation Today News Desk / June 21, 2026

New Delhi, India: The Federation of Indian Pilots (FIP) has intensified its challenge to the emerging narrative surrounding the Air […]

Incidents

Virgin Australia Boeing 737 Returns To Melbourne After Mid-Air Engine Issue

Aviation Today News Desk / June 16, 2026

Melbourne, Australia: A Virgin Australia Boeing 737-800 operating a scheduled domestic service from Melbourne to Perth was forced to return

Washington, United States: A United Airlines Boeing 737-900 operating a scheduled domestic flight was forced to return to Washington Dulles International Airport after the flight crew reported a nose landing gear issue shortly after departure. The incident involved United Airlines Flight 1535, which departed Washington Dulles International Airport (IAD) for Houston George Bush Intercontinental Airport (IAH) on June 9, 2026. According to the Federal Aviation Administration (FAA), the aircraft returned safely to Dulles after pilots reported a problem involving the nose landing gear. FAA officials said the Boeing 737-900 landed safely at approximately 2:05 p.m. local time and confirmed that the agency will investigate the occurrence. Flight tracking data showed that the aircraft departed Dulles at approximately 12:57 p.m. local time and remained airborne for more than an hour before returning to the airport. United Airlines confirmed that the aircraft returned to Washington Dulles as a precaution to address the issue. “The flight returned safely to the airport to address the issue, and we made arrangements to get customers to their destinations,” the airline said in a statement. Emergency response teams were positioned as a precaution when the aircraft arrived back at the airport. The Metropolitan Washington Airports Authority confirmed that its fire and rescue personnel met the aircraft upon landing. The aircraft landed without incident and subsequently taxied to the gate under its own power. Airport officials stated that the emergency return did not affect normal airport operations and that no injuries were reported among passengers or crew. To minimize disruption, United arranged alternative travel options for affected passengers. Flight records indicate that another flight later departed Washington Dulles for Houston and completed the journey successfully. The aircraft involved was a Boeing 737-900, one of the largest variants of the 737 Next Generation family widely used on domestic routes throughout the United States. The FAA investigation is expected to determine the precise cause of the reported nose landing gear issue and whether any mechanical, maintenance, or operational factors contributed to the event.

Incidents

United Airlines Boeing 737 Returns To Washington Dulles After Nose Landing Gear Issue

Aviation Today News Desk / June 12, 2026

Washington, United States: A United Airlines Boeing 737-900 operating a scheduled domestic flight was forced to return to Washington Dulles

Incidents

Virgin Atlantic Flight Makes Emergency Landing In Ireland After Engine Malfunction

Aviation Today News Desk / June 1, 2026

Shannon, Ireland: A Virgin Atlantic Airbus A330-900neo operating a scheduled service from London Heathrow to Montego Bay, Jamaica, made an

Minneapolis, United States: A United Airlines flight from Chicago to Minneapolis was met by law enforcement after a passenger allegedly attempted to breach the cockpit during the flight, triggering a major security response. The incident occurred on May 29, aboard a United Airlines service traveling from Chicago O'Hare International Airport (ORD) to Minneapolis–Saint Paul International Airport (MSP). During the flight, a passenger allegedly became disruptive and attempted to move toward the flight deck area, triggering an immediate response from cabin crew and flight personnel. Flight attendants and crew members reportedly intervened to prevent access to the cockpit, while the flight crew coordinated with air traffic control and law enforcement authorities. The aircraft subsequently landed safely, where police and security personnel met the flight upon arrival. Reports indicate that the situation prompted the activation of a heightened security response, with references made to a "Level 4" threat classification. However, U.S. aviation authorities and United Airlines have not publicly issued detailed statements explaining the specific classification or confirming the exact security designation. No injuries were immediately reported among the 147 passengers and six crew members and authorities took the passenger into custody following the aircraft's arrival. Investigations into the incident remain ongoing. A Level 4 threat generally refers to a severe security situation that requires immediate operational response and enhanced coordination among flight crews, airport authorities, law enforcement agencies, and federal security personnel. Such alerts may be associated with potential unlawful interference with flight operations, attempted cockpit intrusion, credible hijacking concerns, or situations that could pose a direct threat to aircraft safety. The exact terminology and classification systems can vary between agencies, airlines, airports, and security organizations. Earlier in May, United Airlines Flight 1837 operating to Newark Liberty International Airport experienced a security incident after a passenger allegedly attacked a flight attendant and attempted to gain access to the flight deck area. The aircraft landed safely and the passenger was detained by authorities. A separate United Airlines flight operating from Newark to Guatemala City was also forced to divert after a passenger allegedly attempted to open a cabin door during flight, prompting an emergency response and law enforcement action upon landing. Authorities have not announced whether federal charges will be filed in connection with the latest Chicago-Minneapolis incident. Investigators are expected to review crew reports, passenger statements, onboard security procedures, and any available cabin surveillance evidence as part of the inquiry. United Airlines has not publicly disclosed additional details regarding the passenger involved or the precise sequence of events leading to the reported cockpit breach attempt.

Incidents

United Flight Hit By Security Scare After Alleged Cockpit Breach Attempt By A Passenger

Aviation Today News Desk / May 30, 2026

Minneapolis, United States: A United Airlines flight from Chicago to Minneapolis was met by law enforcement after a passenger allegedly

Narita, Japan: A Japan Airlines (JAL) Boeing 767 operating a domestic service from Tokyo Haneda Airport (HND) to Kagoshima Airport (KOJ) made an emergency landing at Narita International Airport (NRT) on May 29 after a suspected tire failure during takeoff prompted the crew to divert the aircraft. The aircraft, carrying 218 passengers and eight crew members, landed safely at Narita at approximately 11:55 a.m. local time. No injuries were reported among those on board. According to Japan's Ministry of Land, Infrastructure, Transport and Tourism (MLIT) and local media reports, the incident began shortly after departure from Haneda Airport when the crew detected a problem believed to be related to the aircraft's landing gear tires. As a precaution, the Boeing 767 discontinued its planned flight to Kagoshima and diverted to Narita, where emergency services were positioned ahead of the landing. The aircraft touched down without further incident and passengers later disembarked safely. Airport and transport authorities immediately launched an investigation into the occurrence. The incident resulted in temporary operational disruptions at both airports. Following the emergency landing, Narita Airport's Runway A was closed for approximately two hours while officials inspected the aircraft and conducted safety assessments. Airport operations later resumed after the runway was cleared for use. Meanwhile, officials at Haneda Airport discovered debris on Runway D, the same runway used by the JAL aircraft for departure. Authorities temporarily closed the runway beginning around 10:30 a.m. to determine whether the debris originated from the Boeing 767. After inspections were completed, Runway D reopened at approximately 1:45 p.m. However, investigators have not yet confirmed whether the debris was connected to the Japan Airlines aircraft. Further details indicated that the aircraft conducted a low approach inspection, during which damage was reportedly observed on two forward tires of the main landing gear. The report suggested the event may have involved more extensive tire damage than initially believed. There were no reported injuries among the 226 occupants onboard and the aircraft landed safely following the occurrence.

Incidents

Japan Airlines Diverts To Narita After Suspected Tire Failure On Takeoff From Tokyo

Aviation Today News Desk / May 30, 2026

Narita, Japan: A Japan Airlines (JAL) Boeing 767 operating a domestic service from Tokyo Haneda Airport (HND) to Kagoshima Airport

Airlines

FAA Proposes Penalty Against Alaska Airlines Over Alleged Intoxicated Passenger Boarding

Aviation Today News Desk / May 29, 2026

Washington, United States: The U.S. Federal Aviation Administration (FAA) has proposed a civil penalty of $165,000 against Alaska Airlines after

Lucknow, India: An Akasa Air Boeing 737 MAX 8 operating from Bengaluru to Bhubaneswar made an emergency landing at Lucknow’s Chaudhary Charan Singh International Airport on May 27 after the flight encountered adverse weather conditions at its destination and subsequently reported low fuel levels during diversion. The flight, operating as QP1503 and registered as VT-YAJ, was carrying a total of 194 passengers and crew members onboard when the incident occurred. According to multiple media reports and airport officials, the aircraft was initially unable to land at Bhubaneswar due to unfavorable weather conditions. The flight was subsequently diverted to Lucknow at approximately 8:40 PM local time. While approaching Lucknow, the crew reportedly issued a “PAN PAN” call to Air Traffic Control (ATC) at around 9:02 PM after fuel levels became critically low during the extended diversion. In aviation terminology, a “PAN PAN” declaration indicates an urgent situation requiring priority assistance, though it is considered less severe than a “MAYDAY” distress call. The pilot-in-command requested priority handling and a clear approach to ensure the aircraft could land safely in a single attempt amid fuel constraints. Following the alert, Lucknow ATC declared a full emergency and immediately activated standard emergency response procedures. Crash fire tenders and emergency response teams were positioned at designated points along Runway 09 by approximately 9:04 PM as a precautionary measure. The aircraft landed safely at Lucknow International Airport at around 9:21 PM. Shortly after touchdown, the flight crew informed ATC that all aircraft operations were normal and that no emergency assistance was required. Authorities subsequently withdrew the full emergency status at approximately 9:30 PM. Airport officials confirmed that all emergency and safety protocols were executed as per standard operating procedures and that the situation was handled without incident. No injuries to passengers or crew were reported. According to reports, three passengers deboarded the aircraft in Lucknow before the flight later resumed its journey to Bhubaneswar. In an official statement, Akasa Air confirmed that the diversion was caused by adverse weather conditions at Bhubaneswar and stated that the crew followed all established operational and safety procedures throughout the incident. “Akasa Air flight QP 1503 operating from Bengaluru to Bhubaneswar on 27 May 2026 was diverted to Lucknow due to adverse weather conditions, which were not favourable for landing. The pilot followed all established operational and safety protocols in line with standard procedures,” the airline said. The carrier further stated that the flight later departed Lucknow and landed safely in Bhubaneswar at 00:02 hrs on May 28. “At Akasa Air, the safety and well-being of our passengers and crew remain our highest priority. We regret the inconvenience caused due to circumstances beyond our control and appreciate our passengers’ understanding,” the airline added.

Incidents

Akasa Air Flight Diverts To Lucknow After Weather Disruption And Low Fuel Alert

Aviation Today News Desk / May 29, 2026

Lucknow, India: An Akasa Air Boeing 737 MAX 8 operating from Bengaluru to Bhubaneswar made an emergency landing at Lucknow’s

Hong Kong, China: A Cathay Pacific Airbus A350-900 operating flight CX156 from Brisbane to Hong Kong encountered severe turbulence during the early hours of May 23, injuring 10 people and forcing emergency medical assistance upon arrival at Hong Kong International Airport. The aircraft, identified as an Airbus A350-941 registered B-LRV, departed Brisbane shortly after midnight and was approximately two hours from landing in Hong Kong when the turbulence struck unexpectedly during breakfast service in the economy cabin. Cathay Pacific confirmed that six cabin crew members and four passengers sustained injuries in the incident. Eight of them were later transported to hospitals in Hong Kong for further medical treatment and observation after the aircraft landed safely at approximately 6:45 a.m. local time, a Cathay spokesman said. Passengers onboard described scenes of panic as the aircraft suddenly dropped in altitude for several seconds. One traveler compared the experience to “free-falling from a drop tower,” while others reported hearing screams throughout the cabin as unsecured items, food trays, coffee cups and mobile phones were thrown into the air. The turbulence reportedly occurred without prior warning while cabin crew were actively serving meals in the aisles, leaving many passengers and crew unrestrained at the time of impact. Several overhead lockers reportedly opened during the violent jolts, while food carts overturned and cabin debris scattered across the aircraft interior. Some reports also indicated that oxygen masks deployed in parts of the cabin following the sudden movement. Photographs circulating on social media after the incident showed extensive cabin disruption, including food-covered aisles, damaged service equipment and scattered personal belongings. One injured flight attendant was reportedly seen being transported in a neck brace after landing. Several passengers said the turbulence appeared to originate from an unexpected weather system or thunderstorm activity encountered during night operations. One passenger said there had been no seatbelt warning prior to the event and speculated that a storm cell may not have been visible on radar in the darkness. However, aviation observers and later reports suggested the aircraft may have encountered severe clear-air turbulence, which can occur suddenly without visible cloud formations or advanced warning to pilots. Medical professionals traveling onboard reportedly assisted injured passengers and crew members for the remainder of the flight until emergency responders boarded the aircraft in Hong Kong. Airport medical teams and ambulances had been placed on standby before arrival after authorities were informed of the turbulence event. Cathay Pacific said the affected passengers and crew received immediate care following the landing and stated that safety remains the airline’s highest priority. The carrier added that it would continue providing assistance to those injured.

Incidents

Cathay Pacific A350 Hit By Severe Turbulence, 10 Injured On Brisbane-Hong Kong Flight

Aviation Today News Desk / May 25, 2026

Hong Kong, China: A Cathay Pacific Airbus A350-900 operating flight CX156 from Brisbane to Hong Kong encountered severe turbulence during

Bangalore, India: An Air India Airbus A321 operating flight AI2651 from Delhi to Bengaluru suffered a tail-strike incident while landing at Bengaluru’s Kempegowda International Airport on Thursday morning, prompting the airline to ground the aircraft for detailed technical inspections. The incident occurred during the landing phase of the domestic service arriving from Delhi. According to airline officials and multiple media reports, the aircraft landed safely and all passengers and crew members disembarked normally without injuries. The aircraft encountered wake turbulence while approaching the runway at Bengaluru airport. The turbulence was reportedly generated by a departing wide-body aircraft operating nearby at the time of the approach. As the Airbus A321 approached for landing, the pilots initiated a precautionary go-around manoeuvre after experiencing unstable conditions caused by the wake turbulence. During the manoeuvre, the aircraft’s rear lower fuselage reportedly made contact with the runway, resulting in the tail strike. Air India confirmed the occurrence in an official statement, saying the aircraft “experienced a tail-strike during landing.” The airline added that the aircraft has since been withdrawn from service for comprehensive inspections and engineering assessments. The aircraft involved was a narrow-body Airbus A321 operating the Delhi–Bengaluru sector as AI2651. Flight-tracking data also identified the aircraft as an Airbus A321neo variant typically deployed on high-density domestic routes. The aircraft was carrying 181 people, including crew members onboard during the incident. Following the incident, Air India cancelled the return Bengaluru–Delhi service AI2652. The airline stated that alternative travel arrangements were being made for affected passengers while ground staff in Bengaluru were assisting travellers with rebooking and support services. The airline further said the incident would be investigated in coordination with relevant aviation regulatory authorities and under established operational safety procedures.

Incidents

Air India A321 Suffers Tail Strike During Bengaluru Landing, Aircraft Grounded

Aviation Today News Desk / May 22, 2026

Bangalore, India: An Air India Airbus A321 operating flight AI2651 from Delhi to Bengaluru suffered a tail-strike incident while landing

AirlineSafety

Indian Pilot’s Body: AI171 Pilots Did Not Move Fuel Switches, Calls For Simulator Tests

Virgin Australia Boeing 737 Returns To Melbourne After Mid-Air Engine Issue

United Airlines Boeing 737 Returns To Washington Dulles After Nose Landing Gear Issue

Virgin Atlantic Flight Makes Emergency Landing In Ireland After Engine Malfunction

United Flight Hit By Security Scare After Alleged Cockpit Breach Attempt By A Passenger

Japan Airlines Diverts To Narita After Suspected Tire Failure On Takeoff From Tokyo

FAA Proposes Penalty Against Alaska Airlines Over Alleged Intoxicated Passenger Boarding

Akasa Air Flight Diverts To Lucknow After Weather Disruption And Low Fuel Alert

Cathay Pacific A350 Hit By Severe Turbulence, 10 Injured On Brisbane-Hong Kong Flight

Air India A321 Suffers Tail Strike During Bengaluru Landing, Aircraft Grounded

Follow Us

Quick Links

Navigate

General Support

News Desk Support

Follow Us