Back to the log
Aircraft
HB-JFQ
Common
- Mode S hex
- 4B1856
- Manufacturer
- Dassault Aviation
- Serial number
- 213
- Year built
- 201313 years old
- Operator
- Japat Ag
- Country of registration
Switzerland- First contact
- 16 Sept 2016, 07:26
- Last contact
- 18 Sept 2026, 09:22
- Logged visits
- 652
The station's story
- Cumulative contact time
- 155 h
- Distinct days
- 459
- Highest captured altitude
- 45,000 ft
- Discovery rank
- #18,033 of 60,453
- Longest contact
- 1 h 40 min
- Contacts on this Mode S address
- 662 contacts on the address, 652 under this registration: the address has carried several identities over time.
Same airframe, also seen as
- M-MNAAfrom 6 Apr 2016 to 2 Sept 2016 · 43 contacts
- HB-JFQfrom 28 Feb 2018 to 28 Nov 2018 · 82 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.
Visits
| Callsign | Route | First contact | Last contact | Altitude at end of contact | Positions |
|---|---|---|---|---|---|
| HBJFQ | route not resolved | 11 Feb 2019, 07:3111 Feb 2019 | 11 Feb 2019, 07:43 | 20,000 ft | 336 |
| HBJFQ | route not resolved | 8 Feb 2019, 06:228 Feb 2019 | 8 Feb 2019, 06:35 | 10,250 ft | 670 |
| HBJFQ | route not resolved | 6 Feb 2019, 08:046 Feb 2019 | 6 Feb 2019, 08:21 | 37,575 ft | 1,543 |
| HBJFQ | route not resolved | 4 Feb 2019, 18:124 Feb 2019 | 4 Feb 2019, 18:15 | 6,650 ft | 8 |
| HBJFQ | route not resolved | 4 Feb 2019, 11:594 Feb 2019 | 4 Feb 2019, 12:22 | 16,000 ft | 924 |
| not transmitted | route not resolved | 4 Feb 2019, 11:284 Feb 2019 | 4 Feb 2019, 11:32 | not transmitted | no position received |
| HBJFQ | route not resolved | 4 Feb 2019, 07:494 Feb 2019 | 4 Feb 2019, 08:23 | 1,025 ft | 2,407 |
| not transmitted | route not resolved | 1 Feb 2019, 17:481 Feb 2019 | 1 Feb 2019, 17:48 | not transmitted | no position received |
| HBJFQ | route not resolved | 31 Jan 2019, 16:0731 Jan 2019 | 31 Jan 2019, 16:23 | 38,000 ft | 1,111 |
| HBJFQ | route not resolved | 30 Jan 2019, 19:0930 Jan 2019 | 30 Jan 2019, 19:16 | 10,600 ft | 63 |
| HBJFQ | route not resolved | 30 Jan 2019, 17:5330 Jan 2019 | 30 Jan 2019, 17:58 | 19,000 ft | 6 |
| HBJFQ | route not resolved | 29 Jan 2019, 06:3129 Jan 2019 | 29 Jan 2019, 06:38 | 19,000 ft | 137 |
| HBJFQ | route not resolved | 22 Jan 2019, 11:3722 Jan 2019 | 22 Jan 2019, 11:44 | 10,525 ft | 9 |
| HBJFQ | route not resolved | 21 Jan 2019, 19:0921 Jan 2019 | 21 Jan 2019, 19:10 | 17,775 ft | 114 |
| HBJFQ | route not resolved | 20 Dec 2018, 17:2120 Dec 2018 | 20 Dec 2018, 17:35 | 34,050 ft | 871 |
| HBJFQ | route not resolved | 21 Feb 2018, 18:4121 Feb 2018 | 21 Feb 2018, 18:42 | 20,750 ft | 1 |
| HBJFQ | route not resolved | 21 Feb 2018, 17:2921 Feb 2018 | 21 Feb 2018, 17:35 | 23,000 ft | 41 |
| HBJFQ | route not resolved | 21 Feb 2018, 08:1121 Feb 2018 | 21 Feb 2018, 08:16 | 11,300 ft | 70 |
| HBJFQ | route not resolved | 17 Feb 2018, 16:1217 Feb 2018 | 17 Feb 2018, 16:15 | 21,750 ft | no position received |
| not transmitted | route not resolved | 17 Feb 2018, 13:2717 Feb 2018 | 17 Feb 2018, 13:36 | 30,000 ft | 4 |
| HBJFQ | route not resolved | 13 Feb 2018, 07:1313 Feb 2018 | 13 Feb 2018, 07:24 | 8,750 ft | no position received |
| HBJFQ | route not resolved | 12 Feb 2018, 06:3712 Feb 2018 | 12 Feb 2018, 06:48 | 25,025 ft | no position received |
| HBJFQ | route not resolved | 8 Feb 2018, 07:128 Feb 2018 | 8 Feb 2018, 07:17 | 16,750 ft | no position received |
| HBJFQ | route not resolved | 4 Feb 2018, 18:064 Feb 2018 | 4 Feb 2018, 18:24 | 38,000 ft | no position received |
| HBJFQ | route not resolved | 2 Feb 2018, 06:232 Feb 2018 | 2 Feb 2018, 06:42 | 10,450 ft | 1,349 |
