Winds Aloft — Model-Derived Wind Analysis
How PlaneWX computes winds at your cruise altitude using multi-model atmospheric data instead of legacy FB winds forecasts.
Why Model Winds?
Traditional Winds & Temperatures Aloft forecasts (FB winds / FD winds) are issued by the Aviation Weather Center twice daily and represent broad-area averages tied to fixed reporting stations. PlaneWX replaces these with route-specific, model-derived winds sampled directly along your flight path.
Legacy FB Winds
- • Updated twice daily (00Z, 12Z)
- • Fixed station locations (may not be on your route)
- • Single model source
- • Fixed altitude levels (3K, 6K, 9K, 12K…)
PlaneWX Model Winds
- • Updated hourly (HRRR) to every 6 hours (GFS, ECMWF, HRDPS)
- • Sampled at multiple points along your route
- • Multi-model consensus (HRRR / HRDPS / ICON / AROME + GFS + ECMWF by region)
- • Any altitude from surface to FL450+
How It Works
Route Sampling
PlaneWX generates sample points along your route (3–15 points depending on distance, spaced about every 25 NM and capped at 15). Each point gets a full atmospheric sounding from every available model.
Multi-Model Extraction
At each sample point, wind speed and direction are extracted from every model that returned data for your route (for example HRRR + GFS + ECMWF on CONUS, or GFS + ECMWF when a regional model is unavailable or out of range). Winds are decomposed into U/V vector components for mathematically correct averaging — simple speed/direction averaging produces wrong results when models disagree on direction.
Vector-Averaged Consensus
Yes — PlaneWX averages the models. Specifically, the U/V components are equally averaged across every successful model sample at every route point, then converted back to a single direction and speed. That consensus wind is what appears in the Winds Aloft card (labeled e.g. “GFS + ECMWF, 15 route samples”). When one model shows a stronger low-level jet than another, the consensus lands between them — which can look lighter than a single-model EFB like ForeFlight.
Flight Impact Calculation
The consensus wind is resolved into headwind/tailwind and crosswind components using your true course. Combined with your TAS, PlaneWX computes ground speed and the percentage impact on your flight time.
Reading the Winds Aloft Card
Cruise Wind
The route-averaged wind at your cruise altitude, shown as direction and speed (e.g., “270°/35kt”). This represents the average conditions you’ll experience en route.
Headwind / Tailwind
The along-track component of the cruise wind. Positive values are headwinds (slower); negative values are tailwinds (faster). Color-coded: green for beneficial tailwinds, amber/red for significant headwinds.
Ground Speed
Your estimated ground speed (TAS adjusted for headwind/tailwind).
Time Impact
The percentage impact on flight time compared to a no-wind scenario. For example, “+12%” means the flight will take roughly 12% longer due to headwinds. Green indicates time savings from tailwinds.
Weather Models
PlaneWX picks the model mix from your route geography. US domestic flights use HRRR + GFS + ECMWF; routes with both endpoints inside the Canadian HRDPS domain add Environment Canada's HRDPS; European routes add ICON EU (and ICON D2 when both airports are inside its central-Europe nest); western European routes also add Météo-France AROME when both endpoints are inside its domain.
HRRR (High-Resolution Rapid Refresh)
3 km resolution, updated hourly. Best for near-term (0–18h) wind forecasts over CONUS. Captures terrain effects and mesoscale wind patterns that coarser models miss.
HRDPS (GEM High Resolution Deterministic Prediction System)
2.5 km resolution from Environment Canada, updated every 6 hours, out to about 48 hours. The Canadian analogue to HRRR — tuned for Canadian terrain, including the Rockies in Alberta and BC. Used when both route endpoints are inside the HRDPS domain (with HRRR also included on border / northern-US legs).
GFS (Global Forecast System)
0.25° resolution (~25 km), updated every 6 hours. Global coverage out to 16 days. Provides wind data for international routes and longer-range forecasts.
ECMWF (IFS)
0.25° resolution, updated every 6 hours. Generally considered the most skillful global model for medium-range forecasts. Provides an independent check on GFS wind predictions — especially useful for Canadian medium-range planning.
ICON EU / ICON D2 (DWD)
European high-resolution models from Germany's DWD. ICON EU (~7 km) covers Europe; ICON D2 (~2 km) nests over central Europe. Activated when both route endpoints are inside the European domain — the same geography rules as icing and turbulence analysis.
AROME (Météo-France)
2.5 km resolution from Météo-France. Near-term only (under 48 hours). Applies on western European routes when both endpoints are inside its domain — the UK and Ireland, France, the Low Countries, western Germany, the Alps, and northern/central Spain. Scotland, Portugal, southern Spain, and Italy east of 12°E fall outside. Same geography rules as icing and turbulence analysis.
When models disagree significantly about wind speed or direction, the consensus may understate the true wind. The briefing narrative will call out notable model disagreements. Your briefing's Models line always lists the models that actually ran for that route. The route-profile cloud grid uses the same geography-aware mix (HRRR / HRDPS / GFS / ECMWF).
Multi-Altitude Wind Table
In the Weather Sources tab, you’ll find a complete winds-at-altitude table showing model consensus winds from the surface through your service ceiling. Each row shows:
This data can help you choose the optimal cruise altitude for your trip — balancing headwind/tailwind impact against altitude-related factors like icing and turbulence.
Model Winds Comparison
Below the consensus table, Weather Sources also shows a per-model comparison(e.g. GFS vs ECMWF vs HRRR) at each altitude, plus consensus headwind/tailwind and an agreement label (unanimous / majority / split). When models disagree near cruise, a callout explains that the averaged wind may understate the stronger model — useful when comparing PlaneWX to a single-model EFB.