Back to the log
Aircraft
YU-SAI
Common
The station's story
- Cumulative contact time
- 22 h
- Distinct days
- 38
- Highest captured altitude
- 40,000 ft
- Discovery rank
- #49,909 of 57,181
- Longest contact
- 0 h 47 min
- Contacts on this Mode S address
- 67 contacts on the address, 59 under this registration: the address has carried several identities over time.
Observed callsigns
NAD (42 contacts, 2023-2024)
Operator as per the registry of 12 Aug 2026; observed callsigns are the freshest measurement.
Visits
| Callsign | Route | First contact | Last contact | Altitude at end of contact | Positions |
|---|---|---|---|---|---|
| NAD521 | route not resolved | 10 Mar 2024, 18:3410 Mar 2024 | 10 Mar 2024, 19:10 | 38,000 ft | no position received |
| NAD521 | route not resolved | 10 Mar 2024, 17:0710 Mar 2024 | 10 Mar 2024, 17:44 | 4,650 ft | no position received |
| NAD521 | route not resolved | 7 Mar 2024, 13:427 Mar 2024 | 7 Mar 2024, 14:07 | 36,000 ft | no position received |
| NAD521 | route not resolved | 7 Mar 2024, 12:187 Mar 2024 | 7 Mar 2024, 12:50 | 4,150 ft | no position received |
| NAD521 | route not resolved | 1 Mar 2024, 19:161 Mar 2024 | 1 Mar 2024, 19:40 | 35,000 ft | no position received |
| NAD521 | route not resolved | 29 Feb 2024, 12:4429 Feb 2024 | 29 Feb 2024, 12:52 | 36,000 ft | no position received |
| NAD521 | route not resolved | 26 Feb 2024, 10:1426 Feb 2024 | 26 Feb 2024, 10:16 | 36,000 ft | no position received |
| NAD521 | route not resolved | 12 Feb 2024, 14:1912 Feb 2024 | 12 Feb 2024, 14:42 | 35,000 ft | no position received |
| NAD521 | route not resolved | 9 Feb 2024, 07:539 Feb 2024 | 9 Feb 2024, 08:33 | 36,000 ft | no position received |
| NAD521 | route not resolved | 20 Jan 2024, 20:4320 Jan 2024 | 20 Jan 2024, 20:58 | 36,950 ft | no position received |
| NAD521 | route not resolved | 20 Jan 2024, 16:0620 Jan 2024 | 20 Jan 2024, 16:37 | 35,975 ft | no position received |
| NAD521 | route not resolved | 16 Jan 2024, 16:4216 Jan 2024 | 16 Jan 2024, 17:00 | 32,525 ft | no position received |
| NAD521 | route not resolved | 16 Jan 2024, 15:0416 Jan 2024 | 16 Jan 2024, 15:30 | 6,425 ft | no position received |
| NAD521 | route not resolved | 16 Jan 2024, 10:4416 Jan 2024 | 16 Jan 2024, 10:57 | 35,975 ft | no position received |
| NAD521 | route not resolved | 13 Jan 2024, 14:5013 Jan 2024 | 13 Jan 2024, 15:11 | 28,500 ft | no position received |
| NAD521 | route not resolved | 13 Jan 2024, 11:0513 Jan 2024 | 13 Jan 2024, 11:10 | 35,975 ft | no position received |
| NAD521 | route not resolved | 28 Dec 2023, 18:5428 Dec 2023 | 28 Dec 2023, 19:04 | 24,375 ft | no position received |
| NAD521 | route not resolved | 28 Dec 2023, 17:5028 Dec 2023 | 28 Dec 2023, 18:02 | 5,075 ft | no position received |
| NAD521 | route not resolved | 28 Dec 2023, 13:1028 Dec 2023 | 28 Dec 2023, 13:41 | 34,000 ft | no position received |
| NAD521 | route not resolved | 28 Dec 2023, 10:1428 Dec 2023 | 28 Dec 2023, 10:38 | 6,000 ft | no position received |
| NAD521 | route not resolved | 22 Dec 2023, 20:5222 Dec 2023 | 22 Dec 2023, 20:58 | 35,000 ft | no position received |
| NAD521 | route not resolved | 22 Dec 2023, 16:5222 Dec 2023 | 22 Dec 2023, 16:56 | 34,000 ft | no position received |
| not transmitted | route not resolved | 29 Oct 2023, 13:1129 Oct 2023 | 29 Oct 2023, 13:15 | 35,000 ft | no position received |
| not transmitted | route not resolved | 23 Oct 2023, 13:1623 Oct 2023 | 23 Oct 2023, 13:20 | 33,000 ft | no position received |
| YUSAI | route not resolved | 1 Oct 2023, 18:531 Oct 2023 | 1 Oct 2023, 19:14 | 33,000 ft | no position received |
