Back to the log
Aircraft
F-HXPG
Common
The station's story
- Cumulative contact time
- 324 h
- Distinct days
- 671
- Highest captured altitude
- 36,000 ft
- 25 corrupted frame(s) excluded from this maximum
- Discovery rank
- #34,609 of 57,441
- Longest contact
- 0 h 52 min
- Contacts on this Mode S address
- 1,304 contacts on the address, 1,272 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 (677 contacts, 2022-2026)
Operator as per the registry of 29 Jul 2026; observed callsigns are the freshest measurement.
Visits
| Callsign | Route | First contact | Last contact | Altitude at end of contact | Positions |
|---|---|---|---|---|---|
| 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 |
| FHXPG | route not resolved | 1 Feb 2022, 13:281 Feb 2022 | 1 Feb 2022, 13:33 | 4,429 ft | no position received |
| FHXPG | route not resolved | 1 Feb 2022, 09:081 Feb 2022 | 1 Feb 2022, 09:41 | 28,000 ft | no position received |
| FHXPG | route not resolved | 27 Jan 2022, 14:3227 Jan 2022 | 27 Jan 2022, 14:43 | 27,000 ft | no position received |
| FHXPG | route not resolved | 27 Jan 2022, 09:4827 Jan 2022 | 27 Jan 2022, 10:00 | 30,000 ft | no position received |
| FHXPG | route not resolved | 26 Jan 2022, 18:3426 Jan 2022 | 26 Jan 2022, 18:40 | 12,825 ft | no position received |
| FHXPG | route not resolved | 26 Jan 2022, 10:4526 Jan 2022 | 26 Jan 2022, 11:24 | 30,000 ft | no position received |
| FHXPG | route not resolved | 25 Jan 2022, 18:0325 Jan 2022 | 25 Jan 2022, 18:17 | 22,000 ft | no position received |
| FHXPG | route not resolved | 24 Jan 2022, 07:1824 Jan 2022 | 24 Jan 2022, 07:31 | 27,000 ft | no position received |
| FHXPG | route not resolved | 15 Jan 2022, 08:3815 Jan 2022 | 15 Jan 2022, 08:49 | 28,000 ft | no position received |
| FHXPG | route not resolved | 14 Jan 2022, 12:5414 Jan 2022 | 14 Jan 2022, 13:04 | 27,000 ft | no position received |
| FHXPG | route not resolved | 14 Jan 2022, 10:1214 Jan 2022 | 14 Jan 2022, 10:34 | 26,050 ft | no position received |
| FHXPG | route not resolved | 14 Jan 2022, 07:1614 Jan 2022 | 14 Jan 2022, 07:31 | 25,000 ft | no position received |
| FHXPG | route not resolved | 13 Jan 2022, 12:3613 Jan 2022 | 13 Jan 2022, 13:08 | 31,000 ft | no position received |
