Back to the log
Aircraft
3A-MAJ
Uncommonnot seen for 9 years
The station's story
Address not received since 8 Jul 2017. The marker states the absence, it does not say why.
- Cumulative contact time
- 8 h
- Distinct days
- 26
- Highest captured altitude
- 13,000 ft
- Discovery rank
- #19,951 of 57,065
- Longest contact
- 0 h 52 min
Same airframe, also seen as
- F-HMCRfrom 24 Feb 2018 to 25 Mar 2019 · 55 contacts
- 3A-MAJfrom 1 Oct 2019 to 7 Aug 2026 · 25 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 |
|---|---|---|---|---|---|
| 3AMAJ | route not resolved | 20 Jan 2017, 14:3520 Jan 2017 | 20 Jan 2017, 14:38 | 3,125 ft | no position received |
| 3AMAJ | route not resolved | 19 Jan 2017, 14:4719 Jan 2017 | 19 Jan 2017, 14:55 | 1,275 ft | no position received |
| 3AMAJ | route not resolved | 19 Jan 2017, 12:1419 Jan 2017 | 19 Jan 2017, 13:05 | 12,725 ft | no position received |
| 3AMAJ | route not resolved | 19 Jan 2017, 11:0819 Jan 2017 | 19 Jan 2017, 11:31 | 10,750 ft | no position received |
| not transmitted | route not resolved | 18 Jan 2017, 17:1218 Jan 2017 | 18 Jan 2017, 17:12 | not transmitted | no position received |
| 3AMAJ | route not resolved | 18 Jan 2017, 09:5318 Jan 2017 | 18 Jan 2017, 10:13 | 11,550 ft | no position received |
| 3AMAJ | route not resolved | 17 Jan 2017, 15:0417 Jan 2017 | 17 Jan 2017, 15:56 | 4,450 ft | no position received |
| 3AMAJ | route not resolved | 16 Jan 2017, 14:1616 Jan 2017 | 16 Jan 2017, 14:21 | 1,525 ft | no position received |
| 3AMAJ | route not resolved | 16 Jan 2017, 09:5116 Jan 2017 | 16 Jan 2017, 10:16 | 12,850 ft | no position received |
| 3AMAJ | route not resolved | 16 Jan 2017, 09:0416 Jan 2017 | 16 Jan 2017, 09:05 | 1,500 ft | no position received |
| 3AMAJ | route not resolved | 15 Jan 2017, 14:4615 Jan 2017 | 15 Jan 2017, 14:51 | 1,425 ft | no position received |
| 3AMAJ | route not resolved | 15 Jan 2017, 10:4415 Jan 2017 | 15 Jan 2017, 11:09 | 13,000 ft | no position received |
| not transmitted | route not resolved | 15 Jan 2017, 10:0615 Jan 2017 | 15 Jan 2017, 10:06 | not transmitted | no position received |
| 3AMAJ | route not resolved | 2 Jan 2017, 12:142 Jan 2017 | 2 Jan 2017, 12:55 | 2,875 ft | no position received |
| not transmitted | route not resolved | 31 Dec 2016, 15:1631 Dec 2016 | 31 Dec 2016, 15:18 | 3,175 ft | no position received |
| 3AMAJ | route not resolved | 31 Dec 2016, 14:1531 Dec 2016 | 31 Dec 2016, 14:34 | 12,400 ft | no position received |
| not transmitted | route not resolved | 23 Dec 2016, 15:2823 Dec 2016 | 23 Dec 2016, 15:29 | 3,200 ft | no position received |
| not transmitted | route not resolved | 23 Dec 2016, 10:3623 Dec 2016 | 23 Dec 2016, 10:38 | 3,575 ft | no position received |
| not transmitted | route not resolved | 22 Dec 2016, 14:4222 Dec 2016 | 22 Dec 2016, 14:43 | 3,875 ft | no position received |
| 3AMAJ | route not resolved | 22 Dec 2016, 13:3822 Dec 2016 | 22 Dec 2016, 13:39 | 3,650 ft | no position received |
| not transmitted | route not resolved | 18 Dec 2016, 16:5618 Dec 2016 | 18 Dec 2016, 16:59 | 3,275 ft | no position received |
| 3AMAJ | route not resolved | 18 Dec 2016, 11:2618 Dec 2016 | 18 Dec 2016, 11:31 | 5,600 ft | no position received |
| not transmitted | route not resolved | 16 Dec 2016, 14:1916 Dec 2016 | 16 Dec 2016, 14:19 | 3,075 ft | no position received |
