LOWW throughput estimate

mst@fyi:~$ estimate LOWW_jet_fuel_throughput

Vienna Airport kerosene throughput.

Jet A-1 demand is estimated by Vienna local civil day from observed departing flights. The batch pipeline resolves aircraft types and destinations, applies FEAT mission fuel plus an ICAO APU allowance as the midpoint, and uses OpenAP as a published secondary cross-check.

OpenSky FEAT OpenAP ICAO APU OurAirports units: tonnes and m3 Jet A-1

Manual fallback

optional inputs
No generated JSON loaded yet. Manual aggregate inputs are active.
inputs saved in this browser

The default values are a manual fallback. When generated JSON is reachable, this page uses the published estimator output from status.mst.fyi.

Estimate

--
Local-day throughput midpoint -- metric tonnes Jet A-1
Uncertainty band -- low to high, tonnes
Approximate volume -- m3 at 785 kg/m3
Route imputation factor -- manual fallback only
Observed departures -- published route coverage or manual pattern
Model cross-check -- OpenAP hybrid and direct model coverage

Method

published JSON model

What this page does

  • Each date is a Vienna local civil day, from 00:00 to 24:00 Europe/Vienna.
  • The published pipeline ingests OpenSky departures and destination ICAO codes.
  • Destination coordinates come from OurAirports; great-circle distances use FEAT's published route-distance correction.
  • The current fuel model applies FEAT's aircraft-specific quadratic coefficients for 133 supported type designators.
  • FEAT already covers main-engine Taxi-Out through Taxi-In; the pipeline does not add taxi fuel twice.
  • Aircraft APU fuel is added from ICAO Doc 9889 defaults: 80 kg per short-haul and 300 kg per long-haul operation, with a broad 0-200% APU uncertainty bracket because actual runtime is not observed.
  • OpenAP 2.4 provides a secondary mission and taxi estimate using its range-based mass model; FEAT remains the midpoint because some shared aircraft types differ by more than 30%.
  • Unsupported type/route combinations use same-day type, route, or airport-wide fuel distributions and publish their fallback counts.
  • Direct FEAT values use the paper's 5% validation envelope; empirical fallbacks use their reference distribution's quartiles, and the daily band widens when needed to contain the OpenAP hybrid.
  • Forecast rows use a capped 12-week linear trend plus residuals from the four most recent matching weekdays, with rolling backtest error published per horizon.
  • Volume conversion uses Jet A-1 density 785 kg/m3, so m3 = tonnes x 1000 / 785.
  • The history chart offers 3-month, year-to-date, 1-year, and horizontally scrollable full-archive views plus the next 14 forecast local days.
  • The MTOW table compares exact OpenAP type MTOWs with VIE's official monthly MTOW. Arrival-plus-departure movements are halved only for the departure-count benchmark; the official MTOW value is not halved.
  • The normalized MTOW match diagnoses fleet mix and OpenSky counts. It does not calibrate or scale fuel consumption.
  • The manual controls remain as an offline aggregate fallback when published JSON cannot be loaded; they use direct expected departures and an explicit pattern multiplier.

What this page does not do

  • It does not fetch OpenSky, run FEAT/OpenAP, model tankering, or infer missing aircraft types in the browser.
  • It is designed to render static outputs from a separate reproducible batch pipeline.
  • Tankering, payload, weather, actual APU runtime, and metered uplift remain unobserved.
  • Ground vehicles and de-icing fluid are outside aircraft Jet A-1 throughput; they are not added to the kerosene total.