The Ground Proximity Warning System, the Engineer at Sundstrand Who Refused to Let CFIT Keep Killing Airliners, and the Forward-Looking Terrain Alert That Finally Closed the Last Gap

How one engineer's decades-long campaign turned CFIT from aviation's leading killer into a rare event in modern commercial operations.

Aviation Technology Analyst

Controlled Flight Into Terrain - CFIT - was responsible for roughly one in three fatal airline accidents through the 1960s. A single engineer’s work, years of regulatory persistence, and two catastrophic accidents ultimately produced the cockpit technology that brought that statistic close to zero in modern commercial aviation.

What Is CFIT and Why Did It Dominate Aviation Fatalities for 15 Years?

CFIT describes an accident in which a fully functional aircraft, flown by a competent crew following standard procedures, strikes the ground or an obstacle with no loss of aircraft control preceding the impact. The aircraft was doing what it was supposed to do. The terrain was simply there.

ICAO estimated that CFIT accounted for roughly a third of all fatal airline accidents through the 1960s. These accidents were not caused by reckless flying. They were caused by the absence of any independent cockpit system monitoring the relationship between the aircraft’s flight path and the terrain below and ahead.

The accident record from that era is extensive. Allegheny Airlines hit a ridge in Pennsylvania in 1959. A Scandinavian Airlines DC-8 struck a mountain in New Jersey in 1960. A Mohawk Airlines flight hit Roundtop Mountain in New York in 1963. United Air Lines hit a ridge near Lake Tahoe in 1964. Each accident left investigators with a data record showing a normal flight right up until it wasn’t.

Don Bateman and the Data-Driven Case for a Warning System

In the early 1970s, an engineer at Sundstrand Data Control in Redmond, Washington began studying the CFIT problem systematically. Don Bateman had access to the accident data his employer’s flight data recorders had captured - a dataset most engineers in the industry never saw.

Bateman was not analyzing pilot error in the narrative sense. He was examining instrument readings in the moments before impact. What he found was that CFIT accidents shared predictable warning signatures in the flight data: excessive sink rates relative to radio altitude, landing gear retracted at altitudes where gear should be extended, flaps not in a landing configuration near the ground, descent below an ILS glide slope, and altitude loss after takeoff or during a go-around.

The concept that followed was precise: monitor those parameters continuously, define thresholds that indicated dangerous conditions, and generate an immediate aural and visual alert when any threshold was crossed.

How GPWS Works: The Seven Modes That Changed Everything

The Ground Proximity Warning System (GPWS) Bateman developed monitored flight parameters in real time and triggered alerts when those parameters entered defined danger zones. The alert language was deliberately imperative: “SINK RATE.” “PULL UP.” “TOO LOW TERRAIN.” Not advisory. Commands.

The original system operated across seven modes:

  • Mode 1: Excessive descent rate
  • Mode 2: Excessive terrain closure rate, based on radio altimeter readings
  • Mode 3: Altitude loss after takeoff or a go-around
  • Mode 4: Unsafe terrain clearance with gear up or flaps not in landing configuration
  • Mode 5: Descent below the ILS glide slope
  • Mode 6: Altitude callouts on approach
  • Mode 7 (added later): Windshear detection

Why Was the Aviation Industry Slow to Adopt GPWS?

The aviation industry in the early 1970s had legitimate technical objections. Nuisance alerts - warnings that fire when no actual danger exists - erode crew response to genuine alerts over time. That is a real human factors problem, not reflexive resistance to change.

There was also the standard cost-benefit calculation applied to any new required equipment: weight, certification path, cost, and statistical proof of benefit. And there was institutional reluctance to mandate something that implicitly acknowledged existing procedures were inadequate.

Bateman spent years building the response to those objections. He demonstrated the system, presented accident data to the FAA, and appeared at ICAO meetings. The system was technically mature, the alerts were reliable, and the CFIT statistics answered the cost-and-complexity question directly. He kept showing up.

TWA Flight 514: The Accident That Forced the FAA’s Hand

On December 1, 1974, TWA Flight 514 was conducting a VOR approach to Runway 12 at Dulles International Airport. The crew interpreted their ATC clearance to allow descent to a lower altitude at that segment of the approach than the procedure required. They descended.

The aircraft struck a ridge near Front Royal, Virginia, approximately 12 miles from the runway. All 92 people aboard were killed.

The cockpit voice recorder captured a crew that was focused, communicating, and following procedures as they understood them. Nothing in the cockpit indicated they were below the minimum altitude for that segment of the approach.

That accident triggered an immediate FAA investigation. Within months, the FAA had mandated GPWS for all large transport category aircraft in U.S. airspace - the system Bateman had spent years arguing for was now a regulatory requirement.

The Sharp Decline in CFIT - and the Gap That Remained

By the late 1970s, GPWS was standard commercial aviation equipment. The accident data confirmed the argument: CFIT fatalities in commercial aviation dropped sharply as systems deployed across the fleet.

But the original GPWS had a fundamental limitation. The system was entirely reactive. It monitored current flight parameters against current radio altitude. It had no terrain database, no GPS position fix, and no awareness of what the terrain ahead looked like. It could identify that a sink rate was excessive for a given altitude. It could not identify that in 30 seconds, at the current track and descent rate, a ridge would be at that altitude.

That gap was deadly on approaches over mountainous terrain where an aircraft was in a stable, apparently normal descent and the terrain ahead was rising to meet it. The system saw nothing anomalous in the present moment. The danger was entirely in what was coming.

