Aviation Today Archives - Page 35 of 64

India: A Right to Information (RTI) response from the Directorate General of Civil Aviation (DGCA), as reported by The Times of India, has revealed that Indian airspace recorded 65 in-flight engine shutdowns over the past five years. The data also disclosed 11 Mayday calls between January 1, 2024, and May 31, 2025, four of which were linked to Hyderabad’s air traffic control region. Engine Shutdowns Involving Multiple Airlines and Aircraft The incidents spanned both domestic and foreign carriers, with shutdowns occurring during takeoff, in cruise, or as a precautionary measure following cockpit alerts. The DGCA identified key technical causes, including: Blocked or contaminated fuel filters Interrupted fuel supply Oil pressure loss Foreign object ingestion Turbine control unit malfunctions All 65 incidents were classified as reportable occurrences under India’s civil aviation regulations and were investigated by the concerned operators under DGCA supervision. “We continue to witness shutdowns due to recurring causes like fuel contamination or component wear. Every occurrence is tracked and mandates technical review,” said Capt. C. S. Randhawa, President of the Federation of Indian Pilots. Mayday Calls Highlight Critical Emergencies The DGCA confirmed that the 11 Mayday calls issued during the 17-month period were in response to severe emergencies requiring immediate crew response. These included engine fires, hydraulic failures, and other situations jeopardizing flight safety. “A Mayday is the most serious alert. When pilots call one, it means the situation demands urgent intervention be it fire, total engine loss, or system failure,” explained Anil Rao, Executive Member, ALPA-India. Though the RTI reply did not identify the specific flights or aircraft types, officials confirmed that all events were subject to post-flight safety reviews, many involving the Aircraft Accident Investigation Bureau (AAIB). BCAS Staffing Vacancies Raise Oversight Concerns Separately, the Bureau of Civil Aviation Security (BCAS), India’s aviation security watchdog, reported 224 vacancies out of 598 sanctioned posts as of March 2025. The shortfall represents a staffing gap of over 37%. A recent parliamentary standing committee had raised concerns that such vacancies may hinder effective regulatory oversight. Air India Express Crash Raises Safety Scrutiny The disclosure comes shortly after the Air India Express Flight IX-171 crash near Ahmedabad on June 12, 2025, in which an engine failure during climb-out was suspected based on preliminary reports. While the DGCA has not confirmed whether the case is counted among the 65 shutdowns, the timeline places it within the scope of the RTI data. Aviation regulators emphasize that twin-engine aircraft are certified under ETOPS to continue flying with one engine inoperative, but each incident is taken seriously. Investigations may lead to maintenance bulletins, airworthiness directives, or fleet-wide inspections. Lack of Public Safety Dashboard India currently does not provide a public-facing aviation safety dashboard like the FAA’s Aviation Safety Information Analysis and Sharing (ASIAS) system. Access to data on technical issues or Mayday calls remains limited, often requiring RTI filings. Increased transparency in aviation safety has been a growing demand among Indian aviation stakeholders. In its June 2025 report, a civil aviation working group recommended enhanced publication of anonymized safety statistics and the establishment of a centralized digital platform for incident data.

DGCA Confirms 65 Engine Shutdowns Since 2020 and 11 Maydays in Last 17 Months

Aviation Today News Desk / July 17, 2025

India: A Right to Information (RTI) response from the Directorate General of Civil Aviation (DGCA), as reported by The Times […]

