Back to the log
Aircraft
F-UJCH
Common
Identity resolved on 13 Aug 2026: the aircraft was too recent for the registry at the time of the first contact, on 26 Jul 2019. What this page shows comes from a later registry; each contact keeps what was known on the day it was heard.
- Mode S hex
- 3B75A8
- Manufacturer
- Airbus
- Serial number
- 1808
- Year built
- 20179 years old
- Operator
- not in the registry
- Country of registration
France- First contact
- 26 Jul 2019, 09:30
- Last contact
- 25 Aug 2026, 11:18
- Logged visits
- 560
The station's story
- Cumulative contact time
- 209 h
- Distinct days
- 345
- Highest captured altitude
- 41,500 ft
- Discovery rank
- #35,476 of 60,404
- Longest contact
- 3 h 56 min
- Contacts on this Mode S address
- 569 contacts on the address, 560 under this registration: the address has carried several identities over time.
Same airframe, also seen as
- EC-338from 14 Jun 2019 to 28 Mar 2020 · 4 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.
Observed callsigns
FAF (160 contacts, 2019-2026) · CTM (64 contacts, 2020-2026) · VLT (9 contacts, 2019-2021)
Operator as per the registry of 12 Oct 2026; observed callsigns are the freshest measurement.
Visits
| Callsign | Route | First contact | Last contact | Altitude at end of contact | Positions |
|---|---|---|---|---|---|
| VANT36 | route not resolved | 4 Apr 2023, 22:564 Apr 2023 | 4 Apr 2023, 23:00 | 20,700 ft | 233 |
| VANT36 | route not resolved | 4 Apr 2023, 20:244 Apr 2023 | 4 Apr 2023, 20:29 | 28,500 ft | 184 |
| VALIANT3 | route not resolved | 3 Apr 2023, 08:513 Apr 2023 | 3 Apr 2023, 08:57 | 27,500 ft | 215 |
| VANT91 | route not resolved | 1 Apr 2023, 11:091 Apr 2023 | 1 Apr 2023, 11:54 | 27,700 ft | 2,879 |
| VANT91 | route not resolved | 1 Apr 2023, 07:021 Apr 2023 | 1 Apr 2023, 07:42 | 33,000 ft | 3,488 |
| RMUS36 | route not resolved | 31 Mar 2023, 15:0131 Mar 2023 | 31 Mar 2023, 15:13 | 23,750 ft | 681 |
| RMUS36 | route not resolved | 31 Mar 2023, 13:5131 Mar 2023 | 31 Mar 2023, 14:02 | 28,500 ft | 422 |
| ROMUS35 | route not resolved | 30 Mar 2023, 22:5230 Mar 2023 | 30 Mar 2023, 22:55 | 20,425 ft | 45 |
| ROMUS35 | route not resolved | 30 Mar 2023, 19:4530 Mar 2023 | 30 Mar 2023, 19:50 | 28,500 ft | 203 |
| ROMUS35 | route not resolved | 18 Jan 2023, 08:4118 Jan 2023 | 18 Jan 2023, 11:50 | 15,600 ft | 10,115 |
| VLNT35 | route not resolved | 17 Jan 2023, 21:3617 Jan 2023 | 17 Jan 2023, 21:47 | 22,225 ft | 630 |
| VLNT35 | route not resolved | 17 Jan 2023, 18:3217 Jan 2023 | 17 Jan 2023, 18:38 | 28,500 ft | 423 |
| ROMUS35 | route not resolved | 17 Jan 2023, 08:5317 Jan 2023 | 17 Jan 2023, 10:54 | 27,100 ft | 8,164 |
| VANT35 | route not resolved | 16 Jan 2023, 08:5916 Jan 2023 | 16 Jan 2023, 12:39 | 22,225 ft | 11,822 |
| VALT35 | route not resolved | 12 Jan 2023, 23:0312 Jan 2023 | 12 Jan 2023, 23:14 | 17,425 ft | 494 |
| VANT55 | route not resolved | 11 Jan 2023, 07:4011 Jan 2023 | 11 Jan 2023, 07:51 | 26,775 ft | 689 |
| VALNT36 | route not resolved | 10 Jan 2023, 23:0410 Jan 2023 | 10 Jan 2023, 23:11 | 20,250 ft | 478 |
| VALNT36 | route not resolved | 10 Jan 2023, 20:4710 Jan 2023 | 10 Jan 2023, 20:51 | 24,500 ft | 233 |
| VANT35 | route not resolved | 9 Jan 2023, 08:349 Jan 2023 | 9 Jan 2023, 10:53 | 19,475 ft | 7,738 |
| VALNT35 | route not resolved | 6 Jan 2023, 11:516 Jan 2023 | 6 Jan 2023, 11:52 | 25,150 ft | no position received |
| FAF4130 | route not resolved | 4 Jan 2023, 18:134 Jan 2023 | 4 Jan 2023, 18:38 | 21,650 ft | 1,734 |
| FAF4130 | route not resolved | 4 Jan 2023, 08:444 Jan 2023 | 4 Jan 2023, 09:10 | 38,000 ft | 2,106 |
| VALNT37 | route not resolved | 3 Jan 2023, 22:073 Jan 2023 | 3 Jan 2023, 22:11 | 22,450 ft | 264 |
| VALNT37 | route not resolved | 3 Jan 2023, 20:193 Jan 2023 | 3 Jan 2023, 20:26 | 28,500 ft | no position received |
| VANT91 | route not resolved | 19 Dec 2022, 15:2119 Dec 2022 | 19 Dec 2022, 16:09 | 24,550 ft | 3,300 |
