It is, perhaps, the most universal of human failings: falling asleep when you should not. We have all done it — during lectures, during meetings, during films we swore we wanted to watch. But most of us have not done it while flying an aircraft at 8,000 feet. Some pilots have. And the stories — once you know everyone survived — are among the most delightfully absurd episodes in all of aviation. They involve autopilots that work too well, fuel gauges that beg to be noticed, and air traffic controllers who spend desperate minutes trying to wake up someone who is dreaming his way across an ocean. This is the story of what happens when pilots nod off — and the aircraft, unaware that nobody is minding the shop, simply keeps flying.

The Gulf of Mexico Wake-Up Call

On February 17, 1994, a pilot departed Springfield, Kentucky, in a Piper PA-34 Seneca bound for Crossville, Tennessee — a straightforward flight of perhaps an hour. He set the autopilot, trimmed the aircraft, and settled in for the cruise. At some point — he later could not say exactly when — he fell asleep. The autopilot, being a machine with no opinions about the situation, continued flying the aircraft on its last heading: due south. The Seneca passed over Crossville without stopping. It passed over Chattanooga. It crossed the entire state of Alabama. It flew over the Florida panhandle and out over the Gulf of Mexico.

The pilot woke up around 11:30 in the morning. Below him was nothing but open water. Behind him was approximately 500 miles of airspace he had no memory of crossing. The fuel gauges were nearly empty. He was 210 miles south of Panama City, Florida, with barely enough fuel to turn around. He did not make it to land. The engines quit over the Gulf and the Seneca ditched in the water roughly 70 nautical miles west of St. Petersburg. The pilot was rescued uninjured. The aircraft sank and was never recovered. The NTSB report is a model of understatement: the probable cause was fuel exhaustion due to the pilot falling asleep and overflying the destination.

The Navy Pilot With Four Gallons Left

In one of the most quietly terrifying stories in military aviation folklore, a US Navy A-4 Skyhawk pilot on a cross-country training flight engaged the autopilot as night fell over Louisiana and promptly fell asleep. The A-4, faithful to its last instruction, continued flying due east. The jet crossed Louisiana. It crossed the Florida panhandle. It overflew Jacksonville Naval Air Station — the pilot’s actual destination — without a murmur. It continued out over the Atlantic Ocean, heading for Africa at 400 knots. Fifty miles offshore, an increasingly frantic air traffic controller finally managed to wake the pilot by radio. The Skyhawk turned around and landed at Jacksonville. When the squadron commanding officer measured the fuel remaining in the tanks, he found four gallons. Not four hundred. Four. At the A-4’s fuel consumption rate, four gallons represented approximately two minutes of flight time. Had the controller taken sixty seconds longer to establish contact, the pilot would have been swimming in the Atlantic.

The 737 That Flew Over Its Own Airport

It is one thing for a solo pilot in a Piper to nod off. It is quite another for both pilots of a commercial airliner to fall asleep simultaneously — but it has happened more than once. In August 2022, the pilots of Ethiopian Airlines Flight ET-343, a Boeing 737, were cruising at 37,000 feet on approach to Addis Ababa when both fell asleep. Air traffic control tried repeatedly to reach the aircraft. No response. The 737 flew directly over Bole International Airport, still at cruise altitude, and continued south. What saved the passengers was the autopilot itself. The aircraft had been cleared to descend, but with no pilot input, it remained at 37,000 feet. When it overflew the runway waypoint and the autopilot disconnected — as it is designed to do at the end of the programmed route — the disconnect chime woke both pilots. They rubbed their eyes, realised they were 25 miles past the airport at seven miles high, and executed a sheepish return for landing. Both pilots were suspended. The airline declined to comment publicly. The passengers, reportedly, were unaware anything had happened.

Northwest Flight 188: The One That Made the News

The most famous falling-asleep incident — though the pilots have always denied they were asleep — occurred on October 21, 2009. Northwest Airlines Flight 188, an Airbus A320 carrying 144 passengers from San Diego to Minneapolis, overflew its destination by 150 miles before the pilots re-established contact with air traffic control. For 78 minutes, the aircraft was completely out of radio contact. Fighter jets were scrambled. NORAD was alerted. Authorities feared a hijacking. The aircraft flew serenely over Minneapolis at 37,000 feet, crossed into Wisconsin, and only turned around when the cabin crew sent a message asking what was happening. The pilots — Captain Timothy Cheney and First Officer Richard Cole — told investigators they had been engrossed in a discussion about airline scheduling software on their personal laptops, which were open in the cockpit. They said they lost track of time. They said they were not asleep. The NTSB found their explanation difficult to reconcile with 78 minutes of silence and concluded that the most likely explanation was that both had fallen asleep. Both pilots had their licences revoked.

Why It Happens — and Why It Keeps Happening

Pilot fatigue is not a joke, even when the stories are funny. The International Civil Aviation Organization estimates that fatigue is a contributing factor in 15 to 20 percent of aviation incidents. Modern cockpits are warm, quiet, pressurised, and dimly lit during cruise — conditions that are, from a physiological standpoint, almost perfectly designed to induce sleep. Commercial pilots fly irregular schedules, cross multiple time zones, and are sometimes required to operate during their circadian low points — the hours between 2:00 and 6:00 in the morning when the human body most wants to sleep. General aviation pilots often fly long cross-country legs alone, with no one to talk to and nothing to do but watch the autopilot hold altitude and heading. Some airlines have adopted “controlled rest” policies that allow one pilot to nap for up to 45 minutes during cruise while the other remains alert. The logic is pragmatic: if pilots are going to fall asleep anyway, it is better to manage it than to pretend it does not happen. But for solo pilots, there is no controlled rest. There is only the autopilot, the hum of the engine, and the hope that the fuel gauges will catch your attention before the Gulf of Mexico does. Sources: General Aviation News, NTSB accident reports, Simple Flying, The Aviation Geek Club