Skip to content

Facebook Instagram Linkedin X-twitter Youtube

About Us
Contact Us
Advertisement

About Us
Contact Us
Advertisement

Aviation Newsletter

WhatsApp Channel

Search

Latest News
Aviation Today Perspectives
Aviation Jobs
About Us

Latest News
Aviation Today Perspectives
Aviation Jobs
About Us

Search

Latest News
Aviation Today Perspectives
Aviation Jobs
About Us

Latest News
Aviation Today Perspectives
Aviation Jobs
About Us

News

Civil Aviation

Pilot Training

Flight School Analysis

Aviation Jobs

Training

Services

About Us

Contact Us

Search

Just In

Isar Aerospace Spectrum Rocket Reaches Orbit In Historic European Commercial Launch
Four Miami Family Members Killed After Piper PA-34 Crashes In The Bahamas
Three Killed After Cessna 402B Crashes And Catches Fire In Brazil’s Mato Grosso
Netherlands Signs Sweden Deal For Saab GlobalEye AEW&C Aircraft, Delivery Set For 2031
Sydney Airport Imposes Flight Restrictions After Air Traffic Controller Shortage
Delta Flight DL2311 Makes 27,000-Foot Emergency Descent After Pressurization Issue
India’s DGCA Reportedly Directs One-Time Drug Testing Of All Pilots By July 2027
Delta Flight 1390 Declares Emergency After Cabin Fumes Detected Before Chicago Landing
EasyJet Faces $72 Million Lawsuit Over Six Airbus A319s Stranded Since 2022
Amazon Air 767 Crew Warned Of Excessive Speed Before Miami Runway Overrun, NTSB Reveals

Isar Aerospace Spectrum Rocket Reaches Orbit In Historic European Commercial Launch

Isar Aerospace Spectrum Rocket Reaches Orbit In Historic European Commercial Launch

Four Miami Family Members Killed After Piper PA-34 Crashes In The Bahamas

Four Miami Family Members Killed After Piper PA-34 Crashes In The Bahamas

Three Killed After Cessna 402B Crashes And Catches Fire In Brazil’s Mato Grosso

Three Killed After Cessna 402B Crashes And Catches Fire In Brazil’s Mato Grosso

Netherlands Signs Sweden Deal For Saab GlobalEye AEW&C Aircraft, Delivery Set For 2031

Netherlands Signs Sweden Deal For Saab GlobalEye AEW&C Aircraft, Delivery Set For 2031

Sydney Airport Imposes Flight Restrictions After Air Traffic Controller Shortage

Sydney Airport Imposes Flight Restrictions After Air Traffic Controller Shortage

Latest Breaking News & Developments

Latest Breaking News & Developments

Isar Aerospace Spectrum Rocket Reaches Orbit In Historic European Commercial Launch

Aerospace

Isar Aerospace Spectrum Rocket Reaches Orbit In Historic European Commercial Launch

Posted onSeptember 12, 2026September 12, 2026

Four Miami Family Members Killed After Piper PA-34 Crashes In The Bahamas

Aircraft Crashes

Four Miami Family Members Killed After Piper PA-34 Crashes In The Bahamas

Posted onSeptember 12, 2026September 12, 2026

Three Killed After Cessna 402B Crashes And Catches Fire In Brazil’s Mato Grosso

Aircraft Crashes

Three Killed After Cessna 402B Crashes And Catches Fire In Brazil’s Mato Grosso

Posted onSeptember 11, 2026September 11, 2026

Netherlands Signs Sweden Deal For Saab GlobalEye AEW&C Aircraft, Delivery Set For 2031

Military Aviation

Netherlands Signs Sweden Deal For Saab GlobalEye AEW&C Aircraft, Delivery Set For 2031

Posted onSeptember 11, 2026September 11, 2026

Sydney Airport Imposes Flight Restrictions After Air Traffic Controller Shortage

Airports

Sydney Airport Imposes Flight Restrictions After Air Traffic Controller Shortage

Posted onSeptember 11, 2026September 11, 2026

Read More Stories

Read More Stories

Aviation Today Exclusive

Inside Aviation

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

3:51

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

3:10

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

5:32

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

3:42

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

4:05

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

4:06

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

3:46

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

5:37

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

5:44

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

5:23

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

6:03

TiHAN Highlights Autonomous Shuttles, Cargo Drones & Smart Mobility

5:38

Gandhi Automations Showcasing Advanced Hangar Door Technologies for Aviation Infrastructure

5:20

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

2:56

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

7:19

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

2:06

Aviation Today Perspectives

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

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

Read More

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

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

Read More

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

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

Read More

Aviation Today Perspectives

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

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

Read More

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

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

Read More

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

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

Read More

Read More Perspectives

Aircraft Crashes

Airlines

Incidents

Four Miami Family Members Killed After Piper PA-34 Crashes In The Bahamas

Four Miami Family Members Killed After Piper PA-34 Crashes In The Bahamas

Agua Boa, Brazil: Three people were killed when a small Cessna 402B crashed and caught fire on a rural property near Água Boa in Brazil's central-western state of Mato Grosso on Thursday, September 10, 2026 according to local authorities. The aircraft was destroyed in the post-impact fire, and investigators are working to establish the circumstances of the crash, the flight's details and the identities of those onboard. The aircraft came down at a rural property about 18–20 kilometres from the urban area of Água Boa. Brazilian reports identified the aircraft as a Cessna 402B, manufactured in 1970, with serial number 402B0035. Later reports linked the aircraft to US registration N401NA, although Brazilian records and images from earlier aircraft sales have also shown other registration markings, including PS-WJR and PS-WJU. The registration discrepancy has not been resolved by authorities and should not be treated as proof of an illegal operation. The aircraft caught fire after the crash and was almost completely destroyed. The Corpo de Bombeiros was called at about 8:50 a.m. local time and used approximately 4,000 litres of water to extinguish the flames. After the fire was brought under control, firefighters found three bodies in the wreckage. The bodies were taken for forensic examination, while the Polícia Civil, Polícia Militar and Perícia Oficial e Identificação Técnica (Politec) worked at the site. Police initially said the condition of the wreckage made it impossible to identify the victims or determine key details of the flight. Delegado Carlos Alberto, who was handling the occurrence, said: “The state in which the aircraft was found initially made its identification impossible. For this reason, it was not possible, so far, to confirm information about any flight plan, the aircraft's place of origin or destination, nor the identity of the people who were onboard.” Later reporting established that three people were onboard, with all three confirmed dead. However, their names have not been officially released in the latest reports reviewed for this update. Earlier reports had used the wording “at least three killed” because authorities had initially been unable to determine the total number of occupants. The aircraft's operational purpose and operator also remain unconfirmed. Reports have not established whether it was conducting a private, charter, cargo or other type of flight. Likewise, authorities had not officially confirmed its departure point, intended destination or whether a flight plan had been filed. One local report claimed the aircraft may have departed from an airfield in Goiânia, but that detail has not been independently confirmed by the authorities and should therefore not be presented as established fact. Brazil's Centro de Investigação e Prevenção de Acidentes Aeronáuticos (CENIPA) was notified and is expected to participate in the complementary investigative work alongside the police and forensic authorities. The cause of the crash has not been determined, and there is currently no confirmed evidence identifying mechanical failure, weather, pilot action or another specific factor as the cause. Investigators are expected to examine the wreckage, aircraft documentation, registration history, possible flight-plan information and forensic evidence as they establish what happened before the Cessna 402B crashed and caught fire in rural Água Boa.

Three Killed After Cessna 402B Crashes And Catches Fire In Brazil’s Mato Grosso

Cessna 172 Crashes After Reported Engine Failure Near Grand Central Airport, One Injured

Cessna 172 Crashes After Reported Engine Failure Near Grand Central Airport, One Injured

