Not currently tracked · last seen 7h ago
- Flights observed
- 428 showing last 50
- Avg flight time
- 2h 46m
- Typical route
- ORY → ORY
- Last seen
- 7h ago
Last known area
Recent flights last 50
| Date | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|
| 2026-07-13 | - | Jul 13, 18:15 UTC | Jul 13, 20:50 UTC | 2h 35m |
| 2026-07-13 | ORY → DJE | Jul 13, 14:25 UTC | Jul 13, 16:50 UTC | 2h 25m |
| 2026-07-13 | - | Jul 13, 09:40 UTC | Jul 13, 13:00 UTC | 3h 20m |
| 2026-07-13 | ORY → CHQ | Jul 13, 05:31 UTC | Jul 13, 08:30 UTC | 3h 0m |
| 2026-07-12 | - | Jul 12, 15:35 UTC | Jul 12, 18:20 UTC | 2h 45m |
| 2026-07-12 | ORY → ZTH | Jul 12, 11:40 UTC | Jul 12, 14:10 UTC | 2h 30m |
| 2026-07-12 | - | Jul 12, 08:05 UTC | Jul 12, 10:20 UTC | 2h 15m |
| 2026-07-12 | - | Jul 12, 04:25 UTC | Jul 12, 06:30 UTC | 2h 5m |
| 2026-07-11 | ORY → ORY | Jul 11, 14:00 UTC | Jul 11, 20:40 UTC | 6h 40m |
| 2026-07-11 | ATH → ORY | Jul 11, 09:40 UTC | Jul 11, 12:40 UTC | 3h 0m |
| 2026-07-11 | ORY → ATH | Jul 11, 05:35 UTC | Jul 11, 08:25 UTC | 2h 50m |
| 2026-07-10 | OPO → ORY | Jul 10, 18:05 UTC | Jul 10, 19:50 UTC | 1h 45m |
| 2026-07-10 | BES → OPO | Jul 10, 15:35 UTC | Jul 10, 16:55 UTC | 1h 20m |
| 2026-07-10 | OPO → BES | Jul 10, 13:15 UTC | Jul 10, 14:35 UTC | 1h 20m |
| 2026-07-10 | ORY → OPO | Jul 10, 10:10 UTC | Jul 10, 12:05 UTC | 1h 55m |
| 2026-07-10 | - | Jul 10, 05:30 UTC | Jul 10, 08:05 UTC | 2h 35m |
| 2026-07-09 | - | Jul 9, 18:20 UTC | Jul 9, 21:20 UTC | 3h 0m |
| 2026-07-09 | - | Jul 9, 15:15 UTC | Jul 9, 16:45 UTC | 1h 30m |
| 2026-07-09 | - | Jul 9, 12:35 UTC | Jul 9, 14:05 UTC | 1h 30m |
| 2026-07-09 | - | Jul 9, 08:55 UTC | Jul 9, 11:00 UTC | 2h 5m |
| 2026-07-09 | - | Jul 9, 05:35 UTC | Jul 9, 07:25 UTC | 1h 50m |
| 2026-07-08 | - | Jul 8, 20:00 UTC | Jul 8, 21:25 UTC | 1h 25m |
| 2026-07-08 | - | Jul 8, 17:30 UTC | Jul 8, 18:50 UTC | 1h 20m |
| 2026-07-08 | RHO → ORY | Jul 8, 12:00 UTC | Jul 8, 15:30 UTC | 3h 30m |
| 2026-07-08 | ORY → RHO | Jul 8, 07:05 UTC | Jul 8, 10:15 UTC | 3h 10m |
| 2026-07-07 | - | Jul 7, 17:45 UTC | Jul 7, 20:15 UTC | 2h 30m |
| 2026-07-07 | - | Jul 7, 14:10 UTC | Jul 7, 16:15 UTC | 2h 5m |
| 2026-07-07 | FNC → ORY | Jul 7, 09:15 UTC | Jul 7, 12:10 UTC | 2h 55m |
| 2026-07-07 | ORY → ATH | Jul 7, 05:10 UTC | Jul 7, 07:50 UTC | 2h 40m |
| 2026-07-06 | - | Jul 6, 19:00 UTC | Jul 6, 20:55 UTC | 1h 55m |
| 2026-07-06 | - | Jul 6, 16:00 UTC | Jul 6, 17:35 UTC | 1h 35m |
| 2026-07-06 | - | Jul 6, 12:00 UTC | Jul 6, 14:25 UTC | 2h 25m |
| 2026-07-06 | ORY → TNG | Jul 6, 08:30 UTC | Jul 6, 10:40 UTC | 2h 10m |
| 2026-07-06 | ARN → ORY | Jul 6, 05:00 UTC | Jul 6, 07:15 UTC | 2h 15m |
| 2026-07-05 | ORY → ARN | Jul 5, 20:00 UTC | Jul 5, 22:10 UTC | 2h 10m |
| 2026-07-05 | ATH → ORY | Jul 5, 15:45 UTC | Jul 5, 18:45 UTC | 3h 0m |
| 2026-07-05 | ORY → ATH | Jul 5, 11:35 UTC | Jul 5, 14:20 UTC | 2h 45m |
| 2026-07-04 | ORY → ORY | Jul 4, 18:25 UTC | Jul 5, 08:15 UTC | 13h 50m |
| 2026-07-04 | - | Jul 4, 13:30 UTC | Jul 4, 16:50 UTC | 3h 20m |
| 2026-07-04 | - | Jul 4, 08:55 UTC | Jul 4, 11:45 UTC | 2h 50m |
| 2026-07-04 | - | Jul 4, 04:10 UTC | Jul 4, 07:25 UTC | 3h 15m |
| 2026-07-03 | - | Jul 3, 17:40 UTC | Jul 3, 20:30 UTC | 2h 50m |
| 2026-07-03 | BCN → ORY | Jul 3, 14:40 UTC | Jul 3, 16:05 UTC | 1h 25m |
| 2026-07-03 | ORY → BCN | Jul 3, 12:00 UTC | Jul 3, 13:15 UTC | 1h 15m |
| 2026-07-03 | ORY → ORY | Jul 3, 05:05 UTC | Jul 3, 10:25 UTC | 5h 20m |
| 2026-07-02 | ORY → ORY | Jul 2, 12:55 UTC | Jul 2, 19:35 UTC | 6h 40m |
| 2026-07-02 | - | Jul 2, 09:30 UTC | Jul 2, 11:35 UTC | 2h 5m |
| 2026-07-02 | - | Jul 2, 05:40 UTC | Jul 2, 07:35 UTC | 1h 55m |
| 2026-07-01 | - | Jul 1, 18:40 UTC | Jul 1, 20:40 UTC | 2h 0m |
| 2026-07-01 | - | Jul 1, 15:55 UTC | Jul 1, 17:25 UTC | 1h 30m |
Specifications
| Registration | F-HXSI |
| Aircraft type | AIRBUS A-320neo (A20N) |
| Mode-S code | 39DE48 · 16357110 (octal) |
Looking for transponder-level data? View the Mode-S 39DE48 page for country allocation, callsign history, and ADS-B signal details.
F-HXSI frequently asked
What type of aircraft is F-HXSI?
F-HXSI is a AIRBUS A-320neo (ICAO type code A20N).
What is the Mode-S transponder code for F-HXSI?
F-HXSI broadcasts on Mode-S (ICAO 24-bit) address 39DE48 (octal 16357110). View the transponder page.
What route does F-HXSI typically fly?
F-HXSI most frequently flies between ORY and ORY based on observed flights.
Where is F-HXSI right now?
F-HXSI is not currently being tracked; last seen 7h ago.