Apparatus

Try JFK, AAL1290, BAW, or N225AN.

sensors Mode-S transponder

A813AA

ICAO 24-bit transponder address · allocated to United States

Currently assigned to N6198N · CESSNA 172 Skyhawk · operated by CHRISTIANSEN AVIATION LLC

Hex
A813AA
Octal
52011652
Decimal
11,015,082
Country
US
Tail
N6198N
Type
C172
No current signal · last broadcast Jul 26, 21:10 UTC
Flights observed
277
Distinct callsigns
2
Country
US
Last broadcast
Jul 26, 21:10 UTC

Last known position

Most recent position reported by Mode-S A813AA.

Country allocation

The ICAO 24-bit address A813AA 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 2 distinct

Callsign Airline Flights Last seen
BYF30 - 275 2026-07-26
NGF6291 - 2 2026-07-24

Recent flights last 50

DateFlightRouteTakeoffLandingDuration
2026-07-26 BYF30 - Jul 26, 20:30 UTCJul 26, 21:10 UTC40m
2026-07-26 BYF30 - Jul 26, 17:25 UTCJul 26, 18:05 UTC40m
2026-07-25 BYF30 SQL → SQL Jul 25, 14:40 UTCJul 25, 15:40 UTC1h 0m
2026-07-24 BYF30 SQL → SQL Jul 24, 22:50 UTCJul 25, 00:25 UTC1h 35m
2026-07-24 BYF30 SQL → SQL Jul 24, 19:50 UTCJul 24, 21:00 UTC1h 10m
2026-07-24 BYF30 MCE → SQL Jul 24, 02:05 UTCJul 24, 03:50 UTC1h 45m
2026-07-24 NGF6291 SQL → MCE Jul 24, 00:35 UTCJul 24, 01:25 UTC50m
2026-07-23 BYF30 SQL → SQL Jul 23, 21:05 UTCJul 23, 21:50 UTC45m
2026-07-22 BYF30 SQL → SQL Jul 22, 23:40 UTCJul 22, 23:55 UTC15m
2026-07-22 BYF30 - Jul 22, 19:45 UTCJul 22, 20:55 UTC1h 10m
2026-07-22 BYF30 - Jul 22, 18:40 UTCJul 22, 19:30 UTC50m
2026-07-22 BYF30 - Jul 22, 00:30 UTCJul 22, 01:00 UTC30m
2026-07-21 BYF30 - Jul 21, 22:55 UTCJul 21, 23:55 UTC1h 0m
2026-07-21 BYF30 SQL → SQL Jul 21, 01:45 UTCJul 21, 03:05 UTC1h 20m
2026-07-20 BYF30 SQL → SQL Jul 20, 21:35 UTCJul 20, 23:10 UTC1h 35m
2026-07-20 BYF30 - Jul 20, 00:05 UTCJul 20, 03:15 UTC3h 10m
2026-07-19 BYF30 HIO → RDD Jul 19, 19:45 UTCJul 19, 23:10 UTC3h 25m
2026-07-19 BYF30 - Jul 19, 00:20 UTCJul 19, 02:20 UTC2h 0m
2026-07-18 BYF30 - Jul 18, 21:00 UTCJul 18, 21:35 UTC35m
2026-07-18 BYF30 YDT → BLI Jul 18, 18:50 UTCJul 18, 19:45 UTC55m
2026-07-18 BYF30 RSJ → YDT Jul 18, 00:45 UTCJul 18, 01:10 UTC25m
2026-07-17 BYF30 - Jul 17, 19:05 UTCJul 17, 20:15 UTC1h 10m
2026-07-16 BYF30 - Jul 16, 23:20 UTCJul 17, 01:05 UTC1h 45m
2026-07-16 BYF30 - Jul 16, 19:14 UTCJul 16, 22:05 UTC2h 50m
2026-07-16 BYF30 SQL → RDD Jul 16, 16:09 UTCJul 16, 18:10 UTC2h 0m
2026-07-16 BYF30 SQL → SQL Jul 16, 02:30 UTCJul 16, 02:45 UTC15m
2026-07-16 BYF30 SQL → SQL Jul 16, 02:15 UTCJul 16, 02:25 UTC10m
2026-07-16 BYF30 SQL → SQL Jul 16, 02:05 UTCJul 16, 02:10 UTC5m
2026-07-15 BYF30 SQL → SQL Jul 15, 17:25 UTCJul 15, 17:55 UTC30m
2026-07-15 BYF30 SQL → SQL Jul 15, 15:45 UTCJul 15, 16:10 UTC25m
2026-07-15 BYF30 PAO → SQL Jul 15, 00:35 UTCJul 15, 00:45 UTC10m
2026-07-14 BYF30 SQL → PAO Jul 14, 17:20 UTCJul 14, 17:25 UTC5m
2026-07-14 BYF30 SQL → SQL Jul 14, 04:00 UTCJul 14, 05:35 UTC1h 35m
2026-07-13 BYF30 SQL → SQL Jul 13, 22:30 UTCJul 13, 23:50 UTC1h 20m
2026-07-13 BYF30 SQL → SQL Jul 13, 18:30 UTCJul 13, 20:55 UTC2h 25m
2026-07-12 BYF30 SQL → SQL Jul 12, 18:45 UTCJul 12, 19:50 UTC1h 5m
2026-07-12 BYF30 SQL → SQL Jul 12, 18:35 UTCJul 12, 18:40 UTC5m
2026-07-12 BYF30 SQL → SQL Jul 12, 00:55 UTCJul 12, 02:20 UTC1h 25m
2026-07-11 BYF30 - Jul 11, 03:25 UTCJul 11, 04:01 UTC35m
2026-07-11 BYF30 - Jul 11, 00:30 UTCJul 11, 01:05 UTC35m
2026-07-10 BYF30 SQL → SQL Jul 10, 20:55 UTCJul 10, 22:05 UTC1h 10m
2026-07-10 BYF30 - Jul 10, 18:25 UTCJul 10, 18:30 UTC5m
2026-07-10 BYF30 SQL → SQL Jul 10, 17:55 UTCJul 10, 18:00 UTC5m
2026-07-09 BYF30 SQL → SQL Jul 9, 21:40 UTCJul 9, 23:05 UTC1h 25m
2026-07-09 BYF30 SQL → SQL Jul 9, 18:15 UTCJul 9, 19:50 UTC1h 35m
2026-07-09 BYF30 SQL → SQL Jul 9, 02:20 UTCJul 9, 02:25 UTC5m
2026-07-09 BYF30 - Jul 9, 02:00 UTCJul 9, 02:15 UTC15m
2026-07-09 BYF30 SQL → SQL Jul 9, 01:30 UTCJul 9, 01:35 UTC5m
2026-07-06 BYF30 SQL → SQL Jul 6, 01:20 UTCJul 6, 02:50 UTC1h 30m
2026-07-05 BYF30 - Jul 5, 22:30 UTCJul 5, 23:40 UTC1h 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 N6198N page for operator, model, and routing details .

Mode-S A813AA frequently asked

What is Mode-S code A813AA?
A813AA is an ICAO 24-bit transponder address. Allocated to United States. Assigned to N6198N.
Where is Mode-S A813AA registered?
Mode-S code A813AA 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 A813AA broadcasting right now?
No active broadcast right now. Last signal was Jul 26, 21:10 UTC.
Hex, octal, and decimal Mode-S codes: what's the difference?
The same 24-bit identifier expressed in different bases: hex A813AA, octal 52011652, decimal 11,015,082.
What flights does A813AA operate?
Mode-S A813AA has broadcast 2 distinct callsigns, including BYF30, NGF6291.