Not currently tracked · last seen 10d ago
- Flights observed
- 41
- Avg flight time
- 1h 39m
- Typical route
- -
- Last seen
- 10d ago
Last known area
Recent flights last 41
| Date | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|
| 2026-07-11 | - | Jul 11, 16:10 UTC | Jul 11, 16:55 UTC | 45m |
| 2026-07-11 | - | Jul 11, 07:40 UTC | Jul 11, 14:35 UTC | 6h 55m |
| 2026-07-09 | - | Jul 9, 02:40 UTC | Jul 9, 05:35 UTC | 2h 55m |
| 2026-07-04 | - | Jul 4, 11:35 UTC | Jul 4, 12:25 UTC | 50m |
| 2026-07-03 | - | Jul 3, 13:55 UTC | Jul 3, 15:05 UTC | 1h 10m |
| 2026-07-02 | - | Jul 2, 12:00 UTC | Jul 2, 12:25 UTC | 25m |
| 2026-07-01 | - | Jul 1, 04:00 UTC | Jul 1, 04:50 UTC | 50m |
| 2026-06-27 | - | Jun 27, 12:15 UTC | Jun 27, 20:39 UTC | 8h 25m |
| 2026-06-24 | - | Jun 24, 01:34 UTC | Jun 24, 09:49 UTC | 8h 15m |
| 2026-06-22 | - | Jun 22, 11:39 UTC | Jun 22, 12:05 UTC | 25m |
| 2026-06-22 | - | Jun 22, 06:19 UTC | Jun 22, 08:10 UTC | 1h 50m |
| 2026-06-17 | - | Jun 17, 02:50 UTC | Jun 17, 03:00 UTC | 10m |
| 2026-06-10 | - | Jun 10, 12:15 UTC | Jun 10, 13:00 UTC | 45m |
| 2026-06-09 | - | Jun 9, 09:55 UTC | Jun 9, 11:45 UTC | 1h 50m |
| 2026-06-07 | - | Jun 7, 10:05 UTC | Jun 7, 10:20 UTC | 15m |
| 2026-06-07 | - | Jun 7, 08:35 UTC | Jun 7, 08:55 UTC | 20m |
| 2026-06-05 | - | Jun 5, 08:05 UTC | Jun 5, 08:55 UTC | 50m |
| 2026-06-05 | - | Jun 5, 05:20 UTC | Jun 5, 05:50 UTC | 30m |
| 2026-06-05 | - | Jun 5, 04:35 UTC | Jun 5, 04:45 UTC | 10m |
| 2026-06-05 | - | Jun 5, 03:30 UTC | Jun 5, 04:20 UTC | 50m |
| 2026-06-04 | - | Jun 4, 11:00 UTC | Jun 4, 11:15 UTC | 15m |
| 2026-06-04 | - | Jun 4, 03:35 UTC | Jun 4, 04:55 UTC | 1h 20m |
| 2026-05-27 | - | May 27, 02:54 UTC | May 27, 03:04 UTC | 10m |
| 2026-05-26 | - | May 26, 03:05 UTC | May 26, 03:19 UTC | 15m |
| 2026-05-19 | - | May 19, 08:15 UTC | May 19, 08:55 UTC | 40m |
| 2026-05-19 | - | May 19, 02:15 UTC | May 19, 03:10 UTC | 55m |
| 2026-05-17 | - | May 17, 17:35 UTC | May 17, 17:55 UTC | 20m |
| 2026-05-17 | - | May 17, 15:40 UTC | May 17, 16:55 UTC | 1h 15m |
| 2026-05-17 | - | May 17, 10:00 UTC | May 17, 13:25 UTC | 3h 25m |
| 2026-05-13 | - | May 13, 12:15 UTC | May 13, 12:55 UTC | 40m |
| 2026-05-12 | - | May 12, 09:55 UTC | May 12, 11:10 UTC | 1h 15m |
| 2026-05-05 | - | May 5, 08:25 UTC | May 5, 10:55 UTC | 2h 30m |
| 2026-05-01 | - | May 1, 08:35 UTC | May 1, 12:45 UTC | 4h 10m |
| 2026-04-30 | - | Apr 30, 02:55 UTC | Apr 30, 10:20 UTC | 7h 25m |
| 2026-04-25 | - | Apr 25, 15:00 UTC | Apr 25, 15:50 UTC | 50m |
| 2026-04-25 | - | Apr 25, 13:15 UTC | Apr 25, 14:05 UTC | 50m |
| 2026-04-22 | - | Apr 22, 12:20 UTC | Apr 22, 12:45 UTC | 25m |
| 2026-04-21 | - | Apr 21, 08:45 UTC | Apr 21, 10:00 UTC | 1h 15m |
| 2026-04-16 | - | Apr 16, 11:54 UTC | Apr 16, 12:19 UTC | 25m |
| 2026-04-16 | - | Apr 16, 05:09 UTC | Apr 16, 05:34 UTC | 25m |
| 2026-04-16 | - | Apr 16, 04:24 UTC | Apr 16, 05:05 UTC | 40m |
Specifications
| Registration | VT-AOS |
| Aircraft type | BOMBARDIER BD-100 Challenger 350 (CL35) |
| Mode-S code | 80173D · 40013475 (octal) |
Looking for transponder-level data? View the Mode-S 80173D page for country allocation, callsign history, and ADS-B signal details.
VT-AOS frequently asked
What type of aircraft is VT-AOS?
VT-AOS is a BOMBARDIER BD-100 Challenger 350 (ICAO type code CL35).
What is the Mode-S transponder code for VT-AOS?
VT-AOS broadcasts on Mode-S (ICAO 24-bit) address 80173D (octal 40013475). View the transponder page.
Where is VT-AOS right now?
VT-AOS is not currently being tracked; last seen 10d ago.