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