sensors Mode-S transponder

A9DBC7

ICAO 24-bit transponder address · allocated to United States

Currently assigned to N734VE · CESSNA 172 Skyhawk · operated by FLYBY AVIATION LLC

Hex
A9DBC7
Octal
52355707
Decimal
11,131,847
Country
US
Tail
N734VE
Type
C172
No current signal · last broadcast 1h ago
Flights observed
55
Distinct callsigns
1
Country
US
Last broadcast
1h ago

Last known position

Most recent position reported by Mode-S A9DBC7.

Country allocation

The ICAO 24-bit address A9DBC7 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
N734VE - 55 2026-05-30

Recent flights last 50

DateFlightRouteTakeoffLandingDuration
2026-05-30 N734VE LGU → LGU May 30, 14:30 UTCMay 30, 14:40 UTC10m
2026-05-29 N734VE - May 29, 17:20 UTCMay 29, 18:20 UTC1h 0m
2026-05-29 N734VE LGU → LGU May 29, 16:00 UTCMay 29, 16:20 UTC20m
2026-05-29 N734VE LGU → LGU May 29, 02:45 UTCMay 29, 03:20 UTC35m
2026-05-28 N734VE LGU → LGU May 28, 14:10 UTCMay 28, 15:05 UTC55m
2026-05-26 N734VE - May 26, 16:55 UTCMay 26, 17:44 UTC50m
2026-05-25 N734VE LGU → LGU May 25, 17:25 UTCMay 25, 18:20 UTC55m
2026-05-24 N734VE LGU → LGU May 24, 20:20 UTCMay 24, 21:10 UTC50m
2026-05-23 N734VE LGU → LGU May 23, 15:30 UTCMay 23, 16:15 UTC45m
2026-05-22 N734VE LGU → LGU May 22, 17:35 UTCMay 22, 18:10 UTC35m
2026-05-22 N734VE LGU → LGU May 22, 13:55 UTCMay 22, 14:55 UTC1h 0m
2026-05-21 N734VE LGU → LGU May 21, 22:15 UTCMay 21, 23:00 UTC45m
2026-05-20 N734VE LGU → LGU May 20, 14:50 UTCMay 20, 15:50 UTC1h 0m
2026-05-19 N734VE LGU → LGU May 19, 15:55 UTCMay 19, 18:15 UTC2h 20m
2026-05-18 N734VE LGU → LGU May 18, 15:25 UTCMay 18, 16:00 UTC35m
2026-05-16 N734VE LGU → LGU May 16, 14:20 UTCMay 16, 15:10 UTC50m
2026-05-15 N734VE LGU → LGU May 15, 20:55 UTCMay 15, 21:35 UTC40m
2026-05-15 N734VE LGU → LGU May 15, 15:50 UTCMay 15, 16:40 UTC50m
2026-05-13 N734VE LGU → LGU May 13, 15:05 UTCMay 13, 16:05 UTC1h 0m
2026-05-13 N734VE LGU → LGU May 13, 00:35 UTCMay 13, 01:25 UTC50m
2026-05-12 N734VE - May 12, 20:30 UTCMay 12, 21:25 UTC55m
2026-05-12 N734VE LGU → LGU May 12, 03:20 UTCMay 12, 04:25 UTC1h 5m
2026-05-11 N734VE LGU → LGU May 11, 18:20 UTCMay 11, 19:15 UTC55m
2026-05-11 N734VE LGU → LGU May 11, 15:30 UTCMay 11, 16:20 UTC50m
2026-05-10 N734VE LGU → LGU May 10, 15:49 UTCMay 10, 16:14 UTC25m
2026-05-09 N734VE - May 9, 20:55 UTCMay 9, 22:10 UTC1h 15m
2026-05-08 N734VE LGU → LGU May 8, 18:10 UTCMay 8, 19:25 UTC1h 15m
2026-05-07 N734VE LGU → LGU May 7, 22:35 UTCMay 7, 23:29 UTC55m
2026-05-07 N734VE LGU → LGU May 7, 14:50 UTCMay 7, 15:40 UTC50m
2026-05-07 N734VE LGU → LGU May 7, 02:30 UTCMay 7, 03:15 UTC45m
2026-05-04 N734VE LGU → LGU May 4, 18:20 UTCMay 4, 19:15 UTC56m
2026-05-03 N734VE - May 3, 16:45 UTCMay 3, 17:20 UTC35m
2026-05-02 N734VE - May 2, 19:45 UTCMay 2, 20:50 UTC1h 5m
2026-05-02 N734VE - May 2, 03:20 UTCMay 2, 04:35 UTC1h 15m
2026-05-02 N734VE - May 2, 01:45 UTCMay 2, 02:45 UTC1h 0m
2026-05-01 N734VE - May 1, 23:00 UTCMay 2, 00:45 UTC1h 45m
2026-05-01 N734VE LGU → LGU May 1, 15:40 UTCMay 1, 16:45 UTC1h 5m
2026-04-30 N734VE LGU → LGU Apr 30, 19:25 UTCApr 30, 20:20 UTC55m
2026-04-29 N734VE LGU → LGU Apr 29, 22:20 UTCApr 29, 22:55 UTC35m
2026-04-28 N734VE LGU → LGU Apr 28, 21:45 UTCApr 28, 22:20 UTC35m
2026-04-27 N734VE LGU → LGU Apr 27, 23:25 UTCApr 28, 00:10 UTC45m
2026-04-25 N734VE LGU → LGU Apr 25, 16:00 UTCApr 25, 16:45 UTC45m
2026-04-25 N734VE LGU → LGU Apr 25, 01:00 UTCApr 25, 01:35 UTC35m
2026-04-24 N734VE LGU → LGU Apr 24, 17:40 UTCApr 24, 18:30 UTC50m
2026-04-24 N734VE LGU → LGU Apr 24, 15:45 UTCApr 24, 16:20 UTC35m
2026-04-23 N734VE LGU → LGU Apr 23, 20:20 UTCApr 23, 21:10 UTC50m
2026-04-18 N734VE - Apr 18, 19:05 UTCApr 18, 20:25 UTC1h 20m
2026-04-18 N734VE LGU → LGU Apr 18, 15:25 UTCApr 18, 16:05 UTC40m
2026-04-17 N734VE - Apr 17, 17:45 UTCApr 17, 18:10 UTC25m
2026-04-15 N734VE - Apr 15, 01:15 UTCApr 15, 02:10 UTC55m

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

Mode-S A9DBC7 frequently asked

What is Mode-S code A9DBC7?
A9DBC7 is an ICAO 24-bit transponder address. Allocated to United States. Assigned to N734VE.
Where is Mode-S A9DBC7 registered?
Mode-S code A9DBC7 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 A9DBC7 broadcasting right now?
No active broadcast right now. Last signal was 1h ago.
Hex, octal, and decimal Mode-S codes: what's the difference?
The same 24-bit identifier expressed in different bases: hex A9DBC7, octal 52355707, decimal 11,131,847.
What flights does A9DBC7 operate?
Mode-S A9DBC7 has broadcast 1 distinct callsign, including N734VE.