Skip to content

Facebook Instagram Linkedin X-twitter Youtube

About Us
Contact Us
Advertisement

About Us
Contact Us
Advertisement

Aviation Newsletter

WhatsApp Channel

Search

News
Pilot Training
Flight School Analysis
Civil Aviation
Aviation Jobs
Training
Services
More

News
Pilot Training
Flight School Analysis
Civil Aviation
Aviation Jobs
Training
Services
More

Search

News
Pilot Training
Flight School Analysis
Civil Aviation
Aviation Jobs
Training
Services
More

News
Pilot Training
Flight School Analysis
Civil Aviation
Aviation Jobs
Training
Services
More

News

Civil Aviation

Pilot Training

Flight School Analysis

Aviation Jobs

Training

Services

About Us

Contact Us

Search

Aviation Today News Desk

Delhi, India: An Air India Boeing 777-300ER operating flight AI173 from Delhi to San Francisco was forced to return to Delhi after suffering a technical malfunction mid-flight, remaining airborne for more than eight hours before landing safely at Indira Gandhi International Airport. The incident occurred on May 27 and involved approximately 230 passengers onboard the long-haul flight bound for the United States. According to airline officials and flight-tracking data, the aircraft had already spent over three hours in the air and entered Chinese airspace when the crew decided to discontinue the journey and return to Delhi in accordance with safety procedures. Initial reports stated that the issue involved the aircraft’s Traffic Collision Avoidance System (TCAS), a critical airborne safety system designed to prevent mid-air collisions by enabling aircraft to electronically detect and communicate with nearby traffic. The system operates independently of ground-based air traffic control and is considered mandatory for certain long-haul international operations, including trans-Pacific and North Atlantic routes. While Air India did not officially disclose the exact nature of the malfunction in its initial public statement, it is suspected that the aircraft experienced problems linked to the TCAS equipment during the flight. Some aviation reports and social media aviation monitoring pages further claimed that both TCAS channels onboard the aircraft became unavailable, though the airline has not publicly confirmed those specific details. Flight-tracking platforms showed the Boeing 777-300ER reversing course while over Chinese airspace before commencing the lengthy return sector to Delhi. Due to the aircraft’s weight, fuel load, and operational requirements for a safe landing, the jet remained airborne for several additional hours before touchdown. Air India confirmed that the aircraft landed safely and would undergo a detailed technical inspection in line with the carrier’s maintenance and safety protocols. The airline also stated that alternative arrangements were made for affected passengers, including hotel accommodation, refreshments, rebooking support, and rescheduling options. “The aircraft landed safely and will undergo technical inspection in line with Air India’s safety standards,” the airline said in its statement while expressing regret over the inconvenience caused to passengers. No injuries were reported during the incident, and passengers were safely deboarded after the aircraft’s arrival back in Delhi.

Air India Flight To San Francisco Returns To Delhi After Mid-Air Technical Malfunction

May 29, 2026

Washington, United States: The U.S. Federal Aviation Administration (FAA) has proposed a civil penalty of $165,000 against Alaska Airlines after alleging the carrier allowed intoxicated passengers to board multiple flights over a one-year period. According to the FAA, the alleged violations occurred on 11 separate flights between February 2024 and February 2025. Federal aviation regulations prohibit airlines from permitting any individual who appears intoxicated to board an aircraft due to the potential safety and security risks posed during flight operations. The agency announced the proposed enforcement action on May 26, stating that Alaska Airlines now has 30 days from receiving the FAA’s enforcement letter to respond to the allegations or contest the proposed penalty. While the FAA did not disclose details regarding the specific flights, routes, airports, passengers, or onboard incidents involved, the regulator said the alleged cases were identified during a review of the airline’s policies and procedures concerning intoxicated passengers. In response, Alaska Airlines said it fully cooperated with the FAA’s audit and has already implemented corrective measures aimed at strengthening compliance with federal safety expectations. “We take seriously our responsibility to provide a safe and secure environment for our guests and employees,” the airline said in a statement. “Since the FAA shared these concerns with us over a year ago, we made meaningful changes to ensure compliance with the FAA’s expectations including enhanced training for all flight attendants and customer service agents.” The airline added that it respects the outcome of the FAA’s audit and remains confident that the changes introduced over the past year have improved adherence to regulatory standards. The proposed penalty marks the latest in a series of FAA enforcement actions involving airline compliance and safety oversight. Under FAA regulations, airlines are responsible for denying boarding to passengers who appear visibly intoxicated. Such rules are designed to reduce the risk of disruptive behavior, onboard disturbances, and potential threats to flight safety.

