thito01
Pre-takeoff checklist
Long, long, story. Many things should have been done differently:
In January of 2017, I was going though some financial issues due to having to move for a new job and having two house payments. I took on good friend (we worked for same company) as a minor partner for my aircraft. Let's call him Joe for now. Joe had his private and was working on his IFR. He was previously in a 3-person partnership until one of them forgot to put the gear down. He was located in Chattanooga and I was in central Florida so we moved the aircraft his old hanger in Chattanooga at a very small airport.
In transit to Chattanooga, the aircraft developed a gear issue so it was taken to the shop that had maintained his previous aircraft because of that previous relationship. For some reason, it took 3 months to get the aircraft hydro-pack rebuilt (PA32R-300). During this time, the aircraft was left on the ramp and not hangered.
The next time I flew the aircraft was when I was at the company headquarters in Chattanooga in Nov of 2017, but I only was in it for about 30 minutes doing some take-off and landings. When I first started the aircraft I noticed that the terrain card was missing. Joe said "It's always been that way, so I thought it was normal."
Unfortunately, my partner never did get his IFR and seldom flew the aircraft due to work and home schedules.
Move forward to Feburary of 2019.
I was getting ready to move the aircraft back to Florida and he went out to the aircraft and found that the Xerion engine monitor would not light up. An email to the manufacturer resulted in finding out that they had discontinued support.
Many delays happened at this point. A new engine monitor was purchased at Sun-n-Fun of 2019 but was not delivered till Jan 2020. While I should have been pressing the dealer, the real problem was that the small airport where the aircraft was located did not have an A&P so the plane either had to be moved or an A&P had to work most of an hour from his base. The original plan was to ferry it over. Let's just say that the FSDO first said one thing, then required something else, then changed it's mind again to the point that they wanted all the original engine guages re-installed just to ferry it 24 air-miles. This took over a year! Finally, in Mar 2020 the A&P got so fed up with the FSDO that he agreed to eat the trip-charges if I would let him work on it at his convenience. I agreed. Then Covid hit.
Some side issues, which will be important later. 1) The Sandel SNS-3308 EHSI was de-laminating. The A&P found a used one, at a decent price, and with the updated software for the GNS-430W interface so it was replaced. 2) I also had to have the GTX330 updated for to GTX330-ES. I had actually sent the GTX330 in to Garmin in 2019 and got the update performed. And, 3) I decided to add a GLD52R for ADS-B Out.
The aircraft was finally ready to fly in Dec 2020 and I planed to get it in Jan. Jan 2, 2021, I had a complete unary track lock-up that put me in the hospital for a couple of days with sepsis. Then a TRUP (roto-rooter job) in March. (No cancer, and I never had a high BPH. Due to almost 3 months on a catheter, my recovery took a while and so I had self-grounded until July.
The first weekend of Aug, I was just one hour from the aircraft for my first grandson's first birthday so it was arranged that the A&P would fly over, pick me up, and I would take him home before bringing the aircraft back to Florida. I got a bi-annual and a Basic-Med and waited for the aircraft.
After he picked me up, as we climbed out, the landing gear would not come up, so we landed and he took the aircraft back to his shop. It was a valve problem that took a lot longer than it should have because the first replacement valve was also bad so they kept looking for some other problem before replacing the new valve.
One thing I noticed during this short flight was that the screen on the 430w was starting to de-laminate. Because I had had declamation problems with the Sandel, I figured it was just age on the 430. The shop talked to Garmin and they will still replace the screens.
I did finally get the aircraft back this last weekend.
But, some other things were 'popping up':
1) The shop was having issues getting the GNS430W to actually interface with the SNS3308. I actually sent them photos of the old configuration screens from just after the GNS430W and GTX330 was installed 2008 so they could try to make them match. The final conclusion was that the GNS430W needed a newer level of software to support the newer level of software on the SNS3308. (I no longer think that is the issue.)
2) The GNS430W was reporting 'missing devices' on the buses. The shop just assumed that I had had something removed in the past so did not mention it to me. It was not until I was flying the A&P back to his base this weekend that I saw the messages and I asked about it. He said he thought it was normal because my partner said he thought it was normal.
3) I discovered that the database card in the GNS430W was missing a mark I put on mine. I had an 'A' card and a 'B' card that I swapped back and forth. Each was labeled with a small 'A' or 'B'. While my partner had been updating the card data, he had not been paying attention to the marks I had made.
So, today it dawned on me to check the serial numbers of the GNS430W. I have owned the aircraft since 2005 and was the owner that had the WAAS update performed. The logbook entries, in two places, indicate a serial number of starting with '97' while the unit that is now in the aircraft starts with '96'.
So, now it appears that back in 2017, most likely when the aircraft was in the shop for 3 months, my GNS430W was taken and another GNS430W was put in it's place. My partner did not have but a few hours in the aircraft so did not think anything about it. During my short flight in late 2017, I was worried about the missing terrain card and did not notice or look for any other messages. The current shop was not concerned with the 'missing bus connections' because my partner told them he was used to seeing them. We just were not saying the right things to raise the correct red-flag.
Another small item. When I re-started a database subscription with Garmin (not Jeppesen as in the past) this Aug, I needed a serial number so I asked the A&P for it. He sent me a picture of the back end. So, I registered my subscription with the 'wrong' unit and not the 'right' unit serial number.
Now what is my next step? Should I contact Garmin and report the original serial number as stolen? What could they even do even if they had someone currently subscribed with that serial number? Is this a claim I need to report to my insurance agent considering that I believe that it happened 4 years ago? Reporting to LEOs also seems out of the question due to the time-frame.
Garmin has quoted a $1500 cost for fixing the screen and updating the software, but now I don't know if they will find something else wrong with it when they bench-test it, and what that would cost me (FYI, software is V5.30.)
In January of 2017, I was going though some financial issues due to having to move for a new job and having two house payments. I took on good friend (we worked for same company) as a minor partner for my aircraft. Let's call him Joe for now. Joe had his private and was working on his IFR. He was previously in a 3-person partnership until one of them forgot to put the gear down. He was located in Chattanooga and I was in central Florida so we moved the aircraft his old hanger in Chattanooga at a very small airport.
In transit to Chattanooga, the aircraft developed a gear issue so it was taken to the shop that had maintained his previous aircraft because of that previous relationship. For some reason, it took 3 months to get the aircraft hydro-pack rebuilt (PA32R-300). During this time, the aircraft was left on the ramp and not hangered.
The next time I flew the aircraft was when I was at the company headquarters in Chattanooga in Nov of 2017, but I only was in it for about 30 minutes doing some take-off and landings. When I first started the aircraft I noticed that the terrain card was missing. Joe said "It's always been that way, so I thought it was normal."
Unfortunately, my partner never did get his IFR and seldom flew the aircraft due to work and home schedules.
Move forward to Feburary of 2019.
I was getting ready to move the aircraft back to Florida and he went out to the aircraft and found that the Xerion engine monitor would not light up. An email to the manufacturer resulted in finding out that they had discontinued support.
Many delays happened at this point. A new engine monitor was purchased at Sun-n-Fun of 2019 but was not delivered till Jan 2020. While I should have been pressing the dealer, the real problem was that the small airport where the aircraft was located did not have an A&P so the plane either had to be moved or an A&P had to work most of an hour from his base. The original plan was to ferry it over. Let's just say that the FSDO first said one thing, then required something else, then changed it's mind again to the point that they wanted all the original engine guages re-installed just to ferry it 24 air-miles. This took over a year! Finally, in Mar 2020 the A&P got so fed up with the FSDO that he agreed to eat the trip-charges if I would let him work on it at his convenience. I agreed. Then Covid hit.
Some side issues, which will be important later. 1) The Sandel SNS-3308 EHSI was de-laminating. The A&P found a used one, at a decent price, and with the updated software for the GNS-430W interface so it was replaced. 2) I also had to have the GTX330 updated for to GTX330-ES. I had actually sent the GTX330 in to Garmin in 2019 and got the update performed. And, 3) I decided to add a GLD52R for ADS-B Out.
The aircraft was finally ready to fly in Dec 2020 and I planed to get it in Jan. Jan 2, 2021, I had a complete unary track lock-up that put me in the hospital for a couple of days with sepsis. Then a TRUP (roto-rooter job) in March. (No cancer, and I never had a high BPH. Due to almost 3 months on a catheter, my recovery took a while and so I had self-grounded until July.
The first weekend of Aug, I was just one hour from the aircraft for my first grandson's first birthday so it was arranged that the A&P would fly over, pick me up, and I would take him home before bringing the aircraft back to Florida. I got a bi-annual and a Basic-Med and waited for the aircraft.
After he picked me up, as we climbed out, the landing gear would not come up, so we landed and he took the aircraft back to his shop. It was a valve problem that took a lot longer than it should have because the first replacement valve was also bad so they kept looking for some other problem before replacing the new valve.
One thing I noticed during this short flight was that the screen on the 430w was starting to de-laminate. Because I had had declamation problems with the Sandel, I figured it was just age on the 430. The shop talked to Garmin and they will still replace the screens.
I did finally get the aircraft back this last weekend.
But, some other things were 'popping up':
1) The shop was having issues getting the GNS430W to actually interface with the SNS3308. I actually sent them photos of the old configuration screens from just after the GNS430W and GTX330 was installed 2008 so they could try to make them match. The final conclusion was that the GNS430W needed a newer level of software to support the newer level of software on the SNS3308. (I no longer think that is the issue.)
2) The GNS430W was reporting 'missing devices' on the buses. The shop just assumed that I had had something removed in the past so did not mention it to me. It was not until I was flying the A&P back to his base this weekend that I saw the messages and I asked about it. He said he thought it was normal because my partner said he thought it was normal.
3) I discovered that the database card in the GNS430W was missing a mark I put on mine. I had an 'A' card and a 'B' card that I swapped back and forth. Each was labeled with a small 'A' or 'B'. While my partner had been updating the card data, he had not been paying attention to the marks I had made.
So, today it dawned on me to check the serial numbers of the GNS430W. I have owned the aircraft since 2005 and was the owner that had the WAAS update performed. The logbook entries, in two places, indicate a serial number of starting with '97' while the unit that is now in the aircraft starts with '96'.
So, now it appears that back in 2017, most likely when the aircraft was in the shop for 3 months, my GNS430W was taken and another GNS430W was put in it's place. My partner did not have but a few hours in the aircraft so did not think anything about it. During my short flight in late 2017, I was worried about the missing terrain card and did not notice or look for any other messages. The current shop was not concerned with the 'missing bus connections' because my partner told them he was used to seeing them. We just were not saying the right things to raise the correct red-flag.
Another small item. When I re-started a database subscription with Garmin (not Jeppesen as in the past) this Aug, I needed a serial number so I asked the A&P for it. He sent me a picture of the back end. So, I registered my subscription with the 'wrong' unit and not the 'right' unit serial number.
Now what is my next step? Should I contact Garmin and report the original serial number as stolen? What could they even do even if they had someone currently subscribed with that serial number? Is this a claim I need to report to my insurance agent considering that I believe that it happened 4 years ago? Reporting to LEOs also seems out of the question due to the time-frame.
Garmin has quoted a $1500 cost for fixing the screen and updating the software, but now I don't know if they will find something else wrong with it when they bench-test it, and what that would cost me (FYI, software is V5.30.)