Back to the log
Aircraft
F-HMLJ
Common
The station's story
Address not received since 3 Jul 2023. The marker states the absence, it does not say why.
- Cumulative contact time
- 1,269 h
- Distinct days
- 1,329
- Highest captured altitude
- 39,000 ft
- Discovery rank
- #3,255 of 57,381
- Longest contact
- 1 h 18 min
Observed callsigns
AFR (1,962 contacts, 2017-2022) · HOP (1,251 contacts, 2016-2019)
Operator as per the registry of 12 Aug 2026; observed callsigns are the freshest measurement.
Visits
| Callsign | Route | First contact | Last contact | Altitude at end of contact | Positions |
|---|---|---|---|---|---|
| HOP84XO | LFRS > LFML | 9 Feb 2017, 15:509 Feb 2017 | 9 Feb 2017, 15:59 | 26,425 ft | no position received |
| HOP62VE | route not resolved | 9 Feb 2017, 13:269 Feb 2017 | 9 Feb 2017, 13:41 | 32,000 ft | no position received |
| HOP63SJ | LFRS > LFMN | 9 Feb 2017, 11:219 Feb 2017 | 9 Feb 2017, 11:36 | 32,400 ft | no position received |
| HOP81AD | LFML > LFRS | 9 Feb 2017, 08:489 Feb 2017 | 9 Feb 2017, 08:53 | 34,000 ft | no position received |
| HOP81JW | route not resolved | 9 Feb 2017, 07:169 Feb 2017 | 9 Feb 2017, 07:54 | 7,000 ft | no position received |
| HOP86XX | LFRS > LFML | 8 Feb 2017, 19:398 Feb 2017 | 8 Feb 2017, 19:51 | 24,000 ft | no position received |
| HOP84XO | LFRS > LFML | 8 Feb 2017, 15:468 Feb 2017 | 8 Feb 2017, 15:59 | 25,850 ft | no position received |
| HOP62VE | route not resolved | 8 Feb 2017, 13:248 Feb 2017 | 8 Feb 2017, 13:38 | 32,025 ft | no position received |
| HOP63SJ | LFRS > LFMN | 8 Feb 2017, 11:228 Feb 2017 | 8 Feb 2017, 11:36 | 33,000 ft | no position received |
| HOP80ZY | route not resolved | 8 Feb 2017, 07:178 Feb 2017 | 8 Feb 2017, 07:49 | 7,650 ft | no position received |
| HOP87DJ | LFML > LFRS | 7 Feb 2017, 22:257 Feb 2017 | 7 Feb 2017, 22:30 | 34,025 ft | no position received |
| HOP86XX | LFRS > LFML | 7 Feb 2017, 20:547 Feb 2017 | 7 Feb 2017, 21:17 | 20,050 ft | no position received |
| AF508PN | route not resolved | 7 Feb 2017, 18:477 Feb 2017 | 7 Feb 2017, 19:06 | 33,000 ft | no position received |
| HOP84XO | LFRS > LFML | 7 Feb 2017, 17:127 Feb 2017 | 7 Feb 2017, 17:21 | 27,525 ft | no position received |
| HOP62VE | route not resolved | 7 Feb 2017, 13:237 Feb 2017 | 7 Feb 2017, 13:39 | 34,000 ft | no position received |
| AF547VT | route not resolved | 7 Feb 2017, 11:207 Feb 2017 | 7 Feb 2017, 12:00 | 34,000 ft | no position received |
| HOP80ZY | route not resolved | 7 Feb 2017, 07:127 Feb 2017 | 7 Feb 2017, 07:40 | 14,900 ft | no position received |
| HOP87DJ | LFML > LFRS | 6 Feb 2017, 21:276 Feb 2017 | 6 Feb 2017, 21:37 | 21,500 ft | no position received |
| HOP86XX | LFRS > LFML | 6 Feb 2017, 19:576 Feb 2017 | 6 Feb 2017, 20:10 | 29,225 ft | no position received |
| HOP30TZ | route not resolved | 6 Feb 2017, 17:346 Feb 2017 | 6 Feb 2017, 17:39 | 33,900 ft | no position received |
| HOP84XO | LFRS > LFML | 6 Feb 2017, 15:486 Feb 2017 | 6 Feb 2017, 16:00 | 28,550 ft | no position received |
| HOP62VE | route not resolved | 6 Feb 2017, 13:186 Feb 2017 | 6 Feb 2017, 13:35 | 34,000 ft | no position received |
| HOP63SJ | LFRS > LFMN | 6 Feb 2017, 11:126 Feb 2017 | 6 Feb 2017, 11:24 | 33,025 ft | no position received |
| HOP82TP | route not resolved | 6 Feb 2017, 08:546 Feb 2017 | 6 Feb 2017, 09:24 | 16,950 ft | no position received |
| HOP80ZY | route not resolved | 6 Feb 2017, 07:126 Feb 2017 | 6 Feb 2017, 07:56 | 6,975 ft | no position received |
