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