Tuva, Russia: An Air China Airbus A350-900 operating as Flight CA967 from Shanghai Pudong to Milan Malpensa was involved in a serious airspace incident over southern Siberia after it climbed through an occupied flight level, coming dangerously close to a cargo aircraft. According to preliminary radar and ATC data, the Air China aircraft began a climb from 34,100 feet to 36,000 feet without receiving explicit clearance from Russian air traffic control. During this unauthorized climb, the aircraft came within approximately 300 to 400 feet vertically of an SF Airlines Boeing 767 freighter cruising at 35,000 feet on a crossing path. The incident occurred over the Tuva region of the Russian Federation at approximately 21:39 UTC. TCAS Resolution Prevents Collision Both aircraft were equipped with functioning Traffic Collision Avoidance Systems (TCAS), which detected the impending conflict and issued resolution advisories. Crews on both aircraft responded promptly to TCAS instructions. No collision occurred, and both flights continued to their respective destinations without further incident. The separation between the two aircraft fell significantly below the minimum vertical separation required under ICAO standards, which is 1,000 feet for aircraft at cruising altitude. Controller-Pilot Communication Discrepancies Cockpit audio recordings released on social media and verified by local media outlets reveal apparent miscommunication between the Air China crew and Russian air traffic control. In the audio, the pilot of the SF Airlines cargo aircraft can be heard questioning the Air China flight’s climb, stating that the aircraft had initiated the climb while only 20 nautical miles ahead and without clearance. The Air China pilot did not confirm that clearance was received and appeared to acknowledge that the climb had not been explicitly approved. Russian controllers can be heard instructing other aircraft in the vicinity to maintain level flight to avoid additional conflict during the incident. Investigation Authorities from the Civil Aviation Administration of China (CAAC) and Russia's Federal Air Transport Agency (Rosaviatsiya) have launched a joint investigation. Both regulatory bodies have confirmed that standard incident reporting procedures have been initiated and that flight data recorders, cockpit voice recordings, and ATC logs will be reviewed. Officials are examining possible causes including frequency congestion, language barriers, and incorrect readbacks. The Tuva region lies within a transition area where communication overlaps and limited coverage have previously been noted in operational reports. No passengers or crew were injured during the incident. Flight CA967 continued to Milan Malpensa, arriving on schedule. The SF Airlines Boeing 767 also completed its scheduled route without diversion. Authorities have not yet released the final investigation timeline. Air China has not issued a public statement as of this report.

Incidents

Air China A350 Breaches Altitude Separation, Near-Miss with Cargo Jet Over Russia

Aviation Today News Desk / July 16, 2025

Tuva, Russia: An Air China Airbus A350-900 operating as Flight CA967 from Shanghai Pudong to Milan Malpensa was involved in

Vancouver, Canada: A stolen Cessna 172 aircraft caused a significant security incident and temporary flight disruptions at Vancouver International Airport (YVR) on Tuesday afternoon, prompting an emergency response by airport authorities and federal law enforcement agencies. According to a statement issued by the Richmond Royal Canadian Mounted Police (RCMP), the aircraft was reported stolen from the Victoria Flying Club, based at Victoria International Airport, shortly after 1:00 p.m. PDT. The plane was identified as having departed Victoria without authorization and subsequently entered Vancouver’s controlled airspace without prior clearance. Airport officials and air traffic controllers monitored the aircraft as it approached and circled the airspace above Vancouver International Airport. Flight tracking data showed the Cessna maneuvering erratically at low altitude, raising immediate concerns among air traffic personnel. Out of precaution, the airport implemented a full ground stop on all inbound arrivals at approximately 1:15 p.m., halting flight operations while authorities coordinated a response. At approximately 1:45 p.m., the aircraft made a safe landing at YVR. The RCMP, supported by YVR Security and RCMP Air Services, moved quickly to secure the aircraft and arrest the individual who was taken into custody without incident on the airfield. No injuries were reported during the event, and the aircraft sustained no apparent damage. A total of nine inbound flights were diverted during the lockdown period, and dozens more were delayed. The temporary ground stop lasted for approximately 39 minutes, with normal flight operations resuming shortly after 2:00 p.m. The Vancouver Airport Authority later confirmed that while residual delays were expected, the airport had returned to regular operational status. In an official update, Richmond RCMP stated that the individual taken into custody is believed to have acted alone. The identity of the suspect has not yet been disclosed, and no motive has been confirmed at this stage of the investigation. Authorities confirmed that the individual did not possess clearance to operate the aircraft and is not believed to be a licensed commercial pilot. The Transportation Safety Board of Canada (TSB) has been notified and is assessing whether a formal investigation will be opened. Meanwhile, the RCMP has launched a criminal investigation into the unauthorized use of the aircraft, including potential violations of the Canadian Aviation Regulations and other federal statutes. The Victoria Flying Club, operator of the aircraft, issued a brief statement acknowledging the incident and confirmed it is fully cooperating with investigators. Airport operations at YVR have since stabilized, and the airport authority has advised travelers to monitor airline communications for any residual delays or schedule adjustments. No further public safety threats are currently associated with the event, according to police. Authorities are expected to release additional details as the investigation progresses.