FAA Proposes Penalty Against Alaska Airlines Over Alleged Intoxicated Passenger Boarding

May 29, 2026

Lucknow, India: An Akasa Air Boeing 737 MAX 8 operating from Bengaluru to Bhubaneswar made an emergency landing at Lucknow’s Chaudhary Charan Singh International Airport on May 27 after the flight encountered adverse weather conditions at its destination and subsequently reported low fuel levels during diversion. The flight, operating as QP1503 and registered as VT-YAJ, was carrying a total of 194 passengers and crew members onboard when the incident occurred. According to multiple media reports and airport officials, the aircraft was initially unable to land at Bhubaneswar due to unfavorable weather conditions. The flight was subsequently diverted to Lucknow at approximately 8:40 PM local time. While approaching Lucknow, the crew reportedly issued a “PAN PAN” call to Air Traffic Control (ATC) at around 9:02 PM after fuel levels became critically low during the extended diversion. In aviation terminology, a “PAN PAN” declaration indicates an urgent situation requiring priority assistance, though it is considered less severe than a “MAYDAY” distress call. The pilot-in-command requested priority handling and a clear approach to ensure the aircraft could land safely in a single attempt amid fuel constraints. Following the alert, Lucknow ATC declared a full emergency and immediately activated standard emergency response procedures. Crash fire tenders and emergency response teams were positioned at designated points along Runway 09 by approximately 9:04 PM as a precautionary measure. The aircraft landed safely at Lucknow International Airport at around 9:21 PM. Shortly after touchdown, the flight crew informed ATC that all aircraft operations were normal and that no emergency assistance was required. Authorities subsequently withdrew the full emergency status at approximately 9:30 PM. Airport officials confirmed that all emergency and safety protocols were executed as per standard operating procedures and that the situation was handled without incident. No injuries to passengers or crew were reported. According to reports, three passengers deboarded the aircraft in Lucknow before the flight later resumed its journey to Bhubaneswar. In an official statement, Akasa Air confirmed that the diversion was caused by adverse weather conditions at Bhubaneswar and stated that the crew followed all established operational and safety procedures throughout the incident. “Akasa Air flight QP 1503 operating from Bengaluru to Bhubaneswar on 27 May 2026 was diverted to Lucknow due to adverse weather conditions, which were not favourable for landing. The pilot followed all established operational and safety protocols in line with standard procedures,” the airline said. The carrier further stated that the flight later departed Lucknow and landed safely in Bhubaneswar at 00:02 hrs on May 28. “At Akasa Air, the safety and well-being of our passengers and crew remain our highest priority. We regret the inconvenience caused due to circumstances beyond our control and appreciate our passengers’ understanding,” the airline added.

Akasa Air Flight Diverts To Lucknow After Weather Disruption And Low Fuel Alert

May 29, 2026

