FLARM in Stealth Mode at US 15M/Standard Nationals - Loved It!

On Sunday, August 9, 2015 at 10:32:19 AM UTC-7, jfitch wrote:
On Sunday, August 9, 2015 at 5:51:45 AM UTC-7, wrote:
On Sunday, August 9, 2015 at 1:27:50 AM UTC-4, jfitch wrote:
On Saturday, August 8, 2015 at 7:41:24 PM UTC-7, Andy Blackburn wrote:
Hmmm...

Not according to the Flarm Dataport Specification 7.03 released on July 30, 2015 that says no target data is put onto the serial port for targets above 2 km in distance. At 17,000' and 110 kts IAS for two head-to-head targets that's a hair over 10 seconds.

9B

Without the target data on the serial port, you will not get a voice enunciation of that target from your third party device.

Not correct in all cases.
My Clearnav, with PF in Stealth, calls conflicts with audible "traffic 12 o'clock high". Some other combinations may not do this.
With this setup, as I used in Elmira, there is zero reason to look in the cockpit for any info from Flarm.
For ME, this is the perfect combination of adding additional safety to my scan, and having no tactical affect on the flight.
UH

This is entirely correct in all cases. Your ClearNav sees and warns only of those things the Flarm puts on its serial port. If it isn't on the serial port, it isn't there for ClearNav (or any other device). The question is, does the Flarm put a traffic warning on the serial port for a collision threat more than 2 km away in stealth mode? As was pointed out, traffic more than 2 km away is not a threat, except in certain circumstances such as fast closing speeds head on under a strong street.

It looks like the spec allows traffic information for targets that generate a collision warning. The tricky part is that this presumes that aircraft changes heading to become a threat. You'd need to understand a bit about how the algorithm sorts head-to-head targets and how close they have to be expected to come to generate an alarm. Based on what I understand about the algorithm it is possible that a target that changes course can go from hidden under Stealth to a threat at a distance between the maximum alarm range and the 2 km Stealth traffic limit and therefore become a bit of a nasty surprise. Most pilots fly pretty straight under cloud streets and in convergence.

Note to users - minimize the snaking around under cloud streets in stealth mode.

9B

On Sunday, August 9, 2015 at 4:01:35 PM UTC-7, Andy Blackburn wrote:
On Sunday, August 9, 2015 at 10:32:19 AM UTC-7, jfitch wrote:
On Sunday, August 9, 2015 at 5:51:45 AM UTC-7, wrote:
On Sunday, August 9, 2015 at 1:27:50 AM UTC-4, jfitch wrote:
On Saturday, August 8, 2015 at 7:41:24 PM UTC-7, Andy Blackburn wrote:
Hmmm...

Not according to the Flarm Dataport Specification 7.03 released on July 30, 2015 that says no target data is put onto the serial port for targets above 2 km in distance. At 17,000' and 110 kts IAS for two head-to-head targets that's a hair over 10 seconds.

9B

Without the target data on the serial port, you will not get a voice enunciation of that target from your third party device.

Not correct in all cases.
My Clearnav, with PF in Stealth, calls conflicts with audible "traffic 12 o'clock high". Some other combinations may not do this.
With this setup, as I used in Elmira, there is zero reason to look in the cockpit for any info from Flarm.
For ME, this is the perfect combination of adding additional safety to my scan, and having no tactical affect on the flight.
UH

This is entirely correct in all cases. Your ClearNav sees and warns only of those things the Flarm puts on its serial port. If it isn't on the serial port, it isn't there for ClearNav (or any other device). The question is, does the Flarm put a traffic warning on the serial port for a collision threat more than 2 km away in stealth mode? As was pointed out, traffic more than 2 km away is not a threat, except in certain circumstances such as fast closing speeds head on under a strong street.

Typo corrected.

It looks like the spec allows traffic information for targets that generate a collision warning. The tricky part is that this presumes that NEITHER aircraft changes heading to become a threat. You'd need to understand a bit about how the algorithm sorts head-to-head targets and how close they have to be expected to come to generate an alarm. Based on what I understand about the algorithm it is possible that a target that changes course can go from hidden under Stealth to a threat at a distance between the maximum alarm range and the 2 km Stealth traffic limit and therefore become a bit of a nasty surprise. Most pilots fly pretty straight under cloud streets and in convergence.

Note to users - minimize the snaking around under cloud streets in stealth mode.

9B