Incidents

Stolen Cessna Causes Disruption at Vancouver Airport, Suspect Had No Pilot License

Aviation Today News Desk / July 16, 2025

Vancouver, Canada: A stolen Cessna 172 aircraft caused a significant security incident and temporary flight disruptions at Vancouver International Airport

London, United Kingdom: Four people were killed when a medical transport aircraft operated by Zeusch Aviation crashed shortly after takeoff from London Southend Airport on Sunday, July 14. Authorities have confirmed that all four occupants onboard the Beechcraft B200 Super King Air perished in the incident. The UK’s Air Accidents Investigation Branch (AAIB) and Essex Police are continuing a full investigation into the cause of the crash, which occurred just seconds after the aircraft lifted off from Runway 05. Fatalities Confirmed In an official statement released Monday, Essex Police confirmed the deaths of all four individuals aboard. Chief Superintendent Morgan Cronin stated: "Sadly, we can now confirm that all four people on board died. We are working closely with partner agencies, including the Air Accidents Investigation Branch, to recover all available information." Formal identification of the victims is ongoing, and their families are being supported by liaison officers. While official identities have not yet been published by Essex Police, documents reviewed by Britain’s national news agency PA indicate that the deceased included two Dutch pilots, a 31-year-old Chilean-born German flight nurse, and another foreign medical staff member. The nurse, later identified by multiple media outlets as Maria Fernanda Rojas Ortiz, was reportedly on her first day of duty aboard the aircraft. Crash Circumstances The aircraft, registered in the Netherlands and operated by Zeusch Aviation, was performing a medical repatriation flight bound for the Netherlands, following earlier stops in Greece and Croatia. The flight was designated SUZ1. Witnesses and preliminary flight data suggest the aircraft became airborne, banked sharply to the left, inverted, and descended rapidly before crashing into the ground near the airport perimeter. The impact produced a large fireball and thick smoke visible across much of Essex. Emergency services from Essex Police, Fire and Rescue, ambulance services, and Southend Airport personnel responded within minutes. A full cordon was established, and nearby roads were closed as a precaution. A Civil Aviation Authority (CAA) air exclusion zone remains in place over the site. The crash site was secured to facilitate recovery of wreckage, flight recorders, and technical components, which are now being examined by AAIB inspectors. London Southend Airport suspended all flights immediately following the crash. The airport remains closed as of Tuesday, July 15, with no estimated time for reopening announced. Airlines have advised passengers to check for updates and alternative travel arrangements. Investigation Continues The AAIB has deployed a multidisciplinary team to Southend to investigate the circumstances leading to the accident. Both the cockpit voice recorder (CVR) and flight data recorder (FDR) have been located and are undergoing analysis. No preliminary findings have yet been published. In a statement, Zeusch Aviation acknowledged the loss of its crew and support staff and expressed full cooperation with UK authorities: "We are devastated by this tragic event. Our thoughts are with the families of our crew and colleagues. We are assisting investigators and will continue to share relevant updates in due course." Authorities have urged members of the public who witnessed the crash or captured it on video to provide their materials directly to investigators rather than share them on social media. Chief Superintendent Cronin added that the priority now is “to support the families affected and establish the full facts behind what happened.”

Aircraft Crashes

All Four Aboard Killed in Southend Airport Crash, AAIB Recovers Flight Recorders

Aviation Today News Desk / July 15, 2025

London, United Kingdom: Four people were killed when a medical transport aircraft operated by Zeusch Aviation crashed shortly after takeoff

Recruitment

Emirates Begins Pilot Hiring Roadshows Across UK, Ireland, Greece, Serbia and Hungary

