Back to the log
Aircraft
F-HVAA
Regular
The station's story
Address not received since 26 Feb 2022. The marker states the absence, it does not say why.
- Cumulative contact time
- 11 h
- Distinct days
- 48
- Highest captured altitude
- 9,500 ft
- Discovery rank
- #16,717 of 57,065
- Longest contact
- 0 h 31 min
Visits
| Callsign | Route | First contact | Last contact | Altitude at end of contact | Positions |
|---|---|---|---|---|---|
| FHVAA | route not resolved | 24 Feb 2019, 15:1724 Feb 2019 | 24 Feb 2019, 15:22 | 875 ft | no position received |
| not transmitted | route not resolved | 24 Feb 2019, 08:4724 Feb 2019 | 24 Feb 2019, 08:48 | 5,400 ft | no position received |
| FHVAA | route not resolved | 23 Feb 2019, 17:1123 Feb 2019 | 23 Feb 2019, 17:29 | 3,075 ft | no position received |
| not transmitted | route not resolved | 6 Feb 2019, 13:436 Feb 2019 | 6 Feb 2019, 13:44 | 3,075 ft | no position received |
| not transmitted | route not resolved | 6 Feb 2019, 09:436 Feb 2019 | 6 Feb 2019, 09:44 | 3,250 ft | no position received |
| not transmitted | route not resolved | 6 Feb 2019, 09:066 Feb 2019 | 6 Feb 2019, 09:07 | 5,550 ft | no position received |
| FHVAA | route not resolved | 22 Jan 2019, 16:3322 Jan 2019 | 22 Jan 2019, 16:53 | 3,575 ft | no position received |
| FHVAA | route not resolved | 19 Jan 2019, 15:5119 Jan 2019 | 19 Jan 2019, 16:21 | 3,625 ft | no position received |
| not transmitted | route not resolved | 19 Jan 2019, 14:3919 Jan 2019 | 19 Jan 2019, 14:43 | 4,075 ft | no position received |
| FHVAA | route not resolved | 18 Jan 2019, 16:1418 Jan 2019 | 18 Jan 2019, 16:18 | 1,575 ft | no position received |
| FHVAA | route not resolved | 18 Jan 2019, 13:1418 Jan 2019 | 18 Jan 2019, 13:18 | 8,500 ft | no position received |
| FHVAA | route not resolved | 10 Jan 2019, 16:5410 Jan 2019 | 10 Jan 2019, 17:25 | 3,600 ft | no position received |
| not transmitted | route not resolved | 6 Jan 2019, 11:226 Jan 2019 | 6 Jan 2019, 11:22 | not transmitted | no position received |
| FHVAA | route not resolved | 5 Jan 2019, 09:035 Jan 2019 | 5 Jan 2019, 09:35 | 5,450 ft | no position received |
| FHVAA | route not resolved | 1 Jan 2019, 15:511 Jan 2019 | 1 Jan 2019, 15:54 | 2,525 ft | no position received |
| not transmitted | route not resolved | 30 Dec 2018, 12:4430 Dec 2018 | 30 Dec 2018, 12:45 | 1,925 ft | no position received |
| not transmitted | route not resolved | 29 Dec 2018, 15:2129 Dec 2018 | 29 Dec 2018, 15:21 | 3,775 ft | no position received |
| FHVAA | route not resolved | 22 Dec 2017, 15:3622 Dec 2017 | 22 Dec 2017, 15:47 | 3,250 ft | no position received |
| FHVAA | route not resolved | 22 Nov 2017, 10:0422 Nov 2017 | 22 Nov 2017, 10:14 | 3,400 ft | no position received |
| not transmitted | route not resolved | 2 Jan 2017, 16:112 Jan 2017 | 2 Jan 2017, 16:12 | 3,575 ft | no position received |
| FHVAA | route not resolved | 2 Jan 2017, 14:532 Jan 2017 | 2 Jan 2017, 14:57 | 3,425 ft | no position received |
| not transmitted | route not resolved | 2 Jan 2017, 13:452 Jan 2017 | 2 Jan 2017, 13:45 | not transmitted | no position received |
| FHVAA | route not resolved | 21 Dec 2016, 08:2421 Dec 2016 | 21 Dec 2016, 08:29 | 6,075 ft | no position received |
| FHVAA | route not resolved | 11 Aug 2016, 18:3611 Aug 2016 | 11 Aug 2016, 19:04 | 2,775 ft | no position received |
