redbaron1982

I don't get the question... you're supposed to do whatever makes sense to you. If you feel better paying Lasar 2x, the go for it. If not, you can get the parts from Aircraft Spruce. Or, as mentioned above, get the alternative and pay 1/4 of Lasar price: https://www.aircraftspruce.com/catalog/appages/safairflush_05-01503.php

I don't know if it is normal, my J (and I guess most airplanes) have a white (or kind of white) belly so it is hard to see any deposit. I do know that a graying deposit in the tail pipe is normal. From your pics it looks like there is toooo much white. Did you try cleaning it up and see how long it takes to build up again?

I'm sure oil wouldn't leave a white powder behind. The only thing I can think of that is grayish is lead.

My J is a 1986 model, not sure when the new style cowls flaps become standard. My baffle seals, AFAIK, are in good shape. I have considered using Gee Bees seals.

When I try to lean to takeoff EGT while climbing on my J the CHT go above 400F, with cowl flaps trailing (halfway close). Do you keep you cowl flaps full open? Today at cruise (8500ft) and 22x2500, I was running at 380F with closed cowl flaps and 15F LOP. OAT was 15C. I'm still not sure if I have a cooling issue or not.

I'm too chicken to run the tank dry, not going to happen at least for several years lol

Today I ran my left tank until the low fuel light came on. I immediately switched to my right tank. When landed I filled up the left and it took 30.1g. So I guess in my J model the warning comes when 2 gals of usable fuel remains.

I was wondering that myself a few days ago. Then I thought it's better to keep the evidence around of this guy's being a douchebag. But I'm open to delete it. I guess we can vote. If you guys prefer me to delete the thread, just like this post.

I have my IPad pro with Velcro on top of my steam gauges. Now with GP pilot I have synthetic vision and can fly down to minimum (and a little more) without anything else. My SOP is after being cleared for the approach I stick my iPad on the panel and fly it all the way to land using the syn vision. I don't even need a radar altimeter because I get AGL altitude using the GPS.

Nowhere. You're perfect and we are glad to have you here helping all of us. Our own DanG here in Mooneyspace.

You check all the boxes of a person that has all the hazardous attitudes and lack of ADM / CRM understanding.

So, basically what you're saying is to print all STAR/IAP for all possible airports ahead of time? What about SIDs?

Sure your analysis is correct, and I'm sure back in 2010 you would have done the same analysis about Blackberry being unbeatable, or same for Internet Explorer, and so many other "kings" that fell into disgrace rather quickly.

After some comments in this thread, I decided to move my logbook to a dedicated app. Now I'm giving a try to GP, I'm still trying to get used to the UI, although it looks much better than FF, it will take a few flights to get used to it.

A 2+ year update on this, the KFC150 was finally repaired by @Jake@BevanAviation and it still working perfect. The avionics blower fix, replacing the burnt transistor, also is still working just fine.

In my J, the KFC150 has always tended to run on the hotter side. Because of that, I had some issues with the KFC computer. While I was getting it fixed, I checked the electronic cooling fan and discovered it wasn't working, so I had that repaired as well. Now, when I turn on the master switch, I can clearly hear the electronic fan running. In your case, while on the ground with the engine not running, I'd try pulling the electronic fan breaker and listening to see if you hear it spin down. If you don't hear anything when you pull the breaker, that would suggest the fan may not be working.

I guess off topic of the main thread, but talking about logs. Is there any value in having the physical logbook scanned? Are there any requirement for a logbook to be considered legal? Mainly the entries for flight reviews or similar.

There are multiple misconceptions and wrong assumptions in your post: 1) I really wanted GP to work for me. I mentioned some of the reason why I wanted to migrate to GP. 2) Foreflight doesn't allow you to select which columns to export. 3) GP doesn't allow you to select which columns to import 4) CSV are tricky, but I'd expect GP devs are up to the task. One of the issues were extra spaces, as you mentioned. A simple "trim" of the input, which is common sanitization process when handling user input. As an exmaple, MyFlightBook imported FF CSV without any issue. Same user (me), same computer, same file, it failed with GP, but it worked with MyFlightBook.

My problem was having a really bad first experience with GP. The first thing I tried to do was to import all the data I have in ForeFlight. I followed Garmin's procedure and it failed with "Something went wrong" type of error. I reach out to support, and they were not able to help me. I had to debug GP using Chrome's dev tools to get the import to work. Even after that, the logbook entries were all messed up.

I did not, I followed Garmin's official procedure, basically: export from FF, import back in GP. Both the web and the support tech I talked to, indicated that that was the process to follow.

Yeah, I was using the web version, just trying to copy over all the info I have in ForeFlight over to GP. The experience was so bad, with the app itself and with support that I decided that it was enough. Now I realized that after the cancellation they gave me a 30 days free demo (I used the original 30 days demo a couple of years ago). So maybe I'm going to give it another try inflight. Thanks for the advise on MyFlightBook, in 2 minutes I was able to import all my logbook entries from FF and everything matches, my currency is showing up correctly, etc.

After ForeFlight got acquired by a private equity, and known how private equity companies works, I decided to cancel my subscription and move over to Garmin Pilot. Today I finally went for it, and it ended with cancelling my subscription 30 minutes after I started it. The first thing that I tried was to import from ForeFlight my logbook. I got an "Error importing logbook" message, no indication of what was going on, anything. I reached out to support, and they didn't know what was going on either, and asked me to start manually splitting my logbook into smaller chunks. Before doing that I checked if there was any useful message in Chrome's dev console, and there was: "Fligth table cannot be found" or something. So I fixed the CSV export from ForeFlight (it had some extra white spaces that confused Garmin) and I got to the next step. Now I got a lot of "unrecognized" columns. Some that were important for currency, like "Landings" or "Takeoffs". I asked to the support guy if I had to update all this manually, and he said yes. I was still trying to make this work, so I went and finish the import and looked at the result: first, the UI is ugly, it looks like a web page from the 2000s. And then, all currencies were messed up. My IFR currency was showing 0 instrument approaches, when I actually had 6 in the last 6 months. I mean, the approaches were showing up in the logbook entries, but it was not counting towards my currency. At that point I said this is enough and ask the support guy to cancel my subscription. The thing that pissed me off the most is that the support guy was like "yeah, this is how it works" and when I asked to cancel the subscription he said "ok" and just cancelled it. Literally no intention to make the product work for me. I really wanted to migrate, I do see some advantages (its a bit cheaper than Forefligt, I can use my Android tablet as a backup, etc)... but I was shocked by the bad quality of, at least, the logbook part of the app.

Mine has a strikefinder, but I never thought the static wicks were just for that. I thought flying IMC could build up static and affects COMs/NAVs radios.

This is one is another one that seems way overprices. I'm missing 4 or 5... that $250... crazy

These are the covers I make, they are for ETA switches (like the ones I have on my '85 J Model)