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