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