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

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

July 14, 2025

Ahmedabad, India: The Aircraft Accident Investigation Bureau (AAIB) has released the preliminary report into the crash of Air India’s Boeing 787-8 Dreamliner, registration VT-ANB, which occurred on 12 June 2025 shortly after takeoff from Ahmedabad’s Sardar Vallabhbhai Patel International Airport. The scheduled flight, operating as AI171, was bound for London Gatwick Airport with 230 passengers, 10 cabin crew, and 2 flight crew on board. All 241 persons on board perished in the accident. Additionally, 19 fatalities were reported on the ground. Aircraft and Crew Information The aircraft involved was a Boeing 787-8 with serial number 36279, manufactured in 2013, and operated by Air India. Both engines were General Electric GEnx-1B series units, installed in March and May 2025 respectively. The aircraft had a valid Certificate of Airworthiness and had undergone its last Airworthiness Review on 22 May 2025. The Pilot-in-Command held an ATPL with over 15,638 hours of total flying experience, including 8,596 hours on type. The First Officer held a CPL with 3,403 hours of total flying experience, of which 1,128 hours were on type. Both pilots were based in Mumbai, had arrived in Ahmedabad the previous day, and had met required rest periods. The First Officer was the Pilot Flying for the accident flight. Sequence of Events On 12 June 2025, VT-ANB had earlier operated AI423 from Delhi and landed at Ahmedabad at 05:47 UTC. A post-flight defect regarding “STAB POS XDCR” was logged and addressed by on-duty maintenance personnel before the aircraft was released for its next flight. Flight AI171 was scheduled for departure at 07:40 UTC. The aircraft pushed back from Bay 34 at 07:48 UTC, taxied to Runway 23, and received takeoff clearance at 08:07:33 UTC. The aircraft began its takeoff roll at 08:07:37 UTC. According to data recovered from the Enhanced Airborne Flight Recorder (EAFR), the aircraft reached V1 at 08:08:33 UTC and rotation speed (Vr) at 08:08:35 UTC. It lifted off at 08:08:39 UTC and reached a maximum recorded indicated airspeed of 180 knots at 08:08:42 UTC. At that moment, both engine fuel control switches, first for Engine 1 and then for Engine 2, with a one-second interval transitioned from the “RUN” to the “CUTOFF” position. The data indicated an immediate decrease in N1 and N2 engine speeds, consistent with fuel supply being cut off. Cockpit voice recordings captured a pilot questioning the action, with one asking, “Why did you cut off?” and the other responding that he had not. No further verbal conflict or distress was recorded before the power loss. Power Loss and Emergency Response The sudden loss of thrust from both engines triggered the deployment of the Ram Air Turbine (RAT), visible on CCTV footage from the airport. The RAT began supplying hydraulic power by 08:08:47 UTC, confirming the engines were no longer providing power. At 08:08:52 UTC, the Engine 1 fuel control switch was moved back to “RUN,” followed by Engine 2 at 08:08:56 UTC. The Auxiliary Power Unit (APU) inlet door also began to open at this time, indicating an automatic start sequence. Both engines attempted relight: Engine 1 showed signs of core recovery, while Engine 2 relit but could not stabilize its core speed. At 08:09:05 UTC, a MAYDAY call was transmitted by one of the pilots. No further communication was received. The aircraft lost altitude rapidly and crashed into the BJ Medical College hostel complex approximately 0.9 nautical miles from the end of Runway 23. The impact caused destruction of five buildings and extensive fire damage. All occupants of the aircraft were fatally injured. According to the report, the Emergency Locator Transmitter (ELT) was not activated during the sequence. Recovery and Wreckage The wreckage was spread across an area of approximately 1000 feet by 400 feet. The vertical stabilizer, main landing gear, fuselage components, both engines, and nose gear were found at various distances from the initial impact point. The thrust levers were discovered near the idle position, though flight data indicated they were forward (takeoff thrust) until impact. The fuel control switches were found in the “RUN” position post-crash. The forward EAFR was successfully recovered and downloaded using equipment supplied by the U.S. National Transportation Safety Board (NTSB). It contained approximately 49 hours of flight data and two hours of audio, including the accident flight. The aft EAFR was too severely damaged to retrieve data. Ongoing Investigation The investigation team comprises AAIB India officers, subject matter experts, and international participants from NTSB (USA), Boeing, General Electric, the FAA, and authorities representing nations whose citizens were onboard. As of the preliminary report, there are no recommendations issued to operators or manufacturers of the B787-8 aircraft or GEnx-1B engines. Fuel samples tested from the bowsers and tanks used to refuel the aircraft were found satisfactory. Additional trace samples collected from the APU and refuel/jettison systems are being sent for further testing. Statements from witnesses and the sole surviving passenger have been recorded. Post-mortem analyses are underway to determine any relevant aeromedical findings. The AAIB emphasized that the investigation remains ongoing, and all evidence, including maintenance records, crew history, and system components, will continue to be evaluated.

