Flight Safety Information - November 12, 2026 No. 223 In This Issue : Five Federal Agencies Agree to Coordinate Counter-Drone Technology, Aviation Safety : Accident: American B789 near Tokyo on Nov 15th 2024, turbulence injures two cabin crew : American 787 Reportedly Ignores ATC Instruction, Nearly Collides with Lufthansa 747 : Incident: Norwegian B38M at Umea on Oct 1st 2026, takeoff from wrong intersection : United 737 Jet Blast Suspected After Cessna Flips Upside Down at John Wayne Airport : Velocity 173 Elite FG, N776TB, crashed into trees while on approach : Lufthansa A380 Pilots Furious with ATC After 17 Minute Takeoff Delay at San Francisco Airport : The float equipped Twin Otter's left float partially detached. : Airline data breaches expose Asia’s aviation cyber risks : Calendar of Events Five Federal Agencies Agree to Coordinate Counter-Drone Technology, Aviation Safety The agreement establishes a framework for testing and deploying counter-drone systems while limiting risks to civilian aircraft, communications, and navigation equipment. Five federal departments have signed a new agreement to coordinate the testing and deployment of counter-drone technologies, establishing a process aimed at addressing unauthorized drone threats without disrupting civilian aviation operations. The departments of Transportation, Defense, Homeland Security, Energy, and Justice announced the memorandum of understanding (MOU) on Nov. 9. The agreement calls for greater coordination with the Federal Aviation Administration (FAA) and Federal Communications Commission (FCC) as agencies develop and evaluate systems designed to detect, track, stop, or take control of unauthorized drones. “This agreement builds on the work already underway with our federal partners and establishes a consistent process to ensure counter-drone technologies can be used without compromising aviation safety,” FAA Administrator Bryan Bedford said in a press release. The agreement, led by the White House Task Force to Restore American Airspace Sovereignty, comes as federal agencies work to address drone threats along the southern U.S. border, at military installations, and around critical infrastructure. Counter-drone technologies can pose risks to civilian aviation, particularly when systems designed to disrupt or disable drones interfere with aircraft communications or navigation equipment. Under the new agreement, participating agencies will coordinate technical requirements, field testing, and data sharing to determine whether counter-drone systems can operate without creating additional risks to aircraft or other airspace users. The agencies will also consider Transportation Department, FAA, and FCC requirements and testing data when researching, developing, testing, and evaluating new counter-drone capabilities. The FAA will play a central role in evaluating proposed technologies and determining whether adequate safety protocols and airspace coordination measures are in place. The agency will conduct safety risk assessments, provide technical data identifying unsafe conditions, and recommend steps to reduce potential risks. If additional safeguards are necessary, the FAA may implement protective measures, including temporary airspace restrictions. The Transportation Department may also provide guidance on how counter-drone technologies fit into the broader civilian transportation system. The agreement builds on existing federal efforts to expand counter-drone capabilities while addressing aviation safety concerns. Those efforts include a temporary flight restriction along the southern U.S. border and a completed FAA safety assessment of the Department of Defense’s (DOD) high-energy laser counter-drone system. Defense Secretary Pete Hegseth pointed to that work as an example of how emerging counter-drone technologies can be deployed alongside civilian aviation operations. “We have demonstrated on the Southern Border that next-generation counter-drone defenses, including high-energy lasers, can be deployed rapidly and safely alongside civilian aviation,” Hegseth said. The Trump administration has rebranded the DOD as the Department of War. Federal officials also emphasized the need to protect critical infrastructure and other sensitive locations from unauthorized drone activity. Energy Secretary Chris Wright said the agreement would support efforts to protect energy infrastructure, while Homeland Security Secretary Markwayne Mullin pointed to the need to counter drone threats along the southern border. FBI Director Kash Patel said the bureau worked with state and local law enforcement to address drone threats during the FIFA World Cup, including seizing more than 700 drones. “This agreement strengthens the federal coordination behind that work, so new counter-drone tools are tested, deconflicted, and ready to deploy safely alongside civilian aviation,” Patel said. Accident: American B789 near Tokyo on Nov 15th 2024, turbulence injures two cabin crew By Simon Hradecky, created Friday, Nov 22nd 2024 20:24Z, last updated Wednesday, Nov 11th 2026 16:43Z An American Airlines Boeing 787-9, registration N833AA performing flight AA-168 from Tokyo Haneda (Japan) to New York JFK,NY (USA) with 279 passengers and 14 crew, was enroute at FL350 when the aircraft encountered moderate to severe turbulence causing serious injuries to two of 10 flight attendants. The aircraft continued to destination. The FAA reported: "AIRCRAFT ENCOUNTERED MODERATE TO SEVERE TURBULENCE INJURYING FLIGHT ATTENDANTS, TOKYO, JAPAN." stating two flight attendants received serious injuries. On Nov 11th 2026 the NTSB released their final report and investigation docket concluding the probable cause of the accident was: An encounter with turbulence while in cruise flight, resulting in serious injuries to two flight attendants. The NTSB analysed: American Airlines flight 168, encountered unanticipated moderate to severe turbulence during cruise at 34,000 feet (FL340) while enroute to John F. Kennedy International Airport (JFK), New York, New York from Tokyo Haneda International Airport (HND), Tokyo, Japan. As a result, two flight attendants (FAs) sustained serious injuries. Before departing, the flight crew stated they all reviewed the weather forecast on their weather briefing app before departure and noted no significant turbulence or convective activity. The flight departed HND in Visual Meteorological Conditions (VMC) and climbed on the assigned standard instrument departure procedure and leveled off at FL340 in VMC above an overcast layer. The flight crew stated the flight was smooth during the climb out, with occasional “very light” turbulence. During cruise, the captain and the first officer recalled monitoring the weather radar and did not detect any convective activity in the area. Approximately 30-40 minutes after departure, the overcast area rose into the airplane’s altitude. At that time, the FAs were moving around the galley and cabin for service. The captain made an announcement for the FAs to be seated, but the airplane encountered moderate to severe turbulence. After the turbulence subsided, the captain was informed that two FAs had been injured and were unable to continue their duties. Neither requested immediate medical attention. The flight continued uneventfully to JFK, where the injured FAs were met by company personnel and later sought medical evaluation. One FA was diagnosed with a fractured tibia, and another with a fractured ankle. Two additional FAs later reported minor injuries. No passengers were injured. https://flightaware.com/live/flight/AAL168/history/20241115/0820Z/RJTT/KJFK American 787 Reportedly Ignores ATC Instruction, Nearly Collides with Lufthansa 747 An apparent failure to follow an air traffic control hold instruction forced a Lufthansa jumbo jet to make an abrupt stop, narrowly avoiding a collision. By Helen William November 8, 20264 Mins Read Photo: By Curimedia | P H O T O G R A P H Y - Boeing 747-830 Lufthansa D-ABYKUploaded by Dura-Ace, CC BY 2.0, https://commons.wikimedia.org/w/index.php?curid=29924639 COLOGNE- Lufthansa (LH) flight LH463, operated by Boeing 747-8 D-ABYT, had to stop abruptly while taxiing toward a runway at Miami International Airport (MIA) on Thursday, November 5, 2026. The aircraft was preparing to depart for Frankfurt Airport (FRA). The incident involved an American Airlines (AA) Boeing 787-8 operating flight AA1155 from Philadelphia International Airport (PHL). The Dreamliner reportedly entered the Lufthansa aircraft’s path after air traffic control instructed its crew to hold at the Yankee position. Photo: By tjdarmstadt – IMG_6410.jpg, CC BY 2.0, https://commons.wikimedia.org/w/index.php?curid=61529569 Taxiway Conflict Unfolded at Miami Airport The incident occurred during routine ground operations at Miami International Airport. The Lufthansa Boeing 747-8 was taxiing toward the runway for its flight to Frankfurt when the American Airlines Boeing 787-8 reportedly moved into its path. The American Airlines aircraft had arrived from Philadelphia as flight AA1155. According to the reported radio communications, air traffic control had instructed its crew to wait at the Yankee position instead of continuing along the taxiway. However, the Dreamliner apparently failed to follow the hold instruction and continued moving. Its movement brought the aircraft into the path of the approaching Lufthansa Boeing 747-8. Radio communications also indicated that the American Airlines crew had already made several incorrect turns before the encounter with the Lufthansa aircraft. These earlier navigation errors added context to the incident. The American aircraft was supposed to remain at the designated Yankee position according to the instructions from air traffic control. Instead, it reportedly continued taxiing and entered the area occupied by the Lufthansa jumbo jet. The reported radio exchange raised concerns about the American crew’s compliance with the assigned taxi instructions. The Lufthansa crew had to react immediately to avoid a collision. Its Boeing 747-8, registered as D-ABYT, was still moving at full rolling speed when the pilots applied the brakes. According to the radio exchange, the Lufthansa crew informed the control tower that it had to brake the aircraft to a complete standstill while moving at full taxiing speed. The abrupt braking prevented the two aircraft from colliding. The Lufthansa pilots had been preparing for a routine departure when the unexpected movement of the American Airlines Dreamliner forced them to stop. The sudden manoeuvre also caused considerable frustration in the Lufthansa cockpit. The crew questioned how such a dangerous situation could develop during ordinary taxiing operations. Photo- Kiefer. from Frankfurt, Germany; Wikimedia Commons Lufthansa Pilot Describes Encounter The Lufthansa pilot made his frustration clear during the radio communication with the control tower. The crew described the situation with the words, “That was very close to an accident.” The statement reflected the seriousness of the encounter. What should have been a routine taxi toward the runway had turned into a situation requiring immediate action from the Lufthansa pilots. Aero Telegraph reported that the American Airlines aircraft had apparently disregarded the instruction to wait at the Yankee position. The radio traffic also highlighted the earlier incorrect turns made by the American crew. Miami Ground Incident Raises Safety Concerns Airport taxiways require careful coordination between pilots and air traffic controllers. Hold instructions are particularly important because they prevent aircraft from entering areas where other aircraft are moving. In this incident, the instruction for the American Airlines Boeing 787-8 to wait at the Yankee position was intended to keep it clear of the Lufthansa aircraft’s taxiing path. The reported failure to remain at that position created a dangerous conflict between two large commercial aircraft. The Lufthansa crew’s abrupt braking prevented the encounter from becoming a collision. The incident highlights the importance of following assigned taxi routes, complying with air traffic control instructions, and maintaining awareness of surrounding aircraft during ground operations. The available account confirms that the Lufthansa crew managed to stop the Boeing 747-8 in time. The encounter ended without a collision, although the reported radio exchange showed how quickly a routine taxiing operation could develop into a serious safety concern. Stay tuned with us. Further, follow us on social media for the latest updates. Join us on Telegram Group for the Latest Aviation Updates. Subsequently, follow us on Google News Incident: Norwegian B38M at Umea on Oct 1st 2026, takeoff from wrong intersection By Simon Hradecky, created Monday, Nov 9th 2026 20:42Z, last updated Monday, Nov 9th 2026 20:42Z A Norwegian Air Sweden Boeing 737-8 MAX, registration SE-RTE performing flight D8-4016 from Umea to Stockholm (Sweden), was taxiing for departure from Umea's runway 14, entered the runway at taxiway C about 1050 meters down the runway (measured from threshold runway 14). The aircraft turned left and commenced takeoff with 1170 meters remaining for takeoff, became airborne and climbed to safety. On Nov 6th 2026 Sweden's Statens Haverikommission (SHK) rated the occurrence a serious incident and opened an investigation reporting: "A Boeing 737 MAX 8 commenced take-off from a different taxiway than the one used in the take-off performance calculation. The available take-off distance was therefore shorter than that taken into account in the calculation. The aircraft took off approximately 500 meters short of the runway end and passed it at an altitude of approximately 70 feet. The incident is considered a serious incident, as there were limited remaining safety barriers between the incident and a possible accident." The aircraft had performed another flight (D8-4012) earlier the same day, where the aircraft entered the runway via taxiway C, turned right to backtrack runway 14 and commenced takeoff at the runway threshold. Another B38M of Norwegian had performed two more flights out of Umea the same day also backtracking runway 14 from taxiway C. United 737 Jet Blast Suspected After Cessna Flips Upside Down at John Wayne Airport ATC audio and the aircraft’s operator point to a departing jet, while airport officials first cited wind. By Kevin Derby November 9, 20266 Mins Read Photo: By © Raimond Spekking / CC BY-SA 4.0 (via Wikimedia Commons), CC BY-SA 4.0, https://commons.wikimedia.org/w/index.php?curid=36767130 Share CHICAGO- United Airlines (UA) features in the first accounts of a Cessna 172 Skyhawk that overturned at John Wayne Airport (SNA) in Orange County, California, on Saturday, November 7. The aircraft’s operator and ATC audio point to jet blast from a departing airliner, with the operator naming United or Southwest Airlines (WN). Airport officials first attributed the incident to wind. Nobody was hurt. United Jet Blast Flips Cessna 172 The Cessna, registered N57BM, flipped at around 2:38 PM local time. Orange County Fire Authority and airport officials told CBS Los Angeles that firefighters were called to the ramp at around 2:40 PM. The ramp belongs to ACI Jet, a fixed-base operator (FBO) that handles private and general aviation at the airport. Early reports placed the incident on a runway, but officials confirmed it happened on the ramp. The aircraft ended up upside down with two people aboard. The operator says they were a flight instructor and a student. Neither was injured. A large crane lifted the Cessna back onto its landing gear before it was towed away. The extent of the damage is not yet known. Simple Flying reported that recordings from ATC App capture the pilot of another Cessna 172 taxiing behind N57BM. The pilot says the aircraft “just flipped over” and that they turned back to avoid hitting it. When the controller asks whether everyone is okay, the pilot replies that they had been hit by jet blast from a United Boeing 737. The occupants of the overturned Cessna do not respond on the recording. The other pilot explains that they had already shut down their engines, so they could not hear or answer radio calls. Photo: By © Raimond Spekking / CC BY-SA 4.0 (via Wikimedia Commons), CC BY-SA 4.0, https://commons.wikimedia.org/w/index.php?curid=36745546 Conflicting Accounts From Airport Officials and the Operator Orange County Fire Authority and airport officials first told CBS Los Angeles that wind blew the plane over while it sat parked in its stall with nobody aboard. Airport officials later said it was a Cessna 172 carrying a pilot and a passenger, with no injuries. An airport spokesperson attributed the incident to high winds. Neither the fire authority nor the airport has said jet blast caused it. Both said they would share more as the investigation continues. Wind has overturned aircraft at the airport before. In November 2023, a Cessna 172 flipped near a taxiway during gusts of around 50 mph. Orange County Flight Center (OCFC), which owns the Cessna, told CBS Los Angeles that jet blast from “a United or Southwest airline jet” overturned the aircraft. The operator says that jet was cleared to take off as its Cessna left the ramp toward the taxiway. It could not confirm which airline was responsible. OCFC’s director also said a major reconstruction and realignment project at the airport is adversely affecting general aviation aircraft and may jeopardize flight safety. Airport officials have not confirmed that claim. Which flight was involved and how the Cessna was moving at the time also remain unclear. Photo: Andrew E. Cohen | Flickr Jet Blast Endangers Light Aircraft Jet blast is a known hazard for light aircraft near larger jets on the ground. The exhaust can affect nearby aircraft even when an airliner is only taxiing, and the risk grows as pilots add thrust for takeoff. According to Boeing, the exposed area can extend up to 400 feet behind large jets at breakaway thrust. At takeoff thrust, it can reach 1,900 feet. A light aircraft has little weight to resist that force. The Cessna 182M in the Flagstaff case below has a certified maximum gross weight of 2,800 lbs. Photo: Richard Silagi | Wikimedia Commons https://commons.wikimedia.org/wiki/File:United_Express_(Skywest)_Embraer_E175_N134SY_at_SFO_April_2017.jpg Earlier Jet Blast Incidents Involving Light Aircraft At about 8:40 AM on March 6, 2026, a Cessna 182M was cleared to taxi for departure at Flagstaff Pulliam Airport in Arizona. On the airport’s only taxiway, it met jet blast from a parked SkyWest Airlines Bombardier CRJ700. The Cessna flipped and came to rest inverted. Both wings and the tail section were substantially damaged, and the pilot and passenger suffered minor injuries. The National Transportation Safety Board (NTSB) published its final report on June 22, 2026. According to the CRJ700’s operator, the jet had just been repaired, and mechanics were testing its engines at takeoff power. They had not moved it away from the passenger terminal and had not told air traffic control. The Cessna taxied behind the jet after both engines reached takeoff power. The CRJ700’s planning manual lists a 60 mph jet blast 290 feet from the engine with one engine at maximum thrust. Investigators estimated the Cessna was 240 feet away. The operator said its mechanics had to contact ATC before ground engine runs, while the airport manager said no policy designated areas for high-power engine runs. The NTSB named the mechanics’ decision to run the engines at takeoff power in front of an active taxiway, and their failure to notify ATC, as the probable cause. Its findings also list the adequacy of airport policy and procedures as an organizational issue. Tucson 2002 On September 2, 2002, a Cessna 172 landed on runway 11R at Tucson International Airport and taxied toward the ramp while a United Boeing 737 held short at taxiway A4 for takeoff from runway 11L. The instructor was discussing jet blast awareness with the student, and they taxied as far to the right as they could. As they passed, the Boeing spooled up its engines and moved onto the runway for takeoff. The Cessna suffered wing and propeller damage, and neither occupant was hurt. The NTSB cited the instructor’s failure to keep an adequate distance from the jet as the probable cause. It also listed the controller’s failure to issue a jet blast advisory as a factor. Skiathos Aircraft take off unusually close to public viewing areas at Skiathos Airport in Greece. On Monday, August 10, a 52-year-old Italian tourist suffered severe head trauma after a departing aircraft’s jet blast knocked her down. She was airlifted to Volos General Hospital, and another woman reportedly suffered an arm fracture three days later. In July 2022, a 61 year old British tourist suffered serious head injuries, a fractured pelvis, and injuries to her right shoulder and left wrist. Airline and General Aviation Traffic Share John Wayne Airport recorded 319,042 aircraft operations in 2025, including 216,093 general aviation movements and 94,388 commercial movements. General aviation made up about 67.7% of the total. The airport has two runways. The commercial runway is 5,700 feet long, and the general aviation runway is 2,887 feet. The airport handled more than 11.3 million passengers in 2025. DWU Consulting’s analysis of federal T-100 data shows Southwest Airlines as the largest carrier, with 29.2% of 2025 enplaned passengers. American Airlines (AA) followed with 16.8% and United Airlines with 14.3%. Alaska Airlines had 10.5% and Delta Air Lines had 9.2%. Stay tuned with us. Further, follow us on social media for the latest updates. Join us on Telegram Group for the Latest Aviation Updates. Subsequently, follow us on Google News Velocity 173 Elite FG, N776TB, crashed into trees while on approach Date:Tuesday 10 November 2026 Time:22:26 UTC Type: Velocity 173 Elite FG Owner/operator:Private Registration:N776TB MSN:DMO403 Year of manufacture:1999 Fatalities:Fatalities: 1 / Occupants: 2 Other fatalities:0 Aircraft damage:Destroyed Category:Accident Location:1 mile SE of Gwinnett County Airport, GA (LZU/KLZU) - United States of America Phase:Approach Nature:Unknown Departure airport:Lawrenceville-Gwinnett County Briscoe Field, GA (LZU/KLZU) Destination airport:Lawrenceville-Gwinnett County Briscoe Field, GA (LZU/KLZU) Investigating agency: NTSB Confidence Rating: Information is only available from news, social media or unofficial sources Narrative: A Velocity 173 Elite FG, N776TB, crashed into trees while on approach to Gwinnett County Airport, GA (LZU/KLZU). The pilot had report engine trouble. The aircraft had departed KLZU at 16:49 (21:49 UTC), about 37 minutes before the accident. METAR: KLZU 102156Z 27006KT 9SM CLR 22/05 A3007 RMK AO2 SLP191 T02170050 $ KLZU 102256Z 27005KT 10SM CLR 19/04 A3008 RMK AO2 SLP195 T01940044 $ICAO Occurrence Category: SCF-PP: System/Component Failure or Malfunction (Powerplant) Sources: https://www.wsbtv.com/news/local/1-dead-1-injured-after-small-plane-crashes-metro-atlanta/RWCB7AIXLVFN5H3GIMUNATPRNY/?outputType=amp https://www.11alive.com/gallery/news/local/aerials-airplane-crashes-into-woodline-near-gwinnett-county-airport/85-45381e21-f2a2-4cd0-957a-26289bf6525b https://www.fox5atlanta.com/news/what-we-know-about-lawrenceville-plane-crash https://registry.faa.gov/AircraftInquiry/Search/NNumberResult?nNumberTxt=776TB https://www.flightradar24.com/data/aircraft/n776tb#428511ac https://www.jetphotos.com/photo/11373022 (Photo) Location Revision history: Date/timeContributorUpdates 10-Nov-2026 23:52 UTCJustanormalpersonAdded1 1-Nov-2026 01:09 UTCJustanormalpersonUpdated [Aircraft type, Damage, ] 11-Nov-2026 01:12 UTCJustanormalpersonUpdated [Aircraft type, Cn, Operator, ] 11-Nov-2026 01:15 UTCJustanormalpersonUpdated [Cn, Source, ] 11-Nov-2026 01:31 UTCJustanormalpersonUpdated [Total fatalities, Total occupants, Source, ] 11-Nov-2026 06:50 UTCASNUpdated [Time, Registration, Location, Phase, Departure airport, Destination airport, Source, Narrative, Category, ] 11-Nov-2026 06:52 UTCASNUpdated [Narrative, ] Corrections or additions? ... Edit this accident description Lufthansa A380 Pilots Furious with ATC After 17 Minute Takeoff Delay at San Francisco Airport The Lufthansa crew questioned whether improved air traffic control coordination could have reduced its runway waiting time and fuel consumption. By Helen William October 15, 20266 Mins Read Photo: By Lasse Fuss - Own work, CC BY-SA 3.0, https://commons.wikimedia.org/w/index.php?curid=18058676 SAN FRANCISCO- Lufthansa (LH) pilots operating flight LH459 questioned air traffic control after reportedly waiting 17 minutes for takeoff clearance at San Francisco International Airport (SFO) on October 9, 2026. The Airbus A380 was scheduled to fly from San Francisco to Munich Airport (MUC). The crew questioned whether better coordination between tower and approach controllers could have reduced the delay and unnecessary fuel consumption. Photo: By Venkat Mangudi – P1171035, CC BY 2.0, https://commons.wikimedia.org/w/index.php?curid=46460427 Lufthansa Pilots Question 17-Minute Takeoff Delay at SFO The incident attracted attention after an air traffic control recording captured the exchange between the Lufthansa flight crew and controllers at San Francisco International Airport. The discussion focused on the time the aircraft spent waiting for an opportunity to take off while other aircraft continued arriving. Why Lufthansa Flight LH459 Had to Wait According to the recording described in the report, Lufthansa flight LH459 was preparing to depart for Munich when the pilots asked the tower controller how much longer they would have to wait. The tower controller indicated that several aircraft were approaching the airport and that traffic on final approach was keeping the sequence busy. The controller suggested that the aircraft might receive an opportunity to depart after two more arrivals. The Lufthansa pilots subsequently received takeoff clearance and transferred to the departure controller. However, the crew continued to question why the aircraft had waited so long without an earlier opportunity to depart. The pilots asked whether the approach and tower controllers coordinated departure gaps during busy traffic periods. They said the aircraft had waited 17 minutes and raised concerns about the fuel consumed while holding near the runway. The departure controller responded that the crew should raise questions about creating a departure gap with the tower controller. The response did not provide a detailed explanation of why an earlier departure opportunity had not been available. The Lufthansa pilots said they intended to submit a report and wanted the issue clarified to help prevent similar situations during future departures, OMAAT flagged. By Curimedia – Airbus A380-841 Lufthansa D-AIMC First Landing in Barcelona Airport, CC BY 2.0, https://commons.wikimedia.org/w/index.php?curid=23489544 Why Takeoff Delays Occur at Busy Airports Air traffic controllers must manage arriving and departing aircraft while maintaining the required separation between movements. At a busy airport such as SFO, the arrival sequence can limit the opportunities available for departing aircraft. A departure gap may require controllers to adjust the sequence of arriving aircraft or wait until traffic conditions allow a safe takeoff. Those decisions depend on factors such as runway availability, aircraft separation requirements, traffic volume, and the operating conditions at the time. Creating an opening for one departing aircraft can also affect other aircraft in the sequence. Controllers must therefore consider the overall traffic flow rather than the needs of a single flight. The radio exchange indicates that arrivals were occupying the available sequence during the Lufthansa aircraft’s wait. However, the recording alone does not establish whether the controllers could have created an earlier departure gap without affecting other traffic. Photo: By Lasse Fuss – Own work, CC BY-SA 3.0, https://commons.wikimedia.org/w/index.php?curid=18058671 Lufthansa Pilots Raise Concerns About Fuel Consumption Fuel consumption was a central issue in the pilots’ complaint. Aircraft continue to consume fuel while taxiing and waiting on the ground with their engines running, although the amount depends on operating conditions and engine settings. For an Airbus A380, even a relatively short ground delay can create an additional operating cost. Airlines must account for fuel expenses across their networks, making unnecessary waiting a legitimate concern for flight crews and airline management. However, reducing the waiting time for one aircraft does not automatically guarantee lower fuel consumption across the entire airport. Creating additional space in the arrival sequence could also delay other aircraft or require changes to traffic flow. A proper assessment would need information about the aircraft’s actual fuel burn, the traffic sequence, runway conditions, and the available departure opportunities. The recording does not provide enough information to calculate the fuel consumed during the 17-minute wait or determine the financial impact. Photo: Lufthansa Was the Lufthansa Crew Right to Complain? The pilots had a reasonable basis to ask whether better coordination between approach and tower controllers could have improved the departure sequence. Their concern about fuel consumption also has a clear operational basis. However, a 17-minute wait does not, by itself, demonstrate a failure in air traffic control. Busy airports regularly balance competing demands from arriving and departing aircraft, and controllers cannot always provide an immediate departure clearance. The central question is whether an earlier departure opportunity was operationally feasible. Answering that question would require more than the radio exchange, including information about the runway configuration, arrival traffic, required separation, and controller decisions. The crew’s intention to file a report could help direct attention to the event. An operational review could assess whether the delay was unavoidable or whether adjustments to traffic coordination might have improved efficiency. No formal finding of controller error is established by the available account of the exchange. Photo: By © Raimond Spekking / CC BY-SA 4.0 (via Wikimedia Commons), CC BY-SA 4.0, https://commons.wikimedia.org/w/index.php?curid=36767130 What the SFO Incident Means for Airport Efficiency The exchange highlights the challenge of balancing fuel efficiency with safe and orderly airport operations. Pilots naturally want to minimize time spent waiting on the ground, while controllers must maintain separation and manage traffic across the airport. Better coordination can help reduce avoidable waiting when traffic conditions permit. However, any proposed change must account for its effect on other aircraft, not simply shorten the delay experienced by one flight. The incident therefore raises a relevant operational question: could controllers have identified a departure gap earlier, or did the arrival sequence leave no practical opportunity to release the Lufthansa aircraft? The available recording does not provide enough information to settle that question. Photo: By tjdarmstadt – IMG_6248.jpg, CC BY 2.0, https://commons.wikimedia.org/w/index.php?curid=61529535 Bottom Line The Lufthansa flight LH459 crew questioned a 17-minute takeoff wait at San Francisco International Airport, arguing that better coordination between tower and approach controllers could have reduced fuel consumption. Their concern was understandable, but the delay alone does not prove that air traffic control made an error. Determining whether the wait could have been avoided would require a detailed review of the airport’s traffic sequence and operating conditions. Stay tuned with us. Further, follow us on social media for the latest updates. Join us on Telegram Group for the Latest Aviation Updates. Subsequently, follow us on Google News The float equipped Twin Otter's left float partially detached. Date:Wednesday 11 November 2026 Time: Type: de Havilland Canada DHC-6 Twin Otter 300 Owner/operator:Trans Maldivian Airlines Registration:8Q-TAL MSN:324 Year of manufacture:1971 Engine model:P&W Canada PT6A-27 Fatalities:Fatalities: 0 / Occupants: Other fatalities:0 Aircraft damage:Substantial Location:Malé-Velana International Airport (MLE/VRMM) - Maldives Phase:Unknown Nature:Passenger Departure airport: Destination airport:Confidence Rating: Information is only available from news, social media or unofficial sources Narrative: The float equipped Twin Otter's left float partially detached. Sources: https://sun.mv/230386 https://x.com/AviatorsMaldive/status/2120458156455383342?a=I2TUgbhHW5QW75VYpgU&s=20 https://twinotterworld.com/msn-324 History of this aircraft Other occurrences involving this aircraft 9 March 2012FAP-317Fuerza Aérea del Peru - FAP0Laguna Caballococha, Ramón Castilla, LoretosubHeavy landingLocation Media: Revision history: Date/timeContributorUpdates 11-Nov-2026 12:42 UTCSignorPignoliniAdded 11-Nov-2026 12:47 UTCASNUpdated [Aircraft type, Registration, Cn, Location, Phase, Source, Embed code, Narrative, Category, ] 11-Nov-2026 13:02 UTCASNUpdated [Source, Embed code, ] Corrections or additions? ... Edit this accident description Airline data breaches expose Asia’s aviation cyber risks Airlines and Aviation Asia WRITTEN BY : Siriporn Sachamuneewongse November 12, 2026 Cybersecurity is becoming a critical part of aviation safety as Asian airlines rely increasingly on interconnected digital systems. RAMON CC / Shutterstock.com Asia's aviation industry faces a growing cybersecurity challenge. Recent data breaches affecting several airlines have exposed vulnerabilities in an industry that increasingly relies on interconnected digital platforms. A major warning emerged this November. Several major Asian airlines disclosed unauthorised access to passenger booking information held by global travel technology provider Amadeus. The affected carriers include Singapore Airlines, Cathay Pacific, Japan Airlines, All Nippon Airways (ANA) and Thai Airways. Bangkok Airways also issued a separate passenger notice about an information security incident involving Amadeus. The incident has raised questions about how airlines manage third-party technology risks. Critical passenger services often depend on external platforms, making supplier security increasingly important. Thai Airways reported that approximately 60,529 passenger records may have been accessed. Singapore Airlines reported exposure involving approximately 46,000 booking records, while Cathay Pacific identified around 53,000 affected bookings. Japan Airlines and ANA also confirmed potential exposure of passenger reservation information. They reported approximately 92,000 and 37,800 affected customers, respectively. Malaysia Airlines and Asiana Airlines also disclosed incidents involving the same provider. Meanwhile, Bangkok Airways advised passengers that the incident may have affected some booking information. The exposed information potentially included passenger names, booking references and travel itineraries. Some records also contained contact and travel-document details. The airlines said the incidents did not affect their internal systems or flight operations. They also reported no compromise of payment information. Nevertheless, the breach shows how a vulnerability outside an airline's direct IT environment can expose customer information across international networks. The implications are significant for a region experiencing strong growth in international connectivity. Airlines and technology companies increasingly share information and rely on common digital infrastructure. A weakness in one part of this ecosystem can quickly become a regional problem. ICAO: Cybersecurity must become part of aviation safety The International Civil Aviation Organization (ICAO) has established a framework to address this challenge. It emphasises that cybersecurity is essential to the safety, security, efficiency and resilience of international civil aviation. Its Aviation Cybersecurity Strategy rests on seven pillars: international cooperation, governance, legislation and regulation, cybersecurity policy, information sharing, incident management and emergency planning, and capacity building and cybersecurity culture. ICAO's vision is for global civil aviation to be "resilient to cyber-attacks, safe and secure, while continuing to innovate and grow". A key reference is its Global Cyber Risk Considerations, Document 10213. The document guides governments and aviation stakeholders on harmonising cyber risk management. It calls for cybersecurity to become part of aviation safety, security, air navigation efficiency and capacity management, rather than remain a separate IT concern. For Asia-Pacific, the priority is to translate ICAO's global framework into consistent national requirements and practical measures across airlines and airports. The opportunity for Asia: Move from individual protection to collective resilience Asia's aviation growth will increasingly depend on digital connectivity. Integrated passenger services, biometric identification, automated airports, electronic flight information and AI-assisted air traffic management are becoming central to the region's competitiveness. But greater connectivity also means greater interdependence. The airline data breaches show how one technology provider can become a common point of exposure for carriers across several countries. For major hubs such as Bangkok, Singapore, Hong Kong, Kuala Lumpur, Tokyo and Seoul, cybersecurity is no longer simply an IT concern. It plays a vital role in maintaining international connectivity, protecting passenger information and sustaining confidence in the travel industry. The real test for Asian aviation is not whether the industry can prevent every cyberattack. It is whether airlines and airports can contain incidents, protect passengers and maintain essential services without compromising safety. As airlines and airports accelerate digital transformation, they must build cybersecurity into every stage of the process. This includes selecting technology suppliers and operating automated infrastructure. CALENDAR OF EVENTS . AIN Corporate Aviation Leadership Summit (CALS) Mx November 16, 2026 Savannah, Georgia . Aircraft Fire Hazards, Protection, and Investigation 17 to 19 November 2026, Woburn MA : Save The Date - February 11-12, 2027 - ProDIGIQ User Conference . 2027 ACSF Safety Symposium - April 6-8, 2027 - ERAU Daytona Beach, FL Curt Lewis