sensors Mode-S transponder
AA2315
ICAO 24-bit transponder address · allocated to United States
Currently assigned to N752SP · EMBRAER EMB-135 Legacy · operated by CONTINENTAL CARRIER LLC
- Hex
- AA2315
- Octal
- 52421425
- Decimal
- 11,150,101
- Country
- US
- Tail
- N752SP
- Type
- E35L
- Flights observed
- 48
- Distinct callsigns
- 20
- Country
- US
- Last broadcast
- 1d ago
Last known position
Country allocation
The ICAO 24-bit address AA2315 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 20 distinct
| Callsign | Airline | Flights | Last seen |
|---|---|---|---|
| VTE752 | Corporate Flight Management | 18 | 2026-06-03 |
| VTE7752 | Corporate Flight Management | 12 | 2026-06-03 |
| VTE922 | Corporate Flight Management | 1 | 2026-04-20 |
| VTE921 | Corporate Flight Management | 1 | 2026-04-19 |
| VTE920 | - | 1 | 2026-04-18 |
| VTE882 | Corporate Flight Management | 1 | 2026-05-07 |
| VTE881 | Corporate Flight Management | 1 | 2026-05-06 |
| VTE8752 | Corporate Flight Management | 1 | 2026-05-15 |
| VTE7548 | Corporate Flight Management | 1 | 2026-04-30 |
| VTE601 | Corporate Flight Management | 1 | 2026-04-30 |
| VTE600 | Corporate Flight Management | 1 | 2026-04-30 |
| VTE548 | Corporate Flight Management | 1 | 2026-04-30 |
| VTE059 | Corporate Flight Management | 1 | 2026-05-16 |
| VTE058 | Corporate Flight Management | 1 | 2026-05-16 |
| VTE056 | Corporate Flight Management | 1 | 2026-05-16 |
| VTE055 | Corporate Flight Management | 1 | 2026-05-16 |
| VTE054 | - | 1 | 2026-05-16 |
| VTE053 | - | 1 | 2026-05-16 |
| VTE052 | Corporate Flight Management | 1 | 2026-05-16 |
| N752SP | - | 1 | 2026-05-25 |
Recent flights last 48
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-06-03 | VTE752 | IKK → PHL | Jun 3, 19:35 UTC | Jun 3, 21:15 UTC | 1h 40m |
| 2026-06-03 | VTE7752 | - | Jun 3, 17:50 UTC | Jun 3, 18:25 UTC | 35m |
| 2026-06-01 | VTE7752 | - | Jun 1, 00:55 UTC | Jun 1, 02:00 UTC | 1h 5m |
| 2026-05-31 | VTE752 | IKK → PHL | May 31, 20:25 UTC | May 31, 23:55 UTC | 3h 30m |
| 2026-05-27 | VTE752 | IKK → PHL | May 27, 23:05 UTC | May 28, 03:10 UTC | 4h 5m |
| 2026-05-25 | VTE752 | IKK → PHL | May 25, 23:30 UTC | May 26, 02:10 UTC | 2h 40m |
| 2026-05-25 | VTE7752 | - | May 25, 20:40 UTC | May 25, 20:55 UTC | 15m |
| 2026-05-25 | N752SP | - | May 25, 18:50 UTC | May 25, 19:30 UTC | 39m |
| 2026-05-22 | VTE752 | IKK → PHL | May 22, 15:40 UTC | May 22, 16:20 UTC | 40m |
| 2026-05-22 | VTE752 | IKK → PHL | May 22, 12:55 UTC | May 22, 13:10 UTC | 15m |
| 2026-05-17 | VTE7752 | - | May 17, 21:30 UTC | May 17, 22:10 UTC | 40m |
| 2026-05-17 | VTE752 | IKK → PHL | May 17, 16:40 UTC | May 17, 18:20 UTC | 1h 40m |
| 2026-05-16 | VTE059 | LEX → BNA | May 16, 22:50 UTC | May 16, 23:30 UTC | 40m |
| 2026-05-16 | VTE058 | - | May 16, 21:55 UTC | May 16, 22:05 UTC | 10m |
| 2026-05-16 | VTE056 | - | May 16, 19:25 UTC | May 16, 19:55 UTC | 30m |
| 2026-05-16 | VTE055 | - | May 16, 17:10 UTC | May 16, 17:25 UTC | 15m |
| 2026-05-16 | VTE054 | - | May 16, 15:35 UTC | May 16, 15:50 UTC | 15m |
| 2026-05-16 | VTE053 | - | May 16, 14:11 UTC | May 16, 14:16 UTC | 5m |
| 2026-05-16 | VTE052 | - | May 16, 12:11 UTC | May 16, 12:55 UTC | 45m |
| 2026-05-15 | VTE8752 | - | May 15, 19:10 UTC | May 15, 21:50 UTC | 2h 40m |
| 2026-05-08 | VTE752 | IKK → PHL | May 8, 01:45 UTC | May 8, 02:39 UTC | 55m |
| 2026-05-07 | VTE752 | IKK → PHL | May 7, 20:35 UTC | May 7, 21:20 UTC | 45m |
| 2026-05-07 | VTE882 | MKE → GLE | May 7, 01:15 UTC | May 7, 03:35 UTC | 2h 20m |
| 2026-05-06 | VTE881 | HPN → FLL | May 6, 23:30 UTC | May 6, 23:40 UTC | 10m |
| 2026-05-04 | VTE752 | IKK → PHL | May 4, 14:45 UTC | May 4, 15:05 UTC | 20m |
| 2026-05-04 | VTE752 | IKK → PHL | May 4, 10:55 UTC | May 4, 13:30 UTC | 2h 35m |
| 2026-04-30 | VTE548 | PBI → HPN | Apr 30, 22:00 UTC | May 1, 00:55 UTC | 2h 55m |
| 2026-04-30 | VTE7548 | HPN → FRG | Apr 30, 18:40 UTC | Apr 30, 18:55 UTC | 15m |
| 2026-04-30 | VTE601 | FRG → OWB | Apr 30, 16:55 UTC | Apr 30, 17:55 UTC | 1h 0m |
| 2026-04-30 | VTE600 | MQY → INT | Apr 30, 15:15 UTC | Apr 30, 15:55 UTC | 40m |
| 2026-04-27 | VTE7752 | - | Apr 27, 02:05 UTC | Apr 27, 02:15 UTC | 10m |
| 2026-04-26 | VTE752 | IKK → PHL | Apr 26, 22:50 UTC | Apr 27, 01:00 UTC | 2h 10m |
| 2026-04-26 | VTE7752 | - | Apr 26, 18:10 UTC | Apr 26, 18:25 UTC | 15m |
| 2026-04-24 | VTE7752 | - | Apr 24, 21:00 UTC | Apr 24, 21:25 UTC | 25m |
| 2026-04-24 | VTE752 | IKK → PHL | Apr 24, 18:55 UTC | Apr 24, 19:15 UTC | 20m |
| 2026-04-24 | VTE752 | IKK → PHL | Apr 24, 17:10 UTC | Apr 24, 17:55 UTC | 45m |
| 2026-04-24 | VTE7752 | - | Apr 24, 15:20 UTC | Apr 24, 16:10 UTC | 50m |
| 2026-04-23 | VTE7752 | - | Apr 23, 19:55 UTC | Apr 23, 20:20 UTC | 25m |
| 2026-04-23 | VTE752 | IKK → PHL | Apr 23, 17:30 UTC | Apr 23, 19:15 UTC | 1h 44m |
| 2026-04-23 | VTE7752 | - | Apr 23, 14:10 UTC | Apr 23, 16:05 UTC | 1h 55m |
| 2026-04-23 | VTE7752 | - | Apr 23, 00:15 UTC | Apr 23, 00:45 UTC | 30m |
| 2026-04-22 | VTE752 | IKK → PHL | Apr 22, 19:10 UTC | Apr 22, 20:50 UTC | 1h 40m |
| 2026-04-22 | VTE752 | IKK → PHL | Apr 22, 17:30 UTC | Apr 22, 17:50 UTC | 20m |
| 2026-04-21 | VTE752 | - | Apr 21, 14:20 UTC | Apr 21, 16:31 UTC | 2h 10m |
| 2026-04-21 | VTE7752 | - | Apr 21, 11:20 UTC | Apr 21, 13:01 UTC | 1h 40m |
| 2026-04-20 | VTE922 | BNA → SNA | Apr 20, 03:55 UTC | Apr 20, 05:45 UTC | 1h 50m |
| 2026-04-19 | VTE921 | ORD → OWB | Apr 19, 16:45 UTC | Apr 19, 18:35 UTC | 1h 50m |
| 2026-04-18 | VTE920 | - | Apr 18, 17:30 UTC | Apr 18, 18:35 UTC | 1h 5m |
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 N752SP page for operator, model, and routing details .