Speculation: Avionics in 5-10 Years?

[N804RV]

Originally Posted by DAGO

Yes, the rear hole did not have a clock.


The student flew and soloed from the rear seat. Communications between the student and instructor was one-way via a gosport (a speaking tube). The instructor would scream at the student via a mouthpiece. The student wore a stethoscope type of headset connected by the speaking tube. All the student could do was listen and comply with the instructions of the usually loud and highly animated instructor and then later get reamed out by the same after landing.





This was "avionics" in its purest form. Just required a pilot, a map, some roads or railroads to follow, a head on a swivel, and an understanding of colored flag or flare signals given for takeoff and landing clearances.

...{snip}....

Thanks! This made my day!

I spent a good deal of my private pilot time flying a Citabria with a "minimum required" VFR panel. Flew the darn thing all over the place with just a handheld GPS and a paper "nav log" for backup.

I'm an old avionics tech, and a bit of a gadget geek. But, sometimes my head hurt$$ from thinking about installing a "glass panel" in my -8.

[java]

Many of you guys are way to optimistic about what may happen. We're reaching the limits of what can be done in the plane... next step up is integration with control. And that will take A LONG TIME.

My expectation is that we'll get what we already have, but with fancier touch screens (already happening, but still not sold on that) and heads up display (liking the idea of that). Someone will eventually come up with auto-throttle for GA (which I don't see much use in) and auto-land (perhaps important for my passenger, in case I drop dead in cruise).

Whatever... it'll be fun to watch.

[the_other_dougreeves]

What will we get, or what do we need?

I'm amazed nobody has said this, but to me, the major problem with avionics is the user interface (UI). All of the modern EFIS UIs are different, and all of them have problems. But IMHO, the biggest problem is that they require the use your hands and look down. NO VOICE CONTROL.

Imagine the following, a not very hypothetical situation from a typical departure from ADS down to the glider club: [TODR presses "AVIONICS" button on stick] tune comm 1-2-4-point-3 "confirm comm dallas approach one-two-four-point-three?" yes [BING] swap comm [BING]

[TODR checks in with the friendly folks at Dallas approach]

THEN: [press "AVIONICS" button on stick] nav new flight plan current position direct dallas love field direct redbird airport direct midway airport direct TSA "confirm new flight plan direct D-A-L direct R-B-D direct J-W-Y? direct T-A-one-one" yes [BONG] [flight plan is automatically displayed on map with first leg highlighted, and ETE, leg distance and ETA displayed on MFD]

AND THEN: [press "AVIONICS" button on stick] autopilot engage follow flight plan climb this speed to 2 thousand 5 hundred [BONG] "autopilot engaged following current flight plan climbing at niner-five knots to 2 thousand 5 hundred" [appropriate AP symbology is displayed on PFD]

You get the idea. Voice control - when it is done properly - beats a ton of buttons and touch screens.

TODR

[erikpmort]

Originally Posted by the_other_dougreeves

What will we get, or what do we need?

I'm amazed nobody has said this, but to me, the major problem with avionics is the user interface (UI). All of the modern EFIS UIs are different, and all of them have problems. But IMHO, the biggest problem is that they require the use your hands and look down. NO VOICE CONTROL.

Imagine the following, a not very hypothetical situation from a typical departure from ADS down to the glider club: [TODR presses "AVIONICS" button on stick] tune comm 1-2-4-point-3 "confirm comm dallas approach one-two-four-point-three?" yes [BING] swap comm [BING]

[TODR checks in with the friendly folks at Dallas approach]

THEN: [press "AVIONICS" button on stick] nav new flight plan current position direct dallas love field direct redbird airport direct midway airport direct TSA "confirm new flight plan direct D-A-L direct R-B-D direct J-W-Y? direct T-A-one-one" yes [BONG] [flight plan is automatically displayed on map with first leg highlighted, and ETE, leg distance and ETA displayed on MFD]

AND THEN: [press "AVIONICS" button on stick] autopilot engage follow flight plan climb this speed to 2 thousand 5 hundred [BONG] "autopilot engaged following current flight plan climbing at niner-five knots to 2 thousand 5 hundred" [appropriate AP symbology is displayed on PFD]

You get the idea. Voice control - when it is done properly - beats a ton of buttons and touch screens.

TODR

Totally. And the technology is there for that. I mean in my iphone at least. UI IS where it's at. Why do you think apple is dominating the phone market- it's not the fastest or this or that, it's nice to use.

To me the big things I want in my plane is 100% traffic coverage for avoidance- excited for 2020. And the computer controlled mixture thing, can't remember the name of it. Again a lot of this stuff exists its all about prices coming down.

Great thread. I think improving safety with technology is so important.

[rjtjrt]

Eric
FADEC, I would think is the name you were after for the mixture.

John

[DaleB]

I have yet to see a voice control implementation that does not suck in devious and infuriating ways. Those could be dangerous in an aircraft. It would have to work a LOT better than the system in my truck, in my wife's car, on my phone or on those of 9 out of 10 people who use their voice-activated phones (yes, iThingies too) to send nearly incomprehensible text messages and emails.

[erikpmort]

Yeah that's it ! I would love that

[bruceh]

The reason your smart phone can do voice commands is that it is always connected to the network. The phone doesn't recognize your voice commands, but it can send the audio file quickly to a network then on to a huge server that figures out what you said. That's basically how Apple's Siri and Google Voice work.
That being said, the real trick will be bringing network connectivity to the cockpit and all of the avionics in your airplane can then talk to the internet.

[bret]

Originally Posted by bruceh

The reason your smart phone can do voice commands is that it is always connected to the network. The phone doesn't recognize your voice commands, but it can send the audio file quickly to a network then on to a huge server that figures out what you said. That's basically how Apple's Siri and Google Voice work.
That being said, the real trick will be bringing network connectivity to the cockpit and all of the avionics in your airplane can then talk to the internet.

Exactly, but, I hate my IPad for voice, my Samsung Galaxy 3 phone is much better for voice recognition, for some reason?

[Michael White]

Originally Posted by rgmwa

10 Years: HAL

Oh please! HAL is SO 2001....