Investigation

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

July 12, 2025

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

July 11, 2025

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

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

July 11, 2025

United Kingdom: Unite the Union has raised serious concerns over the prevalence of sexual harassment across the UK and Ireland’s civil aviation sector. In an official statement issued on 8 July 2025, the union confirmed that frontline workers including cabin crew, check-in agents, baggage handlers, and ground staff continue to face persistent and under-reported incidents of workplace harassment. These findings were released as part of Unite’s ongoing Zero Tolerance to Sexual Harassment campaign, which seeks to enforce employer responsibility following the Worker Protection (Amendment of Equality Act 2010) Act 2023. The Act legally mandates employers to take proactive steps to prevent harassment in the workplace. Reported Conditions in Civil Aviation While the union’s public release did not include numerical data, a follow-up report by International Airport Review presented detailed figures attributed to Unite’s internal survey. These findings were based on data gathered from workers in the civil air transport sector. According to the report: “Over one-third of women working in UK and Ireland civil air transport have been sexually assaulted in the workplace.” Additional data shared in the same article includes: 67% experienced unwanted flirting or sexual gestures 65% were subjected to sexually offensive jokes 55% reported inappropriate touching 40% said pornographic images were shown or shared at work 47% said they experienced harassment on more than two occasions 34% said such incidents occurred more than once 80% of affected workers did not formally report the incidents 76% stated their employer took no action when incidents were reported These findings point to systemic issues in workplace culture across civil aviation roles, where the combination of shift-based work, hierarchical operations, and frequent passenger interactions may increase vulnerability while discouraging reporting. Unite’s Position and Recommendations In response, Unite is urging aviation employers and regulators to take immediate action. The union’s demands include: Implementation of mandatory sexual harassment policies across all aviation employers Sector-specific training for frontline staff and managers Paid release time and formal recognition for trained equality representatives An extension of the current three-month employment tribunal time limit for sexual harassment cases Unite General Secretary Sharon Graham reiterated that aviation workers deserve the same protections as those in any other sector. She called for stronger enforcement mechanisms and urged employers to move beyond compliance to create genuinely safe and respectful workplaces. About Unite the Union Unite the Union is the largest trade union in the United Kingdom and Ireland, representing over 1.2 million members across a wide range of sectors including aviation, transport, manufacturing, and public services. The union plays a leading role in advocating for workers’ rights, collective bargaining, and workplace safety. It is particularly active in the aviation sector, representing staff at major airlines, airports, and ground handling firms. Unite also maintains a network of trained equality representatives and provides legal, mental health, and policy support to members facing harassment or discrimination at work.

Civil Aviation Workforce

1 in 3 Women in UK & Irish Aviation Sexually Assaulted, Unite Backed Report Reveals

July 10, 2025

