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

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
Two Dead After Light Aircraft Crashes In Remote Area Of North Wales, AAIB Investigates
India Targets Electric Air Taxis By 2028 As Sarla Advances eVTOL Testing In Bengaluru
SACAA Preliminary Findings Show No Engine Power At Impact In Fatal South Africa Crash
Heart Aerospace X1 Completes First Flight As World’s Largest Battery-Electric Aircraft
South Korea’s Incheon Overtakes Dubai To Become World’s Busiest International Airport
FAA Orders 471 Boeing 737 MAX Jets To Undergo Crack Inspections Over Structural Risks
Air India Group Mandates Substance Screening For All Pilots Following A320neo Incident
China’s Homegrown C919 Makes International Debut With Air China Flight To Mongolia

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

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

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

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

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

India Targets Electric Air Taxis By 2028 As Sarla Advances eVTOL Testing In Bengaluru

India Targets Electric Air Taxis By 2028 As Sarla Advances eVTOL Testing In Bengaluru

SACAA Preliminary Findings Show No Engine Power At Impact In Fatal South Africa Crash

SACAA Preliminary Findings Show No Engine Power At Impact In Fatal South Africa Crash

Latest Breaking News & Developments

Latest Breaking News & Developments

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

Incidents

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

Posted onAugust 17, 2026August 17, 2026

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

Incidents

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

Posted onAugust 17, 2026August 17, 2026

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

Aircraft Crashes

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

Posted onAugust 17, 2026August 17, 2026

India Targets Electric Air Taxis By 2028 As Sarla Advances eVTOL Testing In Bengaluru

eVTOL

India Targets Electric Air Taxis By 2028 As Sarla Advances eVTOL Testing In Bengaluru

Posted onAugust 16, 2026August 16, 2026

SACAA Preliminary Findings Show No Engine Power At Impact In Fatal South Africa Crash

Investigation

SACAA Preliminary Findings Show No Engine Power At Impact In Fatal South Africa Crash

Posted onAugust 15, 2026August 15, 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

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

Tourist Helicopter Crashes In Rio’s Tijuca National Park, Killing All Four Onboard

Tourist Helicopter Crashes In Rio’s Tijuca National Park, Killing All Four Onboard

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

Nova Scotia Court Approves C$18.075 Million Settlement Over 2015 Air Canada AC624 Crash

Nova Scotia Court Approves C$18.075 Million Settlement Over 2015 Air Canada AC624 Crash

New Delhi, India: Air India’s A320neo operating flight AI2379 from Phuket to Delhi suffered multiple technical and mechanical glitches, including three hydraulic-system failures, an autopilot disconnect and a flight-control stall warning before suddenly losing around 300 feet in altitude, according to information reported by PTI, citing sources. The aircraft encountered turbulence during the August 4 incident, which left 17 people injured. The aircraft, an Airbus A320neo registered VT-EXO, was cruising from Phuket, Thailand, to Delhi when the sudden altitude loss occurred. According to PTI, the autopilot disconnected during the flight, after which the co-pilot manually regained control. A flight-control stall warning then appeared, while several indicator switches briefly went off. Sources also told PTI that the aircraft experienced multiple other technical and mechanical glitches alongside the turbulence. The latest information indicates that the aircraft experienced three separate hydraulic failures. Hydraulic systems use pressurised fluid to operate critical aircraft components, including flight-control systems, making the reported failures a significant part of the ongoing investigation. The crew managed to stabilise the aircraft and subsequently continued the flight to Delhi, where it landed safely. Air India said the aircraft experienced a sudden loss of altitude during cruise before stabilising and continuing normally to Delhi. The flight carried 137 passengers, including three infants, and eight crew members. At least 17 people, 13 passengers and four crew members were reported injured and taken for medical evaluation. The Aircraft Accident Investigation Bureau (AAIB) is investigating the occurrence as a serious incident under ICAO Annex 13, which governs aircraft accident and incident investigations. The aircraft’s flight data recorder and cockpit voice recorder have been secured for examination as investigators work to establish what triggered the altitude loss and the reported technical problems. Airbus has confirmed that it is sending specialists to India to provide technical assistance to the investigation. The manufacturer said it was supporting the relevant investigating authorities in accordance with ICAO Annex 13. France’s Bureau of Enquiry and Analysis for Civil Aviation Safety (BEA) is also joining the investigation because the A320 is manufactured in France. Teams from Airbus and BEA are expected to assist the AAIB as investigators examine the aircraft and recorded flight data. The latest technical findings remain preliminary and have not been established as the final cause of the incident. The reported triple hydraulic failures and other malfunctions are based on sources cited by PTI; they are not yet findings formally released by the AAIB. The investigation is continuing, with technical specialists expected to examine the aircraft’s systems and recorded data before any conclusions are reached. A separate line of investigation concerns the pilot-in-command’s post-flight psychoactive-substance screening. The Civil Aviation Ministry said an initial screening result was “not negative” and required confirmatory laboratory testing. The pilot’s sample was subsequently sent for further analysis, and the final confirmatory result was still awaited in the latest reports. The ministry has not disclosed what substance, if any, was indicated by the initial screening. The distinction is important because an initial “not negative” screening result does not by itself establish drug use. The pilots’ body, ALPA India, has said that commonly used over-the-counter medicines can also produce a non-negative result in psychoactive-substance screening. The confirmatory laboratory test is therefore expected to determine whether the initial result was caused by a prohibited substance or another factor. Both pilots have been taken off flying duties pending the investigation, according to reporting on the ministry’s action. Air India has said it was aware that post-flight screening had been conducted under applicable procedures but had not initially been informed of the results. The final laboratory findings remain an important part of determining whether the screening result has any connection to the August 4 occurrence. The incident was initially widely described as a severe-turbulence event after passengers and crew were thrown from their seats during the sudden altitude change. The newer information from PTI, however, adds a series of reported technical malfunctions including autopilot disconnection, a flight-control stall warning, briefly extinguished indicators and three hydraulic failures to the investigation. Whether these issues caused, contributed to or merely coincided with the altitude loss remains to be established by the AAIB probe. For now, the cause remains officially undetermined. Investigators are examining the aircraft’s systems, flight-recorded data, cockpit recordings and other evidence, with Airbus and France’s BEA assisting the AAIB. The outcome of the pilot’s confirmatory psychoactive-substance test is also awaited. Until those investigations are completed, the reported technical failures and the initial screening result should not be treated as established causes of the incident.

Air India A320neo Reportedly Suffered Three Hydraulic Failures During Phuket-Delhi Flight

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

Chennai, India: An IndiGo Airbus A321neo operating flight 6E-723 from Kolkata to Chennai made a precautionary emergency landing at Chennai International Airport late Tuesday night, August 11, after its left engine became inoperative shortly before landing. The aircraft was carrying 224 passengers and crew members. A full emergency was declared at Chennai Airport at 11:29 p.m. IST, with emergency response teams placed on standby. The aircraft subsequently landed safely on Runway 25 at 11:37 p.m., with all 224 people on board safe and no injuries reported. The flight was scheduled to arrive at 11:30 p.m., making the actual landing seven minutes later than scheduled. According to officials from the Airports Authority of India (AAI), the aircraft reported the technical problem while approaching Chennai. The pilot noticed that the left engine had failed while preparing for landing and alerted air traffic control. Following the alert, airport authorities activated the emergency response arrangements to facilitate the aircraft's safe arrival. The emergency was formally withdrawn at 11:47 p.m., around 10 minutes after the aircraft touched down. Chennai airport authorities said normal operations continued following the incident, with no disruption to airport operations reported. The declaration of a full emergency was a precautionary measure that allowed airport fire, rescue and other emergency services to remain ready for the aircraft's arrival. The aircraft landed without an accident, and there was no reported evacuation, casualty or injury among the 224 people on board. At present, the specific technical cause of the left-engine failure has not been publicly established. The available reports describe the condition as a left-engine failure or a “left engine inoperative condition” and do not provide details about the nature of the malfunction, engine damage or whether a particular component failed. Further technical examination of the aircraft is expected to establish the cause.

IndiGo Airbus A321neo Makes Emergency Landing In Chennai After Left-Engine Failure