Korean Air Flight 801 and the Case for Enhanced GPWS

On August 6, 1997, Korean Air Flight 801, a Boeing 747, was on approach to Antonio B. Won Pat International Airport in Guam. The crew was flying a VOR approach at night. The ILS glide slope was out of service, requiring the crew to manage their own descent to the minimum descent altitude before the final approach fix. They flew below that minimum.

The aircraft struck Nimitz Hill, a ridge approximately 3 miles short of the runway, at 228 feet above sea level. 228 people died.

The basic GPWS generated no terrain warning. The 747 was in a stable descent - no excessive sink rate, no gear anomaly, and no glide slope deviation being monitored because this was a VOR approach. The system assessed the current flight parameters as normal. The terrain ahead was outside its awareness entirely.

How EGPWS Closed the Look-Ahead Gap

Honeywell, which had acquired Sundstrand in the late 1980s, was already developing the answer. The Enhanced Ground Proximity Warning System (EGPWS) added two components the original system lacked: a GPS receiver providing continuous precise position, and a worldwide terrain and obstacle database.

The system now cross-referenced the aircraft’s current position and projected flight path against that database in real time. If the projected path intersected terrain within a defined look-ahead window, the system warned. EGPWS also added a terrain display - green for terrain well below aircraft altitude, yellow for terrain requiring attention, red for immediate threat - that became standard on commercial airliner navigation displays.

It is worth understanding the distinction between terrain alerting and synthetic vision. Terrain alerting fires when the database and position fix indicate the aircraft is projected to intercept terrain. Synthetic vision continuously displays a terrain picture on the primary flight display. Some aircraft have both. Some have terrain display without full alerting capability. The specific systems an aircraft carries, and their precise limitations, have operational consequences.

What TAWS Requirements Apply to Your Aircraft?

The FAA required Enhanced GPWS - defined in U.S. regulations as a Terrain Awareness and Warning System (TAWS) - for all turbine-powered transport category aircraft in U.S. airspace beginning in 2001. ICAO followed with international requirements for turbine aircraft in revenue service.

The requirement structure for general aviation is more limited:

  • Class A TAWS is required for turbine-powered aircraft with more than six passenger seats
  • Class B TAWS applies to turbine aircraft with six or fewer passenger seats
  • Piston-powered aircraft in most configurations are not subject to mandatory terrain warning equipment requirements

CFIT still appears in NTSB records in general aviation with regularity - canyon flying in mountainous terrain, approaches to high-elevation airports at night or in IMC, VFR pilots inadvertently entering clouds near high ground. The physics have not changed. The variable is whether the cockpit has the technology to give a warning before those physics become irreversible.

If you operate in mountainous terrain in an older aircraft without certified TAWS, Garmin GTN and GNS series navigators include terrain alerting. Portable devices with terrain databases are a meaningful improvement over nothing - not certified TAWS substitutes, but the difference between some situational awareness and none.

How to Respond to a TAWS Alert

When GPWS or EGPWS generates a “PULL UP” warning, the trained transport category response is immediate and without deliberation. That is not arbitrary procedure - it reflects a specific understanding of human cognition under pressure.

Bateman’s work on human response directly shaped how the alert language was written and how crew training developed around it. At the altitudes and sink rates where these alerts fire, the available time is measured in seconds. The system has already completed the analysis. The crew’s role at that point is not to evaluate. It is to execute.

Don Bateman’s Legacy in the Numbers

Don Bateman received numerous recognitions over his career, including induction into the International Air and Space Hall of Fame and the FAA Award for Aviation Excellence. By most estimates, the systems he developed have prevented between 3,000 and 5,000 deaths in commercial aviation alone. The general aviation figure is harder to quantify but is not zero.

The engineering was not exotic. The concept was achievable with the technology that existed. What required years of persistence was overcoming the institutional assumption that CFIT was an acceptable cost of operating in complex terrain environments. Bateman had the data, he had the working system, and he kept making the case until the industry ran out of defensible reasons not to act.

The pattern is worth noting: the technology was available before the regulatory mandate existed. The gap between what was technically possible and what was actually required closed one accident investigation at a time. That dynamic has appeared across aviation safety history more than once.

The terrain database in your panel, the voice that calls out terrain on a mountain approach, the colored display painting the ridge ahead yellow or red - all of it traces to that work.


Key Takeaways

  • CFIT accounted for roughly one-third of all fatal airline accidents through the 1960s, making it the dominant cause of commercial aviation fatalities for over a decade.
  • Don Bateman developed GPWS at Sundstrand Data Control after identifying predictable flight data signatures common to CFIT accidents; the December 1, 1974 crash of TWA Flight 514 - killing all 92 aboard - triggered the FAA mandate.
  • The original GPWS was reactive and had no look-ahead capability, a limitation fatally exposed by the August 6, 1997 crash of Korean Air Flight 801, which killed 228 people in Guam.
  • EGPWS/TAWS added GPS positioning and a worldwide terrain database, enabling look-ahead alerting; the FAA required it for turbine transport category aircraft beginning in 2001.
  • Class A TAWS is not required for piston-powered GA aircraft. Pilots operating in mountainous terrain without certified terrain alerting should treat navigators with terrain databases as a minimum mitigation, not an equivalent substitute.

Radio Hangar. Aviation talk, built by pilots. Listen live | More articles