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

SWISS A330 Diverts To Dublin After Smoke From Power Bank Reported Over Atlantic Flight

Incidents

SWISS A330 Diverts To Dublin After Smoke From Power Bank Reported Over Atlantic Flight

August 11, 2026

Two Pilots Killed As Sikorsky S-64 Crashes Fighting Utah’s Widemouth 2 Fire

Aircraft Crashes

Two Pilots Killed As Sikorsky S-64 Crashes Fighting Utah’s Widemouth 2 Fire

August 11, 2026

Baramati, India: A Cessna 172S training aircraft operated by Academy of Carver Aviation Pvt. Ltd. veered off the runway during a training exercise at Baramati Airfield in Maharashtra’s Pune district on Sunday, August 9, 2026. The aircraft, registered VT-SEX, had two people onboard flight instructor Captain Chirag Shashikant Doifode and cadet Abhijeet Jundre. Both escaped unharmed. The incident occurred at about 12:30 pm. The four-seat aircraft was conducting a Circuit and Landing Emergencies training exercise, during which the trainee was required to practise landing following an emergency scenario. Police and aviation authorities said the aircraft was involved in rejected-take-off exercises as part of the training sequence. According to the Ministry of Civil Aviation, the DGCA-approved Academy of Carver Aviation aircraft “suffered a runway excursion at Baramati Airfield.” The ministry said the aircraft “was involved in a Circuit and Landing Emergencies (CL Emergencies) training exercise” and was unable to stop within the paved runway surface before veering onto the extended paved area beyond the runway threshold. A DGCA Air Safety team was sent to the site to conduct a preliminary investigation. Police said the aircraft initially entered the runway through Link Bravo and lined up at the threshold of Runway 29, where it carried out a rejected take-off exercise. It was subsequently positioned at the threshold of Runway 11 for another rejected take-off exercise. During the sequence, the aircraft could not be brought to a complete stop and continued beyond the runway before veering onto the grassy area. Police said the aircraft travelled roughly 20 feet beyond the runway end before entering the grass. Inspector Narayan Pawar said, “The brakes of the aircraft seem to have not worked,” while adding that the situation was under control. Pune Rural Deputy Superintendent of Police Chaitanya Kadam confirmed that both occupants were safe. The aircraft sustained damage during the runway excursion. The Ministry of Civil Aviation said, prima facie, damage was found to the propeller, engine cowling and nose landing gear, with a detailed assessment to be conducted by the competent authorities. The cause of the incident has not yet been established. Police said investigators were examining whether the aircraft developed a technical problem or whether another factor contributed to the runway excursion. A senior police official said, “It is too early to comment on anything,” as the investigation was still at an early stage. Pune Rural Superintendent of Police Sandip Singh Gill said the aircraft skidded while landing. In a statement reported by Economic Times, Gill said: “An aircraft VT-SEX was involved in a runway excursion incident at Baramati Airfield during a training exercise, with Capt Chirag Shashikant Doifode and Cadet Abhijeet Jundre on board. No injuries have been reported.” The aircraft involved was a Cessna 172S, a four-seat single-engine trainer. The DGCA’s list of approved flying training organisations as of March 30, 2026, lists VT-SEX as a Cessna 172S operated by Academy of Carver Aviation Pvt. Ltd., whose flying base is near Baramati Airport. Carver Aviation’s own fleet information also lists VT-SEX among its training aircraft. There was therefore no injury to the cadet, no injury to the instructor and no fatality in the August 9 incident. The aircraft was not carrying passengers beyond the two flight-training occupants, and the incident occurred during a scheduled training exercise rather than a passenger operation. The incident has nevertheless renewed scrutiny of safety conditions at Baramati. Hindustan Times described it as the seventh aircraft accident or incident linked to Baramati’s aviation and flight-training operations since 2022, prompting calls for a broader review of infrastructure, operational systems and oversight. Aviation expert Dhairyashil Vandekar said the latest incident should trigger a comprehensive review of the airfield. “It is important that the safety and confidence of trainee pilots must be paramount,” Vandekar said, adding that Baramati’s infrastructure and operational systems need to keep pace with the volume of flying activity. He called for appropriate air traffic services, modern navigation and communication systems and stronger emergency-response infrastructure. The DGCA is now examining the circumstances and contributing factors behind the August 9 runway excursion. At present, authorities have not attributed the incident to a confirmed brake failure, mechanical defect, pilot error or any other specific cause. The investigation is expected to establish what led the Cessna 172S to leave the paved runway during the training exercise.