Myrtle Beach, United States: American Airlines Flight 1760, a Boeing 737-800 operating from Myrtle Beach International Airport in South Carolina to Charlotte Douglas International Airport in North Carolina, made an emergency return to Myrtle Beach on Monday, August 10, after reportedly striking a flock of birds shortly after takeoff and experiencing an engine malfunction. The aircraft took off from Myrtle Beach at about 8:11 a.m. local time and was only minutes into the flight when the crew reported the problem to air traffic control. According to air traffic recordings obtained through LiveATC.net, the pilot declared a Mayday, saying, “Mayday, mayday, mayday. We’ve got an engine problem here.” The crew subsequently reported an engine malfunction as the aircraft turned back toward Myrtle Beach. Reports indicate the aircraft had struck birds during its climb, with another pilot who witnessed the event telling air traffic control, “I saw he took up birds, it looked like, at least in the left side engine.” The reported bird ingestion involved the aircraft’s left engine, beneath the left wing. Passengers recorded video showing bright orange flames and sparks appearing from the left side of the aircraft beneath the wing. Passenger Patrick Gotwalt captured footage of the event, while witnesses on the ground also reported hearing several loud popping sounds and seeing orange flashes from the aircraft’s left side. Lindsey Mackey, who was on the ground near the beach, told CNN that she heard loud popping noises before noticing orange flashes coming from the aircraft’s left wing. The visual evidence showed what appeared to be flames or sparks coming from the area around the left engine as the aircraft continued flying back toward the airport. As the Boeing 737-800 returned, airport emergency personnel prepared for its arrival. Workers subsequently found substantial bird remains and debris on the runway. Radio communications from the airport included the statement, “We’ve got a lot of bird debris out here. We’re going to grab as many big pieces as we can.” The debris provided physical evidence consistent with reports that the aircraft had struck birds. Flight 1760 landed safely back at Myrtle Beach at approximately 8:40 a.m., after spending roughly 15 minutes in the air, according to reports. The aircraft taxied to the gate under its own power, allowing passengers to disembark normally. No injuries were reported. The flight was carrying 172 passengers/customers and nine crew members, according to the New York Post, although the airline's statement cited by The U.S. Sun referred specifically to the 172 customers aboard. American Airlines said the aircraft was removed from service for a maintenance inspection following the incident. In a statement, the airline said, “The aircraft landed safely and has been taken out of service to be inspected by our maintenance team.” The airline added, “Our team worked to get customers on their way to Charlotte (CLT) on a replacement aircraft.” American also thanked its employees for their professionalism and passengers for their understanding. The aircraft was therefore not continued to Charlotte after the emergency landing. American arranged a replacement aircraft so the affected passengers could continue their journey to Charlotte. Although video footage showed flames coming from the left engine area, the New York Post reported that there was no internal engine fire, indicating that the visible flames did not necessarily represent a sustained fire inside the engine. The aircraft was nevertheless removed from service for inspection. The Federal Aviation Administration confirmed that the aircraft landed at Myrtle Beach at about 8:40 a.m. and said it would investigate the incident. The investigation is expected to establish the precise nature of the engine malfunction and assess the bird-strike evidence. The bird remains recovered after the incident are also significant because wildlife remains from aircraft strikes can be examined to determine the species involved. The FAA's Smithsonian Feather Identification Lab program routinely analyzes bird remains from aircraft strikes to help identify the species and improve airport wildlife-management measures.

American Airlines Flight 1760 Makes Emergency Landing After Bird Strike Damages Engine

SWISS A330 Diverts To Dublin After Smoke From Power Bank Reported Over Atlantic Flight

SWISS A330 Diverts To Dublin After Smoke From Power Bank Reported Over Atlantic Flight

Aircraft Crashes

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

Tourist Helicopter Crashes In Rio’s Tijuca National Park, Killing All Four Onboard

Tourist Helicopter Crashes In Rio’s Tijuca National Park, Killing All Four Onboard

Airlines

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

Nova Scotia Court Approves C$18.075 Million Settlement Over 2015 Air Canada AC624 Crash

Nova Scotia Court Approves C$18.075 Million Settlement Over 2015 Air Canada AC624 Crash

New Delhi, India: Air India’s A320neo operating flight AI2379 from Phuket to Delhi suffered multiple technical and mechanical glitches, including three hydraulic-system failures, an autopilot disconnect and a flight-control stall warning before suddenly losing around 300 feet in altitude, according to information reported by PTI, citing sources. The aircraft encountered turbulence during the August 4 incident, which left 17 people injured. The aircraft, an Airbus A320neo registered VT-EXO, was cruising from Phuket, Thailand, to Delhi when the sudden altitude loss occurred. According to PTI, the autopilot disconnected during the flight, after which the co-pilot manually regained control. A flight-control stall warning then appeared, while several indicator switches briefly went off. Sources also told PTI that the aircraft experienced multiple other technical and mechanical glitches alongside the turbulence. The latest information indicates that the aircraft experienced three separate hydraulic failures. Hydraulic systems use pressurised fluid to operate critical aircraft components, including flight-control systems, making the reported failures a significant part of the ongoing investigation. The crew managed to stabilise the aircraft and subsequently continued the flight to Delhi, where it landed safely. Air India said the aircraft experienced a sudden loss of altitude during cruise before stabilising and continuing normally to Delhi. The flight carried 137 passengers, including three infants, and eight crew members. At least 17 people, 13 passengers and four crew members were reported injured and taken for medical evaluation. The Aircraft Accident Investigation Bureau (AAIB) is investigating the occurrence as a serious incident under ICAO Annex 13, which governs aircraft accident and incident investigations. The aircraft’s flight data recorder and cockpit voice recorder have been secured for examination as investigators work to establish what triggered the altitude loss and the reported technical problems. Airbus has confirmed that it is sending specialists to India to provide technical assistance to the investigation. The manufacturer said it was supporting the relevant investigating authorities in accordance with ICAO Annex 13. France’s Bureau of Enquiry and Analysis for Civil Aviation Safety (BEA) is also joining the investigation because the A320 is manufactured in France. Teams from Airbus and BEA are expected to assist the AAIB as investigators examine the aircraft and recorded flight data. The latest technical findings remain preliminary and have not been established as the final cause of the incident. The reported triple hydraulic failures and other malfunctions are based on sources cited by PTI; they are not yet findings formally released by the AAIB. The investigation is continuing, with technical specialists expected to examine the aircraft’s systems and recorded data before any conclusions are reached. A separate line of investigation concerns the pilot-in-command’s post-flight psychoactive-substance screening. The Civil Aviation Ministry said an initial screening result was “not negative” and required confirmatory laboratory testing. The pilot’s sample was subsequently sent for further analysis, and the final confirmatory result was still awaited in the latest reports. The ministry has not disclosed what substance, if any, was indicated by the initial screening. The distinction is important because an initial “not negative” screening result does not by itself establish drug use. The pilots’ body, ALPA India, has said that commonly used over-the-counter medicines can also produce a non-negative result in psychoactive-substance screening. The confirmatory laboratory test is therefore expected to determine whether the initial result was caused by a prohibited substance or another factor. Both pilots have been taken off flying duties pending the investigation, according to reporting on the ministry’s action. Air India has said it was aware that post-flight screening had been conducted under applicable procedures but had not initially been informed of the results. The final laboratory findings remain an important part of determining whether the screening result has any connection to the August 4 occurrence. The incident was initially widely described as a severe-turbulence event after passengers and crew were thrown from their seats during the sudden altitude change. The newer information from PTI, however, adds a series of reported technical malfunctions including autopilot disconnection, a flight-control stall warning, briefly extinguished indicators and three hydraulic failures to the investigation. Whether these issues caused, contributed to or merely coincided with the altitude loss remains to be established by the AAIB probe. For now, the cause remains officially undetermined. Investigators are examining the aircraft’s systems, flight-recorded data, cockpit recordings and other evidence, with Airbus and France’s BEA assisting the AAIB. The outcome of the pilot’s confirmatory psychoactive-substance test is also awaited. Until those investigations are completed, the reported technical failures and the initial screening result should not be treated as established causes of the incident.

Air India A320neo Reportedly Suffered Three Hydraulic Failures During Phuket-Delhi Flight

Incidents

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

