sensors Mode-S transponder
38519D
ICAO 24-bit transponder address · allocated to France
Currently assigned to F-JDPS · AEROSPOOL WT-9 Dynamic
- Hex
- 38519D
- Octal
- 16050635
- Decimal
- 3,690,909
- Country
- FR
- Tail
- F-JDPS
- Type
- WT9
- Flights observed
- 37
- Distinct callsigns
- 1
- Country
- FR
- Last broadcast
- Jul 26, 12:30 UTC
Last known position
Country allocation
The ICAO 24-bit address 38519D falls within the block assigned to France (FR) by ICAO Annex 10, Volume III. Every aircraft registered in France receives a permanent address from this block at the time of registration; the address stays with the airframe even if the aircraft is re-registered to a different operator within the country.
Callsign history 1 distinct
| Callsign | Airline | Flights | Last seen |
|---|---|---|---|
| FJDPS | - | 37 | 2026-07-26 |
Recent flights last 37
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-26 | FJDPS | FNI → GAT | Jul 26, 11:35 UTC | Jul 26, 12:30 UTC | 55m |
| 2026-07-25 | FJDPS | - | Jul 25, 05:05 UTC | Jul 25, 05:50 UTC | 45m |
| 2026-07-23 | FJDPS | - | Jul 23, 10:30 UTC | Jul 23, 11:10 UTC | 40m |
| 2026-07-21 | FJDPS | - | Jul 21, 04:45 UTC | Jul 21, 05:20 UTC | 35m |
| 2026-07-19 | FJDPS | - | Jul 19, 05:05 UTC | Jul 19, 05:50 UTC | 45m |
| 2026-07-03 | FJDPS | - | Jul 3, 05:05 UTC | Jul 3, 05:55 UTC | 50m |
| 2026-07-01 | FJDPS | - | Jul 1, 06:50 UTC | Jul 1, 07:30 UTC | 40m |
| 2026-06-28 | FJDPS | FNI → GAT | Jun 28, 18:49 UTC | Jun 28, 19:34 UTC | 45m |
| 2026-06-28 | FJDPS | - | Jun 28, 07:40 UTC | Jun 28, 08:25 UTC | 45m |
| 2026-06-24 | FJDPS | - | Jun 24, 04:44 UTC | Jun 24, 05:29 UTC | 45m |
| 2026-06-22 | FJDPS | - | Jun 22, 07:14 UTC | Jun 22, 07:54 UTC | 40m |
| 2026-06-20 | FJDPS | - | Jun 20, 18:19 UTC | Jun 20, 18:59 UTC | 40m |
| 2026-06-19 | FJDPS | - | Jun 19, 07:34 UTC | Jun 19, 08:14 UTC | 40m |
| 2026-06-16 | FJDPS | - | Jun 16, 17:05 UTC | Jun 16, 17:59 UTC | 55m |
| 2026-06-16 | FJDPS | - | Jun 16, 08:35 UTC | Jun 16, 09:15 UTC | 40m |
| 2026-06-14 | FJDPS | GAT → GAT | Jun 14, 08:35 UTC | Jun 14, 09:40 UTC | 1h 5m |
| 2026-06-13 | FJDPS | - | Jun 13, 15:25 UTC | Jun 13, 17:25 UTC | 2h 0m |
| 2026-06-13 | FJDPS | - | Jun 13, 04:25 UTC | Jun 13, 06:25 UTC | 2h 0m |
| 2026-06-12 | FJDPS | - | Jun 12, 12:15 UTC | Jun 12, 13:00 UTC | 45m |
| 2026-06-12 | FJDPS | - | Jun 12, 05:10 UTC | Jun 12, 05:45 UTC | 35m |
| 2026-06-10 | FJDPS | - | Jun 10, 17:55 UTC | Jun 10, 18:40 UTC | 45m |
| 2026-06-10 | FJDPS | - | Jun 10, 06:50 UTC | Jun 10, 07:30 UTC | 40m |
| 2026-06-05 | FJDPS | - | Jun 5, 04:55 UTC | Jun 5, 05:40 UTC | 45m |
| 2026-06-04 | FJDPS | - | Jun 4, 04:40 UTC | Jun 4, 05:25 UTC | 45m |
| 2026-05-28 | FJDPS | - | May 28, 09:10 UTC | May 28, 09:30 UTC | 20m |
| 2026-05-28 | FJDPS | - | May 28, 06:35 UTC | May 28, 06:50 UTC | 15m |
| 2026-05-22 | FJDPS | - | May 22, 11:15 UTC | May 22, 12:00 UTC | 45m |
| 2026-05-18 | FJDPS | - | May 18, 04:51 UTC | May 18, 05:35 UTC | 45m |
| 2026-05-15 | FJDPS | FNI → GAT | May 15, 14:35 UTC | May 15, 15:25 UTC | 49m |
| 2026-05-15 | FJDPS | - | May 15, 05:40 UTC | May 15, 06:30 UTC | 50m |
| 2026-05-13 | FJDPS | FNI → GAT | May 13, 14:40 UTC | May 13, 15:25 UTC | 45m |
| 2026-05-13 | FJDPS | - | May 13, 04:40 UTC | May 13, 05:20 UTC | 40m |
| 2026-04-28 | FJDPS | FNI → GAT | Apr 28, 14:25 UTC | Apr 28, 15:15 UTC | 50m |
| 2026-04-27 | FJDPS | - | Apr 27, 05:35 UTC | Apr 27, 06:25 UTC | 50m |
| 2026-04-15 | FJDPS | FNI → GAT | Apr 15, 11:45 UTC | Apr 15, 12:30 UTC | 45m |
| 2026-04-15 | FJDPS | - | Apr 15, 05:00 UTC | Apr 15, 05:15 UTC | 15m |
| 2026-04-15 | FJDPS | - | Apr 15, 04:30 UTC | Apr 15, 04:50 UTC | 20m |
About Mode-S
A Mode-S transponder code (also called an "ICAO 24-bit address" or "hex code") is a 6-character hexadecimal identifier permanently assigned to an aircraft when it's first registered. Unlike callsigns (which change with each flight) or registrations (which can change if an aircraft is sold internationally), the Mode-S address stays with the airframe for the life of the aircraft in that country.
Every ADS-B transmission from an aircraft includes its Mode-S address, making it the most reliable way to identify a specific airframe. Flight-tracking services like Apparatus use the Mode-S address as the primary key for tying position broadcasts, callsigns, and ownership records together.
Prefer a tail-number view? See the F-JDPS page for operator, model, and routing details .