From: Ulrich Speidel <u.speidel@auckland.ac.nz>
To: starlink@lists.bufferbloat.net
Subject: [Starlink] Re: Podcast on in-flight Wi-Fi (Candela Technologies)
Date: Tue, 13 Jan 2026 10:06:47 +1300 [thread overview]
Message-ID: <23685b96-0e02-43d4-96b9-586f340bc937@auckland.ac.nz> (raw)
In-Reply-To: <CAJUtOOgvyrt=RC4_PF2NS6+EL2AL8heTbDN+iyXtwwBd+rJAcw@mail.gmail.com>
Aircraft-to-ground is fraught with problems: For one, the range here is
at best a couple of hundred miles and this means much of the planet is
out of range here even with ground infrastructure on land. It's also
essentially using cellphone technology, and not in the way it was
intended (spectrum sharing by localising communication).
On-board Wi-Fi is generally using Ka-band backhaul. Since planes in
cruise are above the weather, rain fade isn't an issue here and you
don't need the big antennas for reserve gain that you'd find on Ka-band
ground stations.
Starlink is attractive for backhaul due to the fact that it covers the
whole globe, unlike geostationary sats, which drop below the horizon in
polar areas. That's not an issue for about 99% of the world's commercial
traffic, but it is an issue for flights from Japan and Korea to Europe,
which used to go via Russia but now trek up to Alaska and the Beaufort
Sea and Arctic Ocean to fly into Europe via northern Greenland. GEO
coverage drops out at about 72N shortly after you enter the airspace
over the Beaufort see and doesn't return until you've almost passed
Greenland. This is of course the most boring part of the 14 hour flight
where connectivity would be welcome ;-) Japan Airlines actually warn you
about this effect on their seat pocket Wi-Fi instruction card.
And yes, capacity is very limited. Air New Zealand offer free Wi-Fi (Ka
via GEO) on most of their fleet and normally it's OK. A while ago I
found myself on one of their overnight flights from Narita to Auckland
and found the cabin almost empty when I boarded. Faint hope for a
lie-down though as soon after, I was joined by several Japanese school
classes in their young teens who occupied almost all of the remaining
seats. A cheeky crew member walked up to me asking whether I was in
charge of the lot (aaargh no!) but then proceeded to rescue me to an
empty row for myself. Of course, the kids worked out the Wi-Fi in no
time and it was essentially unusable for most of the flight.
On 12/01/2026 8:17 pm, Frantisek Borsik via Starlink wrote:
> https://www.youtube.com/watch?v=MEX_OqhZKHE
>
> All the best,
>
> Frank
>
> Frantisek (Frank) Borsik
>
>
> *In loving memory of Dave Täht: *1965-2025
>
> https://libreqos.io/2025/04/01/in-loving-memory-of-dave/
>
>
> https://www.linkedin.com/in/frantisekborsik
>
> Signal, Telegram, WhatsApp: +421919416714
>
> iMessage, mobile: +420775230885
>
> Skype: casioa5302ca
>
> frantisek.borsik@gmail.com
> _______________________________________________
> Starlink mailing list -- starlink@lists.bufferbloat.net
> To unsubscribe send an email to starlink-leave@lists.bufferbloat.net
--
****************************************************************
Dr. Ulrich Speidel
School of Computer Science
Room 303S.594 (City Campus)
The University of Auckland
u.speidel@auckland.ac.nz
http://www.cs.auckland.ac.nz/~ulrich/
****************************************************************
next prev parent reply other threads:[~2026-01-12 21:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-12 7:17 [Starlink] Podcast on in-flight Wi-Fi (Candela Technologies) Frantisek Borsik
2026-01-12 15:05 ` [Starlink] " J Pan
2026-01-12 21:06 ` Ulrich Speidel [this message]
2026-01-13 1:02 ` David Lang
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://lists.bufferbloat.net/postorius/lists/starlink.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=23685b96-0e02-43d4-96b9-586f340bc937@auckland.ac.nz \
--to=u.speidel@auckland.ac.nz \
--cc=starlink@lists.bufferbloat.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox