Facebook Instagram Linkedin X-twitter Youtube

About Us
Contact Us
Advertisement

About Us
Contact Us
Advertisement

Aviation Newsletter

WhatsApp Channel

Latest News
Aviation Today Perspectives
Aviation Jobs
About Us

Latest News
Aviation Today Perspectives
Aviation Jobs
About Us

Subscribe Now

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

Subscribe Now

Aviation Today News Desk

Malaysia Airlines MH89 Aborts Takeoff At Narita Over Engine Issue, No Injuries Reported

August 20, 2026

Carlisle, United States: A Cessna 150 collided with a Pennsylvania State Police Bell 407 helicopter at Carlisle Regional Airport in Cumberland County, Pennsylvania, on Wednesday evening, August 19, killing the Cessna pilot and injuring two state police troopers aboard the helicopter. The collision occurred near a runway at the airport, about 110 miles northwest of Philadelphia. The FAA identified the aircraft involved as a Cessna 150 and a Bell 407. The Cessna pilot, believed to have been the aircraft's only occupant, died in the crash. Authorities had not released the pilot's identity pending notification of next of kin. The Bell 407 was operated by the Pennsylvania State Police and was carrying two members of the department's aviation unit, Cpl. Bryce Corman and Tpr. Jason Mills. The helicopter was conducting a routine training exercise at Carlisle after operating from its Harrisburg base. According to Acting Pennsylvania State Police Commissioner Lt. Col. George Bivens, the helicopter was positioned several feet above a grassy area next to a runway when the Cessna approached from behind. The aircraft came down along the runway before veering sharply to the right at the last moment and striking the helicopter from the rear. “As that Cessna came down along that runway for an unknown reason, it veered hard to the right. At the last moment, it struck the helicopter from the rear,” Bivens said. The Cessna struck the helicopter's rear section, involving the tail rotor and then the main rotor, sending both aircraft into a violent crash. The Cessna broke into multiple pieces, while the Bell 407 lost its rotor blades and tail boom before rolling over and coming to rest on its side, partially on its roof. The two troopers were initially trapped inside the helicopter. Corman was able to push out a window and help Mills escape through the opening. Mills was believed to have suffered more serious injuries and significant bleeding, according to Bivens. Both troopers were taken to Penn State Health Milton S. Hershey Medical Center. Dr. Ashley Ludwig, the hospital's trauma medical director, said they arrived as Level 1 trauma patients but had only minor injuries and were in stable condition. One was expected to be discharged Wednesday night, while the other was admitted for further observation. Pennsylvania State Police Commissioner Col. Christopher Paris said the helicopter crew was conducting routine training when the collision occurred. He said the helicopter pilots would not have been able to see the Cessna approaching from behind. “The pilots would not have been able to even see that airplane approaching them,” Paris said. Governor Josh Shapiro visited the medical center and praised the emergency response and medical teams involved in treating the injured troopers. “Tonight could have been much worse,” Shapiro said, adding that the response was “an example of Pennsylvania at its finest.” Emergency personnel responded to the airport following the crash, and the coroner was called to the scene. Local residents Patrick Brown and Lloyd Slusser also reportedly crossed a fence and ran toward the wreckage to assist after witnessing the crash. The Cessna was reportedly from the local area, but authorities have not disclosed its departure point, destination or the purpose of its flight. The aircraft's pilot was believed to be its sole occupant. The exact cause of the collision remains undetermined. Officials said the Cessna's sudden right turn was made for an unknown reason, and investigators will examine why the aircraft veered from its approach path, the helicopter's position, airport operations and communications. Carlisle Regional Airport does not have an air traffic control tower. Pilots operating there use a common traffic radio frequency, and investigators are expected to examine those communications as part of the inquiry. State police also secured photographs and video that could assist investigators in reconstructing the collision. The FAA and National Transportation Safety Board are leading the investigation, with Pennsylvania State Police assisting. The NTSB said the wreckage would be documented and moved to a secure facility for further examination. Although the FAA and NTSB described the incident as a midair collision, Pennsylvania State Police later said the helicopter was on the ground at the time of the impact. Officials have not yet established whether the Cessna was airborne at the exact moment of contact. The distinction, along with the reason for the Cessna's sudden deviation, remains part of the investigation. No final cause has been determined, and authorities have not attributed the crash to pilot error, mechanical failure, communications issues or any other specific factor.

