sensors Mode-S transponder

70C0F9

ICAO 24-bit transponder address · allocated to Oman

Currently assigned to A4O-SF · BOEING 787-9 Dreamliner

Hex
70C0F9
Octal
34140371
Decimal
7,389,433
Country
OM
Tail
A4O-SF
Type
B789
No current signal · last broadcast 11d ago
Flights observed
116
Distinct callsigns
15
Country
OM
Last broadcast
11d ago

Last known position

Most recent position reported by Mode-S 70C0F9.

Country allocation

The ICAO 24-bit address 70C0F9 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
OMA101 - 31 2026-06-29
OMA102 - 27 2026-06-29
OMA103 - 19 2026-06-26
OMA104 - 16 2026-06-27
OMA815 - 6 2026-06-26
OMA816 Oman Air 5 2026-06-23
OMA817 Oman Air 3 2026-05-18
OMA818 Oman Air 2 2026-05-19
OMA7016 - 1 2026-07-02
OMA202 Oman Air 1 2026-04-24
OMA201 Oman Air 1 2026-04-24
OMA172 - 1 2026-06-16
OMA171 Oman Air 1 2026-06-15
OMA144 - 1 2026-07-01
OMA143 - 1 2026-07-01

Recent flights last 50

DateFlightRouteTakeoffLandingDuration
2026-07-02 OMA7016 - Jul 2, 11:40 UTCJul 2, 15:25 UTC3h 45m
2026-07-01 OMA144 - Jul 1, 20:30 UTCJul 2, 02:00 UTC5h 30m
2026-07-01 OMA143 - Jul 1, 10:50 UTCJul 1, 17:00 UTC6h 10m
2026-06-29 OMA102 - Jun 29, 20:15 UTCJun 30, 02:55 UTC6h 41m
2026-06-29 OMA101 - Jun 29, 10:04 UTCJun 29, 16:59 UTC6h 55m
2026-06-27 OMA104 - Jun 27, 09:00 UTCJun 27, 15:45 UTC6h 45m
2026-06-26 OMA103 - Jun 26, 12:44 UTCJun 27, 05:25 UTC16h 40m
2026-06-26 OMA815 - Jun 26, 08:15 UTCJun 26, 10:55 UTC2h 40m
2026-06-26 OMA815 - Jun 26, 05:55 UTCJun 26, 08:10 UTC2h 15m
2026-06-25 OMA102 - Jun 25, 20:05 UTCJun 26, 02:40 UTC6h 35m
2026-06-25 OMA101 - Jun 25, 09:59 UTCJun 25, 17:05 UTC7h 5m
2026-06-24 OMA102 - Jun 24, 20:14 UTCJun 25, 02:54 UTC6h 40m
2026-06-24 OMA101 - Jun 24, 10:39 UTCJun 24, 17:50 UTC7h 10m
2026-06-23 OMA816 BKK → MCT Jun 23, 13:24 UTCJun 23, 16:50 UTC3h 25m
2026-06-23 OMA816 BKK → MCT Jun 23, 12:35 UTCJun 23, 12:49 UTC15m
2026-06-23 OMA815 - Jun 23, 06:04 UTCJun 23, 10:39 UTC4h 35m
2026-06-22 OMA102 - Jun 22, 20:19 UTCJun 23, 02:55 UTC6h 35m
2026-06-22 OMA101 - Jun 22, 10:10 UTCJun 22, 17:15 UTC7h 5m
2026-06-21 OMA102 - Jun 21, 20:14 UTCJun 22, 02:54 UTC6h 40m
2026-06-21 OMA101 - Jun 21, 10:44 UTCJun 21, 17:29 UTC6h 45m
2026-06-20 OMA102 - Jun 20, 20:25 UTCJun 21, 03:05 UTC6h 40m
2026-06-19 OMA102 - Jun 19, 22:19 UTCJun 20, 16:49 UTC18h 30m
2026-06-19 OMA102 LHR → LHR Jun 19, 21:54 UTCJun 20, 16:49 UTC18h 55m
2026-06-18 OMA101 - Jun 18, 22:20 UTCJun 19, 16:49 UTC18h 29m
2026-06-18 OMA102 - Jun 18, 20:20 UTCJun 19, 16:49 UTC20h 29m
2026-06-17 OMA101 - Jun 17, 22:20 UTCJun 18, 17:15 UTC18h 55m
2026-06-17 OMA102 - Jun 17, 20:20 UTCJun 18, 17:15 UTC20h 55m
2026-06-17 OMA102 - Jun 17, 20:10 UTCJun 18, 17:15 UTC21h 5m
2026-06-16 OMA101 - Jun 16, 22:30 UTCJun 17, 17:15 UTC18h 45m
2026-06-16 OMA101 - Jun 16, 20:20 UTCJun 17, 17:15 UTC20h 55m
2026-06-16 OMA172 AMS → LHR Jun 16, 18:50 UTCJun 17, 17:15 UTC22h 26m
2026-06-15 OMA171 MCT → CMN Jun 15, 22:20 UTCJun 16, 16:45 UTC18h 25m
2026-06-15 OMA102 - Jun 15, 20:20 UTCJun 16, 16:45 UTC20h 25m
2026-06-15 OMA101 MCT → LHR Jun 15, 12:55 UTCJun 15, 17:50 UTC4h 55m
2026-06-06 OMA102 LHR → MCT Jun 6, 20:35 UTCJun 7, 00:39 UTC4h 5m
2026-06-06 OMA101 MCT → LHR Jun 6, 02:05 UTCJun 6, 17:29 UTC15h 25m
2026-06-05 OMA104 LHR → LHR Jun 5, 07:50 UTCJun 5, 23:35 UTC15h 45m
2026-06-04 OMA103 MCT → MCT Jun 4, 12:35 UTCJun 5, 05:20 UTC16h 45m
2026-06-03 OMA102 LHR → MCT Jun 3, 20:25 UTCJun 4, 10:40 UTC14h 15m
2026-06-02 OMA101 MCT → LHR Jun 2, 22:20 UTCJun 3, 17:40 UTC19h 20m
2026-06-02 OMA102 LHR → MCT Jun 2, 20:40 UTCJun 3, 17:40 UTC21h 0m
2026-06-01 OMA101 MCT → LHR Jun 1, 23:40 UTCJun 2, 17:30 UTC17h 50m
2026-06-01 OMA101 MCT → LHR Jun 1, 18:55 UTCJun 2, 17:30 UTC22h 35m
2026-06-01 OMA104 LHR → LHR Jun 1, 07:40 UTCJun 2, 00:15 UTC16h 35m
2026-05-31 OMA103 MCT → MCT May 31, 10:20 UTCJun 1, 05:25 UTC19h 5m
2026-05-31 OMA103 MCT → MCT May 31, 08:25 UTCJun 1, 05:25 UTC21h 0m
2026-05-30 OMA104 LHR → LHR May 30, 07:55 UTCMay 31, 01:11 UTC17h 16m
2026-05-30 OMA103 MCT → MCT May 30, 00:50 UTCMay 30, 05:40 UTC4h 50m
2026-05-25 OMA104 LHR → LHR May 25, 07:50 UTCMay 25, 14:35 UTC6h 45m
2026-05-24 OMA103 MCT → MCT May 24, 10:20 UTCMay 25, 05:20 UTC19h 0m

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-SF page for operator, model, and routing details .

Mode-S 70C0F9 frequently asked

What is Mode-S code 70C0F9?
70C0F9 is an ICAO 24-bit transponder address. Allocated to Oman. Assigned to A4O-SF.
Where is Mode-S 70C0F9 registered?
Mode-S code 70C0F9 is allocated to Oman (OM). All aircraft registered there receive a Mode-S address from a fixed block defined by ICAO Annex 10.
Is 70C0F9 broadcasting right now?
No active broadcast right now. Last signal was 11d ago.
Hex, octal, and decimal Mode-S codes: what's the difference?
The same 24-bit identifier expressed in different bases: hex 70C0F9, octal 34140371, decimal 7,389,433.
What flights does 70C0F9 operate?
Mode-S 70C0F9 has broadcast 15 distinct callsigns, including OMA101, OMA102, OMA103, OMA104, OMA815.