Don Bateman, the Honeywell Engineer Who Ended the CFIT Epidemic, and the Terrain Awareness System That Turned the Mountain Into Something You Could See Before You Hit It

Controlled Flight Into Terrain was once the dominant cause of fatal airline accidents - not mechanical failure, not weather, but fully airworthy aircraft flown by competent crews directly into the ground. The engineer who ended that epidemic was Don Bateman, and the system he built is almost certainly somewhere in your panel right now.

What Made CFIT So Deadly

In the 1960s and 1970s, CFIT accounted for roughly half of all fatal airline accidents worldwide. Studies published by Boeing and the International Air Transport Association (IATA) documented more than 2,000 commercial passenger fatalities per year attributable to controlled flight into terrain at the peak of the problem.

The common thread across these accidents was not pilot incompetence. The crew was heads-down on instruments, flying a correct approach, with no reason to suspect terrain between their current position and the runway. The ground simply wasn’t visible in the cockpit picture.

Who Was Don Bateman

Don Bateman was an electrical engineer at Sundstrand Data Control in Redmond, Washington in the late 1960s. He became consumed by the CFIT problem - collecting every accident report he could find, building a database of what aircraft were doing in the moments before impact, and searching for patterns.

What he found consistently: crew attention was saturated, terrain wasn’t on any chart in the scan, and existing cockpit warnings were either absent or came too late. In most of those cockpits, there were no warning systems at all.

How the Original GPWS Worked - and Where It Failed

Bateman developed the first Ground Proximity Warning System (GPWS). The FAA mandated it for large commercial aircraft in 1975, and it immediately reduced CFIT fatalities in equipped aircraft.

The original GPWS used existing aircraft sensors to detect specific dangerous situations, organized into modes. Mode 1 flagged excessive descent rate near the ground. Mode 2 detected excessive terrain closure rate. Mode 3 caught altitude loss after takeoff or go-around. Mode 4 warned of unsafe terrain clearance with gear or flaps not in landing configuration. Mode 5 flagged glideslope deviation. The system responded with PULL UP or TERRAIN TERRAIN.

The fundamental problem: the system was entirely reactive. It had no terrain database, no map, no ability to look ahead. It was a smart altimeter wired to a loud speaker.

This created two persistent failure modes. False alerts triggered when sensor data looked threatening but terrain wasn’t actually a problem. Late alerts arrived when terrain was genuinely dangerous but left the crew fewer than ten seconds to respond. The classic failure scenario - steady flight toward a rising ridge with no descent, no glideslope deviation, correct configuration - generated no GPWS warning until impact was nearly unavoidable.

What “Enhanced” Actually Means in EGPWS

The Enhanced Ground Proximity Warning System (EGPWS) solved the architectural problem by adding a worldwide digital terrain database inside the box. The system no longer asked only “how close is the ground right now?” It asked: if you continue on this trajectory, does your flight path intersect the terrain database?

That is a fundamentally different question. The system now knew the elevation of the ridge ahead. It knew the far wall of the valley. It could project the aircraft’s path forward in time and space.

The EGPWS entered service in the mid-1990s. Honeywell, which had acquired Sundstrand, began equipping commercial aircraft. Regulatory mandates extended the requirement progressively to smaller aircraft categories over the following decade.

Boeing’s Statistical Summary of Commercial Jet Airplane Accidents documents what followed: in the decade after widespread EGPWS adoption, the CFIT rate in equipped aircraft fell by roughly 80 percent. The technology did exactly what it was designed to do.

Why the EGPWS Response Protocol Is Non-Negotiable

Early in the EGPWS deployment, airlines discovered a training problem. Some crews hesitated before executing an aggressive pull-up in response to a TERRAIN warning, because years of original GPWS experience had conditioned them to evaluate alerts before acting. The original system’s false alert rate had taught them skepticism.

The EGPWS largely eliminated ambiguous warnings by replacing sensor inference with actual terrain data. But learned hesitation from the original system didn’t disappear overnight.

The current guidance is unambiguous: when EGPWS or TAWS generates a warning, the response is immediate. No evaluation. The terrain database has already done the evaluation. It is not telling you there might be a threat. It is telling you there is one.

What TAWS Means for GA Pilots

TAWS - Terrain Awareness and Warning System - is the FAA’s regulatory term covering both the original GPWS modes and the enhanced terrain database capability. The FAA requires TAWS for turbine-powered airplanes and large piston aircraft under Part 135. There is no universal mandate for Part 91 general aviation aircraft, but the technology has spread widely through integrated avionics suites.

If you’re flying a Garmin G1000-equipped Cessna or Piper, the amber and red terrain overlays on your moving map are drawing from the same fundamental concept Bateman built, miniaturized and embedded in the avionics stack.

The colors on that display have specific meanings most pilots underestimate. Amber terrain indicates ground within 1,000 feet below your current altitude. Red terrain means terrain is within your current altitude. Both thresholds are computed against barometric altitude - which means they inherit any error in your altimeter setting. Flying in non-standard pressure conditions with an incorrect altimeter setting, the terrain display is off by exactly the same amount.

The terrain database also has resolution limits. In mountainous terrain across the lower 48 states, resolution is good. In remote or internationally sparse areas, the data degrades, and the system doesn’t always indicate when it’s working from lower-quality data. Smooth-looking displayed terrain in a data-sparse area can conceal local ridges the database missed.

Synthetic Vision: Terrain as Continuous Information

A newer generation of terrain awareness goes beyond alerting. Synthetic vision technology - found in the Garmin G3000 and G5000 suites and Avidyne’s Entegra system - renders a three-dimensional terrain picture directly on the primary flight display, continuous and uninterrupted.

Flying toward a ridge in IMC or at night, you see the ridge on the PFD as a brown feature rising above the horizon line. The valley is visible. The peak is visible. Terrain becomes part of the instrument scan rather than a surprise event.

Garmin has reported in research presentations that pilots flying with synthetic vision primary flight displays showed measurably different response patterns in simulator scenarios involving unexpected terrain - the terrain registered as part of normal scan rather than triggering a reactive crisis response.

Synthetic vision and TAWS alerts are complementary, not redundant. Synthetic vision maintains continuous situational awareness. TAWS catches the case where the display didn’t register, the scan broke down, the crew was task-saturated, or the terrain data was outside the rendering window.

Keeping Your Terrain Data Current

The TAWS box that came with a used aircraft may be running a terrain database that is several years old. Major topographic features aren’t changing, but airport obstacle data does. That gap matters when flying instrument approaches into unfamiliar fields in mountainous terrain.

Terrain database updates matter. Know what database version your system is running, and know when it was last updated.

Why This Matters Now

Bateman’s core argument - made against significant industry resistance - was that crews were often flying approaches correctly and still hitting terrain, and that a warning system could save them in the cases where everything nominal still resulted in an accident. The prevailing industry view had been that correct procedure was sufficient. The accident record proved it wasn’t.

The numbers vindicated him. That is a rare and clean result in aviation safety engineering.

Key Takeaways

CFIT killed more than 2,000 commercial passengers per year at its peak; EGPWS reduced the rate in equipped aircraft by roughly 80 percent after widespread adoption in the mid-1990s
The critical difference between original GPWS and EGPWS is a worldwide terrain database - the enhanced system looks ahead, not just down
Amber terrain on your TAWS display means within 1,000 feet below you; red means within your current altitude - both thresholds depend on a correct altimeter setting
Terrain databases have resolution limits; smooth displayed terrain in remote areas does not guarantee smooth actual topography
When TAWS generates a TERRAIN warning, the response is immediate - the database has already evaluated the threat; your job is to execute the escape maneuver