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