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