Latest Aviation News | Updated Global Aviation News

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

Latest News

New Delhi, India: The Airline Pilots' Association of India (ALPA India) has strongly rejected recent remarks by IndiGo Managing Director Rahul Bhatia attributing India's pilot shortage to revised flight duty and fatigue management regulations, asserting instead that deeper structural issues within the aviation industry are constraining the country's pilot workforce. In a statement issued on Tuesday, July 29, 2026, ALPA India said the debate surrounding pilot availability should focus on long-standing industry practices rather than the implementation of revised Flight Duty Time Limitations (FDTL). The pilots' body maintained that India's aviation sector has sufficient interest among aspiring pilots but alleged that barriers within the training and employment ecosystem are restricting the effective supply of qualified flight crew. According to reports by PTI, ALPA India disputed suggestions that enhanced fatigue regulations are responsible for the industry's staffing challenges. Instead, the association argued that three structural issues continue to affect pilot availability: the high cost of cadet training and aircraft type ratings, alleged anti-competitive hiring practices among airlines, and wage-related employment practices that limit pilot mobility. The association urged the Ministry of Civil Aviation (MoCA) and the Competition Commission of India (CCI) to expedite investigations into these issues, stating that addressing structural barriers would provide a more sustainable solution to pilot shortages than revisiting safety-focused flight duty regulations. The remarks came after Rahul Bhatia co-founder of IndiGo and serves as the Managing Director of InterGlobe Aviation Ltd., the parent company of IndiGo expressed concerns over the implementation of revised DGCA Flight Duty Time Limitations, stating that the changes could intensify pilot shortages and increase operational challenges for airlines. His comments reignited discussion across the aviation sector regarding the balance between operational efficiency and flight safety. Bhatia told PTI, "I think Flight Duty Time Limitations (FDTL) needs a review, and I think there's enough conversation going on with the government. All we want to do is appeal to the government that we must follow the global best practices". Responding directly to Rahul Bhatia's recent comments, ALPA India argued that weakening or delaying fatigue management reforms would not resolve the industry's workforce challenges. Instead, it said policy attention should remain focused on ensuring fair market practices while maintaining internationally accepted flight safety standards designed to reduce pilot fatigue. India's revised FDTL regulations were introduced by the Directorate General of Civil Aviation (DGCA) following recommendations aimed at strengthening pilot fatigue management. The rules seek to improve crew rest requirements, regulate night operations and reduce fatigue-related safety risks. While several airlines have expressed operational concerns regarding implementation, pilot associations have consistently maintained that the regulations are essential for maintaining flight safety. ALPA India specifically called for faster progress in investigations into cadet programme pricing and inter-airline hiring practices. The association argued that the financial burden associated with airline cadet programmes and mandatory type-rating training has significantly increased the cost of entering the profession, making commercial pilot careers inaccessible for many aspiring candidates. The pilots' body also alleged that anti-competitive employment practices within the industry have affected labour mobility. It claimed that certain hiring practices discourage experienced pilots from moving between airlines, thereby limiting competition in the labour market and suppressing salary growth. ALPA India said these issues require regulatory scrutiny by the Competition Commission of India. The association further maintained that wage suppression has become another contributing factor behind the industry's pilot supply concerns. According to ALPA India, compensation structures and employment conditions at certain carriers discourage both retention and recruitment despite growing demand for pilots as Indian airlines continue expanding their fleets. ALPA India claimed that airline-backed cadet programmes require aspiring pilots to spend between ₹60 lakh and ₹1.25 crore on training, significantly higher than international type-rating programmes that typically cost around ₹20 lakh. The association further alleged that many cadets are bound by long-term employment agreements despite having no assurance of securing a job. ALPA India reiterated that pilot shortages cannot be attributed solely to duty-time regulations and emphasized that broader structural reforms are necessary. The association said reducing financial barriers for cadet pilots, ensuring competitive hiring practices and addressing employment-related concerns would help strengthen the long-term supply of qualified flight crew in India's rapidly expanding aviation market. Neither the Ministry of Civil Aviation nor the Competition Commission of India had publicly responded to ALPA India's latest appeal at the time of publication. Similarly, no fresh official statement from IndiGo responding specifically to ALPA India's latest remarks had been issued.

Airlines

ALPA Rejects IndiGo’s FDTL Remarks, Cites Structural Issues Behind Pilot Shortage

July 31, 2026

