sensors Mode-S transponder
39BE89
ICAO 24-bit transponder address · allocated to France
Currently assigned to F-HPUJ · AIRBUS A-330-300
- Hex
- 39BE89
- Octal
- 16337211
- Decimal
- 3,784,329
- Country
- FR
- Tail
- F-HPUJ
- Type
- A333
- Flights observed
- 62
- Distinct callsigns
- 19
- Country
- FR
- Last broadcast
- Jul 26, 10:55 UTC
Last known position
Country allocation
The ICAO 24-bit address 39BE89 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 |
|---|---|---|---|
| FWI67Z | - | 12 | 2026-07-11 |
| FWI648 | Air Caraïbes | 9 | 2026-07-25 |
| FWI45V | Air Caraïbes | 8 | 2026-07-24 |
| FWI64Y | - | 7 | 2026-07-08 |
| FWI649 | Air Caraïbes | 7 | 2026-07-26 |
| FWI60T | - | 5 | 2026-07-03 |
| FWI87R | - | 2 | 2026-07-03 |
| FWI71K | Air Caraïbes | 1 | 2026-04-19 |
| FWI5660 | - | 1 | 2026-07-11 |
| FWI5649 | Air Caraïbes | 1 | 2026-07-23 |
| FWI5643 | Air Caraïbes | 1 | 2026-07-17 |
| FWI5607 | - | 1 | 2026-07-10 |
| FWI42P | - | 1 | 2026-07-14 |
| FWI17F | Air Caraïbes | 1 | 2026-04-23 |
| FWI1660 | - | 1 | 2026-07-10 |
| FWI14J | - | 1 | 2026-04-18 |
| FWI11B | Air Caraïbes | 1 | 2026-04-20 |
| CAJ1661 | - | 1 | 2026-06-20 |
| CAJ1660 | - | 1 | 2026-05-12 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-26 | FWI649 | CUN → ORY | Jul 26, 00:35 UTC | Jul 26, 10:45 UTC | 10h 11m |
| 2026-07-25 | FWI648 | ORY → CUN | Jul 25, 11:50 UTC | Jul 25, 21:25 UTC | 9h 35m |
| 2026-07-24 | FWI45V | PTP → ORY | Jul 24, 14:20 UTC | Jul 25, 08:35 UTC | 18h 15m |
| 2026-07-24 | FWI45V | PTP → ORY | Jul 24, 13:45 UTC | Jul 25, 08:35 UTC | 18h 50m |
| 2026-07-23 | FWI45V | PTP → ORY | Jul 23, 16:55 UTC | Jul 24, 10:55 UTC | 18h 0m |
| 2026-07-23 | FWI5649 | CUN → ORY | Jul 23, 03:05 UTC | Jul 23, 13:15 UTC | 10h 10m |
| 2026-07-20 | FWI648 | ORY → CUN | Jul 20, 10:20 UTC | Jul 20, 20:05 UTC | 9h 45m |
| 2026-07-17 | FWI5643 | PTP → ORY | Jul 17, 08:20 UTC | Jul 17, 09:55 UTC | 1h 35m |
| 2026-07-14 | FWI42P | - | Jul 14, 11:45 UTC | Jul 14, 12:55 UTC | 1h 10m |
| 2026-07-11 | FWI67Z | - | Jul 11, 23:15 UTC | Jul 12, 07:35 UTC | 8h 20m |
| 2026-07-11 | FWI67Z | ORY → ORY | Jul 11, 10:45 UTC | Jul 12, 07:35 UTC | 20h 50m |
| 2026-07-11 | FWI5660 | - | Jul 11, 06:05 UTC | Jul 11, 06:30 UTC | 25m |
| 2026-07-10 | FWI1660 | ORY → CDG | Jul 10, 16:20 UTC | Jul 11, 00:30 UTC | 8h 10m |
| 2026-07-10 | FWI5607 | - | Jul 10, 09:10 UTC | Jul 10, 10:35 UTC | 1h 25m |
| 2026-07-08 | FWI64Y | - | Jul 8, 10:10 UTC | Jul 8, 18:35 UTC | 8h 25m |
| 2026-07-07 | FWI649 | CUN → ORY | Jul 7, 00:15 UTC | Jul 7, 10:05 UTC | 9h 50m |
| 2026-07-06 | FWI648 | ORY → CUN | Jul 6, 11:40 UTC | Jul 6, 21:45 UTC | 10h 5m |
| 2026-07-05 | FWI649 | CUN → ORY | Jul 5, 00:45 UTC | Jul 5, 10:25 UTC | 9h 40m |
| 2026-07-04 | FWI648 | ORY → CUN | Jul 4, 12:15 UTC | Jul 4, 22:20 UTC | 10h 5m |
| 2026-07-03 | FWI45V | - | Jul 3, 14:20 UTC | Jul 4, 09:00 UTC | 18h 40m |
| 2026-07-03 | FWI87R | ORY → ORY | Jul 3, 14:10 UTC | Jul 4, 09:00 UTC | 18h 50m |
| 2026-07-03 | FWI60T | - | Jul 3, 01:10 UTC | Jul 3, 09:20 UTC | 8h 10m |
| 2026-07-02 | FWI60T | ORY → ORY | Jul 2, 10:30 UTC | Jul 3, 09:20 UTC | 22h 50m |
| 2026-07-01 | FWI67Z | PUJ → ORY | Jul 1, 18:35 UTC | Jul 2, 07:10 UTC | 12h 35m |
| 2026-07-01 | FWI64Y | - | Jul 1, 10:20 UTC | Jul 2, 07:10 UTC | 20h 50m |
| 2026-06-30 | FWI649 | CUN → ORY | Jun 30, 00:39 UTC | Jun 30, 10:00 UTC | 9h 21m |
| 2026-06-29 | FWI648 | ORY → CUN | Jun 29, 10:04 UTC | Jun 29, 20:35 UTC | 10h 30m |
| 2026-06-27 | FWI67Z | PUJ → ORY | Jun 27, 12:19 UTC | Jun 28, 07:40 UTC | 19h 20m |
| 2026-06-27 | FWI64Y | ORY → ORY | Jun 27, 10:50 UTC | Jun 28, 07:40 UTC | 20h 50m |
| 2026-06-26 | FWI60T | - | Jun 26, 01:24 UTC | Jun 26, 09:20 UTC | 7h 55m |
| 2026-06-25 | FWI60T | - | Jun 25, 10:20 UTC | Jun 26, 09:20 UTC | 23h 0m |
| 2026-06-25 | FWI60T | - | Jun 25, 09:40 UTC | Jun 26, 08:15 UTC | 22h 35m |
| 2026-06-24 | FWI67Z | PUJ → ORY | Jun 24, 22:25 UTC | Jun 25, 06:25 UTC | 8h 0m |
| 2026-06-24 | FWI67Z | PUJ → ORY | Jun 24, 10:39 UTC | Jun 25, 06:25 UTC | 19h 45m |
| 2026-06-20 | CAJ1661 | - | Jun 20, 12:54 UTC | Jun 20, 13:29 UTC | 35m |
| 2026-05-12 | CAJ1660 | ORY → BRU | May 12, 07:40 UTC | May 12, 08:25 UTC | 45m |
| 2026-04-23 | FWI17F | FDF → ORY | Apr 23, 08:50 UTC | Apr 24, 04:15 UTC | 19h 24m |
| 2026-04-20 | FWI11B | FDF → ORY | Apr 20, 12:40 UTC | Apr 21, 07:35 UTC | 18h 55m |
| 2026-04-19 | FWI45V | PTP → ORY | Apr 19, 14:20 UTC | Apr 20, 09:50 UTC | 19h 30m |
| 2026-04-19 | FWI87R | ORY → PTP | Apr 19, 14:10 UTC | Apr 20, 09:50 UTC | 19h 40m |
| 2026-04-19 | FWI71K | FDF → ORY | Apr 19, 05:35 UTC | Apr 19, 08:40 UTC | 3h 5m |
| 2026-04-18 | FWI14J | - | Apr 18, 13:45 UTC | Apr 18, 14:55 UTC | 1h 10m |
| 2026-04-17 | FWI67Z | PUJ → ORY | Apr 17, 07:20 UTC | Apr 17, 08:30 UTC | 1h 10m |
| 2026-04-17 | FWI67Z | PUJ → ORY | Apr 17, 06:55 UTC | Apr 17, 07:15 UTC | 20m |
| 2026-04-17 | FWI67Z | PUJ → ORY | Apr 17, 00:30 UTC | Apr 17, 00:55 UTC | 25m |
| 2026-04-16 | FWI64Y | ORY → PUJ | Apr 16, 13:15 UTC | Apr 16, 13:50 UTC | 35m |
| 2026-04-16 | FWI64Y | ORY → PUJ | Apr 16, 12:34 UTC | Apr 16, 13:05 UTC | 30m |
| 2026-04-16 | FWI649 | CUN → ORY | Apr 16, 09:10 UTC | Apr 16, 09:19 UTC | 10m |
| 2026-04-16 | FWI649 | CUN → ORY | Apr 16, 08:15 UTC | Apr 16, 09:05 UTC | 50m |
| 2026-04-15 | FWI649 | CUN → ORY | Apr 15, 23:35 UTC | Apr 16, 01:00 UTC | 1h 25m |
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-HPUJ page for operator, model, and routing details .