Here is where the number changes.

A temporary crane near the departure end triggers a NOTAM that shortens the declared takeoff distance available. The runway is still open — just shorter today.

Tools working from static runway data still use the full published length. Nothing warns the pilot that the usable distance changed overnight.

Live Airport Updates apply the temporary distance, re-evaluates the limiting factor, and recomputes RTOW against the shortened runway and any new obstacle.

ATC offers an intersection departure to save time. It's tempting — but you're now starting well down the runway with less distance ahead.

A full-length assumption hides the reduced distance. The V-speeds and derate that were safe from the threshold may not be safe from the intersection.

VPT models the intersection's declared distances, recomputes the limiting factor and V-speeds, and re-verifies obstacle clearance along the engine-failure path.

Arrival runway is wet and there's a light tailwind component. Individually minor; together they stretch the landing distance meaningfully.

Dry, headwind assumptions and a habitual autobrake setting can leave you short of margin on a runway that felt "long enough."

Landing enroute performance combines the wet surface, actual wind component and available autobrake settings, and returns the brake-cooling schedule too.

Work in progress displaces the threshold for a few weeks. The landing distance available shrinks; the touchdown point moves.

Without the temporary NOTAM applied, calculations still use the permanent threshold and the full landing distance.

VPT applies the displaced threshold from the active NOTAM, adjusts the declared distances, and re-runs the landing calculation against the real geometry.

High elevation airport on a hot afternoon. Density altitude soars and thrust falls away exactly when you need the runway most.

Simplified tables can under-represent how sharply performance degrades, and may ignore the surrounding terrain that shapes the escape path.

Aircraft-specific logic accounts for temperature and altitude, then verifies the engine-failure procedure against millions of obstacles and terrain.

Snow, slush or standing water on the runway. Contamination changes acceleration, stopping and the go/no-go decision speed.

Dry-runway numbers are dangerously optimistic on a contaminated surface, and reduced-thrust assumptions may no longer be valid.

VPT applies the reported contamination type and depth, adjusts accelerate-stop and accelerate-go distances, and recomputes V1 for the conditions.

A NOTAM closes a runway for part of the day, or restricts it to certain operations. The plan you built this morning may not be valid at your ETA.

Static data offers the closed runway as if it were available — no flag, no alternative.

Automated Runway Monitoring reads the NOTAM text, depicts the closure against the current time, and steers you to a usable runway.

You dispatch with an anti-skid system inoperative under the MEL. The aircraft's own EFB gives a number — but is it complete?

A generic penalty, or none at all. The interaction of the failed item with runway condition and configuration is easy to under-model.

VPT's MEL module computes the actual performance implication of the failure — an independent second opinion alongside the add-on's own figures.