Back to the log
Aircraft
F-JRKK
Regular
Identity resolved on 13 Aug 2026: the aircraft was too recent for the registry at the time of the first contact, on 6 Apr 2016. What this page shows comes from a later registry; each contact keeps what was known on the day it was heard.
- Mode S hex
- 380F5C
- Manufacturer
- Tecnam
- Serial number
- not in the registry
- Year built
- not in the registry
- Operator
- not in the registry
- Country of registration
France
- First contact
- 6 Apr 2016, 11:30
- Last contact
- 15 May 2025, 12:46
- Logged visits
- 1,703
The station's story
- Cumulative contact time
- 441 h
- Distinct days
- 923
- Highest captured altitude
- 13,400 ft
- 7 corrupted frame(s) excluded from this maximum
- Discovery rank
- #1,442 of 57,382
- Longest contact
- 1 h 45 min
Visits
| Callsign | Route | First contact | Last contact | Altitude at end of contact | Positions |
|---|---|---|---|---|---|
| not transmitted | route not resolved | 16 Feb 2019, 12:0816 Feb 2019 | 16 Feb 2019, 12:14 | 2,700 ft | no position received |
| FJRKK | route not resolved | 16 Feb 2019, 10:2716 Feb 2019 | 16 Feb 2019, 10:37 | 6,000 ft | no position received |
| FJRKK | route not resolved | 15 Feb 2019, 14:5215 Feb 2019 | 15 Feb 2019, 15:08 | 5,000 ft | no position received |
| not transmitted | route not resolved | 15 Feb 2019, 13:3615 Feb 2019 | 15 Feb 2019, 13:40 | 2,800 ft | no position received |
| FJRKK | route not resolved | 15 Feb 2019, 09:4515 Feb 2019 | 15 Feb 2019, 10:04 | 2,700 ft | no position received |
| FJRKK | route not resolved | 14 Feb 2019, 17:0314 Feb 2019 | 14 Feb 2019, 17:19 | 5,300 ft | no position received |
| FJRKK | route not resolved | 14 Feb 2019, 15:3514 Feb 2019 | 14 Feb 2019, 15:51 | 2,500 ft | no position received |
| FJRKK | route not resolved | 14 Feb 2019, 12:4414 Feb 2019 | 14 Feb 2019, 12:52 | 2,200 ft | no position received |
| FJRKK | route not resolved | 13 Feb 2019, 15:0813 Feb 2019 | 13 Feb 2019, 15:20 | 2,700 ft | no position received |
| FJRKK | route not resolved | 13 Feb 2019, 12:0413 Feb 2019 | 13 Feb 2019, 12:16 | 3,100 ft | no position received |
| FJRKK | route not resolved | 13 Feb 2019, 10:1113 Feb 2019 | 13 Feb 2019, 10:50 | 2,800 ft | no position received |
| not transmitted | route not resolved | 12 Feb 2019, 14:3112 Feb 2019 | 12 Feb 2019, 14:31 | 2,600 ft | no position received |
| not transmitted | route not resolved | 12 Feb 2019, 13:4712 Feb 2019 | 12 Feb 2019, 13:47 | 2,600 ft | no position received |
| FJRKK | route not resolved | 12 Feb 2019, 12:5212 Feb 2019 | 12 Feb 2019, 13:00 | 4,900 ft | no position received |
| FJRKK | route not resolved | 12 Feb 2019, 09:2712 Feb 2019 | 12 Feb 2019, 09:41 | 2,800 ft | no position received |
| FJRKK | route not resolved | 8 Feb 2019, 16:018 Feb 2019 | 8 Feb 2019, 16:22 | 5,800 ft | no position received |
| FJRKK | route not resolved | 6 Feb 2019, 17:046 Feb 2019 | 6 Feb 2019, 17:13 | 2,900 ft | no position received |
| FJRKK | route not resolved | 6 Feb 2019, 15:406 Feb 2019 | 6 Feb 2019, 16:14 | 9,900 ft | no position received |
| FJRKK | route not resolved | 5 Feb 2019, 16:185 Feb 2019 | 5 Feb 2019, 16:23 | not transmitted | no position received |
| FJRKK | route not resolved | 16 Jan 2019, 14:4016 Jan 2019 | 16 Jan 2019, 14:46 | 6,000 ft | no position received |
| not transmitted | route not resolved | 16 Jan 2019, 10:4816 Jan 2019 | 16 Jan 2019, 11:02 | 3,200 ft | no position received |
| not transmitted | route not resolved | 15 Jan 2019, 10:1515 Jan 2019 | 15 Jan 2019, 10:18 | not transmitted | no position received |
| FJRKK | route not resolved | 11 Jan 2019, 14:3311 Jan 2019 | 11 Jan 2019, 15:06 | 3,100 ft | no position received |
| FJRKK | route not resolved | 6 Jan 2019, 15:276 Jan 2019 | 6 Jan 2019, 15:37 | 2,600 ft | no position received |
| FJRKK | route not resolved | 27 Dec 2018, 14:4427 Dec 2018 | 27 Dec 2018, 15:08 | 3,000 ft | no position received |