Thanks for the info [emoji1360]

Got the data from the inspector today. I then sent everything over to uAvionix. Luckily, they have been very responsive. After reviewing the data I sent them, they don’t believe it to be a grounding problem, but a signal attenuation problem. He had some more questions to which I supplied answers. Now waiting for the next move from them. Still troubleshooting.

Mike, does this sound familiar...about the signal attenuation issue? He asked if I ran a Spot or similar device (I run an inreach...but not on every flight). He also asked about the nav/coms I use (KX-155s) and when the transponder was last checked (last May). I know some frequencies can interfere and they have them listed in their troubleshooting materials.


Sent from my iPad using Tapatalk

Grassstrippilot wrote:Got the data from the inspector today. I then sent everything over to uAvionix. Luckily, they have been very responsive. After reviewing the data I sent them, they don’t believe it to be a grounding problem, but a signal attenuation problem. He had some more questions to which I supplied answers. Now waiting for the next move from them. Still troubleshooting.

Mike, does this sound familiar...about the signal attenuation issue? He asked if I ran a Spot or similar device (I run an inreach...but not on every flight). He also asked about the nav/coms I use (KX-155s) and when the transponder was last checked (last May). I know some frequencies can interfere and they have them listed in their troubleshooting materials.


Sent from my iPad using Tapatalk

No they didn’t discuss any of that. That said, most of the parameters on a PAPR report are gobbledygook to me anyway. But no, with mine, they said check ground and then sent a new one. Maybe they’ve found out a few things since then.

BUT, bottom line is they don’t list all kinds of equipment you can’t operate with a SkyBeacon installed. I have a InReach as well, but nav coms? Sounds like he’s reaching to me. A replacement unit is cheap compared to a tech’s time after a while, not to mention customer good will.

I’d tell them to replace it.

FYI, my NIC errors on my first one were huge = as in 25% plus every flight. So not even really intermittent.

What does the FAA guy say?

MTV

The inspector said he knew that some of the early units had issues, like you have said. UAvionix now has a GPS troubleshooting guide that wasn’t there before. Apparently they have identified certain frequencies that interfere with the GPS reception. I think the KX-155 has two frequencies associated with it...one at each end of the frequency band. I guess they are somewhat easily identifiable if that is the case because you’ll see the failure occur when radio calls are usually made...like in the pattern...when looking at the KMZ data. I’m the same as you. All the data on the PAPR is Greek. I did find a user guide that kind of decrypted it a little. Still...

Good point about no disclaimer about running any other equipment. I’ll see what they come back with today.


Sent from my iPad using Tapatalk

Grassstrippilot wrote:....I’ve been digging through my data on the Skybeacon. Seems it’s had an issue for a while. ......

I installed my Tailbeacon last October.
The test flight went fine, & I got my $500 FAA rebate..
But I decided it wouldn't be a bad idea to get a PAPR report periodically, just in case--
if something went haywire, I didn't want an FAA nasty-gram to be my first clue.
So I get one maybe once a month, it always checks good.

A while back, I decided to buy a spare transponder in case my old Narco AT150 went gunnysack.
Swapped them out a while back, did a PAPR flight,
and discovered that I had to turn up the gain (or whatever) on the Tailbeacon.
Second PAPR flight was fine.

Luckily the inspector has been very cordial. Still I’d rather not be on their radar. I saw that changing the gain, so to speak, was one of the troubleshooting tips. I did do that but am waiting more instructions from them. I’ll update as I go.

I forgot to take a pic of Adam and Sprocket for you on out camping trip last month. [emoji1]


Sent from my iPhone using Tapatalk

The threshold setting on mine went to default after the firmware update.

Prior to the update, the default setting wouldn't pass. After the update the default threshold setting worked fine.

Some kind of black magic going on between the SkyBeacon and the way it sniffes out the transponder. I knew it wasn't an ideal setup when I bought it, but it was the cheapest and easiest path forward which retained my AT-50 (which I have a spare of too!).

Grassstrippilot wrote:....I forgot to take a pic of Adam and Sprocket for you on out camping trip last month. [emoji1] ....

Good old Sprocket!
Haven't seen him in any of your pics for a long time,
I figured the poor little guy had been outgrown & left behind.

