Platform

Launch Site Explorer

For a candidate launch site and a target orbit, resolves exactly which launch azimuths reach it — real spherical trigonometry, not a rule of thumb — then screens the resolved corridor against known shipping lanes, air corridors, built-up land and ports, enriched with recent traffic density. Every signal drawn on the real site, every result exportable as a branded PDF report. The Launch Site Study then compares a whole shortlist of sites — ascent performance, drop zones, logistics, weather, population — down to a reasoned recommendation, on launch performance computed by trajectory optimisation: optimal control, multi-burn missions, upper-air winds and Monte-Carlo dispersions, validated on published benchmarks.

Exact spherical trigonometry

Feasibility — which azimuths actually reach the target orbit

cos(i) = cos(lat) · sin(Az), solved for both azimuth roots within the site's permitted corridor — LEO against a target inclination, SSO derived from altitude through first-order J2 nodal precession, or GEO's near-equatorial case. When nothing in the corridor reaches it directly, the nearest achievable inclination and its plane-change delta-v penalty are reported instead of a flat no.

Both roots, not one

A target inclination generally has two azimuth solutions, not one — both resolved and checked against the site's actual permitted corridor, so a real direct-ascent option is never missed because only the first root was considered.

A real delta-v, not a flag

Not directly achievable still reports a number: a single-impulse upper-bound estimate for LEO, or a combined circularization-plus-plane-change burn at GTO apogee for GEO — against a custom launcher library's own LEO/SSO/GTO payload figures.

Structural safety screen

Does the corridor cross a known hazard — not just a live snapshot

A live AIS vessel count only answers "is a ship there right now." The question that actually matters for siting is structural: does the resolved corridor cross a known shipping lane or air corridor at all. Every signal below is drawn on the real site, colour- and style-coded by severity so adjacent layers never blur together.

Known shipping lanes

Global Major/Middle/Minor shipping-lane center-lines tested against the resolved ray — the primary maritime signal, with a best-effort live AIS vessel count alongside it as a secondary, supplementary note.

Air corridors

Live OpenAIP airspace data — CTR, TMA, ATZ and en-route Airway types together, so a site next to a major airport's own control zone is caught, not just the en-route corridors between navigation fixes.

Built-up land

The resolved ray sampled every 10 km against ESA WorldCover's own published land-cover classification — a structural "does this corridor cross built-up land" check, not a census figure.

Launch Site Explorer with four windows open at once: the main panel (site, target orbit, azimuth corridor, launcher), a dedicated results window reporting a shipping-lane Major crossing, Dubai CTR and Sharjah CTR air-corridor crossings, built-up land, a nearby port/anchorage, recent IMF PortWatch port activity and 4.2M vessel-presence hours from Global Fishing Watch, a map legend for the drawn layers, and the branded PDF report window with the same detail.

Launch Site Explorer · results window, map legend and branded report, all in sync

Planning aid, not certified range-safety clearance. Every structural signal here — shipping lanes, air corridors, built-up land, port proximity — says so explicitly in both the panel and the report. It narrows down where to look first; it is not a substitute for a certified range safety process.

Ports & recent traffic

A local geospatial store, enriched with recent activity

A self-hosted PostGIS store — the NGA World Port Index, Global Fishing Watch's anchorage database and Marine Regions' territorial-waters boundaries — resolves the nearest port or anchorage to the corridor, closing the gap a global shipping-lane dataset alone leaves at port-level approach distances. Two dynamic layers enrich it further, each degrading cleanly when not configured rather than blocking the rest of the screen. SatView never bundles, sells or redistributes this third-party data itself — it only provides the means to connect to each source, on your own credentials where one is required.

IMF PortWatch activity

Recent port calls and import/export volumes for the nearest matched port — a public, keyless data source, no account or key to configure.

Global Fishing Watch traffic

Recent vessel-presence density — all vessel types, not just fishing — across the site's whole display corridor, from your own GFW account. A recent-history figure, not a live feed. Powered by Global Fishing Watch.

Launch Site Study

From a shortlist to a reasoned recommendation

Place several candidate sites — fixed pads, offshore platforms, mobile positions, home ports, or existing ranges as references — and compare them on the same mission, the same vehicle and the same rules. Azimuths, mission planes, ascent performance, drop zones, logistics, weather availability, population, seismic hazard and your own environmental layers, side by side, ending in a study-style PDF report with a recommendation derived from the figures.

Ascent performance, per site

Maximum payload of the same vehicle to the same orbit from every site, by gravity turn, optimised guidance or optimal control (SQP), direct or via a parking orbit, in the site's own upper-air wind, with max Q, max g, q·α and the real orbit reached. See Launch Performance.

Drop zones on the map

Every jettisoned body — boosters, stages, fairing — falls with drag to an impact point and a dispersion ellipse, colour-coded by stage, with its distance to land and the places nearby. Import a trajectory from any other tool and it is screened the same way.

Conclusions you can trace

No hidden weighted score: each criterion ranks the sites with an explicit equivalence tolerance, then Pareto dominance, a mean normalised rank and a sensitivity test (double a weight, leave a criterion out). Non-comparable results are left out with their reason, and the recommendation stays provisional until the open points are settled.

Azimuths tab: one fan diagram per reference site (Kourou, Cape Canaveral, Vandenberg, Baikonur, Wallops, Mahia) showing every launch heading in green when clear and red when excluded by the rule set, with the two headings of the 51.6° mission plane and the excluded populated places listed under each fan.

Azimuths · every launch heading screened against your own rules, site by site

Trajectories tab: altitude and speed profiles of an illustrative two-stage launcher from six sites to a 51.6° / 420 km orbit, then one card per trajectory with payload, orbit reached (419 × 423 km), max Q, land overflight and where the first stage and fairing fall.

