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 | 21 Nov 2017, 20:1921 Nov 2017 | 21 Nov 2017, 20:30 | 24,000 ft | no position received |
| FHMCT | route not resolved | 17 Nov 2017, 19:0217 Nov 2017 | 17 Nov 2017, 19:15 | 22,450 ft | no position received |
| FHMCT | route not resolved | 16 Nov 2017, 19:1516 Nov 2017 | 16 Nov 2017, 19:22 | 17,500 ft | no position received |
| FHMCT | route not resolved | 15 Nov 2017, 09:0715 Nov 2017 | 15 Nov 2017, 09:19 | 25,000 ft | no position received |
| FHMCT | route not resolved | 14 Nov 2017, 20:1314 Nov 2017 | 14 Nov 2017, 20:24 | 24,000 ft | no position received |
| FHMCT | route not resolved | 10 Nov 2017, 20:2610 Nov 2017 | 10 Nov 2017, 20:40 | 29,700 ft | no position received |
| FHMCT | route not resolved | 7 Nov 2017, 20:457 Nov 2017 | 7 Nov 2017, 20:56 | 22,000 ft | no position received |
| FHMCT | route not resolved | 7 Nov 2017, 16:497 Nov 2017 | 7 Nov 2017, 17:06 | 23,975 ft | no position received |
| FHMCT | route not resolved | 5 Nov 2017, 18:545 Nov 2017 | 5 Nov 2017, 19:09 | 24,000 ft | no position received |
| FHMCT | route not resolved | 3 Nov 2017, 19:043 Nov 2017 | 3 Nov 2017, 19:15 | 19,900 ft | no position received |
| FHMCT | route not resolved | 1 Nov 2017, 20:221 Nov 2017 | 1 Nov 2017, 20:32 | 20,000 ft | no position received |
| FHMCT | route not resolved | 28 Oct 2017, 10:5128 Oct 2017 | 28 Oct 2017, 11:04 | 25,000 ft | no position received |
| FHMCT | route not resolved | 27 Oct 2017, 20:2727 Oct 2017 | 27 Oct 2017, 20:39 | 18,000 ft | no position received |
| FHMCT | route not resolved | 27 Oct 2017, 18:3527 Oct 2017 | 27 Oct 2017, 18:50 | 23,675 ft | no position received |
| FHMCT | route not resolved | 25 Oct 2017, 09:3325 Oct 2017 | 25 Oct 2017, 09:47 | 24,000 ft | no position received |
| FHMCT | route not resolved | 20 Oct 2017, 18:5120 Oct 2017 | 20 Oct 2017, 19:03 | 22,350 ft | no position received |
| FHMCT | route not resolved | 4 Oct 2017, 19:314 Oct 2017 | 4 Oct 2017, 19:50 | 24,000 ft | no position received |
| FHMCT | route not resolved | 23 Sept 2017, 10:4923 Sept 2017 | 23 Sept 2017, 11:05 | 25,000 ft | no position received |
| FHMCT | route not resolved | 15 Sept 2017, 22:4015 Sept 2017 | 15 Sept 2017, 22:47 | 18,000 ft | no position received |
| FHMCT | route not resolved | 14 Sept 2017, 08:2214 Sept 2017 | 14 Sept 2017, 08:40 | 25,000 ft | no position received |
| FHMCT | route not resolved | 27 Aug 2017, 20:0527 Aug 2017 | 27 Aug 2017, 20:29 | 26,000 ft | no position received |
| FHMCT | route not resolved | 27 Aug 2017, 16:1127 Aug 2017 | 27 Aug 2017, 16:24 | 23,000 ft | no position received |
| FHMCT | route not resolved | 29 Jul 2017, 14:4429 Jul 2017 | 29 Jul 2017, 15:05 | 26,000 ft | no position received |
| FHMCT | route not resolved | 29 Jul 2017, 10:5229 Jul 2017 | 29 Jul 2017, 11:07 | 25,000 ft | no position received |
| FHMCT | route not resolved | 23 Jul 2017, 19:5223 Jul 2017 | 23 Jul 2017, 20:17 | 26,000 ft | no position received |