Pilot Killed After Cessna 150 Collides With Pennsylvania State Police Helicopter

August 20, 2026

Seven Killed In Helicopter Crash In Kenya’s Samburu County During Safari Charter Flight

August 20, 2026

Kenya Airways Fuel Costs Surge 72% As Middle East Conflict Drives Up Operating Pressure

August 19, 2026

Munich, Germany: A Lufthansa Airbus A380-800 operating flight LH459 from San Francisco International Airport to Munich Airport touched down prematurely near the eastern threshold of Munich’s southern runway on Monday evening, August 17, 2026, damaging runway-threshold lighting. The aircraft, registered D-AIML, was carrying 351 passengers after completing the approximately 11-hour transatlantic flight from San Francisco, United States, to Munich, Germany. All passengers and crew were able to leave the aircraft normally, with no injuries reported. Flight records identify D-AIML as an Airbus A380-841 operated by Lufthansa, while Lufthansa’s published schedule confirms LH459 operates between San Francisco and Munich. According to Lufthansa, the aircraft touched down on the concrete surface before the white-marked runway threshold. During the premature touchdown, the aircraft struck lighting installed around the runway threshold, causing damage to the runway’s visual guidance system. Lufthansa spokesperson Jörg Waber said in a statement, “We can confirm that an AirVIbus A380-800 damaged runway lighting in the area of the runway threshold.” He added that the aircraft had arrived from San Francisco with 351 passengers, subsequently taxied to its assigned position and that all passengers left the aircraft normally. The incident occurred on Munich Airport’s southern runway, identified as Runway 26L when used for approaches from the east. The Deutsche Flugsicherung describes Runway 26L as Munich’s southern runway and says aircraft approaching it from the east use its instrument landing system. Munich Airport characterized the infrastructure damage as minor. According to the airport, a “minor damage” to lighting was identified around the eastern threshold of the southern runway. The damaged lighting was repaired promptly, allowing the runway to return to service less than an hour after the A380 landed. The exact circumstances that caused the A380 to touch down before the designated threshold remain unclear. No official finding has attributed the event to pilot error, weather, aircraft malfunction, runway conditions or any problem with the airport’s approach system. The aircraft touched down short of the marked threshold and that its landing gear struck approach lights. The cause remains under investigation. Germany’s Federal Bureau of Aircraft Accident Investigation, or BFU, has opened an investigation into the occurrence. The A380 involved was approximately 13 years old and carried the registration D-AIML. Flight-history records identify the aircraft as an Airbus A380-841 operated by Lufthansa. The airline’s A380 configuration can accommodate up to 509 passengers, although 351 passengers were onboard LH459 during this particular flight. Separately, on August 15, 2026, a Vietnam Airlines Boeing 787-9 bound for Hanoi experienced an unusually long takeoff run at Munich Airport. The aircraft continued accelerating almost to the end of Runway 26L and reportedly travelled about 120 metres beyond the paved surface before becoming airborne. During the extremely late rotation, its rear underside struck the ground, causing a tailstrike and damage to the aft fuselage. After takeoff, warnings for tail contact and low tyre pressure prompted the crew to remain near Munich at around 9,000 feet for about two hours before returning. The aircraft sustained further landing-gear and tyre damage, with several tyres damaged or deflated, and was unable to taxi after landing. It was carrying 271 passengers and 16 crew, all of whom were reported safe. German authorities are leading the investigation, with Vietnamese investigators assisting, while the cause of the unusually prolonged takeoff remains under investigation.

Lufthansa A380 Lands Short At Munich Airport, Damages Runway Lights During Its Landing

August 19, 2026

US Court Delays Google’s $10M Spirit Airlines Data Deal After Flight Attendants Object

August 19, 2026

