The coach

Why "Glidepath".

I flew helicopters in the Army. Before any approach, you plan the glidepath: a stabilized, pre-computed descent to the runway, flown by reference to instruments, with decision points where you either continue or go around. You do not improvise the last 500 feet.

A training block is the same object. Race day is the runway. The block is the stabilized approach: planned in advance, flown off data, corrected early and in small increments, with honest decision points where the plan changes because the numbers say so. Athletes who improvise the final weeks before a race get the same outcome as pilots who improvise final approach.

[Coach bio placeholder: military background, the path into ultra and Hyrox racing, and why coaching became the job.]

The method

Named frameworks, not vibes.

Every metric in my coaching traces to a published framework. If I cannot tell you where a number comes from, it does not get to make decisions about your training.

Banister performance model (PMC)

Fitness, fatigue, and form modeled from your training load over time. It is how we see a peak coming instead of hoping for one.

Coggan training stress (TSS)

Each session scored for the stress it actually imposed, so a brutal hour and an easy hour stop counting the same.

Seiler 80/20 distribution

Most of your running easy, the hard work genuinely hard. Your time-in-zone gets measured against this, not guessed at.

Foster monotony and strain

Repetitive moderate training is a documented path to staleness and injury. Monotony gets tracked so variety is engineered in.

Skin in the game

My own race calendar.

I train and race on the exact system my athletes use. Same analytics, same block PDFs, same honesty when the data is unflattering.

DateRaceFormatStatus
[Month 2026][Ultra race name][Distance] mi trail ultraUpcoming
[Month 2026][Hyrox event name]Hyrox openUpcoming
[Past date][Past race name][Format][Result placeholder]
Work with me

If the method makes sense to you, apply.