sensors Mode-S transponder

A296E5

ICAO 24-bit transponder address · allocated to United States

Currently assigned to N266SP · CESSNA 172 Skyhawk · operated by CZJ FLYING INC

Hex
A296E5
Octal
50513345
Decimal
10,655,461
Country
US
Tail
N266SP
Type
C172
Broadcasting now · callsign N266SP · 5,300 ft
Flights observed
212
Distinct callsigns
1
Country
US
Last broadcast
17h ago

Current position

A296E5 is currently broadcasting. Map zoomed to live position.

Country allocation

The ICAO 24-bit address A296E5 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
N266SP - 212 2026-07-13

Recent flights last 50

DateFlightRouteTakeoffLandingDuration
2026-07-13 N266SP - Jul 13, 20:15 UTCJul 13, 21:30 UTC1h 15m
2026-07-13 N266SP - Jul 13, 17:20 UTCJul 13, 18:15 UTC55m
2026-07-13 N266SP FNL → FNL Jul 13, 15:35 UTCJul 13, 16:20 UTC45m
2026-07-12 N266SP - Jul 12, 17:01 UTCJul 12, 18:35 UTC1h 35m
2026-07-12 N266SP FNL → FNL Jul 12, 14:01 UTCJul 12, 15:20 UTC1h 20m
2026-07-11 N266SP FNL → FNL Jul 11, 19:55 UTCJul 11, 20:55 UTC1h 0m
2026-07-11 N266SP - Jul 11, 16:50 UTCJul 11, 18:20 UTC1h 30m
2026-07-11 N266SP - Jul 11, 14:15 UTCJul 11, 15:45 UTC1h 30m
2026-07-11 N266SP - Jul 11, 04:25 UTCJul 11, 05:45 UTC1h 20m
2026-07-11 N266SP - Jul 11, 03:25 UTCJul 11, 04:20 UTC55m
2026-07-10 N266SP - Jul 10, 19:55 UTCJul 10, 20:35 UTC40m
2026-07-10 N266SP - Jul 10, 17:35 UTCJul 10, 18:30 UTC55m
2026-07-10 N266SP - Jul 10, 13:55 UTCJul 10, 15:20 UTC1h 25m
2026-07-07 N266SP - Jul 7, 18:10 UTCJul 7, 19:00 UTC50m
2026-07-07 N266SP - Jul 7, 15:15 UTCJul 7, 16:40 UTC1h 25m
2026-07-06 N266SP FNL → FNL Jul 6, 19:50 UTCJul 6, 21:05 UTC1h 15m
2026-07-06 N266SP FNL → FNL Jul 6, 16:20 UTCJul 6, 18:05 UTC1h 45m
2026-07-05 N266SP FNL → FNL Jul 5, 16:50 UTCJul 5, 17:55 UTC1h 5m
2026-07-03 N266SP - Jul 3, 21:50 UTCJul 3, 22:55 UTC1h 5m
2026-07-03 N266SP FNL → FNL Jul 3, 19:20 UTCJul 3, 20:45 UTC1h 25m
2026-07-02 N266SP - Jul 2, 19:45 UTCJul 2, 21:10 UTC1h 25m
2026-07-02 N266SP - Jul 2, 17:30 UTCJul 2, 18:20 UTC50m
2026-07-02 N266SP FNL → FNL Jul 2, 13:25 UTCJul 2, 15:25 UTC2h 0m
2026-07-01 N266SP - Jul 1, 23:55 UTCJul 2, 01:25 UTC1h 30m
2026-07-01 N266SP - Jul 1, 19:20 UTCJul 1, 20:25 UTC1h 5m
2026-07-01 N266SP FNL → FNL Jul 1, 13:45 UTCJul 1, 14:45 UTC1h 0m
2026-06-30 N266SP - Jun 30, 20:50 UTCJun 30, 21:50 UTC1h 0m
2026-06-30 N266SP - Jun 30, 16:55 UTCJun 30, 17:35 UTC40m
2026-06-29 N266SP - Jun 29, 19:35 UTCJun 29, 20:00 UTC25m
2026-06-29 N266SP - Jun 29, 16:59 UTCJun 29, 18:25 UTC1h 25m
2026-06-29 N266SP - Jun 29, 13:39 UTCJun 29, 14:04 UTC25m
2026-06-28 N266SP FNL → FNL Jun 28, 19:55 UTCJun 28, 21:50 UTC1h 55m
2026-06-28 N266SP FNL → FNL Jun 28, 14:50 UTCJun 28, 16:00 UTC1h 10m
2026-06-27 N266SP - Jun 27, 16:24 UTCJun 27, 17:34 UTC1h 10m
2026-06-26 N266SP FNL → FNL Jun 26, 17:35 UTCJun 26, 18:20 UTC45m
2026-06-26 N266SP FNL → FNL Jun 26, 13:49 UTCJun 26, 15:54 UTC2h 5m
2026-06-24 N266SP - Jun 24, 19:49 UTCJun 24, 20:44 UTC55m
2026-06-23 N266SP - Jun 23, 20:24 UTCJun 23, 21:34 UTC1h 10m
2026-06-23 N266SP FNL → FNL Jun 23, 16:39 UTCJun 23, 18:14 UTC1h 35m
2026-06-23 N266SP FNL → FNL Jun 23, 13:45 UTCJun 23, 14:25 UTC40m
2026-06-22 N266SP - Jun 22, 23:05 UTCJun 23, 00:45 UTC1h 40m
2026-06-22 N266SP FNL → FNL Jun 22, 20:00 UTCJun 22, 21:19 UTC1h 20m
2026-06-22 N266SP FNL → FNL Jun 22, 14:45 UTCJun 22, 15:14 UTC30m
2026-06-22 N266SP FNL → FNL Jun 22, 12:44 UTCJun 22, 14:10 UTC1h 25m
2026-06-22 N266SP FNL → FNL Jun 22, 01:00 UTCJun 22, 01:44 UTC45m
2026-06-21 N266SP - Jun 21, 21:24 UTCJun 21, 22:54 UTC1h 30m
2026-06-21 N266SP - Jun 21, 18:10 UTCJun 21, 19:05 UTC55m
2026-06-20 N266SP FNL → FNL Jun 20, 20:20 UTCJun 20, 21:14 UTC55m
2026-06-20 N266SP FNL → FNL Jun 20, 18:10 UTCJun 20, 18:54 UTC45m
2026-06-20 N266SP FNL → FNL Jun 20, 00:09 UTCJun 20, 01:34 UTC1h 25m

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

Mode-S A296E5 frequently asked

What is Mode-S code A296E5?
A296E5 is an ICAO 24-bit transponder address. Allocated to United States. Assigned to N266SP.
Where is Mode-S A296E5 registered?
Mode-S code A296E5 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 A296E5 broadcasting right now?
Yes. Mode-S A296E5 is currently airborne.
Hex, octal, and decimal Mode-S codes: what's the difference?
The same 24-bit identifier expressed in different bases: hex A296E5, octal 50513345, decimal 10,655,461.
What flights does A296E5 operate?
Mode-S A296E5 has broadcast 1 distinct callsign, including N266SP.