Apparatus

Try JFK, AAL1290, BAW, or N225AN.

sensors Mode-S transponder

A267F0

ICAO 24-bit transponder address · allocated to United States

Currently assigned to N254SF · operated by TEXTRON AVIATION INC

Hex
A267F0
Octal
50463760
Decimal
10,643,440
Country
US
Tail
N254SF
Type
C172
No current signal · last broadcast 1d ago
Flights observed
250
Distinct callsigns
1
Country
US
Last broadcast
1d ago

Last known position

Most recent position reported by Mode-S A267F0.

Country allocation

The ICAO 24-bit address A267F0 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
N254SF - 250 2026-07-12

Recent flights last 50

DateFlightRouteTakeoffLandingDuration
2026-07-12 N254SF BJC → BJC Jul 12, 20:15 UTCJul 12, 20:50 UTC35m
2026-07-12 N254SF BJC → BJC Jul 12, 18:01 UTCJul 12, 18:55 UTC55m
2026-07-12 N254SF BJC → BJC Jul 12, 15:40 UTCJul 12, 16:50 UTC1h 10m
2026-07-12 N254SF BJC → BJC Jul 12, 12:35 UTCJul 12, 14:45 UTC2h 10m
2026-07-11 N254SF BJC → BJC Jul 11, 20:55 UTCJul 11, 22:35 UTC1h 40m
2026-07-11 N254SF - Jul 11, 18:00 UTCJul 11, 19:25 UTC1h 25m
2026-07-11 N254SF BJC → BJC Jul 11, 15:30 UTCJul 11, 17:10 UTC1h 40m
2026-07-11 N254SF BJC → BJC Jul 11, 12:45 UTCJul 11, 14:05 UTC1h 20m
2026-07-11 N254SF BJC → BJC Jul 11, 00:30 UTCJul 11, 02:00 UTC1h 30m
2026-07-10 N254SF BJC → BJC Jul 10, 20:10 UTCJul 10, 21:15 UTC1h 5m
2026-07-10 N254SF BJC → BJC Jul 10, 16:50 UTCJul 10, 18:10 UTC1h 20m
2026-07-10 N254SF BJC → BJC Jul 10, 12:45 UTCJul 10, 14:40 UTC1h 55m
2026-07-09 N254SF - Jul 9, 20:05 UTCJul 9, 20:15 UTC10m
2026-07-09 N254SF BJC → BJC Jul 9, 19:50 UTCJul 9, 19:55 UTC5m
2026-07-09 N254SF BJC → BJC Jul 9, 19:40 UTCJul 9, 19:45 UTC5m
2026-07-09 N254SF BJC → BJC Jul 9, 16:20 UTCJul 9, 18:05 UTC1h 45m
2026-07-09 N254SF BJC → BJC Jul 9, 13:55 UTCJul 9, 15:15 UTC1h 20m
2026-07-08 N254SF BJC → BJC Jul 8, 23:55 UTCJul 9, 01:05 UTC1h 10m
2026-07-08 N254SF BJC → BJC Jul 8, 17:50 UTCJul 8, 19:00 UTC1h 10m
2026-07-08 N254SF BJC → BJC Jul 8, 15:25 UTCJul 8, 16:30 UTC1h 5m
2026-07-08 N254SF BJC → BJC Jul 8, 13:05 UTCJul 8, 14:10 UTC1h 5m
2026-07-08 N254SF - Jul 8, 04:00 UTCJul 8, 04:50 UTC50m
2026-07-08 N254SF - Jul 8, 02:25 UTCJul 8, 03:20 UTC55m
2026-07-07 N254SF BJC → BJC Jul 7, 19:50 UTCJul 7, 20:25 UTC35m
2026-07-07 N254SF BJC → BJC Jul 7, 17:30 UTCJul 7, 18:15 UTC45m
2026-07-07 N254SF BJC → BJC Jul 7, 15:00 UTCJul 7, 16:05 UTC1h 5m
2026-07-07 N254SF BJC → BJC Jul 7, 13:05 UTCJul 7, 14:00 UTC55m
2026-07-07 N254SF BJC → BJC Jul 7, 01:00 UTCJul 7, 02:30 UTC1h 30m
2026-07-06 N254SF - Jul 6, 20:15 UTCJul 6, 21:15 UTC1h 0m
2026-07-06 N254SF BJC → BJC Jul 6, 17:50 UTCJul 6, 19:25 UTC1h 35m
2026-07-06 N254SF BJC → BJC Jul 6, 15:25 UTCJul 6, 16:30 UTC1h 5m
2026-07-05 N254SF BJC → BJC Jul 5, 02:35 UTCJul 5, 04:55 UTC2h 20m
2026-07-04 N254SF BJC → BJC Jul 4, 17:40 UTCJul 4, 18:15 UTC35m
2026-07-04 N254SF BJC → BJC Jul 4, 12:45 UTCJul 4, 14:15 UTC1h 30m
2026-07-03 N254SF BJC → BJC Jul 3, 21:45 UTCJul 3, 22:40 UTC55m
2026-07-03 N254SF BJC → BJC Jul 3, 19:10 UTCJul 3, 20:40 UTC1h 30m
2026-07-03 N254SF BJC → BJC Jul 3, 16:20 UTCJul 3, 18:05 UTC1h 45m
2026-07-03 N254SF BJC → BJC Jul 3, 14:40 UTCJul 3, 15:15 UTC35m
2026-07-02 N254SF BJC → BJC Jul 2, 21:15 UTCJul 2, 22:20 UTC1h 5m
2026-07-02 N254SF BJC → BJC Jul 2, 19:40 UTCJul 2, 20:15 UTC35m
2026-07-02 N254SF BJC → BJC Jul 2, 16:55 UTCJul 2, 18:00 UTC1h 5m
2026-07-02 N254SF BJC → BJC Jul 2, 16:40 UTCJul 2, 16:45 UTC5m
2026-07-02 N254SF BJC → BJC Jul 2, 13:15 UTCJul 2, 15:25 UTC2h 10m
2026-07-01 N254SF BJC → BJC Jul 1, 23:05 UTCJul 2, 00:35 UTC1h 30m
2026-07-01 N254SF BJC → BJC Jul 1, 18:40 UTCJul 1, 18:55 UTC15m
2026-07-01 N254SF BJC → BJC Jul 1, 18:25 UTCJul 1, 18:35 UTC10m
2026-07-01 N254SF BJC → BJC Jul 1, 16:20 UTCJul 1, 17:05 UTC45m
2026-07-01 N254SF BJC → BJC Jul 1, 13:45 UTCJul 1, 14:55 UTC1h 10m
2026-06-30 N254SF BJC → BJC Jun 30, 20:50 UTCJun 30, 21:00 UTC10m
2026-06-26 N254SF BJC → BJC Jun 26, 20:50 UTCJun 26, 21:45 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 N254SF page for operator, model, and routing details .

Mode-S A267F0 frequently asked

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