Back to the log
Aircraft
F-HBPC
21 of the 78 contacts seen on this address carry an uncertain identity (corrupted frames from neighbours, flagged by the detectors). The figures on this page distinguish contacts attributable to the airframe from contacts on the address; the rarity badge is suspended.
The station's story
Address not received since 26 Sept 2017. The marker states the absence, it does not say why.
- Cumulative contact time
- 20 h
- Distinct days
- 40
- Highest captured altitude
- 24,300 ft
- 21 corrupted frame(s) excluded from this maximum
- Discovery rank
- #3,486 of 57,065
- Longest contact
- 0 h 50 min
Observed callsigns
AFR (1 contacts, 2017)
Operator as per the registry of 21.07.2026; observed callsigns are the freshest measurement.
Visits
| Callsign | Route | First contact | Last contact | Altitude at end of contact | Positions |
|---|---|---|---|---|---|
| AFR98CZ | route not resolved | 26 Sept 2017, 07:1126 Sept 2017 | 26 Sept 2017, 07:44 | 34,000 ft | no position received |
| FHBPC | route not resolved | 25 Sept 2017, 15:0525 Sept 2017 | 25 Sept 2017, 15:27 | 28,925 ft | no position received |
| FHBPC | route not resolved | 25 Sept 2017, 14:2725 Sept 2017 | 25 Sept 2017, 14:32 | 1,400 ft | no position received |
| FHBPC | route not resolved | 25 Sept 2017, 10:2825 Sept 2017 | 25 Sept 2017, 10:47 | 5,300 ft | no position received |
| FHBPC | route not resolved | 23 Sept 2017, 15:1423 Sept 2017 | 23 Sept 2017, 15:32 | 2,500 ft | no position received |
| not transmitted | route not resolved | 4 Jul 2017, 11:424 Jul 2017 | 4 Jul 2017, 11:46 | not transmitted | no position received |
| FHBPC | route not resolved | 27 Jun 2017, 15:0027 Jun 2017 | 27 Jun 2017, 15:15 | 4,400 ft | no position received |
| not transmitted | route not resolved | 27 Jun 2017, 10:5527 Jun 2017 | 27 Jun 2017, 10:55 | not transmitted | no position received |
| not transmitted | route not resolved | 26 Jun 2017, 17:3026 Jun 2017 | 26 Jun 2017, 17:46 | 34,000 ft | no position received |
| FHBPC | route not resolved | 16 Jun 2017, 17:1916 Jun 2017 | 16 Jun 2017, 17:40 | 2,400 ft | no position received |
| FHBPC | route not resolved | 16 Jun 2017, 15:4316 Jun 2017 | 16 Jun 2017, 15:55 | 1,300 ft | no position received |
| FHBPC | route not resolved | 16 Jun 2017, 15:0116 Jun 2017 | 16 Jun 2017, 15:12 | 1,400 ft | no position received |
| FHBPC | route not resolved | 15 Jun 2017, 16:0515 Jun 2017 | 15 Jun 2017, 16:23 | 2,500 ft | no position received |
| FHBPC | route not resolved | 15 Jun 2017, 14:5415 Jun 2017 | 15 Jun 2017, 14:58 | 1,500 ft | no position received |
| FHBPC | route not resolved | 28 May 2017, 11:0228 May 2017 | 28 May 2017, 11:05 | 4,600 ft | no position received |
| FHBPC | route not resolved | 28 May 2017, 08:4628 May 2017 | 28 May 2017, 08:53 | 3,100 ft | no position received |
| FHBPC | route not resolved | 28 May 2017, 07:4028 May 2017 | 28 May 2017, 07:58 | 1,400 ft | no position received |
| FHBPC | route not resolved | 26 May 2017, 15:0526 May 2017 | 26 May 2017, 15:18 | 2,600 ft | no position received |
| FHBPC | route not resolved | 9 Apr 2017, 06:519 Apr 2017 | 9 Apr 2017, 07:17 | 4,600 ft | no position received |
| not transmitted | route not resolved | 7 Apr 2017, 14:397 Apr 2017 | 7 Apr 2017, 14:52 | 29,000 ft | no position received |
| FHBPC | route not resolved | 7 Apr 2017, 12:537 Apr 2017 | 7 Apr 2017, 13:26 | 1,800 ft | no position received |
| FHBPC | route not resolved | 28 Mar 2017, 07:1228 Mar 2017 | 28 Mar 2017, 07:47 | 37,975 ft | no position received |
| FHBPC | route not resolved | 27 Mar 2017, 09:0127 Mar 2017 | 27 Mar 2017, 09:25 | 33,650 ft | no position received |
| AF211SD | route not resolved | 9 Dec 2016, 11:439 Dec 2016 | 9 Dec 2016, 12:09 | 34,000 ft | no position received |
| FHBPC | route not resolved | 8 Dec 2016, 16:538 Dec 2016 | 8 Dec 2016, 17:04 | 31,525 ft | no position received |
