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