Not currently tracked · last seen 1h ago
- Flights observed
- 183 showing last 50
- Avg flight time
- 45m
- Typical route
- BLR → AMD
- Last seen
- 1h ago
Last known area
Recent flights last 50
| Date | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|
| 2026-05-30 | BLR → VNS | May 30, 00:15 UTC | May 30, 00:30 UTC | 15m |
| 2026-05-29 | MAA → BLR | May 29, 17:25 UTC | May 29, 17:45 UTC | 20m |
| 2026-05-29 | COK → BLR | May 29, 15:20 UTC | May 29, 15:40 UTC | 20m |
| 2026-05-29 | AMD → BLR | May 29, 12:20 UTC | May 29, 14:20 UTC | 2h 0m |
| 2026-05-29 | BLR → AMD | May 29, 09:30 UTC | May 29, 11:05 UTC | 1h 35m |
| 2026-05-29 | NAG → BLR | May 29, 06:40 UTC | May 29, 06:50 UTC | 10m |
| 2026-05-29 | BLR → NAG | May 29, 03:10 UTC | May 29, 03:25 UTC | 15m |
| 2026-05-28 | AMD → BLR | May 28, 12:35 UTC | May 28, 14:10 UTC | 1h 35m |
| 2026-05-28 | BLR → AMD | May 28, 10:35 UTC | May 28, 11:10 UTC | 35m |
| 2026-05-28 | BLR → AMD | May 28, 09:40 UTC | May 28, 09:50 UTC | 10m |
| 2026-05-28 | AMD → BLR | May 28, 06:10 UTC | May 28, 07:50 UTC | 1h 40m |
| 2026-05-28 | BLR → AMD | May 28, 04:10 UTC | May 28, 05:05 UTC | 55m |
| 2026-05-28 | BLR → AMD | May 28, 03:20 UTC | May 28, 03:30 UTC | 10m |
| 2026-05-28 | AMD → BLR | May 28, 00:05 UTC | May 28, 01:45 UTC | 1h 40m |
| 2026-05-27 | BOM → AMD | May 27, 17:55 UTC | May 27, 18:40 UTC | 45m |
| 2026-05-27 | GOI → BOM | May 27, 15:50 UTC | May 27, 16:25 UTC | 35m |
| 2026-05-27 | IXC → AMD | May 27, 08:40 UTC | May 27, 11:55 UTC | 3h 15m |
| 2026-05-27 | AMD → IXC | May 27, 05:55 UTC | May 27, 07:15 UTC | 1h 21m |
| 2026-05-27 | BLR → AMD | May 27, 03:09 UTC | May 27, 04:19 UTC | 1h 10m |
| 2026-05-27 | AMD → BLR | May 27, 00:14 UTC | May 27, 01:59 UTC | 1h 45m |
| 2026-05-26 | IDR → BLR | May 26, 17:15 UTC | May 26, 17:30 UTC | 15m |
| 2026-05-26 | IDR → BLR | May 26, 15:49 UTC | May 26, 16:10 UTC | 20m |
| 2026-05-26 | IXR → BLR | May 26, 13:15 UTC | May 26, 14:09 UTC | 55m |
| 2026-05-26 | - | May 26, 08:39 UTC | May 26, 08:50 UTC | 10m |
| 2026-05-26 | NAG → BLR | May 26, 06:29 UTC | May 26, 06:39 UTC | 10m |
| 2026-05-26 | BLR → NAG | May 26, 03:15 UTC | May 26, 03:25 UTC | 10m |
| 2026-05-26 | AMD → BLR | May 26, 00:09 UTC | May 26, 02:00 UTC | 1h 50m |
| 2026-05-25 | IDR → BLR | May 25, 18:00 UTC | May 25, 18:20 UTC | 20m |
| 2026-05-25 | IDR → BLR | May 25, 16:45 UTC | May 25, 16:55 UTC | 10m |
| 2026-05-25 | AMD → BLR | May 25, 15:15 UTC | May 25, 15:35 UTC | 20m |
| 2026-05-25 | BLR → AMD | May 25, 12:00 UTC | May 25, 12:20 UTC | 20m |
| 2026-05-25 | BLR → AMD | May 25, 11:10 UTC | May 25, 11:20 UTC | 10m |
| 2026-05-25 | NAG → BLR | May 25, 09:40 UTC | May 25, 09:50 UTC | 10m |
| 2026-05-25 | BLR → NAG | May 25, 06:25 UTC | May 25, 06:35 UTC | 10m |
| 2026-05-25 | VNS → BLR | May 25, 03:00 UTC | May 25, 03:20 UTC | 20m |
| 2026-05-24 | AMD → BLR | May 24, 11:55 UTC | May 24, 13:35 UTC | 1h 40m |
| 2026-05-24 | BLR → AMD | May 24, 10:00 UTC | May 24, 10:20 UTC | 20m |
| 2026-05-24 | BLR → AMD | May 24, 09:10 UTC | May 24, 09:20 UTC | 10m |
| 2026-05-24 | DEL → BLR | May 24, 07:40 UTC | May 24, 07:50 UTC | 10m |
| 2026-05-24 | DEL → BLR | May 24, 05:35 UTC | May 24, 06:05 UTC | 30m |
| 2026-05-24 | CCU → BLR | May 24, 01:10 UTC | May 24, 03:30 UTC | 2h 20m |
| 2026-05-23 | CCU → BLR | May 23, 14:55 UTC | May 23, 16:25 UTC | 1h 30m |
| 2026-05-23 | BLR → IXR | May 23, 12:20 UTC | May 23, 12:50 UTC | 30m |
| 2026-05-23 | CCU → IXB | May 23, 10:15 UTC | May 23, 10:45 UTC | 30m |
| 2026-05-23 | BLR → CCU | May 23, 07:35 UTC | May 23, 08:00 UTC | 25m |
| 2026-05-23 | BLR → CCU | May 23, 06:45 UTC | May 23, 07:00 UTC | 15m |
| 2026-05-23 | VNS → BLR | May 23, 03:15 UTC | May 23, 03:35 UTC | 20m |
| 2026-05-23 | BLR → VNS | May 23, 00:20 UTC | May 23, 02:25 UTC | 2h 5m |
| 2026-05-22 | NAG → BLR | May 22, 17:40 UTC | May 22, 17:50 UTC | 10m |
| 2026-05-22 | BLR → NAG | May 22, 14:25 UTC | May 22, 14:35 UTC | 10m |
Specifications
| Registration | VT-BOM |
| Aircraft type | AIRBUS A-320 (A320) |
| Mode-S code | 80138D · 40011615 (octal) |
Looking for transponder-level data? View the Mode-S 80138D page for country allocation, callsign history, and ADS-B signal details.
VT-BOM frequently asked
What type of aircraft is VT-BOM?
VT-BOM is a AIRBUS A-320 (ICAO type code A320).
What is the Mode-S transponder code for VT-BOM?
VT-BOM broadcasts on Mode-S (ICAO 24-bit) address 80138D (octal 40011615). View the transponder page.
What route does VT-BOM typically fly?
VT-BOM most frequently flies between BLR and AMD based on observed flights.
Where is VT-BOM right now?
VT-BOM is not currently being tracked; last seen 1h ago.