sensors Mode-S transponder

A3DB93

ICAO 24-bit transponder address · allocated to United States

Currently assigned to N348FR · AIRBUS A-320neo · operated by BANK OF UTAH TRUSTEE

Hex
A3DB93
Octal
50755623
Decimal
10,738,579
Country
US
Tail
N348FR
Type
A20N
No current signal · last broadcast 8d ago
Flights observed
60
Distinct callsigns
20
Country
US
Last broadcast
8d ago

Last known position

Most recent position reported by Mode-S A3DB93.

Country allocation

The ICAO 24-bit address A3DB93 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 20 distinct

Recent flights last 50

DateFlightRouteTakeoffLandingDuration
2026-05-21 FFT9048 LAS → GYR May 21, 19:20 UTCMay 21, 19:50 UTC30m
2026-05-21 FFT9048 LAS → GYR May 21, 19:13 UTCMay 21, 19:40 UTC27m
2026-04-24 FFT9048 LAS → GYR Apr 24, 18:10 UTCApr 24, 19:40 UTC1h 30m
2026-04-22 FFT4919 MCO → DEN Apr 22, 16:20 UTCApr 22, 19:45 UTC3h 25m
2026-04-22 FFT4919 MCO → DEN Apr 22, 16:21 UTCApr 22, 19:44 UTC3h 23m
2026-04-21 FFT2769 BDL → MCO Apr 21, 00:55 UTCApr 21, 03:15 UTC2h 20m
2026-04-21 FFT2769 BDL → MCO Apr 21, 01:03 UTCApr 21, 03:14 UTC2h 11m
2026-04-20 FFT1684 MCO → BDL Apr 20, 21:24 UTCApr 20, 23:42 UTC2h 18m
2026-04-20 FFT1684 MCO → BDL Apr 20, 21:25 UTCApr 20, 23:45 UTC2h 20m
2026-04-20 FFT4286 DTW → MCO Apr 20, 18:00 UTCApr 20, 20:00 UTC2h 0m
2026-04-20 FFT4937 RDU → DTW Apr 20, 15:20 UTCApr 20, 16:45 UTC1h 25m
2026-04-20 FFT1040 MCO → RDU Apr 20, 12:30 UTCApr 20, 13:55 UTC1h 25m
2026-04-20 FFT1040 MCO → RDU Apr 20, 12:26 UTCApr 20, 13:48 UTC1h 22m
2026-04-20 FFT1086 PHX → MCO Apr 20, 07:30 UTCApr 20, 11:00 UTC3h 30m
2026-04-20 FFT1192 SFO → PHX Apr 20, 02:25 UTCApr 20, 04:00 UTC1h 35m
2026-04-19 FFT1191 PHX → SFO Apr 19, 23:25 UTCApr 20, 01:15 UTC1h 50m
2026-04-19 FFT1191 PHX → SFO Apr 19, 22:43 UTCApr 20, 01:12 UTC2h 29m
2026-04-19 FFT3871 SLC → PHX Apr 19, 19:45 UTCApr 19, 21:00 UTC1h 15m
2026-04-19 FFT1366 SNA → SLC Apr 19, 16:45 UTCApr 19, 18:10 UTC1h 25m
2026-04-19 FFT1719 PHX → SNA Apr 19, 14:35 UTCApr 19, 15:30 UTC55m
2026-04-19 FFT3606 LAX → PHX Apr 19, 02:55 UTCApr 19, 03:55 UTC1h 0m
2026-04-19 FFT2133 PHX → LAS Apr 19, 00:25 UTCApr 19, 01:25 UTC1h 0m
2026-04-18 FFT1720 SNA → PHX Apr 18, 21:50 UTCApr 18, 22:45 UTC55m
2026-04-18 FFT1719 PHX → SNA Apr 18, 20:00 UTCApr 18, 20:55 UTC55m
2026-04-18 FFT3871 SLC → PHX Apr 18, 17:15 UTCApr 18, 18:25 UTC1h 10m
2026-04-18 FFT1440 PHX → SLC Apr 18, 14:55 UTCApr 18, 16:15 UTC1h 20m
2026-04-18 FFT1439 SLC → PHX Apr 18, 03:25 UTCApr 18, 04:15 UTC50m
2026-04-18 FFT1439 SLC → PHX Apr 18, 03:10 UTCApr 18, 04:14 UTC1h 4m
2026-04-18 FFT1504 SFO → SLC Apr 18, 01:30 UTCApr 18, 02:05 UTC35m
2026-04-18 FFT1504 SFO → SLC Apr 18, 00:40 UTCApr 18, 01:10 UTC30m
2026-04-17 FFT1191 PHX → SFO Apr 17, 21:28 UTCApr 17, 23:14 UTC1h 46m
2026-04-17 FFT1703 SYR → DEN Apr 17, 17:25 UTCApr 17, 18:10 UTC45m
2026-04-17 FFT1703 SYR → DEN Apr 17, 15:45 UTCApr 17, 17:15 UTC1h 30m
2026-04-17 FFT1704 PHX → IAH Apr 17, 13:20 UTCApr 17, 14:20 UTC1h 0m
2026-04-17 FFT1704 PHX → IAH Apr 17, 12:15 UTCApr 17, 13:15 UTC1h 0m
2026-04-17 FFT4753 DEN → PHX Apr 17, 05:20 UTCApr 17, 06:30 UTC1h 10m
2026-04-17 FFT4753 DEN → PHX Apr 17, 04:48 UTCApr 17, 06:30 UTC1h 42m
2026-04-17 FFT4766 PHX → DEN Apr 17, 03:20 UTCApr 17, 03:40 UTC20m
2026-04-17 FFT4766 PHX → DEN Apr 17, 02:25 UTCApr 17, 03:15 UTC50m
2026-04-16 FFT1747 PHL → MSY Apr 16, 23:30 UTCApr 17, 01:00 UTC1h 30m
2026-04-16 FFT1748 MSY → PHL Apr 16, 21:14 UTCApr 16, 21:45 UTC30m
2026-04-16 FFT1748 MSY → PHL Apr 16, 20:12 UTCApr 16, 21:44 UTC1h 32m
2026-04-16 FFT2141 PHL → LAS Apr 16, 17:40 UTCApr 16, 19:10 UTC1h 30m
2026-04-16 FFT1376 PHX → DEN Apr 16, 15:15 UTCApr 16, 16:20 UTC1h 5m
2026-04-16 FFT1376 PHX → DEN Apr 16, 15:00 UTCApr 16, 15:10 UTC10m
2026-04-15 FFT3304 LAX → PHX Apr 15, 23:10 UTCApr 15, 23:55 UTC45m
2026-04-15 FFT1061 CVG → MCO Apr 15, 21:05 UTCApr 15, 21:30 UTC25m
2026-04-15 FFT1061 CVG → MCO Apr 15, 20:35 UTCApr 15, 21:00 UTC25m
2026-04-15 FFT3871 SLC → PHX Apr 15, 17:45 UTCApr 15, 19:00 UTC1h 15m
2026-04-15 FFT1440 PHX → SLC Apr 15, 15:15 UTCApr 15, 16:30 UTC1h 15m

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

Mode-S A3DB93 frequently asked

What is Mode-S code A3DB93?
A3DB93 is an ICAO 24-bit transponder address. Allocated to United States. Assigned to N348FR.
Where is Mode-S A3DB93 registered?
Mode-S code A3DB93 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 A3DB93 broadcasting right now?
No active broadcast right now. Last signal was 8d ago.
Hex, octal, and decimal Mode-S codes: what's the difference?
The same 24-bit identifier expressed in different bases: hex A3DB93, octal 50755623, decimal 10,738,579.
What flights does A3DB93 operate?
Mode-S A3DB93 has broadcast 20 distinct callsigns, including FFT9048, FFT4766, FFT4753, FFT3871, FFT1191.