Incidents

Cessna 172S Suffers Runway Excursion At Baramati During Training, 2 Escape Unhurt

August 10, 2026

Atlanta, United States: Delta Air Lines Flight 2204 returned to Hartsfield-Jackson Atlanta International Airport on August 8 after fumes were reported in the flight deck shortly after departure, prompting an emergency landing and evacuation on the taxiway. The Boeing 757-200 was operating from Atlanta to Orlando International Airport in Florida when the flight crew detected the fumes and followed procedures to return to Atlanta. According to the Federal Aviation Administration, the aircraft landed safely at about 8 a.m. local time. The aircraft was carrying approximately 200 passengers and six crew members. After landing, passengers were evacuated using the aircraft’s emergency slides onto the taxiway rather than remaining onboard. Video shared by a passenger on TikTok showed passengers moving toward the exits and sliding onto the tarmac, while crew members could be heard directing them to leave their belongings behind and evacuate. A passenger, Jordan Conlin, who was traveling with his family, told Fox 5 Atlanta that the pilot announced that he and the co-pilot were wearing oxygen masks because of fumes in the cockpit and that the aircraft was turning back to Atlanta. Conlin also recalled the pilot instructing passengers to “brace” during the landing, describing the evacuation as chaotic as passengers left the aircraft. One crew member and one passenger received medical attention following the incident, while the remaining passengers were transported by ground crews to the terminal. Delta subsequently arranged a replacement aircraft to take the passengers to Orlando. Delta confirmed that the crew followed established procedures after reports of fumes in the flight deck and said a slide evacuation took place on a taxiway. The airline apologized to passengers, saying safety remained its top priority. The FAA said it is investigating the incident. The agency confirmed that Flight 2204 returned safely to Atlanta after reported smoke in the cockpit and that passengers evacuated via emergency slides onto the taxiway. The aircraft was taken for inspection following the incident. No fatalities were reported, and the available reports indicate that the aircraft landed safely before the evacuation was carried out. The precise source of the fumes or smoke has not been established publicly. The FAA investigation and aircraft inspection are expected to provide further information about what caused the reported condition in the flight deck.

Incidents

Delta Flight 2204 Makes Emergency Return To Atlanta After Fumes Reported In Cockpit

August 10, 2026

Sydney, Australia: A Jetstar Airbus A320 and a Qatar Airways Boeing 777 came dangerously close to a collision while moving on the ground at Sydney Airport on Sunday morning, August 9, after the Jetstar crew was forced to brake abruptly to avoid the Qatar aircraft. The incident occurred at about 7:00am local time at Sydney Kingsford Smith Airport. The Jetstar A320, operating flight JQ402 from Sydney to Gold Coast Airport, was taxiing for departure when its crew observed the Qatar Airways Boeing 777 being towed by an aircraft tug on a crossing taxiway. The ATSB said both aircraft were brought to an abrupt stop, preventing a collision. According to Australian media reports, the Jetstar aircraft stopped about 50 metres from the Qatar 777. The sudden braking caused a rear cabin crew member aboard the Jetstar aircraft to fall and suffer a broken wrist. No Jetstar passengers were injured. JQ402 was carrying 151 passengers and six crew members, according to Australian media reports. The flight was subsequently cancelled and passengers were rebooked onto later services. The Qatar Boeing 777 was not operating a passenger departure at the time. It had arrived at Sydney from Doha and was being repositioned under tow after passengers had disembarked. The aircraft therefore had no passengers onboard during the near-collision. The precise sequence that brought the two aircraft into such close proximity remains under investigation. Jetstar said its aircraft was following air traffic control instructions when its pilots were forced to brake firmly after another aircraft came into close proximity. The airline has also begun its own investigation. The ATSB said there was damage to the connection between the Qatar 777's nose landing gear and the aircraft tug. Investigators will examine data from both aircraft and air traffic control, while interviewing the flight crew, tug operators, air traffic controllers and other witnesses. CCTV and other recorded information will also be reviewed. ATSB Chief Commissioner Angus Mitchell said it was too early to determine where the communication or coordination breakdown occurred. Investigators will establish what instructions were issued, how they were understood and why the aircraft came so close before the final stop. The incident has also drawn attention to air traffic-control staffing pressures at Sydney Airport. ABC reported that air traffic control was operating under restrictions between 6:00am and 8:00am on Sunday, limiting the number of aircraft moving through the airport. More than 150 flights had also been affected by roster constraints in the days leading up to the incident. However, there is currently no official finding that the staffing situation caused the near-collision. The ATSB investigation will determine whether communication, coordination, ground movements, procedures or other factors contributed. Two people involved in the ground operation, an air traffic ground controller and the tug operator were stood down for mandatory drug and alcohol testing, which the federal transport minister described as standard post-incident procedure. Their stand-down should not be interpreted as a finding of fault. The ATSB has asked anyone with video of Sunday's incident or its immediate aftermath to provide footage to investigators. The investigation remains ongoing.

