sensors Mode-S transponder

AB3D14

ICAO 24-bit transponder address · allocated to United States

Currently assigned to N823MA · CESSNA 208 Caravan · operated by TVPX AIRCRAFT SOLUTIONS INC TRUSTEE

Hex
AB3D14
Octal
52636424
Decimal
11,222,292
Country
US
Tail
N823MA
Type
C208
No current signal · last broadcast 1d ago
Flights observed
118
Distinct callsigns
9
Country
US
Last broadcast
1d ago

Last known position

Most recent position reported by Mode-S AB3D14.

Country allocation

The ICAO 24-bit address AB3D14 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 9 distinct

Recent flights last 50

DateFlightRouteTakeoffLandingDuration
2026-05-28 FDY806 LAX → IPL May 28, 23:35 UTCMay 29, 00:30 UTC55m
2026-05-28 FDY805 IPL → LAX May 28, 21:55 UTCMay 28, 22:45 UTC50m
2026-05-28 FDY810 PHX → IPL May 28, 18:55 UTCMay 28, 19:50 UTC55m
2026-05-28 FDY809 IPL → PHX May 28, 17:25 UTCMay 28, 18:15 UTC50m
2026-05-28 FDY802 LAX → IPL May 28, 15:00 UTCMay 28, 15:55 UTC55m
2026-05-28 FDY801 IPL → LAX May 28, 13:30 UTCMay 28, 14:25 UTC55m
2026-05-28 FDY808 LAX → IPL May 28, 03:20 UTCMay 28, 04:10 UTC50m
2026-05-28 FDY807 IPL → LAX May 28, 01:45 UTCMay 28, 02:40 UTC55m
2026-05-27 FDY806 LAX → IPL May 27, 23:40 UTCMay 28, 00:30 UTC50m
2026-05-27 FDY805 IPL → LAX May 27, 21:50 UTCMay 27, 22:40 UTC50m
2026-05-27 FDY810 PHX → IPL May 27, 19:10 UTCMay 27, 20:05 UTC55m
2026-05-27 FDY809 IPL → PHX May 27, 17:30 UTCMay 27, 18:25 UTC55m
2026-05-27 FDY802 LAX → IPL May 27, 15:10 UTCMay 27, 16:00 UTC50m
2026-05-27 FDY801 IPL → LAX May 27, 13:25 UTCMay 27, 14:25 UTC1h 0m
2026-05-27 FDY808 LAX → IPL May 27, 03:39 UTCMay 27, 04:30 UTC50m
2026-05-27 FDY807 IPL → LAX May 27, 01:59 UTCMay 27, 02:54 UTC55m
2026-05-26 FDY810 PHX → IPL May 26, 19:30 UTCMay 26, 20:24 UTC55m
2026-05-26 FDY809 IPL → PHX May 26, 17:30 UTCMay 26, 18:19 UTC50m
2026-05-26 FDY802 LAX → IPL May 26, 15:09 UTCMay 26, 16:00 UTC50m
2026-05-26 FDY801 IPL → LAX May 26, 13:19 UTCMay 26, 14:20 UTC1h 0m
2026-05-26 FDY807 IPL → LAX May 26, 01:44 UTCMay 26, 03:55 UTC2h 10m
2026-05-25 FDY805 IPL → LAX May 25, 21:54 UTCMay 26, 00:04 UTC2h 10m
2026-05-25 FDY810 PHX → IPL May 25, 19:20 UTCMay 25, 20:09 UTC50m
2026-05-25 FDY809 IPL → PHX May 25, 17:25 UTCMay 25, 18:15 UTC50m
2026-05-25 FDY802 LAX → IPL May 25, 15:00 UTCMay 25, 15:50 UTC50m
2026-05-25 FDY801 IPL → LAX May 25, 13:25 UTCMay 25, 14:15 UTC50m
2026-05-25 FDY807 IPL → LAX May 25, 01:55 UTCMay 25, 04:00 UTC2h 5m
2026-05-24 FDY806 LAX → IPL May 24, 23:35 UTCMay 24, 23:46 UTC11m
2026-05-24 FDY810 PHX → IPL May 24, 19:30 UTCMay 24, 20:15 UTC45m
2026-05-24 FDY809 IPL → PHX May 24, 17:30 UTCMay 24, 18:30 UTC1h 0m
2026-05-23 FDY810 PHX → IPL May 23, 21:55 UTCMay 23, 22:45 UTC50m
2026-05-23 FDY809 IPL → PHX May 23, 19:45 UTCMay 23, 20:40 UTC55m
2026-05-23 FDY802 LAX → IPL May 23, 17:30 UTCMay 23, 18:25 UTC55m
2026-05-23 FDY801 IPL → LAX May 23, 15:45 UTCMay 23, 16:40 UTC55m
2026-05-10 FDY8071 LNS → DUJ May 10, 22:09 UTCMay 10, 23:05 UTC55m
2026-05-07 FDY805 IPL → LAX May 7, 21:50 UTCMay 7, 22:45 UTC55m
2026-05-07 FDY810 PHX → IPL May 7, 19:30 UTCMay 7, 20:15 UTC45m
2026-05-07 FDY809 IPL → PHX May 7, 17:20 UTCMay 7, 18:10 UTC50m
2026-05-07 FDY802 LAX → IPL May 7, 15:00 UTCMay 7, 15:55 UTC55m
2026-05-07 FDY801 IPL → LAX May 7, 13:25 UTCMay 7, 14:15 UTC50m
2026-05-07 FDY808 LAX → IPL May 7, 01:55 UTCMay 7, 04:00 UTC2h 5m
2026-05-06 FDY806 LAX → IPL May 6, 23:15 UTCMay 7, 00:10 UTC55m
2026-05-06 FDY805 IPL → LAX May 6, 21:50 UTCMay 6, 22:40 UTC50m
2026-05-06 FDY810 PHX → IPL May 6, 19:30 UTCMay 6, 20:10 UTC40m
2026-05-06 FDY809 IPL → PHX May 6, 18:35 UTCMay 6, 19:10 UTC35m
2026-05-06 FDY802 LAX → IPL May 6, 15:00 UTCMay 6, 15:50 UTC50m
2026-05-06 FDY801 IPL → LAX May 6, 13:30 UTCMay 6, 14:20 UTC50m
2026-05-06 FDY808 LAX → IPL May 6, 03:20 UTCMay 6, 04:10 UTC50m
2026-05-06 FDY807 IPL → LAX May 6, 01:55 UTCMay 6, 02:45 UTC50m
2026-05-05 FDY810 PHX → IPL May 5, 19:30 UTCMay 5, 20:15 UTC45m

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

Mode-S AB3D14 frequently asked

What is Mode-S code AB3D14?
AB3D14 is an ICAO 24-bit transponder address. Allocated to United States. Assigned to N823MA.
Where is Mode-S AB3D14 registered?
Mode-S code AB3D14 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 AB3D14 broadcasting right now?
No active broadcast right now. Last signal was 1d ago.
Hex, octal, and decimal Mode-S codes: what's the difference?
The same 24-bit identifier expressed in different bases: hex AB3D14, octal 52636424, decimal 11,222,292.
What flights does AB3D14 operate?
Mode-S AB3D14 has broadcast 9 distinct callsigns, including FDY810, FDY809, FDY802, FDY801, FDY808.