sensors Mode-S transponder
A0B2DB
ICAO 24-bit transponder address · allocated to United States
Currently assigned to N144PK · GULFSTREAM 4 · operated by AVIRE LLC
- Hex
- A0B2DB
- Octal
- 50131333
- Decimal
- 10,531,547
- Country
- US
- Tail
- N144PK
- Type
- GLF4
- Flights observed
- 51
- Distinct callsigns
- 3
- Country
- US
- Last broadcast
- 1d ago
Last known position
Country allocation
The ICAO 24-bit address A0B2DB 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 3 distinct
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-06-01 | N144PK | MNZ → TEB | Jun 1, 19:05 UTC | Jun 1, 20:00 UTC | 55m |
| 2026-05-31 | N144PK | TEB → MNZ | May 31, 12:05 UTC | May 31, 12:55 UTC | 50m |
| 2026-05-23 | N144PK | - | May 23, 17:45 UTC | May 23, 19:15 UTC | 1h 31m |
| 2026-05-22 | N144PK | - | May 22, 19:20 UTC | May 22, 21:20 UTC | 2h 0m |
| 2026-05-21 | N144PK | TEB → YUL | May 21, 18:25 UTC | May 21, 19:20 UTC | 55m |
| 2026-05-19 | N144PK | LAS → TEB | May 19, 01:25 UTC | May 19, 05:35 UTC | 4h 10m |
| 2026-05-18 | N144PK | MTY → LAS | May 18, 00:50 UTC | May 18, 04:40 UTC | 3h 50m |
| 2026-05-16 | N144PK | - | May 16, 22:50 UTC | May 17, 02:15 UTC | 3h 25m |
| 2026-05-16 | N144PK | SJC → SFO | May 16, 21:00 UTC | May 16, 21:15 UTC | 15m |
| 2026-05-15 | N144PK | - | May 15, 22:50 UTC | May 15, 23:45 UTC | 55m |
| 2026-05-15 | N144PK | - | May 15, 20:55 UTC | May 15, 21:15 UTC | 20m |
| 2026-05-14 | 00000000 | - | May 14, 02:40 UTC | May 14, 03:30 UTC | 50m |
| 2026-05-14 | 00000000 | SJC → SJC | May 14, 01:40 UTC | May 14, 01:50 UTC | 10m |
| 2026-05-13 | N144PK | - | May 13, 19:10 UTC | May 13, 19:30 UTC | 20m |
| 2026-05-13 | N144PK | - | May 13, 12:25 UTC | May 13, 17:50 UTC | 5h 25m |
| 2026-05-13 | N144PK | - | May 13, 10:35 UTC | May 13, 11:20 UTC | 45m |
| 2026-05-12 | 00000000 | LAS → TEB | May 12, 15:20 UTC | May 12, 19:40 UTC | 4h 20m |
| 2026-05-12 | 00000000 | VNY → LAS | May 12, 13:30 UTC | May 12, 14:15 UTC | 45m |
| 2026-05-12 | N144PK | - | May 12, 06:20 UTC | May 12, 06:30 UTC | 10m |
| 2026-05-12 | N144PK | - | May 12, 02:45 UTC | May 12, 05:20 UTC | 2h 35m |
| 2026-05-11 | N144PK | TEB → YYZ | May 11, 18:50 UTC | May 11, 19:50 UTC | 1h 0m |
| 2026-05-09 | N144PK | - | May 9, 01:00 UTC | May 9, 03:35 UTC | 2h 35m |
| 2026-05-08 | N144PK | - | May 8, 18:35 UTC | May 8, 21:20 UTC | 2h 45m |
| 2026-05-07 | N144PK | - | May 7, 07:30 UTC | May 7, 12:00 UTC | 4h 30m |
| 2026-05-05 | N144PK | - | May 5, 02:50 UTC | May 5, 03:35 UTC | 45m |
| 2026-05-05 | N144PK | BFI → SJC | May 5, 00:15 UTC | May 5, 02:05 UTC | 1h 50m |
| 2026-05-04 | N144PK | SJC → BFI | May 4, 15:30 UTC | May 4, 17:20 UTC | 1h 50m |
| 2026-05-03 | N144PK | - | May 3, 23:04 UTC | May 3, 23:50 UTC | 45m |
| 2026-05-03 | N144PK | - | May 3, 14:10 UTC | May 3, 19:55 UTC | 5h 45m |
| 2026-05-02 | N144PK | - | May 2, 18:30 UTC | May 2, 18:55 UTC | 25m |
| 2026-05-01 | N144PK | - | May 1, 11:45 UTC | May 1, 15:20 UTC | 3h 35m |
| 2026-04-29 | N144PK | - | Apr 29, 23:15 UTC | Apr 30, 00:15 UTC | 1h 0m |
| 2026-04-29 | N144PK | - | Apr 29, 16:35 UTC | Apr 29, 22:20 UTC | 5h 45m |
| 2026-04-26 | N144PK | - | Apr 26, 18:40 UTC | Apr 26, 19:40 UTC | 1h 0m |
| 2026-04-25 | N144PK | - | Apr 25, 16:45 UTC | Apr 25, 20:30 UTC | 3h 45m |
| 2026-04-25 | 00000000 | - | Apr 25, 12:40 UTC | Apr 25, 14:40 UTC | 2h 0m |
| 2026-04-24 | N144PK | - | Apr 24, 14:40 UTC | Apr 24, 17:40 UTC | 3h 0m |
| 2026-04-24 | N144PK00 | IAD → TEB | Apr 24, 11:55 UTC | Apr 24, 12:40 UTC | 45m |
| 2026-04-21 | N144PK | - | Apr 21, 20:05 UTC | Apr 22, 00:25 UTC | 4h 20m |
| 2026-04-20 | 00000000 | - | Apr 20, 12:40 UTC | Apr 20, 17:50 UTC | 5h 10m |
| 2026-04-19 | 00000000 | - | Apr 19, 23:15 UTC | Apr 20, 01:00 UTC | 1h 45m |
| 2026-04-19 | 00000000 | - | Apr 19, 19:30 UTC | Apr 19, 20:20 UTC | 50m |
| 2026-04-18 | 00000000 | - | Apr 18, 18:15 UTC | Apr 18, 18:40 UTC | 25m |
| 2026-04-18 | 00000000 | - | Apr 18, 13:15 UTC | Apr 18, 16:35 UTC | 3h 20m |
| 2026-04-18 | 00000000 | - | Apr 18, 11:45 UTC | Apr 18, 12:25 UTC | 40m |
| 2026-04-16 | 00000000 | - | Apr 16, 01:10 UTC | Apr 16, 03:04 UTC | 1h 55m |
| 2026-04-16 | 00000000 | - | Apr 16, 00:35 UTC | Apr 16, 01:05 UTC | 30m |
| 2026-04-14 | 00000000 | - | Apr 14, 12:50 UTC | Apr 14, 14:15 UTC | 1h 25m |
| 2026-04-14 | 00000000 | - | Apr 14, 12:05 UTC | Apr 14, 12:45 UTC | 40m |
| 2026-04-12 | 00000000 | - | Apr 12, 19:30 UTC | Apr 12, 19:40 UTC | 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 N144PK page for operator, model, and routing details .