Two Killed As Cessna 172 Crashes And Erupts In Flames At San Diego Airport SEO DES: The aircraft was conducting touch-and-go approaches before crashing on its ninth go-around amid winds of 17 knots, gusting to 22 knots SOCIAL: A Cessna 172N Skyhawk II, registered N734ZK, crashed and caught fire near Runway 28L at Montgomery-Gibbs Executive Airport in San Diego on September 7, 2026, killing two people. The aircraft had been conducting touch-and-go approaches before the crash. Preliminary data indicates the accident occurred during its ninth go-around amid winds of 17 knots, gusting to 22 knots. Witnesses reported a possible stall/spin, but investigators have not confirmed the cause. San Diego Fire-Rescue crews extinguished the fire and managed a fuel leak, while the NTSB and FAA began investigating. The victims’ identities have not been released, and the airport was temporarily closed following the crash. San Diego, United States: Two people were killed after a Cessna 172 crashed and erupted in flames at Montgomery-Gibbs Executive Airport in San Diego, California, during a local flight on September 7, 2026. The aircraft, identified as a 1977 Cessna 172N Skyhawk II registered N734ZK, crashed at about 5:19–5:21 p.m. local time near Runway 28L. The National Transportation Safety Board (NTSB) and Federal Aviation Administration (FAA) are investigating the accident. San Diego police confirmed two fatalities after receiving a report of the crash at about 5:21 p.m. The aircraft became engulfed in flames, prompting a major response from San Diego Fire-Rescue. Approximately 30 fire personnel responded to the runway as firefighters worked to extinguish the aircraft fire and address a small fuel leak. San Diego Fire-Rescue Assistant Fire Chief Brian Raines said rescuers initially focused on reaching the occupants but were unable to remove them because of the extent of the damage. “Rescue is always our first priority. That's what the first units were trying to do. The plane was heavily damaged, and we were not able to extricate any of the victims. We had to focus on extinguishing the fire,” Raines said. Witnesses who were working in a nearby hangar said that they heard the crash and ran toward the aircraft with fire extinguishers. Witness Mauricio Godinez said, “As soon as we got back to the plane, flames were engulfing the wings,” adding that the wings were “melting, caving in.” Another witness, identified by FOX 5/KUSI as Melissa, said, “We tried our best to go save them, but it was just too much.” The aircraft was a four-seat, high-wing Cessna 172N Skyhawk II manufactured in 1977, with serial number 17269243 and a Lycoming O-320 engine. The aircraft had departed Montgomery-Gibbs earlier in the day and conducted local maneuvers before returning to the airport. It later departed again at about 4:27 p.m. and began a series of touch-and-go approaches on Runway 28L. The preliminary reconstruction says the accident occurred during the ninth go-around in that sequence. According to the preliminary reconstruction of ADS-B and air-traffic-control data, the Cessna was approaching Runway 28L while aircraft were also operating on the parallel Runway 28R. The controller provided traffic information and cleared the Cessna for the option on 28L. The pilot acknowledged the traffic and subsequently announced a go-around. ATC instructed the aircraft to extend upwind and issued additional traffic information as the Cessna maneuvered in the airport traffic pattern. The controller later warned that the Cessna was drifting north while another aircraft was departing westbound. The pilot responded that the aircraft was correcting south. ATC then provided further instructions for the crosswind turn and continued issuing traffic information. The pilot acknowledged the traffic. Shortly afterward, the controller reported winds of approximately 310 degrees at 17 knots, gusting to 22 knots. The Cessna then announced another go-around. According to the preliminary account, approximately four seconds later an impact sound was heard. The controller immediately informed another aircraft that the Cessna had experienced an accident and said the airport would be closed. A final transmission was subsequently heard from the accident aircraft before communications ended. Witness information cited in the preliminary aviation reconstruction indicates the aircraft may have entered a stall/spin during the attempted go-around before striking the ground near the holding point for Runway 28L. However, investigators have not determined that a stall or spin caused the accident, and no probable cause has been established. The NTSB investigation remains ongoing. The aircraft came to rest upright near the holding point for Runway 28L and was consumed by a post-crash fire. Preliminary photographs and observations indicate the cabin was heavily damaged by the fire, while the wings and tail remained attached to the aircraft. The available preliminary reconstruction says there was little evidence of a substantial debris field before the main wreckage. The identities of the two people killed have not been released by authorities. Investigators had not initially confirmed whether the pilot was experienced or whether the flight was being conducted as a training operation. The airport was temporarily closed following the crash while emergency crews handled the wreckage and fuel leak. The main runway later reopened after the emergency response and initial scene work. The NTSB will examine the aircraft, flight-track data, air-traffic-control communications, weather, pilot qualifications, maintenance records and other evidence to determine what led to the fatal crash.

Two Killed As Cessna 172 Crashes And Erupts In Flames At San Diego Airport

Five Killed As Flying Doctor Service Helicopter Crashes Near Long Lellang, Malaysia SEO DES: Helicopter was conducting a Flying Doctor Service mission when it crashed, killing the pilot, medical officer, assistant medical officer & 2 nurses onboard SOCIAL: Five people, including a pilot and four Malaysian Health Ministry personnel, were killed when a BO-105 helicopter (9M-LLF) crashed near Long Lellang STOLport in Sarawak on September 8, 2026. The helicopter was operated by Layang-Layang Aerospace Sdn Bhd and was conducting a Flying Doctor Service mission. The helicopter had departed Miri and was reportedly operating the Miri–Ba Lai–Long Siut–Long Lellang route. Those killed included a pilot, medical officer, assistant medical officer and two nurses travelling on official duty. Authorities confirmed the crash and fatalities, while search-and-rescue efforts were affected by the remote terrain and haze. Malaysia’s Air Accident Investigation Bureau will investigate the crash, while CAAM confirmed the aircraft and five people aboard. The cause remains unknown, and authorities have urged the public to avoid speculation as the investigation continues. Miri, Malaysia: Five people, including a pilot and four Malaysian Health Ministry personnel, were killed after a Flying Doctor Service helicopter crashed near Long Lellang STOLport in Sarawak, Malaysia, on September 8, 2026. The helicopter, a BO-105 identified as registration 9M-LLF, was operating a Flying Doctor Service mission when it crashed near the end of the airstrip at Long Lellang in the remote Marudi district of northern Sarawak. The aircraft was operated by Layang-Layang Aerospace Sdn Bhd, according to local reports. All five people aboard were killed. The victims included the pilot, a medical officer, an assistant medical officer and two nurses from Malaysia's Ministry of Health, who were travelling on official duty. Miri Division resident and chairman of the Miri Division Disaster Management Committee, Galong Luang, confirmed the deaths after receiving information from emergency and health authorities. “This is based on reports from the Fire and Rescue Department and the Ministry of Health,” Galong said. The crash occurred at approximately 3:40 p.m. near the end of Runway 04. The Civil Aviation Authority of Malaysia (CAAM) said it received notification of the occurrence from the Flight Information Service at 3:58 p.m. Health Minister Datuk Seri Dr Dzulkefly Ahmad said the helicopter had departed from Miri carrying one pilot and four Health Ministry personnel. “Based on the initial information received, the flight departing from Miri was operated by one pilot and carried four MOH health personnel, namely a medical officer, a medical assistant and two nurses who were on official duty,” he said. Initial information from Sarawak Police indicated that the privately owned helicopter had been chartered for Flying Doctor Service operations covering a route from Miri to Ba Lai, Long Siut and Long Lellang. Other local reports described the flight sector as Miri–Ba Lai–Long Siut–Long Lellang, indicating that Long Lellang was part of the helicopter's scheduled Flying Doctor Service mission. Sarawak Police Commissioner Datuk Mohamad Zainal Abdullah said the remote location and haze complicated the initial search-and-rescue response. “Air support using a helicopter from the Kuching Royal Malaysia Police Air Wing Base could not be carried out due to the hazy conditions and because the Civil Aviation Authority of Malaysia did not grant flight clearance,” Mohamad Zainal said. During the initial response, search-and-rescue efforts relied on assistance from local villagers, Malaysian Volunteer Corps personnel and auxiliary police at Long Lellang STOLport, while additional security personnel travelled to the crash site. The helicopter was later confirmed to have crashed near the end of the Long Lellang airstrip. The initial information from the Miri Airport Fire and Rescue Services indicated that the aircraft had taken off from Miri before crashing near the end of the runway at Long Lellang. The Long Lellang STOLport serves one of Sarawak's most isolated regions and is located next to Long Lellang village. The airfield provides access to remote communities, including Kelabit and Penan settlements, with the area lying hundreds of kilometres from Miri and difficult to access by road. The Flying Doctor Service plays a critical role in delivering medical services to isolated communities in Sarawak, where difficult terrain and limited road access often make air transport essential for healthcare teams. The Civil Aviation Authority of Malaysia confirmed that the aircraft involved was a BO-105 helicopter registered 9M-LLF and said five people, including the pilot, were aboard. The cause of the crash has not been established. Malaysia's Air Accident Investigation Bureau (AAIB), under the Ministry of Transport, will investigate the accident in accordance with Part XXVI of the Civil Aviation Regulations 2016. “The Air Accident Investigation Bureau, under the Transport Ministry, will investigate the incident,” CAAM said. Sarawak Police also urged the public not to speculate while authorities continue examining the circumstances of the accident. The investigation is expected to determine the sequence of events leading to the crash of the Flying Doctor Service helicopter and identify any contributing factors. No official cause has been announced.

Five Killed As Flying Doctor Service Helicopter Crashes Near Long Lellang, Malaysia

EasyJet Faces $72 Million Lawsuit Over Six Airbus A319s Stranded Since 2022

EasyJet Faces $72 Million Lawsuit Over Six Airbus A319s Stranded Since 2022

Singapore Transport Minister Defends SIA’s Air India Investment Amid Funding Concerns

Singapore Transport Minister Defends SIA’s Air India Investment Amid Funding Concerns

Air India Terminates Phuket-Delhi Flight Pilot After Positive Drug Test Results

Air India Terminates Phuket-Delhi Flight Pilot After Positive Drug Test Results

Nairobi, Kenya: Kenya’s aviation workers have called off their two-day strike after signing a return-to-work agreement with the government, Kenya Aviation Workers’ Union (KAWU), Kenya Civil Aviation Authority (KCAA), Kenya Airports Authority (KAA) and Jambojet. Workers have been directed to resume normal duties immediately and help restore flight operations. The strike, which began on Sunday, August 30, 2026 and continued through Monday, August 31, 2026 was largely driven by air traffic controllers and disrupted flights at Jomo Kenyatta International Airport (JKIA) in Nairobi, with effects also reported at Moi International Airport in Mombasa, Kisumu International Airport and Eldoret International Airport. The disruption also spilled over into regional operations, with airlines serving Rwanda, Burundi, Tanzania, Uganda, Somalia and Mauritius cancelling or rescheduling flights. The workers’ grievances included the lack of a Collective Bargaining Agreement (CBA) with KCAA, delayed salary reviews, a dispute over union agency fees held by KAA and allegations of victimisation of KAWU members at Jambojet. Passengers at JKIA reported hours-long delays and cancellations, while Kenya Airways warned travellers of disruptions to its schedules. Transport Minister Davis Chirchir said the agreement provides a framework to address three CBAs that have been suspended since 2015. “We have looked at various issues ... with very clear guidelines ... on how we are going to deal with the three CBAs,” Chirchir said. KAWU Secretary General Moss Ndiema confirmed the strike was being withdrawn and called on employees to restore services. “We are simply calling off our strike action and pleading with our members to begin the process of normalising operations, restoring services,” Ndiema said. He also urged workers on duty to begin clearing flights. Under the return-to-work agreement, KAWU and KCAA will resume CBA negotiations, while the KAA agency-fee issue and the union’s recognition dispute with Jambojet will continue through the agreed processes. The agreement also provides protection against victimisation of workers who took part in the industrial action. The Kenyan government had earlier apologised to affected passengers as talks continued. With the strike now called off, airlines and airports are expected to work through the backlog and restore normal schedules.

Kenya Aviation Workers End 2-Day Strike After Disrupting Flights At Major Airports

Kenya Aviation Workers Resume Strike, Causing Delays And Cancellations At Nairobi’s JKIA

