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 4d ago
Flights observed
108
Distinct callsigns
1
Country
US
Last broadcast
4d 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 - 108 2026-05-25

Recent flights last 50

DateFlightRouteTakeoffLandingDuration
2026-05-25 N256SF BJC → BJC May 25, 15:55 UTCMay 25, 17:30 UTC1h 35m
2026-05-23 N256SF BJC → BJC May 23, 21:50 UTCMay 23, 23:30 UTC1h 40m
2026-05-23 N256SF BJC → BJC May 23, 18:20 UTCMay 23, 19:25 UTC1h 5m
2026-05-23 N256SF - May 23, 13:55 UTCMay 23, 14:15 UTC20m
2026-05-23 N256SF - May 23, 13:15 UTCMay 23, 13:50 UTC35m
2026-05-22 N256SF BJC → BJC May 22, 21:05 UTCMay 22, 22:15 UTC1h 10m
2026-05-22 N256SF BJC → BJC May 22, 19:05 UTCMay 22, 20:05 UTC1h 0m
2026-05-22 N256SF BJC → BJC May 22, 16:35 UTCMay 22, 17:40 UTC1h 5m
2026-05-22 N256SF BJC → BJC May 22, 13:40 UTCMay 22, 15:10 UTC1h 30m
2026-05-21 N256SF BJC → BJC May 21, 22:15 UTCMay 21, 23:20 UTC1h 5m
2026-05-21 N256SF - May 21, 20:40 UTCMay 21, 21:25 UTC45m
2026-05-21 N256SF - May 21, 20:20 UTCMay 21, 20:35 UTC15m
2026-05-21 N256SF BJC → BJC May 21, 16:30 UTCMay 21, 17:45 UTC1h 15m
2026-05-20 N256SF BJC → BJC May 20, 23:50 UTCMay 21, 01:35 UTC1h 45m
2026-05-20 N256SF BJC → BJC May 20, 22:10 UTCMay 20, 22:40 UTC30m
2026-05-20 N256SF BJC → BJC May 20, 19:25 UTCMay 20, 21:00 UTC1h 35m
2026-05-16 N256SF BJC → BJC May 16, 22:00 UTCMay 17, 00:20 UTC2h 20m
2026-05-16 N256SF BJC → BJC May 16, 16:25 UTCMay 16, 17:01 UTC35m
2026-05-16 N256SF BJC → BJC May 16, 16:10 UTCMay 16, 16:20 UTC10m
2026-05-16 N256SF BJC → BJC May 16, 15:50 UTCMay 16, 16:05 UTC15m
2026-05-15 N256SF BJC → BJC May 15, 23:50 UTCMay 16, 00:10 UTC20m
2026-05-15 N256SF BJC → BJC May 15, 21:10 UTCMay 15, 21:45 UTC35m
2026-05-15 N256SF - May 15, 19:15 UTCMay 15, 19:25 UTC10m
2026-05-15 N256SF - May 15, 17:30 UTCMay 15, 19:10 UTC1h 40m
2026-05-14 N256SF BJC → BJC May 14, 23:05 UTCMay 14, 23:50 UTC45m
2026-05-14 N256SF - May 14, 18:25 UTCMay 14, 19:20 UTC55m
2026-05-14 N256SF BJC → BJC May 14, 16:10 UTCMay 14, 17:25 UTC1h 15m
2026-05-13 N256SF BJC → BJC May 13, 22:45 UTCMay 14, 00:00 UTC1h 15m
2026-05-13 N256SF BJC → BJC May 13, 20:30 UTCMay 13, 21:30 UTC1h 0m
2026-05-13 N256SF BJC → BJC May 13, 15:50 UTCMay 13, 17:30 UTC1h 40m
2026-05-13 N256SF BJC → BJC May 13, 13:00 UTCMay 13, 14:15 UTC1h 15m
2026-05-13 N256SF BJC → BJC May 13, 01:05 UTCMay 13, 02:00 UTC55m
2026-05-12 N256SF BJC → BJC May 12, 23:10 UTCMay 13, 00:00 UTC50m
2026-05-12 N256SF BJC → BJC May 12, 19:40 UTCMay 12, 21:05 UTC1h 25m
2026-05-12 N256SF FNL → BJC May 12, 16:35 UTCMay 12, 17:00 UTC25m
2026-05-12 N256SF BJC → FNL May 12, 12:55 UTCMay 12, 13:20 UTC25m
2026-05-11 N256SF - May 11, 21:00 UTCMay 11, 21:45 UTC45m
2026-05-11 N256SF - May 11, 20:30 UTCMay 11, 20:55 UTC25m
2026-05-11 N256SF BJC → BJC May 11, 18:35 UTCMay 11, 19:45 UTC1h 10m
2026-05-10 N256SF - May 10, 21:25 UTCMay 10, 21:49 UTC25m
2026-05-10 N256SF - May 10, 20:25 UTCMay 10, 21:19 UTC55m
2026-05-10 N256SF - May 10, 18:35 UTCMay 10, 19:15 UTC40m
2026-05-10 N256SF - May 10, 17:05 UTCMay 10, 17:55 UTC50m
2026-05-09 N256SF BJC → BJC May 9, 20:20 UTCMay 9, 23:05 UTC2h 45m
2026-05-09 N256SF BJC → BJC May 9, 18:00 UTCMay 9, 18:30 UTC30m
2026-05-08 N256SF BJC → BJC May 8, 23:25 UTCMay 9, 01:00 UTC1h 35m
2026-05-08 N256SF BJC → BJC May 8, 21:20 UTCMay 8, 22:15 UTC55m
2026-05-08 N256SF BJC → BJC May 8, 19:15 UTCMay 8, 20:25 UTC1h 10m
2026-05-08 N256SF BJC → BJC May 8, 16:30 UTCMay 8, 17:05 UTC35m
2026-05-08 N256SF - May 8, 03:09 UTCMay 8, 04:14 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 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 4d 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.