sensors Mode-S transponder
ACADBF
ICAO 24-bit transponder address · allocated to United States
Currently assigned to N916JB · HAWKER BEECHCRAFT Hawker 750/850 · operated by BANC OF CALIFORNIA
- Hex
- ACADBF
- Octal
- 53126677
- Decimal
- 11,316,671
- Country
- US
- Tail
- N916JB
- Type
- H25B
- Flights observed
- 52
- Distinct callsigns
- 1
- Country
- US
- Last broadcast
- 3h ago
Current position
Country allocation
The ICAO 24-bit address ACADBF 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 |
|---|---|---|---|
| N916JB | - | 52 | 2026-07-14 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-14 | N916JB | - | Jul 14, 19:45 UTC | Jul 14, 21:35 UTC | 1h 50m |
| 2026-07-10 | N916JB | - | Jul 10, 22:25 UTC | Jul 10, 23:40 UTC | 1h 15m |
| 2026-07-09 | N916JB | - | Jul 9, 22:45 UTC | Jul 9, 23:45 UTC | 1h 0m |
| 2026-07-09 | N916JB | - | Jul 9, 18:30 UTC | Jul 9, 21:40 UTC | 3h 10m |
| 2026-07-07 | N916JB | - | Jul 7, 21:50 UTC | Jul 8, 00:10 UTC | 2h 20m |
| 2026-07-07 | N916JB | - | Jul 7, 12:05 UTC | Jul 7, 20:50 UTC | 8h 45m |
| 2026-07-03 | N916JB | - | Jul 3, 20:55 UTC | Jul 4, 06:00 UTC | 9h 5m |
| 2026-07-03 | N916JB | - | Jul 3, 20:00 UTC | Jul 3, 20:20 UTC | 20m |
| 2026-07-03 | N916JB | - | Jul 3, 02:50 UTC | Jul 3, 04:20 UTC | 1h 30m |
| 2026-07-03 | N916JB | - | Jul 3, 01:55 UTC | Jul 3, 02:15 UTC | 20m |
| 2026-07-01 | N916JB | - | Jul 1, 21:25 UTC | Jul 2, 00:30 UTC | 3h 5m |
| 2026-07-01 | N916JB | - | Jul 1, 12:00 UTC | Jul 1, 14:45 UTC | 2h 45m |
| 2026-06-26 | N916JB | - | Jun 26, 17:50 UTC | Jun 26, 18:24 UTC | 35m |
| 2026-06-22 | N916JB | - | Jun 22, 12:10 UTC | Jun 22, 12:44 UTC | 35m |
| 2026-06-16 | N916JB | TEB → GXY | Jun 16, 00:15 UTC | Jun 16, 04:15 UTC | 4h 0m |
| 2026-06-14 | N916JB | - | Jun 14, 14:20 UTC | Jun 14, 17:20 UTC | 3h 0m |
| 2026-06-12 | N916JB | - | Jun 12, 15:15 UTC | Jun 12, 17:30 UTC | 2h 15m |
| 2026-06-11 | N916JB | - | Jun 11, 21:20 UTC | Jun 11, 23:15 UTC | 1h 55m |
| 2026-06-10 | N916JB | - | Jun 10, 21:30 UTC | Jun 10, 22:45 UTC | 1h 15m |
| 2026-06-09 | N916JB | - | Jun 9, 22:10 UTC | Jun 9, 23:00 UTC | 50m |
| 2026-06-09 | N916JB | - | Jun 9, 11:20 UTC | Jun 9, 12:05 UTC | 45m |
| 2026-06-08 | N916JB | - | Jun 8, 13:45 UTC | Jun 8, 16:05 UTC | 2h 20m |
| 2026-06-04 | N916JB | - | Jun 4, 12:50 UTC | Jun 4, 14:15 UTC | 1h 25m |
| 2026-06-03 | N916JB | - | Jun 3, 19:50 UTC | Jun 3, 21:05 UTC | 1h 15m |
| 2026-06-02 | N916JB | - | Jun 2, 22:50 UTC | Jun 3, 00:15 UTC | 1h 25m |
| 2026-06-02 | N916JB | - | Jun 2, 21:40 UTC | Jun 2, 22:00 UTC | 20m |
| 2026-06-02 | N916JB | - | Jun 2, 12:00 UTC | Jun 2, 12:55 UTC | 55m |
| 2026-06-01 | N916JB | GXY → DSM | Jun 1, 13:55 UTC | Jun 1, 15:55 UTC | 2h 0m |
| 2026-05-29 | N916JB | GXY → GXY | May 29, 17:45 UTC | May 29, 18:30 UTC | 45m |
| 2026-05-27 | N916JB | - | May 27, 19:50 UTC | May 27, 22:15 UTC | 2h 25m |
| 2026-05-27 | N916JB | YYC → AZO | May 27, 12:05 UTC | May 27, 15:50 UTC | 3h 45m |
| 2026-05-26 | N916JB | - | May 26, 20:09 UTC | May 26, 21:55 UTC | 1h 45m |
| 2026-05-14 | N916JB | - | May 14, 19:55 UTC | May 14, 22:25 UTC | 2h 30m |
| 2026-05-14 | N916JB | GXY → HAO | May 14, 13:40 UTC | May 14, 16:05 UTC | 2h 25m |
| 2026-05-11 | N916JB | - | May 11, 15:15 UTC | May 11, 17:15 UTC | 2h 1m |
| 2026-05-08 | N916JB | - | May 8, 19:00 UTC | May 8, 21:15 UTC | 2h 15m |
| 2026-05-08 | N916JB | - | May 8, 13:30 UTC | May 8, 15:20 UTC | 1h 50m |
| 2026-05-07 | N916JB | SJC → GXY | May 7, 05:35 UTC | May 7, 07:45 UTC | 2h 10m |
| 2026-05-06 | N916JB | - | May 6, 18:50 UTC | May 6, 20:55 UTC | 2h 5m |
| 2026-05-05 | N916JB | - | May 5, 20:40 UTC | May 5, 22:25 UTC | 1h 45m |
| 2026-05-04 | N916JB | - | May 4, 13:40 UTC | May 4, 14:55 UTC | 1h 15m |
| 2026-04-29 | N916JB | - | Apr 29, 22:55 UTC | Apr 30, 00:35 UTC | 1h 39m |
| 2026-04-28 | N916JB | - | Apr 28, 19:00 UTC | Apr 28, 21:19 UTC | 2h 20m |
| 2026-04-24 | N916JB | - | Apr 24, 20:05 UTC | Apr 24, 21:45 UTC | 1h 40m |
| 2026-04-24 | N916JB | - | Apr 24, 13:50 UTC | Apr 24, 15:05 UTC | 1h 15m |
| 2026-04-23 | N916JB | - | Apr 23, 20:55 UTC | Apr 24, 00:20 UTC | 3h 25m |
| 2026-04-23 | N916JB | - | Apr 23, 12:10 UTC | Apr 23, 15:00 UTC | 2h 50m |
| 2026-04-15 | N916JB | - | Apr 15, 00:55 UTC | Apr 15, 01:10 UTC | 15m |
| 2026-04-15 | N916JB | - | Apr 15, 00:30 UTC | Apr 15, 00:50 UTC | 20m |
| 2026-04-14 | N916JB | - | Apr 14, 13:15 UTC | Apr 14, 13:55 UTC | 40m |
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 N916JB page for operator, model, and routing details .