Apparatus

Try JFK, AAL1290, BAW, or N225AN.

sensors Mode-S transponder

A5AC7F

ICAO 24-bit transponder address · allocated to United States

Currently assigned to N465DF · operated by CALIFORNIA DEPT OF FORESTRY AND FIRE PROTECTION

Hex
A5AC7F
Octal
51326177
Decimal
10,857,599
Country
US
Tail
N465DF
Type
C130
No current signal · last broadcast Jul 25, 01:50 UTC
Flights observed
101
Distinct callsigns
1
Country
US
Last broadcast
Jul 25, 01:50 UTC

Last known position

Most recent position reported by Mode-S A5AC7F.

Country allocation

The ICAO 24-bit address A5AC7F 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
N465DF - 101 2026-07-25

Recent flights last 50

DateFlightRouteTakeoffLandingDuration
2026-07-25 N465DF - Jul 25, 00:40 UTCJul 25, 01:50 UTC1h 10m
2026-07-24 N465DF - Jul 24, 19:00 UTCJul 24, 19:45 UTC45m
2026-07-23 N465DF - Jul 23, 17:50 UTCJul 23, 19:10 UTC1h 20m
2026-07-22 N465DF - Jul 22, 22:10 UTCJul 23, 01:45 UTC3h 35m
2026-07-22 N465DF - Jul 22, 17:45 UTCJul 22, 18:45 UTC1h 0m
2026-07-21 N465DF - Jul 21, 23:10 UTCJul 22, 00:00 UTC50m
2026-07-21 N465DF - Jul 21, 20:20 UTCJul 21, 20:30 UTC10m
2026-07-21 N465DF - Jul 21, 18:40 UTCJul 21, 19:35 UTC55m
2026-07-21 N465DF - Jul 21, 16:25 UTCJul 21, 17:10 UTC45m
2026-07-21 N465DF - Jul 21, 01:20 UTCJul 21, 02:25 UTC1h 5m
2026-07-20 N465DF - Jul 20, 21:25 UTCJul 20, 21:45 UTC20m
2026-07-16 N465DF - Jul 16, 01:25 UTCJul 16, 02:45 UTC1h 20m
2026-07-15 N465DF - Jul 15, 22:55 UTCJul 16, 00:50 UTC1h 55m
2026-07-14 N465DF - Jul 14, 01:10 UTCJul 14, 01:35 UTC25m
2026-07-12 N465DF - Jul 12, 23:50 UTCJul 13, 00:30 UTC40m
2026-07-12 N465DF - Jul 12, 00:30 UTCJul 12, 01:30 UTC1h 0m
2026-07-10 N465DF - Jul 10, 23:05 UTCJul 11, 03:25 UTC4h 20m
2026-07-10 N465DF - Jul 10, 20:45 UTCJul 10, 21:20 UTC35m
2026-07-10 N465DF - Jul 10, 19:15 UTCJul 10, 20:05 UTC50m
2026-07-09 N465DF MCC → MCC Jul 9, 18:15 UTCJul 9, 19:10 UTC55m
2026-07-08 N465DF - Jul 8, 22:50 UTCJul 8, 23:45 UTC55m
2026-07-08 N465DF - Jul 8, 21:30 UTCJul 8, 22:05 UTC35m
2026-07-07 N465DF MCC → MCC Jul 7, 21:30 UTCJul 8, 03:40 UTC6h 10m
2026-07-07 N465DF MCC → MCC Jul 7, 17:30 UTCJul 7, 18:35 UTC1h 5m
2026-07-07 N465DF MCC → MCC Jul 7, 00:05 UTCJul 7, 00:15 UTC10m
2026-07-06 N465DF - Jul 6, 21:55 UTCJul 6, 23:05 UTC1h 10m
2026-07-05 N465DF MCC → MCC Jul 5, 00:55 UTCJul 5, 01:05 UTC10m
2026-07-04 N465DF MCC → MCC Jul 4, 23:20 UTCJul 5, 00:05 UTC45m
2026-07-04 N465DF MCC → MCC Jul 4, 17:35 UTCJul 4, 18:45 UTC1h 10m
2026-07-02 N465DF MCC → MCC Jul 2, 00:45 UTCJul 2, 01:25 UTC40m
2026-07-01 N465DF MCC → MCC Jul 1, 22:10 UTCJul 1, 22:35 UTC25m
2026-06-30 N465DF MCC → MCC Jun 30, 21:00 UTCJun 30, 22:55 UTC1h 55m
2026-06-30 N465DF MCC → MCC Jun 30, 17:35 UTCJun 30, 18:25 UTC50m
2026-06-29 N465DF MCC → MCC Jun 29, 21:39 UTCJun 29, 21:50 UTC10m
2026-06-29 N465DF MCC → MCC Jun 29, 13:24 UTCJun 29, 13:34 UTC10m
2026-06-28 N465DF MCC → MCC Jun 28, 23:54 UTCJun 29, 00:29 UTC35m
2026-06-28 N465DF MCC → MCC Jun 28, 21:34 UTCJun 28, 21:55 UTC20m
2026-06-27 N465DF MCC → MCC Jun 27, 21:55 UTCJun 27, 23:29 UTC1h 35m
2026-06-27 N465DF MCC → MCC Jun 27, 20:19 UTCJun 27, 20:34 UTC15m
2026-06-25 N465DF MCC → MCC Jun 25, 00:59 UTCJun 25, 01:35 UTC35m
2026-06-23 N465DF MCC → MCC Jun 23, 13:34 UTCJun 23, 13:50 UTC15m
2026-06-22 N465DF MCC → MCC Jun 22, 22:30 UTCJun 22, 23:10 UTC40m
2026-06-22 N465DF MCC → MCC Jun 22, 19:54 UTCJun 22, 20:34 UTC40m
2026-06-20 N465DF - Jun 20, 19:55 UTCJun 20, 20:14 UTC20m
2026-06-19 N465DF MCC → MCC Jun 19, 23:04 UTCJun 19, 23:39 UTC35m
2026-06-19 N465DF - Jun 19, 03:05 UTCJun 19, 04:10 UTC1h 5m
2026-06-19 N465DF - Jun 19, 02:04 UTCJun 19, 02:29 UTC25m
2026-06-19 N465DF - Jun 19, 00:55 UTCJun 19, 01:15 UTC20m
2026-06-18 N465DF - Jun 18, 23:50 UTCJun 19, 00:20 UTC29m
2026-06-18 N465DF - Jun 18, 22:55 UTCJun 18, 23:15 UTC20m

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

Mode-S A5AC7F frequently asked

What is Mode-S code A5AC7F?
A5AC7F is an ICAO 24-bit transponder address. Allocated to United States. Assigned to N465DF.
Where is Mode-S A5AC7F registered?
Mode-S code A5AC7F 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 A5AC7F broadcasting right now?
No active broadcast right now. Last signal was Jul 25, 01:50 UTC.
Hex, octal, and decimal Mode-S codes: what's the difference?
The same 24-bit identifier expressed in different bases: hex A5AC7F, octal 51326177, decimal 10,857,599.
What flights does A5AC7F operate?
Mode-S A5AC7F has broadcast 1 distinct callsign, including N465DF.