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