A quick note before we start: The Safety Layer moves to a weekly cadence starting now. Same depth, tighter interval — more signal, less lag between events and analysis.
On July 2, the National Transportation Safety Board released its preliminary report on the June 14 crash of a Pacific Aerospace 750XL skydiving aircraft at Butler Memorial Airport, Missouri. Eleven skydivers and one pilot died when the aircraft lost control moments after takeoff and crashed nose-first into a field.
The findings come from the NTSB’s preliminary report — the first factual snapshot released within weeks of an accident, designed to document evidence, not assign cause.
What the report found is more interesting than what it didn't.
No pre-impact mechanical malfunction. No failure in the engine components that would have prevented normal operation. In fact, investigators concluded the engine was producing power at the time of impact. Fuel samples were clean — no sediment, no debris. The aircraft met weight and balance limits. Weather was clear, winds light. The pilot had over 4,100 hours, two consecutive jump seasons with the operator, and no prior concerns flagged by the company.
Jeff Guzzetti put it plainly: "I was surprised that they had determined that the engine was producing power. Initially I thought it smacked of a potential engine problem."
That surprise is the story.
When the obvious mechanical explanation gets ruled out this early, the investigation doesn't get simpler. It gets harder — and it shifts toward the aircraft's loading, the pilot's decisions in the seconds after rotation, or something in the operational rhythm of a high-tempo skydiving day that doesn't show up in a maintenance log.
"When you have eliminated the impossible, whatever remains, however improbable, must be the truth."
That's not just detective fiction. It's how modern accident investigation actually works — the probable cause narrows through subtraction, not discovery.
This was the aircraft's third flight of the morning. Two successful jumps already completed — one at 9:20am, one at 10:32am. Refueled at 10:55am. Airborne again at 11:25am. Witnesses reported the aircraft made a left turn shortly after takeoff, lost altitude, and went down near the airport boundary.
None of that appears in the "probable cause" section yet — because there isn't one. A final report is 12 to 18 months out. But the preliminary findings already tell us where the answer isn't. And in aviation safety, elimination is often the first real signal you get.
The temptation here — for press, for forums, for anyone writing about this — is to wait for the final report and stay quiet until then.
That's a mistake.
The pattern of what's been ruled out is itself worth examining now, because it points toward exactly the kind of factors that don't make headlines: cumulative operational tempo, informal loading practices, and decision-making under the quiet pressure of "we've done this three times already today."
Next week: what "no mechanical failure" usually points to — and why this isn't the first time we've been here.
NTSB press release here
If this reached you as a forward, you’re seeing The Safety Layer out of sequence.
It runs weekly — one signal at a time.
#AviationSafety #AirSafety #Investigation #SafetyCulture