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