Alaska, United States: The US National Transportation Safety Board (NTSB) has released its final investigation report into the fatal crash of Bering Air Flight 445, concluding that degraded pilot situational awareness, inadequate airspeed management, operation above the aircraft's maximum allowable weight, shortcomings in Bering Air's safety management, and insufficient Federal Aviation Administration (FAA) oversight combined to cause the accident. The report also identified deficiencies in weather forecasting for supercooled large droplet (SLD) icing and issued new and reiterated safety recommendations aimed at improving commuter airline safety. The accident occurred on February 6, 2025, at about 3:20 p.m. Alaska Standard Time when a Textron Aviation Cessna 208B Grand Caravan EX, registration N321BA, operating as Bering Air Flight 445, crashed onto pack ice in Norton Sound while approaching Nome Airport, Alaska. The Part 135 scheduled commuter flight had departed Unalakleet Airport on the final leg of a three-flight rotation carrying one pilot and nine passengers. All ten occupants were killed. According to the NTSB, the pilot and dispatcher reviewed weather conditions before departure, with forecasts indicating instrument flight conditions, light snow and occasional moderate icing. However, no official weather products warned of the severe supercooled large droplet icing conditions the flight would later encounter. Air traffic control advised the pilot that both runways had been temporarily closed for snow and ice removal and suggested slowing the aircraft to avoid arriving before they reopened. The pilot reduced engine power, causing the aircraft's airspeed to decrease. Around the same time, the aircraft entered moderate-to-severe icing conditions containing supercooled large droplets. Flight data showed the aircraft's airspeed continued to fall despite increased engine power. At about 3:19 p.m., the Low Airspeed Awareness (LAA) system activated and automatically disengaged the autopilot after airspeed dropped below approximately 99 knots. Within seconds, the aircraft's speed fell further, its pitch increased, and it entered an aerodynamic stall before rapidly descending. Air traffic control instructed the pilot to climb after observing the aircraft's low altitude and later issued a low-altitude alert, but no response was received. The aircraft impacted pack ice about 12 miles offshore of Norton Sound and approximately 32 miles east of Nome. Because the aircraft was not required to carry a cockpit voice recorder or flight data recorder, investigators reconstructed the accident using Garmin G1000 avionics data, ADS-B tracking, air traffic control communications and examination of the wreckage. The evidence enabled investigators to establish the sequence of events leading to the fatal loss of control, forming the basis of the NTSB's final findings and safety recommendations. In its final report, the NTSB concluded that the aircraft experienced an aerodynamic stall after the pilot failed to maintain adequate airspeed while operating in icing conditions. Investigators found that following the automatic disengagement of the autopilot, the pilot did not effectively monitor the aircraft's rapidly decreasing airspeed or increasing angle of attack, resulting in a loss of control from which recovery was not possible. The investigation determined that the aircraft encountered supercooled large droplet (SLD) icing, a hazardous condition beyond the certification limits of the Cessna 208 B's TKS ice protection system. Although post-accident examinations found no evidence of any pre-impact mechanical failure and confirmed the TKS system functioned as designed, the icing conditions exceeded those for which the aircraft was certificated. The NTSB also identified operational shortcomings at Bering Air. Investigators found the aircraft departed above the maximum allowable gross take-off weight for flight into known or forecast icing conditions. The report stated that the operator had routinely used an increased maximum take-off weight permitted under a supplemental type certificate, even though the aircraft's flight manual prohibited that higher weight in icing conditions. The Board further concluded that Bering Air's safety management system failed to adequately identify and mitigate operational risks, while internal weight-and-balance practices and oversight were insufficient. The investigation also criticised the FAA's oversight of the operator, concluding that inspectors failed to identify or correct Bering Air's use of improper weight limitations during operations in icing conditions. Additionally, the Board found shortcomings in Alaska's aviation weather products, noting that available forecasts did not adequately communicate the potential for supercooled large droplet icing despite meteorological conditions supporting its development. As part of its final report, the NTSB issued multiple safety recommendations to the FAA, National Weather Service and Bering Air. These include strengthening oversight of Part 135 operators, improving compliance with aircraft weight limitations, enhancing pilot training for operations in severe icing, expanding weather products that identify supercooled large droplet icing in Alaska, and improving operational risk management to help prevent similar accidents.

Investigation

NTSB Final Report Cites Pilot Error, Icing And FAA Failures In Fatal Bering Air Crash

July 31, 2026

