New York --:--
Magazine about Earth, Science and Energy
Mobility

A contaminated ham omelette loaded in Anchorage sickened 196 passengers on a transatlantic jumbo jet, and the two pilots who skipped it kept the cockpit healthy so the airliner landed safely

By SEP 21, 2026 5:50 PM 5 MIN READ
Two separate cockpit meal trays in an aircraft galley illustrating the cockpit meal rule, contaminated ham omelette Photo: David Reamer | Histories of Alaska
Stay in the loopFollow us on Google News

The breakfast tray looked the same in seat after seat.

Ham and omelette, prepared in an airline catering kitchen in Anchorage and loaded during the stopover.

Up front, the captain and first officer passed on it and asked for steak.

Their body clocks said dinner, not breakfast. They were still running on Alaska time.

That accident of appetite is why, on many commercial flights today, the two people flying the plane eat different meals from each other. How did one skipped tray rewrite procedure?

What a body clock did that policy had not yet done

A Boeing 747 was flying from Tokyo to Paris with service stops in Anchorage and Copenhagen, carrying 344 passengers and 20 crew. The flight existed to carry fare-paying passengers between two continents, and keeping its cockpit functional was the single condition everything else depended on. That condition nearly failed.

Investigators found that 196 passengers and one steward developed nausea, vomiting, abdominal cramps and diarrhea shortly after a ham and omelette breakfast was served. It was the largest known case of foodborne illness in aviation history at the time. The source was traced to the ham.

A cook at an Anchorage catering firm had reported for work with two staph lesions on his right hand, covered them with bandages and said nothing to his supervisors. His employer did not check his health status before he handled food.

The detail that made the incident historic was not the outbreak but what did not happen. The pilot and first officer had eaten none of the contaminated omelettes, and with their biological clocks on Alaska rather than European time, they had chosen steak dinners instead. The aircraft landed safely at its scheduled stop in Copenhagen, and everyone aboard eventually recovered.

The omelette that heat could not fix

Before the meal was served, the ham and omelette had been held at room temperature for about 14 hours and then at 50°F for roughly another 14 hours. Preformed toxin was detected in the leftover food, which is why onset was so fast: illness began about an hour after the trays went out.

Staphylococcal toxin is heat stable once formed, so it cannot be cooked out of food that has already been contaminated. Warming the omelette in the galley did nothing to the toxin already present in the ham. Every tray from that batch carried it.

On the ground in Copenhagen the scene was chaotic. Stretchers filled an airport lounge, and overwhelmed doctors worked against a language barrier. The only trays that carried nothing harmful were the two ordered off menu by the crew up front.

One sentence in a medical journal that changed every cockpit

The investigation was led by a United States Public Health Service epidemiologist working with the Alaska health department, alongside colleagues in Copenhagen and Atlanta. Stool and vomitus from ill passengers, leftover food and the cook’s finger lesions all grew Staphylococcus aureus of identical phage types and antibiotic sensitivities. The attack rate was 86 percent among passengers who ate ham handled by that cook and zero among those who ate ham handled only by another preparer.

The paper recommended that “cockpit crew members should eat different meals prepared by different cooks” so that one foodborne illness could not incapacitate an entire flight crew. That single line of advice outlived the outbreak itself.

No regulator mandates the split cockpit meal directly. The FAA had no rule requiring it then and still has none, which is why the practice sits in individual airlines’ operating procedures rather than in law. One carrier mandated separate meals prepared by different cooks, and others followed. That voluntary adoption is the origin of what crews now call the cockpit meal rule.

The 1982 flight that showed the rule was not optional

Seven years later the industry got a second demonstration. Eight of the ten crew on a DC-8 arriving in Boston from Lisbon fell ill with cramps and stomach pains about an hour out, according to UPI’s August 1982 report, and were taken by ambulance to hospitals after landing. Officials suspected tapioca pudding. The copilot, who had not eaten the dessert, did not become sick.

The philosophy the split meal practice sits inside is redundancy in design: no single failure should bring down an aircraft. Every critical system on a modern airliner has a backup, including two pilots. What both incidents exposed is that two pilots sharing one catering batch are not independent, and a shared meal tray was the link nobody had thought to cut.

What that winter flight left behind in Copenhagen and everywhere else

Airline catering today runs under far tighter hygiene auditing and cold chain control than the kitchen that assembled those trays, as the Lancet investigation made plain. The split meal survives anyway, because it costs almost nothing and closes a failure path that food safety rules alone cannot fully seal. It is standard practice on many carriers rather than a universal legal requirement.

That same logic of redundancy shows up wherever one shared weak point can stop everything, from a water balanced cliff railway on a Devon hillside to ice road operations that hang on one seasonal route. Engineers call it a single point of failure, and it applies as cleanly at 35,000 feet as it does on the ground.

Next time a flight attendant offers you beef or fish, then asks the flight deck the same question and writes down two different answers, the reason traces back to an Anchorage kitchen half a century ago and to two pilots whose appetites were still on the wrong clock.

Read the whole thing?

Get the week's signal, not the noise

Our sharpest reporting on energy, climate and nature — free, once a week.

Share this article
Hugo_writer
Hugo RojasTech Editor & Advisor
Hugo is an engineer with strong technical expertise and deep knowledge of the space industry. Multilingual from an early age, his writing combines technical clarity with a strong interest in science and energy.