Chennai, India: An IndiGo Airbus A321neo operating flight 6E-723 from Kolkata to Chennai made a precautionary emergency landing at Chennai International Airport late Tuesday night, August 11, after its left engine became inoperative shortly before landing. The aircraft was carrying 224 passengers and crew members. A full emergency was declared at Chennai Airport at 11:29 p.m. IST, with emergency response teams placed on standby. The aircraft subsequently landed safely on Runway 25 at 11:37 p.m., with all 224 people on board safe and no injuries reported. The flight was scheduled to arrive at 11:30 p.m., making the actual landing seven minutes later than scheduled. According to officials from the Airports Authority of India (AAI), the aircraft reported the technical problem while approaching Chennai. The pilot noticed that the left engine had failed while preparing for landing and alerted air traffic control. Following the alert, airport authorities activated the emergency response arrangements to facilitate the aircraft's safe arrival. The emergency was formally withdrawn at 11:47 p.m., around 10 minutes after the aircraft touched down. Chennai airport authorities said normal operations continued following the incident, with no disruption to airport operations reported. The declaration of a full emergency was a precautionary measure that allowed airport fire, rescue and other emergency services to remain ready for the aircraft's arrival. The aircraft landed without an accident, and there was no reported evacuation, casualty or injury among the 224 people on board. At present, the specific technical cause of the left-engine failure has not been publicly established. The available reports describe the condition as a left-engine failure or a “left engine inoperative condition” and do not provide details about the nature of the malfunction, engine damage or whether a particular component failed. Further technical examination of the aircraft is expected to establish the cause.

IndiGo Airbus A321neo Makes Emergency Landing In Chennai After Left-Engine Failure

Myrtle Beach, United States: American Airlines Flight 1760, a Boeing 737-800 operating from Myrtle Beach International Airport in South Carolina to Charlotte Douglas International Airport in North Carolina, made an emergency return to Myrtle Beach on Monday, August 10, after reportedly striking a flock of birds shortly after takeoff and experiencing an engine malfunction. The aircraft took off from Myrtle Beach at about 8:11 a.m. local time and was only minutes into the flight when the crew reported the problem to air traffic control. According to air traffic recordings obtained through LiveATC.net, the pilot declared a Mayday, saying, “Mayday, mayday, mayday. We’ve got an engine problem here.” The crew subsequently reported an engine malfunction as the aircraft turned back toward Myrtle Beach. Reports indicate the aircraft had struck birds during its climb, with another pilot who witnessed the event telling air traffic control, “I saw he took up birds, it looked like, at least in the left side engine.” The reported bird ingestion involved the aircraft’s left engine, beneath the left wing. Passengers recorded video showing bright orange flames and sparks appearing from the left side of the aircraft beneath the wing. Passenger Patrick Gotwalt captured footage of the event, while witnesses on the ground also reported hearing several loud popping sounds and seeing orange flashes from the aircraft’s left side. Lindsey Mackey, who was on the ground near the beach, told CNN that she heard loud popping noises before noticing orange flashes coming from the aircraft’s left wing. The visual evidence showed what appeared to be flames or sparks coming from the area around the left engine as the aircraft continued flying back toward the airport. As the Boeing 737-800 returned, airport emergency personnel prepared for its arrival. Workers subsequently found substantial bird remains and debris on the runway. Radio communications from the airport included the statement, “We’ve got a lot of bird debris out here. We’re going to grab as many big pieces as we can.” The debris provided physical evidence consistent with reports that the aircraft had struck birds. Flight 1760 landed safely back at Myrtle Beach at approximately 8:40 a.m., after spending roughly 15 minutes in the air, according to reports. The aircraft taxied to the gate under its own power, allowing passengers to disembark normally. No injuries were reported. The flight was carrying 172 passengers/customers and nine crew members, according to the New York Post, although the airline's statement cited by The U.S. Sun referred specifically to the 172 customers aboard. American Airlines said the aircraft was removed from service for a maintenance inspection following the incident. In a statement, the airline said, “The aircraft landed safely and has been taken out of service to be inspected by our maintenance team.” The airline added, “Our team worked to get customers on their way to Charlotte (CLT) on a replacement aircraft.” American also thanked its employees for their professionalism and passengers for their understanding. The aircraft was therefore not continued to Charlotte after the emergency landing. American arranged a replacement aircraft so the affected passengers could continue their journey to Charlotte. Although video footage showed flames coming from the left engine area, the New York Post reported that there was no internal engine fire, indicating that the visible flames did not necessarily represent a sustained fire inside the engine. The aircraft was nevertheless removed from service for inspection. The Federal Aviation Administration confirmed that the aircraft landed at Myrtle Beach at about 8:40 a.m. and said it would investigate the incident. The investigation is expected to establish the precise nature of the engine malfunction and assess the bird-strike evidence. The bird remains recovered after the incident are also significant because wildlife remains from aircraft strikes can be examined to determine the species involved. The FAA's Smithsonian Feather Identification Lab program routinely analyzes bird remains from aircraft strikes to help identify the species and improve airport wildlife-management measures.

American Airlines Flight 1760 Makes Emergency Landing After Bird Strike Damages Engine

SWISS A330 Diverts To Dublin After Smoke From Power Bank Reported Over Atlantic Flight

SWISS A330 Diverts To Dublin After Smoke From Power Bank Reported Over Atlantic Flight

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

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

August 17, 2026

Phoenix, United States: A potential mid-air collision was averted near Phoenix Sky Harbor International Airport on August 14, 2026, after

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

August 17, 2026

Munich, Germany: A Vietnam Airlines Boeing 787-9 bound for Hanoi took an unusually long takeoff run from Munich Airport on

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

August 17, 2026

Trawsfynydd, United Kingdom: Two people have died after a light aircraft crashed in a remote area near Trawsfynydd, Gwynedd, North

