Apparatus

Try JFK, AAL1290, BAW, or N225AN.

sensors Mode-S transponder

ACAFCF

ICAO 24-bit transponder address · allocated to United States

Currently assigned to N91630 · PIPER PA-28-140/150/160/180 · operated by SKYLINK XPRESS INC

Hex
ACAFCF
Octal
53127717
Decimal
11,317,199
Country
US
Tail
N91630
Type
P28A
No current signal · last broadcast 1d ago
Flights observed
85
Distinct callsigns
1
Country
US
Last broadcast
1d ago

Last known position

Most recent position reported by Mode-S ACAFCF.

Country allocation

The ICAO 24-bit address ACAFCF 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
N91630 - 85 2026-06-16

Recent flights last 50

DateFlightRouteTakeoffLandingDuration
2026-06-16 N91630 SBD → SBD Jun 16, 16:10 UTCJun 16, 16:50 UTC40m
2026-06-16 N91630 - Jun 16, 01:10 UTCJun 16, 02:34 UTC1h 25m
2026-06-15 N91630 SBD → SBD Jun 15, 15:40 UTCJun 15, 16:40 UTC1h 0m
2026-06-15 N91630 - Jun 15, 04:04 UTCJun 15, 04:20 UTC15m
2026-06-15 N91630 SBD → SBD Jun 15, 02:44 UTCJun 15, 04:00 UTC1h 15m
2026-06-13 N91630 SBD → SBD Jun 13, 17:55 UTCJun 13, 18:05 UTC10m
2026-06-13 N91630 SBD → SBD Jun 13, 03:05 UTCJun 13, 03:35 UTC30m
2026-06-12 N91630 SBD → SBD Jun 12, 18:55 UTCJun 12, 19:35 UTC40m
2026-06-12 N91630 - Jun 12, 04:00 UTCJun 12, 04:45 UTC45m
2026-06-11 N91630 SBD → SBD Jun 11, 17:15 UTCJun 11, 18:10 UTC55m
2026-06-10 N91630 - Jun 10, 22:50 UTCJun 11, 00:15 UTC1h 25m
2026-06-10 N91630 - Jun 10, 18:05 UTCJun 10, 18:55 UTC50m
2026-06-10 N91630 SBD → SBD Jun 10, 16:30 UTCJun 10, 17:00 UTC30m
2026-06-09 N91630 SBD → SBD Jun 9, 22:40 UTCJun 9, 23:50 UTC1h 10m
2026-06-09 N91630 SBD → SBD Jun 9, 19:10 UTCJun 9, 21:10 UTC2h 0m
2026-06-09 N91630 SBD → SBD Jun 9, 16:55 UTCJun 9, 17:25 UTC30m
2026-06-08 N91630 - Jun 8, 21:05 UTCJun 8, 21:50 UTC45m
2026-06-08 N91630 SBD → BUR Jun 8, 19:45 UTCJun 8, 20:30 UTC45m
2026-06-06 N91630 SBD → SBD Jun 6, 17:29 UTCJun 6, 18:55 UTC1h 25m
2026-06-06 N91630 SBD → SBD Jun 6, 15:30 UTCJun 6, 16:04 UTC35m
2026-06-05 N91630 SBD → SBD Jun 5, 18:15 UTCJun 5, 18:55 UTC40m
2026-06-05 N91630 SBD → SBD Jun 5, 15:15 UTCJun 5, 15:50 UTC35m
2026-06-04 N91630 SBD → SBD Jun 4, 14:50 UTCJun 4, 15:55 UTC1h 5m
2026-06-03 N91630 SBD → SBD Jun 3, 15:55 UTCJun 3, 16:30 UTC35m
2026-06-03 N91630 SBD → SBD Jun 3, 01:25 UTCJun 3, 01:50 UTC25m
2026-05-30 N91630 - May 30, 17:15 UTCMay 30, 17:50 UTC35m
2026-05-29 N91630 - May 29, 19:25 UTCMay 29, 20:30 UTC1h 5m
2026-05-29 N91630 SBD → SBD May 29, 15:30 UTCMay 29, 15:55 UTC25m
2026-05-29 N91630 SBD → SBD May 29, 02:15 UTCMay 29, 02:35 UTC20m
2026-05-29 N91630 SBD → SBD May 29, 00:55 UTCMay 29, 01:20 UTC25m
2026-05-28 N91630 - May 28, 15:45 UTCMay 28, 16:40 UTC55m
2026-05-26 N91630 SBD → SBD May 26, 17:30 UTCMay 26, 18:05 UTC35m
2026-05-26 N91630 SBD → SBD May 26, 01:20 UTCMay 26, 02:15 UTC55m
2026-05-25 N91630 SBD → SBD May 25, 20:19 UTCMay 25, 20:40 UTC20m
2026-05-25 N91630 SBD → SBD May 25, 18:25 UTCMay 25, 18:55 UTC30m
2026-05-25 N91630 SBD → SBD May 25, 16:10 UTCMay 25, 17:05 UTC55m
2026-05-25 N91630 - May 25, 01:55 UTCMay 25, 02:20 UTC25m
2026-05-24 N91630 SBD → SBD May 24, 19:50 UTCMay 24, 20:15 UTC25m
2026-05-23 N91630 - May 23, 22:20 UTCMay 23, 23:00 UTC40m
2026-05-23 N91630 SBD → SBD May 23, 19:40 UTCMay 23, 21:05 UTC1h 25m
2026-05-22 N91630 - May 22, 17:55 UTCMay 22, 18:45 UTC50m
2026-05-22 N91630 - May 22, 05:40 UTCMay 22, 05:50 UTC10m
2026-05-22 N91630 - May 22, 01:50 UTCMay 22, 02:50 UTC1h 0m
2026-05-21 N91630 - May 21, 17:35 UTCMay 21, 18:25 UTC50m
2026-05-21 N91630 SBD → SBD May 21, 15:20 UTCMay 21, 16:30 UTC1h 10m
2026-05-21 N91630 GYR → SBD May 21, 00:45 UTCMay 21, 03:45 UTC3h 0m
2026-05-20 N91630 SBD → GYR May 20, 19:50 UTCMay 20, 22:35 UTC2h 45m
2026-05-20 N91630 SBD → SBD May 20, 14:55 UTCMay 20, 16:00 UTC1h 5m
2026-05-19 N91630 - May 19, 16:55 UTCMay 19, 17:15 UTC20m
2026-05-17 N91630 SBD → SBD May 17, 21:01 UTCMay 17, 21:55 UTC55m

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

Mode-S ACAFCF frequently asked

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