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