Incidents

Jetstar A320 And Qatar 777 Narrowly Avoid Collision During Taxiing At Sydney Airport

August 10, 2026

Tourist Helicopter Crashes In Rio’s Tijuca National Park, Killing All Four Onboard

Aircraft Crashes

Tourist Helicopter Crashes In Rio’s Tijuca National Park, Killing All Four Onboard

August 10, 2026

Australia Plans New Aviation Disability Standards To Improve Accessible Air Travel

Australia

Australia Plans New Aviation Disability Standards To Improve Accessible Air Travel

August 9, 2026

Malaysia Aviation Group Mandates Pilot Drug Tests After Alleged Drug-Trafficking Case

Airlines

Malaysia Aviation Group Mandates Pilot Drug Tests After Alleged Drug-Trafficking Case

August 8, 2026

Texas Couple Killed After Small Plane Crashes Near Bogalusa Airport In Louisiana, US

Aircraft Crashes

Texas Couple Killed After Small Plane Crashes Near Bogalusa Airport In Louisiana, US

August 8, 2026

California, United States: A United Airlines Boeing 737-800 operating Flight 1189 from San Francisco to Los Cabos, Mexico, returned to San Francisco International Airport (SFO) on Thursday after one of its tires was damaged during the takeoff roll, prompting the aircraft to turn back shortly after departure. Few media, citing air traffic control audio, reported that the tire burst during the takeoff roll, while United officially described the incident as damage to one tire. Flight-tracking data showed the aircraft turning back after roughly an hour in flight before landing safely at SFO at about 11:44 a.m. The aircraft was a Boeing 737-800 carrying 165 passengers and eight crew members. Despite the reported tire damage during departure, the aircraft completed the return flight and landed safely at its departure airport. United said there were no reported injuries among those onboard. United Airlines confirmed the incident in a statement, saying, “United flight 1189 sustained damage to one tire while departing San Francisco and safely returned to the airport.” The airline did not specify whether the tire failure was caused by a mechanical defect, debris, wear or another factor, and it did not identify the exact tire involved. Passengers were not taken directly into the terminal after landing. Instead, United said customers “deplaned via airstairs on the tarmac and were taken by bus to the terminal.” The procedure followed the aircraft’s return to SFO while the aircraft and the damaged tire were being inspected. United said it arranged another aircraft to continue the passengers’ journey to Los Cabos later that afternoon, stating, “We've arranged for a different aircraft to take them to Los Cabos later this afternoon.” This allowed the affected passengers to continue their original trip after the Boeing 737-800 was taken out of service for inspection. The incident also affected airport operations, the blocked runway caused delays to some other flights at SFO. There was no reported crash or emergency landing accident, but the circumstances surrounding the tire damage remain under review. The Federal Aviation Administration has said it will investigate the incident. As of the latest available update there are no further FAA findings and official cause has not been released.

Incidents

United Flight 1189 Returns To SFO After Tire Damage During Takeoff, FAA Probes

August 7, 2026

Airlines

EasyJet Agrees £5.7bn Apollo Takeover After Castlelake Walks Away From Bidding Race

August 7, 2026

