# Impossible data on a military aircraft

**URL:** <https://discussions.flightaware.com/t/impossible-data-on-a-military-aircraft/100737>\
**Category:** ADS-B Flight Tracking\
**Created:** [September 8, 2026, 6:01pm UTC](https://discussions.flightaware.com/t/impossible-data-on-a-military-aircraft/100737 "2026-09-08T18:01:32Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![marc131](https://sea1.discourse-cdn.com/flex019/user_avatar/discussions.flightaware.com/marc131/32/137113_2.png) [@marc131](https://discussions.flightaware.com/u/marc131)\
**Post date:** [September 8, 2026, 6:01pm UTC](https://discussions.flightaware.com/t/impossible-data-on-a-military-aircraft/100737/1 "2026-09-08T18:01:33Z")

</div>

Hello.  
Something very curious just happened to me.

For quite some time now, I’ve been seeing this Spanish Army CASA C-295 with some impossible data.

It appears at 243 nmi, at only 3000 ft, and in an area not covered by my station.  
The signal is MLAT, and I have good RSSI.

This is the first time I’ve seen it at my station.

I don’t want to reduce the maximum range since that distance is common during ducting. I receive signals from long distances, but in reasonable situations, that is, towards the sea.

The callsign keeps changing from JASON40, JASON42, BARBO41…  
I’m checking it on ADSB-EXCHANGE and the same thing is happening.

> **[ADS-B Exchange - track aircraft live](https://globe.adsbexchange.com/?icao=342693)**
>
> ADS-B Exchange - track aircraft live - aircraft flight history

My question is, since it’s a military flight, is it transmitting false data, or what could be causing this?

 ![Captura de pantalla_2026-09-08_20-03-00](https://us1.discourse-cdn.com/flex019/uploads/flightaware/original/3X/7/d/7dd3ab6ab13bb88f9fe950a4c0b26bd5fc3a0d28.jpeg)

---

<div class="post-metadata">

**Author:** ![marc131](https://sea1.discourse-cdn.com/flex019/user_avatar/discussions.flightaware.com/marc131/32/137113_2.png) [@marc131](https://discussions.flightaware.com/u/marc131)\
**Post date:** [September 8, 2026, 9:51pm UTC](https://discussions.flightaware.com/t/impossible-data-on-a-military-aircraft/100737/3 "2026-09-08T21:51:38Z")

</div>

No, that’s not it, obviously.

---

<div class="post-metadata">

**Author:** ![obj](https://sea1.discourse-cdn.com/flex019/user_avatar/discussions.flightaware.com/obj/32/118984_2.png) [@obj](https://discussions.flightaware.com/u/obj)\
**Post date:** [September 9, 2026, 12:56am UTC](https://discussions.flightaware.com/t/impossible-data-on-a-military-aircraft/100737/4 "2026-09-09T00:56:46Z")

</div>

Probably a shared aircraft address (hexid)  
i.e. you are seeing the union of mlat positions for \>1 physical aircraft in different places  
(and the grace-period for mlat position feedback means you see some positions where your receiver didn’t actually contribute directly)

---

<div class="post-metadata">

**Author:** ![marc131](https://sea1.discourse-cdn.com/flex019/user_avatar/discussions.flightaware.com/marc131/32/137113_2.png) [@marc131](https://discussions.flightaware.com/u/marc131)\
**Post date:** [September 9, 2026, 1:31pm UTC](https://discussions.flightaware.com/t/impossible-data-on-a-military-aircraft/100737/5 "2026-09-09T13:31:26Z")

</div>

Thanks for your reply. The funny thing is, while the plane was over the center of the country, I was getting an RSSI of 17. 😊