Kenya Aviation Workers Resume Strike, Causing Delays And Cancellations At Nairobi’s JKIA

Delta Flight DL2311 Makes 27,000-Foot Emergency Descent After Pressurization Issue SEO DES: The aircraft descended from approximately 36,200 feet to 9,000 feet in about 10 minutes before diverting to Harry Reid International Airport in Las Vegas SOCIAL: Delta Air Lines Flight DL2311 made an emergency descent of approximately 27,000 feet on September 6, 2026, after an unexpected pressurization issue triggered the deployment of passenger oxygen masks. The Boeing 737-900 was flying from Los Angeles to Salt Lake City with 174 passengers and six crew members onboard. The aircraft descended from approximately 36,200 feet to 9,000 feet in about 10 minutes before diverting to Harry Reid International Airport in Las Vegas. The crew confirmed to air traffic control that oxygen masks had deployed, while Delta said its pilots followed established procedures to bring the aircraft to a safe altitude. The aircraft landed safely in Las Vegas at approximately 6:16 p.m. local time, with no injuries reported. Delta arranged for passengers to continue their journey, while the specific technical cause of the pressurization issue has not yet been publicly disclosed. Image: formulanone (Flickr) Video: Delta Air Lines Las Vegas, United States: Delta Air Lines Flight DL2311 made a rapid emergency descent of approximately 27,000 feet after an unexpected pressurization issue triggered the deployment of passenger oxygen masks, forcing the Los Angeles-to-Salt Lake City flight to divert to Las Vegas on September 6, 2026. The Boeing 737-900 operating the flight departed Los Angeles International Airport (LAX) at approximately 4:54 p.m. local time on Sunday, September 6, bound for Salt Lake City International Airport (SLC). The aircraft was carrying 174 passengers and six crew members. About halfway through the scheduled one-hour-and-22-minute journey, the aircraft was flying at approximately 36,200 feet when the pressurization issue occurred. Flight data showed the aircraft descending to 9,000 feet over approximately 10 minutes, a reduction in altitude of around 27,000 feet. Passenger oxygen masks deployed in the cabin during the emergency descent. Air traffic control communications recorded during the incident captured the crew reporting the situation and requesting an immediate descent toward Las Vegas. “Delta 2311 is currently in rapid descent. We'd like to get down to 9,000 and we're direct to Las Vegas,” a pilot said. When an air traffic controller asked, “Is the oxygen deployed?” the pilot responded, “Affirmative.” Delta said the emergency descent followed an unexpected pressurization issue. The airline has not publicly disclosed the specific technical cause behind the pressurization problem. “As safety comes before everything else at Delta, the flight crew of Delta flight 2311 LAX-SLC followed their training and procedures to safely bring the aircraft to optimal altitude when an unexpected pressurization issue occurred,” a Delta spokesperson said. The aircraft diverted to Harry Reid International Airport (LAS) in Las Vegas and landed safely at approximately 6:16 p.m. local time. Passengers deplaned normally after landing, and Delta arranged another aircraft for passengers to continue their journey to Salt Lake City. “Delta sincerely apologizes to our customers for their experience and thanks our flight crews and other support teams on the ground for their professionalism,” the spokesperson added. The rapid descent attracted widespread attention because of the significant altitude change within a short period. However, aviation safety procedures require crews dealing with a serious cabin pressurization problem at cruising altitude to descend quickly to an altitude where occupants can breathe safely without relying on supplemental oxygen. According to the Federal Aviation Administration, a lack of adequate oxygen can result in hypoxia, a condition caused by an insufficient supply of oxygen to the body. Matthew “Whiz” Buckley, a retired US A Navy F/A-18 fighter pilot with nearly 40 years of flying experience, told Fox News Digital, describing such a pressurization occurrence as “an extremely rare issue” in the United States. Buckley said that in such circumstances, pilots would need “to land as soon as practical, meaning, what's the closest airfield with a nice, long, suitable runway where we can get this thing on the ground safely.” The specific technical reason for the unexpected pressurization problem has not yet been publicly disclosed. The aircraft landed safely in Las Vegas, with no injuries reported in the information released by Delta.

Delta Flight DL2311 Makes 27,000-Foot Emergency Descent After Pressurization Issue

Delta Flight 1390 Declares Emergency After Cabin Fumes Detected Before Chicago Landing

Delta Flight 1390 Declares Emergency After Cabin Fumes Detected Before Chicago Landing

Qantas Flight Diverts To Christchurch After Engine Flames Seen Shortly After Takeoff

Qantas Flight Diverts To Christchurch After Engine Flames Seen Shortly After Takeoff

Crawley, United Kingdom: A Norse Atlantic Airways Boeing 787-9 rejected its takeoff from London Gatwick Airport on September 4, 2026 after a reported nose-gear problem, leaving the aircraft disabled on the runway and forcing the airport to temporarily halt flight operations. The aircraft, a Boeing 787-9 Dreamliner registered G-CKOF, was operating Norse Atlantic flight Z0701 from London Gatwick (LGW) to New York John F. Kennedy International Airport (JFK). It was accelerating for departure from Runway 26L when the crew rejected the takeoff at about 120 knots over the ground, according to preliminary aviation incident information. Reports said that the rejected takeoff followed a problem with the aircraft’s nose landing gear and that the nose wheels had turned about 90 degrees. The aircraft then stopped on the runway and became disabled. The precise technical cause of the nose-wheel movement has not been officially declared by the airline. The aircraft remained on Runway 26L while airport emergency teams responded. The incident did not result in any reported injuries among passengers or crew. A passenger onboard, Alice Kavanagh, described the moment the aircraft stopped as frightening, saying the pilot “slammed the brakes on” after a reported technical fault was detected. The Boeing 787 was subsequently removed from the runway. The aircraft blockage had an immediate effect on Gatwick because the airport effectively operates with one runway at a time. Although Gatwick has two runways, their proximity means they cannot normally be used simultaneously for independent operations. As a result, the closure of Runway 26L temporarily stopped both departing and arriving traffic. London Gatwick confirmed that the runway remained closed for 50 minutes because of the incident. “The runway was closed for 50 minutes this afternoon (Friday 4 September) due to a technical issue with a departing aircraft,” a Gatwick spokesperson said. “The aircraft was towed from the runway, which reopened shortly afterwards following a full safety inspection. As always, safety and security is our number one priority.” The runway reopened after airport teams completed the required safety inspection. Subsequent reporting put the reopening at approximately 14:36 BST, although the airport’s official statement characterized it simply as reopening shortly after the aircraft was removed and the inspection was completed. The temporary closure created a wider disruption across Gatwick’s flight schedule. Several inbound flights were diverted to alternative airports, with London Luton and London Stansted among the destinations reported for diverted services. EasyJet flights were also affected by the disruption. Flight-tracking data later showed severe delays affecting more than 330 flights at Gatwick, with an average delay of about 57 minutes. The effects continued after the runway reopened because aircraft, crews and passengers had been displaced during the closure. For the incident, Gatwick has confirmed only that a technical issue involving a departing aircraft caused the runway closure. The more specific information concerning the nose gear and the reported 90-degree movement of the nose wheels remains preliminary. Further maintenance findings or an official investigation would be needed to establish the exact cause of the rejected takeoff.

Norse Atlantic Rejects Takeoff At Gatwick After Reported Nose Gear Issue, Runway Closed

IndiGo Airlines, 6E1302, IndiGo 6E1302, Doha Bengaluru Flight, Doha Bengaluru, Muscat Diversion, Muscat International Airport, Hamad International Airport, Bengaluru Airport, Pilot Illness, Pilot Medical Issue, Crew

IndiGo Doha-Bengaluru Flight Diverted To Muscat Over Crew Medical Emergency

Aircraft Crashes

Four Miami Family Members Killed After Piper PA-34 Crashes In The Bahamas

Four Miami Family Members Killed After Piper PA-34 Crashes In The Bahamas

Agua Boa, Brazil: Three people were killed when a small Cessna 402B crashed and caught fire on a rural property near Água Boa in Brazil's central-western state of Mato Grosso on Thursday, September 10, 2026 according to local authorities. The aircraft was destroyed in the post-impact fire, and investigators are working to establish the circumstances of the crash, the flight's details and the identities of those onboard. The aircraft came down at a rural property about 18–20 kilometres from the urban area of Água Boa. Brazilian reports identified the aircraft as a Cessna 402B, manufactured in 1970, with serial number 402B0035. Later reports linked the aircraft to US registration N401NA, although Brazilian records and images from earlier aircraft sales have also shown other registration markings, including PS-WJR and PS-WJU. The registration discrepancy has not been resolved by authorities and should not be treated as proof of an illegal operation. The aircraft caught fire after the crash and was almost completely destroyed. The Corpo de Bombeiros was called at about 8:50 a.m. local time and used approximately 4,000 litres of water to extinguish the flames. After the fire was brought under control, firefighters found three bodies in the wreckage. The bodies were taken for forensic examination, while the Polícia Civil, Polícia Militar and Perícia Oficial e Identificação Técnica (Politec) worked at the site. Police initially said the condition of the wreckage made it impossible to identify the victims or determine key details of the flight. Delegado Carlos Alberto, who was handling the occurrence, said: “The state in which the aircraft was found initially made its identification impossible. For this reason, it was not possible, so far, to confirm information about any flight plan, the aircraft's place of origin or destination, nor the identity of the people who were onboard.” Later reporting established that three people were onboard, with all three confirmed dead. However, their names have not been officially released in the latest reports reviewed for this update. Earlier reports had used the wording “at least three killed” because authorities had initially been unable to determine the total number of occupants. The aircraft's operational purpose and operator also remain unconfirmed. Reports have not established whether it was conducting a private, charter, cargo or other type of flight. Likewise, authorities had not officially confirmed its departure point, intended destination or whether a flight plan had been filed. One local report claimed the aircraft may have departed from an airfield in Goiânia, but that detail has not been independently confirmed by the authorities and should therefore not be presented as established fact. Brazil's Centro de Investigação e Prevenção de Acidentes Aeronáuticos (CENIPA) was notified and is expected to participate in the complementary investigative work alongside the police and forensic authorities. The cause of the crash has not been determined, and there is currently no confirmed evidence identifying mechanical failure, weather, pilot action or another specific factor as the cause. Investigators are expected to examine the wreckage, aircraft documentation, registration history, possible flight-plan information and forensic evidence as they establish what happened before the Cessna 402B crashed and caught fire in rural Água Boa.