Bengaluru, India: India is targeting the introduction of electric air taxis by 2028, with Union Civil Aviation Minister Ram Mohan Naidu saying testing of electric vertical take-off and landing (eVTOL) aircraft is expected to accelerate from 2027. The latest development comes as Bengaluru-based Sarla Aviation has secured Design Organisation Approval (DOA) from the Directorate General of Civil Aviation (DGCA), a key regulatory step toward type certification of its indigenous eVTOL aircraft. The approval was handed over to Sarla Aviation at the inauguration of its new Bengaluru headquarters on August 8, 2026. Naidu said India wants to see the aircraft operating by 2028. “By 2028, we want to see these machines fly in India. There is a huge requirement, not only in Bangalore, but Mumbai and Delhi,” he said. He added, “I expect that next year we'll be completely in the testing phase,” while reiterating, “By 2028, we plan to make this happen.” Sarla Aviation has also moved beyond the early prototype stage. On July 1, 2026, the company announced that its half-scale Sylla 1.0 eVTOL technology demonstrator had completed more than 500 tests and over 18 hours of flight testing during a six-month campaign. The 700-kg-class aircraft has a 7.5-metre wingspan and, according to Sarla, became the heaviest electric aircraft to take off in India. The programme tested the aircraft's electric propulsion, battery architecture, distributed propulsion, flight controls, airframe and landing gear as an integrated system. Sarla Aviation CTO and co-founder Rakesh Gaonkar said the Sylla programme had produced the data needed to guide the next stage of development. “Sylla has given us the data we set out to capture, and those learnings are already shaping our next-gen aircraft as we move towards transition and sustained wing-borne flight on our journey to our 6+1 air taxi Shunya,” he said. The next step is Sylla 2.0, which is intended to demonstrate controlled transition from hover to sustained wing-borne flight. That is an important stage before the company moves toward a certifiable passenger-carrying eVTOL. Sarla's planned production aircraft is the six-passenger-plus-pilot Shunya. The developments provide an important update to the electric-air-taxi plan outlined by ET Now. The publication reported that India had set a 2028 target for eVTOL aircraft, with Naidu saying testing would gather pace the following year. The report highlighted Bengaluru, Mumbai and Delhi as cities where demand for such aircraft could be particularly significant because of severe road congestion and lengthy airport-city journeys. An eVTOL is an electrically powered aircraft capable of vertical take-off and landing. Unlike conventional fixed-wing aircraft, it does not require a conventional runway and can potentially operate from smaller facilities closer to urban centres. The technology combines characteristics associated with helicopters, drones and conventional aircraft and is being developed under the broader advanced-air-mobility sector. Sarla Aviation's Shunya is designed around seven electric motors. Six motors provide vertical lift, while a seventh motor mounted at the rear provides forward propulsion. Sarla Aviation co-founder and CEO Adrian Schmidt explained the configuration to ANI: “It's powered by six electric motors that lift it up and one in the rear that pushes it forward. So we have a total of seven electric motors that we're using and it's piloted as of now with six passengers.” The company has said the aircraft's propulsion remains electrically driven. However, Schmidt explained that the design leaves room for a turbo-generator that could potentially recharge the batteries during flight. “We have enough space allocation so that we can consider putting in a turbo generator to charge our batteries mid-flight. But the energy transition from the battery to the motors is always going to be purely electric,” he said. Sarla first unveiled the Shunya prototype at the Bharat Mobility Global Expo in New Delhi in January 2025. The aircraft was presented as a six-passenger eVTOL with a maximum payload of about 680 kg and a targeted top speed of up to 250 km/h. The company said it was designed primarily for short urban journeys of roughly 20–30 km, while reported specifications indicated a potential range of up to 160 km with available battery technology. Sarla's roadmap has also included infrastructure and manufacturing. In November 2025, the company signed an MoU with the Andhra Pradesh government for a 500-acre aerospace campus in Anantapur, with an initial investment of ₹1,300 crore. Sarla described the project as an integrated Urban Air Mobility facility for eVTOL manufacturing and related activities. The company has said the facility is intended to support future aircraft production and air-taxi operations. The company's airport strategy also began taking shape earlier. Sarla Aviation and Bengaluru International Airport Limited signed a partnership agreement in January 2024 to explore an eVTOL ecosystem at Bengaluru airport, including connectivity between the airport and urban areas, vertiport infrastructure and an advanced traffic-management system for future eVTOL operations. Healthcare is another potential application. Bengaluru airport had an agreement with Sarla Aviation for last-mile connectivity and that Manipal Hospitals had also entered an agreement with the company for potential air-ambulance operations. More recent industry reporting indicates that hospitals and air-ambulance operators are increasingly exploring eVTOL partnerships as India develops its advanced-air-mobility ecosystem. The possible uses therefore extend beyond passenger air taxis. The technology could support airport-to-city transfers, last-mile connectivity, air ambulance operations, medical evacuation and cargo transportation. For India, airport connectivity is expected to be one of the earliest practical applications because road journeys between major airports and city centres can take considerable time. Naidu has said an airport-to-city journey that currently takes as long as two hours could potentially be reduced to around 20–30 minutes using eVTOL aircraft. The initial model is therefore expected to focus on short-distance and airport-linked journeys rather than replacing conventional public transportation. The Indian eVTOL market is not limited to Sarla Aviation. Chennai-based The ePlane Company is developing its e200X electric aircraft, while Hyderabad-based BluJ Aerospace is working on eVTOL technology for cargo and other applications. India is therefore developing multiple domestic approaches to advanced air mobility rather than relying solely on one manufacturer. There is also an international dimension to India's air-taxi plans. In 2023, InterGlobe Enterprises, the parent company of IndiGo, announced a partnership with US-based Archer Aviation to explore an all-electric air-taxi service in India, with an original 2026 target. However, that timeline has not materialised as initially envisaged. In 2026, IndiGo Ventures separately invested about ₹10 crore in Sarla Aviation, giving the Indian startup additional strategic backing. Importantly, the IndiGo investment should not be presented as confirmation that IndiGo itself will operate Sarla's eVTOL air-taxi service. Recent reporting said Sarla Aviation clarified that IndiGo's investment did not mean the airline was directly involved in its eVTOL operating plans. The regulatory process remains one of the biggest hurdles. Before commercial passenger operations can begin, eVTOL aircraft must demonstrate compliance with safety and airworthiness requirements and obtain the necessary certification. The DGCA will have to address aircraft design, flight operations, pilot qualifications, infrastructure, vertiports and integration with existing air-traffic systems. Infrastructure is another challenge. Commercial operations will require suitable landing and take-off locations, charging or energy infrastructure, maintenance facilities and systems for managing eVTOL traffic around densely populated areas. Battery performance, aircraft range, weather, operating economics and air-traffic management will also influence whether the 2028 target can be achieved at scale. Sarla's progress in 2026 nevertheless represents a significant shift from the concept and prototype phase. With the Sylla demonstrator having completed an extensive flight-test campaign and the company now holding DGCA Design Organisation Approval, its Shunya programme has entered a more advanced development and certification phase. The government's 2028 target will now depend on the pace of testing, transition-flight development, type certification, infrastructure creation and operational approvals over the next two years.

India Targets Electric Air Taxis By 2028 As Sarla Advances eVTOL Testing In Bengaluru

August 16, 2026

Bengaluru, India: India is targeting the introduction of electric air taxis by 2028, with Union Civil Aviation Minister Ram Mohan

Never miss any important news. Subscribe to our newsletter.

Email

Recent News

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

August 17, 2026

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

August 17, 2026

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

August 17, 2026

Bengaluru, India: India is targeting the introduction of electric air taxis by 2028, with Union Civil Aviation Minister Ram Mohan Naidu saying testing of electric vertical take-off and landing (eVTOL) aircraft is expected to accelerate from 2027. The latest development comes as Bengaluru-based Sarla Aviation has secured Design Organisation Approval (DOA) from the Directorate General of Civil Aviation (DGCA), a key regulatory step toward type certification of its indigenous eVTOL aircraft. The approval was handed over to Sarla Aviation at the inauguration of its new Bengaluru headquarters on August 8, 2026. Naidu said India wants to see the aircraft operating by 2028. “By 2028, we want to see these machines fly in India. There is a huge requirement, not only in Bangalore, but Mumbai and Delhi,” he said. He added, “I expect that next year we'll be completely in the testing phase,” while reiterating, “By 2028, we plan to make this happen.” Sarla Aviation has also moved beyond the early prototype stage. On July 1, 2026, the company announced that its half-scale Sylla 1.0 eVTOL technology demonstrator had completed more than 500 tests and over 18 hours of flight testing during a six-month campaign. The 700-kg-class aircraft has a 7.5-metre wingspan and, according to Sarla, became the heaviest electric aircraft to take off in India. The programme tested the aircraft's electric propulsion, battery architecture, distributed propulsion, flight controls, airframe and landing gear as an integrated system. Sarla Aviation CTO and co-founder Rakesh Gaonkar said the Sylla programme had produced the data needed to guide the next stage of development. “Sylla has given us the data we set out to capture, and those learnings are already shaping our next-gen aircraft as we move towards transition and sustained wing-borne flight on our journey to our 6+1 air taxi Shunya,” he said. The next step is Sylla 2.0, which is intended to demonstrate controlled transition from hover to sustained wing-borne flight. That is an important stage before the company moves toward a certifiable passenger-carrying eVTOL. Sarla's planned production aircraft is the six-passenger-plus-pilot Shunya. The developments provide an important update to the electric-air-taxi plan outlined by ET Now. The publication reported that India had set a 2028 target for eVTOL aircraft, with Naidu saying testing would gather pace the following year. The report highlighted Bengaluru, Mumbai and Delhi as cities where demand for such aircraft could be particularly significant because of severe road congestion and lengthy airport-city journeys. An eVTOL is an electrically powered aircraft capable of vertical take-off and landing. Unlike conventional fixed-wing aircraft, it does not require a conventional runway and can potentially operate from smaller facilities closer to urban centres. The technology combines characteristics associated with helicopters, drones and conventional aircraft and is being developed under the broader advanced-air-mobility sector. Sarla Aviation's Shunya is designed around seven electric motors. Six motors provide vertical lift, while a seventh motor mounted at the rear provides forward propulsion. Sarla Aviation co-founder and CEO Adrian Schmidt explained the configuration to ANI: “It's powered by six electric motors that lift it up and one in the rear that pushes it forward. So we have a total of seven electric motors that we're using and it's piloted as of now with six passengers.” The company has said the aircraft's propulsion remains electrically driven. However, Schmidt explained that the design leaves room for a turbo-generator that could potentially recharge the batteries during flight. “We have enough space allocation so that we can consider putting in a turbo generator to charge our batteries mid-flight. But the energy transition from the battery to the motors is always going to be purely electric,” he said. Sarla first unveiled the Shunya prototype at the Bharat Mobility Global Expo in New Delhi in January 2025. The aircraft was presented as a six-passenger eVTOL with a maximum payload of about 680 kg and a targeted top speed of up to 250 km/h. The company said it was designed primarily for short urban journeys of roughly 20–30 km, while reported specifications indicated a potential range of up to 160 km with available battery technology. Sarla's roadmap has also included infrastructure and manufacturing. In November 2025, the company signed an MoU with the Andhra Pradesh government for a 500-acre aerospace campus in Anantapur, with an initial investment of ₹1,300 crore. Sarla described the project as an integrated Urban Air Mobility facility for eVTOL manufacturing and related activities. The company has said the facility is intended to support future aircraft production and air-taxi operations. The company's airport strategy also began taking shape earlier. Sarla Aviation and Bengaluru International Airport Limited signed a partnership agreement in January 2024 to explore an eVTOL ecosystem at Bengaluru airport, including connectivity between the airport and urban areas, vertiport infrastructure and an advanced traffic-management system for future eVTOL operations. Healthcare is another potential application. Bengaluru airport had an agreement with Sarla Aviation for last-mile connectivity and that Manipal Hospitals had also entered an agreement with the company for potential air-ambulance operations. More recent industry reporting indicates that hospitals and air-ambulance operators are increasingly exploring eVTOL partnerships as India develops its advanced-air-mobility ecosystem. The possible uses therefore extend beyond passenger air taxis. The technology could support airport-to-city transfers, last-mile connectivity, air ambulance operations, medical evacuation and cargo transportation. For India, airport connectivity is expected to be one of the earliest practical applications because road journeys between major airports and city centres can take considerable time. Naidu has said an airport-to-city journey that currently takes as long as two hours could potentially be reduced to around 20–30 minutes using eVTOL aircraft. The initial model is therefore expected to focus on short-distance and airport-linked journeys rather than replacing conventional public transportation. The Indian eVTOL market is not limited to Sarla Aviation. Chennai-based The ePlane Company is developing its e200X electric aircraft, while Hyderabad-based BluJ Aerospace is working on eVTOL technology for cargo and other applications. India is therefore developing multiple domestic approaches to advanced air mobility rather than relying solely on one manufacturer. There is also an international dimension to India's air-taxi plans. In 2023, InterGlobe Enterprises, the parent company of IndiGo, announced a partnership with US-based Archer Aviation to explore an all-electric air-taxi service in India, with an original 2026 target. However, that timeline has not materialised as initially envisaged. In 2026, IndiGo Ventures separately invested about ₹10 crore in Sarla Aviation, giving the Indian startup additional strategic backing. Importantly, the IndiGo investment should not be presented as confirmation that IndiGo itself will operate Sarla's eVTOL air-taxi service. Recent reporting said Sarla Aviation clarified that IndiGo's investment did not mean the airline was directly involved in its eVTOL operating plans. The regulatory process remains one of the biggest hurdles. Before commercial passenger operations can begin, eVTOL aircraft must demonstrate compliance with safety and airworthiness requirements and obtain the necessary certification. The DGCA will have to address aircraft design, flight operations, pilot qualifications, infrastructure, vertiports and integration with existing air-traffic systems. Infrastructure is another challenge. Commercial operations will require suitable landing and take-off locations, charging or energy infrastructure, maintenance facilities and systems for managing eVTOL traffic around densely populated areas. Battery performance, aircraft range, weather, operating economics and air-traffic management will also influence whether the 2028 target can be achieved at scale. Sarla's progress in 2026 nevertheless represents a significant shift from the concept and prototype phase. With the Sylla demonstrator having completed an extensive flight-test campaign and the company now holding DGCA Design Organisation Approval, its Shunya programme has entered a more advanced development and certification phase. The government's 2028 target will now depend on the pace of testing, transition-flight development, type certification, infrastructure creation and operational approvals over the next two years.

