Apparatus

Try JFK, AAL1290, BAW, or N225AN.

sensors Mode-S transponder

A3B04F

ICAO 24-bit transponder address · allocated to United States

Currently assigned to N337FB · PIPER PA-28-140/150/160/180 · operated by FLY KILO CHARLIE LLC

Hex
A3B04F
Octal
50730117
Decimal
10,727,503
Country
US
Tail
N337FB
Type
P28A
No current signal · last broadcast 9h ago
Flights observed
163
Distinct callsigns
1
Country
US
Last broadcast
9h ago

Last known position

Most recent position reported by Mode-S A3B04F.

Country allocation

The ICAO 24-bit address A3B04F 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
N337FB - 163 2026-06-11

Recent flights last 50

DateFlightRouteTakeoffLandingDuration
2026-06-11 N337FB - Jun 11, 15:55 UTCJun 11, 16:50 UTC55m
2026-06-11 N337FB FRG → FRG Jun 11, 13:35 UTCJun 11, 14:55 UTC1h 20m
2026-06-10 N337FB FRG → FRG Jun 10, 19:45 UTCJun 10, 20:30 UTC45m
2026-06-10 N337FB - Jun 10, 17:30 UTCJun 10, 18:40 UTC1h 10m
2026-06-10 N337FB FRG → FRG Jun 10, 16:05 UTCJun 10, 16:40 UTC35m
2026-06-10 N337FB - Jun 10, 11:30 UTCJun 10, 12:50 UTC1h 20m
2026-06-09 N337FB - Jun 9, 23:35 UTCJun 10, 01:00 UTC1h 25m
2026-06-09 N337FB - Jun 9, 21:50 UTCJun 9, 22:55 UTC1h 5m
2026-06-09 N337FB - Jun 9, 20:25 UTCJun 9, 21:10 UTC45m
2026-06-09 N337FB - Jun 9, 17:45 UTCJun 9, 18:35 UTC50m
2026-06-09 N337FB FRG → FRG Jun 9, 13:35 UTCJun 9, 14:25 UTC50m
2026-06-09 N337FB FRG → FRG Jun 9, 11:30 UTCJun 9, 12:45 UTC1h 15m
2026-06-09 N337FB - Jun 9, 02:00 UTCJun 9, 04:40 UTC2h 40m
2026-06-08 N337FB FRG → FRG Jun 8, 21:25 UTCJun 8, 22:00 UTC35m
2026-06-08 N337FB - Jun 8, 19:40 UTCJun 8, 20:50 UTC1h 10m
2026-06-08 N337FB FRG → FRG Jun 8, 17:55 UTCJun 8, 18:55 UTC1h 0m
2026-06-08 N337FB - Jun 8, 13:50 UTCJun 8, 14:45 UTC55m
2026-06-08 N337FB FRG → FRG Jun 8, 11:25 UTCJun 8, 12:35 UTC1h 10m
2026-06-07 N337FB FRG → FRG Jun 7, 17:45 UTCJun 7, 18:50 UTC1h 5m
2026-06-07 N337FB - Jun 7, 15:50 UTCJun 7, 17:05 UTC1h 15m
2026-06-07 N337FB FRG → FRG Jun 7, 13:45 UTCJun 7, 15:00 UTC1h 15m
2026-06-07 N337FB - Jun 7, 11:50 UTCJun 7, 12:35 UTC45m
2026-06-06 N337FB FRG → FRG Jun 6, 14:25 UTCJun 6, 14:40 UTC15m
2026-06-06 N337FB FRG → FRG Jun 6, 11:39 UTCJun 6, 13:00 UTC1h 20m
2026-06-05 N337FB FRG → FRG Jun 5, 19:30 UTCJun 5, 21:55 UTC2h 25m
2026-06-05 N337FB FRG → FRG Jun 5, 17:50 UTCJun 5, 18:35 UTC45m
2026-06-05 N337FB - Jun 5, 16:00 UTCJun 5, 16:35 UTC35m
2026-06-05 N337FB - Jun 5, 13:45 UTCJun 5, 14:30 UTC45m
2026-06-05 N337FB - Jun 5, 11:25 UTCJun 5, 12:50 UTC1h 25m
2026-06-04 N337FB - Jun 4, 23:55 UTCJun 5, 01:40 UTC1h 45m
2026-06-04 N337FB - Jun 4, 22:00 UTCJun 4, 22:55 UTC55m
2026-06-04 N337FB FRG → FRG Jun 4, 19:35 UTCJun 4, 20:40 UTC1h 5m
2026-06-04 N337FB - Jun 4, 18:00 UTCJun 4, 18:45 UTC45m
2026-06-04 N337FB - Jun 4, 15:55 UTCJun 4, 17:00 UTC1h 5m
2026-06-04 N337FB FRG → FRG Jun 4, 13:55 UTCJun 4, 14:10 UTC15m
2026-06-04 N337FB FRG → FRG Jun 4, 11:20 UTCJun 4, 12:50 UTC1h 30m
2026-06-03 N337FB FRG → FRG Jun 3, 22:45 UTCJun 4, 00:20 UTC1h 35m
2026-06-03 N337FB FRG → FRG Jun 3, 19:50 UTCJun 3, 21:20 UTC1h 30m
2026-06-03 N337FB - Jun 3, 14:25 UTCJun 3, 16:35 UTC2h 10m
2026-06-03 N337FB FRG → FRG Jun 3, 11:25 UTCJun 3, 13:05 UTC1h 40m
2026-06-02 N337FB - Jun 2, 18:20 UTCJun 2, 21:40 UTC3h 20m
2026-06-02 N337FB FRG → FRG Jun 2, 15:30 UTCJun 2, 16:45 UTC1h 15m
2026-06-02 N337FB - Jun 2, 14:05 UTCJun 2, 14:50 UTC45m
2026-06-02 N337FB FRG → FRG Jun 2, 11:35 UTCJun 2, 12:50 UTC1h 15m
2026-06-01 N337FB - Jun 1, 18:05 UTCJun 1, 20:20 UTC2h 15m
2026-06-01 N337FB - Jun 1, 15:30 UTCJun 1, 16:25 UTC55m
2026-06-01 N337FB - Jun 1, 11:15 UTCJun 1, 13:10 UTC1h 55m
2026-05-31 N337FB FRG → FRG May 31, 17:45 UTCMay 31, 18:55 UTC1h 10m
2026-05-31 N337FB - May 31, 15:55 UTCMay 31, 16:50 UTC55m
2026-05-29 N337FB FRG → FRG May 29, 21:55 UTCMay 29, 22:30 UTC35m

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

Mode-S A3B04F frequently asked

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