Apparatus

Try JFK, AAL1290, BAW, or N225AN.

sensors Mode-S transponder

A7DBD2

ICAO 24-bit transponder address · allocated to United States

Currently assigned to N605WM · CESSNA 172 Skyhawk · operated by ZWL CONSULTING LLC

Hex
A7DBD2
Octal
51755722
Decimal
11,000,786
Country
US
Tail
N605WM
Type
C172
No current signal · last broadcast 2d ago
Flights observed
70
Distinct callsigns
1
Country
US
Last broadcast
2d ago

Last known position

Most recent position reported by Mode-S A7DBD2.

Country allocation

The ICAO 24-bit address A7DBD2 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
N605WM - 70 2026-05-28

Recent flights last 50

DateFlightRouteTakeoffLandingDuration
2026-05-28 N605WM SQL → SQL May 28, 00:30 UTCMay 28, 01:30 UTC1h 0m
2026-05-27 N605WM SJC → SQL May 27, 18:45 UTCMay 27, 19:00 UTC15m
2026-05-27 N605WM SQL → RHV May 27, 17:55 UTCMay 27, 18:20 UTC25m
2026-05-24 N605WM SQL → SQL May 24, 20:30 UTCMay 24, 21:45 UTC1h 15m
2026-05-23 N605WM SQL → SQL May 23, 16:05 UTCMay 23, 18:35 UTC2h 31m
2026-05-22 N605WM SQL → SQL May 22, 18:40 UTCMay 22, 19:55 UTC1h 15m
2026-05-21 N605WM SQL → SQL May 21, 18:00 UTCMay 21, 19:20 UTC1h 20m
2026-05-20 N605WM SQL → SQL May 20, 19:15 UTCMay 20, 20:05 UTC50m
2026-05-20 N605WM - May 20, 06:20 UTCMay 20, 07:10 UTC50m
2026-05-20 N605WM SQL → MHR May 20, 05:05 UTCMay 20, 06:05 UTC1h 0m
2026-05-19 N605WM SQL → SQL May 19, 20:50 UTCMay 19, 23:05 UTC2h 15m
2026-05-16 N605WM - May 16, 02:05 UTCMay 16, 02:40 UTC35m
2026-05-15 N605WM - May 15, 23:40 UTCMay 16, 00:00 UTC20m
2026-05-15 N605WM - May 15, 21:25 UTCMay 15, 22:25 UTC1h 0m
2026-05-15 N605WM SQL → SQL May 15, 00:00 UTCMay 15, 00:45 UTC45m
2026-05-14 N605WM PAO → SQL May 14, 22:40 UTCMay 14, 22:45 UTC5m
2026-05-13 N605WM SQL → PAO May 13, 18:25 UTCMay 13, 18:35 UTC10m
2026-05-09 N605WM SQL → SQL May 9, 18:55 UTCMay 9, 20:25 UTC1h 30m
2026-05-08 N605WM - May 8, 20:45 UTCMay 8, 21:15 UTC30m
2026-05-08 N605WM - May 8, 18:55 UTCMay 8, 20:10 UTC1h 15m
2026-05-08 N605WM - May 8, 00:25 UTCMay 8, 01:49 UTC1h 25m
2026-05-07 N605WM SQL → SBP May 7, 22:00 UTCMay 7, 23:24 UTC1h 24m
2026-05-06 N605WM SQL → SQL May 6, 21:30 UTCMay 6, 22:10 UTC40m
2026-05-05 N605WM SQL → SQL May 5, 22:01 UTCMay 5, 22:10 UTC10m
2026-05-05 N605WM SQL → SQL May 5, 03:50 UTCMay 5, 04:35 UTC45m
2026-05-03 N605WM - May 3, 22:54 UTCMay 4, 00:19 UTC1h 25m
2026-05-03 N605WM - May 3, 21:54 UTCMay 3, 22:45 UTC50m
2026-05-01 N605WM SQL → SQL May 1, 20:10 UTCMay 1, 21:55 UTC1h 45m
2026-04-30 N605WM - Apr 30, 22:30 UTCApr 30, 22:40 UTC10m
2026-04-30 N605WM - Apr 30, 22:15 UTCApr 30, 22:25 UTC10m
2026-04-30 N605WM SQL → PAO Apr 30, 21:25 UTCApr 30, 22:05 UTC40m
2026-04-30 N605WM SQL → SQL Apr 30, 19:40 UTCApr 30, 20:00 UTC20m
2026-04-30 N605WM SQL → SQL Apr 30, 19:25 UTCApr 30, 19:35 UTC10m
2026-04-30 N605WM SQL → SQL Apr 30, 19:00 UTCApr 30, 19:10 UTC10m
2026-04-29 N605WM PAO → SQL Apr 29, 18:15 UTCApr 29, 18:20 UTC5m
2026-04-29 N605WM SQL → PAO Apr 29, 14:30 UTCApr 29, 14:40 UTC10m
2026-04-28 N605WM - Apr 28, 23:00 UTCApr 29, 00:10 UTC1h 10m
2026-04-28 N605WM - Apr 28, 22:10 UTCApr 28, 22:40 UTC30m
2026-04-27 N605WM - Apr 27, 20:45 UTCApr 27, 20:55 UTC10m
2026-04-27 N605WM SQL → PAO Apr 27, 20:00 UTCApr 27, 20:20 UTC20m
2026-04-24 N605WM - Apr 24, 00:15 UTCApr 24, 00:40 UTC25m
2026-04-23 N605WM - Apr 23, 23:35 UTCApr 24, 00:05 UTC30m
2026-04-23 N605WM SQL → SQL Apr 23, 23:20 UTCApr 23, 23:25 UTC5m
2026-04-23 N605WM - Apr 23, 20:15 UTCApr 23, 20:20 UTC5m
2026-04-23 N605WM SQL → PAO Apr 23, 19:20 UTCApr 23, 19:55 UTC35m
2026-04-23 N605WM SQL → SQL Apr 23, 19:00 UTCApr 23, 19:05 UTC5m
2026-04-22 N605WM SQL → SQL Apr 22, 21:25 UTCApr 23, 00:00 UTC2h 35m
2026-04-20 N605WM SQL → SQL Apr 20, 19:10 UTCApr 20, 19:15 UTC5m
2026-04-20 N605WM SQL → SQL Apr 20, 03:05 UTCApr 20, 03:20 UTC15m
2026-04-20 N605WM SQL → SQL Apr 20, 02:45 UTCApr 20, 02:55 UTC10m

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 N605WM page for operator, model, and routing details .

Mode-S A7DBD2 frequently asked

What is Mode-S code A7DBD2?
A7DBD2 is an ICAO 24-bit transponder address. Allocated to United States. Assigned to N605WM.
Where is Mode-S A7DBD2 registered?
Mode-S code A7DBD2 is allocated to United States (US). All aircraft registered there receive a Mode-S address from a fixed block defined by ICAO Annex 10.
Is A7DBD2 broadcasting right now?
No active broadcast right now. Last signal was 2d ago.
Hex, octal, and decimal Mode-S codes: what's the difference?
The same 24-bit identifier expressed in different bases: hex A7DBD2, octal 51755722, decimal 11,000,786.
What flights does A7DBD2 operate?
Mode-S A7DBD2 has broadcast 1 distinct callsign, including N605WM.