Apparatus

Try JFK, AAL1290, BAW, or N225AN.

sensors Mode-S transponder

A7F05C

ICAO 24-bit transponder address · allocated to United States

Currently assigned to N610SP · CESSNA 172 Skyhawk · operated by POCKET ROCKET LLC

Hex
A7F05C
Octal
51770134
Decimal
11,006,044
Country
US
Tail
N610SP
Type
C172
No current signal · last broadcast Jul 25, 22:45 UTC
Flights observed
140
Distinct callsigns
1
Country
US
Last broadcast
Jul 25, 22:45 UTC

Last known position

Most recent position reported by Mode-S A7F05C.

Country allocation

The ICAO 24-bit address A7F05C 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
N610SP - 140 2026-07-25

Recent flights last 50

DateFlightRouteTakeoffLandingDuration
2026-07-25 N610SP SQL → SQL Jul 25, 21:45 UTCJul 25, 22:45 UTC1h 0m
2026-07-25 N610SP - Jul 25, 20:00 UTCJul 25, 20:15 UTC15m
2026-07-25 N610SP SQL → SQL Jul 25, 19:45 UTCJul 25, 19:55 UTC10m
2026-07-25 N610SP SQL → SQL Jul 25, 18:40 UTCJul 25, 19:30 UTC50m
2026-07-20 N610SP SQL → PAO Jul 20, 14:50 UTCJul 20, 14:55 UTC5m
2026-07-20 N610SP SQL → SQL Jul 20, 01:45 UTCJul 20, 02:15 UTC30m
2026-07-18 N610SP - Jul 18, 19:55 UTCJul 18, 20:50 UTC55m
2026-07-17 N610SP - Jul 17, 21:10 UTCJul 17, 21:55 UTC45m
2026-07-17 N610SP SQL → SQL Jul 17, 17:40 UTCJul 17, 19:09 UTC1h 30m
2026-07-17 N610SP - Jul 17, 00:55 UTCJul 17, 01:59 UTC1h 5m
2026-07-16 N610SP - Jul 16, 19:14 UTCJul 16, 20:29 UTC1h 15m
2026-07-16 N610SP SQL → SQL Jul 16, 17:10 UTCJul 16, 17:30 UTC20m
2026-07-15 N610SP - Jul 15, 22:50 UTCJul 15, 23:15 UTC25m
2026-07-15 N610SP SQL → HWD Jul 15, 22:00 UTCJul 15, 22:35 UTC35m
2026-07-14 N610SP SQL → SQL Jul 14, 22:20 UTCJul 14, 23:00 UTC39m
2026-07-14 N610SP - Jul 14, 18:20 UTCJul 14, 19:10 UTC50m
2026-07-14 N610SP - Jul 14, 17:30 UTCJul 14, 18:15 UTC45m
2026-07-12 N610SP - Jul 12, 21:10 UTCJul 12, 22:40 UTC1h 30m
2026-07-12 N610SP - Jul 12, 18:25 UTCJul 12, 19:50 UTC1h 25m
2026-07-11 N610SP - Jul 11, 23:50 UTCJul 12, 01:15 UTC1h 25m
2026-07-11 N610SP - Jul 11, 21:40 UTCJul 11, 22:30 UTC50m
2026-07-11 N610SP - Jul 11, 18:00 UTCJul 11, 19:15 UTC1h 15m
2026-07-10 N610SP - Jul 10, 18:45 UTCJul 10, 20:30 UTC1h 45m
2026-07-10 N610SP SQL → SQL Jul 10, 01:25 UTCJul 10, 01:55 UTC30m
2026-07-09 N610SP SQL → SQL Jul 9, 19:25 UTCJul 9, 20:30 UTC1h 5m
2026-07-08 N610SP - Jul 8, 23:30 UTCJul 8, 23:45 UTC15m
2026-07-08 N610SP HWD → HWD Jul 8, 23:10 UTCJul 8, 23:25 UTC15m
2026-07-08 N610SP SQL → HWD Jul 8, 22:15 UTCJul 8, 22:35 UTC20m
2026-07-08 N610SP - Jul 8, 20:00 UTCJul 8, 20:35 UTC35m
2026-07-06 N610SP - Jul 6, 19:45 UTCJul 6, 20:35 UTC50m
2026-07-05 N610SP SQL → SQL Jul 5, 23:15 UTCJul 5, 23:45 UTC30m
2026-07-05 N610SP SQL → SQL Jul 5, 18:10 UTCJul 5, 19:05 UTC55m
2026-07-03 N610SP SQL → SQL Jul 3, 01:30 UTCJul 3, 01:35 UTC5m
2026-07-02 N610SP - Jul 2, 20:00 UTCJul 2, 20:10 UTC10m
2026-07-02 N610SP SQL → LVK Jul 2, 18:45 UTCJul 2, 19:25 UTC40m
2026-07-01 N610SP SQL → SQL Jul 1, 18:00 UTCJul 1, 19:05 UTC1h 5m
2026-06-30 N610SP SQL → SQL Jun 30, 19:00 UTCJun 30, 20:05 UTC1h 5m
2026-06-30 N610SP - Jun 30, 16:35 UTCJun 30, 16:45 UTC10m
2026-06-29 N610SP SQL → SQL Jun 29, 22:00 UTCJun 29, 22:24 UTC25m
2026-06-29 N610SP SQL → SQL Jun 29, 20:00 UTCJun 29, 20:35 UTC35m
2026-06-28 N610SP - Jun 28, 23:09 UTCJun 28, 23:50 UTC40m
2026-06-28 N610SP SQL → SQL Jun 28, 19:04 UTCJun 28, 19:20 UTC15m
2026-06-28 N610SP SQL → SQL Jun 28, 18:44 UTCJun 28, 18:59 UTC15m
2026-06-28 N610SP - Jun 28, 18:29 UTCJun 28, 18:40 UTC10m
2026-06-28 N610SP SQL → SQL Jun 28, 18:00 UTCJun 28, 18:25 UTC25m
2026-06-26 N610SP - Jun 26, 00:24 UTCJun 26, 00:50 UTC25m
2026-06-25 N610SP - Jun 25, 21:29 UTCJun 25, 22:54 UTC1h 25m
2026-06-25 N610SP SQL → SQL Jun 25, 19:54 UTCJun 25, 20:05 UTC10m
2026-06-25 N610SP SQL → SQL Jun 25, 19:09 UTCJun 25, 19:29 UTC20m
2026-06-24 N610SP HWD → SQL Jun 24, 23:40 UTCJun 24, 23:59 UTC20m

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

Mode-S A7F05C frequently asked

What is Mode-S code A7F05C?
A7F05C is an ICAO 24-bit transponder address. Allocated to United States. Assigned to N610SP.
Where is Mode-S A7F05C registered?
Mode-S code A7F05C 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 A7F05C broadcasting right now?
No active broadcast right now. Last signal was Jul 25, 22:45 UTC.
Hex, octal, and decimal Mode-S codes: what's the difference?
The same 24-bit identifier expressed in different bases: hex A7F05C, octal 51770134, decimal 11,006,044.
What flights does A7F05C operate?
Mode-S A7F05C has broadcast 1 distinct callsign, including N610SP.