The case
On 28 December 1978 United Airlines Flight 173, a DC-8, circled near Portland, Oregon, for about an hour while its crew worked a landing-gear problem, ran out of fuel and crashed; ten people died. The NTSB (LIT-1371) found the probable cause in the captain’s failure to monitor the fuel state and to respond to the crew’s advisories about it, and a contributing cause in the other crew members’ failure either to grasp its criticality or to communicate their concern to the captain successfully.
The accident became a standard starting point for Crew Resource Management. Beginning with a NASA workshop in 1979, airlines trained crews in assertion, challenge and coordination. Helmreich, Merritt and Wilhelm (LIT-1386) trace CRM through five generations to error management, avoiding, trapping and mitigating error, with the captain’s command kept. Separately, after TWA 514 struck a mountain on 1 December 1974, it emerged that a United crew had nearly made the same error weeks earlier and the warning had stayed within United. The Aviation Safety Reporting System followed in 1976. Both papers and the report are registered unread; the 1974 and 1976 history is the exchange’s, unchecked.
What it shows
- Access without authority. The crew had the fuel state; it did not govern the captain’s action. That is CLAIM-349’s separation of access to a signal from its authority over action, in a cockpit.
- Authority without abolishing command. A25: CRM was “authority without abolishing command”; it sought to “maintain meaningful avenues of challenge while preserving the capacity for decisive action”. The reform changed how authority is organized, not who holds it. This is CLAIM-424’s governance of the conditions of authority, and A25’s answer to its own counterexample of an over-active safety officer: “Non-domination doesn’t imply unconditional veto power.”
- Information partitioned between collectives. ASRS answered a warning that one airline had and the others did not. A25 kept this apart from the cockpit case: the information was partitioned “between collectives”, not within one.
What it does not show
- That CRM caused the later decline in accident rates. The case is the reform’s history, not its evaluation.
- That a crew is an agent. It is an organization of authority whose holder was a person throughout.
Note of 2026-10-22: what the two sources say
- The NTSB’s finding is narrower than “knew”. “While there is evidence to indicate that the crew was aware of the amount of fuel remaining at various times, there is no evidence that the onboard quantity was monitored, in relation to time remaining during the final 30 min of flight” (LIT-1371, p. 25). And “apparently no one was specifically delegated the responsibility of monitoring fuel state” (p. 26). The title said the crew knew the fuel was running out; it is corrected.
- “Without abolishing command” is not in Helmreich et al. Neither the phrase nor the idea is in LIT-1386, which mentions command once. The documented source is the NTSB’s recommendation X-79-17 (LIT-1371, p. 30): crews “indoctrinated in principles of flightdeck resource management, with particular emphasis on the merits of participative management for captains and assertiveness training for other cockpit crewmembers.” The bullet “Authority without abolishing command” is A25’s, and should be read as the exchange’s gloss on that recommendation.
- What Helmreich et al. add. Training did not make the capacity permanent: “a slippage in acceptance of basic concepts, even with recurrent training” (p. 5). That is CLAIM-422’s distinction between a procedure and a maintained capacity, in the paper’s own evidence.
- The procedure already existed. United’s manual already required crew to advise the captain of departures from safe practice (LIT-1371, §1.17.1). The accident was not for want of a rule.