Trajectories · the same vehicle and orbit from six sites, and where every stage falls

Comparison tab: admissible azimuth sectors and Earth-rotation gain per site, then the site synthesis table — admissible azimuths, mission planes, payload to the same orbit, programme cost, expected casualties per flight, protected areas, drops, sea route from the base, aerodrome and port for heavy cargo, weather availability, launch windows, population, nearest large city, shipping lanes and vessel traffic — colour-coded from best to least good.

Comparison · raw figures side by side, colour-coded from best to least good — no combined score

Report tab: world map with the six sites and their ground tracks, followed by the executive summary — a provisional recommendation with its non-dominance, the criteria it ranks first on, the mean normalised rank, sensitivity and the reasons a criterion was left out.

Report · a provisional recommendation, with the reasoning behind it

The ground of each site

Logistics, weather and environment only need the sites, so they come first. Sea routes are computed on SatView's own water grid from your home port, with the main straits and canals; weather availability comes from years of hourly ERA5 reanalysis against your thresholds.

Map of the study: sea routes in yellow from the Le Havre logistics base to Wallops, Cape Canaveral, Kourou, Vandenberg through Panama and on to Mahia in New Zealand, over the admissible azimuth fans of each site in green and the excluded sectors in red.

Map · sea routes from the home port and the azimuth fans of every site, across the Pacific

Logistics tab: sea routes from Le Havre — Kourou 3 794 nm (13.2 days at 12 knots), Cape Canaveral 3 837 nm, Vandenberg 7 714 nm, no sea route to Baikonur, Wallops 3 274 nm, Mahia 11 005 nm — beside the great-circle distance, then the aerodromes and ports around the base with runway lengths, channel depths, cranes and repairs.

Logistics · sea routes and transit days from the base, aerodromes and ports nearby

Availability tab: wind, gust, rain and wave thresholds, a 3-hour window over five years, and the share of time each month when every threshold is met — Kourou 68 % over the year with May at 46 %, Baikonur 98 %, Vandenberg 95 % — with the most frequent blocker per site.

Availability · share of time within your thresholds, month by month, from ERA5

A mobile platform at sea

For each plane of the mission, SatView looks for the working position of a launch platform: the nearest to the home port by sea, far enough off any coast, and reaching the plane by direct ascent with a heading your rules admit. The positions become mobile sites of the study in one click.

Mobile platform tab for a six-plane constellation from Le Havre: four working positions — WP1 51.5° N 2.0° E for the 84° plane, 150 nm from the base; WP2 53.5° N 2.0° E for 64°, 264 nm; WP3 47.5° N 6.0° W for 53°, 317 nm; WP4 44.5° N 7.0° W for 45°, 510 nm — with their admissible headings; no position found for the 0° and 12° planes within 2 000 nm.

Mobile platform · one working position per plane, its heading and the distance by sea

Map of north-western Europe with the Le Havre base and the four working positions in the North Sea and the Bay of Biscay, labelled with their plane and distance by sea.

The positions on the map, around the home port

When, and at what cost

A sun-synchronous plane fixes the lift-off time; SatView gives it per site and heading, then crosses it with the hourly weather to count the days with a launch opportunity in good weather. The programme cost is parametric, from the study's own figures and your unit costs — for comparing sites, not a budget.

Launch windows tab for a sun-synchronous orbit at 500 km with a 10:30 descending node: lift-off times per site, northbound and southbound (Kourou 01:48 and 13:54 UTC, Vandenberg 06:02 and 18:43 UTC), opportunities per year and window length, then the share of days each month with a lift-off opportunity in good weather.

Launch windows · lift-off times for a sun-synchronous plane, and the days with good weather

Cost tab: programme length, flights per year and unit costs (example values), then per site the investment, transport per flight from the base, campaign, expected weather standby and payload shortfall, and the total over ten years — from 132 M€ for Baikonur to 407 M€ for Mahia.

Cost · a parametric programme cost per site from the study’s own figures and your unit costs

How robust is the ranking

No weights are imposed. Five thousand draws take every possible weighting and every figure within its uncertainty; the share of draws where each site comes first says whether the choice holds whatever the weights, or rests on the weights you give.

Robustness of the ranking under uncertainty: Baikonur first in 48 % of the draws and in 80 % with equal weights, Kourou first in 31 %, Wallops in 16 %; the criteria each leader wins on are listed below the table (SMAA-2, 5 000 draws).

Robustness · share of draws where each site comes first, over every weighting

The PDF study

About thirty-five illustrated pages: executive summary, site synthesis, overall standing and robustness of the ranking, method and inputs, azimuths and mission planes, launch performance, trajectories and drop zones, logistics, weather, launch windows, programme cost, environment and hazards, open points, the criteria grid, then one sheet per site.

Cover of the Launch Site Study PDF: satellite map of the six candidate sites with their ground tracks, and the list of sites and the logistics base with their type and coordinates.

Cover · sites, base and ground tracks

PDF site synthesis page: one row per criterion with a pictogram, one column per site, cells coloured green for the best, amber in between and red for the least good.

Site synthesis · one row per criterion

Six public reference sites and a logistics base at Le Havre, an illustrative two-stage launcher with rounded public figures, a 51.6° / 420 km orbit — generated by SatView as is.

A pre-study tool, not a certified analysis. The example vehicles use rounded public figures and are illustrations, not data about real launchers; rules, thresholds and orbits are yours to set. The report lists what it does not cover — maritime law, launching-state liability, notices to mariners and airmen, export control — as open points rather than settled ones.

Every result, a report someone else can read

The same branded PDF export as the rest of the platform — a map snapshot, every site's full feasibility and safety-screen detail, and every shipping lane or nearby port listed individually, not just the worst case.