Sat Sep 11, 2021 3:59 pm
#1869724
I was flying along happily today minding my own business (apart of course from keeping a perfect, heads up, lookout ) when, in the region of Haywards Heath, SE2 alerted me to an aircraft following me closely enough to be disconcerting. I altered course slightly, and so did it, I climbed and descended, and so did it. It felt too close behind for me to want to turn the aircraft through 90 degrees or more to have a look.
When I had a chance I had a closer look at the ipad display and realised that the call sign of the following a/c, "G-AVLO" was actually mine. I immediately assumed I had misconfigured the SE2 with the wrong callsign as I do use it in more that 1 aircraft, but a quick look showed the callsign was correct. Incidentally all the aircraft I fly have mode S transponders without ADSB out, so I transmit ADSB through the SE2
Once I realised this, I relaxed a bit and ignored the chasing aircraft. I have never experienced being followed by my own a/c before.
Later on the ground I had a look at the SE2 configuration and discovered that the ownship filter was not selected on.
Now, either this has been off all the time I have owned the device, (and I have used it for several tens of flights), or it has somehow inadvertently been turned off by me, or by itself.
I don't really know why I'm posting this except to wonder if anyone else has experienced this or has any explanation as to why this happened for the first time today if the ownship filter has been off all the time or what could have been the reason for it turning itself off. I always use skydemon to change the Hexcode and callsign for the a/c I am flying, and as far as I know, you can't make that change on SD. Perhaps you can and I have missed it. I don't think it was to do with the position fof the device as it was in the same position on the canopy of this a/c that it usually is.
I did wonder if there could have been a trial re-broadcast of ADSB traffic in a particular area.
I am now also a bit puzzled that it was always about 0.2nm behind me, and not in my exact GPS position.
Just musing really. Anyone else had this?
When I had a chance I had a closer look at the ipad display and realised that the call sign of the following a/c, "G-AVLO" was actually mine. I immediately assumed I had misconfigured the SE2 with the wrong callsign as I do use it in more that 1 aircraft, but a quick look showed the callsign was correct. Incidentally all the aircraft I fly have mode S transponders without ADSB out, so I transmit ADSB through the SE2
Once I realised this, I relaxed a bit and ignored the chasing aircraft. I have never experienced being followed by my own a/c before.
Later on the ground I had a look at the SE2 configuration and discovered that the ownship filter was not selected on.
Now, either this has been off all the time I have owned the device, (and I have used it for several tens of flights), or it has somehow inadvertently been turned off by me, or by itself.
I don't really know why I'm posting this except to wonder if anyone else has experienced this or has any explanation as to why this happened for the first time today if the ownship filter has been off all the time or what could have been the reason for it turning itself off. I always use skydemon to change the Hexcode and callsign for the a/c I am flying, and as far as I know, you can't make that change on SD. Perhaps you can and I have missed it. I don't think it was to do with the position fof the device as it was in the same position on the canopy of this a/c that it usually is.
I did wonder if there could have been a trial re-broadcast of ADSB traffic in a particular area.
I am now also a bit puzzled that it was always about 0.2nm behind me, and not in my exact GPS position.
Just musing really. Anyone else had this?
gaznav liked this