Back to the log
Aircraft
F-HAYT
Common
The station's story
Address not received since 27 May 2022. The marker states the absence, it does not say why.
- Cumulative contact time
- 47 h
- Distinct days
- 156
- Highest captured altitude
- 11,600 ft
- 2 corrupted frame(s) excluded from this maximum
- Discovery rank
- #23,511 of 57,065
- Longest contact
- 0 h 58 min
- Contacts on this Mode S address
- 237 contacts on the address, 222 under this registration: the address has carried several identities over time.
Visits
| Callsign | Route | First contact | Last contact | Altitude at end of contact | Positions |
|---|---|---|---|---|---|
| FHAYT | route not resolved | 10 Jul 2019, 12:0110 Jul 2019 | 10 Jul 2019, 12:13 | 5,900 ft | no position received |
| not transmitted | route not resolved | 7 Jul 2019, 19:127 Jul 2019 | 7 Jul 2019, 19:19 | 5,600 ft | no position received |
| FHAYT | route not resolved | 6 Jul 2019, 13:056 Jul 2019 | 6 Jul 2019, 13:09 | 6,200 ft | no position received |
| not transmitted | route not resolved | 4 Jul 2019, 19:324 Jul 2019 | 4 Jul 2019, 19:37 | 3,900 ft | no position received |
| FHAYT | route not resolved | 29 Jun 2019, 17:5729 Jun 2019 | 29 Jun 2019, 18:12 | 7,400 ft | no position received |
| FHAYT | route not resolved | 29 Jun 2019, 09:5229 Jun 2019 | 29 Jun 2019, 10:05 | 6,400 ft | no position received |
| FHAYT | route not resolved | 28 Jun 2019, 13:5328 Jun 2019 | 28 Jun 2019, 14:05 | 6,500 ft | no position received |
| FHAYT | route not resolved | 23 Jun 2019, 17:4223 Jun 2019 | 23 Jun 2019, 17:56 | 5,900 ft | no position received |
| FHAYT | route not resolved | 23 Jun 2019, 10:5923 Jun 2019 | 23 Jun 2019, 11:14 | 6,000 ft | no position received |
| FHAYT | route not resolved | 16 Jun 2019, 16:4616 Jun 2019 | 16 Jun 2019, 17:27 | 5,300 ft | no position received |
| not transmitted | route not resolved | 12 Jun 2019, 20:0412 Jun 2019 | 12 Jun 2019, 20:12 | 5,000 ft | no position received |
| FHAYT | route not resolved | 2 Jun 2019, 18:182 Jun 2019 | 2 Jun 2019, 18:30 | 6,400 ft | no position received |
| FHAYT | route not resolved | 1 Jun 2019, 17:201 Jun 2019 | 1 Jun 2019, 17:32 | 6,300 ft | no position received |
| FHAYT | route not resolved | 22 May 2019, 18:5022 May 2019 | 22 May 2019, 19:35 | 4,500 ft | no position received |
| FHAYT | route not resolved | 16 May 2019, 18:4216 May 2019 | 16 May 2019, 18:58 | 6,500 ft | no position received |
| FHAYT | route not resolved | 16 May 2019, 13:5916 May 2019 | 16 May 2019, 14:11 | 6,000 ft | no position received |
| FHAYT | route not resolved | 15 May 2019, 19:2615 May 2019 | 15 May 2019, 19:34 | 3,900 ft | no position received |
| not transmitted | route not resolved | 27 Apr 2019, 12:4327 Apr 2019 | 27 Apr 2019, 12:43 | 3,600 ft | no position received |
| not transmitted | route not resolved | 19 Apr 2019, 18:3819 Apr 2019 | 19 Apr 2019, 18:46 | 4,400 ft | no position received |
| not transmitted | route not resolved | 17 Apr 2019, 19:3817 Apr 2019 | 17 Apr 2019, 19:41 | not transmitted | no position received |
| FHAYT | route not resolved | 17 Apr 2019, 15:2717 Apr 2019 | 17 Apr 2019, 15:30 | 3,800 ft | no position received |
| not transmitted | route not resolved | 17 Apr 2019, 13:3317 Apr 2019 | 17 Apr 2019, 13:33 | 2,400 ft | no position received |
| FHAYT | route not resolved | 14 Apr 2019, 17:4914 Apr 2019 | 14 Apr 2019, 17:56 | 5,000 ft | no position received |
| not transmitted | route not resolved | 23 Mar 2019, 11:3023 Mar 2019 | 23 Mar 2019, 11:34 | 4,700 ft | no position received |
| FHAYT | route not resolved | 23 Mar 2019, 10:5423 Mar 2019 | 23 Mar 2019, 11:01 | 5,600 ft | no position received |