The First Officer Saw It Coming

▶️ Prefer to watch? Every story’s a short video → https://www.youtube.com/@GetSafetyIntel · 📣 Got a near-miss? Share it anonymously (QR + link at the bottom).

Fifty-three years ago tonight, an experienced captain flew a good airplane and a healthy crew straight into a mountain in the dark — and the man in the right seat saw it coming and said so. His last recorded words were the number that would have saved everyone on board. This is a story about the person closest to the work spotting the hazard first, and a system that wasn’t built to let his voice turn the airplane. If you’ve ever been the junior person in the room who wasn’t sure it was your place to speak up, this one’s yours.

At night on September 27, 1973, Texas International Airlines Flight 655 — a Convair 600 turboprop, tail number N94230 — was working a milk run of short hops across Arkansas, El Dorado to Texarkana, on its way to Dallas. In the cockpit were two seasoned professionals: Captain Ralph Crosman, 41, with 11,800 hours; and First Officer William Tumlinson, 37, with 7,106. Behind them, a flight attendant and eight passengers. Eleven souls. There were no survivors.

Here’s the mechanism, because the mechanism is the lesson. On the ground at El Dorado, the crew checked a line of thunderstorms about 35 miles to the west and confirmed a roughly 15-mile break in the weather. Then they made the decision that set everything else in motion: they departed at night, under Visual Flight Rules — “we can see well enough to stay clear of terrain” — instead of activating the instrument flight plan their own dispatcher had already filed. Under instrument rules they’d have been handed altitudes that guarantee terrain clearance, and they’d have been tracked on radar. Under VFR in that stretch of rural Arkansas — where there was no controlled airspace below 18,000 feet — they were on their own, unwatched, in the dark.

The captain flew the airplane deeper into the problem. To get around the weather he deviated roughly 100 miles north, into higher ground, while the first officer hand-flew and the captain called headings and altitudes. The cockpit voice recorder caught the whole slow-motion trap. Tumlinson said plainly he didn’t know their position or what the terrain clearance was out there. The captain ordered a descent to 2,000 feet anyway. Tumlinson pulled the en route chart, did the math, and keyed the warning: “Minimum en route altitude here is forty-four hun—”

Forty-four hundred feet. The recording ends mid-word. They were at 2,000, being sent lower, over ground whose minimum safe altitude was 4,400. The airplane struck Black Fork Mountain. It took searchers three days to find the wreckage, because nobody had been tracking where they went.

The National Transportation Safety Board (report AAR-74-04) put the probable cause squarely on a chain of decisions: continuing into bad weather at night, not using the navigation aids that were right there to fix their position, and — the line that should stop every one of us cold — descending despite the first officer’s stated concern about position and terrain. The man closest to the work saw the hazard, named the exact number, and the descent continued anyway.

