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 | 8 Jul 2017, 09:128 Jul 2017 | 8 Jul 2017, 09:19 | 3,700 ft | no position received |
| 3AMAJ | route not resolved | 8 Jul 2017, 08:278 Jul 2017 | 8 Jul 2017, 08:34 | 1,500 ft | no position received |
| 3AMAJ | route not resolved | 26 Jun 2017, 15:5326 Jun 2017 | 26 Jun 2017, 15:57 | 3,325 ft | no position received |
| 3AMAJ | route not resolved | 25 Jun 2017, 12:5825 Jun 2017 | 25 Jun 2017, 13:16 | 1,550 ft | no position received |
| 3AMAJ | route not resolved | 31 May 2017, 13:0131 May 2017 | 31 May 2017, 13:07 | 2,825 ft | no position received |
| 3AMAJ | route not resolved | 31 May 2017, 12:1331 May 2017 | 31 May 2017, 12:19 | 1,475 ft | no position received |
| 3AMAJ | route not resolved | 24 Apr 2017, 17:5624 Apr 2017 | 24 Apr 2017, 18:28 | 5,375 ft | no position received |
| not transmitted | route not resolved | 20 Apr 2017, 16:5120 Apr 2017 | 20 Apr 2017, 17:06 | 8,675 ft | no position received |
| not transmitted | route not resolved | 20 Apr 2017, 15:0520 Apr 2017 | 20 Apr 2017, 15:10 | 3,200 ft | no position received |
| not transmitted | route not resolved | 20 Apr 2017, 14:2020 Apr 2017 | 20 Apr 2017, 14:26 | 2,200 ft | no position received |
| 3AMAJ | route not resolved | 27 Feb 2017, 09:0727 Feb 2017 | 27 Feb 2017, 09:21 | 4,175 ft | no position received |
| not transmitted | route not resolved | 27 Feb 2017, 08:3227 Feb 2017 | 27 Feb 2017, 08:35 | 1,725 ft | no position received |
| not transmitted | route not resolved | 26 Feb 2017, 15:4126 Feb 2017 | 26 Feb 2017, 15:46 | 1,600 ft | no position received |
| not transmitted | route not resolved | 2 Feb 2017, 17:002 Feb 2017 | 2 Feb 2017, 17:05 | 5,550 ft | no position received |
| 3AMAJ | route not resolved | 2 Feb 2017, 09:292 Feb 2017 | 2 Feb 2017, 09:34 | 6,625 ft | no position received |
| not transmitted | route not resolved | 1 Feb 2017, 16:511 Feb 2017 | 1 Feb 2017, 16:54 | 1,625 ft | no position received |
| 3AMAJ | route not resolved | 1 Feb 2017, 16:191 Feb 2017 | 1 Feb 2017, 16:20 | 1,625 ft | no position received |
| 3AMAJ | route not resolved | 30 Jan 2017, 14:3330 Jan 2017 | 30 Jan 2017, 14:44 | 1,525 ft | no position received |
| not transmitted | route not resolved | 27 Jan 2017, 16:5327 Jan 2017 | 27 Jan 2017, 16:54 | 3,975 ft | no position received |
| 3AMAJ | route not resolved | 23 Jan 2017, 14:3923 Jan 2017 | 23 Jan 2017, 14:41 | 5,100 ft | no position received |
| not transmitted | route not resolved | 23 Jan 2017, 12:0923 Jan 2017 | 23 Jan 2017, 12:12 | 7,600 ft | no position received |
| 3AMAJ | route not resolved | 23 Jan 2017, 11:2523 Jan 2017 | 23 Jan 2017, 11:44 | 11,800 ft | no position received |
| not transmitted | route not resolved | 22 Jan 2017, 15:1722 Jan 2017 | 22 Jan 2017, 15:17 | 4,000 ft | no position received |
| 3AMAJ | route not resolved | 22 Jan 2017, 11:5622 Jan 2017 | 22 Jan 2017, 12:12 | 9,775 ft | no position received |
| not transmitted | route not resolved | 22 Jan 2017, 09:4722 Jan 2017 | 22 Jan 2017, 09:53 | 4,425 ft | no position received |
