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,907 of 57,260
- 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 | 19 Feb 2017, 16:4219 Feb 2017 | 19 Feb 2017, 16:52 | 7,400 ft | no position received |
| FHGTX | route not resolved | 19 Feb 2017, 13:4119 Feb 2017 | 19 Feb 2017, 14:00 | 5,000 ft | no position received |
| FHGTX | route not resolved | 18 Feb 2017, 16:1418 Feb 2017 | 18 Feb 2017, 16:36 | 2,500 ft | no position received |
| FHGTX | route not resolved | 18 Feb 2017, 15:1318 Feb 2017 | 18 Feb 2017, 15:44 | 8,300 ft | no position received |
| FHGTX | route not resolved | 18 Feb 2017, 13:5418 Feb 2017 | 18 Feb 2017, 14:37 | 2,100 ft | no position received |
| FHGTX | route not resolved | 17 Feb 2017, 16:5017 Feb 2017 | 17 Feb 2017, 17:20 | 2,000 ft | no position received |
| FHGTX | route not resolved | 17 Feb 2017, 15:4217 Feb 2017 | 17 Feb 2017, 16:08 | 3,000 ft | no position received |
| FHGTX | route not resolved | 16 Feb 2017, 13:5116 Feb 2017 | 16 Feb 2017, 13:55 | 1,900 ft | no position received |
| FHGTX | route not resolved | 11 Feb 2017, 10:2911 Feb 2017 | 11 Feb 2017, 11:28 | 2,300 ft | no position received |
| FHGTX | route not resolved | 9 Feb 2017, 15:469 Feb 2017 | 9 Feb 2017, 16:03 | 2,200 ft | no position received |
| FHGTX | route not resolved | 3 Feb 2017, 15:453 Feb 2017 | 3 Feb 2017, 16:01 | 2,600 ft | no position received |
| FHGTX | route not resolved | 2 Feb 2017, 17:122 Feb 2017 | 2 Feb 2017, 17:18 | 2,500 ft | no position received |
| FHGTX | route not resolved | 29 Jan 2017, 15:5129 Jan 2017 | 29 Jan 2017, 16:43 | 2,100 ft | no position received |
| FHGTX | route not resolved | 20 Jan 2017, 15:5820 Jan 2017 | 20 Jan 2017, 16:20 | 2,000 ft | no position received |
| FHGTX | route not resolved | 15 Jan 2017, 15:1515 Jan 2017 | 15 Jan 2017, 15:33 | 2,100 ft | no position received |
| FHGTX | route not resolved | 7 Jan 2017, 15:477 Jan 2017 | 7 Jan 2017, 16:02 | 1,800 ft | no position received |
| FHGTX | route not resolved | 6 Jan 2017, 15:216 Jan 2017 | 6 Jan 2017, 15:44 | 2,300 ft | no position received |
| FHGTX | route not resolved | 5 Jan 2017, 14:325 Jan 2017 | 5 Jan 2017, 14:52 | 2,200 ft | no position received |
| FHGTX | route not resolved | 29 Dec 2016, 16:1829 Dec 2016 | 29 Dec 2016, 16:26 | 4,800 ft | no position received |
| FHGTX | route not resolved | 29 Dec 2016, 15:0829 Dec 2016 | 29 Dec 2016, 15:25 | 5,900 ft | no position received |
| FHGTX | route not resolved | 28 Dec 2016, 15:3728 Dec 2016 | 28 Dec 2016, 16:12 | 1,600 ft | no position received |
| FHGTX | route not resolved | 25 Dec 2016, 14:0525 Dec 2016 | 25 Dec 2016, 14:07 | 2,000 ft | no position received |
| FHGTX | route not resolved | 25 Dec 2016, 12:3325 Dec 2016 | 25 Dec 2016, 12:38 | 1,700 ft | no position received |
| FHGTX | route not resolved | 20 Dec 2016, 14:3120 Dec 2016 | 20 Dec 2016, 15:12 | 2,000 ft | no position received |
| FHGTX | route not resolved | 20 Dec 2016, 13:0320 Dec 2016 | 20 Dec 2016, 13:29 | 6,300 ft | no position received |