Apparatus

Try JFK, AAL1290, BAW, or N225AN.

sensors Mode-S transponder

ACFCC2

ICAO 24-bit transponder address · allocated to United States

Currently assigned to N936JG · RAYTHEON 390 Premier 1 · operated by ALS MANAGEMENT LLC

Hex
ACFCC2
Octal
53176302
Decimal
11,336,898
Country
US
Tail
N936JG
Type
PRM1
No current signal · last broadcast 1d ago
Flights observed
62
Distinct callsigns
1
Country
US
Last broadcast
1d ago

Last known position

Most recent position reported by Mode-S ACFCC2.

Country allocation

The ICAO 24-bit address ACFCC2 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
N936JG - 62 2026-07-11

Recent flights last 50

DateFlightRouteTakeoffLandingDuration
2026-07-11 N936JG - Jul 11, 01:40 UTCJul 11, 02:45 UTC1h 5m
2026-07-11 N936JG - Jul 11, 00:15 UTCJul 11, 00:35 UTC20m
2026-07-10 N936JG - Jul 10, 01:15 UTCJul 10, 01:40 UTC25m
2026-07-09 N936JG - Jul 9, 22:55 UTCJul 10, 00:35 UTC1h 40m
2026-07-09 N936JG - Jul 9, 03:00 UTCJul 9, 04:00 UTC1h 0m
2026-07-09 N936JG BFL → SJC Jul 9, 01:50 UTCJul 9, 02:30 UTC40m
2026-07-08 N936JG SJC → BFL Jul 8, 19:25 UTCJul 8, 20:05 UTC40m
2026-07-08 N936JG BFL → SJC Jul 8, 17:40 UTCJul 8, 18:20 UTC40m
2026-07-02 N936JG - Jul 2, 19:25 UTCJul 2, 19:55 UTC30m
2026-07-02 N936JG BFL → RBK Jul 2, 06:30 UTCJul 2, 07:00 UTC30m
2026-07-02 N936JG - Jul 2, 05:05 UTCJul 2, 05:35 UTC30m
2026-07-02 N936JG - Jul 2, 04:10 UTCJul 2, 04:25 UTC15m
2026-07-02 N936JG - Jul 2, 00:40 UTCJul 2, 00:50 UTC10m
2026-07-01 N936JG BFL → CNO Jul 1, 23:15 UTCJul 1, 23:45 UTC30m
2026-07-01 N936JG - Jul 1, 20:10 UTCJul 1, 20:45 UTC35m
2026-06-28 N936JG BFL → RBK Jun 28, 21:45 UTCJun 28, 22:15 UTC30m
2026-06-28 N936JG - Jun 28, 20:09 UTCJun 28, 20:34 UTC25m
2026-06-28 N936JG BFL → HHR Jun 28, 17:50 UTCJun 28, 19:04 UTC1h 15m
2026-06-26 N936JG - Jun 26, 20:59 UTCJun 26, 21:15 UTC15m
2026-06-26 N936JG - Jun 26, 19:50 UTCJun 26, 20:15 UTC25m
2026-06-26 N936JG BFL → MCC Jun 26, 18:20 UTCJun 26, 19:04 UTC45m
2026-06-20 N936JG RBK → BFL Jun 20, 17:39 UTCJun 20, 18:14 UTC35m
2026-06-18 N936JG - Jun 18, 20:40 UTCJun 18, 21:05 UTC25m
2026-06-18 N936JG - Jun 18, 19:25 UTCJun 18, 20:00 UTC35m
2026-06-18 N936JG - Jun 18, 18:20 UTCJun 18, 18:55 UTC35m
2026-06-17 N936JG - Jun 17, 21:15 UTCJun 17, 21:50 UTC35m
2026-06-17 N936JG - Jun 17, 19:25 UTCJun 17, 20:30 UTC1h 5m
2026-06-17 N936JG - Jun 17, 18:05 UTCJun 17, 18:25 UTC20m
2026-06-17 N936JG - Jun 17, 02:45 UTCJun 17, 03:20 UTC35m
2026-06-17 N936JG PHX → BFL Jun 17, 01:00 UTCJun 17, 02:10 UTC1h 10m
2026-06-16 N936JG - Jun 16, 21:50 UTCJun 17, 00:10 UTC2h 20m
2026-06-16 N936JG COE → COE Jun 16, 19:05 UTCJun 16, 19:35 UTC30m
2026-06-16 N936JG COE → COE Jun 16, 15:55 UTCJun 16, 16:45 UTC50m
2026-06-16 N936JG - Jun 16, 01:45 UTCJun 16, 02:15 UTC30m
2026-06-16 N936JG COE → GEG Jun 16, 00:10 UTCJun 16, 01:10 UTC1h 0m
2026-06-15 N936JG COE → COE Jun 15, 02:20 UTCJun 15, 03:30 UTC1h 10m
2026-06-14 N936JG BFL → COE Jun 14, 20:50 UTCJun 14, 23:00 UTC2h 10m
2026-06-14 N936JG - Jun 14, 03:35 UTCJun 14, 04:25 UTC50m
2026-06-13 N936JG BFL → RBK Jun 13, 23:35 UTCJun 14, 00:10 UTC35m
2026-06-13 N936JG - Jun 13, 16:30 UTCJun 13, 17:00 UTC30m
2026-06-12 N936JG - Jun 12, 23:55 UTCJun 13, 00:15 UTC20m
2026-05-30 N936JG - May 30, 02:00 UTCMay 30, 02:15 UTC15m
2026-05-30 N936JG - May 30, 01:10 UTCMay 30, 01:25 UTC15m
2026-05-27 N936JG COE → BFL May 27, 02:14 UTCMay 27, 04:24 UTC2h 10m
2026-05-26 N936JG COE → COE May 26, 23:10 UTCMay 27, 00:04 UTC55m
2026-05-26 N936JG - May 26, 03:25 UTCMay 26, 04:15 UTC50m
2026-05-26 N936JG BFL → BOI May 26, 00:14 UTCMay 26, 01:40 UTC1h 25m
2026-05-25 N936JG BFL → BFL May 25, 03:10 UTCMay 25, 04:15 UTC1h 5m
2026-05-24 N936JG BFL → BFL May 24, 03:45 UTCMay 24, 04:15 UTC30m
2026-05-24 N936JG BFL → BFL May 24, 00:40 UTCMay 24, 01:50 UTC1h 10m

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

Mode-S ACFCC2 frequently asked

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