LANCECASPER

The Power of Mooneyspace! A 3D printed Switch Guard from @Flyler's designed is now guarding my autopilot switch. It was too easy to brush against it after hitting a button on the MFD and this should solve that. I really appreciate the suggestions by everyone and the work that @Flyler put into the design. The "new" one laying on top of the factory one is extremely close and most importantly the screw holes line up perfectly. I also have to say that @Flyler's tractor is also worthy of commendation. It is by far the nicest tractor I have seen in weeks.

I installed one of those in a previous airplane. It's not enough power for the Starlink. Plus the G1000 airplanes don't have a separate clock.

I put it in the upper right corner of the panel above the circuit breakers. When you take the glareshield off there is only one possible spot it will fit in that area due to the structure behind the panel. This way I can use the shortest usb-c cable for the Starlink: https://www.amazon.com/dp/B0DFH5DSPL?ref=fed_asin_title&th=1 This Mid-Continent USB calls for a 7.5amp breaker

This is the one I put in two weeks ago: https://www.aircraftspruce.com/catalog/pnpages/10-07493.php

At least twice that we know of. Once when the previous owner (since 2024) flew it the week before the new owner came to pick it up, on or around October 4. And another time the day (October 9) the new owner picked it up in early October. I hope that the NTSB interviews the previous owner and asks him how many times this has happened since he bought it in 2024. My gut feeling is that he had been fighting with this and maybe a few other things and just lost patience and wanted to hand off his problem to someone else. One other thing I keep thinking about is that he had a CFI there with him on October 9 when they made it back to the airport safely. The CFI that was with him on October 31 that survived the crash had just met him the night before. I wonder if the first CFI tried talking him out of going ahead with the airplane or didn't want any part in getting it back to FL. I hope they interview him also.

No additional location was ever recommended after the Bravo conversion. I would get that other probe out of there, do whatever you have to do to make sure there is no exhaust leak in that area and disconnect whatever indicator it's attached to. (Unless that's where they put your #4 EGT probe.) Make sure the correct factory location probe is displaying on your JPI930 since that is your official instrument now that the original instruments are removed. Pull the other supplementary JPI TIT indicator or clearly mark it INOP. Looking at an incorrect lower TIT indication is a good way to cook a set of cylinders on this engine and at the same time burn up the turbo and the exhaust system and maybe even the occupants. There were a few incidents of the exhaust system getting so hot that it took out the "Y" in the tailpipe and blew 1650 or higher exhaust like a blow torch through the fire wall. That didn't end well. This is a great airplane but running it with the POH numbers will burn up the engine. I keep preaching to the choir on this but . . .

Good to know. I wasn't aware that their autopilot interface worked with the Bendix King KAP150. Their website says just S-Tec autopilots. https://uavionix.com/general-aviation/av-30/add-ons/av-apa/?srsltid=AfmBOooBuAXkcCKSef2VvkR4xFZOaJFv0GPMaTra4DDkhEoaPS1cl2o5 I can see where it might be able to provide heading with the jumpers, but I don't see where it would provide attitude.

I'm familiar with that part number since I provided it to someone that needed it back in 2019: What I am saying is that there's no one at Mooney that assembles voltage regulators. Even back then they put their part number on a regulator that a company assembled, most likely Zeftronics. Why not go to the source?

I can see why you feel that way since any of the recent GDL products are only receivers and none of them have the capability of transmitting anything out whatsoever, so yes, they are very private, you might even say mute. The Garmin GDL39, GDL39-3D, GDL 50 all receive ADS-B in and don't transmit anything out. The Garmin GDL52 receives both ADS-B and XM and doesn't transmit anything out. The Garmin GDL 51, GDL 69 and GDL 69A are all XM receivers only and don't transmit anything out. The Garmin GDL60 is a cellular datalink which allows you to update databases and download engine monitor data. There was one GDL, now ancient by avionics' standards, the GDL90, that was an early transceiver that didn't offer any privacy, but has been discontinued for years.

If it hasn't been modified, your lighter socket should still be 28v, which is a good thing. If it is on a 10 amp circuit breaker, even better. You should be fine. In my opinion Mooney made a mistake stepping it down from 28 to 14. Back in the day people might have been burning up a Walkman or something they plugged in a 28v socket, but nowadays pretty much anything you would plug into it, especially aviation-related, accepts anything from 10-32 volts. Mine has that stepdown "feature" and then the two 14v sockets (front and back seats) are on one lowly 5 amp circuit. Oh and by the way the circuit breaker is back in the avionics bay on the backside of the rear bulkhead behind the luggage compartment. That's the reason I recently had a Mid-Continent 100w USB-C receptacle installed. (I still might see about removing the stepdown "feature" on those sockets.)

Mooney doesn't make voltage regulators. You could try reaching out to Zeftronics: https://zeftronics.com/

I just checked the Home Depot site and they are also down to $229 with free shipping. I recently had a 100w USB-C jack installed in the Mooney. For $229 it's probably time to go ahead and try it out and see if I can live with the antenna on the right side of the glareshield.

Your King Autopilot is Attitude based so w/o your vacuum pump, no Attitude. Once you get vacuum see how it does and go from there.

I don't think those will work with his Bendix King KAP 150 Autopilot.

@SilentT just make sure the used TailBeacon on Ebay has a return policy if it doesn't work. This was a recent thread over the weekend: