aviation-safety

Marshall University Plane Crash Cause: Verified Details and Findings

On November 14, 1970, a chartered Southern Airways Douglas DC-9 crashed into a ridge near Tri-State Airport while on approach to Huntington, West Virginia, killing all 75 people...

Mara Ellison
Marshall University Plane Crash Cause: Verified Details and Findings

Summary of Key Findings on the Marshall University Plane Crash Cause

On November 14, 1970, a chartered Southern Airways Douglas DC-9 crashed into a ridge near Tri-State Airport while on approach to Huntington, West Virginia, killing all 75 people on board. The National Transportation Safety Board (NTCB) determined the crash cause was controlled flight into terrain, primarily due to a false altimeter setting assigned by air traffic control that led the crew to believe they were at a safe altitude. Contributing factors included procedural noncompliance, lack of altitude callouts, and possible ambiguities in ATC clearance. This verified overview explains the factual basis, investigation conclusions, and long‑term safety implications without speculation.

Official Investigation and Chain of Facts

The NTSB led the investigation, with the Federal Aviation Administration and airline representatives participating. The board issued its final report in 1971, stating that the crew followed incorrect altitude instructions that placed the aircraft below the safe approach gradient. Cockpit voice recorder data indicated continued reliance on instrument readings despite visual cues that should have raised doubt. The factual record shows repeated opportunities for intervention that were not taken, emphasizing the interaction between human factors, technology, and procedures.

Investigation Timeline at a Glance

Date or PeriodEventWhy It Matters
Nov 14, 1970DC-9 crashes on approach to Tri-State AirportImmediate safety impact; all 75 aboard killed
Nov–Dec 1970NTSB on‑site investigation and evidence collectionPreserves physical and digital evidence
Apr 1971NTSB publishes final reportEstablished factual record and safety recommendations

Technical Breakdown of the Crash Cause

The stated crash cause centers on controlled flight into terrain driven by an incorrect altimeter setting. Air traffic control issued a setting that produced a systematic altitude error, and the crew did not catch the discrepancy through cross‑checks. The aircraft was flown into rising terrain while believing it was at a safe altitude on instruments. This section breaks down the technical elements in plain language to support durable understanding.

Contributing Elements

  • Altimeter mis-setting provided by ATC.
  • Failure to execute standard altitude callouts.
  • Lack of terrain awareness and use of available navigational aids.
  • Procedural noncompliance not challenged by crew coordination.

Aircraft and Route Context

The aircraft was a Douglas DC-9 operated by Southern Airways, operating as Flight 932 from Knoxville to Huntington with an intermediate stop in Charleston, West Virginia. The flight was carrying the Marshall University football team, booster club members, and coaching staff. Understanding the route, the operator, and the type of equipment helps frame how such an accident could occur and informs targeted prevention measures.

Safety Recommendations and Lasting Impact

In response, the NTSB issued targeted recommendations on altitude verification, ATC phraseology, and cockpit procedures. Airlines and regulators adopted standardized altitude callouts, improved checklist discipline, and clearer separation of duties. These changes became part of broader industry efforts to reduce controlled flight into terrain. This section connects the crash findings to concrete improvements that remain relevant to current operations.

Key Facts at a Glance

AttributeVerified DetailSource Type
AircraftDouglas DC-9, registration N97SInvestigative report
OperatorSouthern AirwaysAirline records
Flight932, Knoxville–Huntington (Tri-State Airport)ATC flight data
DateNovember 14, 1970NTSB factual summary
Fatalities75Official count
Primary crash causeControlled flight into terrain due to wrong altimeter settingNTSB final report
Investigating bodyNTSB with FAA participationPublic investigation docket
Safety impactProcedural and technology reforms in altitude disciplineRegulatory implementation records

FAQ

Reader questions

What was the official cause stated by the NTSB?

The NTSB cited controlled flight into terrain caused by an incorrect altimeter setting and related procedural failures.

Were any individuals held responsible?

No individual was criminally or administratively singled out; the investigation focused on system and procedural factors.

Did the investigation lead to regulatory changes?

Yes, the findings contributed to updated altitude verification procedures and clearer ATC–pilot communication standards.

Why does this accident remain relevant today?

It illustrates how altimeter errors and communication gaps can still matter in modern aviation, reinforcing checklists, cross‑checks, and crew resource management.

Related Reading

More pages in this topic cluster.

Understanding the B-17 Plane Crash: Causes, History, and Safety Lessons

The query b17 plane crash is best understood as an evergreen request for factual context, not a single breaking event. It typically reflects an interest in the structural, opera...

Read next
Boeing 737 Crash History: Verified Incidents, Trends, and Safety Context

The Boeing 737 is the world’s most produced commercial jetliner, and its crash record shapes public trust, regulation, and airline decisions. This article presents a verified,...

Read next
Understanding Moody Aviation Crashes: Causes, Patterns, and Safety Lessons

Moody aviation crashes are accidents where weather-related hazards, operational pressures, and human factors intersect, often intensifying risk in already complex flight regimes...

Read next