Back to the log
Aircraft
F-HFMC
Uncommonnot seen for 5 years
The station's story
Address not received since 11 Sept 2020. The marker states the absence, it does not say why.
- Cumulative contact time
- 50 h
- Distinct days
- 150
- Highest captured altitude
- 34,975 ft
- 1 corrupted frame(s) excluded from this maximum
- Discovery rank
- #20,777 of 57,241
- Longest contact
- 1 h 1 min
- Contacts on this Mode S address
- 187 contacts on the address, 179 under this registration: the address has carried several identities over time.
Observed callsigns
VDR (7 contacts, 2018)
Operator as per the registry of 12 Aug 2026; observed callsigns are the freshest measurement.
Visits
| Callsign | Route | First contact | Last contact | Altitude at end of contact | Positions |
|---|---|---|---|---|---|
| FHFMC | route not resolved | 25 Sept 2018, 16:4525 Sept 2018 | 25 Sept 2018, 16:59 | 24,000 ft | no position received |
| not transmitted | route not resolved | 22 Sept 2018, 18:1522 Sept 2018 | 22 Sept 2018, 18:15 | not transmitted | no position received |
| FHFMC | route not resolved | 22 Sept 2018, 14:5122 Sept 2018 | 22 Sept 2018, 15:12 | 29,650 ft | no position received |
| FHFMC | route not resolved | 16 Sept 2018, 17:2716 Sept 2018 | 16 Sept 2018, 17:42 | 24,000 ft | no position received |
| not transmitted | route not resolved | 13 Sept 2018, 10:2913 Sept 2018 | 13 Sept 2018, 10:30 | 25,000 ft | no position received |
| FHFMC | route not resolved | 3 Sept 2018, 17:333 Sept 2018 | 3 Sept 2018, 18:05 | 28,000 ft | no position received |
| FHFMC | route not resolved | 31 Aug 2018, 10:2831 Aug 2018 | 31 Aug 2018, 10:33 | 29,000 ft | no position received |
| FHFMC | route not resolved | 26 Jul 2018, 11:4326 Jul 2018 | 26 Jul 2018, 11:55 | 24,000 ft | no position received |
| FHFMC | route not resolved | 25 Jun 2018, 17:2725 Jun 2018 | 25 Jun 2018, 17:40 | 24,000 ft | no position received |
| FHFMC | route not resolved | 19 Jun 2018, 18:4819 Jun 2018 | 19 Jun 2018, 18:55 | 19,000 ft | no position received |
| FHFMC | route not resolved | 17 Jun 2018, 17:5617 Jun 2018 | 17 Jun 2018, 18:32 | 24,925 ft | no position received |
| FHFMC | route not resolved | 15 Jun 2018, 09:0715 Jun 2018 | 15 Jun 2018, 09:35 | 27,000 ft | no position received |
| FHFMC | route not resolved | 12 Jun 2018, 11:5212 Jun 2018 | 12 Jun 2018, 12:03 | 24,000 ft | no position received |
| FHFMC | route not resolved | 29 May 2018, 16:1029 May 2018 | 29 May 2018, 16:22 | 24,000 ft | no position received |
| FHFMC | route not resolved | 12 May 2018, 17:0212 May 2018 | 12 May 2018, 17:39 | 24,375 ft | no position received |
| FHFMC | route not resolved | 10 May 2018, 09:5410 May 2018 | 10 May 2018, 10:21 | 29,000 ft | no position received |
| FHFMC | route not resolved | 9 May 2018, 16:249 May 2018 | 9 May 2018, 16:37 | 24,000 ft | no position received |
| FHFMC | route not resolved | 6 May 2018, 18:596 May 2018 | 6 May 2018, 19:12 | 24,000 ft | no position received |
| not transmitted | route not resolved | 5 May 2018, 10:185 May 2018 | 5 May 2018, 10:18 | 25,000 ft | no position received |
| FHFMC | route not resolved | 29 Apr 2018, 15:1529 Apr 2018 | 29 Apr 2018, 15:29 | 24,000 ft | no position received |
| FHFMC | route not resolved | 12 Apr 2018, 18:3212 Apr 2018 | 12 Apr 2018, 19:17 | 15,975 ft | no position received |
| FHFMC | route not resolved | 2 Apr 2018, 18:082 Apr 2018 | 2 Apr 2018, 18:12 | 24,000 ft | no position received |
| not transmitted | route not resolved | 2 Apr 2018, 11:082 Apr 2018 | 2 Apr 2018, 11:09 | 25,000 ft | no position received |
| FHFMC | route not resolved | 2 Apr 2018, 08:182 Apr 2018 | 2 Apr 2018, 08:22 | 24,000 ft | no position received |
| not transmitted | route not resolved | 29 Mar 2018, 12:3029 Mar 2018 | 29 Mar 2018, 12:37 | 24,000 ft | no position received |
