sensors Mode-S transponder
A13060
ICAO 24-bit transponder address · allocated to United States
Currently assigned to N176KH · GULFSTREAM G650 · operated by WILMINGTON TRUST CO TRUSTEE
- Hex
- A13060
- Octal
- 50230140
- Decimal
- 10,563,680
- Country
- US
- Tail
- N176KH
- Type
- GLF6
- Flights observed
- 55
- Distinct callsigns
- 1
- Country
- US
- Last broadcast
- 1d ago
Last known position
Country allocation
The ICAO 24-bit address A13060 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 |
|---|---|---|---|
| N176KH | - | 55 | 2026-07-23 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-23 | N176KH | - | Jul 23, 20:05 UTC | Jul 23, 23:10 UTC | 3h 5m |
| 2026-07-23 | N176KH | - | Jul 23, 15:25 UTC | Jul 23, 19:00 UTC | 3h 35m |
| 2026-07-18 | N176KH | - | Jul 18, 20:55 UTC | Jul 18, 21:20 UTC | 25m |
| 2026-07-18 | N176KH | - | Jul 18, 18:45 UTC | Jul 18, 19:50 UTC | 1h 5m |
| 2026-07-18 | N176KH | - | Jul 18, 14:20 UTC | Jul 18, 14:55 UTC | 35m |
| 2026-07-15 | N176KH | TEB → FRG | Jul 15, 23:40 UTC | Jul 16, 00:15 UTC | 35m |
| 2026-07-15 | N176KH | LAS → TEB | Jul 15, 18:20 UTC | Jul 15, 22:55 UTC | 4h 35m |
| 2026-07-13 | N176KH | - | Jul 13, 01:30 UTC | Jul 13, 02:30 UTC | 1h 0m |
| 2026-07-12 | N176KH | - | Jul 12, 21:35 UTC | Jul 13, 00:55 UTC | 3h 20m |
| 2026-07-09 | N176KH | - | Jul 9, 22:20 UTC | Jul 9, 22:55 UTC | 35m |
| 2026-07-09 | N176KH | - | Jul 9, 20:50 UTC | Jul 9, 21:30 UTC | 40m |
| 2026-07-09 | N176KH | - | Jul 9, 19:10 UTC | Jul 9, 19:45 UTC | 35m |
| 2026-07-02 | N176KH | - | Jul 2, 17:10 UTC | Jul 2, 17:45 UTC | 35m |
| 2026-07-02 | N176KH | - | Jul 2, 15:30 UTC | Jul 2, 16:15 UTC | 45m |
| 2026-07-02 | N176KH | - | Jul 2, 13:10 UTC | Jul 2, 13:40 UTC | 30m |
| 2026-06-29 | N176KH | DCA → FRG | Jun 29, 19:09 UTC | Jun 29, 19:54 UTC | 45m |
| 2026-06-29 | N176KH | - | Jun 29, 14:25 UTC | Jun 29, 15:14 UTC | 50m |
| 2026-06-27 | N176KH | VNY → FRG | Jun 27, 22:09 UTC | Jun 28, 02:29 UTC | 4h 20m |
| 2026-06-26 | N176KH | LAS → VNY | Jun 26, 22:05 UTC | Jun 26, 22:49 UTC | 45m |
| 2026-06-25 | N176KH | - | Jun 25, 13:20 UTC | Jun 25, 17:54 UTC | 4h 35m |
| 2026-06-23 | N176KH | BOS → FRG | Jun 23, 13:59 UTC | Jun 23, 14:44 UTC | 45m |
| 2026-06-23 | N176KH | FRG → BOS | Jun 23, 10:10 UTC | Jun 23, 10:44 UTC | 35m |
| 2026-06-18 | N176KH | - | Jun 18, 10:15 UTC | Jun 18, 10:40 UTC | 25m |
| 2026-06-18 | N176KH | BUR → TEB | Jun 18, 05:10 UTC | Jun 18, 09:15 UTC | 4h 5m |
| 2026-06-17 | N176KH | - | Jun 17, 22:50 UTC | Jun 18, 03:50 UTC | 5h 0m |
| 2026-06-15 | N176KH | DCA → FRG | Jun 15, 06:04 UTC | Jun 15, 07:00 UTC | 55m |
| 2026-06-14 | N176KH | - | Jun 14, 22:10 UTC | Jun 14, 23:00 UTC | 50m |
| 2026-06-14 | N176KH | - | Jun 14, 05:20 UTC | Jun 14, 08:15 UTC | 2h 55m |
| 2026-06-13 | N176KH | - | Jun 13, 19:40 UTC | Jun 13, 23:15 UTC | 3h 35m |
| 2026-06-06 | N176KH | - | Jun 6, 04:30 UTC | Jun 6, 07:25 UTC | 2h 55m |
| 2026-06-05 | N176KH | - | Jun 5, 20:40 UTC | Jun 5, 22:45 UTC | 2h 5m |
| 2026-06-04 | N176KH | - | Jun 4, 04:05 UTC | Jun 4, 06:15 UTC | 2h 10m |
| 2026-06-03 | N176KH | - | Jun 3, 20:15 UTC | Jun 3, 23:30 UTC | 3h 15m |
| 2026-05-28 | N176KH | LAS → FRG | May 28, 16:50 UTC | May 28, 20:55 UTC | 4h 5m |
| 2026-05-27 | N176KH | - | May 27, 22:00 UTC | May 28, 02:30 UTC | 4h 30m |
| 2026-05-26 | N176KH | - | May 26, 05:00 UTC | May 26, 05:15 UTC | 15m |
| 2026-05-26 | N176KH | - | May 26, 03:35 UTC | May 26, 04:35 UTC | 1h 0m |
| 2026-05-25 | N176KH | - | May 25, 20:09 UTC | May 25, 21:09 UTC | 1h 0m |
| 2026-05-25 | N176KH | FRG → TEB | May 25, 18:35 UTC | May 25, 19:15 UTC | 40m |
| 2026-05-24 | N176KH | - | May 24, 05:00 UTC | May 24, 05:15 UTC | 15m |
| 2026-05-24 | N176KH | - | May 24, 03:40 UTC | May 24, 04:35 UTC | 55m |
| 2026-05-23 | N176KH | TEB → BKL | May 23, 20:15 UTC | May 23, 21:15 UTC | 1h 0m |
| 2026-05-23 | N176KH | - | May 23, 18:25 UTC | May 23, 18:55 UTC | 30m |
| 2026-05-01 | N176KH | FTY → FRG | May 1, 02:25 UTC | May 1, 04:00 UTC | 1h 35m |
| 2026-04-30 | N176KH | - | Apr 30, 20:05 UTC | Apr 30, 22:00 UTC | 1h 55m |
| 2026-04-27 | N176KH | - | Apr 27, 18:05 UTC | Apr 27, 18:40 UTC | 35m |
| 2026-04-27 | N176KH | - | Apr 27, 15:00 UTC | Apr 27, 15:25 UTC | 25m |
| 2026-04-26 | N176KH | - | Apr 26, 01:25 UTC | Apr 26, 03:15 UTC | 1h 50m |
| 2026-04-25 | N176KH | - | Apr 25, 18:50 UTC | Apr 25, 20:50 UTC | 2h 0m |
| 2026-04-24 | N176KH | FTY → FRG | Apr 24, 02:25 UTC | Apr 24, 04:10 UTC | 1h 45m |
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 N176KH page for operator, model, and routing details .