sensors Mode-S transponder
A7C618
ICAO 24-bit transponder address · allocated to United States
Currently assigned to N60NF · EMBRAER EMB-505 Phenom 300 · operated by PKG AIR LLC
- Hex
- A7C618
- Octal
- 51743030
- Decimal
- 10,995,224
- Country
- US
- Tail
- N60NF
- Type
- E55P
- Flights observed
- 46
- Distinct callsigns
- 1
- Country
- US
- Last broadcast
- 11h ago
Last known position
Country allocation
The ICAO 24-bit address A7C618 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 |
|---|---|---|---|
| N60NF | - | 46 | 2026-06-25 |
Recent flights last 46
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-06-25 | N60NF | LAS → CLD | Jun 25, 18:59 UTC | Jun 25, 19:54 UTC | 55m |
| 2026-06-25 | N60NF | CLD → LAS | Jun 25, 16:29 UTC | Jun 25, 17:20 UTC | 50m |
| 2026-06-24 | N60NF | - | Jun 24, 19:49 UTC | Jun 24, 23:10 UTC | 3h 20m |
| 2026-06-24 | N60NF | - | Jun 24, 16:09 UTC | Jun 24, 18:50 UTC | 2h 40m |
| 2026-06-22 | N60NF | CLD → CLD | Jun 22, 16:40 UTC | Jun 22, 17:25 UTC | 45m |
| 2026-06-16 | N60NF | COS → CLD | Jun 16, 21:45 UTC | Jun 16, 23:40 UTC | 1h 55m |
| 2026-06-16 | N60NF | - | Jun 16, 19:10 UTC | Jun 16, 21:00 UTC | 1h 51m |
| 2026-06-15 | N60NF | - | Jun 15, 23:30 UTC | Jun 16, 00:05 UTC | 35m |
| 2026-06-15 | N60NF | - | Jun 15, 19:20 UTC | Jun 15, 22:35 UTC | 3h 15m |
| 2026-06-15 | N60NF | CLD → SBA | Jun 15, 16:24 UTC | Jun 15, 17:04 UTC | 40m |
| 2026-06-14 | N60NF | - | Jun 14, 16:20 UTC | Jun 14, 18:00 UTC | 1h 40m |
| 2026-06-14 | N60NF | - | Jun 14, 13:10 UTC | Jun 14, 14:35 UTC | 1h 25m |
| 2026-06-12 | N60NF | CLD → CLD | Jun 12, 16:15 UTC | Jun 12, 21:35 UTC | 5h 20m |
| 2026-06-08 | N60NF | - | Jun 8, 16:10 UTC | Jun 8, 18:05 UTC | 1h 55m |
| 2026-06-07 | N60NF | - | Jun 7, 20:40 UTC | Jun 8, 00:10 UTC | 3h 30m |
| 2026-06-07 | N60NF | - | Jun 7, 15:45 UTC | Jun 7, 19:25 UTC | 3h 40m |
| 2026-06-04 | N60NF | - | Jun 4, 20:05 UTC | Jun 4, 21:15 UTC | 1h 10m |
| 2026-06-04 | N60NF | CLD → OAK | Jun 4, 18:20 UTC | Jun 4, 19:30 UTC | 1h 10m |
| 2026-06-03 | N60NF | - | Jun 3, 19:00 UTC | Jun 3, 23:55 UTC | 4h 55m |
| 2026-05-22 | N60NF | - | May 22, 01:30 UTC | May 22, 03:50 UTC | 2h 20m |
| 2026-05-21 | N60NF | - | May 21, 23:00 UTC | May 22, 00:50 UTC | 1h 50m |
| 2026-05-18 | N60NF | - | May 18, 19:35 UTC | May 18, 21:40 UTC | 2h 5m |
| 2026-05-18 | N60NF | - | May 18, 16:20 UTC | May 18, 18:50 UTC | 2h 29m |
| 2026-05-16 | N60NF | - | May 16, 19:15 UTC | May 16, 20:15 UTC | 1h 0m |
| 2026-05-16 | N60NF | CLD → TUS | May 16, 17:40 UTC | May 16, 18:35 UTC | 55m |
| 2026-05-13 | N60NF | - | May 13, 20:50 UTC | May 13, 22:00 UTC | 1h 10m |
| 2026-05-13 | N60NF | BJC → MEV | May 13, 16:40 UTC | May 13, 18:35 UTC | 1h 55m |
| 2026-05-12 | N60NF | - | May 12, 16:25 UTC | May 12, 18:55 UTC | 2h 30m |
| 2026-05-11 | N60NF | - | May 11, 20:30 UTC | May 12, 18:55 UTC | 22h 25m |
| 2026-05-11 | N60NF | - | May 11, 17:50 UTC | May 11, 18:20 UTC | 30m |
| 2026-05-10 | N60NF | - | May 10, 19:40 UTC | May 10, 21:30 UTC | 1h 50m |
| 2026-05-10 | N60NF | - | May 10, 16:44 UTC | May 10, 17:55 UTC | 1h 10m |
| 2026-05-01 | N60NF | - | May 1, 15:20 UTC | May 1, 17:05 UTC | 1h 45m |
| 2026-04-30 | N60NF | - | Apr 30, 22:35 UTC | Apr 30, 23:40 UTC | 1h 5m |
| 2026-04-30 | N60NF | - | Apr 30, 19:05 UTC | Apr 30, 21:40 UTC | 2h 35m |
| 2026-04-30 | N60NF | - | Apr 30, 17:15 UTC | Apr 30, 17:30 UTC | 15m |
| 2026-04-27 | N60NF | - | Apr 27, 21:05 UTC | Apr 27, 23:30 UTC | 2h 25m |
| 2026-04-27 | N60NF | - | Apr 27, 18:05 UTC | Apr 27, 20:00 UTC | 1h 55m |
| 2026-04-27 | N60NF | - | Apr 27, 16:45 UTC | Apr 27, 17:05 UTC | 20m |
| 2026-04-27 | N60NF | - | Apr 27, 03:10 UTC | Apr 27, 05:00 UTC | 1h 50m |
| 2026-04-26 | N60NF | - | Apr 26, 23:40 UTC | Apr 27, 00:50 UTC | 1h 10m |
| 2026-04-24 | N60NF | - | Apr 24, 16:40 UTC | Apr 24, 18:30 UTC | 1h 50m |
| 2026-04-24 | N60NF | - | Apr 24, 15:20 UTC | Apr 24, 15:45 UTC | 25m |
| 2026-04-13 | N60NF | - | Apr 13, 23:30 UTC | Apr 13, 23:45 UTC | 15m |
| 2026-04-13 | N60NF | - | Apr 13, 19:50 UTC | Apr 13, 22:30 UTC | 2h 40m |
| 2026-04-13 | N60NF | - | Apr 13, 19:35 UTC | Apr 13, 19:45 UTC | 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 N60NF page for operator, model, and routing details .