Sonoma, United States: A small single-engine aircraft crashed while attempting to land at Sonoma Valley Airport in Northern California on Wednesday afternoon, injuring all three people onboard and triggering a multi-agency emergency response. The accident occurred at approximately 4:19 p.m. local time on May 27, 2026, at Sonoma Valley Airport, also known as Schellville Airport, located along Arnold Drive in Sonoma County, California. According to the Sonoma County Sheriff’s Office, deputies responded alongside crews from the Schell-Vista Fire Protection District and Sonoma Valley Fire District after reports of an aircraft accident during landing. First responders located the damaged aircraft resting near a levee adjacent to the runway within airport property. Authorities confirmed the aircraft involved was a single-engine airplane that had departed from Auburn Municipal Airport before attempting to land in Sonoma. Three occupants identified as the pilot and two passengers were onboard at the time of the crash. Initial reports from emergency agencies stated that all three occupants sustained injuries. Two individuals were transported to hospitals for treatment, while one occupant declined medical transport. Later updates from California Highway Patrol officials indicated one person suffered major injuries and two others sustained minor injuries. The aircraft involved was a Murphy SR2500 Super Rebel, registration N135DS, manufactured in 2001 and operated by JM Environmental Inc. According to local fire officials, one injured occupant was airlifted to Santa Rosa Memorial Hospital, while another was transported by ground ambulance to Queen of the Valley Hospital in Napa. Images from the crash scene showed the aircraft overturned with substantial damage inside a watery ditch next to the runway area. Emergency responders secured the scene while investigators began preliminary assessments. Officials stated the aircraft came to rest in a field across a levee but remained confined within airport grounds. No post-crash fire was reported. The Federal Aviation Administration (FAA) and the National Transportation Safety Board (NTSB) have launched an investigation into the accident. Investigators are expected to examine the wreckage, flight path, aircraft maintenance records, pilot information, and weather conditions as part of the inquiry.

3 Onboard Injured As Single-Engine Plane Crashes During Landing At Sonoma Airport

May 29, 2026

New Delhi, India: Indian investigators are preparing an interim report into last year’s fatal Air India Boeing 787 Dreamliner crash instead of a final report, as authorities continue examining one of the deadliest aviation disasters. According to Reuters, the Aircraft Accident Investigation Bureau (AAIB) is expected to issue the interim findings ahead of the first anniversary of the June 12, 2025 crash involving Air India Flight AI171, which was operating from Ahmedabad to London Gatwick. The accident killed 260 people after the Boeing 787-8 lost thrust moments after takeoff and crashed into a medical college hostel near the airport. The interim document will be “more comprehensive” than the 15-page preliminary report released in July 2025 and is expected to examine possible primary causes and contributing factors behind the crash. However, investigators said the final report is still not ready because of the complexity of the inquiry and the time required for additional analysis. The preliminary AAIB report found that the aircraft’s engine fuel control switches moved almost simultaneously from the “RUN” to “CUTOFF” position shortly after takeoff, starving both engines of fuel. Cockpit recordings reviewed during the investigation indicated confusion between the pilots over the movement of the switches. The early assessment by U.S. officials reviewing cockpit voice recordings supported the view that the captain may have cut fuel flow to the engines. Indian investigators, however, said at the time that it was “too early to reach any definite conclusions.” The ongoing investigation involves multiple international agencies because the aircraft was designed and manufactured in the United States. The U.S. National Transportation Safety Board (NTSB) is participating in the probe, while Boeing is assisting as a technical adviser. By issuing an interim report instead of a final one, Indian authorities will not be required to circulate draft findings in advance to the NTSB for review and comment. Under International Civil Aviation Organization (ICAO) rules, draft final reports are generally shared with participating states for consultation before publication. The investigation has gained renewed attention following a separate Air India Boeing 787 incident earlier this year involving fuel control switches. In February 2026, pilots operating a Dreamliner flight from London to Bengaluru reported that the fuel switches did not remain fixed in the “RUN” position during engine start attempts before stabilizing on a third attempt. Indian aviation regulator Directorate General of Civil Aviation (DGCA) officials are expected to travel to Boeing facilities in Seattle in June to observe testing of the fuel switch panel from that aircraft. Under international aviation standards, a final accident report is generally expected within one year of a crash. If the investigation remains incomplete, authorities are required to issue an interim statement outlining progress in the inquiry. Investigators said work on the final report is continuing and no timeline has been confirmed for its release.

Report: India Preparing Interim Report On Fatal Air India Boeing 787 Crash Investigation

May 28, 2026

