sensors Mode-S transponder
A9A092
ICAO 24-bit transponder address · allocated to United States
Currently assigned to N7195Q · CESSNA 172 Skyhawk · operated by PUGET SOUND FLYERS
- Hex
- A9A092
- Octal
- 52320222
- Decimal
- 11,116,690
- Country
- US
- Tail
- N7195Q
- Type
- C172
- Flights observed
- 54
- Distinct callsigns
- 1
- Country
- US
- Last broadcast
- Jul 24, 20:50 UTC
Last known position
Country allocation
The ICAO 24-bit address A9A092 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 |
|---|---|---|---|
| N7195Q | - | 54 | 2026-07-24 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-24 | N7195Q | - | Jul 24, 19:30 UTC | Jul 24, 20:50 UTC | 1h 20m |
| 2026-07-22 | N7195Q | - | Jul 22, 20:00 UTC | Jul 22, 21:40 UTC | 1h 40m |
| 2026-07-21 | N7195Q | - | Jul 21, 23:00 UTC | Jul 22, 00:00 UTC | 1h 0m |
| 2026-07-18 | N7195Q | - | Jul 18, 21:05 UTC | Jul 18, 21:30 UTC | 25m |
| 2026-07-18 | N7195Q | - | Jul 18, 17:45 UTC | Jul 18, 18:10 UTC | 25m |
| 2026-07-17 | N7195Q | PAE → PAE | Jul 17, 17:44 UTC | Jul 17, 18:55 UTC | 1h 10m |
| 2026-07-15 | N7195Q | - | Jul 15, 22:10 UTC | Jul 15, 22:50 UTC | 40m |
| 2026-07-14 | N7195Q | CLM → PAE | Jul 14, 02:40 UTC | Jul 14, 03:25 UTC | 45m |
| 2026-07-14 | N7195Q | PAE → CLM | Jul 14, 00:20 UTC | Jul 14, 01:55 UTC | 1h 35m |
| 2026-07-12 | N7195Q | PAE → PAE | Jul 12, 20:40 UTC | Jul 12, 21:05 UTC | 25m |
| 2026-07-06 | N7195Q | PAE → PAE | Jul 6, 21:40 UTC | Jul 6, 22:45 UTC | 1h 5m |
| 2026-07-06 | N7195Q | - | Jul 6, 01:45 UTC | Jul 6, 02:40 UTC | 55m |
| 2026-07-02 | N7195Q | - | Jul 2, 21:25 UTC | Jul 2, 23:00 UTC | 1h 35m |
| 2026-07-02 | N7195Q | - | Jul 2, 19:20 UTC | Jul 2, 20:50 UTC | 1h 30m |
| 2026-06-25 | N7195Q | PAE → PAE | Jun 25, 05:35 UTC | Jun 25, 07:34 UTC | 2h 0m |
| 2026-06-24 | N7195Q | - | Jun 24, 21:40 UTC | Jun 24, 22:10 UTC | 30m |
| 2026-06-24 | N7195Q | PAE → PAE | Jun 24, 00:25 UTC | Jun 24, 02:00 UTC | 1h 35m |
| 2026-06-23 | N7195Q | TWD → PAE | Jun 23, 23:14 UTC | Jun 23, 23:39 UTC | 25m |
| 2026-06-23 | N7195Q | PAE → TWD | Jun 23, 21:59 UTC | Jun 23, 22:25 UTC | 25m |
| 2026-06-19 | N7195Q | - | Jun 19, 19:39 UTC | Jun 19, 20:40 UTC | 1h 0m |
| 2026-06-19 | N7195Q | PAE → PAE | Jun 19, 00:14 UTC | Jun 19, 01:29 UTC | 1h 15m |
| 2026-06-14 | N7195Q | - | Jun 14, 21:30 UTC | Jun 14, 22:20 UTC | 50m |
| 2026-06-14 | N7195Q | - | Jun 14, 17:40 UTC | Jun 14, 18:25 UTC | 45m |
| 2026-06-12 | N7195Q | - | Jun 12, 20:35 UTC | Jun 12, 21:00 UTC | 25m |
| 2026-06-12 | N7195Q | - | Jun 12, 19:50 UTC | Jun 12, 20:05 UTC | 15m |
| 2026-06-12 | N7195Q | - | Jun 12, 06:15 UTC | Jun 12, 08:05 UTC | 1h 50m |
| 2026-06-11 | N7195Q | - | Jun 11, 19:45 UTC | Jun 11, 20:40 UTC | 55m |
| 2026-06-01 | N7195Q | - | Jun 1, 01:30 UTC | Jun 1, 02:00 UTC | 30m |
| 2026-05-31 | N7195Q | - | May 31, 21:45 UTC | May 31, 22:50 UTC | 1h 5m |
| 2026-05-22 | N7195Q | TTD → PAE | May 22, 22:10 UTC | May 22, 23:45 UTC | 1h 35m |
| 2026-05-22 | N7195Q | - | May 22, 20:00 UTC | May 22, 21:25 UTC | 1h 25m |
| 2026-05-21 | N7195Q | - | May 21, 02:40 UTC | May 21, 04:00 UTC | 1h 20m |
| 2026-05-19 | N7195Q | PAE → PAE | May 19, 22:30 UTC | May 19, 23:00 UTC | 30m |
| 2026-05-18 | N7195Q | PAE → PAE | May 18, 23:05 UTC | May 18, 23:50 UTC | 45m |
| 2026-05-18 | N7195Q | - | May 18, 00:35 UTC | May 18, 01:20 UTC | 45m |
| 2026-05-08 | N7195Q | PAE → PAE | May 8, 19:40 UTC | May 8, 20:10 UTC | 30m |
| 2026-05-03 | N7195Q | - | May 3, 21:24 UTC | May 3, 22:54 UTC | 1h 30m |
| 2026-05-01 | N7195Q | - | May 1, 19:50 UTC | May 1, 21:15 UTC | 1h 25m |
| 2026-05-01 | N7195Q | - | May 1, 17:35 UTC | May 1, 19:00 UTC | 1h 25m |
| 2026-04-30 | N7195Q | PAE → PAE | Apr 30, 19:45 UTC | Apr 30, 20:20 UTC | 35m |
| 2026-04-29 | N7195Q | - | Apr 29, 19:15 UTC | Apr 29, 20:20 UTC | 1h 5m |
| 2026-04-28 | N7195Q | - | Apr 28, 21:30 UTC | Apr 28, 22:45 UTC | 1h 15m |
| 2026-04-27 | N7195Q | PAE → PAE | Apr 27, 21:50 UTC | Apr 27, 23:55 UTC | 2h 5m |
| 2026-04-25 | N7195Q | - | Apr 25, 23:45 UTC | Apr 26, 00:25 UTC | 40m |
| 2026-04-24 | N7195Q | - | Apr 24, 18:00 UTC | Apr 24, 19:05 UTC | 1h 5m |
| 2026-04-23 | N7195Q | PAE → PAE | Apr 23, 21:25 UTC | Apr 23, 22:15 UTC | 50m |
| 2026-04-21 | N7195Q | - | Apr 21, 21:55 UTC | Apr 21, 22:45 UTC | 50m |
| 2026-04-21 | N7195Q | - | Apr 21, 20:20 UTC | Apr 21, 20:50 UTC | 30m |
| 2026-04-21 | N7195Q | - | Apr 21, 19:25 UTC | Apr 21, 19:40 UTC | 15m |
| 2026-04-20 | N7195Q | - | Apr 20, 22:00 UTC | Apr 20, 22:40 UTC | 40m |
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 N7195Q page for operator, model, and routing details .