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