Last March we installed a FlightFeeder at Placid Lakes Airport (09FA) so we could see the ADS-B flights that arrive and depart. Unfortunately after the install the ADS-B equipped aircraft arriving and departing 09FA showed on the airport page for Sebring, FL (KSEF) about 15 miles away. We contacted tech support who assumed this must be a bug of some sort and submitted a ticket. After months of back and forth via text, email and phone calls someone finally managed to communicate with the “ADS-B Team” who determined that all non-ICAO airports (the vast majority of them) were excluded from ADS-B position tracking, even those that host a FlightFeeder. This provides little benefit for non-ICAO fields who host a FlightFeeder as the airport page will not show flights unless they are fed from ATC. No data from the FlightFeeder will be posted on the host airport page. While I don’t understand why FlightAware will not include any non-ICAO airports in there position only database including there FlightFeeder hosts and Enterprise customers, FlightAware should be more upfront about this limitation before an airport invests in a FlightFeeder instillation or pays for an enterprise account.
Ironically the FlightFeeder airport featured in FlightAware’s latest ADS-B newsletter SOARING CLUB OF HOUSTON AIRPORT (WALLER, TX) 89TA is not supported. I wonder if the Soaring Club was aware of that before they installed both 978 and 1090 feeders on there field.