Skip to content

Facebook Instagram Linkedin X-twitter Youtube

About Us
Contact Us
Advertisement

About Us
Contact Us
Advertisement

Aviation Newsletter

WhatsApp Channel

Search

News
Pilot Training
Flight School Analysis
Civil Aviation
Aviation Jobs
Training
Services
More

News
Pilot Training
Flight School Analysis
Civil Aviation
Aviation Jobs
Training
Services
More

Search

News
Pilot Training
Flight School Analysis
Civil Aviation
Aviation Jobs
Training
Services
More

News
Pilot Training
Flight School Analysis
Civil Aviation
Aviation Jobs
Training
Services
More

News

Civil Aviation

Pilot Training

Flight School Analysis

Aviation Jobs

Training

Services

About Us

Contact Us

Search

Aviation Today News Desk

2 Taiwanese Air Force Pilots Killed In Trainer Aircraft Crash During Training Exercise

June 2, 2026

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

June 1, 2026

Virgin Atlantic Flight Makes Emergency Landing In Ireland After Engine Malfunction

June 1, 2026

Hyderabad, India: A disruption occurred on May 31 when an IndiGo flight scheduled to operate from Hyderabad to Nagpur was cancelled before departure after a technical fault was detected. The cancellation also affected the corresponding return service from Nagpur to Hyderabad. The airline has not released details regarding the specific technical issue involved in the cancellation, nor has it disclosed the number of passengers affected. The affected travelers were offered assistance and accommodated on alternate flight arrangements. In a separate incident an IndiGo aircraft en route from Bengaluru to Nagpur made a precautionary landing at Hyderabad's Rajiv Gandhi International Airport after the flight crew reported a technical snag while the aircraft was airborne. The incident occurred on May 29 when an IndiGo flight operating from Bengaluru to Nagpur was forced to divert to Hyderabad after pilots detected a suspected technical malfunction during the flight. The aircraft, carrying 126 passengers, landed safely at Rajiv Gandhi International Airport, where emergency services were placed on standby as a precaution. According to officials, the crew followed standard operating procedures and elected to divert the aircraft to Hyderabad after identifying the issue. All passengers and crew members remained safe, and no injuries were reported. While the exact nature of the technical problem has not been disclosed, local reports indicated that the fault was rectified the same day. However, the aircraft reportedly remained in Hyderabad for further inspection and operational checks. IndiGo had not issued a detailed public statement identifying the causes of technical fault. The incidents did not result in any injuries, and both were handled in accordance with established aviation safety procedures.

Two IndiGo Flights Hit By Technical Issues In 3 Days, One Cancelled And One Diverted

June 1, 2026

Georgia, United States: A newlywed groom and a helicopter pilot were killed when a helicopter carrying three people crashed in a remote wooded area of North Georgia shortly after departing a wedding venue late Friday night, while the bride survived with injuries, according to family members, company officials and authorities. The couple were Indian-origin Malayalis from families with roots in Kerala. The crash occurred at approximately 10:30 p.m. on May 29 near Mt. Vernon Drive in Dawson County, southwest of Dawsonville. The Federal Aviation Administration (FAA) confirmed that the aircraft involved was a Robinson R66 helicopter carrying three occupants. Family members identified one of the victims as 25-year-old groom Dave Fiji, who had celebrated his wedding only hours before the accident. The surviving passenger has been identified by relatives and local reports as his bride, Jesni Sam. The identity of the pilot has not yet been officially released by authorities. According to investigators, the helicopter had departed from a North Georgia wedding venue and was returning from a late-night flight when it went down in heavily wooded terrain. The aircraft was owned and operated by Prestige Helicopters, an Atlanta-area helicopter company. Emergency crews from the Dawson County Sheriff’s Office, Fire and EMS responded after receiving reports of a possible downed aircraft. The rugged location of the wreckage significantly complicated rescue efforts. Residents near the crash site said first responders were forced to cut through dense forest to access the area. One local resident told television reporters that crews used off-road vehicles and chainsaws to reach the wreckage, while the survivor was not recovered for several hours due to the challenging terrain. Officials confirmed that two occupants died at the scene while the female survivor was transported to a hospital for treatment. Authorities have not publicly disclosed details regarding the extent of her injuries. Prestige Helicopters Director of Operations Andy Whitaker confirmed that the crashed helicopter belonged to the company. Whitaker described the accident as unprecedented in the company's history, stating that Prestige Helicopters had maintained a clean safety record for approximately four decades before the fatal crash. Whitaker also said the pilot was familiar with the route and had flown it numerous times previously. While investigators have not determined the cause of the accident, weather conditions are emerging as one area of focus in the early stages of the investigation. Radar data from local weather coverage indicated rain and thunderstorms moving across portions of Dawson County between 9 p.m. and 11 p.m. Friday. Witnesses also reported fog in the area around the time of the crash. Prestige Helicopters' operating guidelines state that flights require at least six miles of visibility and a cloud ceiling above 600 feet, and the company does not operate flights during electrical storms or significant wind conditions. At this stage, neither the FAA nor the National Transportation Safety Board (NTSB) has identified weather as the cause of the accident. Investigators have emphasized that no conclusions have been reached and that the crash remains under investigation. The NTSB is expected to examine weather data, flight tracks, aircraft maintenance records, pilot qualifications, operational procedures and wreckage evidence. The helicopter will be moved to a secure facility for further examination. Federal investigators are also reviewing radar information, air traffic communications and witness accounts as they work to establish the sequence of events leading up to the crash. A preliminary NTSB report is expected within a few weeks, though a final determination of the probable cause could take months or longer.