Aviation Today News Desk / July 15, 2025

Europe: Emirates has launched an extensive series of pilot recruitment roadshows across the UK, Ireland, and Europe as part of

United States

Severe Storms Trigger 5,000+ Flight Delays and 800 Cancellations Across U.S. Airports

Aviation Today News Desk / July 14, 2025

United States: Air travel across the United States experienced major disruption on Monday as severe weather systems swept across multiple

London, United Kingdom: A twin-engine turboprop aircraft operated by Zeusch Aviation crashed shortly after takeoff from London Southend Airport on Saturday, July 13, prompting the temporary closure of the airport and an ongoing investigation by UK aviation authorities. Aircraft and Flight Information The aircraft involved was a Beechcraft B200 Super King Air, registered to Netherlands-based Zeusch Aviation. According to flight data and initial confirmations from the operator, the aircraft was conducting a medical transport mission at the time of the crash. The flight was reportedly en route to the Netherlands, having earlier stopped in Greece and Croatia. It was designated as flight SUZ1. The incident occurred moments after the aircraft departed from Runway 05 at Southend Airport in Essex. Witnesses and preliminary flight path data indicate the aircraft became airborne before sharply banking left, inverting, and descending rapidly to the ground, resulting in a fireball and thick black smoke visible from several kilometers away. Emergency Response Emergency services responded within minutes. Essex Police confirmed that fire and rescue personnel, ambulances, and airport fire crews were immediately deployed to the crash site, located near the end of the airport's main runway. A cordon was established around the wreckage, and the public was advised to avoid the area. Authorities have not confirmed the number of individuals onboard at the time of the crash or released any information on casualties, though recovery operations have been ongoing since Saturday afternoon. Airport Closure London Southend Airport suspended all operations in the aftermath of the crash. As of Monday, July 14, the airport remains closed while the investigation continues. Flight departures and arrivals have been cancelled or diverted, and passengers have been advised to check with airlines for alternative arrangements. Investigation The UK’s Air Accidents Investigation Branch (AAIB) has launched an official investigation into the crash. Inspectors and recovery teams have been deployed to the scene to secure flight data recorders and other evidence critical to understanding the cause of the incident. The AAIB has not yet released any preliminary findings or official statements on possible mechanical failure or pilot action. Zeusch Aviation has issued a brief statement acknowledging the accident and confirming that the aircraft was operating under its command. The company expressed cooperation with the AAIB and local authorities and stated that more information would be shared as it becomes available. Eyewitness Reports Several individuals near the airport, including those on nearby roads and golf courses, reported seeing the aircraft experience difficulties moments after takeoff. Some described the aircraft waving or banking before entering what appeared to be an uncontrolled descent. Others reported hearing a loud explosion and seeing a plume of smoke rising above the crash site. Local authorities have requested that individuals who witnessed the incident or recorded video footage provide their material directly to investigators rather than share it publicly. As of this report, no formal casualty figures or identities have been released. The AAIB is expected to issue an initial update in the coming days once primary data, including the cockpit voice recorder and flight data recorder, is recovered and analyzed. Operations at Southend Airport will remain suspended pending clearance from investigators and relevant safety authorities. Authorities have asked the public to refrain from speculation and allow the investigative process to proceed. Further details will be shared following the release of the AAIB’s preliminary report.

Aircraft Crashes

Small Aircraft Crashes Seconds After Takeoff from Southend Airport, UK AAIB Probes

Aviation Today News Desk / July 14, 2025

London, United Kingdom: A twin-engine turboprop aircraft operated by Zeusch Aviation crashed shortly after takeoff from London Southend Airport on

Investigation

Cockpit Voice Captures Fuel Cutoff Confusion in Air India AI171 Crash Preliminary Report

Aviation Today News Desk / July 12, 2025

Gujarat, India: The Aircraft Accident Investigation Bureau (AAIB) has released the preliminary report into the crash of Air India’s Boeing