Atlanta, United States: The U.S. Federal Aviation Administration (FAA) is investigating a serious runway separation incident involving two Delta Air Lines aircraft at Hartsfield-Jackson Atlanta International Airport after the jets came into close proximity during simultaneous arrival and departure operations late on July 27. The incident involved Delta Air Lines Flight DL1568, arriving from Pittsburgh, and Delta Air Lines Flight DL2472, departing for Rochester, New York. According to the FAA and flight-tracking data, Flight 1568 was on final approach when the crew initiated a go-around after the departing aircraft had not cleared the runway environment in time. As the arriving aircraft climbed away from the runway, it came into conflict with the departing Delta jet. Both flight crews received Traffic Collision Avoidance System (TCAS) resolution advisories, prompting immediate evasive action. Air traffic controllers instructed the departing aircraft to turn and continue climbing while the arriving aircraft followed its missed-approach procedure. The crews complied with the alerts and ATC instructions, allowing both aircraft to safely regain separation. According to publicly reported flight data, the aircraft came within approximately 1,800 feet horizontally and 600 feet vertically at their closest point before increasing separation. No injuries were reported, and both flights continued safely after the event. Flight 1568 subsequently entered a holding pattern before landing safely in Atlanta, while Flight 2472 continued its scheduled flight to Rochester. Air traffic control audio reviewed by multiple media outlets captured the urgency of the event. Controllers quickly issued revised instructions after recognizing the developing conflict, while one pilot was heard expressing surprise at how close the aircraft had come. The communications indicate that both the controllers and flight crews acted promptly in response to the TCAS warnings, helping prevent a more serious incident. The FAA confirmed it is investigating the occurrence to determine the sequence of events, including runway occupancy, aircraft spacing and air traffic control actions. As of the latest update, the agency has not released preliminary findings or identified a probable cause. No damage to either aircraft has been reported, and no onboard injuries have been disclosed. The airline's operating crews followed established safety procedures, including compliance with TCAS resolution advisories and ATC instructions, allowing both flights to continue safely.

Incidents

FAA Investigates Close Call Between Two Delta Air Lines Aircraft At Atlanta Airport

July 30, 2026

around 180 passengers came dangerously close to a serious accident while approaching London Heathrow Airport earlier this month, after a reported air data system failure led to a loss of airspeed information during the aircraft's final descent. The incident, which occurred on July 6 aboard Flight BA919 from Düsseldorf, Germany, is now under investigation by the UK's Air Accidents Investigation Branch (AAIB). The aircraft was descending over east London at approximately 4,000 feet near Canary Wharf when one of its air data systems reportedly malfunctioned. Air data systems provide pilots with critical flight information including airspeed, altitude and other performance parameters essential for safely controlling the aircraft, particularly during the approach and landing phases. According to reports first published by The Sun, the loss of air data reportedly resulted in the Airbus A320 entering an aerodynamic stall, a condition in which the wings no longer generate sufficient lift because the aircraft's angle of attack becomes excessive. Unlike an engine failure, a stall does not mean the engines stop operating; instead, the aircraft risks losing altitude rapidly unless immediate corrective action is taken. Reports said the first officer initially attempted to recover the aircraft before the captain intervened directly in the cockpit to regain control. A source described the recovery as particularly challenging because it occurred at low altitude during the final approach, stating that such physical intervention by a captain is highly unusual. Several reports described the event as one of the most serious aviation near misses in the United Kingdom in recent years. According to reports, the occurrence has been recorded as a "loss of control in-flight" and described as "pilot induced." However, the AAIB has not released any preliminary findings, and the cause of the incident, including the sequence of events leading to the reported loss of control, remains under investigation. It is therefore too early to determine whether crew actions, equipment failure, or a combination of factors contributed to the event. In a statement, British Airways confirmed that it is cooperating with the AAIB's investigation into the serious incident. The UK's Civil Aviation Authority (CAA), in line with its standard practice, has declined to comment while the investigation remains ongoing. The AAIB's investigation into Flight BA919 is expected to examine aircraft systems, recorded flight data, cockpit voice recordings, maintenance history, crew actions and operational procedures before determining the cause of the incident and issuing any safety recommendations.

Incidents

British Airways A320 Investigated Following Reported Loss Of Airspeed Near Heathrow

July 30, 2026

crashed while attempting to land at the Dan Creek airstrip near McCarthy, Alaska, with federal investigators probing the fatal accident. According to the Alaska State Troopers, the crash was reported at approximately 9:30 p.m. on July 27, 2026, after a personal aircraft went down at the Dan Creek airstrip, located roughly 15 to 20 miles east of the remote community of McCarthy in the Wrangell-St. Elias Mountains. Responders reached the site aboard a state aircraft early the following morning and discovered the wreckage shortly after 6 a.m. on July 28, confirming that all three occupants had died. An initial report from the Federal Aviation Administration (FAA) identified the aircraft as a Piper PA-22-150, a four-seat, single-engine airplane operating as a personal flight. According to the FAA, the aircraft banked left while landing, impacted terrain and caught fire, resulting in a post-crash fire that destroyed the aircraft and killed the pilot and two passengers. The remains of the three occupants were recovered from the wreckage and transported to the Alaska State Medical Examiner's Office for autopsy and formal identification, Alaska State Troopers said. Family members have identified local pilot Jason Lobo and 23-year-old Anadyr Elliott as two of the three people killed in the accident. The identity of the third occupant had not been officially confirmed at the time of reporting. The National Transportation Safety Board (NTSB) has opened an investigation into the accident after being notified by Alaska State Troopers. The agency is expected to determine the circumstances and probable cause of the crash. The accident remains under investigation, and authorities have not released any additional information regarding factors that may have contributed to the crash.

