Alex, thanks for your input on the 900 vs. 930. I have some experience with UX/UI design, and I can see why they went to a smaller number… I’ve seen many times where an operator (not just pilots) fixates too much on the number when all they need to know in the moment is that the data is in range. The values I absolutely need to see are the larger ones and the smaller can be extracted post-flight, but a valid concern for some. I’m also hesitant about how the 930’s size would fit with the 3” spaces I already have. I would prefer to have it in my direct view on pilot-side and the panel doesn’t have room for that over there.
@carusoam, to answer some of your questions: I’m a lower hour pilot, but spread over a few decades and a few airframes. Most of them are of the C variety, but my flight training had me in Charleston, Albuquerque, Cheyenne, Camarillo, and Colorado Springs. I got my instrument rating in C Springs with half of that training in Camarillo.
I got into the Mooney because it fit my mission flying up and down CA mostly. I have no intentions of challenging thunderstorms. I grew up around them enough to not consider testing that boundary. I got my instrument ticket to better manage the CA marine layer, but I’m glad I got experience in Colorado summer and winter weather to learn what to avoid.
As for my non-flying experience, I’ve been serving in the military, both full and part time, for 19 years now and been a laser scientist, space and missile operator, quality engineer, systems engineer, instructor, electromagnetic warfare, and operation officer. Hopefully I can bring some help to others as well in MS as I get my feet under me here!