Newlywed Groom And Pilot Killed In Georgia Helicopter Crash; Bride Survives

June 1, 2026

New Delhi, India: InterGlobe Aviation, the parent company of India’s largest airline, IndiGo, reported a consolidated net loss of ₹2,536.9 crore for the quarter ended March 31, 2026 (Q4 FY26), reversing from a net profit of ₹3,067.5 crore recorded during the corresponding quarter of the previous financial year. The sharp decline in profitability came amid significant foreign exchange losses, elevated fuel prices, operational disruptions, and one-time charges that weighed heavily on the carrier’s financial performance despite a marginal increase in revenue. According to the airline’s financial results, revenue from operations rose 1.3% year-on-year to ₹22,438 crore in the January-March 2026 quarter, compared with ₹22,152 crore in Q4 FY25. However, the increase in revenue was insufficient to offset mounting cost pressures. A major factor behind the quarterly loss was a foreign exchange loss of approximately ₹4,823 crore, driven by the depreciation of the Indian rupee against the US dollar. The impact was particularly significant for IndiGo as a large portion of its expenses including aircraft leases, maintenance costs and other aviation-related payments are dollar-denominated. The airline also faced rising aviation turbine fuel (ATF) costs during the quarter amid geopolitical tensions and higher crude oil prices. Fuel remains one of the largest expense components for airlines and contributed substantially to the pressure on margins. In addition, IndiGo reported a one-time charge of ₹250 crore during the quarter. The airline also continued to face operational challenges, including disruptions linked to airspace restrictions and capacity-related constraints that affected network efficiency. Despite the reported loss, the company stated that its underlying business performance remained profitable. Excluding the impact of foreign exchange fluctuations and exceptional items, IndiGo posted a net profit of approximately ₹1,921 crore during the quarter. For the full financial year ended March 31, 2026, IndiGo reported a consolidated net loss of around ₹2,394 crore. The company’s annual results were affected by foreign exchange losses of nearly ₹8,100 crore, disruption-related costs estimated at about ₹580 crore, and expenses of roughly ₹1,200 crore associated with the implementation of new labour regulations. At the operational level, IndiGo carried approximately 123.4 million passengers during FY26, representing a 4% increase compared with the previous year. Total income for the fiscal year rose 6.4% to ₹89,513 crore, reflecting continued demand growth in India’s aviation sector despite a challenging operating environment. The airline’s board also approved the partial prepayment of finance lease obligations owed to its wholly-owned subsidiary, InterGlobe Aviation Financial Services IFSC Private Limited. The prepayment, to be executed in one or more tranches, may total up to US$450 million and is intended to support future aircraft and aviation asset acquisitions. Management indicated that IndiGo is evaluating fuel hedging strategies after remaining largely unhedged during a period of heightened volatility in crude oil prices. The airline said such measures could help reduce exposure to future fuel price fluctuations. Looking ahead, IndiGo expects capacity growth to moderate in the near term. The airline has guided for capacity expansion of approximately 3-4% in the first quarter of FY27, significantly lower than the 16.4% growth recorded during the corresponding period a year earlier. Following the earnings announcement, market participants indicated that IndiGo shares would remain in focus as investors assess the impact of currency movements, fuel costs, regulatory developments and operational performance on the airline’s future profitability.

IndiGo Posts ₹2,537Cr Quarter 4 Loss Amid Forex Hit, Higher Fuel Costs & Disruptions

May 31, 2026

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.

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

May 30, 2026

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.

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

May 30, 2026

