LANCECASPER

Look at the N number - same airplane, much discussion and many more pictures about the wing and the paint earlier in this thread

Wow that's a big wingtip

Usually it's the potentiometer on the dimmer. It was on my Ovation. I replaced it and was good to go. Talk to Dan at LASAR. Sent from my iPhone using Tapatalk

Anything can cause an uptick or downtick in a market, but over the long term, it's always supply and demand that determines value, nothing else.

I don't think he was sworn in until '09.

Well . . if Mooney isn't making the parts you need any more . . . You might be able to sell them on the idea that you will have damage history which will decrease your value. If the LASAR upgrade is worded correctly in your airframe logbook it may not have to show damage history.

It's baaaaaaack . . . http://www.ebay.com/itm/93-MOONEY-TLS-BRAVO-1700-TT-/122570286326?hash=item1c89c224f6:g:0ioAAOSwo4pYf~Q9&vxp=mtr

Send me a picture of the one you have I may have an extra.

I would hold out for the LASAR wingtip fairings. https://lasar.com/mods/

Living in Texas it's the first thing I'v bought for every Mooney I've owned.

I used to have a KFC225 in an Ovation. I live near San Antonio and the only time it would porpoise is if I was flying directly over SeaWorld . . just kidding. What part of the U. S. do you live in? This may help in getting you a good recommendation on a shop that doesn't just throw parts at it. Central Texas Avionics in Georgetown TX helped with a trim switch issue on the KFC225 but seemed to know King Autopilots inside and out. I would be very confident taking my airplane back there for an autopilot issue. They were very fair also.

What is the Shaw part number shown on the fuel cap?

That's why trainers are used for training. Make the mistakes in a very forgiving airplane that someone else owns and maintains. If the insurance company would even consider covering someone doing initial training in a complex, retractable, turbo charged airplane the cost is going to be exorbitant. If you bring it in gear up or do a prop strike with low hours then the insurance goes from exorbitant or either astronomical or unobtainable. 25 hours into my training 32 years ago I bought a Cessna 172 to finish up my training in. I flew it 500 hours in 3-1/2 yrs. It had no autopilot so I learned to hold altitude and heading. I sold it for $5000 more than I paid for it. I had a Grumman Tiger that I flew 100 hours in for a year and broke even on. Then I bought a 172RG to build up retractable time, again no autopilot, not much faster than a 172. I flew it 100 hours in 15 months and got $15000 more than I paid for it on trade for a 10 year old Mooney 231. Still after 600 hours total time in Cessnas and a Grumman, I was way behind the 231 for the first few months I owned it. I kept that for three years, got my Instrument Rating in it, put a little over 400 hours on it, got all my money back out of it and bought a Bravo. Was I ready for a Bravo at that point? Not really, but Mooney provided Flight Safety Training at the time and I flew it a lot over the next few years and I became very comfortable with it. Looking back, I can't even imagine starting out in the Bravo. It happens all the time though where people who have some money buy an airplane they aren't ready for - people who sell airplanes say that those people have more dollars than sense. They aren't used to being told no. They think instruments and automation will make up for their lack of training and experience - actually it's just the opposite. Then way too often you end up reading about them in NTSB reports after they have killed themselves and their families after spinning it into the ground. (This is an extreme example, but still supports the idea of "just because you can, doesn't mean you should": http://www.newsmax.com/TheWire/lake-erie-crash-pilot-rookie/2017/01/20/id/769591/)

What insurance rates have you been quoted? That's the first step

Exactly . . lol They look 10 knots faster with static wicks! That was probably when Mooney was on their Personal Airliner ad campaign.

Ovations have them and they aren't Turbo.

I think Paul kept the encoding altimeter since that's what drives the KAS297B Altitude Pre-Select.

It's probably a friend of the Seller trying to help him drive up the price.

The M20M & M20R parts manual shows an alternate part number for the replaceable screw-in part to be a DD-1W made by TCO. Here's one on Ebay: http://www.ebay.com/itm/DD1W-Static-Wick-/132201852553 I wouldn't lose any sleep over buying the non-certified version (same part number $22.47) : http://www.skygeek.com/tco-dd1w-static-wick.html (I bought one of these in November 2014 from SkyGeek for an Ovation I had. If I remember correctly the DD-1W are more flexible. On the first Bravo I owned it seemed like there was always one broken (10-900-59/1))

And then 5 days later they retracted.

