sensors Mode-S transponder

A106B4

ICAO 24-bit transponder address · allocated to United States

Currently assigned to N16502 · EMBRAER ERJ-135 · operated by CORPORATE FLIGHT MANAGEMENT INC

Hex
A106B4
Octal
50203264
Decimal
10,553,012
Country
US
Tail
N16502
Type
E135
No current signal · last broadcast 2h ago
Flights observed
151
Distinct callsigns
20
Country
US
Last broadcast
2h ago

Last known position

Most recent position reported by Mode-S A106B4.

Country allocation

The ICAO 24-bit address A106B4 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 20 distinct

Recent flights last 50

DateFlightRouteTakeoffLandingDuration
2026-05-30 VTE3388 PHX → SOW May 30, 02:35 UTCMay 30, 02:50 UTC15m
2026-05-29 VTE3397 VEL → PHX May 29, 23:55 UTCMay 30, 01:05 UTC1h 10m
2026-05-29 VTE3390 PHX → VEL May 29, 21:15 UTCMay 29, 22:15 UTC1h 0m
2026-05-29 VTE3385 SOW → PHX May 29, 19:05 UTCMay 29, 19:30 UTC25m
2026-05-29 VTE3386 PHX → SOW May 29, 17:20 UTCMay 29, 17:35 UTC15m
2026-05-29 VTE3383 SOW → PHX May 29, 15:30 UTCMay 29, 15:50 UTC20m
2026-05-29 VTE3388 PHX → SOW May 29, 02:15 UTCMay 29, 02:35 UTC20m
2026-05-28 VTE3397 VEL → PHX May 28, 23:25 UTCMay 29, 00:45 UTC1h 20m
2026-05-28 VTE3390 PHX → VEL May 28, 21:15 UTCMay 28, 22:15 UTC1h 0m
2026-05-28 VTE3385 SOW → PHX May 28, 19:25 UTCMay 28, 19:45 UTC20m
2026-05-28 VTE3386 PHX → SOW May 28, 17:45 UTCMay 28, 18:00 UTC15m
2026-05-28 VTE3383 SOW → PHX May 28, 15:50 UTCMay 28, 16:10 UTC20m
2026-05-28 VTE3388 PHX → SOW May 28, 02:20 UTCMay 28, 02:35 UTC15m
2026-05-27 VTE3385 SOW → PHX May 27, 19:20 UTCMay 27, 19:40 UTC20m
2026-05-27 VTE3388 PHX → SOW May 27, 02:14 UTCMay 27, 02:34 UTC20m
2026-05-26 VTE3390 PHX → VEL May 26, 21:14 UTCMay 26, 22:20 UTC1h 5m
2026-05-26 VTE3385 SOW → PHX May 26, 19:20 UTCMay 26, 19:40 UTC20m
2026-05-26 VTE3386 PHX → SOW May 26, 17:35 UTCMay 26, 17:50 UTC15m
2026-05-26 VTE3383 SOW → PHX May 26, 15:39 UTCMay 26, 16:05 UTC25m
2026-05-26 VTE3388 PHX → SOW May 26, 02:44 UTCMay 26, 03:00 UTC15m
2026-05-25 VTE3397 VEL → PHX May 25, 23:24 UTCMay 26, 00:44 UTC1h 20m
2026-05-25 VTE3390 PHX → VEL May 25, 21:09 UTCMay 25, 22:25 UTC1h 15m
2026-05-25 VTE3385 SOW → PHX May 25, 19:20 UTCMay 25, 19:40 UTC20m
2026-05-25 VTE3386 PHX → SOW May 25, 17:40 UTCMay 25, 18:00 UTC20m
2026-05-25 VTE3383 SOW → PHX May 25, 15:30 UTCMay 25, 15:50 UTC20m
2026-05-25 VTE3388 PHX → SOW May 25, 03:00 UTCMay 25, 03:20 UTC20m
2026-05-24 VTE3390 PHX → VEL May 24, 23:00 UTCMay 24, 23:46 UTC46m
2026-05-24 VTE3385 SOW → PHX May 24, 20:30 UTCMay 24, 20:50 UTC20m
2026-05-24 VTE3386 PHX → SOW May 24, 19:15 UTCMay 24, 19:35 UTC20m
2026-05-24 VTE3383 SOW → PHX May 24, 15:40 UTCMay 24, 16:00 UTC20m
2026-05-23 VTE3386 PHX → SOW May 23, 17:30 UTCMay 23, 17:45 UTC15m
2026-05-23 VTE3383 SOW → PHX May 23, 15:55 UTCMay 23, 16:20 UTC25m
2026-05-23 VTE3388 PHX → SOW May 23, 02:15 UTCMay 23, 02:35 UTC19m
2026-05-22 VTE3397 VEL → PHX May 22, 23:25 UTCMay 23, 00:25 UTC1h 0m
2026-05-22 VTE3390 PHX → VEL May 22, 21:05 UTCMay 22, 22:10 UTC1h 5m
2026-05-22 VTE3385 SOW → PHX May 22, 19:20 UTCMay 22, 19:40 UTC20m
2026-05-22 VTE3386 PHX → SOW May 22, 17:40 UTCMay 22, 17:45 UTC5m
2026-05-22 VTE3383 SOW → PHX May 22, 15:15 UTCMay 22, 15:40 UTC25m
2026-05-22 VTE3388 PHX → SOW May 22, 02:15 UTCMay 22, 02:35 UTC20m
2026-05-21 VTE3397 VEL → PHX May 21, 23:35 UTCMay 22, 00:40 UTC1h 5m
2026-05-21 VTE3390 PHX → VEL May 21, 21:15 UTCMay 21, 22:25 UTC1h 10m
2026-05-21 VTE3385 SOW → PHX May 21, 19:10 UTCMay 21, 19:35 UTC25m
2026-05-21 VTE3386 PHX → SOW May 21, 17:40 UTCMay 21, 17:55 UTC15m
2026-05-21 VTE3383 SOW → PHX May 21, 15:40 UTCMay 21, 16:01 UTC20m
2026-05-21 VTE3388 PHX → SOW May 21, 02:10 UTCMay 21, 02:30 UTC20m
2026-05-20 VTE3385 SOW → PHX May 20, 19:30 UTCMay 20, 19:55 UTC25m
2026-05-20 VTE3388 PHX → SOW May 20, 02:20 UTCMay 20, 02:35 UTC15m
2026-05-19 VTE3397 VEL → PHX May 19, 23:20 UTCMay 20, 00:40 UTC1h 20m
2026-05-19 VTE3390 PHX → VEL May 19, 21:15 UTCMay 19, 22:20 UTC1h 5m
2026-05-19 VTE3385 SOW → PHX May 19, 19:40 UTCMay 19, 19:55 UTC15m

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

Mode-S A106B4 frequently asked

What is Mode-S code A106B4?
A106B4 is an ICAO 24-bit transponder address. Allocated to United States. Assigned to N16502.
Where is Mode-S A106B4 registered?
Mode-S code A106B4 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 A106B4 broadcasting right now?
No active broadcast right now. Last signal was 2h ago.
Hex, octal, and decimal Mode-S codes: what's the difference?
The same 24-bit identifier expressed in different bases: hex A106B4, octal 50203264, decimal 10,553,012.
What flights does A106B4 operate?
Mode-S A106B4 has broadcast 20 distinct callsigns, including VTE3385, VTE3388, VTE3386, VTE3383, VTE3390.