Apparatus

Try JFK, AAL1290, BAW, or N225AN.

sensors Mode-S transponder

A1FB0F

ICAO 24-bit transponder address · allocated to United States

Currently assigned to N227AN · CESSNA 172 Skyhawk · operated by CALIFORNIA IN NICE INC

Hex
A1FB0F
Octal
50375417
Decimal
10,615,567
Country
US
Tail
N227AN
Type
C172
Broadcasting now · callsign N227AN · 1,600 ft
Flights observed
147
Distinct callsigns
1
Country
US
Last broadcast
3h ago

Current position

A1FB0F is currently broadcasting. Map zoomed to live position.

Country allocation

The ICAO 24-bit address A1FB0F 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
N227AN - 147 2026-06-15

Recent flights last 50

DateFlightRouteTakeoffLandingDuration
2026-06-15 N227AN RHV → RHV Jun 15, 22:10 UTCJun 15, 22:35 UTC25m
2026-06-15 N227AN - Jun 15, 17:50 UTCJun 15, 18:35 UTC45m
2026-06-15 N227AN - Jun 15, 02:30 UTCJun 15, 03:15 UTC45m
2026-06-15 N227AN MHR → RHV Jun 15, 00:05 UTCJun 15, 00:55 UTC50m
2026-06-14 N227AN RHV → MHR Jun 14, 20:40 UTCJun 14, 21:30 UTC50m
2026-06-14 N227AN RHV → RHV Jun 14, 17:35 UTCJun 14, 19:20 UTC1h 45m
2026-06-13 N227AN RHV → RHV Jun 13, 20:20 UTCJun 13, 21:35 UTC1h 15m
2026-06-13 N227AN RHV → RHV Jun 13, 00:45 UTCJun 13, 01:05 UTC20m
2026-06-12 N227AN - Jun 12, 16:50 UTCJun 12, 17:10 UTC20m
2026-06-12 N227AN - Jun 12, 02:05 UTCJun 12, 02:50 UTC45m
2026-06-12 N227AN - Jun 12, 00:05 UTCJun 12, 00:45 UTC41m
2026-06-11 N227AN - Jun 11, 22:30 UTCJun 11, 23:10 UTC40m
2026-06-11 N227AN - Jun 11, 19:50 UTCJun 11, 20:45 UTC55m
2026-06-11 N227AN RHV → RHV Jun 11, 18:10 UTCJun 11, 18:15 UTC5m
2026-06-11 N227AN RHV → RHV Jun 11, 16:25 UTCJun 11, 16:35 UTC10m
2026-06-10 N227AN RHV → RHV Jun 10, 23:20 UTCJun 11, 01:25 UTC2h 5m
2026-06-10 N227AN RHV → RHV Jun 10, 20:40 UTCJun 10, 22:15 UTC1h 35m
2026-06-10 N227AN RHV → RHV Jun 10, 18:15 UTCJun 10, 19:15 UTC1h 0m
2026-06-09 N227AN RHV → RHV Jun 9, 19:35 UTCJun 9, 20:00 UTC25m
2026-06-09 N227AN RHV → RHV Jun 9, 17:45 UTCJun 9, 18:30 UTC45m
2026-06-08 N227AN RHV → RHV Jun 8, 20:20 UTCJun 8, 21:45 UTC1h 25m
2026-06-08 N227AN RHV → RHV Jun 8, 18:10 UTCJun 8, 19:30 UTC1h 20m
2026-06-07 N227AN - Jun 7, 22:45 UTCJun 8, 00:15 UTC1h 30m
2026-06-07 N227AN - Jun 7, 17:05 UTCJun 7, 17:45 UTC40m
2026-06-07 N227AN - Jun 7, 03:50 UTCJun 7, 04:15 UTC25m
2026-06-07 N227AN - Jun 7, 00:10 UTCJun 7, 00:49 UTC40m
2026-06-06 N227AN RHV → RHV Jun 6, 19:19 UTCJun 6, 20:49 UTC1h 30m
2026-06-06 N227AN RHV → RHV Jun 6, 15:44 UTCJun 6, 17:00 UTC1h 15m
2026-06-05 N227AN RHV → RHV Jun 5, 18:15 UTCJun 5, 19:50 UTC1h 35m
2026-06-05 N227AN RHV → RHV Jun 5, 15:45 UTCJun 5, 17:00 UTC1h 15m
2026-06-05 N227AN RHV → RHV Jun 5, 02:20 UTCJun 5, 02:40 UTC20m
2026-06-05 N227AN RHV → RHV Jun 5, 01:45 UTCJun 5, 02:15 UTC30m
2026-06-04 N227AN RHV → RHV Jun 4, 23:40 UTCJun 5, 00:45 UTC1h 5m
2026-06-04 N227AN - Jun 4, 19:45 UTCJun 4, 21:35 UTC1h 50m
2026-06-03 N227AN RHV → RHV Jun 3, 19:15 UTCJun 3, 20:25 UTC1h 10m
2026-06-03 N227AN RHV → RHV Jun 3, 16:45 UTCJun 3, 18:20 UTC1h 35m
2026-05-18 N227AN RHV → RHV May 18, 16:00 UTCMay 18, 16:10 UTC10m
2026-05-18 N227AN RHV → RHV May 18, 15:40 UTCMay 18, 15:55 UTC15m
2026-05-18 N227AN RHV → RHV May 18, 15:05 UTCMay 18, 15:35 UTC30m
2026-05-17 N227AN - May 17, 21:40 UTCMay 17, 22:05 UTC25m
2026-05-17 N227AN - May 17, 19:35 UTCMay 17, 20:30 UTC55m
2026-05-17 N227AN RHV → RHV May 17, 16:45 UTCMay 17, 17:01 UTC15m
2026-05-17 N227AN - May 17, 16:30 UTCMay 17, 16:40 UTC10m
2026-05-16 N227AN - May 16, 23:40 UTCMay 17, 01:05 UTC1h 25m
2026-05-16 N227AN - May 16, 21:30 UTCMay 16, 21:45 UTC15m
2026-05-16 N227AN - May 16, 19:20 UTCMay 16, 20:15 UTC55m
2026-05-16 N227AN RHV → RHV May 16, 16:40 UTCMay 16, 18:00 UTC1h 20m
2026-05-16 N227AN RHV → RHV May 16, 00:30 UTCMay 16, 01:35 UTC1h 5m
2026-05-15 N227AN RHV → RHV May 15, 22:20 UTCMay 15, 23:20 UTC1h 0m
2026-05-15 N227AN - May 15, 18:05 UTCMay 15, 18:20 UTC15m

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

Mode-S A1FB0F frequently asked

What is Mode-S code A1FB0F?
A1FB0F is an ICAO 24-bit transponder address. Allocated to United States. Assigned to N227AN.
Where is Mode-S A1FB0F registered?
Mode-S code A1FB0F 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 A1FB0F broadcasting right now?
Yes. Mode-S A1FB0F is currently airborne.
Hex, octal, and decimal Mode-S codes: what's the difference?
The same 24-bit identifier expressed in different bases: hex A1FB0F, octal 50375417, decimal 10,615,567.
What flights does A1FB0F operate?
Mode-S A1FB0F has broadcast 1 distinct callsign, including N227AN.