sensors Mode-S transponder
3988DD
ICAO 24-bit transponder address · allocated to France
- Hex
- 3988DD
- Octal
- 16304335
- Decimal
- 3,770,589
- Country
- FR
- Flights observed
- 25
- Distinct callsigns
- 1
- Country
- FR
- Last broadcast
- Jul 26, 17:25 UTC
Last known position
Country allocation
The ICAO 24-bit address 3988DD 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 |
|---|---|---|---|
| FJLXP | - | 25 | 2026-07-26 |
Recent flights last 25
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-26 | FJLXP | - | Jul 26, 17:05 UTC | Jul 26, 17:25 UTC | 20m |
| 2026-07-25 | FJLXP | - | Jul 25, 15:30 UTC | Jul 25, 15:45 UTC | 15m |
| 2026-07-20 | FJLXP | - | Jul 20, 05:55 UTC | Jul 20, 06:25 UTC | 30m |
| 2026-07-18 | FJLXP | - | Jul 18, 15:20 UTC | Jul 18, 15:30 UTC | 10m |
| 2026-07-14 | FJLXP | - | Jul 14, 13:50 UTC | Jul 14, 14:45 UTC | 55m |
| 2026-07-10 | FJLXP | - | Jul 10, 16:15 UTC | Jul 10, 17:00 UTC | 45m |
| 2026-07-09 | FJLXP | - | Jul 9, 14:25 UTC | Jul 9, 17:15 UTC | 2h 50m |
| 2026-07-09 | FJLXP | - | Jul 9, 12:35 UTC | Jul 9, 13:50 UTC | 1h 15m |
| 2026-07-01 | FJLXP | - | Jul 1, 18:50 UTC | Jul 1, 19:20 UTC | 30m |
| 2026-07-01 | FJLXP | - | Jul 1, 15:40 UTC | Jul 1, 15:50 UTC | 10m |
| 2026-06-22 | FJLXP | - | Jun 22, 05:40 UTC | Jun 22, 06:29 UTC | 50m |
| 2026-06-20 | FJLXP | - | Jun 20, 13:19 UTC | Jun 20, 13:39 UTC | 20m |
| 2026-06-17 | FJLXP | - | Jun 17, 15:30 UTC | Jun 17, 15:50 UTC | 20m |
| 2026-06-17 | FJLXP | - | Jun 17, 12:50 UTC | Jun 17, 13:10 UTC | 20m |
| 2026-06-09 | FJLXP | - | Jun 9, 11:25 UTC | Jun 9, 12:40 UTC | 1h 15m |
| 2026-06-09 | FJLXP | - | Jun 9, 07:20 UTC | Jun 9, 08:50 UTC | 1h 30m |
| 2026-06-07 | FJLXP | - | Jun 7, 16:05 UTC | Jun 7, 17:15 UTC | 1h 10m |
| 2026-05-30 | FJLXP | - | May 30, 17:15 UTC | May 30, 17:45 UTC | 30m |
| 2026-05-30 | FJLXP | - | May 30, 15:20 UTC | May 30, 16:00 UTC | 40m |
| 2026-05-29 | FJLXP | - | May 29, 17:50 UTC | May 29, 18:20 UTC | 30m |
| 2026-05-29 | FJLXP | - | May 29, 16:05 UTC | May 29, 16:40 UTC | 35m |
| 2026-04-30 | FJLXP | - | Apr 30, 13:25 UTC | Apr 30, 14:15 UTC | 50m |
| 2026-04-20 | FJLXP | - | Apr 20, 05:50 UTC | Apr 20, 06:20 UTC | 30m |
| 2026-04-19 | FJLXP | - | Apr 19, 14:15 UTC | Apr 19, 14:40 UTC | 25m |
| 2026-04-18 | FJLXP | - | Apr 18, 16:00 UTC | Apr 18, 16:10 UTC | 10m |
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.