Rajasthan, India: Two Indian Air Force (IAF) pilots were killed after a Jaguar trainer aircraft crashed during a routine training sortie near Churu district in Rajasthan on Tuesday afternoon. The aircraft had taken off from Air Force Station Suratgarh and was operating as part of a scheduled training mission when the incident occurred. Aircraft Involved and Crash Location The aircraft involved was a twin-seat SEPECAT Jaguar, used by the IAF primarily for ground attack and tactical reconnaissance roles. According to officials, the crash took place around 1:25 PM near Bhanoda village, approximately 40 kilometers from Suratgarh. The aircraft came down in an open agricultural field and was engulfed in flames shortly after impact. Eyewitnesses in the area reported hearing a loud explosion followed by a large plume of smoke. Local authorities confirmed that the debris was scattered across a wide radius, but no civilian injuries or property damage occurred on the ground. In an official statement released shortly after the incident, the Indian Air Force confirmed: “A Jaguar aircraft met with an accident during a training sortie from Air Force Station Suratgarh. Both pilots onboard sustained fatal injuries. A Court of Inquiry has been ordered to ascertain the cause of the accident.” Emergency response teams from the IAF and local civil administration arrived at the site to secure the wreckage and begin preliminary investigations. Inquiry Initiated A Court of Inquiry has been constituted to investigate the circumstances leading to the crash. Investigators are expected to examine flight data, maintenance records, communication logs, and eyewitness accounts. As per procedure, all training missions involving Jaguar aircraft have been temporarily reviewed for operational checks. This is the third reported Jaguar crash involving the Indian Air Force in 2025. Previous incidents occurred in March (Haryana) and April (Gujarat). In each case, aircraft of the same class were involved. Background on the Jaguar Fleet The Jaguar, originally developed by Anglo-French collaboration in the 1960s, has been a part of the IAF fleet since the late 1970s. While the platform has undergone multiple upgrades under programs such as DARIN III, many of the aircraft remain structurally dated, raising long-standing concerns over operational risk and survivability systems especially in trainer variants. Despite recent enhancements, the fleet has faced increasing scrutiny due to rising maintenance requirements and the limited effectiveness of legacy safety systems, including ejection seats. The IAF has yet to formally announce a retirement schedule for the Jaguars, which were earlier projected to remain in service until the early 2030s. The outcome of the inquiry will determine whether additional measures are required concerning training protocols, fleet readiness, or aircraft systems. No additional information about the identities or ranks of the pilots has been released by the IAF as of this report. The next of kin have been informed, and appropriate military honors will follow.

Military Aviation

Two Indian Air Force Pilots Killed in Jaguar Crash, Third Training Accident in 2025

July 10, 2025

Manitoba, Canada: Two student pilots lost their lives in a mid-air collision involving training aircraft operated by Harv’s Air near Steinbach South Airport in the Rural Municipality of Hanover, Manitoba. The incident occurred at approximately 8:45 a.m. on 8 July during routine circuit training. According to the Royal Canadian Mounted Police (RCMP), the aircraft involved a Cessna 152 and a Cessna 172 collided roughly 400 metres from the runway while performing training exercises involving takeoffs and landings. Emergency services responded swiftly, but both pilots ,one male and one female were pronounced dead at the scene. No passengers were on board either aircraft. The names of the deceased have not yet been released pending family notifications. Both aircraft were registered to Harv’s Air, a well-established flight training school in Manitoba. Initial information suggests that one aircraft was on final approach while the other was climbing out, likely after a touch-and-go. The school’s owner indicated the collision may have resulted from a breakdown in visual separation or communication between the two student pilots. Weather conditions were reported to be favourable at the time of the accident. There is no evidence of mechanical failure or external interference. RCMP have ruled out criminal involvement. The Transportation Safety Board of Canada (TSB) has launched a full investigation. Officials are analyzing flight logs, maintenance records, and any available radio communications. A team has been dispatched to the site to conduct a detailed examination of the wreckage and to interview witnesses and school personnel. Harv’s Air released a statement expressing condolences to the families and confirming that flight training operations have been suspended temporarily out of respect and to support the investigation. Previous Incident in British Columbia In a separate incident earlier this year, on April 18, 2025, a Cessna 172 operated by Principal Air crashed near Chilliwack Airport, British Columbia, during a dual training flight. Both the flight instructor and the student pilot were killed. That flight was also being conducted under daylight VFR conditions and remains under investigation by the TSB. Authorities have not indicated any systemic issues linking the crashes, but findings from both investigations may contribute to broader safety reviews across the general aviation training sector. Further updates will be provided as the investigations proceed

Aircraft Crashes

Two Student Pilots Killed in Mid-Air Collision During Circuit Training in Manitoba

July 9, 2025

