sensors Mode-S transponder
39CF04
ICAO 24-bit transponder address · allocated to France
Currently assigned to F-HTYE · AIRBUS A-350-900
- Hex
- 39CF04
- Octal
- 16347404
- Decimal
- 3,788,548
- Country
- FR
- Tail
- F-HTYE
- Type
- A359
- Flights observed
- 88
- Distinct callsigns
- 20
- Country
- FR
- Last broadcast
- 15h ago
Last known position
Country allocation
The ICAO 24-bit address 39CF04 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 | - | 8 | 2026-07-02 |
| AFR436 | - | 6 | 2026-07-02 |
| AFR407 | - | 5 | 2026-06-22 |
| AFR258 | Air France | 4 | 2026-05-26 |
| AFR935 | - | 3 | 2026-06-26 |
| AFR406 | - | 3 | 2026-06-21 |
| AFR338 | - | 3 | 2026-06-23 |
| AFR337P | - | 3 | 2026-06-23 |
| AFR253 | Air France | 3 | 2026-05-23 |
| AFR174 | - | 3 | 2026-06-28 |
| AFR173 | - | 3 | 2026-06-29 |
| AFR754 | Air France | 2 | 2026-05-28 |
| AFR579 | - | 2 | 2026-06-13 |
| AFR578 | - | 2 | 2026-06-26 |
| AFR53X | Air France | 2 | 2026-06-20 |
| AFR52X | - | 2 | 2026-06-19 |
| AFR491 | - | 2 | 2026-06-18 |
| AFR430 | Air France | 2 | 2026-05-16 |
| AFR264 | - | 2 | 2026-06-21 |
| AFR11E | Air France | 2 | 2026-05-22 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-03 | AFR579A | - | Jul 3, 17:35 UTC | Jul 4, 07:40 UTC | 14h 5m |
| 2026-07-02 | AFR435 | - | Jul 2, 22:55 UTC | Jul 3, 14:35 UTC | 15h 40m |
| 2026-07-02 | AFR436 | - | Jul 2, 15:05 UTC | Jul 3, 14:35 UTC | 23h 30m |
| 2026-07-02 | AFR4085 | JFK → CDG | Jul 2, 05:50 UTC | Jul 2, 12:20 UTC | 6h 30m |
| 2026-07-01 | AFR064 | - | Jul 1, 19:10 UTC | Jul 2, 02:45 UTC | 7h 35m |
| 2026-07-01 | AFR4087 | SEA → CDG | Jul 1, 05:30 UTC | Jul 1, 12:00 UTC | 6h 30m |
| 2026-06-30 | AFR064 | CDG → EWR | Jun 30, 19:15 UTC | Jul 1, 02:55 UTC | 7h 40m |
| 2026-06-29 | AFR684 | CDG → RUH | Jun 29, 21:39 UTC | Jun 30, 11:40 UTC | 14h 1m |
| 2026-06-29 | AFR173 | - | Jun 29, 04:50 UTC | Jun 29, 14:54 UTC | 10h 5m |
| 2026-06-28 | AFR174 | - | Jun 28, 14:25 UTC | Jun 29, 01:50 UTC | 11h 25m |
| 2026-06-28 | AFR57J | LAS → CDG | Jun 28, 01:04 UTC | Jun 28, 10:50 UTC | 9h 45m |
| 2026-06-27 | AFR56T | - | Jun 27, 12:04 UTC | Jun 27, 22:15 UTC | 10h 10m |
| 2026-06-26 | AFR578 | - | Jun 26, 17:00 UTC | Jun 27, 07:19 UTC | 14h 20m |
| 2026-06-26 | AFR935 | - | Jun 26, 06:19 UTC | Jun 26, 09:20 UTC | 3h 0m |
| 2026-06-25 | AFR935 | - | Jun 25, 13:29 UTC | Jun 26, 09:20 UTC | 19h 50m |
| 2026-06-25 | AFR935 | - | Jun 25, 11:04 UTC | Jun 26, 09:20 UTC | 22h 15m |
| 2026-06-25 | AFR934 | - | Jun 25, 09:59 UTC | Jun 26, 09:00 UTC | 23h 0m |
| 2026-06-24 | AFR848 | - | Jun 24, 11:24 UTC | Jun 25, 05:25 UTC | 18h 0m |
| 2026-06-23 | AFR337P | - | Jun 23, 21:29 UTC | Jun 24, 06:35 UTC | 9h 5m |
| 2026-06-23 | AFR338 | - | Jun 23, 09:24 UTC | Jun 23, 18:45 UTC | 9h 20m |
| 2026-06-22 | AFR407 | - | Jun 22, 16:34 UTC | Jun 23, 03:39 UTC | 11h 5m |
| 2026-06-21 | AFR406 | - | Jun 21, 22:29 UTC | Jun 22, 01:35 UTC | 3h 5m |
| 2026-06-21 | AFR267 | - | Jun 21, 03:30 UTC | Jun 21, 16:59 UTC | 13h 30m |
| 2026-06-21 | AFR264 | - | Jun 21, 00:04 UTC | Jun 21, 00:34 UTC | 30m |
| 2026-06-20 | AFR264 | - | Jun 20, 13:24 UTC | Jun 20, 23:19 UTC | 9h 55m |
| 2026-06-20 | AFR53X | IAD → CDG | Jun 20, 02:29 UTC | Jun 20, 09:05 UTC | 6h 35m |
| 2026-06-19 | AFR52X | - | Jun 19, 16:25 UTC | Jun 20, 00:14 UTC | 7h 50m |
| 2026-06-18 | AFR491 | - | Jun 18, 22:25 UTC | Jun 19, 13:04 UTC | 14h 39m |
| 2026-06-18 | AFR491 | - | Jun 18, 15:05 UTC | Jun 19, 13:04 UTC | 21h 59m |
| 2026-06-18 | AFR490 | - | Jun 18, 14:45 UTC | Jun 19, 12:59 UTC | 22h 14m |
| 2026-06-17 | AFR337P | - | Jun 17, 20:55 UTC | Jun 18, 06:00 UTC | 9h 5m |
| 2026-06-17 | AFR338 | CDG → SEA | Jun 17, 08:35 UTC | Jun 17, 17:50 UTC | 9h 15m |
| 2026-06-16 | AFR085 | SFO → CDG | Jun 16, 05:55 UTC | Jun 16, 16:15 UTC | 10h 20m |
| 2026-06-15 | AFR086 | CDG → SFO | Jun 15, 16:30 UTC | Jun 16, 02:50 UTC | 10h 20m |
| 2026-06-15 | AFR435 | - | Jun 15, 04:10 UTC | Jun 15, 12:39 UTC | 8h 30m |
| 2026-06-14 | AFR436 | - | Jun 14, 14:25 UTC | Jun 15, 00:49 UTC | 10h 24m |
| 2026-06-13 | AFR579 | - | Jun 13, 17:45 UTC | Jun 14, 07:40 UTC | 13h 55m |
| 2026-06-13 | AFR173 | MEX → CDG | Jun 13, 04:40 UTC | Jun 13, 14:50 UTC | 10h 10m |
| 2026-06-12 | AFR174 | - | Jun 12, 14:35 UTC | Jun 13, 01:45 UTC | 11h 10m |
| 2026-06-11 | AFR407 | - | Jun 11, 16:45 UTC | Jun 12, 04:00 UTC | 11h 15m |
| 2026-06-11 | AFR407 | SCL → CDG | Jun 11, 14:55 UTC | Jun 11, 15:05 UTC | 10m |
| 2026-06-10 | AFR406 | CDG → SCL | Jun 10, 22:25 UTC | Jun 11, 00:20 UTC | 1h 55m |
| 2026-06-09 | AFR579 | CKY → CDG | Jun 9, 16:45 UTC | Jun 10, 06:05 UTC | 13h 20m |
| 2026-06-09 | AFR53X | IAD → CDG | Jun 9, 01:45 UTC | Jun 9, 08:40 UTC | 6h 55m |
| 2026-06-08 | AFR52X | CDG → IAD | Jun 8, 15:35 UTC | Jun 8, 23:05 UTC | 7h 30m |
| 2026-06-08 | AFR179 | MEX → CDG | Jun 8, 01:45 UTC | Jun 8, 12:00 UTC | 10h 15m |
| 2026-06-07 | AFR178 | CDG → MEX | Jun 7, 12:05 UTC | Jun 7, 23:05 UTC | 11h 0m |
| 2026-06-06 | AFR069 | PHX → CDG | Jun 6, 22:30 UTC | Jun 7, 08:15 UTC | 9h 45m |
| 2026-06-06 | AFR068 | CDG → PHX | Jun 6, 09:24 UTC | Jun 6, 19:34 UTC | 10h 10m |
| 2026-06-05 | AFR578 | CDG → CKY | Jun 5, 16:40 UTC | Jun 6, 06:10 UTC | 13h 30m |
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-HTYE page for operator, model, and routing details .