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