Garfly

Yes, simple, single level circular hangars would make more sense in most places. As the designer admitted: “Where I live in Canada there is a lot of wide-open space around the airports where people are free to build hangars. So, there’s not an appetite ... for something more complicated. I need an airport that has limited space and a long waiting list for hangar space.”

Yeah, I think the image with the aircraft inside gives a pretty good idea of scale. By the look of it, though, it's probably more compact than your usual 9 aircraft hangar. And every machine is in poll position. Nice.

Canadian Pilot Creates Alternative Hangar Storage Solution WWW.FLYINGMAG.COM ‘Aircraft carousel’ design helps provide additional hangar storage availability, especially at airports with space constraints.

Something of an update:

In my experience, though, OzRwys Support has always been quick on the uptake, friendly and helpful.

You may need to trim your expectations regarding the Forum. To my mind, though, you got a pretty good run.

Skippy, I thought the waters were well clarified on this issue last year. I thought we established that your transponder while Mode S was not an ES ADSB-OUT device and therefore was fine to run together with your SE2 (IN and OUT). That being the case, no contradiction arises between any of the statements you quote above - including your own.

I'd say that fixating on any one thing can be dangerous in aviation (even more so on the road). But that'd include fixating on the front window if the threat is not to be seen out there. While driving we instinctively combine info from all three mirrors and the view out-front to get the situational awareness we need. Maybe we need to develop that kind of instinct in the air to divide our attention between screen and windscreen.

Where's the mud?

That middle "ADS-B" light flashes green when the device is transmitting an ADSB signal. You can turn it on in OzRwys in the "Traffic" menu which you can reach by pressing on the little rectangular traffic button on the main OzRwys screen (in the upper right). But that does not explain why it is not receiving traffic. As long as you have established a network connection between the SE2 device and your iOS device (via the iOS "WiFi" menu) then it should display visible targets even with ADSB-OUT turned off in the OzRwys Traffic menu. More info here about how the different symbols indicate different operations. 15. Traffic DOCS.OZRUNWAYS.COM The reason OzRwys give you the option of switching ADSB-OUT off is that it allows you to use the SE2 as an IN only device. This is very useful for anyone who is operating an aircraft that already has an ADSB-OUT transponder but no dedicated traffic-IN display. You can use your own SE2 with a paired tablet/phone to see other traffic whilst using the installed Xponder to be seen (it's against the regs to have two OUT devices going at once in the same aircraft).

Yes Alan, it should work on the ground, though it'll only see line-of-sight targets within a certain range. In normal use it expects to see a good view of the sky from the cockpit. I suppose that the OzRwys craft you're seeing just don't have ADSB-OUT. But, if you expect they should have (pretty much all commercial aircraft do these days) but they're not showing as ADSB targets (with the little radio wave icon in the corner of the bubble) even though they're in line-of-sight, then you might want to check your settings. If you scroll down to the bottom of your "Settings" menu in OzRwys you should see a "Device Options" and a "SkyEcho2" option. In the former you should check that "Enable GDL90" is switched on. And in the SE2 menu you should look to see if all the options are selected ON. Also, that screen has a window that shows "Visible Aircraft". If there are ADSB transmitting craft nearby (and in-sight) it will show how many its picking up. I find this to be a good quick check on its functioning - as long as I'm sure there must be at least one in range.

Moneybox, I think the reason you are seeing so few targets is that your OzRunways is, by default, only set up to show the aircraft participating in its own (web-based) 'traffic' exchange system. It does not include the ADSB traffic that Flight Radar 24 (and similar) apps display. There is an explanation about how those various systems operate and interact here: 15. Traffic DOCS.OZRUNWAYS.COM But there is a way to have ADSB traffic show on your EFB (OzRwys or AvPlan) map page (short of using an ADSB receiver) and that is by using the AvTraffic app. The Premium version allows integration with OzRwys/AvPlan such that it displays ADSB traffic (sourced from the ADSB-Exchange) merged with your own EFB's in-house traffic. The EFBs use various symbols to indicate the different sources of data. But all of this type of traffic info is subject to some slight delay since it is coming via the internet. For more reliable aircraft-to-aircraft, real-time traffic you'd need to have an ADSB-IN device (like the SkyEcho2 or better). But even AvTraffic doesn't bother displaying ADSB targets from all over the country (and world) like FR24 etc. because it's designed as a practical piloting tool. Still, I think it shows everything within a hundred nautical miles or more. OzRyws' own system limits itself to the 18 nearest (participating) aircraft, which, at night, might well cover the whole country as your screen shot shows. AvTraffic AVTRAFFIC.COM

Yeah, I see they're presenting there too.

But, to reiterate, that action might have been the (expected) reaction to a double engine failure rather than the cause of it: “Here (in the AAIB prelim report) there is a reference to the pilot cutting off, let’s assume that the pilots cut off both the switches and then put it back again. Now that’s exactly what you’re supposed to do as per the checklist if you lose thrust on both engines." Capt. Sam Thomas. See the minute from around 07:30 https://www.youtube.com/watch?v=rJ_oNlBE_o8

Or have been let down before by "understanding" them all too well.

Russ Niles of AvWeb adds this take: Without Video, We'll Never Really Know - AVweb AVWEB.COM Will the real cause of the crash of Air India 171 ever be known? Excerpt: "As with everything else it seems, those switches feed wires that end up at a computer, which has the final decision on whether the simple opening or closing of a circuit can proceed. That little box, strapped unceremoniously to the main fan housing of the massive engine, controls all things to do with the fuel, including its sudden absence, a handy feature if it’s on fire but a disaster a few seconds after the mains have air under them. A solder joint on that control unit is prone to cracking and airlines were advised to replace them in 2021. This plane was said to be up to date on all those sorts of maintenance advisories, so I assume it was done. But the working theory heading around the airline blogs and forums is that it’s possible that a cracked solder joint interrupted the current from the switches under the Gs of rotation to stop the fuel flow long enough to shut down both engines. As far-fetched as it seems, it introduces enough doubt to lay waste to all the other depressing scenarios being bandied about and the arguments that flow from there."

Yes, I gather Capt. Thomas' point was that the moving of those switches, at all, has wrongly been taken as incontrovertible evidence of foul play. I, for one, am glad to see someone running his argument. Time might tell.