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 | 14 Apr 2023, 15:3514 Apr 2023 | 14 Apr 2023, 16:05 | 25,000 ft | no position received |
| FHMCT | route not resolved | 15 Jan 2023, 12:2815 Jan 2023 | 15 Jan 2023, 12:51 | 19,000 ft | no position received |
| FHMCT | route not resolved | 15 Jan 2023, 11:0115 Jan 2023 | 15 Jan 2023, 11:19 | 4,275 ft | no position received |
| FHMCT | route not resolved | 6 Jan 2023, 19:446 Jan 2023 | 6 Jan 2023, 19:57 | 26,000 ft | no position received |
| FHMCT | route not resolved | 6 Jan 2023, 17:596 Jan 2023 | 6 Jan 2023, 18:10 | 20,650 ft | no position received |
| FHMCT | route not resolved | 3 Jan 2023, 13:523 Jan 2023 | 3 Jan 2023, 14:01 | 18,000 ft | no position received |
| FHMCT | route not resolved | 2 Jan 2023, 11:392 Jan 2023 | 2 Jan 2023, 11:51 | 21,825 ft | no position received |
| FHMCT | route not resolved | 27 Dec 2022, 14:1027 Dec 2022 | 27 Dec 2022, 14:31 | 18,000 ft | no position received |
| FHMCT | route not resolved | 27 Dec 2022, 11:2327 Dec 2022 | 27 Dec 2022, 11:58 | 4,100 ft | no position received |
| FHMCT | route not resolved | 23 Dec 2022, 20:3523 Dec 2022 | 23 Dec 2022, 20:51 | 28,000 ft | no position received |
| FHMCT | route not resolved | 23 Dec 2022, 18:0523 Dec 2022 | 23 Dec 2022, 18:19 | 27,000 ft | no position received |
| FHMCT | route not resolved | 11 Dec 2022, 14:4711 Dec 2022 | 11 Dec 2022, 15:08 | 18,000 ft | no position received |
| FHMCT | route not resolved | 11 Dec 2022, 12:0311 Dec 2022 | 11 Dec 2022, 12:16 | 27,000 ft | no position received |
| FHMCT | route not resolved | 13 Nov 2022, 17:4613 Nov 2022 | 13 Nov 2022, 18:07 | 26,000 ft | no position received |
| FHMCT | route not resolved | 10 Nov 2022, 19:2810 Nov 2022 | 10 Nov 2022, 19:39 | 39,400 ft | no position received |
| FHMCT | route not resolved | 24 Oct 2022, 16:4424 Oct 2022 | 24 Oct 2022, 17:04 | 18,000 ft | no position received |
| FHMCT | route not resolved | 24 Oct 2022, 14:2424 Oct 2022 | 24 Oct 2022, 14:38 | 19,200 ft | no position received |
| FHMCT | route not resolved | 4 Sept 2022, 17:324 Sept 2022 | 4 Sept 2022, 17:49 | 18,000 ft | no position received |
| FHMCT | route not resolved | 4 Sept 2022, 15:054 Sept 2022 | 4 Sept 2022, 15:18 | 19,000 ft | no position received |
| FHMCT | route not resolved | 25 Aug 2022, 08:0925 Aug 2022 | 25 Aug 2022, 08:21 | 21,000 ft | no position received |
| FHMCT | route not resolved | 22 Aug 2022, 20:1722 Aug 2022 | 22 Aug 2022, 20:26 | 18,000 ft | no position received |
| FHMCT | route not resolved | 6 Aug 2022, 18:366 Aug 2022 | 6 Aug 2022, 18:54 | 24,000 ft | no position received |
| not transmitted | route not resolved | 5 Aug 2022, 17:205 Aug 2022 | 5 Aug 2022, 17:21 | 23,350 ft | no position received |
| FHMCT | route not resolved | 4 Aug 2022, 15:234 Aug 2022 | 4 Aug 2022, 16:02 | 28,000 ft | no position received |
| FHMCT | route not resolved | 30 Jul 2022, 15:5530 Jul 2022 | 30 Jul 2022, 16:09 | 27,000 ft | no position received |
