sensors Mode-S transponder
39B493
ICAO 24-bit transponder address · allocated to France
Currently assigned to F-HNET · AIRBUS A-350-900
- Hex
- 39B493
- Octal
- 16332223
- Decimal
- 3,781,779
- Country
- FR
- Tail
- F-HNET
- Type
- A359
- Flights observed
- 110
- Distinct callsigns
- 19
- Country
- FR
- Last broadcast
- 1h ago
Last known position
Country allocation
The ICAO 24-bit address 39B493 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 19 distinct
| Callsign | Airline | Flights | Last seen |
|---|---|---|---|
| FWI51W | - | 15 | 2026-06-30 |
| FWI11B | - | 12 | 2026-07-07 |
| FWI43M | - | 10 | 2026-07-12 |
| FWI57Q | - | 9 | 2026-06-30 |
| FBU92K | French Bee | 9 | 2026-05-04 |
| FWI67Z | Air Caraïbes | 8 | 2026-05-27 |
| FWI60T | Air Caraïbes | 8 | 2026-05-28 |
| FBU72J | French Bee | 8 | 2026-05-03 |
| FWI64Y | Air Caraïbes | 7 | 2026-05-30 |
| FWI649 | - | 5 | 2026-07-13 |
| FWI648 | - | 5 | 2026-07-13 |
| FBU95X | French Bee | 3 | 2026-06-28 |
| FBU89M | French Bee | 3 | 2026-06-27 |
| FBU93E | - | 2 | 2026-06-29 |
| FBU91S | - | 2 | 2026-06-28 |
| FWI46E | - | 1 | 2026-07-05 |
| FWI42P | - | 1 | 2026-07-01 |
| FWI17F | - | 1 | 2026-07-06 |
| FWI10A | - | 1 | 2026-04-13 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-13 | FWI649 | - | Jul 13, 23:45 UTC | Jul 14, 00:45 UTC | 1h 0m |
| 2026-07-13 | FWI648 | ORY → CUN | Jul 13, 11:40 UTC | Jul 13, 21:20 UTC | 9h 40m |
| 2026-07-12 | FWI43M | ORY → ORY | Jul 12, 12:05 UTC | Jul 13, 06:40 UTC | 18h 35m |
| 2026-07-11 | FWI649 | CUN → ORY | Jul 11, 23:15 UTC | Jul 12, 08:50 UTC | 9h 35m |
| 2026-07-11 | FWI648 | ORY → CUN | Jul 11, 10:30 UTC | Jul 11, 20:05 UTC | 9h 35m |
| 2026-07-10 | FWI43M | - | Jul 10, 12:50 UTC | Jul 11, 07:00 UTC | 18h 10m |
| 2026-07-10 | FWI43M | ORY → ORY | Jul 10, 11:55 UTC | Jul 11, 07:00 UTC | 19h 5m |
| 2026-07-09 | FWI43M | - | Jul 9, 12:50 UTC | Jul 10, 07:05 UTC | 18h 15m |
| 2026-07-09 | FWI43M | ORY → ORY | Jul 9, 12:05 UTC | Jul 10, 07:05 UTC | 19h 0m |
| 2026-07-08 | FWI649 | CUN → ORY | Jul 8, 23:10 UTC | Jul 9, 08:35 UTC | 9h 25m |
| 2026-07-08 | FWI648 | ORY → CUN | Jul 8, 09:55 UTC | Jul 8, 19:55 UTC | 10h 0m |
| 2026-07-07 | FWI11B | - | Jul 7, 10:50 UTC | Jul 8, 05:15 UTC | 18h 25m |
| 2026-07-07 | FWI11B | ORY → ORY | Jul 7, 10:35 UTC | Jul 8, 05:15 UTC | 18h 40m |
| 2026-07-06 | FWI11B | - | Jul 6, 12:50 UTC | Jul 7, 07:00 UTC | 18h 10m |
| 2026-07-06 | FWI11B | ORY → ORY | Jul 6, 12:40 UTC | Jul 7, 07:00 UTC | 18h 20m |
| 2026-07-06 | FWI17F | - | Jul 6, 02:25 UTC | Jul 6, 04:20 UTC | 1h 55m |
| 2026-07-05 | FWI46E | - | Jul 5, 09:30 UTC | Jul 5, 11:00 UTC | 1h 30m |
| 2026-07-04 | FWI11B | ORY → ORY | Jul 4, 12:05 UTC | Jul 5, 06:30 UTC | 18h 25m |
| 2026-07-03 | FWI43M | - | Jul 3, 12:50 UTC | Jul 4, 06:55 UTC | 18h 5m |
| 2026-07-03 | FWI43M | ORY → ORY | Jul 3, 11:55 UTC | Jul 4, 06:55 UTC | 19h 0m |
| 2026-07-01 | FWI43M | - | Jul 1, 12:50 UTC | Jul 2, 07:00 UTC | 18h 10m |
| 2026-07-01 | FWI42P | ORY → ORY | Jul 1, 12:15 UTC | Jul 2, 07:00 UTC | 18h 45m |
| 2026-06-30 | FWI51W | - | Jun 30, 12:50 UTC | Jul 1, 07:15 UTC | 18h 25m |
| 2026-06-30 | FWI57Q | ORY → ORY | Jun 30, 11:55 UTC | Jul 1, 07:15 UTC | 19h 20m |
| 2026-06-29 | FBU93E | YUL → ORY | Jun 29, 03:49 UTC | Jun 29, 10:04 UTC | 6h 15m |
| 2026-06-28 | FBU91S | ORY → YUL | Jun 28, 17:55 UTC | Jun 29, 00:39 UTC | 6h 45m |
| 2026-06-28 | FBU95X | SFO → ORY | Jun 28, 00:39 UTC | Jun 28, 11:00 UTC | 10h 20m |
| 2026-06-27 | FBU89M | ORY → SFO | Jun 27, 10:29 UTC | Jun 27, 20:55 UTC | 10h 25m |
| 2026-06-26 | FWI11B | ORY → ORY | Jun 26, 11:05 UTC | Jun 27, 06:19 UTC | 19h 15m |
| 2026-06-25 | FWI51W | - | Jun 25, 12:50 UTC | Jun 26, 06:50 UTC | 18h 0m |
| 2026-06-25 | FWI51W | ORY → ORY | Jun 25, 11:59 UTC | Jun 26, 06:50 UTC | 18h 50m |
| 2026-06-24 | FWI11B | - | Jun 24, 10:49 UTC | Jun 25, 05:29 UTC | 18h 40m |
| 2026-06-23 | FWI11B | ORY → ORY | Jun 23, 11:10 UTC | Jun 24, 05:44 UTC | 18h 35m |
| 2026-06-21 | FWI57Q | ORY → ORY | Jun 21, 11:15 UTC | Jun 22, 06:39 UTC | 19h 25m |
| 2026-06-20 | FBU93E | YUL → ORY | Jun 20, 03:44 UTC | Jun 20, 09:49 UTC | 6h 5m |
| 2026-06-19 | FBU91S | ORY → YUL | Jun 19, 18:25 UTC | Jun 20, 01:09 UTC | 6h 45m |
| 2026-06-18 | FWI57Q | ORY → ORY | Jun 18, 11:35 UTC | Jun 19, 06:24 UTC | 18h 49m |
| 2026-06-09 | FWI51W | CAY → ORY | Jun 9, 12:50 UTC | Jun 10, 07:15 UTC | 18h 25m |
| 2026-06-09 | FWI51W | CAY → ORY | Jun 9, 11:45 UTC | Jun 10, 07:15 UTC | 19h 30m |
| 2026-06-06 | FBU95X | SFO → ORY | Jun 6, 23:24 UTC | Jun 7, 09:15 UTC | 9h 50m |
| 2026-06-06 | FBU89M | ORY → SFO | Jun 6, 09:50 UTC | Jun 6, 20:30 UTC | 10h 40m |
| 2026-06-04 | FBU95X | SFO → ORY | Jun 4, 23:40 UTC | Jun 5, 09:50 UTC | 10h 10m |
| 2026-06-04 | FBU89M | ORY → SFO | Jun 4, 10:25 UTC | Jun 4, 20:50 UTC | 10h 25m |
| 2026-05-31 | FWI57Q | ORY → CAY | May 31, 11:50 UTC | Jun 1, 06:40 UTC | 18h 50m |
| 2026-05-30 | FWI64Y | ORY → PUJ | May 30, 10:30 UTC | May 30, 19:00 UTC | 8h 30m |
| 2026-05-29 | FWI51W | CAY → ORY | May 29, 12:50 UTC | May 30, 07:00 UTC | 18h 10m |
| 2026-05-29 | FWI57Q | ORY → CAY | May 29, 11:25 UTC | May 30, 07:00 UTC | 19h 35m |
| 2026-05-28 | FWI60T | SDQ → ORY | May 28, 15:45 UTC | May 29, 06:50 UTC | 15h 5m |
| 2026-05-28 | FWI60T | SDQ → ORY | May 28, 09:00 UTC | May 29, 06:50 UTC | 21h 50m |
| 2026-05-27 | FWI67Z | PUJ → ORY | May 27, 10:50 UTC | May 28, 05:55 UTC | 19h 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-HNET page for operator, model, and routing details .