Aircraft Crashes

Three Killed After Piper PA-22 Crashes During Landing Attempt At Alaska Airstrip

July 30, 2026

San Juan Province, Argentina: All seven people aboard a Bell 412 helicopter were killed after the aircraft crashed in Argentina's San Juan Province on July 29 while en route to support wildfire suppression operations in the neighboring province of La Rioja, authorities confirmed. The helicopter, operated under contract to Argentina's Federal Emergency Agency (AFE), went down during the morning near Ischigualasto Provincial Park, around 1,100 kilometers northwest of Buenos Aires. Officials said the aircraft had been conducting training activities in San Juan before departing to assist firefighters battling a forest fire in La Rioja. According to the AFE, the helicopter's last recorded communication was received at 10:26 a.m. local time. After contact was lost, another aircraft operating in the area located the crash site and alerted authorities, triggering the emergency response. There were seven people on board, and all were killed. No survivors were reported, and authorities did not report any injuries on the ground. Those killed included Carlos Heredia, Director of Civil Protection in San Juan; Germán Videla, Deputy Chief of the San Juan Provincial Police; Rubén Castro and Jorge Carbajal, both senior officers with the provincial Fire Department; pilot Matías Valenzuela; and AFE firefighters Andrés Bosch and Rodrigo Aimetta, who were deployed from other jurisdictions. San Juan Governor Marcelo Orrego confirmed the fatalities in a statement posted on social media, "It is with deep sorrow that we received the news of the helicopter accident that occurred in our province, in which seven people sadly lost their lives." The governor also extended condolences to the victims' families."I want to express my deepest condolences to the families of all the victims at this time of immense grief. We stand with each and every one of their loved ones." In an official statement, the Federal Emergency Agency said the Bell 412 had been assigned to support emergency operations after completing training activities in San Juan. "The causes of the accident are under investigation." AFE added that it remains in contact with the relevant authorities and will release additional official information as it becomes available. Following the tragedy, Governor Orrego declared three days of official mourning across San Juan Province. State celebrations were suspended, and flags at government buildings were ordered to be flown at half-mast in memory of the victims. The cause of the crash has not yet been determined, and the investigation is ongoing

Aircraft Crashes

Seven Killed After Bell 412 Helicopter Crashes En Route To Argentina Wildfire Mission

July 30, 2026

New Delhi, India: The investigation into the crash of Air India flight AI-171 has entered its final stages, with the government telling Parliament that an advanced examination of the aircraft’s fuel control switch and its locking mechanism found no abnormality. However, the inspection of the complete thrust control module remains underway at the original equipment manufacturer's facility in Seattle. Minister of State for Civil Aviation Murlidhar Mohol provided the update during the Monsoon Session of Parliament on Wednesday, July 29, 2026, in response to questions in the Rajya Sabha. According to the Ministry of Civil Aviation's response, the tests were ordered by the Directorate General of Civil Aviation (DGCA) as part of continuing airworthiness checks after the Boeing 787 aircraft type was grounded in February this year. "A detailed examination of the fuel control switch, including the structural integrity of its locking detents, found no abnormality," Mohol said. The government further stated: "Inspection of the complete Thrust Control Module at the OEM's facility is underway." The finding is significant because the movement of the two engine fuel control switches has been a central focus of the investigation into the June 12, 2025 crash, which happened shortly after takeoff from Ahmedabad. The aircraft came down in the Meghani Nagar area, killing 260 people, including 241 of the 242 people aboard the aircraft and 19 people on the ground. One passenger survived the crash. The preliminary investigation found that both switches moved from the RUN position to CUT OFF shortly after takeoff, resulting in the loss of thrust from both engines. The preliminary report, however, did not establish why the switches moved or assign responsibility for the movement. The latest examination has so far found no abnormality in the locking mechanism of the fuel control switch. However, the government has not said that the investigation has established the cause of the switches moving to the CUTOFF position. The complete thrust control module is still being examined, and the outcome of that inspection remains awaited. The government also rejected suggestions that the Aircraft Accident Investigation Bureau (AAIB) has delayed the final report into the crash. Mohol said investigations into major air accidents do not follow a fixed timeline and that the AI-171 inquiry is progressing in accordance with established investigation procedures. "All probable causes and contributing factors leading to the accident are being investigated," the minister said. The Ministry of Civil Aviation said the final investigation report will contain the findings of the probe and will be made public and uploaded on the AAIB's website once the investigation is completed. The preliminary report also noted that the aircraft had been certified as airworthy before the flight and that its maintenance records did not show a reported defect involving the fuel control switches. It also recorded that the aircraft's throttle control module had previously been replaced, although the replacements were unrelated to reported fuel-switch defects. The investigation subsequently drew international attention because the fuel control switches are part of the Boeing 787's thrust control system and are designed with locking mechanisms intended to prevent unintended movement. The latest government statement indicates that the structural integrity of the locking detents has now been examined and that no abnormality was identified in that specific component. However, the government has not yet released a final conclusion on what caused the switches to move during the AI-171 flight. The continuing inspection of the complete thrust control module is therefore an important remaining part of the technical examination. The AAIB's final report is expected to establish the complete sequence of events, identify the causes and contributing factors, and determine whether any safety recommendations are required. Until the final report is released, the precise cause of the fuel control switches moving to CUTOFF remains unresolved in the publicly available investigation findings. The latest government update therefore clears one specific area of concern: the fuel control switch locking mechanism but does not, by itself, close the wider question of why both switches moved to the CUTOFF position shortly after takeoff. The investigation remains ongoing, with the complete thrust control module examination and the AAIB's final assessment is still pending.

