sensors Mode-S transponder
70C109
ICAO 24-bit transponder address · allocated to Oman
Currently assigned to A4O-MN · BOEING 737 MAX 8
- Hex
- 70C109
- Octal
- 34140411
- Decimal
- 7,389,449
- Country
- OM
- Tail
- A4O-MN
- Type
- B38M
- Flights observed
- 74
- Distinct callsigns
- 15
- Country
- OM
- Last broadcast
- 1h ago
Last known position
Country allocation
The ICAO 24-bit address 70C109 falls within the block assigned to Oman (OM) by ICAO Annex 10, Volume III. Every aircraft registered in Oman receives a permanent address from this block at the time of registration; the address stays with the airframe even if the aircraft is re-registered to a different operator within the country.
Callsign history 15 distinct
| Callsign | Airline | Flights | Last seen |
|---|---|---|---|
| OMA317 | Oman Air | 21 | 2026-05-30 |
| OMA318 | Oman Air | 13 | 2026-05-30 |
| OMA211 | Oman Air | 7 | 2026-05-29 |
| OMA212 | Oman Air | 5 | 2026-05-29 |
| OMA694 | - | 4 | 2026-04-19 |
| OMA693 | Oman Air | 4 | 2026-04-19 |
| OMA266 | Oman Air | 4 | 2026-05-25 |
| OMA265 | Oman Air | 4 | 2026-05-19 |
| OMA235 | Oman Air | 2 | 2026-05-16 |
| OMA232 | Oman Air | 2 | 2026-04-23 |
| OMA166 | Oman Air | 2 | 2026-05-01 |
| OMA165 | Oman Air | 2 | 2026-05-01 |
| OMA680 | Oman Air | 1 | 2026-04-24 |
| OMA291 | Oman Air | 1 | 2026-05-29 |
| OMA231 | Oman Air | 1 | 2026-04-23 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-05-30 | OMA318 | DAC → MCT | May 30, 10:05 UTC | May 30, 10:15 UTC | 10m |
| 2026-05-30 | OMA317 | MCT → DAC | May 30, 05:50 UTC | May 30, 08:50 UTC | 3h 0m |
| 2026-05-29 | OMA291 | MCT → CCJ | May 29, 12:40 UTC | May 29, 13:05 UTC | 25m |
| 2026-05-29 | OMA212 | TRV → MCT | May 29, 03:10 UTC | May 29, 03:25 UTC | 15m |
| 2026-05-29 | OMA211 | MCT → TRV | May 29, 01:20 UTC | May 29, 01:50 UTC | 30m |
| 2026-05-28 | OMA212 | TRV → MCT | May 28, 03:10 UTC | May 28, 03:20 UTC | 10m |
| 2026-05-27 | OMA318 | DAC → MCT | May 27, 10:15 UTC | May 28, 01:55 UTC | 15h 40m |
| 2026-05-27 | OMA317 | MCT → DAC | May 27, 05:49 UTC | May 27, 08:45 UTC | 2h 56m |
| 2026-05-25 | OMA266 | LKO → MCT | May 25, 04:40 UTC | May 25, 05:40 UTC | 1h 0m |
| 2026-05-24 | OMA318 | DAC → MCT | May 24, 10:30 UTC | May 24, 13:45 UTC | 3h 15m |
| 2026-05-24 | OMA317 | MCT → DAC | May 24, 05:55 UTC | May 24, 08:45 UTC | 2h 50m |
| 2026-05-23 | OMA317 | MCT → DAC | May 23, 12:30 UTC | May 24, 08:45 UTC | 20h 15m |
| 2026-05-23 | OMA318 | DAC → MCT | May 23, 10:20 UTC | May 24, 08:45 UTC | 22h 25m |
| 2026-05-23 | OMA317 | MCT → DAC | May 23, 05:45 UTC | May 23, 08:50 UTC | 3h 5m |
| 2026-05-22 | OMA317 | MCT → DAC | May 22, 12:40 UTC | May 23, 08:50 UTC | 20h 9m |
| 2026-05-22 | OMA317 | MCT → DAC | May 22, 10:25 UTC | May 23, 08:50 UTC | 22h 24m |
| 2026-05-22 | OMA317 | MCT → DAC | May 22, 06:00 UTC | May 22, 09:00 UTC | 3h 0m |
| 2026-05-21 | OMA317 | MCT → DAC | May 21, 12:45 UTC | May 22, 09:00 UTC | 20h 15m |
| 2026-05-21 | OMA318 | DAC → MCT | May 21, 10:30 UTC | May 22, 09:00 UTC | 22h 30m |
| 2026-05-21 | OMA317 | MCT → DAC | May 21, 06:05 UTC | May 21, 09:00 UTC | 2h 55m |
| 2026-05-20 | OMA317 | MCT → DAC | May 20, 12:40 UTC | May 21, 09:00 UTC | 20h 20m |
| 2026-05-20 | OMA318 | DAC → MCT | May 20, 10:30 UTC | May 21, 09:00 UTC | 22h 30m |
| 2026-05-19 | OMA317 | MCT → DAC | May 19, 17:05 UTC | May 20, 08:40 UTC | 15h 36m |
| 2026-05-19 | OMA266 | LKO → MCT | May 19, 04:50 UTC | May 19, 17:15 UTC | 12h 25m |
| 2026-05-19 | OMA265 | MCT → LKO | May 19, 00:10 UTC | May 19, 01:55 UTC | 1h 45m |
| 2026-05-18 | OMA265 | MCT → LKO | May 18, 04:30 UTC | May 19, 01:55 UTC | 21h 24m |
| 2026-05-18 | OMA265 | MCT → LKO | May 18, 00:25 UTC | May 18, 02:10 UTC | 1h 45m |
| 2026-05-16 | OMA235 | MCT → HYD | May 16, 23:50 UTC | May 17, 14:20 UTC | 14h 30m |
| 2026-05-16 | OMA235 | MCT → HYD | May 16, 16:15 UTC | May 17, 14:15 UTC | 22h 0m |
| 2026-05-16 | OMA266 | LKO → MCT | May 16, 04:45 UTC | May 17, 04:00 UTC | 23h 15m |
| 2026-05-15 | OMA318 | DAC → MCT | May 15, 10:05 UTC | May 16, 02:00 UTC | 15h 54m |
| 2026-05-15 | OMA317 | MCT → DAC | May 15, 01:25 UTC | May 15, 08:35 UTC | 7h 10m |
| 2026-05-14 | OMA318 | DAC → MCT | May 14, 10:15 UTC | May 14, 13:10 UTC | 2h 55m |
| 2026-05-14 | OMA317 | MCT → DAC | May 14, 05:45 UTC | May 14, 08:35 UTC | 2h 50m |
| 2026-05-10 | OMA318 | DAC → MCT | May 10, 10:19 UTC | May 10, 13:25 UTC | 3h 5m |
| 2026-05-09 | OMA317 | MCT → DAC | May 9, 16:25 UTC | May 10, 08:35 UTC | 16h 10m |
| 2026-05-09 | OMA317 | MCT → DAC | May 9, 12:20 UTC | May 10, 08:35 UTC | 20h 15m |
| 2026-05-09 | OMA317 | MCT → DAC | May 9, 12:05 UTC | May 10, 08:35 UTC | 20h 30m |
| 2026-05-05 | OMA318 | DAC → MCT | May 5, 10:10 UTC | May 6, 02:10 UTC | 16h 0m |
| 2026-05-04 | OMA317 | MCT → DAC | May 4, 23:05 UTC | May 5, 08:35 UTC | 9h 30m |
| 2026-05-03 | OMA318 | DAC → MCT | May 3, 10:15 UTC | May 4, 00:10 UTC | 13h 55m |
| 2026-05-03 | OMA317 | MCT → DAC | May 3, 06:15 UTC | May 3, 08:50 UTC | 2h 35m |
| 2026-05-02 | OMA317 | MCT → DAC | May 2, 14:10 UTC | May 3, 08:50 UTC | 18h 39m |
| 2026-05-01 | OMA166 | IST → MCT | May 1, 16:30 UTC | May 1, 20:35 UTC | 4h 5m |
| 2026-05-01 | OMA165 | MCT → IST | May 1, 10:30 UTC | May 1, 10:50 UTC | 20m |
| 2026-05-01 | OMA212 | TRV → MCT | May 1, 03:15 UTC | May 1, 03:25 UTC | 10m |
| 2026-05-01 | OMA211 | MCT → TRV | May 1, 01:40 UTC | May 1, 01:55 UTC | 15m |
| 2026-04-30 | OMA266 | LKO → MCT | Apr 30, 03:35 UTC | Apr 30, 03:50 UTC | 15m |
| 2026-04-29 | OMA265 | MCT → LKO | Apr 29, 14:00 UTC | Apr 30, 01:50 UTC | 11h 49m |
| 2026-04-29 | OMA212 | TRV → MCT | Apr 29, 03:19 UTC | Apr 29, 03:30 UTC | 10m |
About Mode-S
A Mode-S transponder code (also called an "ICAO 24-bit address" or "hex code") is a 6-character hexadecimal identifier permanently assigned to an aircraft when it's first registered. Unlike callsigns (which change with each flight) or registrations (which can change if an aircraft is sold internationally), the Mode-S address stays with the airframe for the life of the aircraft in that country.
Every ADS-B transmission from an aircraft includes its Mode-S address, making it the most reliable way to identify a specific airframe. Flight-tracking services like Apparatus use the Mode-S address as the primary key for tying position broadcasts, callsigns, and ownership records together.
Prefer a tail-number view? See the A4O-MN page for operator, model, and routing details .