Not currently tracked · last seen 1h ago
- Flights observed
- 126 showing last 50
- Avg flight time
- 14h 3m
- Typical route
- ORY → ORY
- Last seen
- 1h ago
Last known area
Recent flights last 50
| Date | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|
| 2026-07-14 | - | Jul 14, 09:10 UTC | Jul 14, 10:30 UTC | 1h 20m |
| 2026-07-14 | - | Jul 14, 03:05 UTC | Jul 14, 04:25 UTC | 1h 20m |
| 2026-07-13 | - | Jul 13, 08:35 UTC | Jul 13, 09:40 UTC | 1h 5m |
| 2026-07-12 | - | Jul 12, 03:40 UTC | Jul 12, 12:15 UTC | 8h 35m |
| 2026-07-11 | ORY → MIA | Jul 11, 15:45 UTC | Jul 12, 00:30 UTC | 8h 45m |
| 2026-07-11 | - | Jul 11, 03:01 UTC | Jul 11, 04:25 UTC | 1h 25m |
| 2026-07-09 | - | Jul 9, 10:25 UTC | Jul 10, 00:50 UTC | 14h 25m |
| 2026-07-08 | ORY → ORY | Jul 8, 11:30 UTC | Jul 9, 06:15 UTC | 18h 45m |
| 2026-07-08 | - | Jul 8, 04:30 UTC | Jul 8, 06:35 UTC | 2h 5m |
| 2026-07-07 | - | Jul 7, 11:50 UTC | Jul 8, 04:15 UTC | 16h 25m |
| 2026-07-05 | - | Jul 5, 13:20 UTC | Jul 6, 07:20 UTC | 18h 0m |
| 2026-07-05 | ORY → ORY | Jul 5, 12:40 UTC | Jul 6, 07:20 UTC | 18h 40m |
| 2026-07-04 | PUJ → ORY | Jul 4, 13:45 UTC | Jul 5, 09:05 UTC | 19h 20m |
| 2026-07-03 | - | Jul 3, 15:20 UTC | Jul 4, 09:40 UTC | 18h 20m |
| 2026-07-03 | ORY → ORY | Jul 3, 15:10 UTC | Jul 4, 09:40 UTC | 18h 30m |
| 2026-07-02 | OAK → ORY | Jul 2, 23:35 UTC | Jul 3, 09:30 UTC | 9h 55m |
| 2026-07-02 | ORY → SFO | Jul 2, 09:55 UTC | Jul 2, 20:45 UTC | 10h 50m |
| 2026-06-30 | - | Jun 30, 11:20 UTC | Jul 1, 05:55 UTC | 18h 35m |
| 2026-06-30 | ORY → ORY | Jun 30, 10:50 UTC | Jul 1, 05:55 UTC | 19h 5m |
| 2026-06-28 | ORY → ORY | Jun 28, 11:50 UTC | Jun 29, 07:15 UTC | 19h 25m |
| 2026-06-27 | ORY → ORY | Jun 27, 11:59 UTC | Jun 28, 07:05 UTC | 19h 5m |
| 2026-06-26 | - | Jun 26, 09:20 UTC | Jun 27, 04:09 UTC | 18h 50m |
| 2026-06-26 | ORY → ORY | Jun 26, 08:45 UTC | Jun 27, 04:09 UTC | 19h 25m |
| 2026-06-25 | EWR → ORY | Jun 25, 03:54 UTC | Jun 25, 10:20 UTC | 6h 25m |
| 2026-06-24 | ORY → EWR | Jun 24, 17:34 UTC | Jun 25, 01:19 UTC | 7h 45m |
| 2026-06-23 | ORY → ORY | Jun 23, 11:54 UTC | Jun 24, 06:45 UTC | 18h 50m |
| 2026-06-20 | PUJ → ORY | Jun 20, 11:20 UTC | Jun 21, 06:19 UTC | 19h 0m |
| 2026-06-20 | PUJ → ORY | Jun 20, 10:20 UTC | Jun 21, 06:19 UTC | 20h 0m |
| 2026-06-19 | ORY → ORY | Jun 19, 12:25 UTC | Jun 20, 07:14 UTC | 18h 50m |
| 2026-06-18 | SFO → ORY | Jun 18, 23:25 UTC | Jun 19, 09:40 UTC | 10h 14m |
| 2026-06-18 | ORY → SFO | Jun 18, 09:50 UTC | Jun 18, 20:25 UTC | 10h 35m |
| 2026-06-17 | PUJ → ORY | Jun 17, 11:20 UTC | Jun 18, 06:15 UTC | 18h 55m |
| 2026-06-17 | ORY → ORY | Jun 17, 10:15 UTC | Jun 18, 06:15 UTC | 20h 0m |
| 2026-06-16 | ORY → ORY | Jun 16, 11:35 UTC | Jun 17, 06:40 UTC | 19h 6m |
| 2026-06-15 | - | Jun 15, 22:35 UTC | Jun 16, 06:15 UTC | 7h 40m |
| 2026-06-13 | ORY → PUJ | Jun 13, 10:45 UTC | Jun 13, 18:55 UTC | 8h 10m |
| 2026-06-12 | ORY → ORY | Jun 12, 11:25 UTC | Jun 13, 06:45 UTC | 19h 19m |
| 2026-06-12 | SDQ → ORY | Jun 12, 05:15 UTC | Jun 12, 06:50 UTC | 1h 35m |
| 2026-06-11 | SDQ → ORY | Jun 11, 08:20 UTC | Jun 12, 06:50 UTC | 22h 31m |
| 2026-06-09 | FDF → ORY | Jun 9, 11:20 UTC | Jun 10, 05:30 UTC | 18h 10m |
| 2026-06-09 | ORY → FDF | Jun 9, 10:40 UTC | Jun 10, 05:30 UTC | 18h 50m |
| 2026-06-06 | PUJ → ORY | Jun 6, 11:19 UTC | Jun 7, 05:40 UTC | 18h 20m |
| 2026-06-06 | ORY → PUJ | Jun 6, 10:20 UTC | Jun 7, 05:40 UTC | 19h 20m |
| 2026-06-04 | ORY → CAY | Jun 4, 14:25 UTC | Jun 5, 09:10 UTC | 18h 45m |
| 2026-06-03 | PUJ → ORY | Jun 3, 11:20 UTC | Jun 4, 05:55 UTC | 18h 35m |
| 2026-06-03 | ORY → PUJ | Jun 3, 10:20 UTC | Jun 4, 05:55 UTC | 19h 35m |
| 2026-06-02 | ORY → FDF | Jun 2, 12:25 UTC | Jun 3, 07:05 UTC | 18h 40m |
| 2026-05-31 | CUN → ORY | May 31, 00:00 UTC | May 31, 00:45 UTC | 45m |
| 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 |
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 ORY and ORY based on observed flights.
Where is F-HHAV right now?
F-HHAV is not currently being tracked; last seen 1h ago.