Apparatus

Try JFK, AAL1290, BAW, or N225AN.

sensors Mode-S transponder

A28F6F

ICAO 24-bit transponder address · allocated to United States

Currently assigned to N264SF · operated by TEXTRON AVIATION INC

Hex
A28F6F
Octal
50507557
Decimal
10,653,551
Country
US
Tail
N264SF
Type
C172
No current signal · last broadcast 16m ago
Flights observed
142
Distinct callsigns
1
Country
US
Last broadcast
16m ago

Last known position

Most recent position reported by Mode-S A28F6F.

Country allocation

The ICAO 24-bit address A28F6F 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
N264SF - 142 2026-05-30

Recent flights last 50

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

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

Mode-S A28F6F frequently asked

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