News

Civil Aviation

Pilot Training

Flight School Analysis

Aviation Jobs

Training

Services

About Us

Incidents

Los Angeles, United States: A DHL Boeing 737-800 freighter suffered a brake-system malfunction during landing at Los Angeles International Airport (LAX) on August 26, 2026, causing four tires to blow and a fire to erupt around its main landing gear. The two crew members aboard the aircraft were not injured. The aircraft, a Boeing 737-800BDSF registered as N326FL, was operated by Kalitta Charters II on behalf of DHL as Flight K5-1814 from Phoenix Sky Harbor International Airport to Los Angeles. The freighter landed on Runway 25L at approximately 11:10 p.m. local time. Video footage shows the aircraft touching down before white smoke began emerging from the main landing-gear area. Within seconds, several loud pops and flashes were visible, followed by flames and sparks beneath the aircraft as it continued its landing roll. The aircraft subsequently slowed and stopped on the runway while fire crews moved toward it. Footage showed flames concentrated around the landing-gear and tire area as emergency responders began extinguishing the fire. During the incident, the flight crew communicated with air traffic control about the braking problem. In the recorded radio exchange, one of the pilots said, “I don’t know if we blew a tire, but it feels like the brakes locked up.” The crew also advised the tower that the anti-skid system was inoperative and that the brakes may have locked up, with the crew concerned that some of the tires could have been damaged. The Federal Aviation Administration said preliminary information indicated that the aircraft’s brakes malfunctioned during landing and that four tires were blown. The agency has launched an investigation into the incident, meaning the precise mechanical cause has not yet been established. The Los Angeles Fire Department responded after receiving a report of an aircraft fire at approximately 11:06 p.m. The department deployed 13 units to the scene. Firefighters initially received information indicating an engine fire, but after reaching the aircraft, they determined that the problem involved the landing gear and brakes. The LAFD said the left main landing gear caught fire and that the flames spread to the tires on that side. Firefighters used water to extinguish the fire, and the aircraft's two occupants were able to leave the aircraft without assistance. No injuries were reported. The final LAFD unit left the scene at approximately 12:44 a.m. “The cause of the mechanical failure remains under investigation by the appropriate federal and company authorities,” the Los Angeles Fire Department said. DHL described the event as an “apparent brake system issue” that resulted in a brake overheat. The company confirmed that everyone aboard was safe and said the aircraft operator was working to move the disabled freighter so that it could undergo further inspection and assessment. “There were no injuries, and all crew members are safe,” DHL said. The incident temporarily closed Runway 25L as emergency personnel and maintenance crews dealt with the disabled aircraft. Air traffic control also kept other aircraft clear of the runway while the emergency response was underway. The aircraft remained on the ground at LAX into the following morning while arrangements were made to move it from the runway and assess the damage. N326FL is a Boeing 737-800 that was manufactured in 2001 and later converted from passenger service to the BDSF freighter configuration. The conversion was completed in December 2022. The aircraft was operating in DHL livery under Kalitta Charters II, a U.S. cargo carrier. The available evidence establishes the sequence of events as a normal landing followed by a suspected brake lockup or malfunction, tire failures, a fire involving the main landing gear, the aircraft coming to a stop on Runway 25L, and the subsequent response by LAX emergency crews. However, investigators have not yet identified the specific component or technical failure responsible for the brake malfunction.

DHL Boeing 737 Freighter Suffers Brake Lockup, Tire Bursts And Fire During LAX Landing

Aviation Today News Desk August 28, 2026

Los Angeles, United States: A DHL Boeing 737-800 freighter suffered a brake-system malfunction during landing at Los Angeles International Airport (LAX)

