Not currently tracked · last seen 1h ago
- Flights observed
- 207 showing last 50
- Avg flight time
- 2h 30m
- Typical route
- ORY → ORY
- Last seen
- 1h ago
Last known area
Recent flights last 50
| Date | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|
| 2026-06-02 | - | Jun 2, 19:10 UTC | Jun 2, 20:30 UTC | 1h 20m |
| 2026-06-02 | ORY → SVQ | Jun 2, 16:05 UTC | Jun 2, 18:00 UTC | 1h 55m |
| 2026-06-02 | MLA → ORY | Jun 2, 11:00 UTC | Jun 2, 13:30 UTC | 2h 30m |
| 2026-06-02 | ORY → MLA | Jun 2, 07:35 UTC | Jun 2, 10:00 UTC | 2h 25m |
| 2026-06-02 | PRG → ORY | Jun 2, 04:50 UTC | Jun 2, 06:15 UTC | 1h 25m |
| 2026-06-01 | ORY → PRG | Jun 1, 18:40 UTC | Jun 1, 20:00 UTC | 1h 20m |
| 2026-06-01 | CAI → ORY | Jun 1, 13:00 UTC | Jun 1, 17:20 UTC | 4h 20m |
| 2026-06-01 | - | Jun 1, 07:15 UTC | Jun 1, 10:35 UTC | 3h 20m |
| 2026-06-01 | BCN → ORY | Jun 1, 04:25 UTC | Jun 1, 05:50 UTC | 1h 25m |
| 2026-05-31 | ORY → BCN | May 31, 19:25 UTC | May 31, 20:35 UTC | 1h 10m |
| 2026-05-31 | RBA → ORY | May 31, 14:55 UTC | May 31, 17:35 UTC | 2h 40m |
| 2026-05-31 | ORY → RBA | May 31, 11:35 UTC | May 31, 13:50 UTC | 2h 15m |
| 2026-05-30 | ORY → MIR | May 30, 19:35 UTC | May 30, 21:15 UTC | 1h 40m |
| 2026-05-30 | ORY → ATH | May 30, 16:25 UTC | May 30, 18:25 UTC | 2h 0m |
| 2026-05-30 | ORY → DBV | May 30, 13:35 UTC | May 30, 15:30 UTC | 1h 55m |
| 2026-05-30 | CTA → ORY | May 30, 09:20 UTC | May 30, 11:35 UTC | 2h 15m |
| 2026-05-30 | ORY → CTA | May 30, 05:45 UTC | May 30, 07:55 UTC | 2h 10m |
| 2026-05-29 | OPO → ORY | May 29, 18:10 UTC | May 29, 20:00 UTC | 1h 50m |
| 2026-05-29 | - | May 29, 15:20 UTC | May 29, 16:45 UTC | 1h 25m |
| 2026-05-29 | OPO → BES | May 29, 12:55 UTC | May 29, 14:10 UTC | 1h 15m |
| 2026-05-29 | ORY → OPO | May 29, 10:05 UTC | May 29, 11:55 UTC | 1h 50m |
| 2026-05-29 | AGA → ORY | May 29, 05:30 UTC | May 29, 08:25 UTC | 2h 55m |
| 2026-05-28 | - | May 28, 18:20 UTC | May 28, 21:05 UTC | 2h 45m |
| 2026-05-28 | - | May 28, 15:10 UTC | May 28, 16:40 UTC | 1h 30m |
| 2026-05-28 | ORY → PMI | May 28, 12:20 UTC | May 28, 13:50 UTC | 1h 30m |
| 2026-05-28 | VIE → ORY | May 28, 08:55 UTC | May 28, 10:35 UTC | 1h 40m |
| 2026-05-28 | ORY → VIE | May 28, 06:05 UTC | May 28, 07:35 UTC | 1h 30m |
| 2026-05-27 | - | May 27, 16:40 UTC | May 27, 19:50 UTC | 3h 10m |
| 2026-05-27 | - | May 27, 12:30 UTC | May 27, 15:35 UTC | 3h 5m |
| 2026-05-27 | LIS → ORY | May 27, 09:15 UTC | May 27, 11:10 UTC | 1h 55m |
| 2026-05-27 | ORY → LIS | May 27, 05:29 UTC | May 27, 07:40 UTC | 2h 10m |
| 2026-05-26 | OUD → ORY | May 26, 17:55 UTC | May 26, 20:15 UTC | 2h 20m |
| 2026-05-26 | ORY → OUD | May 26, 14:20 UTC | May 26, 16:45 UTC | 2h 25m |
| 2026-05-26 | ORY → ORY | May 26, 05:00 UTC | May 26, 12:10 UTC | 7h 10m |
| 2026-05-25 | ORY → ORY | May 25, 12:50 UTC | May 25, 20:04 UTC | 7h 14m |
| 2026-05-24 | ORY → ORY | May 24, 18:25 UTC | May 25, 08:15 UTC | 13h 50m |
| 2026-05-24 | ARN → ORY | May 24, 14:10 UTC | May 24, 16:25 UTC | 2h 15m |
| 2026-05-24 | ORY → ARN | May 24, 10:45 UTC | May 24, 13:00 UTC | 2h 15m |
| 2026-05-24 | - | May 24, 07:35 UTC | May 24, 09:35 UTC | 2h 0m |
| 2026-05-24 | - | May 24, 04:15 UTC | May 24, 06:15 UTC | 2h 0m |
| 2026-05-23 | SVQ → ORY | May 23, 18:50 UTC | May 23, 20:45 UTC | 1h 55m |
| 2026-05-23 | ORY → SVQ | May 23, 15:10 UTC | May 23, 17:10 UTC | 2h 0m |
| 2026-05-23 | BDS → ORY | May 23, 11:05 UTC | May 23, 13:15 UTC | 2h 10m |
| 2026-05-23 | ORY → BDS | May 23, 07:40 UTC | May 23, 09:45 UTC | 2h 5m |
| 2026-05-23 | - | May 23, 04:50 UTC | May 23, 06:35 UTC | 1h 45m |
| 2026-05-22 | ORY → FCO | May 22, 20:00 UTC | May 22, 21:50 UTC | 1h 50m |
| 2026-05-22 | FCO → ORY | May 22, 17:10 UTC | May 22, 18:50 UTC | 1h 40m |
| 2026-05-22 | ORY → FCO | May 22, 14:10 UTC | May 22, 15:55 UTC | 1h 45m |
| 2026-05-22 | - | May 22, 11:05 UTC | May 22, 12:45 UTC | 1h 40m |
| 2026-05-22 | ORY → FCO | May 22, 07:40 UTC | May 22, 09:30 UTC | 1h 50m |
Specifications
| Registration | F-HXSC |
| Aircraft type | AIRBUS A-320neo (A20N) |
| Mode-S code | 39DE42 · 16357102 (octal) |
Looking for transponder-level data? View the Mode-S 39DE42 page for country allocation, callsign history, and ADS-B signal details.
F-HXSC frequently asked
What type of aircraft is F-HXSC?
F-HXSC is a AIRBUS A-320neo (ICAO type code A20N).
What is the Mode-S transponder code for F-HXSC?
F-HXSC broadcasts on Mode-S (ICAO 24-bit) address 39DE42 (octal 16357102). View the transponder page.
What route does F-HXSC typically fly?
F-HXSC most frequently flies between ORY and ORY based on observed flights.
Where is F-HXSC right now?
F-HXSC is not currently being tracked; last seen 1h ago.