Skip to content

Facebook Instagram Linkedin X-twitter Youtube

About Us
Contact Us
Advertisement

About Us
Contact Us
Advertisement

Aviation Newsletter

WhatsApp Channel

Search

Latest News
Aviation Today Perspectives
Aviation Jobs
About Us

Latest News
Aviation Today Perspectives
Aviation Jobs
About Us

Search

Latest News
Aviation Today Perspectives
Aviation Jobs
About Us

Latest News
Aviation Today Perspectives
Aviation Jobs
About Us

News

Civil Aviation

Pilot Training

Flight School Analysis

Aviation Jobs

Training

Services

About Us

Contact Us

Search

Just In

Lufthansa A380 Lands Short At Munich Airport, Damages Runway Lights During Its Landing
US Court Delays Google’s $10M Spirit Airlines Data Deal After Flight Attendants Object
India’s Supreme Court Pushes Government To Finalise New Aviation Rules Within 3 Weeks
British Airways BA585 Baggage Cart Carrying Checked Luggage Catches Fire At Milan
Hainan Airlines Flight HU753 Diverts To Russia After Mechanical Fault Over Siberia
India Records 889 Serious Aircraft Technical Defects in 2025, Highest In Five Years
Three Onboard Killed As Bell 206 Helicopter Crashes On Greek Island Of Sifnos
Somali Airlines Targets Mid-September Return After 35 Years Of Shutdown
Two American Airlines Jets Sharing Same Callsign Avoid Near-Midair Collision In Phoenix
Vietnam Airlines Boeing 787 Suffers Tailstrike After Extended Takeoff Run At Munich

Lufthansa A380 Lands Short At Munich Airport, Damages Runway Lights During Its Landing

Lufthansa A380 Lands Short At Munich Airport, Damages Runway Lights During Its Landing

US Court Delays Google’s $10M Spirit Airlines Data Deal After Flight Attendants Object

US Court Delays Google’s $10M Spirit Airlines Data Deal After Flight Attendants Object

India’s Supreme Court Pushes Government To Finalise New Aviation Rules Within 3 Weeks

India’s Supreme Court Pushes Government To Finalise New Aviation Rules Within 3 Weeks

British Airways BA585 Baggage Cart Carrying Checked Luggage Catches Fire At Milan

British Airways BA585 Baggage Cart Carrying Checked Luggage Catches Fire At Milan

Hainan Airlines Flight HU753 Diverts To Russia After Mechanical Fault Over Siberia

Hainan Airlines Flight HU753 Diverts To Russia After Mechanical Fault Over Siberia

Latest Breaking News & Developments

Latest Breaking News & Developments

Lufthansa A380 Lands Short At Munich Airport, Damages Runway Lights During Its Landing

Incidents

Lufthansa A380 Lands Short At Munich Airport, Damages Runway Lights During Its Landing

Posted onAugust 19, 2026August 19, 2026

US Court Delays Google’s $10M Spirit Airlines Data Deal After Flight Attendants Object

Airlines

US Court Delays Google’s $10M Spirit Airlines Data Deal After Flight Attendants Object

Posted onAugust 19, 2026August 19, 2026

India’s Supreme Court Pushes Government To Finalise New Aviation Rules Within 3 Weeks

India

India’s Supreme Court Pushes Government To Finalise New Aviation Rules Within 3 Weeks

Posted onAugust 19, 2026August 19, 2026

British Airways BA585 Baggage Cart Carrying Checked Luggage Catches Fire At Milan

Incidents

British Airways BA585 Baggage Cart Carrying Checked Luggage Catches Fire At Milan

Posted onAugust 18, 2026August 18, 2026

Hainan Airlines Flight HU753 Diverts To Russia After Mechanical Fault Over Siberia

Incidents

Hainan Airlines Flight HU753 Diverts To Russia After Mechanical Fault Over Siberia

Posted onAugust 18, 2026August 18, 2026

Read More Stories

Read More Stories

Aviation Today Exclusive

Inside Aviation

Tecnam Presents Modern Trainers for Modern Pilots | Wings India 2026 Exclusive

Tecnam Presents Modern Trainers for Modern Pilots | Wings India 2026 Exclusive

3:51

Boeing’s Wisk Aero Presents Fully Autonomous Gen 6 eVTOL Aircraft | Wings India 2026 Exclusive

Boeing’s Wisk Aero Presents Fully Autonomous Gen 6 eVTOL Aircraft | Wings India 2026 Exclusive

3:10

High Concentration, Zero Error: Responsibility of Air Traffic Control | Wings India 2026 Exclusive

High Concentration, Zero Error: Responsibility of Air Traffic Control | Wings India 2026 Exclusive

5:32

TAV1000i – Design & Built in India Simulator for Precision in Ab-Initio Pilot Training

TAV1000i – Design & Built in India Simulator for Precision in Ab-Initio Pilot Training

3:42

Smiths Detection’s Next-Generation CT Baggage Screening Technology | Wings India 2026

Smiths Detection’s Next-Generation CT Baggage Screening Technology | Wings India 2026

4:05

From Solar Champion to Charter Gateway Pioneer: CIAL’s Evolution | Wings India 2026

From Solar Champion to Charter Gateway Pioneer: CIAL’s Evolution | Wings India 2026

4:06

Sakthi Aviation & Defence Systems Introduces L410NG to Boost India's Remote Connectivity

Sakthi Aviation & Defence Systems Introduces L410NG to Boost India's Remote Connectivity

3:46

DAU School Of Law Unveils Aviation Law Vertical For India’s Aviation Sector | Wings India 2026

DAU School Of Law Unveils Aviation Law Vertical For India’s Aviation Sector | Wings India 2026

5:37

A Clear Path to Becoming a Pilot: United 7 Aero’s Global Training Model | Wings India 2026

A Clear Path to Becoming a Pilot: United 7 Aero’s Global Training Model | Wings India 2026

5:44

Raghu Vamsi's Arrobot Presents Next-Generation Aerial & Ground Robotics | Wings India 2026

Raghu Vamsi's Arrobot Presents Next-Generation Aerial & Ground Robotics | Wings India 2026

5:23

Made In India Diamond DA40 NG: Combining Technology & Efficiency for Flight Training

Made In India Diamond DA40 NG: Combining Technology & Efficiency for Flight Training

6:03

TiHAN Highlights Autonomous Shuttles, Cargo Drones & Smart Mobility

TiHAN Highlights Autonomous Shuttles, Cargo Drones & Smart Mobility

5:38

Gandhi Automations Showcasing Advanced Hangar Door Technologies for Aviation Infrastructure

Gandhi Automations Showcasing Advanced Hangar Door Technologies for Aviation Infrastructure

5:20

Aviacom on High-Fidelity Flight Simulator Technology | Wings India 2026 Exclusive

Aviacom on High-Fidelity Flight Simulator Technology | Wings India 2026 Exclusive

2:56

EgyptAir Training Academy Highlights B737 MAX Type Rating & Training Programs | Wings India 2026

EgyptAir Training Academy Highlights B737 MAX Type Rating & Training Programs | Wings India 2026

7:19

Aksi Aerospace Group Showcases Indigenous Drone Manufacturing Ecosystem | Wings India 2026 Exclusive

Aksi Aerospace Group Showcases Indigenous Drone Manufacturing Ecosystem | Wings India 2026 Exclusive

2:06

Aviation Today Perspectives

From Demonstrations to Networks: The Real Test of Advanced Air Mobility - Part 6

From Demonstrations to Networks: The Real Test of Advanced Air Mobility – Part 6

Read More

From Demonstrations to Networks: The Real Test of Advanced Air Mobility - Part 5

From Demonstrations to Networks: The Real Test of Advanced Air Mobility – Part 5

Read More

From Demonstrations to Networks: The Real Test of Advanced Air Mobility - PART 4

From Demonstrations to Networks: The Real Test of Advanced Air Mobility – Part 4

Read More

Aviation Today Perspectives

From Demonstrations to Networks: The Real Test of Advanced Air Mobility - Part 6

From Demonstrations to Networks: The Real Test of Advanced Air Mobility – Part 6

Read More

From Demonstrations to Networks: The Real Test of Advanced Air Mobility - Part 5

From Demonstrations to Networks: The Real Test of Advanced Air Mobility – Part 5

Read More

From Demonstrations to Networks: The Real Test of Advanced Air Mobility - PART 4

From Demonstrations to Networks: The Real Test of Advanced Air Mobility – Part 4

Read More

Read More Perspectives

Aircraft Crashes

Airlines

Incidents

Sifnos, Greece: A private Bell 206 helicopter operated by Bellavia Aviation Services crashed near the heliport on the Greek island of Sifnos on August 17, killing all three people on board. The helicopter was carrying Greek pilot Giorgos Raikos and British newlyweds Alexander Cromie and Marie Ebert. Local reports identified the couple as tourists travelling to Sifnos for their honeymoon. The flight had departed from Markopoulo, near Athens, and was scheduled to arrive at Sifnos at about 6:15 p.m. local time. The crash occurred shortly after 6 p.m. in the Tholos area, close to the island’s heliport and residential properties. Greece’s Fire Service said its operations centre was alerted at 6:17 p.m. Two firefighters and one vehicle were dispatched to tackle the fire, while a rescue team from nearby Syros was sent by a Fire Service RAFNAR high-speed vessel to reinforce the response. The helicopter crashed during its approach to Sifnos and burst into flames on impact. Firefighters recovered the bodies of all three occupants while extinguishing the blaze. Local reports said two victims were found in the wreckage, while the third was located a short distance away. The deputy mayor of Sifnos, Manolis Foundoulakis, said he arrived at the scene minutes after the crash and described the aircraft as almost completely destroyed. “What I saw was an amorphous mass, because almost nothing was left of the helicopter,” he told Greek media. The crash occurred close to homes, but reports said no neighbouring properties were damaged. A local resident told Greek media that the wreckage fell only about 50 metres from inhabited houses and the landing area, beside the Monastery of Panagia Vrysi. Witness accounts have raised the possibility of a technical problem, although no cause has been established. Residents reportedly heard an unusual or loud noise from the helicopter shortly before it crashed, while some reports said smoke was visible before the aircraft went down. Foundoulakis said residents described “a strange noise” and suspected a possible mechanical problem. Video footage circulating after the accident appears to show the helicopter beginning to rotate rapidly shortly before impact. The footage has focused investigators and aviation specialists on the possibility of a loss of tail-rotor effectiveness or failure. However, this remains only a line of inquiry and has not been established as the cause of the crash. Investigators are expected to examine the helicopter’s mechanical components, the video footage, witness statements and available flight data. The aircraft was identified by multiple reports as a Bell 206 operated by Bellavia Aviation Services, a Greek helicopter charter operator that advertises private helicopter transfers to Sifnos and other Greek destinations. Greek authorities have begun investigating the circumstances of the crash. The Fire Service initially secured the scene and conducted the preliminary investigation, while the National Air and Railway Accident Investigation and Safety Board (EODASAAM) is expected to investigate the aviation accident and determine its cause. Greece’s Ministry of Infrastructure and Transport expressed condolences to the families and said the investigation into the circumstances and causes had been transferred to the competent investigation body. The investigation will focus on the final moments of the flight, the aircraft’s technical condition, possible mechanical failure, the flight path and available records, weather conditions, witness accounts and the video showing the aircraft’s final movements. Authorities have not yet released a definitive cause, and mechanical failure, human factors and other possibilities remain under examination.

Three Onboard Killed As Bell 206 Helicopter Crashes On Greek Island Of Sifnos

Trawsfynydd, United Kingdom: Two people have died after a light aircraft crashed in a remote area near Trawsfynydd, Gwynedd, North Wales, on August 14, after failing to arrive at Caernarfon Airport as scheduled. North Wales Police said it received reports shortly after midday that the aircraft, which had been travelling from an airfield in England, had not reached its destination. A multi-agency air and ground search was launched, with the aircraft eventually located in a remote area near Trawsfynydd. Both people on board were pronounced dead at the scene. The Air Accidents Investigation Branch (AAIB) has been notified and deployed a team of investigators to the site. The incident came to light shortly after noon when the aircraft failed to arrive at Caernarfon Airport, its scheduled destination. Police and partner agencies then began searching for the missing aircraft from the air and ground. The remote location of the wreckage near Trawsfynydd made the operation challenging, although police have not publicly disclosed the exact crash site. North Wales Police Chief Superintendent Owain Llewellyn said: “This has been a challenging search operation,” while thanking the agencies involved for their professionalism and dedication. Police have not released details of what caused the aircraft to crash, and there is currently no official indication that a mechanical failure, weather conditions, pilot action or any other factor was responsible. The AAIB is now leading the technical investigation, meaning any explanation of the circumstances remains premature. The police said they would support the AAIB investigation “to ensure the circumstances leading to this incident are fully understood.” The two occupants were the only people confirmed to have been on board, and both died at the crash site. Their identities have not yet been released publicly by North Wales Police. No official information has also been released on their ages, nationalities, whether one was the pilot and the other a passenger, or their relationship to each other. Police said specialist officers would support the families and friends of those involved. Chief Superintendent Llewellyn said: “Our thoughts are with the families and friends of those involved in this tragic incident.” The aircraft was travelling from an airfield in England towards Caernarfon Airport in Gwynedd. However, neither North Wales Police nor the media reports available so far have identified the departure airfield. The exact route, flight purpose and planned arrival time have also not been disclosed. Details about the aircraft itself also remain limited. Authorities have described it only as a “light aircraft”. Its manufacturer, model, registration, operator and owner have not been publicly confirmed in the official police statement or the initial media reports reviewed for this report. Until those details are confirmed by the AAIB, police, the aircraft registry or another authoritative source, they should not be attributed to the aircraft involved. The search involved multiple agencies using both air and ground resources before the aircraft was located. The police have praised the emergency agencies involved, but the initial statement does not provide a full list of participating organisations, the number of rescuers deployed, the aircraft or helicopters used in the search, or how long it took to locate the wreckage. Those details may emerge as the investigation and recovery operation progresses. The AAIB has now sent investigators to the scene. Its role is to establish the circumstances and probable cause of the accident and, where appropriate, make safety recommendations. No preliminary findings from the investigation have been publicly released.

Two Dead After Light Aircraft Crashes In Remote Area Of North Wales, AAIB Investigates

Two US Army Soldiers Killed As Fort Hood-Based Apache Crashes During Training In Texas

Two US Army Soldiers Killed As Fort Hood-Based Apache Crashes During Training In Texas

Arizona, United States: A Glasair Sportsman 2+2 carrying two people crashed in the remote Mazatzal Wilderness west of Payson in Gila County, Arizona, on Monday, August 10, 2026, killing both occupants, Brad Lawrence, 75, and Carter Buckner, 19, of Payson, as the National Transportation Safety Board (NTSB) and Federal Aviation Administration (FAA) investigate what caused the accident. The crash site was located west of Polles Mesa in rugged wilderness terrain, with reports placing the accident at around 11 p.m. The aircraft was identified by the FAA as a Glasair Sportsman 2+2, a privately operated light aircraft. No airline or commercial operator has been identified in the reports, and authorities have not publicly confirmed the aircraft’s registration, departure point or intended destination. The NTSB said investigators were continuing to gather information, while the FAA confirmed that the agency was also investigating the crash. The Gila County Sheriff’s Office was alerted to a possible downed aircraft west of Polles Mesa in the Mazatzal Wilderness. The location’s remote and rugged terrain created significant challenges for the response. A helicopter from the Maricopa County Sheriff’s Office helped locate the wreckage, while a Pinal County Sheriff’s Office helicopter transported deputies to the crash site for the initial investigation. The Gila County Sheriff’s Office said the assistance was required because of the “remoteness and rugged terrain.” Gila County Sheriff J. Adam Shepherd thanked the neighboring agencies for their assistance following the crash. “Sheriff J. Adam Shepherd would like to thank the Maricopa County Sheriff's Office and Pinal County Sheriff's Office for their coordinated assistance,” the sheriff’s office said in a statement, adding that the sheriff extended “our deepest condolences to everyone impacted by this tragedy.” The victims were identified as Lawrence and Buckner, both Payson residents. Authorities have not established publicly who was flying the aircraft at the time of the crash. The circumstances leading up to the accident, including the aircraft’s flight path and what happened immediately before impact, remain under investigation. Lawrence was well known in the local aviation community. According to FOX 10, he served as vice president of the Payson Pilots Association for nearly three years and was described by fellow pilots as an experienced aviator with a strong passion for flying. “He was a very experienced aviator. He had two airplanes. His own hanger and house beside the hanger, so that gives you an indication of his passion for aviation,” Payson Pilots Association president Kevin McCully told FOX 10. Lawrence was also involved in aviation outreach. Kevin McCully, president of the Payson Pilots Association said Lawrence had participated in the Experimental Aircraft Association’s Young Eagles program, which provides young people with introductory flights to encourage interest in aviation. McCully said he did not believe the fatal flight was part of the Young Eagles program, but suggested Lawrence may have been demonstrating his aircraft and helping Buckner become involved in aviation. “He loved to travel. Loved his airplane of course. And he was just a wonderful man,” Debbie Snow, a member of Lawrence’s family, told FOX 10 while remembering the longtime pilot. McCully added, “We’re all going to miss him very much.” The crash investigation is now being led at the federal level by the NTSB, with the FAA assisting. As of the latest available reports, investigators had not released a probable cause, possible mechanical issue, weather factor or other explanation for the crash. Further details are expected as investigators examine the wreckage, aircraft records, flight information and other evidence from the remote crash site.

Two Killed As Small Plane Crashes Near Payson, Arizona; NTSB Probes Fatal Accident

Two Pilots Killed As Sikorsky S-64 Crashes Fighting Utah’s Widemouth 2 Fire

Two Pilots Killed As Sikorsky S-64 Crashes Fighting Utah’s Widemouth 2 Fire

US Court Delays Google’s $10M Spirit Airlines Data Deal After Flight Attendants Object

US Court Delays Google’s $10M Spirit Airlines Data Deal After Flight Attendants Object

Mogadishu, Somalia: Somali Airlines is targeting a return to scheduled passenger operations around mid-September 2026, more than 35 years after the national carrier stopped flying amid Somalia’s civil war, according to the country’s Civil Aviation Authority. Ahmed Ma’allin, director of the Somali Civil Aviation Authority, said the relaunch preparations had reached their final stage. “Somali Airlines is in its final stages, the first flight will be around mid September,” he said. The latest target would mark the airline’s first scheduled commercial operations since 1991, when its services were halted following the collapse of Somalia’s central government and the outbreak of civil war. Somali Airlines was established in 1964 and previously operated a network linking Somalia with destinations in Africa, the Middle East and Europe. The September target is the latest in a series of attempts to restore the state-owned carrier. In July 2025, the Somali government announced an agreement involving two Airbus A320 aircraft as the initial fleet for the revived airline. At the time, Transport and Civil Aviation Minister Mohamed Farah Nuuh said the aircraft were expected to enter service within two months. The minister said during the July 2025 announcement in Mogadishu that the government had acquired two A320s and planned to expand the fleet. “For now, we shall start with these two, then two or three more will follow,” he said. The government subsequently set additional timelines for the airline’s return, including a target to resume operations before the end of 2025. That deadline passed without the carrier beginning scheduled commercial services, making the September 2026 target another attempt to turn the long-running revival plan into an operating airline. The initial fleet is expected to comprise two Airbus A320 aircraft secured under the 2025 agreement. The government has indicated that the two aircraft are only the first phase of a wider fleet-building programme, with additional aircraft expected as the airline expands. However, aircraft acquisition alone does not complete the restart process. The airline must satisfy safety and regulatory requirements, obtain the necessary operating approvals and ensure that pilots, engineers, cabin crew and other personnel are appropriately qualified. Maintenance arrangements, insurance, flight planning, airport handling and other operational systems must also be in place before regular commercial services can begin. The Somali Civil Aviation Authority’s current aeronautical information system shows that Somalia has continued developing its regulatory and operational aviation framework. Its 2026 aeronautical information publication is effective from July 9, 2026, and includes current material covering Somalia’s airspace, airports and flight operations. Despite the September target, the authorities have not publicly disclosed a specific inaugural route, destination list or frequency for Somali Airlines in the August 2026 reports reviewed. The reports also do not establish a confirmed date within September beyond Ma’allin’s indication that the first flight could be around the middle of the month. The airline’s historical network, however, included destinations in East Africa, the Middle East and Europe. The revived carrier is expected to operate initially with the A320s and expand its network as additional aircraft become available. The government’s longer-term objective is to build a national airline capable of competing with established international and regional carriers serving Somalia. The revival also has significance beyond the airline itself. Somali officials have previously linked the project to improved connectivity for the Somali diaspora, employment in aviation and related industries, reduced dependence on foreign carriers and the broader rebuilding of the country’s aviation sector. The government’s 2025 announcement was made at the Prime Minister’s Office in Mogadishu, where officials confirmed the acquisition of the two A320 aircraft. The official Somali National News Agency, SONNA, described the return of the carrier as part of Somalia’s broader recovery and rebuilding efforts. Somalia has also made wider progress in rebuilding its aviation system after decades of disruption. The Somali Civil Aviation Authority’s current publications show an active regulatory framework, while the country has continued developing airport and air-navigation infrastructure.

