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.
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,228
- Longest contact
- 1 h 45 min
Visits
| Callsign | Route | First contact | Last contact | Altitude at end of contact | Positions |
|---|---|---|---|---|---|
| FJRKK | route not resolved | 22 Oct 2023, 11:1622 Oct 2023 | 22 Oct 2023, 11:22 | 4,300 ft | no position received |
| FJRKK | route not resolved | 15 Oct 2023, 17:3415 Oct 2023 | 15 Oct 2023, 18:20 | not transmitted | no position received |
| FJRKK | route not resolved | 11 Oct 2023, 15:1411 Oct 2023 | 11 Oct 2023, 15:34 | 2,900 ft | no position received |
| FJRKK | route not resolved | 11 Oct 2023, 12:4711 Oct 2023 | 11 Oct 2023, 13:02 | 2,700 ft | no position received |
| FJRKK | route not resolved | 11 Oct 2023, 10:5311 Oct 2023 | 11 Oct 2023, 11:18 | 2,900 ft | no position received |
| not transmitted | route not resolved | 11 Oct 2023, 09:5411 Oct 2023 | 11 Oct 2023, 10:00 | 2,800 ft | no position received |
| FJRKK | route not resolved | 11 Oct 2023, 08:4011 Oct 2023 | 11 Oct 2023, 08:46 | 2,800 ft | no position received |
| FJRKK | route not resolved | 10 Oct 2023, 10:0010 Oct 2023 | 10 Oct 2023, 10:18 | 2,900 ft | no position received |
| FJRKK | route not resolved | 8 Oct 2023, 16:468 Oct 2023 | 8 Oct 2023, 17:16 | 2,900 ft | no position received |
| FJRKK | route not resolved | 8 Oct 2023, 15:598 Oct 2023 | 8 Oct 2023, 16:13 | 6,200 ft | no position received |
| FJRKK | route not resolved | 8 Oct 2023, 14:178 Oct 2023 | 8 Oct 2023, 14:50 | 2,900 ft | no position received |
| not transmitted | route not resolved | 8 Oct 2023, 13:238 Oct 2023 | 8 Oct 2023, 13:30 | 2,500 ft | no position received |
| FJRKK | route not resolved | 8 Oct 2023, 12:438 Oct 2023 | 8 Oct 2023, 12:50 | 2,700 ft | no position received |
| FJRKK | route not resolved | 8 Oct 2023, 10:218 Oct 2023 | 8 Oct 2023, 10:45 | 3,600 ft | no position received |
| FJRKK | route not resolved | 7 Oct 2023, 15:187 Oct 2023 | 7 Oct 2023, 15:24 | 5,200 ft | no position received |
| FJRKK | route not resolved | 7 Oct 2023, 13:237 Oct 2023 | 7 Oct 2023, 13:45 | 2,800 ft | no position received |
| FJRKK | route not resolved | 7 Oct 2023, 11:047 Oct 2023 | 7 Oct 2023, 11:23 | 2,600 ft | no position received |
| FJRKK | route not resolved | 7 Oct 2023, 09:347 Oct 2023 | 7 Oct 2023, 09:42 | 2,700 ft | no position received |
| FJRKK | route not resolved | 7 Oct 2023, 08:417 Oct 2023 | 7 Oct 2023, 08:51 | 3,600 ft | no position received |
| FJRKK | route not resolved | 5 Oct 2023, 08:585 Oct 2023 | 5 Oct 2023, 09:16 | 2,800 ft | no position received |
| FJRKK | route not resolved | 4 Oct 2023, 10:554 Oct 2023 | 4 Oct 2023, 11:22 | 2,800 ft | no position received |
| FJRKK | route not resolved | 1 Oct 2023, 17:511 Oct 2023 | 1 Oct 2023, 18:00 | 2,900 ft | no position received |
| FJRKK | route not resolved | 1 Oct 2023, 16:571 Oct 2023 | 1 Oct 2023, 17:07 | 3,500 ft | no position received |
| not transmitted | route not resolved | 1 Oct 2023, 12:191 Oct 2023 | 1 Oct 2023, 12:38 | not transmitted | no position received |
| FJRKK | route not resolved | 1 Oct 2023, 11:201 Oct 2023 | 1 Oct 2023, 11:32 | not transmitted | no position received |