India Targets Electric Air Taxis By 2028 As Sarla Advances eVTOL Testing In Bengaluru

August 16, 2026

Fochville, South Africa: The preliminary accident report, released on 28 July 2026 by the Accident and Incident Investigations Division (AIID) of the South African Civil Aviation Authority (SACAA), found that the engine of a Bird Aviation Piper PA-28-180 registered ZS-ESZ was not producing power when the aircraft struck the ground near Fochville, Gauteng, on 27 June 2026. The report remains preliminary, with the investigation still ongoing and the AIID cautioning that its findings do not apportion blame or liability. According to the report, the operator was Bird Aviation, while the aircraft was being used under a hire-and-fly arrangement for hour-building. The operation was classified as Training under Part 91, and the aircraft belonged to the approved training organisation (ATO) from which it was hired. The accident involved two people, a 21-year-old Indian pilot and one passenger. Both were fatally injured and the aircraft was destroyed. The pilot held a valid Private Pilot Licence (PPL) and was building flight hours toward a Commercial Pilot Licence (CPL) through the ATO. The flight took place on the afternoon of 27 June 2026, when the pilot and passenger departed Lanseria International Airport (FALA) in Gauteng on an hour-building flight, intending to return to the same airport. The flight was conducted under visual meteorological conditions (VMC) and in accordance with Part 91 of the Civil Aviation Regulations. The flight had initially been planned for 0900Z, but departure was delayed because of persistent haze and low visibility. After conditions improved, the aircraft departed Runway 07 at 1325Z, as confirmed by an air traffic control officer at Lanseria. It then flew toward the Johannesburg General Flying Area (GFA), Flight Area Dangerous 182 (FAD 182). Multiple eyewitnesses later reported seeing the aircraft flying unusually low and performing unfamiliar manoeuvres. The aircraft subsequently flipped and began spinning to the left before impacting the ground. The crash occurred on a farm at Elandsfontein, south-east of Fochville, Gauteng, at coordinates 26° 35' 27.30" South, 27° 33' 41.24" East, with a field elevation of 5,124 feet. The accident was recorded at 1415Z. The pilot was a 21-year-old Indian national with a valid PPL. His licence was initially issued by the regulator on 25 May 2026 and was valid until 30 April 2027. His Class 2 aviation medical certificate was issued on 26 March 2025 and was valid until 31 March 2030. The report states that the aircraft type was endorsed on his licence and that he had no previous accidents recorded in relation to the investigation. The pilot had accumulated 132.2 total flight hours, including 19.4 hours in the previous seven days and 55.1 hours in the previous 90 days. He had flown 43.8 hours on the aircraft during the previous 90 days and had accumulated 122.7 hours on the Piper PA-28-180. The aircraft was a 1977-built Piper PA-28-180, a four-seat, single-engine, all-metal, low-wing aircraft with fixed tricycle landing gear. It was powered by a four-cylinder, naturally aspirated 180-horsepower Lycoming O-360-series engine. Its serial number was 28-3303, and it had accumulated 3,242.6 airframe hours by the time of the accident. The AIID found that the aircraft had valid registration and airworthiness documentation. Its current Certificate of Registration had been issued on 19 September 2025, while its latest Certificate of Airworthiness was valid until 31 October 2026. The aircraft underwent its mandatory periodic inspection on 13 March 2026 at 3,218.4 airframe hours, after which a Certificate of Release to Service was issued, valid until 12 March 2027 or 3,318.4 total airframe hours, whichever came first. The aircraft was maintained by an approved aircraft maintenance organisation whose certificate was valid until 30 June 2026. The organisation held Category A and Category C ratings for the aircraft's airframe and engine. The ATO's certificate had been renewed on 17 November 2025 and was valid until 28 February 2029. Fuel records showed that 111 litres of Avgas 100LL had been uplifted after the aircraft's flight on 26 June 2026, with the pilot refuelling the tanks before parking the aircraft. The Piper PA-28-180 has a fuel capacity of 189 litres, providing approximately six hours of endurance. The preliminary findings state that the aircraft departed Lanseria with full fuel tanks and no technical issues. However, fuel was found leaking from the aircraft after the accident. The report does not currently identify the fuel leak as the cause of the engine power loss. Weather conditions were favourable and were not considered a contributing factor. The 1400Z METAR from Lanseria recorded winds from 300° at 7 knots, CAVOK visibility, a temperature of 16°C, scattered clouds at 4,500 feet, a dew point of 5°C and QNH of 1026 hPa. The aircraft's navigation and communication equipment had no recorded defects before the flight. It was not equipped with a flight data recorder (FDR) or cockpit voice recorder (CVR), and the report states that neither was required for this aircraft type. The wreckage examination showed that the aircraft hit the ground in a steep nose-down attitude at high speed with little forward momentum. The debris was concentrated around the impact point, with a crater being the only ground scar identified. The aircraft came to rest facing south-east. Investigators found that the ailerons could not be moved and were both in the down position, while the elevator and rudder moved freely. The landing gear had broken and collapsed rearwards. Both wings suffered severe leading-edge damage and accordion-like deformation that ruptured the fuel tanks. The damage was consistent with heavy compressive loading during the steep, rapid-impact sequence. The top engine cowling had separated from the aircraft and was found approximately 10 metres ahead of the main wreckage. The engine cradle was deformed and the engine was facing slightly to the right. The propeller showed asymmetric damage, with one blade bent rearwards and the other showing little or no deformation. Neither blade displayed S-curve bending. The AIID said the damage pattern was consistent with the propeller being non-rotating at impact. This evidence, together with eyewitness accounts of the pilot apparently attempting to restart the engine, led investigators to conclude that the engine was not producing power at the time of impact. However, the preliminary report does not yet establish the underlying reason for the loss of engine power. The instrument panel was broken into multiple pieces, with several indicators dislodged from their original positions. The report does not provide a final interpretation of the instrument evidence at this stage. There was no evidence of a pre- or post-impact fire. Investigators considered the accident not survivable because of the extent of cockpit damage. Emergency responders reported that the pilot-in-command was not wearing his seat belt and was consequently thrown from the aircraft. Medical and pathological information is reserved for the final report. The aircraft was operating in the Johannesburg GFA within FAD 182, outside the Terminal Control Area. FAD 182 extends from the ground to Flight Level 100, or 10,000 feet, except where it intersects the TMA. Bird Aviation also used the Safely Track Me application to monitor flights. The system relied on the pilot's mobile-phone GPS signal. Tracking was active when ZS-ESZ departed Lanseria, but shortly after the aircraft exited the Johannesburg Special Rules Area West TMA, the phone stopped transmitting its GPS position and the aircraft could no longer be tracked through the application. The AIID's preliminary findings confirm that the pilot was qualified and medically fit for the flight, the aircraft was being used under a valid hire-and-fly arrangement for hour-building, the operator/ATO held a valid certificate, the aircraft had valid registration and airworthiness documentation, and its maintenance records were up to date. The investigation therefore establishes several key facts but has not yet determined the precise cause of the accident. The aircraft left Lanseria with full fuel and no known technical issues; the engine was not producing power at impact; weather was not a factor; and the aircraft entered a steep, high-speed descent before striking the ground. The AIID is continuing to examine other aspects of the accident that could have safety implications. No safety recommendations have been issued at this stage. The AIID said these will be addressed in the final report. The investigation was classified as a Category 1 accident. The AIID appointed an investigator-in-charge and a co-investigator, dispatched investigators to the site and notified the relevant states and organisations under South African regulations and ICAO Annex 13. The AIID will lead the investigation and issue the final report. The AIID has warned that the preliminary report is based on evidence gathered during an ongoing investigation and that information may change if additional evidence emerges. Accordingly, the current finding should be described as the engine not producing power at impact, rather than stating that investigators have already determined the cause of the engine power loss.

