Twenty-Two Seconds

▶️ 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).

Eighteen years ago today, a commuter train and a freight train ran head-on into each other on a single-track curve near Chatsworth, California, and 25 people died. There was no equipment failure, no broken rail, no weather. A man at the controls looked away from his job for the last time, and a red signal meant to stop him did its job perfectly — it just had no way to reach past him and stop the train. Here’s the afternoon it happened, and the two systems the country built afterward so that a moment of human distraction couldn’t be the last line of defense again.

About 4:22 in the afternoon on a Friday, westbound Metrolink train 111 — one locomotive pushing three packed passenger cars at the end of the commute — came around a curve near Chatsworth, on the northwest edge of Los Angeles. Coming the other way on the same track was Union Pacific freight train LOF65-12. They hit head-on. The force drove the Metrolink locomotive about 52 feet back into its own lead passenger coach, telescoping steel into the space where people were sitting. Twenty-five people were killed, including the engineer. Emergency crews transported 102 injured passengers to hospitals. (NTSB report RAR-10/01.)

Here is the part a safety person has to sit with, because it’s not a machine story — it’s a human-and-system story.

That stretch of railroad had a signal at Control Point Topanga, and that signal was red — it was telling train 111 to stop and hold for the freight. The engineer went past it. The National Transportation Safety Board determined the probable cause was his failure to observe and respond to the red signal because he was engaged in prohibited use of a wireless device — he was text-messaging on duty. Investigators found he’d sent and received 43 text messages and made four phone calls during his shift that day. His last text went out at 4:22:01 p.m. The collision was recorded at 4:22:23 p.m.

Twenty-two seconds.

That’s the whole margin. Not a design flaw, not a decade of neglect — twenty-two seconds of a working man’s attention pulled off the one thing that mattered, on a system that had staked 25 lives on him never doing exactly that.

It’s tempting to make this a story about one careless man, close the file, and feel safe because you’d never do it. Don’t. That’s the trap, and it’s the opposite of the lesson. The NTSB named a second cause, and it’s the one that should keep you up: contributing to the accident was the lack of a positive train control system that would have stopped the Metrolink train short of the red signal and prevented the collision. Read that again. The engineer’s error was the trigger. The reason the error was fatal was that there was nothing behind him. The red signal was a warning with no muscle — it could tell the train to stop, but it couldn’t stop the train.

That’s the whole HOP point, and Chatsworth is the hardest version of it. Error is normal — humans get distracted, and a workforce of thousands operating for millions of hours will produce a distracted moment; it’s a statistical certainty, not a character defect. Blame is emotionally satisfying and operationally useless: you can fire the man, and you have changed nothing about the next distracted moment coming down the line at somebody else. What actually changes the outcome is a system that assumes the error will happen and puts something in its path. The person closest to the work — the engineer — was the last human who could catch it, and when he didn’t, the design had no backup human, no automatic brake, nothing. A safety system whose entire failure mode is “the operator has to be perfect, forever” is not a safety system. It’s a bet.

Two rules came out of Chatsworth, and they’re the two halves of how you actually fix a distraction hazard (current as of September 12, 2026 — verify the live text at ecfr.gov before you build a program on it).

The rule aimed at the behavior: nineteen days after the crash, the Federal Railroad Administration issued Emergency Order No. 26 (October 1, 2008) banning nonoperational use of cell phones and personal electronic devices by railroad operating employees while running a train. It was later codified as 49 CFR Part 220, Subpart C — Electronic Devices. That’s the “put the phone down” rule, written in 25 people’s names.

The rule aimed at the system: Congress passed the Rail Safety Improvement Act of 2008 (Public Law 110-432, signed October 16, 2008), mandating Positive Train Control — governed by 49 CFR Part 236, Subpart I — across roughly 70,000 miles of the highest-risk track. PTC is the backstop that was missing: it monitors where a train is and what its signals say, and if the crew doesn’t respond, the system stops the train itself. The deadline was fought and pushed — from 2015 to 2018 and, for some railroads, to 2020 — but PTC was operational across all required lines by the end of 2020. The technology that would have made September 12, 2008 a non-event took twelve years to finish installing.

