Moffett Field 1973: NASA Convair 990 and Navy P-3 Mid-Air Collision

Advertisement
Timeline
Event 1 —
The two aircraft approached the same traffic area while operating under ATC.
1.
Event 2 —
The controller identified conflicting traffic as the aircraft continued toward one another.
2.
Event 3 —
Instructions were issued as the separation margin narrowed.
3.
Event 4 —
The aircraft continued to converge despite the attempted resolution.
4.
Event 5 —
The aircraft collided in midair.
5.
Event 6 —
The collision resulted in a fatal crash.
6.

The Clearance That Changed Everything

On April 12, 1973, two very different aircraft were approaching Moffett Field in California.

One was Galileo, NASA's Convair 990 research aircraft, registration N711NA.

The other was a U.S. Navy P-3C Orion, Bureau Number 157332, returning from a training mission.

The P-3 had been operating in the local traffic pattern, practicing touch-and-go landings.

Both aircraft were approaching the same airfield.

Both were operating under visual flight rules.

And both were talking to the tower.

Then the controller issued a runway assignment that put the two aircraft on a collision course.

The Convair 990 had previously been cleared for Runway 32R.

But about three miles from the airport, the controller cleared it to land on Runway 32L.

The Convair crew acknowledged the clearance.

The controller simultaneously cleared the Navy P-3 to continue its approach to Runway 32L.

The tower operator had intended the Convair to land on Runway 32R.

He had called the wrong runway.

NASA's historical record of the joint NASA-Navy investigation explicitly identified this runway-assignment error. (NASA)

The consequences were fatal.

Galileo

The NASA Convair 990 was not an ordinary airliner.

It had been converted into a flying research laboratory.

Known as Galileo, it carried NASA personnel and scientific equipment.

On the day of the accident, the aircraft had been conducting research over the Monterey Bay area.

There were 11 people aboard: three crew members and eight NASA scientists or technicians.

The flight itself had been routine.

There was no engine emergency.

No severe weather.

No mechanical failure.

The crew was simply returning to Moffett Field.

The aircraft entered the airport area and began its approach.

The P-3 was also returning to Moffett.

It had spent several hours on a training flight before entering the airport traffic pattern.

The crew had been conducting touch-and-go operations on Runway 32L.

That meant the P-3 was already established in a local pattern.

The NASA Convair was arriving from outside.

The runway assignments were therefore critical.

Two Aircraft, One Runway

The P-3 crew had been flying repeated approaches.

The Convair was initially cleared toward Runway 32R.

The aircraft continued its approach.

Then the clearance changed.

The crew read back the clearance.

The P-3 was also operating for Runway 32L.

The tower controller intended to keep the aircraft separated by using the parallel runways.

But the wrong runway had been issued to the Convair.

That single communication error destroyed the separation plan.

The joint investigation later found that the controller's intention had been to land the Convair on Runway 32R but that the wrong runway had been called. (NASA)

This is precisely why readbacks matter.

The Convair crew correctly read back the runway they had been assigned.

From their perspective, they were following the clearance.

The P-3 crew was also following its instructions.

But the three parties were no longer operating from the same mental picture.

The Final Approach

The aircraft converged near the approach to Moffett Field.

The Convair was descending toward Runway 32L.

The P-3 was also approaching Runway 32L.

The aircraft were close to the ground.

At approximately 300 feet above the ground, the two aircraft collided.

The impact occurred near the airport, over the Sunnyvale Municipal Golf Course.

The Convair 990 and P-3 both crashed.

The NASA aircraft was destroyed.

All 11 people aboard Galileo died.

Five of the six people aboard the Navy aircraft died.

One Navy crewmember survived. (NASA)

Sixteen people were killed.

One person survived.

Why the Accident Was So Significant

The accident was not simply a story about two pilots failing to see each other.

It was an example of how the air traffic control system can create a conflict when the information supplied to aircraft is wrong.

The pilots were doing what they believed they had been instructed to do.

The Convair crew was not intentionally entering the P-3's runway.

The P-3 crew was not intentionally occupying the Convair's runway.

The controller's mistaken runway call created the conflict.

This is one of the most important distinctions in ATC accident analysis.

A controller's mistake does not necessarily mean a controller deliberately violated a procedure.

A simple verbal error can have enormous consequences when aircraft are moving quickly and the clearance is operationally significant.

