I’m not a pilot, but I just flew a helicopter over California
nytimes.com
nytimes.com
Sounds like the author just took a normal flying lesson but didn't call it that so they could write it up as a marketing piece for an app. Why the NYTimes ran it is beyond m… oh right money.
In my case, "with ZERO flight experience, I walked into a busy airport and within minutes I was at the controls of a full-sized airplane hurtling toward the White House!!" Translation: I signed up for a flight lesson during which my instructor let me turn the two-seater single propeller plane 360°. Both statements about that same event are technically true; one is so misleading it's basically a lie. (BTW it's called a "discovery flight" and it's super fun—highly recommend!)
The Gray Lady Winked: How the New York Times's Misreporting, Distortions and Fabrications Radically Alter History
https://www.amazon.com/Gray-Lady-Winked-Misreporting-Fabrica...
In 2007 I landed a small plane with zero flight experience! I mean, that was actually the point of the exercise, but that's how it goes. Maybe if I marketed myself better I could have had an article in the new york times.
It seems almost every article is just another form of advertisement. Someone pays in some way and then the article has an agenda with implied call to action, or what I call, "call to thought".
I think it makes sense because we've been in with the Internet and Web 2.0 for a long time now and we don't need centralized curated content anymore, so these editorials have to now make money from selling their influence and promotional powers more so than just information.
The reason you don’t see small helicopters or fixed wing aircraft with complex autopilot systems coupled to the flight controls is that it’s expensive for a lot of the reasons you want it to be - the reliability, airworthiness and usability requirements that make it safe are also expensive to implement. At that price point it’s usually easier to have a human do all that work, especially for the types of missions those aircraft do. The technology has been there for decades, and there’s probably a reason why it hasn’t trickled down to these sorts of small aircraft yet.
Also, do you really want your flight control system to be entirely reliant on ensuring that the latest update to iOS doesn’t inadvertently brick the app that lets you control your aircraft? Let alone the possibility of someone exploiting a vulnerability in iOS to degrade your flight performance. There’s a reason that flight software is not trivially updated.
It’s not a stretch to go from there to a Bluetooth -> serial adapter. I remember years ago one android app even went to the extent of documenting how to do so.
Most helicopter 135 operators self-limit to VFR only, perhaps this is something like a VFR only autopilot they have in mind?
The use of the word "protocols" underlines that it's kind of weird that we're still handling these comms through scratchy, staticy analog radio with humans at both ends. ATC uses computers to track flights and assign flight paths, why is it so difficult to have their computers talk directly with the aircraft? And I don't even mean remotely controlled flight, just "here's what ATC is asking you to do, press button to ack".
That's mostly a rhetorical question, mind you, since modernizing ATC is a notoriously difficult problem and FAA's NextGen has been under construction since 2007, with vague hopes of getting something usable by 2025. But still.
https://en.wikipedia.org/wiki/Next_Generation_Air_Transporta...
I think pilots get a lot of situational awareness as well from listening to the common frequency.
I don't pretend to know much about aircraft control, but my understanding is that controllers generally are hopping between several planes in quick succession and they follow a strict subset of English when communicating with pilots. So, I'd be surprised if the task required advanced reasoning skills that would be impossible recreate in an algorithm.
> I think pilots get a lot of situational awareness as well from listening to the common frequency.
That seems like it could be solved in other ways though. For instance, the airport could publish the relevant information into a data stream and broadcast it to air traffic.
It could be displayed on a screen within the cockpit. The cockpit could also have a computer that read certain information aloud to the pilots to provide important information without them needing to look at the screen. Furthermore, airports could broadcast the same alerts on the old analogue radio channels to legacy aircraft.
That's already a thing with the big aircraft: https://en.wikipedia.org/wiki/ACARS
You can decode them on your SDR, they're in-the-clear:
VHF ACARS (fairly local):
https://www.youtube.com/watch?v=xGD_GFxH9ps
and the satellite version of the system here (every aircraft shares 1 of 4 geosynchronous satellites and you can pick up some interesting things):
CPDLC exists today and has been in use for a couple of decades: https://en.wikipedia.org/wiki/Controller%E2%80%93pilot_data_...
However, like everything in aviation, progress is slow because aircraft are expensive to buy, can last a long time, and are very expensive to modify.
At this point, if we go to Mars, I'd like to be incharge and a gatekeeper for UX/UI. It is not possible to fix the world as it is here on Earth.
"Swipe up and hold to eject!" chirps Alexa as we plunge 200 feet in 2 seconds...
The trouble today is that systems can fail, weather can change, and unlike a car you can’t just stop on the side of the road until the issue is fixed.
EDIT: remove unnecessary contextualization
The key quote is this: "You still need someone with training in communications protocols, what speed and elevation to fly and where the system is unsafe to operate."
Flying a helicopter is, by its nature, unsafe to operate. At any moment, you could have an emergency. If you have someone at the controls who only knows joystick flight when any such emergency occurs, good luck to them.
Helicopters are not like airplanes; they are not a "set and forget" experience. You have to actually fly the helicopter from point A to point B. You have to be ready to make that helicopter drop at a moment's notice because if the engine dies, you need air blowing up through the rotor to keep it spinning. If it slows down enough, that is automatically "Game Over". (Search "rotor stall".) In the helicopter I flew, you had two seconds to get the collective down, and that was only the beginning.
Watch [1]. At 1:24, the engine dies, and you hear a horn almost immediately. That's the low rotor speed horn. The horn goes off after about a second; that's because the pilot slammed the collective full down.
Then the pilot turns left and crash lands. Why? Because there were wires in front of him. The wires could have flipped the helicopter. Would a bot have flown into those wires? Almost certainly, and everyone would be dead.
Oh, and did you notice that the low rotor speed horn was sounding a lot during the crash sequence? That's because during such an event, you have to maintain the rotor speed in balance while trying to pick a spot and bring the helicopter in. He had a full helicopter, so he actually couldn't force the rotor speed much higher. And yet he couldn't go full down either because that would not slow them down near the ground.
In other words, those guys are lucky that their pilot is awesome. And even though he was, they still landed hard.
On top of that, as dmitrygr says [2], flying the helicopter is a fraction of what you have to do.
I would never fly in a helicopter where the "pilot" was anything but.
And the same goes for airplanes. They may be able to fly themselves, but that is only true in non-emergencies. And even in some non-emergencies.
Pilots are expensive because they train for the worst, and most of the time, when it does happen, they handle it with aplomb.
Bots will not. When it comes down to it, bots will never replace humans where life-threatening emergencies can happen.
In a smaller aircraft, you're relying a lot more on your forward momentum (i.e. forward airspeed) to cushion your landing, whereas in a larger helicopter the rotor inertia has enough energy such that you can place it straight down on pretty much any flat surface the system can find. Garmin already has something called Smart Glide for fixed wing aircraft where it calculates engine out trajectories, and so I don't see this as something impossible with a helicopter. Especially coupled with a wire strike cut (basically just a sharp knife sticking out of the front of the helicopter that just cuts any cables you run into).
I'd think given the use cases for some helicopter flights (e.g. sightseeing tours) where you're typically in VFR weather there's certainly an opportunity to have automated flights. I agree we're not there yet, but I don't see it as impossible in the near future.
(I mainly fly fixed-wing, but I have about 50 hours in an R22)
You are correct that a lot can be automated, but if there is anything that cannot be, humans have to be in the cockpit. And if humans have to be in the cockpit, then we actually don't want as much automation as possible. [1] See also [2].
The biggest problem I see with automating helicopter flight is that the hardest part of an autorotation is picking a spot to land. I don't think that can be automated. You would either have to have super high resolution radar pointed at the ground or high resolution computer vision that can identify flat spots which are as varied as the human race. I don't think either is feasible anytime soon. And that's without even considering the higher power draw they would require, as a sibling comment mentions.
Then you have to consider what happens in the case of full power outage, including no battery. In that case, you have effectively doomed the people onboard if there is not a real pilot.
[1]: https://www.nbcnews.com/news/us-news/airline-pilots-depend-t...
There was no better way to guarantee that I (a network manager at the time), would ever be in that aircraft with its wheels off the ground.