Translate it to the floor: you probably don’t run a locomotive, but you run something — a forklift, a crane, a boom truck, a haul truck, a press, a fleet of vehicles. Chatsworth’s question for your site isn’t “do my people know not to look at their phones?” They already know. The question is: when one of them looks anyway — and one of them will — what physically stops the bad outcome? If the honest answer is “we trust the operator,” you have a red signal and no brake.

Most incidents are E, H, and S at once. This one landed almost entirely on the H and the S — but the reason it belongs on every safety leader’s desk is where it could have landed.

Safety (S): the spine of the story — a single human operator with no engineered backstop behind him, a passed red signal, a head-on closing speed with nothing to bleed it off. That’s the failure, and PTC is the fix.

Health (H): 25 dead, overwhelmingly from blunt-force trauma as the locomotive telescoped into the lead coach; 102 more hauled to hospitals with injuries ranging to critical. And the part that doesn’t show in the count — the surviving passengers, the first responders who worked a telescoped rail car for hours, and two rail communities that carried it for years. Trauma is an exposure. It doesn’t clear when the wreckage is towed.

Environmental (E): be honest and narrow. These were diesel-electric locomotives, and a fire broke out in the wreckage fed by locomotive fuel, in a residential rail corridor in the middle of a major city. There’s no verified record of a major offsite chemical release here — the harm stayed with the people on the trains. But hold that up against why the PTC mandate exists. Congress didn’t scope PTC to every mile of track — it scoped it to passenger lines and to the freight main lines that carry poison-inhalation-hazard chemicals like chlorine and anhydrous ammonia. Because the exact same failure — an operator distracted, a signal passed, no backstop — is, on a chlorine train through a town, not 25 funerals but a toxic cloud over a neighborhood. One plain line: the missing backstop that killed commuters in Chatsworth is, on a different consist, a chemical release over a fenceline — E, H, and S all riding the same track, decided by the same twenty-two seconds.

Eighteen years later, the NTSB is still writing the Chatsworth finding — this time on the water. On August 6, 2026, the NTSB released its report (Marine Investigation Report MIR-26-24) on a fatal collision in the Houston Ship Channel near Lynchburg, Texas: the bulk carrier Yangze 7 and the towing vessel Miss Peggy collided on July 19, 2024. The Miss Peggy capsized and sank with five crew aboard; one crewmember was found dead in the wreckage and another was seriously injured. The cause: the pilot directing the Yangze 7 had been on a 39-minute nonoperational phone call — it ended 2 minutes and 16 seconds before impact — and never saw the towboat. The NTSB added that distraction by personal electronic devices was a factor or probable cause in at least 10 marine casualties between 2009 and 2024, killing three and injuring 45, and recommended the Coast Guard and the American Pilots’ Association flat-out prohibit nonoperational device use by anyone directing a vessel. So what for safety leaders: this is the same finding as Chatsworth, in a different uniform, eighteen years on. The behavior rule keeps getting written — rail, then marine — and the behavior keeps happening, because a rule is a red signal: it tells people to stop, it can’t make them. The industries that actually cut distraction deaths are the ones that engineered the device out of the moment of movement, not the ones that just wrote another policy. Ask which one you’re doing. (Source: NTSB, MIR-26-24, Aug 6, 2026.)

