REVIEW 3 major objections 3 minor
A First Look at Starlink In-Flight Performance: An Intercontinental Empirical Study
T0 review · 3 major / 3 minor · reviewed 2026-08-05 · deepseek-v4-flash
Pith's one-line read An in-flight Starlink terminal on an aircraft achieves median downlink throughput of 64 Mbps and uplink throughput of 24 Mbps, with uplink performance varying by altitude.
desk verdict A genuinely first in-flight Starlink measurement set with usable numbers, but the altitude analysis in the abstract is under-specified and likely confounded with descent phase and geography. read the letter →
The pith
A machine-rendered reading of the paper's core claim, the machinery that carries it, and where it could break.
The reading
What carries the argument
The measurement campaign itself is the machinery: a Starlink terminal onboard an aircraft, with a single user device running throughput and ping tests during flights over the Baltic Sea and the Pacific Ocean. Altitude-stratified analysis splits results at 17,000 feet. Ping measurements aimed at different ground stations, together with inter-satellite links (ISLs, the links that pass traffic directly between satellites), are used to separate the latency contributors.
What would settle it
Overfly the same ground station at two altitudes in level flight, pinging a fixed target: if uplink throughput is the same at high and low altitude, the reported descent slowdown is caused by route or handover rather than altitude; if uplink drops at low altitude with the ground station held fixed, the altitude explanation survives.
Extended reading notes
Core claim
The central discovery is an empirical baseline for in-flight Starlink performance measured from a single user device. Across intercontinental flights, the service delivered median downlink throughput of 64 Mbps and median uplink throughput of 24 Mbps. The uplink degraded with the aircraft's descent: median throughput was about 33 Mbps above 17,000 feet and fell to around 20 Mbps at lower altitudes. Round-trip time depended strongly on the location of the ground station being pinged and on the use of inter-satellite links, and the paper uses 5.5 hours of ping measurements over the Pacific Ocean to explore queuing at satellites, ISL routing, and feeder-link congestion as sources of deviation f
Load-bearing premise
The paper attributes the uplink slowdown during descent to altitude, but descent also changes the flight's location, ground-station distances, and satellite handovers, so altitude and those co-varying factors are entangled.
Editorial extensions
If this is right
- Aviation connectivity baselines should be altitude-aware: uplink capacity at cruise altitude appears to be roughly 1.6 times the uplink capacity during descent.
- User-perceived latency on in-flight Starlink cannot be read off satellite altitude alone; ground-station location and ISL routing are primary factors.
- The 5.5 hours of Pacific ping data give a starting point for separating satellite queuing, feeder-link congestion, and ISL routing as distinct latency sources.
- The paper's comparison of a ground terminal and an aircraft terminal frames in-flight performance against residential expectations, giving airlines a concrete service-quality reference.
Reading between the lines
- If the altitude effect is causal, upload-heavy tasks on flights could be scheduled during cruise to roughly double effective uplink throughput compared with descent; the paper does not state this operational consequence.
- Because RTT tracks ground-station location, a route-level latency forecast for a planned flight could be built from the constellation's ground-station map without new onboard hardware.
- The descent-phase uplink drop may also occur for terrestrial mobile users whenever the elevation angle to the satellite changes quickly; a roadside or maritime test would show whether the effect is altitude-specific or more general.
- A controlled test overflying the same ground station at high and low altitudes would tell whether the 17,000-foot split is altitude itself or the geography and handovers that accompany descent.
Signed reviews
Editorial analysis
A structured set of objections, weighed in public.
Referee Report
Summary. The paper reports an empirical measurement study of Starlink in-flight performance, based on measurements over the Baltic Sea and the Pacific Ocean. The abstract claims that a single user device achieves median downlink throughput of 64 Mbps and median uplink throughput of 24 Mbps, with uplink throughput approximately 33 Mbps above 17,000 feet and dropping to around 20 Mbps during descent. It also reports that round-trip time (RTT) depends strongly on the location of the pinged ground station and on the use of inter-satellite links, and it compares in-flight performance to a ground terminal from a residential user's perspective.
Significance. If the empirical results hold, the paper provides a useful first benchmark for aviation-grade Starlink performance, a domain that has seen rapid deployment but little published measurement. The intercontinental scope—Baltic Sea and Pacific Ocean—and the comparison with fixed ground-terminal performance are valuable. The RTT analysis using 5.5 hours of ping data also addresses an under-explored area of LEO satellite network behavior. However, the claims as stated in the abstract lack the methodological detail and statistical support needed to establish the central altitude-related finding.
major comments (3)
- [Abstract] The central claim that uplink throughput drops from ~33 Mbps above 17,000 ft to ~20 Mbps at lower altitudes is confounded with flight phase and geography. Descent typically coincides with approach to an airport, changes in ground-station access, satellite elevation, and ISL routing. The abstract gives no route information, ground-station locations, or data on whether the lower-altitude segments occur over different regions. Without per-phase controls or matched pairs, the 13 Mbps gap cannot be attributed to altitude rather than co-varying location or coverage conditions.
- [Abstract] No sample sizes, number of flights, measurement dates, or equipment details are provided. The term 'single user device' does not identify the Starlink terminal hardware, antenna generation, or measurement software. This missing information is essential for reproducibility and for judging whether the results generalize across aircraft, routes, or network configurations.
- [Abstract] The throughput and RTT results are reported as point values ('approximately 33 Mbps', 'around 20 Mbps') without confidence intervals, percentiles, or statistical tests. The phrase 'significant reduction' is used for the uplink drop, but no significance test or effect-size measure is mentioned. Without this, the reader cannot assess whether the observed differences are stable or within measurement noise.
minor comments (3)
- [Abstract] The 17,000-ft threshold appears to be chosen after observing the data. If so, a brief justification or a data-driven selection procedure (e.g., changepoint detection) would strengthen the analysis; otherwise the threshold should be described as a post hoc split.
- [Abstract] The RTT discussion mentions 5.5 hours of ping measurements over the Pacific but does not state how many flights, ping targets, or measurement sessions this includes. Clarifying this would improve interpretability.
- [Abstract] The abstract uses imprecise language ('approximately 33 Mbps', 'around 20 Mbps') for median values. Reporting exact medians and interquartile ranges would increase precision.
Circularity Check
No circularity: empirical measurement study with direct observations and no fitted-parameter derivation.
full rationale
The paper is an empirical measurement study. The reported median downlink (64 Mbps) and uplink (24 Mbps) throughputs, the altitude-stratified uplink medians (~33 Mbps above 17,000 ft and ~20 Mbps below), and the RTT observations are presented as direct measurements of Starlink performance during flights, not as outputs of a model derived from those same measurements. There is no fitted parameter later renamed as a prediction, no quantity defined in terms of the quantity it is supposed to explain, and no load-bearing self-citation chain visible in the abstract. The 17,000-ft altitude split is an analytic threshold applied to measured data; whether it is confounded with descent path or ground-station geography is a validity/soundness concern, not a circularity concern. The RTT discussion hypothesizes causes (ISL routing, queuing, feeder congestion) but does not claim to derive those causes from the same RTT data in a tautological way. Since the review is abstract-only and the full derivation chain is not available, there is no quoted textual evidence of a specific reduction of a claimed result to its own inputs. Therefore the appropriate finding is no significant circularity, score 0.
Assumptions & free parameters
free parameters (1)
- Altitude threshold for cruise/descent split =
17,000 feet
assumptions (3)
- domain assumption A single user device with the aircraft's Starlink installation provides throughput and RTT samples representative of in-flight service.
- domain assumption Measured RTT deviations are attributable to network-internal causes (ISL routing, satellite queuing, feeder congestion) rather than to the measurement path or device.
- domain assumption Altitude, not co-varying route or ground-station geometry, explains the uplink throughput difference above and below 17,000 ft.
Cite this review
Pith. "Pith review of A First Look at Starlink In-Flight Performance: An Intercontinental Empirical Study." pith.science (2026). https://pith.science/paper/FPFCAZXP
@misc{pith2026250809839,
author = {Pith},
title = {Pith review of: A First Look at Starlink In-Flight Performance: An Intercontinental Empirical Study},
year = {2026},
howpublished = {\url{https://pith.science/paper/FPFCAZXP}},
note = {Machine review of arXiv:2508.09839}
}
read the original abstract
Starlink delivers Internet services to users across terrestrial, maritime, and aviation domains. The prior works have studied its performance at fixed sites and in-motion vehicles, while an in-depth analysis of in-flight performance remains absent. With major airlines now offering Starlink Internet onboard, there is a growing need to evaluate and improve its performance for aviation users. This paper addresses this shortcoming by conducting in-flight measurements over the Baltic Sea and the Pacific Ocean. Our measurement results show that a single user device experiences median throughputs of 64 Mbps and 24 Mbps for the downlink and uplink, respectively. The median uplink throughput is approximately 33 Mbps when the aircraft maintains an altitude above 17,000 feet. However, a significant reduction in uplink performance is observed during the aircraft descent phase, with the median throughput dropping to around 20 Mbps at lower altitudes. Round-trip time (RTT) is highly dependent on the location of the ground station being pinged and the use of inter-satellite links (ISLs). We dive deeper into 5.5 hours of ping measurements collected over the Pacific Ocean and investigate factors influencing RTT, hypothesizing that ISLs routing, data queuing at satellites, and feeder link congestion contribute to deviations from theoretical values. For comparative analysis, we evaluate the Starlink ground terminal and in-flight connectivity performance from the perspectives of a residential user and an airline passenger, respectively.
Reviewed August 5, 2026 · model on record in the stance chip above.
Discussion (0). Continue with ORCID to comment.