sensors Mode-S transponder
ADDA5F
ICAO 24-bit transponder address · allocated to United States
Currently assigned to N992DC · BOMBARDIER BD-100 Challenger 300 · operated by JWJ LEASING LLC
- Hex
- ADDA5F
- Octal
- 53355137
- Decimal
- 11,393,631
- Country
- US
- Tail
- N992DC
- Type
- CL30
- Flights observed
- 67
- Distinct callsigns
- 1
- Country
- US
- Last broadcast
- 1d ago
Current position
Country allocation
The ICAO 24-bit address ADDA5F 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 |
|---|---|---|---|
| N992DC | - | 67 | 2026-07-26 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-26 | N992DC | - | Jul 26, 19:15 UTC | Jul 26, 20:50 UTC | 1h 35m |
| 2026-07-26 | N992DC | - | Jul 26, 13:50 UTC | Jul 26, 15:20 UTC | 1h 30m |
| 2026-07-25 | N992DC | - | Jul 25, 01:15 UTC | Jul 25, 04:00 UTC | 2h 45m |
| 2026-07-24 | N992DC | - | Jul 24, 23:10 UTC | Jul 25, 00:35 UTC | 1h 25m |
| 2026-07-24 | N992DC | - | Jul 24, 21:15 UTC | Jul 24, 22:35 UTC | 1h 20m |
| 2026-07-24 | N992DC | - | Jul 24, 18:25 UTC | Jul 24, 19:10 UTC | 45m |
| 2026-07-24 | N992DC | - | Jul 24, 15:45 UTC | Jul 24, 17:20 UTC | 1h 35m |
| 2026-07-24 | N992DC | - | Jul 24, 13:15 UTC | Jul 24, 14:40 UTC | 1h 25m |
| 2026-07-23 | N992DC | - | Jul 23, 13:50 UTC | Jul 23, 18:30 UTC | 4h 40m |
| 2026-07-19 | N992DC | - | Jul 19, 23:30 UTC | Jul 20, 02:30 UTC | 3h 0m |
| 2026-07-17 | N992DC | - | Jul 17, 20:55 UTC | Jul 17, 23:39 UTC | 2h 45m |
| 2026-07-16 | N992DC | - | Jul 16, 20:29 UTC | Jul 16, 22:55 UTC | 2h 25m |
| 2026-07-16 | N992DC | - | Jul 16, 16:35 UTC | Jul 16, 18:55 UTC | 2h 20m |
| 2026-07-04 | N992DC | - | Jul 4, 00:35 UTC | Jul 4, 02:05 UTC | 1h 30m |
| 2026-07-03 | N992DC | - | Jul 3, 21:55 UTC | Jul 3, 23:25 UTC | 1h 30m |
| 2026-07-01 | N992DC | - | Jul 1, 19:20 UTC | Jul 1, 20:50 UTC | 1h 30m |
| 2026-07-01 | N992DC | - | Jul 1, 15:15 UTC | Jul 1, 17:15 UTC | 2h 0m |
| 2026-06-29 | N992DC | - | Jun 29, 16:00 UTC | Jun 29, 17:24 UTC | 1h 25m |
| 2026-06-26 | N992DC | - | Jun 26, 19:24 UTC | Jun 26, 20:34 UTC | 1h 10m |
| 2026-06-24 | N992DC | - | Jun 24, 19:34 UTC | Jun 24, 22:49 UTC | 3h 15m |
| 2026-06-24 | N992DC | - | Jun 24, 12:44 UTC | Jun 24, 15:29 UTC | 2h 45m |
| 2026-06-15 | N992DC | - | Jun 15, 23:09 UTC | Jun 16, 02:40 UTC | 3h 30m |
| 2026-06-15 | N992DC | - | Jun 15, 19:25 UTC | Jun 15, 21:50 UTC | 2h 25m |
| 2026-06-14 | N992DC | - | Jun 14, 15:55 UTC | Jun 14, 18:40 UTC | 2h 45m |
| 2026-06-13 | N992DC | - | Jun 13, 18:05 UTC | Jun 13, 18:20 UTC | 15m |
| 2026-06-12 | N992DC | - | Jun 12, 18:20 UTC | Jun 12, 21:15 UTC | 2h 55m |
| 2026-06-10 | N992DC | - | Jun 10, 14:45 UTC | Jun 10, 16:15 UTC | 1h 30m |
| 2026-06-08 | N992DC | - | Jun 8, 15:10 UTC | Jun 8, 16:25 UTC | 1h 15m |
| 2026-06-08 | N992DC | - | Jun 8, 01:25 UTC | Jun 8, 03:00 UTC | 1h 35m |
| 2026-06-05 | N992DC | - | Jun 5, 20:35 UTC | Jun 5, 21:50 UTC | 1h 15m |
| 2026-06-04 | N992DC | - | Jun 4, 22:55 UTC | Jun 5, 00:30 UTC | 1h 35m |
| 2026-06-04 | N992DC | - | Jun 4, 21:05 UTC | Jun 4, 22:20 UTC | 1h 15m |
| 2026-05-26 | N992DC | - | May 26, 17:25 UTC | May 26, 19:10 UTC | 1h 45m |
| 2026-05-25 | N992DC | - | May 25, 14:55 UTC | May 25, 16:15 UTC | 1h 20m |
| 2026-05-12 | N992DC | - | May 12, 20:10 UTC | May 12, 21:30 UTC | 1h 20m |
| 2026-05-09 | N992DC | - | May 9, 21:45 UTC | May 10, 00:24 UTC | 2h 40m |
| 2026-05-09 | N992DC | - | May 9, 15:10 UTC | May 9, 15:25 UTC | 15m |
| 2026-05-05 | N992DC | - | May 5, 20:50 UTC | May 5, 21:20 UTC | 30m |
| 2026-05-05 | N992DC | - | May 5, 19:00 UTC | May 5, 20:45 UTC | 1h 45m |
| 2026-05-05 | N992DC | - | May 5, 03:15 UTC | May 5, 05:55 UTC | 2h 40m |
| 2026-05-02 | N992DC | TEB → DAL | May 2, 22:15 UTC | May 3, 01:25 UTC | 3h 10m |
| 2026-04-30 | N992DC | DAL → TEB | Apr 30, 20:30 UTC | Apr 30, 23:20 UTC | 2h 50m |
| 2026-04-30 | N992DC | - | Apr 30, 15:05 UTC | Apr 30, 18:30 UTC | 3h 25m |
| 2026-04-30 | N992DC | - | Apr 30, 03:05 UTC | Apr 30, 03:40 UTC | 35m |
| 2026-04-29 | N992DC | - | Apr 29, 22:00 UTC | Apr 29, 22:40 UTC | 40m |
| 2026-04-29 | N992DC | - | Apr 29, 17:01 UTC | Apr 29, 20:20 UTC | 3h 20m |
| 2026-04-28 | N992DC | - | Apr 28, 17:50 UTC | Apr 28, 20:00 UTC | 2h 10m |
| 2026-04-28 | N992DC | - | Apr 28, 12:00 UTC | Apr 28, 14:40 UTC | 2h 40m |
| 2026-04-26 | N992DC | - | Apr 26, 22:00 UTC | Apr 27, 00:05 UTC | 2h 5m |
| 2026-04-26 | N992DC | - | Apr 26, 01:20 UTC | Apr 26, 02:40 UTC | 1h 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 N992DC page for operator, model, and routing details .