sensors Mode-S transponder

A27A83

ICAO 24-bit transponder address · allocated to United States

Currently assigned to N259SF · operated by TEXTRON AVIATION INC

Hex
A27A83
Octal
50475203
Decimal
10,648,195
Country
US
Tail
N259SF
Type
C172
No current signal · last broadcast 16h ago
Flights observed
119
Distinct callsigns
1
Country
US
Last broadcast
16h ago

Last known position

Most recent position reported by Mode-S A27A83.

Country allocation

The ICAO 24-bit address A27A83 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
N259SF - 119 2026-05-29

Recent flights last 50

DateFlightRouteTakeoffLandingDuration
2026-05-29 N259SF BJC → BJC May 29, 17:10 UTCMay 29, 18:15 UTC1h 5m
2026-05-28 N259SF BJC → BJC May 28, 21:20 UTCMay 28, 22:20 UTC1h 0m
2026-05-28 N259SF BJC → BJC May 28, 14:05 UTCMay 28, 15:10 UTC1h 5m
2026-05-27 N259SF BJC → BJC May 27, 19:10 UTCMay 27, 20:10 UTC1h 0m
2026-05-27 N259SF - May 27, 16:50 UTCMay 27, 18:15 UTC1h 25m
2026-05-27 N259SF BJC → BJC May 27, 14:50 UTCMay 27, 16:05 UTC1h 15m
2026-05-27 N259SF BJC → BJC May 27, 12:45 UTCMay 27, 13:55 UTC1h 10m
2026-05-27 N259SF BJC → BJC May 27, 01:49 UTCMay 27, 03:04 UTC1h 15m
2026-05-26 N259SF BJC → BJC May 26, 21:25 UTCMay 26, 22:50 UTC1h 25m
2026-05-26 N259SF BJC → BJC May 26, 18:10 UTCMay 26, 19:10 UTC1h 0m
2026-05-26 N259SF BJC → BJC May 26, 14:09 UTCMay 26, 15:39 UTC1h 30m
2026-05-26 N259SF BJC → BJC May 26, 01:14 UTCMay 26, 02:19 UTC1h 5m
2026-05-25 N259SF BJC → BJC May 25, 18:00 UTCMay 25, 18:40 UTC40m
2026-05-24 N259SF BJC → BJC May 24, 12:45 UTCMay 24, 13:20 UTC35m
2026-05-23 N259SF - May 23, 19:35 UTCMay 23, 20:25 UTC50m
2026-05-23 N259SF - May 23, 16:40 UTCMay 23, 17:30 UTC50m
2026-05-23 N259SF BJC → BJC May 23, 13:55 UTCMay 23, 15:00 UTC1h 5m
2026-05-22 N259SF BJC → BJC May 22, 20:35 UTCMay 22, 22:35 UTC2h 0m
2026-05-22 N259SF - May 22, 16:45 UTCMay 22, 17:15 UTC30m
2026-05-22 N259SF - May 22, 15:45 UTCMay 22, 16:40 UTC55m
2026-05-22 N259SF BJC → BJC May 22, 13:10 UTCMay 22, 14:00 UTC50m
2026-05-21 N259SF - May 21, 18:45 UTCMay 21, 19:50 UTC1h 5m
2026-05-21 N259SF - May 21, 17:30 UTCMay 21, 17:50 UTC20m
2026-05-21 N259SF - May 21, 16:10 UTCMay 21, 17:20 UTC1h 10m
2026-05-21 N259SF BJC → BJC May 21, 14:15 UTCMay 21, 15:15 UTC1h 0m
2026-05-21 N259SF BJC → BJC May 21, 01:05 UTCMay 21, 03:00 UTC1h 55m
2026-05-20 N259SF BJC → BJC May 20, 20:55 UTCMay 20, 22:15 UTC1h 20m
2026-05-20 N259SF BJC → BJC May 20, 18:55 UTCMay 20, 19:35 UTC40m
2026-05-19 N259SF BJC → BJC May 19, 21:25 UTCMay 19, 23:15 UTC1h 50m
2026-05-17 N259SF BJC → BJC May 17, 13:40 UTCMay 17, 14:35 UTC55m
2026-05-16 N259SF BJC → BJC May 16, 15:40 UTCMay 16, 16:55 UTC1h 15m
2026-05-15 N259SF BJC → BJC May 15, 23:10 UTCMay 16, 01:30 UTC2h 20m
2026-05-15 N259SF BJC → BJC May 15, 19:25 UTCMay 15, 20:45 UTC1h 20m
2026-05-15 N259SF BJC → BJC May 15, 17:35 UTCMay 15, 18:35 UTC1h 0m
2026-05-15 N259SF BJC → BJC May 15, 14:35 UTCMay 15, 16:10 UTC1h 34m
2026-05-15 N259SF - May 15, 03:50 UTCMay 15, 05:30 UTC1h 40m
2026-05-15 N259SF - May 15, 01:45 UTCMay 15, 02:40 UTC55m
2026-05-14 N259SF BJC → BJC May 14, 22:35 UTCMay 15, 00:00 UTC1h 25m
2026-05-14 N259SF BJC → BJC May 14, 13:10 UTCMay 14, 14:10 UTC1h 0m
2026-05-13 N259SF BJC → BJC May 13, 23:20 UTCMay 13, 23:25 UTC5m
2026-05-13 N259SF BJC → BJC May 13, 22:35 UTCMay 13, 22:45 UTC10m
2026-05-13 N259SF BJC → BJC May 13, 22:15 UTCMay 13, 22:30 UTC15m
2026-05-13 N259SF BJC → BJC May 13, 18:45 UTCMay 13, 20:15 UTC1h 30m
2026-05-13 N259SF BJC → BJC May 13, 16:00 UTCMay 13, 17:00 UTC1h 0m
2026-05-13 N259SF BJC → BJC May 13, 13:15 UTCMay 13, 14:35 UTC1h 20m
2026-05-13 N259SF BJC → BJC May 13, 03:25 UTCMay 13, 05:05 UTC1h 40m
2026-05-12 N259SF BJC → BJC May 12, 23:25 UTCMay 13, 00:30 UTC1h 5m
2026-05-12 N259SF BJC → BJC May 12, 20:15 UTCMay 12, 21:30 UTC1h 15m
2026-05-12 N259SF BJC → BJC May 12, 18:10 UTCMay 12, 19:00 UTC50m
2026-05-12 N259SF - May 12, 15:30 UTCMay 12, 16:25 UTC55m

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

Mode-S A27A83 frequently asked

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