Latest Aviation News | Updated Global Aviation News

Skip to content

Facebook Instagram Linkedin X-twitter Youtube

About Us
Contact Us
Advertisement

About Us
Contact Us
Advertisement

Aviation Newsletter

WhatsApp Channel

Search

Latest News
Aviation Today Perspectives
Aviation Jobs
About Us

Latest News
Aviation Today Perspectives
Aviation Jobs
About Us

Search

Latest News
Aviation Today Perspectives
Aviation Jobs
About Us

Latest News
Aviation Today Perspectives
Aviation Jobs
About Us

News

Civil Aviation

Pilot Training

Flight School Analysis

Aviation Jobs

Training

Services

About Us

Contact Us

Search

Latest News

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

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.

Airports

Sydney Airport Imposes Flight Restrictions After Air Traffic Controller Shortage

September 11, 2026

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.

Incidents

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

September 11, 2026

DGCA Reportedly Directs One-Time Drug Testing Of All Pilots Following Air India Incident

India

India’s DGCA Reportedly Directs One-Time Drug Testing Of All Pilots By July 2027

September 10, 2026

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

Incidents

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

September 10, 2026

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

Airlines

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

September 10, 2026

Amazon Air 767 Crew Warned Of Excessive Speed Before Miami Runway Overrun, NTSB Reveals SEO DES: The Sept 6 crash killed 5 airport cleaning workers on ground, injured 5 others, while both pilots survived; NTSB continues its examination of the crash SOCIAL: One of the pilots of Amazon Prime Air Flight 7598 repeatedly warned that the Boeing 767 was travelling too fast during its final approach to Miami International Airport, according to newly released NTSB cockpit recorder information. The recording captured repeated concerns about excessive speed, followed by “sink rate” and “too low terrain” warnings before the aircraft touched down on Runway 30. Flight data showed the aircraft touched down at a groundspeed of 158 knots before the crew briefly initiated a go-around. The throttles were increased to go-around thrust but were reduced to idle four seconds later, with the brakes reapplied. The NTSB found no indication that the speed brakes or thrust reversers were deployed before the aircraft left the paved surface, travelled about 1,300 feet beyond the runway and struck vehicles. The September 6, 2026 crash killed five airport cleaning workers, while five other people were injured and both pilots survived. The NTSB has interviewed the flight crew and continues examining the approach, automated warnings, attempted go-around, runway excursion and other factors. Investigators have not yet determined the probable cause. Miami, United States: One of the pilots of Amazon Prime Air Flight 7598 repeatedly warned that the Boeing 767 was travelling too fast during its final approach to Miami International Airport, according to newly released cockpit recorder information from the US National Transportation Safety Board (NTSB). The NTSB said that about one minute and 42 seconds before the cockpit voice recorder ended, one pilot called for the flaps to be set to 20 degrees while the other cautioned that the aircraft was “too fast.” The pilot continued making comments about the aircraft's excessive speed throughout the remainder of the recording, but investigators said there was no consistent verbal response to those concerns. The newly released preliminary evidence provides the clearest account yet of the final moments before the cargo aircraft overran Runway 30 on September 6, 2026, struck vehicles beyond the airport and killed five people on the ground. The Boeing 767-33A, operated by 21 Air as Amazon Prime Air Flight 7598, had arrived from San Juan, Puerto Rico, on its third flight of the day. Only the two pilots were onboard the aircraft. The NTSB recovered both the cockpit voice recorder and flight data recorder and successfully read them at its laboratory in Washington. The cockpit recorder contained more than two hours of good-quality audio across four channels, while the flight recorder contained about 54 hours of information covering more than 400 parameters. According to the preliminary timeline, the crew was cleared to land on Runway 30 about four minutes before the recording ended. The landing gear was lowered, and the crew progressively selected additional flap settings. About 1 minute and 23 seconds before the end of the recording, sounds consistent with the autopilot disconnect were captured. The aircraft then descended amid a series of automated warnings. The cockpit recorded two “sink rate” warnings, followed by the electronic 500-foot, 100-foot and minimums callouts. About 48 seconds before the recording ended, the automated “too low terrain” warning sounded four times, followed by another such warning seconds later. Sounds consistent with touchdown were recorded about 31 seconds before the end of the cockpit recording. Flight data showed the aircraft's nose and right main landing gear touched down at a groundspeed of 158 knots. The brakes were applied as the aircraft slowed to 146 knots, while the left main gear touched down at 134 knots. About 15 seconds before the end of the recording, a pilot called for a go-around. At the same time, the brakes were released at a groundspeed of 120 knots and the throttles were increased to a setting consistent with go-around thrust. However, four seconds later, the throttles were reduced to idle and the brakes were reapplied while the aircraft was still travelling at 117 knots. About seven seconds before the flight recorder ended, the recorded acceleration values changed markedly. The aircraft subsequently left the paved surface, according to the preliminary data. The NTSB said the final recorded groundspeed was 65 knots and found no indication in the recorded data that either the speed brakes or thrust reversers were deployed. The aircraft travelled about 1,300 feet beyond the runway, struck a van carrying airport cleaning workers, continued through the airport perimeter area and later struck a Toyota Corolla Cross before catching fire. The NTSB stressed that all recorder information released so far is preliminary and subject to change. It has not yet determined the probable cause of the accident. The confirmed death toll remains five, according to the latest available information from Miami-Dade authorities. All five people killed were occupants of the van struck by the Boeing 767. The victims were identified as, Rolando Aleman Leon, 55; Yoel Rodriguez Naranjo, 53; Julio C. Pineda, 75; Carlos Acosta Fajardo, 53 and Javierkys Reyes Quevedo, 47. They were employees of Professional Ocean Service Corp., an aircraft-cleaning contractor at Miami International Airport. Reports said the workers were finishing their shift when the crash occurred. Five other people were injured in the accident. The two pilots survived and were released from hospital. The latest local authority updates reported that two other injured people remained in critical condition, while another was in stable condition. NTSB investigators have interviewed the captain and first officer and will conduct a detailed review of the cockpit recording before producing a written transcript. The investigation is continuing into the circumstances surrounding the approach and landing, including the aircraft's speed, the automated cockpit warnings, the attempted go-around and why the speed brakes and thrust reversers were not indicated as deployed in the recorded data. Investigators are also examining the broader circumstances surrounding the runway excursion, including weather and runway safety factors. The NTSB has previously said it will review whether the absence of an Engineered Materials Arresting System (EMAS) at the runway end was relevant, although Miami International Airport met applicable FAA runway safety requirements. The final NTSB report, which will determine the probable cause and issue any safety recommendations, is expected to take considerably longer. For now, the investigation remains ongoing.

