News

Civil Aviation

Pilot Training

Flight School Analysis

Aviation Jobs

Training

Services

About Us

Incidents

Naha, Japan: A Japan Air Self-Defense Force (JASDF) F-15J fighter jet suffered a landing-gear malfunction while landing at Naha Airport in Okinawa on August 18, forcing the closure of the airport’s second runway for about four hours and delaying dozens of civilian flights. The pilot escaped without injury. The aircraft was identified as a Mitsubishi F-15J Eagle, registration 22-8809. The single-seat fighter was operating from JASDF Naha Air Base and was returning from a scramble mission conducted as part of Japan’s response to a possible airspace intrusion. The incident occurred at around 12:55 p.m. local time as the F-15J landed on Runway 36L, also known as Naha Airport’s B Runway. According to Japan Air Self-Defense Force (JASDF) officials, the aircraft developed a problem involving its landing gear during the landing sequence. The jet subsequently became tilted and stopped on the runway. The precise mechanical cause remains under investigation. Images and video from the scene showed the aircraft resting at an angle, with its left side lowered toward the runway. The occurrence was a possible failure of the left main landing gear. Other reports said the fighter slid along the runway after the gear collapsed, with the aircraft rotating roughly 180 degrees before coming to rest facing in the opposite direction. A JASDF spokesman told Stars and Stripes that the landing gear apparently failed as the aircraft touched down shortly before 1 p.m. and that the fighter’s left wing contacted the runway before it came to a stop. The spokesman said the pilot was not injured and that the extent of damage to the aircraft was still being assessed. The aircraft was eventually removed from the runway using recovery equipment, including a crane. Naha Airport officials said the runway remained closed for approximately four hours while the fighter was removed, the area was cleaned and safety inspections were completed. Runway operations subsequently resumed. The closure had a significant effect on civilian operations because Naha Airport is a dual-use facility, serving both commercial aviation and the JASDF. With the B Runway unavailable, civilian aircraft were required to use the other runway. Airport officials said 40 commercial flights were delayed, with some delays exceeding 30 minutes. The incident also drew a response from Okinawa Governor Denny Tamaki, who described the situation as deeply regrettable and called for the cause of the incident to be investigated. The governor’s office has sought information on the circumstances surrounding the fighter’s landing and measures to prevent a recurrence. The F-15J’s condition and the precise reason for the landing-gear failure remain subject to investigation. At this stage, available official data does not establish whether the malfunction resulted from a particular component failure, maintenance issue or other technical factor.

JASDF F-15J Suffers Landing Gear Failure At Naha Airport, Delaying Dozens Of Flights

Aviation Today News Desk August 20, 2026

Naha, Japan: A Japan Air Self-Defense Force (JASDF) F-15J fighter jet suffered a landing-gear malfunction while landing at Naha Airport in

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

Aviation Today News Desk August 20, 2026

Narita, Japan: A Malaysia Airlines Airbus A330 operating Flight MH89 from Tokyo Narita Airport to Kuala Lumpur aborted takeoff on August

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

Aviation Today News Desk 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

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

Aviation Today News Desk August 18, 2026

Milan, Italy: A baggage cart carrying checked luggage caught fire at Milan Malpensa Airport in Italy on Sunday, August 16, shortly

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

Aviation Today News Desk August 18, 2026

Krasnoyarsk, Russia: Hainan Airlines Flight HU753, operating from Beijing Capital International Airport in China to Manchester Airport in the United Kingdom,

