F-16s Launch Empty—One Terrifying Option

In the chaos of 9/11, a handful of fighter pilots launched without missiles and calmly planned to stop a hijacked airliner by using their own jets as battering rams—a stark example of how air defense improvises when doctrine and time run out.

The Short Version

Two D.C. Air National Guard F-16 pilots, including Lt. Heather “Lucky” Penney, launched unarmed and prepared a deliberate ramming tactic to keep United Flight 93 from reaching Washington, D.C.
Their plan divided targets: one jet into the airliner’s cockpit, the other into the tail, to destroy flight controls or destabilize the aircraft.
National command authorized lethal force against hijacked aircraft that morning; communication delays meant front-line pilots often flew without timely guidance.
The “ram mission” sits within a broader 9/11 reality: procedures existed for hijackings, but the day’s speed and confusion forced decisions at the edge of doctrine.

What “prepared to ram” actually meant

When Heather Penney and her flight lead, Marc “Sass” Sasseville, scrambled from Andrews Air Force Base on September 11, their jets carried no live missiles—time was the scarce commodity, and loading weapons would have ceded it. The pair assessed a last-resort tactic grounded in aerodynamics and cockpit systems: Sasseville would take the cockpit, where the hijackers and flight controls were concentrated; Penney would strike the tail to sever control authority. In effect, they planned to break the aircraft’s ability to fly by destroying its brain and its balance. This was not a Hollywood flourish. It was a disciplined, pre-briefed division of aim points with the specific intent to neutralize the airliner even at the cost of their own lives.

Penney’s role in that mission is no longer oral history alone. The National Museum of the U.S. Air Force summarizes her as “known for flying a ramming mission to prevent United Airlines Flight 93 from reaching Washington, D.C.,” an institutional framing that aligns with her long-standing public account and the D.C. Air National Guard’s recollections of that day. The operational logic was brutally simple: an unarmed interceptor still has mass, speed, and a pilot trained to place both with precision. In a hijacking underway, those are weapons of last resort.

Authority, timing, and the communications gap

The ramming plan did not emerge in a vacuum. Even as the air picture fragmented, national command moved toward the hardest call: authorizing the shootdown of hijacked aircraft that refused to comply. Accounts from the day, and later disclosures, place President George W. Bush and Vice President Dick Cheney in a real-time discussion about lethal engagement authority; the 9/11 Commission documented that authorization being conveyed down the chain of command, though late and imperfectly. The Commission and subsequent briefings describe the core problem with stark clarity: by the time shootdown authority reached the air defense sector responsible for the Northeast, United 93 had already crashed in Pennsylvania; the transmission of that order did not reach line pilots in time to shape their tactics in the critical window.

This is the essential tension of 9/11 air defense: policy was converging on lethal force while the tactical edge was already improvising without clear, prompt guidance. Pilots in the cockpit lived inside that latency. If you cannot count on a live missile and cannot wait for a radio message that may not arrive, you plan with what you have—aircraft and intent. That is how ramming becomes not only thinkable but operationally coherent within the cascading delays and unknowns of the morning.

How U.S. air defense got there: doctrine versus the day

Before 9/11, U.S. air defense procedures for hijackings were built around escort, shadowing, and coordination with civil authorities, not the expectation that a domestic airliner would be used as a cruise missile. The well-worn playbook emphasized notification, scramble, and intercept—measures designed to monitor and, if necessary, shepherd a straying aircraft to a safe landing. Intercepts were routine; catastrophic, time-compressed kamikaze scenarios were not. The Commission’s staff work and defense analyses describe this mismatch between peacetime assumptions and wartime reality: chains of authority, interagency calls, and sector relays that worked in exercises could not keep pace with four near-simultaneous hijackings, transponders silenced, and airliners turned into weapons.

Within that context, the D.C. Air National Guard’s decision calculus makes operational sense. Weapon-loading is minutes to tens of minutes; launch now is seconds. A quick-reaction scramble buys the only currency that matters: geometry. Once an interceptor has geometry—meaning position, speed, and angle to influence the target’s flight path—options expand, from aggressive formation cues to kinetic force. With missiles unavailable and engagement authority uncertain, ramming was the final rung on a ladder that had been stripped to its last rail by circumstance.

Flight 93 and the mission that wasn’t needed

United Flight 93 never reached Washington. Its passengers and crew—having learned of the other strikes—charged the cockpit. The airliner crashed near Shanksville, Pennsylvania. By the time shootdown authorization was effectively communicated to the air defense sector, the window for any military intercept had already closed on that flight. For Penney and Sasseville, that meant the ramming plan remained unexecuted. For air defense professionals, it remains a case study in moral clarity under operational uncertainty: they briefed the hardest tactic because it was the only one left that could have worked if they found the aircraft.

The fact that the mission ended without contact has not dimmed its significance. In the years since, Penney’s description of her game plan—and the Guard’s matter-of-fact embrace of it—has shifted public understanding of what “prepared to intercept” meant that morning. It was not airborne theater. It was a premeditated, anatomically specific kill plan shaped by aircraft design and pilot skill.

What professionals take from the “ram mission” today

Three enduring lessons flow from that decision set. First, speed to the fight remains the non-negotiable variable in homeland air defense. Time lost to loading, coordination, or incomplete radar plots is never recovered; the intercept geometry you do not seize now will not be available later. Second, command-and-control latency is lethal. The 9/11 Commission’s timeline of when shootdown authority reached the Northeast Air Defense Sector is a sober warning about the distance between national decisions and cockpit awareness; modern architectures aim to compress that gap, but the hazard is structural, not historical. Third, pilots and controllers will always encounter the edges of doctrine. When they do, their decisions are bounded by physics, training, and intent—not by the neatness of a flowchart. Ramming, in that light, is not aberrant. It is an extension of airmanship into the space where weapons and words cannot reach in time.

If you grew up with Cold War air-defense images—armed alert fighters, clear rules of engagement, controllers vectoring interceptors to tidy merges—the 9/11 record is disquieting. The real world is messier: weapons not yet hung, orders not yet received, targets not yet tracked. And then two pilots in clean F-16s brief aim points no tactics manual ever printed and taxi anyway. That, more than any bureaucratic chart, tells you what the profession values when the clock and the stakes are highest.