Apparatus

Try JFK, AAL1290, BAW, or N225AN.

sensors Mode-S transponder

A28BB8

ICAO 24-bit transponder address · allocated to United States

Currently assigned to N263SF · operated by TEXTRON AVIATION INC

Hex
A28BB8
Octal
50505670
Decimal
10,652,600
Country
US
Tail
N263SF
Type
C172
No current signal · last broadcast 17h ago
Flights observed
250
Distinct callsigns
1
Country
US
Last broadcast
17h ago

Last known position

Most recent position reported by Mode-S A28BB8.

Country allocation

The ICAO 24-bit address A28BB8 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
N263SF - 250 2026-07-13

Recent flights last 50

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

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

Mode-S A28BB8 frequently asked

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