Somali Airlines Targets Mid-September Return After 35 Years Of Shutdown

Air India Group Mandates Substance Screening For All Pilots Following A320neo Incident SEO DES: The move follows an August 4 incident in which the captain underwent substance testing that returned a non-negative result after a sudden 300 ft altitude loss SOCIAL: Air India and Air India Express have begun one-time mandatory substance screening for more than 5,000 pilots, going beyond DGCA’s requirement of annual random testing of at least 10% of flight crew. The exercise began August 13, with pilots being tested at training centres, briefing locations and other designated facilities. No completion figures have been officially released yet. The expanded testing follows the August 4 Phuket-Delhi incident, in which an Air India A320neo lost about 300 feet in altitude, leaving 24 passengers and crew injured. Both pilots underwent mandatory screening, with the captain’s initial test requiring confirmation. A later media report said the captain tested positive for marijuana in the confirmatory test, although this has not been officially confirmed by DGCA or the Ministry of Civil Aviation. Civil Aviation Minister K. Ram Mohan Naidu said the incident is being investigated with aviation safety as the priority. The expanded screening marks a stronger step by Air India to monitor pilot fitness, while the airline and regulator are expected to assess the findings and determine any further safety measures. New Delhi, India: Air India and Air India Express have begun mandatory substance screening for more than 5,000 pilots, with the airline launching the one-time, group-wide testing exercise on August 13. The programme covers pilots across both carriers and goes beyond the existing regulatory requirement for airlines to randomly test at least 10% of flight crew for psychoactive substances each year. Air India has not publicly disclosed how many pilots have completed the new screening or what percentage of the total pilot pool has been tested. Current reports describe the exercise as ongoing rather than completed. The testing covers substances and medications prohibited under aviation regulations and is being conducted at multiple points across the airline’s operations. According to an internal Air India communication cited by Reuters, pilots can be screened alongside training sessions at the airline’s Gurugram academy, after flights at briefing centres and offices, and at locations designated according to their home bases. Air India Express pilots are included in the exercise. The airline has said the additional screening is intended to strengthen safety standards and reassure passengers and other stakeholders. Air India announced the expanded testing programme on August 13, saying it already complies with the Directorate General of Civil Aviation’s existing requirements but had decided to go further. The airline’s senior vice-president for flight operations, Captain Manish Uppal, told pilots that protecting passenger trust was central to the decision. After this one-time exercise, Air India is expected to return to the applicable regulatory framework, which currently requires annual random testing of at least 10% of flight crew. The move follows the August 4 serious incident involving an Air India Airbus A320neo operating from Phuket to Delhi. The aircraft experienced a sudden loss of about 300 feet in altitude while cruising before stabilising and continuing to Delhi. The flight was carrying 137 passengers and eight crew members, and subsequent reports said 24 passengers and crew members were injured. Following the incident, both pilots underwent mandatory screening for psychoactive substances after the aircraft landed in Delhi. The Ministry of Civil Aviation said the captain’s initial result required further laboratory confirmation, and both pilots were removed from flying duties while the investigation continued. The Aircraft Accident Investigation Bureau is examining flight data, aircraft systems, maintenance and operational records, medical information and crew accounts, with Airbus and France’s BEA assisting the Indian investigation. The subsequent development that brought the pilot-testing issue into sharper focus was the reported result of the confirmatory laboratory test. Several media outlets reported on August 11, citing sources familiar with the matter, that the captain had tested positive for marijuana in the confirmatory test. Separately, the Ministry of Civil Aviation officially summoned Air India CEO Campbell Wilson for a briefing on the investigation. That result, however, has not been publicly confirmed in an official statement by the DGCA or the Ministry of Civil Aviation. The official position previously released by the ministry was that the captain’s initial screening required confirmatory testing. The reported positive confirmatory result therefore remains attributed to sources familiar with the matter rather than an officially published regulatory finding. Civil Aviation Minister K. Ram Mohan Naidu has meanwhile maintained that the incident is being investigated and that aviation safety remains the priority. The government’s response has included directing the regulator to strengthen oversight of psychoactive-substance testing, while Air India has moved beyond the minimum regulatory requirement by subjecting its entire pilot pool to the expanded screening exercise. The wider significance of the move will depend not only on the completion of the current testing programme, but also on how the airline and regulator translate its findings into long-term safety and fitness-for-duty measures.

Air India Group Mandates Substance Screening For All Pilots Following A320neo Incident

international operations. Beijing, China: Air China’s COMAC C919 completed its first scheduled international passenger service on August 12, 2026, when flight CA723 departed Beijing Capital International Airport at about 3 p.m. for Ulaanbaatar, Mongolia, marking the first time the Chinese-developed narrowbody aircraft carried passengers on a regular route between China and another country. The aircraft arrived at Chinggis Khaan International Airport at about 4:58 p.m. with 121 passengers onboard. China operates the route daily, with CA723 scheduled to depart Beijing at 3 p.m. and arrive in Ulaanbaatar at 5:15 p.m., while return flight CA724 departs Ulaanbaatar at 6:30 p.m. and reaches Beijing at 8:35 p.m., with all times local. The Beijing-Ulaanbaatar operation marks the latest stage in the C919’s commercial development since the aircraft entered airline service in 2023. The C919 was developed by Commercial Aircraft Corporation of China (COMAC), the country’s state-owned commercial aircraft manufacturer, as China’s first domestically developed narrowbody mainline jet built to international airworthiness standards. COMAC lists the aircraft’s basic configuration at 158 to 192 seats, with a range of 4,075 to 5,555 kilometers. The programme reached a major milestone on November 2, 2015, when the first C919 completed final assembly and rolled out, followed by its maiden flight on May 5, 2017. The aircraft received its type certificate from the Civil Aviation Administration of China (CAAC) on September 29, 2022, and the first C919 was delivered to launch customer China Eastern Airlines on December 9, 2022. China Eastern subsequently operated the aircraft’s first commercial passenger flight on May 28, 2023, completing the development, manufacturing, certification and commercial-entry stages of the programme. The C919’s international exposure began before Wednesday’s scheduled service. In February 2024, a China Eastern C919 flew to Singapore for the Singapore Airshow, marking the aircraft’s first appearance at the event. COMAC then conducted a series of demonstration flights in Southeast Asia in 2024, including visits to Vietnam, Laos, Cambodia, Malaysia and Indonesia, to assess the aircraft’s compatibility with local airports, ground-support equipment and operating procedures. The C919 programme has also expanded beyond the original aircraft configuration. On July 29, 2026, COMAC conducted the first flight of the C919 high-altitude variant at Shanghai Pudong International Airport. The aircraft flew for 1 hour and 59 minutes and completed all planned test items. COMAC said the variant incorporates a shortened fuselage and system modifications designed for high-altitude operations. The aircraft remains heavily dependent on an international supply chain. Its LEAP-1C engines are supplied by CFM International, the GE Aerospace-Safran joint venture, while Honeywell, Collins Aerospace, Parker Hannifin, Moog and other Western companies supply systems and equipment. Air Data News reported that this dependence became particularly visible during the 2025 US-China trade dispute, when Washington temporarily suspended export licenses involving technology and engines destined for COMAC before the restrictions were later lifted. The C919’s dependence on foreign technology has also been a factor in China’s efforts to develop domestic alternatives. Replacing established Western systems requires more than manufacturing substitute components, because replacement systems must meet requirements for reliability, weight, fuel efficiency, durability and certification. Production has been another major part of the programme’s development. COMAC delivered 15 C919 aircraft to customers in 2025, well below an earlier target of 75 aircraft. South China Morning Post reported in January 2026 that COMAC was targeting at least 28 deliveries during 2026 and that, if production reached the expected pace, the manufacturer could produce one C919 every 10 to 15 days. The report said two aircraft had already taken shape during the first three weeks of 2026 and were undergoing delivery procedures. COMAC has also been expanding its production infrastructure. ChinaTravelNews reported in July 2026 that deliveries were expected to reach at least 28 C919 aircraft in 2026, with production potentially increasing to one aircraft every 10 to 15 days. The second phase of the C919 final-assembly-line expansion in Shanghai Pudong is expected to take annual production capacity above 100 aircraft, while COMAC has set a longer-term target of 200 aircraft a year by 2029. Earlier production plans were even more ambitious. In March 2025, COMAC raised its planned C919 production capacity for that year to 75 aircraft from an earlier target of 50, while setting a 200-aircraft annual production objective for 2029. The actual 2025 delivery figure subsequently came in at 15 aircraft. The C919’s order book has been concentrated largely among Chinese airlines. By December 2024, Air Data News reported that Air China, China Southern and China Eastern together had ordered 306 C919 aircraft, although only 14 had been delivered to the three carriers at that point. COMAC was simultaneously exploring potential overseas customers in Indonesia, Cambodia and Kazakhstan, while Vietnam Airlines, AirAsia and Brazil’s Total Linhas A

China’s Homegrown C919 Makes International Debut With Air China Flight To Mongolia

WestJet To Pay C$4.5 Million In Decade-Long Flight Attendants’ Harassment Case SEO DES: The case stemmed from alleged sexual assaults involving a WestJet pilot in 2008 and 2010 followed by claims of inadequate investigations & harassment reporting SOCIAL: The Supreme Court of British Columbia approved WestJet’s C$4.5 million settlement on August 10, 2026, ending a decade-long sexual-harassment class action involving 3,452 current and former female flight attendants. The settlement was found fair, reasonable and in the class members’ best interests. The settlement follows allegations that WestJet failed to maintain an effective workplace free from harassment. It includes an independent assessment of workplace harassment, underreporting and the effectiveness of WestJet’s reporting and response systems, although the airline denies wrongdoing and admits no liability. Eligible claimants are expected to receive about C$470 each, subject to final administration costs. Deloitte LLP will administer the claims process once it opens, while the settlement remains subject to a mandatory 30-day finalization period following the August 10 approval. Vancouver, Canada: WestJet’s C$4.5 million settlement with female flight attendants in a decade-long sexual harassment class action was approved by the Supreme Court of British Columbia on August 10, 2026, bringing the long-running case closer to an end while requiring the airline to commission an independent workplace assessment into harassment, underreporting and the effectiveness of its reporting systems. The settlement covers current and former female WestJet mainline flight attendants who worked between April 4, 2014, and February 28, 2021, and who did not opt out of the class action. The court found the settlement fair, reasonable and in the best interests of the class. Under the approved agreement, the C$4.5 million settlement fund will first cover court-approved legal fees, disbursements, applicable taxes, settlement administration expenses and an honorarium for representative plaintiff Mandalena Lewis. The remaining amount will be distributed among eligible class members who submit valid claims. The class-action lawyers currently estimate that each eligible claimant who files a valid claim will receive about C$470, although the final amount could change slightly after administration costs are finalized. The settlement does not include an admission of liability or wrongdoing by WestJet. The airline continues to deny the allegations, and the disputed claims were never determined at trial. WestJet has also not agreed to some of the major forms of relief originally sought by the lawsuit, including mandatory anti-harassment training for pilots, an admission of wrongdoing or an admission that it breached its employment contracts. Instead, one of the key non-monetary terms requires WestJet to retain an independent and qualified third party to assess the prevalence of workplace harassment, the extent to which harassment is underreported, and how the airline’s systems for reporting and responding to harassment can be made more effective. WestJet must provide employees with a summary of the assessment’s findings. Deloitte LLP has been appointed as the independent claims administrator and is preparing a secure online claims portal. Eligible class members do not need to submit anything yet. Once the portal is ready, they will receive notice containing the claims link, instructions, the deadline and payment information. Class members will have three months from the date that notice is sent to submit a valid claim. Deloitte is then expected to review and process the claims within up to 60 days after the claims deadline, with approved payments to be made through Interac e-Transfer. The settlement is not yet final. A mandatory 30-day period follows the court’s August 10 approval before the agreement becomes final. Lewis, a former WestJet flight attendant, launched the class action in April 2016 after alleging that the airline had failed to uphold its promise to provide female employees with a workplace free from harassment. The case grew out of allegations surrounding an incident involving Lewis and a WestJet pilot during a layover in Maui, Hawaii, in January 2010, when Lewis was 25. According to court-related accounts, Lewis alleged that she was sexually assaulted by the pilot and that another female flight attendant had also been assaulted by the same pilot in 2008. Lewis alleged that she reported the 2010 incident to WestJet and that the airline’s subsequent investigation was inadequate. She said she received limited information about how the investigation was being conducted and was warned that she could face discipline if she discussed the incident with others. WestJet managers later told her that the pilot had not been terminated following the investigation, although restrictions were placed on his ability to fly to certain destinations and Lewis was not supposed to be scheduled to work with him. Lewis later learned in August 2015 that another female flight attendant had allegedly reported an assault involving the same pilot in 2008. She argued that if WestJet had properly investigated that earlier complaint and disciplined the pilot, she would not have been assaulted. The allegations formed part of her broader claim that the airline had failed to create and maintain an effective system to prevent and respond to harassment. Lewis also alleged that after she reported the incident to police in Maui, WestJet rerouted the pilot so that he would not be available to face questioning there. Lewis eventually abandoned an individual civil claim and pursued a class action after learning that other flight attendants had experienced harassment. Her employment with WestJet ended in 2016, with court documents submitted by the airline describing her termination as being for “gross insubordination”; Lewis and her legal team alleged that the termination was retaliation for her efforts to hold WestJet accountable internally. These allegations were disputed and were not established at trial. Lewis had worked for WestJet from March 2008 until January 2016. In the litigation, she described observing and experiencing inappropriate conduct involving female flight attendants, particularly conduct by pilots. Her legal case, however, was structured primarily as a breach-of-contract claim, rather than as a conventional personal-injury or tort claim. The argument was that WestJet’s anti-harassment commitments were incorporated into employees’ contracts and that the company had failed to implement and maintain an effective harassment-prevention system. The lawsuit initially faced a major legal obstacle. In December 2017, the B.C. The Supreme Court rejected WestJet’s attempt to strike the claim. WestJet argued, among other things, that the dispute belonged before the Canadian Human Rights Tribunal, that disgorgement was not an available remedy, that the claim amounted to an abuse of process and that Lewis’s action was barred by limitation rules. Justice Humphries rejected those arguments, allowing the case to proceed. WestJet appealed, but the contractual foundation of the case survived. The B.C. The Court of Appeal ultimately rejected the airline’s jurisdictional argument, holding that an employment contract could provide a legal basis for a court claim even where human-rights legislation also provided avenues of redress. The Supreme Court of Canada did not take up the matter. The first attempt to certify the matter as a class action was unsuccessful. In 2021, the B.C. The Supreme Court accepted that most of Lewis’s proposed common issues could potentially be addressed collectively but concluded that a class proceeding was not the preferable procedure. The court considered the Canadian Human Rights Tribunal a more practical avenue because it could provide both systemic and individual remedies. That decision was overturned in significant part by the B.C. Court of Appeal on April 19, 2022. The appellate court certified the class action, finding that the issues surrounding WestJet’s alleged failure to implement and enforce its anti-harassment commitments could be examined collectively. The court rejected the argument that human-rights proceedings were necessarily a preferable alternative to the class action. The class period was subsequently the subject of another dispute. WestJet sought to shorten the period covered by the certification order to July 31, 2018, when the Canadian Union of Public Employees was certified as the bargaining agent for WestJet flight attendants. In November 2023, the court rejected the attempt to cut off the class period at that point, leaving February 28, 2021, as the end of the class period. The litigation also reached the disclosure stage. In December 2024, Justice Jacqueline Hughes ordered WestJet to produce harassment-related records covering the class period. The court said the airline had been slow and potentially adversarial in producing documents. WestJet had provided 24 harassment complaints, but internal statistics indicated that significantly more complaints existed. The ruling said some complaints involved sexual harassment and sexual assault. The court ordered WestJet to produce harassment complaints made by flight attendants during the class period from April 4, 2014, to February 28, 2021, rather than limiting disclosure only to complaints against male pilots involving class members. Justice Hughes did not, however, extend the case to harassment complaints involving WestJet’s entire workforce, finding that the lawsuit concerned the employment contracts of flight attendants. The disclosure dispute was significant because the court record indicated that WestJet’s internal statistics showed substantially more complaints than the 24 files initially produced. The court also found that the requested documents concerning exit interviews, complaints, the company’s core policies and anti-harassment program, investigations and the people conducting those investigations were relevant to the class action, although documents concerning settlements were excluded from the production order. The settlement negotiations eventually produced the C$4.5 million agreement. The Guardian reported that the settlement was finalized on June 22, 2026, following months of negotiations, before receiving judicial approval on August 10. The approved settlement covers 3,452 female flight attendants. The settlement amount became a point of controversy among some class members. Eight women had objected to court approval in February after details of the proposed agreement emerged, arguing that the compensation was too low and that the settlement did not provide sufficient accountability. Lewis herself expressed disappointment after the approval, telling the Guardian that she was glad the litigation was over but was exhausted and “shaking my head.” She said she had been advised that the settlement was the best result that could be achieved as legal expenses continued to accumulate. Lewis also compared the outcome with WestJet’s separate C$12.5 million baggage-fee class-action settlement, which was nearly three times larger. She said the outcome did not amount to the justice she had sought, telling, “We didn’t get justice here.” The settlement nevertheless provides a structural measure beyond the monetary payment. The independent workplace assessment is intended to examine whether harassment is occurring, how frequently employees may be failing to report it and whether existing mechanisms for reporting and responding to complaints are effective. WestJet will be required to provide employees with a summary of the findings. WestJet said it was pleased to have reached a mutually agreed settlement. In a statement, the airline said it remained committed to strengthening its operations and training, with a focus on the safety and wellbeing of its employees, and on advancing a culture of empowerment. With the August 10 approval, the litigation has moved from the courtroom dispute over WestJet’s alleged anti-harassment obligations to the implementation of the settlement. The agreement must pass the 30-day finalization period, after which Deloitte will begin processing eligible claims once the claims process opens. The class-action website says the claims portal and exact deadline will be published when the process begins.

WestJet To Pay C$4.5 Million In Decade-Long Flight Attendants’ Harassment Case

Munich, Germany: A Lufthansa Airbus A380-800 operating flight LH459 from San Francisco International Airport to Munich Airport touched down prematurely near the eastern threshold of Munich’s southern runway on Monday evening, August 17, 2026, damaging runway-threshold lighting. The aircraft, registered D-AIML, was carrying 351 passengers after completing the approximately 11-hour transatlantic flight from San Francisco, United States, to Munich, Germany. All passengers and crew were able to leave the aircraft normally, with no injuries reported. Flight records identify D-AIML as an Airbus A380-841 operated by Lufthansa, while Lufthansa’s published schedule confirms LH459 operates between San Francisco and Munich. According to Lufthansa, the aircraft touched down on the concrete surface before the white-marked runway threshold. During the premature touchdown, the aircraft struck lighting installed around the runway threshold, causing damage to the runway’s visual guidance system. Lufthansa spokesperson Jörg Waber said in a statement, “We can confirm that an AirVIbus A380-800 damaged runway lighting in the area of the runway threshold.” He added that the aircraft had arrived from San Francisco with 351 passengers, subsequently taxied to its assigned position and that all passengers left the aircraft normally. The incident occurred on Munich Airport’s southern runway, identified as Runway 26L when used for approaches from the east. The Deutsche Flugsicherung describes Runway 26L as Munich’s southern runway and says aircraft approaching it from the east use its instrument landing system. Munich Airport characterized the infrastructure damage as minor. According to the airport, a “minor damage” to lighting was identified around the eastern threshold of the southern runway. The damaged lighting was repaired promptly, allowing the runway to return to service less than an hour after the A380 landed. The exact circumstances that caused the A380 to touch down before the designated threshold remain unclear. No official finding has attributed the event to pilot error, weather, aircraft malfunction, runway conditions or any problem with the airport’s approach system. The aircraft touched down short of the marked threshold and that its landing gear struck approach lights. The cause remains under investigation. Germany’s Federal Bureau of Aircraft Accident Investigation, or BFU, has opened an investigation into the occurrence. The A380 involved was approximately 13 years old and carried the registration D-AIML. Flight-history records identify the aircraft as an Airbus A380-841 operated by Lufthansa. The airline’s A380 configuration can accommodate up to 509 passengers, although 351 passengers were onboard LH459 during this particular flight. Separately, on August 15, 2026, a Vietnam Airlines Boeing 787-9 bound for Hanoi experienced an unusually long takeoff run at Munich Airport. The aircraft continued accelerating almost to the end of Runway 26L and reportedly travelled about 120 metres beyond the paved surface before becoming airborne. During the extremely late rotation, its rear underside struck the ground, causing a tailstrike and damage to the aft fuselage. After takeoff, warnings for tail contact and low tyre pressure prompted the crew to remain near Munich at around 9,000 feet for about two hours before returning. The aircraft sustained further landing-gear and tyre damage, with several tyres damaged or deflated, and was unable to taxi after landing. It was carrying 271 passengers and 16 crew, all of whom were reported safe. German authorities are leading the investigation, with Vietnamese investigators assisting, while the cause of the unusually prolonged takeoff remains under investigation.

