sensors Mode-S transponder
39CF0F
ICAO 24-bit transponder address · allocated to France
Currently assigned to F-HTYP · AIRBUS A-350-900
- Hex
- 39CF0F
- Octal
- 16347417
- Decimal
- 3,788,559
- Country
- FR
- Tail
- F-HTYP
- Type
- A359
- Flights observed
- 222
- Distinct callsigns
- 20
- Country
- FR
- Last broadcast
- Jul 26, 21:35 UTC
Current position
Country allocation
The ICAO 24-bit address 39CF0F 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 |
|---|---|---|---|
| AFR407 | Air France | 16 | 2026-07-24 |
| AFR435 | - | 12 | 2026-07-03 |
| AFR406 | Air France | 11 | 2026-07-23 |
| AFR174 | Air France | 10 | 2026-05-28 |
| AFR173 | Air France | 9 | 2026-05-29 |
| AFR52X | Air France | 8 | 2026-06-07 |
| AFR431 | Air France | 8 | 2026-05-31 |
| AFR096 | Air France | 8 | 2026-07-21 |
| AFR436 | - | 7 | 2026-07-03 |
| AFR097 | Air France | 6 | 2026-07-22 |
| AFR491 | - | 5 | 2026-07-10 |
| AFR191 | - | 5 | 2026-06-11 |
| AFR754 | Air France | 4 | 2026-05-26 |
| AFR53M | Air France | 4 | 2026-05-31 |
| AFR430 | Air France | 4 | 2026-05-31 |
| AFR199 | Air France | 4 | 2026-07-23 |
| AFR198 | Air France | 4 | 2026-07-22 |
| AFR874 | Air France | 3 | 2026-05-27 |
| AFR871 | Air France | 3 | 2026-04-18 |
| AFR868 | Air France | 3 | 2026-04-17 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-26 | AFR490 | CDG → PTY | Jul 26, 14:10 UTC | Jul 26, 21:35 UTC | 7h 25m |
| 2026-07-26 | AFR57J | LAS → CDG | Jul 26, 01:10 UTC | Jul 26, 10:35 UTC | 9h 26m |
| 2026-07-25 | AFR56T | CDG → LAS | Jul 25, 12:05 UTC | Jul 25, 22:40 UTC | 10h 35m |
| 2026-07-24 | AFR407 | SCL → CDG | Jul 24, 17:10 UTC | Jul 25, 03:25 UTC | 10h 15m |
| 2026-07-23 | AFR406 | CDG → SCL | Jul 23, 21:50 UTC | Jul 23, 22:50 UTC | 1h 0m |
| 2026-07-23 | AFR199 | BKK → CDG | Jul 23, 05:00 UTC | Jul 23, 16:40 UTC | 11h 40m |
| 2026-07-22 | AFR198 | CDG → BKK | Jul 22, 14:55 UTC | Jul 23, 01:30 UTC | 10h 35m |
| 2026-07-22 | AFR097 | MCO → CDG | Jul 22, 02:55 UTC | Jul 22, 11:15 UTC | 8h 20m |
| 2026-07-21 | AFR096 | CDG → MCO | Jul 21, 15:05 UTC | Jul 21, 23:25 UTC | 8h 20m |
| 2026-07-21 | AFR179 | MEX → CDG | Jul 21, 02:00 UTC | Jul 21, 12:15 UTC | 10h 15m |
| 2026-07-20 | AFR178 | CDG → MEX | Jul 20, 12:20 UTC | Jul 20, 23:00 UTC | 10h 40m |
| 2026-07-18 | AFR995 | JNB → CDG | Jul 18, 17:05 UTC | Jul 19, 03:30 UTC | 10h 25m |
| 2026-07-17 | AFR990 | - | Jul 17, 22:20 UTC | Jul 18, 08:25 UTC | 10h 6m |
| 2026-07-17 | AFR097 | - | Jul 17, 03:14 UTC | Jul 17, 11:20 UTC | 8h 5m |
| 2026-07-16 | AFR096 | - | Jul 16, 15:05 UTC | Jul 16, 23:55 UTC | 8h 50m |
| 2026-07-16 | AFR097 | MCO → CDG | Jul 16, 03:10 UTC | Jul 16, 11:10 UTC | 8h 0m |
| 2026-07-15 | AFR096 | - | Jul 15, 15:05 UTC | Jul 15, 23:45 UTC | 8h 40m |
| 2026-07-15 | AFR179 | - | Jul 15, 01:30 UTC | Jul 15, 11:45 UTC | 10h 15m |
| 2026-07-14 | AFR178 | - | Jul 14, 12:00 UTC | Jul 14, 22:50 UTC | 10h 49m |
| 2026-07-13 | AFR357E | YYZ → CDG | Jul 13, 22:15 UTC | Jul 14, 05:05 UTC | 6h 50m |
| 2026-07-13 | AFR356G | - | Jul 13, 12:30 UTC | Jul 13, 19:45 UTC | 7h 15m |
| 2026-07-13 | AFR33J | - | Jul 13, 00:20 UTC | Jul 13, 08:15 UTC | 7h 55m |
| 2026-07-12 | AFR32J | - | Jul 12, 12:40 UTC | Jul 12, 21:10 UTC | 8h 30m |
| 2026-07-12 | AFR349 | YUL → CDG | Jul 12, 03:05 UTC | Jul 12, 09:25 UTC | 6h 20m |
| 2026-07-11 | AFR348F | - | Jul 11, 16:55 UTC | Jul 11, 23:40 UTC | 6h 45m |
| 2026-07-10 | AFR491 | - | Jul 10, 21:50 UTC | Jul 11, 13:10 UTC | 15h 20m |
| 2026-07-10 | AFR490 | - | Jul 10, 14:25 UTC | Jul 11, 11:45 UTC | 21h 21m |
| 2026-07-10 | AFR33J | - | Jul 10, 01:05 UTC | Jul 10, 09:00 UTC | 7h 55m |
| 2026-07-09 | AFR32J | - | Jul 9, 13:20 UTC | Jul 9, 22:10 UTC | 8h 50m |
| 2026-07-09 | AFR349 | YUL → CDG | Jul 9, 03:15 UTC | Jul 9, 09:30 UTC | 6h 15m |
| 2026-07-08 | AFR348F | - | Jul 8, 17:00 UTC | Jul 8, 23:55 UTC | 6h 55m |
| 2026-07-07 | AFR491 | - | Jul 7, 23:05 UTC | Jul 8, 13:30 UTC | 14h 25m |
| 2026-07-07 | AFR491 | - | Jul 7, 15:50 UTC | Jul 8, 13:30 UTC | 21h 40m |
| 2026-07-07 | AFR490 | - | Jul 7, 15:25 UTC | Jul 8, 13:30 UTC | 22h 5m |
| 2026-07-05 | AFR097 | - | Jul 5, 03:20 UTC | Jul 5, 11:15 UTC | 7h 55m |
| 2026-07-04 | AFR096 | - | Jul 4, 15:45 UTC | Jul 5, 00:30 UTC | 8h 45m |
| 2026-07-03 | AFR435 | - | Jul 3, 22:00 UTC | Jul 4, 12:55 UTC | 14h 55m |
| 2026-07-03 | AFR436 | - | Jul 3, 15:50 UTC | Jul 4, 12:55 UTC | 21h 5m |
| 2026-07-03 | AFR436 | - | Jul 3, 14:30 UTC | Jul 4, 12:55 UTC | 22h 25m |
| 2026-07-02 | AFR375G | YVR → CDG | Jul 2, 21:00 UTC | Jul 3, 05:45 UTC | 8h 45m |
| 2026-07-02 | AFR374F | - | Jul 2, 09:20 UTC | Jul 2, 18:40 UTC | 9h 20m |
| 2026-07-01 | AFR741 | SDQ → CDG | Jul 1, 11:50 UTC | Jul 2, 06:00 UTC | 18h 10m |
| 2026-06-30 | AFR579 | - | Jun 30, 16:05 UTC | Jul 1, 06:50 UTC | 14h 45m |
| 2026-06-30 | AFR435 | - | Jun 30, 11:20 UTC | Jun 30, 12:45 UTC | 1h 25m |
| 2026-06-29 | AFR436 | - | Jun 29, 14:14 UTC | Jun 29, 23:25 UTC | 9h 10m |
| 2026-06-29 | AFR935 | - | Jun 29, 05:34 UTC | Jun 29, 09:10 UTC | 3h 35m |
| 2026-06-28 | AFR935 | - | Jun 28, 10:04 UTC | Jun 29, 09:10 UTC | 23h 5m |
| 2026-06-27 | AFR337P | SEA → CDG | Jun 27, 21:15 UTC | Jun 28, 06:44 UTC | 9h 30m |
| 2026-06-27 | AFR338 | - | Jun 27, 08:44 UTC | Jun 27, 18:09 UTC | 9h 25m |
| 2026-06-25 | AFR253 | - | Jun 25, 19:49 UTC | Jun 26, 15:25 UTC | 19h 35m |
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-HTYP page for operator, model, and routing details .