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