diamondaviators.net

The new release overlays "real-time" Flight Aware data on the map when you have a cellular connection. It's not intended for use in the air and presumably gets preempted by ADS-B IN, when that's being received. It's very laggy, but interesting.

The one feature FF really needs to add ASAP is one for depicting unpublished holds. This is a feature Garmin Pilot added recently and is a huge deal for those of us flying with G1000 software last updated in 2009.

TwinStarScott wrote: ↑Thu May 28, 2020 4:53 pm The one feature FF really needs to add ASAP is one for depicting unpublished holds. This is a feature Garmin Pilot added recently and is a huge deal for those of us flying with G1000 software last updated in 2009.

I could use some enlightenment here. Where does one get data for an unpublished hold so one can publish it?

Data for the 'unpublished hold' comes from an ATC instruction. It's not 'published', i.e. part of the FAA charted procedures, e.g. the hold at the end of a missed approach. I agree with Scott that this would be a nice addition to ForeFlight. From the Garmin website:

Customized holding procedures (Garmin Pilot)

Pilots now have the flexibility to easily build customized holding patterns. These holds may be created over an existing fix or over a user-defined waypoint and then inserted into a flight plan. When creating a hold, pilots can easily input an inbound or outbound course, select left or right turns and specify leg length in time or distance. Unpublished holds or those assigned by air traffic control are easily created and displayed within Garmin Pilot to simplify the process of visualizing and flying a holding pattern.

https://www.garmin.com/en-US/blog/aviat ... pilot-app/

Flying today I believe I have confirmed that the FlightAware targets are not used when ADSB-IN is being processed by FF. This is a good thing, as the latency of the FA data can be huge.