Three Killed After Cessna 402B Crashes And Catches Fire In Brazil’s Mato Grosso

Cessna 172 Crashes After Reported Engine Failure Near Grand Central Airport, One Injured

Cessna 172 Crashes After Reported Engine Failure Near Grand Central Airport, One Injured

Two Killed As Cessna 172 Crashes And Erupts In Flames At San Diego Airport SEO DES: The aircraft was conducting touch-and-go approaches before crashing on its ninth go-around amid winds of 17 knots, gusting to 22 knots SOCIAL: A Cessna 172N Skyhawk II, registered N734ZK, crashed and caught fire near Runway 28L at Montgomery-Gibbs Executive Airport in San Diego on September 7, 2026, killing two people. The aircraft had been conducting touch-and-go approaches before the crash. Preliminary data indicates the accident occurred during its ninth go-around amid winds of 17 knots, gusting to 22 knots. Witnesses reported a possible stall/spin, but investigators have not confirmed the cause. San Diego Fire-Rescue crews extinguished the fire and managed a fuel leak, while the NTSB and FAA began investigating. The victims’ identities have not been released, and the airport was temporarily closed following the crash. San Diego, United States: Two people were killed after a Cessna 172 crashed and erupted in flames at Montgomery-Gibbs Executive Airport in San Diego, California, during a local flight on September 7, 2026. The aircraft, identified as a 1977 Cessna 172N Skyhawk II registered N734ZK, crashed at about 5:19–5:21 p.m. local time near Runway 28L. The National Transportation Safety Board (NTSB) and Federal Aviation Administration (FAA) are investigating the accident. San Diego police confirmed two fatalities after receiving a report of the crash at about 5:21 p.m. The aircraft became engulfed in flames, prompting a major response from San Diego Fire-Rescue. Approximately 30 fire personnel responded to the runway as firefighters worked to extinguish the aircraft fire and address a small fuel leak. San Diego Fire-Rescue Assistant Fire Chief Brian Raines said rescuers initially focused on reaching the occupants but were unable to remove them because of the extent of the damage. “Rescue is always our first priority. That's what the first units were trying to do. The plane was heavily damaged, and we were not able to extricate any of the victims. We had to focus on extinguishing the fire,” Raines said. Witnesses who were working in a nearby hangar said that they heard the crash and ran toward the aircraft with fire extinguishers. Witness Mauricio Godinez said, “As soon as we got back to the plane, flames were engulfing the wings,” adding that the wings were “melting, caving in.” Another witness, identified by FOX 5/KUSI as Melissa, said, “We tried our best to go save them, but it was just too much.” The aircraft was a four-seat, high-wing Cessna 172N Skyhawk II manufactured in 1977, with serial number 17269243 and a Lycoming O-320 engine. The aircraft had departed Montgomery-Gibbs earlier in the day and conducted local maneuvers before returning to the airport. It later departed again at about 4:27 p.m. and began a series of touch-and-go approaches on Runway 28L. The preliminary reconstruction says the accident occurred during the ninth go-around in that sequence. According to the preliminary reconstruction of ADS-B and air-traffic-control data, the Cessna was approaching Runway 28L while aircraft were also operating on the parallel Runway 28R. The controller provided traffic information and cleared the Cessna for the option on 28L. The pilot acknowledged the traffic and subsequently announced a go-around. ATC instructed the aircraft to extend upwind and issued additional traffic information as the Cessna maneuvered in the airport traffic pattern. The controller later warned that the Cessna was drifting north while another aircraft was departing westbound. The pilot responded that the aircraft was correcting south. ATC then provided further instructions for the crosswind turn and continued issuing traffic information. The pilot acknowledged the traffic. Shortly afterward, the controller reported winds of approximately 310 degrees at 17 knots, gusting to 22 knots. The Cessna then announced another go-around. According to the preliminary account, approximately four seconds later an impact sound was heard. The controller immediately informed another aircraft that the Cessna had experienced an accident and said the airport would be closed. A final transmission was subsequently heard from the accident aircraft before communications ended. Witness information cited in the preliminary aviation reconstruction indicates the aircraft may have entered a stall/spin during the attempted go-around before striking the ground near the holding point for Runway 28L. However, investigators have not determined that a stall or spin caused the accident, and no probable cause has been established. The NTSB investigation remains ongoing. The aircraft came to rest upright near the holding point for Runway 28L and was consumed by a post-crash fire. Preliminary photographs and observations indicate the cabin was heavily damaged by the fire, while the wings and tail remained attached to the aircraft. The available preliminary reconstruction says there was little evidence of a substantial debris field before the main wreckage. The identities of the two people killed have not been released by authorities. Investigators had not initially confirmed whether the pilot was experienced or whether the flight was being conducted as a training operation. The airport was temporarily closed following the crash while emergency crews handled the wreckage and fuel leak. The main runway later reopened after the emergency response and initial scene work. The NTSB will examine the aircraft, flight-track data, air-traffic-control communications, weather, pilot qualifications, maintenance records and other evidence to determine what led to the fatal crash.

Two Killed As Cessna 172 Crashes And Erupts In Flames At San Diego Airport

Five Killed As Flying Doctor Service Helicopter Crashes Near Long Lellang, Malaysia SEO DES: Helicopter was conducting a Flying Doctor Service mission when it crashed, killing the pilot, medical officer, assistant medical officer & 2 nurses onboard SOCIAL: Five people, including a pilot and four Malaysian Health Ministry personnel, were killed when a BO-105 helicopter (9M-LLF) crashed near Long Lellang STOLport in Sarawak on September 8, 2026. The helicopter was operated by Layang-Layang Aerospace Sdn Bhd and was conducting a Flying Doctor Service mission. The helicopter had departed Miri and was reportedly operating the Miri–Ba Lai–Long Siut–Long Lellang route. Those killed included a pilot, medical officer, assistant medical officer and two nurses travelling on official duty. Authorities confirmed the crash and fatalities, while search-and-rescue efforts were affected by the remote terrain and haze. Malaysia’s Air Accident Investigation Bureau will investigate the crash, while CAAM confirmed the aircraft and five people aboard. The cause remains unknown, and authorities have urged the public to avoid speculation as the investigation continues. Miri, Malaysia: Five people, including a pilot and four Malaysian Health Ministry personnel, were killed after a Flying Doctor Service helicopter crashed near Long Lellang STOLport in Sarawak, Malaysia, on September 8, 2026. The helicopter, a BO-105 identified as registration 9M-LLF, was operating a Flying Doctor Service mission when it crashed near the end of the airstrip at Long Lellang in the remote Marudi district of northern Sarawak. The aircraft was operated by Layang-Layang Aerospace Sdn Bhd, according to local reports. All five people aboard were killed. The victims included the pilot, a medical officer, an assistant medical officer and two nurses from Malaysia's Ministry of Health, who were travelling on official duty. Miri Division resident and chairman of the Miri Division Disaster Management Committee, Galong Luang, confirmed the deaths after receiving information from emergency and health authorities. “This is based on reports from the Fire and Rescue Department and the Ministry of Health,” Galong said. The crash occurred at approximately 3:40 p.m. near the end of Runway 04. The Civil Aviation Authority of Malaysia (CAAM) said it received notification of the occurrence from the Flight Information Service at 3:58 p.m. Health Minister Datuk Seri Dr Dzulkefly Ahmad said the helicopter had departed from Miri carrying one pilot and four Health Ministry personnel. “Based on the initial information received, the flight departing from Miri was operated by one pilot and carried four MOH health personnel, namely a medical officer, a medical assistant and two nurses who were on official duty,” he said. Initial information from Sarawak Police indicated that the privately owned helicopter had been chartered for Flying Doctor Service operations covering a route from Miri to Ba Lai, Long Siut and Long Lellang. Other local reports described the flight sector as Miri–Ba Lai–Long Siut–Long Lellang, indicating that Long Lellang was part of the helicopter's scheduled Flying Doctor Service mission. Sarawak Police Commissioner Datuk Mohamad Zainal Abdullah said the remote location and haze complicated the initial search-and-rescue response. “Air support using a helicopter from the Kuching Royal Malaysia Police Air Wing Base could not be carried out due to the hazy conditions and because the Civil Aviation Authority of Malaysia did not grant flight clearance,” Mohamad Zainal said. During the initial response, search-and-rescue efforts relied on assistance from local villagers, Malaysian Volunteer Corps personnel and auxiliary police at Long Lellang STOLport, while additional security personnel travelled to the crash site. The helicopter was later confirmed to have crashed near the end of the Long Lellang airstrip. The initial information from the Miri Airport Fire and Rescue Services indicated that the aircraft had taken off from Miri before crashing near the end of the runway at Long Lellang. The Long Lellang STOLport serves one of Sarawak's most isolated regions and is located next to Long Lellang village. The airfield provides access to remote communities, including Kelabit and Penan settlements, with the area lying hundreds of kilometres from Miri and difficult to access by road. The Flying Doctor Service plays a critical role in delivering medical services to isolated communities in Sarawak, where difficult terrain and limited road access often make air transport essential for healthcare teams. The Civil Aviation Authority of Malaysia confirmed that the aircraft involved was a BO-105 helicopter registered 9M-LLF and said five people, including the pilot, were aboard. The cause of the crash has not been established. Malaysia's Air Accident Investigation Bureau (AAIB), under the Ministry of Transport, will investigate the accident in accordance with Part XXVI of the Civil Aviation Regulations 2016. “The Air Accident Investigation Bureau, under the Transport Ministry, will investigate the incident,” CAAM said. Sarawak Police also urged the public not to speculate while authorities continue examining the circumstances of the accident. The investigation is expected to determine the sequence of events leading to the crash of the Flying Doctor Service helicopter and identify any contributing factors. No official cause has been announced.