Lufthansa A380 Lands Short At Munich Airport, Damages Runway Lights During Its Landing

Milan, Italy: A baggage cart carrying checked luggage caught fire at Milan Malpensa Airport in Italy on Sunday, August 16, shortly before the baggage was due to be handled for a British Airways flight to London Heathrow, prompting airport firefighters to intervene and damaging a small number of passengers' bags. The incident occurred on the airport apron and did not involve a fire onboard the aircraft. The fire involved an Aviapartner baggage-handling cart at Milan Malpensa. The handling company operates ground services at the airport, and the cart had just completed baggage handling associated with a British Airways flight arriving from London when it caught fire. Initial reports focused on the possibility of a lithium-ion battery inside one of the bags, but subsequent airport-source information pointed to an electrical fault in the ground vehicle instead. The incident was captured on video by former BBC journalist Jon Sopel, who was at Malpensa waiting to travel on British Airways flight BA585 from Milan to London Heathrow. The footage showed dense black smoke rising from the baggage container, with flames visible around the luggage. Ground personnel moved other baggage containers away from the burning unit to prevent the fire from spreading before airport fire crews arrived. The aircraft associated with BA585 was an Airbus A321neo registered G-NEOT, powered by two CFM International LEAP-1A32 engines. The scheduled route was Milan Malpensa Airport (MXP) to London Heathrow Airport (LHR), with British Airways operating the service under flight number BA585. The fire occurred before the affected luggage could create a fire risk inside the aircraft. The burning baggage unit remained on the ground and was dealt with by airport emergency crews. The other containers were moved away from the fire, helping prevent the flames from spreading to additional baggage or equipment. Firefighters extinguished the blaze rapidly using water. British Airways confirmed that some passengers' checked baggage was damaged. In a statement, the airline said: “We’re aware of a small number of checked bags that were damaged by fire while on the ground at Milan Malpensa Airport. The incident was quickly dealt with, and there were no injuries or impact to any flights.” The airline added: “We’ve been in contact with the small number of customers whose bags are affected to apologise and provide support. We are working closely with our partners, and an investigation is underway to establish the cause.” That statement is significant because it confirms that the fire affected checked baggage on the ground but did not result in injuries or a fire onboard the aircraft. It also shows that British Airways had not initially announced a confirmed cause and was relying on an investigation with its ground-handling partners. The investigation remained underway, while British Airways confirmed that only a small number of checked bags were damaged and that there were no injuries.

British Airways BA585 Baggage Cart Carrying Checked Luggage Catches Fire At Milan

Krasnoyarsk, Russia: Hainan Airlines Flight HU753, operating from Beijing Capital International Airport in China to Manchester Airport in the United Kingdom, diverted to Krasnoyarsk International Airport in Russia on August 15 after the Airbus A330-300 developed a mechanical fault while flying over Siberia. The aircraft landed safely, with no injuries, deaths or damage reported. The flight was operated by an Airbus A330-343, registration B-304L, with 230 people on board. Flight-tracking data showed the aircraft departed Beijing for Manchester and was cruising at approximately FL340, or 34,000 feet, when the problem occurred. The aircraft was around 190 nautical miles southeast of Krasnoyarsk when it descended to approximately FL200 and diverted toward Krasnoyarsk International Airport. According to reports, the problem emerged approximately four hours into the flight. The aircraft's sensors detected the fault and the crew issued an emergency signal before diverting to Krasnoyarsk.. Russian emergency authorities had prepared for the aircraft's arrival, deploying 51 personnel and 15 vehicles. The response included 39 personnel and 11 vehicles from Russia's Ministry of Emergency Situations, according to reports. Emergency teams were positioned as a precaution, but the aircraft completed the landing without an accident. Russia's Emergencies Ministry confirmed that there were no injuries or deaths and that neither the aircraft nor airport infrastructure was damaged. English- and Chinese-speaking airport personnel were also reported to have assisted passengers and crew following the landing. Hainan Airlines confirmed the diversion and apologised to passengers. In its statement, the airline said: “On 15 August 2026, our flight HU753 (Beijing–Manchester) diverted to Krasnoyarsk International Airport in Russia due to a mechanical fault. The flight landed safely at 07:28 Beijing time.” The airline added: “The company plans to replace the aircraft to operate the onward flight. We will properly arrange passenger service support to ensure safe arrival at the destination. We sincerely apologise for any inconvenience caused to passengers.” Hainan Airlines also reiterated: “Hainan Airlines always adheres to the principles of safety first and passengers first, providing safe, comfortable and efficient services.” The exact nature of the mechanical fault has not been officially disclosed. Hainan Airlines described the problem as a “mechanical fault,” while Russian authorities referred to it as a technical malfunction. Therefore, claims that the incident involved a particular system failure should be treated cautiously. The diversion left passengers in Krasnoyarsk while Hainan Airlines arranged an onward journey. The airline said a replacement aircraft would be sent to Krasnoyarsk to continue the service to Manchester, while passenger support arrangements were being made.

Hainan Airlines Flight HU753 Diverts To Russia After Mechanical Fault Over Siberia

Phoenix, United States: A potential mid-air collision was averted near Phoenix Sky Harbor International Airport on August 14, 2026, after two American Airlines Boeing 737-800s were simultaneously operating under the same “American 2482” callsign while flying in opposite directions between Phoenix and Chicago. One aircraft was arriving at Phoenix from Chicago O’Hare International Airport, while another had just departed Phoenix for Chicago. The unusual overlap occurred after the inbound Flight 2482 was delayed by weather, prompting American Airlines to use another aircraft already at Phoenix so passengers waiting for the outbound service could depart on schedule. Because Flight 2482 normally operates as a Chicago-Phoenix round trip using the same flight number, the replacement aircraft also operated under the 2482 identification. The resulting callsign duplication placed both aircraft in the same area of airspace while communicating on the same frequency. Flightradar24 reported that the arriving aircraft was descending through about 11,000 feet while the departing aircraft was climbing toward 9,000 feet when the duplication was recognized. The FAA said the aircraft maintained the required separation throughout the incident. The Phoenix air traffic controller quickly recognized the problem and began distinguishing the two aircraft as “American 2482 on the arrival” and “American 2482 on the departure.” The controller then kept the arriving aircraft above the departing aircraft and prevented the departure from climbing into the arrival’s altitude, maintaining vertical separation as their flight paths converged. The controller also alerted both crews to the other aircraft. Reports said the pilots were able to see each other while they were still miles apart, providing an additional layer of awareness as the two aircraft crossed paths. No source has publicly released an exact minimum horizontal distance between the aircraft, and the FAA has confirmed only that required separation was maintained. The incident was captured in air traffic control audio published by ATC.com and subsequently highlighted by media outlets. After the departing aircraft had cleared the area, the controller said, “I’ve been working air traffic for 25 years. I’ve never seen two aircraft pretty much merge with the same call sign. That’s pretty incredible.” The arriving pilot later complimented the controller, saying “nice work.” The controller responded, “It could have been disastrous, but I’m glad it worked out.” The precise passenger and crew numbers aboard the two Boeing 737-800s have not been publicly disclosed by the FAA or American Airlines. Both aircraft completed their flights safely, with no injuries or collision reported. American Airlines said, “The diligence and professionalism of air traffic controllers and our pilots ensured required separation was always maintained and the issue was identified and addressed. Both flights continued safely and without incident.” Aviation safety expert Steve Arroyo, a former airline dispatcher and pilot, said the incident likely resulted from an oversight within the airline’s dispatch operation. He told Associated Press that someone should have identified that the two aircraft would be airborne at the same time under identical flight numbers. Arroyo described the event as an example of the aviation system’s ability to recover from an error once it reaches another safety layer. The FAA and American Airlines are investigating how the duplicate callsign was allowed to occur. The investigation will determine how the delayed inbound flight and the replacement outbound aircraft were planned and identified, and why the normal safeguards for avoiding simultaneous use of the same callsign did not prevent the situation.

Two American Airlines Jets Sharing Same Callsign Avoid Near-Midair Collision In Phoenix

Vietnam Airlines Boeing 787 Suffers Tailstrike After Extended Takeoff Run At Munich SEO DES: The crew climbed to 9,000 feet and remained near Munich for two hours; Returned after tail-contact and low-tyre-pressure warnings, with damage SOCIAL: A Vietnam Airlines Boeing 787-9 flying from Munich to Hanoi took an unusually long takeoff roll on Runway 26L on August 15, 2026, before becoming airborne near the runway end. The aircraft reportedly travelled about 120 metres beyond the paved surface, with a tailstrike occurring during the late rotation. After takeoff, the crew climbed to around 9,000 feet and remained near Munich for about two hours before returning to the airport after warnings for tail contact and low tyre pressure. The aircraft sustained tail, landing-gear and tyre damage and could not taxi away after landing. The aircraft carried 271 passengers and 16 crew, all of whom were reported safe with no injuries. German authorities are leading the investigation, with Vietnamese investigators assisting, while the exact cause of the prolonged takeoff remains under investigation. Munich, Germany: A Vietnam Airlines Boeing 787-9 bound for Hanoi took an unusually long takeoff run from Munich Airport on August 15 before finally becoming airborne beyond the normal paved runway area, in an incident that resulted in runway damage, a tail strike and subsequent damage to the aircraft's landing gear. The aircraft later returned to Munich after remaining airborne for about two hours, with no injuries reported among the passengers or crew. The exact reason for the aircraft's prolonged acceleration and extremely late liftoff remains under investigation. The most significant part of the incident occurred during the takeoff roll. Video footage recorded from inside the cabin and from outside the airport shows the 787 accelerating along Runway 26L for an unusually long distance before rotation. Instead of lifting off with substantial runway remaining, the aircraft continued almost to the end of the approximately 4,000-metre runway. Reports based on flight-tracking data indicate that the aircraft reached the runway end area before becoming airborne, with reports putting the excursion beyond the paved surface at roughly 120 metres. The available video is particularly significant because it shows that the issue was not simply a conventional tailstrike during an otherwise normal rotation. The aircraft appears to remain on the ground for an unusually long period, with the runway threshold passing while the aircraft was still accelerating. It eventually rotated at the very end of the runway area, after which a large cloud of dust was visible beneath the rear of the aircraft. The reason for the unusually slow or prolonged takeoff has not been established. Online speculation has included possibilities such as an incorrect takeoff configuration, incorrect thrust or a problem affecting the aircraft's acceleration. However, none of those explanations has been confirmed by Vietnam Airlines or investigators and should not be presented as the cause. Vietnam Airlines has described the event as resulting from a technical issue and said the crew followed safety procedures. The airline has not publicly identified a specific technical failure responsible for the aircraft's unusually long takeoff roll. That distinction is important because the aircraft's subsequent warnings and damage do not, by themselves, establish what caused the initial lack of acceleration. Vietnam's aviation authorities have provided additional information on what happened after the aircraft became airborne. According to the latest reporting on the Civil Aviation Authority of Vietnam's information, warnings indicating tail contact and low tyre pressure were triggered shortly after takeoff. The authorities said the aircraft subsequently returned to Munich, while German authorities led the investigation with Vietnamese investigators assisting. After the aircraft finally lifted off, the crew did not immediately attempt to land. The Boeing 787 climbed to around 9,000 feet and remained in the Munich area for approximately two hours. During that period, the crew assessed the situation and reduced the aircraft's weight before returning to the airport. The tailstrike occurred as the aircraft became airborne after the exceptionally long takeoff run. The rear underside of the aircraft contacted the ground, producing the visible dust plume captured on video. A tailstrike can damage the aircraft's lower aft fuselage, pressure vessel, structural frames, systems, wiring and other components around the tail area. In this case, photographs and video circulating after the incident showed damage around the rear fuselage and the loss or damage of the Boeing 787's tailstrike protection component. The full extent of the structural damage, however, remains subject to technical inspection. The aircraft also sustained landing-gear and tyre damage. Reports indicate that several tyres were damaged or deflated, and footage following the return showed the aircraft unable to taxi away from the runway under its own power. The landing-gear damage also resulted in debris being left on the runway. The aircraft eventually landed back at Munich Airport, using the airport's other runway. Following the landing, the affected aircraft remained on the runway, forcing the closure of the runway and requiring airport authorities to clear debris and deal with the disabled aircraft. Traffic was subsequently handled through the other available runway, causing disruption at the German hub. There were no reported injuries among the passengers or crew. The aircraft was carrying passengers and crew on the Munich-Hanoi service; Vietnam Airlines has reported the total as 271 passengers and 16 crew members. All occupants were reported safe after the aircraft returned to Munich. The incident is now being examined by the relevant German authorities, with Vietnamese aviation investigators assisting. Investigators will need to establish why the Boeing 787 did not achieve the expected acceleration during the takeoff roll, why the aircraft reached the end of the runway area before becoming airborne and whether any technical, operational or performance-related factor contributed to the event.

Vietnam Airlines Boeing 787 Suffers Tailstrike After Extended Takeoff Run At Munich

Aircraft Crashes

Sifnos, Greece: A private Bell 206 helicopter operated by Bellavia Aviation Services crashed near the heliport on the Greek island of Sifnos on August 17, killing all three people on board. The helicopter was carrying Greek pilot Giorgos Raikos and British newlyweds Alexander Cromie and Marie Ebert. Local reports identified the couple as tourists travelling to Sifnos for their honeymoon. The flight had departed from Markopoulo, near Athens, and was scheduled to arrive at Sifnos at about 6:15 p.m. local time. The crash occurred shortly after 6 p.m. in the Tholos area, close to the island’s heliport and residential properties. Greece’s Fire Service said its operations centre was alerted at 6:17 p.m. Two firefighters and one vehicle were dispatched to tackle the fire, while a rescue team from nearby Syros was sent by a Fire Service RAFNAR high-speed vessel to reinforce the response. The helicopter crashed during its approach to Sifnos and burst into flames on impact. Firefighters recovered the bodies of all three occupants while extinguishing the blaze. Local reports said two victims were found in the wreckage, while the third was located a short distance away. The deputy mayor of Sifnos, Manolis Foundoulakis, said he arrived at the scene minutes after the crash and described the aircraft as almost completely destroyed. “What I saw was an amorphous mass, because almost nothing was left of the helicopter,” he told Greek media. The crash occurred close to homes, but reports said no neighbouring properties were damaged. A local resident told Greek media that the wreckage fell only about 50 metres from inhabited houses and the landing area, beside the Monastery of Panagia Vrysi. Witness accounts have raised the possibility of a technical problem, although no cause has been established. Residents reportedly heard an unusual or loud noise from the helicopter shortly before it crashed, while some reports said smoke was visible before the aircraft went down. Foundoulakis said residents described “a strange noise” and suspected a possible mechanical problem. Video footage circulating after the accident appears to show the helicopter beginning to rotate rapidly shortly before impact. The footage has focused investigators and aviation specialists on the possibility of a loss of tail-rotor effectiveness or failure. However, this remains only a line of inquiry and has not been established as the cause of the crash. Investigators are expected to examine the helicopter’s mechanical components, the video footage, witness statements and available flight data. The aircraft was identified by multiple reports as a Bell 206 operated by Bellavia Aviation Services, a Greek helicopter charter operator that advertises private helicopter transfers to Sifnos and other Greek destinations. Greek authorities have begun investigating the circumstances of the crash. The Fire Service initially secured the scene and conducted the preliminary investigation, while the National Air and Railway Accident Investigation and Safety Board (EODASAAM) is expected to investigate the aviation accident and determine its cause. Greece’s Ministry of Infrastructure and Transport expressed condolences to the families and said the investigation into the circumstances and causes had been transferred to the competent investigation body. The investigation will focus on the final moments of the flight, the aircraft’s technical condition, possible mechanical failure, the flight path and available records, weather conditions, witness accounts and the video showing the aircraft’s final movements. Authorities have not yet released a definitive cause, and mechanical failure, human factors and other possibilities remain under examination.

Three Onboard Killed As Bell 206 Helicopter Crashes On Greek Island Of Sifnos

Trawsfynydd, United Kingdom: Two people have died after a light aircraft crashed in a remote area near Trawsfynydd, Gwynedd, North Wales, on August 14, after failing to arrive at Caernarfon Airport as scheduled. North Wales Police said it received reports shortly after midday that the aircraft, which had been travelling from an airfield in England, had not reached its destination. A multi-agency air and ground search was launched, with the aircraft eventually located in a remote area near Trawsfynydd. Both people on board were pronounced dead at the scene. The Air Accidents Investigation Branch (AAIB) has been notified and deployed a team of investigators to the site. The incident came to light shortly after noon when the aircraft failed to arrive at Caernarfon Airport, its scheduled destination. Police and partner agencies then began searching for the missing aircraft from the air and ground. The remote location of the wreckage near Trawsfynydd made the operation challenging, although police have not publicly disclosed the exact crash site. North Wales Police Chief Superintendent Owain Llewellyn said: “This has been a challenging search operation,” while thanking the agencies involved for their professionalism and dedication. Police have not released details of what caused the aircraft to crash, and there is currently no official indication that a mechanical failure, weather conditions, pilot action or any other factor was responsible. The AAIB is now leading the technical investigation, meaning any explanation of the circumstances remains premature. The police said they would support the AAIB investigation “to ensure the circumstances leading to this incident are fully understood.” The two occupants were the only people confirmed to have been on board, and both died at the crash site. Their identities have not yet been released publicly by North Wales Police. No official information has also been released on their ages, nationalities, whether one was the pilot and the other a passenger, or their relationship to each other. Police said specialist officers would support the families and friends of those involved. Chief Superintendent Llewellyn said: “Our thoughts are with the families and friends of those involved in this tragic incident.” The aircraft was travelling from an airfield in England towards Caernarfon Airport in Gwynedd. However, neither North Wales Police nor the media reports available so far have identified the departure airfield. The exact route, flight purpose and planned arrival time have also not been disclosed. Details about the aircraft itself also remain limited. Authorities have described it only as a “light aircraft”. Its manufacturer, model, registration, operator and owner have not been publicly confirmed in the official police statement or the initial media reports reviewed for this report. Until those details are confirmed by the AAIB, police, the aircraft registry or another authoritative source, they should not be attributed to the aircraft involved. The search involved multiple agencies using both air and ground resources before the aircraft was located. The police have praised the emergency agencies involved, but the initial statement does not provide a full list of participating organisations, the number of rescuers deployed, the aircraft or helicopters used in the search, or how long it took to locate the wreckage. Those details may emerge as the investigation and recovery operation progresses. The AAIB has now sent investigators to the scene. Its role is to establish the circumstances and probable cause of the accident and, where appropriate, make safety recommendations. No preliminary findings from the investigation have been publicly released.

Two Dead After Light Aircraft Crashes In Remote Area Of North Wales, AAIB Investigates

Two US Army Soldiers Killed As Fort Hood-Based Apache Crashes During Training In Texas

Two US Army Soldiers Killed As Fort Hood-Based Apache Crashes During Training In Texas

