Not currently tracked · last seen Jul 25, 16:00 UTC
- Flights observed
- 197 showing last 50
- Avg flight time
- 3h 47m
- Typical route
- MCT → SHJ
- Last seen
- Jul 25, 16:00 UTC
Last known area
Recent flights last 50
| Date | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|
| 2026-07-25 | - | Jul 25, 15:40 UTC | Jul 25, 16:00 UTC | 20m |
| 2026-07-25 | - | Jul 25, 13:55 UTC | Jul 25, 14:20 UTC | 25m |
| 2026-07-24 | - | Jul 24, 16:00 UTC | Jul 24, 16:25 UTC | 25m |
| 2026-07-24 | - | Jul 24, 13:50 UTC | Jul 24, 14:15 UTC | 25m |
| 2026-07-23 | LHE → MCT | Jul 23, 21:40 UTC | Jul 24, 00:05 UTC | 2h 25m |
| 2026-07-23 | HYD → MCT | Jul 23, 01:10 UTC | Jul 24, 00:05 UTC | 22h 55m |
| 2026-07-22 | MCT → HYD | Jul 22, 20:40 UTC | Jul 23, 01:35 UTC | 4h 55m |
| 2026-07-21 | MED → MCT | Jul 21, 23:30 UTC | Jul 22, 12:50 UTC | 13h 20m |
| 2026-07-21 | - | Jul 21, 08:50 UTC | Jul 21, 09:50 UTC | 1h 0m |
| 2026-07-21 | MCT → DMM | Jul 21, 06:45 UTC | Jul 21, 07:35 UTC | 50m |
| 2026-07-20 | DMM → MCT | Jul 20, 15:30 UTC | Jul 20, 16:30 UTC | 1h 0m |
| 2026-07-20 | - | Jul 20, 07:25 UTC | Jul 20, 07:50 UTC | 25m |
| 2026-07-20 | MCT → SHJ | Jul 20, 05:20 UTC | Jul 20, 05:50 UTC | 30m |
| 2026-07-18 | - | Jul 18, 12:30 UTC | Jul 18, 13:40 UTC | 1h 10m |
| 2026-07-17 | MCT → RUH | Jul 17, 23:39 UTC | Jul 18, 09:20 UTC | 9h 41m |
| 2026-07-17 | - | Jul 17, 16:04 UTC | Jul 17, 17:09 UTC | 1h 5m |
| 2026-07-17 | - | Jul 17, 13:15 UTC | Jul 17, 14:35 UTC | 1h 20m |
| 2026-07-17 | SHJ → SHJ | Jul 17, 07:14 UTC | Jul 17, 07:35 UTC | 20m |
| 2026-07-17 | MCT → SHJ | Jul 17, 05:39 UTC | Jul 17, 05:50 UTC | 10m |
| 2026-07-15 | - | Jul 15, 15:45 UTC | Jul 15, 16:50 UTC | 1h 5m |
| 2026-07-15 | - | Jul 15, 13:10 UTC | Jul 15, 14:25 UTC | 1h 15m |
| 2026-07-14 | - | Jul 14, 09:15 UTC | Jul 14, 10:20 UTC | 1h 5m |
| 2026-07-14 | - | Jul 14, 00:05 UTC | Jul 14, 07:25 UTC | 7h 20m |
| 2026-07-13 | - | Jul 13, 21:35 UTC | Jul 13, 22:10 UTC | 35m |
| 2026-07-13 | SHJ → MCT | Jul 13, 15:40 UTC | Jul 13, 16:05 UTC | 25m |
| 2026-07-13 | - | Jul 13, 14:10 UTC | Jul 13, 14:20 UTC | 10m |
| 2026-07-13 | - | Jul 13, 07:45 UTC | Jul 13, 08:35 UTC | 50m |
| 2026-07-12 | - | Jul 12, 23:10 UTC | Jul 13, 06:01 UTC | 6h 50m |
| 2026-07-11 | - | Jul 11, 08:45 UTC | Jul 11, 09:45 UTC | 1h 0m |
| 2026-07-11 | - | Jul 11, 06:15 UTC | Jul 11, 07:15 UTC | 1h 0m |
| 2026-07-11 | - | Jul 11, 00:25 UTC | Jul 11, 01:10 UTC | 45m |
| 2026-07-10 | - | Jul 10, 22:25 UTC | Jul 10, 23:10 UTC | 45m |
| 2026-07-10 | - | Jul 10, 00:10 UTC | Jul 10, 23:00 UTC | 22h 50m |
| 2026-07-09 | - | Jul 9, 21:45 UTC | Jul 9, 22:15 UTC | 30m |
| 2026-07-09 | SHJ → MCT | Jul 9, 16:10 UTC | Jul 9, 16:35 UTC | 25m |
| 2026-07-09 | MCT → SHJ | Jul 9, 13:50 UTC | Jul 9, 14:15 UTC | 25m |
| 2026-07-09 | - | Jul 9, 08:45 UTC | Jul 9, 09:40 UTC | 55m |
| 2026-07-08 | - | Jul 8, 15:35 UTC | Jul 9, 07:10 UTC | 15h 35m |
| 2026-07-08 | MCT → SHJ | Jul 8, 13:45 UTC | Jul 8, 14:10 UTC | 25m |
| 2026-07-07 | - | Jul 7, 23:30 UTC | Jul 8, 11:45 UTC | 12h 15m |
| 2026-07-06 | - | Jul 6, 20:10 UTC | Jul 7, 15:00 UTC | 18h 50m |
| 2026-07-06 | - | Jul 6, 15:25 UTC | Jul 6, 16:20 UTC | 55m |
| 2026-07-06 | - | Jul 6, 13:00 UTC | Jul 6, 14:00 UTC | 1h 0m |
| 2026-07-05 | - | Jul 5, 07:00 UTC | Jul 5, 12:55 UTC | 5h 55m |
| 2026-07-05 | - | Jul 5, 06:25 UTC | Jul 5, 06:45 UTC | 20m |
| 2026-07-04 | - | Jul 4, 23:35 UTC | Jul 4, 23:40 UTC | 5m |
| 2026-07-04 | - | Jul 4, 22:10 UTC | Jul 4, 22:25 UTC | 15m |
| 2026-07-04 | - | Jul 4, 00:40 UTC | Jul 4, 16:35 UTC | 15h 55m |
| 2026-07-03 | - | Jul 3, 06:20 UTC | Jul 3, 12:20 UTC | 6h 0m |
| 2026-07-02 | SHJ → MCT | Jul 2, 15:45 UTC | Jul 2, 16:10 UTC | 25m |
Specifications
| Registration | A4O-MO |
| Aircraft type | BOEING 737 MAX 8 (B38M) |
| Mode-S code | 70C11C · 34140434 (octal) |
Looking for transponder-level data? View the Mode-S 70C11C page for country allocation, callsign history, and ADS-B signal details.
A4O-MO frequently asked
What type of aircraft is A4O-MO?
A4O-MO is a BOEING 737 MAX 8 (ICAO type code B38M).
What is the Mode-S transponder code for A4O-MO?
A4O-MO broadcasts on Mode-S (ICAO 24-bit) address 70C11C (octal 34140434). View the transponder page.
What route does A4O-MO typically fly?
A4O-MO most frequently flies between MCT and SHJ based on observed flights.
Where is A4O-MO right now?
A4O-MO is not currently being tracked; last seen Jul 25, 16:00 UTC.