Not currently tracked · last seen 2d ago
- Flights observed
- 25
- Avg flight time
- 1h 5m
- Typical route
- -
- Last seen
- 2d ago
Last known area
Recent flights last 25
| Date | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|
| 2026-05-31 | RTM → POZ | May 31, 17:05 UTC | May 31, 18:20 UTC | 1h 15m |
| 2026-05-31 | RNS → RTM | May 31, 14:15 UTC | May 31, 15:20 UTC | 1h 5m |
| 2026-05-31 | VIE → RNS | May 31, 11:25 UTC | May 31, 13:20 UTC | 1h 55m |
| 2026-05-30 | RNS → VIE | May 30, 07:35 UTC | May 30, 09:25 UTC | 1h 50m |
| 2026-05-30 | RTM → RNS | May 30, 05:20 UTC | May 30, 06:20 UTC | 1h 0m |
| 2026-05-29 | POZ → RTM | May 29, 08:15 UTC | May 29, 09:30 UTC | 1h 15m |
| 2026-05-26 | - | May 26, 14:24 UTC | May 26, 15:00 UTC | 35m |
| 2026-05-26 | - | May 26, 11:15 UTC | May 26, 12:50 UTC | 1h 35m |
| 2026-05-18 | POZ → WAW | May 18, 06:01 UTC | May 18, 06:40 UTC | 40m |
| 2026-05-16 | LIN → POZ | May 16, 17:40 UTC | May 16, 18:55 UTC | 1h 15m |
| 2026-05-14 | POZ → LIN | May 14, 08:15 UTC | May 14, 09:45 UTC | 1h 30m |
| 2026-05-13 | - | May 13, 15:40 UTC | May 13, 17:00 UTC | 1h 20m |
| 2026-05-13 | POZ → OSL | May 13, 06:40 UTC | May 13, 07:55 UTC | 1h 15m |
| 2026-05-11 | - | May 11, 11:20 UTC | May 11, 11:45 UTC | 25m |
| 2026-05-11 | - | May 11, 07:25 UTC | May 11, 07:40 UTC | 15m |
| 2026-05-07 | - | May 7, 19:20 UTC | May 7, 19:45 UTC | 25m |
| 2026-05-07 | - | May 7, 10:30 UTC | May 7, 11:15 UTC | 45m |
| 2026-05-07 | POZ → SZZ | May 7, 07:05 UTC | May 7, 07:25 UTC | 20m |
| 2026-05-06 | PRG → POZ | May 6, 17:55 UTC | May 6, 18:25 UTC | 30m |
| 2026-05-06 | POZ → PRG | May 6, 10:15 UTC | May 6, 10:50 UTC | 35m |
| 2026-05-03 | - | May 3, 13:25 UTC | May 3, 16:00 UTC | 2h 35m |
| 2026-04-28 | - | Apr 28, 13:00 UTC | Apr 28, 13:50 UTC | 50m |
| 2026-04-28 | AYT → ATH | Apr 28, 10:35 UTC | Apr 28, 11:40 UTC | 1h 5m |
| 2026-04-25 | - | Apr 25, 08:25 UTC | Apr 25, 11:05 UTC | 2h 40m |
| 2026-04-13 | POZ → POZ | Apr 13, 10:55 UTC | Apr 13, 11:05 UTC | 10m |
Specifications
| Registration | SP-CUD |
| Aircraft type | BOMBARDIER BD-100 Challenger 350 (CL35) |
| Mode-S code | 488A63 · 22105143 (octal) |
Looking for transponder-level data? View the Mode-S 488A63 page for country allocation, callsign history, and ADS-B signal details.
SP-CUD frequently asked
What type of aircraft is SP-CUD?
SP-CUD is a BOMBARDIER BD-100 Challenger 350 (ICAO type code CL35).
What is the Mode-S transponder code for SP-CUD?
SP-CUD broadcasts on Mode-S (ICAO 24-bit) address 488A63 (octal 22105143). View the transponder page.
Where is SP-CUD right now?
SP-CUD is not currently being tracked; last seen 2d ago.