Investigation

Amazon Air 767 Crew Warned Of Excessive Speed Before Miami Runway Overrun, NTSB Reveals

September 10, 2026

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

Aircraft Crashes

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

September 9, 2026

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.

Aircraft Crashes

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

September 9, 2026

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

Airports

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

September 9, 2026

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.

Aircraft Crashes

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

September 9, 2026

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

Airlines

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

September 8, 2026

« Previous Next »

Subscribe to our Newsletter

Email

Recent News

UK Backs £60M Mission To Remove Two Defunct Satellites From Earth's Orbit By 2032

UK Backs £60M Mission To Remove Two Defunct Satellites From Earth’s Orbit By 2032

October 18, 2026

Two Killed In Aircraft Crash Near Drymen After Departure From Glasgow Airport

Two Killed In Aircraft Crash Near Drymen After Departure From Glasgow Airport

October 17, 2026

Houthi Missiles Strike Aden Airport Near Yemenia Flight, Passengers Evacuated Safely

Houthi Missiles Strike Aden Airport Near Yemenia Flight, Passengers Evacuated Safely

October 17, 2026

Wausau, United States: The National Transportation Safety Board (NTSB) preliminary report, reported publicly on 13 October 2026, details the pilot’s account, fuel-system inspection and aircraft damage. During a post-accident interview with a Federal Aviation Administration (FAA) inspector, the pilot’s aviation mechanic said the pilot attributed the power loss to his delay in switching tanks and not turning on the electric fuel-boost pump. The NTSB has not issued a final probable-cause determination, and the investigation remains ongoing. A delayed switch between fuel tanks and failure to activate the electric fuel-boost pump were cited by the pilot as reasons for the loss of engine power that forced a Beechcraft K35 carrying US lawmaker Tom Tiffany to make an emergency water landing in Lake Wausau, Wisconsin, on 12 September 2026. The aircraft, registered N6071E, was substantially damaged in the accident. Both occupants, pilot Leonard Boltz, 73, and passenger Tiffany, 68 sustained minor injuries and escaped from the aircraft before being rescued. The NTSB report states that the accident occurred at approximately 8:49 p.m. Central Daylight Time on 12 September 2026, near Wausau, Wisconsin. The Beech K35 was operating a personal flight under Part 91 of the US Federal Aviation Regulations from La Crosse Regional Airport to Wausau Downtown Airport. According to the report, the pilot was flying in the airport traffic pattern for landing at Wausau Downtown Airport. Shortly after extending the landing gear while abeam the runway threshold, he observed a “higher-than-normal engine exhaust gas temperature (EGT).” The report states: “According to the pilot, the higher-than-normal engine EGT reminded him to switch fuel tanks.” The pilot selected the right main fuel tank and moved the mixture and throttle levers fully forward, but the engine did not respond. He told investigators that he did not activate the electric fuel-boost pump while attempting to restore engine power. The pilot then maneuvered the aircraft towards the runway and prepared for a water landing. The aircraft struck the water, substantially damaging its fuselage, left wing, left aileron and engine mount. After the aircraft was recovered from Lake Wausau, investigators examined its fuel system and cockpit controls. The inspection found: The left main fuel tank was empty. The right main tank and both auxiliary fuel tanks were full of fuel. All fuel-tank caps were secure. The electric fuel-boost pump switch was in the OFF position. The fuel selector valve was positioned to the right main fuel tank. The throttle, mixture and propeller controls were nearly fully forward. These findings document the aircraft’s condition after the accident. The NTSB has not yet issued a final determination establishing the complete sequence of events that led to the loss of engine power. Earlier on 12 September, the pilot flew the aircraft from Langlade County Airport in Antigo, Wisconsin, to La Crosse Regional Airport. The aircraft departed Antigo with 70 gallons of fuel distributed across four tanks: 25 gallons in each main tank and 10 gallons in each auxiliary tank. The pilot did not refuel at La Crosse before departing for Wausau. He told investigators that he had selected the left main fuel tank for both flight legs, except for a brief period when he selected the auxiliary tanks during cruise flight before returning to the left tank. The flight from La Crosse to Wausau departed at approximately 8:15 p.m. local time. During the approach to Wausau, the pilot noticed the elevated exhaust gas temperature and switched to the right main tank. Despite advancing the engine controls, power was not restored. The NTSB report records the pilot’s explanation to his aviation mechanic following the accident: “the loss of engine power was due to his delay in switching fuel tanks and not turning on the electric fuel boost pump.” The aircraft landed in Lake Wausau after the pilot was unable to restore engine power. Both the occupants managed to exit the aircraft and reach shallow water. They called 911 and were rescued by a Wausau Fire Department airboat shortly after the accident. Both men sustained minor injuries. The aircraft remained in the water until recovery crews removed it on 14 September, with the recovery operation involving divers and other personnel. It was subsequently secured in a hangar for examination. The NTSB’s preliminary findings identify the pilot’s reported fuel-management errors and document the condition of the fuel tanks, selector valve and boost-pump switch after the accident. However, preliminary reports are subject to change as an investigation progresses. The report does not constitute a final probable-cause determination. Further investigative work may clarify the circumstances surrounding the engine-power loss and the emergency landing.