Delhi, India: An Air India Boeing 777-300ER operating flight AI173 from Delhi to San Francisco was forced to return to Delhi after suffering a technical malfunction mid-flight, remaining airborne for more than eight hours before landing safely at Indira Gandhi International Airport. The incident occurred on May 27 and involved approximately 230 passengers onboard the long-haul flight bound for the United States. According to airline officials and flight-tracking data, the aircraft had already spent over three hours in the air and entered Chinese airspace when the crew decided to discontinue the journey and return to Delhi in accordance with safety procedures. Initial reports stated that the issue involved the aircraft’s Traffic Collision Avoidance System (TCAS), a critical airborne safety system designed to prevent mid-air collisions by enabling aircraft to electronically detect and communicate with nearby traffic. The system operates independently of ground-based air traffic control and is considered mandatory for certain long-haul international operations, including trans-Pacific and North Atlantic routes. While Air India did not officially disclose the exact nature of the malfunction in its initial public statement, it is suspected that the aircraft experienced problems linked to the TCAS equipment during the flight. Some aviation reports and social media aviation monitoring pages further claimed that both TCAS channels onboard the aircraft became unavailable, though the airline has not publicly confirmed those specific details. Flight-tracking platforms showed the Boeing 777-300ER reversing course while over Chinese airspace before commencing the lengthy return sector to Delhi. Due to the aircraft’s weight, fuel load, and operational requirements for a safe landing, the jet remained airborne for several additional hours before touchdown. Air India confirmed that the aircraft landed safely and would undergo a detailed technical inspection in line with the carrier’s maintenance and safety protocols. The airline also stated that alternative arrangements were made for affected passengers, including hotel accommodation, refreshments, rebooking support, and rescheduling options. “The aircraft landed safely and will undergo technical inspection in line with Air India’s safety standards,” the airline said in its statement while expressing regret over the inconvenience caused to passengers. No injuries were reported during the incident, and passengers were safely deboarded after the aircraft’s arrival back in Delhi.

Air India Flight To San Francisco Returns To Delhi After Mid-Air Technical Malfunction

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 alleging the carrier allowed intoxicated passengers to board multiple flights over a one-year period. According to the FAA, the alleged violations occurred on 11 separate flights between February 2024 and February 2025. Federal aviation regulations prohibit airlines from permitting any individual who appears intoxicated to board an aircraft due to the potential safety and security risks posed during flight operations. The agency announced the proposed enforcement action on May 26, stating that Alaska Airlines now has 30 days from receiving the FAA’s enforcement letter to respond to the allegations or contest the proposed penalty. While the FAA did not disclose details regarding the specific flights, routes, airports, passengers, or onboard incidents involved, the regulator said the alleged cases were identified during a review of the airline’s policies and procedures concerning intoxicated passengers. In response, Alaska Airlines said it fully cooperated with the FAA’s audit and has already implemented corrective measures aimed at strengthening compliance with federal safety expectations. “We take seriously our responsibility to provide a safe and secure environment for our guests and employees,” the airline said in a statement. “Since the FAA shared these concerns with us over a year ago, we made meaningful changes to ensure compliance with the FAA’s expectations including enhanced training for all flight attendants and customer service agents.” The airline added that it respects the outcome of the FAA’s audit and remains confident that the changes introduced over the past year have improved adherence to regulatory standards. The proposed penalty marks the latest in a series of FAA enforcement actions involving airline compliance and safety oversight. Under FAA regulations, airlines are responsible for denying boarding to passengers who appear visibly intoxicated. Such rules are designed to reduce the risk of disruptive behavior, onboard disturbances, and potential threats to flight safety.

FAA Proposes Penalty Against Alaska Airlines Over Alleged Intoxicated Passenger Boarding

May 29, 2026

« Previous Page1 … Page13 Page14 Page15 Page16 Page17 … Page124 Next »

Follow Us

Facebook-f Instagram Linkedin-in X-twitter Youtube

AVIATION TODAY brings the latest in aviation and aims to cater information to professionals and Aviation Enthusiasts about the Industry.

Quick Links

About Us
Contact Us
Services
Advertise
FAQ

Navigate

Latest News
Civil Aviation
Pilot Training
Flight School Analysis
Aviation Jobs
Training

General Support

info@aviationtoday.in

News Desk Support

news@aviationtoday.in

Follow Us

Facebook-f Instagram Linkedin-in X-twitter Youtube

© Copyright 2026 Aviation Today. All rights reserved.

Terms of Use
Privacy Policy
Disclaimer

Search

About Us
News
Pilot Training
Civil Aviation
Flight School Analysis
Aviation Jobs
Training
Services
More
Contact Us
Advertisement

Aviation Newsletter

Facebook Instagram Linkedin X-twitter Youtube