Airlines

Govt Says Air India AI171 Crash Probe Finds No Fault In Fuel Switch Locking Mechanism

July 29, 2026

DAE Completes $9B Macquarie AirFinance Deal, Becomes World's 3rd-Largest Aircraft Lessor

United Arab Emirates

DAE Completes $9B Macquarie AirFinance Deal, Becomes World’s 3rd-Largest Aircraft Lessor

July 29, 2026

Airbus Completes Longest-Ever A350-1000 ULR Development Flight Ahead Of Project Sunrise SEO DES: Airbus' A350-1000 ULR test aircraft completed a record 24-hour, 24-minute nonstop development flight covering 12,460 nautical miles from Melbourne to Toulouse SOCIAL: Airbus’ A350-1000 ULR test aircraft MSN707 completed a record 24-hour-24-minute nonstop development flight from Melbourne, Australia, to Toulouse, France, covering 12,460 nautical miles. The flight was part of Airbus’ two-part development programme supporting Qantas’ Project Sunrise ultra-long-haul operations. The test evaluated the aircraft’s fuel-management systems, rear centre tank, cabin comfort, air-conditioning and new twin Flight Crew Rest Compartment. Pilots also followed specialised fatigue-management procedures, while Qantas pilots gained experience flying the A350-1000 ULR variant. The flight involved Airbus and Qantas pilots and flight-test engineers, with the aircraft following a route across the Pacific, North America and the Atlantic. The mission is expected to help validate the A350-1000 ULR for future nonstop commercial services connecting Australia with Europe and North America. Toulouse, France: Airbus has completed the longest flight ever flown by its A350-1000 ULR flight-test aircraft MSN707, with the specially instrumented MSN707 flying nonstop from Melbourne, Australia, to Toulouse, France, for 24 hours and 24 minutes. The aircraft covered 12,460 nautical miles (23,075 km or 14,338 miles) before landing in Toulouse on the morning of July 28, 2026. The flight was part of a two-part development flight-test programme. On July 23, MSN707 departed Toulouse on its longest point-to-point flight to Melbourne. A few days later, the aircraft began its return journey to Toulouse, carrying two Qantas guest pilots alongside the Airbus test crew. Airbus said the return flight was technically classified as a development test rather than a certification flight. The programme is designed to demonstrate the A350-1000ULR's ability to complete a 23-hour block-time mission. Block time runs from the release of the parking brake at departure until the aircraft reaches its arrival stand and is intended to provide sufficient operational margin around the planned 21-hour-40-minute flight time for Qantas' forthcoming Project Sunrise routes, including time for holding, diversion and taxiing. The aircraft is powered by two Rolls-Royce Trent XWB-97 engines and features an additional rear centre tank (RCT) with a 20,900-litre fuel capacity. The tank is designed to support ultra-long-range operations covering almost 10,000 nautical miles. During the flight, Airbus used the fully fueled RCT to validate remaining test points and assess fuel-management systems, while also evaluating cabin comfort and air-conditioning performance. Airbus Test Pilot Xavier Pepin, who served as captain on the record-setting return leg, said the first, approximately 20-hour leg was used to stabilise various cabin air-temperature settings for accurate measurements. The return flight then allowed the team to address backup test points that could not be completed during the first leg. The flight also evaluated the A350-1000ULR's new twin Flight Crew Rest Compartment. The specially designed facility has two separate sections with individual entrances, allowing pilots to access their respective rest areas without disturbing one another during airline operations. However, because the compartments were occupied by ventilation-measurement equipment during the test, the crew instead used the aircraft's eight-berth rear cabin-crew rest compartment for sleeping. The return flight from Melbourne followed a route across the Pacific toward Los Angeles, over the United States and Canada, and across the Atlantic south of Greenland before passing over the UK and continuing to southern France. Airbus selected a more northerly Atlantic routing to avoid potential air-traffic-control issues that could arise if published airline tracks were not updated before departure, potentially resulting in mismatched flight plans. Fatigue management was another key element of the ultra-long-range test. Airbus said pilots worked four-hour shifts but rotated every two hours, creating a two-hour overlap between the incoming and outgoing pilots. The arrangement was intended to support detailed handovers and maintain situational awareness throughout the 20- to 23-hour missions. On the return flight, at least one Airbus test pilot remained in a pilot seat whenever a Qantas pilot occupied the other seat, as Airbus retained operational responsibility for the mission. The schedule also allowed the Qantas pilots to take the controls at designated times. Both were already qualified on the A350 but were experiencing the A350-1000 ULR variant for the first time. The return flight was commanded by Airbus Test Pilot Xavier Pepin. Two Qantas pilots, Captain Andrew Coull and Captain David Summergreene, joined the mission, while one Airbus pilot from the outbound crew disembarked. Five pilots were therefore aboard for the return leg: three Airbus pilots and the two Qantas pilots. The two Test-Flight Engineers, Laurent Rossignol and Nicolas Granier, and three Flight-Test Engineers, Tuan Do, Alexia Plummet and Jaime Angoloti, remained on board for the return flight. The outbound leg had been led by Airbus Test Pilot Vincent Sibelle, who served as captain and was responsible for the overall mission organisation. The other Airbus pilots were Xavier Pepin, Josef Bayoud and Chetan Takalkar. The two Test-Flight Engineers monitored aircraft systems from the cockpit, while the three Flight-Test Engineers worked from stations in the main cabin, coordinating tests including cabin-comfort and fuel monitoring. The MSN707 test aircraft first flew on June 2, 2026, and is equipped with specialised instrumentation for the development programme. The latest flight is intended to help validate the aircraft's capabilities and systems ahead of its planned use for Qantas' Project Sunrise ultra-long-haul operations. The flight also attracted significant public attention. Reuters reported that more than 3.6 million people tracked the aircraft online, making it the second-most-followed flight ever on Flightradar24. The test demonstrated the potential of the A350-1000 ULR to support nonstop commercial services linking Australia's east coast with destinations in Europe and North America. The Melbourne-Toulouse development flight marks a major milestone in the testing of an aircraft designed to make some of the world's longest commercial passenger flights possible. Airbus' latest test programme is focused not only on endurance and fuel management but also on cabin conditions, crew-rest arrangements and operational procedures required for missions lasting more than 20 hours.

