sensors Mode-S transponder
AB2144
ICAO 24-bit transponder address · allocated to United States
Currently assigned to N816SP · GULFSTREAM 4 · operated by LOCKTON ENTERPRISES INC
- Hex
- AB2144
- Octal
- 52620504
- Decimal
- 11,215,172
- Country
- US
- Tail
- N816SP
- Type
- GLF4
- Flights observed
- 47
- Distinct callsigns
- 2
- Country
- US
- Last broadcast
- Jul 26, 00:50 UTC
Last known position
Country allocation
The ICAO 24-bit address AB2144 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 2 distinct
Recent flights last 47
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-25 | KFB816 | - | Jul 25, 22:25 UTC | Jul 26, 00:40 UTC | 2h 15m |
| 2026-07-24 | N816SP | - | Jul 24, 16:50 UTC | Jul 24, 18:50 UTC | 2h 0m |
| 2026-07-24 | N816SP | - | Jul 24, 15:10 UTC | Jul 24, 15:40 UTC | 30m |
| 2026-07-23 | KFB816 | - | Jul 23, 23:35 UTC | Jul 24, 00:30 UTC | 55m |
| 2026-07-23 | KFB816 | - | Jul 23, 21:50 UTC | Jul 23, 22:35 UTC | 45m |
| 2026-07-23 | KFB816 | - | Jul 23, 19:40 UTC | Jul 23, 20:45 UTC | 1h 5m |
| 2026-07-23 | KFB816 | SFO → SJC | Jul 23, 17:05 UTC | Jul 23, 17:25 UTC | 20m |
| 2026-07-22 | N816SP | - | Jul 22, 21:45 UTC | Jul 23, 02:45 UTC | 5h 0m |
| 2026-07-22 | N816SP | - | Jul 22, 19:00 UTC | Jul 22, 19:35 UTC | 35m |
| 2026-07-22 | N816SP | - | Jul 22, 15:45 UTC | Jul 22, 18:00 UTC | 2h 15m |
| 2026-07-19 | KFB816 | - | Jul 19, 16:05 UTC | Jul 19, 21:25 UTC | 5h 20m |
| 2026-07-16 | KFB816 | OPF → OAK | Jul 16, 15:35 UTC | Jul 16, 20:49 UTC | 5h 15m |
| 2026-07-15 | N816SP | - | Jul 15, 23:05 UTC | Jul 15, 23:35 UTC | 30m |
| 2026-07-15 | N816SP | - | Jul 15, 16:40 UTC | Jul 15, 21:45 UTC | 5h 5m |
| 2026-07-15 | N816SP | SBD → SBA | Jul 15, 14:30 UTC | Jul 15, 15:05 UTC | 35m |
| 2026-07-12 | N816SP | - | Jul 12, 16:25 UTC | Jul 12, 21:40 UTC | 5h 15m |
| 2026-07-08 | N816SP | - | Jul 8, 20:15 UTC | Jul 8, 21:10 UTC | 55m |
| 2026-07-08 | KFB816 | - | Jul 8, 16:35 UTC | Jul 8, 18:45 UTC | 2h 10m |
| 2026-07-07 | N816SP | - | Jul 7, 18:50 UTC | Jul 7, 19:00 UTC | 10m |
| 2026-07-07 | KFB816 | - | Jul 7, 15:20 UTC | Jul 7, 18:05 UTC | 2h 45m |
| 2026-07-06 | KFB816 | - | Jul 6, 18:55 UTC | Jul 6, 22:35 UTC | 3h 40m |
| 2026-07-06 | KFB816 | PNE → PWK | Jul 6, 15:25 UTC | Jul 6, 17:10 UTC | 1h 45m |
| 2026-07-04 | KFB816 | - | Jul 4, 15:25 UTC | Jul 4, 19:50 UTC | 4h 25m |
| 2026-07-03 | KFB816 | DEN → RBK | Jul 3, 19:30 UTC | Jul 3, 21:25 UTC | 1h 55m |
| 2026-07-03 | KFB816 | - | Jul 3, 18:10 UTC | Jul 3, 18:40 UTC | 30m |
| 2026-07-03 | KFB816 | - | Jul 3, 15:25 UTC | Jul 3, 17:05 UTC | 1h 40m |
| 2026-07-03 | KFB816 | - | Jul 3, 01:10 UTC | Jul 3, 01:55 UTC | 45m |
| 2026-07-03 | KFB816 | YDT → BLI | Jul 3, 00:10 UTC | Jul 3, 00:20 UTC | 10m |
| 2026-07-02 | KFB816 | - | Jul 2, 17:30 UTC | Jul 2, 22:40 UTC | 5h 10m |
| 2026-07-02 | KFB816 | - | Jul 2, 15:15 UTC | Jul 2, 15:50 UTC | 35m |
| 2026-07-01 | KFB816 | - | Jul 1, 23:00 UTC | Jul 2, 00:55 UTC | 1h 55m |
| 2026-07-01 | KFB816 | - | Jul 1, 16:35 UTC | Jul 1, 19:25 UTC | 2h 50m |
| 2026-06-30 | KFB816 | - | Jun 30, 16:55 UTC | Jun 30, 20:55 UTC | 4h 0m |
| 2026-06-29 | KFB816 | - | Jun 29, 23:49 UTC | Jun 30, 04:35 UTC | 4h 46m |
| 2026-06-29 | N816SP | - | Jun 29, 19:15 UTC | Jun 29, 19:44 UTC | 30m |
| 2026-06-06 | N816SP | - | Jun 6, 16:39 UTC | Jun 6, 17:00 UTC | 20m |
| 2026-06-06 | N816SP | - | Jun 6, 15:15 UTC | Jun 6, 15:30 UTC | 15m |
| 2026-06-06 | N816SP | - | Jun 6, 12:35 UTC | Jun 6, 12:49 UTC | 15m |
| 2026-05-30 | N816SP | - | May 30, 18:40 UTC | May 30, 19:25 UTC | 45m |
| 2026-05-30 | N816SP | - | May 30, 16:25 UTC | May 30, 16:40 UTC | 15m |
| 2026-04-30 | N816SP | - | Apr 30, 01:30 UTC | Apr 30, 01:45 UTC | 15m |
| 2026-04-29 | N816SP | - | Apr 29, 23:05 UTC | Apr 30, 00:55 UTC | 1h 50m |
| 2026-04-28 | N816SP | - | Apr 28, 13:45 UTC | Apr 28, 15:50 UTC | 2h 5m |
| 2026-04-28 | N816SP | - | Apr 28, 12:45 UTC | Apr 28, 13:00 UTC | 15m |
| 2026-04-19 | N816SP | - | Apr 19, 17:35 UTC | Apr 19, 17:50 UTC | 15m |
| 2026-04-19 | N816SP | - | Apr 19, 16:25 UTC | Apr 19, 16:45 UTC | 20m |
| 2026-04-19 | N816SP | - | Apr 19, 13:50 UTC | Apr 19, 14:05 UTC | 15m |
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 N816SP page for operator, model, and routing details .