Back to the log
Aircraft
F-GTBT
Common
The station's story
Address not received since 8 Aug 2022. The marker states the absence, it does not say why.
- Cumulative contact time
- 19 h
- Distinct days
- 43
- Highest captured altitude
- 10,700 ft
- 4 corrupted frame(s) excluded from this maximum
- Discovery rank
- #4,406 of 57,441
- Longest contact
- 1 h 40 min
- Contacts on this Mode S address
- 70 contacts on the address, 52 under this registration: the address has carried several identities over time.
Observed callsigns
AFR (1 contacts, 2017)
Operator as per the registry of 29 Jul 2026; observed callsigns are the freshest measurement.
Visits
| Callsign | Route | First contact | Last contact | Altitude at end of contact | Positions |
|---|---|---|---|---|---|
| FGTBT | route not resolved | 29 Jun 2018, 12:2829 Jun 2018 | 29 Jun 2018, 12:46 | 2,200 ft | no position received |
| FGTBT | route not resolved | 27 Jun 2018, 14:4327 Jun 2018 | 27 Jun 2018, 14:56 | 6,400 ft | no position received |
| FGTBT | route not resolved | 18 Apr 2018, 17:3618 Apr 2018 | 18 Apr 2018, 18:50 | 2,000 ft | no position received |
| FGTBT | route not resolved | 15 Apr 2018, 11:2815 Apr 2018 | 15 Apr 2018, 13:09 | 2,400 ft | no position received |
| FGTBT | route not resolved | 6 Apr 2018, 18:526 Apr 2018 | 6 Apr 2018, 19:25 | 2,300 ft | no position received |
| FGTBT | route not resolved | 5 Apr 2018, 16:005 Apr 2018 | 5 Apr 2018, 16:11 | 5,000 ft | no position received |
| FGTBT | route not resolved | 24 Mar 2018, 11:1924 Mar 2018 | 24 Mar 2018, 11:58 | 2,800 ft | no position received |
| FGTBT | route not resolved | 21 Mar 2018, 16:5821 Mar 2018 | 21 Mar 2018, 17:26 | 1,900 ft | no position received |
| FGTBT | route not resolved | 19 Feb 2018, 10:1219 Feb 2018 | 19 Feb 2018, 10:45 | 28,000 ft | no position received |
| FGTBT | route not resolved | 18 Feb 2018, 17:2418 Feb 2018 | 18 Feb 2018, 17:39 | 2,000 ft | no position received |
| FGTBT | route not resolved | 18 Feb 2018, 12:0318 Feb 2018 | 18 Feb 2018, 12:16 | 6,300 ft | no position received |
| FGTBT | route not resolved | 13 Feb 2018, 17:2313 Feb 2018 | 13 Feb 2018, 17:35 | 2,500 ft | no position received |
| FGTBT | route not resolved | 13 Feb 2018, 16:2613 Feb 2018 | 13 Feb 2018, 16:39 | 9,600 ft | no position received |
| AFR89GC | LFPG > LIRF | 18 Nov 2017, 15:0418 Nov 2017 | 18 Nov 2017, 15:53 | 32,975 ft | no position received |
| FGTBT | route not resolved | 2 Nov 2017, 11:052 Nov 2017 | 2 Nov 2017, 11:44 | 8,400 ft | no position received |
| FGTBT | route not resolved | 15 Oct 2017, 17:5615 Oct 2017 | 15 Oct 2017, 18:08 | 1,900 ft | no position received |
| FGTBT | route not resolved | 14 Oct 2017, 14:2614 Oct 2017 | 14 Oct 2017, 14:39 | 5,400 ft | no position received |
| FGTBT | route not resolved | 17 Sept 2017, 11:2817 Sept 2017 | 17 Sept 2017, 11:50 | 28,975 ft | no position received |
| FGTBT | route not resolved | 15 Sept 2017, 15:3015 Sept 2017 | 15 Sept 2017, 15:42 | 5,300 ft | no position received |
| FGTBT | route not resolved | 3 Sept 2017, 19:103 Sept 2017 | 3 Sept 2017, 19:21 | 2,300 ft | no position received |
| FGTBT | route not resolved | 3 Sept 2017, 10:223 Sept 2017 | 3 Sept 2017, 10:55 | 35,000 ft | no position received |
| not transmitted | route not resolved | 13 Aug 2017, 18:4213 Aug 2017 | 13 Aug 2017, 19:04 | 2,000 ft | no position received |
| FGTBT | route not resolved | 6 Jul 2017, 16:036 Jul 2017 | 6 Jul 2017, 16:18 | 6,400 ft | no position received |
| FGTBT | route not resolved | 1 Jul 2017, 14:381 Jul 2017 | 1 Jul 2017, 14:46 | 2,200 ft | no position received |
| FGTBT | route not resolved | 30 Jun 2017, 20:0530 Jun 2017 | 30 Jun 2017, 20:11 | 1,900 ft | no position received |