Back to the log
Aircraft
LN-RTG
Regularnot seen for 9 years
The station's story
Address not received since 14 May 2017. The marker states the absence, it does not say why.
- Cumulative contact time
- 10 h
- Distinct days
- 16
- Highest captured altitude
- 43,000 ft
- Discovery rank
- #12,307 of 57,065
- Longest contact
- 1 h 11 min
Same airframe, also seen as
- N716GCfrom 1 Jun 2018 to 2 Jun 2026 · 16 contacts
- VT-AROfrom 23 Jun 2019 to 31 Aug 2019 · 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.
Observed callsigns
RTG (20 contacts, 2016-2017)
Operator as per the registry of 21.07.2026; observed callsigns are the freshest measurement.
Visits
| Callsign | Route | First contact | Last contact | Altitude at end of contact | Positions |
|---|---|---|---|---|---|
| RTG3125 | route not resolved | 14 May 2017, 12:4514 May 2017 | 14 May 2017, 13:57 | 40,000 ft | 2,444 |
| RTG3125 | route not resolved | 12 May 2017, 11:4112 May 2017 | 12 May 2017, 11:48 | 1,575 ft | no position received |
| not transmitted | route not resolved | 12 May 2017, 10:3912 May 2017 | 12 May 2017, 10:47 | not transmitted | no position received |
| RTG3125 | route not resolved | 11 May 2017, 14:4711 May 2017 | 11 May 2017, 15:14 | 1,775 ft | no position received |
| RTG3125 | route not resolved | 11 May 2017, 10:0011 May 2017 | 11 May 2017, 10:20 | 1,700 ft | 1 |
| RTG3125 | route not resolved | 11 May 2017, 08:5611 May 2017 | 11 May 2017, 08:57 | 1,675 ft | no position received |
| RTG3125 | route not resolved | 8 May 2017, 09:438 May 2017 | 8 May 2017, 10:33 | 1,225 ft | 2,728 |
| RTG3119 | route not resolved | 28 Mar 2017, 15:0128 Mar 2017 | 28 Mar 2017, 15:10 | 32,450 ft | 319 |
| RTG3118 | route not resolved | 28 Mar 2017, 13:3728 Mar 2017 | 28 Mar 2017, 14:11 | 16,475 ft | 788 |
| RTG3102 | route not resolved | 1 Mar 2017, 11:291 Mar 2017 | 1 Mar 2017, 11:54 | 40,000 ft | 1,401 |
| RTG3114 | route not resolved | 1 Mar 2017, 09:311 Mar 2017 | 1 Mar 2017, 09:55 | 11,925 ft | 145 |
| RTG3108 | route not resolved | 26 Feb 2017, 11:0926 Feb 2017 | 26 Feb 2017, 11:42 | 43,000 ft | 1,743 |
| RTG3102 | route not resolved | 26 Feb 2017, 09:3526 Feb 2017 | 26 Feb 2017, 10:09 | 18,875 ft | 1,537 |
| RTG3105 | route not resolved | 25 Feb 2017, 16:2425 Feb 2017 | 25 Feb 2017, 16:27 | 40,000 ft | 8 |
| RTG3106 | route not resolved | 25 Feb 2017, 10:3125 Feb 2017 | 25 Feb 2017, 11:22 | 22,000 ft | 1,009 |
| not transmitted | route not resolved | 20 Feb 2017, 07:5420 Feb 2017 | 20 Feb 2017, 07:54 | not transmitted | no position received |
| RTG3106 | route not resolved | 18 Feb 2017, 18:4818 Feb 2017 | 18 Feb 2017, 19:26 | 1,075 ft | 2,337 |
| RTG3107 | route not resolved | 16 Feb 2017, 08:2016 Feb 2017 | 16 Feb 2017, 08:34 | 38,175 ft | 186 |
| RTG3079 | route not resolved | 30 Sept 2016, 12:3530 Sept 2016 | 30 Sept 2016, 12:56 | 38,000 ft | 63 |
| LNRTG | route not resolved | 25 Jul 2016, 06:3725 Jul 2016 | 25 Jul 2016, 07:04 | 39,000 ft | 1,487 |
| RTG3043 | route not resolved | 16 Jun 2016, 10:2316 Jun 2016 | 16 Jun 2016, 10:43 | 36,000 ft | 375 |
| RTG3039 | route not resolved | 3 Jun 2016, 12:233 Jun 2016 | 3 Jun 2016, 12:52 | 38,000 ft | 123 |
| RTG3039 | route not resolved | 30 May 2016, 10:0030 May 2016 | 30 May 2016, 10:38 | 39,000 ft | 258 |
Page 1 of 1 · 23 visits
