VyCurve Climb performance & awareness

Climbs, departures & the phase-target gradient

Every departure climbs away from the same runway. VyCurve reads how, without keeping score against anyone.

The climb report is the front page of a VyCurve field. It answers four plain questions — what a typical departure looks like, whether it is changing, why it varies, and how much terrain margin there is — from the ADS-B tracks your field already generates. At its center is the climb-profile score: a descriptive read of how a departure compared to the field's own observed envelope and a distance-based gradient target, phase by phase. It is an educational awareness aid for pilots and communities who want to understand and improve climbs. It is not a performance certification, not enforcement, and never a verdict on any flight.

Request a demo Back to the overview
Initial · 0–3 mi Middle · 3–7 mi Final · 7–10 mi 1,500 500 1,000 ft AGL Height above ground (ft AGL) — illustrative Estimated margin over the terrain — flagged when it is thin One observed departure Median climb (all departures) Phase-target gradient Terrain along the route Distance from runway (nm) 0 2 4 6 8 10
Observed departure Median climb Middle 50% Full range Terrain

Fig. 1. Illustrative rendering for Fairview Airfield (FAA), a fictional demonstration field. Every figure on this page is synthetic — drawn to show what the read looks like, not what any real airport or aircraft recorded. The gradient is a project reference, not a regulatory minimum.

The climb is the first thing everyone watches

A departure clears the terrain, passes over the neighborhood, and sets the tone of a check-ride, all in the first few miles. Reading it plainly — against the field's own envelope, never against another pilot — is what turns "that felt slow" into something a community can actually look at.

With the neighbors

How high departures actually are over the ground, in aggregate, replaces a stack of individual impressions. Where the median climb crosses each area — and how much margin it keeps — is a shared picture, not a complaint log.

With the pilots

Climb performance changes with aircraft, loading, density altitude, and technique. The score shows how one departure compared to the field's observed envelope on that day — a private, educational debrief, phase by phase, never a public ranking.

With the board

Trends in the median climb and its terrain margin give managers a descriptive, methodology-backed way to weigh a pattern note or some outreach — with the sampling caveats attached to every number.

The climb-profile score, opened up

One 0–100 number, built from three distance-based phases and a gradient target that needs no assumed airspeed. It rewards a climb that keeps gaining altitude over the ground at the expected rate — and it shows its work, phase by phase.

Graphical excellence is that which gives to the viewer the greatest number of ideas in the shortest time with the least ink in the smallest space.

Edward R. Tufte, The Visual Display of Quantitative Information

The three phases

Illustrative
Quarter-mile ticks that met the phase gradient target Initial · 0–3 mi · 240 ft/NM 88% met Middle · 3–7 mi · 120 ft/NM 79% met Final · 7–10 mi · 60 ft/NM 61% met

Fig. 2. Each bar is the share of quarter-mile samples that met that phase's gradient target. Green marks the strongest phase, amber the clearest thing to look at next — a private debrief cue, never a public scorecard.

Quarter-mile FPM vs the target

Illustrative
400 200 target 400 fpm 200 100 0 3 7 10 Distance from runway (nm) · smoothed climb rate

Fig. 3. Where the navy line sits above the graphite step, the climb beat the target for that quarter mile; below it, it fell short. Density altitude, loading, and ATC level-offs all move it — so it is read alongside the conditions, not on its own.

78 / 100 Climb-profile score · demonstration departure

A descriptive summary of how this departure compared to the field's own observed envelope and gradient target — not a determination that it was safe, legal, airworthy, or well-flown.

A gradient, not a rate

The target is feet gained per nautical mile over the ground — 240 in the initial phase, 120 in the middle, 60 in the final. Because it is a gradient, it needs no assumed airspeed and is exactly the line the score compares against.

Three distance-based phases

Initial 0–3 mi, Middle 3–7 mi, Final 7–10 mi. Each phase is scored on its own, so a strong start and a fading finish read as two separate, teachable facts rather than one blurred average.

Ticks meeting target

Alongside the score, the report shows how many quarter-mile samples actually met the phase target — the honest denominator behind the headline, so one number is never read on its own.

Always a distribution

Every phase is reported against the field's own envelope — never a pass/fail, never a ranking of identifiable pilots or aircraft. Masking is on by default here exactly as it is everywhere else.

