sensors Mode-S transponder
A28C86
ICAO 24-bit transponder address · allocated to United States
Currently assigned to N2630M · CESSNA 172 Skyhawk · operated by MOCK AIR LLC
- Hex
- A28C86
- Octal
- 50506206
- Decimal
- 10,652,806
- Country
- US
- Tail
- N2630M
- Type
- C172
- Flights observed
- 61
- Distinct callsigns
- 1
- Country
- US
- Last broadcast
- 20d ago
Last known position
Country allocation
The ICAO 24-bit address A28C86 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 |
|---|---|---|---|
| N2630M | - | 60 | 2026-07-25 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-25 | N2630M | - | Jul 25, 13:50 UTC | Jul 25, 14:15 UTC | 25m |
| 2026-07-24 | N2630M | - | Jul 24, 23:25 UTC | Jul 24, 23:50 UTC | 25m |
| 2026-07-24 | N2630M | - | Jul 24, 21:40 UTC | Jul 24, 21:55 UTC | 15m |
| 2026-07-24 | N2630M | - | Jul 24, 20:40 UTC | Jul 24, 20:55 UTC | 15m |
| 2026-07-24 | N2630M | - | Jul 24, 09:30 UTC | Jul 24, 13:00 UTC | 3h 30m |
| 2026-07-23 | - | - | Jul 23, 20:40 UTC | Jul 23, 20:50 UTC | 10m |
| 2026-07-15 | N2630M | - | Jul 15, 22:15 UTC | Jul 15, 22:40 UTC | 25m |
| 2026-07-13 | N2630M | - | Jul 13, 21:15 UTC | Jul 13, 21:55 UTC | 40m |
| 2026-07-13 | N2630M | - | Jul 13, 17:20 UTC | Jul 13, 17:30 UTC | 10m |
| 2026-07-12 | N2630M | - | Jul 12, 18:45 UTC | Jul 12, 19:25 UTC | 40m |
| 2026-07-07 | N2630M | - | Jul 7, 20:10 UTC | Jul 7, 20:35 UTC | 25m |
| 2026-07-07 | N2630M | - | Jul 7, 04:20 UTC | Jul 7, 04:30 UTC | 10m |
| 2026-07-07 | N2630M | - | Jul 7, 03:05 UTC | Jul 7, 03:15 UTC | 10m |
| 2026-07-06 | N2630M | - | Jul 6, 21:45 UTC | Jul 6, 21:55 UTC | 10m |
| 2026-07-04 | N2630M | - | Jul 4, 14:20 UTC | Jul 4, 14:50 UTC | 30m |
| 2026-07-02 | N2630M | - | Jul 2, 19:10 UTC | Jul 2, 19:55 UTC | 45m |
| 2026-07-01 | N2630M | - | Jul 1, 19:35 UTC | Jul 1, 20:30 UTC | 55m |
| 2026-07-01 | N2630M | - | Jul 1, 14:55 UTC | Jul 1, 16:00 UTC | 1h 5m |
| 2026-06-30 | N2630M | - | Jun 30, 21:35 UTC | Jun 30, 22:30 UTC | 55m |
| 2026-06-29 | N2630M | - | Jun 29, 23:29 UTC | Jun 29, 23:39 UTC | 10m |
| 2026-06-29 | N2630M | - | Jun 29, 03:10 UTC | Jun 29, 04:04 UTC | 55m |
| 2026-06-27 | N2630M | - | Jun 27, 17:39 UTC | Jun 27, 18:29 UTC | 50m |
| 2026-06-24 | N2630M | - | Jun 24, 03:19 UTC | Jun 24, 04:00 UTC | 40m |
| 2026-06-22 | N2630M | - | Jun 22, 18:35 UTC | Jun 22, 19:34 UTC | 1h 0m |
| 2026-06-21 | N2630M | - | Jun 21, 20:45 UTC | Jun 21, 21:39 UTC | 55m |
| 2026-06-20 | N2630M | - | Jun 20, 00:09 UTC | Jun 20, 01:34 UTC | 1h 25m |
| 2026-06-19 | N2630M | - | Jun 19, 19:39 UTC | Jun 19, 20:29 UTC | 50m |
| 2026-06-12 | N2630M | - | Jun 12, 22:50 UTC | Jun 12, 23:25 UTC | 35m |
| 2026-06-06 | N2630M | - | Jun 6, 18:39 UTC | Jun 6, 19:14 UTC | 35m |
| 2026-06-05 | N2630M | - | Jun 5, 19:00 UTC | Jun 5, 19:10 UTC | 10m |
| 2026-06-05 | N2630M | - | Jun 5, 13:05 UTC | Jun 5, 13:15 UTC | 10m |
| 2026-05-30 | N2630M | - | May 30, 00:45 UTC | May 30, 01:00 UTC | 15m |
| 2026-05-29 | N2630M | - | May 29, 21:35 UTC | May 29, 22:00 UTC | 25m |
| 2026-05-28 | N2630M | - | May 28, 20:00 UTC | May 28, 21:00 UTC | 1h 0m |
| 2026-05-28 | N2630M | - | May 28, 13:50 UTC | May 28, 14:45 UTC | 55m |
| 2026-05-27 | N2630M | - | May 27, 22:00 UTC | May 27, 23:45 UTC | 1h 45m |
| 2026-05-27 | N2630M | - | May 27, 02:09 UTC | May 27, 03:04 UTC | 55m |
| 2026-05-26 | N2630M | - | May 26, 23:49 UTC | May 27, 00:25 UTC | 35m |
| 2026-05-26 | N2630M | - | May 26, 20:34 UTC | May 26, 23:05 UTC | 2h 30m |
| 2026-05-26 | N2630M | - | May 26, 14:35 UTC | May 26, 17:30 UTC | 2h 55m |
| 2026-05-26 | N2630M | - | May 26, 14:05 UTC | May 26, 14:30 UTC | 25m |
| 2026-05-25 | N2630M | - | May 25, 21:35 UTC | May 25, 23:35 UTC | 2h 0m |
| 2026-05-25 | N2630M | - | May 25, 12:50 UTC | May 25, 14:40 UTC | 1h 50m |
| 2026-05-21 | N2630M | - | May 21, 17:45 UTC | May 21, 18:45 UTC | 1h 0m |
| 2026-05-07 | N2630M | - | May 7, 13:55 UTC | May 7, 14:20 UTC | 25m |
| 2026-05-06 | N2630M | - | May 6, 12:20 UTC | May 6, 13:50 UTC | 1h 30m |
| 2026-05-04 | N2630M | - | May 4, 16:35 UTC | May 4, 18:05 UTC | 1h 30m |
| 2026-04-30 | N2630M | - | Apr 30, 22:20 UTC | Apr 30, 22:50 UTC | 30m |
| 2026-04-27 | N2630M | - | Apr 27, 12:05 UTC | Apr 27, 12:25 UTC | 20m |
| 2026-04-26 | N2630M | - | Apr 26, 23:05 UTC | Apr 26, 23:55 UTC | 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 N2630M page for operator, model, and routing details .