Apparatus

Try JFK, AAL1290, BAW, or N225AN.

sensors Mode-S transponder

A26F5E

ICAO 24-bit transponder address · allocated to United States

Currently assigned to N256SF · operated by TEXTRON AVIATION INC

Hex
A26F5E
Octal
50467536
Decimal
10,645,342
Country
US
Tail
N256SF
Type
C172
No current signal · last broadcast 17h ago
Flights observed
223
Distinct callsigns
1
Country
US
Last broadcast
17h ago

Last known position

Most recent position reported by Mode-S A26F5E.

Country allocation

The ICAO 24-bit address A26F5E 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
N256SF - 223 2026-07-13

Recent flights last 50

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

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

Mode-S A26F5E frequently asked

What is Mode-S code A26F5E?
A26F5E is an ICAO 24-bit transponder address. Allocated to United States. Assigned to N256SF.
Where is Mode-S A26F5E registered?
Mode-S code A26F5E 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 A26F5E 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 A26F5E, octal 50467536, decimal 10,645,342.
What flights does A26F5E operate?
Mode-S A26F5E has broadcast 1 distinct callsign, including N256SF.