Not currently tracked · last seen 6h ago
- Flights observed
- 131 showing last 50
- Avg flight time
- 1h 43m
- Typical route
- OPO → ORY
- Last seen
- 6h ago
Last known area
Recent flights last 50
| Date | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|
| 2026-07-13 | - | Jul 13, 20:55 UTC | Jul 13, 22:00 UTC | 1h 5m |
| 2026-07-13 | - | Jul 13, 18:30 UTC | Jul 13, 19:20 UTC | 50m |
| 2026-07-13 | CPH → LIS | Jul 13, 04:30 UTC | Jul 13, 08:01 UTC | 3h 30m |
| 2026-07-12 | LIS → CPH | Jul 12, 20:35 UTC | Jul 12, 23:45 UTC | 3h 10m |
| 2026-07-12 | OPO → LIS | Jul 12, 18:10 UTC | Jul 12, 18:45 UTC | 35m |
| 2026-07-12 | LIS → OPO | Jul 12, 15:35 UTC | Jul 12, 16:15 UTC | 40m |
| 2026-07-12 | GVA → LIS | Jul 12, 11:30 UTC | Jul 12, 13:55 UTC | 2h 25m |
| 2026-07-12 | - | Jul 12, 08:05 UTC | Jul 12, 10:05 UTC | 2h 0m |
| 2026-07-12 | - | Jul 12, 04:05 UTC | Jul 12, 06:50 UTC | 2h 45m |
| 2026-07-11 | - | Jul 11, 20:25 UTC | Jul 11, 22:45 UTC | 2h 20m |
| 2026-07-11 | - | Jul 11, 17:20 UTC | Jul 11, 18:25 UTC | 1h 5m |
| 2026-07-11 | LIS → MAD | Jul 11, 15:20 UTC | Jul 11, 16:15 UTC | 55m |
| 2026-07-11 | MXP → LIS | Jul 11, 10:20 UTC | Jul 11, 12:50 UTC | 2h 30m |
| 2026-07-11 | LIS → MXP | Jul 11, 06:50 UTC | Jul 11, 09:05 UTC | 2h 15m |
| 2026-07-10 | VCE → LIS | Jul 10, 17:30 UTC | Jul 10, 20:30 UTC | 3h 0m |
| 2026-07-10 | LIS → VCE | Jul 10, 13:50 UTC | Jul 10, 16:15 UTC | 2h 25m |
| 2026-07-10 | LIS → LIS | Jul 10, 07:10 UTC | Jul 10, 12:10 UTC | 5h 0m |
| 2026-07-10 | BCN → LIS | Jul 10, 04:15 UTC | Jul 10, 05:50 UTC | 1h 35m |
| 2026-07-09 | LIS → BCN | Jul 9, 21:50 UTC | Jul 9, 23:20 UTC | 1h 30m |
| 2026-07-09 | - | Jul 9, 17:50 UTC | Jul 9, 20:25 UTC | 2h 35m |
| 2026-07-09 | - | Jul 9, 13:45 UTC | Jul 9, 16:20 UTC | 2h 35m |
| 2026-07-09 | OPO → LIS | Jul 9, 08:30 UTC | Jul 9, 09:10 UTC | 40m |
| 2026-07-08 | FNC → OPO | Jul 8, 21:45 UTC | Jul 8, 23:25 UTC | 1h 40m |
| 2026-07-08 | - | Jul 8, 20:35 UTC | Jul 8, 20:40 UTC | 5m |
| 2026-07-08 | - | Jul 8, 18:55 UTC | Jul 8, 19:55 UTC | 1h 0m |
| 2026-07-08 | ORY → OPO | Jul 8, 15:30 UTC | Jul 8, 17:15 UTC | 1h 45m |
| 2026-07-08 | OPO → ORY | Jul 8, 12:25 UTC | Jul 8, 14:15 UTC | 1h 50m |
| 2026-07-08 | FNC → OPO | Jul 8, 07:45 UTC | Jul 8, 09:20 UTC | 1h 35m |
| 2026-07-08 | - | Jul 8, 06:35 UTC | Jul 8, 06:45 UTC | 10m |
| 2026-07-08 | - | Jul 8, 04:55 UTC | Jul 8, 05:50 UTC | 55m |
| 2026-07-07 | FNC → OPO | Jul 7, 21:40 UTC | Jul 7, 23:15 UTC | 1h 35m |
| 2026-07-07 | OPO → FNC | Jul 7, 18:50 UTC | Jul 7, 20:35 UTC | 1h 45m |
| 2026-07-07 | - | Jul 7, 15:15 UTC | Jul 7, 17:05 UTC | 1h 50m |
| 2026-07-07 | OPO → ORY | Jul 7, 12:05 UTC | Jul 7, 14:00 UTC | 1h 55m |
| 2026-07-07 | ORY → OPO | Jul 7, 08:10 UTC | Jul 7, 10:05 UTC | 1h 55m |
| 2026-07-07 | OPO → ORY | Jul 7, 05:10 UTC | Jul 7, 07:10 UTC | 2h 0m |
| 2026-07-06 | LGW → OPO | Jul 6, 21:20 UTC | Jul 6, 23:10 UTC | 1h 50m |
| 2026-07-06 | OPO → LGW | Jul 6, 18:20 UTC | Jul 6, 20:10 UTC | 1h 50m |
| 2026-07-06 | ORY → OPO | Jul 6, 15:25 UTC | Jul 6, 17:15 UTC | 1h 50m |
| 2026-07-06 | OPO → ORY | Jul 6, 12:25 UTC | Jul 6, 14:15 UTC | 1h 50m |
| 2026-07-06 | ORY → OPO | Jul 6, 08:10 UTC | Jul 6, 09:50 UTC | 1h 40m |
| 2026-07-06 | OPO → ORY | Jul 6, 05:25 UTC | Jul 6, 07:05 UTC | 1h 40m |
| 2026-07-05 | - | Jul 5, 20:40 UTC | Jul 5, 22:30 UTC | 1h 50m |
| 2026-07-05 | OPO → LGW | Jul 5, 17:30 UTC | Jul 5, 19:20 UTC | 1h 50m |
| 2026-07-05 | - | Jul 5, 14:10 UTC | Jul 5, 16:10 UTC | 2h 0m |
| 2026-07-05 | - | Jul 5, 11:05 UTC | Jul 5, 13:00 UTC | 1h 55m |
| 2026-07-05 | - | Jul 5, 00:00 UTC | Jul 5, 01:00 UTC | 1h 0m |
| 2026-07-04 | FNC → PXO | Jul 4, 23:20 UTC | Jul 4, 23:25 UTC | 5m |
| 2026-07-04 | - | Jul 4, 22:25 UTC | Jul 4, 22:30 UTC | 5m |
| 2026-07-04 | - | Jul 4, 20:40 UTC | Jul 4, 21:40 UTC | 1h 0m |
Specifications
| Registration | CS-TNY |
| Aircraft type | AIRBUS A-320 (A320) |
| Mode-S code | 4951D9 · 22250731 (octal) |
Looking for transponder-level data? View the Mode-S 4951D9 page for country allocation, callsign history, and ADS-B signal details.
CS-TNY frequently asked
What type of aircraft is CS-TNY?
CS-TNY is a AIRBUS A-320 (ICAO type code A320).
What is the Mode-S transponder code for CS-TNY?
CS-TNY broadcasts on Mode-S (ICAO 24-bit) address 4951D9 (octal 22250731). View the transponder page.
What route does CS-TNY typically fly?
CS-TNY most frequently flies between OPO and ORY based on observed flights.
Where is CS-TNY right now?
CS-TNY is not currently being tracked; last seen 6h ago.