Washington, D.C., United States: The National Transportation Safety Board (NTSB) has released its final report into the in-flight depressurization incident involving Alaska Airlines Flight 1282, identifying critical failures by both Boeing and the Federal Aviation Administration (FAA). The incident, which occurred on January 5, 2024, involved the mid-cabin exit door plug separating mid-air from a Boeing 737-9 MAX, leading to an emergency landing in Portland, Oregon. No fatalities occurred, though eight people sustained minor injuries. The NTSB investigation concludes that a series of manufacturing errors, documentation lapses, and oversight failures contributed to the serious safety breach. Incident Summary Alaska Airlines Flight 1282 departed from Portland International Airport at 5:07 p.m. on January 5, 2024. While climbing through approximately 14,830 feet, the aircraft experienced a sudden depressurization due to the separation of the left mid-cabin exit door plug. The cabin pressure rapidly dropped, oxygen masks deployed, and a loud explosive sound was heard. The crew declared an emergency and landed safely back in Portland at 5:27 p.m., 20 minutes after departure. The aircraft was carrying 171 passengers and six crew members. Manufacturing Lapses at Boeing Identified According to the NTSB’s 19-page final report, the door plug had been removed by Boeing personnel at the company’s Renton, Washington facility during fuselage repairs in September 2023. However, no documentation of the removal or reinstallation was found, violating standard production protocols. Furthermore, investigators determined that four critical bolts securing the door plug were never reinstalled. Boeing's internal tracking systems failed to log the maintenance action. The report states, "Boeing did not have procedures to ensure that the required safety documentation or final inspections were completed after door plug reinstallation." The door plug, which is used to cover an optional emergency exit area on high-density seating configurations, is designed to be held in place by 12 fittings and four key retention bolts. The NTSB confirmed that the plug gradually shifted out of position and ultimately detached due to missing fasteners. Inadequate Training and Procedures The NTSB noted that Boeing’s assembly teams lacked adequate training to properly handle door plug installations. The company’s work instructions were described as overly complex and lacking clarity, particularly regarding non-routine work. The investigation found that the work was performed by a team unfamiliar with the procedure. It was further revealed that quality assurance staff failed to verify the bolt installation, allowing the aircraft to proceed through final assembly and delivery without detecting the omission. FAA Oversight Deficiencies In addition to Boeing’s errors, the NTSB cited the FAA’s ineffective compliance and surveillance mechanisms. While the agency had conducted multiple audits at Boeing facilities in prior years, it failed to detect or address systemic lapses in documentation, workforce training, and final assembly inspections. The NTSB concluded that the FAA’s oversight was “inadequate to identify recurring noncompliance” and did not sufficiently mitigate risk associated with critical assembly processes. Probable Cause and Contributing Factors The report states the probable cause of the accident as: "The in-flight separation of the left mid-cabin exit door plug due to the failure of Boeing to ensure that the plug was reinstalled with all required retention hardware during production... Contributing to the accident was the FAA’s ineffective oversight of Boeing’s production processes and safety compliance." Safety Recommendations Issued In total, the NTSB issued 19 safety recommendations, including: A redesign of the 737-9 MAX mid-exit door plug to prevent inadvertent displacement Improved documentation protocols and quality control procedures for component removal and reinstallation Enhanced workforce training for Boeing production and quality assurance personnel Strengthened FAA audit procedures and risk-based surveillance methods Mandated tracking of critical fastener installation for all high-risk components Nine recommendations were directed to Boeing and ten to the FAA. In a statement, Boeing acknowledged the findings and stated that it has implemented "significant corrective actions" in response to the incident and the investigation. The company has committed over $1 billion toward improving safety systems, production oversight, and employee training across its 737 program. The FAA stated that it is reviewing the NTSB’s recommendations and has already implemented a production cap on 737 MAX aircraft pending further compliance improvements. The January 2024 incident raised renewed scrutiny of the Boeing 737 MAX program, which had previously been grounded worldwide following two fatal crashes in 2018 and 2019. Following this event, hundreds of MAX 9 aircraft were temporarily grounded for inspection by the FAA, leading to widespread schedule disruptions for multiple airlines.

Investigation