A cargo jet ran off the runway in Miami — and the recorder caught a crewmember calling the danger out loud, and it not landing. On September 9, 2026, the NTSB issued an investigative update on the September 6 runway excursion of 21 Air Flight 7598, a Boeing 767 cargo jet, at Miami International. Per the preliminary cockpit-voice-recorder readout, on approach one pilot warned the other that they were too fast, and kept saying it — the NTSB’s words: “there was not a consistent verbal response to the comments about speed.” The plane got automated “sink rate” and “too low terrain” warnings, touched down long and fast (about 158 knots), never deployed thrust reversers or speed brakes in the data, called a go-around too late, and departed the paved surface. It’s preliminary, and no one is assigning cause yet. So what for safety leaders: the person who could see the hazard saw it and said it — repeatedly — and the callout didn’t turn into action. That’s the other half of the Chatsworth lesson. It isn’t enough for the person closest to the work to spot the danger; your system has to make their voice land and trigger a stop. A warning that doesn’t change what happens next is just noise with good intentions. When your newest or quietest crew member says “this is wrong,” what in your operation guarantees the machine actually stops? (Source: NTSB investigative update, DCA26MA352, Sept 9, 2026.)

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

A yard hostler is backing a trailer into a dock on a busy shipping afternoon. His phone lights up on the seat with a dispatch text — the shift is behind and they’re reworking the door assignments in real time, so of course he glances at it; that’s the job talking to him. In that glance the truck drifts a few feet off his line, toward a loader who’d stepped out from between two trailers to check a seal and assumed the truck saw him. A groundman working the dock sees the geometry go wrong before anyone else does and yells one word — “STOP” — and the hostler stands on the brake and stops short. Nobody’s touched. Everybody’s heart rate is up. They reset, the loader waits until the truck’s parked, and the door assignments get sorted after the trailer’s spotted, not during.

The HOP read: nobody in this story is reckless. The text was work — real production pressure, not a character flaw — and glancing at a buzzing phone is a thing a hundred good operators do a hundred shifts running without anything happening. The loader stepping out to check a seal was doing his job too. What caught it wasn’t a smarter, more disciplined worker; it was a groundman positioned to see the whole picture and empowered to stop the move with one word — no “are you sure,” no waiting to be proven right. That’s the Chatsworth backstop in miniature: the operator’s attention slipped, and this time there was something behind him. Two questions worth more than another distraction policy: Can anyone on your yard stop a moving vehicle with one word, and does that word land instantly? And what have you done to keep the phone out of the operator’s hands while the wheels are turning — a mount, a do-not-disturb-while-moving lock, a rule that dispatch waits for “spotted” — instead of just telling people not to look?

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.

Pick one job on your site where a person operates something with momentum — a forklift, a crane, a yard truck, a company vehicle, a press — and answer two questions honestly. One: what pulls their eyes off the task? A phone, a handheld scanner, a two-way radio, a dispatch screen — name the specific thing that competes for their attention while the equipment is live. Two: if their attention slips for twenty-two seconds, what physically stops the bad outcome? A backup alarm nobody can override, a spotter with real stop authority, an interlock, a speed limiter, a proximity cutoff — or nothing but the hope that they won’t slip. If the only answer to question two is “they know better,” you’ve found today’s job. Chatsworth had a red signal and a rulebook. What it didn’t have was a brake that didn’t need the man. Give your people the brake.

Sources: NTSB — Collision of Metrolink Train 111 with Union Pacific LOF65-12 (DCA08MR009 / Report RAR-10/01) → https://www.ntsb.gov/investigations/Pages/DCA08MR009.aspx · Rail Safety Improvement Act of 2008, Public Law 110-432 → https://www.congress.gov/110/plaws/publ432/PLAW-110publ432.pdf · 49 CFR Part 220, Subpart C (Electronic Devices) → https://www.ecfr.gov/current/title-49/subtitle-B/chapter-II/part-220/subpart-C · NTSB — Cellphone Use Leads to Fatal Vessel Collision (MIR-26-24, Aug 6, 2026) → https://www.ntsb.gov/news/press-releases/Pages/NR20260806.aspx · NTSB — B-767 Runway Excursion Investigative Update (DCA26MA352, Sept 9, 2026) → https://www.ntsb.gov/news/press-releases/Pages/NR20260909.aspx

🎬 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 — no names, no company, no blame. 📤 Forward this to a crew member who needs it today.

Please stay Safe & Hydrated!!!