Airbus

Airbus Completes Longest-Ever A350-1000 ULR Development Flight Ahead Of Project Sunrise

July 29, 2026

Incidents

American Eagle Flight 5816 Diverts To Norfolk After Reported Smoke In Cabin

July 29, 2026

Washington, United States: The U.S. Federal Aviation Administration (FAA) on July 27, 2026, proposed inspections of passenger seat assemblies on 453 U.S.-registered Boeing 737 MAX aircraft after receiving a report that some seats may not have been correctly installed in their floor tracks. The proposed Airworthiness Directive (AD) applies to certain Boeing 737-8, 737-9 and 737-8200 aircraft. According to the FAA, the issue involves track-mounted passenger seat assemblies whose aft fitting shear plungers may not have been correctly lowered and engaged in the seat tracks. The regulator said an incorrectly installed seat assembly could disengage from the seat tracks under increased loads, during turbulence or in an emergency landing. The FAA warned that, if the condition is not corrected, it could result in injuries to passengers or crew during an emergency landing or block an aisle and slow an evacuation. The FAA said the proposed directive would require operators to conduct a detailed inspection of the seat-track fittings on each left- and right-side track-mounted passenger seat assembly to verify that they are correctly installed. Any required corrective action would also have to be carried out. "There could be up to 69 track-mounted passenger seat assemblies on each 737 MAX plane," according to details cited in the FAA proposal. The agency estimates one work-hour for the required action per affected seat assembly, with the inspection and corrective work expected to cost operators about $85 per seat assembly. The FAA estimates the total inspection cost for U.S. operators at up to $2.66 million, while Boeing has indicated that some or all costs associated with the proposed AD may be covered under warranty. The FAA's proposed rule was prompted by Boeing Special Attention Requirements Bulletin 737-25-1927 RB, dated December 10, 2025. Boeing had previously provided guidance to operators on the issue, and the FAA is now proposing to make the required inspections and corrective actions mandatory. The agency said it had determined that the unsafe condition identified in the report is likely to exist or develop on other aircraft of the same type design. The proposal does not currently indicate that all 453 aircraft have incorrectly installed seats. Instead, the FAA is proposing inspections to determine whether the seat assemblies are correctly secured and to require corrective action where necessary. The FAA has set September 10, 2026, as the deadline for public comments on the proposed directive. The agency will consider comments before deciding whether to issue a final Airworthiness Directive. The FAA proposal itself does not identify a specific accident or injury linked to the seat installation issue. Rather, the regulator is acting on the potential safety risk posed by a seat assembly becoming disengaged from its track during high-load conditions. The development comes as the FAA continues heightened oversight of Boeing's production and quality-control processes. On July 17, 2026, the agency announced that Boeing would be allowed to resume issuing airworthiness certificates for all newly produced 737 MAX and 787 aircraft from July 20, following months of FAA review of production quality data. The latest seat-track proposal is therefore another regulatory action focused on ensuring that aircraft meet approved design and safety requirements, but it does not amount to a grounding order or an immediate suspension of 737 MAX operations.