Five Killed As Flying Doctor Service Helicopter Crashes Near Long Lellang, Malaysia

Airlines

EasyJet Faces $72 Million Lawsuit Over Six Airbus A319s Stranded Since 2022

EasyJet Faces $72 Million Lawsuit Over Six Airbus A319s Stranded Since 2022

Singapore Transport Minister Defends SIA’s Air India Investment Amid Funding Concerns

Singapore Transport Minister Defends SIA’s Air India Investment Amid Funding Concerns

Air India Terminates Phuket-Delhi Flight Pilot After Positive Drug Test Results

Air India Terminates Phuket-Delhi Flight Pilot After Positive Drug Test Results

Nairobi, Kenya: Kenya’s aviation workers have called off their two-day strike after signing a return-to-work agreement with the government, Kenya Aviation Workers’ Union (KAWU), Kenya Civil Aviation Authority (KCAA), Kenya Airports Authority (KAA) and Jambojet. Workers have been directed to resume normal duties immediately and help restore flight operations. The strike, which began on Sunday, August 30, 2026 and continued through Monday, August 31, 2026 was largely driven by air traffic controllers and disrupted flights at Jomo Kenyatta International Airport (JKIA) in Nairobi, with effects also reported at Moi International Airport in Mombasa, Kisumu International Airport and Eldoret International Airport. The disruption also spilled over into regional operations, with airlines serving Rwanda, Burundi, Tanzania, Uganda, Somalia and Mauritius cancelling or rescheduling flights. The workers’ grievances included the lack of a Collective Bargaining Agreement (CBA) with KCAA, delayed salary reviews, a dispute over union agency fees held by KAA and allegations of victimisation of KAWU members at Jambojet. Passengers at JKIA reported hours-long delays and cancellations, while Kenya Airways warned travellers of disruptions to its schedules. Transport Minister Davis Chirchir said the agreement provides a framework to address three CBAs that have been suspended since 2015. “We have looked at various issues ... with very clear guidelines ... on how we are going to deal with the three CBAs,” Chirchir said. KAWU Secretary General Moss Ndiema confirmed the strike was being withdrawn and called on employees to restore services. “We are simply calling off our strike action and pleading with our members to begin the process of normalising operations, restoring services,” Ndiema said. He also urged workers on duty to begin clearing flights. Under the return-to-work agreement, KAWU and KCAA will resume CBA negotiations, while the KAA agency-fee issue and the union’s recognition dispute with Jambojet will continue through the agreed processes. The agreement also provides protection against victimisation of workers who took part in the industrial action. The Kenyan government had earlier apologised to affected passengers as talks continued. With the strike now called off, airlines and airports are expected to work through the backlog and restore normal schedules.

Kenya Aviation Workers End 2-Day Strike After Disrupting Flights At Major Airports

Kenya Aviation Workers Resume Strike, Causing Delays And Cancellations At Nairobi’s JKIA

Kenya Aviation Workers Resume Strike, Causing Delays And Cancellations At Nairobi’s JKIA

Incidents

Delta Flight DL2311 Makes 27,000-Foot Emergency Descent After Pressurization Issue SEO DES: The aircraft descended from approximately 36,200 feet to 9,000 feet in about 10 minutes before diverting to Harry Reid International Airport in Las Vegas SOCIAL: Delta Air Lines Flight DL2311 made an emergency descent of approximately 27,000 feet on September 6, 2026, after an unexpected pressurization issue triggered the deployment of passenger oxygen masks. The Boeing 737-900 was flying from Los Angeles to Salt Lake City with 174 passengers and six crew members onboard. The aircraft descended from approximately 36,200 feet to 9,000 feet in about 10 minutes before diverting to Harry Reid International Airport in Las Vegas. The crew confirmed to air traffic control that oxygen masks had deployed, while Delta said its pilots followed established procedures to bring the aircraft to a safe altitude. The aircraft landed safely in Las Vegas at approximately 6:16 p.m. local time, with no injuries reported. Delta arranged for passengers to continue their journey, while the specific technical cause of the pressurization issue has not yet been publicly disclosed. Image: formulanone (Flickr) Video: Delta Air Lines Las Vegas, United States: Delta Air Lines Flight DL2311 made a rapid emergency descent of approximately 27,000 feet after an unexpected pressurization issue triggered the deployment of passenger oxygen masks, forcing the Los Angeles-to-Salt Lake City flight to divert to Las Vegas on September 6, 2026. The Boeing 737-900 operating the flight departed Los Angeles International Airport (LAX) at approximately 4:54 p.m. local time on Sunday, September 6, bound for Salt Lake City International Airport (SLC). The aircraft was carrying 174 passengers and six crew members. About halfway through the scheduled one-hour-and-22-minute journey, the aircraft was flying at approximately 36,200 feet when the pressurization issue occurred. Flight data showed the aircraft descending to 9,000 feet over approximately 10 minutes, a reduction in altitude of around 27,000 feet. Passenger oxygen masks deployed in the cabin during the emergency descent. Air traffic control communications recorded during the incident captured the crew reporting the situation and requesting an immediate descent toward Las Vegas. “Delta 2311 is currently in rapid descent. We'd like to get down to 9,000 and we're direct to Las Vegas,” a pilot said. When an air traffic controller asked, “Is the oxygen deployed?” the pilot responded, “Affirmative.” Delta said the emergency descent followed an unexpected pressurization issue. The airline has not publicly disclosed the specific technical cause behind the pressurization problem. “As safety comes before everything else at Delta, the flight crew of Delta flight 2311 LAX-SLC followed their training and procedures to safely bring the aircraft to optimal altitude when an unexpected pressurization issue occurred,” a Delta spokesperson said. The aircraft diverted to Harry Reid International Airport (LAS) in Las Vegas and landed safely at approximately 6:16 p.m. local time. Passengers deplaned normally after landing, and Delta arranged another aircraft for passengers to continue their journey to Salt Lake City. “Delta sincerely apologizes to our customers for their experience and thanks our flight crews and other support teams on the ground for their professionalism,” the spokesperson added. The rapid descent attracted widespread attention because of the significant altitude change within a short period. However, aviation safety procedures require crews dealing with a serious cabin pressurization problem at cruising altitude to descend quickly to an altitude where occupants can breathe safely without relying on supplemental oxygen. According to the Federal Aviation Administration, a lack of adequate oxygen can result in hypoxia, a condition caused by an insufficient supply of oxygen to the body. Matthew “Whiz” Buckley, a retired US A Navy F/A-18 fighter pilot with nearly 40 years of flying experience, told Fox News Digital, describing such a pressurization occurrence as “an extremely rare issue” in the United States. Buckley said that in such circumstances, pilots would need “to land as soon as practical, meaning, what's the closest airfield with a nice, long, suitable runway where we can get this thing on the ground safely.” The specific technical reason for the unexpected pressurization problem has not yet been publicly disclosed. The aircraft landed safely in Las Vegas, with no injuries reported in the information released by Delta.

Delta Flight DL2311 Makes 27,000-Foot Emergency Descent After Pressurization Issue

Delta Flight 1390 Declares Emergency After Cabin Fumes Detected Before Chicago Landing

Delta Flight 1390 Declares Emergency After Cabin Fumes Detected Before Chicago Landing

Qantas Flight Diverts To Christchurch After Engine Flames Seen Shortly After Takeoff

Qantas Flight Diverts To Christchurch After Engine Flames Seen Shortly After Takeoff

Crawley, United Kingdom: A Norse Atlantic Airways Boeing 787-9 rejected its takeoff from London Gatwick Airport on September 4, 2026 after a reported nose-gear problem, leaving the aircraft disabled on the runway and forcing the airport to temporarily halt flight operations. The aircraft, a Boeing 787-9 Dreamliner registered G-CKOF, was operating Norse Atlantic flight Z0701 from London Gatwick (LGW) to New York John F. Kennedy International Airport (JFK). It was accelerating for departure from Runway 26L when the crew rejected the takeoff at about 120 knots over the ground, according to preliminary aviation incident information. Reports said that the rejected takeoff followed a problem with the aircraft’s nose landing gear and that the nose wheels had turned about 90 degrees. The aircraft then stopped on the runway and became disabled. The precise technical cause of the nose-wheel movement has not been officially declared by the airline. The aircraft remained on Runway 26L while airport emergency teams responded. The incident did not result in any reported injuries among passengers or crew. A passenger onboard, Alice Kavanagh, described the moment the aircraft stopped as frightening, saying the pilot “slammed the brakes on” after a reported technical fault was detected. The Boeing 787 was subsequently removed from the runway. The aircraft blockage had an immediate effect on Gatwick because the airport effectively operates with one runway at a time. Although Gatwick has two runways, their proximity means they cannot normally be used simultaneously for independent operations. As a result, the closure of Runway 26L temporarily stopped both departing and arriving traffic. London Gatwick confirmed that the runway remained closed for 50 minutes because of the incident. “The runway was closed for 50 minutes this afternoon (Friday 4 September) due to a technical issue with a departing aircraft,” a Gatwick spokesperson said. “The aircraft was towed from the runway, which reopened shortly afterwards following a full safety inspection. As always, safety and security is our number one priority.” The runway reopened after airport teams completed the required safety inspection. Subsequent reporting put the reopening at approximately 14:36 BST, although the airport’s official statement characterized it simply as reopening shortly after the aircraft was removed and the inspection was completed. The temporary closure created a wider disruption across Gatwick’s flight schedule. Several inbound flights were diverted to alternative airports, with London Luton and London Stansted among the destinations reported for diverted services. EasyJet flights were also affected by the disruption. Flight-tracking data later showed severe delays affecting more than 330 flights at Gatwick, with an average delay of about 57 minutes. The effects continued after the runway reopened because aircraft, crews and passengers had been displaced during the closure. For the incident, Gatwick has confirmed only that a technical issue involving a departing aircraft caused the runway closure. The more specific information concerning the nose gear and the reported 90-degree movement of the nose wheels remains preliminary. Further maintenance findings or an official investigation would be needed to establish the exact cause of the rejected takeoff.

