Not currently tracked · last seen 17h ago
- Flights observed
- 79 showing last 50
- Avg flight time
- 13h 58m
- Typical route
- REC → MAD
- Last seen
- 17h ago
Last known area
Recent flights last 50
| Date | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|
| 2026-05-29 | MAD → REC | May 29, 09:55 UTC | May 29, 12:00 UTC | 2h 5m |
| 2026-05-28 | REC → MAD | May 28, 11:20 UTC | May 29, 06:45 UTC | 19h 25m |
| 2026-05-28 | REC → MAD | May 28, 10:30 UTC | May 29, 06:45 UTC | 20h 15m |
| 2026-05-28 | REC → OPO | May 28, 06:00 UTC | May 28, 08:10 UTC | 2h 10m |
| 2026-05-27 | REC → OPO | May 27, 11:20 UTC | May 28, 08:10 UTC | 20h 50m |
| 2026-05-27 | MAD → REC | May 27, 09:25 UTC | May 28, 08:10 UTC | 22h 45m |
| 2026-05-27 | REC → MAD | May 27, 04:04 UTC | May 27, 06:15 UTC | 2h 10m |
| 2026-05-25 | MAD → REC | May 25, 09:35 UTC | May 25, 11:50 UTC | 2h 15m |
| 2026-05-24 | REC → MAD | May 24, 11:45 UTC | May 25, 06:20 UTC | 18h 35m |
| 2026-05-24 | OPO → REC | May 24, 10:25 UTC | May 25, 06:20 UTC | 19h 55m |
| 2026-05-22 | REC → OPO | May 22, 11:20 UTC | May 23, 07:15 UTC | 19h 55m |
| 2026-05-22 | MAD → REC | May 22, 10:45 UTC | May 23, 07:15 UTC | 20h 29m |
| 2026-05-21 | REC → MAD | May 21, 11:20 UTC | May 22, 06:55 UTC | 19h 35m |
| 2026-05-20 | REC → OPO | May 20, 11:35 UTC | May 21, 06:55 UTC | 19h 20m |
| 2026-05-20 | MAD → REC | May 20, 09:55 UTC | May 21, 06:55 UTC | 21h 0m |
| 2026-05-20 | REC → MAD | May 20, 04:10 UTC | May 20, 06:20 UTC | 2h 11m |
| 2026-05-18 | MAD → REC | May 18, 10:50 UTC | May 18, 12:50 UTC | 2h 0m |
| 2026-05-17 | REC → MAD | May 17, 11:25 UTC | May 18, 06:25 UTC | 19h 0m |
| 2026-05-17 | REC → MAD | May 17, 10:00 UTC | May 18, 06:25 UTC | 20h 25m |
| 2026-05-16 | REC → OPO | May 16, 05:15 UTC | May 16, 07:16 UTC | 2h 1m |
| 2026-05-14 | OPO → REC | May 14, 10:20 UTC | May 14, 12:25 UTC | 2h 5m |
| 2026-05-14 | REC → OPO | May 14, 05:50 UTC | May 14, 07:35 UTC | 1h 45m |
| 2026-05-13 | REC → OPO | May 13, 11:20 UTC | May 14, 07:35 UTC | 20h 15m |
| 2026-05-13 | MAD → REC | May 13, 09:20 UTC | May 14, 07:35 UTC | 22h 15m |
| 2026-05-13 | REC → MAD | May 13, 03:50 UTC | May 13, 05:45 UTC | 1h 55m |
| 2026-05-11 | MAD → REC | May 11, 09:25 UTC | May 11, 12:05 UTC | 2h 40m |
| 2026-05-10 | REC → MAD | May 10, 11:30 UTC | May 11, 06:15 UTC | 18h 45m |
| 2026-05-10 | OPO → REC | May 10, 10:24 UTC | May 11, 06:15 UTC | 19h 50m |
| 2026-05-09 | REC → OPO | May 9, 05:20 UTC | May 9, 07:20 UTC | 2h 0m |
| 2026-05-08 | REC → OPO | May 8, 12:00 UTC | May 9, 07:20 UTC | 19h 20m |
| 2026-05-08 | MAD → REC | May 8, 09:59 UTC | May 9, 07:20 UTC | 21h 20m |
| 2026-05-07 | REC → MAD | May 7, 11:45 UTC | May 8, 06:30 UTC | 18h 45m |
| 2026-05-07 | OPO → REC | May 7, 10:15 UTC | May 8, 06:30 UTC | 20h 15m |
| 2026-05-06 | MAD → REC | May 6, 12:10 UTC | May 7, 07:10 UTC | 18h 59m |
| 2026-05-06 | REC → MAD | May 6, 04:05 UTC | May 6, 06:15 UTC | 2h 10m |
| 2026-05-04 | MAD → REC | May 4, 10:35 UTC | May 4, 12:55 UTC | 2h 20m |
| 2026-05-03 | REC → MAD | May 3, 11:25 UTC | May 4, 06:15 UTC | 18h 50m |
| 2026-05-03 | OPO → REC | May 3, 10:20 UTC | May 4, 06:15 UTC | 19h 55m |
| 2026-05-01 | REC → OPO | May 1, 13:20 UTC | May 2, 08:00 UTC | 18h 40m |
| 2026-05-01 | REC → OPO | May 1, 11:20 UTC | May 2, 08:00 UTC | 20h 40m |
| 2026-05-01 | MAD → REC | May 1, 11:10 UTC | May 2, 08:00 UTC | 20h 50m |
| 2026-04-30 | REC → MAD | Apr 30, 11:55 UTC | May 1, 07:15 UTC | 19h 20m |
| 2026-04-30 | OPO → REC | Apr 30, 10:30 UTC | May 1, 07:15 UTC | 20h 45m |
| 2026-04-30 | REC → OPO | Apr 30, 05:30 UTC | Apr 30, 07:45 UTC | 2h 15m |
| 2026-04-29 | REC → OPO | Apr 29, 11:55 UTC | Apr 30, 07:45 UTC | 19h 49m |
| 2026-04-29 | REC → OPO | Apr 29, 10:00 UTC | Apr 30, 07:45 UTC | 21h 44m |
| 2026-04-29 | REC → MAD | Apr 29, 04:49 UTC | Apr 29, 07:05 UTC | 2h 15m |
| 2026-04-27 | MAD → REC | Apr 27, 09:55 UTC | Apr 27, 12:10 UTC | 2h 15m |
| 2026-04-26 | REC → MAD | Apr 26, 11:20 UTC | Apr 27, 06:55 UTC | 19h 35m |
| 2026-04-26 | OPO → REC | Apr 26, 10:10 UTC | Apr 27, 06:55 UTC | 20h 45m |
Specifications
| Registration | CS-TSU |
| Aircraft type | BOEING 767-300 (B763) |
| Mode-S code | 495275 · 22251165 (octal) |
Looking for transponder-level data? View the Mode-S 495275 page for country allocation, callsign history, and ADS-B signal details.
CS-TSU frequently asked
What type of aircraft is CS-TSU?
CS-TSU is a BOEING 767-300 (ICAO type code B763).
What is the Mode-S transponder code for CS-TSU?
CS-TSU broadcasts on Mode-S (ICAO 24-bit) address 495275 (octal 22251165). View the transponder page.
What route does CS-TSU typically fly?
CS-TSU most frequently flies between REC and MAD based on observed flights.
Where is CS-TSU right now?
CS-TSU is not currently being tracked; last seen 17h ago.