Brazil Formally Accuses 16 Voepass Employees Over 2024 ATR Crash That Killed 62 SEO DES: Brazil's August 6 accusations follow CENIPA's final report after a two-year probe into negligence, maintenance failures, omissions and de-icing issues SOCIAL: Brazilian federal police have formally accused 16 current and former Voepass employees over the August 2024 ATR 72 crash that killed all 62 people aboard. The accusations follow a two-year criminal investigation into alleged negligence and safety failures. The probe cited improper maintenance, omitted technical failures, operational lapses and the aircraft’s de-icing problems. CENIPA’s final report, released July 23, identified 19 contributing factors, including severe icing, crew actions and regulatory weaknesses. The case now moves to Brazil’s Federal Public Prosecutor’s Office, which will assess the evidence and decide whether to bring criminal charges against those accused. Image: BBC Video: FOX 4 Dallas-Fort Worth Vinhedo, Brazil: Brazilian federal police have formally accused 16 current and former Voepass employees over the August 2024 crash of an ATR 72-500 that killed all 62 people aboard, opening a new criminal-responsibility chapter in the investigation nearly two years after the aircraft fell in Vinhedo, São Paulo. The accusations were announced by police on Thursday, August 6, 2026, after a two-year investigation into alleged malpractice, negligence, omissions and failures in the airline's operation and maintenance practices. Among those formally accused is Voepass owner and president José Luiz Felicio Filho. Federal police also accused 15 other current and former employees of endangering air traffic safety resulting in a fatal disaster, an offence that can carry a prison sentence of up to 12 years. Some of those accused additionally face allegations involving the omission of technical failures from aircraft logbooks. The 16 accused have not publicly commented on the police action, while prosecutors must now decide whether to bring formal criminal charges. The accident occurred on August 9, 2024, when Voepass Flight 2283 was operating from Cascavel in Paraná to São Paulo-Guarulhos. The ATR 72-500, registration PS-VPB, was carrying 58 passengers and four crew members. During the flight, the aircraft encountered severe icing conditions and progressively lost performance before entering an uncontrolled descent and flat-spin sequence. It fell about 13,000 feet and crashed into the grounds of a gated residential condominium in Vinhedo, killing everyone aboard. The latest criminal investigation has placed particular attention on what happened before the aircraft was dispatched for its final flight. Federal police investigator André Ribeiro said the ATR was irregularly cleared to depart despite known severe icing conditions and despite de-icing system failures occurring on three flights earlier that same day. Investigators also found from the aircraft's recorded data that the de-icing system had repeatedly failed or had been manually switched on and off during 136 flights. Ribeiro said the investigation represented a major turning point for Brazil's approach to aviation accidents and suggested that prosecutors should also examine possible responsibility involving Brazil's National Civil Aviation Agency, ANAC. The police investigation concluded that deliberate omissions, improper maintenance practices and organizational failures contributed directly to the decision to send the aircraft into dangerous weather. The new accusations follow the technical investigation already completed by Brazil's Center for Investigation and Prevention of Aeronautical Accidents, CENIPA. The Brazilian Air Force officially released the CENIPA final report on July 23, 2026, during a press conference in Brasília, after first presenting its findings privately to representatives and relatives of the victims. The 266-page report, identified as A-116/CENIPA/2024, was subsequently made available to the public through the CENIPA system. CENIPA did not assign criminal blame. Instead, its investigation reconstructed the technical, operational, human, organizational and regulatory factors that contributed to the accident. The report identified 19 contributing factors, including severe icing, failures involving the aircraft's de-icing system, crew actions, operational decision-making, maintenance shortcomings, organizational weaknesses and deficiencies in regulatory oversight. Earlier problems involving the aircraft's Airframe De-Icing system were not properly entered into maintenance records, while some maintenance activities were carried out without adequate supervision. CENIPA investigator Lieutenant Colonel Paulo Mendes Fróes said the company had developed a practice in which pilots and mechanics did not formally record aircraft problems so that aircraft could continue operating the following day. CENIPA said the crew's ability to process the warnings may have been affected by high workload and the phenomena known as “inattentional blindness” and “inattentional deafness”, in which critical information can fail to receive adequate attention despite being available to the crew. The investigation also identified weaknesses involving cockpit coordination, flight planning, pilot judgment, decision-making and the management of the aircraft's degraded performance. The investigation further found that the aircraft should not have been dispatched at the time of departure because of a fault involving its windshield-wiper system. CENIPA determined, however, that this particular defect did not directly contribute to the crash. More broadly, investigators found that maintenance practices and the airline's organizational processes allowed technical problems to remain unresolved or inadequately documented. ANAC's role also came under scrutiny in the CENIPA report. Investigators found that the regulator had previously identified weaknesses involving Voepass's maintenance controls, technical irregularities and other operational risks, but those findings did not translate into sufficiently effective risk-management measures to prevent the deterioration of the company's safety environment. ANAC said after receiving the report that it would conduct a detailed technical analysis of the findings and recommendations within its area of responsibility, with the review expected to take up to 120 days. CENIPA also issued safety recommendations extending beyond Voepass. One recommendation called for the European Union Aviation Safety Agency, EASA, to work with ATR on reviewing the aircraft's “Degraded Performance” procedure. Another recommendation concerned changing the “increase speed” alert from a caution-level alert to a warning-level alert, which would require immediate corrective action from the crew. With the Federal Police now having formally accused 16 people, the case moves into its next legal stage. The August 6 accusations therefore represent a separate development that follows the technical conclusions released by CENIPA on July 23. The accusations do not themselves constitute convictions or final criminal charges. The Federal Public Prosecutor's Office must determine whether the evidence warrants bringing charges against the accused. For the families of the 62 victims, however, the latest development marks a significant shift from determining what went wrong to examining who may ultimately be held legally responsible for allowing those failures to continue.

