sensors Mode-S transponder
A94DC7
ICAO 24-bit transponder address · allocated to United States
Currently assigned to N699ST · BOMBARDIER CL-600 Challenger · operated by ORANGE EQUIPMENT LLC
- Hex
- A94DC7
- Octal
- 52246707
- Decimal
- 11,095,495
- Country
- US
- Tail
- N699ST
- Type
- CL60
- Flights observed
- 75
- Distinct callsigns
- 2
- Country
- US
- Last broadcast
- 22h ago
Last known position
Country allocation
The ICAO 24-bit address A94DC7 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-20 | HPJ699 | TMB → FXE | Jul 20, 20:55 UTC | Jul 20, 21:15 UTC | 20m |
| 2026-07-20 | HPJ699 | - | Jul 20, 17:15 UTC | Jul 20, 20:00 UTC | 2h 45m |
| 2026-07-17 | HPJ699 | - | Jul 17, 15:44 UTC | Jul 17, 18:19 UTC | 2h 35m |
| 2026-07-17 | HPJ699 | - | Jul 17, 13:25 UTC | Jul 17, 13:45 UTC | 20m |
| 2026-07-16 | HPJ699 | - | Jul 16, 19:14 UTC | Jul 16, 19:40 UTC | 25m |
| 2026-07-16 | HPJ699 | - | Jul 16, 17:30 UTC | Jul 16, 17:54 UTC | 25m |
| 2026-07-15 | HPJ699 | - | Jul 15, 21:50 UTC | Jul 15, 23:15 UTC | 1h 25m |
| 2026-07-14 | HPJ699 | - | Jul 14, 20:05 UTC | Jul 14, 21:35 UTC | 1h 30m |
| 2026-07-13 | N699ST | - | Jul 13, 14:05 UTC | Jul 13, 14:40 UTC | 35m |
| 2026-07-13 | N699ST | - | Jul 13, 12:25 UTC | Jul 13, 12:45 UTC | 20m |
| 2026-07-10 | N699ST | - | Jul 10, 15:55 UTC | Jul 10, 16:30 UTC | 35m |
| 2026-07-10 | N699ST | - | Jul 10, 14:25 UTC | Jul 10, 14:45 UTC | 20m |
| 2026-07-08 | HPJ699 | - | Jul 8, 16:00 UTC | Jul 8, 16:35 UTC | 35m |
| 2026-07-08 | HPJ699 | - | Jul 8, 13:15 UTC | Jul 8, 14:55 UTC | 1h 40m |
| 2026-07-07 | HPJ699 | - | Jul 7, 23:30 UTC | Jul 8, 00:40 UTC | 1h 10m |
| 2026-07-07 | HPJ699 | TMB → YUL | Jul 7, 19:45 UTC | Jul 7, 22:45 UTC | 3h 0m |
| 2026-07-07 | HPJ699 | - | Jul 7, 18:15 UTC | Jul 7, 18:35 UTC | 20m |
| 2026-07-06 | N699ST | - | Jul 6, 14:00 UTC | Jul 6, 14:25 UTC | 25m |
| 2026-07-06 | N699ST | - | Jul 6, 11:40 UTC | Jul 6, 11:55 UTC | 15m |
| 2026-07-02 | N699ST | - | Jul 2, 18:35 UTC | Jul 2, 19:10 UTC | 35m |
| 2026-07-02 | N699ST | - | Jul 2, 17:15 UTC | Jul 2, 17:35 UTC | 20m |
| 2026-06-30 | HPJ699 | - | Jun 30, 12:35 UTC | Jun 30, 15:50 UTC | 3h 15m |
| 2026-06-21 | N699ST | - | Jun 21, 14:50 UTC | Jun 21, 15:15 UTC | 25m |
| 2026-06-21 | N699ST | - | Jun 21, 13:04 UTC | Jun 21, 13:20 UTC | 15m |
| 2026-06-18 | N699ST | - | Jun 18, 16:10 UTC | Jun 18, 16:35 UTC | 25m |
| 2026-06-18 | N699ST | - | Jun 18, 14:50 UTC | Jun 18, 15:10 UTC | 20m |
| 2026-06-15 | HPJ699 | - | Jun 15, 17:50 UTC | Jun 15, 18:29 UTC | 40m |
| 2026-06-15 | HPJ699 | - | Jun 15, 16:49 UTC | Jun 15, 17:25 UTC | 35m |
| 2026-06-15 | HPJ699 | - | Jun 15, 15:35 UTC | Jun 15, 15:45 UTC | 10m |
| 2026-06-07 | HPJ699 | OAK → FXE | Jun 7, 20:40 UTC | Jun 8, 01:40 UTC | 5h 0m |
| 2026-06-07 | HPJ699 | LAS → OAK | Jun 7, 16:20 UTC | Jun 7, 17:25 UTC | 1h 5m |
| 2026-06-04 | HPJ699 | - | Jun 4, 15:10 UTC | Jun 4, 19:50 UTC | 4h 40m |
| 2026-05-29 | HPJ699 | - | May 29, 21:20 UTC | May 29, 23:40 UTC | 2h 20m |
| 2026-05-27 | HPJ699 | - | May 27, 15:30 UTC | May 27, 17:40 UTC | 2h 10m |
| 2026-05-27 | HPJ699 | - | May 27, 14:20 UTC | May 27, 14:40 UTC | 20m |
| 2026-05-25 | HPJ699 | - | May 25, 16:50 UTC | May 25, 17:00 UTC | 10m |
| 2026-05-25 | N699ST | - | May 25, 14:10 UTC | May 25, 16:15 UTC | 2h 5m |
| 2026-05-23 | N699ST | - | May 23, 12:15 UTC | May 23, 14:15 UTC | 2h 0m |
| 2026-05-20 | N699ST | LAS → FXE | May 20, 17:30 UTC | May 20, 21:50 UTC | 4h 20m |
| 2026-05-16 | N699ST | - | May 16, 14:11 UTC | May 16, 19:05 UTC | 4h 55m |
| 2026-05-13 | HPJ699 | - | May 13, 06:45 UTC | May 13, 06:55 UTC | 10m |
| 2026-05-13 | HPJ699 | - | May 13, 03:05 UTC | May 13, 06:15 UTC | 3h 10m |
| 2026-05-12 | HPJ699 | - | May 12, 10:35 UTC | May 12, 14:10 UTC | 3h 35m |
| 2026-05-11 | HPJ699 | - | May 11, 21:00 UTC | May 11, 22:35 UTC | 1h 34m |
| 2026-05-11 | HPJ699 | SUA → TEB | May 11, 17:25 UTC | May 11, 19:40 UTC | 2h 15m |
| 2026-05-10 | HPJ699 | - | May 10, 22:25 UTC | May 10, 22:49 UTC | 25m |
| 2026-05-08 | HPJ699 | - | May 8, 20:15 UTC | May 8, 20:35 UTC | 20m |
| 2026-05-08 | HPJ699 | - | May 8, 17:45 UTC | May 8, 18:25 UTC | 40m |
| 2026-05-06 | HPJ699 | - | May 6, 12:55 UTC | May 6, 13:30 UTC | 35m |
| 2026-05-06 | HPJ699 | - | May 6, 11:45 UTC | May 6, 12:01 UTC | 15m |
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 N699ST page for operator, model, and routing details .