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