Apparatus

Try JFK, AAL1290, BAW, or N225AN.

sensors Mode-S transponder

A11316

ICAO 24-bit transponder address · allocated to United States

Currently assigned to N16894 · CESSNA 172 Skyhawk · operated by SAZ DYNAMICS LLC

Hex
A11316
Octal
50211426
Decimal
10,556,182
Country
US
Tail
N16894
Type
C172
No current signal · last broadcast 13d ago
Flights observed
173
Distinct callsigns
1
Country
US
Last broadcast
13d ago

Last known position

Most recent position reported by Mode-S A11316.

Country allocation

The ICAO 24-bit address A11316 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
N16894 - 173 2026-07-26

Recent flights last 50

DateFlightRouteTakeoffLandingDuration
2026-07-26 N16894 - Jul 26, 20:10 UTCJul 26, 20:35 UTC25m
2026-07-26 N16894 PAO → PAO Jul 26, 16:30 UTCJul 26, 18:25 UTC1h 55m
2026-07-26 N16894 HWD → PAO Jul 26, 00:00 UTCJul 26, 00:10 UTC10m
2026-07-25 N16894 PAO → HWD Jul 25, 22:10 UTCJul 25, 22:50 UTC40m
2026-07-25 N16894 - Jul 25, 19:20 UTCJul 25, 20:25 UTC1h 5m
2026-07-25 N16894 - Jul 25, 18:15 UTCJul 25, 18:45 UTC30m
2026-07-24 N16894 PAO → PAO Jul 24, 17:45 UTCJul 24, 21:10 UTC3h 25m
2026-07-22 N16894 PAO → PAO Jul 22, 02:00 UTCJul 22, 02:45 UTC45m
2026-07-21 N16894 PAO → PAO Jul 21, 20:05 UTCJul 21, 20:25 UTC20m
2026-07-20 N16894 PAO → PAO Jul 20, 20:45 UTCJul 20, 21:25 UTC40m
2026-07-19 N16894 PAO → PAO Jul 19, 23:05 UTCJul 19, 23:25 UTC20m
2026-07-18 N16894 PAO → PAO Jul 18, 22:35 UTCJul 18, 23:35 UTC1h 0m
2026-07-18 N16894 PAO → PAO Jul 18, 17:15 UTCJul 18, 18:35 UTC1h 20m
2026-07-17 N16894 SJC → PAO Jul 17, 17:05 UTCJul 17, 17:15 UTC10m
2026-07-08 N16894 PAO → SJC Jul 8, 21:20 UTCJul 8, 21:30 UTC10m
2026-07-07 N16894 PAO → PAO Jul 7, 22:55 UTCJul 7, 23:25 UTC30m
2026-07-06 N16894 PAO → PAO Jul 6, 16:15 UTCJul 6, 17:20 UTC1h 5m
2026-07-05 N16894 PAO → PAO Jul 5, 19:30 UTCJul 5, 21:30 UTC2h 0m
2026-07-05 N16894 PAO → PAO Jul 5, 17:30 UTCJul 5, 18:05 UTC35m
2026-07-04 N16894 - Jul 4, 19:35 UTCJul 4, 20:30 UTC55m
2026-07-04 N16894 PAO → PAO Jul 4, 19:10 UTCJul 4, 19:20 UTC10m
2026-07-03 N16894 PAO → PAO Jul 3, 18:45 UTCJul 3, 19:45 UTC1h 0m
2026-07-03 N16894 PAO → PAO Jul 3, 18:20 UTCJul 3, 18:25 UTC5m
2026-07-03 N16894 PAO → PAO Jul 3, 15:20 UTCJul 3, 15:30 UTC10m
2026-07-03 N16894 PAO → PAO Jul 3, 15:10 UTCJul 3, 15:15 UTC5m
2026-07-02 N16894 PAO → PAO Jul 2, 17:45 UTCJul 2, 19:20 UTC1h 35m
2026-07-01 N16894 - Jul 1, 18:45 UTCJul 1, 19:30 UTC45m
2026-07-01 N16894 - Jul 1, 18:30 UTCJul 1, 18:40 UTC10m
2026-07-01 N16894 PAO → SQL Jul 1, 18:10 UTCJul 1, 18:20 UTC10m
2026-06-29 N16894 PAO → PAO Jun 29, 22:39 UTCJun 29, 23:14 UTC35m
2026-06-29 N16894 PAO → PAO Jun 29, 18:49 UTCJun 29, 19:00 UTC10m
2026-06-29 N16894 PAO → PAO Jun 29, 18:19 UTCJun 29, 18:30 UTC10m
2026-06-29 N16894 PAO → PAO Jun 29, 18:05 UTCJun 29, 18:14 UTC10m
2026-06-29 N16894 PAO → PAO Jun 29, 17:49 UTCJun 29, 17:59 UTC10m
2026-06-29 N16894 PAO → PAO Jun 29, 17:34 UTCJun 29, 17:45 UTC10m
2026-06-29 N16894 PAO → PAO Jun 29, 17:24 UTCJun 29, 17:30 UTC5m
2026-06-28 N16894 - Jun 28, 21:30 UTCJun 28, 22:20 UTC50m
2026-06-28 N16894 PAO → HWD Jun 28, 21:10 UTCJun 28, 21:20 UTC10m
2026-06-28 N16894 HWD → PAO Jun 28, 17:34 UTCJun 28, 17:50 UTC15m
2026-06-28 N16894 PAO → HWD Jun 28, 17:00 UTCJun 28, 17:30 UTC30m
2026-06-27 N16894 PAO → PAO Jun 27, 21:44 UTCJun 27, 22:29 UTC45m
2026-06-27 N16894 PAO → PAO Jun 27, 16:55 UTCJun 27, 17:25 UTC30m
2026-06-26 N16894 - Jun 26, 20:15 UTCJun 26, 20:24 UTC10m
2026-06-26 N16894 PAO → PAO Jun 26, 19:50 UTCJun 26, 20:10 UTC20m
2026-06-25 N16894 PAO → PAO Jun 25, 19:54 UTCJun 25, 20:49 UTC55m
2026-06-24 N16894 PAO → PAO Jun 24, 23:54 UTCJun 25, 00:44 UTC50m
2026-06-24 N16894 PAO → PAO Jun 24, 20:05 UTCJun 24, 21:50 UTC1h 45m
2026-06-22 N16894 PAO → PAO Jun 22, 17:44 UTCJun 22, 18:35 UTC50m
2026-06-20 N16894 PAO → PAO Jun 20, 16:29 UTCJun 20, 16:39 UTC10m
2026-06-20 N16894 PAO → PAO Jun 20, 15:49 UTCJun 20, 16:14 UTC25m

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

Mode-S A11316 frequently asked

What is Mode-S code A11316?
A11316 is an ICAO 24-bit transponder address. Allocated to United States. Assigned to N16894.
Where is Mode-S A11316 registered?
Mode-S code A11316 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 A11316 broadcasting right now?
No active broadcast right now. Last signal was 13d ago.
Hex, octal, and decimal Mode-S codes: what's the difference?
The same 24-bit identifier expressed in different bases: hex A11316, octal 50211426, decimal 10,556,182.
What flights does A11316 operate?
Mode-S A11316 has broadcast 1 distinct callsign, including N16894.