NTSB Blames Boeing for Manufacturing Errors for Alaska Airlines Door Plug Incident

Aviation Today News Desk / July 11, 2025

Washington, D.C., United States: The National Transportation Safety Board (NTSB) has released its final report into the in-flight depressurization incident

Johor, Malaysia: A Royal Malaysia Police (RMP) helicopter crashed into Sungai Pulai during a multinational security exercise on Thursday morning, injuring five officers. As of Friday morning, two of the injured remain in critical condition, while three are reported stable and under observation at Sultanah Aminah Hospital in Johor Bahru. The incident occurred during a ceremonial fly-past as part of the Multilateral Nuclear Security Detection Exercise (MITSATOM 2025), which involves participation from Malaysia, Singapore, Indonesia, and Thailand. The Airbus AS355N helicopter, registered 9M-PHG, took off at 9:51 AM from the Tanjung Kupang Police Station and nosedived into the river approximately 46 minutes later, near a jetty in Gelang Patah. Condition of Crew Members The five officers onboard were quickly rescued by marine police units present at the scene. They were immediately transferred to hospital for emergency medical care. According to the Royal Malaysia Police, the following personnel were on board: ACP Faizul Mohammad (pilot) Supt Ahmad Bustamin Baharom (co-pilot) Insp Muhammad Yusri Hamzah (observer) Sgt Mohd Firdzus Zulkifli L/Kpl Mohammad Farid Fikri Mat Noor The Inspector-General of Police confirmed that two officers are in critical condition and receiving respiratory support in the Intensive Care Unit, while the remaining three are stable. Investigation and Safety Review The Civil Aviation Authority of Malaysia (CAAM) has initiated a formal investigation into the crash in accordance with Part XXVI of the Civil Aviation Regulations 2016. The case has been transferred to the Air Accident Investigation Bureau (AAIB) under the Ministry of Transport. Authorities are currently focused on recovering the helicopter's black box and flight data recorders. The wreckage remains partially submerged, and recovery operations are ongoing. The helicopter involved in the crash was an Airbus AS355N model, which has been in service with the police since 1996. Following the incident, a dedicated technical committee has been formed to assess the viability of the AS355N fleet and determine whether the aircraft model should continue operating within the police force. Official Statements and Inter-Agency Coordination The Ministry of Science, Technology and Innovation (MOSTI) has confirmed its full cooperation with the investigation. In a public statement, the ministry said it will support the authorities in examining all safety and procedural aspects linked to the incident. No fatalities have been reported. The swift response by marine units and on-site personnel was instrumental in the immediate rescue of all five crew members. Further updates will be provided following the conclusion of the investigation and medical assessments.

Helicopter Crash, Uncategorized

Malaysia Police Helicopter Crash: 5 Injured and 2 in Critical Condition, Probe Underway

Aviation Today News Desk / July 11, 2025

Johor, Malaysia: A Royal Malaysia Police (RMP) helicopter crashed into Sungai Pulai during a multinational security exercise on Thursday morning,

Aviation Today

DGCA Confirms 65 Engine Shutdowns Since 2020 and 11 Maydays in Last 17 Months

Air China A350 Breaches Altitude Separation, Near-Miss with Cargo Jet Over Russia

Stolen Cessna Causes Disruption at Vancouver Airport, Suspect Had No Pilot License

All Four Aboard Killed in Southend Airport Crash, AAIB Recovers Flight Recorders

Emirates Begins Pilot Hiring Roadshows Across UK, Ireland, Greece, Serbia and Hungary

Severe Storms Trigger 5,000+ Flight Delays and 800 Cancellations Across U.S. Airports

Small Aircraft Crashes Seconds After Takeoff from Southend Airport, UK AAIB Probes

Cockpit Voice Captures Fuel Cutoff Confusion in Air India AI171 Crash Preliminary Report

NTSB Blames Boeing for Manufacturing Errors for Alaska Airlines Door Plug Incident

Malaysia Police Helicopter Crash: 5 Injured and 2 in Critical Condition, Probe Underway

Follow Us

Quick Links

Navigate

General Support

News Desk Support

Follow Us