Two Miles Without Data: Mass Marathons and the Cardiac Screening Gap

Two miles. The distance between mile 18 and mile 20 of the Portland Marathon, or 3.2 kilometers. At mile 18, Trey Lara stopped to kiss his wife. At mile 20, he collapsed. Between those two markers there is no published split, no average pace, no heart-rate data. Only a 3.2-kilometer gap, and behind it a 25-year-old man who never finished.

I read the story several times, not to find more emotion — I leave that part to the fans. I read it to find a number. And the first thing I noticed: the boundary of the race is also the boundary where medical data begins. The day football stopped, I started counting steps again — steps with no referee, no official record, only a body and a watch.

Context: a mass-participation race

The Portland Marathon is a mass-participation event. This must be settled before anything else, because it decides how we read the whole story. There is no qualifying standard, no national ranking, no selection. Anyone who registers can run.

Trey Lara was a young pastor who ran to relax and relieve stress. He trained for many months before race day. He died just days before his 25th birthday. The organizer, Motiv Sports, with executive director Crystian Kumnick, confirmed a medical emergency but declined to give athlete-specific details. A community GoFundMe raised about 60,000 USD.

The frame of reference here is public health, not performance. And I write about it that way.

Three layers of data, only one measurable

This case has three layers of data, and only one is truly measurable.

The first is location: mile 18, mile 20. These are spatial markers, not performance markers. The second is the stated cause — sudden cardiac arrest. That is the media's and the family's wording, not a coroner's finding. The third — the one I need most — is entirely absent: no split, no pace, no heart rate. Without those three, any judgment about whether the runner pushed too hard or paced correctly is speculation.

But that absence is itself data. The final third of a marathon is where cumulative cardiac and thermal load peaks. The runner collapsed at mile 20, after an interaction at mile 18 — right as he entered that segment. Over years of building pressing indices for football teams before moving into athletics, I learned one thing: what breaks a person is usually cumulative load, not a single moment.

Age 25 is the most important variable, and it reverses how we read the case.

For runners over 40, sudden death in endurance running is usually tied to atherosclerotic coronary disease. For a 25-year-old, the suspect list sits in the structural or electrical disorder group: hypertrophic cardiomyopathy, congenital coronary anomalies, ion-channel disorders such as long-QT or CPVT, or myocarditis. These conditions share one trait: silent until they cause a fatal event, and undetectable by a routine physical.

The American Heart Association distinguishes cardiac arrest from myocardial infarction. Cardiac arrest is loss of heart function from an electrical rhythm disturbance; myocardial infarction is blocked blood flow to the heart muscle. The article's citation of this definition suggests the suspicion leans toward an electrical mechanism, not a heart attack in the ordinary sense.

There is another cause group the original piece does not mention, but which a data person must put on the exclusion list: exercise-associated hyponatremia, caused by drinking too much fluid during endurance running, can also cause collapse and cardiac arrest. And post-viral myocarditis is a leading cause of sudden death in young adults. I raise these as hypotheses to be excluded, not as assertions.

The estimated rate of sudden death in marathon running is about 0.5 to 1 per 100,000 participants. A small rate. But when the number of mass-race entrants grows faster than the medical screening infrastructure, that small rate multiplies into a large problem.

Blind spot: correlation is not causation

This is the part I want to say plainly, even when it is not easy to hear.

The family says Lara was completely healthy, with no underlying disease. That is lay testimony, not medical evidence. The original article itself placed a caveat beside those words: this is not yet a conclusion ruling out hidden cardiac abnormalities. I respect that caveat. And I must also note: many congenital and electrical heart conditions are asymptomatic, undetectable by a general check-up.

The kiss at mile 18 is the detail that made the story spread. I understand why. But as an analyst, I must separate two layers: the emotional layer that drives sharing, and the systemic layer that is the real subject. Recreational runners typically step to the start line without an ECG, without an echocardiogram, without a stress test. Not because they are careless, but because the system does not require it.

The organizer's confirmation of an emergency, followed by silence on individual detail, is standard privacy practice. I do not read that silence as a sign of fault. But it also means an independent safety review is difficult: medical-station density, spacing between points, AED response time — all fall in an undisclosed zone. In out-of-hospital cardiac arrest, response time is often the decisive variable between life and death. Without knowing that time, we cannot say the system was enough or lacking.

People call me a data monk. A monk needs no cathedral — only the truth. And the reality here: we lack the data to conclude, but we do not lack the data to act.

Signals for the next cycle

Four signals I will track. One: the coroner's official cause-of-death finding, to distinguish structural disease, electrical disorder, or another cause. Two: any change in the organizer's medical protocol and AED density. Three: official confirmation of the race date and course, to settle the October 4 detail. Four: discussions on whether cardiac screening should be mandatory before endurance race entry.

One death does not create a trend. But it creates a data point, and that data point points at a real gap. Data is a mirror. Most of the market looks into it and sees only itself. I look in and see a question no one wants to answer: when the mass-marathon wave runs faster than the system protecting it, who will slow down first?