Boeing

FAA Proposes Seat Inspections For 453 Boeing 737 MAX Jets Over Installation Issue

July 28, 2026

SWISS Flight Airbus A330 Diverted To Bangor After Smoke Reported Aboard The Aircraft SEO DES: Smoke was detected in the forward section of Business Class; FAA preliminarily reported a cockpit fire, but the smoke source remains unconfirmed SOCIAL: SWISS Flight LX16 from Zurich to New York JFK diverted to Bangor International Airport in Maine on July 27 after smoke was reportedly detected aboard. The Airbus A330 was carrying 208 people, and all passengers and crew landed safely. SWISS said the smoke was of unknown origin in the forward Business Class section, while the FAA preliminarily said the crew reported a cockpit fire. The aircraft landed on Runway 33, where emergency responders inspected it but found no signs of fire or excessive heat. The runway was temporarily closed for over 30 minutes, causing some flight delays. SWISS said the aircraft would undergo a thorough inspection and that it would not speculate on the cause until the checks were completed, while arrangements were made for passengers to continue their journey to New York. Bangor, United States: A Swiss International AirLines Airbus A330 operating Flight LX16 from Zurich to New York's John F. Kennedy International Airport made an emergency diversion to Bangor International Airport in Maine on Monday, July 27, after smoke was reported aboard the aircraft. The flight, carrying 208 passengers and crew, landed safely in Bangor at around noon local time. The aircraft was an Airbus A330, and emergency crews were placed on standby before it arrived at the airport. According to Swiss International Air Lines, the diversion was prompted by smoke of unknown origin detected in the forward section of the Business Class cabin. The airline said its pilots decided to land without delay and declare an emergency, allowing air traffic control to give the aircraft priority to land. The situation was also described differently in preliminary information released by the Federal Aviation Administration. The FAA said the flight crew had reported a cockpit fire before landing. The agency cautioned that the information was preliminary and subject to change. The airline, meanwhile, said the exact source of the smoke had not been identified. The aircraft was cruising at about 32,000 feet and was roughly 100 nautical miles southeast of Bangor when the crew diverted toward the airport. The crew reportedly initially reported smoke of unknown origin before subsequently telling air traffic control that there was an active fire in the cockpit that they were unable to extinguish. The pilots reportedly opened the cockpit door to allow smoke to escape, after which the smoke situation changed and was also noticed in the passenger cabin. The crew proceeded with the emergency diversion and landed on Runway 33 at Bangor International Airport. After landing, the aircraft stopped and shut down its engines while emergency responders assessed the situation. Firefighters entered the aircraft and inspected the interior, including equipment intended to detect heat. No signs of fire or excessive heat were found, and the source of the smoke remained undetermined. Passengers told local media that they noticed an electrical-type smell during the flight. One passenger said the smell appeared to be coming from the area of a seat, although this has not been established as the cause of the incident. Passengers also reported that the oxygen masks did not deploy and that they were not required to evacuate the aircraft on the runway. All 208 people aboard were reported safe, and no injuries were reported. The aircraft was subsequently inspected, while SWISS worked with authorities and Bangor International Airport to arrange onward travel for passengers to New York. The emergency landing temporarily closed the runway at Bangor International Airport for a little over 30 minutes, causing delays to other flights. The runway was reopened at about 12:30 p.m., according to an airport spokesperson. SWISS spokesperson Michael Pelzer said the airline understood that such a diversion could be unsettling for passengers and said teams in Switzerland and the United States were working to arrange onward travel. The airline also said the aircraft would undergo a thorough inspection by its experts and that it would not speculate on the cause of the smoke until the investigation and inspection were complete. The FAA said it would investigate the incident. The aircraft's emergency diversion was resolved without further incident, with all passengers and crew safely on the ground in Bangor.

Incidents

SWISS Flight Airbus A330 Diverted To Bangor After Smoke Reported Aboard The Aircraft

July 28, 2026

« Previous Next »

Subscribe to our Newsletter

Email

Recent News

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

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

August 18, 2026

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

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

August 18, 2026

