Apparatus

Try JFK, AAL1290, BAW, or N225AN.

sensors Mode-S transponder

A3F119

ICAO 24-bit transponder address · allocated to United States

Currently assigned to N353MV · CESSNA 172 Skyhawk · operated by IGAL ZUBERY

Hex
A3F119
Octal
50770431
Decimal
10,744,089
Country
US
Tail
N353MV
Type
C172
No current signal · last broadcast 10h ago
Flights observed
285
Distinct callsigns
1
Country
US
Last broadcast
10h ago

Last known position

Most recent position reported by Mode-S A3F119.

Country allocation

The ICAO 24-bit address A3F119 falls within the block assigned to United States (US) by ICAO Annex 10, Volume III. Every aircraft registered in United States 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 1 distinct

Callsign Airline Flights Last seen
N353MV - 285 2026-07-18

Recent flights last 50

DateFlightRouteTakeoffLandingDuration
2026-07-18 N353MV - Jul 18, 00:55 UTCJul 18, 01:50 UTC55m
2026-07-17 N353MV SMO → SMO Jul 17, 21:20 UTCJul 17, 22:49 UTC1h 30m
2026-07-17 N353MV SMO → SMO Jul 17, 18:44 UTCJul 17, 20:00 UTC1h 15m
2026-07-17 N353MV SMO → SMO Jul 17, 15:55 UTCJul 17, 16:49 UTC55m
2026-07-16 N353MV - Jul 16, 21:35 UTCJul 16, 22:19 UTC45m
2026-07-16 N353MV - Jul 16, 18:29 UTCJul 16, 20:00 UTC1h 30m
2026-07-16 N353MV - Jul 16, 17:30 UTCJul 16, 18:19 UTC50m
2026-07-16 N353MV - Jul 16, 00:00 UTCJul 16, 01:00 UTC1h 0m
2026-07-15 N353MV - Jul 15, 22:10 UTCJul 15, 23:00 UTC50m
2026-07-15 N353MV SMO → SBA Jul 15, 21:05 UTCJul 15, 21:55 UTC50m
2026-07-15 N353MV - Jul 15, 18:50 UTCJul 15, 19:40 UTC50m
2026-07-15 N353MV AVX → SMO Jul 15, 16:35 UTCJul 15, 17:35 UTC1h 0m
2026-07-15 N353MV - Jul 15, 15:30 UTCJul 15, 16:00 UTC30m
2026-07-15 N353MV - Jul 15, 01:45 UTCJul 15, 02:40 UTC55m
2026-07-14 N353MV SMO → SMO Jul 14, 23:55 UTCJul 15, 00:45 UTC50m
2026-07-14 N353MV SMO → SMO Jul 14, 22:40 UTCJul 14, 22:50 UTC9m
2026-07-14 N353MV SMO → SMO Jul 14, 21:10 UTCJul 14, 21:55 UTC45m
2026-07-14 N353MV - Jul 14, 18:25 UTCJul 14, 19:50 UTC1h 25m
2026-07-14 N353MV SMO → SMO Jul 14, 01:15 UTCJul 14, 02:20 UTC1h 5m
2026-07-09 N353MV SMO → SMO Jul 9, 16:05 UTCJul 9, 16:50 UTC45m
2026-07-09 N353MV SMO → SMO Jul 9, 00:05 UTCJul 9, 01:25 UTC1h 20m
2026-07-08 N353MV - Jul 8, 19:55 UTCJul 8, 21:15 UTC1h 20m
2026-07-08 N353MV - Jul 8, 18:20 UTCJul 8, 18:45 UTC25m
2026-07-08 N353MV - Jul 8, 16:50 UTCJul 8, 17:30 UTC40m
2026-07-08 N353MV SMO → SMO Jul 8, 02:25 UTCJul 8, 03:20 UTC55m
2026-07-07 N353MV - Jul 7, 19:30 UTCJul 7, 20:45 UTC1h 15m
2026-07-07 N353MV SMO → SMO Jul 7, 18:35 UTCJul 7, 18:55 UTC20m
2026-07-07 N353MV SMO → SMO Jul 7, 16:15 UTCJul 7, 16:50 UTC35m
2026-07-06 N353MV SMO → SMO Jul 6, 20:35 UTCJul 6, 21:35 UTC1h 0m
2026-07-06 N353MV SMO → SMO Jul 6, 18:35 UTCJul 6, 18:45 UTC10m
2026-07-06 N353MV SMO → SMO Jul 6, 17:45 UTCJul 6, 18:05 UTC20m
2026-07-06 N353MV SMO → SMO Jul 6, 15:40 UTCJul 6, 16:45 UTC1h 5m
2026-07-06 N353MV SMO → SMO Jul 6, 00:40 UTCJul 6, 01:25 UTC45m
2026-07-05 N353MV SMO → SMO Jul 5, 21:45 UTCJul 5, 22:15 UTC30m
2026-07-05 N353MV SMO → SMO Jul 5, 18:45 UTCJul 5, 20:45 UTC2h 0m
2026-07-05 N353MV - Jul 5, 01:35 UTCJul 5, 01:40 UTC5m
2026-07-05 N353MV - Jul 5, 01:20 UTCJul 5, 01:30 UTC10m
2026-07-05 N353MV - Jul 5, 01:00 UTCJul 5, 01:05 UTC5m
2026-07-05 N353MV SMO → SMO Jul 5, 00:50 UTCJul 5, 00:55 UTC5m
2026-07-04 N353MV SMO → SMO Jul 4, 23:05 UTCJul 4, 23:35 UTC30m
2026-07-04 N353MV SMO → SMO Jul 4, 18:55 UTCJul 4, 20:45 UTC1h 50m
2026-07-04 N353MV - Jul 4, 17:40 UTCJul 4, 17:45 UTC5m
2026-07-04 N353MV SMO → SMO Jul 4, 17:20 UTCJul 4, 17:35 UTC15m
2026-07-04 N353MV SMO → SMO Jul 4, 16:55 UTCJul 4, 17:15 UTC20m
2026-07-04 N353MV SBA → SMO Jul 4, 00:30 UTCJul 4, 01:20 UTC50m
2026-07-03 N353MV SMO → SBA Jul 3, 22:35 UTCJul 3, 23:25 UTC50m
2026-07-03 N353MV SMO → SMO Jul 3, 20:30 UTCJul 3, 20:50 UTC20m
2026-07-03 N353MV SMO → SMO Jul 3, 19:40 UTCJul 3, 20:25 UTC45m
2026-07-03 N353MV SMO → SMO Jul 3, 17:35 UTCJul 3, 17:40 UTC5m
2026-07-03 N353MV SMO → SMO Jul 3, 17:15 UTCJul 3, 17:20 UTC5m

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

Mode-S A3F119 frequently asked

What is Mode-S code A3F119?
A3F119 is an ICAO 24-bit transponder address. Allocated to United States. Assigned to N353MV.
Where is Mode-S A3F119 registered?
Mode-S code A3F119 is allocated to United States (US). All aircraft registered there receive a Mode-S address from a fixed block defined by ICAO Annex 10.
Is A3F119 broadcasting right now?
No active broadcast right now. Last signal was 10h ago.
Hex, octal, and decimal Mode-S codes: what's the difference?
The same 24-bit identifier expressed in different bases: hex A3F119, octal 50770431, decimal 10,744,089.
What flights does A3F119 operate?
Mode-S A3F119 has broadcast 1 distinct callsign, including N353MV.