New Delhi, India: The Supreme Court of India has pushed the Central Government of India to finalise new aviation rules within three weeks amid concerns over unpredictable airfares, surge pricing, baggage charges and passenger refunds, while warning that airlines failing to comply with applicable government directions could be grounded. The development followed a hearing before a bench of Justices Vikram Nath and Sandeep Mehta on August 17, 2026. The Central Government informed the court that it had fast-tracked the process of framing rules under the Bharatiya Vayuyan Adhiniyam, 2024, and expected the framework to be finalised within three weeks. The government also placed the draft rules before the bench in a sealed cover, saying that some final discussions were still underway. During the hearing, the Supreme Court of India issued a stern warning over airline compliance. “If airlines are not complying, ground them,” the bench said, according to reports of the proceedings. The observation came after the court was told that airlines were allegedly not complying with directions issued by the government of India concerning fares. The remark does not amount to an immediate order grounding any particular airline; rather, it signals that the court expects the existing regulatory directions to be enforced against carriers that fail to comply. The proposed regulatory framework is being prepared under the Bharatiya Vayuyan Adhiniyam, 2024, which replaced the Aircraft Act, 1934 as the principal legislation governing India's civil aviation sector. The new law came into force in January 2025, while the corresponding rules are being framed to operationalise its provisions. According to the latest reports, the draft rules submitted to the Supreme Court of India address several areas directly affecting passengers. These include airline ticket pricing, surge fares, excess baggage charges and passenger refunds. The broader proceedings also involve concerns over cancellation and refund norms, ancillary charges and the need for stronger protection against arbitrary increases in the cost of air travel. The proposed framework is particularly significant because India's airline market currently operates largely on dynamic pricing, under which fares change according to demand, availability and other commercial factors. The latest government proposal is expected to establish clearer rules governing when and how intervention can take place when fares rise sharply. However, the precise mechanism for controlling surge pricing has not yet been publicly finalized, and reports do not establish that the government has approved a permanent fixed airfare cap. The Supreme Court of India also examined whether the proposed framework would provide an effective regulatory mechanism. After examining the draft placed before it, the bench reportedly questioned whether an effective regulator had been provided for. This issue is significant because the proceedings are not limited to ticket prices; they also concern how passenger-protection requirements will be monitored and enforced once the new rules come into force. For airlines, the immediate position remains that existing government directions continue to apply while the new rules are being finalised. The Central Government of India told the court that the Ministry of Civil Aviation has been issuing office memorandums to airlines concerning pricing during the interim period. The petitioners, however, argued that airlines were not following those directions, prompting the Supreme Court's warning that non-compliant carriers should face action, including grounding. The case originates from a petition filed by social activist S. Laxminarayanan seeking tighter regulation of airfares and greater protection for passengers. The plea has raised concerns about steep and unpredictable increases in ticket prices, surge pricing, baggage charges, cancellation and refund practices and other ancillary fees. It has also sought stronger regulatory oversight of the aviation sector. The Supreme Court of India has been examining the issue for several months. In earlier proceedings, the court expressed concern over sharp increases in airfares during periods of high demand and sought a mechanism to provide greater predictability and protection to passengers. On May 15, the court observed that there should be some “rationalisation” of airfares and sought measures to provide relief to air passengers. The latest August hearing follows the court's July direction requiring the Central Government to place the proposed aviation rules before it. The government had said the rules had been framed and were undergoing the statutory process. The court nevertheless required the proposed framework to be produced before it in a sealed cover, even if the rules had not yet completed the parliamentary process. The Central Government of India has now secured three more weeks to complete the rule-making process. The matter has been listed for further hearing on September 7, 2026, when the Supreme Court of India is expected to consider the status of the final rules and the regulatory mechanism proposed for enforcing them. For passengers, the eventual rules could bring greater clarity to how airlines price tickets during periods of unusually high demand, how additional baggage charges are applied and how cancellations and refunds are handled. For airlines, the framework could introduce clearer compliance obligations and potentially stronger enforcement where government directions are breached. The exact obligations, however, will become clear only after the Central Government completes the rule-making process and formally notifies the final rules. The latest development therefore marks a significant step towards a formal regulatory framework for airfare and passenger-related charges, but it does not yet mean that a new airfare cap or a final surge-pricing formula is in force. The Central Government is still completing the rules, and the Supreme Court of India is due to review the matter again on September 7.

India’s Supreme Court Pushes Government To Finalise New Aviation Rules Within 3 Weeks

August 19, 2026

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

« Previous Page1 … Page7 Page8 Page9 Page10 Page11 … Page144 Next »

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

Facebook-f Instagram Linkedin-in X-twitter Youtube

Terms of Use
Privacy Policy
Disclaimer

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

Aviation Newsletter

Facebook Instagram Linkedin X-twitter Youtube