Back to the log
Aircraft
F-HMCT
Regular
The station's story
Address not received since 14 Apr 2023. The marker states the absence, it does not say why.
- Cumulative contact time
- 76 h
- Distinct days
- 205
- Highest captured altitude
- 35,025 ft
- 2 corrupted frame(s) excluded from this maximum
- Discovery rank
- #261 of 57,065
- Longest contact
- 0 h 46 min
Same airframe, also seen as
- 9A-LANfrom 20 Sept 2023 to 2 Aug 2026 · 42 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 |
|---|---|---|---|---|---|
| FHMCT | route not resolved | 12 Feb 2020, 15:2712 Feb 2020 | 12 Feb 2020, 15:38 | 27,000 ft | no position received |
| FHMCT | route not resolved | 8 Jan 2020, 15:008 Jan 2020 | 8 Jan 2020, 15:16 | 18,000 ft | no position received |
| FHMCT | route not resolved | 8 Jan 2020, 12:528 Jan 2020 | 8 Jan 2020, 13:05 | 5,650 ft | no position received |
| FHMCT | route not resolved | 28 Dec 2019, 14:3528 Dec 2019 | 28 Dec 2019, 14:57 | 24,000 ft | no position received |
| FHMCT | route not resolved | 23 Dec 2019, 11:2723 Dec 2019 | 23 Dec 2019, 11:39 | 16,000 ft | no position received |
| FHMCT | route not resolved | 14 Dec 2019, 15:4614 Dec 2019 | 14 Dec 2019, 16:01 | 18,000 ft | no position received |
| FHMCT | route not resolved | 3 Nov 2019, 15:563 Nov 2019 | 3 Nov 2019, 16:09 | 26,000 ft | no position received |
| FHMCT | route not resolved | 6 Oct 2019, 17:356 Oct 2019 | 6 Oct 2019, 17:46 | 20,000 ft | no position received |
| FHMCT | route not resolved | 23 Sept 2019, 10:4323 Sept 2019 | 23 Sept 2019, 10:50 | 27,000 ft | no position received |
| FHMCT | route not resolved | 4 Sept 2019, 15:094 Sept 2019 | 4 Sept 2019, 15:27 | 18,000 ft | no position received |
| FHMCT | route not resolved | 4 Sept 2019, 11:114 Sept 2019 | 4 Sept 2019, 11:30 | 27,000 ft | no position received |
| FHMCT | route not resolved | 23 Aug 2019, 13:0823 Aug 2019 | 23 Aug 2019, 13:42 | 26,000 ft | no position received |
| FHMCT | route not resolved | 9 Aug 2019, 14:199 Aug 2019 | 9 Aug 2019, 14:42 | 25,000 ft | no position received |
| FHMCT | route not resolved | 9 Aug 2019, 08:599 Aug 2019 | 9 Aug 2019, 09:33 | 24,000 ft | no position received |
| FHMCT | route not resolved | 8 Aug 2019, 19:568 Aug 2019 | 8 Aug 2019, 20:17 | 25,000 ft | no position received |
| FHMCT | route not resolved | 28 Jul 2019, 13:0828 Jul 2019 | 28 Jul 2019, 13:16 | 22,000 ft | no position received |
| not transmitted | route not resolved | 28 Jul 2019, 10:4028 Jul 2019 | 28 Jul 2019, 10:49 | 25,000 ft | no position received |
| FHMCT | route not resolved | 15 Jul 2019, 18:2515 Jul 2019 | 15 Jul 2019, 18:50 | 22,000 ft | no position received |
| not transmitted | route not resolved | 27 Jun 2019, 17:3027 Jun 2019 | 27 Jun 2019, 17:37 | 11,500 ft | no position received |
| FHMCT | route not resolved | 27 Jun 2019, 10:4227 Jun 2019 | 27 Jun 2019, 11:02 | 3,525 ft | no position received |
| FHMCT | route not resolved | 2 Jun 2019, 20:032 Jun 2019 | 2 Jun 2019, 20:13 | 18,000 ft | no position received |
| FHMCT | route not resolved | 24 May 2019, 10:4724 May 2019 | 24 May 2019, 10:59 | 25,000 ft | no position received |
| not transmitted | route not resolved | 5 May 2019, 18:275 May 2019 | 5 May 2019, 18:32 | 18,000 ft | no position received |
| FHMCT | route not resolved | 27 Apr 2019, 10:3727 Apr 2019 | 27 Apr 2019, 10:42 | 25,000 ft | no position received |
| FHMCT | route not resolved | 8 Apr 2019, 14:428 Apr 2019 | 8 Apr 2019, 15:02 | 18,000 ft | no position received |
