Not currently tracked · last seen 13h ago
- Flights observed
- 192 showing last 50
- Avg flight time
- 1h 7m
- Typical route
- AMD → BOM
- Last seen
- 13h ago
Last known area
Recent flights last 50
| Date | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|
| 2026-06-02 | ATQ → DEL | Jun 2, 05:15 UTC | Jun 2, 06:00 UTC | 45m |
| 2026-06-02 | DEL → ATQ | Jun 2, 02:55 UTC | Jun 2, 03:30 UTC | 35m |
| 2026-06-01 | ATQ → DEL | Jun 1, 08:20 UTC | Jun 1, 09:10 UTC | 50m |
| 2026-06-01 | DEL → ATQ | Jun 1, 06:05 UTC | Jun 1, 06:40 UTC | 35m |
| 2026-05-31 | DEL → CMB | May 31, 19:15 UTC | Jun 1, 02:55 UTC | 7h 40m |
| 2026-05-31 | AMD → DEL | May 31, 14:55 UTC | May 31, 16:05 UTC | 1h 10m |
| 2026-05-31 | BOM → AMD | May 31, 12:40 UTC | May 31, 12:50 UTC | 10m |
| 2026-05-31 | AMD → BOM | May 31, 09:55 UTC | May 31, 10:40 UTC | 45m |
| 2026-05-30 | COK → BOM | May 30, 15:55 UTC | May 30, 16:10 UTC | 15m |
| 2026-05-30 | COK → BOM | May 30, 14:35 UTC | May 30, 15:00 UTC | 25m |
| 2026-05-30 | BOM → COK | May 30, 12:45 UTC | May 30, 13:25 UTC | 40m |
| 2026-05-30 | BOM → ATQ | May 30, 05:20 UTC | May 30, 10:40 UTC | 5h 20m |
| 2026-05-29 | AMD → BOM | May 29, 15:25 UTC | May 29, 16:20 UTC | 56m |
| 2026-05-29 | BOM → AMD | May 29, 13:00 UTC | May 29, 13:35 UTC | 35m |
| 2026-05-29 | AMD → BOM | May 29, 10:00 UTC | May 29, 10:50 UTC | 50m |
| 2026-05-29 | BOM → AMD | May 29, 08:05 UTC | May 29, 08:40 UTC | 35m |
| 2026-05-29 | CJB → BOM | May 29, 04:55 UTC | May 29, 05:35 UTC | 40m |
| 2026-05-29 | CJB → BOM | May 29, 03:45 UTC | May 29, 04:15 UTC | 30m |
| 2026-05-29 | BOM → CJB | May 29, 01:50 UTC | May 29, 02:15 UTC | 25m |
| 2026-05-29 | BOM → CJB | May 29, 01:05 UTC | May 29, 01:15 UTC | 10m |
| 2026-05-28 | AMD → BOM | May 28, 15:50 UTC | May 28, 16:50 UTC | 1h 0m |
| 2026-05-28 | BOM → AMD | May 28, 13:00 UTC | May 28, 13:10 UTC | 10m |
| 2026-05-28 | AMD → BOM | May 28, 10:05 UTC | May 28, 10:55 UTC | 50m |
| 2026-05-28 | BOM → AMD | May 28, 07:55 UTC | May 28, 08:35 UTC | 40m |
| 2026-05-28 | CJB → BOM | May 28, 04:55 UTC | May 28, 05:20 UTC | 25m |
| 2026-05-28 | CJB → BOM | May 28, 03:45 UTC | May 28, 04:10 UTC | 25m |
| 2026-05-28 | BOM → CJB | May 28, 01:50 UTC | May 28, 02:20 UTC | 30m |
| 2026-05-28 | BOM → CJB | May 28, 01:05 UTC | May 28, 01:15 UTC | 10m |
| 2026-05-27 | - | May 27, 19:50 UTC | May 27, 20:05 UTC | 15m |
| 2026-05-27 | BOM → CCU | May 27, 14:10 UTC | May 27, 14:35 UTC | 25m |
| 2026-05-27 | AMD → BOM | May 27, 11:15 UTC | May 27, 12:00 UTC | 45m |
| 2026-05-27 | BOM → AMD | May 27, 09:10 UTC | May 27, 09:20 UTC | 10m |
| 2026-05-27 | CJB → BOM | May 27, 05:04 UTC | May 27, 05:35 UTC | 30m |
| 2026-05-27 | CJB → BOM | May 27, 03:50 UTC | May 27, 04:24 UTC | 35m |
| 2026-05-27 | BOM → CJB | May 27, 01:44 UTC | May 27, 02:24 UTC | 40m |
| 2026-05-27 | BOM → CJB | May 27, 00:59 UTC | May 27, 01:14 UTC | 15m |
| 2026-05-26 | AMD → BOM | May 26, 15:29 UTC | May 26, 16:30 UTC | 1h 0m |
| 2026-05-26 | DEL → AMD | May 26, 12:24 UTC | May 26, 12:54 UTC | 30m |
| 2026-05-26 | ATQ → DEL | May 26, 08:10 UTC | May 26, 08:50 UTC | 40m |
| 2026-05-26 | DEL → ATQ | May 26, 06:10 UTC | May 26, 06:44 UTC | 35m |
| 2026-05-26 | AMD → DEL | May 26, 03:09 UTC | May 26, 04:30 UTC | 1h 20m |
| 2026-05-26 | - | May 26, 00:39 UTC | May 26, 01:30 UTC | 50m |
| 2026-05-25 | TRV → DEL | May 25, 15:05 UTC | May 25, 18:05 UTC | 3h 0m |
| 2026-05-25 | DEL → TRV | May 25, 11:10 UTC | May 25, 14:05 UTC | 2h 55m |
| 2026-05-25 | TRV → DEL | May 25, 06:10 UTC | May 25, 09:15 UTC | 3h 5m |
| 2026-05-25 | DEL → TRV | May 25, 02:15 UTC | May 25, 05:20 UTC | 3h 5m |
| 2026-05-24 | - | May 24, 17:35 UTC | May 24, 18:20 UTC | 45m |
| 2026-05-24 | DEL → ATQ | May 24, 15:25 UTC | May 24, 15:55 UTC | 30m |
| 2026-05-24 | AMD → DEL | May 24, 08:35 UTC | May 24, 12:20 UTC | 3h 45m |
| 2026-05-24 | GAU → DEL | May 24, 05:15 UTC | May 24, 07:20 UTC | 2h 5m |
Specifications
| Registration | VT-PPI |
| Aircraft type | AIRBUS A-321 (A321) |
| Mode-S code | 80047C · 40002174 (octal) |
Looking for transponder-level data? View the Mode-S 80047C page for country allocation, callsign history, and ADS-B signal details.
VT-PPI frequently asked
What type of aircraft is VT-PPI?
VT-PPI is a AIRBUS A-321 (ICAO type code A321).
What is the Mode-S transponder code for VT-PPI?
VT-PPI broadcasts on Mode-S (ICAO 24-bit) address 80047C (octal 40002174). View the transponder page.
What route does VT-PPI typically fly?
VT-PPI most frequently flies between AMD and BOM based on observed flights.
Where is VT-PPI right now?
VT-PPI is not currently being tracked; last seen 13h ago.