Not currently tracked · last seen 22h ago
- Flights observed
- 36
- Avg flight time
- 36m
- Typical route
- MUB → JNB
- Last seen
- 22h ago
Last known area
Recent flights last 36
| Date | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|
| 2026-06-09 | VFA → JNB | Jun 9, 13:00 UTC | Jun 9, 13:45 UTC | 45m |
| 2026-06-09 | JNB → VFA | Jun 9, 08:35 UTC | Jun 9, 09:15 UTC | 40m |
| 2026-06-09 | - | Jun 9, 06:40 UTC | Jun 9, 07:20 UTC | 40m |
| 2026-06-09 | - | Jun 9, 04:40 UTC | Jun 9, 05:10 UTC | 30m |
| 2026-06-08 | MUB → JNB | Jun 8, 07:00 UTC | Jun 8, 07:25 UTC | 25m |
| 2026-06-08 | MUB → JNB | Jun 8, 04:25 UTC | Jun 8, 04:45 UTC | 20m |
| 2026-06-05 | MUB → JNB | Jun 5, 14:00 UTC | Jun 5, 14:40 UTC | 40m |
| 2026-06-05 | MUB → JNB | Jun 5, 10:05 UTC | Jun 5, 10:50 UTC | 45m |
| 2026-06-04 | MUB → JNB | Jun 4, 14:50 UTC | Jun 4, 15:30 UTC | 40m |
| 2026-06-04 | MUB → JNB | Jun 4, 10:35 UTC | Jun 4, 11:30 UTC | 55m |
| 2026-06-02 | MUB → JNB | Jun 2, 14:05 UTC | Jun 2, 14:50 UTC | 45m |
| 2026-06-02 | - | Jun 2, 10:00 UTC | Jun 2, 10:45 UTC | 45m |
| 2026-05-29 | - | May 29, 13:25 UTC | May 29, 14:05 UTC | 40m |
| 2026-05-29 | - | May 29, 11:25 UTC | May 29, 12:05 UTC | 40m |
| 2026-05-28 | KIM → JNB | May 28, 13:40 UTC | May 28, 14:15 UTC | 35m |
| 2026-05-28 | KIM → JNB | May 28, 11:25 UTC | May 28, 12:05 UTC | 40m |
| 2026-05-27 | KIM → JNB | May 27, 07:05 UTC | May 27, 07:30 UTC | 25m |
| 2026-05-27 | MUB → JNB | May 27, 04:39 UTC | May 27, 05:04 UTC | 25m |
| 2026-05-26 | - | May 26, 14:00 UTC | May 26, 14:40 UTC | 40m |
| 2026-05-26 | - | May 26, 09:45 UTC | May 26, 10:29 UTC | 45m |
| 2026-05-26 | - | May 26, 07:05 UTC | May 26, 07:29 UTC | 25m |
| 2026-05-26 | - | May 26, 05:05 UTC | May 26, 05:34 UTC | 30m |
| 2026-05-25 | JNB → BFN | May 25, 12:15 UTC | May 25, 12:35 UTC | 20m |
| 2026-05-25 | JNB → BFN | May 25, 10:10 UTC | May 25, 10:35 UTC | 25m |
| 2026-05-25 | MUB → JNB | May 25, 07:00 UTC | May 25, 07:20 UTC | 20m |
| 2026-05-25 | MUB → JNB | May 25, 04:35 UTC | May 25, 05:00 UTC | 25m |
| 2026-05-24 | MUB → JNB | May 24, 14:15 UTC | May 24, 15:05 UTC | 50m |
| 2026-05-24 | MUB → JNB | May 24, 10:20 UTC | May 24, 11:00 UTC | 40m |
| 2026-05-23 | MUB → JNB | May 23, 14:00 UTC | May 23, 14:45 UTC | 45m |
| 2026-05-23 | JNB → MUB | May 23, 09:55 UTC | May 23, 10:40 UTC | 45m |
| 2026-05-22 | - | May 22, 13:55 UTC | May 22, 14:40 UTC | 45m |
| 2026-05-22 | - | May 22, 09:55 UTC | May 22, 10:45 UTC | 50m |
| 2026-05-22 | - | May 22, 07:00 UTC | May 22, 07:15 UTC | 15m |
| 2026-05-22 | - | May 22, 04:30 UTC | May 22, 04:50 UTC | 20m |
| 2026-05-21 | - | May 21, 13:40 UTC | May 21, 14:15 UTC | 35m |
| 2026-05-21 | - | May 21, 11:40 UTC | May 21, 12:15 UTC | 35m |
Specifications
| Registration | ZS-CMI |
| Aircraft type | BEECH 1900 (B190) |
| Mode-S code | 008699 · 00103231 (octal) |
Looking for transponder-level data? View the Mode-S 008699 page for country allocation, callsign history, and ADS-B signal details.
ZS-CMI frequently asked
What type of aircraft is ZS-CMI?
ZS-CMI is a BEECH 1900 (ICAO type code B190).
What is the Mode-S transponder code for ZS-CMI?
ZS-CMI broadcasts on Mode-S (ICAO 24-bit) address 008699 (octal 00103231). View the transponder page.
What route does ZS-CMI typically fly?
ZS-CMI most frequently flies between MUB and JNB based on observed flights.
Where is ZS-CMI right now?
ZS-CMI is not currently being tracked; last seen 22h ago.