Service · Runway Analysis

Takeoff analysis for the runways you actually use.

SCAP takeoff performance computed against your certified database, runway end by runway end, with the governing limit named rather than buried.

Request an analysis

Output

What you get per runway end.

Not a single maximum weight, but the set of limits behind it — so when a weight looks wrong, you can see which constraint produced it.

Maximum takeoff weight by limit — field length, climb, obstacle, tyre speed and brake energy — with the governing one identified.
V1, VR and V2 for the resulting weight and configuration.
Assumed temperature for reduced-thrust departures, computed as its own certified case.
Flap optimised across the available settings, or fixed where your procedures fix it.
Climb gradients at the analysed weight.
Contaminated cases — dry through standing water, slush and slippery, with depth and braking coefficient as real inputs.

Your policies

Analysis that matches how you actually operate.

Runway analysis goes beyond basic calculations. We use manufacturer data together with your own operational policies, so the performance data matches your real-world procedures rather than a generic default.

V1 policyOptimised, or fixed to your procedure — whichever your operations manual specifies.
Acceleration altitudeYour acceleration height and the segment structure that follows from it.
Contaminated runway proceduresThe contaminant set and braking policy your certificate approves, not a nominal wet case.
Obstacle clearance requirementsThe clearance criteria you operate to, applied per runway end.
Obstacle splayCustomised splay geometry where your procedures depart from the standard construction.
Engine-out proceduresThe analysis is run against the engine-out routing you actually fly — see engine out procedures.

Runway data

Geometry taken from source, refreshed on cycle.

A takeoff analysis is only as good as the runway it was run on. We build ours from the authority's own dataset rather than from a spreadsheet somebody maintained by hand.

Declared distances — TORA, TODA, ASDA and LDA for each end, with clearway and stopway derived.
Gradient, displaced threshold, touchdown zone and threshold elevation.
The controlling obstacle for each runway end: type, height above ground, distance, offset and FAR Part 77 category.
Surface, width, strength and lighting, with true alignment per end.
Rebuilt every 28-day cycle from the FAA NASR airport dataset — around 19,400 airports, 23,200 runways and 39,900 runway ends.

Screenshotimg/shot-rwa-results.jpg
runway analysis result table

The engine

The SCAP module, at the precision the original was written in.

The manufacturer's SCAP takeoff module carried across to Rust and run in single-precision float — the same arithmetic width as the certified Fortran, which ordinary web code cannot reproduce. It is checked cell for cell against an independent reference implementation before any result leaves it.

EngineThe manufacturer's SCAP takeoff module, ported to Rust at float32 fidelity.
VerificationCell-for-cell parity against an independent reference implementation of the same engine.
Aircraft coverageEach type is enabled once its performance database is decoded and registered — see SCAP database creation. If you hold the database, we can enable the type; if you do not, we can often build it.
DeliveryAs analysis tables for your manuals, as an API into your own systems, or live inside Volatus — one click from a flight to the analysis of the runway it is using.
Also on boardThe same engine runs inside eLila EFB, so the crew's numbers and the analysis tables come from one source.

Takeoff analysis for the runways you actually use.

What you get per runway end.

Analysis that matches how you actually operate.

Geometry taken from source, refreshed on cycle.

The SCAP module, at the precision the original was written in.

Give us your limiting airport.