AirNav Systems Forum

AirNav Radar => AirNav Radar Discussion => Topic started by: anorak on October 03, 2012, 08:35:08 PM

Title: broken or miscoded transponder
Post by: anorak on October 03, 2012, 08:35:08 PM
21:11 on 03/10/12 and I have a broken or miscoded transponder on screen.  Checking the log entries I have it recorded at heights up to 80,000ft + (log entry attached)
Does anyone else see it please?
Dave.

Title: Re: broken or miscoded transponder
Post by: RodBearden on October 03, 2012, 09:23:01 PM
Hi Dave

I get a 000000 almost all the time here in Chorley, sometimes with valid callsigns like LEUCHA20, GETSUM11, EPS238, DLH014, GGFEY etc, but most often without any callsign or other data.

I've got it at the moment, squawking 0254  but no other info at all. It's so common that I hardly notice it.

I put most of it down to BAE Warton, which is in direct line of sight, where mysterious things may be happening. But I'm sure that some of them are genuinely broken or miscoded transponders.

Rod
Title: Re: broken or miscoded transponder
Post by: anorak on October 04, 2012, 09:02:12 AM
Warton "Skunk works" ?
Cheers Rod.
Title: Re: broken or miscoded transponder
Post by: anorak on October 04, 2012, 05:56:34 PM
It`s been around again for the last 3 1/2 hours, lower level tonight. Would MLAT work for this?
Title: Re: broken or miscoded transponder
Post by: Runway 31 on October 04, 2012, 06:03:01 PM
Dont see why not, still wouldnt tell you what it is but with sufficient MLATERS should give you an idea where it is

Alan
Title: Re: broken or miscoded transponder
Post by: anorak on October 04, 2012, 07:19:43 PM
All clues to what it is.  Mlat seems like it might be worth investigating, any one in the south and west with the facility?
Thanks Alan.