New Delhi, India: India’s Directorate General of Civil Aviation (DGCA) recorded 889 serious technical defects during flight operations in 2025, the highest figure in the five-year data released by the Civil Aviation Ministry, with cases rising nearly 28.5% from 692 in 2024. The figures were disclosed by Minister of State for Civil Aviation Murlidhar Mohol in a written reply in the Lok Sabha on August 6, 2026, in response to questions from Congress MP Shyamkumar Daulat Barve. The data showed 514 serious technical defects in 2021, 528 in 2022, 487 in 2023, 692 in 2024 and 889 in 2025. The 2025 total was 197 cases higher than the previous year and about 73% above the 2021 figure. However, the parliamentary disclosure does not provide an aircraft-by-aircraft breakdown of the 889 cases, including aircraft registration, model, airline or the specific technical fault involved. The figures therefore cannot be used to attribute the cases to particular Boeing or Airbus aircraft, engines or aircraft systems. Mohol said the DGCA has established Civil Aviation Requirements (CARs), safety advisories, directives and other regulatory instructions to ensure safe aircraft operations. He said, “For monitoring compliance, DGCA has a systematic safety oversight mechanism encompassing all aircraft and airport operators.” He added, “The safety oversight process includes regulatory audits, night surveillance, ramp inspections, spot checks and special audits. DGCA publishes the Annual Surveillance Plan (ASP) on its website.” The government data also showed that the DGCA took action over safety violations involving airlines and Maintenance, Repair and Overhaul (MRO) operators in 42 cases in 2025, compared with 31 in 2024, 24 in 2023, seven in 2022 and one in 2021. A separate parliamentary disclosure made in July 2025 provides airline-wise technical-defect figures and offers additional context, but it is a different dataset from the 889 serious-defect series. It recorded 183 technical defects reported by scheduled commercial airlines between January 1 and July 21, 2025. Air India and Air India Express together accounted for 85, IndiGo for 62, Akasa Air for 28 and SpiceJet for eight. The earlier data showed 421 technical defects in 2024, 448 in 2023, 528 in 2022 and 514 in 2021. The government said reported defects are investigated and appropriate rectification action is taken. Mohol said, “All defects reported by the airline to the Directorate General of Civil Aviation (DGCA) are required to be investigated for taking appropriate rectification action.” He further said, “The investigation of all defects, particularly major defects, has to be completed expeditiously so as to take preventive/corrective action at the earliest possible.” The government stated that major defects are investigated by the operator in association with the DGCA. The latest available 2026 data provides another indication of the technical issues being reported across Indian aviation, although it should not be added directly to the 889-case five-year series. The Civil Aviation Ministry told the Rajya Sabha on August 3 that 352 “significant technical defects” were reported in domestic and international flight operations between January and June 2026. Of these, 334 related to domestic operations and 18 to international services. Akasa Air accounted for the largest share of the 2026 cases with 152, followed by Air India Express with 53, IndiGo with 47 and Air India with 46. Star Air recorded 29, while SpiceJet and Fly91 reported nine each and IndiaOne Air five. The ministry also said the DGCA issued 382 show-cause notices to airlines for safety violations between January 2024 and June 2026. Separately, the regulator initiated 51 enforcement actions against scheduled airlines between 2023 and 2025 for major violations of safety standards. The measures included financial penalties, suspension of approvals or authorisations and warnings. The government has also reported 2,420 significant technical defects across domestic and international flight operations during the three-year period covered by the latest Rajya Sabha question. That figure, like the 352 cases reported for the first half of 2026, belongs to a separate dataset and should not be combined with the 889 serious defects recorded for 2025. The disclosures show a clear rise in reported technical-defect cases, particularly in 2025, but they do not establish that each case involved a different aircraft or that the defects resulted in an accident, emergency or flight cancellation. The government data available in the cited parliamentary replies also does not provide a fault-by-fault list identifying the aircraft model, registration or affected component for the 889 cases. The figures instead highlight the scale of technical-defect reporting and the DGCA’s enforcement and surveillance activity. The regulator’s stated oversight framework covers aircraft and airport operators through audits, night surveillance, ramp inspections, spot checks and special audits, while airlines are required to investigate and rectify reported defects.

India Records 889 Serious Aircraft Technical Defects in 2025, Highest In Five Years

August 18, 2026

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

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

August 18, 2026

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

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

August 17, 2026

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

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

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

From Demonstrations to Networks: The Real Test of Advanced Air Mobility Citywide Networks Must Be Designed Around Real Travel Patterns

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

From Demonstrations to Networks: The Real Test of Advanced Air Mobility Part 2- Aviation Today Perspectives

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

Follow Us

Facebook-f Instagram Linkedin-in X-twitter Youtube

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

Quick Links

About Us
Contact Us
Services
Advertise
FAQ

Navigate

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

General Support

info@aviationtoday.in

News Desk Support

news@aviationtoday.in

Follow Us

Facebook-f Instagram Linkedin-in X-twitter Youtube

© Copyright 2026 Aviation Today. All rights reserved.

Terms of Use
Privacy Policy
Disclaimer

Search

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

Aviation Newsletter

Facebook Instagram Linkedin X-twitter Youtube