Apparatus

Try JFK, AAL1290, BAW, or N225AN.

sensors Mode-S transponder

AA3FB2

ICAO 24-bit transponder address · allocated to United States

Currently assigned to N76FF · operated by FF22 LLC

Hex
AA3FB2
Octal
52437662
Decimal
11,157,426
Country
US
Tail
N76FF
Type
C172
No current signal · last broadcast 15h ago
Flights observed
121
Distinct callsigns
1
Country
US
Last broadcast
15h ago

Last known position

Most recent position reported by Mode-S AA3FB2.

Country allocation

The ICAO 24-bit address AA3FB2 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
N76FF - 121 2026-05-29

Recent flights last 50

DateFlightRouteTakeoffLandingDuration
2026-05-29 N76FF - May 29, 22:55 UTCMay 29, 23:10 UTC15m
2026-05-29 N76FF - May 29, 20:45 UTCMay 29, 21:25 UTC40m
2026-05-29 N76FF BJC → BJC May 29, 18:40 UTCMay 29, 19:55 UTC1h 15m
2026-05-29 N76FF BJC → BJC May 29, 13:45 UTCMay 29, 14:45 UTC1h 0m
2026-05-28 N76FF BJC → BJC May 28, 21:15 UTCMay 28, 21:55 UTC40m
2026-05-28 N76FF BJC → BJC May 28, 19:05 UTCMay 28, 19:40 UTC35m
2026-05-27 N76FF BJC → BJC May 27, 23:30 UTCMay 28, 00:30 UTC1h 0m
2026-05-27 N76FF BJC → BJC May 27, 19:25 UTCMay 27, 20:10 UTC45m
2026-05-27 N76FF BJC → BJC May 27, 15:55 UTCMay 27, 17:35 UTC1h 40m
2026-05-26 N76FF BJC → BJC May 26, 19:40 UTCMay 26, 20:45 UTC1h 5m
2026-05-26 N76FF BJC → BJC May 26, 13:19 UTCMay 26, 13:54 UTC35m
2026-05-25 N76FF BJC → BJC May 25, 20:30 UTCMay 25, 22:15 UTC1h 45m
2026-05-25 N76FF BJC → BJC May 25, 16:40 UTCMay 25, 17:30 UTC50m
2026-05-25 N76FF BJC → BJC May 25, 14:00 UTCMay 25, 15:40 UTC1h 40m
2026-05-24 N76FF BJC → BJC May 24, 17:40 UTCMay 24, 19:00 UTC1h 20m
2026-05-24 N76FF BJC → BJC May 24, 15:20 UTCMay 24, 16:25 UTC1h 5m
2026-05-23 N76FF BJC → BJC May 23, 16:05 UTCMay 23, 16:45 UTC40m
2026-05-23 N76FF BJC → BJC May 23, 13:35 UTCMay 23, 15:20 UTC1h 45m
2026-05-22 N76FF BJC → BJC May 22, 22:20 UTCMay 22, 23:05 UTC45m
2026-05-22 N76FF BJC → BJC May 22, 15:30 UTCMay 22, 16:50 UTC1h 20m
2026-05-22 N76FF BJC → BJC May 22, 12:40 UTCMay 22, 14:00 UTC1h 20m
2026-05-21 N76FF BJC → BJC May 21, 21:20 UTCMay 21, 22:15 UTC55m
2026-05-21 N76FF - May 21, 18:55 UTCMay 21, 20:00 UTC1h 5m
2026-05-21 N76FF BJC → BJC May 21, 17:20 UTCMay 21, 17:55 UTC35m
2026-05-21 N76FF BJC → BJC May 21, 14:15 UTCMay 21, 15:40 UTC1h 25m
2026-05-21 N76FF - May 21, 04:30 UTCMay 21, 05:25 UTC55m
2026-05-21 N76FF - May 21, 03:10 UTCMay 21, 04:00 UTC50m
2026-05-21 N76FF BJC → BJC May 21, 00:00 UTCMay 21, 00:55 UTC55m
2026-05-20 N76FF BJC → BJC May 20, 01:50 UTCMay 20, 02:40 UTC50m
2026-05-19 N76FF BJC → BJC May 19, 23:10 UTCMay 20, 00:40 UTC1h 30m
2026-05-17 N76FF BJC → BJC May 17, 16:01 UTCMay 17, 16:30 UTC30m
2026-05-16 N76FF BJC → BJC May 16, 15:55 UTCMay 16, 16:50 UTC55m
2026-05-15 N76FF BJC → BJC May 15, 21:10 UTCMay 15, 22:05 UTC55m
2026-05-15 N76FF BJC → BJC May 15, 18:10 UTCMay 15, 19:20 UTC1h 10m
2026-05-13 N76FF BJC → BJC May 13, 18:30 UTCMay 13, 19:45 UTC1h 15m
2026-05-13 N76FF BJC → BJC May 13, 16:15 UTCMay 13, 17:05 UTC50m
2026-05-13 N76FF BJC → BJC May 13, 02:45 UTCMay 13, 05:10 UTC2h 25m
2026-05-12 N76FF BJC → BJC May 12, 23:05 UTCMay 13, 00:05 UTC1h 0m
2026-05-12 N76FF BJC → BJC May 12, 20:15 UTCMay 12, 21:45 UTC1h 30m
2026-05-12 N76FF BJC → BJC May 12, 18:10 UTCMay 12, 19:15 UTC1h 5m
2026-05-12 N76FF BJC → BJC May 12, 16:10 UTCMay 12, 17:10 UTC1h 0m
2026-05-12 N76FF - May 12, 02:45 UTCMay 12, 04:20 UTC1h 35m
2026-05-11 N76FF - May 11, 22:10 UTCMay 11, 22:35 UTC24m
2026-05-11 N76FF BJC → BJC May 11, 15:55 UTCMay 11, 17:00 UTC1h 6m
2026-05-11 N76FF BJC → BJC May 11, 13:25 UTCMay 11, 14:35 UTC1h 10m
2026-05-10 N76FF BJC → BJC May 10, 17:25 UTCMay 10, 18:45 UTC1h 20m
2026-05-10 N76FF BJC → BJC May 10, 14:54 UTCMay 10, 16:14 UTC1h 20m
2026-05-09 N76FF BJC → BJC May 9, 15:50 UTCMay 9, 17:30 UTC1h 40m
2026-05-09 N76FF BJC → BJC May 9, 13:20 UTCMay 9, 14:00 UTC40m
2026-05-09 N76FF BJC → BJC May 9, 00:45 UTCMay 9, 02:05 UTC1h 20m

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

Mode-S AA3FB2 frequently asked

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