Phoenix, United States: A potential mid-air collision was averted near Phoenix Sky Harbor International Airport on August 14, 2026, after two American Airlines Boeing 737-800s were simultaneously operating under the same “American 2482” callsign while flying in opposite directions between Phoenix and Chicago. One aircraft was arriving at Phoenix from Chicago O’Hare International Airport, while another had just departed Phoenix for Chicago. The unusual overlap occurred after the inbound Flight 2482 was delayed by weather, prompting American Airlines to use another aircraft already at Phoenix so passengers waiting for the outbound service could depart on schedule. Because Flight 2482 normally operates as a Chicago-Phoenix round trip using the same flight number, the replacement aircraft also operated under the 2482 identification. The resulting callsign duplication placed both aircraft in the same area of airspace while communicating on the same frequency. Flightradar24 reported that the arriving aircraft was descending through about 11,000 feet while the departing aircraft was climbing toward 9,000 feet when the duplication was recognized. The FAA said the aircraft maintained the required separation throughout the incident. The Phoenix air traffic controller quickly recognized the problem and began distinguishing the two aircraft as “American 2482 on the arrival” and “American 2482 on the departure.” The controller then kept the arriving aircraft above the departing aircraft and prevented the departure from climbing into the arrival’s altitude, maintaining vertical separation as their flight paths converged. The controller also alerted both crews to the other aircraft. Reports said the pilots were able to see each other while they were still miles apart, providing an additional layer of awareness as the two aircraft crossed paths. No source has publicly released an exact minimum horizontal distance between the aircraft, and the FAA has confirmed only that required separation was maintained. The incident was captured in air traffic control audio published by ATC.com and subsequently highlighted by media outlets. After the departing aircraft had cleared the area, the controller said, “I’ve been working air traffic for 25 years. I’ve never seen two aircraft pretty much merge with the same call sign. That’s pretty incredible.” The arriving pilot later complimented the controller, saying “nice work.” The controller responded, “It could have been disastrous, but I’m glad it worked out.” The precise passenger and crew numbers aboard the two Boeing 737-800s have not been publicly disclosed by the FAA or American Airlines. Both aircraft completed their flights safely, with no injuries or collision reported. American Airlines said, “The diligence and professionalism of air traffic controllers and our pilots ensured required separation was always maintained and the issue was identified and addressed. Both flights continued safely and without incident.” Aviation safety expert Steve Arroyo, a former airline dispatcher and pilot, said the incident likely resulted from an oversight within the airline’s dispatch operation. He told Associated Press that someone should have identified that the two aircraft would be airborne at the same time under identical flight numbers. Arroyo described the event as an example of the aviation system’s ability to recover from an error once it reaches another safety layer. The FAA and American Airlines are investigating how the duplicate callsign was allowed to occur. The investigation will determine how the delayed inbound flight and the replacement outbound aircraft were planned and identified, and why the normal safeguards for avoiding simultaneous use of the same callsign did not prevent the situation.

Two American Airlines Jets Sharing Same Callsign Avoid Near-Midair Collision In Phoenix

Aviation Today News Desk August 17, 2026

Phoenix, United States: A potential mid-air collision was averted near Phoenix Sky Harbor International Airport on August 14, 2026, after two

Vietnam Airlines Boeing 787 Suffers Tailstrike After Extended Takeoff Run At Munich

Aviation Today News Desk August 17, 2026

Munich, Germany: A Vietnam Airlines Boeing 787-9 bound for Hanoi took an unusually long takeoff run from Munich Airport on August

Chennai, India: An IndiGo Airbus A321neo operating flight 6E-723 from Kolkata to Chennai made a precautionary emergency landing at Chennai International Airport late Tuesday night, August 11, after its left engine became inoperative shortly before landing. The aircraft was carrying 224 passengers and crew members. A full emergency was declared at Chennai Airport at 11:29 p.m. IST, with emergency response teams placed on standby. The aircraft subsequently landed safely on Runway 25 at 11:37 p.m., with all 224 people on board safe and no injuries reported. The flight was scheduled to arrive at 11:30 p.m., making the actual landing seven minutes later than scheduled. According to officials from the Airports Authority of India (AAI), the aircraft reported the technical problem while approaching Chennai. The pilot noticed that the left engine had failed while preparing for landing and alerted air traffic control. Following the alert, airport authorities activated the emergency response arrangements to facilitate the aircraft's safe arrival. The emergency was formally withdrawn at 11:47 p.m., around 10 minutes after the aircraft touched down. Chennai airport authorities said normal operations continued following the incident, with no disruption to airport operations reported. The declaration of a full emergency was a precautionary measure that allowed airport fire, rescue and other emergency services to remain ready for the aircraft's arrival. The aircraft landed without an accident, and there was no reported evacuation, casualty or injury among the 224 people on board. At present, the specific technical cause of the left-engine failure has not been publicly established. The available reports describe the condition as a left-engine failure or a “left engine inoperative condition” and do not provide details about the nature of the malfunction, engine damage or whether a particular component failed. Further technical examination of the aircraft is expected to establish the cause.

IndiGo Airbus A321neo Makes Emergency Landing In Chennai After Left-Engine Failure

Aviation Today News Desk August 12, 2026

Chennai, India: An IndiGo Airbus A321neo operating flight 6E-723 from Kolkata to Chennai made a precautionary emergency landing at Chennai International

