Back to the log
Aircraft
F-HEMI
Common
The station's story
- Cumulative contact time
- 405 h
- Distinct days
- 730
- Highest captured altitude
- 45,000 ft
- Discovery rank
- #27,802 of 57,223
- Longest contact
- 1 h 36 min
- Contacts on this Mode S address
- 1,128 contacts on the address, 1,123 under this registration: the address has carried several identities over time.
Same airframe, also seen as
- M-ICRCfrom 25 May 2016 to 24 Sept 2018 · 57 contacts
These registrations share the same serial number and type according to the reference data. Serial numbers can collide, though: it is a deduction, not a certainty.
Observed callsigns
VLJ (1,071 contacts, 2018-2026)
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 |
|---|---|---|---|---|---|
| VLJ12AH | route not resolved | 22 Jul 2019, 11:0422 Jul 2019 | 22 Jul 2019, 11:18 | 27,000 ft | 289 |
| VLJ12AH | route not resolved | 22 Jul 2019, 10:1722 Jul 2019 | 22 Jul 2019, 10:29 | 3,525 ft | 392 |
| VLJ01AH | route not resolved | 20 Jul 2019, 13:5620 Jul 2019 | 20 Jul 2019, 14:35 | 39,025 ft | 2,285 |
| VLJ28GH | route not resolved | 15 Jul 2019, 18:1315 Jul 2019 | 15 Jul 2019, 18:32 | 33,125 ft | 889 |
| VLJ28GH | route not resolved | 14 Jul 2019, 11:0014 Jul 2019 | 14 Jul 2019, 11:34 | 34,000 ft | 1,215 |
| VLJ06AH | route not resolved | 12 Jul 2019, 20:1212 Jul 2019 | 12 Jul 2019, 20:29 | 31,475 ft | 913 |
| VLJ06AH | route not resolved | 12 Jul 2019, 16:3912 Jul 2019 | 12 Jul 2019, 17:09 | 38,000 ft | 1,159 |
| VLJ04AH | route not resolved | 11 Jul 2019, 18:3011 Jul 2019 | 11 Jul 2019, 18:57 | 34,625 ft | 359 |
| VLJ17GZ | route not resolved | 6 Jul 2019, 13:556 Jul 2019 | 6 Jul 2019, 14:04 | 24,350 ft | 134 |
| VLJ17GZ | route not resolved | 6 Jul 2019, 10:066 Jul 2019 | 6 Jul 2019, 10:28 | 40,000 ft | 535 |
| VLJ22CH | route not resolved | 4 Jul 2019, 17:074 Jul 2019 | 4 Jul 2019, 17:29 | 41,000 ft | 249 |
| not transmitted | route not resolved | 1 Jul 2019, 21:191 Jul 2019 | 1 Jul 2019, 21:19 | 42,025 ft | no position received |
| VLJ51GH | route not resolved | 28 Jun 2019, 07:2028 Jun 2019 | 28 Jun 2019, 07:59 | 39,000 ft | 1,578 |
| VLJ51GH | route not resolved | 28 Jun 2019, 04:3728 Jun 2019 | 28 Jun 2019, 05:23 | 37,500 ft | 3,468 |
| VLJ99FH | route not resolved | 27 Jun 2019, 08:3927 Jun 2019 | 27 Jun 2019, 08:59 | 34,000 ft | 978 |
| VLJ99FH | route not resolved | 26 Jun 2019, 15:1526 Jun 2019 | 26 Jun 2019, 15:41 | 36,000 ft | 1,149 |
| VLJ30GH | route not resolved | 26 Jun 2019, 00:2526 Jun 2019 | 26 Jun 2019, 00:37 | 27,000 ft | 728 |
| VLJ30GH | route not resolved | 25 Jun 2019, 19:3625 Jun 2019 | 25 Jun 2019, 19:43 | 6,475 ft | 232 |
| VLJ22GH | route not resolved | 22 Jun 2019, 23:0022 Jun 2019 | 22 Jun 2019, 23:33 | 32,000 ft | 1,952 |
| VLJ84FH | route not resolved | 18 Jun 2019, 19:4018 Jun 2019 | 18 Jun 2019, 19:54 | 23,000 ft | 460 |
| VLJ84FH | route not resolved | 18 Jun 2019, 07:4618 Jun 2019 | 18 Jun 2019, 08:04 | 16,750 ft | 483 |
| VLJ82FH | route not resolved | 17 Jun 2019, 16:4717 Jun 2019 | 17 Jun 2019, 17:15 | 29,000 ft | 1,411 |
| VLJ82FH | route not resolved | 17 Jun 2019, 08:5917 Jun 2019 | 17 Jun 2019, 09:24 | 19,100 ft | 1,271 |
| VLJ04FH | route not resolved | 12 Jun 2019, 14:1812 Jun 2019 | 12 Jun 2019, 14:39 | 34,050 ft | 362 |
| VLJ04FH | route not resolved | 12 Jun 2019, 09:0512 Jun 2019 | 12 Jun 2019, 09:21 | 32,675 ft | 698 |
