sensors Mode-S transponder
39CF03
ICAO 24-bit transponder address · allocated to France
Currently assigned to F-HTYD · AIRBUS A-350-900
- Hex
- 39CF03
- Octal
- 16347403
- Decimal
- 3,788,547
- Country
- FR
- Tail
- F-HTYD
- Type
- A359
- Flights observed
- 204
- Distinct callsigns
- 20
- Country
- FR
- Last broadcast
- Jul 24, 00:05 UTC
Last known position
Country allocation
The ICAO 24-bit address 39CF03 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 20 distinct
| Callsign | Airline | Flights | Last seen |
|---|---|---|---|
| AFR435 | Air France | 20 | 2026-07-21 |
| AFR436 | Air France | 12 | 2026-07-20 |
| AFR407 | - | 11 | 2026-06-28 |
| AFR406 | - | 7 | 2026-06-27 |
| AFR348F | - | 6 | 2026-07-19 |
| AFR194 | Air France | 6 | 2026-06-01 |
| AFR75K | - | 5 | 2026-07-15 |
| AFR52X | - | 5 | 2026-07-08 |
| AFR491 | - | 5 | 2026-07-16 |
| AFR349 | - | 5 | 2026-07-20 |
| AFR191 | Air France | 5 | 2026-06-01 |
| AFR074 | - | 5 | 2026-07-15 |
| AFR578 | Air France | 4 | 2026-07-21 |
| AFR490 | Air France | 4 | 2026-07-23 |
| AFR465 | - | 4 | 2026-07-13 |
| AFR431 | Air France | 4 | 2026-05-09 |
| AFR416 | - | 4 | 2026-07-14 |
| AFR415 | - | 4 | 2026-07-14 |
| AFR579 | - | 3 | 2026-06-20 |
| AFR53X | - | 3 | 2026-07-09 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-23 | AFR490 | CDG → PTY | Jul 23, 14:40 UTC | Jul 24, 00:05 UTC | 9h 25m |
| 2026-07-22 | AFR375G | YVR → CDG | Jul 22, 21:35 UTC | Jul 23, 06:15 UTC | 8h 40m |
| 2026-07-22 | AFR374F | CDG → YVR | Jul 22, 01:55 UTC | Jul 22, 19:15 UTC | 17h 20m |
| 2026-07-21 | AFR578 | CDG → CKY | Jul 21, 16:50 UTC | Jul 22, 16:35 UTC | 23h 45m |
| 2026-07-21 | AFR578 | CDG → CKY | Jul 21, 16:00 UTC | Jul 22, 14:45 UTC | 22h 45m |
| 2026-07-21 | AFR435 | MEX → CDG | Jul 21, 09:50 UTC | Jul 21, 12:35 UTC | 2h 45m |
| 2026-07-21 | AFR435 | MEX → CDG | Jul 21, 02:50 UTC | Jul 21, 03:05 UTC | 15m |
| 2026-07-20 | AFR436 | CDG → BOG | Jul 20, 14:15 UTC | Jul 20, 23:50 UTC | 9h 35m |
| 2026-07-20 | AFR349 | YUL → CDG | Jul 20, 02:45 UTC | Jul 20, 09:05 UTC | 6h 20m |
| 2026-07-19 | AFR348F | - | Jul 19, 16:45 UTC | Jul 19, 23:35 UTC | 6h 50m |
| 2026-07-19 | AFR435 | MEX → CDG | Jul 19, 02:50 UTC | Jul 19, 12:35 UTC | 9h 45m |
| 2026-07-18 | AFR436 | CDG → BOG | Jul 18, 14:20 UTC | Jul 19, 00:15 UTC | 9h 55m |
| 2026-07-18 | AFR349 | YUL → CDG | Jul 18, 03:15 UTC | Jul 18, 09:40 UTC | 6h 25m |
| 2026-07-17 | AFR348F | - | Jul 17, 18:05 UTC | Jul 18, 00:39 UTC | 6h 35m |
| 2026-07-16 | AFR491 | - | Jul 16, 23:25 UTC | Jul 17, 14:30 UTC | 15h 5m |
| 2026-07-16 | AFR490 | - | Jul 16, 15:40 UTC | Jul 17, 14:30 UTC | 22h 50m |
| 2026-07-15 | AFR75K | RDU → CDG | Jul 15, 22:20 UTC | Jul 16, 05:35 UTC | 7h 15m |
| 2026-07-15 | AFR074 | - | Jul 15, 11:35 UTC | Jul 15, 19:40 UTC | 8h 5m |
| 2026-07-14 | AFR415 | - | Jul 14, 23:00 UTC | Jul 15, 07:05 UTC | 8h 5m |
| 2026-07-14 | AFR416 | - | Jul 14, 12:10 UTC | Jul 14, 20:40 UTC | 8h 30m |
| 2026-07-13 | AFR465 | - | Jul 13, 10:50 UTC | Jul 14, 06:00 UTC | 19h 10m |
| 2026-07-13 | AFR465 | - | Jul 13, 09:05 UTC | Jul 14, 06:00 UTC | 20h 55m |
| 2026-07-12 | AFR75K | - | Jul 12, 22:35 UTC | Jul 13, 05:45 UTC | 7h 10m |
| 2026-07-12 | AFR074 | - | Jul 12, 12:01 UTC | Jul 12, 19:50 UTC | 7h 50m |
| 2026-07-11 | AFR465 | - | Jul 11, 16:50 UTC | Jul 12, 05:45 UTC | 12h 55m |
| 2026-07-11 | AFR465 | - | Jul 11, 08:55 UTC | Jul 12, 05:45 UTC | 20h 50m |
| 2026-07-10 | AFR75K | - | Jul 10, 23:00 UTC | Jul 11, 06:01 UTC | 7h 0m |
| 2026-07-10 | AFR074 | - | Jul 10, 11:45 UTC | Jul 10, 20:05 UTC | 8h 20m |
| 2026-07-09 | AFR415 | FOR → CDG | Jul 9, 23:00 UTC | Jul 10, 07:05 UTC | 8h 5m |
| 2026-07-09 | AFR416 | - | Jul 9, 12:20 UTC | Jul 9, 20:45 UTC | 8h 25m |
| 2026-07-09 | AFR53X | IAD → CDG | Jul 9, 01:55 UTC | Jul 9, 08:55 UTC | 7h 0m |
| 2026-07-08 | AFR52X | - | Jul 8, 15:35 UTC | Jul 8, 23:05 UTC | 7h 30m |
| 2026-07-08 | AFR11E | - | Jul 8, 05:20 UTC | Jul 8, 11:55 UTC | 6h 35m |
| 2026-07-07 | AFR012 | CDG → JFK | Jul 7, 19:05 UTC | Jul 8, 02:15 UTC | 7h 10m |
| 2026-07-05 | AFR75K | RDU → CDG | Jul 5, 22:35 UTC | Jul 6, 05:30 UTC | 6h 55m |
| 2026-07-05 | AFR074 | - | Jul 5, 11:25 UTC | Jul 5, 19:30 UTC | 8h 5m |
| 2026-07-04 | AFR337P | SEA → CDG | Jul 4, 23:00 UTC | Jul 5, 08:05 UTC | 9h 5m |
| 2026-07-04 | AFR338 | - | Jul 4, 09:20 UTC | Jul 4, 18:50 UTC | 9h 30m |
| 2026-07-03 | AFR75K | - | Jul 3, 22:55 UTC | Jul 4, 06:15 UTC | 7h 20m |
| 2026-07-03 | AFR074 | - | Jul 3, 12:15 UTC | Jul 3, 20:15 UTC | 8h 0m |
| 2026-07-02 | AFR934 | - | Jul 2, 09:40 UTC | Jul 2, 13:10 UTC | 3h 30m |
| 2026-07-01 | AFR375G | - | Jul 1, 20:30 UTC | Jul 2, 05:15 UTC | 8h 45m |
| 2026-07-01 | AFR374F | - | Jul 1, 09:10 UTC | Jul 1, 18:30 UTC | 9h 20m |
| 2026-06-30 | AFR333F | BOS → CDG | Jun 30, 21:30 UTC | Jul 1, 03:40 UTC | 6h 10m |
| 2026-06-30 | AFR334M | - | Jun 30, 11:50 UTC | Jun 30, 18:40 UTC | 6h 50m |
| 2026-06-28 | AFR407 | - | Jun 28, 16:55 UTC | Jun 29, 03:44 UTC | 10h 50m |
| 2026-06-28 | AFR407 | - | Jun 28, 14:45 UTC | Jun 28, 14:54 UTC | 10m |
| 2026-06-27 | AFR406 | - | Jun 27, 22:29 UTC | Jun 28, 09:05 UTC | 10h 35m |
| 2026-06-26 | AFR435 | - | Jun 26, 23:30 UTC | Jun 27, 13:55 UTC | 14h 25m |
| 2026-06-26 | AFR435 | - | Jun 26, 16:49 UTC | Jun 27, 13:55 UTC | 21h 5m |
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-HTYD page for operator, model, and routing details .