Holds the gradient — and fades in the final phase

The same aircraft type can climb two very different ways. Read side by side against the target, the difference is not a grade — it is a picture of a habit that is easy to see and easy to adjust.

Holds the gradient

Illustrative
target gradient Runway → 10 nm · height above ground

Fig. 4. The navy climb stays above the gradient in every phase; 90% of its quarter-mile ticks met target. A steady, well-margined departure.

Fades in the final phase

Illustrative
target gradient Runway → 10 nm · height above ground

Fig. 5. A strong start, then the climb flattens below the gradient past 7 mi; only 64% met target. Same runway, same aircraft type; a different habit in the final third.

Steady climb — score

86

90% of ticks met target

Fading climb — score

63

64% of ticks met target

Field median score

78

Across scored departures

Scored departures

3,180

One demonstration season

All values are synthetic and illustrative. The score reflects a comparison to this fictional field's own observed envelope and gradient target; it is not a comparison between pilots and not a statement of any aircraft's certified performance.

Why a climb varies — terrain, and the air itself

Before the report reaches for any story about technique, it shows the two things that move a climb the most: the ground it has to clear, and how thin the air was on the day.

Climb angle & terrain clearance

Illustrative
20:1 3° Observed median climb Runway → 3 nm · height above ground

Fig. 6. The median climb clears the terrain well above the shared 20:1 and 3° reference slopes. These are drawn as context, never as a compliance line — margin to think about, not a finding about a flight.

Score vs density altitude

Illustrative
Departure density altitude → Score /100

Fig. 7. Scores fall as density altitude rises — less dense air, less climb. The pattern spans the whole demonstration fleet; it explains no single flight, and the report says so wherever it appears.

What this is — and emphatically is not

An awareness tool earns trust by stating its limits as plainly as its findings. The climb score ships with all of these, and they travel with every figure it produces.

Not a performance certification

The climb-profile score is a descriptive comparison to the field's own observed envelope and a project gradient reference — not a statement of any aircraft's certified performance, and not an airworthiness, maintenance, or fitness assessment. The 240 / 120 / 60 ft/NM gradient is a shared reference line for reading a climb, not a regulatory minimum and not a target any pilot is obliged to hit.

Errors happen — and are stated

Everything here is reconstructed from ADS-B position reports, which carry GPS noise, time offsets, dropped samples, and barometric altitude that must be converted to height above ground using terrain data of finite resolution. ATC level-offs, a nearby taller obstacle, or a grid cell that sits off the route can all move a number. Where the data cannot support a score, VyCurve caps or withholds it and shows the confidence and the flags. Treat every number as an estimate with error, not a measurement.

Illustrative here, and not legal or regulatory anywhere

Every chart, score, and figure on this page is synthetic and illustrative, drawn for Fairview Airfield (FAA), a fictional demonstration field. Nothing here reflects a real airport, aircraft, or pilot. And nothing VyCurve produces — on this page or in a live report — is a regulatory finding, a compliance determination, an accident-investigation input, or a legal instrument. It does not establish fault, safety, or legality for any flight.

What the climb read is for

  • Helping pilots learn and refine steady, well-margined climbs.
  • Giving a field a shared, factual picture of how departures actually fly.
  • Surfacing thin terrain margins as review cues for areas, with sample sizes attached.
  • Attributing variation to terrain and conditions before anything else.
  • Turning a single departure into a private, constructive debrief.

What it is never for

  • Certifying performance, airworthiness, or fitness to fly.
  • Punishing, ranking, or naming identifiable pilots or aircraft.
  • Enforcement, complaint targeting, or fault-finding of any kind.
  • Judging whether a flight was safe, legal, or correctly flown.
  • Being read as anything more than descriptive aggregation.

The point is learning, not punishment

A well-margined climb and a well-flown one are usually the same climb. VyCurve exists so pilots, clubs, boards, and neighbors can understand airport movements and improve them together — climbs and landings alike — from the same restrained, observed picture. If a field wants a tool for blame, this is deliberately the wrong one.

See the climb report on your own field's data

A demo walks through the climb report, the community map, and the approach score together — with the privacy model and every caveat on the table — then, if you like, we point a receiver at your pattern and let your own data make the case.

Request a demo See approaches & the approach score →

Demos run about thirty minutes and use demonstration data only.