New Delhi, India: The Directorate General of Civil Aviation (DGCA), Government of India, has officially launched a structured ranking system for all DGCA-approved Flying Training Organizations (FTOs) operating across the country. The move is part of a broader strategy to enhance the quality, safety, standardization, and regulatory oversight in India’s pilot training ecosystem. Objective Behind the Ranking Framework The newly introduced framework aims to: Ensure training quality and standardization by establishing uniform evaluation benchmarks across all FTOs. Enhance transparency and accountability, allowing regulatory bodies, students, and stakeholders to access comparable and verifiable data regarding FTO performance. Assist aspiring pilots and families in identifying credible and high-performing training institutions based on consistent performance metrics, rather than location, marketing claims, or cost. Support policy-making and regulatory monitoring by enabling DGCA to identify well-performing FTOs for potential growth or collaboration, while subjecting underperforming ones to additional scrutiny or corrective measures. Implementation Schedule and Evaluation Cycle The ranking system will be operational starting 1st October 2025. Rankings will be released twice a year, preferably on 1st October and 1st April. Each FTO will be scored and categorized based on its overall performance against a comprehensive set of pre-defined parameters. Ranking Categories FTOs will be classified under the following categories, based on percentage scores: Score Range (%) Category 85% and above A++ 70% to less than 85% A+ 50% to less than 70% A Below 50% B FTOs falling under Category B will be issued a notice by the DGCA for self-assessment and performance improvement. Evaluation Parameters and Weightage Each FTO will be assessed using a combination of quantitative and operational metrics across various domains. The parameters and their corresponding weightages are as follows: 1. Infrastructure & Training Capacity Fleet size (single and multi-engine): 5% Availability of ground school & simulators: 5% Instructor-to-aircraft ratio (annual): 10% Student-to-instructor ratio (annual): 10% 2. Operational Performance Average time to complete 200 flying hours: 10% Utilization of each aircraft in past 6 months: 5% Ratio of trainees completing 200 hrs to new cadets enrolled (12 months): 5% 3. Safety & Regulatory Compliance Significant safety concerns (Level-I) raised in DGCA audits: 5% BA (Breath Alcohol) positive cases in past 12 months: 5% Number of accidents in past 12 months: 18% Number of incidents in past 12 months: 2% Non-reporting of accidents/incidents: Penalty of -5 per case 4. Maintenance Support Fleet-to-AME (Aircraft Maintenance Engineer) ratio: 10% 5. Student Support & Institutional Practices Availability of financial aid or scholarships: 2% Placement assistance in the aviation sector: 2% Transparency in payment and refund policies: 2% Resolution of student grievances: 4% Data Submission and Verification All FTOs are required to submit their performance data as per timelines set by the DGCA. The regulator reserves the right to verify data through audits and inspections. Any form of misreporting or non-compliance will result in a lower ranking and may attract regulatory action.

Flying Training Organization

India’s Flying Training Organizations to Be Ranked by DGCA Under New Evaluation Policy

July 9, 2025

India: On the morning of July 8, 2025, IndiGo flight 6E-7295, operating from Indore to Raipur, was compelled to return to its departure airport shortly after takeoff due to a technical fault detected in-flight. The aircraft, which departed Indore around 6:35 a.m. IST, had traveled approximately 60 nautical miles when the flight crew identified the issue. Acting in accordance with standard operating procedures, the pilot made a precautionary decision to turn the aircraft back to Indore to ensure passenger and crew safety. The aircraft landed without incident, and no injuries were reported. A total of 51 passengers were on board at the time. In a statement, IndiGo confirmed the incident and stated that an internal technical assessment is currently underway. The airline has provided affected passengers with the option of rescheduling their journey or receiving a full refund. IndiGo reiterated that the decision to return was made purely as a safety measure. The Directorate General of Civil Aviation (DGCA) has been informed, and further inspection of the aircraft is in progress. Flight 6E-784 Delayed in Surat Due to Bee Swarm Near Cargo Hold In an unrelated event, IndiGo flight 6E-784, scheduled to operate from Surat to Jaipur on July 7, 2025, experienced a delay of nearly one hour following an unusual disruption caused by a swarm of bees. The incident occurred while the aircraft was on the ground and preparing for pushback. Airport ground staff observed a cluster of bees gathered near the aircraft’s cargo door, raising safety and operational concerns. In response, airport authorities deployed a fire engine to disperse the swarm safely without causing harm to passengers or wildlife. Following clearance and a thorough external check of the aircraft, the flight resumed operations and departed without any further issues. IndiGo acknowledged the delay and issued an apology to passengers for the inconvenience. The DGCA has not issued any advisories or penalties in connection with these events as of this report.

