Back to the log
Aircraft
F-HGTX
Common
The station's story
- Cumulative contact time
- 603 h
- Distinct days
- 931
- Highest captured altitude
- 12,300 ft
- 4 corrupted frame(s) excluded from this maximum
- Discovery rank
- #4,908 of 57,391
- Longest contact
- 1 h 57 min
- Contacts on this Mode S address
- 1,582 contacts on the address, 1,579 under this registration: the address has carried several identities over time.
Visits
| Callsign | Route | First contact | Last contact | Altitude at end of contact | Positions |
|---|---|---|---|---|---|
| FHGTX | route not resolved | 23 May 2019, 08:4723 May 2019 | 23 May 2019, 09:07 | 3,800 ft | no position received |
| FHGTX | route not resolved | 17 May 2019, 11:4917 May 2019 | 17 May 2019, 12:21 | 2,400 ft | no position received |
| FHGTX | route not resolved | 13 May 2019, 11:0813 May 2019 | 13 May 2019, 11:36 | 8,000 ft | no position received |
| FHGTX | route not resolved | 7 May 2019, 14:477 May 2019 | 7 May 2019, 14:53 | 4,900 ft | no position received |
| FHGTX | route not resolved | 7 May 2019, 12:387 May 2019 | 7 May 2019, 12:52 | 2,500 ft | no position received |
| FHGTX | route not resolved | 7 May 2019, 11:127 May 2019 | 7 May 2019, 11:36 | 8,900 ft | no position received |
| FHGTX | route not resolved | 2 May 2019, 12:112 May 2019 | 2 May 2019, 12:28 | 2,600 ft | no position received |
| FHGTX | route not resolved | 2 May 2019, 10:392 May 2019 | 2 May 2019, 11:00 | 7,900 ft | no position received |
| FHGTX | route not resolved | 1 May 2019, 13:211 May 2019 | 1 May 2019, 13:39 | 2,800 ft | no position received |
| FHGTX | route not resolved | 1 May 2019, 11:521 May 2019 | 1 May 2019, 12:19 | 7,900 ft | no position received |
| FHGTX | route not resolved | 24 Apr 2019, 11:5924 Apr 2019 | 24 Apr 2019, 12:28 | 2,400 ft | no position received |
| FHGTX | route not resolved | 24 Apr 2019, 10:3924 Apr 2019 | 24 Apr 2019, 11:09 | 7,600 ft | no position received |
| FHGTX | route not resolved | 22 Apr 2019, 13:0222 Apr 2019 | 22 Apr 2019, 13:17 | 2,600 ft | no position received |
| FHGTX | route not resolved | 22 Apr 2019, 11:3322 Apr 2019 | 22 Apr 2019, 12:03 | 7,800 ft | no position received |
| FHGTX | route not resolved | 21 Apr 2019, 13:4621 Apr 2019 | 21 Apr 2019, 14:22 | 2,000 ft | no position received |
| FHGTX | route not resolved | 19 Apr 2019, 10:4419 Apr 2019 | 19 Apr 2019, 11:20 | 5,400 ft | no position received |
| FHGTX | route not resolved | 12 Apr 2019, 17:1912 Apr 2019 | 12 Apr 2019, 17:46 | 2,800 ft | no position received |
| FHGTX | route not resolved | 12 Apr 2019, 07:4212 Apr 2019 | 12 Apr 2019, 08:14 | 7,900 ft | no position received |
| FHGTX | route not resolved | 10 Apr 2019, 10:5210 Apr 2019 | 10 Apr 2019, 11:46 | 2,800 ft | no position received |
| FHGTX | route not resolved | 10 Apr 2019, 09:2510 Apr 2019 | 10 Apr 2019, 09:49 | 5,800 ft | no position received |
| FHGTX | route not resolved | 30 Mar 2019, 17:5030 Mar 2019 | 30 Mar 2019, 17:59 | 2,900 ft | no position received |
| FHGTX | route not resolved | 30 Mar 2019, 11:0930 Mar 2019 | 30 Mar 2019, 11:17 | 3,000 ft | no position received |
| FHGTX | route not resolved | 24 Mar 2019, 16:5924 Mar 2019 | 24 Mar 2019, 17:22 | 2,400 ft | no position received |
| FHGTX | route not resolved | 23 Mar 2019, 17:1223 Mar 2019 | 23 Mar 2019, 17:32 | 2,600 ft | no position received |
| FHGTX | route not resolved | 22 Mar 2019, 17:3522 Mar 2019 | 22 Mar 2019, 17:48 | 2,200 ft | no position received |