Performance Report
Outcome first. Evidence on demand. The ride is already recorded. Review explains why it happened, what limited or unlocked performance, and the one thing to take into the next session.
What did this ride actually produce?
Actual first. Session opportunity and target second. No graph reading required.
How this jump was built and what it produced
Edge, pop, pop velocity, height, airtime and distance mapped into one jump story.
Waiting for selected jump evidence…
Opportunity. Execution. Result.
One visual chain joining the conditions, approach, aerodynamic opportunity, release and flight.
Apparent wind × jump height
Every mapped jump in the selected ride. This shows association, not causation.
Coach will separate a lack of opportunity from a failure to convert good opportunity before recommending a technical change.
What do these metrics mean?
Reading the gaps…
Reading your ride…
I’m joining your WOO evidence, conditions and goal into one clear coaching call.
Reading the largest gap…
What supports the coaching call?
Current-session evidence stays visible. Methodology and long-term sector analysis are collapsed until you ask for them.
Did more wind produce more height?
Select a recorded session and Coach maps each timed WOO jump to the BeachStats observations already captured by the 10-minute collector. A current BeachStats outage does not invalidate stored history; no fallback weather is ever substituted.
Did the wind change explain your jump height?
Wind and jump height on one shared timeline. The purpose is simple: did changing wind actually track changing jump height?
How close are you to your current performance envelope?
Each row shows what you achieved, what the ride gave you, and the selected goal. Landing is normalised correctly: lower G is better.
How stable is the signal?
Recent-session movement and the source behind the opportunity estimate. This tells you how much weight to put on the conclusion.
DEEP DIVE · MODEL & METHODMetrics, context, geometry and evidence method
Each metric keeps its real measurement. The bar shows achieved performance, the orange marker shows the session reference, and the goal line is the selected target.
What did the conditions actually give you?
The session reference uses the saved pre-ride prediction where it exists. Rider, equipment, wind, water and tack geometry stay separate so Coach can explain the gap without pretending every session offered the same ceiling.
Reading tack and wind geometry…
Conditions → Achieved → Next target.
What is measured, what is derived, and what is still a hypothesis.
WOO measures board-level jump height, airtime and landing G-force. WOO + smartwatch adds GPS context such as speed and jump distance.
WOO measurement documentation ↗Published kitesurfing research shows that height, airtime, take-off load and landing impact are related but they do not tell the same story. Coach therefore keeps boost performance and landing control separate.
Load analysis study ↗Goofy/regular stance × wind side is a BTE Coach hypothesis. It is displayed and tested against approach speed, jump distance and matched sessions; it does not become a fixed performance penalty without evidence.
LONGER-TERM CONDITIONSHistorical wind × height by tack sector
Historical wind-at-jump × height · split by tack sector
Coach uses each session’s recorded wind direction to place it into your normal tack sector, then maps each WOO jump time to persisted BeachStats wind speed. This avoids guessing tack from GPS and avoids using the suspect BeachStats direction field.