NTSB Preliminary Report Details Fuel Issues In Aircraft Carrying US Lawmaker

October 17, 2026

Nine Safe After Bombardier Challenger 604 Loses Door Shortly After Abuja Departure

Nine Safe After Bombardier Challenger 604 Loses Door Shortly After Abuja Departure

October 17, 2026

Aviation Today Perspectives

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

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

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

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

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

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

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

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

Automation Rises, But Are Indian Pilots Being Trained To Keep Pace With The Future?

Automation Rises, But Are Indian Pilots Being Trained To Keep Pace With The Future?

START: India is emerging as the fastest-growing aviation market worldwide, yet it faces a significant hurdle: a shortage of trained technical personnel, including pilots, engineers, and technicians. This challenge is expected to become more acute as Electric Vertical Takeoff and Landing (eVTOL) vehicles enter the market within the next year or two, creating an additional need for pilots. The issue stems largely from inadequate planning and foresight by the authorities. Consequently, many aspiring Indian pilots are pursuing training in countries like Sri Lanka, Thailand, Bosnia, Montenegro, and the Philippines. In fact, approximately 700 out of every 1,000 commercial pilot licenses issued by the Directorate General of Civil Aviation (DGCA) are earned abroad. India’s Potential as a Global Hub for Aviation Education Considering India’s expansive geography and favorable weather for flying, the country is ideally suited to be a global hub for aviation education. In the 1980s and 1990s, students from nations such as Iran, Jordan, Palestine, Afghanistan, Sri Lanka, Bhutan, and several African countries came to India for flight training. Today, the trend has reversed, with Indian students going overseas for pilot education. One key reason is the slow pace of domestic training programs and the cumbersome security clearance process for foreign students, which discourages them from enrolling in India. Competition from International Flight Schools Meanwhile, nations like the United Arab Emirates, Qatar, and Saudi Arabia have established world-class flight schools. Students from neighboring Arab countries now mostly prefer the United States, Canada, and Europe for training, despite these regions lacking ideal weather for primary flight instruction. Domestic regulations further complicate matters. The DGCA allows a flight school to operate only if it meets minimum requirements for aircraft and paid-up capital, while the Airports Authority of India (AAI) imposes additional capital requirements. These rules do not guarantee quality education but are often sufficient to prevent many capable entrepreneurs from opening flight schools. By contrast, an Indian entrepreneur started a flight school in New Zealand with a single rented aircraft, which has since expanded to a fleet of over 20 planes and now attracts Indian students. Shortage of Trainer Aircraft The shortage of trainer aircraft is another pressing challenge. In the 1970s, Prof. David Hazen of Princeton University, invited by the Indian government to establish the first aeronautical department at IIT Kanpur, outlined a roadmap for India to achieve self-reliance in aviation training. However, progress has been slow. The DGCA developed the Swati light aircraft, manufactured by Bharat Heavy Electricals Limited (BHEL), but a fatal accident during testing brought the program to an end. Similarly, the Hansa trainer created by the National Aerospace Laboratory (NAL) was rejected by most flight schools. Lessons from the Pushpak Aircraft A comparison with the Pushpak aircraft is instructive. Manufactured in the 1950s, HAL produced 160 Pushpaks, which served India reliably for over 50 years and maintained an excellent safety record. In 1968, the government gifted one Pushpak each to Singapore and Malaysia to help them establish their flight training programs. The Pushpak’s success was largely due to it being modeled closely on the proven US Aeronca Chief. NAL later developed the next-generation Hansa (NG Hansa), which was showcased at the 2020 Wings India airshow, but production has yet to start, and setting up the necessary infrastructure would still take several years even if action begins immediately. Global Trainer Aircraft Shortages and LSAs The shortage of trainer aircraft is not unique to India. Major manufacturers such as Cessna and Piper had slowed production, underestimating demand, and now struggle to meet global requirements. Other countries have tackled this problem by incorporating Light Sport Aircraft (LSAs) into flight training. Equipped with advanced navigation systems, LSAs are cost-effective, environmentally friendly, and widely used in the US and EU for commercial pilot instruction. However, Indian regulations currently do not permit LSAs for commercial pilot training. Despite being equipped with only a magnetic compass, pilots trained on Pushpaks have gone on to fly advanced aircraft like the Boeing 777 and Airbus A320. Allowing LSAs in India could reduce aircraft shortages, encourage domestic manufacturing, generate employment, and attract foreign investment. Lack of Experienced Flight Instructors The lack of experienced flight instructors adds another layer of difficulty. Rapid growth in airlines such as Indigo and Air India has led many instructors to leave training schools for better pay, career progression, and recognition in commercial aviation. This high turnover leaves less-experienced instructors teaching students, unlike other professional fields where teachers usually have extensive industry experience. In countries like the US, airline pilots can provide primary flight training in their spare time, giving trainees the advantage of learning from seasoned professionals and ensuring higher safety standards. Without urgent, proactive measures, India will continue to rely on foreign nations to fulfill the increasing demand for skilled professionals in its civil aviation sector. https://www.hindustantimes.com/ht-insight/knowledge/flight-training-a-challenge-in-civil-aviation-101727069965710.html

India’s Aviation Boom Threatened By Severe Pilot, Instructor And Aircraft Shortages

Follow Us

Facebook-f Instagram Linkedin-in X-twitter Youtube

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

Quick Links

About Us
Contact Us
Services
Advertise
FAQ

Navigate

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

General Support

info@aviationtoday.in

News Desk Support

news@aviationtoday.in

Follow Us

Facebook-f Instagram Linkedin-in X-twitter Youtube

© Copyright 2026 Aviation Today. All rights reserved.

Terms of Use
Privacy Policy
Disclaimer

Search

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

Aviation Newsletter

Facebook Instagram Linkedin X-twitter Youtube