Not currently tracked · last seen 1d ago
- Flights observed
- 53 showing last 50
- Avg flight time
- 8h 31m
- Typical route
- PUJ → ORY
- Last seen
- 1d ago
Last known area
Recent flights last 50
| Date | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|
| 2026-07-11 | - | Jul 11, 23:15 UTC | Jul 12, 07:35 UTC | 8h 20m |
| 2026-07-11 | ORY → ORY | Jul 11, 10:45 UTC | Jul 12, 07:35 UTC | 20h 50m |
| 2026-07-11 | - | Jul 11, 06:05 UTC | Jul 11, 06:30 UTC | 25m |
| 2026-07-10 | ORY → CDG | Jul 10, 16:20 UTC | Jul 11, 00:30 UTC | 8h 10m |
| 2026-07-10 | - | Jul 10, 09:10 UTC | Jul 10, 10:35 UTC | 1h 25m |
| 2026-07-08 | - | Jul 8, 10:10 UTC | Jul 8, 18:35 UTC | 8h 25m |
| 2026-07-07 | CUN → ORY | Jul 7, 00:15 UTC | Jul 7, 10:05 UTC | 9h 50m |
| 2026-07-06 | ORY → CUN | Jul 6, 11:40 UTC | Jul 6, 21:45 UTC | 10h 5m |
| 2026-07-05 | CUN → ORY | Jul 5, 00:45 UTC | Jul 5, 10:25 UTC | 9h 40m |
| 2026-07-04 | ORY → CUN | Jul 4, 12:15 UTC | Jul 4, 22:20 UTC | 10h 5m |
| 2026-07-03 | - | Jul 3, 14:20 UTC | Jul 4, 09:00 UTC | 18h 40m |
| 2026-07-03 | ORY → ORY | Jul 3, 14:10 UTC | Jul 4, 09:00 UTC | 18h 50m |
| 2026-07-03 | - | Jul 3, 01:10 UTC | Jul 3, 09:20 UTC | 8h 10m |
| 2026-07-02 | ORY → ORY | Jul 2, 10:30 UTC | Jul 3, 09:20 UTC | 22h 50m |
| 2026-07-01 | PUJ → ORY | Jul 1, 18:35 UTC | Jul 2, 07:10 UTC | 12h 35m |
| 2026-07-01 | - | Jul 1, 10:20 UTC | Jul 2, 07:10 UTC | 20h 50m |
| 2026-06-30 | CUN → ORY | Jun 30, 00:39 UTC | Jun 30, 10:00 UTC | 9h 21m |
| 2026-06-29 | ORY → CUN | Jun 29, 10:04 UTC | Jun 29, 20:35 UTC | 10h 30m |
| 2026-06-27 | PUJ → ORY | Jun 27, 12:19 UTC | Jun 28, 07:40 UTC | 19h 20m |
| 2026-06-27 | ORY → ORY | Jun 27, 10:50 UTC | Jun 28, 07:40 UTC | 20h 50m |
| 2026-06-26 | - | Jun 26, 01:24 UTC | Jun 26, 09:20 UTC | 7h 55m |
| 2026-06-25 | - | Jun 25, 10:20 UTC | Jun 26, 09:20 UTC | 23h 0m |
| 2026-06-25 | - | Jun 25, 09:40 UTC | Jun 26, 08:15 UTC | 22h 35m |
| 2026-06-24 | PUJ → ORY | Jun 24, 22:25 UTC | Jun 25, 06:25 UTC | 8h 0m |
| 2026-06-24 | PUJ → ORY | Jun 24, 10:39 UTC | Jun 25, 06:25 UTC | 19h 45m |
| 2026-06-20 | - | Jun 20, 12:54 UTC | Jun 20, 13:29 UTC | 35m |
| 2026-05-12 | ORY → BRU | May 12, 07:40 UTC | May 12, 08:25 UTC | 45m |
| 2026-04-23 | FDF → ORY | Apr 23, 08:50 UTC | Apr 24, 04:15 UTC | 19h 24m |
| 2026-04-20 | FDF → ORY | Apr 20, 12:40 UTC | Apr 21, 07:35 UTC | 18h 55m |
| 2026-04-19 | PTP → ORY | Apr 19, 14:20 UTC | Apr 20, 09:50 UTC | 19h 30m |
| 2026-04-19 | ORY → PTP | Apr 19, 14:10 UTC | Apr 20, 09:50 UTC | 19h 40m |
| 2026-04-19 | FDF → ORY | Apr 19, 05:35 UTC | Apr 19, 08:40 UTC | 3h 5m |
| 2026-04-18 | - | Apr 18, 13:45 UTC | Apr 18, 14:55 UTC | 1h 10m |
| 2026-04-17 | PUJ → ORY | Apr 17, 07:20 UTC | Apr 17, 08:30 UTC | 1h 10m |
| 2026-04-17 | PUJ → ORY | Apr 17, 06:55 UTC | Apr 17, 07:15 UTC | 20m |
| 2026-04-17 | PUJ → ORY | Apr 17, 00:30 UTC | Apr 17, 00:55 UTC | 25m |
| 2026-04-16 | ORY → PUJ | Apr 16, 13:15 UTC | Apr 16, 13:50 UTC | 35m |
| 2026-04-16 | ORY → PUJ | Apr 16, 12:34 UTC | Apr 16, 13:05 UTC | 30m |
| 2026-04-16 | CUN → ORY | Apr 16, 09:10 UTC | Apr 16, 09:19 UTC | 10m |
| 2026-04-16 | CUN → ORY | Apr 16, 08:15 UTC | Apr 16, 09:05 UTC | 50m |
| 2026-04-15 | CUN → ORY | Apr 15, 23:35 UTC | Apr 16, 01:00 UTC | 1h 25m |
| 2026-04-15 | ORY → CUN | Apr 15, 19:05 UTC | Apr 15, 20:40 UTC | 1h 35m |
| 2026-04-15 | ORY → CUN | Apr 15, 18:35 UTC | Apr 15, 19:00 UTC | 25m |
| 2026-04-15 | ORY → CUN | Apr 15, 11:00 UTC | Apr 15, 11:45 UTC | 45m |
| 2026-04-15 | ORY → CUN | Apr 15, 10:05 UTC | Apr 15, 10:55 UTC | 50m |
| 2026-04-15 | PUJ → ORY | Apr 15, 05:15 UTC | Apr 15, 06:40 UTC | 1h 25m |
| 2026-04-14 | PUJ → ORY | Apr 14, 22:55 UTC | Apr 14, 23:05 UTC | 10m |
| 2026-04-14 | PUJ → ORY | Apr 14, 22:40 UTC | Apr 14, 22:50 UTC | 10m |
| 2026-04-14 | ORY → PUJ | Apr 14, 10:50 UTC | Apr 14, 11:10 UTC | 20m |
| 2026-04-14 | - | Apr 14, 10:10 UTC | Apr 14, 11:05 UTC | 55m |
Specifications
| Registration | F-HPUJ |
| Aircraft type | AIRBUS A-330-300 (A333) |
| Mode-S code | 39BE89 · 16337211 (octal) |
Looking for transponder-level data? View the Mode-S 39BE89 page for country allocation, callsign history, and ADS-B signal details.
F-HPUJ frequently asked
What type of aircraft is F-HPUJ?
F-HPUJ is a AIRBUS A-330-300 (ICAO type code A333).
What is the Mode-S transponder code for F-HPUJ?
F-HPUJ broadcasts on Mode-S (ICAO 24-bit) address 39BE89 (octal 16337211). View the transponder page.
What route does F-HPUJ typically fly?
F-HPUJ most frequently flies between PUJ and ORY based on observed flights.
Where is F-HPUJ right now?
F-HPUJ is not currently being tracked; last seen 1d ago.