I agree completely! I make it a goal to try to get along with everyone. The one thing I have a hard time ignoring though are lies. If PTK slams Garmin or Avidyne or Mooney or anyone Mooneyspace member with things that absolutely are untrue I have a hard time with self control, wanting to correct an injustice. But I'm done. Anyone who reads all the way through the post will see it for what it is. He can continue to post whatever he likes on this and I won't directly respond. There's nothing that makes someone who likes to argue more frustrated than someone who won't argue back. On to much more positive things . . . Avidyne offers things on their IFD550 GPS/NAV/COM that aren't available anywhere else, so it will be well worth the effort for Thinwing to allow Garmin and Avidyne to get things sorted out. When the IFD550 was introduced they allowed current IFD540 owners an upgrade path at a reasonable cost with a new warranty and zero install costs. I just swapped mine out a few days ago and am looking forward to flying with it. The architecture on the Avidyne IFD means that many more good things are in the pipeline for down that road.

1. We know for sure that Garmin software GDU v6.21, GDC v3.09, GMU v2.01worked with Avidyne 10.1.3. It was Garmin's update of GDU 7.21 that is not compatible with Avidyne 10.1.3 or 10.2. Simply go back to GDU v6.21, GDC v3.09, GMU v2.01 and Avidyne 10.1.3 until it all gets sorted out. 2. My 2nd suggestion was sarcastic, why would anyone wait and not just go back to the software that worked? The Beechtalk reference was completely relevant ( https://www.beechtalk.com/forums/viewtopic.php?f=21&t=139908). You have to either say that (1) all of the equipment he put in (100% Garmin) doesn't work together, which I believe it does, if all of the software levels are compatible or (2) it was a bad install, which can happen. Which was it? You're saying that all Garmin stuff always works 100% of the time no matter what software levels they are at and that an installer should never be blamed. Sorry it has to be one or the other. We are waiting with baited breath wondering which you'll pick. Your suggestion of having Avidyne pay him reveals how biased you are. The Avidyne equipment is working just fine, the Red X's are on the Garmin G500, yet both Avidyne and Garmin are behaving like adults and continuing to work toward a solution, something that reasonable people and companies do.

Maybe look for another annunciator on ebay.

At least it's my mouth that I talk out of. I enjoy the way you ignore what's brought to your attention about the problems that have existed with the G500 that have nothing to do with Avidyne. Should this customer hold Garmin accountable or the shop that installed it? https://www.beechtalk.com/forums/viewtopic.php?f=21&t=139908 The customer that posted here on Mooneyspace about their Avidyne/G500 problems has three choices: 1) Insist that the shop take the units back to a software combination, which does in fact exist, that was tested and approved and works. The shop should have done this in the first place. or 2) Wait for 10.2.1 from Avidyne, but do not update G500 software past 7.12 while waiting for 10.1.2 or 3) Sit and complain I know which one you would choose, hopefully the customer picks the 1st choice which gets him back in the air right away. Any of the three is fine with me since my Avidyne IFD550 is working beautifully.

If you do your research you'll see that Garmin has been chasing this issue in G500, 600, 950 and 1000 installations for years - long before Avidyne introduced the IFD540. They had issues when Garmin 530's and 430's were installed with G500's and when GIA63's were installed with G1000's, when GIA63W's were installed, etc, etc. This is not new - this has been going on for nearly 9 years. The vast majority of G500 owners are satisfied and haven't had problems. The ones who have had problems have been very frustrated. The vast majority of Avidyne owners are extremely satisfied. Spend some time at the Avidyne booth at Sun N' Fun or Oshkosh and you'll see it for yourself. According to Peter, if the same remedy is applied to Garmin as Avidyne, then all shops should drop Garmin and refuse to install any of their equipment. All owners should rip out the offending equipment and march down the streets of Olathe KS in protest. But what do most reasonable people do? They work through the issue until it's resolved. This is one of the prices we pay for progress. There are those who complain and there are those who get things done. Is it frustrating? Of course. Feedback will get any good company's attention. You have Avidyne's attention - they are working on it. I would be equally bending Garmin's ear as well since losing AHRS has been a weak spot in their glass panels. Installation manuals are good the day they are printed but subject to change. What is the difference between people who are staified and people who aren't? Many times it does come down to the competency of the shop that did the work: https://www.beechtalk.com/forums/viewtopic.php?f=21&t=139908 Read through that thread and see if it was the manufacturer's fault or the fault of the shop that installed the equipment. What would it hurt to call Garmin and Avidyne Tech Support before major surgery on the panel to see how the current versions are playing with each other? This thread wouldn't exist if that had been done, but then there would be nothing to complain about.