Cape Town, South Africa: South African Airways (SAA) is facing mounting scrutiny after allegations emerged that the airline delayed reporting a serious fuel emergency involving two flights at Cape Town International Airport, prompting calls for a Parliamentary inquiry into aviation safety oversight in South Africa. The controversy centres on SAA flights SA313 and SA327, which were affected by severe weather conditions over Cape Town on 11 May 2026. According to reports, the airline allegedly took eight days to notify the South African Civil Aviation Authority (SACAA) about the incidents, despite regulations requiring such events to be reported within 72 hours. The issue has triggered criticism from South Africa’s opposition Democratic Alliance (DA), which has formally requested an urgent hearing before Parliament’s Portfolio Committee on Transport. The party said the delay raises concerns about SAA’s safety management systems, regulatory compliance, and transparency. Chris Hunsinger, Democratic Alliance spokesperson on transport, said the incident reflects what he described as a broader pattern of failures within the country’s aviation oversight framework. He warned that repeated operational incidents, delayed reporting, and questions surrounding accountability were eroding public confidence in aviation safety. According to aviation sources cited in local reports, flight SA313, operated by an Airbus A320 from Johannesburg to Cape Town, encountered severe weather during its arrival into Cape Town amid gale-force north-westerly winds, heavy rain, low cloud, and dangerous windshear conditions. The aircraft reportedly conducted a missed approach after receiving onboard windshear alerts. Pilot and aviation analyst Duncan Gillespie stated that a second landing attempt at Cape Town would likely have left the aircraft without sufficient reserves to divert safely to its nominated alternate airport, George Airport. The aircraft subsequently diverted to George, but deteriorating weather conditions there allegedly prevented a safe landing. The aircraft later continued to Gqeberha, where reports claim it landed with fuel reserves below internationally accepted minimum levels. Gillespie alleged the aircraft may have landed with less than 15 minutes of fuel remaining. Under international aviation regulations, commercial aircraft are generally expected to land with approximately 30 minutes of final reserve fuel, and crews are normally required to declare a fuel emergency if projected landing fuel falls below that threshold. Questions have also been raised over whether the crew declared a formal “Mayday Fuel” emergency during the incident. Gillespie noted there was no visible indication on public flight-tracking systems that the aircraft had transmitted the emergency transponder code commonly associated with a Mayday declaration. SAA spokesperson Mphilo Dlamini did not directly address questions regarding the alleged fuel emergency, remaining fuel levels after landing, or whether the crew had declared an emergency. Instead, the airline stated that severe weather conditions affected operations across the Western Cape on 11 May and maintained that SAA followed all required aviation safety procedures and reporting protocols. The SACAA had also not publicly responded to detailed media questions at the time several reports were published. The DA said it intends summoning SAA, SACAA, Air Traffic and Navigation Services (ATNS), and the Department of Transport before Parliament to explain the delayed reporting, oversight concerns, and broader operational issues affecting South African aviation. The party also highlighted ongoing problems within ATNS, including the suspension of 326 instrument flight procedures. The DA further pointed to concerns over regulatory independence, arguing that SACAA investigates entities operating under the same government department, potentially creating conflicts of interest in aviation oversight.

SAA Faces Scrutiny Over Delayed Reporting Of Alleged 2 Fuel Emergency Incidents

May 28, 2026

