sensors Mode-S transponder
AAAC3A
ICAO 24-bit transponder address · allocated to United States
Currently assigned to N787TK · operated by IAL CORP
- Hex
- AAAC3A
- Octal
- 52526072
- Decimal
- 11,185,210
- Country
- US
- Tail
- N787TK
- Type
- P28A
- Flights observed
- 48
- Distinct callsigns
- 1
- Country
- US
- Last broadcast
- 17h ago
Last known position
Country allocation
The ICAO 24-bit address AAAC3A 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 |
|---|---|---|---|
| N787TK | - | 48 | 2026-07-13 |
Recent flights last 48
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-13 | N787TK | - | Jul 13, 18:05 UTC | Jul 13, 18:20 UTC | 15m |
| 2026-07-13 | N787TK | - | Jul 13, 11:10 UTC | Jul 13, 12:15 UTC | 1h 5m |
| 2026-07-13 | N787TK | - | Jul 13, 09:55 UTC | Jul 13, 10:15 UTC | 20m |
| 2026-07-11 | N787TK | - | Jul 11, 17:35 UTC | Jul 11, 17:55 UTC | 20m |
| 2026-07-11 | N787TK | - | Jul 11, 13:45 UTC | Jul 11, 14:10 UTC | 25m |
| 2026-06-28 | N787TK | JCI → JCI | Jun 28, 21:24 UTC | Jun 28, 21:55 UTC | 30m |
| 2026-06-24 | N787TK | JCI → JCI | Jun 24, 21:00 UTC | Jun 24, 22:29 UTC | 1h 30m |
| 2026-06-23 | N787TK | - | Jun 23, 15:24 UTC | Jun 23, 15:34 UTC | 10m |
| 2026-06-23 | N787TK | - | Jun 23, 14:15 UTC | Jun 23, 14:35 UTC | 20m |
| 2026-06-19 | N787TK | - | Jun 19, 19:25 UTC | Jun 19, 19:34 UTC | 10m |
| 2026-06-19 | N787TK | - | Jun 19, 18:30 UTC | Jun 19, 18:54 UTC | 25m |
| 2026-06-15 | N787TK | - | Jun 15, 15:15 UTC | Jun 15, 16:24 UTC | 1h 10m |
| 2026-06-12 | N787TK | - | Jun 12, 16:30 UTC | Jun 12, 17:05 UTC | 35m |
| 2026-06-12 | N787TK | - | Jun 12, 15:25 UTC | Jun 12, 15:40 UTC | 15m |
| 2026-06-09 | N787TK | JCI → JCI | Jun 9, 22:50 UTC | Jun 9, 23:50 UTC | 1h 0m |
| 2026-06-05 | N787TK | - | Jun 5, 22:10 UTC | Jun 5, 22:50 UTC | 40m |
| 2026-06-03 | N787TK | - | Jun 3, 21:00 UTC | Jun 3, 21:15 UTC | 15m |
| 2026-06-03 | N787TK | - | Jun 3, 20:00 UTC | Jun 3, 20:25 UTC | 25m |
| 2026-06-03 | N787TK | - | Jun 3, 18:00 UTC | Jun 3, 18:35 UTC | 35m |
| 2026-06-01 | N787TK | - | Jun 1, 15:45 UTC | Jun 1, 16:00 UTC | 15m |
| 2026-06-01 | N787TK | - | Jun 1, 14:55 UTC | Jun 1, 15:05 UTC | 10m |
| 2026-05-31 | N787TK | JCI → JCI | May 31, 20:35 UTC | May 31, 21:30 UTC | 55m |
| 2026-05-31 | N787TK | - | May 31, 17:50 UTC | May 31, 18:35 UTC | 45m |
| 2026-05-26 | N787TK | - | May 26, 21:49 UTC | May 26, 22:35 UTC | 45m |
| 2026-05-20 | N787TK | - | May 20, 23:50 UTC | May 21, 00:35 UTC | 45m |
| 2026-05-20 | N787TK | - | May 20, 17:25 UTC | May 20, 19:20 UTC | 1h 55m |
| 2026-05-16 | N787TK | - | May 16, 21:00 UTC | May 16, 21:20 UTC | 20m |
| 2026-05-16 | N787TK | - | May 16, 19:55 UTC | May 16, 20:20 UTC | 25m |
| 2026-05-13 | N787TK | - | May 13, 20:35 UTC | May 13, 20:50 UTC | 15m |
| 2026-05-13 | N787TK | - | May 13, 19:05 UTC | May 13, 19:25 UTC | 20m |
| 2026-05-12 | N787TK | - | May 12, 18:55 UTC | May 12, 20:15 UTC | 1h 20m |
| 2026-05-11 | N787TK | - | May 11, 19:05 UTC | May 11, 20:25 UTC | 1h 20m |
| 2026-05-06 | N787TK | - | May 6, 22:05 UTC | May 6, 23:10 UTC | 1h 5m |
| 2026-05-02 | N787TK | - | May 2, 20:25 UTC | May 2, 21:40 UTC | 1h 15m |
| 2026-05-02 | N787TK | - | May 2, 16:55 UTC | May 2, 18:50 UTC | 1h 55m |
| 2026-05-02 | N787TK | - | May 2, 13:10 UTC | May 2, 14:45 UTC | 1h 35m |
| 2026-05-02 | N787TK | - | May 2, 11:05 UTC | May 2, 12:30 UTC | 1h 25m |
| 2026-05-02 | N787TK | OJC → OJC | May 2, 10:45 UTC | May 2, 10:50 UTC | 5m |
| 2026-05-01 | N787TK | - | May 1, 19:10 UTC | May 1, 20:00 UTC | 50m |
| 2026-05-01 | N787TK | - | May 1, 17:00 UTC | May 1, 17:10 UTC | 10m |
| 2026-05-01 | N787TK | - | May 1, 14:00 UTC | May 1, 14:15 UTC | 15m |
| 2026-04-30 | N787TK | - | Apr 30, 21:40 UTC | Apr 30, 22:10 UTC | 30m |
| 2026-04-29 | N787TK | - | Apr 29, 22:00 UTC | Apr 29, 23:00 UTC | 1h 0m |
| 2026-04-29 | N787TK | JCI → JCI | Apr 29, 19:05 UTC | Apr 29, 20:10 UTC | 1h 5m |
| 2026-04-27 | N787TK | - | Apr 27, 19:05 UTC | Apr 27, 19:15 UTC | 10m |
| 2026-04-27 | N787TK | - | Apr 27, 17:40 UTC | Apr 27, 18:00 UTC | 20m |
| 2026-04-25 | N787TK | - | Apr 25, 20:40 UTC | Apr 25, 21:00 UTC | 20m |
| 2026-04-25 | N787TK | - | Apr 25, 19:40 UTC | Apr 25, 20:00 UTC | 20m |
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 N787TK page for operator, model, and routing details .