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