A new flight-simulator study claims the most infamous turns of 9/11 look more like automation than shaky hands—and the debate it triggers is bigger than one cockpit. Story Snapshot A formal simulator project asserts key 9/11 maneuvers strain plausibility for low-time pilots and fit automated or precision-guided control profiles [3]. Aviation research shows autopilots can execute aggressive, precise maneuvers when configured for that purpose, proving capability—though not deployment on 9/11 [4][1]. The official record describes air traffic control actions and standard system tracking with no verified remote-takeover mechanism disclosed [5]. The 9/11 Commission records hijacker interaction with standard cockpit automation, which supports manual control aided by routine systems, not remote override [12]. What the simulator study claims and why it matters The new presentation, Manual or Automated? A Flight Simulation Study of Reported Aircraft Maneuvers on 9/11, frames specific bank angles, descent rates, and high-speed turns as exceeding what low-experience pilots could likely perform reliably under stress. Its core thesis is not that airplanes cannot do these maneuvers, but that the consistency and precision in the historical tracks look more like automated or guided control than ad hoc hand-flying [3]. That distinction—capability versus operator skill—is the fulcrum of this fight. Supporters point to decades of research showing autopilot systems can be tuned for highly precise tracking and coordinated turns. NASA documented an experimental flight test maneuver autopilot that stabilized and executed aggressive test profiles, demonstrating repeatable precision well beyond typical line operations [4]. Academic formation-flight work further shows transport-category aircraft can hold formation and perform coordinated maneuvers with automation supported by disciplined pilot inputs, validating high-precision envelope management in simulation and flight-test environments [1]. The capability plainly exists; the question is whether it existed on those flights as used. What the public record supports—and what it does not The National Air Traffic Controllers Association’s retrospective underscores how the system handled the unfolding crisis with standard air traffic control tools, voice coordination, and radar coverage—no parallel network, no acknowledged remote-control infrastructure [5]. The 9/11 Commission Report describes interactions with routine cockpit automation, including autopilot modes engaged and disengaged during segments of the flights, and a hijacker-directed turn using ordinary systems on one aircraft [12]. That record anchors the conventional reading: humans in the cockpit, possibly using standard automation, but not directed by an undisclosed remote-takeover device. Common sense shaped by conservative principles asks for proof of mechanism before rewriting a historical baseline. The simulator team’s results challenge pilot-skill assumptions, but they do not present verified hardware, installations, or authenticated maintenance records demonstrating a remote or precision-guidance retrofit on the specific aircraft. Without a chain of verifiable evidence linking a capability to an installation and then to operational use, the prudential view treats such claims as hypotheses demanding more than performance replication to overturn the record. Where simulations illuminate—and where they mislead Simulation excels at testing plausibility bounds and surfacing human factors gaps. It is less reliable when used to imply that a reproduced path proves a particular mechanism. Professional training culture reminds us that manual flying proficiency erodes without practice, which is why safety leaders advocate deliberate stick-and-rudder reps even for advanced-automation fleets [11]. That wisdom cuts both ways: undertrained pilots might fail in repeat tests, but that alone cannot eliminate the possibility that a few determined individuals could succeed once. A single success in the real world does not require a high average in the lab. The hard-nosed reconciliation is straightforward. First, accept that sophisticated automation for tight maneuvers exists and has been flight-tested in other contexts [4][1]. Second, recognize that the official 9/11 record documents standard air traffic control workflows and cockpit automation usage without confirming any exotic remote-control architecture [5][12]. Third, read the simulator findings as a stress test on human-skill narratives, not as dispositive proof of an alternative control scheme. The bar to upend history is not intriguing performance data; it is verifiable mechanism tied to the specific aircraft. Sources: [1] Web – Maneuvers During Automatic Formation Flight of Transport Aircraft … [3] Web – Manual or Automated? A Flight Simulation Study of Reported Aircraft … [4] Web – [PDF] Development and Flight Test of an Experimental Maneuver … [5] Web – ATC on 9/11: ‘The Single Greatest Feat in All of ATC History’ – NATCA [11] Web – [PDF] Silver Linings – Flight Safety Foundation [12] Web – [PDF] The 9/11 Commission Report – Avalon Project