Function Fixation: Focusing on the Wrong Thing

Eastern Air Lines Flight 401 took off from New York’s JFK Airport on the evening of December 29, 1972, bound for Miami. The flight was initially uneventful, cruising smoothly toward a midnight arrival in Florida. As the L-1011 TriStar jet began its approach, First Officer Albert Stockstill lowered the landing gear. That’s when the crew noticed something unusual: the green indicator light for the nose landing gear did not illuminate. This tiny light was supposed to confirm that the nose gear was down and locked for landing. Its absence signaled a potential problem – either the nose gear had failed to deploy or the indicator bulb itself had burned out.

Faced with this uncertainty, Captain Bob Loft made a critical decision. Rather than landing without confirmation of the nose gear status, he aborted the landing and requested to enter a holding pattern over the Everglades to troubleshoot the issue. Air traffic control cleared Flight 401 to climb to 2,000 feet and circle back for another approach once ready. The First Officer engaged the autopilot to hold the aircraft at an altitude of 2,000 feet while the crew worked on the problem. This action, intended to free up the crew's mental bandwidth, created the first link in a fatal chain: with the task of flying outsourced to the autopilot, the entire flight deck—Captain Loft, First Officer Stockstill, and Flight Engineer Don Repo, became a single-minded troubleshooting team

Inside the cockpit, all eyes turned to the troublesome light. The crew’s immediate question: was it a landing gear failure or just a faulty indicator light? Flight Engineer Don Repo performed a quick “light test” – essentially a bulb check – and found that the nose gear light still wouldn’t illuminate. This suggested the bulb was indeed burned out or the assembly was faulty. To ensure the gear was down, Repo left his seat and climbed down into the avionics bay below the cockpit (nicknamed the “hell hole”) where a small porthole could be used to visually confirm the nose gear’s position. Meanwhile, Captain Loft and First Officer Stockstill decided to try and replace the light bulb. Stockstill tried removing the indicator assembly, but unfortunately, it jammed in its socket, refusing to then reattach properly.  What began as a simple task – changing a bulb – quickly became a frustrating struggle.

However, unknown to the crew, a new problem was developing. As Captain Loft turned to speak to Repo (before he went down into the electronics bay), he unintentionally pressed against the control yoke. This slight pressure, no more than 20 pounds, was just enough to disengage the autopilot’s altitude hold mode. The autopilot, no longer holding altitude, reverted to a basic flight mode that responded to control inputs, and the slight forward pressure caused the jet to begin a gradual descent. In the dark of night over the Everglades, with no city lights below to provide visual reference, neither of the flight crew in the cockpit at the time noticed as the aircraft’s nose dipped almost imperceptibly and began a very gentle (only a few hundred feet per minute) descent.

For the next few minutes, Flight 401 was quietly losing altitude while the cockpit crew remained engrossed in the problem of the landing gear light. The plane sank 100 feet, then 200, then more. An alarm chime sounded in the cockpit – a tone meant to warn that the aircraft had deviated from its assigned altitude. But the chime came from the engineer’s station (where Repo would usually be sitting; however, he was currently down in the avionics bay). On the cockpit voice recorder, investigators heard the tone sounding – but neither the Captain nor First Officer seemed to react to it. At least four warning signals of the descent were evident: the altimeter reading was slowly decreasing, the subtle downward trend on the vertical speed indicator showed a shallow descent, the change in the autopilot display, and the altitude deviation audio alert. Astonishingly, all went unnoticed by the Captain and First Officer, who were still focused on and wrestling with the stuck light assembly.

Down below, Repo confirmed by sight that the nose gear was in fact down and locked in place. It turned out that the “problem” was nothing more than a faulty indicator, but in the time it took for him to verify the position of the nose wheel visually, the aircraft had lost almost half its altitude. When Repo scrambled back up to the cockpit and the crew refocused on their flight instruments, they were at a dangerously low altitude. First Officer Stockstill, startled, exclaimed, “We did something to the altitude… we’re still at 2,000, right?” to which Captain Loft uttered, “Hey—what’s happening here?”. In that instant, the reality became clear – the plane was no longer at 2,000 feet. But, unfortunately, it was too late.

Seconds later, at 11:42 PM, Flight 401’s left wingtip sliced into the swampy ground. In a left turn, the enormous jetliner slammed into the Everglades at 227 mph. The aircraft broke apart as it skidded through the marsh, leaving a trail of wreckage over 1,600 feet long. The impact and chaos in the darkness were devastating: out of 176 people on board, 101 lost their lives in the crash (including Captain Loft and First Officer Stockstill). 

The crash of Flight 401 swiftly became infamous not only for its human toll but for the almost absurdly trivial cause behind it. When investigators combed through the wreckage and data, they discovered that aside from the burned-out bulb, the $15 million L-1011 aircraft had no mechanical faults at all. The nose gear had been down and locked the entire time – a safe landing could have been made. In other words, the plane crashed because the crew fixated on a minor indication problem and stopped flying the airplane. As one safety expert bluntly summarized, “Fixation on a tiny bulb caused the death of 101 people.”

