> they wrote ETOPS regulations ... then failed to apply that to their software
you are pointing out that they prioritized that planes in the air could land safely over allowing more planes to take off. I'm actually quite reassured now.
>The issue is when shit hits the fan then will you be able to depend on communications with air traffic control?
Yes, when the SHTF aircraft comms will work as designed, not even close to the same frequency bands, nor modulation techniques, nor power output levels. Not even a slight chance that cell phones will interfere.
In my minimal experience with airplane crashes[1], the aircraft's electrical system was kaput, and I relayed communications to/from ATC and Fire Dept. via ... wait for it, the pilot's personal cell phone.
[1] I ran an FBO at a tiny municipal airport during college (I re-fueled aircraft). I only participated in a few airplane crashes during my tenure there.
> I signed a petition against the White House's plan to put airport usage fees in place for general aviation, effectively charging pilots to talk to air traffic control. This is a Really Bad Idea (I'm happy to delineiate why in future comments if there is interest but for now I'll play the "I'm a pilot, trust me" card).
Well, I'm interested.
The obvious guess that comes to mind is that pilots are now incentivized to avoid communication with ATC, consequentially reducing ATC's effectiveness. Is there something more subtle going on?
More interesting question is why the WH thought it was a good idea. Who was lobbying for it? I was under the impression that whatever union or union-like organization is built around ATC folks is pretty adamant about promoting safety stuff, and would never tolerate something like this.
> Are you _absolutely_ certain you can prevent unauthorized use of this channel? Keep in mind what you're proposing is that hundreds of semi-independent agencies have the ability to push this information directly into the aircraft FMC.
Er, no, that's not what I'm proposing.
I'm proposing a way to get the six pieces of complex information from the ATC onto a display which the pilot can read, to avoid the pilot having to remember/write down those six pieces of information in a potentially information-dense situation. I would have this in addition to the existing voice control as a backup. The pilot still does the flying.
> But the flight plan wasn't erroneous - it was perfectly valid.
Well. Then the real issue is that a single flight plan, erroneous or not, should not stop the full system. It should flag that flight plan for problem resolution and keep on working with the rest of the flight plans.
Would result in a slightly inconvenienced flight dispatcher, or worst case an inconvenienced flight, instead of a nationwide shutdown.
> The real issue is that a single erroneous flight plan should not stop the full system.
But the flight plan wasn't erroneous - it was perfectly valid. It just happened to have a weird coincidence of two identically tagged airports spanning the UK. If someone had put an extra waypoint in between the two, nothing would have broken (AIUI).
> People keep saying that yet no one has been able to define to me what “legitimate interest” the public has for tracking a private plane. I don’t believe one exists.
If you have an objection to this tracking, you'd have to take it up with the FAA. Because the legitimate interest is that the rules require airplanes to transmit this information any anyone is free to listen to it.
Which is a great thing for aviation safety, so I'm glad the rules exist.
> I think those that dismiss this concern entirely are the folks who cannot think critically.
So if you don't agree, you can't think critically. Got it.
Or maybe, we did think about it critically and simply don't agree.
There are various way this can be solved. We have modern encryption that could make this far, far safer then it is today. We have methods from data leaking. We have process to only allow data to be decrypted if required.
This would actually force us to really think critically about who has what access when. In planing this the airlines, unions, FAA should sit together with some technical experts and think of this critically.
This seems less complex to me then a modern high bypass turbo engine.
There’s a meaningful difference between providing cover and reminding people that major systems like the one in question are in a different category than the average web app.
The fact that such a nationwide stoppage hasn’t occurred since 2001 speaks to the stability of these systems, and I’m not sure what you’re suggesting here.
> There is a reason this was broken and grounded flights nationwide. Providing cover for systems that allowed this to happen is not productive.
I’m not trying to sound snarky here, but things do tend to break for reasons. Are you suggesting that there is a cure?
> The agency is primarily a regulatory body, responsible for keeping the national airspace safe, and yet it is also in charge of operating air traffic control, an inherent conflict that causes big issues when it comes to upgrades.
There's no conflict there.
Now NSA meant to keep US infrastructure safe, and attack US companies/people is a conflict. But the FAA being responsible for both safety and ATC is far from a conflict.
I'd prefer the FAA moved slowly and got it right. This isn't an area where young-hip 20 somethings re-invented the tech' in the latest web-2.0 fad. This is an area where you want mathematically provable correctness and unit testing up the ying-yang.
> Air travel is very safe and regulated because of behavior that persisted until recently
Air travel is very safe because the entire world of aviation has focused on analysis and improvement rather than infighting and blaming. If anything, I worry more about how the aviation community worldwide seems to be fragmenting right now, and the effect that may have on safety going forward.
But then I do read stories about the FAA and EASA still cooperating very tightly and respectfully, realize most of the infighting is by armchair quarterbacks on the Internet and the pros are still doing the Right Thing, and I sleep a little better.
> so this was illegal.
> In both cases a management
> issue.
I think attempting to call the other ATC 11 (!) times in the span of a couple of minutes before the crash goes way beyond a management issue, it's also a cultural issue.
Those controllers were looking at a screen showing that two airplanes were about to crash into one another.
In most other western countries that person would have thought "well, fuck this!" and started yelling at them on the channel itself, implied procedures, stepping on toes, and pecking order be damned.
I'm ok with this.
reply