Arizona, United States: A Glasair Sportsman 2+2 carrying two people crashed in the remote Mazatzal Wilderness west of Payson in Gila County, Arizona, on Monday, August 10, 2026, killing both occupants, Brad Lawrence, 75, and Carter Buckner, 19, of Payson, as the National Transportation Safety Board (NTSB) and Federal Aviation Administration (FAA) investigate what caused the accident. The crash site was located west of Polles Mesa in rugged wilderness terrain, with reports placing the accident at around 11 p.m. The aircraft was identified by the FAA as a Glasair Sportsman 2+2, a privately operated light aircraft. No airline or commercial operator has been identified in the reports, and authorities have not publicly confirmed the aircraft’s registration, departure point or intended destination. The NTSB said investigators were continuing to gather information, while the FAA confirmed that the agency was also investigating the crash. The Gila County Sheriff’s Office was alerted to a possible downed aircraft west of Polles Mesa in the Mazatzal Wilderness. The location’s remote and rugged terrain created significant challenges for the response. A helicopter from the Maricopa County Sheriff’s Office helped locate the wreckage, while a Pinal County Sheriff’s Office helicopter transported deputies to the crash site for the initial investigation. The Gila County Sheriff’s Office said the assistance was required because of the “remoteness and rugged terrain.” Gila County Sheriff J. Adam Shepherd thanked the neighboring agencies for their assistance following the crash. “Sheriff J. Adam Shepherd would like to thank the Maricopa County Sheriff's Office and Pinal County Sheriff's Office for their coordinated assistance,” the sheriff’s office said in a statement, adding that the sheriff extended “our deepest condolences to everyone impacted by this tragedy.” The victims were identified as Lawrence and Buckner, both Payson residents. Authorities have not established publicly who was flying the aircraft at the time of the crash. The circumstances leading up to the accident, including the aircraft’s flight path and what happened immediately before impact, remain under investigation. Lawrence was well known in the local aviation community. According to FOX 10, he served as vice president of the Payson Pilots Association for nearly three years and was described by fellow pilots as an experienced aviator with a strong passion for flying. “He was a very experienced aviator. He had two airplanes. His own hanger and house beside the hanger, so that gives you an indication of his passion for aviation,” Payson Pilots Association president Kevin McCully told FOX 10. Lawrence was also involved in aviation outreach. Kevin McCully, president of the Payson Pilots Association said Lawrence had participated in the Experimental Aircraft Association’s Young Eagles program, which provides young people with introductory flights to encourage interest in aviation. McCully said he did not believe the fatal flight was part of the Young Eagles program, but suggested Lawrence may have been demonstrating his aircraft and helping Buckner become involved in aviation. “He loved to travel. Loved his airplane of course. And he was just a wonderful man,” Debbie Snow, a member of Lawrence’s family, told FOX 10 while remembering the longtime pilot. McCully added, “We’re all going to miss him very much.” The crash investigation is now being led at the federal level by the NTSB, with the FAA assisting. As of the latest available reports, investigators had not released a probable cause, possible mechanical issue, weather factor or other explanation for the crash. Further details are expected as investigators examine the wreckage, aircraft records, flight information and other evidence from the remote crash site.

Two Killed As Small Plane Crashes Near Payson, Arizona; NTSB Probes Fatal Accident

Two Pilots Killed As Sikorsky S-64 Crashes Fighting Utah’s Widemouth 2 Fire

Two Pilots Killed As Sikorsky S-64 Crashes Fighting Utah’s Widemouth 2 Fire

Airlines

US Court Delays Google’s $10M Spirit Airlines Data Deal After Flight Attendants Object

US Court Delays Google’s $10M Spirit Airlines Data Deal After Flight Attendants Object

Mogadishu, Somalia: Somali Airlines is targeting a return to scheduled passenger operations around mid-September 2026, more than 35 years after the national carrier stopped flying amid Somalia’s civil war, according to the country’s Civil Aviation Authority. Ahmed Ma’allin, director of the Somali Civil Aviation Authority, said the relaunch preparations had reached their final stage. “Somali Airlines is in its final stages, the first flight will be around mid September,” he said. The latest target would mark the airline’s first scheduled commercial operations since 1991, when its services were halted following the collapse of Somalia’s central government and the outbreak of civil war. Somali Airlines was established in 1964 and previously operated a network linking Somalia with destinations in Africa, the Middle East and Europe. The September target is the latest in a series of attempts to restore the state-owned carrier. In July 2025, the Somali government announced an agreement involving two Airbus A320 aircraft as the initial fleet for the revived airline. At the time, Transport and Civil Aviation Minister Mohamed Farah Nuuh said the aircraft were expected to enter service within two months. The minister said during the July 2025 announcement in Mogadishu that the government had acquired two A320s and planned to expand the fleet. “For now, we shall start with these two, then two or three more will follow,” he said. The government subsequently set additional timelines for the airline’s return, including a target to resume operations before the end of 2025. That deadline passed without the carrier beginning scheduled commercial services, making the September 2026 target another attempt to turn the long-running revival plan into an operating airline. The initial fleet is expected to comprise two Airbus A320 aircraft secured under the 2025 agreement. The government has indicated that the two aircraft are only the first phase of a wider fleet-building programme, with additional aircraft expected as the airline expands. However, aircraft acquisition alone does not complete the restart process. The airline must satisfy safety and regulatory requirements, obtain the necessary operating approvals and ensure that pilots, engineers, cabin crew and other personnel are appropriately qualified. Maintenance arrangements, insurance, flight planning, airport handling and other operational systems must also be in place before regular commercial services can begin. The Somali Civil Aviation Authority’s current aeronautical information system shows that Somalia has continued developing its regulatory and operational aviation framework. Its 2026 aeronautical information publication is effective from July 9, 2026, and includes current material covering Somalia’s airspace, airports and flight operations. Despite the September target, the authorities have not publicly disclosed a specific inaugural route, destination list or frequency for Somali Airlines in the August 2026 reports reviewed. The reports also do not establish a confirmed date within September beyond Ma’allin’s indication that the first flight could be around the middle of the month. The airline’s historical network, however, included destinations in East Africa, the Middle East and Europe. The revived carrier is expected to operate initially with the A320s and expand its network as additional aircraft become available. The government’s longer-term objective is to build a national airline capable of competing with established international and regional carriers serving Somalia. The revival also has significance beyond the airline itself. Somali officials have previously linked the project to improved connectivity for the Somali diaspora, employment in aviation and related industries, reduced dependence on foreign carriers and the broader rebuilding of the country’s aviation sector. The government’s 2025 announcement was made at the Prime Minister’s Office in Mogadishu, where officials confirmed the acquisition of the two A320 aircraft. The official Somali National News Agency, SONNA, described the return of the carrier as part of Somalia’s broader recovery and rebuilding efforts. Somalia has also made wider progress in rebuilding its aviation system after decades of disruption. The Somali Civil Aviation Authority’s current publications show an active regulatory framework, while the country has continued developing airport and air-navigation infrastructure.

Somali Airlines Targets Mid-September Return After 35 Years Of Shutdown

Air India Group Mandates Substance Screening For All Pilots Following A320neo Incident SEO DES: The move follows an August 4 incident in which the captain underwent substance testing that returned a non-negative result after a sudden 300 ft altitude loss SOCIAL: Air India and Air India Express have begun one-time mandatory substance screening for more than 5,000 pilots, going beyond DGCA’s requirement of annual random testing of at least 10% of flight crew. The exercise began August 13, with pilots being tested at training centres, briefing locations and other designated facilities. No completion figures have been officially released yet. The expanded testing follows the August 4 Phuket-Delhi incident, in which an Air India A320neo lost about 300 feet in altitude, leaving 24 passengers and crew injured. Both pilots underwent mandatory screening, with the captain’s initial test requiring confirmation. A later media report said the captain tested positive for marijuana in the confirmatory test, although this has not been officially confirmed by DGCA or the Ministry of Civil Aviation. Civil Aviation Minister K. Ram Mohan Naidu said the incident is being investigated with aviation safety as the priority. The expanded screening marks a stronger step by Air India to monitor pilot fitness, while the airline and regulator are expected to assess the findings and determine any further safety measures. New Delhi, India: Air India and Air India Express have begun mandatory substance screening for more than 5,000 pilots, with the airline launching the one-time, group-wide testing exercise on August 13. The programme covers pilots across both carriers and goes beyond the existing regulatory requirement for airlines to randomly test at least 10% of flight crew for psychoactive substances each year. Air India has not publicly disclosed how many pilots have completed the new screening or what percentage of the total pilot pool has been tested. Current reports describe the exercise as ongoing rather than completed. The testing covers substances and medications prohibited under aviation regulations and is being conducted at multiple points across the airline’s operations. According to an internal Air India communication cited by Reuters, pilots can be screened alongside training sessions at the airline’s Gurugram academy, after flights at briefing centres and offices, and at locations designated according to their home bases. Air India Express pilots are included in the exercise. The airline has said the additional screening is intended to strengthen safety standards and reassure passengers and other stakeholders. Air India announced the expanded testing programme on August 13, saying it already complies with the Directorate General of Civil Aviation’s existing requirements but had decided to go further. The airline’s senior vice-president for flight operations, Captain Manish Uppal, told pilots that protecting passenger trust was central to the decision. After this one-time exercise, Air India is expected to return to the applicable regulatory framework, which currently requires annual random testing of at least 10% of flight crew. The move follows the August 4 serious incident involving an Air India Airbus A320neo operating from Phuket to Delhi. The aircraft experienced a sudden loss of about 300 feet in altitude while cruising before stabilising and continuing to Delhi. The flight was carrying 137 passengers and eight crew members, and subsequent reports said 24 passengers and crew members were injured. Following the incident, both pilots underwent mandatory screening for psychoactive substances after the aircraft landed in Delhi. The Ministry of Civil Aviation said the captain’s initial result required further laboratory confirmation, and both pilots were removed from flying duties while the investigation continued. The Aircraft Accident Investigation Bureau is examining flight data, aircraft systems, maintenance and operational records, medical information and crew accounts, with Airbus and France’s BEA assisting the Indian investigation. The subsequent development that brought the pilot-testing issue into sharper focus was the reported result of the confirmatory laboratory test. Several media outlets reported on August 11, citing sources familiar with the matter, that the captain had tested positive for marijuana in the confirmatory test. Separately, the Ministry of Civil Aviation officially summoned Air India CEO Campbell Wilson for a briefing on the investigation. That result, however, has not been publicly confirmed in an official statement by the DGCA or the Ministry of Civil Aviation. The official position previously released by the ministry was that the captain’s initial screening required confirmatory testing. The reported positive confirmatory result therefore remains attributed to sources familiar with the matter rather than an officially published regulatory finding. Civil Aviation Minister K. Ram Mohan Naidu has meanwhile maintained that the incident is being investigated and that aviation safety remains the priority. The government’s response has included directing the regulator to strengthen oversight of psychoactive-substance testing, while Air India has moved beyond the minimum regulatory requirement by subjecting its entire pilot pool to the expanded screening exercise. The wider significance of the move will depend not only on the completion of the current testing programme, but also on how the airline and regulator translate its findings into long-term safety and fitness-for-duty measures.

Air India Group Mandates Substance Screening For All Pilots Following A320neo Incident

international operations. Beijing, China: Air China’s COMAC C919 completed its first scheduled international passenger service on August 12, 2026, when flight CA723 departed Beijing Capital International Airport at about 3 p.m. for Ulaanbaatar, Mongolia, marking the first time the Chinese-developed narrowbody aircraft carried passengers on a regular route between China and another country. The aircraft arrived at Chinggis Khaan International Airport at about 4:58 p.m. with 121 passengers onboard. China operates the route daily, with CA723 scheduled to depart Beijing at 3 p.m. and arrive in Ulaanbaatar at 5:15 p.m., while return flight CA724 departs Ulaanbaatar at 6:30 p.m. and reaches Beijing at 8:35 p.m., with all times local. The Beijing-Ulaanbaatar operation marks the latest stage in the C919’s commercial development since the aircraft entered airline service in 2023. The C919 was developed by Commercial Aircraft Corporation of China (COMAC), the country’s state-owned commercial aircraft manufacturer, as China’s first domestically developed narrowbody mainline jet built to international airworthiness standards. COMAC lists the aircraft’s basic configuration at 158 to 192 seats, with a range of 4,075 to 5,555 kilometers. The programme reached a major milestone on November 2, 2015, when the first C919 completed final assembly and rolled out, followed by its maiden flight on May 5, 2017. The aircraft received its type certificate from the Civil Aviation Administration of China (CAAC) on September 29, 2022, and the first C919 was delivered to launch customer China Eastern Airlines on December 9, 2022. China Eastern subsequently operated the aircraft’s first commercial passenger flight on May 28, 2023, completing the development, manufacturing, certification and commercial-entry stages of the programme. The C919’s international exposure began before Wednesday’s scheduled service. In February 2024, a China Eastern C919 flew to Singapore for the Singapore Airshow, marking the aircraft’s first appearance at the event. COMAC then conducted a series of demonstration flights in Southeast Asia in 2024, including visits to Vietnam, Laos, Cambodia, Malaysia and Indonesia, to assess the aircraft’s compatibility with local airports, ground-support equipment and operating procedures. The C919 programme has also expanded beyond the original aircraft configuration. On July 29, 2026, COMAC conducted the first flight of the C919 high-altitude variant at Shanghai Pudong International Airport. The aircraft flew for 1 hour and 59 minutes and completed all planned test items. COMAC said the variant incorporates a shortened fuselage and system modifications designed for high-altitude operations. The aircraft remains heavily dependent on an international supply chain. Its LEAP-1C engines are supplied by CFM International, the GE Aerospace-Safran joint venture, while Honeywell, Collins Aerospace, Parker Hannifin, Moog and other Western companies supply systems and equipment. Air Data News reported that this dependence became particularly visible during the 2025 US-China trade dispute, when Washington temporarily suspended export licenses involving technology and engines destined for COMAC before the restrictions were later lifted. The C919’s dependence on foreign technology has also been a factor in China’s efforts to develop domestic alternatives. Replacing established Western systems requires more than manufacturing substitute components, because replacement systems must meet requirements for reliability, weight, fuel efficiency, durability and certification. Production has been another major part of the programme’s development. COMAC delivered 15 C919 aircraft to customers in 2025, well below an earlier target of 75 aircraft. South China Morning Post reported in January 2026 that COMAC was targeting at least 28 deliveries during 2026 and that, if production reached the expected pace, the manufacturer could produce one C919 every 10 to 15 days. The report said two aircraft had already taken shape during the first three weeks of 2026 and were undergoing delivery procedures. COMAC has also been expanding its production infrastructure. ChinaTravelNews reported in July 2026 that deliveries were expected to reach at least 28 C919 aircraft in 2026, with production potentially increasing to one aircraft every 10 to 15 days. The second phase of the C919 final-assembly-line expansion in Shanghai Pudong is expected to take annual production capacity above 100 aircraft, while COMAC has set a longer-term target of 200 aircraft a year by 2029. Earlier production plans were even more ambitious. In March 2025, COMAC raised its planned C919 production capacity for that year to 75 aircraft from an earlier target of 50, while setting a 200-aircraft annual production objective for 2029. The actual 2025 delivery figure subsequently came in at 15 aircraft. The C919’s order book has been concentrated largely among Chinese airlines. By December 2024, Air Data News reported that Air China, China Southern and China Eastern together had ordered 306 C919 aircraft, although only 14 had been delivered to the three carriers at that point. COMAC was simultaneously exploring potential overseas customers in Indonesia, Cambodia and Kazakhstan, while Vietnam Airlines, AirAsia and Brazil’s Total Linhas A

China’s Homegrown C919 Makes International Debut With Air China Flight To Mongolia

WestJet To Pay C$4.5 Million In Decade-Long Flight Attendants’ Harassment Case SEO DES: The case stemmed from alleged sexual assaults involving a WestJet pilot in 2008 and 2010 followed by claims of inadequate investigations & harassment reporting SOCIAL: The Supreme Court of British Columbia approved WestJet’s C$4.5 million settlement on August 10, 2026, ending a decade-long sexual-harassment class action involving 3,452 current and former female flight attendants. The settlement was found fair, reasonable and in the class members’ best interests. The settlement follows allegations that WestJet failed to maintain an effective workplace free from harassment. It includes an independent assessment of workplace harassment, underreporting and the effectiveness of WestJet’s reporting and response systems, although the airline denies wrongdoing and admits no liability. Eligible claimants are expected to receive about C$470 each, subject to final administration costs. Deloitte LLP will administer the claims process once it opens, while the settlement remains subject to a mandatory 30-day finalization period following the August 10 approval. Vancouver, Canada: WestJet’s C$4.5 million settlement with female flight attendants in a decade-long sexual harassment class action was approved by the Supreme Court of British Columbia on August 10, 2026, bringing the long-running case closer to an end while requiring the airline to commission an independent workplace assessment into harassment, underreporting and the effectiveness of its reporting systems. The settlement covers current and former female WestJet mainline flight attendants who worked between April 4, 2014, and February 28, 2021, and who did not opt out of the class action. The court found the settlement fair, reasonable and in the best interests of the class. Under the approved agreement, the C$4.5 million settlement fund will first cover court-approved legal fees, disbursements, applicable taxes, settlement administration expenses and an honorarium for representative plaintiff Mandalena Lewis. The remaining amount will be distributed among eligible class members who submit valid claims. The class-action lawyers currently estimate that each eligible claimant who files a valid claim will receive about C$470, although the final amount could change slightly after administration costs are finalized. The settlement does not include an admission of liability or wrongdoing by WestJet. The airline continues to deny the allegations, and the disputed claims were never determined at trial. WestJet has also not agreed to some of the major forms of relief originally sought by the lawsuit, including mandatory anti-harassment training for pilots, an admission of wrongdoing or an admission that it breached its employment contracts. Instead, one of the key non-monetary terms requires WestJet to retain an independent and qualified third party to assess the prevalence of workplace harassment, the extent to which harassment is underreported, and how the airline’s systems for reporting and responding to harassment can be made more effective. WestJet must provide employees with a summary of the assessment’s findings. Deloitte LLP has been appointed as the independent claims administrator and is preparing a secure online claims portal. Eligible class members do not need to submit anything yet. Once the portal is ready, they will receive notice containing the claims link, instructions, the deadline and payment information. Class members will have three months from the date that notice is sent to submit a valid claim. Deloitte is then expected to review and process the claims within up to 60 days after the claims deadline, with approved payments to be made through Interac e-Transfer. The settlement is not yet final. A mandatory 30-day period follows the court’s August 10 approval before the agreement becomes final. Lewis, a former WestJet flight attendant, launched the class action in April 2016 after alleging that the airline had failed to uphold its promise to provide female employees with a workplace free from harassment. The case grew out of allegations surrounding an incident involving Lewis and a WestJet pilot during a layover in Maui, Hawaii, in January 2010, when Lewis was 25. According to court-related accounts, Lewis alleged that she was sexually assaulted by the pilot and that another female flight attendant had also been assaulted by the same pilot in 2008. Lewis alleged that she reported the 2010 incident to WestJet and that the airline’s subsequent investigation was inadequate. She said she received limited information about how the investigation was being conducted and was warned that she could face discipline if she discussed the incident with others. WestJet managers later told her that the pilot had not been terminated following the investigation, although restrictions were placed on his ability to fly to certain destinations and Lewis was not supposed to be scheduled to work with him. Lewis later learned in August 2015 that another female flight attendant had allegedly reported an assault involving the same pilot in 2008. She argued that if WestJet had properly investigated that earlier complaint and disciplined the pilot, she would not have been assaulted. The allegations formed part of her broader claim that the airline had failed to create and maintain an effective system to prevent and respond to harassment. Lewis also alleged that after she reported the incident to police in Maui, WestJet rerouted the pilot so that he would not be available to face questioning there. Lewis eventually abandoned an individual civil claim and pursued a class action after learning that other flight attendants had experienced harassment. Her employment with WestJet ended in 2016, with court documents submitted by the airline describing her termination as being for “gross insubordination”; Lewis and her legal team alleged that the termination was retaliation for her efforts to hold WestJet accountable internally. These allegations were disputed and were not established at trial. Lewis had worked for WestJet from March 2008 until January 2016. In the litigation, she described observing and experiencing inappropriate conduct involving female flight attendants, particularly conduct by pilots. Her legal case, however, was structured primarily as a breach-of-contract claim, rather than as a conventional personal-injury or tort claim. The argument was that WestJet’s anti-harassment commitments were incorporated into employees’ contracts and that the company had failed to implement and maintain an effective harassment-prevention system. The lawsuit initially faced a major legal obstacle. In December 2017, the B.C. The Supreme Court rejected WestJet’s attempt to strike the claim. WestJet argued, among other things, that the dispute belonged before the Canadian Human Rights Tribunal, that disgorgement was not an available remedy, that the claim amounted to an abuse of process and that Lewis’s action was barred by limitation rules. Justice Humphries rejected those arguments, allowing the case to proceed. WestJet appealed, but the contractual foundation of the case survived. The B.C. The Court of Appeal ultimately rejected the airline’s jurisdictional argument, holding that an employment contract could provide a legal basis for a court claim even where human-rights legislation also provided avenues of redress. The Supreme Court of Canada did not take up the matter. The first attempt to certify the matter as a class action was unsuccessful. In 2021, the B.C. The Supreme Court accepted that most of Lewis’s proposed common issues could potentially be addressed collectively but concluded that a class proceeding was not the preferable procedure. The court considered the Canadian Human Rights Tribunal a more practical avenue because it could provide both systemic and individual remedies. That decision was overturned in significant part by the B.C. Court of Appeal on April 19, 2022. The appellate court certified the class action, finding that the issues surrounding WestJet’s alleged failure to implement and enforce its anti-harassment commitments could be examined collectively. The court rejected the argument that human-rights proceedings were necessarily a preferable alternative to the class action. The class period was subsequently the subject of another dispute. WestJet sought to shorten the period covered by the certification order to July 31, 2018, when the Canadian Union of Public Employees was certified as the bargaining agent for WestJet flight attendants. In November 2023, the court rejected the attempt to cut off the class period at that point, leaving February 28, 2021, as the end of the class period. The litigation also reached the disclosure stage. In December 2024, Justice Jacqueline Hughes ordered WestJet to produce harassment-related records covering the class period. The court said the airline had been slow and potentially adversarial in producing documents. WestJet had provided 24 harassment complaints, but internal statistics indicated that significantly more complaints existed. The ruling said some complaints involved sexual harassment and sexual assault. The court ordered WestJet to produce harassment complaints made by flight attendants during the class period from April 4, 2014, to February 28, 2021, rather than limiting disclosure only to complaints against male pilots involving class members. Justice Hughes did not, however, extend the case to harassment complaints involving WestJet’s entire workforce, finding that the lawsuit concerned the employment contracts of flight attendants. The disclosure dispute was significant because the court record indicated that WestJet’s internal statistics showed substantially more complaints than the 24 files initially produced. The court also found that the requested documents concerning exit interviews, complaints, the company’s core policies and anti-harassment program, investigations and the people conducting those investigations were relevant to the class action, although documents concerning settlements were excluded from the production order. The settlement negotiations eventually produced the C$4.5 million agreement. The Guardian reported that the settlement was finalized on June 22, 2026, following months of negotiations, before receiving judicial approval on August 10. The approved settlement covers 3,452 female flight attendants. The settlement amount became a point of controversy among some class members. Eight women had objected to court approval in February after details of the proposed agreement emerged, arguing that the compensation was too low and that the settlement did not provide sufficient accountability. Lewis herself expressed disappointment after the approval, telling the Guardian that she was glad the litigation was over but was exhausted and “shaking my head.” She said she had been advised that the settlement was the best result that could be achieved as legal expenses continued to accumulate. Lewis also compared the outcome with WestJet’s separate C$12.5 million baggage-fee class-action settlement, which was nearly three times larger. She said the outcome did not amount to the justice she had sought, telling, “We didn’t get justice here.” The settlement nevertheless provides a structural measure beyond the monetary payment. The independent workplace assessment is intended to examine whether harassment is occurring, how frequently employees may be failing to report it and whether existing mechanisms for reporting and responding to complaints are effective. WestJet will be required to provide employees with a summary of the findings. WestJet said it was pleased to have reached a mutually agreed settlement. In a statement, the airline said it remained committed to strengthening its operations and training, with a focus on the safety and wellbeing of its employees, and on advancing a culture of empowerment. With the August 10 approval, the litigation has moved from the courtroom dispute over WestJet’s alleged anti-harassment obligations to the implementation of the settlement. The agreement must pass the 30-day finalization period, after which Deloitte will begin processing eligible claims once the claims process opens. The class-action website says the claims portal and exact deadline will be published when the process begins.

WestJet To Pay C$4.5 Million In Decade-Long Flight Attendants’ Harassment Case

Incidents

Munich, Germany: A Lufthansa Airbus A380-800 operating flight LH459 from San Francisco International Airport to Munich Airport touched down prematurely near the eastern threshold of Munich’s southern runway on Monday evening, August 17, 2026, damaging runway-threshold lighting. The aircraft, registered D-AIML, was carrying 351 passengers after completing the approximately 11-hour transatlantic flight from San Francisco, United States, to Munich, Germany. All passengers and crew were able to leave the aircraft normally, with no injuries reported. Flight records identify D-AIML as an Airbus A380-841 operated by Lufthansa, while Lufthansa’s published schedule confirms LH459 operates between San Francisco and Munich. According to Lufthansa, the aircraft touched down on the concrete surface before the white-marked runway threshold. During the premature touchdown, the aircraft struck lighting installed around the runway threshold, causing damage to the runway’s visual guidance system. Lufthansa spokesperson Jörg Waber said in a statement, “We can confirm that an AirVIbus A380-800 damaged runway lighting in the area of the runway threshold.” He added that the aircraft had arrived from San Francisco with 351 passengers, subsequently taxied to its assigned position and that all passengers left the aircraft normally. The incident occurred on Munich Airport’s southern runway, identified as Runway 26L when used for approaches from the east. The Deutsche Flugsicherung describes Runway 26L as Munich’s southern runway and says aircraft approaching it from the east use its instrument landing system. Munich Airport characterized the infrastructure damage as minor. According to the airport, a “minor damage” to lighting was identified around the eastern threshold of the southern runway. The damaged lighting was repaired promptly, allowing the runway to return to service less than an hour after the A380 landed. The exact circumstances that caused the A380 to touch down before the designated threshold remain unclear. No official finding has attributed the event to pilot error, weather, aircraft malfunction, runway conditions or any problem with the airport’s approach system. The aircraft touched down short of the marked threshold and that its landing gear struck approach lights. The cause remains under investigation. Germany’s Federal Bureau of Aircraft Accident Investigation, or BFU, has opened an investigation into the occurrence. The A380 involved was approximately 13 years old and carried the registration D-AIML. Flight-history records identify the aircraft as an Airbus A380-841 operated by Lufthansa. The airline’s A380 configuration can accommodate up to 509 passengers, although 351 passengers were onboard LH459 during this particular flight. Separately, on August 15, 2026, a Vietnam Airlines Boeing 787-9 bound for Hanoi experienced an unusually long takeoff run at Munich Airport. The aircraft continued accelerating almost to the end of Runway 26L and reportedly travelled about 120 metres beyond the paved surface before becoming airborne. During the extremely late rotation, its rear underside struck the ground, causing a tailstrike and damage to the aft fuselage. After takeoff, warnings for tail contact and low tyre pressure prompted the crew to remain near Munich at around 9,000 feet for about two hours before returning. The aircraft sustained further landing-gear and tyre damage, with several tyres damaged or deflated, and was unable to taxi after landing. It was carrying 271 passengers and 16 crew, all of whom were reported safe. German authorities are leading the investigation, with Vietnamese investigators assisting, while the cause of the unusually prolonged takeoff remains under investigation.

Lufthansa A380 Lands Short At Munich Airport, Damages Runway Lights During Its Landing

Milan, Italy: A baggage cart carrying checked luggage caught fire at Milan Malpensa Airport in Italy on Sunday, August 16, shortly before the baggage was due to be handled for a British Airways flight to London Heathrow, prompting airport firefighters to intervene and damaging a small number of passengers' bags. The incident occurred on the airport apron and did not involve a fire onboard the aircraft. The fire involved an Aviapartner baggage-handling cart at Milan Malpensa. The handling company operates ground services at the airport, and the cart had just completed baggage handling associated with a British Airways flight arriving from London when it caught fire. Initial reports focused on the possibility of a lithium-ion battery inside one of the bags, but subsequent airport-source information pointed to an electrical fault in the ground vehicle instead. The incident was captured on video by former BBC journalist Jon Sopel, who was at Malpensa waiting to travel on British Airways flight BA585 from Milan to London Heathrow. The footage showed dense black smoke rising from the baggage container, with flames visible around the luggage. Ground personnel moved other baggage containers away from the burning unit to prevent the fire from spreading before airport fire crews arrived. The aircraft associated with BA585 was an Airbus A321neo registered G-NEOT, powered by two CFM International LEAP-1A32 engines. The scheduled route was Milan Malpensa Airport (MXP) to London Heathrow Airport (LHR), with British Airways operating the service under flight number BA585. The fire occurred before the affected luggage could create a fire risk inside the aircraft. The burning baggage unit remained on the ground and was dealt with by airport emergency crews. The other containers were moved away from the fire, helping prevent the flames from spreading to additional baggage or equipment. Firefighters extinguished the blaze rapidly using water. British Airways confirmed that some passengers' checked baggage was damaged. In a statement, the airline said: “We’re aware of a small number of checked bags that were damaged by fire while on the ground at Milan Malpensa Airport. The incident was quickly dealt with, and there were no injuries or impact to any flights.” The airline added: “We’ve been in contact with the small number of customers whose bags are affected to apologise and provide support. We are working closely with our partners, and an investigation is underway to establish the cause.” That statement is significant because it confirms that the fire affected checked baggage on the ground but did not result in injuries or a fire onboard the aircraft. It also shows that British Airways had not initially announced a confirmed cause and was relying on an investigation with its ground-handling partners. The investigation remained underway, while British Airways confirmed that only a small number of checked bags were damaged and that there were no injuries.

British Airways BA585 Baggage Cart Carrying Checked Luggage Catches Fire At Milan

Krasnoyarsk, Russia: Hainan Airlines Flight HU753, operating from Beijing Capital International Airport in China to Manchester Airport in the United Kingdom, diverted to Krasnoyarsk International Airport in Russia on August 15 after the Airbus A330-300 developed a mechanical fault while flying over Siberia. The aircraft landed safely, with no injuries, deaths or damage reported. The flight was operated by an Airbus A330-343, registration B-304L, with 230 people on board. Flight-tracking data showed the aircraft departed Beijing for Manchester and was cruising at approximately FL340, or 34,000 feet, when the problem occurred. The aircraft was around 190 nautical miles southeast of Krasnoyarsk when it descended to approximately FL200 and diverted toward Krasnoyarsk International Airport. According to reports, the problem emerged approximately four hours into the flight. The aircraft's sensors detected the fault and the crew issued an emergency signal before diverting to Krasnoyarsk.. Russian emergency authorities had prepared for the aircraft's arrival, deploying 51 personnel and 15 vehicles. The response included 39 personnel and 11 vehicles from Russia's Ministry of Emergency Situations, according to reports. Emergency teams were positioned as a precaution, but the aircraft completed the landing without an accident. Russia's Emergencies Ministry confirmed that there were no injuries or deaths and that neither the aircraft nor airport infrastructure was damaged. English- and Chinese-speaking airport personnel were also reported to have assisted passengers and crew following the landing. Hainan Airlines confirmed the diversion and apologised to passengers. In its statement, the airline said: “On 15 August 2026, our flight HU753 (Beijing–Manchester) diverted to Krasnoyarsk International Airport in Russia due to a mechanical fault. The flight landed safely at 07:28 Beijing time.” The airline added: “The company plans to replace the aircraft to operate the onward flight. We will properly arrange passenger service support to ensure safe arrival at the destination. We sincerely apologise for any inconvenience caused to passengers.” Hainan Airlines also reiterated: “Hainan Airlines always adheres to the principles of safety first and passengers first, providing safe, comfortable and efficient services.” The exact nature of the mechanical fault has not been officially disclosed. Hainan Airlines described the problem as a “mechanical fault,” while Russian authorities referred to it as a technical malfunction. Therefore, claims that the incident involved a particular system failure should be treated cautiously. The diversion left passengers in Krasnoyarsk while Hainan Airlines arranged an onward journey. The airline said a replacement aircraft would be sent to Krasnoyarsk to continue the service to Manchester, while passenger support arrangements were being made.

Hainan Airlines Flight HU753 Diverts To Russia After Mechanical Fault Over Siberia

Phoenix, United States: A potential mid-air collision was averted near Phoenix Sky Harbor International Airport on August 14, 2026, after two American Airlines Boeing 737-800s were simultaneously operating under the same “American 2482” callsign while flying in opposite directions between Phoenix and Chicago. One aircraft was arriving at Phoenix from Chicago O’Hare International Airport, while another had just departed Phoenix for Chicago. The unusual overlap occurred after the inbound Flight 2482 was delayed by weather, prompting American Airlines to use another aircraft already at Phoenix so passengers waiting for the outbound service could depart on schedule. Because Flight 2482 normally operates as a Chicago-Phoenix round trip using the same flight number, the replacement aircraft also operated under the 2482 identification. The resulting callsign duplication placed both aircraft in the same area of airspace while communicating on the same frequency. Flightradar24 reported that the arriving aircraft was descending through about 11,000 feet while the departing aircraft was climbing toward 9,000 feet when the duplication was recognized. The FAA said the aircraft maintained the required separation throughout the incident. The Phoenix air traffic controller quickly recognized the problem and began distinguishing the two aircraft as “American 2482 on the arrival” and “American 2482 on the departure.” The controller then kept the arriving aircraft above the departing aircraft and prevented the departure from climbing into the arrival’s altitude, maintaining vertical separation as their flight paths converged. The controller also alerted both crews to the other aircraft. Reports said the pilots were able to see each other while they were still miles apart, providing an additional layer of awareness as the two aircraft crossed paths. No source has publicly released an exact minimum horizontal distance between the aircraft, and the FAA has confirmed only that required separation was maintained. The incident was captured in air traffic control audio published by ATC.com and subsequently highlighted by media outlets. After the departing aircraft had cleared the area, the controller said, “I’ve been working air traffic for 25 years. I’ve never seen two aircraft pretty much merge with the same call sign. That’s pretty incredible.” The arriving pilot later complimented the controller, saying “nice work.” The controller responded, “It could have been disastrous, but I’m glad it worked out.” The precise passenger and crew numbers aboard the two Boeing 737-800s have not been publicly disclosed by the FAA or American Airlines. Both aircraft completed their flights safely, with no injuries or collision reported. American Airlines said, “The diligence and professionalism of air traffic controllers and our pilots ensured required separation was always maintained and the issue was identified and addressed. Both flights continued safely and without incident.” Aviation safety expert Steve Arroyo, a former airline dispatcher and pilot, said the incident likely resulted from an oversight within the airline’s dispatch operation. He told Associated Press that someone should have identified that the two aircraft would be airborne at the same time under identical flight numbers. Arroyo described the event as an example of the aviation system’s ability to recover from an error once it reaches another safety layer. The FAA and American Airlines are investigating how the duplicate callsign was allowed to occur. The investigation will determine how the delayed inbound flight and the replacement outbound aircraft were planned and identified, and why the normal safeguards for avoiding simultaneous use of the same callsign did not prevent the situation.

Two American Airlines Jets Sharing Same Callsign Avoid Near-Midair Collision In Phoenix

Vietnam Airlines Boeing 787 Suffers Tailstrike After Extended Takeoff Run At Munich SEO DES: The crew climbed to 9,000 feet and remained near Munich for two hours; Returned after tail-contact and low-tyre-pressure warnings, with damage SOCIAL: A Vietnam Airlines Boeing 787-9 flying from Munich to Hanoi took an unusually long takeoff roll on Runway 26L on August 15, 2026, before becoming airborne near the runway end. The aircraft reportedly travelled about 120 metres beyond the paved surface, with a tailstrike occurring during the late rotation. After takeoff, the crew climbed to around 9,000 feet and remained near Munich for about two hours before returning to the airport after warnings for tail contact and low tyre pressure. The aircraft sustained tail, landing-gear and tyre damage and could not taxi away after landing. The aircraft carried 271 passengers and 16 crew, all of whom were reported safe with no injuries. German authorities are leading the investigation, with Vietnamese investigators assisting, while the exact cause of the prolonged takeoff remains under investigation. Munich, Germany: A Vietnam Airlines Boeing 787-9 bound for Hanoi took an unusually long takeoff run from Munich Airport on August 15 before finally becoming airborne beyond the normal paved runway area, in an incident that resulted in runway damage, a tail strike and subsequent damage to the aircraft's landing gear. The aircraft later returned to Munich after remaining airborne for about two hours, with no injuries reported among the passengers or crew. The exact reason for the aircraft's prolonged acceleration and extremely late liftoff remains under investigation. The most significant part of the incident occurred during the takeoff roll. Video footage recorded from inside the cabin and from outside the airport shows the 787 accelerating along Runway 26L for an unusually long distance before rotation. Instead of lifting off with substantial runway remaining, the aircraft continued almost to the end of the approximately 4,000-metre runway. Reports based on flight-tracking data indicate that the aircraft reached the runway end area before becoming airborne, with reports putting the excursion beyond the paved surface at roughly 120 metres. The available video is particularly significant because it shows that the issue was not simply a conventional tailstrike during an otherwise normal rotation. The aircraft appears to remain on the ground for an unusually long period, with the runway threshold passing while the aircraft was still accelerating. It eventually rotated at the very end of the runway area, after which a large cloud of dust was visible beneath the rear of the aircraft. The reason for the unusually slow or prolonged takeoff has not been established. Online speculation has included possibilities such as an incorrect takeoff configuration, incorrect thrust or a problem affecting the aircraft's acceleration. However, none of those explanations has been confirmed by Vietnam Airlines or investigators and should not be presented as the cause. Vietnam Airlines has described the event as resulting from a technical issue and said the crew followed safety procedures. The airline has not publicly identified a specific technical failure responsible for the aircraft's unusually long takeoff roll. That distinction is important because the aircraft's subsequent warnings and damage do not, by themselves, establish what caused the initial lack of acceleration. Vietnam's aviation authorities have provided additional information on what happened after the aircraft became airborne. According to the latest reporting on the Civil Aviation Authority of Vietnam's information, warnings indicating tail contact and low tyre pressure were triggered shortly after takeoff. The authorities said the aircraft subsequently returned to Munich, while German authorities led the investigation with Vietnamese investigators assisting. After the aircraft finally lifted off, the crew did not immediately attempt to land. The Boeing 787 climbed to around 9,000 feet and remained in the Munich area for approximately two hours. During that period, the crew assessed the situation and reduced the aircraft's weight before returning to the airport. The tailstrike occurred as the aircraft became airborne after the exceptionally long takeoff run. The rear underside of the aircraft contacted the ground, producing the visible dust plume captured on video. A tailstrike can damage the aircraft's lower aft fuselage, pressure vessel, structural frames, systems, wiring and other components around the tail area. In this case, photographs and video circulating after the incident showed damage around the rear fuselage and the loss or damage of the Boeing 787's tailstrike protection component. The full extent of the structural damage, however, remains subject to technical inspection. The aircraft also sustained landing-gear and tyre damage. Reports indicate that several tyres were damaged or deflated, and footage following the return showed the aircraft unable to taxi away from the runway under its own power. The landing-gear damage also resulted in debris being left on the runway. The aircraft eventually landed back at Munich Airport, using the airport's other runway. Following the landing, the affected aircraft remained on the runway, forcing the closure of the runway and requiring airport authorities to clear debris and deal with the disabled aircraft. Traffic was subsequently handled through the other available runway, causing disruption at the German hub. There were no reported injuries among the passengers or crew. The aircraft was carrying passengers and crew on the Munich-Hanoi service; Vietnam Airlines has reported the total as 271 passengers and 16 crew members. All occupants were reported safe after the aircraft returned to Munich. The incident is now being examined by the relevant German authorities, with Vietnamese aviation investigators assisting. Investigators will need to establish why the Boeing 787 did not achieve the expected acceleration during the takeoff roll, why the aircraft reached the end of the runway area before becoming airborne and whether any technical, operational or performance-related factor contributed to the event.

Vietnam Airlines Boeing 787 Suffers Tailstrike After Extended Takeoff Run At Munich

Join our WhatsApp Channel

Aviation Today Exclusive Interviews

Inside Aviation

Tecnam Presents Modern Trainers for Modern Pilots | Wings India 2026 Exclusive

Tecnam Presents Modern Trainers for Modern Pilots | Wings India 2026 Exclusive

3:51

Boeing’s Wisk Aero Presents Fully Autonomous Gen 6 eVTOL Aircraft | Wings India 2026 Exclusive

Boeing’s Wisk Aero Presents Fully Autonomous Gen 6 eVTOL Aircraft | Wings India 2026 Exclusive

3:10

High Concentration, Zero Error: Responsibility of Air Traffic Control | Wings India 2026 Exclusive

High Concentration, Zero Error: Responsibility of Air Traffic Control | Wings India 2026 Exclusive

5:32

TAV1000i – Design & Built in India Simulator for Precision in Ab-Initio Pilot Training