This accident was not the final consequence of a single error but was the cumulative result of minor deviations… which triggered a sequence of disastrous results.

How could three experienced aviators, including a veteran captain with nearly 30,000 flight hours, allow this to happen? The simple answer: they fell victim to function fixation - focusing so intently on a single issue that one loses situational awareness of the broader environment - a dangerous cognitive trap. The crew of Flight 401 became so preoccupied with diagnosing the landing gear indicator that they ignored multiple warning signs of a far greater danger. As the U.S. National Transportation Safety Board (NTSB) later observed, “this accident was not the final consequence of a single error but was the cumulative result of minor deviations… which triggered a sequence of disastrous results.”

At first glance, troubleshooting a landing gear light might seem straightforward, almost routine. However, small stresses can compound and narrow a person’s focus. Psychologists note that people can still process peripheral information under manageable stress – we maintain a mental “radar” for things unrelated to our main task. However, as stress and time pressure increase, our field of attention can shrink dramatically. We experience what researchers call cognitive tunneling, where one task consumes most of our mental bandwidth at the expense of all others. 

In the cockpit of Flight 401, several human factors combined to create a classic case of tunnel vision. The failure of the indicator light set off concern about the landing gear – a legitimate safety issue – but it was also a false alarm. The frustration of the jammed light assembly and the crew’s inability to quickly resolve the problem elevated their stress. With each passing minute, the pressure grew as the crew knew the plane couldn’t land until this issue was solved. This moderate stress was enough to induce a tunnel-vision focus on the light. As one analysis noted, the captain and first officer likely became so absorbed in trying to unjam and replace the bulb that “all of their attention was given to this one small problem, at the expense of flying the aircraft”.

Compounding this was the darkness of the Everglades night and the absence of external visual cues, further hiding other problems from the crew. When the aircraft reached its holding pattern at 2000 feet, engaging the autopilot created a false sense of security. The crew offloaded their primary responsibility—flying the plane—to a system they trusted implicitly. This dulled their vigilance and made them less likely to monitor the aircraft's altitude and attitude, a well-documented risk in any highly automated environment. The autopilot was working exactly as designed, but the human-machine team had broken down because the humans stopped supervising their flying aid. When a hint of the true problem (the slow loss of altitude) pierced their consciousness, it was too late to recover. The tragic irony is that the real crisis was entirely self-induced – the plane was working fine; the humans failed. As the investigation concluded, the primary cause was pilot error and loss of situational awareness. In essence, the Flight 401 crew solved the wrong problem: they technically managed to figure out the light (it was indeed burned out, as suspected) – but in doing so, they abandoned their primary duty: to fly the aircraft safely.

It’s tempting to view the mistakes of Flight 401’s crew as a uniquely aviation-related problem, but the cognitive trap they fell into is by no means limited to the world of flying. Leaders in business and organizations face similar risks of tunnel vision. Under pressure, it’s too common for a leader or team to become fixated on one goal, metric, or crisis, to the detriment of other critical priorities. In the corporate world, this kind of function fixation might manifest as an obsessive focus on hitting a quarterly sales target while ignoring signs of a brewing ethical scandal. Or it could be a project team so zeroed in on delivering a product feature that they miss a fundamental shift in customer needs or a new competitor’s threat. Just as in a cockpit, high-stakes and rapidly evolving situations can overwhelm a leader’s bandwidth, leading to a kind of organizational “altitude loss” that goes unchecked until it’s too late.

To avoid this fate, leaders need to cultivate habits and systems that counteract function fixation:

• In aviation, there is a golden rule in emergencies: aviate, navigate, communicate - in that order - i.e. fly the plane before anything else. For leaders, the equivalent is to always keep the core mission in view. No matter what urgent issue flares up, ensure someone is minding the fundamental operations. This requires the ability to delegate and prioritize workload.  Upon encountering the problem, the captain should have immediately and explicitly delegated tasks: "You have the aircraft and the radios. I will investigate the light with the engineer." Captain Loft, however, allowed the entire team's workload to converge on a single, non-critical task, and Eastern 401’s crew effectively all stopped “flying” to fix the light – a mistake leaders should avoid by always maintaining a grasp on the primary objectives and health of the enterprise. In addition, this means leaders should empower their team to monitor different “gauges” in the organization. Encourage direct reports or peers to voice concerns and report anomalies in their areas. Just as a co-pilot might call out “altitude” if the captain misses it, a good team culture allows for constructive alerts. As a leader, ask yourself: “Do I have people around me who will tell me when something’s going wrong outside my immediate focus?” If not, create that environment.
• During crunch times – be it a crisis response, a major deal closing, or any high-stakes project – deliberately step back to scan the broader landscape. Encourage your team to do the same. Simple practices like periodic check-ins to remind each other of the primary objective, brief pause-and-review meetings, or rotating roles can help jolt a group from a narrowing mindset. In the Flight 401 scenario, a simple altitude check every minute could have broken the spell. As a leader, using techniques like team debriefs after a project, careful reviews of potential risks, or having someone play the role of a skeptic to challenge the plan can help uncover problems that might have been missed.
• Part of a leader’s job is to triage: to discern when a small issue is truly mission-critical or when it’s a minor glitch that can be deferred, delegated, or even deleted altogether. The Flight 401 crew treated the inoperative light as if it were an immediate life-or-death issue, when in fact there were other methods to determine if the landing gear was down. In business, leaders sometimes pour disproportionate time and resources into minor issues (think about the last time you spent a day-long meeting ‘wordsmithing’ a mission statement), while a larger risk goes unmanaged. Develop your situational awareness to know what’s truly essential in the moment. If you find yourself or your team fixated on a detail, ask: “Is this the landing gear or just the light? What’s the bigger picture right now?”
• The lessons drawn from the tragedy of Flight 401 forced airlines to embrace a culture of openness and continuous learning (through Crew Resource Management and other safety programs) to ensure mistakes are caught early and learned from. Modern leaders should do the same. Encourage everyone in your team or organization to report near-misses or concerns without fear. Treat warnings and bad news not as distractions or threats, but as valuable signals that keep you informed. In essence, keep your metaphorical altimeter where you can see it. A culture of transparency and agility will help prevent groupthink or fixation on the wrong priorities.

