Apparatus

Try JFK, AAL1290, BAW, or N225AN.

sensors Mode-S transponder

AAB62F

ICAO 24-bit transponder address · allocated to United States

Currently assigned to N79FF · operated by FF22 LLC

Hex
AAB62F
Octal
52533057
Decimal
11,187,759
Country
US
Tail
N79FF
Type
C172
No current signal · last broadcast 1d ago
Flights observed
237
Distinct callsigns
1
Country
US
Last broadcast
1d ago

Last known position

Most recent position reported by Mode-S AAB62F.

Country allocation

The ICAO 24-bit address AAB62F 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
N79FF - 237 2026-07-12

Recent flights last 50

DateFlightRouteTakeoffLandingDuration
2026-07-12 N79FF BJC → BJC Jul 12, 16:10 UTCJul 12, 17:20 UTC1h 10m
2026-07-12 N79FF BJC → BJC Jul 12, 12:50 UTCJul 12, 13:35 UTC45m
2026-07-12 N79FF BJC → BJC Jul 12, 03:40 UTCJul 12, 05:10 UTC1h 30m
2026-07-11 N79FF BJC → BJC Jul 11, 18:35 UTCJul 11, 19:15 UTC40m
2026-07-11 N79FF BJC → BJC Jul 11, 14:55 UTCJul 11, 16:05 UTC1h 10m
2026-07-10 N79FF BJC → BJC Jul 10, 20:30 UTCJul 10, 21:40 UTC1h 10m
2026-07-10 N79FF BJC → BJC Jul 10, 18:20 UTCJul 10, 19:20 UTC1h 0m
2026-07-10 N79FF BJC → BJC Jul 10, 16:10 UTCJul 10, 17:10 UTC1h 0m
2026-07-10 N79FF BJC → BJC Jul 10, 13:10 UTCJul 10, 14:25 UTC1h 15m
2026-07-09 N79FF BJC → BJC Jul 9, 16:55 UTCJul 9, 18:30 UTC1h 35m
2026-07-09 N79FF BJC → BJC Jul 9, 12:35 UTCJul 9, 14:30 UTC1h 55m
2026-07-08 N79FF BJC → BJC Jul 8, 17:10 UTCJul 8, 18:25 UTC1h 15m
2026-07-08 N79FF BJC → BJC Jul 8, 14:25 UTCJul 8, 15:10 UTC45m
2026-07-08 N79FF BJC → BJC Jul 8, 11:50 UTCJul 8, 13:25 UTC1h 35m
2026-07-08 N79FF BJC → BJC Jul 8, 00:00 UTCJul 8, 01:45 UTC1h 45m
2026-07-07 N79FF BJC → BJC Jul 7, 18:25 UTCJul 7, 19:50 UTC1h 25m
2026-07-07 N79FF BJC → BJC Jul 7, 14:05 UTCJul 7, 15:15 UTC1h 10m
2026-07-06 N79FF BJC → BJC Jul 6, 22:05 UTCJul 6, 23:50 UTC1h 45m
2026-07-06 N79FF BJC → BJC Jul 6, 18:45 UTCJul 6, 20:10 UTC1h 25m
2026-07-06 N79FF BJC → BJC Jul 6, 16:10 UTCJul 6, 17:30 UTC1h 20m
2026-07-06 N79FF BJC → BJC Jul 6, 13:30 UTCJul 6, 14:55 UTC1h 25m
2026-07-06 N79FF BJC → BJC Jul 6, 00:30 UTCJul 6, 01:45 UTC1h 15m
2026-07-05 N79FF BJC → BJC Jul 5, 17:55 UTCJul 5, 18:40 UTC45m
2026-07-05 N79FF BJC → BJC Jul 5, 17:30 UTCJul 5, 17:45 UTC15m
2026-07-04 N79FF BJC → BJC Jul 4, 15:30 UTCJul 4, 16:20 UTC50m
2026-07-04 N79FF BJC → BJC Jul 4, 13:05 UTCJul 4, 13:15 UTC10m
2026-07-04 N79FF - Jul 4, 12:30 UTCJul 4, 12:35 UTC5m
2026-07-04 N79FF BJC → BJC Jul 4, 12:05 UTCJul 4, 12:25 UTC20m
2026-07-04 N79FF BJC → BJC Jul 4, 03:30 UTCJul 4, 06:00 UTC2h 30m
2026-07-03 N79FF BJC → BJC Jul 3, 15:30 UTCJul 3, 16:20 UTC50m
2026-07-03 N79FF BJC → BJC Jul 3, 12:40 UTCJul 3, 14:10 UTC1h 30m
2026-07-03 N79FF BJC → BJC Jul 3, 00:15 UTCJul 3, 01:40 UTC1h 25m
2026-07-02 N79FF BJC → BJC Jul 2, 21:00 UTCJul 2, 22:05 UTC1h 5m
2026-07-02 N79FF BJC → BJC Jul 2, 18:10 UTCJul 2, 18:50 UTC40m
2026-07-02 N79FF BJC → BJC Jul 2, 14:55 UTCJul 2, 16:00 UTC1h 5m
2026-07-02 N79FF BJC → BJC Jul 2, 12:10 UTCJul 2, 13:30 UTC1h 20m
2026-07-02 N79FF BJC → BJC Jul 2, 01:25 UTCJul 2, 02:20 UTC55m
2026-07-01 N79FF BJC → BJC Jul 1, 22:50 UTCJul 1, 23:35 UTC45m
2026-07-01 N79FF BJC → BJC Jul 1, 19:45 UTCJul 1, 21:05 UTC1h 20m
2026-07-01 N79FF - Jul 1, 17:00 UTCJul 1, 18:15 UTC1h 15m
2026-07-01 N79FF - Jul 1, 16:35 UTCJul 1, 16:55 UTC20m
2026-07-01 N79FF BJC → BJC Jul 1, 14:05 UTCJul 1, 15:40 UTC1h 35m
2026-07-01 N79FF BJC → BJC Jul 1, 11:45 UTCJul 1, 12:55 UTC1h 10m
2026-06-30 N79FF BJC → BJC Jun 30, 18:35 UTCJun 30, 20:05 UTC1h 30m
2026-06-30 N79FF BJC → BJC Jun 30, 16:15 UTCJun 30, 17:25 UTC1h 10m
2026-06-30 N79FF BJC → BJC Jun 30, 13:30 UTCJun 30, 15:10 UTC1h 40m
2026-06-30 N79FF BJC → BJC Jun 30, 00:00 UTCJun 30, 01:55 UTC1h 56m
2026-06-29 N79FF BJC → BJC Jun 29, 20:35 UTCJun 29, 21:50 UTC1h 15m
2026-06-29 N79FF BJC → BJC Jun 29, 03:44 UTCJun 29, 04:09 UTC25m
2026-06-28 N79FF BJC → BJC Jun 28, 22:10 UTCJun 28, 23:44 UTC1h 35m

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

Mode-S AAB62F frequently asked

What is Mode-S code AAB62F?
AAB62F is an ICAO 24-bit transponder address. Allocated to United States. Assigned to N79FF.
Where is Mode-S AAB62F registered?
Mode-S code AAB62F 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 AAB62F 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 AAB62F, octal 52533057, decimal 11,187,759.
What flights does AAB62F operate?
Mode-S AAB62F has broadcast 1 distinct callsign, including N79FF.