Myrtle Beach, United States: American Airlines Flight 1760, a Boeing 737-800 operating from Myrtle Beach International Airport in South Carolina to Charlotte Douglas International Airport in North Carolina, made an emergency return to Myrtle Beach on Monday, August 10, after reportedly striking a flock of birds shortly after takeoff and experiencing an engine malfunction. The aircraft took off from Myrtle Beach at about 8:11 a.m. local time and was only minutes into the flight when the crew reported the problem to air traffic control. According to air traffic recordings obtained through LiveATC.net, the pilot declared a Mayday, saying, “Mayday, mayday, mayday. We’ve got an engine problem here.” The crew subsequently reported an engine malfunction as the aircraft turned back toward Myrtle Beach. Reports indicate the aircraft had struck birds during its climb, with another pilot who witnessed the event telling air traffic control, “I saw he took up birds, it looked like, at least in the left side engine.” The reported bird ingestion involved the aircraft’s left engine, beneath the left wing. Passengers recorded video showing bright orange flames and sparks appearing from the left side of the aircraft beneath the wing. Passenger Patrick Gotwalt captured footage of the event, while witnesses on the ground also reported hearing several loud popping sounds and seeing orange flashes from the aircraft’s left side. Lindsey Mackey, who was on the ground near the beach, told CNN that she heard loud popping noises before noticing orange flashes coming from the aircraft’s left wing. The visual evidence showed what appeared to be flames or sparks coming from the area around the left engine as the aircraft continued flying back toward the airport. As the Boeing 737-800 returned, airport emergency personnel prepared for its arrival. Workers subsequently found substantial bird remains and debris on the runway. Radio communications from the airport included the statement, “We’ve got a lot of bird debris out here. We’re going to grab as many big pieces as we can.” The debris provided physical evidence consistent with reports that the aircraft had struck birds. Flight 1760 landed safely back at Myrtle Beach at approximately 8:40 a.m., after spending roughly 15 minutes in the air, according to reports. The aircraft taxied to the gate under its own power, allowing passengers to disembark normally. No injuries were reported. The flight was carrying 172 passengers/customers and nine crew members, according to the New York Post, although the airline's statement cited by The U.S. Sun referred specifically to the 172 customers aboard. American Airlines said the aircraft was removed from service for a maintenance inspection following the incident. In a statement, the airline said, “The aircraft landed safely and has been taken out of service to be inspected by our maintenance team.” The airline added, “Our team worked to get customers on their way to Charlotte (CLT) on a replacement aircraft.” American also thanked its employees for their professionalism and passengers for their understanding. The aircraft was therefore not continued to Charlotte after the emergency landing. American arranged a replacement aircraft so the affected passengers could continue their journey to Charlotte. Although video footage showed flames coming from the left engine area, the New York Post reported that there was no internal engine fire, indicating that the visible flames did not necessarily represent a sustained fire inside the engine. The aircraft was nevertheless removed from service for inspection. The Federal Aviation Administration confirmed that the aircraft landed at Myrtle Beach at about 8:40 a.m. and said it would investigate the incident. The investigation is expected to establish the precise nature of the engine malfunction and assess the bird-strike evidence. The bird remains recovered after the incident are also significant because wildlife remains from aircraft strikes can be examined to determine the species involved. The FAA's Smithsonian Feather Identification Lab program routinely analyzes bird remains from aircraft strikes to help identify the species and improve airport wildlife-management measures.

American Airlines Flight 1760 Makes Emergency Landing After Bird Strike Damages Engine

Aviation Today News Desk August 12, 2026

Myrtle Beach, United States: American Airlines Flight 1760, a Boeing 737-800 operating from Myrtle Beach International Airport in South Carolina to

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

Aviation Today News Desk August 11, 2026

Dublin, Ireland: A SWISS Airbus A330-300 operating flight LX52 from Zurich to Boston was diverted to Dublin after smoke was reported

Incidents

JASDF F-15J Suffers Landing Gear Failure At Naha Airport, Delaying Dozens Of Flights

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

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

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

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

Two American Airlines Jets Sharing Same Callsign Avoid Near-Midair Collision In Phoenix

Vietnam Airlines Boeing 787 Suffers Tailstrike After Extended Takeoff Run At Munich

IndiGo Airbus A321neo Makes Emergency Landing In Chennai After Left-Engine Failure

American Airlines Flight 1760 Makes Emergency Landing After Bird Strike Damages Engine

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

Quick Links

Navigate

General Support

News Desk Support