Cedar City, United States: A training helicopter operated by the aviation program of Southern Utah University crashed at Cedar City Regional Airport on Saturday morning, leaving a pilot and a student pilot injured and prompting a federal investigation into the accident. According to authorities, the crash occurred on May 23, 2026, at Cedar City Airport in Iron County, Utah. Officers from the Cedar City Police Department responded to the scene after receiving reports of an accident involving an SUU helicopter used for flight training operations. Police said two people were onboard the aircraft at the time of the accident, a pilot instructor and a student pilot. Both occupants survived the crash and were transported to Cedar City Hospital with injuries described as non-life-threatening. Officials confirmed the helicopter sustained significant damage during the accident. However, no additional injuries were reported on the ground and no other property was damaged. Authorities have not yet publicly identified the helicopter type, registration number, flight phase, or the exact cause of the crash. “We are aware of the accident involving an SUU helicopter at the Cedar City Airport this morning,” SUU public relations director Brooke Heath said in a brief written statement. “The safety of our students, faculty, and staff is our top priority, and we are working closely with the NTSB (National Transportation Safety Board) and FAA (Federal Aviation Administration) to investigate the incident,” Heath’s statement concluded. The Federal Aviation Administration (FAA) and the National Transportation Safety Board (NTSB) have launched an investigation into the incident. Federal investigators are expected to examine operational records, maintenance history, weather conditions, pilot training procedures, and wreckage evidence to determine the cause of the crash. Southern Utah University operates one of the largest collegiate helicopter training fleets in the United States through its aviation division based in Cedar City. The university’s rotorcraft training program uses helicopters for commercial pilot, instructor, mountain flying, and emergency procedure training. Cedar City Regional Airport, located about two miles northwest of Cedar City, is a major hub for flight training activity in southern Utah and hosts both fixed-wing and rotorcraft operations. As of now, officials have not released additional details regarding the sequence of events leading to the crash, and the investigation remains ongoing.

SUU Flight Training Helicopter Crash In Utah Injures Instructor And Student Pilot

May 27, 2026

Detroit, United States: A Delta Air Lines Connection flight operating from Madison, Wisconsin, to Detroit, Michigan, declared a medical emergency after the co-pilot briefly lost consciousness during the aircraft’s approach and landing phase, according to airline statements and air traffic control (ATC) communications. The incident occurred on May 23, 2026, aboard a flight operated by Endeavor Air, a wholly owned regional subsidiary of Delta Air Lines. The aircraft departed from Dane County Regional Airport and was arriving at Detroit Metropolitan Wayne County Airport when the emergency unfolded. According to ATC audio, the captain informed controllers that the first officer had become incapacitated during the approach. In the transmission, the captain stated: “Declaring a medical emergency, my first officer’s incapacitated.” Air traffic controllers subsequently cleared the aircraft for priority landing. The aircraft landed safely in Detroit without further incident. Delta confirmed that paramedics met the flight after it taxied to the gate and that the first officer had regained consciousness by the time emergency personnel boarded the aircraft. The co-pilot was then transported to a hospital for medical evaluation. Flight tracking data indicated the flight completed the journey in approximately one hour and arrived around 20 minutes ahead of schedule despite the emergency declaration. No passengers or cabin crew members were reported injured during the incident. In a statement, Delta said safety remained its highest priority and praised the crew’s handling of the situation. The airline stated that the professionalism of the Endeavor Air crew and the response of emergency personnel helped ensure the flight concluded safely. The airline did not disclose the medical cause behind the co-pilot’s temporary loss of consciousness. There was also no indication of any technical or mechanical issue involving the aircraft itself. The incident also came days after another unrelated pilot medical emergency involving a Jet2.com flight traveling from Tenerife, Spain, to Birmingham, United Kingdom, which diverted to Porto, Portugal, after one of the pilots reportedly became unwell mid-flight.

Delta Connection Flight Declares Emergency After Co-Pilot Loses Consciousness During Landing

May 27, 2026

