sensors Mode-S transponder
39CE24
ICAO 24-bit transponder address · allocated to France
Currently assigned to F-HTRE · AIRBUS A-350-900
- Hex
- 39CE24
- Octal
- 16347044
- Decimal
- 3,788,324
- Country
- FR
- Tail
- F-HTRE
- Type
- A359
- Flights observed
- 126
- Distinct callsigns
- 20
- Country
- FR
- Last broadcast
- 40m ago
Last known position
Country allocation
The ICAO 24-bit address 39CE24 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 |
|---|---|---|---|
| FWI67Z | Air Caraïbes | 18 | 2026-06-10 |
| FWI51W | - | 17 | 2026-07-13 |
| FWI57Q | - | 9 | 2026-07-10 |
| FWI11B | - | 9 | 2026-07-09 |
| FWI60T | Air Caraïbes | 7 | 2026-06-18 |
| FBU95X | French Bee | 7 | 2026-06-25 |
| FBU89M | French Bee | 7 | 2026-06-25 |
| FWI64Y | Air Caraïbes | 6 | 2026-06-10 |
| FWI649 | Air Caraïbes | 4 | 2026-05-11 |
| FWI43M | - | 4 | 2026-07-07 |
| FWI71K | - | 3 | 2026-07-09 |
| FWI648 | Air Caraïbes | 3 | 2026-05-11 |
| FWI42P | - | 3 | 2026-06-27 |
| FWI10A | - | 3 | 2026-07-01 |
| FBU92K | French Bee | 3 | 2026-05-26 |
| FBU72J | French Bee | 3 | 2026-05-25 |
| FWI29V | Air Caraïbes | 2 | 2026-05-04 |
| FBU85A | - | 2 | 2026-06-30 |
| FBU80G | - | 2 | 2026-06-29 |
| FBU76W | - | 2 | 2026-05-25 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-13 | FWI51W | ORY → ORY | Jul 13, 12:00 UTC | Jul 14, 06:35 UTC | 18h 35m |
| 2026-07-12 | FWI51W | ORY → ORY | Jul 12, 11:30 UTC | Jul 13, 06:25 UTC | 18h 55m |
| 2026-07-11 | FWI51W | ORY → ORY | Jul 11, 11:45 UTC | Jul 12, 06:45 UTC | 19h 0m |
| 2026-07-10 | FWI51W | - | Jul 10, 13:05 UTC | Jul 11, 07:05 UTC | 18h 0m |
| 2026-07-10 | FWI57Q | ORY → ORY | Jul 10, 11:50 UTC | Jul 11, 07:05 UTC | 19h 15m |
| 2026-07-09 | FWI11B | ORY → ORY | Jul 9, 11:50 UTC | Jul 10, 06:15 UTC | 18h 25m |
| 2026-07-09 | FWI71K | - | Jul 9, 07:25 UTC | Jul 9, 08:50 UTC | 1h 25m |
| 2026-07-08 | FWI14J | ORY → FDF | Jul 8, 14:40 UTC | Jul 8, 16:05 UTC | 1h 25m |
| 2026-07-07 | FWI43M | ORY → ORY | Jul 7, 12:00 UTC | Jul 8, 06:40 UTC | 18h 40m |
| 2026-07-06 | FWI51W | ORY → ORY | Jul 6, 14:05 UTC | Jul 7, 08:45 UTC | 18h 40m |
| 2026-07-05 | FWI5671 | - | Jul 5, 07:50 UTC | Jul 5, 11:15 UTC | 3h 25m |
| 2026-07-04 | FWI57Q | - | Jul 4, 13:50 UTC | Jul 4, 15:35 UTC | 1h 45m |
| 2026-07-03 | FWI51W | ORY → ORY | Jul 3, 11:45 UTC | Jul 4, 06:35 UTC | 18h 50m |
| 2026-07-02 | FWI51W | - | Jul 2, 13:05 UTC | Jul 3, 07:15 UTC | 18h 10m |
| 2026-07-02 | FWI57Q | - | Jul 2, 12:05 UTC | Jul 3, 07:15 UTC | 19h 10m |
| 2026-07-01 | FWI10A | ORY → ORY | Jul 1, 11:20 UTC | Jul 2, 06:00 UTC | 18h 40m |
| 2026-06-30 | FBU85A | - | Jun 30, 03:55 UTC | Jun 30, 14:10 UTC | 10h 15m |
| 2026-06-29 | FBU85A | - | Jun 29, 17:10 UTC | Jun 30, 01:14 UTC | 8h 5m |
| 2026-06-29 | FBU80G | - | Jun 29, 06:50 UTC | Jun 29, 14:50 UTC | 8h 0m |
| 2026-06-28 | FBU80G | ORY → SFO | Jun 28, 17:04 UTC | Jun 29, 03:20 UTC | 10h 15m |
| 2026-06-27 | FWI42P | ORY → ORY | Jun 27, 12:19 UTC | Jun 28, 06:44 UTC | 18h 25m |
| 2026-06-26 | FWI51W | - | Jun 26, 13:04 UTC | Jun 27, 07:49 UTC | 18h 45m |
| 2026-06-26 | FWI51W | ORY → ORY | Jun 26, 12:29 UTC | Jun 27, 07:49 UTC | 19h 20m |
| 2026-06-25 | FBU95X | SFO → ORY | Jun 25, 23:19 UTC | Jun 26, 09:39 UTC | 10h 20m |
| 2026-06-25 | FBU89M | ORY → SFO | Jun 25, 09:55 UTC | Jun 25, 20:30 UTC | 10h 35m |
| 2026-06-23 | FBU95X | SFO → ORY | Jun 23, 23:44 UTC | Jun 24, 09:55 UTC | 10h 10m |
| 2026-06-23 | FBU89M | ORY → SFO | Jun 23, 10:35 UTC | Jun 23, 21:20 UTC | 10h 45m |
| 2026-06-21 | FBU95X | SFO → ORY | Jun 21, 00:14 UTC | Jun 21, 10:09 UTC | 9h 55m |
| 2026-06-20 | FBU89M | ORY → SFO | Jun 20, 10:59 UTC | Jun 20, 21:44 UTC | 10h 45m |
| 2026-06-20 | FWI5660 | - | Jun 20, 00:04 UTC | Jun 20, 07:44 UTC | 7h 40m |
| 2026-06-18 | FWI60T | SDQ → ORY | Jun 18, 08:45 UTC | Jun 18, 09:50 UTC | 1h 5m |
| 2026-06-16 | FBU95X | SFO → ORY | Jun 16, 23:30 UTC | Jun 17, 10:00 UTC | 10h 30m |
| 2026-06-16 | FBU89M | ORY → SFO | Jun 16, 10:09 UTC | Jun 16, 20:45 UTC | 10h 36m |
| 2026-06-14 | FWI51W | - | Jun 14, 13:05 UTC | Jun 15, 07:20 UTC | 18h 14m |
| 2026-06-14 | FWI57Q | ORY → CAY | Jun 14, 12:25 UTC | Jun 15, 07:20 UTC | 18h 54m |
| 2026-06-13 | FBU95X | SFO → ORY | Jun 13, 23:10 UTC | Jun 14, 09:30 UTC | 10h 21m |
| 2026-06-13 | FBU89M | ORY → SFO | Jun 13, 09:55 UTC | Jun 13, 20:25 UTC | 10h 30m |
| 2026-06-11 | FBU95X | SFO → ORY | Jun 11, 23:30 UTC | Jun 12, 09:35 UTC | 10h 5m |
| 2026-06-11 | FBU89M | ORY → SFO | Jun 11, 10:00 UTC | Jun 11, 21:05 UTC | 11h 5m |
| 2026-06-10 | FWI67Z | PUJ → ORY | Jun 10, 11:05 UTC | Jun 11, 05:55 UTC | 18h 50m |
| 2026-06-10 | FWI64Y | ORY → PUJ | Jun 10, 10:15 UTC | Jun 11, 05:55 UTC | 19h 40m |
| 2026-06-07 | FWI57Q | ORY → CAY | Jun 7, 11:40 UTC | Jun 8, 06:35 UTC | 18h 55m |
| 2026-06-05 | FWI51W | CAY → ORY | Jun 5, 11:25 UTC | Jun 6, 06:55 UTC | 19h 30m |
| 2026-06-04 | FWI60T | SDQ → ORY | Jun 4, 23:00 UTC | Jun 5, 06:25 UTC | 7h 25m |
| 2026-06-04 | FWI60T | SDQ → ORY | Jun 4, 09:05 UTC | Jun 5, 06:25 UTC | 21h 20m |
| 2026-06-04 | FWI60T | SDQ → ORY | Jun 4, 08:25 UTC | Jun 5, 06:25 UTC | 22h 0m |
| 2026-06-03 | CAJ1613 | - | Jun 3, 19:35 UTC | Jun 3, 20:55 UTC | 1h 20m |
| 2026-06-03 | CAJ1516 | - | Jun 3, 12:40 UTC | Jun 3, 16:05 UTC | 3h 25m |
| 2026-06-03 | CAJ1612 | - | Jun 3, 05:20 UTC | Jun 3, 08:05 UTC | 2h 45m |
| 2026-05-30 | FBU95X | SFO → ORY | May 30, 23:25 UTC | May 31, 09:45 UTC | 10h 20m |
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-HTRE page for operator, model, and routing details .