Bob5151F

I'm looking for a MSC in the mid-Atlantic area. Any recommendations?

Yesterday while flying my O3, the SynVis on the PFD went off-line (it had been working) and I got an aural message "Terrain not available". Every minute or 2 I would get a "terrain available" alert but nothing happened on the PFD and then it said "terrain not available" again. This happened numerous times. After about 20 minutes everything returned to normal. There were no issues with GPS coverage, Upon landing I restarted the system and got all sorts of error messages that the PFD wasn't reading data (not only terrain) off the Supp data card. I removed the card and did the Obstacle, SafeTaxi, and Airport directory updates that were due today. I subsequently rebooted the system 5 times. On 3 of the 5 the system came up fine, on the other 2 I got multiple database error messages. Anyone have any thoughts? Data Card got corrupted? PFD Card reader not making contact with disk intermittently? PFD Card reader fault?

I'm in Seattle. Growing up on the east coast (the other side of the Delaware river from you), I'm very fond of DnD but they are not out here. Top Pot is the local equivalent. Bringing goodies always helps with response time from the techs There's a French bakery on the way to the airport so I got an assortment of croissants (plain, chocolate, ham & cheese). They were gone by the time I returned the GPU. So this fix cost me 2 SD cards and 2 sets of pastries. About $80 all in.

It worked. After I failed on the first try using 1612revE last week, I got a new SD card and used the file in revF. I followed the steps exactly and pulled the GPS2/NAV2 and COM2 CBs to kill GIA#2. Total power on time was about 7-8 minutes. As it happened, I borrowed a GPU from my local Garmin service shop (they appreciated the pastries ) and learned the following: They told me the recent magvar data file that was embedded with the last NavData update was flawed causing the problem. Compounding the issue is that the revE file was corrupted and that has caused a lot of heartburn.

Thanks Jeff I'm assuming the 2 GB SD card I tried the other day was bad and I have a new one coming from Amazon, so I will give the update another try on Monday. You have been way more helpful the Garmin support. Good news on the update time. It was a hassle trying to borrow a GPU. Thanks! Bob

Jeff Great news! Just to be clear- you did not pull the AHRS or MFD CBs? Just GPS2/NAV2 and COM2? Also, did you use FAT32 formatting on the SD card? Bob

I have an Ovation3 and I tried the SD card option. I was able to load it onto a 2GB SD card no problem (I have Windows), but when I put the card into the top slot of the PFD and power up the system proceeds as if the SD card isn't there. Any ideas?

I would agree we don't want "our friends" being too helpful. Having flown a lot of IFR, I always like to have choices because mother nature is a real practical joker.

I would also add that I do not blame the people named above. They are good technical folks and do not necessarily make resource allocation decisions within Mooney. We need to get the attention of their management!

They includes: Stacey Ellis, Paul Kehner, Frank Crawford, Betsy Strosser

If any of you would like to be part of an action group to push Mooney, please contact me at: robert.e.fishman@gmail.com Some of you already have and I'm compiling a list. Thanks

Bob They is the people at Mooney. I have had numerous emails with them (mostly the same people) before and after the new ownership structure. No one at Mooney is try to dodge their obligation to solve this. They just won't get it done.

It is a safety issue because WAAS allows precision approaches with lower minimums. Having flown a lot of IFR and living in the Pacific NW, there are a lot of airports where having lower minimums would allow more options especially in case of a problem.

Bob, with respect, they have been saying for years they are working on it and their website says "we haven't forgotten about you". The are admitting responsibility by that statement. The current owners own the type certificate. Only they can authorize a fix. I think that using a legal dodge to evade responsibility is one of the things that is wrong with our society. At the very least, they have a moral obligation to us and it's not like we are asking to get something for free. We all know this will cost us and are prepared to pay. I love my Mooney (this is my second one) and have nearly 3000 hours in them. But this is a safety issue and they need to step up.

I have talked to Garmin. It's a Mooney issue because of the type certificate. The write up on the website has said that since 2015. It says second quarter not 2Q 2016. The question is second quarter of what year -2030?

Here is the ad I would run: ATTENTION OWNERS OF 2005-2007 MOONEY OVATIONS & BRAVOS WITH STEC AUTOPILOTS As all of you know, despite promises by Mooney that our aircraft were upgradable to incorporate WAAS when we purchased our aircraft, Mooney has left us stranded. For nearly 10 years now, we have tried to get Mooney to deliver on the promise, to no avail. It is clear from their ever changing responses, that there is a lack of commitment to solving this safety of flight issue for over 100 aircraft. Despite having owned two Mooney’s over the past 26 years, this lack of attention makes me reluctant to purchase a Mooney again. If you would be interested in forming a group to explore ways to push Mooney to do the right thing by us, please contact me at: robert.e.fishman@gmail.com

I was told when I bought my STEC equipped 2006 Ovation (new from the factory), that it was WAAS upgradable. that was 10 years ago. I agree the legal road has a lot of potholes. I'm thinking of taking out some ads (MAPA Log, Flying, AOPA Pilot)to advertise our plight. They might just do something to shut us up and avoid the negative publicity that would impact future sales. Anyone have an opinion about that?

Thanks for the reply. I agree that going legal is premature. I'm just frustrated that I can't get a commitment from them. It's been a couple p]of years now. Count me in on any efforts to push them into action. I've also run into an issue on ADS-B. I have been looking into the Garmin 345R with it's own WAAS to solve the compliance issue assuming Mooney leaves us stranded on WAAS. Seems they need to release an updated software (I'm on -30) for that to display the ADS-B WX on the MFD. What do you think of an ad in MAPA log asking all stranded STEC users to identify themselves to get a group going?

Does anyone know how many of us are stranded non-WAAS G1000s with STEC autopilots? The timing is important as we face ILS cand VOR closures and it impacts the ADS-B solution for us as well. My guess is about 100 Ovations and Bravos. I've been checking with Mooney every 3 months or so and everytime the story changes. I really think they don't care about us. Should we up the ante? Do a class action suit to compel them to act? Take out an advertisement in MAPA log (if they would run it) or Flying and embarrass them into doing something?

I agree. Clay Lacy is excellent

Rich I used to live in the Bay Area (DVO then RHV) and now am based at BFI. My son also went to UW. I recommend BFI for convenience and it has better FBOs than RNT. PAE is a 45-60 min drive depending on traffic. The only downside to BFI is fuel is expensive. Also try to arrive/depart BFI between 9 AM and 4 PM. Early in the AM and in the evening there is a lot of big air cargo traffic at BFI you don't want to mix it up with. Be sure to check out the Museum of Flight which is on the west side of the field. Bob

I have had fluctuations on the high and low side. I even got 32.5" on the takeoff roll, followed by off on high scale (>35). Not bad for a normally aspirated engine. The problem is intermittent and seems to settle down after 10-15 minutes of flying.