Norse Atlantic Rejects Takeoff At Gatwick After Reported Nose Gear Issue, Runway Closed

IndiGo Airlines, 6E1302, IndiGo 6E1302, Doha Bengaluru Flight, Doha Bengaluru, Muscat Diversion, Muscat International Airport, Hamad International Airport, Bengaluru Airport, Pilot Illness, Pilot Medical Issue, Crew

IndiGo Doha-Bengaluru Flight Diverted To Muscat Over Crew Medical Emergency

Join our WhatsApp Channel

Aviation Today Exclusive Interviews

Inside Aviation

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

3:51

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

3:10

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

5:32

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

3:42

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

4:05

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

4:06

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

3:46

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

5:37

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

5:44

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

5:23

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

6:03

TiHAN Highlights Autonomous Shuttles, Cargo Drones & Smart Mobility

5:38

Gandhi Automations Showcasing Advanced Hangar Door Technologies for Aviation Infrastructure

5:20

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

2:56

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

7:19

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

2:06

Latest News

Isar Aerospace Spectrum Rocket Reaches Orbit In Historic European Commercial Launch

Isar Aerospace Spectrum Rocket Reaches Orbit In Historic European Commercial Launch

September 12, 2026

Andenes, Norway: German space startup Isar Aerospace successfully launched its Spectrum rocket into orbit from Andoya Space in northern Norway

Four Miami Family Members Killed After Piper PA-34 Crashes In The Bahamas

Four Miami Family Members Killed After Piper PA-34 Crashes In The Bahamas

September 12, 2026

North Andros, The Bahamas: Four members of a Miami family died after their Piper PA-34 lost contact with air traffic

Agua Boa, Brazil: Three people were killed when a small Cessna 402B crashed and caught fire on a rural property near Água Boa in Brazil's central-western state of Mato Grosso on Thursday, September 10, 2026 according to local authorities. The aircraft was destroyed in the post-impact fire, and investigators are working to establish the circumstances of the crash, the flight's details and the identities of those onboard. The aircraft came down at a rural property about 18–20 kilometres from the urban area of Água Boa. Brazilian reports identified the aircraft as a Cessna 402B, manufactured in 1970, with serial number 402B0035. Later reports linked the aircraft to US registration N401NA, although Brazilian records and images from earlier aircraft sales have also shown other registration markings, including PS-WJR and PS-WJU. The registration discrepancy has not been resolved by authorities and should not be treated as proof of an illegal operation. The aircraft caught fire after the crash and was almost completely destroyed. The Corpo de Bombeiros was called at about 8:50 a.m. local time and used approximately 4,000 litres of water to extinguish the flames. After the fire was brought under control, firefighters found three bodies in the wreckage. The bodies were taken for forensic examination, while the Polícia Civil, Polícia Militar and Perícia Oficial e Identificação Técnica (Politec) worked at the site. Police initially said the condition of the wreckage made it impossible to identify the victims or determine key details of the flight. Delegado Carlos Alberto, who was handling the occurrence, said: “The state in which the aircraft was found initially made its identification impossible. For this reason, it was not possible, so far, to confirm information about any flight plan, the aircraft's place of origin or destination, nor the identity of the people who were onboard.” Later reporting established that three people were onboard, with all three confirmed dead. However, their names have not been officially released in the latest reports reviewed for this update. Earlier reports had used the wording “at least three killed” because authorities had initially been unable to determine the total number of occupants. The aircraft's operational purpose and operator also remain unconfirmed. Reports have not established whether it was conducting a private, charter, cargo or other type of flight. Likewise, authorities had not officially confirmed its departure point, intended destination or whether a flight plan had been filed. One local report claimed the aircraft may have departed from an airfield in Goiânia, but that detail has not been independently confirmed by the authorities and should therefore not be presented as established fact. Brazil's Centro de Investigação e Prevenção de Acidentes Aeronáuticos (CENIPA) was notified and is expected to participate in the complementary investigative work alongside the police and forensic authorities. The cause of the crash has not been determined, and there is currently no confirmed evidence identifying mechanical failure, weather, pilot action or another specific factor as the cause. Investigators are expected to examine the wreckage, aircraft documentation, registration history, possible flight-plan information and forensic evidence as they establish what happened before the Cessna 402B crashed and caught fire in rural Água Boa.

Three Killed After Cessna 402B Crashes And Catches Fire In Brazil’s Mato Grosso

September 11, 2026

Agua Boa, Brazil: Three people were killed when a small Cessna 402B crashed and caught fire on a rural property

Netherlands Signs Sweden Deal For Saab GlobalEye AEW&C Aircraft, Delivery Set For 2031

Netherlands Signs Sweden Deal For Saab GlobalEye AEW&C Aircraft, Delivery Set For 2031

September 11, 2026

The Hague, Netherlands: The Netherlands has signed a Letter of Intent with Sweden to acquire one Saab GlobalEye Airborne Early

Never miss any important news. Subscribe to our newsletter.

Email

Recent News

Isar Aerospace Spectrum Rocket Reaches Orbit In Historic European Commercial Launch

Isar Aerospace Spectrum Rocket Reaches Orbit In Historic European Commercial Launch

September 12, 2026

Four Miami Family Members Killed After Piper PA-34 Crashes In The Bahamas

Four Miami Family Members Killed After Piper PA-34 Crashes In The Bahamas

September 12, 2026

Agua Boa, Brazil: Three people were killed when a small Cessna 402B crashed and caught fire on a rural property near Água Boa in Brazil's central-western state of Mato Grosso on Thursday, September 10, 2026 according to local authorities. The aircraft was destroyed in the post-impact fire, and investigators are working to establish the circumstances of the crash, the flight's details and the identities of those onboard. The aircraft came down at a rural property about 18–20 kilometres from the urban area of Água Boa. Brazilian reports identified the aircraft as a Cessna 402B, manufactured in 1970, with serial number 402B0035. Later reports linked the aircraft to US registration N401NA, although Brazilian records and images from earlier aircraft sales have also shown other registration markings, including PS-WJR and PS-WJU. The registration discrepancy has not been resolved by authorities and should not be treated as proof of an illegal operation. The aircraft caught fire after the crash and was almost completely destroyed. The Corpo de Bombeiros was called at about 8:50 a.m. local time and used approximately 4,000 litres of water to extinguish the flames. After the fire was brought under control, firefighters found three bodies in the wreckage. The bodies were taken for forensic examination, while the Polícia Civil, Polícia Militar and Perícia Oficial e Identificação Técnica (Politec) worked at the site. Police initially said the condition of the wreckage made it impossible to identify the victims or determine key details of the flight. Delegado Carlos Alberto, who was handling the occurrence, said: “The state in which the aircraft was found initially made its identification impossible. For this reason, it was not possible, so far, to confirm information about any flight plan, the aircraft's place of origin or destination, nor the identity of the people who were onboard.” Later reporting established that three people were onboard, with all three confirmed dead. However, their names have not been officially released in the latest reports reviewed for this update. Earlier reports had used the wording “at least three killed” because authorities had initially been unable to determine the total number of occupants. The aircraft's operational purpose and operator also remain unconfirmed. Reports have not established whether it was conducting a private, charter, cargo or other type of flight. Likewise, authorities had not officially confirmed its departure point, intended destination or whether a flight plan had been filed. One local report claimed the aircraft may have departed from an airfield in Goiânia, but that detail has not been independently confirmed by the authorities and should therefore not be presented as established fact. Brazil's Centro de Investigação e Prevenção de Acidentes Aeronáuticos (CENIPA) was notified and is expected to participate in the complementary investigative work alongside the police and forensic authorities. The cause of the crash has not been determined, and there is currently no confirmed evidence identifying mechanical failure, weather, pilot action or another specific factor as the cause. Investigators are expected to examine the wreckage, aircraft documentation, registration history, possible flight-plan information and forensic evidence as they establish what happened before the Cessna 402B crashed and caught fire in rural Água Boa.

Three Killed After Cessna 402B Crashes And Catches Fire In Brazil’s Mato Grosso

September 11, 2026

Netherlands Signs Sweden Deal For Saab GlobalEye AEW&C Aircraft, Delivery Set For 2031

Netherlands Signs Sweden Deal For Saab GlobalEye AEW&C Aircraft, Delivery Set For 2031

September 11, 2026

