Back to the log
Aircraft
F-GNSF
Commonnot seen for 7 years
The station's story
Address not received since 13 Feb 2019. The marker states the absence, it does not say why.
- Cumulative contact time
- 5 h
- Distinct days
- 28
- Highest captured altitude
- 10,100 ft
- Discovery rank
- #13,759 of 57,065
- Longest contact
- 0 h 48 min
Observed callsigns
NAK (25 contacts, 2016-2019)
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 |
|---|---|---|---|---|---|
| not transmitted | route not resolved | 13 Feb 2019, 10:4113 Feb 2019 | 13 Feb 2019, 10:42 | 8,100 ft | no position received |
| NAK730 | route not resolved | 8 Jan 2019, 14:218 Jan 2019 | 8 Jan 2019, 14:29 | 10,100 ft | no position received |
| not transmitted | route not resolved | 8 Jan 2019, 11:518 Jan 2019 | 8 Jan 2019, 12:03 | 6,000 ft | no position received |
| not transmitted | route not resolved | 8 Nov 2018, 11:558 Nov 2018 | 8 Nov 2018, 11:55 | 7,100 ft | no position received |
| NAK755C | route not resolved | 7 Jun 2018, 10:267 Jun 2018 | 7 Jun 2018, 10:33 | 8,000 ft | no position received |
| NAK762A | route not resolved | 24 May 2018, 11:1124 May 2018 | 24 May 2018, 11:14 | 8,000 ft | no position received |
| NAK790 | route not resolved | 19 Apr 2018, 16:2319 Apr 2018 | 19 Apr 2018, 16:51 | 9,000 ft | no position received |
| NAK790 | route not resolved | 19 Apr 2018, 11:1819 Apr 2018 | 19 Apr 2018, 11:41 | 9,900 ft | no position received |
| NAK728P | route not resolved | 7 Mar 2018, 13:507 Mar 2018 | 7 Mar 2018, 14:12 | 9,100 ft | no position received |
| not transmitted | route not resolved | 1 Mar 2018, 17:561 Mar 2018 | 1 Mar 2018, 17:57 | 8,000 ft | no position received |
| not transmitted | route not resolved | 27 Feb 2018, 12:0727 Feb 2018 | 27 Feb 2018, 12:08 | 10,100 ft | no position received |
| NAK727A | route not resolved | 15 Nov 2017, 10:3815 Nov 2017 | 15 Nov 2017, 10:45 | 7,000 ft | no position received |
| NAK730B | route not resolved | 22 Sept 2017, 15:4022 Sept 2017 | 22 Sept 2017, 15:45 | 7,000 ft | no position received |
| NAK730B | route not resolved | 15 Sept 2017, 11:0215 Sept 2017 | 15 Sept 2017, 11:08 | 8,000 ft | no position received |
| NAK747 | route not resolved | 30 Aug 2017, 16:5430 Aug 2017 | 30 Aug 2017, 16:56 | 8,000 ft | no position received |
| NAK747 | route not resolved | 23 Jun 2017, 14:1323 Jun 2017 | 23 Jun 2017, 14:20 | 7,000 ft | no position received |
| NAK707 | route not resolved | 2 Jun 2017, 14:282 Jun 2017 | 2 Jun 2017, 14:35 | 7,000 ft | no position received |
| NAK707Z | route not resolved | 2 Jun 2017, 10:432 Jun 2017 | 2 Jun 2017, 11:28 | 7,100 ft | no position received |
| NAK736B | route not resolved | 24 May 2017, 11:5224 May 2017 | 24 May 2017, 12:02 | 8,000 ft | no position received |
| NAK356D | route not resolved | 27 Mar 2017, 11:4827 Mar 2017 | 27 Mar 2017, 11:50 | 8,000 ft | no position received |
| not transmitted | route not resolved | 27 Mar 2017, 10:0627 Mar 2017 | 27 Mar 2017, 10:07 | 7,100 ft | no position received |
| not transmitted | route not resolved | 14 Feb 2017, 18:1014 Feb 2017 | 14 Feb 2017, 18:11 | 7,100 ft | no position received |
| not transmitted | route not resolved | 9 Jan 2017, 19:159 Jan 2017 | 9 Jan 2017, 19:15 | 7,000 ft | no position received |
| NAK356 | route not resolved | 6 Dec 2016, 13:056 Dec 2016 | 6 Dec 2016, 13:12 | 8,000 ft | no position received |
| NAK356 | route not resolved | 4 Nov 2016, 14:174 Nov 2016 | 4 Nov 2016, 14:28 | 8,000 ft | no position received |