Back to the log
Aircraft
F-HXPG
Common
The station's story
- Cumulative contact time
- 343 h
- Distinct days
- 706
- Highest captured altitude
- 36,000 ft
- 25 corrupted frame(s) excluded from this maximum
- Discovery rank
- #34,834 of 60,659
- Longest contact
- 0 h 58 min
- Contacts on this Mode S address
- 1,373 contacts on the address, 1,341 under this registration: the address has carried several identities over time.
Same airframe, also seen as
- I-FXRGfrom 6 Apr 2016 to 14 May 2019 · 129 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
OYO (739 contacts, 2022-2026)
Operator as per the registry of 9 Nov 2026; observed callsigns are the freshest measurement.
Visits
| Callsign | Route | First contact | Last contact | Altitude at end of contact | Positions |
|---|---|---|---|---|---|
| OYO001 | route not resolved | 10 Mar 2022, 11:3410 Mar 2022 | 10 Mar 2022, 11:46 | 32,000 ft | no position received |
| OYO001 | route not resolved | 10 Mar 2022, 06:3010 Mar 2022 | 10 Mar 2022, 06:42 | 29,200 ft | no position received |
| OYO001 | route not resolved | 10 Mar 2022, 03:3110 Mar 2022 | 10 Mar 2022, 03:41 | 34,000 ft | no position received |
| OYO001 | route not resolved | 9 Mar 2022, 06:029 Mar 2022 | 9 Mar 2022, 06:17 | 33,000 ft | no position received |
| OYO001 | route not resolved | 9 Mar 2022, 03:279 Mar 2022 | 9 Mar 2022, 04:02 | 10,350 ft | no position received |
| OYO001 | route not resolved | 8 Mar 2022, 18:528 Mar 2022 | 8 Mar 2022, 19:35 | 32,000 ft | no position received |
| OYO001 | route not resolved | 8 Mar 2022, 08:368 Mar 2022 | 8 Mar 2022, 08:50 | 32,000 ft | no position received |
| not transmitted | route not resolved | 6 Mar 2022, 20:026 Mar 2022 | 6 Mar 2022, 20:02 | 14,000 ft | no position received |
| OYO001 | route not resolved | 6 Mar 2022, 09:426 Mar 2022 | 6 Mar 2022, 09:57 | 24,000 ft | no position received |
| OYO001 | route not resolved | 3 Mar 2022, 19:373 Mar 2022 | 3 Mar 2022, 19:37 | 25,000 ft | no position received |
| OYO001 | route not resolved | 2 Mar 2022, 07:452 Mar 2022 | 2 Mar 2022, 08:13 | 24,000 ft | no position received |
| OYO001 | route not resolved | 24 Feb 2022, 08:4724 Feb 2022 | 24 Feb 2022, 09:01 | 30,000 ft | no position received |
| FHXPG | route not resolved | 23 Feb 2022, 18:4423 Feb 2022 | 23 Feb 2022, 18:45 | 7,250 ft | no position received |
| FHXPG | route not resolved | 22 Feb 2022, 13:4622 Feb 2022 | 22 Feb 2022, 13:58 | 31,000 ft | no position received |
| FHXPG | route not resolved | 22 Feb 2022, 12:0022 Feb 2022 | 22 Feb 2022, 12:18 | 30,000 ft | no position received |
| not transmitted | route not resolved | 22 Feb 2022, 08:1022 Feb 2022 | 22 Feb 2022, 08:11 | 12,600 ft | no position received |
| FHXPG | route not resolved | 19 Feb 2022, 14:4519 Feb 2022 | 19 Feb 2022, 14:54 | 22,100 ft | no position received |
| FHXPG | route not resolved | 19 Feb 2022, 07:5019 Feb 2022 | 19 Feb 2022, 08:07 | 1,275 ft | no position received |
| not transmitted | route not resolved | 19 Feb 2022, 06:1819 Feb 2022 | 19 Feb 2022, 06:19 | 28,000 ft | no position received |
| FHXPG | route not resolved | 15 Feb 2022, 12:4915 Feb 2022 | 15 Feb 2022, 13:11 | 28,000 ft | no position received |
| FHXPG | route not resolved | 15 Feb 2022, 08:4915 Feb 2022 | 15 Feb 2022, 09:00 | 1,350 ft | no position received |
| FHXPG | route not resolved | 4 Feb 2022, 14:094 Feb 2022 | 4 Feb 2022, 14:38 | 32,000 ft | no position received |
| FHXPG | route not resolved | 4 Feb 2022, 09:074 Feb 2022 | 4 Feb 2022, 09:22 | 31,000 ft | no position received |
| FHXPG | route not resolved | 4 Feb 2022, 06:214 Feb 2022 | 4 Feb 2022, 06:38 | 26,000 ft | no position received |
| not transmitted | route not resolved | 3 Feb 2022, 16:383 Feb 2022 | 3 Feb 2022, 16:38 | 10,000 ft | no position received |