SACAA Preliminary Findings Show No Engine Power At Impact In Fatal South Africa Crash

August 15, 2026

Do you have the Pilot in you?

Explore More

Webinar

Industry Expert’s Voice

Indian Aviation Statistics

Submit Aviation Blog

Editor's Pick

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

Incidents

Posted onAugust 17, 2026August 17, 2026

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

Incidents

Posted onAugust 17, 2026August 17, 2026

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

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

Aircraft Crashes

Posted onAugust 17, 2026August 17, 2026

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

India Targets Electric Air Taxis By 2028 As Sarla Advances eVTOL Testing In Bengaluru

eVTOL

Posted onAugust 16, 2026August 16, 2026

India Targets Electric Air Taxis By 2028 As Sarla Advances eVTOL Testing In Bengaluru

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

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

August 17, 2026

Phoenix, United States: A potential mid-air collision was averted near Phoenix Sky Harbor International Airport on August 14, 2026, after

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

August 17, 2026

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

August 17, 2026

Bengaluru, India: India is targeting the introduction of electric air taxis by 2028, with Union Civil Aviation Minister Ram Mohan Naidu saying testing of electric vertical take-off and landing (eVTOL) aircraft is expected to accelerate from 2027. The latest development comes as Bengaluru-based Sarla Aviation has secured Design Organisation Approval (DOA) from the Directorate General of Civil Aviation (DGCA), a key regulatory step toward type certification of its indigenous eVTOL aircraft. The approval was handed over to Sarla Aviation at the inauguration of its new Bengaluru headquarters on August 8, 2026. Naidu said India wants to see the aircraft operating by 2028. “By 2028, we want to see these machines fly in India. There is a huge requirement, not only in Bangalore, but Mumbai and Delhi,” he said. He added, “I expect that next year we'll be completely in the testing phase,” while reiterating, “By 2028, we plan to make this happen.” Sarla Aviation has also moved beyond the early prototype stage. On July 1, 2026, the company announced that its half-scale Sylla 1.0 eVTOL technology demonstrator had completed more than 500 tests and over 18 hours of flight testing during a six-month campaign. The 700-kg-class aircraft has a 7.5-metre wingspan and, according to Sarla, became the heaviest electric aircraft to take off in India. The programme tested the aircraft's electric propulsion, battery architecture, distributed propulsion, flight controls, airframe and landing gear as an integrated system. Sarla Aviation CTO and co-founder Rakesh Gaonkar said the Sylla programme had produced the data needed to guide the next stage of development. “Sylla has given us the data we set out to capture, and those learnings are already shaping our next-gen aircraft as we move towards transition and sustained wing-borne flight on our journey to our 6+1 air taxi Shunya,” he said. The next step is Sylla 2.0, which is intended to demonstrate controlled transition from hover to sustained wing-borne flight. That is an important stage before the company moves toward a certifiable passenger-carrying eVTOL. Sarla's planned production aircraft is the six-passenger-plus-pilot Shunya. The developments provide an important update to the electric-air-taxi plan outlined by ET Now. The publication reported that India had set a 2028 target for eVTOL aircraft, with Naidu saying testing would gather pace the following year. The report highlighted Bengaluru, Mumbai and Delhi as cities where demand for such aircraft could be particularly significant because of severe road congestion and lengthy airport-city journeys. An eVTOL is an electrically powered aircraft capable of vertical take-off and landing. Unlike conventional fixed-wing aircraft, it does not require a conventional runway and can potentially operate from smaller facilities closer to urban centres. The technology combines characteristics associated with helicopters, drones and conventional aircraft and is being developed under the broader advanced-air-mobility sector. Sarla Aviation's Shunya is designed around seven electric motors. Six motors provide vertical lift, while a seventh motor mounted at the rear provides forward propulsion. Sarla Aviation co-founder and CEO Adrian Schmidt explained the configuration to ANI: “It's powered by six electric motors that lift it up and one in the rear that pushes it forward. So we have a total of seven electric motors that we're using and it's piloted as of now with six passengers.” The company has said the aircraft's propulsion remains electrically driven. However, Schmidt explained that the design leaves room for a turbo-generator that could potentially recharge the batteries during flight. “We have enough space allocation so that we can consider putting in a turbo generator to charge our batteries mid-flight. But the energy transition from the battery to the motors is always going to be purely electric,” he said. Sarla first unveiled the Shunya prototype at the Bharat Mobility Global Expo in New Delhi in January 2025. The aircraft was presented as a six-passenger eVTOL with a maximum payload of about 680 kg and a targeted top speed of up to 250 km/h. The company said it was designed primarily for short urban journeys of roughly 20–30 km, while reported specifications indicated a potential range of up to 160 km with available battery technology. Sarla's roadmap has also included infrastructure and manufacturing. In November 2025, the company signed an MoU with the Andhra Pradesh government for a 500-acre aerospace campus in Anantapur, with an initial investment of ₹1,300 crore. Sarla described the project as an integrated Urban Air Mobility facility for eVTOL manufacturing and related activities. The company has said the facility is intended to support future aircraft production and air-taxi operations. The company's airport strategy also began taking shape earlier. Sarla Aviation and Bengaluru International Airport Limited signed a partnership agreement in January 2024 to explore an eVTOL ecosystem at Bengaluru airport, including connectivity between the airport and urban areas, vertiport infrastructure and an advanced traffic-management system for future eVTOL operations. Healthcare is another potential application. Bengaluru airport had an agreement with Sarla Aviation for last-mile connectivity and that Manipal Hospitals had also entered an agreement with the company for potential air-ambulance operations. More recent industry reporting indicates that hospitals and air-ambulance operators are increasingly exploring eVTOL partnerships as India develops its advanced-air-mobility ecosystem. The possible uses therefore extend beyond passenger air taxis. The technology could support airport-to-city transfers, last-mile connectivity, air ambulance operations, medical evacuation and cargo transportation. For India, airport connectivity is expected to be one of the earliest practical applications because road journeys between major airports and city centres can take considerable time. Naidu has said an airport-to-city journey that currently takes as long as two hours could potentially be reduced to around 20–30 minutes using eVTOL aircraft. The initial model is therefore expected to focus on short-distance and airport-linked journeys rather than replacing conventional public transportation. The Indian eVTOL market is not limited to Sarla Aviation. Chennai-based The ePlane Company is developing its e200X electric aircraft, while Hyderabad-based BluJ Aerospace is working on eVTOL technology for cargo and other applications. India is therefore developing multiple domestic approaches to advanced air mobility rather than relying solely on one manufacturer. There is also an international dimension to India's air-taxi plans. In 2023, InterGlobe Enterprises, the parent company of IndiGo, announced a partnership with US-based Archer Aviation to explore an all-electric air-taxi service in India, with an original 2026 target. However, that timeline has not materialised as initially envisaged. In 2026, IndiGo Ventures separately invested about ₹10 crore in Sarla Aviation, giving the Indian startup additional strategic backing. Importantly, the IndiGo investment should not be presented as confirmation that IndiGo itself will operate Sarla's eVTOL air-taxi service. Recent reporting said Sarla Aviation clarified that IndiGo's investment did not mean the airline was directly involved in its eVTOL operating plans. The regulatory process remains one of the biggest hurdles. Before commercial passenger operations can begin, eVTOL aircraft must demonstrate compliance with safety and airworthiness requirements and obtain the necessary certification. The DGCA will have to address aircraft design, flight operations, pilot qualifications, infrastructure, vertiports and integration with existing air-traffic systems. Infrastructure is another challenge. Commercial operations will require suitable landing and take-off locations, charging or energy infrastructure, maintenance facilities and systems for managing eVTOL traffic around densely populated areas. Battery performance, aircraft range, weather, operating economics and air-traffic management will also influence whether the 2028 target can be achieved at scale. Sarla's progress in 2026 nevertheless represents a significant shift from the concept and prototype phase. With the Sylla demonstrator having completed an extensive flight-test campaign and the company now holding DGCA Design Organisation Approval, its Shunya programme has entered a more advanced development and certification phase. The government's 2028 target will now depend on the pace of testing, transition-flight development, type certification, infrastructure creation and operational approvals over the next two years.

