In 1997, a team of engineers hid an entire flight simulator inside the code of Microsoft Excel as an unlisted “Easter egg” — and to this day, it remains one of the most sophisticated pieces of hidden software ever secretly shipped to millions of corporate computers

In 1997, a team of engineers hid an entire flight simulator inside the code of Microsoft Excel as an unlisted “Easter egg” — and to this day, it remains one of the most sophisticated pieces of hidden software ever secretly shipped to millions of corporate computers Featured Image

Somewhere on the hard drives of millions of corporate computers in the late 1990s, buried inside a piece of software almost universally used for tax returns, sales forecasts, and quarterly reports, there was a small 3D world.

You could not reach it through any menu. You could not find any reference to it in the help files. It did not appear in any official documentation. To get to it, you had to perform a very specific and deeply strange sequence of actions inside Microsoft Excel 97, including typing a cell reference, pressing Tab, and then Ctrl+Shift-clicking on a particular toolbar icon.

If you did all of that correctly, the spreadsheet would vanish. In its place would appear a purple landscape, viewed from above, with the user’s mouse controlling a slow, drifting flight across the terrain. Eventually, if you flew far enough, you would come across a black monolith floating in the void, with the names of the Excel development team scrolling slowly across its face.

The flight simulator hidden in Microsoft Excel 97 is one of the most famous Easter eggs in software history. And the story of how it got there, and why it disappeared, tells you something genuinely interesting about a vanished era of computing.

What it actually was

It’s worth being precise about what the egg was, because the popular name has drifted from the reality.

People call it the “Excel 97 flight simulator.” It is not actually a flight simulator in the traditional sense. There are no gauges, no cockpit, no airplane controls, no planes. What it is, more accurately, is a small 3D rendered environment — a “magic carpet” view across a textured landscape — that ends with a Kubrick-style monolith displaying the developers’ names. The Rezmason project, a faithful web-based preservation of the original, describes it as exactly that: a 3D credits sequence dressed up as a flying demo.

What made it genuinely impressive was not the gameplay (there isn’t really any) but the engineering. In 1996, when the egg was built, real-time 3D rendering inside a productivity application was not standard. Excel 97 was a spreadsheet program. It was not supposed to have its own 3D engine. Yet the developers had quietly built one in, using early versions of Microsoft’s DirectDraw graphics technology, and shipped it on millions of business PCs without anyone outside the team knowing it was there.

The culture that produced it

The Excel flight egg didn’t happen in isolation. It was the product of a very specific moment in software culture — what one might call the golden age of Microsoft Easter eggs.

Throughout the 1990s, Microsoft developers were locked in an informal arms race over who could hide the most elaborate secret in the most respectable-looking software. Word had a hidden pinball game. Access had a hidden racing game. Excel 95 had a Doom-clone first-person shooter called the “Hall of Tortured Souls.” Excel 2000 had a hidden first-person shooter called Dev Hunter. Windows itself shipped with a series of hidden 3D environments listing the operating system’s developers.

The reason this happened, as several of the original developers later explained, was extremely human. Big software projects in the 1990s required enormous compile times. Engineers would sit around for hours waiting for builds to finish, with nothing to do. They juggled. They learned card tricks. They wrote secret games and hid them inside the software they were paid to ship.

Easter eggs were also one of the few ways developers could put their own names into a product. Microsoft, like most large software companies, didn’t credit individual programmers in shipping products. Hiding your name inside the software — or your team’s name, scrolling across a monolith — was a way to leave a small, defiant signature.

The thing nobody outside the team knew

The detail that makes the Excel flight egg genuinely remarkable is the scale at which it shipped. It wasn’t a curiosity in a single build. It went out with every copy of Excel 97 ever sold. That is millions of installations — corporate accounting departments, government agencies, banks, schools, every Microsoft Office customer on Earth.

For years, copies of Excel 97 were sitting on company hard drives all over the world with a secret 3D flying world hidden inside them. Most users never knew. The IT staff at Fortune 500 companies almost certainly never knew. The auditors who built financial models in Excel for hours every day, almost without exception, had no idea that the same software contained a hidden universe accessible by a particular keyboard combination.

That gap — between what the software appeared to be and what it actually contained — is what makes Easter eggs of this era so culturally interesting. The shipping copy of a spreadsheet program had more layers than its users could imagine.

Why it ended

The era of Microsoft Easter eggs died abruptly in the early 2000s, killed by a single corporate initiative.

In 2002, in response to a series of security crises, Microsoft launched what it called its Trustworthy Computing initiative. The basic premise was that all undocumented, unreviewed, unaudited code in Microsoft products had to go. Easter eggs — by definition undocumented, by design unreviewed — were an obvious casualty. They were also, in a post-9/11 security environment increasingly concerned with software supply-chain risks, no longer the harmless fun they had once been. An undocumented 3D engine running silently inside Excel was, from a security auditor’s perspective, an unaccountable mystery.

By the time Office 2003 shipped, the Easter eggs were gone. Excel returned to being only a spreadsheet. The hidden 3D worlds were stripped out, the secret games removed, the scrolling developer credits retired.

The Excel 97 flight is still preserved today, faithfully recreated in browser form, as a kind of museum exhibit of a more playful era of software development. You can fly across the purple landscape, find the monolith, and read the names of the developers who, twenty-nine years ago, decided that the world’s most boring program deserved one small hidden secret.

It is still, by some distance, the most impressive thing ever to be hidden inside a spreadsheet.

Subscribe to our newsletter!

Our latest tutorials delivered straight to your inbox

Make Tech Easier Editorial Team Avatar

Read next

Every time you book a flight or check a hotel room, your request is routed through a green-screen mainframe system that traces back to the 1960s — and the entire multi-billion-dollar travel industry still relies on this ancient digital foundation because replacing it would be enormously expensive, dangerous, and slow
A 65-year-old programming language called COBOL still quietly processes over $3 trillion in banking transactions every single day — and because the original engineers are rapidly retiring, banks are scrambling to pay younger developers fortunes just to keep the ancient infrastructure from breaking
Stanford scientists just built a room-temperature quantum device that uses “twisted light” to connect electrons and photons — an long-sought breakthrough that could finally take quantum computing out of extreme sub-zero labs and into everyday devices
When Microsoft was developing Windows 95, developers discovered that SimCity had a severe memory bug that caused it to crash on the new operating system—but instead of forcing the game studio to fix it, Microsoft engineers actually rewrote the core Windows 95 source code to detect if SimCity was running and safely allocate memory for it.
The first computer bug was a literal moth, pulled out of a relay in a Harvard computer in 1947 and taped into the logbook with the note “first actual case of bug being found” — and the logbook is still preserved at the Smithsonian
Latest Windows Update Problems and How to Fix Them
I Replaced Claude Code With Codex, And I Should Have Done It Sooner
OneCommander Is a Great File Explorer Alternative for Power Users