Not currently tracked · last seen Jul 26, 21:45 UTC
- Flights observed
- 302 showing last 50
- Avg flight time
- 2h 23m
- Typical route
- MAA → BOM
- Last seen
- Jul 26, 21:45 UTC
Last known area
Recent flights last 50
| Date | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|
| 2026-07-26 | BOM → JED | Jul 26, 13:45 UTC | Jul 26, 21:45 UTC | 8h 0m |
| 2026-07-26 | BKK → BOM | Jul 26, 11:40 UTC | Jul 26, 12:15 UTC | 35m |
| 2026-07-26 | BKK → BOM | Jul 26, 08:05 UTC | Jul 26, 10:30 UTC | 2h 25m |
| 2026-07-26 | BOM → BKK | Jul 26, 03:45 UTC | Jul 26, 06:35 UTC | 2h 51m |
| 2026-07-26 | BOM → BKK | Jul 26, 02:30 UTC | Jul 26, 02:45 UTC | 15m |
| 2026-07-25 | JED → BOM | Jul 25, 13:35 UTC | Jul 26, 00:45 UTC | 11h 10m |
| 2026-07-25 | AMD → BOM | Jul 25, 06:45 UTC | Jul 25, 07:35 UTC | 50m |
| 2026-07-25 | BOM → AMD | Jul 25, 04:45 UTC | Jul 25, 04:55 UTC | 10m |
| 2026-07-25 | MAA → BOM | Jul 25, 02:45 UTC | Jul 25, 03:15 UTC | 30m |
| 2026-07-25 | MAA → BOM | Jul 25, 01:50 UTC | Jul 25, 02:10 UTC | 20m |
| 2026-07-24 | BOM → MAA | Jul 24, 18:20 UTC | Jul 24, 18:50 UTC | 30m |
| 2026-07-24 | BOM → MAA | Jul 24, 17:35 UTC | Jul 24, 17:45 UTC | 10m |
| 2026-07-24 | MAA → BOM | Jul 24, 13:45 UTC | Jul 24, 14:10 UTC | 25m |
| 2026-07-24 | - | Jul 24, 08:00 UTC | Jul 24, 13:00 UTC | 5h 0m |
| 2026-07-24 | MAA → BOM | Jul 24, 05:30 UTC | Jul 24, 05:50 UTC | 20m |
| 2026-07-24 | MAA → BOM | Jul 24, 04:20 UTC | Jul 24, 04:50 UTC | 30m |
| 2026-07-24 | - | Jul 24, 01:40 UTC | Jul 24, 03:15 UTC | 1h 35m |
| 2026-07-23 | - | Jul 23, 12:10 UTC | Jul 23, 12:30 UTC | 20m |
| 2026-07-23 | - | Jul 23, 10:25 UTC | Jul 23, 11:05 UTC | 40m |
| 2026-07-23 | - | Jul 23, 07:35 UTC | Jul 23, 09:30 UTC | 1h 55m |
| 2026-07-23 | IXC → BOM | Jul 23, 05:35 UTC | Jul 23, 05:55 UTC | 20m |
| 2026-07-23 | IXC → BOM | Jul 23, 03:55 UTC | Jul 23, 04:40 UTC | 45m |
| 2026-07-23 | BOM → IXC | Jul 23, 00:55 UTC | Jul 23, 02:45 UTC | 1h 50m |
| 2026-07-21 | - | Jul 21, 10:45 UTC | Jul 21, 11:15 UTC | 30m |
| 2026-07-20 | - | Jul 20, 16:40 UTC | Jul 20, 19:00 UTC | 2h 20m |
| 2026-07-20 | AMD → DEL | Jul 20, 11:25 UTC | Jul 20, 14:45 UTC | 3h 20m |
| 2026-07-19 | - | Jul 19, 23:25 UTC | Jul 20, 04:35 UTC | 5h 10m |
| 2026-07-19 | - | Jul 19, 16:20 UTC | Jul 19, 21:55 UTC | 5h 35m |
| 2026-07-19 | KTM → DEL | Jul 19, 12:05 UTC | Jul 19, 13:20 UTC | 1h 15m |
| 2026-07-19 | - | Jul 19, 09:10 UTC | Jul 19, 09:50 UTC | 40m |
| 2026-07-19 | DEL → DEL | Jul 19, 04:05 UTC | Jul 19, 07:05 UTC | 3h 0m |
| 2026-07-18 | PNQ → DEL | Jul 18, 23:35 UTC | Jul 19, 01:20 UTC | 1h 45m |
| 2026-07-18 | DEL → PNQ | Jul 18, 20:50 UTC | Jul 18, 21:20 UTC | 30m |
| 2026-07-18 | - | Jul 18, 15:25 UTC | Jul 18, 19:00 UTC | 3h 35m |
| 2026-07-18 | - | Jul 18, 09:30 UTC | Jul 18, 13:30 UTC | 4h 0m |
| 2026-07-18 | - | Jul 18, 02:00 UTC | Jul 18, 05:30 UTC | 3h 31m |
| 2026-07-17 | - | Jul 17, 20:10 UTC | Jul 17, 21:50 UTC | 1h 40m |
| 2026-07-17 | - | Jul 17, 14:10 UTC | Jul 17, 16:00 UTC | 1h 50m |
| 2026-07-17 | - | Jul 17, 12:19 UTC | Jul 17, 12:30 UTC | 10m |
| 2026-07-17 | - | Jul 17, 11:00 UTC | Jul 17, 11:30 UTC | 30m |
| 2026-07-16 | DEL → DEL | Jul 16, 20:45 UTC | Jul 17, 06:20 UTC | 9h 35m |
| 2026-07-16 | - | Jul 16, 18:44 UTC | Jul 16, 19:20 UTC | 35m |
| 2026-07-16 | - | Jul 16, 08:15 UTC | Jul 16, 18:00 UTC | 9h 45m |
| 2026-07-16 | - | Jul 16, 00:30 UTC | Jul 16, 04:20 UTC | 3h 50m |
| 2026-07-15 | - | Jul 15, 19:20 UTC | Jul 15, 23:25 UTC | 4h 5m |
| 2026-07-15 | - | Jul 15, 06:30 UTC | Jul 15, 09:30 UTC | 3h 0m |
| 2026-07-15 | - | Jul 15, 02:05 UTC | Jul 15, 05:15 UTC | 3h 10m |
| 2026-07-14 | - | Jul 14, 12:55 UTC | Jul 14, 15:15 UTC | 2h 20m |
| 2026-07-14 | - | Jul 14, 10:10 UTC | Jul 14, 11:25 UTC | 1h 15m |
| 2026-07-14 | - | Jul 14, 06:45 UTC | Jul 14, 07:35 UTC | 50m |
Specifications
| Registration | VT-CIO |
| Aircraft type | AIRBUS A-320neo (A20N) |
| Mode-S code | 800C87 · 40006207 (octal) |
Looking for transponder-level data? View the Mode-S 800C87 page for country allocation, callsign history, and ADS-B signal details.
VT-CIO frequently asked
What type of aircraft is VT-CIO?
VT-CIO is a AIRBUS A-320neo (ICAO type code A20N).
What is the Mode-S transponder code for VT-CIO?
VT-CIO broadcasts on Mode-S (ICAO 24-bit) address 800C87 (octal 40006207). View the transponder page.
What route does VT-CIO typically fly?
VT-CIO most frequently flies between MAA and BOM based on observed flights.
Where is VT-CIO right now?
VT-CIO is not currently being tracked; last seen Jul 26, 21:45 UTC.