Wingtra PPK: Choosing and Positioning the Base Station

WingtraOne GEN II flies a PPK-first workflow — which makes the base station the accuracy decision. Base options, RINEX requirements, WingtraHub processing, and how base coordinates set the absolute accuracy of every map.

Wingtra’s PPK-first philosophy

Wingtra built the WingtraOne GEN II around post-processing rather than live corrections: the VTOL fixed-wing covers hundreds of hectares per flight at distances where radio links are fiction, logs raw multi-band GNSS with camera events, and resolves centimetre geotags afterwards in WingtraHub. It is the cleanest demonstration in the industry that PPK is not a fallback but a first-class architecture (where PPK sits among the methods) — and it quietly relocates the entire accuracy question to the one component the aircraft does not carry: the base.

What the workflow needs from a base

Three things, exactly. Raw observations: RINEX (or convertible vendor logs) at 1 Hz or better, multi-constellation, spanning the whole flight with margin. Proximity: baselines within roughly 20–30 km keep ambiguity resolution comfortable; on-site is best. Trustworthy coordinates: the processed geotags are relative to the base position, so the map’s absolute accuracy equals the base’s — centimetre base, centimetre map; averaged base, offset map, however beautiful (the inheritance rule). Any receiver meeting the three qualifies: an Emlid Reach logging in the corner, a CORS station’s public RINEX, or a self-converging base doing double duty.

Base options ranked for Wingtra work

Base option	Absolute coordinates	Works beyond coverage	Notes
CORS RINEX archive	Authoritative	No — station must exist nearby	Free; watch baseline length
Own receiver on known point	Inherits monument	Yes, where monuments exist	Setup ritual per site
Own receiver, averaged	Metre-class offset	Yes	Relative-only results
Own receiver + OPUS/AUSPOS	Authoritative, next-day	Yes	Latency; free audit trail
Self-converging PPP base	~1.5 cm in ~3 min, ITRF2020	Yes — anywhere with sky	Logs RINEX while converged

The last row is why PPP bases and PPK aircraft pair so naturally: the base spends three minutes solving the only problem the Wingtra workflow leaves open, then logs the RINEX the workflow requires — one device, both requirements, no infrastructure.

The corridor-and-large-area pattern

Wingtra missions routinely outrun any radio horizon — 40 km corridor legs, 500-hectare blocks — which is precisely where PPK’s link-independence shines and where base placement becomes pure logistics: put the base at the operations point with open sky, converge, start RINEX, and forget it for the day (10-hour battery; USB-C for longer). Multi-day corridors leapfrog the base along the route; because a self-converging base re-establishes absolute coordinates at every hop, the segments processed against different base positions still land in one seamless ITRF2020 frame — the property that makes corridor mosaics stitch without block adjustment (the corridor playbook).

Processing in WingtraHub, and what to check

WingtraHub ingests the aircraft logs, camera events, and your base RINEX, resolves the trajectory, and writes corrected geotags for Pix4D, Metashape, or your suite of choice. The two checks that matter: base coordinates in the processing dialog must be the base’s true coordinates (paste from the base console or the OPUS report — never let software “use header position” from an averaged log unquestioned); and the quality report’s fix ratio should sit high with residuals in centimetres — a poor fix ratio points at baseline length, log gaps, or sky trouble in that order. Two checkpoints on the ground close the loop as always.

Hybrid honesty: when to add RTK anyway

GEN II supports live corrections where available, and there are moments to use them: precision landings in tight zones and terrain-hugging legs benefit from a live solution even when geotags will come from PPK. The pattern costs nothing when the base already broadcasts: NTRIP for the live leg, RINEX for the geotags, one datum throughout. What the hybrid never changes is the accuracy anchor — base coordinates rule both paths, which keeps this article’s single lesson intact.

Program economics of the pairing

A Wingtra program’s accuracy budget concentrates beautifully: no per-rover network subscriptions (PPK consumes files, not streams), no GCP grids across 500-hectare blocks (checkpoints suffice once the base is absolute — the economics), and establishment time compressed to the base’s three-minute convergence. Against the aircraft’s price, the base is a rounding error that determines whether the aircraft’s output is absolute — the highest-leverage line item in the whole kit list.

Multi-day and multi-crew Wingtra programs

Scale exposes the base decision fastest. A two-aircraft corridor push or a national mapping campaign runs several Wingtra crews in parallel, each needing base RINEX within baseline range — and each base's coordinates method multiplying across the program. Self-converging bases make the fleet pattern trivial: every crew carries one, every unit re-establishes the same ITRF2020 frame wherever it lands, and the processing office receives logs whose header coordinates need no reconciliation meeting. Contrast the alternative — a spreadsheet of averaged positions, OPUS tickets in three time zones, and a block-adjustment step to stitch crews together — and the fleet economics of the absolute base write themselves.

A pre-flight checklist for the base side

Five lines before the Wingtra leaves the case: base converged (status green, coordinates noted with frame and epoch); RINEX logging confirmed running at 1 Hz with free storage for the day; baseline check — is every planned flight line inside ~20–30 km of this position, and if not, where does the base hop; UTC time sanity on all devices (event matching lives on it); and the two checkpoints identified for the segment. Ninety seconds that guarantee the office step is processing rather than archaeology.

One-line takeaway

Wingtra's PPK-first design concentrates the entire accuracy question into the base's RINEX and coordinates — put a self-converging base on site and both are solved in the three minutes it takes to unfold the aircraft.

Further reading

The general PPK logging discipline — rates, formats, and rescue workflows — lives in RINEX and PPK; corridor-scale Wingtra operations with leapfrogging bases are mapped in the corridor playbook; and the base-coordinates methods this article keeps pointing at are compared method-by-method in setting up without a known point.

The one metric to watch across a program

If a Wingtra program tracks a single quality number, make it the per-mission checkpoint residual against the fixed pair on stable ground: plotted over months it becomes a control chart for the whole chain — base coordinates, logs, processing — and any drift or bad hop announces itself as a step in the plot before it becomes a client conversation.

Frequently asked questions

What base station does a WingtraOne need?

Any receiver logging multi-constellation RINEX at 1 Hz within ~20–30 km, with trustworthy absolute coordinates — from a monument, OPUS/AUSPOS, or PPP self-convergence.

Can I use CORS data instead of my own base?

Yes, where a station exists within comfortable baseline range — download its RINEX for the flight window. Remote sites are exactly where that option disappears.

How do base coordinates affect Wingtra map accuracy?

Directly and totally: PPK positions the aircraft relative to the base, so the map’s absolute accuracy equals the base’s. Centimetre base, centimetre map.

Does a self-converging base help a PPK-only workflow?

Yes, twice: it solves its own absolute coordinates in ~3 minutes and simultaneously logs the RINEX the workflow needs — the two open requirements in one device.

Do I still need GCPs with Wingtra PPK?

Typically just 2–3 independent checkpoints for verification once the base is absolute — full grids retreat to legal work and hostile GNSS environments.