TAV1000i – Design & Built in India Simulator for Precision in Ab-Initio Pilot Training

3:42

Smiths Detection’s Next-Generation CT Baggage Screening Technology | Wings India 2026

Smiths Detection’s Next-Generation CT Baggage Screening Technology | Wings India 2026

4:05

From Solar Champion to Charter Gateway Pioneer: CIAL’s Evolution | Wings India 2026

From Solar Champion to Charter Gateway Pioneer: CIAL’s Evolution | Wings India 2026

4:06

Sakthi Aviation & Defence Systems Introduces L410NG to Boost India's Remote Connectivity

Sakthi Aviation & Defence Systems Introduces L410NG to Boost India's Remote Connectivity

3:46

DAU School Of Law Unveils Aviation Law Vertical For India’s Aviation Sector | Wings India 2026

DAU School Of Law Unveils Aviation Law Vertical For India’s Aviation Sector | Wings India 2026

5:37

A Clear Path to Becoming a Pilot: United 7 Aero’s Global Training Model | Wings India 2026

A Clear Path to Becoming a Pilot: United 7 Aero’s Global Training Model | Wings India 2026

5:44

Raghu Vamsi's Arrobot Presents Next-Generation Aerial & Ground Robotics | Wings India 2026

Raghu Vamsi's Arrobot Presents Next-Generation Aerial & Ground Robotics | Wings India 2026

5:23

Made In India Diamond DA40 NG: Combining Technology & Efficiency for Flight Training

Made In India Diamond DA40 NG: Combining Technology & Efficiency for Flight Training

6:03

TiHAN Highlights Autonomous Shuttles, Cargo Drones & Smart Mobility

TiHAN Highlights Autonomous Shuttles, Cargo Drones & Smart Mobility

5:38

Gandhi Automations Showcasing Advanced Hangar Door Technologies for Aviation Infrastructure

Gandhi Automations Showcasing Advanced Hangar Door Technologies for Aviation Infrastructure

5:20

Aviacom on High-Fidelity Flight Simulator Technology | Wings India 2026 Exclusive

Aviacom on High-Fidelity Flight Simulator Technology | Wings India 2026 Exclusive

2:56

EgyptAir Training Academy Highlights B737 MAX Type Rating & Training Programs | Wings India 2026

EgyptAir Training Academy Highlights B737 MAX Type Rating & Training Programs | Wings India 2026

7:19

Aksi Aerospace Group Showcases Indigenous Drone Manufacturing Ecosystem | Wings India 2026 Exclusive

Aksi Aerospace Group Showcases Indigenous Drone Manufacturing Ecosystem | Wings India 2026 Exclusive

2:06

Latest News

Munich, Germany: A Lufthansa Airbus A380-800 operating flight LH459 from San Francisco International Airport to Munich Airport touched down prematurely near the eastern threshold of Munich’s southern runway on Monday evening, August 17, 2026, damaging runway-threshold lighting. The aircraft, registered D-AIML, was carrying 351 passengers after completing the approximately 11-hour transatlantic flight from San Francisco, United States, to Munich, Germany. All passengers and crew were able to leave the aircraft normally, with no injuries reported. Flight records identify D-AIML as an Airbus A380-841 operated by Lufthansa, while Lufthansa’s published schedule confirms LH459 operates between San Francisco and Munich. According to Lufthansa, the aircraft touched down on the concrete surface before the white-marked runway threshold. During the premature touchdown, the aircraft struck lighting installed around the runway threshold, causing damage to the runway’s visual guidance system. Lufthansa spokesperson Jörg Waber said in a statement, “We can confirm that an AirVIbus A380-800 damaged runway lighting in the area of the runway threshold.” He added that the aircraft had arrived from San Francisco with 351 passengers, subsequently taxied to its assigned position and that all passengers left the aircraft normally. The incident occurred on Munich Airport’s southern runway, identified as Runway 26L when used for approaches from the east. The Deutsche Flugsicherung describes Runway 26L as Munich’s southern runway and says aircraft approaching it from the east use its instrument landing system. Munich Airport characterized the infrastructure damage as minor. According to the airport, a “minor damage” to lighting was identified around the eastern threshold of the southern runway. The damaged lighting was repaired promptly, allowing the runway to return to service less than an hour after the A380 landed. The exact circumstances that caused the A380 to touch down before the designated threshold remain unclear. No official finding has attributed the event to pilot error, weather, aircraft malfunction, runway conditions or any problem with the airport’s approach system. The aircraft touched down short of the marked threshold and that its landing gear struck approach lights. The cause remains under investigation. Germany’s Federal Bureau of Aircraft Accident Investigation, or BFU, has opened an investigation into the occurrence. The A380 involved was approximately 13 years old and carried the registration D-AIML. Flight-history records identify the aircraft as an Airbus A380-841 operated by Lufthansa. The airline’s A380 configuration can accommodate up to 509 passengers, although 351 passengers were onboard LH459 during this particular flight. Separately, on August 15, 2026, a Vietnam Airlines Boeing 787-9 bound for Hanoi experienced an unusually long takeoff run at Munich Airport. The aircraft continued accelerating almost to the end of Runway 26L and reportedly travelled about 120 metres beyond the paved surface before becoming airborne. During the extremely late rotation, its rear underside struck the ground, causing a tailstrike and damage to the aft fuselage. After takeoff, warnings for tail contact and low tyre pressure prompted the crew to remain near Munich at around 9,000 feet for about two hours before returning. The aircraft sustained further landing-gear and tyre damage, with several tyres damaged or deflated, and was unable to taxi after landing. It was carrying 271 passengers and 16 crew, all of whom were reported safe. German authorities are leading the investigation, with Vietnamese investigators assisting, while the cause of the unusually prolonged takeoff remains under investigation.

Lufthansa A380 Lands Short At Munich Airport, Damages Runway Lights During Its Landing

August 19, 2026

Munich, Germany: A Lufthansa Airbus A380-800 operating flight LH459 from San Francisco International Airport to Munich Airport touched down prematurely

US Court Delays Google’s $10M Spirit Airlines Data Deal After Flight Attendants Object

US Court Delays Google’s $10M Spirit Airlines Data Deal After Flight Attendants Object

August 19, 2026

New York, United States: A US bankruptcy court has postponed a hearing on Google’s proposed $10 million purchase of internal

New Delhi, India: The Supreme Court of India has pushed the Central Government of India to finalise new aviation rules within three weeks amid concerns over unpredictable airfares, surge pricing, baggage charges and passenger refunds, while warning that airlines failing to comply with applicable government directions could be grounded. The development followed a hearing before a bench of Justices Vikram Nath and Sandeep Mehta on August 17, 2026. The Central Government informed the court that it had fast-tracked the process of framing rules under the Bharatiya Vayuyan Adhiniyam, 2024, and expected the framework to be finalised within three weeks. The government also placed the draft rules before the bench in a sealed cover, saying that some final discussions were still underway. During the hearing, the Supreme Court of India issued a stern warning over airline compliance. “If airlines are not complying, ground them,” the bench said, according to reports of the proceedings. The observation came after the court was told that airlines were allegedly not complying with directions issued by the government of India concerning fares. The remark does not amount to an immediate order grounding any particular airline; rather, it signals that the court expects the existing regulatory directions to be enforced against carriers that fail to comply. The proposed regulatory framework is being prepared under the Bharatiya Vayuyan Adhiniyam, 2024, which replaced the Aircraft Act, 1934 as the principal legislation governing India's civil aviation sector. The new law came into force in January 2025, while the corresponding rules are being framed to operationalise its provisions. According to the latest reports, the draft rules submitted to the Supreme Court of India address several areas directly affecting passengers. These include airline ticket pricing, surge fares, excess baggage charges and passenger refunds. The broader proceedings also involve concerns over cancellation and refund norms, ancillary charges and the need for stronger protection against arbitrary increases in the cost of air travel. The proposed framework is particularly significant because India's airline market currently operates largely on dynamic pricing, under which fares change according to demand, availability and other commercial factors. The latest government proposal is expected to establish clearer rules governing when and how intervention can take place when fares rise sharply. However, the precise mechanism for controlling surge pricing has not yet been publicly finalized, and reports do not establish that the government has approved a permanent fixed airfare cap. The Supreme Court of India also examined whether the proposed framework would provide an effective regulatory mechanism. After examining the draft placed before it, the bench reportedly questioned whether an effective regulator had been provided for. This issue is significant because the proceedings are not limited to ticket prices; they also concern how passenger-protection requirements will be monitored and enforced once the new rules come into force. For airlines, the immediate position remains that existing government directions continue to apply while the new rules are being finalised. The Central Government of India told the court that the Ministry of Civil Aviation has been issuing office memorandums to airlines concerning pricing during the interim period. The petitioners, however, argued that airlines were not following those directions, prompting the Supreme Court's warning that non-compliant carriers should face action, including grounding. The case originates from a petition filed by social activist S. Laxminarayanan seeking tighter regulation of airfares and greater protection for passengers. The plea has raised concerns about steep and unpredictable increases in ticket prices, surge pricing, baggage charges, cancellation and refund practices and other ancillary fees. It has also sought stronger regulatory oversight of the aviation sector. The Supreme Court of India has been examining the issue for several months. In earlier proceedings, the court expressed concern over sharp increases in airfares during periods of high demand and sought a mechanism to provide greater predictability and protection to passengers. On May 15, the court observed that there should be some “rationalisation” of airfares and sought measures to provide relief to air passengers. The latest August hearing follows the court's July direction requiring the Central Government to place the proposed aviation rules before it. The government had said the rules had been framed and were undergoing the statutory process. The court nevertheless required the proposed framework to be produced before it in a sealed cover, even if the rules had not yet completed the parliamentary process. The Central Government of India has now secured three more weeks to complete the rule-making process. The matter has been listed for further hearing on September 7, 2026, when the Supreme Court of India is expected to consider the status of the final rules and the regulatory mechanism proposed for enforcing them. For passengers, the eventual rules could bring greater clarity to how airlines price tickets during periods of unusually high demand, how additional baggage charges are applied and how cancellations and refunds are handled. For airlines, the framework could introduce clearer compliance obligations and potentially stronger enforcement where government directions are breached. The exact obligations, however, will become clear only after the Central Government completes the rule-making process and formally notifies the final rules. The latest development therefore marks a significant step towards a formal regulatory framework for airfare and passenger-related charges, but it does not yet mean that a new airfare cap or a final surge-pricing formula is in force. The Central Government is still completing the rules, and the Supreme Court of India is due to review the matter again on September 7.

India’s Supreme Court Pushes Government To Finalise New Aviation Rules Within 3 Weeks

August 19, 2026

New Delhi, India: The Supreme Court of India has pushed the Central Government of India to finalise new aviation rules

Milan, Italy: A baggage cart carrying checked luggage caught fire at Milan Malpensa Airport in Italy on Sunday, August 16, shortly before the baggage was due to be handled for a British Airways flight to London Heathrow, prompting airport firefighters to intervene and damaging a small number of passengers' bags. The incident occurred on the airport apron and did not involve a fire onboard the aircraft. The fire involved an Aviapartner baggage-handling cart at Milan Malpensa. The handling company operates ground services at the airport, and the cart had just completed baggage handling associated with a British Airways flight arriving from London when it caught fire. Initial reports focused on the possibility of a lithium-ion battery inside one of the bags, but subsequent airport-source information pointed to an electrical fault in the ground vehicle instead. The incident was captured on video by former BBC journalist Jon Sopel, who was at Malpensa waiting to travel on British Airways flight BA585 from Milan to London Heathrow. The footage showed dense black smoke rising from the baggage container, with flames visible around the luggage. Ground personnel moved other baggage containers away from the burning unit to prevent the fire from spreading before airport fire crews arrived. The aircraft associated with BA585 was an Airbus A321neo registered G-NEOT, powered by two CFM International LEAP-1A32 engines. The scheduled route was Milan Malpensa Airport (MXP) to London Heathrow Airport (LHR), with British Airways operating the service under flight number BA585. The fire occurred before the affected luggage could create a fire risk inside the aircraft. The burning baggage unit remained on the ground and was dealt with by airport emergency crews. The other containers were moved away from the fire, helping prevent the flames from spreading to additional baggage or equipment. Firefighters extinguished the blaze rapidly using water. British Airways confirmed that some passengers' checked baggage was damaged. In a statement, the airline said: “We’re aware of a small number of checked bags that were damaged by fire while on the ground at Milan Malpensa Airport. The incident was quickly dealt with, and there were no injuries or impact to any flights.” The airline added: “We’ve been in contact with the small number of customers whose bags are affected to apologise and provide support. We are working closely with our partners, and an investigation is underway to establish the cause.” That statement is significant because it confirms that the fire affected checked baggage on the ground but did not result in injuries or a fire onboard the aircraft. It also shows that British Airways had not initially announced a confirmed cause and was relying on an investigation with its ground-handling partners. The investigation remained underway, while British Airways confirmed that only a small number of checked bags were damaged and that there were no injuries.

British Airways BA585 Baggage Cart Carrying Checked Luggage Catches Fire At Milan

August 18, 2026

Milan, Italy: A baggage cart carrying checked luggage caught fire at Milan Malpensa Airport in Italy on Sunday, August 16,

Never miss any important news. Subscribe to our newsletter.

Email

Recent News

Munich, Germany: A Lufthansa Airbus A380-800 operating flight LH459 from San Francisco International Airport to Munich Airport touched down prematurely near the eastern threshold of Munich’s southern runway on Monday evening, August 17, 2026, damaging runway-threshold lighting. The aircraft, registered D-AIML, was carrying 351 passengers after completing the approximately 11-hour transatlantic flight from San Francisco, United States, to Munich, Germany. All passengers and crew were able to leave the aircraft normally, with no injuries reported. Flight records identify D-AIML as an Airbus A380-841 operated by Lufthansa, while Lufthansa’s published schedule confirms LH459 operates between San Francisco and Munich. According to Lufthansa, the aircraft touched down on the concrete surface before the white-marked runway threshold. During the premature touchdown, the aircraft struck lighting installed around the runway threshold, causing damage to the runway’s visual guidance system. Lufthansa spokesperson Jörg Waber said in a statement, “We can confirm that an AirVIbus A380-800 damaged runway lighting in the area of the runway threshold.” He added that the aircraft had arrived from San Francisco with 351 passengers, subsequently taxied to its assigned position and that all passengers left the aircraft normally. The incident occurred on Munich Airport’s southern runway, identified as Runway 26L when used for approaches from the east. The Deutsche Flugsicherung describes Runway 26L as Munich’s southern runway and says aircraft approaching it from the east use its instrument landing system. Munich Airport characterized the infrastructure damage as minor. According to the airport, a “minor damage” to lighting was identified around the eastern threshold of the southern runway. The damaged lighting was repaired promptly, allowing the runway to return to service less than an hour after the A380 landed. The exact circumstances that caused the A380 to touch down before the designated threshold remain unclear. No official finding has attributed the event to pilot error, weather, aircraft malfunction, runway conditions or any problem with the airport’s approach system. The aircraft touched down short of the marked threshold and that its landing gear struck approach lights. The cause remains under investigation. Germany’s Federal Bureau of Aircraft Accident Investigation, or BFU, has opened an investigation into the occurrence. The A380 involved was approximately 13 years old and carried the registration D-AIML. Flight-history records identify the aircraft as an Airbus A380-841 operated by Lufthansa. The airline’s A380 configuration can accommodate up to 509 passengers, although 351 passengers were onboard LH459 during this particular flight. Separately, on August 15, 2026, a Vietnam Airlines Boeing 787-9 bound for Hanoi experienced an unusually long takeoff run at Munich Airport. The aircraft continued accelerating almost to the end of Runway 26L and reportedly travelled about 120 metres beyond the paved surface before becoming airborne. During the extremely late rotation, its rear underside struck the ground, causing a tailstrike and damage to the aft fuselage. After takeoff, warnings for tail contact and low tyre pressure prompted the crew to remain near Munich at around 9,000 feet for about two hours before returning. The aircraft sustained further landing-gear and tyre damage, with several tyres damaged or deflated, and was unable to taxi after landing. It was carrying 271 passengers and 16 crew, all of whom were reported safe. German authorities are leading the investigation, with Vietnamese investigators assisting, while the cause of the unusually prolonged takeoff remains under investigation.

Lufthansa A380 Lands Short At Munich Airport, Damages Runway Lights During Its Landing

August 19, 2026

US Court Delays Google’s $10M Spirit Airlines Data Deal After Flight Attendants Object

US Court Delays Google’s $10M Spirit Airlines Data Deal After Flight Attendants Object

August 19, 2026

New Delhi, India: The Supreme Court of India has pushed the Central Government of India to finalise new aviation rules within three weeks amid concerns over unpredictable airfares, surge pricing, baggage charges and passenger refunds, while warning that airlines failing to comply with applicable government directions could be grounded. The development followed a hearing before a bench of Justices Vikram Nath and Sandeep Mehta on August 17, 2026. The Central Government informed the court that it had fast-tracked the process of framing rules under the Bharatiya Vayuyan Adhiniyam, 2024, and expected the framework to be finalised within three weeks. The government also placed the draft rules before the bench in a sealed cover, saying that some final discussions were still underway. During the hearing, the Supreme Court of India issued a stern warning over airline compliance. “If airlines are not complying, ground them,” the bench said, according to reports of the proceedings. The observation came after the court was told that airlines were allegedly not complying with directions issued by the government of India concerning fares. The remark does not amount to an immediate order grounding any particular airline; rather, it signals that the court expects the existing regulatory directions to be enforced against carriers that fail to comply. The proposed regulatory framework is being prepared under the Bharatiya Vayuyan Adhiniyam, 2024, which replaced the Aircraft Act, 1934 as the principal legislation governing India's civil aviation sector. The new law came into force in January 2025, while the corresponding rules are being framed to operationalise its provisions. According to the latest reports, the draft rules submitted to the Supreme Court of India address several areas directly affecting passengers. These include airline ticket pricing, surge fares, excess baggage charges and passenger refunds. The broader proceedings also involve concerns over cancellation and refund norms, ancillary charges and the need for stronger protection against arbitrary increases in the cost of air travel. The proposed framework is particularly significant because India's airline market currently operates largely on dynamic pricing, under which fares change according to demand, availability and other commercial factors. The latest government proposal is expected to establish clearer rules governing when and how intervention can take place when fares rise sharply. However, the precise mechanism for controlling surge pricing has not yet been publicly finalized, and reports do not establish that the government has approved a permanent fixed airfare cap. The Supreme Court of India also examined whether the proposed framework would provide an effective regulatory mechanism. After examining the draft placed before it, the bench reportedly questioned whether an effective regulator had been provided for. This issue is significant because the proceedings are not limited to ticket prices; they also concern how passenger-protection requirements will be monitored and enforced once the new rules come into force. For airlines, the immediate position remains that existing government directions continue to apply while the new rules are being finalised. The Central Government of India told the court that the Ministry of Civil Aviation has been issuing office memorandums to airlines concerning pricing during the interim period. The petitioners, however, argued that airlines were not following those directions, prompting the Supreme Court's warning that non-compliant carriers should face action, including grounding. The case originates from a petition filed by social activist S. Laxminarayanan seeking tighter regulation of airfares and greater protection for passengers. The plea has raised concerns about steep and unpredictable increases in ticket prices, surge pricing, baggage charges, cancellation and refund practices and other ancillary fees. It has also sought stronger regulatory oversight of the aviation sector. The Supreme Court of India has been examining the issue for several months. In earlier proceedings, the court expressed concern over sharp increases in airfares during periods of high demand and sought a mechanism to provide greater predictability and protection to passengers. On May 15, the court observed that there should be some “rationalisation” of airfares and sought measures to provide relief to air passengers. The latest August hearing follows the court's July direction requiring the Central Government to place the proposed aviation rules before it. The government had said the rules had been framed and were undergoing the statutory process. The court nevertheless required the proposed framework to be produced before it in a sealed cover, even if the rules had not yet completed the parliamentary process. The Central Government of India has now secured three more weeks to complete the rule-making process. The matter has been listed for further hearing on September 7, 2026, when the Supreme Court of India is expected to consider the status of the final rules and the regulatory mechanism proposed for enforcing them. For passengers, the eventual rules could bring greater clarity to how airlines price tickets during periods of unusually high demand, how additional baggage charges are applied and how cancellations and refunds are handled. For airlines, the framework could introduce clearer compliance obligations and potentially stronger enforcement where government directions are breached. The exact obligations, however, will become clear only after the Central Government completes the rule-making process and formally notifies the final rules. The latest development therefore marks a significant step towards a formal regulatory framework for airfare and passenger-related charges, but it does not yet mean that a new airfare cap or a final surge-pricing formula is in force. The Central Government is still completing the rules, and the Supreme Court of India is due to review the matter again on September 7.