The Environment at Moffett

Moffett Field was a busy aviation facility.

It served military operations while also supporting NASA's Ames Research Center.

P-3 Orion aircraft were common in the local environment, conducting anti-submarine warfare training and pattern work.

NASA research aircraft operated from the same complex.

NASA historical material notes that the Convair 990 flying laboratory was part of Ames' airborne research capability. (NASA Science)

The coexistence of military training and NASA research operations made traffic coordination particularly important.

The P-3 had been operating in a local pattern.

Both had legitimate reasons to be in the airport environment.

The system needed to keep those operations separated.

The Collision Avoidance Problem

The accident also demonstrated the limitations of visual separation.

At the time, the aircraft were operating under VFR.

There was no modern airborne collision-avoidance system providing the type of warning pilots receive today from TCAS/ACAS-equipped aircraft.

The aircraft were therefore dependent on controller instructions, visual detection and procedural separation.

Once the controller issued the wrong runway assignment, the system had lost one of its most important defenses.

The pilots could theoretically see each other.

But two aircraft approaching the same runway at several hundred feet above the ground may have only seconds to recognize a conflict and maneuver.

A runway assignment error therefore created a rapidly closing window.

The Investigation

A joint NASA-Navy board investigated the accident.

The board determined that both aircraft were operating under visual flight rules.

The Convair was making a straight-in approach.

The tower controller had originally cleared the Convair toward Runway 32R.

At approximately seven miles from the airport, the aircraft was again cleared toward the right runway.

The Convair pilot acknowledged it.

The P-3 was also cleared to continue toward Runway 32L.

That sequence was the central mechanism of the accident. (NASA)

The Human Factors

There is a tendency in accident reporting to reduce an event like this to one sentence:

Technically, that describes the initiating error.

But aviation safety requires asking why a single error was able to progress all the way to a fatal collision.

The system had multiple opportunities to detect the conflict.

The Convair crew knew they had been assigned 32L.

The P-3 crew knew they were using 32L.

The controller believed he had separated them.

The three mental models did not match.

That is a classic aviation safety problem.

A safe system should not depend on every individual making every decision perfectly.

It should contain cross-checks.

It should contain redundancy.

It should make dangerous misunderstandings visible before they become irreversible.

Accident Facts

Aviation Safety Network records both aircraft as separate fatal accidents at Moffett Field on April 12, 1973, with 11 fatalities aboard the NASA Convair and five aboard the Navy P-3. (Flight Safety Foundation)

What Changed Afterward

The accident occurred during a period when midair collisions were a major aviation safety concern.

Only a few days after the crash, the U.S. Senate discussed the accident and proposed legislation concerning airborne collision-avoidance systems. The Congressional Record described the tragedy as a recent example of the continuing danger of midair collisions. (Congress.gov)

The larger aviation system was beginning to recognize that relying entirely on human visual detection and ground-based separation was not enough.

Technology would eventually provide another layer.

Today, airborne collision-avoidance systems provide crews with information that was not available to the crews of Galileo and the P-3.

That does not make controller accuracy less important.

It demonstrates why aviation safety uses multiple layers of defense.

The Broader Safety Lesson

The Moffett accident is one of the clearest demonstrations of how a seemingly small communication error can become catastrophic when the system lacks enough redundancy.

The controller did not intend to clear two aircraft into the same approach.

The Convair crew did not knowingly violate a clearance.

The P-3 crew was not knowingly entering a conflict.

Yet the system produced exactly that result.

The lesson for controllers is obvious: runway numbers, headings and clearances must be treated as safety-critical information.

The lesson for pilots is equally important: a clearance must be understood, monitored and cross-checked against the actual traffic environment.

Safety cannot depend on a single person never making a mistake.

The safest systems are those in which an inevitable human error is caught before it becomes a fatal event.

At Moffett Field, that second layer did not stop the mistake.

Sixteen people paid the price.

Date
April 12, 1973
Aircraft
NASA Convair 990 / U.S. Navy P-3C Orion
Registration
N711NA / BuNo 157332
Location
Near Moffett Field, California
Category
Midair collision
Fatalities
16 (11 aboard the Convair, 5 aboard the P-3)

Sources

Audio from the original air traffic control recording, sourced from public recordings and released investigation records. The reconstruction, animation and written account are our own.
Advertisement

Official Investigation Source

The weekly incident