sensors Mode-S transponder
39A565
ICAO 24-bit transponder address · allocated to France
Currently assigned to F-HJLF · SOCATA TBM-900/910/930/940
- Hex
- 39A565
- Octal
- 16322545
- Decimal
- 3,777,893
- Country
- FR
- Tail
- F-HJLF
- Type
- TBM9
- Flights observed
- 81
- Distinct callsigns
- 2
- Country
- FR
- Last broadcast
- 7h ago
Last known position
Country allocation
The ICAO 24-bit address 39A565 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 2 distinct
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-24 | FHJLF | - | Jul 24, 14:25 UTC | Jul 24, 15:25 UTC | 1h 0m |
| 2026-07-24 | FHJLF | - | Jul 24, 12:20 UTC | Jul 24, 13:50 UTC | 1h 30m |
| 2026-07-24 | FHJLF | - | Jul 24, 08:15 UTC | Jul 24, 09:45 UTC | 1h 30m |
| 2026-07-24 | FHJLF | - | Jul 24, 06:10 UTC | Jul 24, 07:10 UTC | 1h 0m |
| 2026-07-21 | FHJLF | IBZ → LBG | Jul 21, 15:05 UTC | Jul 21, 17:30 UTC | 2h 25m |
| 2026-07-18 | FHJLF | - | Jul 18, 12:30 UTC | Jul 18, 14:00 UTC | 1h 30m |
| 2026-07-15 | FHJLF | - | Jul 15, 12:50 UTC | Jul 15, 13:05 UTC | 15m |
| 2026-07-13 | FHJLF | - | Jul 13, 11:25 UTC | Jul 13, 12:45 UTC | 1h 20m |
| 2026-07-12 | FHJLF | JAH → LBG | Jul 12, 18:10 UTC | Jul 12, 19:50 UTC | 1h 40m |
| 2026-07-10 | FHJLF | - | Jul 10, 07:25 UTC | Jul 10, 08:50 UTC | 1h 25m |
| 2026-07-09 | FHJLF | MLA → LBG | Jul 9, 10:55 UTC | Jul 9, 14:25 UTC | 3h 30m |
| 2026-07-07 | FHJLF | - | Jul 7, 10:10 UTC | Jul 7, 13:25 UTC | 3h 15m |
| 2026-07-05 | FHJLF | - | Jul 5, 17:55 UTC | Jul 5, 19:30 UTC | 1h 35m |
| 2026-07-05 | FHJLF | - | Jul 5, 14:45 UTC | Jul 5, 16:05 UTC | 1h 20m |
| 2026-07-05 | FHJLF | - | Jul 5, 13:15 UTC | Jul 5, 14:10 UTC | 55m |
| 2026-07-04 | FHJLF | - | Jul 4, 14:15 UTC | Jul 4, 16:15 UTC | 2h 0m |
| 2026-07-04 | FHJLF | - | Jul 4, 10:00 UTC | Jul 4, 10:35 UTC | 35m |
| 2026-07-03 | FHJLF | - | Jul 3, 15:55 UTC | Jul 3, 17:30 UTC | 1h 35m |
| 2026-06-28 | FHJLF | CEQ → TNF | Jun 28, 16:14 UTC | Jun 28, 17:44 UTC | 1h 30m |
| 2026-06-26 | FHJLF | - | Jun 26, 15:45 UTC | Jun 26, 17:35 UTC | 1h 50m |
| 2026-06-20 | FHJLF | - | Jun 20, 08:09 UTC | Jun 20, 09:39 UTC | 1h 30m |
| 2026-06-20 | FHJLF | - | Jun 20, 05:59 UTC | Jun 20, 07:34 UTC | 1h 35m |
| 2026-06-17 | FHJLF | - | Jun 17, 15:00 UTC | Jun 17, 16:40 UTC | 1h 40m |
| 2026-06-17 | FHJLF | NUE → CEQ | Jun 17, 12:20 UTC | Jun 17, 14:00 UTC | 1h 40m |
| 2026-06-17 | FHJLF | BOD → NUE | Jun 17, 06:50 UTC | Jun 17, 09:10 UTC | 2h 20m |
| 2026-06-17 | FHJLF | - | Jun 17, 04:30 UTC | Jun 17, 05:50 UTC | 1h 20m |
| 2026-06-14 | FHJLF | LME → LBG | Jun 14, 12:00 UTC | Jun 14, 12:40 UTC | 40m |
| 2026-06-13 | FHJLF | LBG → LME | Jun 13, 08:20 UTC | Jun 13, 09:05 UTC | 45m |
| 2026-06-12 | FHJLF | - | Jun 12, 16:15 UTC | Jun 12, 16:55 UTC | 40m |
| 2026-06-11 | FHJLF | LBG → LME | Jun 11, 13:55 UTC | Jun 11, 14:35 UTC | 40m |
| 2026-06-07 | FHJLF | - | Jun 7, 17:40 UTC | Jun 7, 18:45 UTC | 1h 5m |
| 2026-06-07 | FHJLF | - | Jun 7, 06:20 UTC | Jun 7, 06:55 UTC | 35m |
| 2026-06-05 | FHJLF | - | Jun 5, 17:30 UTC | Jun 5, 18:15 UTC | 45m |
| 2026-06-05 | FHJLF | - | Jun 5, 09:10 UTC | Jun 5, 10:10 UTC | 1h 0m |
| 2026-06-04 | FHJLF | - | Jun 4, 15:40 UTC | Jun 4, 17:20 UTC | 1h 40m |
| 2026-06-04 | FHJLF | - | Jun 4, 07:15 UTC | Jun 4, 08:15 UTC | 1h 0m |
| 2026-06-02 | FHJLF | LBG → GVA | Jun 2, 16:10 UTC | Jun 2, 17:20 UTC | 1h 10m |
| 2026-05-31 | FHJLF | - | May 31, 16:10 UTC | May 31, 17:50 UTC | 1h 40m |
| 2026-05-29 | FHJLF | - | May 29, 14:45 UTC | May 29, 16:25 UTC | 1h 40m |
| 2026-05-26 | FHJLF | - | May 26, 05:45 UTC | May 26, 06:10 UTC | 25m |
| 2026-05-21 | FHJLF | - | May 21, 18:50 UTC | May 21, 19:40 UTC | 50m |
| 2026-05-21 | FHJLF | CDG → FAB | May 21, 15:50 UTC | May 21, 16:50 UTC | 1h 0m |
| 2026-05-16 | FHJLF | - | May 16, 14:01 UTC | May 16, 17:20 UTC | 3h 20m |
| 2026-05-15 | FHJLF | - | May 15, 07:45 UTC | May 15, 09:15 UTC | 1h 30m |
| 2026-05-13 | FHJLF | - | May 13, 11:00 UTC | May 13, 12:45 UTC | 1h 45m |
| 2026-05-10 | FHJLF | - | May 10, 06:59 UTC | May 10, 08:35 UTC | 1h 35m |
| 2026-05-07 | FHJLF | EBU → CEQ | May 7, 15:50 UTC | May 7, 16:30 UTC | 40m |
| 2026-05-07 | FHJLF | - | May 7, 15:20 UTC | May 7, 15:35 UTC | 15m |
| 2026-05-07 | FHJLF | - | May 7, 13:25 UTC | May 7, 14:00 UTC | 35m |
| 2026-05-07 | FHJLF | - | May 7, 12:05 UTC | May 7, 12:15 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.
Prefer a tail-number view? See the F-HJLF page for operator, model, and routing details .