Skip to main content

Same air. Same task. See where the race was really won.

GlideComp compares every track flown on the day — who climbed better, who glided smarter, whose decisions paid off — so you can see exactly what the fast pilots did differently and take it to the next comp. Scoring comes built in: GAP or open distance, in your browser, every point explained.

Browse competitions

Free · Scores and analysis are public — no account needed to read them

Pilot's GAP scores explained

GlideComp explains why your pilot scored the way they did. Distance points, time points, all explained in plain English.

  • Every start-cylinder crossing, and which one scored
  • The day's validity — how many points were on offer at all
  • Distance split into its linear and difficulty halves
  • Why the time points were zero
See a real comp's scores

Click any score to open that pilot's report card.

A whole pilot report card in GlideComp, scaled down: the flight's start-cylinder crossings and turnpoints beside a map of the task, then the day's validity, then distance, time, leading and arrival points each broken out with their arithmetic, down to the total
GAP & open-distance scoring
Field analysis across every pilot
IGC files from any instrument
XCTrack task import (.xctsk)
Public audit log
Nothing to install
For pilots

Everyone flew the same air. Why were they faster?

The scores tell you who won. GlideComp's analysis tells you what separated the field — by measuring every track flown on the task against every other one.

Line chart: minutes behind the fastest pilot at each of seven turnpoints. The leader runs flat along zero at the top, the next four are picked out in colour, and the rest of the field fans downward in grey with several lines stopping early.
Minutes behind the leader, turnpoint by turnpoint. Every pilot's race against the fastest one. Lines that stop early are pilots who landed out.
Heatmap: 32 pilots down the side in finishing order, 24 behavioural metrics across the top grouped by family, each cell shaded by percentile. The top rows are visibly darker across most columns.
Every pilot against every metric. Rows are pilots in finishing order, columns are the measures, darker is a better percentile. The dark band along the top is what winning looked like.
Scatter plot: each dot is a pilot, gliding speed on the horizontal axis from 38 to 72 km/h, finishing rank up the vertical axis with rank 1 at the top, and a fitted trend curve rising left to right.
Gliding speed against finishing rank. One dot per pilot. The strongest separator on this task: the pilots who glided faster between climbs finished ahead.
Height against time: a filled orange thermal-top line and a dashed pink cloud-base line, both climbing to about 3000 metres by mid-afternoon before the orange line drops away after 18:30.
Thermal top against cloud base. The working band through the day, from the weather model. The orange line falling away is the day shutting down.
Climb rate by hour: a median line around 1 to 2 metres per second with shaded percentile bands, start gates and the task deadline marked with vertical rules, and rows beneath showing takeoff times and climb counts.
How strong the climbs were, hour by hour. Measured from the field's own tracks, not a model — so you can see the day weakening under the pilots still on course.
Gantt-style chart: one row per task leg on a time axis. Each row has a pale bar spanning when the field flew that leg and a solid band inside it spanning the circling its wind was measured from, with an arrow for wind direction and a label giving speed and compass point.
What the wind did on each leg. The pale bar is the time when the field flew the leg. The solid band inside it is the circling that the wind was estimated from. On a leg that everyone glided, that band is very small.

From Corryong Cup 2026, Task 1 — 32 pilots. Names are shortened to letters here, in finishing order.

Climbing

Whether you out-climbed the pilots sharing your thermal, how long you took to find the core, how high in the day's band you topped out, and whether you left good lift or milked it until it died.

Gliding

Speed between climbs, glide angle against the rest of the field, how far you drifted off the course line, and whether you pushed harder when the next climb was stronger.

Decision-making

How low you were willing to go before committing to the next climb, the low saves you dug out, distance covered between thermals, and how much of the race you spent hunting.

Gaggle

Time spent flying with others, climbs you joined on someone else's marker, and how often going it alone actually paid off.

Race craft

How long after the gate opened you started, where race time went leg by leg, how far behind the leader you reached ESS, and what height you had left when you got there.

The day itself

Wind and climb strength hour by hour, drawn from the field's own tracks and read against the weather model — because half of what looks like skill is really the day you got.

Every metric is ranked by how strongly it actually separated the field that day, and checked across the comp's other tasks — so you can tell a real lesson from a quirk of one day's weather. Each pilot's score comes with the same treatment: a plain-English timeline of the flight, on the map and in 3D. See the report for Corryong Cup 2026, Task 1 →

For organisers & scorers

The scoring runs itself

No software to install, no spreadsheet to babysit, and nobody waiting on the scorer at the end of the day.

Set the task

Import or build the task in the browser, then share it — pilots scan a QR code to load it straight into XCTrack, Flyskyhy or SeeYou Navigator.

Pilots upload their own tracks

IGC from any instrument, submitted by the pilot or by you on their behalf. Scores recompute as tracks land, and every task page is public the moment it exists.

Every point explained

GAP to the CIVL formulas or a simple open-distance format, with penalties, corrections and task edits all recorded in a public audit log. Nobody has to take the numbers on trust.

?

Questions?

A browser. Sign in, create the competition, add a task, and share the link. Pilots upload their IGC tracks, and GlideComp scores them automatically. There is no software to install and no spreadsheet to maintain.

With the GAP formulas that FAI competitions use: distance, time and leading points. A new competition gets the official defaults, and you can change the advanced parameters when you need to. There is also an open-distance format for club XC days. The scoring guide explains both in detail.

Where your day went, against every pilot who flew the same task. GlideComp measures each pilot's climbing, gliding, decision-making, gaggle flying and race craft from the track logs. It then ranks those measures by how strongly they separated the field, so the report starts with what was important on the day. Read it beside your own report card, and you have something specific to work on before the next competition.

Anyone who follows the competition. A track submitted for scoring becomes part of the public record of that task. That record is what makes the comparison possible, and every pilot in the field accepts the same terms. A flight that you analyse privately, outside a competition, stays yours.

Not to follow a competition, because competitions, tasks and scores are public pages. To submit a track, sign in with Google or with a one-time code sent to your email. An organiser can also upload tracks for a pilot.

Yes. Tasks import and export as .xctsk, and waypoints download in standard formats. Pilots can scan a QR code to load the task or the waypoints directly into XCTrack, Flyskyhy, SeeYou Navigator and most other flight apps. Any instrument that produces an IGC file works for scoring.

Apply a penalty with a reason, and the scores recompute immediately. A public audit log records every change that can move a score: penalties, re-uploads and task edits. Pilots can therefore always see why the numbers changed.

GlideComp is free to use, and Tushar Pokle sponsors it. It is an open project, and the source is on GitHub.

Fly it, score it, learn from it

Create a competition, import your task, and have the standings — and the day's analysis — waiting before the retrieve gets back.

See a sample comp

Free · Sign in with Google