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