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 | 8 Apr 2019, 11:488 Apr 2019 | 8 Apr 2019, 12:11 | 4,450 ft | no position received |
| not transmitted | route not resolved | 31 Mar 2019, 10:4931 Mar 2019 | 31 Mar 2019, 10:57 | 25,000 ft | no position received |
| FHMCT | route not resolved | 10 Mar 2019, 13:2210 Mar 2019 | 10 Mar 2019, 13:45 | 18,000 ft | no position received |
| FHMCT | route not resolved | 10 Mar 2019, 11:1310 Mar 2019 | 10 Mar 2019, 11:40 | 6,100 ft | no position received |
| FHMCT | route not resolved | 10 Feb 2019, 14:3910 Feb 2019 | 10 Feb 2019, 15:06 | 22,000 ft | no position received |
| FHMCT | route not resolved | 10 Feb 2019, 11:0610 Feb 2019 | 10 Feb 2019, 11:30 | 4,675 ft | no position received |
| FHMCT | route not resolved | 2 Feb 2019, 12:112 Feb 2019 | 2 Feb 2019, 12:27 | 18,000 ft | no position received |
| FHMCT | route not resolved | 2 Feb 2019, 10:552 Feb 2019 | 2 Feb 2019, 11:10 | 7,025 ft | no position received |
| FHMCT | route not resolved | 20 Jan 2019, 20:2020 Jan 2019 | 20 Jan 2019, 20:48 | 26,000 ft | no position received |
| FHMCT | route not resolved | 18 Jan 2019, 18:3618 Jan 2019 | 18 Jan 2019, 18:57 | 25,000 ft | no position received |
| FHMCT | route not resolved | 6 Jan 2019, 13:056 Jan 2019 | 6 Jan 2019, 13:22 | 18,000 ft | no position received |
| FHMCT | route not resolved | 6 Jan 2019, 11:156 Jan 2019 | 6 Jan 2019, 11:45 | 5,925 ft | no position received |
| FHMCT | route not resolved | 27 Dec 2018, 14:2527 Dec 2018 | 27 Dec 2018, 14:45 | 18,000 ft | no position received |
| FHMCT | route not resolved | 27 Dec 2018, 10:5227 Dec 2018 | 27 Dec 2018, 11:15 | 3,725 ft | no position received |
| FHMCT | route not resolved | 28 Nov 2018, 16:5728 Nov 2018 | 28 Nov 2018, 17:03 | 10,600 ft | no position received |
| FHMCT | route not resolved | 4 Nov 2018, 16:284 Nov 2018 | 4 Nov 2018, 16:45 | 24,000 ft | no position received |
| FHMCT | route not resolved | 27 Oct 2018, 11:1327 Oct 2018 | 27 Oct 2018, 11:22 | 25,000 ft | no position received |
| not transmitted | route not resolved | 14 Oct 2018, 19:0114 Oct 2018 | 14 Oct 2018, 19:23 | 24,000 ft | no position received |
| FHMCT | route not resolved | 12 Oct 2018, 10:1212 Oct 2018 | 12 Oct 2018, 10:35 | 2,300 ft | no position received |
| FHMCT | route not resolved | 7 Oct 2018, 19:017 Oct 2018 | 7 Oct 2018, 19:15 | 26,000 ft | no position received |
| FHMCT | route not resolved | 4 Oct 2018, 11:174 Oct 2018 | 4 Oct 2018, 11:54 | 27,000 ft | no position received |
| FHMCT | route not resolved | 30 Sept 2018, 19:4730 Sept 2018 | 30 Sept 2018, 19:55 | 20,000 ft | no position received |
| FHMCT | route not resolved | 22 Sept 2018, 10:3022 Sept 2018 | 22 Sept 2018, 10:51 | 25,000 ft | no position received |
| FHMCT | route not resolved | 26 Aug 2018, 18:4326 Aug 2018 | 26 Aug 2018, 19:04 | 18,000 ft | no position received |
| FHMCT | route not resolved | 26 Aug 2018, 15:2726 Aug 2018 | 26 Aug 2018, 15:47 | 27,000 ft | no position received |