Honolulu, United States: Honolulu police are investigating the death of 50-year-old Southwest Airlines flight attendant Jenny Lupton, who was found dead at the Hilton Hawaiian Village in Waikīkī, Honolulu, on August 20, 2026, while on a work layover. Authorities have not determined how she died, and the Honolulu Police Department has urged the public to rely on verified information while the investigation continues. According to the Honolulu Police Department, an unattended death investigation was opened in Waikīkī on August 20 involving Lupton. The department's Homicide Detail is handling the case and is working with her family. Police said detectives are conducting interviews, reviewing and recovering surveillance video and examining evidence. HPD said, "At this time, no conclusions have been made regarding the manner of death." The department also said, "This is a thorough investigation that will take time." Police added that certain information will be withheld to protect the integrity of the investigation and that the public would be notified if detectives identify an immediate threat to public safety. Lupton, who was from Moore, Oklahoma, had worked for Southwest Airlines for 29 years, according to her family. She was also a mother to a 15-year-old son. Family members described her as outgoing, funny and deeply connected to those around her. Her niece Hannah Lupton followed her into the aviation industry and said Jenny had influenced her decision to become a flight attendant. Lupton was in Hawaii for work and had reportedly planned to remain on the islands for several days before returning home. Her family said she was familiar with Hawaii and had visited the islands multiple times. The circumstances surrounding her death became the focus of attention after her body was discovered near a dumpster at the Hilton Hawaiian Village. The U.S. Sun reported that a hotel employee found her at about 6 a.m. on August 20. Lupton's family was later contacted by the Honolulu Department of the Medical Examiner and told that she appeared to have fallen from the balcony of her 24th-floor hotel room. That reported fall has not been established by HPD as the official manner of death. The police department has specifically said that no conclusion. Lupton's family has raised questions about the circumstances and said they do not believe she intentionally harmed herself. Her sister, Tresa Lupton, told the media that Jenny had been communicating with the family shortly before her death and appeared to be enjoying her time in Hawaii. "She just went out with one of her flight attendant friends, and they danced and had a good time". The family has questioned the timeline surrounding Lupton's death and said it wants investigators to establish exactly what happened between her last known activities and the discovery of her body. "The timeline doesn't make sense, and we are afraid that maybe there was foul play," Tresa said. The family has also reportedly been told that numerous surveillance cameras cover the area around the hotel. Reports citing hotel security said police were reviewing footage from more than 70 cameras. However, authorities have not publicly said whether anyone witnessed Lupton's fall or released surveillance findings. Tresa said the family was initially left with questions about what had happened and was seeking more information from authorities. She described her reaction to learning of her sister's death as one of disbelief. "I was in disbelief and trying to not believe what I was experiencing," Tresa said. "But I still can't believe it. It doesn't seem real." Lupton's family has also remembered her for her personality and close relationships. Her niece Hannah said Jenny was a major influence on her own aviation career, while other relatives described her as someone who made friends easily and brought energy to social gatherings. "She was truly the best aunt anyone could have asked for," Hannah said. "She was the light of every party, the person who could make a room brighter simply by being in it." Another niece, Sarah Lupton, described Jenny as "the funniest person I know" and said she had "a really big heart." Southwest Airlines confirmed that Lupton died during a layover in Hawaii and said it was supporting her family and coworkers while cooperating with authorities. "The Southwest Airlines family is deeply saddened by the passing of our colleague," the airline said. "We have offered our condolences and support to the Employee’s family and co-workers and are engaged with local authorities as they investigate." For now, investigators have not publicly classified Lupton's death as an accident, suicide or homicide. HPD said its detectives are continuing interviews, reviewing surveillance footage and examining evidence. The department has also asked the public to avoid spreading unconfirmed information while the investigation remains active. The case therefore remains open, with the official cause and manner of death still pending.

Southwest Airlines Flight Attendant Found Dead During Hawaii Layover, Probe Underway

Aviation Today News Desk August 25, 2026

Honolulu, United States: Honolulu police are investigating the death of 50-year-old Southwest Airlines flight attendant Jenny Lupton, who was found dead

Dallas, United States: A passenger's laptop caught fire aboard American Airlines Flight 2398 while the Airbus A321 was approaching Dallas-Fort Worth International Airport (DFW) from Atlanta on August 21, prompting a cabin emergency and an immediate response from the flight crew. Flight 2398 was operating from Hartsfield-Jackson Atlanta International Airport to Dallas-Fort Worth International Airport with 133 people on board when smoke and fire were reported from a passenger's electronic device during the landing phase. The aircraft was an Airbus A321. According to air traffic control audio, the pilot initially reported a fire in the rear section of the aircraft while flight attendants were attempting to extinguish it. The pilot told controllers, "Cabin fire in the back of the airplane," as the crew worked to bring the situation under control. Passenger Jessica Irgens told CBS News that the incident began roughly 30 minutes before landing when another passenger's laptop started smoking and then caught fire. She said she was sitting about two rows from the device and moved toward the rear of the aircraft after smoke began filling the cabin. According to Irgens, the laptop's owner placed the burning device in the aisle while passengers attempted to assist. She said the crew managed to secure the device in a thermal containment bag within about five minutes. The pilot subsequently told air traffic control, "I think we have about four to five passengers that were burned by the laptop," adding that "The laptop contained about mid-aircraft." These figures came from the pilot's initial report and should not be treated as the final confirmed injury count. American Airlines confirmed that the aircraft landed safely at DFW and said the incident involved smoke from a customer's device during landing. The airline said, "American Airlines flight 2398 landed safely at DFW after reports of smoke from a customer's device during landing." It added, "We thank our crew for their professionalism and swift response to quickly contain the device." The airline also said the aircraft taxied to the gate under its own power and that emergency personnel met the aircraft upon arrival in accordance with standard procedure. One passenger received medical attention at the scene and was subsequently released, according to American Airlines. DFW separately confirmed that emergency crews responded and one patient was treated and released. The Federal Aviation Administration said flight attendants contained the fire using a thermal containment bag. The Airbus A321 landed at DFW at approximately 6:55 p.m. local time, and the FAA said it was investigating the incident. The exact technical failure that caused the laptop to ignite has not been publicly established. The available official information identifies the source as a customer's device, while the FAA has separately warned that lithium-ion batteries can undergo a process known as thermal runaway. Such an event can occur when a battery is damaged, overheated, exposed to water, overcharged or improperly packed. The incident therefore did not result in an emergency diversion or emergency landing at an alternate airport. Flight 2398 continued to Dallas-Fort Worth after the cabin crew contained the device and landed safely at its scheduled destination. The aircraft then reached the gate under its own power, where emergency personnel responded.

American Airlines Flight Lands Safely After Passenger Laptop Catches Fire

Aviation Today News Desk August 24, 2026

Dallas, United States: A passenger’s laptop caught fire aboard American Airlines Flight 2398 while the Airbus A321 was approaching Dallas-Fort Worth

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

Incidents

DHL Boeing 737 Freighter Suffers Brake Lockup, Tire Bursts And Fire During LAX Landing

Southwest Airlines Flight Attendant Found Dead During Hawaii Layover, Probe Underway

American Airlines Flight Lands Safely After Passenger Laptop Catches Fire

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

Quick Links

Navigate

General Support

News Desk Support