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