Not currently tracked · last seen 1d ago
- Flights observed
- 61 showing last 50
- Avg flight time
- 7h 29m
- Typical route
- MCT → BOM
- Last seen
- 1d ago
Last known area
Recent flights last 50
| Date | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|
| 2026-05-31 | MCT → BOM | May 31, 13:55 UTC | Jun 1, 07:55 UTC | 18h 0m |
| 2026-05-29 | HYD → MCT | May 29, 16:30 UTC | May 30, 12:15 UTC | 19h 45m |
| 2026-05-29 | BOM → MCT | May 29, 05:05 UTC | May 29, 16:50 UTC | 11h 45m |
| 2026-05-29 | MCT → BOM | May 29, 02:35 UTC | May 29, 03:30 UTC | 55m |
| 2026-05-27 | BOM → MCT | May 27, 04:34 UTC | May 27, 05:09 UTC | 35m |
| 2026-05-26 | MCT → HYD | May 26, 07:24 UTC | May 27, 03:24 UTC | 20h 0m |
| 2026-05-25 | MCT → HYD | May 25, 23:35 UTC | May 26, 12:00 UTC | 12h 25m |
| 2026-05-25 | MCT → HYD | May 25, 10:20 UTC | May 26, 08:15 UTC | 21h 54m |
| 2026-05-25 | MCT → HYD | May 25, 10:05 UTC | May 26, 08:15 UTC | 22h 10m |
| 2026-05-24 | MCT → BOM | May 24, 19:45 UTC | May 25, 07:55 UTC | 12h 10m |
| 2026-05-24 | MCT → BOM | May 24, 09:10 UTC | May 25, 07:55 UTC | 22h 45m |
| 2026-05-24 | MCT → BOM | May 24, 06:35 UTC | May 24, 07:50 UTC | 1h 15m |
| 2026-05-23 | TRV → MCT | May 23, 03:15 UTC | May 23, 03:25 UTC | 10m |
| 2026-05-22 | BOM → MCT | May 22, 12:00 UTC | May 23, 02:00 UTC | 14h 0m |
| 2026-05-22 | MCT → BOM | May 22, 03:15 UTC | May 22, 10:15 UTC | 7h 0m |
| 2026-05-22 | MCT → TRV | May 22, 01:45 UTC | May 22, 02:00 UTC | 15m |
| 2026-05-20 | TRV → MCT | May 20, 03:15 UTC | May 20, 03:30 UTC | 15m |
| 2026-05-20 | MCT → TRV | May 20, 01:30 UTC | May 20, 02:00 UTC | 30m |
| 2026-05-19 | MCT → TRV | May 19, 04:50 UTC | May 20, 02:00 UTC | 21h 10m |
| 2026-05-19 | TRV → MCT | May 19, 03:20 UTC | May 20, 02:00 UTC | 22h 40m |
| 2026-05-18 | MCT → BOM | May 18, 06:35 UTC | May 19, 02:05 UTC | 19h 29m |
| 2026-05-16 | JED → MCT | May 16, 03:20 UTC | May 16, 17:10 UTC | 13h 51m |
| 2026-05-15 | CAI → MCT | May 15, 16:45 UTC | May 16, 02:00 UTC | 9h 15m |
| 2026-05-15 | MCT → CAI | May 15, 14:30 UTC | May 15, 14:55 UTC | 24m |
| 2026-05-15 | TRV → MCT | May 15, 03:25 UTC | May 15, 03:35 UTC | 10m |
| 2026-05-15 | MCT → TRV | May 15, 01:45 UTC | May 15, 02:05 UTC | 20m |
| 2026-05-14 | TRV → MCT | May 14, 03:15 UTC | May 14, 03:30 UTC | 15m |
| 2026-05-14 | MCT → TRV | May 14, 01:40 UTC | May 14, 02:00 UTC | 20m |
| 2026-05-13 | MED → MCT | May 13, 02:20 UTC | May 13, 17:00 UTC | 14h 40m |
| 2026-05-11 | MCT → BOM | May 11, 06:25 UTC | May 11, 07:00 UTC | 35m |
| 2026-05-05 | JED → MCT | May 5, 16:35 UTC | May 5, 17:00 UTC | 25m |
| 2026-05-04 | BOM → MCT | May 4, 05:00 UTC | May 4, 05:15 UTC | 15m |
| 2026-05-04 | MCT → BOM | May 4, 03:00 UTC | May 4, 03:30 UTC | 30m |
| 2026-05-03 | DOH → MCT | May 3, 19:10 UTC | May 3, 19:45 UTC | 35m |
| 2026-05-03 | MCT → DOH | May 3, 04:55 UTC | May 3, 17:29 UTC | 12h 35m |
| 2026-05-03 | MCT → BOM | May 3, 02:45 UTC | May 3, 03:15 UTC | 30m |
| 2026-05-02 | JED → MCT | May 2, 16:45 UTC | May 2, 17:40 UTC | 55m |
| 2026-05-01 | BOM → MCT | May 1, 09:45 UTC | May 1, 09:55 UTC | 10m |
| 2026-05-01 | MCT → BOM | May 1, 07:00 UTC | May 1, 08:00 UTC | 1h 0m |
| 2026-04-30 | JED → MCT | Apr 30, 17:05 UTC | Apr 30, 18:10 UTC | 1h 5m |
| 2026-04-29 | JED → MCT | Apr 29, 05:00 UTC | Apr 29, 17:35 UTC | 12h 36m |
| 2026-04-29 | MCT → BOM | Apr 29, 02:40 UTC | Apr 29, 03:19 UTC | 40m |
| 2026-04-28 | JED → MCT | Apr 28, 12:25 UTC | Apr 28, 17:50 UTC | 5h 25m |
| 2026-04-27 | JED → MCT | Apr 27, 09:30 UTC | Apr 28, 00:35 UTC | 15h 5m |
| 2026-04-27 | MCT → BOM | Apr 27, 07:10 UTC | Apr 27, 07:45 UTC | 35m |
| 2026-04-26 | JED → MCT | Apr 26, 09:45 UTC | Apr 27, 00:40 UTC | 14h 55m |
| 2026-04-26 | MCT → BOM | Apr 26, 07:25 UTC | Apr 26, 08:05 UTC | 40m |
| 2026-04-24 | JED → MCT | Apr 24, 11:05 UTC | Apr 25, 02:55 UTC | 15h 50m |
| 2026-04-24 | MCT → BOM | Apr 24, 08:50 UTC | Apr 24, 09:40 UTC | 50m |
| 2026-04-24 | JED → MCT | Apr 24, 04:25 UTC | Apr 24, 05:15 UTC | 50m |
Specifications
| Registration | A4O-BY |
| Aircraft type | BOEING 737-900 (B739) |
| Mode-S code | 70C0C9 · 34140311 (octal) |
Looking for transponder-level data? View the Mode-S 70C0C9 page for country allocation, callsign history, and ADS-B signal details.
A4O-BY frequently asked
What type of aircraft is A4O-BY?
A4O-BY is a BOEING 737-900 (ICAO type code B739).
What is the Mode-S transponder code for A4O-BY?
A4O-BY broadcasts on Mode-S (ICAO 24-bit) address 70C0C9 (octal 34140311). View the transponder page.
What route does A4O-BY typically fly?
A4O-BY most frequently flies between MCT and BOM based on observed flights.
Where is A4O-BY right now?
A4O-BY is not currently being tracked; last seen 1d ago.