Back to the log
Aircraft
F-HPUR
Common
The station's story
- Cumulative contact time
- 411 h
- Distinct days
- 760
- Highest captured altitude
- 41,025 ft
- 1 corrupted frame(s) excluded from this maximum
- Discovery rank
- #25,032 of 60,215
- Longest contact
- 1 h 25 min
- Contacts on this Mode S address
- 1,143 contacts on the address, 1,142 under this registration: the address has carried several identities over time.
Observed callsigns
VLJ (1,055 contacts, 2017-2026)
Operator as per the registry of 28 Sept 2026; observed callsigns are the freshest measurement.
Visits
| Callsign | Route | First contact | Last contact | Altitude at end of contact | Positions |
|---|---|---|---|---|---|
| VLJ42CR | route not resolved | 25 Mar 2019, 17:3625 Mar 2019 | 25 Mar 2019, 17:52 | 32,125 ft | 527 |
| VLJ49CR | route not resolved | 23 Mar 2019, 09:3123 Mar 2019 | 23 Mar 2019, 09:45 | 37,000 ft | 92 |
| VLJ83BE | route not resolved | 20 Mar 2019, 16:5820 Mar 2019 | 20 Mar 2019, 17:09 | 26,000 ft | 521 |
| VLJ83BE | route not resolved | 20 Mar 2019, 08:4220 Mar 2019 | 20 Mar 2019, 09:04 | 2,925 ft | 1,578 |
| VLJ030C | route not resolved | 17 Mar 2019, 12:5917 Mar 2019 | 17 Mar 2019, 13:17 | 38,000 ft | 889 |
| VLJ030C | route not resolved | 17 Mar 2019, 11:5517 Mar 2019 | 17 Mar 2019, 12:08 | 5,201 ft | 413 |
| not transmitted | route not resolved | 16 Mar 2019, 08:4416 Mar 2019 | 16 Mar 2019, 08:50 | 18,000 ft | 4 |
| VLJ14CA | route not resolved | 15 Mar 2019, 16:4915 Mar 2019 | 15 Mar 2019, 17:17 | 6,275 ft | 1,178 |
| VLJ24BS | route not resolved | 15 Mar 2019, 11:1515 Mar 2019 | 15 Mar 2019, 11:34 | 31,550 ft | 1,414 |
| VLJ24BS | route not resolved | 15 Mar 2019, 08:5615 Mar 2019 | 15 Mar 2019, 09:10 | 34,900 ft | 547 |
| VLJ96BR | route not resolved | 14 Mar 2019, 01:3814 Mar 2019 | 14 Mar 2019, 01:45 | 38,000 ft | 12 |
| VLJ95BE | route not resolved | 12 Mar 2019, 18:5712 Mar 2019 | 12 Mar 2019, 19:14 | 31,975 ft | 994 |
| VLJ95BE | route not resolved | 12 Mar 2019, 08:4012 Mar 2019 | 12 Mar 2019, 08:57 | 31,875 ft | 957 |
| VLJ02CR | route not resolved | 10 Mar 2019, 22:0910 Mar 2019 | 10 Mar 2019, 22:16 | 37,925 ft | 66 |
| VLJ96BR | route not resolved | 10 Mar 2019, 10:0110 Mar 2019 | 10 Mar 2019, 10:14 | 37,000 ft | 183 |
| VLJ63BE | route not resolved | 9 Mar 2019, 14:279 Mar 2019 | 9 Mar 2019, 14:32 | 22,000 ft | 71 |
| VLJ04BR | route not resolved | 3 Mar 2019, 17:543 Mar 2019 | 3 Mar 2019, 18:05 | 18,000 ft | 770 |
| VLJ04BR | route not resolved | 1 Mar 2019, 11:471 Mar 2019 | 1 Mar 2019, 11:52 | 6,275 ft | 232 |
| VLJ33BR | route not resolved | 26 Feb 2019, 23:1526 Feb 2019 | 26 Feb 2019, 23:35 | 29,950 ft | 674 |
| VLJ33BR | route not resolved | 25 Feb 2019, 09:2525 Feb 2019 | 25 Feb 2019, 09:45 | 39,000 ft | 1,175 |
| not transmitted | route not resolved | 17 Jan 2019, 17:0817 Jan 2019 | 17 Jan 2019, 17:09 | 34,000 ft | no position received |
| VLJ036A | route not resolved | 17 Jan 2019, 08:3217 Jan 2019 | 17 Jan 2019, 08:45 | 35,000 ft | 62 |
| VLJ018A | route not resolved | 10 Jan 2019, 09:5410 Jan 2019 | 10 Jan 2019, 10:07 | 39,000 ft | 329 |
| VLJ017A | route not resolved | 8 Jan 2019, 00:478 Jan 2019 | 8 Jan 2019, 01:02 | 36,000 ft | 659 |
| VLJ017A | route not resolved | 7 Jan 2019, 17:157 Jan 2019 | 7 Jan 2019, 17:33 | 35,000 ft | 337 |
