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