sensors Mode-S transponder
A515BB
ICAO 24-bit transponder address · allocated to United States
Currently assigned to N427BB · BEECH 36 Bonanza · operated by BOLDER TRAVEL LLC
- Hex
- A515BB
- Octal
- 51212673
- Decimal
- 10,819,003
- Country
- US
- Tail
- N427BB
- Type
- BE36
- Flights observed
- 49
- Distinct callsigns
- 1
- Country
- US
- Last broadcast
- 5d ago
Last known position
Country allocation
The ICAO 24-bit address A515BB 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 |
|---|---|---|---|
| N427BB | - | 49 | 2026-07-08 |
Recent flights last 49
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-08 | N427BB | - | Jul 8, 19:05 UTC | Jul 8, 19:55 UTC | 50m |
| 2026-07-08 | N427BB | - | Jul 8, 17:15 UTC | Jul 8, 17:35 UTC | 20m |
| 2026-07-08 | N427BB | BJC → APA | Jul 8, 11:00 UTC | Jul 8, 11:15 UTC | 15m |
| 2026-07-04 | N427BB | - | Jul 4, 20:25 UTC | Jul 4, 21:10 UTC | 45m |
| 2026-07-04 | N427BB | - | Jul 4, 15:40 UTC | Jul 4, 16:20 UTC | 40m |
| 2026-07-03 | N427BB | - | Jul 3, 02:05 UTC | Jul 3, 02:20 UTC | 15m |
| 2026-07-02 | N427BB | - | Jul 2, 11:25 UTC | Jul 2, 11:40 UTC | 15m |
| 2026-06-23 | N427BB | BJC → BJC | Jun 23, 00:19 UTC | Jun 23, 01:04 UTC | 45m |
| 2026-06-16 | N427BB | - | Jun 16, 20:35 UTC | Jun 16, 21:00 UTC | 25m |
| 2026-06-16 | N427BB | - | Jun 16, 17:45 UTC | Jun 16, 18:35 UTC | 50m |
| 2026-06-16 | N427BB | - | Jun 16, 11:49 UTC | Jun 16, 12:05 UTC | 15m |
| 2026-06-12 | N427BB | - | Jun 12, 22:20 UTC | Jun 12, 22:35 UTC | 15m |
| 2026-06-12 | N427BB | - | Jun 12, 18:35 UTC | Jun 12, 19:15 UTC | 40m |
| 2026-06-12 | N427BB | - | Jun 12, 16:40 UTC | Jun 12, 17:10 UTC | 30m |
| 2026-06-12 | N427BB | BJC → APA | Jun 12, 12:00 UTC | Jun 12, 12:15 UTC | 15m |
| 2026-06-11 | N427BB | - | Jun 11, 00:30 UTC | Jun 11, 01:30 UTC | 1h 0m |
| 2026-06-10 | N427BB | - | Jun 10, 22:20 UTC | Jun 10, 23:10 UTC | 50m |
| 2026-06-09 | N427BB | - | Jun 9, 15:00 UTC | Jun 9, 15:45 UTC | 45m |
| 2026-06-09 | N427BB | - | Jun 9, 12:50 UTC | Jun 9, 13:50 UTC | 1h 0m |
| 2026-06-09 | N427BB | - | Jun 9, 01:55 UTC | Jun 9, 02:10 UTC | 15m |
| 2026-06-08 | N427BB | BJC → APA | Jun 8, 10:55 UTC | Jun 8, 11:10 UTC | 15m |
| 2026-06-07 | N427BB | BJC → BJC | Jun 7, 17:00 UTC | Jun 7, 18:20 UTC | 1h 20m |
| 2026-05-24 | N427BB | - | May 24, 18:25 UTC | May 24, 18:45 UTC | 20m |
| 2026-05-24 | N427BB | - | May 24, 15:05 UTC | May 24, 15:30 UTC | 25m |
| 2026-05-23 | N427BB | - | May 23, 15:05 UTC | May 23, 16:05 UTC | 1h 0m |
| 2026-05-23 | N427BB | BJC → BJC | May 23, 14:40 UTC | May 23, 14:50 UTC | 10m |
| 2026-05-21 | N427BB | - | May 21, 21:40 UTC | May 21, 21:55 UTC | 15m |
| 2026-05-21 | N427BB | - | May 21, 16:45 UTC | May 21, 17:20 UTC | 35m |
| 2026-05-21 | N427BB | APA → GXY | May 21, 15:00 UTC | May 21, 16:05 UTC | 1h 5m |
| 2026-05-21 | N427BB | BJC → APA | May 21, 10:45 UTC | May 21, 11:35 UTC | 50m |
| 2026-05-16 | N427BB | - | May 16, 19:30 UTC | May 16, 20:05 UTC | 35m |
| 2026-05-16 | N427BB | - | May 16, 17:35 UTC | May 16, 18:15 UTC | 40m |
| 2026-05-15 | N427BB | - | May 15, 03:05 UTC | May 15, 03:20 UTC | 15m |
| 2026-05-14 | N427BB | BJC → APA | May 14, 18:05 UTC | May 14, 18:20 UTC | 15m |
| 2026-05-12 | N427BB | - | May 12, 18:55 UTC | May 12, 19:55 UTC | 1h 0m |
| 2026-05-12 | N427BB | - | May 12, 16:45 UTC | May 12, 17:30 UTC | 45m |
| 2026-05-11 | N427BB | - | May 11, 14:55 UTC | May 11, 15:35 UTC | 40m |
| 2026-05-11 | N427BB | - | May 11, 12:50 UTC | May 11, 14:00 UTC | 1h 10m |
| 2026-05-11 | N427BB | BJC → BJC | May 11, 00:25 UTC | May 11, 00:54 UTC | 30m |
| 2026-05-09 | N427BB | - | May 9, 01:35 UTC | May 9, 02:00 UTC | 25m |
| 2026-05-04 | N427BB | - | May 4, 12:45 UTC | May 4, 13:05 UTC | 20m |
| 2026-05-03 | N427BB | APA → BJC | May 3, 00:50 UTC | May 3, 01:10 UTC | 20m |
| 2026-05-02 | N427BB | BJC → APA | May 2, 14:20 UTC | May 2, 14:40 UTC | 20m |
| 2026-04-20 | N427BB | - | Apr 20, 21:55 UTC | Apr 20, 22:20 UTC | 25m |
| 2026-04-20 | N427BB | - | Apr 20, 20:05 UTC | Apr 20, 20:15 UTC | 10m |
| 2026-04-20 | N427BB | - | Apr 20, 17:25 UTC | Apr 20, 18:50 UTC | 1h 25m |
| 2026-04-20 | N427BB | - | Apr 20, 16:15 UTC | Apr 20, 16:45 UTC | 30m |
| 2026-04-20 | N427BB | - | Apr 20, 14:15 UTC | Apr 20, 15:00 UTC | 45m |
| 2026-04-20 | N427BB | - | Apr 20, 11:55 UTC | Apr 20, 13:30 UTC | 1h 35m |
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 N427BB page for operator, model, and routing details .