One powerful framework that aligns well with these traits is Adaptive Leadership. Introduced by Harvard Business School’s Dr. Ronald Heifetz, adaptive leadership is all about embracing change and uncertainty proactively. It’s a leadership mindset that values flexibility, learning, and quick adjustment over rigid plans or fixed routines. In the fast-changing “flight conditions” of today’s business environment, this approach can keep leaders from getting stuck in one mode of thinking.

Remain flexible, make real-time adjustments, and navigate uncertainty with confidence

Adaptive leadership is “the ability to remain flexible, make real-time adjustments, and navigate uncertainty with confidence.” Adaptive leaders recognize when they are facing a new or unprecedented challenge – what Heifetz calls an “adaptive challenge” – that can’t be solved with business-as-usual tactics. Instead of becoming fixated on their original plan or a single aspect of the problem, they pivot and experiment with new solutions. They encourage feedback and diverse perspectives, much like a good pilot scans all instruments and listens to their crew, rather than just staring at one gauge.

Several key traits define adaptive leaders and show why they are less prone to functional fixation:

• Adaptive leaders constantly scan their environment: they anticipate disruption rather than merely react to it. This means they’re less likely to be blindsided by a gradual change (like Flight 401’s descent) because they make it a habit to look around. In practice, a CEO with an adaptive mindset might regularly seek input from different departments, monitor industry trends, and consider worst-case scenarios, ensuring no single concern completely absorbs their attention at the expense of others.
• Instead of holding onto a fixed idea of how things must be done, adaptive leaders stay open to new ideas and information. They treat failures and alarms as learning opportunities rather than annoyances. This mindset of probing and updating is critical in business: if data or colleagues are signaling a problem, adaptive leaders pause, reassess, and reprioritize instead of plowing ahead on autopilot based on their initial supposition.
• It may sound paradoxical, but the best adaptive leaders combine flexibility in thinking with decisiveness in action. They can rapidly switch gears when needed – for example, abandoning a cherished project that isn’t panning out – yet they do so in a controlled, deliberate manner. They don’t get paralyzed by unsolvable problems, nor do they stubbornly barrel forward, ignoring signs of trouble. This balance would serve a cockpit crew well: the team must be willing to change plans immediately rather than focusing on the wrong issue when new information emerges. Adaptive leadership trains one to make those real-time adjustments; in essence, it’s the leadership embodiment of “course-correcting” to avoid danger.
• Another hallmark of adaptive leadership is mobilizing your team. Adaptive leaders know they can’t have their eyes on everything, so they cultivate strong teams and delegate authority. They encourage people at all levels to take initiative and share information. By doing so, they create a network of awareness within the organization. This decentralization of vigilance means it’s less likely that everyone will miss the same critical signal. It builds redundancy in the best sense: if one person doesn’t catch it, someone else will. A team or organization led in this way is far more resilient to shocks – it won’t suffer the equivalent of all pilots fixating on one broken light.

Modern leaders operate in environments of turbulence and rapid change – our “cockpits” are often full of master warning lights, some crucial and some merely distracting. The danger of tunnel vision is that we might obsess over one indicator (a minor technical glitch, a single customer complaint, a failing internal target, or even an outdated assumption we’ve latched onto) and miss a crisis unfolding elsewhere. To counter this, make it a habit to regularly “look out the window” and survey the landscape: What else is happening? What are we missing? Create a team culture where someone can tap you on the shoulder and say, “Captain, check our altitude.”

No matter what minor issue demands attention, never neglect the primary objective.

Perhaps the most important takeaway is a simple mantra pilots use: “Fly the plane.” No matter what minor issue demands attention, never neglect the primary objective. In leadership terms: keep your mission and people front and center. Address problems in stride, but don’t let them consume you to the point that you abandon your core responsibilities. If the crew of Flight 401 had remembered to fly the plane first, the outcome would have been very different. In the same way, if you, as a leader, ensure that someone is always minding the essential processes (even if you’re troubleshooting a specific issue), you’ll prevent small glitches from spiraling into catastrophe.