sensors Mode-S transponder
A9CC7A
ICAO 24-bit transponder address · allocated to United States
Currently assigned to N730QS · BOMBARDIER BD-100 Challenger 350 · operated by NETJETS SALES INC, EDWARDS LIFESCIENCES LLC, GREAT POINT ADVISORS II LLC, HLJM AIR LLC, YANG JACKSON, SWANK LLC
- Hex
- A9CC7A
- Octal
- 52346172
- Decimal
- 11,127,930
- Country
- US
- Tail
- N730QS
- Type
- CL35
- Flights observed
- 149
- Distinct callsigns
- 2
- Country
- US
- Last broadcast
- 2d ago
Last known position
Country allocation
The ICAO 24-bit address A9CC7A 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 2 distinct
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-11 | EJA730 | - | Jul 11, 16:25 UTC | Jul 11, 18:25 UTC | 2h 0m |
| 2026-07-11 | EJA730 | - | Jul 11, 14:45 UTC | Jul 11, 15:25 UTC | 40m |
| 2026-07-10 | EJA730 | - | Jul 10, 20:30 UTC | Jul 10, 22:55 UTC | 2h 25m |
| 2026-07-10 | EJA730 | - | Jul 10, 17:50 UTC | Jul 10, 19:30 UTC | 1h 40m |
| 2026-07-10 | EJA730 | - | Jul 10, 13:10 UTC | Jul 10, 14:25 UTC | 1h 15m |
| 2026-07-10 | EJA730 | - | Jul 10, 11:55 UTC | Jul 10, 12:20 UTC | 25m |
| 2026-07-09 | EJA730 | - | Jul 9, 21:10 UTC | Jul 9, 21:35 UTC | 25m |
| 2026-07-09 | EJA730 | SJC → AZO | Jul 9, 16:30 UTC | Jul 9, 19:55 UTC | 3h 25m |
| 2026-07-08 | EJA730 | SAN → SJC | Jul 8, 21:20 UTC | Jul 8, 22:20 UTC | 1h 0m |
| 2026-07-08 | EJA730 | - | Jul 8, 18:40 UTC | Jul 8, 19:20 UTC | 40m |
| 2026-07-08 | EJA730 | - | Jul 8, 17:00 UTC | Jul 8, 17:30 UTC | 30m |
| 2026-07-07 | EJA730 | - | Jul 7, 22:20 UTC | Jul 7, 22:45 UTC | 25m |
| 2026-07-07 | EJA730 | - | Jul 7, 20:20 UTC | Jul 7, 21:10 UTC | 50m |
| 2026-07-07 | EJA730 | - | Jul 7, 18:40 UTC | Jul 7, 19:05 UTC | 25m |
| 2026-07-07 | EJA730 | BFI → CLD | Jul 7, 03:30 UTC | Jul 7, 06:00 UTC | 2h 30m |
| 2026-07-06 | EJA730 | - | Jul 6, 19:20 UTC | Jul 6, 21:40 UTC | 2h 20m |
| 2026-07-06 | EJA730 | - | Jul 6, 15:40 UTC | Jul 6, 17:00 UTC | 1h 20m |
| 2026-07-05 | EJA730 | SJC → SLC | Jul 5, 19:55 UTC | Jul 5, 21:15 UTC | 1h 20m |
| 2026-07-05 | EJA730 | BUR → SJC | Jul 5, 18:10 UTC | Jul 5, 18:55 UTC | 45m |
| 2026-07-05 | EJA730 | BJC → BUR | Jul 5, 15:45 UTC | Jul 5, 17:40 UTC | 1h 55m |
| 2026-07-04 | EJA730 | - | Jul 4, 18:35 UTC | Jul 5, 14:40 UTC | 20h 5m |
| 2026-07-04 | EJA730 | - | Jul 4, 17:20 UTC | Jul 5, 14:40 UTC | 21h 20m |
| 2026-07-04 | EJA730 | - | Jul 4, 14:05 UTC | Jul 4, 14:45 UTC | 40m |
| 2026-07-03 | EJA730 | - | Jul 3, 22:20 UTC | Jul 4, 00:40 UTC | 2h 20m |
| 2026-07-03 | EJA730 | - | Jul 3, 17:45 UTC | Jul 3, 19:05 UTC | 1h 20m |
| 2026-07-03 | EJA730 | - | Jul 3, 15:20 UTC | Jul 3, 16:20 UTC | 1h 0m |
| 2026-07-03 | N730QS | - | Jul 3, 01:55 UTC | Jul 3, 02:35 UTC | 40m |
| 2026-07-01 | N730QS | - | Jul 1, 18:50 UTC | Jul 1, 19:25 UTC | 35m |
| 2026-07-01 | EJA730 | APA → SJC | Jul 1, 15:10 UTC | Jul 1, 17:25 UTC | 2h 15m |
| 2026-06-30 | EJA730 | - | Jun 30, 19:50 UTC | Jun 30, 20:10 UTC | 20m |
| 2026-06-30 | EJA730 | - | Jun 30, 14:30 UTC | Jun 30, 16:30 UTC | 2h 0m |
| 2026-06-29 | EJA730 | - | Jun 29, 20:35 UTC | Jun 29, 23:05 UTC | 2h 30m |
| 2026-06-29 | EJA730 | - | Jun 29, 17:10 UTC | Jun 29, 17:49 UTC | 40m |
| 2026-06-29 | EJA730 | - | Jun 29, 13:44 UTC | Jun 29, 16:00 UTC | 2h 15m |
| 2026-06-28 | EJA730 | - | Jun 28, 21:55 UTC | Jun 28, 22:15 UTC | 20m |
| 2026-06-28 | EJA730 | - | Jun 28, 18:14 UTC | Jun 28, 20:54 UTC | 2h 40m |
| 2026-06-28 | EJA730 | - | Jun 28, 15:24 UTC | Jun 28, 16:35 UTC | 1h 10m |
| 2026-06-27 | EJA730 | - | Jun 27, 21:10 UTC | Jun 28, 13:19 UTC | 16h 10m |
| 2026-06-27 | EJA730 | SBA → BUR | Jun 27, 18:54 UTC | Jun 27, 19:09 UTC | 15m |
| 2026-06-27 | EJA730 | SJC → SBA | Jun 27, 16:55 UTC | Jun 27, 17:34 UTC | 40m |
| 2026-06-25 | EJA730 | MCC → SJC | Jun 25, 00:35 UTC | Jun 25, 00:59 UTC | 25m |
| 2026-06-24 | EJA730 | - | Jun 24, 18:05 UTC | Jun 24, 23:10 UTC | 5h 5m |
| 2026-06-24 | EJA730 | - | Jun 24, 15:09 UTC | Jun 24, 16:05 UTC | 55m |
| 2026-06-23 | EJA730 | - | Jun 23, 21:14 UTC | Jun 23, 22:25 UTC | 1h 10m |
| 2026-06-20 | EJA730 | - | Jun 20, 15:14 UTC | Jun 20, 16:00 UTC | 45m |
| 2026-06-16 | EJA730 | - | Jun 16, 11:45 UTC | Jun 16, 12:25 UTC | 40m |
| 2026-06-11 | N730QS | - | Jun 11, 18:00 UTC | Jun 11, 19:00 UTC | 1h 0m |
| 2026-06-09 | EJA730 | SNA → MVY | Jun 9, 19:35 UTC | Jun 9, 21:25 UTC | 1h 50m |
| 2026-06-08 | EJA730 | SNA → MVY | Jun 8, 16:25 UTC | Jun 8, 18:25 UTC | 2h 0m |
| 2026-06-08 | EJA730 | SNA → MVY | Jun 8, 13:55 UTC | Jun 8, 15:45 UTC | 1h 50m |
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 N730QS page for operator, model, and routing details .