FlightFeeder Issues - No Response

FlightAware ADS-B Flight Tracking
1

Hi everyone,

My FlightFeeder has suddenly developed some worrying symptoms.
Yesterday it started emitting a burning or chemical smell from the case/ports, and there is also a high‑pitched noise coming from the area around the USB‑C power input.

The unit was still feeding normally, but I powered it off immediately for safety.

I’m located in New Zealand, so any replacement hardware would take longer to ship and would be a higher cost for FlightAware. Because of that, I want to make sure I’m diagnosing this correctly before assuming the unit is beyond recovery.

Has anyone experienced this before? Does this usually indicate a failed power supply or an internal hardware fault? I’ve already contacted FlightAware support but haven’t received a reply yet, so I’m hoping someone here might have advice or know whether this typically results in a replacement unit.

Thanks in advance.

2

I think you have to wait until Monday, surely the FA servers run 24/7 but I think FA staff is working only during office hours.

For the flightfeeder hardware FA can diagnose what is wrong, most users here use their own hardware and that isn’t comparible with a Flightfeeder.

1 Like
3

I had a similar issue with a flightfeeder a couple of weeks ago. They shipped out another flightfeeder and it’s having nothing but problems. A reboot fixes things but only for a few minutes

Status

Signal Reception:

NOT CONNECTED TO MODE S RECEIVER

MLAT:

LOCAL CLOCK SOURCE IS UNSTABLE

FlightAware:

CONNECTED