Back to the log
Aircraft
S5-ICR
Regularnot seen for 6 years
The station's story
Address not received since 20 Dec 2019. The marker states the absence, it does not say why.
- Cumulative contact time
- 88 h
- Distinct days
- 182
- Highest captured altitude
- 41,025 ft
- Discovery rank
- #5,268 of 57,185
- Longest contact
- 1 h 0 min
Same airframe, also seen as
- OY-JRUfrom 27 May 2022 to 30 Jan 2023 · 10 contacts
These registrations share the same serial number and type according to the reference data. Serial numbers can collide, though: it is a deduction, not a certainty.
Visits
| Callsign | Route | First contact | Last contact | Altitude at end of contact | Positions |
|---|---|---|---|---|---|
| S5ICR | route not resolved | 27 Jul 2017, 16:0227 Jul 2017 | 27 Jul 2017, 16:31 | 30,000 ft | no position received |
| S5ICR | route not resolved | 21 Jul 2017, 12:1421 Jul 2017 | 21 Jul 2017, 12:55 | 20,375 ft | no position received |
| S5ICR | route not resolved | 16 Jul 2017, 16:3316 Jul 2017 | 16 Jul 2017, 16:44 | 21,000 ft | no position received |
| S5ICR | route not resolved | 16 Jul 2017, 15:2416 Jul 2017 | 16 Jul 2017, 15:42 | 5,350 ft | no position received |
| S5ICR | route not resolved | 16 Jul 2017, 13:3716 Jul 2017 | 16 Jul 2017, 13:50 | 16,900 ft | no position received |
| S5ICR | route not resolved | 15 Jul 2017, 20:3415 Jul 2017 | 15 Jul 2017, 20:51 | 33,975 ft | no position received |
| S5ICR | route not resolved | 15 Jul 2017, 15:0115 Jul 2017 | 15 Jul 2017, 15:25 | 28,825 ft | no position received |
| S5ICR | route not resolved | 15 Jul 2017, 13:2215 Jul 2017 | 15 Jul 2017, 13:30 | 21,000 ft | no position received |
| S5ICR | route not resolved | 14 Jul 2017, 15:2914 Jul 2017 | 14 Jul 2017, 15:49 | 17,475 ft | no position received |
| S5ICR | route not resolved | 14 Jul 2017, 13:3614 Jul 2017 | 14 Jul 2017, 13:39 | 10,450 ft | no position received |
| S5ICR | route not resolved | 11 Jul 2017, 19:0311 Jul 2017 | 11 Jul 2017, 19:14 | 30,475 ft | no position received |
| S5ICR | route not resolved | 11 Jul 2017, 17:2711 Jul 2017 | 11 Jul 2017, 17:36 | 35,000 ft | no position received |
| S5ICR | route not resolved | 9 Jul 2017, 13:129 Jul 2017 | 9 Jul 2017, 13:30 | 36,500 ft | no position received |
| S5ICR | route not resolved | 1 Jul 2017, 14:421 Jul 2017 | 1 Jul 2017, 14:49 | 37,000 ft | no position received |
| S5ICR | route not resolved | 30 Jun 2017, 17:4130 Jun 2017 | 30 Jun 2017, 17:56 | 39,000 ft | no position received |
| S5ICR | route not resolved | 28 May 2017, 21:0028 May 2017 | 28 May 2017, 21:13 | 33,000 ft | no position received |
| S5ICR | route not resolved | 28 May 2017, 19:0928 May 2017 | 28 May 2017, 19:30 | 12,550 ft | no position received |
| S5ICR | route not resolved | 24 May 2017, 15:0824 May 2017 | 24 May 2017, 15:31 | 39,000 ft | no position received |
| S5ICR | route not resolved | 21 May 2017, 17:4521 May 2017 | 21 May 2017, 18:04 | 33,575 ft | no position received |
| S5ICR | route not resolved | 19 May 2017, 09:4919 May 2017 | 19 May 2017, 10:21 | 39,650 ft | no position received |
| S5ICR | route not resolved | 16 May 2017, 16:0616 May 2017 | 16 May 2017, 16:23 | 11,600 ft | no position received |
| S5ICR | route not resolved | 14 May 2017, 11:0414 May 2017 | 14 May 2017, 11:30 | 38,000 ft | no position received |
| S5ICR | route not resolved | 2 May 2017, 19:392 May 2017 | 2 May 2017, 20:06 | 33,000 ft | no position received |
| S5ICR | route not resolved | 2 May 2017, 08:172 May 2017 | 2 May 2017, 08:50 | 33,100 ft | no position received |
| S5ICR | route not resolved | 6 Mar 2017, 16:406 Mar 2017 | 6 Mar 2017, 17:09 | 35,975 ft | no position received |
