Good thing I welded 1/16" steel in there. Still need to know the required opening diameter.
Steve, my impression is that even if the support ring fit, the electronics are too wide to fit between the fabric surfaces without rubbing. True?
Why not the Skybeacon?
Personally i think its ugly.
In fact, so is the Tailbeacon,
but imho less noticeable on tbe tail.
Also imho less prone to damage on the tail--
Ive knocked off a wingtip nav light before,
but never an aft nav light (yet).
I also dont like the lack of symetry with two different looking wingtip arrangements--
must be my OCD tendencies.
Here's a non-commercial ADS-B site run by enthusiasts: https://www.adsbexchange.com
Click on the radar icon on the right. You can zoom out and drag to anywhere in the world, and set that location as a default. The receivers are provided by volunteers and are not tied in to the FAA.
Mike, how did you update the skybeacon software--
Download to PC, then plug a (USB?) cord between it & the unit?
If so, did you have to remove the unit from the airplane?
Or is it some sort of wireless magic?
It is a compromise, inexpensive to buy the equipment and to install. If you don't like the looks there are a bunch of alternatives. All it takes is cubic dollars and the choices are out there
If I were starting with an uncovered rudder, I think I'd consider doing what it takes to put the tail beacon in, including fairing the fabric somehow. But also use a conventional strobe / tail light with a separate ring. The main reason is because the wingtip model's strobe is so deficient. I assume it's legal, but it's not at all bright. One thought against that plan would be if the strobe wiring interfered with the ADSB function.
I just received my uAvionix tailbeacon but I take from this thread, it will not fit to replace a Super Cub taillight. I'd be interested if anyone successfully fits it to a standard SC rudder. …..
Yes, I knew that - thanks. That's why I was pondering a separate Wheelen unit on the tail.Gordon, not sure if you know but FYI the Tailbeacon does not include a strobe feature--
I just noticed this unusual nav light installation on a local Cub.
Maybe applicable to mounting a Tailbeacon?
It would be a lot less noticeable if the sealant matched the paint.
View attachment 44639
I don't think the tailBeacon would work in that configuration.I just noticed this unusual nav light installation on a local Cub.
Maybe applicable to mounting a Tailbeacon?
It would be a lot less noticeable if the sealant matched the paint.
would they play nice together??? noise wise??
….Did a short 10 minute flight in some nearby class C airspace as a test.
When I went online to check the results, everything looked good on the PAPR report except for one thing:
under "missing elements", "flight ID" was red-tagged.
Gonna call uAvionix later today and ask them about it.....
I had one of those conversations with the ADS-B Nazis in DC as well. The guy was polite, but inflexible. He told me my altitude reporting wasn't working correctly (actually, it wasn't reporting pressure altitude at all) and suggested I return the unit to the manufacturer. I told him I was aware of the problem, the unit had been to the manufacturer numerous times without resolution and I was actively working on the issue with the manufacturer. Then he said I would not be allowed to fly in ADS-B airspace with a unit that wasn't passing. OK, so ADS-B isn't even a rule yet (and most ATC facilities couldn't receive ADS-B information a year ago when I had this conversation with them), so what air space was considered to be "ADS-B Air space" since the rule doesn't apply until 2020? I was flying in a remote area nowhere near any controlled air space and was staying far away from controlled air space while I worked on the problem. Additionally, the first flight with any ADS-B unit is a test flight since you don't know for sure it is functioning correctly until you pull a performance report, how can he tell me I'm not allowed to fly the unit for troubleshooting and diagnostic purposes? Pulling a function report is how I know it is or isn't working correctly, and what needs to be addressed. Many first, second or multiple flights often times have issues with the ADS-B out. That's why we pull the reports, is so we can find and resolve the issues.
What I learned is that the guy in DC only seemed to understand 1090-ES functionality, and had extremely limited knowledge of the interaction between a UAT-Out unit and the transponder. And they seem to be completely inflexible when it comes to giving any leeway to diagnose and repair a problem. His only solution was that it had to be shipped back to the manufacturer for repairs even though that wasn't going to affect the issue one way or the other since I was having a dynamic interaction problem that was only showing up in flight.
I finally swapped ADS-B units between my planes effectively moving the problem unit to a different registration number while I resolved the issue. This particular unit seemed to have chronic issues with query and reply communications between it and my transponders, both of which are newer digital transponders. It would work perfectly on the ground, then get a failing error rate on the pressure altitude once I was in the air. If I remember right >2% error rate is failing. I was able to eventually resolve the issue, but the FAA telling me I wasn't allowed to turn it on wasn't helpful in the resolution.
-Cub Builder