Back to the log
Aircraft
F-GTYA
Common
The station's story
- Cumulative contact time
- 89 h
- Distinct days
- 220
- Highest captured altitude
- 10,100 ft
- 1 corrupted frame(s) excluded from this maximum
- Discovery rank
- #17,743 of 60,168
- Longest contact
- 1 h 14 min
Observed callsigns
NAK (217 contacts, 2016-2026)
Operator as per the registry of 21 Sept 2026; observed callsigns are the freshest measurement.
Visits
| Callsign | Route | First contact | Last contact | Altitude at end of contact | Positions |
|---|---|---|---|---|---|
| NAK14D | route not resolved | 22 Feb 2018, 15:5522 Feb 2018 | 22 Feb 2018, 15:58 | 7,700 ft | no position received |
| NAK356 | route not resolved | 16 Feb 2018, 09:2416 Feb 2018 | 16 Feb 2018, 09:32 | 6,000 ft | no position received |
| NAK730S | route not resolved | 6 Dec 2017, 11:086 Dec 2017 | 6 Dec 2017, 11:17 | 7,900 ft | no position received |
| NAK625A | route not resolved | 13 Nov 2017, 16:4413 Nov 2017 | 13 Nov 2017, 16:52 | 7,100 ft | no position received |
| FGTYA | route not resolved | 27 Oct 2017, 15:4127 Oct 2017 | 27 Oct 2017, 15:47 | 3,800 ft | no position received |
| not transmitted | route not resolved | 16 Oct 2017, 14:1716 Oct 2017 | 16 Oct 2017, 14:17 | 4,200 ft | no position received |
| not transmitted | route not resolved | 12 Oct 2017, 11:4412 Oct 2017 | 12 Oct 2017, 11:45 | 6,100 ft | no position received |
| not transmitted | route not resolved | 12 Oct 2017, 09:1612 Oct 2017 | 12 Oct 2017, 09:25 | 5,500 ft | no position received |
| not transmitted | route not resolved | 9 Oct 2017, 13:459 Oct 2017 | 9 Oct 2017, 13:45 | not transmitted | no position received |
| not transmitted | route not resolved | 5 Oct 2017, 12:085 Oct 2017 | 5 Oct 2017, 12:09 | not transmitted | no position received |
| not transmitted | route not resolved | 22 Sept 2017, 14:4122 Sept 2017 | 22 Sept 2017, 14:42 | 4,300 ft | no position received |
| NAK335 | route not resolved | 15 Sept 2017, 07:4215 Sept 2017 | 15 Sept 2017, 07:51 | 7,000 ft | no position received |
| not transmitted | route not resolved | 13 Sept 2017, 09:1913 Sept 2017 | 13 Sept 2017, 09:19 | 6,300 ft | no position received |
| NAK335 | route not resolved | 12 Sept 2017, 14:4912 Sept 2017 | 12 Sept 2017, 14:57 | 7,000 ft | no position received |
| NAK351 | route not resolved | 7 Sept 2017, 13:307 Sept 2017 | 7 Sept 2017, 13:37 | 8,000 ft | no position received |
| NAK356 | route not resolved | 6 Sept 2017, 08:426 Sept 2017 | 6 Sept 2017, 08:54 | 8,100 ft | no position received |
| NAK356 | route not resolved | 30 Aug 2017, 15:4430 Aug 2017 | 30 Aug 2017, 15:52 | 7,000 ft | no position received |
| NAK356 | route not resolved | 30 Aug 2017, 13:0630 Aug 2017 | 30 Aug 2017, 13:12 | 7,000 ft | no position received |
| NAK356 | route not resolved | 30 Aug 2017, 09:2630 Aug 2017 | 30 Aug 2017, 09:35 | 7,000 ft | no position received |
| NAK736B | route not resolved | 2 Aug 2017, 10:302 Aug 2017 | 2 Aug 2017, 10:39 | 9,000 ft | no position received |
| not transmitted | route not resolved | 2 Jun 2017, 09:502 Jun 2017 | 2 Jun 2017, 10:01 | 8,100 ft | no position received |
| NAK356 | route not resolved | 1 Jun 2017, 08:571 Jun 2017 | 1 Jun 2017, 09:00 | 8,000 ft | no position received |
| not transmitted | route not resolved | 30 May 2017, 17:5130 May 2017 | 30 May 2017, 17:51 | 9,000 ft | no position received |
| NAK351 | route not resolved | 24 May 2017, 08:1324 May 2017 | 24 May 2017, 08:24 | 8,000 ft | no position received |
| FGTYA | route not resolved | 18 May 2017, 16:0218 May 2017 | 18 May 2017, 16:06 | 4,600 ft | no position received |