Investigation

Brazil Formally Accuses 16 Voepass Employees Over 2024 ATR Crash That Killed 62

August 7, 2026

« Previous Next »

Subscribe to our Newsletter

Email

Recent News

Milan, Italy: A baggage cart carrying checked luggage caught fire at Milan Malpensa Airport in Italy on Sunday, August 16, shortly before the baggage was due to be handled for a British Airways flight to London Heathrow, prompting airport firefighters to intervene and damaging a small number of passengers' bags. The incident occurred on the airport apron and did not involve a fire onboard the aircraft. The fire involved an Aviapartner baggage-handling cart at Milan Malpensa. The handling company operates ground services at the airport, and the cart had just completed baggage handling associated with a British Airways flight arriving from London when it caught fire. Initial reports focused on the possibility of a lithium-ion battery inside one of the bags, but subsequent airport-source information pointed to an electrical fault in the ground vehicle instead. The incident was captured on video by former BBC journalist Jon Sopel, who was at Malpensa waiting to travel on British Airways flight BA585 from Milan to London Heathrow. The footage showed dense black smoke rising from the baggage container, with flames visible around the luggage. Ground personnel moved other baggage containers away from the burning unit to prevent the fire from spreading before airport fire crews arrived. The aircraft associated with BA585 was an Airbus A321neo registered G-NEOT, powered by two CFM International LEAP-1A32 engines. The scheduled route was Milan Malpensa Airport (MXP) to London Heathrow Airport (LHR), with British Airways operating the service under flight number BA585. The fire occurred before the affected luggage could create a fire risk inside the aircraft. The burning baggage unit remained on the ground and was dealt with by airport emergency crews. The other containers were moved away from the fire, helping prevent the flames from spreading to additional baggage or equipment. Firefighters extinguished the blaze rapidly using water. British Airways confirmed that some passengers' checked baggage was damaged. In a statement, the airline said: “We’re aware of a small number of checked bags that were damaged by fire while on the ground at Milan Malpensa Airport. The incident was quickly dealt with, and there were no injuries or impact to any flights.” The airline added: “We’ve been in contact with the small number of customers whose bags are affected to apologise and provide support. We are working closely with our partners, and an investigation is underway to establish the cause.” That statement is significant because it confirms that the fire affected checked baggage on the ground but did not result in injuries or a fire onboard the aircraft. It also shows that British Airways had not initially announced a confirmed cause and was relying on an investigation with its ground-handling partners. The investigation remained underway, while British Airways confirmed that only a small number of checked bags were damaged and that there were no injuries.

British Airways BA585 Baggage Cart Carrying Checked Luggage Catches Fire At Milan

August 18, 2026