Sydney, Australia: Sydney Airport faced another round of flight cancellations and significant delays on Friday, September 11, 2026 after a shortage of available air traffic controllers forced Airservices Australia to impose temporary air traffic-flow restrictions. Airservices said the measures were introduced “to safely manage aviation demand” after unexpected staff absences left the Sydney control tower without enough operational controllers. Around 14 inbound flights were cancelled, while delays exceeded one hour in the morning. The restrictions were lifted at 8:15 a.m. local time, with some minor delays continuing. Airservices Deputy Chief Executive Peter Curran told a Senate committee that the immediate disruption followed unplanned overnight absenteeism. “Last night, at relatively short notice, we had some unplanned absenteeism, which we weren't able to recover from,” Curran said. “We're down in the tower this morning and that led to some significant delays.” Sydney currently has 49 employed air traffic controllers, but 41 are required to be operational, while eight were unavailable because of longer-term absences, leaving little capacity to absorb unexpected sickness or other staff shortages. The latest disruption follows similar problems in recent weeks. Airservices acknowledged “roster constraints” when Sydney experienced major delays in August, including a day when more than 150 flights were affected. On September 10, 2026 Qantas and Virgin Australia each reported six Sydney cancellations, with dozens of other flights delayed. Airservices said it was “enhancing our training pipeline to add further controllers to improve roster depth” and was working to address rostering problems that reduce workforce flexibility. The staffing problem is not new. Airservices CEO Rob Sharp previously said the shortage developed during the COVID-19 pandemic after the organisation offered early-retirement arrangements to controllers nearing retirement. Sharp said the organisation subsequently found itself short of experienced personnel. He has also stressed that training replacements take considerable time; Airservices has been recruiting aggressively, with additional controllers moving through training and a new Sydney Tower simulator installed to increase training capacity. The issue has also become a safety concern. The ATSB is investigating a series of Sydney Airport occurrences dating back to July 27, 2026 when a Qantas Boeing 737 was cleared to cross runway 34L while a QantasLink Dash 8 was landing. ATC detected the conflict and stopped the Boeing before it entered the runway. The ATSB classified that occurrence as a serious incident. Further incidents followed in August. On August 9, 2026 a Virgin Australia Boeing 737 beginning its take-off roll on runway 34L encountered a Qantas Boeing 737 crossing the runway; the Virgin crew rejected the take-off. The ATSB is investigating the occurrence as a runway incursion. The same day, a Jetstar Airbus A320 came into close proximity with a Qatar Airways Boeing 777 being towed, forcing both aircraft to stop; a Jetstar cabin crew member was injured. The ATSB is also investigating a 16 August taxiing conflict involving Virgin Australia and Qantas Boeing 737s, an 18 August conflict involving Qantas Airbus A321 and Boeing 737 aircraft, and a 25 August incident in which incomplete traffic information was passed to a Jetstar A320 before pushback. In the latter two cases, the ATSB said safety defences remained effective and classified the events as incidents rather than serious incidents. Airservices has said safety is not being compromised by the staffing shortage, with traffic-flow restrictions being used to reduce aircraft movements when staffing levels cannot support normal capacity. Earlier, Sharp said, “We put in place measures that reduce the traffic levels to ensure safety, but this can lead to flight delays.” The scale of the staffing problem was highlighted before the Senate committee on September 11, 2026. Airservices said Australian airports recorded 2,536 cancellations in the year to August 31, 2026 of which 121 were attributed to Airservices, including 103 at Sydney. That equates to roughly one Airservices-attributable cancellation every three days nationally. Airservices is now seeking to increase controller numbers, strengthen standby coverage and improve rosters. The organisation has also been using controllers from other facilities to help cover Sydney, while the government and aviation industry face pressure to resolve the shortage before further growth in Sydney-area aviation places additional demand on the system. The ATSB investigations into the safety incidents remain ongoing, and no final finding has established that staffing shortages caused any of the individual occurrences.

Sydney Airport Imposes Flight Restrictions After Air Traffic Controller Shortage

September 11, 2026

Do you have the Pilot in you?

Explore More

Webinar

Industry Expert’s Voice

Indian Aviation Statistics

Submit Aviation Blog

Editor's Pick

Isar Aerospace Spectrum Rocket Reaches Orbit In Historic European Commercial Launch

Aerospace

Posted onSeptember 12, 2026September 12, 2026

Isar Aerospace Spectrum Rocket Reaches Orbit In Historic European Commercial Launch

Four Miami Family Members Killed After Piper PA-34 Crashes In The Bahamas

Aircraft Crashes

Posted onSeptember 12, 2026September 12, 2026

Four Miami Family Members Killed After Piper PA-34 Crashes In The Bahamas

Three Killed After Cessna 402B Crashes And Catches Fire In Brazil’s Mato Grosso

Aircraft Crashes

Posted onSeptember 11, 2026September 11, 2026

Three Killed After Cessna 402B Crashes And Catches Fire In Brazil’s Mato Grosso

Netherlands Signs Sweden Deal For Saab GlobalEye AEW&C Aircraft, Delivery Set For 2031

Military Aviation

Posted onSeptember 11, 2026September 11, 2026

Netherlands Signs Sweden Deal For Saab GlobalEye AEW&C Aircraft, Delivery Set For 2031

Airlines

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

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

August 27, 2025

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

UK Air Traffic Failure Causes 1,300 Cancellations, Disrupts Europe And Global Routes

UK Air Traffic Failure Causes 1,300 Cancellations, Disrupts Europe And Global Routes

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

Leipzig, Germany: The German government on Tuesday, September 1, 2026, blamed Russia for an attempted explosive-drone attack at Leipzig/Halle Airport on August 4, 2026 saying investigators had established links to Russian state entities and that the incident formed part of a broader campaign of hybrid operations against Europe. German Interior Minister Alexander Dobrindt said police investigations, the pattern of the incident and intelligence findings pointed to Russian responsibility. “Taken together, the police investigations, the pattern and intelligence findings prove a Russian responsibility for the attempted attack at Leipzig airport,” Dobrindt said. He added that intelligence indicated that people involved in the operation had acted “on behalf of Russian state entities.” Dobrindt said investigators had identified the drone’s configuration, components, explosives and detonator as elements “known to us from other Russian hybrid operations and its war against Ukraine.” He said the technology found at the scene demonstrated “a high degree of technical expertise” and considerable planning, while suggesting that lower-level operatives may have been used to carry out the operation. Foreign Minister Johann Wadephul said Germany did not regard the Leipzig incident as an isolated case. “It fits into a broader pattern of Russian hybrid operations in Europe,” he said. Wadephul described Germany as facing the “daily reality of hybrid warfare” and said the government would respond with measures that were “proportionate and measured, yet equally resolute.” The attribution came after Chancellor Friedrich Merz said on Sunday, August 30, that the investigation was nearing completion. “We are in the process of concluding the investigation,” Merz said, adding that there was broad agreement within the Federal Government on the response and that it would be made clear “in the coming days.” He also said Germany’s European Union and NATO partners had been informed and would be prepared for the government’s announcement. The incident itself occurred on August 4, 2026 when an explosives-laden drone was discovered inside the secure area of Leipzig/Halle Airport near Ukrainian Antonov cargo aircraft. The device was defused by bomb-disposal specialists after its detonator failed to trigger the explosives. Reports have put the explosive load at about 600 grams, with investigators later finding traces of the military explosive hexogen at another location near the airport. The Ukrainian Antonov aircraft at Leipzig/Halle are used to transport military supplies to Ukraine. Investigators have examined whether the drone was intended to strike one of those aircraft. The failed detonation meant the suspected attack did not cause the potentially catastrophic damage German officials warned could have resulted if the explosives had detonated. A second drone was also investigated after a DHL cargo aircraft encountered an unidentified object and had to divert. Early reports suggested the object could have been another drone involved in the operation, although investigators later questioned whether the second incident was directly connected to the planned attack. A third drone was subsequently found in a field near the airport, with forensic investigators detecting traces that were initially assessed as possibly being hexogen. The airport briefly faced operational disruption during the initial incident, while authorities secured the area and carried out explosive-disposal operations. Leipzig/Halle is a major European cargo hub and has become an important logistics location for Ukrainian Antonov aircraft after Russia destroyed the airline’s home base at Hostomel in Ukraine following its 2022 invasion. Germany has now announced diplomatic and economic measures in response to the attribution. Berlin said Russia’s consulate general in Bonn would be closed, while the agreement covering the Russian House cultural centre in Berlin would be terminated. Germany also plans to push for additional EU sanctions and travel restrictions targeting Russian nationals and increase pressure on Russia’s so-called shadow fleet. The Russian ambassador was summoned to the German Foreign Ministry following the announcement. Russia rejected the accusation. Kremlin spokesman Dmitry Peskov said the allegations had not been supported by evidence and described Germany’s actions as an escalation, while Russian Foreign Ministry spokeswoman Maria Zakharova said Moscow would respond to what she called Berlin’s “anti-Russian action.” Germany’s accusation has received support from European allies and NATO. NATO Secretary General Mark Rutte said Berlin had presented clear evidence of Moscow’s role, while European Commission President Ursula von der Leyen expressed solidarity with Germany. Leaders and officials from Poland, Italy, the UK, Sweden, France and Canada also backed Berlin’s response and warned against further Russian hybrid activity in Europe. Tuesday’s announcement marks the first time the German government has officially and directly identified Russia as responsible for the Leipzig/Halle airport incident. Berlin has linked the case to a wider security concern involving alleged Russian sabotage, espionage, cyber activity, disinformation and attacks on critical infrastructure across Europe.

Germany Blames Russia For Attempted Explosive Drone Attack At Leipzig/Halle Airport

September 2, 2026

EEOC Sues Gate Gourmet Over Alleged Sexual Harassment At Denver Airport

EEOC Sues Gate Gourmet Over Alleged Sexual Harassment At Denver Airport

August 29, 2026

Airports

Isar Aerospace Spectrum Rocket Reaches Orbit In Historic European Commercial Launch

Isar Aerospace Spectrum Rocket Reaches Orbit In Historic European Commercial Launch

September 12, 2026

Andenes, Norway: German space startup Isar Aerospace successfully launched its Spectrum rocket into orbit from Andoya Space in northern Norway

Four Miami Family Members Killed After Piper PA-34 Crashes In The Bahamas

Four Miami Family Members Killed After Piper PA-34 Crashes In The Bahamas

September 12, 2026

