sensors Mode-S transponder
A80546
ICAO 24-bit transponder address · allocated to United States
Currently assigned to N616CM · SOCATA TBM-700A/B/C · operated by EIRECORP CORPORATE AVIATION INC TRUSTEE
- Hex
- A80546
- Octal
- 52002506
- Decimal
- 11,011,398
- Country
- US
- Tail
- N616CM
- Type
- TBM7
- Flights observed
- 48
- Distinct callsigns
- 1
- Country
- US
- Last broadcast
- 2d ago
Last known position
Country allocation
The ICAO 24-bit address A80546 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 |
|---|---|---|---|
| N616CM | - | 48 | 2026-07-16 |
Recent flights last 48
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-16 | N616CM | - | Jul 16, 10:45 UTC | Jul 16, 12:20 UTC | 1h 35m |
| 2026-07-15 | N616CM | - | Jul 15, 10:20 UTC | Jul 15, 12:10 UTC | 1h 50m |
| 2026-07-12 | N616CM | - | Jul 12, 12:40 UTC | Jul 12, 15:20 UTC | 2h 40m |
| 2026-07-10 | N616CM | - | Jul 10, 08:10 UTC | Jul 10, 11:05 UTC | 2h 55m |
| 2026-07-06 | N616CM | - | Jul 6, 10:20 UTC | Jul 6, 11:30 UTC | 1h 10m |
| 2026-07-04 | N616CM | - | Jul 4, 14:45 UTC | Jul 4, 15:40 UTC | 55m |
| 2026-07-02 | N616CM | - | Jul 2, 18:10 UTC | Jul 2, 18:55 UTC | 45m |
| 2026-07-02 | N616CM | - | Jul 2, 07:25 UTC | Jul 2, 08:15 UTC | 50m |
| 2026-06-28 | N616CM | BQH → BFS | Jun 28, 12:25 UTC | Jun 28, 13:49 UTC | 1h 25m |
| 2026-06-26 | N616CM | - | Jun 26, 09:20 UTC | Jun 26, 10:55 UTC | 1h 35m |
| 2026-06-21 | N616CM | - | Jun 21, 15:30 UTC | Jun 21, 16:44 UTC | 1h 15m |
| 2026-06-21 | N616CM | - | Jun 21, 11:34 UTC | Jun 21, 12:49 UTC | 1h 15m |
| 2026-06-20 | N616CM | LPL → BFS | Jun 20, 16:59 UTC | Jun 20, 17:39 UTC | 40m |
| 2026-06-20 | N616CM | - | Jun 20, 13:34 UTC | Jun 20, 14:19 UTC | 45m |
| 2026-06-20 | N616CM | - | Jun 20, 10:25 UTC | Jun 20, 11:34 UTC | 1h 10m |
| 2026-06-19 | N616CM | - | Jun 19, 18:25 UTC | Jun 19, 19:19 UTC | 55m |
| 2026-06-19 | N616CM | - | Jun 19, 17:49 UTC | Jun 19, 17:59 UTC | 10m |
| 2026-06-19 | N616CM | - | Jun 19, 16:29 UTC | Jun 19, 17:29 UTC | 1h 0m |
| 2026-06-19 | N616CM | BFS → BFS | Jun 19, 09:59 UTC | Jun 19, 11:30 UTC | 1h 30m |
| 2026-06-18 | N616CM | - | Jun 18, 13:20 UTC | Jun 18, 16:50 UTC | 3h 30m |
| 2026-06-17 | N616CM | - | Jun 17, 14:45 UTC | Jun 17, 16:15 UTC | 1h 30m |
| 2026-06-16 | N616CM | - | Jun 16, 12:25 UTC | Jun 16, 16:00 UTC | 3h 35m |
| 2026-05-18 | N616CM | - | May 18, 08:01 UTC | May 18, 09:40 UTC | 1h 40m |
| 2026-05-12 | N616CM | - | May 12, 08:30 UTC | May 12, 12:00 UTC | 3h 30m |
| 2026-05-10 | N616CM | - | May 10, 14:20 UTC | May 10, 16:59 UTC | 2h 40m |
| 2026-05-06 | N616CM | - | May 6, 16:35 UTC | May 6, 17:15 UTC | 40m |
| 2026-05-05 | N616CM | - | May 5, 07:10 UTC | May 5, 07:50 UTC | 40m |
| 2026-05-04 | N616CM | - | May 4, 14:10 UTC | May 4, 17:00 UTC | 2h 50m |
| 2026-05-03 | N616CM | - | May 3, 14:25 UTC | May 3, 17:10 UTC | 2h 45m |
| 2026-04-30 | N616CM | - | Apr 30, 16:50 UTC | Apr 30, 17:25 UTC | 35m |
| 2026-04-30 | N616CM | - | Apr 30, 13:10 UTC | Apr 30, 13:40 UTC | 30m |
| 2026-04-30 | N616CM | - | Apr 30, 07:15 UTC | Apr 30, 07:55 UTC | 40m |
| 2026-04-24 | N616CM | FDH → BFS | Apr 24, 18:10 UTC | Apr 24, 21:00 UTC | 2h 50m |
| 2026-04-24 | N616CM | BFS → FDH | Apr 24, 08:05 UTC | Apr 24, 10:50 UTC | 2h 45m |
| 2026-04-18 | N616CM | - | Apr 18, 18:05 UTC | Apr 18, 19:50 UTC | 1h 45m |
| 2026-04-18 | N616CM | - | Apr 18, 11:30 UTC | Apr 18, 12:00 UTC | 30m |
| 2026-04-18 | N616CM | - | Apr 18, 09:20 UTC | Apr 18, 10:25 UTC | 1h 5m |
| 2026-04-17 | N616CM | - | Apr 17, 19:25 UTC | Apr 17, 20:05 UTC | 40m |
| 2026-04-17 | N616CM | - | Apr 17, 18:55 UTC | Apr 17, 19:20 UTC | 25m |
| 2026-04-16 | N616CM | - | Apr 16, 17:15 UTC | Apr 16, 18:50 UTC | 1h 35m |
| 2026-04-16 | N616CM | - | Apr 16, 16:40 UTC | Apr 16, 17:10 UTC | 30m |
| 2026-04-15 | N616CM | - | Apr 15, 08:01 UTC | Apr 15, 08:35 UTC | 35m |
| 2026-04-14 | N616CM | - | Apr 14, 20:55 UTC | Apr 14, 21:50 UTC | 55m |
| 2026-04-14 | N616CM | - | Apr 14, 20:10 UTC | Apr 14, 20:50 UTC | 40m |
| 2026-04-14 | N616CM | - | Apr 14, 09:40 UTC | Apr 14, 10:45 UTC | 1h 5m |
| 2026-04-13 | N616CM | - | Apr 13, 14:25 UTC | Apr 13, 15:00 UTC | 35m |
| 2026-04-13 | N616CM | - | Apr 13, 07:20 UTC | Apr 13, 07:50 UTC | 30m |
| 2026-04-12 | N616CM | HYC → BFS | Apr 12, 17:20 UTC | Apr 12, 18:30 UTC | 1h 10m |
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 N616CM page for operator, model, and routing details .