Krasnoyarsk, Russia: Hainan Airlines Flight HU753, operating from Beijing Capital International Airport in China to Manchester Airport in the United Kingdom, diverted to Krasnoyarsk International Airport in Russia on August 15 after the Airbus A330-300 developed a mechanical fault while flying over Siberia. The aircraft landed safely, with no injuries, deaths or damage reported. The flight was operated by an Airbus A330-343, registration B-304L, with 230 people on board. Flight-tracking data showed the aircraft departed Beijing for Manchester and was cruising at approximately FL340, or 34,000 feet, when the problem occurred. The aircraft was around 190 nautical miles southeast of Krasnoyarsk when it descended to approximately FL200 and diverted toward Krasnoyarsk International Airport. According to reports, the problem emerged approximately four hours into the flight. The aircraft's sensors detected the fault and the crew issued an emergency signal before diverting to Krasnoyarsk.. Russian emergency authorities had prepared for the aircraft's arrival, deploying 51 personnel and 15 vehicles. The response included 39 personnel and 11 vehicles from Russia's Ministry of Emergency Situations, according to reports. Emergency teams were positioned as a precaution, but the aircraft completed the landing without an accident. Russia's Emergencies Ministry confirmed that there were no injuries or deaths and that neither the aircraft nor airport infrastructure was damaged. English- and Chinese-speaking airport personnel were also reported to have assisted passengers and crew following the landing. Hainan Airlines confirmed the diversion and apologised to passengers. In its statement, the airline said: “On 15 August 2026, our flight HU753 (Beijing–Manchester) diverted to Krasnoyarsk International Airport in Russia due to a mechanical fault. The flight landed safely at 07:28 Beijing time.” The airline added: “The company plans to replace the aircraft to operate the onward flight. We will properly arrange passenger service support to ensure safe arrival at the destination. We sincerely apologise for any inconvenience caused to passengers.” Hainan Airlines also reiterated: “Hainan Airlines always adheres to the principles of safety first and passengers first, providing safe, comfortable and efficient services.” The exact nature of the mechanical fault has not been officially disclosed. Hainan Airlines described the problem as a “mechanical fault,” while Russian authorities referred to it as a technical malfunction. Therefore, claims that the incident involved a particular system failure should be treated cautiously. The diversion left passengers in Krasnoyarsk while Hainan Airlines arranged an onward journey. The airline said a replacement aircraft would be sent to Krasnoyarsk to continue the service to Manchester, while passenger support arrangements were being made.

Hainan Airlines Flight HU753 Diverts To Russia After Mechanical Fault Over Siberia

August 18, 2026

New Delhi, India: India’s Directorate General of Civil Aviation (DGCA) recorded 889 serious technical defects during flight operations in 2025, the highest figure in the five-year data released by the Civil Aviation Ministry, with cases rising nearly 28.5% from 692 in 2024. The figures were disclosed by Minister of State for Civil Aviation Murlidhar Mohol in a written reply in the Lok Sabha on August 6, 2026, in response to questions from Congress MP Shyamkumar Daulat Barve. The data showed 514 serious technical defects in 2021, 528 in 2022, 487 in 2023, 692 in 2024 and 889 in 2025. The 2025 total was 197 cases higher than the previous year and about 73% above the 2021 figure. However, the parliamentary disclosure does not provide an aircraft-by-aircraft breakdown of the 889 cases, including aircraft registration, model, airline or the specific technical fault involved. The figures therefore cannot be used to attribute the cases to particular Boeing or Airbus aircraft, engines or aircraft systems. Mohol said the DGCA has established Civil Aviation Requirements (CARs), safety advisories, directives and other regulatory instructions to ensure safe aircraft operations. He said, “For monitoring compliance, DGCA has a systematic safety oversight mechanism encompassing all aircraft and airport operators.” He added, “The safety oversight process includes regulatory audits, night surveillance, ramp inspections, spot checks and special audits. DGCA publishes the Annual Surveillance Plan (ASP) on its website.” The government data also showed that the DGCA took action over safety violations involving airlines and Maintenance, Repair and Overhaul (MRO) operators in 42 cases in 2025, compared with 31 in 2024, 24 in 2023, seven in 2022 and one in 2021. A separate parliamentary disclosure made in July 2025 provides airline-wise technical-defect figures and offers additional context, but it is a different dataset from the 889 serious-defect series. It recorded 183 technical defects reported by scheduled commercial airlines between January 1 and July 21, 2025. Air India and Air India Express together accounted for 85, IndiGo for 62, Akasa Air for 28 and SpiceJet for eight. The earlier data showed 421 technical defects in 2024, 448 in 2023, 528 in 2022 and 514 in 2021. The government said reported defects are investigated and appropriate rectification action is taken. Mohol said, “All defects reported by the airline to the Directorate General of Civil Aviation (DGCA) are required to be investigated for taking appropriate rectification action.” He further said, “The investigation of all defects, particularly major defects, has to be completed expeditiously so as to take preventive/corrective action at the earliest possible.” The government stated that major defects are investigated by the operator in association with the DGCA. The latest available 2026 data provides another indication of the technical issues being reported across Indian aviation, although it should not be added directly to the 889-case five-year series. The Civil Aviation Ministry told the Rajya Sabha on August 3 that 352 “significant technical defects” were reported in domestic and international flight operations between January and June 2026. Of these, 334 related to domestic operations and 18 to international services. Akasa Air accounted for the largest share of the 2026 cases with 152, followed by Air India Express with 53, IndiGo with 47 and Air India with 46. Star Air recorded 29, while SpiceJet and Fly91 reported nine each and IndiaOne Air five. The ministry also said the DGCA issued 382 show-cause notices to airlines for safety violations between January 2024 and June 2026. Separately, the regulator initiated 51 enforcement actions against scheduled airlines between 2023 and 2025 for major violations of safety standards. The measures included financial penalties, suspension of approvals or authorisations and warnings. The government has also reported 2,420 significant technical defects across domestic and international flight operations during the three-year period covered by the latest Rajya Sabha question. That figure, like the 352 cases reported for the first half of 2026, belongs to a separate dataset and should not be combined with the 889 serious defects recorded for 2025. The disclosures show a clear rise in reported technical-defect cases, particularly in 2025, but they do not establish that each case involved a different aircraft or that the defects resulted in an accident, emergency or flight cancellation. The government data available in the cited parliamentary replies also does not provide a fault-by-fault list identifying the aircraft model, registration or affected component for the 889 cases. The figures instead highlight the scale of technical-defect reporting and the DGCA’s enforcement and surveillance activity. The regulator’s stated oversight framework covers aircraft and airport operators through audits, night surveillance, ramp inspections, spot checks and special audits, while airlines are required to investigate and rectify reported defects.