India’s Supreme Court Pushes Government To Finalise New Aviation Rules Within 3 Weeks

August 19, 2026

Milan, Italy: A baggage cart carrying checked luggage caught fire at Milan Malpensa Airport in Italy on Sunday, August 16, shortly before the baggage was due to be handled for a British Airways flight to London Heathrow, prompting airport firefighters to intervene and damaging a small number of passengers' bags. The incident occurred on the airport apron and did not involve a fire onboard the aircraft. The fire involved an Aviapartner baggage-handling cart at Milan Malpensa. The handling company operates ground services at the airport, and the cart had just completed baggage handling associated with a British Airways flight arriving from London when it caught fire. Initial reports focused on the possibility of a lithium-ion battery inside one of the bags, but subsequent airport-source information pointed to an electrical fault in the ground vehicle instead. The incident was captured on video by former BBC journalist Jon Sopel, who was at Malpensa waiting to travel on British Airways flight BA585 from Milan to London Heathrow. The footage showed dense black smoke rising from the baggage container, with flames visible around the luggage. Ground personnel moved other baggage containers away from the burning unit to prevent the fire from spreading before airport fire crews arrived. The aircraft associated with BA585 was an Airbus A321neo registered G-NEOT, powered by two CFM International LEAP-1A32 engines. The scheduled route was Milan Malpensa Airport (MXP) to London Heathrow Airport (LHR), with British Airways operating the service under flight number BA585. The fire occurred before the affected luggage could create a fire risk inside the aircraft. The burning baggage unit remained on the ground and was dealt with by airport emergency crews. The other containers were moved away from the fire, helping prevent the flames from spreading to additional baggage or equipment. Firefighters extinguished the blaze rapidly using water. British Airways confirmed that some passengers' checked baggage was damaged. In a statement, the airline said: “We’re aware of a small number of checked bags that were damaged by fire while on the ground at Milan Malpensa Airport. The incident was quickly dealt with, and there were no injuries or impact to any flights.” The airline added: “We’ve been in contact with the small number of customers whose bags are affected to apologise and provide support. We are working closely with our partners, and an investigation is underway to establish the cause.” That statement is significant because it confirms that the fire affected checked baggage on the ground but did not result in injuries or a fire onboard the aircraft. It also shows that British Airways had not initially announced a confirmed cause and was relying on an investigation with its ground-handling partners. The investigation remained underway, while British Airways confirmed that only a small number of checked bags were damaged and that there were no injuries.

British Airways BA585 Baggage Cart Carrying Checked Luggage Catches Fire At Milan

August 18, 2026

Krasnoyarsk, Russia: Hainan Airlines Flight HU753, operating from Beijing Capital International Airport in China to Manchester Airport in the United Kingdom, diverted to Krasnoyarsk International Airport in Russia on August 15 after the Airbus A330-300 developed a mechanical fault while flying over Siberia. The aircraft landed safely, with no injuries, deaths or damage reported. The flight was operated by an Airbus A330-343, registration B-304L, with 230 people on board. Flight-tracking data showed the aircraft departed Beijing for Manchester and was cruising at approximately FL340, or 34,000 feet, when the problem occurred. The aircraft was around 190 nautical miles southeast of Krasnoyarsk when it descended to approximately FL200 and diverted toward Krasnoyarsk International Airport. According to reports, the problem emerged approximately four hours into the flight. The aircraft's sensors detected the fault and the crew issued an emergency signal before diverting to Krasnoyarsk.. Russian emergency authorities had prepared for the aircraft's arrival, deploying 51 personnel and 15 vehicles. The response included 39 personnel and 11 vehicles from Russia's Ministry of Emergency Situations, according to reports. Emergency teams were positioned as a precaution, but the aircraft completed the landing without an accident. Russia's Emergencies Ministry confirmed that there were no injuries or deaths and that neither the aircraft nor airport infrastructure was damaged. English- and Chinese-speaking airport personnel were also reported to have assisted passengers and crew following the landing. Hainan Airlines confirmed the diversion and apologised to passengers. In its statement, the airline said: “On 15 August 2026, our flight HU753 (Beijing–Manchester) diverted to Krasnoyarsk International Airport in Russia due to a mechanical fault. The flight landed safely at 07:28 Beijing time.” The airline added: “The company plans to replace the aircraft to operate the onward flight. We will properly arrange passenger service support to ensure safe arrival at the destination. We sincerely apologise for any inconvenience caused to passengers.” Hainan Airlines also reiterated: “Hainan Airlines always adheres to the principles of safety first and passengers first, providing safe, comfortable and efficient services.” The exact nature of the mechanical fault has not been officially disclosed. Hainan Airlines described the problem as a “mechanical fault,” while Russian authorities referred to it as a technical malfunction. Therefore, claims that the incident involved a particular system failure should be treated cautiously. The diversion left passengers in Krasnoyarsk while Hainan Airlines arranged an onward journey. The airline said a replacement aircraft would be sent to Krasnoyarsk to continue the service to Manchester, while passenger support arrangements were being made.

Hainan Airlines Flight HU753 Diverts To Russia After Mechanical Fault Over Siberia

August 18, 2026

Do you have the Pilot in you?

Explore More

Webinar

Industry Expert’s Voice

Indian Aviation Statistics

Submit Aviation Blog

Editor's Pick

Lufthansa A380 Lands Short At Munich Airport, Damages Runway Lights During Its Landing

Incidents

Posted onAugust 19, 2026August 19, 2026

Lufthansa A380 Lands Short At Munich Airport, Damages Runway Lights During Its Landing

US Court Delays Google’s $10M Spirit Airlines Data Deal After Flight Attendants Object

Airlines

Posted onAugust 19, 2026August 19, 2026

US Court Delays Google’s $10M Spirit Airlines Data Deal After Flight Attendants Object

India’s Supreme Court Pushes Government To Finalise New Aviation Rules Within 3 Weeks

India

Posted onAugust 19, 2026August 19, 2026

India’s Supreme Court Pushes Government To Finalise New Aviation Rules Within 3 Weeks

British Airways BA585 Baggage Cart Carrying Checked Luggage Catches Fire At Milan

Incidents

Posted onAugust 18, 2026August 18, 2026

British Airways BA585 Baggage Cart Carrying Checked Luggage Catches Fire At Milan

Airlines

Montreal, Canada: The International Civil Aviation Organization (ICAO) has sounded a strong warning on global air safety, highlighting rising accident rates as flight activity reaches record levels. In its latest State of Global Aviation Safety report released this month, the UN aviation agency revealed that 2024 saw 95 accidents involving scheduled commercial flights, compared with 66 the previous year. Of these, 10 were fatal, resulting in 296 deaths, an alarming jump from 72 in 2023. The global accident rate also rose to 2.56 per million departures, up from 1.87 the previous year. While ICAO stressed that aviation remains the safest form of travel, the organization called for urgent international action to address mounting risks as passenger demand continues to grow worldwide. ICAO’s data show that the most significant accident categories included controlled flight into terrain, loss of control in flight, mid-air collisions, and runway incursions. These accounted for 25 percent of total fatalities and 40 percent of fatal accidents in 2024. Turbulence has also emerged as a key concern, responsible for nearly three-quarters of serious injuries recorded last year. The Asia-Pacific and Europe/North Atlantic regions each reported three fatal accidents, while a single catastrophic crash in South America caused 62 deaths. Overall, Asia-Pacific recorded the highest number of fatalities, followed by South America, then Europe and the North Atlantic. Alongside accident data, ICAO flagged growing risks from Global Navigation Satellite System (GNSS) disruptions, such as jamming and spoofing, which threaten the reliability of modern navigation. The organization is updating guidance and working with member states to protect GNSS integrity, while also strengthening runway safety initiatives, turbulence monitoring, and wildlife strike reporting. ICAO is further developing frameworks for civil-military cooperation to manage risks linked to conflict zones and restricted airspace, and it is preparing safety systems for the integration of unmanned aircraft and advanced air mobility vehicles into shared skies. ICAO leaders underscored that the rise in accidents is a wake-up call for regulators, airlines, and governments worldwide. Secretary General Juan Carlos Salazar noted that the long-term safety trend remains positive but emphasized that “aviation remains the safest form of transport” only if proactive measures are sustained.

ICAO Warns of Rising Air Safety Risks as Global Flight Activity Hits Record Levels

August 27, 2025

Montreal, Canada: The International Civil Aviation Organization (ICAO) has sounded a strong warning on global air safety, highlighting rising accident

Explosive-Laden Drone Found At Leipzig Airport As DHL Freighter Strikes Object Mid-Air

August 6, 2026

Caracas, Venezuela: Venezuelan authorities declared a nationwide state of emergency after two powerful earthquakes struck the country within seconds of each other on June 24, triggering widespread destruction across Caracas and several surrounding regions, forcing the closure of the nation's main international airport and launching a large-scale search-and-rescue operation. According to the United States Geological Survey (USGS), a magnitude 7.2 earthquake struck approximately 160 kilometers west of Caracas near Morón, followed just 39 seconds later by a stronger magnitude 7.5 tremor. Seismologists described the event as a rare seismic doublet. More than 20 aftershocks were recorded in the hours that followed. The earthquakes caused extensive damage across the capital and nearby states, with multiple residential and commercial buildings collapsing, roads and transportation infrastructure disrupted, and emergency crews deployed throughout affected areas. Interim President Delcy Rodríguez announced a state of emergency during a televised address alongside National Assembly President Jorge Rodríguez and Interior Minister Diosdado Cabello. While extending condolences to families of those killed, Rodríguez did not provide an official nationwide death toll or injury count, saying authorities were still assessing the scale of the disaster. The closure of Simón Bolívar International Airport in Maiquetía, Venezuela's primary international gateway serving Caracas, emerged as one of the most significant impacts on the country's transportation network. Government officials said the airport sustained serious structural damage, prompting the suspension of all flight operations pending safety inspections. Videos circulating on social media showed scenes of panic inside the airport as passengers rushed to evacuate. Witnesses reported ceiling panels collapsing, power interruptions, and debris falling inside terminal areas during the strongest shaking. Reports also indicated damage to pedestrian structures within the airport complex and along transportation routes connecting the facility to Caracas. Metro and rail services were suspended as authorities assessed damage to public infrastructure. Emergency responders worked through the night searching for survivors trapped beneath collapsed structures in several districts of Caracas. Photographs from the scene showed rescue teams digging through rubble as residents gathered outside damaged buildings. Although the Venezuelan government has not yet released official casualty figures, local authorities reported fatalities in parts of the capital. According to municipal officials, three people were killed in Caracas' Baruta district following the collapse of two buildings. In neighboring Chacao district, local authorities reported one fatality and the collapse of four buildings. Officials in the coastal state of Falcón reported at least 22 injuries, while several people were reported missing as rescue operations continued. "High casualties and extensive damage are probable and the disaster is likely widespread," the USGS said, estimating the death toll would most likely range from 10,000 to 100,000. “We have buildings, homes and houses which have collapsed and we are taking care of things with everything we have available in terms of security, civil assistance," Interior Minister Diosdado Cabello said on state television. The USGS issued a red alert following the earthquakes, warning of potentially severe humanitarian consequences. The agency's automated assessment suggested a high likelihood of significant casualties and major economic losses due to the magnitude of the event and the affected population density. However, these projections remain preliminary and are not official casualty figures. A tsunami warning was briefly issued after the earthquakes but was subsequently withdrawn. The earthquakes struck during a public holiday period, sending thousands of residents into streets and open areas as buildings swayed across Caracas and surrounding regions. Witnesses described walls cracking, staircases shifting and objects falling from ceilings during the prolonged shaking. Damage has been reported across several states, including Miranda, La Guaira, Aragua, Carabobo and Falcón. In La Guaira, where the country's main airport is located, authorities reported significant structural impacts and disruptions to communications and transportation links. Hospitals were placed on emergency footing as medical facilities prepared for additional casualties. The Venezuelan government also suspended classes for the remainder of the week while engineers assess the safety of educational institutions and public buildings. International assistance efforts are beginning to mobilize. U.S. officials announced the deployment of disaster response personnel, search-and-rescue teams and humanitarian aid resources to support relief operations. Indian Prime Minister Narendra Modi also expressed condolences and said India stood ready to provide assistance if required. Authorities warned residents to remain alert as aftershocks continue and urged the public to avoid damaged buildings until structural assessments are completed. Rescue operations remain ongoing, and officials say casualty figures and damage assessments are expected to evolve as emergency teams gain access to affected areas across the country.

Venezuela Earthquakes Force Closure Of Caracas International Airport Amid State Of Emergency

June 25, 2026

Moscow, Russia: Russian air defenses intercepted nearly 60 Ukrainian drones approaching Moscow in the early hours of Monday, prompting the temporary suspension of flights at all four major airports serving the Russian capital before operations were later restored, Russian authorities said. Moscow Mayor Sergei Sobyanin said on Telegram that almost 60 drones heading toward the capital were shot down overnight. He did not provide further details on the scale of the attack or potential damage but said emergency services had been dispatched to locations where drone debris fell. Russia's aviation watchdog, Rosaviatsia, temporarily halted operations at Sheremetyevo, Domodedovo, Vnukovo and Zhukovsky airports as a safety precaution during the attack. The agency later announced that flight operations had resumed after authorities determined conditions were safe. Officials did not immediately disclose how long the restrictions remained in effect or whether flights were delayed or cancelled. At roughly the same time, Russia carried out drone attacks on Ukraine, including strikes on Zaporizhzhia and Odessa. The Zaporizhzhia Regional Prosecutor’s Office reported on Telegram,“Throughout the night and morning of June 22, 2026, the Russians struck civilian infrastructure in Zaporizhzhia using unmanned aerial vehicles (UAVs). As a result of the enemy shelling, two women, aged 39 and 53, were killed. Another seven people were injured, including an 11-year-old boy.” The attack targeted civilian infrastructure in the southeastern Ukrainian city, with emergency services responding to the scene as authorities assessed the full extent of the damage. Ukrainian officials said the strike formed part of a broader wave of overnight Russian attacks reported across several regions of the country. The latest drone assault comes only days after Ukraine carried out a renewed strike on Moscow's only oil refinery, one of the region's most important fuel-production facilities. The refinery, operated by Gazprom Neft in Moscow's Kapotnya district, was struck for a second time within a week during a major Ukrainian drone offensive on June 18. Industry sources told Reuters that the attack damaged a key processing unit and temporarily halted refinery operations. The Moscow refinery is the capital region's largest fuel supplier and produced 11.6 million metric tons of oil products in 2024, including gasoline, diesel and aviation fuel. The facility has become a recurring target as Ukraine intensifies long-range strikes against Russian energy infrastructure. The June 22 attack reflects an escalating drone campaign by Ukraine aimed at military, energy and logistics infrastructure deep inside Russian territory. Ukrainian officials have previously described such operations as a response to Russia's continuing attacks on Ukrainian cities and infrastructure. The attack occurred amid heightened security concerns around Moscow following one of the largest drone assaults on the Russian capital since the war began. During the June 18 offensive, Russia said it shot down hundreds of drones across the country, including around 180 near Moscow. That attack damaged the city's oil refinery, disrupted airport operations and injured at least 16 people in the Moscow region, according to regional Governor Andrei Vorobyov. In response to the growing threat of drone incursions, Rosaviatsia recently announced new restrictions on light aircraft and drone operations in Moscow and several neighboring regions. The measures, which took effect on June 20, establish a minimum operating altitude of 5,200 meters, effectively grounding most private aircraft and drones in affected areas while leaving commercial airline operations unaffected.

Drone Attack Near Moscow Forces Temporary Closure Of Four Major Airports

June 22, 2026

Edinburgh, Scotland: Edinburgh Airport resumed operations on Saturday after a major security incident forced the evacuation of the terminal, the closure of surrounding roads, and widespread disruption to flights and ground transport services. The incident began at approximately 6:50 p.m. local time on Friday, June 19, when authorities received reports of a potentially suspicious package at the airport. Police Scotland immediately launched a security response, ordering the evacuation of the terminal building while specialist Explosive Ordnance Disposal (EOD) teams were deployed to assess the item. A security cordon was established around the airport, and several access roads were closed as bomb disposal experts conducted their investigation. Hundreds of passengers were evacuated from the terminal and directed away from the airport while emergency personnel secured the area. According to Police Scotland, the evacuation was implemented as a precautionary measure following the report of the suspicious package. Officers urged travelers to contact their airlines for updates and warned of significant disruption while enquiries were ongoing. Airport operator Edinburgh Airport confirmed that specialist teams were investigating the item and advised passengers to check directly with their airlines before travelling to the airport. Flight operations were significantly affected throughout the evening. Multiple arriving aircraft were diverted to alternative airports, including Glasgow Airport, while numerous departures were delayed or suspended. Several flights reportedly entered holding patterns or altered their routes as the security operation unfolded. Ground transportation services were also disrupted. Coach operator Citylink announced that its airport services were unable to access the terminal because of the ongoing incident. Temporary pickup and drop-off arrangements were established at nearby locations, including the Moxy Hotel and Hilton Hotel bus stops. The airport remained largely shut down for several hours while EOD specialists examined the package. Operations began returning to normal during the early hours of Saturday after authorities completed their assessment and lifted restrictions. The prolonged closure created knock-on effects across airline schedules, with passengers warned to expect delays and operational disruptions as carriers worked to reposition aircraft and recover their networks. As of Saturday morning, airport operations had resumed, although airlines continued to advise travelers to verify the status of their flights before heading to the airport. Police Scotland has not announced any arrests in connection with the incident, and investigations into the circumstances surrounding the discovery remain ongoing.

Edinburgh Airport Reopens After Overnight Evacuation Over Suspicious Package Alert

June 20, 2026

Airports

Munich, Germany: A Lufthansa Airbus A380-800 operating flight LH459 from San Francisco International Airport to Munich Airport touched down prematurely near the eastern threshold of Munich’s southern runway on Monday evening, August 17, 2026, damaging runway-threshold lighting. The aircraft, registered D-AIML, was carrying 351 passengers after completing the approximately 11-hour transatlantic flight from San Francisco, United States, to Munich, Germany. All passengers and crew were able to leave the aircraft normally, with no injuries reported. Flight records identify D-AIML as an Airbus A380-841 operated by Lufthansa, while Lufthansa’s published schedule confirms LH459 operates between San Francisco and Munich. According to Lufthansa, the aircraft touched down on the concrete surface before the white-marked runway threshold. During the premature touchdown, the aircraft struck lighting installed around the runway threshold, causing damage to the runway’s visual guidance system. Lufthansa spokesperson Jörg Waber said in a statement, “We can confirm that an AirVIbus A380-800 damaged runway lighting in the area of the runway threshold.” He added that the aircraft had arrived from San Francisco with 351 passengers, subsequently taxied to its assigned position and that all passengers left the aircraft normally. The incident occurred on Munich Airport’s southern runway, identified as Runway 26L when used for approaches from the east. The Deutsche Flugsicherung describes Runway 26L as Munich’s southern runway and says aircraft approaching it from the east use its instrument landing system. Munich Airport characterized the infrastructure damage as minor. According to the airport, a “minor damage” to lighting was identified around the eastern threshold of the southern runway. The damaged lighting was repaired promptly, allowing the runway to return to service less than an hour after the A380 landed. The exact circumstances that caused the A380 to touch down before the designated threshold remain unclear. No official finding has attributed the event to pilot error, weather, aircraft malfunction, runway conditions or any problem with the airport’s approach system. The aircraft touched down short of the marked threshold and that its landing gear struck approach lights. The cause remains under investigation. Germany’s Federal Bureau of Aircraft Accident Investigation, or BFU, has opened an investigation into the occurrence. The A380 involved was approximately 13 years old and carried the registration D-AIML. Flight-history records identify the aircraft as an Airbus A380-841 operated by Lufthansa. The airline’s A380 configuration can accommodate up to 509 passengers, although 351 passengers were onboard LH459 during this particular flight. Separately, on August 15, 2026, a Vietnam Airlines Boeing 787-9 bound for Hanoi experienced an unusually long takeoff run at Munich Airport. The aircraft continued accelerating almost to the end of Runway 26L and reportedly travelled about 120 metres beyond the paved surface before becoming airborne. During the extremely late rotation, its rear underside struck the ground, causing a tailstrike and damage to the aft fuselage. After takeoff, warnings for tail contact and low tyre pressure prompted the crew to remain near Munich at around 9,000 feet for about two hours before returning. The aircraft sustained further landing-gear and tyre damage, with several tyres damaged or deflated, and was unable to taxi after landing. It was carrying 271 passengers and 16 crew, all of whom were reported safe. German authorities are leading the investigation, with Vietnamese investigators assisting, while the cause of the unusually prolonged takeoff remains under investigation.

