Not currently tracked · last seen 6h ago
- Flights observed
- 420 showing last 50
- Avg flight time
- 1h 34m
- Typical route
- GVA → LHR
- Last seen
- 6h ago
Last known area
Recent flights last 50
| Date | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|
| 2026-07-13 | FRA → GVA | Jul 13, 19:45 UTC | Jul 13, 20:35 UTC | 50m |
| 2026-07-13 | - | Jul 13, 17:40 UTC | Jul 13, 18:30 UTC | 50m |
| 2026-07-13 | ATH → GVA | Jul 13, 13:30 UTC | Jul 13, 16:10 UTC | 2h 40m |
| 2026-07-13 | GVA → ATH | Jul 13, 09:10 UTC | Jul 13, 11:20 UTC | 2h 10m |
| 2026-07-13 | - | Jul 13, 06:30 UTC | Jul 13, 07:45 UTC | 1h 15m |
| 2026-07-12 | - | Jul 12, 20:10 UTC | Jul 12, 21:25 UTC | 1h 15m |
| 2026-07-12 | - | Jul 12, 17:35 UTC | Jul 12, 18:50 UTC | 1h 15m |
| 2026-07-12 | GVA → LHR | Jul 12, 14:30 UTC | Jul 12, 15:50 UTC | 1h 20m |
| 2026-07-12 | - | Jul 12, 12:01 UTC | Jul 12, 13:15 UTC | 1h 15m |
| 2026-07-12 | - | Jul 12, 09:10 UTC | Jul 12, 10:30 UTC | 1h 20m |
| 2026-07-12 | - | Jul 12, 07:31 UTC | Jul 12, 08:05 UTC | 35m |
| 2026-07-12 | GVA → ZRH | Jul 12, 05:30 UTC | Jul 12, 06:01 UTC | 30m |
| 2026-07-12 | OPO → GVA | Jul 12, 02:10 UTC | Jul 12, 04:05 UTC | 1h 55m |
| 2026-07-11 | GVA → OPO | Jul 11, 19:40 UTC | Jul 11, 21:40 UTC | 2h 0m |
| 2026-07-11 | LHR → GVA | Jul 11, 17:15 UTC | Jul 11, 18:30 UTC | 1h 15m |
| 2026-07-11 | GVA → LHR | Jul 11, 14:50 UTC | Jul 11, 16:10 UTC | 1h 20m |
| 2026-07-11 | - | Jul 11, 10:05 UTC | Jul 11, 13:30 UTC | 3h 25m |
| 2026-07-11 | GVA → AYT | Jul 11, 05:35 UTC | Jul 11, 08:40 UTC | 3h 5m |
| 2026-07-10 | - | Jul 10, 15:40 UTC | Jul 10, 16:55 UTC | 1h 15m |
| 2026-07-10 | - | Jul 10, 11:45 UTC | Jul 10, 13:00 UTC | 1h 15m |
| 2026-07-10 | - | Jul 10, 07:55 UTC | Jul 10, 10:15 UTC | 2h 20m |
| 2026-07-10 | GVA → ARN | Jul 10, 04:30 UTC | Jul 10, 06:50 UTC | 2h 20m |
| 2026-07-09 | FRA → GVA | Jul 9, 20:00 UTC | Jul 9, 20:55 UTC | 55m |
| 2026-07-09 | GVA → FRA | Jul 9, 17:15 UTC | Jul 9, 18:10 UTC | 55m |
| 2026-07-09 | - | Jul 9, 08:55 UTC | Jul 9, 10:05 UTC | 1h 10m |
| 2026-07-09 | GVA → LHR | Jul 9, 05:50 UTC | Jul 9, 07:05 UTC | 1h 15m |
| 2026-07-08 | - | Jul 8, 10:05 UTC | Jul 8, 10:35 UTC | 30m |
| 2026-07-08 | ZRH → ZRH | Jul 8, 09:40 UTC | Jul 8, 09:45 UTC | 5m |
| 2026-07-07 | - | Jul 7, 18:00 UTC | Jul 7, 19:40 UTC | 1h 40m |
| 2026-07-07 | ZRH → WAW | Jul 7, 15:25 UTC | Jul 7, 17:05 UTC | 1h 40m |
| 2026-07-07 | DUB → ZRH | Jul 7, 12:30 UTC | Jul 7, 14:20 UTC | 1h 50m |
| 2026-07-07 | ZRH → DUB | Jul 7, 09:15 UTC | Jul 7, 11:15 UTC | 2h 0m |
| 2026-07-07 | - | Jul 7, 01:05 UTC | Jul 7, 04:55 UTC | 3h 50m |
| 2026-07-06 | - | Jul 6, 20:15 UTC | Jul 6, 23:30 UTC | 3h 15m |
| 2026-07-06 | ZRH → ZRH | Jul 6, 11:00 UTC | Jul 6, 12:10 UTC | 1h 10m |
| 2026-07-05 | - | Jul 5, 14:25 UTC | Jul 5, 16:00 UTC | 1h 35m |
| 2026-07-05 | - | Jul 5, 11:25 UTC | Jul 5, 13:05 UTC | 1h 40m |
| 2026-07-05 | VCE → ZRH | Jul 5, 08:55 UTC | Jul 5, 09:55 UTC | 1h 0m |
| 2026-07-05 | ZRH → VCE | Jul 5, 06:50 UTC | Jul 5, 07:30 UTC | 40m |
| 2026-07-04 | - | Jul 4, 15:35 UTC | Jul 4, 19:25 UTC | 3h 50m |
| 2026-07-04 | - | Jul 4, 10:40 UTC | Jul 4, 13:55 UTC | 3h 15m |
| 2026-07-04 | - | Jul 4, 07:45 UTC | Jul 4, 08:50 UTC | 1h 5m |
| 2026-07-04 | ZRH → PRG | Jul 4, 05:40 UTC | Jul 4, 06:40 UTC | 1h 0m |
| 2026-07-03 | - | Jul 3, 13:10 UTC | Jul 3, 14:55 UTC | 1h 45m |
| 2026-07-03 | - | Jul 3, 10:15 UTC | Jul 3, 11:50 UTC | 1h 35m |
| 2026-07-02 | BER → ZRH | Jul 2, 09:00 UTC | Jul 2, 10:00 UTC | 1h 0m |
| 2026-07-02 | ZRH → BER | Jul 2, 06:30 UTC | Jul 2, 07:45 UTC | 1h 15m |
| 2026-07-01 | - | Jul 1, 18:35 UTC | Jul 1, 19:50 UTC | 1h 15m |
| 2026-07-01 | - | Jul 1, 16:10 UTC | Jul 1, 17:30 UTC | 1h 20m |
| 2026-07-01 | ZRH → ZRH | Jul 1, 15:15 UTC | Jul 1, 15:30 UTC | 15m |
Specifications
| Registration | HB-JCB |
| Aircraft type | AIRBUS A220-300 (BCS3) |
| Mode-S code | 4B17F9 · 22613771 (octal) |
Looking for transponder-level data? View the Mode-S 4B17F9 page for country allocation, callsign history, and ADS-B signal details.
HB-JCB frequently asked
What type of aircraft is HB-JCB?
HB-JCB is a AIRBUS A220-300 (ICAO type code BCS3).
What is the Mode-S transponder code for HB-JCB?
HB-JCB broadcasts on Mode-S (ICAO 24-bit) address 4B17F9 (octal 22613771). View the transponder page.
What route does HB-JCB typically fly?
HB-JCB most frequently flies between GVA and LHR based on observed flights.
Where is HB-JCB right now?
HB-JCB is not currently being tracked; last seen 6h ago.