sensors Mode-S transponder
A95C06
ICAO 24-bit transponder address · allocated to United States
Currently assigned to N702AK · DASSAULT Falcon 2000 · operated by MATAPALO HOLDINGS LLC
- Hex
- A95C06
- Octal
- 52256006
- Decimal
- 11,099,142
- Country
- US
- Tail
- N702AK
- Type
- F2TH
- Flights observed
- 48
- Distinct callsigns
- 1
- Country
- US
- Last broadcast
- 1d ago
Last known position
Country allocation
The ICAO 24-bit address A95C06 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 |
|---|---|---|---|
| N702AK | - | 48 | 2026-07-13 |
Recent flights last 48
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-13 | N702AK | - | Jul 13, 15:15 UTC | Jul 13, 20:05 UTC | 4h 50m |
| 2026-07-13 | N702AK | - | Jul 13, 12:10 UTC | Jul 13, 13:50 UTC | 1h 40m |
| 2026-07-12 | N702AK | - | Jul 12, 18:55 UTC | Jul 12, 22:35 UTC | 3h 40m |
| 2026-07-12 | N702AK | - | Jul 12, 16:40 UTC | Jul 12, 17:30 UTC | 50m |
| 2026-07-07 | N702AK | BED → APC | Jul 7, 16:20 UTC | Jul 7, 22:10 UTC | 5h 50m |
| 2026-07-07 | N702AK | - | Jul 7, 14:40 UTC | Jul 7, 15:10 UTC | 30m |
| 2026-07-05 | N702AK | - | Jul 5, 18:40 UTC | Jul 5, 19:20 UTC | 40m |
| 2026-07-03 | N702AK | - | Jul 3, 12:20 UTC | Jul 3, 14:55 UTC | 2h 35m |
| 2026-07-02 | N702AK | - | Jul 2, 23:25 UTC | Jul 3, 01:15 UTC | 1h 50m |
| 2026-07-02 | N702AK | VNY → BNA | Jul 2, 18:25 UTC | Jul 2, 22:10 UTC | 3h 45m |
| 2026-07-02 | N702AK | - | Jul 2, 01:50 UTC | Jul 2, 02:30 UTC | 40m |
| 2026-06-28 | N702AK | - | Jun 28, 19:14 UTC | Jun 28, 22:49 UTC | 3h 35m |
| 2026-06-26 | N702AK | LAS → BNA | Jun 26, 19:30 UTC | Jun 26, 22:40 UTC | 3h 10m |
| 2026-06-26 | N702AK | - | Jun 26, 16:44 UTC | Jun 26, 18:29 UTC | 1h 45m |
| 2026-06-22 | N702AK | OAK → PDX | Jun 22, 03:35 UTC | Jun 22, 04:54 UTC | 1h 20m |
| 2026-06-20 | N702AK | - | Jun 20, 21:10 UTC | Jun 20, 22:25 UTC | 1h 15m |
| 2026-06-20 | N702AK | - | Jun 20, 17:34 UTC | Jun 20, 18:40 UTC | 1h 5m |
| 2026-06-19 | N702AK | - | Jun 19, 16:25 UTC | Jun 19, 19:14 UTC | 2h 50m |
| 2026-06-15 | N702AK | - | Jun 15, 16:55 UTC | Jun 15, 17:50 UTC | 55m |
| 2026-06-12 | N702AK | - | Jun 12, 13:00 UTC | Jun 12, 17:25 UTC | 4h 25m |
| 2026-06-12 | N702AK | - | Jun 12, 11:30 UTC | Jun 12, 12:00 UTC | 30m |
| 2026-06-07 | N702AK | - | Jun 7, 04:25 UTC | Jun 7, 08:35 UTC | 4h 10m |
| 2026-06-07 | N702AK | SJC → LAS | Jun 7, 02:14 UTC | Jun 7, 03:15 UTC | 1h 0m |
| 2026-06-05 | N702AK | - | Jun 5, 23:25 UTC | Jun 6, 00:20 UTC | 55m |
| 2026-06-05 | N702AK | - | Jun 5, 01:50 UTC | Jun 5, 05:35 UTC | 3h 45m |
| 2026-06-04 | N702AK | - | Jun 4, 01:50 UTC | Jun 4, 02:40 UTC | 50m |
| 2026-06-03 | N702AK | SJC → DTW | Jun 3, 01:25 UTC | Jun 3, 05:25 UTC | 4h 0m |
| 2026-06-02 | N702AK | VNY → SJC | Jun 2, 22:55 UTC | Jun 2, 23:45 UTC | 50m |
| 2026-06-01 | N702AK | - | Jun 1, 15:55 UTC | Jun 1, 21:10 UTC | 5h 15m |
| 2026-05-28 | N702AK | - | May 28, 19:35 UTC | May 28, 22:15 UTC | 2h 40m |
| 2026-05-26 | N702AK | - | May 26, 15:24 UTC | May 26, 17:55 UTC | 2h 30m |
| 2026-05-25 | N702AK | - | May 25, 19:50 UTC | May 25, 20:19 UTC | 30m |
| 2026-05-25 | N702AK | - | May 25, 17:15 UTC | May 25, 17:35 UTC | 20m |
| 2026-05-22 | N702AK | - | May 22, 18:15 UTC | May 22, 18:50 UTC | 35m |
| 2026-05-22 | N702AK | - | May 22, 16:50 UTC | May 22, 17:05 UTC | 15m |
| 2026-05-20 | N702AK | - | May 20, 03:15 UTC | May 20, 05:30 UTC | 2h 16m |
| 2026-05-19 | N702AK | OPF → TEB | May 19, 20:00 UTC | May 19, 22:35 UTC | 2h 35m |
| 2026-05-18 | N702AK | - | May 18, 18:00 UTC | May 18, 23:00 UTC | 4h 59m |
| 2026-05-18 | N702AK | - | May 18, 15:35 UTC | May 18, 16:15 UTC | 40m |
| 2026-05-14 | N702AK | - | May 14, 14:55 UTC | May 14, 20:25 UTC | 5h 30m |
| 2026-05-07 | N702AK | - | May 7, 16:45 UTC | May 7, 17:25 UTC | 40m |
| 2026-05-06 | N702AK | - | May 6, 16:20 UTC | May 6, 16:50 UTC | 30m |
| 2026-04-28 | N702AK | - | Apr 28, 18:15 UTC | Apr 28, 20:00 UTC | 1h 45m |
| 2026-04-26 | N702AK | - | Apr 26, 18:55 UTC | Apr 26, 20:35 UTC | 1h 40m |
| 2026-04-22 | N702AK | - | Apr 22, 19:10 UTC | Apr 22, 20:25 UTC | 1h 15m |
| 2026-04-21 | N702AK | - | Apr 21, 12:15 UTC | Apr 21, 13:35 UTC | 1h 20m |
| 2026-04-19 | N702AK | - | Apr 19, 15:40 UTC | Apr 19, 16:55 UTC | 1h 15m |
| 2026-04-16 | N702AK | - | Apr 16, 19:25 UTC | Apr 16, 20:45 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 N702AK page for operator, model, and routing details .