Lufthansa A380 Lands Short At Munich Airport, Damages Runway Lights During Its Landing

August 19, 2026

Munich, Germany: A Lufthansa Airbus A380-800 operating flight LH459 from San Francisco International Airport to Munich Airport touched down prematurely

US Court Delays Google’s $10M Spirit Airlines Data Deal After Flight Attendants Object

US Court Delays Google’s $10M Spirit Airlines Data Deal After Flight Attendants Object

August 19, 2026

New Delhi, India: The Supreme Court of India has pushed the Central Government of India to finalise new aviation rules within three weeks amid concerns over unpredictable airfares, surge pricing, baggage charges and passenger refunds, while warning that airlines failing to comply with applicable government directions could be grounded. The development followed a hearing before a bench of Justices Vikram Nath and Sandeep Mehta on August 17, 2026. The Central Government informed the court that it had fast-tracked the process of framing rules under the Bharatiya Vayuyan Adhiniyam, 2024, and expected the framework to be finalised within three weeks. The government also placed the draft rules before the bench in a sealed cover, saying that some final discussions were still underway. During the hearing, the Supreme Court of India issued a stern warning over airline compliance. “If airlines are not complying, ground them,” the bench said, according to reports of the proceedings. The observation came after the court was told that airlines were allegedly not complying with directions issued by the government of India concerning fares. The remark does not amount to an immediate order grounding any particular airline; rather, it signals that the court expects the existing regulatory directions to be enforced against carriers that fail to comply. The proposed regulatory framework is being prepared under the Bharatiya Vayuyan Adhiniyam, 2024, which replaced the Aircraft Act, 1934 as the principal legislation governing India's civil aviation sector. The new law came into force in January 2025, while the corresponding rules are being framed to operationalise its provisions. According to the latest reports, the draft rules submitted to the Supreme Court of India address several areas directly affecting passengers. These include airline ticket pricing, surge fares, excess baggage charges and passenger refunds. The broader proceedings also involve concerns over cancellation and refund norms, ancillary charges and the need for stronger protection against arbitrary increases in the cost of air travel. The proposed framework is particularly significant because India's airline market currently operates largely on dynamic pricing, under which fares change according to demand, availability and other commercial factors. The latest government proposal is expected to establish clearer rules governing when and how intervention can take place when fares rise sharply. However, the precise mechanism for controlling surge pricing has not yet been publicly finalized, and reports do not establish that the government has approved a permanent fixed airfare cap. The Supreme Court of India also examined whether the proposed framework would provide an effective regulatory mechanism. After examining the draft placed before it, the bench reportedly questioned whether an effective regulator had been provided for. This issue is significant because the proceedings are not limited to ticket prices; they also concern how passenger-protection requirements will be monitored and enforced once the new rules come into force. For airlines, the immediate position remains that existing government directions continue to apply while the new rules are being finalised. The Central Government of India told the court that the Ministry of Civil Aviation has been issuing office memorandums to airlines concerning pricing during the interim period. The petitioners, however, argued that airlines were not following those directions, prompting the Supreme Court's warning that non-compliant carriers should face action, including grounding. The case originates from a petition filed by social activist S. Laxminarayanan seeking tighter regulation of airfares and greater protection for passengers. The plea has raised concerns about steep and unpredictable increases in ticket prices, surge pricing, baggage charges, cancellation and refund practices and other ancillary fees. It has also sought stronger regulatory oversight of the aviation sector. The Supreme Court of India has been examining the issue for several months. In earlier proceedings, the court expressed concern over sharp increases in airfares during periods of high demand and sought a mechanism to provide greater predictability and protection to passengers. On May 15, the court observed that there should be some “rationalisation” of airfares and sought measures to provide relief to air passengers. The latest August hearing follows the court's July direction requiring the Central Government to place the proposed aviation rules before it. The government had said the rules had been framed and were undergoing the statutory process. The court nevertheless required the proposed framework to be produced before it in a sealed cover, even if the rules had not yet completed the parliamentary process. The Central Government of India has now secured three more weeks to complete the rule-making process. The matter has been listed for further hearing on September 7, 2026, when the Supreme Court of India is expected to consider the status of the final rules and the regulatory mechanism proposed for enforcing them. For passengers, the eventual rules could bring greater clarity to how airlines price tickets during periods of unusually high demand, how additional baggage charges are applied and how cancellations and refunds are handled. For airlines, the framework could introduce clearer compliance obligations and potentially stronger enforcement where government directions are breached. The exact obligations, however, will become clear only after the Central Government completes the rule-making process and formally notifies the final rules. The latest development therefore marks a significant step towards a formal regulatory framework for airfare and passenger-related charges, but it does not yet mean that a new airfare cap or a final surge-pricing formula is in force. The Central Government is still completing the rules, and the Supreme Court of India is due to review the matter again on September 7.

India’s Supreme Court Pushes Government To Finalise New Aviation Rules Within 3 Weeks

August 19, 2026

Milan, Italy: A baggage cart carrying checked luggage caught fire at Milan Malpensa Airport in Italy on Sunday, August 16, shortly before the baggage was due to be handled for a British Airways flight to London Heathrow, prompting airport firefighters to intervene and damaging a small number of passengers' bags. The incident occurred on the airport apron and did not involve a fire onboard the aircraft. The fire involved an Aviapartner baggage-handling cart at Milan Malpensa. The handling company operates ground services at the airport, and the cart had just completed baggage handling associated with a British Airways flight arriving from London when it caught fire. Initial reports focused on the possibility of a lithium-ion battery inside one of the bags, but subsequent airport-source information pointed to an electrical fault in the ground vehicle instead. The incident was captured on video by former BBC journalist Jon Sopel, who was at Malpensa waiting to travel on British Airways flight BA585 from Milan to London Heathrow. The footage showed dense black smoke rising from the baggage container, with flames visible around the luggage. Ground personnel moved other baggage containers away from the burning unit to prevent the fire from spreading before airport fire crews arrived. The aircraft associated with BA585 was an Airbus A321neo registered G-NEOT, powered by two CFM International LEAP-1A32 engines. The scheduled route was Milan Malpensa Airport (MXP) to London Heathrow Airport (LHR), with British Airways operating the service under flight number BA585. The fire occurred before the affected luggage could create a fire risk inside the aircraft. The burning baggage unit remained on the ground and was dealt with by airport emergency crews. The other containers were moved away from the fire, helping prevent the flames from spreading to additional baggage or equipment. Firefighters extinguished the blaze rapidly using water. British Airways confirmed that some passengers' checked baggage was damaged. In a statement, the airline said: “We’re aware of a small number of checked bags that were damaged by fire while on the ground at Milan Malpensa Airport. The incident was quickly dealt with, and there were no injuries or impact to any flights.” The airline added: “We’ve been in contact with the small number of customers whose bags are affected to apologise and provide support. We are working closely with our partners, and an investigation is underway to establish the cause.” That statement is significant because it confirms that the fire affected checked baggage on the ground but did not result in injuries or a fire onboard the aircraft. It also shows that British Airways had not initially announced a confirmed cause and was relying on an investigation with its ground-handling partners. The investigation remained underway, while British Airways confirmed that only a small number of checked bags were damaged and that there were no injuries.

British Airways BA585 Baggage Cart Carrying Checked Luggage Catches Fire At Milan

August 18, 2026

Krasnoyarsk, Russia: Hainan Airlines Flight HU753, operating from Beijing Capital International Airport in China to Manchester Airport in the United Kingdom, diverted to Krasnoyarsk International Airport in Russia on August 15 after the Airbus A330-300 developed a mechanical fault while flying over Siberia. The aircraft landed safely, with no injuries, deaths or damage reported. The flight was operated by an Airbus A330-343, registration B-304L, with 230 people on board. Flight-tracking data showed the aircraft departed Beijing for Manchester and was cruising at approximately FL340, or 34,000 feet, when the problem occurred. The aircraft was around 190 nautical miles southeast of Krasnoyarsk when it descended to approximately FL200 and diverted toward Krasnoyarsk International Airport. According to reports, the problem emerged approximately four hours into the flight. The aircraft's sensors detected the fault and the crew issued an emergency signal before diverting to Krasnoyarsk.. Russian emergency authorities had prepared for the aircraft's arrival, deploying 51 personnel and 15 vehicles. The response included 39 personnel and 11 vehicles from Russia's Ministry of Emergency Situations, according to reports. Emergency teams were positioned as a precaution, but the aircraft completed the landing without an accident. Russia's Emergencies Ministry confirmed that there were no injuries or deaths and that neither the aircraft nor airport infrastructure was damaged. English- and Chinese-speaking airport personnel were also reported to have assisted passengers and crew following the landing. Hainan Airlines confirmed the diversion and apologised to passengers. In its statement, the airline said: “On 15 August 2026, our flight HU753 (Beijing–Manchester) diverted to Krasnoyarsk International Airport in Russia due to a mechanical fault. The flight landed safely at 07:28 Beijing time.” The airline added: “The company plans to replace the aircraft to operate the onward flight. We will properly arrange passenger service support to ensure safe arrival at the destination. We sincerely apologise for any inconvenience caused to passengers.” Hainan Airlines also reiterated: “Hainan Airlines always adheres to the principles of safety first and passengers first, providing safe, comfortable and efficient services.” The exact nature of the mechanical fault has not been officially disclosed. Hainan Airlines described the problem as a “mechanical fault,” while Russian authorities referred to it as a technical malfunction. Therefore, claims that the incident involved a particular system failure should be treated cautiously. The diversion left passengers in Krasnoyarsk while Hainan Airlines arranged an onward journey. The airline said a replacement aircraft would be sent to Krasnoyarsk to continue the service to Manchester, while passenger support arrangements were being made.

Hainan Airlines Flight HU753 Diverts To Russia After Mechanical Fault Over Siberia

August 18, 2026

More News

Munich, Germany: A Lufthansa Airbus A380-800 operating flight LH459 from San Francisco International Airport to Munich Airport touched down prematurely near the eastern threshold of Munich’s southern runway on Monday evening, August 17, 2026, damaging runway-threshold lighting. The aircraft, registered D-AIML, was carrying 351 passengers after completing the approximately 11-hour transatlantic flight from San Francisco, United States, to Munich, Germany. All passengers and crew were able to leave the aircraft normally, with no injuries reported. Flight records identify D-AIML as an Airbus A380-841 operated by Lufthansa, while Lufthansa’s published schedule confirms LH459 operates between San Francisco and Munich. According to Lufthansa, the aircraft touched down on the concrete surface before the white-marked runway threshold. During the premature touchdown, the aircraft struck lighting installed around the runway threshold, causing damage to the runway’s visual guidance system. Lufthansa spokesperson Jörg Waber said in a statement, “We can confirm that an AirVIbus A380-800 damaged runway lighting in the area of the runway threshold.” He added that the aircraft had arrived from San Francisco with 351 passengers, subsequently taxied to its assigned position and that all passengers left the aircraft normally. The incident occurred on Munich Airport’s southern runway, identified as Runway 26L when used for approaches from the east. The Deutsche Flugsicherung describes Runway 26L as Munich’s southern runway and says aircraft approaching it from the east use its instrument landing system. Munich Airport characterized the infrastructure damage as minor. According to the airport, a “minor damage” to lighting was identified around the eastern threshold of the southern runway. The damaged lighting was repaired promptly, allowing the runway to return to service less than an hour after the A380 landed. The exact circumstances that caused the A380 to touch down before the designated threshold remain unclear. No official finding has attributed the event to pilot error, weather, aircraft malfunction, runway conditions or any problem with the airport’s approach system. The aircraft touched down short of the marked threshold and that its landing gear struck approach lights. The cause remains under investigation. Germany’s Federal Bureau of Aircraft Accident Investigation, or BFU, has opened an investigation into the occurrence. The A380 involved was approximately 13 years old and carried the registration D-AIML. Flight-history records identify the aircraft as an Airbus A380-841 operated by Lufthansa. The airline’s A380 configuration can accommodate up to 509 passengers, although 351 passengers were onboard LH459 during this particular flight. Separately, on August 15, 2026, a Vietnam Airlines Boeing 787-9 bound for Hanoi experienced an unusually long takeoff run at Munich Airport. The aircraft continued accelerating almost to the end of Runway 26L and reportedly travelled about 120 metres beyond the paved surface before becoming airborne. During the extremely late rotation, its rear underside struck the ground, causing a tailstrike and damage to the aft fuselage. After takeoff, warnings for tail contact and low tyre pressure prompted the crew to remain near Munich at around 9,000 feet for about two hours before returning. The aircraft sustained further landing-gear and tyre damage, with several tyres damaged or deflated, and was unable to taxi after landing. It was carrying 271 passengers and 16 crew, all of whom were reported safe. German authorities are leading the investigation, with Vietnamese investigators assisting, while the cause of the unusually prolonged takeoff remains under investigation.

Lufthansa A380 Lands Short At Munich Airport, Damages Runway Lights During Its Landing

August 19, 2026

US Court Delays Google’s $10M Spirit Airlines Data Deal After Flight Attendants Object

US Court Delays Google’s $10M Spirit Airlines Data Deal After Flight Attendants Object

August 19, 2026

New Delhi, India: The Supreme Court of India has pushed the Central Government of India to finalise new aviation rules within three weeks amid concerns over unpredictable airfares, surge pricing, baggage charges and passenger refunds, while warning that airlines failing to comply with applicable government directions could be grounded. The development followed a hearing before a bench of Justices Vikram Nath and Sandeep Mehta on August 17, 2026. The Central Government informed the court that it had fast-tracked the process of framing rules under the Bharatiya Vayuyan Adhiniyam, 2024, and expected the framework to be finalised within three weeks. The government also placed the draft rules before the bench in a sealed cover, saying that some final discussions were still underway. During the hearing, the Supreme Court of India issued a stern warning over airline compliance. “If airlines are not complying, ground them,” the bench said, according to reports of the proceedings. The observation came after the court was told that airlines were allegedly not complying with directions issued by the government of India concerning fares. The remark does not amount to an immediate order grounding any particular airline; rather, it signals that the court expects the existing regulatory directions to be enforced against carriers that fail to comply. The proposed regulatory framework is being prepared under the Bharatiya Vayuyan Adhiniyam, 2024, which replaced the Aircraft Act, 1934 as the principal legislation governing India's civil aviation sector. The new law came into force in January 2025, while the corresponding rules are being framed to operationalise its provisions. According to the latest reports, the draft rules submitted to the Supreme Court of India address several areas directly affecting passengers. These include airline ticket pricing, surge fares, excess baggage charges and passenger refunds. The broader proceedings also involve concerns over cancellation and refund norms, ancillary charges and the need for stronger protection against arbitrary increases in the cost of air travel. The proposed framework is particularly significant because India's airline market currently operates largely on dynamic pricing, under which fares change according to demand, availability and other commercial factors. The latest government proposal is expected to establish clearer rules governing when and how intervention can take place when fares rise sharply. However, the precise mechanism for controlling surge pricing has not yet been publicly finalized, and reports do not establish that the government has approved a permanent fixed airfare cap. The Supreme Court of India also examined whether the proposed framework would provide an effective regulatory mechanism. After examining the draft placed before it, the bench reportedly questioned whether an effective regulator had been provided for. This issue is significant because the proceedings are not limited to ticket prices; they also concern how passenger-protection requirements will be monitored and enforced once the new rules come into force. For airlines, the immediate position remains that existing government directions continue to apply while the new rules are being finalised. The Central Government of India told the court that the Ministry of Civil Aviation has been issuing office memorandums to airlines concerning pricing during the interim period. The petitioners, however, argued that airlines were not following those directions, prompting the Supreme Court's warning that non-compliant carriers should face action, including grounding. The case originates from a petition filed by social activist S. Laxminarayanan seeking tighter regulation of airfares and greater protection for passengers. The plea has raised concerns about steep and unpredictable increases in ticket prices, surge pricing, baggage charges, cancellation and refund practices and other ancillary fees. It has also sought stronger regulatory oversight of the aviation sector. The Supreme Court of India has been examining the issue for several months. In earlier proceedings, the court expressed concern over sharp increases in airfares during periods of high demand and sought a mechanism to provide greater predictability and protection to passengers. On May 15, the court observed that there should be some “rationalisation” of airfares and sought measures to provide relief to air passengers. The latest August hearing follows the court's July direction requiring the Central Government to place the proposed aviation rules before it. The government had said the rules had been framed and were undergoing the statutory process. The court nevertheless required the proposed framework to be produced before it in a sealed cover, even if the rules had not yet completed the parliamentary process. The Central Government of India has now secured three more weeks to complete the rule-making process. The matter has been listed for further hearing on September 7, 2026, when the Supreme Court of India is expected to consider the status of the final rules and the regulatory mechanism proposed for enforcing them. For passengers, the eventual rules could bring greater clarity to how airlines price tickets during periods of unusually high demand, how additional baggage charges are applied and how cancellations and refunds are handled. For airlines, the framework could introduce clearer compliance obligations and potentially stronger enforcement where government directions are breached. The exact obligations, however, will become clear only after the Central Government completes the rule-making process and formally notifies the final rules. The latest development therefore marks a significant step towards a formal regulatory framework for airfare and passenger-related charges, but it does not yet mean that a new airfare cap or a final surge-pricing formula is in force. The Central Government is still completing the rules, and the Supreme Court of India is due to review the matter again on September 7.

India’s Supreme Court Pushes Government To Finalise New Aviation Rules Within 3 Weeks

August 19, 2026

Milan, Italy: A baggage cart carrying checked luggage caught fire at Milan Malpensa Airport in Italy on Sunday, August 16, shortly before the baggage was due to be handled for a British Airways flight to London Heathrow, prompting airport firefighters to intervene and damaging a small number of passengers' bags. The incident occurred on the airport apron and did not involve a fire onboard the aircraft. The fire involved an Aviapartner baggage-handling cart at Milan Malpensa. The handling company operates ground services at the airport, and the cart had just completed baggage handling associated with a British Airways flight arriving from London when it caught fire. Initial reports focused on the possibility of a lithium-ion battery inside one of the bags, but subsequent airport-source information pointed to an electrical fault in the ground vehicle instead. The incident was captured on video by former BBC journalist Jon Sopel, who was at Malpensa waiting to travel on British Airways flight BA585 from Milan to London Heathrow. The footage showed dense black smoke rising from the baggage container, with flames visible around the luggage. Ground personnel moved other baggage containers away from the burning unit to prevent the fire from spreading before airport fire crews arrived. The aircraft associated with BA585 was an Airbus A321neo registered G-NEOT, powered by two CFM International LEAP-1A32 engines. The scheduled route was Milan Malpensa Airport (MXP) to London Heathrow Airport (LHR), with British Airways operating the service under flight number BA585. The fire occurred before the affected luggage could create a fire risk inside the aircraft. The burning baggage unit remained on the ground and was dealt with by airport emergency crews. The other containers were moved away from the fire, helping prevent the flames from spreading to additional baggage or equipment. Firefighters extinguished the blaze rapidly using water. British Airways confirmed that some passengers' checked baggage was damaged. In a statement, the airline said: “We’re aware of a small number of checked bags that were damaged by fire while on the ground at Milan Malpensa Airport. The incident was quickly dealt with, and there were no injuries or impact to any flights.” The airline added: “We’ve been in contact with the small number of customers whose bags are affected to apologise and provide support. We are working closely with our partners, and an investigation is underway to establish the cause.” That statement is significant because it confirms that the fire affected checked baggage on the ground but did not result in injuries or a fire onboard the aircraft. It also shows that British Airways had not initially announced a confirmed cause and was relying on an investigation with its ground-handling partners. The investigation remained underway, while British Airways confirmed that only a small number of checked bags were damaged and that there were no injuries.

British Airways BA585 Baggage Cart Carrying Checked Luggage Catches Fire At Milan

August 18, 2026

Subscribe to our Newsletter

Email

Subscribe to our Newsletter

Email

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

Coming Soon!

Explore

Contact

First Name

Last Name

Phone/Mobile

Email

Topic

Your Message

Attach Document

Choose File

Search

About Us
Latest News
Aviation Today Perspectives
Aviation Jobs
Contact Us
Advertisement

Aviation Newsletter

Facebook Instagram Linkedin X-twitter Youtube