Incidents

IndiGo Flight Returns Mid-Air to Indore Due to Technical Problem, 51 Passengers Safe

July 8, 2025

Malaysia

AirAsia to Acquire Up to 70 Airbus A321XLRs, Plans Low-Cost Flights to Europe & US

July 8, 2025

Wald im Pinzgau, Austria: A German-registered light aircraft crashed in the Austrian Alps on Saturday afternoon, killing all four occupants onboard. The crash occurred near the Trattenbach glacier in the municipality of Wald im Pinzgau, Salzburg state. Authorities have launched a joint investigation into the incident. Flight Details and Crash Site The aircraft, a single-engine propeller plane, departed from Oberschleißheim airfield near Munich, Germany. It was conducting a sightseeing flight over the Alps when it disappeared from radar around 12:45 PM local time. Emergency services located the wreckage at an altitude of approximately 2,300 meters in a remote, mountainous area. The aircraft had impacted steep terrain and caught fire on impact. Rescue units confirmed that all four occupants were deceased at the scene. Victim Identification Austrian and German authorities have identified the victims as: A 70-year-old man from the Ebersberg district, Bavaria His 33-year-old son from Regensburg The son’s 33-year-old girlfriend The 59-year-old pilot from Markt Schwaben All victims were German nationals. The families have been notified. Response and Recovery Operations Over 70 personnel from fire and rescue services participated in the recovery effort, which was complicated by the inaccessible terrain and high elevation. The aircraft’s ballistic recovery system had not deployed during the crash and had to be safely disarmed before wreckage recovery could begin. The bodies were recovered and transported to Salzburg for forensic examination. The public prosecutor’s office has ordered autopsies as part of standard procedure. Investigation The cause of the crash remains under investigation. Austrian air accident investigators, in coordination with German authorities, are examining possible technical faults, pilot error, and weather conditions. No adverse weather was reported at the time of the flight. The aircraft did not carry a flight data recorder or cockpit voice recorder, as these are not mandatory for this category of aircraft. Investigators are analyzing radar data, flight planning records, and available GPS traces. Wreckage analysis is being conducted on-site and will continue at a secured facility. No preliminary findings have been released. The Austrian Safety Investigation Authority (SIA) is leading the technical investigation, while the Salzburg prosecutor’s office oversees the legal process. Authorities have confirmed that the airspace around the crash site remains restricted pending completion of fieldwork.

Aircraft Crashes

German Sightseeing Flight Crashes in Austrian Alps, All Four German Nationals Killed

July 7, 2025

Bengaluru, India: A Commercial Pilot scheduled to operate Air India flight AI 2414 from Bengaluru to Delhi collapsed inside the cockpit just before takeoff on Friday morning, triggering a delay and raising fresh concerns about pilot health and fatigue within the aviation sector. Pilot Collapses During Pre-Flight Checks The incident occurred at Kempegowda International Airport while the flight crew was completing mandatory pre-flight procedures. According to sources, the pilot fell ill while signing the aircraft’s technical log, a standard requirement before pushback. Airport medical teams and ground staff responded promptly, and the pilot was transported to a nearby hospital, where he is reported to be in stable condition. Air India confirmed the incident stating, “The operating pilot on AI 2414 (Bengaluru–Delhi sector) reported unwell during pre-flight checks and was immediately attended to. A standby pilot was arranged, and the flight departed with a revised schedule. The pilot is under medical care and is stable. All relevant safety procedures were followed.” Flight Departed After Crew Replacement Air India quickly activated its standby crew protocol. The replacement pilot assumed command of the flight after mandatory clearance checks. Flight AI 2414, originally scheduled to depart at 3:05 AM IST, eventually took off at 4:36 AM IST and landed in Delhi at approximately 7:30 AM. Passengers were kept informed during the delay, and no further disruptions were reported. This medical emergency comes just weeks after another concerning incident involving pilot health. On April 9, 2025, a First Officer with Air India Express suffered a fatal cardiac arrest shortly after operating a domestic flight from Srinagar to Delhi. According to reports, the young pilot, identified as Captain Armaan, vomited inside the cockpit shortly after landing. He exited the aircraft and collapsed outside the galley area. Emergency services rushed him to the hospital, but he was declared dead on arrival. The back-to-back nature of these incidents has led to growing concern about health risks among commercial pilots, especially in the wake of demanding flight schedules and overnight duties. The Directorate General of Civil Aviation (DGCA) has been actively monitoring airline crew rostering practices, particularly at Air India. Earlier this year, the regulator identified multiple violations in flight and duty time limitations (FDTL) and rest requirements. Following an internal audit, Air India removed several officials involved in crew scheduling. The DGCA is also in the process of implementing revised FDTL norms effective July 2025. Key changes include: Increasing weekly rest time from 36 to 48 hours Limiting the number of night landings to two per week Capping consecutive night duties to three Mandatory off-duty period for red-eye (overnight) flights These changes aim to reduce fatigue-related risks and improve operational safety across Indian carriers.