Agua Boa, Brazil: Three people were killed when a small Cessna 402B crashed and caught fire on a rural property near Água Boa in Brazil's central-western state of Mato Grosso on Thursday, September 10, 2026 according to local authorities. The aircraft was destroyed in the post-impact fire, and investigators are working to establish the circumstances of the crash, the flight's details and the identities of those onboard. The aircraft came down at a rural property about 18–20 kilometres from the urban area of Água Boa. Brazilian reports identified the aircraft as a Cessna 402B, manufactured in 1970, with serial number 402B0035. Later reports linked the aircraft to US registration N401NA, although Brazilian records and images from earlier aircraft sales have also shown other registration markings, including PS-WJR and PS-WJU. The registration discrepancy has not been resolved by authorities and should not be treated as proof of an illegal operation. The aircraft caught fire after the crash and was almost completely destroyed. The Corpo de Bombeiros was called at about 8:50 a.m. local time and used approximately 4,000 litres of water to extinguish the flames. After the fire was brought under control, firefighters found three bodies in the wreckage. The bodies were taken for forensic examination, while the Polícia Civil, Polícia Militar and Perícia Oficial e Identificação Técnica (Politec) worked at the site. Police initially said the condition of the wreckage made it impossible to identify the victims or determine key details of the flight. Delegado Carlos Alberto, who was handling the occurrence, said: “The state in which the aircraft was found initially made its identification impossible. For this reason, it was not possible, so far, to confirm information about any flight plan, the aircraft's place of origin or destination, nor the identity of the people who were onboard.” Later reporting established that three people were onboard, with all three confirmed dead. However, their names have not been officially released in the latest reports reviewed for this update. Earlier reports had used the wording “at least three killed” because authorities had initially been unable to determine the total number of occupants. The aircraft's operational purpose and operator also remain unconfirmed. Reports have not established whether it was conducting a private, charter, cargo or other type of flight. Likewise, authorities had not officially confirmed its departure point, intended destination or whether a flight plan had been filed. One local report claimed the aircraft may have departed from an airfield in Goiânia, but that detail has not been independently confirmed by the authorities and should therefore not be presented as established fact. Brazil's Centro de Investigação e Prevenção de Acidentes Aeronáuticos (CENIPA) was notified and is expected to participate in the complementary investigative work alongside the police and forensic authorities. The cause of the crash has not been determined, and there is currently no confirmed evidence identifying mechanical failure, weather, pilot action or another specific factor as the cause. Investigators are expected to examine the wreckage, aircraft documentation, registration history, possible flight-plan information and forensic evidence as they establish what happened before the Cessna 402B crashed and caught fire in rural Água Boa.

Three Killed After Cessna 402B Crashes And Catches Fire In Brazil’s Mato Grosso

September 11, 2026

Netherlands Signs Sweden Deal For Saab GlobalEye AEW&C Aircraft, Delivery Set For 2031

Netherlands Signs Sweden Deal For Saab GlobalEye AEW&C Aircraft, Delivery Set For 2031

September 11, 2026

Sydney, Australia: Sydney Airport faced another round of flight cancellations and significant delays on Friday, September 11, 2026 after a shortage of available air traffic controllers forced Airservices Australia to impose temporary air traffic-flow restrictions. Airservices said the measures were introduced “to safely manage aviation demand” after unexpected staff absences left the Sydney control tower without enough operational controllers. Around 14 inbound flights were cancelled, while delays exceeded one hour in the morning. The restrictions were lifted at 8:15 a.m. local time, with some minor delays continuing. Airservices Deputy Chief Executive Peter Curran told a Senate committee that the immediate disruption followed unplanned overnight absenteeism. “Last night, at relatively short notice, we had some unplanned absenteeism, which we weren't able to recover from,” Curran said. “We're down in the tower this morning and that led to some significant delays.” Sydney currently has 49 employed air traffic controllers, but 41 are required to be operational, while eight were unavailable because of longer-term absences, leaving little capacity to absorb unexpected sickness or other staff shortages. The latest disruption follows similar problems in recent weeks. Airservices acknowledged “roster constraints” when Sydney experienced major delays in August, including a day when more than 150 flights were affected. On September 10, 2026 Qantas and Virgin Australia each reported six Sydney cancellations, with dozens of other flights delayed. Airservices said it was “enhancing our training pipeline to add further controllers to improve roster depth” and was working to address rostering problems that reduce workforce flexibility. The staffing problem is not new. Airservices CEO Rob Sharp previously said the shortage developed during the COVID-19 pandemic after the organisation offered early-retirement arrangements to controllers nearing retirement. Sharp said the organisation subsequently found itself short of experienced personnel. He has also stressed that training replacements take considerable time; Airservices has been recruiting aggressively, with additional controllers moving through training and a new Sydney Tower simulator installed to increase training capacity. The issue has also become a safety concern. The ATSB is investigating a series of Sydney Airport occurrences dating back to July 27, 2026 when a Qantas Boeing 737 was cleared to cross runway 34L while a QantasLink Dash 8 was landing. ATC detected the conflict and stopped the Boeing before it entered the runway. The ATSB classified that occurrence as a serious incident. Further incidents followed in August. On August 9, 2026 a Virgin Australia Boeing 737 beginning its take-off roll on runway 34L encountered a Qantas Boeing 737 crossing the runway; the Virgin crew rejected the take-off. The ATSB is investigating the occurrence as a runway incursion. The same day, a Jetstar Airbus A320 came into close proximity with a Qatar Airways Boeing 777 being towed, forcing both aircraft to stop; a Jetstar cabin crew member was injured. The ATSB is also investigating a 16 August taxiing conflict involving Virgin Australia and Qantas Boeing 737s, an 18 August conflict involving Qantas Airbus A321 and Boeing 737 aircraft, and a 25 August incident in which incomplete traffic information was passed to a Jetstar A320 before pushback. In the latter two cases, the ATSB said safety defences remained effective and classified the events as incidents rather than serious incidents. Airservices has said safety is not being compromised by the staffing shortage, with traffic-flow restrictions being used to reduce aircraft movements when staffing levels cannot support normal capacity. Earlier, Sharp said, “We put in place measures that reduce the traffic levels to ensure safety, but this can lead to flight delays.” The scale of the staffing problem was highlighted before the Senate committee on September 11, 2026. Airservices said Australian airports recorded 2,536 cancellations in the year to August 31, 2026 of which 121 were attributed to Airservices, including 103 at Sydney. That equates to roughly one Airservices-attributable cancellation every three days nationally. Airservices is now seeking to increase controller numbers, strengthen standby coverage and improve rosters. The organisation has also been using controllers from other facilities to help cover Sydney, while the government and aviation industry face pressure to resolve the shortage before further growth in Sydney-area aviation places additional demand on the system. The ATSB investigations into the safety incidents remain ongoing, and no final finding has established that staffing shortages caused any of the individual occurrences.

Sydney Airport Imposes Flight Restrictions After Air Traffic Controller Shortage

September 11, 2026

More News

Isar Aerospace Spectrum Rocket Reaches Orbit In Historic European Commercial Launch

Isar Aerospace Spectrum Rocket Reaches Orbit In Historic European Commercial Launch

September 12, 2026

Four Miami Family Members Killed After Piper PA-34 Crashes In The Bahamas

Four Miami Family Members Killed After Piper PA-34 Crashes In The Bahamas

September 12, 2026

Agua Boa, Brazil: Three people were killed when a small Cessna 402B crashed and caught fire on a rural property near Água Boa in Brazil's central-western state of Mato Grosso on Thursday, September 10, 2026 according to local authorities. The aircraft was destroyed in the post-impact fire, and investigators are working to establish the circumstances of the crash, the flight's details and the identities of those onboard. The aircraft came down at a rural property about 18–20 kilometres from the urban area of Água Boa. Brazilian reports identified the aircraft as a Cessna 402B, manufactured in 1970, with serial number 402B0035. Later reports linked the aircraft to US registration N401NA, although Brazilian records and images from earlier aircraft sales have also shown other registration markings, including PS-WJR and PS-WJU. The registration discrepancy has not been resolved by authorities and should not be treated as proof of an illegal operation. The aircraft caught fire after the crash and was almost completely destroyed. The Corpo de Bombeiros was called at about 8:50 a.m. local time and used approximately 4,000 litres of water to extinguish the flames. After the fire was brought under control, firefighters found three bodies in the wreckage. The bodies were taken for forensic examination, while the Polícia Civil, Polícia Militar and Perícia Oficial e Identificação Técnica (Politec) worked at the site. Police initially said the condition of the wreckage made it impossible to identify the victims or determine key details of the flight. Delegado Carlos Alberto, who was handling the occurrence, said: “The state in which the aircraft was found initially made its identification impossible. For this reason, it was not possible, so far, to confirm information about any flight plan, the aircraft's place of origin or destination, nor the identity of the people who were onboard.” Later reporting established that three people were onboard, with all three confirmed dead. However, their names have not been officially released in the latest reports reviewed for this update. Earlier reports had used the wording “at least three killed” because authorities had initially been unable to determine the total number of occupants. The aircraft's operational purpose and operator also remain unconfirmed. Reports have not established whether it was conducting a private, charter, cargo or other type of flight. Likewise, authorities had not officially confirmed its departure point, intended destination or whether a flight plan had been filed. One local report claimed the aircraft may have departed from an airfield in Goiânia, but that detail has not been independently confirmed by the authorities and should therefore not be presented as established fact. Brazil's Centro de Investigação e Prevenção de Acidentes Aeronáuticos (CENIPA) was notified and is expected to participate in the complementary investigative work alongside the police and forensic authorities. The cause of the crash has not been determined, and there is currently no confirmed evidence identifying mechanical failure, weather, pilot action or another specific factor as the cause. Investigators are expected to examine the wreckage, aircraft documentation, registration history, possible flight-plan information and forensic evidence as they establish what happened before the Cessna 402B crashed and caught fire in rural Água Boa.

Three Killed After Cessna 402B Crashes And Catches Fire In Brazil’s Mato Grosso

September 11, 2026

Netherlands Signs Sweden Deal For Saab GlobalEye AEW&C Aircraft, Delivery Set For 2031

Netherlands Signs Sweden Deal For Saab GlobalEye AEW&C Aircraft, Delivery Set For 2031

September 11, 2026

Subscribe to our Newsletter

Email

Subscribe to our Newsletter

Email

Follow Us

Facebook-f Instagram Linkedin-in X-twitter Youtube

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

Quick Links

About Us
Contact Us
Services
Advertise
FAQ

Navigate

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

General Support

info@aviationtoday.in

News Desk Support

news@aviationtoday.in

Follow Us

Facebook-f Instagram Linkedin-in X-twitter Youtube

© Copyright 2026 Aviation Today. All rights reserved.

Terms of Use
Privacy Policy
Disclaimer

Coming Soon!

Explore

Newsletter

First Name

Last Name

Phone/Mobile

Email

Topic

Your Message

Attach Document

Choose File

Search

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

Aviation Newsletter

Facebook Instagram Linkedin X-twitter Youtube