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