> Like many unusual situations there are usually at least two things that need to happen to cause the scenario I described:
> 1) Ignorance to TFRs/NOTAMS (Notice to Airman for those unfamiliar).
> 2) Loss of communication with the correct air traffic control.
Yeah, #1 is easy enough to happen because NOTAM (and, while we're ranting, METAR as well, or the fact that aviation still uses feet and knots despite everyone but the US and UK being on metric) is fundamentally broken, a relic of very old times that has never been updated (similar to the clusterfuck that is flight/staff planning and booking) because no one wants to invest money into upgrading all the legacy crap. So all it takes for a serious incident is a simple human error: forgetting to change a comms frequency, overlooking a NOTAM in all the spam, or accidentally using metric units.
> I point out #2 because there's likely little industry support for the approach you describe. Additionally, you add an additional safety issue because users (pilots) will learn to depend on them and the variability of cell connectivity at altitude, weather, speed, geography, etc is uncertain. Aviation doesn't like that.
I wasn't talking about commercial air flights, I was referring to the Cessna and other small-scale GA. They're barely faster than a high-speed train (an 172 manages 300 km/h, a German ICE 350 km/h, and I can use LTE in the latter), so for wide parts of any GA flight a pilot should have LTE access on their phone.
Anyway: yes, people will learn to depend on their phones/tablets to alert them if they enter a TFR zone or that they have to change their radio frequency. But ffs... the status quo leads to so many issues every year [1], because pilots have zero assistance if they're in an older plane with a classic, no-glass setup, or in a plane with a glass cockpit but no assistance. Adding a fallback option is the safer way, it avoids incidents.
And the truly safe way would be to upgrade all the legacy crap, or at least augment it in a backward-compatible way: a digital carrier in radios that can carry cryptographically signed messages for radios that signal new frequency and squawk codes, for example, that the pilot simply has to confirm and be done.
> 1) Ignorance to TFRs/NOTAMS (Notice to Airman for those unfamiliar).
> 2) Loss of communication with the correct air traffic control.
Yeah, #1 is easy enough to happen because NOTAM (and, while we're ranting, METAR as well, or the fact that aviation still uses feet and knots despite everyone but the US and UK being on metric) is fundamentally broken, a relic of very old times that has never been updated (similar to the clusterfuck that is flight/staff planning and booking) because no one wants to invest money into upgrading all the legacy crap. So all it takes for a serious incident is a simple human error: forgetting to change a comms frequency, overlooking a NOTAM in all the spam, or accidentally using metric units.
> I point out #2 because there's likely little industry support for the approach you describe. Additionally, you add an additional safety issue because users (pilots) will learn to depend on them and the variability of cell connectivity at altitude, weather, speed, geography, etc is uncertain. Aviation doesn't like that.
I wasn't talking about commercial air flights, I was referring to the Cessna and other small-scale GA. They're barely faster than a high-speed train (an 172 manages 300 km/h, a German ICE 350 km/h, and I can use LTE in the latter), so for wide parts of any GA flight a pilot should have LTE access on their phone.
Anyway: yes, people will learn to depend on their phones/tablets to alert them if they enter a TFR zone or that they have to change their radio frequency. But ffs... the status quo leads to so many issues every year [1], because pilots have zero assistance if they're in an older plane with a classic, no-glass setup, or in a plane with a glass cockpit but no assistance. Adding a fallback option is the safer way, it avoids incidents.
And the truly safe way would be to upgrade all the legacy crap, or at least augment it in a backward-compatible way: a digital carrier in radios that can carry cryptographically signed messages for radios that signal new frequency and squawk codes, for example, that the pilot simply has to confirm and be done.
[1] https://aviation.stackexchange.com/questions/8751/how-often-...