Pilots

Air India Pilot Collapses Before Takeoff, Raising Alarm Over Growing Crew Health Risks

July 5, 2025

« Previous Next »

Subscribe to our Newsletter

Email

Recent News

US Targets More Than 1,000 Space Launches And Reentries Annually By 2030

US Targets More Than 1,000 Space Launches And Reentries Annually By 2030

August 22, 2026

The measures follow the July 28 arrest of an off-duty Malaysia Airlines second officer in Jakarta after over 26kg of MDMA and methamphetamine were seized The measures follow the July 28 arrest of an off-duty Malaysia Airlines second officer in Jakarta after over 26kg of MDMA and methamphetamine were seized

Malaysia Tightens Aviation Rules With Stricter Drug And Alcohol Screening For Crews

August 22, 2026

Maine, United States: A Diamond DA20-A1 Katana single-engine aircraft crashed into the water near Fort William Henry in Bristol, Maine, on Thursday, August 20, killing the pilot and injuring the passenger. Two men were aboard the aircraft when it went down near the mouth of the Pemaquid River, where it empties into Pemaquid Harbor. The crash was reported at around 1 p.m. local time, while the Federal Aviation Administration placed the crash time at approximately 1:40 p.m. The aircraft came down near Fort William Henry in the New Harbor area of Bristol, in Lincoln County, and was found upside down in approximately four feet of water close to shore. The aircraft was identified by the FAA as a Diamond DA20, a two-seat, single-engine aircraft. Aircraft-registration and aviation records identify the accident aircraft as N83RF, a 1996 Diamond DA20-A1 Katana, serial number 10139. The aircraft is a fixed-wing, single-engine airplane with two seats and a Rotax reciprocating engine. Current registration data identifies it as privately registered rather than operated by an airline. According to the Lincoln County Sheriff's Office, the aircraft had departed Brunswick Executive Airport and was headed for Knox County Regional Airport in Owls Head, roughly east of the crash site. Investigators initially believed the aircraft may have experienced a mechanical problem, but officials stressed that the actual cause had not been established. The sheriff's office said, “Initial information indicated the aircraft had left Brunswick Airport with a destination of the Knox County Airport and possibly experienced some type of mechanical failure.” The aircraft's final moments were followed by a rapid response from people on the shoreline. Nearby residents and a building crew who witnessed the crash rushed into the water to help. The pilot was pulled from the aircraft but died at the scene, while the passenger managed to escape from the wreckage on his own. The passenger was taken to MaineHealth Lincoln Hospital in Damariscotta, at the Miles campus, with non-life-threatening injuries. Officials said he was expected to survive. The identities of both occupants had not been released in the latest reports. The emergency response involved the Bristol Fire and Rescue Department, Lincoln County Sheriff's Office and Central Lincoln County Ambulance Service. The Maine Marine Patrol also assisted at the crash site. Responders placed containment equipment around the aircraft, which was lying inverted in the shallow harbor water. A local marine barge was subsequently used to remove the Diamond DA20 from the water. The aircraft was taken to a secure location where it could be examined as part of the federal investigation. The Federal Aviation Administration and National Transportation Safety Board are investigating the crash. FAA public affairs specialist Rick Breitenfeldt said the “FAA, as well as the National Transportation Safety Board, will investigate the cause of the crash.” No official cause had been determined as of the latest available reports. The initial reference to a possible mechanical failure remains only an investigative lead and should not be presented as the confirmed cause. The NTSB is expected to examine the aircraft, its maintenance history, flight data and other operational factors before determining what led to the crash.

