Not currently tracked · last seen 2h ago
- Flights observed
- 420 showing last 50
- Avg flight time
- 2h 15m
- Typical route
- PRG → AYT
- Last seen
- 2h ago
Last known area
Recent flights last 50
| Date | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|
| 2026-07-13 | - | Jul 13, 21:30 UTC | Jul 14, 00:05 UTC | 2h 35m |
| 2026-07-13 | PRG → BJV | Jul 13, 18:05 UTC | Jul 13, 20:20 UTC | 2h 15m |
| 2026-07-13 | - | Jul 13, 14:05 UTC | Jul 13, 16:55 UTC | 2h 50m |
| 2026-07-13 | PRG → AYT | Jul 13, 10:00 UTC | Jul 13, 12:50 UTC | 2h 50m |
| 2026-07-13 | - | Jul 13, 06:05 UTC | Jul 13, 08:40 UTC | 2h 35m |
| 2026-07-13 | - | Jul 13, 02:15 UTC | Jul 13, 04:40 UTC | 2h 25m |
| 2026-07-12 | KGS → PRG | Jul 12, 21:25 UTC | Jul 12, 23:55 UTC | 2h 30m |
| 2026-07-12 | PRG → KGS | Jul 12, 17:40 UTC | Jul 12, 20:01 UTC | 2h 20m |
| 2026-07-12 | - | Jul 12, 14:05 UTC | Jul 12, 16:15 UTC | 2h 10m |
| 2026-07-12 | - | Jul 12, 11:01 UTC | Jul 12, 12:45 UTC | 1h 45m |
| 2026-07-12 | - | Jul 12, 06:50 UTC | Jul 12, 08:50 UTC | 2h 0m |
| 2026-07-12 | - | Jul 12, 04:01 UTC | Jul 12, 05:40 UTC | 1h 40m |
| 2026-07-11 | - | Jul 11, 20:10 UTC | Jul 11, 22:10 UTC | 2h 0m |
| 2026-07-11 | - | Jul 11, 16:15 UTC | Jul 11, 18:25 UTC | 2h 10m |
| 2026-07-11 | - | Jul 11, 13:20 UTC | Jul 11, 14:40 UTC | 1h 20m |
| 2026-07-11 | PRG → CDG | Jul 11, 10:30 UTC | Jul 11, 11:50 UTC | 1h 20m |
| 2026-07-11 | RHO → PRG | Jul 11, 06:35 UTC | Jul 11, 09:15 UTC | 2h 40m |
| 2026-07-11 | PRG → RHO | Jul 11, 03:05 UTC | Jul 11, 05:35 UTC | 2h 30m |
| 2026-07-10 | TGD → PRG | Jul 10, 19:25 UTC | Jul 10, 20:50 UTC | 1h 25m |
| 2026-07-10 | - | Jul 10, 16:35 UTC | Jul 10, 17:50 UTC | 1h 15m |
| 2026-07-10 | - | Jul 10, 13:20 UTC | Jul 10, 14:35 UTC | 1h 15m |
| 2026-07-10 | - | Jul 10, 10:45 UTC | Jul 10, 12:10 UTC | 1h 25m |
| 2026-07-10 | - | Jul 10, 06:45 UTC | Jul 10, 09:40 UTC | 2h 55m |
| 2026-07-10 | - | Jul 10, 03:00 UTC | Jul 10, 05:35 UTC | 2h 35m |
| 2026-07-09 | - | Jul 9, 20:15 UTC | Jul 9, 22:35 UTC | 2h 20m |
| 2026-07-09 | PRG → VLC | Jul 9, 16:45 UTC | Jul 9, 19:00 UTC | 2h 15m |
| 2026-07-09 | - | Jul 9, 13:20 UTC | Jul 9, 15:15 UTC | 1h 55m |
| 2026-07-09 | - | Jul 9, 10:45 UTC | Jul 9, 12:30 UTC | 1h 45m |
| 2026-07-09 | RHO → PRG | Jul 9, 06:55 UTC | Jul 9, 09:50 UTC | 2h 55m |
| 2026-07-09 | PRG → RHO | Jul 9, 03:30 UTC | Jul 9, 05:55 UTC | 2h 25m |
| 2026-07-08 | RHO → PRG | Jul 8, 20:25 UTC | Jul 8, 23:15 UTC | 2h 50m |
| 2026-07-08 | PRG → RHO | Jul 8, 16:45 UTC | Jul 8, 19:15 UTC | 2h 30m |
| 2026-07-08 | OLB → PRG | Jul 8, 13:40 UTC | Jul 8, 15:25 UTC | 1h 45m |
| 2026-07-08 | PRG → OLB | Jul 8, 10:50 UTC | Jul 8, 12:30 UTC | 1h 40m |
| 2026-07-08 | CHQ → PRG | Jul 8, 07:05 UTC | Jul 8, 09:40 UTC | 2h 35m |
| 2026-07-08 | PRG → CHQ | Jul 8, 03:05 UTC | Jul 8, 05:25 UTC | 2h 20m |
| 2026-07-07 | KGS → PRG | Jul 7, 21:40 UTC | Jul 8, 00:15 UTC | 2h 35m |
| 2026-07-07 | PRG → KGS | Jul 7, 18:10 UTC | Jul 7, 20:30 UTC | 2h 20m |
| 2026-07-07 | - | Jul 7, 13:50 UTC | Jul 7, 16:45 UTC | 2h 55m |
| 2026-07-07 | - | Jul 7, 10:15 UTC | Jul 7, 12:45 UTC | 2h 30m |
| 2026-07-07 | - | Jul 7, 07:10 UTC | Jul 7, 09:05 UTC | 1h 55m |
| 2026-07-07 | - | Jul 7, 04:20 UTC | Jul 7, 06:00 UTC | 1h 40m |
| 2026-07-06 | - | Jul 6, 21:20 UTC | Jul 6, 23:50 UTC | 2h 30m |
| 2026-07-06 | PRG → BJV | Jul 6, 18:05 UTC | Jul 6, 20:15 UTC | 2h 10m |
| 2026-07-06 | - | Jul 6, 14:05 UTC | Jul 6, 17:00 UTC | 2h 55m |
| 2026-07-06 | - | Jul 6, 10:15 UTC | Jul 6, 12:45 UTC | 2h 30m |
| 2026-07-06 | DLM → PRG | Jul 6, 06:10 UTC | Jul 6, 08:50 UTC | 2h 40m |
| 2026-07-06 | PRG → AYT | Jul 6, 02:10 UTC | Jul 6, 04:30 UTC | 2h 20m |
| 2026-07-05 | - | Jul 5, 21:00 UTC | Jul 5, 23:50 UTC | 2h 50m |
| 2026-07-05 | PRG → AYT | Jul 5, 17:15 UTC | Jul 5, 19:50 UTC | 2h 35m |
Specifications
| Registration | OK-FYC |
| Aircraft type | AIRBUS A220-300 (BCS3) |
| Mode-S code | 49D5EF · 22352757 (octal) |
Looking for transponder-level data? View the Mode-S 49D5EF page for country allocation, callsign history, and ADS-B signal details.
OK-FYC frequently asked
What type of aircraft is OK-FYC?
OK-FYC is a AIRBUS A220-300 (ICAO type code BCS3).
What is the Mode-S transponder code for OK-FYC?
OK-FYC broadcasts on Mode-S (ICAO 24-bit) address 49D5EF (octal 22352757). View the transponder page.
What route does OK-FYC typically fly?
OK-FYC most frequently flies between PRG and AYT based on observed flights.
Where is OK-FYC right now?
OK-FYC is not currently being tracked; last seen 2h ago.