Bangalore; India: A major aviation scare unfolded at Kempegowda International Airport on Tuesday evening after smoke was detected inside an IndiGo Airbus A321neo operating a Bengaluru-Chennai flight, forcing the emergency evacuation of more than 230 passengers and crew members just before takeoff. According to the Directorate General of Civil Aviation (DGCA) and airline officials, the incident involved IndiGo flight 6E 6017, which had begun taxiing towards the runway when smoke was observed inside both the cabin and cockpit, triggering an immediate emergency response. The aircraft had completed pushback and was taxiing for departure to Chennai when smoke was reported onboard. Following the detection, the flight crew immediately halted operations and ordered an emergency evacuation as a precautionary measure. All passengers were evacuated using the aircraft’s emergency escape slides on the taxiway, with airport fire and emergency response teams rushing to assist. The evacuation was completed before the aircraft could line up for takeoff. During the emergency evacuation, two passengers sustained minor injuries, according to DGCA and multiple media reports. They were provided immediate medical attention at the terminal and were reported to be in stable condition. Despite the panic, authorities confirmed that all passengers and crew were safely evacuated. IndiGo confirmed the incident and stated that safety procedures were followed immediately after smoke was detected. “On 26 May 2026, while IndiGo flight 6E 6017 from Bengaluru to Chennai was taxiing toward the runway for departure, smoke was noticed in the aircraft. In the interest of safety, an immediate evacuation was carried out, and all relevant authorities were informed. All customers and crew are safe and have been moved to the terminal, where they are being attended to by our teams to ensure their well-being,” the airline said in its official statement. The airline also arranged an alternate aircraft to operate the Bengaluru-Chennai service and provided assistance to affected passengers. The DGCA confirmed that the aircraft, an Airbus A321neo (VT-IME), has been grounded for inspection and rectification. According to the regulator, smoke was reported shortly after pushback when the aircraft began taxiing, with observations indicating smoke presence in both the cockpit and cabin. A detailed investigation has been initiated to determine the root cause. Authorities are examining possible technical issues, including: Electrical system malfunction Air-conditioning or auxiliary system failure Potential wiring or equipment overheating Passengers described a sudden and alarming situation as smoke filled parts of the aircraft during taxiing. One passenger saidI that smoke appeared shortly after the flight began moving, causing immediate panic among those onboard. Another passenger described “dense smoke” and a strong smell inside the cabin, adding that elderly passengers and children faced difficulties during the evacuation process. Eyewitness accounts also noted that passengers rushed toward exits as crew members guided them through emergency procedures. The exact cause of the smoke remains under investigation, with DGCA expected to release preliminary findings after a detailed technical inspection of the aircraft systems.

230 Passengers Evacuated At Bengaluru Airport After Smoke Detected On IndiGo Flight

May 27, 2026

Tokyo, Japan: A Skymark Airlines Boeing 737 operating a domestic flight from Tokyo’s Haneda Airport to Fukuoka made an emergency return on Monday after the crew detected a landing gear tire abnormality mid-flight, later confirmed to involve a ruptured tire, according to Japan’s transport ministry and airline officials. The aircraft, carrying 169 passengers and crew, departed Haneda shortly after 3 p.m. local time and proceeded normally for nearly two hours before the flight crew identified a technical issue related to the landing gear system. Following standard safety procedures, the pilots declared an emergency and initiated a precautionary return to Haneda Airport. The aircraft landed safely back at Haneda without any injuries reported among passengers or crew members. The airline confirmed that all onboard remained safe throughout the incident and that the situation was handled in line with established emergency protocols. After landing, inspections conducted by airport authorities and Japan’s Ministry of Land, Infrastructure, Transport and Tourism confirmed that one of the aircraft’s tires had ruptured. Officials have not yet determined whether the damage occurred during takeoff, in-flight, or during landing gear operation after departure. Following the emergency landing, Haneda Airport temporarily closed Runway C to conduct safety inspections and remove any possible debris or rubber residue. The runway was later reopened at around 7:40 p.m. local time after checks confirmed safe operating conditions and no structural damage. Skymark Airlines operates a major domestic network from Haneda, connecting key cities across Japan, including Fukuoka, Sapporo, and Okinawa. The airline has not reported any further operational disruptions related to the incident, though the aircraft will undergo a detailed technical inspection before returning to service. Authorities are continuing to review the cause of the tire rupture as part of standard post-incident safety procedures.

Skymark Boeing 737 Makes Emergency Return To Haneda After Tire Rupture

May 26, 2026

« Previous Page1 … Page5 Page6 Page7 Page8 Page9 … Page115 Next »

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
News
Pilot Training
Civil Aviation
Flight School Analysis
Aviation Jobs
Training
Services
More
Contact Us
Advertisement

Aviation Newsletter

Facebook Instagram Linkedin X-twitter Youtube