Flight Safety Information - November 18, 2026 No. 227 In This Issue : Cruz announces partial deal on aviation safety overhaul : Severe turbulence injures 5 on JetBlue flight to Florida : What the UAS Community Can Learn From Crewed Aviation Safety: Know the Aircraft, Rehearse the Emergency : Incident: Thai A359 near Delhi on Nov 15th 2026, engine problem : Russian An-12 military transport plane caught fire mid-air and crashed : Incident: Indigo A21N at Mangaluru on Nov 16th 2026, rejected takeoff due to engine failure : FAA temporarily stops router installations connected to air travel stoppage : Downing of a US Army MQM-170 UAV through the use of electronic warfare : Boeing 737-7H4, suffered a blown tire on takeoff : Calendar of Events Cruz announces partial deal on aviation safety overhaul The Senate Commerce Committee chair said the agreement would mandate an aircraft location-receiving technology, though he acknowledged “we still have a couple of details to negotiate” related to the military. Sam Ogozalek 11/17/2026, 1:27pm ET Nearly two years after a deadly midair crash over Washington, Senate Commerce Chair Ted Cruz (R-Texas) said Tuesday that a partial deal had been reached on an air safety overhaul meant to avoid that calamity again. Cruz said the Senate and House had “reached an agreement in principle” to mandate a type of location-receiving technology known as Automatic Dependent Surveillance-Broadcast In, or ADS-B In, on flights that already must broadcast via ADS-B Out. He acknowledged that more work was to be done. “We still have a couple of details to negotiate with the House Armed Services Committee,” he said at an event for victims’ families outside the Capitol. “But with this agreement in principle, I believe we’re going to get this bill done, and my objective is to get it done this year.” It wasn’t immediately clear what those details were nor was it clear what the ADS-B In deal entails exactly. The breakthrough significantly increases the odds that Congress may finish the push to finalize air safety legislation during the lame-duck session of Congress. Committee ranking member Maria Cantwell (D-Wash.) added that the agreement is on civil aviation provisions and that it was reached Thursday with the House Transportation and Infrastructure Committee. ADS-B In language had been a major sticking point as the Senate and House championed competing bills responding to last year’s Washington midair disaster, the ROTOR Act, S. 2503 (119), and the ALERT Act, H.R. 7613 (119), respectively. A spokesperson for the House Armed Services Committee didn’t immediately provide comment. The January 2025 crash between a PSA Airlines and Army Black Hawk helicopter killed 67. Severe turbulence injures 5 on JetBlue flight to Florida All five declined hospital transport after the plane landed at Fort Lauderdale-Hollywood International Airport early Tuesday By Anders Hagstrom FOXBusiness Fiber optics, copper wires ‘do not mix well’: Former FAA senior executive Former FAA senior executive Michael O’Donnell discusses the fallout from a nationwide ground stop as airlines work through a backlog of delays on ‘The Claman Countdown.’ Five people were injured in severe turbulence during a JetBlue flight from Puerto Rico to Florida on Tuesday, authorities say. The flight landed at Fort Lauderdale-Hollywood International Airport early Tuesday morning, with Broward Sheriff Fire Rescue personnel administering medical evaluations to the five people after they deplaned. All five individuals declined transportation to nearby hospitals, police say. JetBlue confirmed the turbulence incident in a statement to Local 10 News. There were no reports that the plane suffered damage during the flight. "The safety of our customers and crewmembers remains our top priority," JetBlue said in a statement. The bumpy flight comes just days after the FAA ordered a nationwide ground stop late last week, stranding over a million passengers across the country. What the UAS Community Can Learn From Crewed Aviation Safety: Know the Aircraft, Rehearse the Emergency Contributed Guest Article • Uncrewed Insights Chris Raabe flying | Image via Chris Raabe Contributed by Chris Raabe, PhD, Global CTO, ACSL Checklist. Maintenance. Procedures. I’m both a drone pilot and recreational single-engine airplane pilot. I’m flying an experimental plane now, and am in the process of building another. Flying a drone and flying an aircraft are, for the most part, very different experiences, but both carry an incredible responsibility. One thing stands out to me when looking at the two: The crewed aircraft industry has over 120 years of safety experience under its belt. It’s worth examining the lessons and procedures it has developed. Before taking the runway, pilots are taught to wiggle all of their controls. Student pilots may think this is a silly and unnecessary step, but it's an intentional safeguard against something that has led to loss of life in the past. In 1935, two very experienced test pilots died seconds after takeoff because neither noticed that the elevator gust lock was still engaged, preventing them from controlling pitch. This was the birth of the preflight checklist. Safety is a word that gets tossed around frequently in this industry. UAS platforms have become remarkably capable, remarkably quickly. From autonomous functionality to obstacle sensing to ADS-B technology, significant safety milestones have emerged in a short time. Working on my own aircraft, keeping it airworthy, learning the systems, and training for the license itself has taught me that safety isn’t a mindset you visit once. Aviation safety is about sets of habits you rehearse until they’re automatic, long before you ever need them. The drone industry was born from radio control hobbyists; it's still young and moving fast. In the U.S., recreational drone pilots require no license, and commercial pilots must only prove their aeronautical knowledge, not their practical flying skill. That makes sense for an industry sprouting from hobbyists, but in my opinion it doesn't match the actual level of risk. And the risk is real, even as reliability and autonomy improve. You never know when a bird is going to take interest in a drone, or when the weather is going to turn faster than the forecast predicts, or if a system fails mid-flight. Lessons That Have Proven Their Worth A critical part of crewed aircraft safety procedures is what are called “memory items,” the immediate actions you must take from memory when a certain condition presents itself. What controls am I reaching for? Where are they located on my instrument panel? What order do I need to hit them? Image via Chris Raabe These are lessons drilled into every pilot earning a crewed aircraft license, and they bring confidence and ownership. The engine sputters, and my fingers immediately move from the lower right to the upper left: flap handle up, fuel cutoff valve open, engine choke closed, throttle open, fuel pump switch on, ignition B on, ignition A on. For drone pilots, similarly memorizing buttons, locations, workflow, and what to do in various emergency scenarios is the first step. It sounds like common sense, but in reality, pilots often get a drone out of the box and into the air without ever thinking it through. What do you do if the drone starts moving in an unexpected direction? What if it loses GPS? What if the wind suddenly picks up? Every pilot needs to consider scenarios before they’re actually living through them. A bad crash doesn’t affect just the pilot flying. It can injure a bystander, damage property, and set back the credibility of the wider drone community. Getting into the field, memorizing the controller and drone settings in case of an emergency isn’t a regulatory checkbox, but it’s one of the most important things you can do to fly safely. Crewed aviation built structured tools around safety procedures, some of which the UAS community has adopted. • P.A.V.E. breaks risk into Pilot, Aircraft, enVironment, and External pressures to evaluate flight hazards. • I’M SAFE is another protocol adopted into Part 107 training where a pilot runs through a fitness-to-fly self-checklist: Illness, Medication, Stress, Alcohol, Fatigue, Emotion. Communication deserves more attention. When you’re flying or training with an instructor, the first thing they tell you is never touch the controls until I say, “You have the flight controls.” As soon as you touch controls, you say back, “I have the flight controls,” and I once again confirm, “You have the flight controls.” Over-communicating helps reduce risk while clearly defining who is doing what. As drone fleets expand, and more systems are put into the air at once or flying BVLOS operations, we can take lessons from this. What Procedures Drone Pilots Should Adopt Crewed aviation emergencies line up with uncrewed aviation more than we think. Loss of GPS is loss of navigation. A lost connection to the control tower is a communication failure. A critical low battery is an engine failure. Platforms have come a long way in performance and reliability, and we’ve become used to that. While the systems continue to improve and become more capable, I believe it is even more crucial for pilots to take safety measures into their own hands. Image via Chris Raabe Pilots need to focus on building real-world flying skills, taking the time to run safety-focused missions on their own with dedicated time to learn how to handle emergencies. Before you fly, spend 10 minutes preplanning emergencies, landing sites, and failure scenarios for the mission, and communicate that point to everyone on site. Lastly, understand that risk doesn’t discriminate by experience. Most of us will fly hundreds of uneventful missions, but an unexpected emergency can appear at any moment, no matter how much stick time a pilot has. Personally, during long stretches of uneventful flight in an airplane, I like to practice button sequences for various scenarios to keep my muscle memory fresh. When I’m flying over a forest or rugged terrain, I am always scanning for places to land in case of an emergency. I apply the same lessons to operating a drone, making sure I’m ready to adjust it in an emergency, locate it in the sky, and fly in manual mode. I know my aircraft. I know how the engine sounds at different RPMs, how the wind noise changes with speed, and how it should smell when everything’s right. UAS pilots need to focus more on practicing challenging scenarios and knowing their drone inside and out. When a crewed aircraft pilot rents an aircraft, they are asked whether they have time flying that model. If not, they must complete a “transition checkout” where they fly with a Certified Flight Instructor until signed off. This helps bridge the knowledge gap and build familiarity with the aircraft. Prepare For The Unexpected While Embracing Innovation Despite the preflight checklist being introduced in 1935 after that initial incident, the elevator gust lock has been responsible for several more deadly crashes in '47, ‘79, ‘92, and even as late as 2014. Knowing your aircraft, practicing regularly, following procedures, and memorizing emergency motions will always remain critical. Pilots can't be complacent even after safety systems continue to improve. Automation is the future of most enterprise operations. There’s no doubt we’re headed that direction, and it’s the right one. But that doesn’t excuse you from knowing your system in detail. What’s your Return to Home (RTH) flight path? Does it retrace your route home or fly straight back? What altitude does it climb to during RTH? Where is your emergency motor cutoff? Have you actually logged stick time in manual mode, or only automated/positioning mode? Are you flying by the camera feed alone? And have you practiced with the nose facing you, operating the drone in reverse? What’s your critical low battery threshold, and does your mission plan actually respect it? Aviation developed its safety procedures through experience, practice, and commitment. It earned it through more than a century of hard lessons, most of them written in hindsight. The drone industry doesn't get to skip that process entirely, but we also don’t have to relearn it from zero either. Incident: Thai A359 near Delhi on Nov 15th 2026, engine problem By Simon Hradecky, created Monday, Nov 16th 2026 17:38Z, last updated Monday, Nov 16th 2026 17:38Z A Thai Airways Airbus A350-900, registration HS-THT performing flight TG-925 from Munich (Germany) to Bangkok (Thailand), was enroute at FL370 overflying Delhi (India) when the crew decided to divert to Delhi. The aircraft landed safely on Delhi's runway 28 about one hour after leaving FL370. Germany's and Thailand's media report an engine (Trent XWB) problem. The airline reported a technical fault, a replacement aircraft would be dispatched to Delhi to continue as flight TG-8479. The flight TG-8479 was cancelled. The aircraft remained on the ground in Delhi for about 34 hours before continuing to Bangkok. Russian An-12 military transport plane caught fire mid-air and crashed Date:Tuesday 17 November 2026 Time:20:27Type: Antonov An-12BK Owner/operator:Russian Air Force Registration: MSN: Fatalities:Fatalities: 19 / Occupants: 19 Other fatalities:0 Aircraft damage:Destroyed Location:Near Yagunovo, Kemerovo Oblast - Russia Phase:En routeNature:Military Departure airport:Novosibirsk Destination airport:Kansk Narrative: A Russian An-12 military transport plane caught fire mid-air and crashed near the village of Yagunovo while attempting an emergency landing at Kemerovo Airport, approximately 5 km short of the runway. (in central Russia), according to reports out of Russia. All 19 occupants died in the crash. Sources: https://x.com/Osint613/status/2122708220921651632 https://x.com/BNODesk/status/2122717961626501541?a=ZgJ42_9f8nty3XzBnWk&s=20 https://uk.news.yahoo.com/17-dead-russian-military-aircraft-153930654.html https://x.com/MarcinRogowsk14/status/2122729542695387400 time of crash from security cam https://x.com/bayraktar_1love/status/2122765970972262844 Location Media: Revision history: Date/timeContributorUpdates 17-Nov-2026 15:26 UTCDolly564Added 17-Nov-2026 16:09 UTC2600:1000:b178:45fbUpdated [Total fatalities, Total occupants, Source, ] 17-Nov-2026 16:10 UTC2001:b07:ab5:8733:cUpdated [Operator, Total fatalities, Total occupants, Nature, Source, ] 17-Nov-2026 16:13 UTCgerard57Updated [Phase, Source, Narrative, ] 17-Nov-2026 16:29 UTCAnon.Updated [Source, ] 17-Nov-2026 16:32 UTCIceman 29Updated [Aircraft type, Country, Source, Narrative, ] 17-Nov-2026 16:44 UTCIceman 29Updated [Country, Embed code, ] 17-Nov-2026 16:47 UTCIceman 29Updated [Country, Category, ] 17-Nov-2026 17:01 UTCvasilfUpdated [Time, Location, Nature, Departure airport, Destination airport, Category, ]17-Nov-2026 17:09 UTCvasilfUpdated [Location, ] 17-Nov-2026 17:21 UTCDolly564Updated [Location, Source, ] 17-Nov-2026 17:32 UTCTigerTimonUpdated [Time, Source, ] 17-Nov-2026 18:20 UTC2001:b07:ab5:8733:cUpdated [Departure airport, Destination airport, ] 17-Nov-2026 19:31 UTCIceman 29Updated [Date, Total fatalities, Total occupants, Country, Source, Narrative, ] 17-Nov-2026 20:05 UTC2a02:810d:1c1a:0:20Updated [Date, ] Corrections or additions? ... Edit this accident description Incident: Indigo A21N at Mangaluru on Nov 16th 2026, rejected takeoff due to engine failure By Simon Hradecky, created Tuesday, Nov 17th 2026 15:57Z, last updated Tuesday, Nov 17th 2026 15:57Z An Indigoa Airbus A321-200N, registration VT-IBB performing flight 6E-388 from Mangaluru to Bangalore (India) with 236 people on board, was accelerating for takeoff from Mangaluru's runway 24 when the crew rejected takeoff at high speed (about 135 knots over ground) after the left hand engine emitted a number of bangs and streaks of flame. The aircraft slowed safely and stopped on the runway for about 10 minutes before returning to the apron. The airline reported a technical problem occurred shortly before takeoff. A replacement A321-200N registration VT-ILJ reached Bangalore with a delay of about 4:50 hours. The occurrence aircraft is still on the ground in Mangaluru about 27 hours after the rejected takeoff. FAA temporarily stops router installations connected to air travel stoppage The Federal Aviation Administration has paused installing routers linked to last week’s air traffic trouble that caused chaos for traveler • By JOSH FUNK and KEVIN FREKING • Associated Press Nov 17, 2026 Updated 16 mins ago WASHINGTON (AP) — The Federal Aviation Administration has paused installing routers linked to last week’s ground stop that caused chaos for travelers, the agency said Tuesday. The move comes amid growing scrutiny over the nation’s air traffic control system and as the Trump administration is making a new request for $50 billion to improve air travel. Democrats in the Senate are demanding that the administration provide clear answers about what went wrong. President Donald Trump has blamed old technology and Democrats for the nationwide grounding of all planes and upheaval at the nation’s airports. But the FAA has been struggling to modernize the air traffic control system for decades — going back well before the first Trump administration. FAA spokesperson Ian Gregor said the agency paused new installations of Juniper routers and disabled the functionality of all existing ones on Friday after technicians linked the problems to a new router in El Dorado, Arkansas. The FAA has said that another router installed three weeks earlier in Amarillo, Texas, also went haywire. The system became overloaded when the federal contractor that maintains the FAA’s telecommunications network was replacing outdated copper wires with fiber optic lines across the nation. The closure of U.S. airspace was needed, Transportation Secretary Sean Duffy said, after the new router that L3Harris installed in Arkansas resulted in a cascade of intermittent communications and radar signals at 17 of the 22 regional air traffic control centers. The centers direct planes cruising at high altitudes. The FAA said that “excessive data” was flooding the system “at a rate of 1,000 connection attempts every 4 to 5 seconds.” That deluge created instability with “aircraft communications and radar feeds," the agency said. For now, the FAA is relying on older Cisco routers that have been in place for 25 years to continue operating the network while they investigate the cause of Friday’s trouble. The routers that malfunctioned last week are being tested in a lab at the headquarters of L3Harris. A spokesperson for Hewlett Packard Enterprise, which owns Juniper, told ABC News that the company believes the routers were working properly when the ground stop occurred. The company did not immediately respond to inquiries from The Associated Press. “Based on what we know today, the device functioned as it was configured to by the installer. It did not fail or act improperly,” the company said in its statement. Democrats on the Senate Commerce Committee said they believe that only 400 out of more than 3,600 new routers have been installed. “Identifying the device that failed does not establish why it failed. FAA must investigate further to determine the root cause and report to Congress on how it intends to prevent future issues,” the Democrats said in a letter sent to Duffy. Upgrading the nation’s air transportation system is an effort that Congress has dedicated significant sums to in recent years. The problems with aging equipment at the FAA date back decades and past efforts to modernize the system have come up short. Duffy has pushed Congress for billions more dollars to upgrade a system he said had been neglected for decades, saying again Monday that much more is needed. The Trump administration on Tuesday sent a letter to key lawmakers outlining its request for $50.1 billion to modernize the system and make other improvements at airports. The request calls for $10.1 billion for updating the nation’s air traffic control system. Similar amounts would go toward boosting airport infrastructure, replacing or refurbishing terminals at high-impact hubs, constructing five new traffic control centers and improving or replacing up to 140 FAA-owned air traffic control towers. “Congressional approval of these funds will equip the FAA to deliver to the American people a brand-new air traffic control system that is safer, smarter, faster, and more efficient,” states the letter, which was obtained by The Associated Press. Congress approved $12.5 billion last year to modernize much of the key infrastructure that more than 45,000 flights a day rely on to reach their destinations safely. The funds were earmarked for replacing outdated technologies such as copper wires, floppy discs and radars built in the 1980s, but much of that money will also go toward runway upgrades and other construction projects. Downing of a US Army MQM-170 UAV through the use of electronic warfare Date:Monday 16 November 2026 Time:Type: Griffon Aerospace MQM-170 Outlaw Owner/operator:US Army Registration:MSN: Fatalities:Fatalities: 0 / Occupants: 0 Other fatalities:0 Aircraft damage:Unknown Location:Qeshm Island, Strait of Hormuz - Iran Phase:Combat Nature:Military Departure airport: Destination airport: Narrative: On 16 November 2026, Iran’s Islamic Revolutionary Guard Corps (IRGC) claimed the downing of a US Army MQM-170 UAV as it was flying over Qeshm Island in the Strait of Hormuz. The IRGC stated that the drone was downed through the use of electronic warfare to take control of the aircraft's guidance and control systems. Sources: https://www.aa.com.tr/en/middle-east/iran-says-it-captured-us-drone-south-of-qeshm-island-in-strait-of-hormuz/4126410 Revision history: Date/timeContributorUpdates 17-Nov-2026 12:37 UTCNeboAdded Corrections or additions? ... Edit this accident description Boeing 737-7H4, suffered a blown tire on takeoff Date:Sunday 15 November 2026 Time:20:17 UTC Type: Boeing 737-7H4 (WL) Owner/operator:Southwest Airlines Registration:N926WN MSN:36629/2663 Year of manufacture:2008 Engine model:CFMI CFM56-7B Fatalities:Fatalities: 0 / Occupants: Other fatalities:0 Aircraft damage:Minor, repairedCategory:Incident Location:Orlando International Airport, FL (MCO/KMCO) - United States of America Phase:Take off Nature:Passenger - Scheduled Departure airport:Orlando International Airport, FL (MCO/KMCO) Destination airport:Knoxville Airport, TN (TYS/KTYS) Confidence Rating: Information is only available from news, social media or unofficial sources Narrative: Southwest Airlines flight WN2879, a Boeing 737-7H4, suffered a blown tire on takeoff from Orlando (MCO), Florida. The aircraft returned to MCO and landed 36 minutes after takeoff. ICAO Occurrence Category: SCF-NP: System/Component Failure or Malfunction (Non-Powerplant) Sources: FAA https://www.flightaware.com/live/flight/SWA2879/history/20261115/2010Z/KMCO/KTYS Location Revision history: Date/timeContributorUpdates 17-Nov-2026 12:46 UTCASNAdded Corrections or additions? ... Edit this accident description CALENDAR OF EVENTS : Save The Date - February 11-12, 2027 - ProDIGIQ User Conference . 2027 ACSF Safety Symposium - April 6-8, 2027 - ERAU Daytona Beach, FL Curt Lewis