India Targets Electric Air Taxis By 2028 As Sarla Advances eVTOL Testing In Bengaluru

August 16, 2026

Fochville, South Africa: The preliminary accident report, released on 28 July 2026 by the Accident and Incident Investigations Division (AIID) of the South African Civil Aviation Authority (SACAA), found that the engine of a Bird Aviation Piper PA-28-180 registered ZS-ESZ was not producing power when the aircraft struck the ground near Fochville, Gauteng, on 27 June 2026. The report remains preliminary, with the investigation still ongoing and the AIID cautioning that its findings do not apportion blame or liability. According to the report, the operator was Bird Aviation, while the aircraft was being used under a hire-and-fly arrangement for hour-building. The operation was classified as Training under Part 91, and the aircraft belonged to the approved training organisation (ATO) from which it was hired. The accident involved two people, a 21-year-old Indian pilot and one passenger. Both were fatally injured and the aircraft was destroyed. The pilot held a valid Private Pilot Licence (PPL) and was building flight hours toward a Commercial Pilot Licence (CPL) through the ATO. The flight took place on the afternoon of 27 June 2026, when the pilot and passenger departed Lanseria International Airport (FALA) in Gauteng on an hour-building flight, intending to return to the same airport. The flight was conducted under visual meteorological conditions (VMC) and in accordance with Part 91 of the Civil Aviation Regulations. The flight had initially been planned for 0900Z, but departure was delayed because of persistent haze and low visibility. After conditions improved, the aircraft departed Runway 07 at 1325Z, as confirmed by an air traffic control officer at Lanseria. It then flew toward the Johannesburg General Flying Area (GFA), Flight Area Dangerous 182 (FAD 182). Multiple eyewitnesses later reported seeing the aircraft flying unusually low and performing unfamiliar manoeuvres. The aircraft subsequently flipped and began spinning to the left before impacting the ground. The crash occurred on a farm at Elandsfontein, south-east of Fochville, Gauteng, at coordinates 26° 35' 27.30" South, 27° 33' 41.24" East, with a field elevation of 5,124 feet. The accident was recorded at 1415Z. The pilot was a 21-year-old Indian national with a valid PPL. His licence was initially issued by the regulator on 25 May 2026 and was valid until 30 April 2027. His Class 2 aviation medical certificate was issued on 26 March 2025 and was valid until 31 March 2030. The report states that the aircraft type was endorsed on his licence and that he had no previous accidents recorded in relation to the investigation. The pilot had accumulated 132.2 total flight hours, including 19.4 hours in the previous seven days and 55.1 hours in the previous 90 days. He had flown 43.8 hours on the aircraft during the previous 90 days and had accumulated 122.7 hours on the Piper PA-28-180. The aircraft was a 1977-built Piper PA-28-180, a four-seat, single-engine, all-metal, low-wing aircraft with fixed tricycle landing gear. It was powered by a four-cylinder, naturally aspirated 180-horsepower Lycoming O-360-series engine. Its serial number was 28-3303, and it had accumulated 3,242.6 airframe hours by the time of the accident. The AIID found that the aircraft had valid registration and airworthiness documentation. Its current Certificate of Registration had been issued on 19 September 2025, while its latest Certificate of Airworthiness was valid until 31 October 2026. The aircraft underwent its mandatory periodic inspection on 13 March 2026 at 3,218.4 airframe hours, after which a Certificate of Release to Service was issued, valid until 12 March 2027 or 3,318.4 total airframe hours, whichever came first. The aircraft was maintained by an approved aircraft maintenance organisation whose certificate was valid until 30 June 2026. The organisation held Category A and Category C ratings for the aircraft's airframe and engine. The ATO's certificate had been renewed on 17 November 2025 and was valid until 28 February 2029. Fuel records showed that 111 litres of Avgas 100LL had been uplifted after the aircraft's flight on 26 June 2026, with the pilot refuelling the tanks before parking the aircraft. The Piper PA-28-180 has a fuel capacity of 189 litres, providing approximately six hours of endurance. The preliminary findings state that the aircraft departed Lanseria with full fuel tanks and no technical issues. However, fuel was found leaking from the aircraft after the accident. The report does not currently identify the fuel leak as the cause of the engine power loss. Weather conditions were favourable and were not considered a contributing factor. The 1400Z METAR from Lanseria recorded winds from 300° at 7 knots, CAVOK visibility, a temperature of 16°C, scattered clouds at 4,500 feet, a dew point of 5°C and QNH of 1026 hPa. The aircraft's navigation and communication equipment had no recorded defects before the flight. It was not equipped with a flight data recorder (FDR) or cockpit voice recorder (CVR), and the report states that neither was required for this aircraft type. The wreckage examination showed that the aircraft hit the ground in a steep nose-down attitude at high speed with little forward momentum. The debris was concentrated around the impact point, with a crater being the only ground scar identified. The aircraft came to rest facing south-east. Investigators found that the ailerons could not be moved and were both in the down position, while the elevator and rudder moved freely. The landing gear had broken and collapsed rearwards. Both wings suffered severe leading-edge damage and accordion-like deformation that ruptured the fuel tanks. The damage was consistent with heavy compressive loading during the steep, rapid-impact sequence. The top engine cowling had separated from the aircraft and was found approximately 10 metres ahead of the main wreckage. The engine cradle was deformed and the engine was facing slightly to the right. The propeller showed asymmetric damage, with one blade bent rearwards and the other showing little or no deformation. Neither blade displayed S-curve bending. The AIID said the damage pattern was consistent with the propeller being non-rotating at impact. This evidence, together with eyewitness accounts of the pilot apparently attempting to restart the engine, led investigators to conclude that the engine was not producing power at the time of impact. However, the preliminary report does not yet establish the underlying reason for the loss of engine power. The instrument panel was broken into multiple pieces, with several indicators dislodged from their original positions. The report does not provide a final interpretation of the instrument evidence at this stage. There was no evidence of a pre- or post-impact fire. Investigators considered the accident not survivable because of the extent of cockpit damage. Emergency responders reported that the pilot-in-command was not wearing his seat belt and was consequently thrown from the aircraft. Medical and pathological information is reserved for the final report. The aircraft was operating in the Johannesburg GFA within FAD 182, outside the Terminal Control Area. FAD 182 extends from the ground to Flight Level 100, or 10,000 feet, except where it intersects the TMA. Bird Aviation also used the Safely Track Me application to monitor flights. The system relied on the pilot's mobile-phone GPS signal. Tracking was active when ZS-ESZ departed Lanseria, but shortly after the aircraft exited the Johannesburg Special Rules Area West TMA, the phone stopped transmitting its GPS position and the aircraft could no longer be tracked through the application. The AIID's preliminary findings confirm that the pilot was qualified and medically fit for the flight, the aircraft was being used under a valid hire-and-fly arrangement for hour-building, the operator/ATO held a valid certificate, the aircraft had valid registration and airworthiness documentation, and its maintenance records were up to date. The investigation therefore establishes several key facts but has not yet determined the precise cause of the accident. The aircraft left Lanseria with full fuel and no known technical issues; the engine was not producing power at impact; weather was not a factor; and the aircraft entered a steep, high-speed descent before striking the ground. The AIID is continuing to examine other aspects of the accident that could have safety implications. No safety recommendations have been issued at this stage. The AIID said these will be addressed in the final report. The investigation was classified as a Category 1 accident. The AIID appointed an investigator-in-charge and a co-investigator, dispatched investigators to the site and notified the relevant states and organisations under South African regulations and ICAO Annex 13. The AIID will lead the investigation and issue the final report. The AIID has warned that the preliminary report is based on evidence gathered during an ongoing investigation and that information may change if additional evidence emerges. Accordingly, the current finding should be described as the engine not producing power at impact, rather than stating that investigators have already determined the cause of the engine power loss.