This is aviation, so the book is Title 14, not the 1910 and 1926 most of us live in — but the bones are identical. Scheduled passenger airlines run under Instrument Flight Rules (14 CFR Part 121), on filed instrument flight plans built around the minimum en route altitude — the MEA (see 14 CFR 91.177) — the floor below which you are betting your life on ground you cannot see. Translate it to your floor: the MEA is the permit, the LOTO verification, the atmosphere test before you enter — the predetermined line that takes “I think we’re fine” out of one person’s hands on a dark night. Flight 655 died in the gap between “legally allowed to eyeball it” and “required to fly a number that clears the rock.” (Verify current text at https://www.ecfr.gov before you build anything on it — regs move.)

The one-liner, written in the blood of eleven people: the moment the decision to go lower depends on one person’s read of the dark, you don’t have a safety system — you have a coin flip with a good résumé.

I’ll be straight with you, the way I always am: this one doesn’t braid E, H and S together the way most of our stories do. Environmental (E): the footprint was a fuel spill and burn on a remote mountainside — wreckage that sat in what’s now the Black Fork Mountain Wilderness. No downstream water contamination, no town under a plume; I’m not going to invent one. Health (H): eleven dead, no survivors, and three days of searchers combing ridgelines because the flight was never tracked — but no community exposure, because the mountain was empty. Safety (S): this is where all the weight fell — a passenger flight at night, VFR, unmonitored, descending below the terrain-clearing altitude with the one warning voice out-ranked. So here’s the honest tie-together: this wasn’t the usual E-and-H-and-S knot. But the lesson underneath it is the exact same one that saves the creek and the town in every other issue we run — the person closest to the work saw the hazard first, and the system has to be built so that when they say it out loud, the operation actually stops.

Heat: stop waiting for the rule — the enforcement is already here. On September 16, 2026, OSHA’s standards director said the agency plans to issue a supplemental proposed heat rule “in the coming months,” which resets the clock again — the Unified Agenda now shows a supplemental proposal in December 2026 and final action not until October 2027. Do not read “no final rule” as “no exposure.” The revised Heat National Emphasis Program (updated April 2026) is live and steering inspections across 55 high-risk indoor and outdoor industries right now, and OSHA is still citing heat-illness cases under the General Duty Clause today. So what for safety leaders: you don’t get to wait for October 2027. If you don’t already have a written plan — water, rest, shade, and real acclimatization for new and returning workers, plus someone actually watching for symptoms — you’re carrying the whole risk on the General Duty Clause, and that’s exactly where the citations are landing. (Source: Safety+Health/NSC; U.S. DOL.)

Trenches are still swallowing crews — and OSHA is putting names on it. This month OSHA cited a Colorado excavation contractor over the deaths of two workers, Cristopher Ramirez, 26, and Jorge Baez Valadez, 41, who were buried in an April trench collapse while installing a sewer line; a second Colorado contractor was hit with roughly $92,800 in trenching penalties in the same stretch. That’s 29 CFR 1926 Subpart P. A cubic yard of soil weighs about as much as a small car, and a wall lets go in under a second — nobody digs their way out. So what for safety leaders: at five feet you need a protective system — slope it, shore it, or drop a trench box — spoil set back at least two feet, and a competent person inspecting before entry, after every rain, and every time conditions change. These deaths are almost always 100% preventable, which is exactly what makes the citations stick. (Source: OSHA/U.S. DOL; CBS News Colorado.)

Shared blamelessly, because that’s the only way anyone learns from it.

A maintenance apprentice is helping a respected senior tech clear a jam on a conveyor drive. The senior’s already thrown a disconnect and is reaching in. The apprentice notices two things at once: the lock on that disconnect isn’t the tech’s personal lock, and there’s a second drive motor on the far end that nobody’s touched. His gut says say something — and right behind it comes the voice we all know: he’s done this a thousand times, don’t be the new guy who slows the job. He almost swallows it. Then he asks the small, awkward question anyway: “Hey — is that thing dead on both ends?” The tech stops. They walk it back, find the second disconnect still closed, and confirm the line had stored energy that would’ve turned that drive under his hands. Nobody got hurt. It became a two-minute story at the toolbox talk instead of a phone call to somebody’s family.

The HOP read: that apprentice wasn’t a hero and the senior tech wasn’t careless — both of them were being normal. The pull to stay quiet in front of experience and rank is not a character flaw, it’s the physics of the human animal, and “he’s obviously got it” is how a huge share of lockout fatalities start (29 CFR 1910.147 — control of hazardous energy, group lockout, and stored-energy verification). The save wasn’t a braver kid. It was two things working together: a crew culture where a green guy could ask the dumb question out loud, and a senior man who stopped instead of bristling. That gap — a question you’re allowed to ask and a boss who halts when you ask it — is the entire distance between a near-miss and a funeral. Ask yourself which one First Officer Tumlinson had.

Got a fail or a near-miss? Hit reply, or scan the QR below — we’ll feature it anonymously — no names, no company, no blame. Just the lesson, so the next crew doesn’t learn it the hard way.

Share your near-miss here → https://scantoconfess.com — 100% anonymous, no names, no company, no blame.

Before your next shift or crew brief, have the most senior person in the room say this out loud to the newest: “If you ever see something that doesn’t look right, I want you to stop me — by name — even if I’m in the middle of it, even if it turns out you’re wrong. Especially if it’s me doing it.” Then make it real the first time it happens: when the green guy calls a stop, you stop, you look, and you thank him — right or wrong — because you’re not rewarding the catch, you’re protecting the next one. Flight 655 had a first officer who saw the mountain coming and said the altitude out loud. The system just wasn’t built to let his voice turn the airplane. Build yours so it can.

🎬 Rather watch than read? Every Safety Intel story is a short video on YouTube → https://www.youtube.com/@GetSafetyIntel — subscribe so you never miss one. 📸 Share YOUR near-miss (100% anonymous): https://scantoconfess.com — or just scan the QR above. 📤 Forward this to a crew member who needs it today.

Please stay Safe & Hydrated!!!

Texas International Airlines Flight 655 — date, aircraft, crew, 11 fatalities, VFR departure, CVR sequence, probable cause: NTSB Aircraft Accident Report AAR-74-04 (April 7, 1974): https://www.ntsb.gov/investigations/AccidentReports/Reports/AAR7404.pdf

Flight 655 summary, crew, and the CVR quote “minimum en route altitude here is forty-four hun—”: https://en.wikipedia.org/wiki/Texas_International_Airlines_Flight_655

IFR and minimum-altitude operating rules — 14 CFR Part 121 and 14 CFR 91.177 (verify current text): https://www.ecfr.gov

OSHA heat rulemaking and revised Heat National Emphasis Program (supplemental proposal signaled Sept. 16, 2026): https://www.osha.gov/heat-exposure/rulemaking

Colorado trench-collapse citations and worker names (CBS News Colorado): https://www.cbsnews.com/colorado/news/backhoe-excavating-company-fine-trench-collapse-two-workers-killed-windsor-firestone-construction-accident-christopher-ramirez-jorge-valadez

OSHA control of hazardous energy (lockout/tagout) — 29 CFR 1910.147: https://www.osha.gov/laws-regs/regulations/standardnumber/1910/1910.147