Diamond DA20 Crashes Into Water Near Bristol; Pilot Killed, Passenger Injured

August 21, 2026

Former Airline Co-Pilot Sentenced To Life For Killing Former Captain, Plotting Five More

Former Airline Co-Pilot Sentenced To Life For Killing Former Captain, Plotting Five More

August 21, 2026

Sydney, Australia: The Australian Transport Safety Bureau (ATSB) on Friday, August 21, 2026, confirmed an investigation into a fourth ground-safety incident at Sydney Airport within just over three weeks, involving two Qantas aircraft that received potentially conflicting taxi instructions on August 18. The investigation, AO-2026-091, concerns an Airbus A321, registration VH-OGA, operating Qantas Flight QF405 to Melbourne, and a Boeing 737-838, registration VH-VXL, operating Qantas Flight QF589 from the Gold Coast. The ATSB's latest announcement said investigators will interview the air traffic controllers and flight crews involved, examine recorded data and collect other relevant evidence. The agency has not yet determined a cause or contributing factor and said a final report will be released after the investigation is completed. The August 18 event occurred at about 8:09 a.m. Australian Eastern Standard Time. After landing on Runway 34R, Qantas Boeing 737-838, QF589 taxied west on Taxiway Lima with clearance to turn right at Taxiway Bravo. At the same time, Qantas Airbus A321-271NY, QF405 was taxiing south on Taxiway Charlie after being cleared to turn right onto Taxiway Lima. As the A321 approached the taxiway, its crew saw the Boeing 737 approaching from the left and stopped the aircraft, allowing the 737 to pass. The ATSB classified the occurrence as an incident, with the aviation occurrence categories listed as failure to pass traffic and information/procedural error. There were no injuries or aircraft damage. The ATSB said there was “no immediate risk of collision” because QF405 braked normally before stopping. It nevertheless opened an investigation to understand the potential conflicting instructions given to the two crews. Airservices Australia said it reported the potential traffic conflict to safety authorities on Tuesday, August 18, and Qantas said its aircraft had been cleared to proceed in accordance with air traffic control instructions and that it would support the investigation. The latest event is the fourth Sydney Airport safety incident being investigated by the ATSB since July 27. Importantly, the ATSB has not found a common cause or fault in any of the four incidents at this stage. All four investigations remain active or pending, meaning claims that staffing shortages, training problems or the new Sydney Basin airspace changes caused the incidents would go beyond what the safety bureau has established so far. Airservices Australia has said the incidents involve different circumstances and that each is being examined on its individual facts. The first incident occurred on July 27, 2026, and is recorded by the ATSB as AO-2026-086 “Breakdown of coordination involving Bombardier DHC-8, VH-QOC, and Boeing 737, VH-XZG, at Sydney Airport.” The occurrence took place at 8:14 a.m. AEST and involved QantasLink Flight QLK424D, travelling from Canberra to Sydney, and Qantas Flight QFA124, travelling from Queenstown, New Zealand, to Sydney. ATC cleared the Boeing 737 to cross Runway 34L from Runway 25 while the QantasLink DHC-8 was still in its landing roll on Runway 34L. Controllers detected the developing conflict and alerted both crews, after which the 737 stopped beyond the runway holding point. The ATSB has classified the investigation as an active short occurrence investigation, with completion anticipated in Q4 2026. The second incident occurred on August 9 at about 7:20 a.m. and involved Jetstar Flight JQ402, an Airbus A320-232 registered VH-VQJ, and a Qatar Airways Boeing 777-300ER, registered A7-BEU, which was being towed by a tug. The ATSB's investigation number is AO-2026-087, titled “Taxiing proximity event involving Airbus A320-232, VH-VQJ and Boeing 777, A7-BEU, at Sydney Airport.” As the Jetstar aircraft taxied before departure for the Gold Coast, its crew saw the Qatar 777 in close proximity on a crossing taxiway. Both aircraft stopped abruptly, and a Jetstar cabin crew member was reported to have suffered a minor injury. No aircraft damage was reported. The incident triggered immediate scrutiny of ground operations. The Australian Transport Minister, Catherine King, said a ground controller and the tug operator were stood down for mandatory drug and alcohol testing, describing it as standard policy while the ATSB investigation was under way. “As is policy, the ground controller and tug operator have been stood down for mandatory drug & alcohol testing,” the minister's statement said. No passengers were injured, while the Jetstar crew member was assessed by paramedics. Only about three hours later, on the morning of August 9, Sydney Airport recorded its third incident in the sequence. The ATSB investigation, AO-2026-090, is titled “Runway incursion and rejected take-off involving Boeing 737-8SA, VH-IJQ, and Boeing 737-838, VH-XZH.” The aircraft were Virgin Australia Flight VA555, scheduled from Sydney to Perth, and Qantas Flight QF728, scheduled from Sydney to Ayers Rock Airport. At around 10 a.m., ATC cleared the Virgin Australia 737, registered VH-IJQ, for a full-length departure from Runway 34L. As the Virgin crew applied thrust, they saw the Qantas 737, registered VH-XZH, begin crossing the runway from Taxiway Lima. The Qantas crew reported that it had also received clearance from ATC to cross. The Virgin crew reduced thrust and stopped on the runway, while ATC simultaneously cancelled the take-off clearance. After the Qantas aircraft cleared the runway, the Virgin 737 was cleared to depart. The ATSB classified the occurrence as an incident involving information/procedural error, loss of separation, rejected take-off and runway incursion. No injuries or aircraft damage were recorded. The four incidents have also intensified scrutiny of Sydney's air traffic-control workforce and the major airspace changes introduced ahead of the opening of Western Sydney International Airport. CASA implemented the new Sydney Basin airspace arrangements on July 9, creating new controlled airspace around Western Sydney International and changing the structure around Sydney Kingsford Smith, Bankstown and Camden airports. CASA said the changes were designed to integrate the airports while maintaining capacity, efficiency and aircraft separation. Reuters reported that the ATSB had received a June report from an air traffic controller warning that staff at Sydney Airport were not adequately prepared for complex airspace and procedural changes linked to the opening of Western Sydney International Airport. The report cited concerns over limited training time and the volume of new material. CASA later found that Airservices Australia had implemented appropriate training, procedures and operational support arrangements. The sequence has also prompted warnings from aviation safety specialists. Retired commercial pilot and former ATSB safety investigator Geoff Klouth said the repeated events should be addressed quickly. “We've been very fortunate that there haven't been collisions, but it doesn't mean it won't happen in the future,” he said, warning that the consequences of a future failure could be catastrophic. For now, however, the official position remains that there is no established common cause behind the four incidents. The ATSB is examining each occurrence separately while also looking for common contributing factors. The July 27 coordination breakdown, the August 9 Jetstar-Qatar taxiing event, the August 9 Virgin-Qantas runway incursion and rejected take-off, and the August 18 Qantas taxiing conflict are all still under investigation. Until the ATSB releases its findings, staffing shortages, training pressures, airspace redesign and procedural errors should be treated as areas of concern or investigation rather than confirmed causes.

Sydney Airport Faces Fourth Safety Incident In Less Than A Month As ATSB Launches Probe

August 21, 2026

Aviation Today Perspectives

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

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

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

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

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

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

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

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

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

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

Follow Us

Facebook-f Instagram Linkedin-in X-twitter Youtube

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

Quick Links

About Us
Contact Us
Services
Advertise
FAQ

Navigate

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

General Support

info@aviationtoday.in

News Desk Support

news@aviationtoday.in

Follow Us

Facebook-f Instagram Linkedin-in X-twitter Youtube

© Copyright 2026 Aviation Today. All rights reserved.

Terms of Use
Privacy Policy
Disclaimer

Search

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

Aviation Newsletter

Facebook Instagram Linkedin X-twitter Youtube