SACAA Preliminary Findings Show No Engine Power At Impact In Fatal South Africa Crash

August 15, 2026

More News

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

August 17, 2026

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

August 17, 2026

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

August 17, 2026

Bengaluru, India: India is targeting the introduction of electric air taxis by 2028, with Union Civil Aviation Minister Ram Mohan Naidu saying testing of electric vertical take-off and landing (eVTOL) aircraft is expected to accelerate from 2027. The latest development comes as Bengaluru-based Sarla Aviation has secured Design Organisation Approval (DOA) from the Directorate General of Civil Aviation (DGCA), a key regulatory step toward type certification of its indigenous eVTOL aircraft. The approval was handed over to Sarla Aviation at the inauguration of its new Bengaluru headquarters on August 8, 2026. Naidu said India wants to see the aircraft operating by 2028. “By 2028, we want to see these machines fly in India. There is a huge requirement, not only in Bangalore, but Mumbai and Delhi,” he said. He added, “I expect that next year we'll be completely in the testing phase,” while reiterating, “By 2028, we plan to make this happen.” Sarla Aviation has also moved beyond the early prototype stage. On July 1, 2026, the company announced that its half-scale Sylla 1.0 eVTOL technology demonstrator had completed more than 500 tests and over 18 hours of flight testing during a six-month campaign. The 700-kg-class aircraft has a 7.5-metre wingspan and, according to Sarla, became the heaviest electric aircraft to take off in India. The programme tested the aircraft's electric propulsion, battery architecture, distributed propulsion, flight controls, airframe and landing gear as an integrated system. Sarla Aviation CTO and co-founder Rakesh Gaonkar said the Sylla programme had produced the data needed to guide the next stage of development. “Sylla has given us the data we set out to capture, and those learnings are already shaping our next-gen aircraft as we move towards transition and sustained wing-borne flight on our journey to our 6+1 air taxi Shunya,” he said. The next step is Sylla 2.0, which is intended to demonstrate controlled transition from hover to sustained wing-borne flight. That is an important stage before the company moves toward a certifiable passenger-carrying eVTOL. Sarla's planned production aircraft is the six-passenger-plus-pilot Shunya. The developments provide an important update to the electric-air-taxi plan outlined by ET Now. The publication reported that India had set a 2028 target for eVTOL aircraft, with Naidu saying testing would gather pace the following year. The report highlighted Bengaluru, Mumbai and Delhi as cities where demand for such aircraft could be particularly significant because of severe road congestion and lengthy airport-city journeys. An eVTOL is an electrically powered aircraft capable of vertical take-off and landing. Unlike conventional fixed-wing aircraft, it does not require a conventional runway and can potentially operate from smaller facilities closer to urban centres. The technology combines characteristics associated with helicopters, drones and conventional aircraft and is being developed under the broader advanced-air-mobility sector. Sarla Aviation's Shunya is designed around seven electric motors. Six motors provide vertical lift, while a seventh motor mounted at the rear provides forward propulsion. Sarla Aviation co-founder and CEO Adrian Schmidt explained the configuration to ANI: “It's powered by six electric motors that lift it up and one in the rear that pushes it forward. So we have a total of seven electric motors that we're using and it's piloted as of now with six passengers.” The company has said the aircraft's propulsion remains electrically driven. However, Schmidt explained that the design leaves room for a turbo-generator that could potentially recharge the batteries during flight. “We have enough space allocation so that we can consider putting in a turbo generator to charge our batteries mid-flight. But the energy transition from the battery to the motors is always going to be purely electric,” he said. Sarla first unveiled the Shunya prototype at the Bharat Mobility Global Expo in New Delhi in January 2025. The aircraft was presented as a six-passenger eVTOL with a maximum payload of about 680 kg and a targeted top speed of up to 250 km/h. The company said it was designed primarily for short urban journeys of roughly 20–30 km, while reported specifications indicated a potential range of up to 160 km with available battery technology. Sarla's roadmap has also included infrastructure and manufacturing. In November 2025, the company signed an MoU with the Andhra Pradesh government for a 500-acre aerospace campus in Anantapur, with an initial investment of ₹1,300 crore. Sarla described the project as an integrated Urban Air Mobility facility for eVTOL manufacturing and related activities. The company has said the facility is intended to support future aircraft production and air-taxi operations. The company's airport strategy also began taking shape earlier. Sarla Aviation and Bengaluru International Airport Limited signed a partnership agreement in January 2024 to explore an eVTOL ecosystem at Bengaluru airport, including connectivity between the airport and urban areas, vertiport infrastructure and an advanced traffic-management system for future eVTOL operations. Healthcare is another potential application. Bengaluru airport had an agreement with Sarla Aviation for last-mile connectivity and that Manipal Hospitals had also entered an agreement with the company for potential air-ambulance operations. More recent industry reporting indicates that hospitals and air-ambulance operators are increasingly exploring eVTOL partnerships as India develops its advanced-air-mobility ecosystem. The possible uses therefore extend beyond passenger air taxis. The technology could support airport-to-city transfers, last-mile connectivity, air ambulance operations, medical evacuation and cargo transportation. For India, airport connectivity is expected to be one of the earliest practical applications because road journeys between major airports and city centres can take considerable time. Naidu has said an airport-to-city journey that currently takes as long as two hours could potentially be reduced to around 20–30 minutes using eVTOL aircraft. The initial model is therefore expected to focus on short-distance and airport-linked journeys rather than replacing conventional public transportation. The Indian eVTOL market is not limited to Sarla Aviation. Chennai-based The ePlane Company is developing its e200X electric aircraft, while Hyderabad-based BluJ Aerospace is working on eVTOL technology for cargo and other applications. India is therefore developing multiple domestic approaches to advanced air mobility rather than relying solely on one manufacturer. There is also an international dimension to India's air-taxi plans. In 2023, InterGlobe Enterprises, the parent company of IndiGo, announced a partnership with US-based Archer Aviation to explore an all-electric air-taxi service in India, with an original 2026 target. However, that timeline has not materialised as initially envisaged. In 2026, IndiGo Ventures separately invested about ₹10 crore in Sarla Aviation, giving the Indian startup additional strategic backing. Importantly, the IndiGo investment should not be presented as confirmation that IndiGo itself will operate Sarla's eVTOL air-taxi service. Recent reporting said Sarla Aviation clarified that IndiGo's investment did not mean the airline was directly involved in its eVTOL operating plans. The regulatory process remains one of the biggest hurdles. Before commercial passenger operations can begin, eVTOL aircraft must demonstrate compliance with safety and airworthiness requirements and obtain the necessary certification. The DGCA will have to address aircraft design, flight operations, pilot qualifications, infrastructure, vertiports and integration with existing air-traffic systems. Infrastructure is another challenge. Commercial operations will require suitable landing and take-off locations, charging or energy infrastructure, maintenance facilities and systems for managing eVTOL traffic around densely populated areas. Battery performance, aircraft range, weather, operating economics and air-traffic management will also influence whether the 2028 target can be achieved at scale. Sarla's progress in 2026 nevertheless represents a significant shift from the concept and prototype phase. With the Sylla demonstrator having completed an extensive flight-test campaign and the company now holding DGCA Design Organisation Approval, its Shunya programme has entered a more advanced development and certification phase. The government's 2028 target will now depend on the pace of testing, transition-flight development, type certification, infrastructure creation and operational approvals over the next two years.

India Targets Electric Air Taxis By 2028 As Sarla Advances eVTOL Testing In Bengaluru

August 16, 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

Notify

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