AOA widget scale

[diablouser]

I find the current AOA widget almost useless when I want to use it most.  It is so small that you can't find it at a glance while in the pattern when it should be eyeballs out.  The audio is good in the flare and sometimes, when you get lucky,  touchdown and stall agree.

However it should be a relatively simple programming add to do this.

When the airspeed drops to a user set speed the widget expands to the size of the airspeed tape and is just to its right. 

Now it can be seen at a glance.  On my RV-10 I would  set it around 85 knots, on my S-20 about 50.

Bruce Patton

 

[skyview_user]

+1

 

[gtae07]

When the airspeed drops to a user set speed the widget expands to the size of the airspeed tape and is just to its right.

Keying it off airspeed defeats half the purpose of AOA and means it might not be there in maneuvering flight or other accelerated stall situations.

I'd rather see a remote display and some way to make the widget behave differently--to me it makes more intuitive sense to have it start out "empty", add bars as AOA increases, and start at the top of the widget working downwards to the chevrons at the bottom.

 

[Raymo]

Another suggestion: Provide an option to remove the widget for those of us that only use the audio tones for AOA. I suppose it might be useful during IFR flight/approach but once on final, my eyes are outside.

 

[airguy]

Another suggestion: Provide an option to remove the widget for those of us that only use the audio tones for AOA. I suppose it might be useful during IFR flight/approach but once on final, my eyes are outside.

This is me. I don't think I've ever looked at the visual indicator once yet beyond setting it up originally. When I'm close enough to critical AOA for it to start talking to me, my eyes are outside and staying there and I'm relying on my ears to tell me how much margin I have.

For those that want a visual indicator, perhaps something that would trigger the AOA indicator to a much larger widget when it increases past 50% or some other threshold? I can see this being problematic on an IFR approach though, displacing other data...