India Records 889 Serious Aircraft Technical Defects in 2025, Highest In Five Years

August 18, 2026

Sifnos, Greece: A private Bell 206 helicopter operated by Bellavia Aviation Services crashed near the heliport on the Greek island of Sifnos on August 17, killing all three people on board. The helicopter was carrying Greek pilot Giorgos Raikos and British newlyweds Alexander Cromie and Marie Ebert. Local reports identified the couple as tourists travelling to Sifnos for their honeymoon. The flight had departed from Markopoulo, near Athens, and was scheduled to arrive at Sifnos at about 6:15 p.m. local time. The crash occurred shortly after 6 p.m. in the Tholos area, close to the island’s heliport and residential properties. Greece’s Fire Service said its operations centre was alerted at 6:17 p.m. Two firefighters and one vehicle were dispatched to tackle the fire, while a rescue team from nearby Syros was sent by a Fire Service RAFNAR high-speed vessel to reinforce the response. The helicopter crashed during its approach to Sifnos and burst into flames on impact. Firefighters recovered the bodies of all three occupants while extinguishing the blaze. Local reports said two victims were found in the wreckage, while the third was located a short distance away. The deputy mayor of Sifnos, Manolis Foundoulakis, said he arrived at the scene minutes after the crash and described the aircraft as almost completely destroyed. “What I saw was an amorphous mass, because almost nothing was left of the helicopter,” he told Greek media. The crash occurred close to homes, but reports said no neighbouring properties were damaged. A local resident told Greek media that the wreckage fell only about 50 metres from inhabited houses and the landing area, beside the Monastery of Panagia Vrysi. Witness accounts have raised the possibility of a technical problem, although no cause has been established. Residents reportedly heard an unusual or loud noise from the helicopter shortly before it crashed, while some reports said smoke was visible before the aircraft went down. Foundoulakis said residents described “a strange noise” and suspected a possible mechanical problem. Video footage circulating after the accident appears to show the helicopter beginning to rotate rapidly shortly before impact. The footage has focused investigators and aviation specialists on the possibility of a loss of tail-rotor effectiveness or failure. However, this remains only a line of inquiry and has not been established as the cause of the crash. Investigators are expected to examine the helicopter’s mechanical components, the video footage, witness statements and available flight data. The aircraft was identified by multiple reports as a Bell 206 operated by Bellavia Aviation Services, a Greek helicopter charter operator that advertises private helicopter transfers to Sifnos and other Greek destinations. Greek authorities have begun investigating the circumstances of the crash. The Fire Service initially secured the scene and conducted the preliminary investigation, while the National Air and Railway Accident Investigation and Safety Board (EODASAAM) is expected to investigate the aviation accident and determine its cause. Greece’s Ministry of Infrastructure and Transport expressed condolences to the families and said the investigation into the circumstances and causes had been transferred to the competent investigation body. The investigation will focus on the final moments of the flight, the aircraft’s technical condition, possible mechanical failure, the flight path and available records, weather conditions, witness accounts and the video showing the aircraft’s final movements. Authorities have not yet released a definitive cause, and mechanical failure, human factors and other possibilities remain under examination.

