You may have noticed on Strava that there is quite an extensive list of Sports into which activities can be categorised. Here, for no reason other than curiosity, is a chart showing relatively how many of each activity we have on Crickles:
Since the number of activities in each Sport ranges from Rides, which is in six figures, down to Handcycles, for which we only have one, I’ve used a log scale.
Cardiac Stress Score can be calculated for any of these Sports in which a heart rate monitor is used (and estimated imprecisely even if one isn’t).
UPDATE: the algorithm for calculating CSS in the absence of heart rate data has been significantly enhanced since the time of writing.
I think most of us reflect on what we have achieved in the past year. For me, it’s been a mixed year with regards to exercise. I did my first sprint and Olympic distance triathlons. I completed my first marathon for 16 years (I only ran one before) – in just under 4 hours.
But I didn’t get my sub 20 minute 5K time. Close at 20:38. And my cycling went to pieces with the focus on running.
Just recently I spent some time looking at my run data on Crickles. Taking a few of the runs I plotted out the relationship between heart rate, speed and gradient. It’s a bit messy (although I have some ideas to tidy that), but the curve/surface is quite interesting. I plotted the curves initially to help statistically create a normal range for my running conditions, with a longer term view to help track abnormal heart rates for a given situation.
I then limited the curve to gradients of +/- 2 degrees gradient initially. And I was struck by what it showed, but not entirely surprised.
As I start to run my heart rate speeds up. No great insights there. There is then a plateau until just over 11Km/h. That fits with what I experience. I know from my Garmin that up to 11-11.5Km/h I can sustain. It’s comfortable. My legs wear out first.
Go too much above that speed and everything becomes harder. That is my lactate threshold for running. That’s where the pain starts and I have to breathe harder to clear the carbon dioxide generated by lactic acid in the muscles from my system. They have to work anaerobically at these sorts of speeds.
The curve kicks up again just over 14Km/h. That’s the respiratory compensation point. Beyond that I can’t clear the lactic acid from my system by breathing and I am on borrowed time.
And that is why I can’t do a 5K in under 20 minutes yet. Sometimes you hit psychological blocks as a runner. I have watched my son streak away in the last few months having joined a running club. He was stuck, probably because of his brain, but his heart rate data suggested he could run much faster. And they unlocked that speed in him. But I am stuck by physiology at the moment.
So, I’ll be sprinting and running up hills in the new year. And working on some algorithms to track my progress. My Garmin says I can do sub 20. I know I can’t. Yet.
Have a great Xmas. And good luck for 2018.
Let us know your goals and what you want to see from the site.
There is a new feature on the Navigator for everyone on the BETA programme: you can now see your current training zones. The tab structure has been changed slightly so that when you’re not logged in the tab bar now looks like this:
Notice in particular the MORE option on the right. When you choose this you get the log-in screen that takes your BETA programme password screen. When you log in, the tab bar changes to this:
You can see that the HR Zones and Regularity tabs have appeared and I’ve selected the HR Zones tab. This shows my current training zones as calculated from the Crickles estimate of my current Lactate Threshold Heart Rate (LTHR). It also shows the date at which the zones were last changed – such changes are triggered from time to time in response to athlete activity data.
If you don’t yet have a BETA log in and would like one, please read this post and then, if you’re happy to proceed, send me an email requesting a password along with your date of birth.
Separately from the BETA programme, the standard Seasonal tab has also changed: Zone 5 was previously spilt into Z5a, Z5b and Z5c. These have now been consolidated for easier zone-to-zone and quarter-to-quarter comparisons:
The Relative CSS report – which is at the time of writing is the landing page on the Navigator – shows how the chosen athlete’s totalled Cardiac Stress accrued over the period defined by the Date range compares with others. This total CSS is a product of three factors:
The number of activities
The duration of each activity
The cardiac intensity of each activity.
The first of these is straightforward. Information on items 2 and 3 is available on the Relative profile report. Here’s how it now looks:
In this case “Athlete” is me. The chart on the left shows how the duration of my activities over the chosen period (the last six weeks) compares with that of others, with the y-axis being scaled in hours. I’m in green. The widest part comes at about half an hour, indicating that more of my activities have been of this duration than any other. By contrast, other athletes – the blue shape – are doing a far greater proportion of their activities over a period of 1-2 hours. Unlike others, I have no activities – zero width – around the two hour mark over this period.
It’s important to note that the number of activities (item 1 on the list of three factors above) is not reflected here at all – from this chart alone it’s impossible to know whether I’m doing three times as many or half as many total hours as others. This only shows the proportion of activities at each duration.
The chart on the right shows the distribution of cardiac intensity. Again, the chosen athlete (me again) is in green and others are in blue. From this I can see that for me the widest part – the intensity at which I most frequently exercised – is at about 87% whereas for others it lies at about 82%. On the other hand, some other athletes have exercised at over 100% intensity in this period and I haven’t. (100% is not a magic value – you can think of it, approximately, as exercising at or above your established Lactate Threshold Heart Rate.)
Like most of the reports on the Navigator, it responds to your choices for Athlete, Date range and Group – Group defines who is counted as “Others”.
This form of chart is likely to be unfamiliar to most people. However, compared to the old visualisation, it more clearly shows the relative distributions and has less risk of misleading at the extremes. Once you get used to it, it’s an intuitive plot that conveys its information nicely.
Following some early feedback from the Beta, a couple of new features have been added to the Navigator.
First, to make the Navigator quicker and easier to find, there’s a new big green button on the home page of this website:
(Depending upon your browser, you can probably see the picture of the buttons above as well as the actual buttons.) Old School access is still, of course, available using the web address navigator.crickles.org.
Second, when you’re using the Navigator there is now a small block of help text pertaining to each report. As in this example, this appears in the side panel and changes according to the tab that you’re looking at (in this case Fit-Fat):
General help on the use of the Navigator, such as how to reset the Date range quickly, is still available here.
You may have noticed recently that there is a new report on the Navigator that requires a password, and that a few of the posts on this website are now password protected. This reflects some significant changes to Crickles that are being released initially in a BETA programme. If you’d like to participate and check out the new features please read on…
To access the BETA functionality
Send an email requesting access to email@example.com.
I will need your Date of Birth – this will enable us to factor in age into the new analysis.
This aside, you are only asked to agree to:
Accepting the confidentiality terms;
Giving me feedback;
Acknowledging the limitations of the beta.
This is all described further in the Mechanics of the beta section below.
Please do try it out!
Here’s what’s in the beta:
More analysis of heart rate data
One of the main features of the BETA is a new Regularity report. This gives a new type of analysis on your heart rate data. It also gives some analysis on the “strap crap” that is filtered out by the Crickles data cleaning routines.
For those on the programme, a full description is available here.
Just your data
To date, all of the analysis on the Navigator has been available to everyone on an “all see all” basis. The new report is potentially more confidential in character and so each athlete can see only his or her own data. This is why we now require a password to access that report. In future, we may password-protect more information, such as FTP curves – subject to what people would prefer. However, peer comparisons are super-useful and we’ll keep these as a prominent feature.
To date, you can compare yourself to others using the Group dropdown. However, apart from the gender sub-selection that this offers, this isn’t useful for most of the Crickles population. On the beta, once you’re logged in you can now choose Strava Friends from the Group dropdown. This then enables you to compare yourself specifically against your Strava friends on the relevant reports (Relative CSS, Relative Profile, All-in and This week). This is much more meaningful – and you can still compare yourself to the overall Crickles cohort and your gender group.
Mechanics of the beta
Please email me as above to request a password. All passwords are encrypted in use and cannot be hacked in plain from a web server. However your password is not encrypted “in flight” when I send it to you. If you are concerned about security I can text you your password instead of emailing it, and if you’re very worried I can give it you by phone.
At this stage I haven’t built a mechanism for you to choose or re-set your own password. Also, the password setting process is still manual and it may take me a while to get round to sending out yours if a lot of people ask for them.
As far as I’m aware, this new analysis, and indeed some of the existing analysis, is unique and unavailable anywhere else. While I’m continuing to develop it, please treat it as commercially sensitive – for example, don’t email Strava describing it and asking for them to copy it!
To log in, choose the Regularity report, which will throw the log-in screen (unless you’re already logged in). The User ID you need is simply your Strava ID (e.g. mine is 301194). You can see this on the Athlete dropdown in brackets. Once you’ve logged in you’ll be returned to the main page (Relative CSS) and will need to choose Regularity again to see it.
While this functionality is still in beta, you can always escape back to the current way that the Navigator works by refreshing the page. This will log you out. On Safari at least, the browser caches your ID and password so you don’t need to re-enter them. The iPhone doesn’t do this – when we move beyond beta I intend to build this into Crickles so that you will rarely need to re-enter your credentials.
You will also get a general-purpose password for accessing the protected posts on crickles.org.
If you sign up to try out the beta, please could you give me feedback on the new features. It would also be super-helpful to know:
what you use Crickles for;
what you never use;
roughly how often you look at the Navigator;
whether you ever use Crickles Activity Charts;
what further improvements would make Crickles most helpful.
A couple of weeks ago Cardio Mark ran the Dublin marathon in a very creditable time of under four hours. I’m impressed. When I used to run regularly, I once or twice managed half marathon distance and I never finished wishing I’d done twice as much. Completing a marathon requires months of training and resolute determination.
A couple of days before Mark’s marathon I went for a bike ride. I had the day to myself so cycled over to Dunkery Beacon – the highest point in South West England and the region’s signature bike climb. It’s not the longest climb and not the absolute steepest but its combination of length and severity is nonetheless testing. The rest of my ride was not without interest, extending to 93 miles with 7.5k feet of ascent and taking me around 6:40 with a couple of stops. It was equivalent in difficulty to a reasonably stiff domestic sportive. Fit cyclists do not need to train for such sportives – they’re easy enough that you can just rock up and do them.
Out of curiosity, I compared Mark’s marathon with my bike ride using Crickles Activity Charts. Charting a histogram of our heart rates gives this, with Mark’s histogram in pink lying over mine in blue:
On the morning of my ride my resting heart rate was 46 bpm, which is marginally above Mark’s (44 bpm). Crickles shows our prevailing Lactate Threshold Heart Rates to be similar too (mine was 162 bpm and Mark’s was 157 bpm). The chart thus shows that not only did Mark record far fewer beats during his marathon than I did during my ride, he also managed his effort much more prudently with the entirety of his cardiac activity well under his LTHR in contrast to my ride in which I was well over my LTHR for a significant portion of the time. It is graphically evident that my ride placed a much greater load on my heart than Mark’s marathon placed on his. This is reflected in our respective Cardiac Stress Scores – 570 for me and 300 for Mark. (Reflecting on this, I realised that the Crickles CSS methodology does not fully capture the restorative effect of my two coffee stops. I calculated the effect of these and it decreases my CSS by 17 points – just under 3%, so not a significant amount.)
By contrast, the differences in our Suffer Scores on Strava was much narrower – Mark’s Suffer Score was 255 compared to my 299. This confirms my previous finding that the Strava Suffer Score is not a good measure of cardiac stress.
There is an important point here for cyclists. Mark’s marathon felt hard and was hard because of the intense amount of corporeal stress that running for four hours places on the body. Skeletal muscle and the bones, ligaments and tendons to which it is attached, can feel the pain. There is also that intangible of “the wall” as it is harder to refuel adequately when running. Cycling inflicts far less strain on skeletal muscle and doesn’t pound our body in the same way. Unlike our peripheral muscles, our exercising heart does not feel pain and we thus have no direct real-time index of the stress to which we subject it. So long as we ride within our strength limits and eat and drink well, the wall of bodily pain that marathon runners have to run through has no analogy in cycling and there is nothing to indicate how much cardiac stress we’re accruing. The only direct evidence that our sportive was equivalent in cardiac stress to two marathons might be a histogram or a CSS number. An appreciation of this might spur us to think more seriously about the amount of recovery we need to build into our exercise schedule.
I have updated this post now. Previously I just attached the word file – time constraints. But today I have some time, so here goes. As far as I can tell, this is the most complete analysis of the data that exists to date.
A search using the term “Marathon” and “Death” or “Mortality” on Pubmed yielded 167 references (most recently performed 20/10/17). The abstracts of these were reviewed. The reference lists of the final articles included in this paper were scanned for further relevant literature and review articles were obtained and read and their reference lists reviewed. On-line web searches and direct approaches to authors were made to provide additional data.
The End-Note library can be found here. It does not include the texts of some of the papers which were behind pay-walls.
A total of 8 papers were included in the final analysis. The papers can be divided into two categories. The first category comprises a series of papers which looked broadly at hundreds of marathons run across the USA over the past 40 years. The second category comprises a number of papers that have focused on two marathons in the USA – The Marine Corps Marathon and the Twin Cities Marathon – and also the London Marathon.
I have not included results relevant to half marathons or ultra-marathons or other events, such as triathlons, except where indicated in the text. Furthermore, I have not included mortality from marathons run as part of an event, such as a triathlon.
There have been a number of efforts to collect data from a larger number of marathons that have been staged across America. It is probable that the data from these papers overlaps. Furthermore, it is more likely that deaths will be missed compared with the studies which have focused on specific marathons, and therefore these papers have the potential to underestimate the true fatality rate.
Redelmeier et al. 20071
Redelmeier and Greenwald published an analysis of 26 marathons and their related deaths, staged in the USA, which they followed for up to 30 years. The principal focus of the paper was to compare the number of marathon deaths with the expected number of motor vehicle fatalities to determine whether running a marathon was safer than not running one.
The authors screened the 328 American marathons listed in Runner’s World on 01/01/2005. They excluded those with less than 20 years of data, fewer than 1000 participants annually, or those that were located primarily on off-road trails or that were part of triathlons or other combined endurance events. They selected 26 marathons randomly from the remainder. Note that the Marine Corps data is included in this analysis.
Data on “sudden cardiac deaths” was obtained from local newspapers on the days after each marathon. Race directors were contacted.
A total of 3,292,268 participants were included in the analysis. There were 26 “sudden cardiac deaths”. 15 marathons had no death, 6 had one death, and 5 had more than one (Boston, New York, Chicago, Honolulu and the Marine Corps Marathon). New York had 2 deaths in 1994.
The average age of the fatalities was 41 years. 81% (21) of those who died were men. 5 deaths occurred in people who had completed a marathon before.
There were autopsy results on 24; 21 had coronary artery disease. Coronary anomalies were noted in 2. Electrolyte abnormalities were thought to be significant in 4 and heat stroke in 1. Most died within a mile of the finish line (Figures 1a and 1b).
The overall risk of a fatality, as estimated by this paper was 0.79/100,000 or 1 death for every 126,626 finishers.
Figure 1a. Location of Fatalities, Redelmeier et al. 2007
Figure 1b. Location of Fatalities, Redelmeier et al. 2007
Mathews et al. 20122
Using publically available racing (MarathonGuide.com, Athlinks, and The Association of Road Racing Statisticians) and news (Google, LexisNexis) databases and by directly contacting race organisers, the authors collected statistics on marathon finishers and deaths between 2000 and 2009. Data was cross-referenced with MarathonGuide.com.
The denominator – the numbers completing marathons during the 10-year period – was 3,718,336. There were 2,255,060 men who completed a marathon and 1,463,276 women.
They identified 28 people who died during the race or within 24 hours of finishing. 6 women and 22 men died. The male death rate was 0.98/100,000 and the female death rate was 0.41/100,000. The overall death rate was 0.75/100,000.
The median age of death was 41.5 years (IQR 25.5, range 22-68).
14 deaths occurred in people over the age of 45. 13 of those deaths were caused by atherosclerosis (Table 1). In younger racers, none of the deaths were caused by cardiovascular disease.
The median distance travelled before dying was 22.5 miles (IQR 10.6). 7 completed the marathon before dying. 18 deaths occurred after mile 20. Cardiac and cardiovascular aetiologies accounted for 24/28 deaths.
People were more likely to die in October marathons (n=11); 27% of marathon participants raced in October. This was of no consolation to myself when I ran the Dublin Marathon, in October, aged 47.
Table 1. Cause of Death, Mathews et al. 2012
Kim et al. 20123
In 2012, a study by Kim et al was published in the New England Journal of Medicine. They looked at cardiac arrests that occurred whilst running or within an hour of running a marathon or half marathon. I have not reported the ½ marathon data.
The database of cardiac arrests was compiled prospectively from Jan 1st 2000 to 31st May 2010 – a slightly different time period to Mathews et al. The arrests were cross referenced using LexisNexis and Google. Further searches were performed directed at particular race events and their local newspapers. Contact was also made with race officials. Cases of cardiac arrest were retained for the final analysis if they were identified in 3 separate data sources or confirmed with race staff. The next of kin of those who died were written to asking for further data about exercise history and family history and asking for consent to access medical data.
Running USA compiled statistics for participation (not finishers) rates in marathons or half-marathons in the USA. It was estimated that 3,949,000 people participated in a marathon, and 6,922,000 participated in a half marathon.
59 cardiac arrests were identified, 40 in marathons and 19 in half marathons. The incidence of cardiac arrest was 1.01/100,000 in marathons. 51 of the 59 people who arrested were male. 34 of the 40 arrests in marathons were in men. Male marathon participants had a rate of cardiac arrest of 1.41/100,000. The mean age of those who arrested was 42±13 years.
42 of the 59 died. The mean age of those who died was 39±9 years. The death rate was 0.63/100,000 during marathons (n=25) and 0.25/100,000 (n=17) during half-marathons. Overall men were more likely to die than women (0.62/100,000 vs. 0.14/100,000) during marathons and half-marathons.
Most arrests occurred in the latter quartile of the race (Figure 2). The data was not separated by race type or by mortality.
Hypertrophic cardiomyopathy was the most common underlying diagnosis overall. In those who survived, coronary disease was more common.
It was recognised that the method of ascertainment of cardiac arrests may have missed some cases, and therefore, the true rates of cardiac arrest and death may be higher. Complete clinical data was missing on approximately 50% of the cases. It was also recognised that the participants may have run multiple marathons, and therefore the total number of unique participants, would have been lower.
Figure 2. Location of Cardiac Arrests, Kim et al. 2012
Webner et al. 20124
In 2009 this group sent 33 item surveys to 400 race directors of US Marathons to ask about the number of marathon participants and associated deaths. 88 (22%) returned the surveys. The marathons were run between 1976 and 2009.
There were a total of 1,710,052 runners. Races had between 30 and 30,000 participants. 30 arrests and 10 deaths were reported. The risk of death was therefore 1 in 171,005, or 0.58/100,000. The cause of death was coronary artery disease in 7. One person had an anomalous coronary artery. The cause of death was not established in 2 cases. 28 of the 30 runners who arrested were male. The mean age of those who arrested was 49.7 years. The mean age and sex distribution of those who died was not specified in the paper.
The location of the arrests was again skewed towards the final miles of the marathon (Figure 3).
There were more participants in this paper, and one less death, than reported when the abstract was presented in abstract form in 2011. Discrepancies between abstracts and final papers are common as the peer review process often picks up errors.
Figure 3. Location of Cardiac Arrests, Webner et al. 2012
These papers can be brought together. It is clear that the typical person who arrests is a middle-aged male around 40 years old. The cause of death is often considered to be coronary artery disease. Typically, cardiac arrest and death occurs in the latter quartile of the race.
The risk of death estimated by these studies was approximately 0.70 per 100,000 finishers, that is 1 death per 142,000 participants (Table 2).
Table 2. Risk of Death During Marathons
Of the two studies that reported marathon deaths by sex, that is Redelmeier et al. and Mathews et al, there were 43 males (80%) who died and 11 females (20%). Mathews et al. reported the breakdown of participants by sex in addition. In that study there were 22 men who died and 6 women. The rate of male deaths was 0.98/100,000 (1 per 102,503) vs. 0.41/100,000 (1 per 243,879) in females (Table 3).
Table 3. Risk of Death by Sex
If further data was available from the papers, more accurate estimates could be made.
The Marine Corps Marathon and the Twin Cities Marathons
A number of papers have been published by the medical team associated with two marathons in the USA: The Marine Corps Marathon (MCM), held in Washington DC and the Twin Cities Marathon (TCM) in Minneapolis. Three papers have been published over the years, looking at data from these two marathons. All are freely available online.
Maron et al. 19965
This paper focused on the MCM from 1976-1994 and the TCM from 1982-1994. All deaths were included. The data is reproduced in table 4.
215,413 runners successfully completed the marathons during this time. 4 sudden deaths occurred during (n=3) or shortly after (15 minutes, n=1) completion of the marathon. 3 were male and 1 was female. The 3 men had coronary disease, the 1 woman an anomalous coronary artery. The one woman died in 1990 in the MCM, aged 19. One man died in the TCM in 1989, aged 40. Two men died in 1986 and 1993 in the MCM, aged 32 and 58 respectively.
Table 4. Maron et al. 1996
Roberts et al. 20006
This paper looked at the 81,277 entrants in the TCM from 1982 to 1994. It therefore contains no new information over and above that of Maron et al. 1996 with regards to deaths.
Its focus was describing all medical issues experienced by marathon runners. For interest medical encounter rates were 25.3/1,000.
Of note, it was stated that 60,757 finished the course – slightly different to the 60,379 from the 1996 paper. There were 48,330 male finishers and 12,427 females. There appears to be a further typographical error in the text, and this number is derived from the table reproduced below (Table 5).
Table 5. Roberts et al. 2000
Updating the data from 1996 yields the following (Table 6):
Table 6. Combination of Maron et al. 1996 and Roberts et al. 2000
Roberts et al. 20137
This paper used data from the two marathons between 1982 and 2009. 1982 was chosen, as data was reported by sex from that year onwards.
The paper reported that there were 540,892 finishers during the study period. 379,863 were male and 168,227 were female.
In total 14 runners collapsed suddenly. 7 were successfully resuscitated. There were 7 sudden cardiac deaths. There was still only 1 female fatality (age 19, anomalous coronary artery, 1990, MCM). The rest who died were male. The underlying diagnosis for all men was coronary artery disease. The mean age of the men was 48 years. The location of the collapse was on average at 16 miles.
The rate of death overall was 1/78,299 finishers or 1.28/100,000. In men the rate was 1/63,311 finishers (1.58/100,000) whereas in women it was lower at 1/68,227 (0.59/100,000).
Details of the deaths are as follows (Table 7).
Table 7. Details of Deaths. Roberts et al. 2013
The Marine Corps Marathon have now published data on their website of the number of finishers since the race began in 1976. It can be found here, and is reproduced in table 8.
Table 8. Marine Corps Marathon Finishers
This allows for a combination of all of the papers, leading to a final estimate of risk:
Between 1982 and 2009 there were 540,892 finishers. From 1976 to 1981 a further 26,387 completed the MCM. The total finishers of the two races from their inception (MCM 1976, TCM 1982) to 2009 was therefore 567,279. There were 7 deaths in that time. The rate of death, therefore, was 1.23/100,000 finishers, or 1 death for every 81,039 finishers.
The London Marathon
Dan Tunstall-Pedoe was the London Marathon Medical Director between 1981 and 2006. He presented data on the first 26 London Marathons in 2007.7
In the paper, data was obtained from St John’s ambulance, receiving hospitals and the coroner. The paper stated that there were a total of 650,000 finishers. A total of 8 deaths were recorded in this time.
The first death was in 1990, and ascribed to hypertrophic cardiomyopathy (HCM). In 2001 and 2005 there were two further deaths from HCM. Deaths in 1993, 1995, 1996, 1997 and 2003 were ascribed to ischaemic heart disease.
This yielded a crude rate of death of 1/81,250 (1.23/100,000).
There is also corroborative data online, written by him and published at Peak Performance with data up to and including 2003. The data there is slightly different. HCM deaths were reported as occurring in 1990 and 2001 – as above. 5 deaths from ischaemic heart disease were reported as occurring in 1991, 1994, 1995, 1997 and 2003. This was the same number of deaths as in the published paper over the same timeframe. Data was published on the number of finishers up until 2003. This yielded a death rate of 1/67,414 (1.48/100,000).
An online search to determine the number of finishers yielded data from additional sites. There are race reports, hosted on the London Marathon website, which mention the number of finishers in the very early races. Wikipedia provides data on the first London Marathon. Marathonguide.com has data on the number of London Marathon finishers. I also searched the London Evening Standard and BBC News Websites. Combining the data from these sources yields the following table (Table 9). All the data is from marathonguide.com unless otherwise specified.
I also emailed Professor Sanjay Sharma, the current director of the London Marathon, who was kind enough to respond directly. He stated that there have been 14 deaths.
As of 2017 over 1,000,000 people had completed the London Marathon (1,038,733). This yields a death rate of 1/74,105 or 1.35/100,000. I look forward to seeing a more detailed paper from Professor Sharma with confirmed finishing statistics and further medical details, including the age and sex, of those who died.
Table 9 summarises the data as far as is possible.
4 Tunstall-Pedoe D. Marathon Cardiac Deaths. Sports Med 2007;37:448-50.
HCM Death from hypertrophic cardiomyopathy
IHD Death from ischaemic heart disease
These two sets of data can be drawn together, yielding a death rate of 1/76,477 finishers or 1.31 deaths/100,000 finishers. The two separate marathons have strikingly similar results (Table 10). The rates of death are higher than those ascertained by more general surveys, as would be predicted as the authors were directly linked with providing medical support to the marathons over many years.
Table 10. Mortality During Specific Marathons
Men around the age of 40 are the most likely to die participating in a marathon. Death typically occurs in the latter stages of the marathon, and is often caused by previously undiagnosed ischaemic heart disease, although hypertrophic cardiomyopathy and increasingly heat stroke are also concerns.
Different methodologies have yielded conflicting estimates of the death rates during marathons. Large surveys of multiple marathons have suggested that the death rate is 0.70/100,000 finishers. Detailed studies of a small number of events has suggested the rate is higher at 1.31/100,000 finishers.
As always, the truth is somewhere in between. But what is clear is that the chances of dying during a marathon are very low.
The data are frustrating. The authors of the papers almost certainly have some further data, not included in the publications that could facilitate a more formal meta-analysis.
What is needed, however, is a prospective registry of entrants / finishers and medical events from race directors. It would help understand what the true extent of the problems are. It would help concentrate medical expertise and help train event professionals to deal with the most common scenarios.
How to screen for these problems in advance? An ECG can be helpful and is often advised, but does not reliably pick up either ischaemic heart disease or hypertrophic cardiomyopathy. An echocardiogram can diagnose hypertrophic cardiomyopathy reliably. A cardiac CT can pick up asymptomatic coronary disease. Judging from the lack of symptoms and training, an exercise tolerance test or stress-echocardiogram is likely to be falsely reassuring. But that is a lot of testing to prevent a rare event. It’s not cost effective, and can probably not be supported by the NHS in the UK, at least.
The Crickles Navigator has a new Summary tab giving headline figures for the athlete and a comparison of each with peers. Currently, there are six figures shown in the Value column:
Period CSS shows the total Cardiac Stress Score for the period defined by the Date range. This period defaults to the last six weeks but can easily be changed in the side panel.
Period XSS extends this measure to cover also activities on Strava for which there is no heart rate data. The estimate of cardiac stress is less good than CSS, which requires a heart rate monitor, but better than assuming that it’s zero. If you always wear a heart rate monitor CSS and XSS will be equal (though not for the peer group). If you never wear a heart rate monitor, CSS will always be zero but XSS will usually be positive.
Current LTHR is the latest Crickles estimate of your Lactate Threshold Heart Rate. (Occasionally this estimate may lag one activity behind your last effort.) This only appears if you use a heart rate monitor.
Current Fitness, Fatigue and Form are as described here. Since they are current estimate, neither these values nor Current LTHR change as you change the Date Range.
The numbers alongside these in the Crickles Percentile column show how you compare to the Group chosen in the side panel (by default, the entire Crickles population). If the Crickles Percentile is 100 you have the highest value. If the Crickles Percentile is 50 you’re on the median.
By design, this tab works particularly well on the iPhone.
Over time, we may add more information to this tab.
NB: There is a known bug that the Summary tab will be totally blank (i.e. no data) if you have included the character “(” in your Strava name. If this affects you and you’re interested in seeing your Summary data before I otherwise get round to fixing it, please let me know!