Collins/ARINC is used for oceanic HF radio. They run "San Francisco Radio" and "New York Radio" specifically, which are the HF radio operators that relay oceanic messages to ATC.
(They also own a small number of private VHF stations for relaying company messages to air carrier operations domestically, but these aren't used for ATC purposes.)
Otherwise, the VHF radio links are operated directly by FAA TechOps.
L3Harris owns the telecommunications backhaul between facilities.
Yes, I doubt someone pushed out an update minutes before the outage. The hard bugs are the ones that take a long time to impact a system and don't always appear in testing.
Most of these systems started out as teletype printers, back in the day. The teletype systems only had an all-caps character set.
Aviation is global, and we still need to interop with countries and airports that still use actual teletype. So the legacy protocols still remain, even though much of it is tunneled over IP links now.
Also: The keyboards used in both airplanes and in ATC facilities are often special reduced-footprint keyboards without shift/caps keys. (They're also often ABC layout rather than QWERTY.) So there's that, too.
Actual teletype machines? No. (Though flight strip printers used at ATC consoles are basically mini teletype printers.)
However, AFTN (used for disseminating flight plans and weather between ATC facilities) still uses landline modems running TTY-originated protocols.
In the US we've moved moved off AFTN in favor of AMHS/X.400, as have most countries - but my understanding is there's still some last holdouts that haven't fully switched over.
Most air traffic is IFR. You definitely need radio for IFR traffic in for deconfliction in most of the world. (There's a few exceptions in very remote places, but that's mostly academic.) Even legacy procedural (non-radar) separation assumes you have working radio, and a radio failure is an emergency.
VFR traffic doesn't necessarily need radio, and is not affected by this groundstop.
You don’t need radio for IFR (as the whole point of a flight plan is that if you lose contact you continue to fly your plan). But you kind of do need radar.
You actually don't need radar, and ATC can do non-radar "procedural" control where they block off sections of airways or entire airports, one-in one-out at a time, like sections of railroad track. There are still a few parts of the remote US, as well as large sections of Northern Canada, where radar coverage is nonexistant and ATC is done via procedural control. Radar outages also happen on occasion, which would necessitate this.
As for lack of radio, this would only work if ATC blocked out your entire route from start to finish - which isn't practically ever done. Otherwise, they need to be able to maintain positive control over your flight since the airspace isn't reserved, which means conflicts are possible.
If you lose radio communication, it's an emergency and they'll move everyone out of your way. This doesn't work very well if everyone loses radio communication simultaneously.
Right, but isn't a lot of that necessary radio aircraft-to-aircraft, like ADS-B? Obviously not ideal, but I thought IFR traffic could feasibly maintain separation without ATC help.
ADS-B can't legally be used to maintain separation. It's only approved for use as an aid to awareness for additional safety.
Could you in an emergency, if you had no other options? Yes. But ATC can't legally give you a clearance that was dependent on using ADS-B for separation.
(Similarly, if there's a potential traffic conflict, and you tell ATC you see the other traffic on your ADS-B display, they just have to disregard that statement and assume that you can't see the other aircraft at all.)
You can definitely file a flight plan later than that. 30 minutes before departure is the recommended filing time (per AIM 5-1-6), but you can even file for an immediate departure. It's just that at less then 30 minutes additional delay is possible, depending on backend handling and human processing. But in most cases the strip will print within a minute or two of submitting the flight plan.
But also, this is about when the flight plans expire out of the system if they're not activated for departure - so it's saying unused flight plans won't be deleted for 4 hours, so pilots won't have to refile for departure.
There isn't really one. This is a system that's supposed to have it's own built in redundancy and must not go down.
Flight Service uses a different set of radios and can relay messages to ATC, but they've been slowly dismantled over the last two decades and wouldn't have the capacity to step in for an outage (nor should they be expected to - that's not their purpose).
Some aircraft have CPDLC for text-based communication, but it's asynchronous and you can't use that as a replacement for voice communication in the terminal environment. Also, many aircraft aren't equipped to receive it.
Pilots are trained on lost comms procedures, so if you're in the air and the radio fails they'd fall back to those regulations. Basically all the aircraft would fly their last assigned clearance, and attempt to deconflict manually with other aircraft over air-to-air radio (similar to flying into an untowered airport).
Indeed. There's plenty of National Forests (not National Parks) with near zero cell service, and often even less once you start venturing into undeveloped BLM land.
To be fair, putting satellites in space is very expensive so the chances of it not being owned by some billionaire asshole is zero. But some billionaire assholes are better than others.
I'm amazed MS Paint is somehow up to version 11, let alone 11.2605 (!). I literally can't remember the last time I used it, but what are they even changing?
I remember when I was doing pixel art, there were some purists that insisted that using layers and transparency/opacity to create windows for your buildings is more or less cheating. According to them, one should manually figure out what the color palette should be for things seen through a window.
Anyway, I continued using layers and transparency/opacity. Pixel art was hard enough already for me, so I didn’t feel that it made sense to artificially make it even more difficult for myself at the time. I had enough other aspects of pixel art to work out already in order to try to get better at it.
And create single-pixel images. My most used application of Paint by far is creating single-pixel PNG files to work around the fact that "solid color" is not an option for lock/login screen backgrounds.
There's some suggestion there that shapes (including lines) are separate entities from pixels. Wikipedia references a now-deleted answers.microsoft.com version of the first question https://web.archive.org/web/20250203164656/https://answers.m... with a couple of people saying that resize is useless. Wiki also says "re-copied" images blur, which is why I wondered if that meant pasting. Also this: https://learn.microsoft.com/en-us/answers/questions/5673783/... a complaint that the tool for drawing pixels doesn't indicate exactly which pixel it will draw to.
I can't reproduce any of those issues. When drawing the indicator snaps to a pixel, so it's perfectly clear where it's going. When I draw a line, it's pixel-perfect when moving the control points, likewise after it finalises. And when I copy a section of the image and paste it back in, it's pixel-perfect as I move and when I finalise. There doesn't seem to be a true resize; all I seem to be able to do is change the size of the canvas, which doesn't add any kind of aliasing.
But I've only used the program for less than 5 minutes, so maybe it's configured differently?
Reminds me of Zawinski's Law of Software Envelopment[^1,2]: "Every program attempts to expand until it can read mail. Those programs which cannot so expand are replaced by ones which can."
I hope MS is not getting exclusive right for manufacturing spoons because I want mine to scoop up stuff like soup or ice-cream without smart features activated by elegant touch UI on the handle like cutting down trees being in the way to the grocery store to 'elevate user experience', or others. This stuffing more and more into everything and anything for the sake of shock and awe is a stupid (and dangerous) thing.
You haven't spotted that it's regularly being released the month following the revision number. (-: Because Microsoft will of course have a release pipeline that things have to go through.
They're not a positional notation. It's version 11.2605.91 recently. It was 11.2605.81 earlier this year. There was an 11.2605.71 and an 11.2605.61 before that. Last year, there was a 11.2504.451 . The year before there was a 11.2402.32 .
Microsoft's versioning systems are not 4 columns where a tick around of one increments the one before it. The easiest way to think of them is madness made for marketing purposes. (Windows NT starting at 3.1, for example.) There is some logic to it, but nowadays it's often four entirely different things jammed together, ticking around independently. Like the version of Windows, the year and month of the release, and perhaps a daily build number or some such.
Windows NT itself has a monotonically increasing build number as part of its versioning that started some time in 1992 and is currently just over 26 thousand.
Windows 7 added ribbons to the UI. It's unlikely it was a rewrite. Just a retooling of what Vista had, which in turn what Windows XP had, which... [continue down the line until Windows 1.0].
You can't have finished software any more. It's now illegal or something. Must keep changing things forever. And must add some AI features of course, to make the VCs happy.
> Weather data can be published every minute and shown live as a full map over the screen
This already exists via FIS-B.
> not as random abbreviations of wind and cloud coverage
The abbreviations (METARs) are a feature, not a bug. There are numerical legal minimums for weather that determine whether a landing is legal or not. A graphical map doesn't tell you this. The METARs are condensed because they're easy for professional pilots to skim.
(Back in the days of teletypes they also saved bandwidth, but that's just a historical note at this point.)
Regardless, pilots already have access to both textual and graphical weather products in the cockpit.
> And we already know where each aircraft is, and where they took off, and where they're headed. So practically speaking the radio talk can be limited to only the important communication and emergencies, while increasing the situational awareness by at least ten fold.
As a pilot myself, I think you're vastly misunderstanding the nature of ATC communication. 90% of communication on the radio are time-sensitve, important things - mostly heading and altitude changes to avoid other traffic.
Weather and clearances (when not relayed by ACARS, FIS-B, or CPDLC) are routinely handled on dedicated frequencies and aren't really causing meaningful frequency congestion.
(They also own a small number of private VHF stations for relaying company messages to air carrier operations domestically, but these aren't used for ATC purposes.)
Otherwise, the VHF radio links are operated directly by FAA TechOps.
L3Harris owns the telecommunications backhaul between facilities.
reply