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

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

US Army UH-72 Lakota Crashes In Alabama During Training Flight, Three Survive SEO DES: A UH-72 carrying an instructor and 2 student pilots reportedly lost power and crashed during a training flight with the cause under investigation SOCIAL: A U.S. Army UH-72 Lakota helicopter was involved in an aviation mishap Monday afternoon, July 27, during routine flight training in a remote area near Opp, Alabama. Three people were aboard, including one instructor pilot and two student pilots. All three occupants survived and were taken to a Dothan-area hospital for medical evaluation. Their identities and injury details have not been publicly released, but all were reported to be in stable condition. The Army has not disclosed how the helicopter came down, the extent of aircraft damage, or the cause of the mishap. The incident remains under investigation, with no fatalities reported. Opp, United States: A US Army UH-72 Lakota helicopter was involved in an aviation mishap Monday afternoon, July 27, it crashed in a privately owned field on Cool Springs Road near the Opp Bypass in Covington County, with all three people aboard reported in stable condition, according to Fort Rucker officials. The helicopter was operating in a remote training area near Opp when the incident occurred. Officials say the crew was conducting routine flight training. Covington County Sheriff Blake Turman says it appears that the helicopter lost power and crashed. Fort Rucker officials confirmed that a single UH-72 Lakota was involved in the aviation mishap and that three people were aboard the aircraft. According to information released by Fort Rucker officials, all three occupants survived the incident and were reported to be in stable condition. Occupants are identified as an instructor pilot and two student pilots and they were taken to a Dothan-area hospital for medical evaluation and treatment. The identities of the three occupants have not been publicly released in the official information currently available. Officials have also not disclosed the extent of their injuries. The circumstances that led to the helicopter mishap, including how the aircraft came down and whether it sustained significant damage, have not been publicly detailed. Fort Rucker officials have not announced a cause, and the incident remains under investigation. The Army has described the event as an "aviation mishap." No fatalities have been reported. The UH-72 Lakota is operated by the US Army for missions including training and support operations. The helicopter involved in Monday's incident was being used during a routine training flight. As of the latest available official information, the three people aboard remained in stable condition, while the cause of the mishap was under investigation.

Aircraft Crashes

US Army UH-72 Lakota Crashes In Alabama During Training Flight, Three Survive

July 28, 2026

Gujarat, India: An IndiGo flight operating from Dubai to Mumbai made a precautionary emergency landing at Rajkot International Airport in Gujarat on Monday, July 27, after the crew reportedly detected a smoke alert from the aircraft's cargo hold area. All 194 people onboard, comprising 187 passengers and seven crew members, safely disembarked after the Airbus A321 landed at Rajkot. The flight, IndiGo 6E 1452, was operating from Dubai International Airport to Chhatrapati Shivaji Maharaj International Airport in Mumbai. The aircraft departed Dubai at around 11:30 a.m. IST before being diverted to Rajkot as a precaution following the reported smoke indication from the cargo hold. An airport official said, "Flight IGO1452, aircraft type A321, operating from Dubai to Mumbai, was diverted to Rajkot due to smoke detected in the cargo hold area." Airport authorities were alerted to the situation at around 2:45 p.m., following which a full emergency was declared at Rajkot International Airport. Emergency response teams, including fire tenders, ambulances, rescue vehicles and medical personnel, were deployed as part of the airport's emergency procedures. Local hospitals and police authorities were also alerted and kept on standby. The flight crew initially detected smoke indicators in the cargo hold during the mid-air journey, prompting the diversion to Rajkot as a precaution. IndiGo, however, said in a statement: “IndiGo flight 6E 1452, operating from Dubai to Mumbai, was diverted to Rajkot International Airport today as a precautionary measure due to a technical issue. The aircraft landed safely at Rajkot, and all passengers have deboarded securely. An inspection of the aircraft is currently underway before it is cleared to resume operations,” the spokesperson said. The Airbus A321 landed safely at Hirasar International Airport, also known as Rajkot International Airport, at approximately 3:27 p.m. Police, security personnel and firefighters were present at the airport as the aircraft arrived. No injuries were reported among the passengers or crew. Sources at the airport said IndiGo was arranging another aircraft to carry the affected passengers onward to Mumbai. The exact cause was not immediately established, and reports did not confirm whether an actual fire occurred in the cargo compartment. Authorities were expected to examine the aircraft to determine the cause. The incident triggered the airport's full emergency response protocol, but the aircraft completed the landing without any reported damage or injuries.

Incidents

IndiGo Dubai-Mumbai Flight Makes Emergency Landing After Reported Cargo Hold Smoke

July 28, 2026

Eugene, United States: An Alaska Airlines Boeing 737-800 operating Flight AS471 from Santa Ana, California, to Seattle, Washington, safely diverted to Eugene, Oregon, on July 23, 2026, after the crew received a low oil quantity and pressure warning involving the aircraft's left-hand CFM56 engine. The aircraft, registered as N563AS, was cruising at 36,000 feet (FL360) when the issue occurred approximately 90 nautical miles south-southeast of Eugene, Oregon. In response to the low oil pressure indication, the flight crew precautionarily shut down the affected engine and initiated a diversion to Eugene Airport (EUG). Flight AS471 was carrying 161 passengers and six crew members at the time of the incident. Following the engine shutdown, the pilots continued the flight safely with the remaining engine operating and diverted to Eugene as a precaution. The aircraft landed safely on Runway 34L at Eugene Airport approximately 25 minutes after the diversion was initiated. No injuries were reported among the passengers or crew following the landing. The aircraft was subsequently taken out of service for inspection and maintenance to determine the precise cause of the low oil quantity and pressure indication. The incident involved one of the aircraft's two CFM56 engines, with the left-hand engine being shut down as a precaution. Passengers were later transferred to a replacement Boeing 737-800, registered as N597AS, to continue their journey to Seattle. The replacement aircraft eventually arrived in Seattle approximately four hours later than the original scheduled arrival time. The incident demonstrates the procedures followed by flight crews when an engine-related warning occurs during cruise. Boeing 737-800 aircraft are designed and certified to continue flight safely following the loss or shutdown of one engine, allowing pilots to divert to a suitable airport while maintaining control of the aircraft. The aircraft's diversion to Eugene allowed the crew to land safely and have the affected engine inspected before the aircraft could return to normal operations. No injuries were reported in connection with the incident.

Incidents

Alaska Airlines 737 Diverts To Eugene After Engine Oil Warning Prompts Mid-Air Shutdown

July 27, 2026

« Previous Next »

Subscribe to our Newsletter

Email

Recent News

Greek F-4E Phantom II Crashes During Tanagra Airshow, Killing Two Pilots Onboard

Greek F-4E Phantom II Crashes During Tanagra Airshow, Killing Two Pilots Onboard

September 7, 2026

Anak Krakatau Volcanic Eruption Disrupts 2,300 Flights, Forces Closure Of 7 Airports

Anak Krakatau Volcanic Eruption Disrupts 2,300 Flights, Forces Closure Of 7 Airports

September 7, 2026

A Small Grumman AA-5 Crash Near Fresno River Kills Three Among Four Onboard

A Small Grumman AA-5 Crash Near Fresno River Kills Three Among Four Onboard

September 7, 2026

Five Killed, Five Injured After Amazon Air Boeing 767 Overruns Runway At Miami Airport

Five Killed, Five Injured After Amazon Air Boeing 767 Overruns Runway At Miami Airport

September 7, 2026

REGENT’s Viceroy Seaglider Completes First Human-Crewed Flight In Rhode Island

REGENT’s Viceroy Seaglider Completes First Human-Crewed Flight In Rhode Island

September 6, 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