Three Onboard Killed As Bell 206 Helicopter Crashes On Greek Island Of Sifnos

August 18, 2026

Mogadishu, Somalia: Somali Airlines is targeting a return to scheduled passenger operations around mid-September 2026, more than 35 years after the national carrier stopped flying amid Somalia’s civil war, according to the country’s Civil Aviation Authority. Ahmed Ma’allin, director of the Somali Civil Aviation Authority, said the relaunch preparations had reached their final stage. “Somali Airlines is in its final stages, the first flight will be around mid September,” he said. The latest target would mark the airline’s first scheduled commercial operations since 1991, when its services were halted following the collapse of Somalia’s central government and the outbreak of civil war. Somali Airlines was established in 1964 and previously operated a network linking Somalia with destinations in Africa, the Middle East and Europe. The September target is the latest in a series of attempts to restore the state-owned carrier. In July 2025, the Somali government announced an agreement involving two Airbus A320 aircraft as the initial fleet for the revived airline. At the time, Transport and Civil Aviation Minister Mohamed Farah Nuuh said the aircraft were expected to enter service within two months. The minister said during the July 2025 announcement in Mogadishu that the government had acquired two A320s and planned to expand the fleet. “For now, we shall start with these two, then two or three more will follow,” he said. The government subsequently set additional timelines for the airline’s return, including a target to resume operations before the end of 2025. That deadline passed without the carrier beginning scheduled commercial services, making the September 2026 target another attempt to turn the long-running revival plan into an operating airline. The initial fleet is expected to comprise two Airbus A320 aircraft secured under the 2025 agreement. The government has indicated that the two aircraft are only the first phase of a wider fleet-building programme, with additional aircraft expected as the airline expands. However, aircraft acquisition alone does not complete the restart process. The airline must satisfy safety and regulatory requirements, obtain the necessary operating approvals and ensure that pilots, engineers, cabin crew and other personnel are appropriately qualified. Maintenance arrangements, insurance, flight planning, airport handling and other operational systems must also be in place before regular commercial services can begin. The Somali Civil Aviation Authority’s current aeronautical information system shows that Somalia has continued developing its regulatory and operational aviation framework. Its 2026 aeronautical information publication is effective from July 9, 2026, and includes current material covering Somalia’s airspace, airports and flight operations. Despite the September target, the authorities have not publicly disclosed a specific inaugural route, destination list or frequency for Somali Airlines in the August 2026 reports reviewed. The reports also do not establish a confirmed date within September beyond Ma’allin’s indication that the first flight could be around the middle of the month. The airline’s historical network, however, included destinations in East Africa, the Middle East and Europe. The revived carrier is expected to operate initially with the A320s and expand its network as additional aircraft become available. The government’s longer-term objective is to build a national airline capable of competing with established international and regional carriers serving Somalia. The revival also has significance beyond the airline itself. Somali officials have previously linked the project to improved connectivity for the Somali diaspora, employment in aviation and related industries, reduced dependence on foreign carriers and the broader rebuilding of the country’s aviation sector. The government’s 2025 announcement was made at the Prime Minister’s Office in Mogadishu, where officials confirmed the acquisition of the two A320 aircraft. The official Somali National News Agency, SONNA, described the return of the carrier as part of Somalia’s broader recovery and rebuilding efforts. Somalia has also made wider progress in rebuilding its aviation system after decades of disruption. The Somali Civil Aviation Authority’s current publications show an active regulatory framework, while the country has continued developing airport and air-navigation infrastructure.

Somali Airlines Targets Mid-September Return After 35 Years Of Shutdown

August 17, 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