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