With the bit of turbulence ya'll have been having with the sky/tailbeacon system updates, would you still go with the uAvionix transmitter over something comparable, like a Garmin GDL 82?

Side note, new here and super appreciative of the education in these forums.

King17 wrote:With the bit of turbulence ya'll have been having with the sky/tailbeacon system updates, would you still go with the uAvionix transmitter over something comparable, like a Garmin GDL 82?

Side note, new here and super appreciative of the education in these forums.

I’m guessing that there are more that don’t have problems than those that do. Up until I found out about my issue, I’ve been happy with it. And I’m guessing that once it’s resolved, and as Mike said...no more issues...I’ll still be very happy with it. So far they seem to be very responsive in getting it resolved. I’m on the road right now and won’t get to do the testing they’ve requested until Wednesday.


Sent from my iPhone using Tapatalk

I would order from uAvionix again, although I’d buy a tail beacon as opposed to a SkyBeacon. The so called “strobe” on the SkyBeacon is just a flashing LED.

My understanding is that most if not all the problems people have had with these things were with early iterations. In any case, they fixed my problem with minimum fuss. The thing works, meets the requirements, is relatively inexpensive, and VERY easy to install.

Even the Garmin unit requires quite a bit more installation effort. Have to crawl around in the belly, make up some connectors, and run antenna wire and install an external GPS antenna. Could do it yourself with the right tools, but still....

MTV

Thanks fellas. That gives me a lot more warm fuzzies making the decision.

King17 wrote:With the bit of turbulence ya'll have been having with the sky/tailbeacon system updates, would you still go with the uAvionix transmitter over something comparable, like a Garmin GDL 82?

Side note, new here and super appreciative of the education in these forums.

I've had no issues with my tailbeacon (knock on wood) and I fly out of a relatively busy Class C.

I am completely satisfied with my tailbeacon. My goal was to have something I buy, install myself, and it simply work to fulfill the requirement. It has done this. Zero money spent on install, 5 mins setup in the app, maybe less. The skybeacon is a bit cheaper but it's ugly as sin and since I have strobes it would be a downgrade in terms of visibility. I called uAvionix a couple times before buying and their technical support was very helpful.

I’ve got a different UAvionix ADS-B product but my experience is similar to Asa’s.

Good tech support, and I’ve had no issues with dropouts on the PAPRs.

Would not change a thing. Very happy with uAvionix SkyBeacon and SkySensor.

Like Asa, I'm very happy I went with uAvionix for my ADS-B installation. In my case, since I'm experimental (and had a decent transponder) I chose to go with the echoUAT with their SkyFX external GPS module, for a bundled price of just under $1400. Quick and easy DIY install (no wired connections for me, since I don't have an EFIS). The setup process takes about 5-minutes using their dedicated free smart-phone software. Last step was making the logbook entry.

I did have to contact their tech support once because of an issue I caused during the installation. I fat-fingered my N-number and couldn't seem to make the corrected one "stick" in the configuration. Their initial response told me exactly what I needed to do to resolve it (turn on Airplane mode then re-enable the Wi-Fi connection). By the way, those instructions were right there in the documentation, but having read it once, it seemed so simple that I didn't need to refer back to it – or so I thought! RTM, Jim!

Flight check resulted in a "clean" PAPR report, so I'm very happy with it.

Well, I’ve jumped through the troubleshooting hoops...checking signal interference, checking the ground, checking resistance and voltage...and after everything checked out, they have decided to send me a new unit. Hopefully I’ll get it next week and get it on shortly thereafter.

They have been really good to work with and made the recommendation themselves to replace it. I’ll update when I get it swapped and and test flown.


Sent from my iPhone using Tapatalk

Hope that solves it for ya [emoji1360]

My uavionix experince...

Last year, after the floats to wheels changeover, I was putting away the tools and equipment. Our mechanic was behind the airplane for about 15 minutes. When I finished I went to see what else needed to be done. He had installed the tail beacon and set it up via the app.

The test fight went perfectly. In the past year we’ve mostly flown in uncontrolled airspace, with occasional IFR and Class D, C, and B(!) airspace.

No problems whatsoever. I have not taken the time to download any further reports.

At $2000; they win the ADS-B solution. in in my opinion.

YMMV