sensors Mode-S transponder
39BF0C
ICAO 24-bit transponder address · allocated to France
Currently assigned to F-HPYM · DIAMOND DA-62
- Hex
- 39BF0C
- Octal
- 16337414
- Decimal
- 3,784,460
- Country
- FR
- Tail
- F-HPYM
- Type
- DA62
- Flights observed
- 82
- Distinct callsigns
- 4
- Country
- FR
- Last broadcast
- 4d ago
Last known position
Country allocation
The ICAO 24-bit address 39BF0C 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 4 distinct
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-13 | FHPYM | - | Jul 13, 09:10 UTC | Jul 13, 10:50 UTC | 1h 40m |
| 2026-07-10 | FHPYM2 | - | Jul 10, 08:10 UTC | Jul 10, 09:25 UTC | 1h 15m |
| 2026-07-09 | FHPYM | - | Jul 9, 16:45 UTC | Jul 9, 17:15 UTC | 30m |
| 2026-07-09 | FHPYM | - | Jul 9, 15:55 UTC | Jul 9, 16:10 UTC | 15m |
| 2026-07-09 | FHPYM | - | Jul 9, 06:15 UTC | Jul 9, 06:35 UTC | 20m |
| 2026-07-09 | FHPYM | - | Jul 9, 04:50 UTC | Jul 9, 05:25 UTC | 35m |
| 2026-07-07 | FHPYM | - | Jul 7, 05:40 UTC | Jul 7, 06:10 UTC | 30m |
| 2026-07-06 | FHPYM | - | Jul 6, 16:05 UTC | Jul 6, 16:15 UTC | 10m |
| 2026-07-06 | FHPYM | - | Jul 6, 06:05 UTC | Jul 6, 06:20 UTC | 15m |
| 2026-07-06 | FHPYM | - | Jul 6, 04:50 UTC | Jul 6, 05:15 UTC | 25m |
| 2026-07-04 | FHPYM | - | Jul 4, 14:25 UTC | Jul 4, 14:35 UTC | 10m |
| 2026-07-03 | FHPYM | - | Jul 3, 13:05 UTC | Jul 3, 15:10 UTC | 2h 5m |
| 2026-07-03 | FHPYM | - | Jul 3, 07:15 UTC | Jul 3, 09:15 UTC | 2h 0m |
| 2026-07-02 | FHPYM | - | Jul 2, 18:30 UTC | Jul 2, 20:45 UTC | 2h 15m |
| 2026-07-02 | FHPYM | - | Jul 2, 09:50 UTC | Jul 2, 11:20 UTC | 1h 30m |
| 2026-07-02 | FHPYM | - | Jul 2, 06:15 UTC | Jul 2, 07:50 UTC | 1h 35m |
| 2026-07-01 | FHPYM | - | Jul 1, 12:30 UTC | Jul 1, 13:05 UTC | 35m |
| 2026-07-01 | FHPYM | - | Jul 1, 09:40 UTC | Jul 1, 10:10 UTC | 30m |
| 2026-06-30 | FHPYM | - | Jun 30, 13:45 UTC | Jun 30, 13:55 UTC | 10m |
| 2026-06-21 | FHPYM | - | Jun 21, 12:10 UTC | Jun 21, 13:39 UTC | 1h 30m |
| 2026-06-20 | FHPYM | - | Jun 20, 07:19 UTC | Jun 20, 09:05 UTC | 1h 45m |
| 2026-06-18 | FHPYM | - | Jun 18, 11:30 UTC | Jun 18, 12:45 UTC | 1h 15m |
| 2026-06-18 | FHPYM | - | Jun 18, 10:00 UTC | Jun 18, 10:45 UTC | 45m |
| 2026-06-15 | FHPYM | - | Jun 15, 14:20 UTC | Jun 15, 15:19 UTC | 1h 0m |
| 2026-06-15 | FHPYM | - | Jun 15, 13:15 UTC | Jun 15, 13:45 UTC | 30m |
| 2026-06-15 | FHPYM | - | Jun 15, 09:05 UTC | Jun 15, 09:40 UTC | 35m |
| 2026-06-15 | FHPYM | - | Jun 15, 06:24 UTC | Jun 15, 08:20 UTC | 1h 55m |
| 2026-06-15 | FHPYM | - | Jun 15, 03:50 UTC | Jun 15, 05:20 UTC | 1h 30m |
| 2026-06-12 | FHPYM | - | Jun 12, 13:50 UTC | Jun 12, 15:05 UTC | 1h 15m |
| 2026-06-12 | FHPYM | - | Jun 12, 10:00 UTC | Jun 12, 10:55 UTC | 55m |
| 2026-06-12 | FHPYM | - | Jun 12, 08:05 UTC | Jun 12, 09:05 UTC | 1h 0m |
| 2026-06-11 | FHPYM | - | Jun 11, 19:10 UTC | Jun 11, 19:40 UTC | 30m |
| 2026-06-11 | FHPYM | - | Jun 11, 13:35 UTC | Jun 11, 14:10 UTC | 35m |
| 2026-06-11 | FHPYM | - | Jun 11, 10:00 UTC | Jun 11, 11:00 UTC | 1h 0m |
| 2026-06-11 | FHPYM | - | Jun 11, 08:15 UTC | Jun 11, 09:00 UTC | 45m |
| 2026-06-10 | FHPYM | - | Jun 10, 16:30 UTC | Jun 10, 16:55 UTC | 25m |
| 2026-06-10 | FHPYM | - | Jun 10, 14:35 UTC | Jun 10, 15:00 UTC | 25m |
| 2026-06-10 | FHPYM | - | Jun 10, 13:40 UTC | Jun 10, 14:00 UTC | 20m |
| 2026-06-10 | FHPYM | - | Jun 10, 11:25 UTC | Jun 10, 12:40 UTC | 1h 15m |
| 2026-06-10 | FHPYM | - | Jun 10, 10:25 UTC | Jun 10, 10:40 UTC | 15m |
| 2026-05-27 | FHPYM | - | May 27, 05:40 UTC | May 27, 07:05 UTC | 1h 25m |
| 2026-05-26 | FHPYM | - | May 26, 14:40 UTC | May 26, 15:14 UTC | 35m |
| 2026-05-26 | FHPYM | - | May 26, 12:30 UTC | May 26, 13:50 UTC | 1h 20m |
| 2026-05-26 | FHPYM | - | May 26, 09:55 UTC | May 26, 10:20 UTC | 25m |
| 2026-05-26 | FHPYM | - | May 26, 07:40 UTC | May 26, 08:59 UTC | 1h 20m |
| 2026-05-25 | FHPYM | - | May 25, 07:55 UTC | May 25, 08:15 UTC | 20m |
| 2026-05-24 | FHPYM | - | May 24, 12:35 UTC | May 24, 13:35 UTC | 1h 0m |
| 2026-05-24 | FHPYM | - | May 24, 05:00 UTC | May 24, 06:05 UTC | 1h 5m |
| 2026-05-22 | FHPYM | - | May 22, 16:25 UTC | May 22, 16:45 UTC | 20m |
| 2026-05-22 | FHPYM | - | May 22, 14:45 UTC | May 22, 15:25 UTC | 40m |
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-HPYM page for operator, model, and routing details .