696 Users and Data Fields

[BrianL99]

I'm curious how my fellow posters have their 696 configured?

How many rows of Data Fields and which ones do you have set?

I'm curious in general how other flyers configure their 696. There are so many options available, I think it's way more confusing than necessary. I suspect most flyers just accept the defaults?

Personally, I just re-arrangement my Data Fields again. I have (2) Rows and they show: GS, Dist Dest, ETE Next, WX Wind, TRK, BRG, NVAV Time, Fuel Timer.

Inquiring minds want to know.

[FastEddieB]

Well, I can only speak for me with my 496:



Distance Next, GS, ETE Next, ETE Dest, all displayed over the faux HSI.

Note my groundspeed!

Hint: I'm climbing, and NOT through 2,000'!

[CTLSi]

......

[SportPilot]

.......

[3Dreaming]

So you don't have a 696? A mess of steam gauges is the equivalent of an advanced GPS device? Confused...

You would be confused with all of those round instruments, because you learned to fly with glass.

BTW, the 496 has many of the same features of the 696 in a smaller package.

[Wm.Ince]

So you don't have a 696? A mess of steam gauges is the equivalent of an advanced GPS device? Confused...

Indeed you are.

[snaproll]

Well, I can only speak for me with my 496:



Distance Next, GS, ETE Next, ETE Dest, all displayed over the faux HSI.

Note my groundspeed!

Hint: I'm climbing, and NOT through 2,000'!

Great looking panel.. I know there are those who criticize everything, post ignorant comments, and speak more with their thick wallet than experience, but ignoring them works better than debating every comment. I also have a 496, wish I had more steam gauges (Mattel toy panel drives me nuts sometimes), and appreciate the time and energy it takes to design and construct a panel (been there - done that). When certain folks have a few aircraft design/build/test experiences under their belt, I might take their comments more seriously. For the majority of you, I really do appreciate the comments, insights, and assistance.

[SportPilot]

.......

[snaproll]

I think it's silly to argue the merits of glass vs steam gauges. They both serve the same function and I don't see that one has an advantage over the other if weight savings is not that important. When you're flying and looking at the gauge for information, what does it matter as long as it works? I wonder what the reliability statistics are?

I am in total agreement, and most pilots are looking outside the cockpit the majority of time and taking a very limited time to check instruments. Those who spend time starring at the panel are the contributors to the mid-air count. Don't know if there are reliability statistics but I see more malfunctions in glass panel readings based on my limited experience with glass. Good example is my flight yesterday from OXR to RIR, was climbing to 5500, got a fuel pressure alarm at 4000, panel said 0 fuel pressure, flow said 6.2 GPH, and continued climb to 5500. Five minutes later, pressure said 2.6 PSI - flew another hour with no changes.. Simple logic - running at WOT, normal flow, normal power, apparent malfunction. Will pull cowl this week and check connections. Glass versus steam gauges are based on pilot preference - both work and serve the same function.

[Wm.Ince]

Distance Next, GS, ETE Next, ETE Dest, all displayed over the faux HSI.

Very adequate panel with a nice layout. You could fly that airplane anywhere.

[FastEddieB]

I...appreciate the time and energy it takes to design and construct a panel (been there - done that). When certain folks have a few aircraft design/build/test experiences under their belt, I might take their comments more seriously.

Just to be clear, I did not build that panel - my Sky Arrow was an S-LSA delivered with pretty much that panel in place.

For anything involving altitude or airspeed, I'm 100% on the steam gauges. About the only thing I use the Dynon for is TAS and DA calculations.

Back on point, I like the faux HSI display immensely. If you set up a VNAV profile, a "glideslope" needle comes down from the top, aiding with descent planning. I have mine set to get me to 1,500' above field elevation at 500 fpm 3 miles out from the destination, setting me up to overfly already in level flight. Hardly necessary, but it is a joy to use.

[snaproll]

I...appreciate the time and energy it takes to design and construct a panel (been there - done that). When certain folks have a few aircraft design/build/test experiences under their belt, I might take their comments more seriously.

Just to be clear, I did not build that panel - my Sky Arrow was an S-LSA delivered with pretty much that panel in place.

For anything involving altitude or airspeed, I'm 100% on the steam gauges. About the only thing I use the Dynon for is TAS and DA calculations.

Back on point, I like the faux HSI display immensely. If you set up a VNAV profile, a "glideslope" needle comes down from the top, aiding with descent planning. I have mine set to get me to 1,500' above field elevation at 500 fpm 3 miles out from the destination, setting me up to overfly already in level flight. Hardly necessary, but it is a joy to use.

Eddie,
I was not suggesting you built the panel, just complimenting the design and layout - great placement of instrumentation. I think my point is those who criticize on this forum have no experience designing and building, but sure don't run out of negative comments. Thanks again... Don

[deltafox]

In cruise I use two data fields; 1) GS/Dist Nxt/ETE/VSR 2) Next/BRG/Trk/XTX. I routinely check (using ETE and Fuel Flow) how much gas I will have in each tank when I land. Then I do a sanity check for ETE using the GS and Dist Nxt.

In the pattern I use the panel with the bug set on the most common runway at home field. Makes it handy to check each pattern leg.

[BrianL99]

In the pattern I use the panel with the bug set on the most common runway at home field. Makes it handy to check each pattern leg.

A man after my own heart!

I was big on using "bugs" in my 6 Pack Cirrus. I used them for wind direction, runways & a few other odds & ends. I haven't yet figured out a simple solution with a glass panel, but I know it's there somewhere. I better get out my 696 Manual & figure out the simplest way to set a bug with it ... then again, there's nothing much "simple" with the 696 interface.