Apparatus

Try JFK, AAL1290, BAW, or N225AN.

sensors Mode-S transponder

A0105B

ICAO 24-bit transponder address · allocated to United States

Currently assigned to N103FE · BOEING 767-300 · operated by FEDERAL EXPRESS CORP

Hex
A0105B
Octal
50010133
Decimal
10,489,947
Country
US
Tail
N103FE
Type
B763
No current signal · last broadcast 12h ago
Flights observed
194
Distinct callsigns
20
Country
US
Last broadcast
12h ago

Last known position

Most recent position reported by Mode-S A0105B.

Country allocation

The ICAO 24-bit address A0105B 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

Callsign Airline Flights Last seen
FDX6068 - 14 2026-06-24
FDX6067 - 14 2026-06-24
FDX6126 - 12 2026-06-26
FDX6091 - 10 2026-07-01
FDX6127 - 9 2026-06-26
FDX6019 - 9 2026-07-13
FDX5607 - 9 2026-06-30
FDX6020 - 8 2026-07-08
FDX5148 - 8 2026-07-09
FDX5960 FedEx Express 6 2026-06-16
FDX5926 - 6 2026-06-09
FDX5231 - 6 2026-06-26
FDX6073 - 5 2026-06-28
FDX6053 - 5 2026-07-09
FDX6003 - 5 2026-06-27
FDX5194 FedEx Express 5 2026-04-26
FDX5158 - 5 2026-06-29
FDX9172 - 4 2026-07-12
FDX6071 - 4 2026-07-09
FDX9158 - 3 2026-06-18

Recent flights last 50

DateFlightRouteTakeoffLandingDuration
2026-07-13 FDX6019 - Jul 13, 20:20 UTCJul 13, 23:35 UTC3h 15m
2026-07-12 FDX9125 - Jul 12, 16:45 UTCJul 12, 16:55 UTC10m
2026-07-12 FDX9172 - Jul 12, 11:40 UTCJul 12, 11:55 UTC15m
2026-07-12 FDX9172 - Jul 12, 01:10 UTCJul 12, 01:40 UTC30m
2026-07-11 FDX5153 - Jul 11, 12:55 UTCJul 11, 14:30 UTC1h 35m
2026-07-10 FDX5608 - Jul 10, 22:20 UTCJul 11, 00:05 UTC1h 45m
2026-07-09 FDX6053 - Jul 9, 14:15 UTCJul 9, 14:50 UTC35m
2026-07-09 FDX6071 - Jul 9, 10:05 UTCJul 9, 10:55 UTC50m
2026-07-09 FDX5148 - Jul 9, 03:50 UTCJul 9, 06:15 UTC2h 25m
2026-07-08 FDX6020 - Jul 8, 13:50 UTCJul 9, 02:05 UTC12h 15m
2026-07-07 FDX6019 - Jul 7, 20:20 UTCJul 7, 23:45 UTC3h 25m
2026-07-01 FDX6091 - Jul 1, 15:20 UTCJul 1, 15:55 UTC35m
2026-07-01 FDX6091 - Jul 1, 14:20 UTCJul 1, 14:30 UTC10m
2026-06-30 FDX6159 - Jun 30, 20:55 UTCJun 30, 22:30 UTC1h 35m
2026-06-30 FDX5607 - Jun 30, 17:15 UTCJun 30, 17:30 UTC15m
2026-06-30 FDX5607 - Jun 30, 15:50 UTCJun 30, 16:15 UTC25m
2026-06-29 FDX5158 - Jun 29, 21:14 UTCJun 29, 22:44 UTC1h 30m
2026-06-29 FDX6013 - Jun 29, 16:59 UTCJun 29, 17:19 UTC20m
2026-06-29 FDX9073 - Jun 29, 10:29 UTCJun 29, 14:29 UTC4h 0m
2026-06-28 FDX6073 KIX → ICN Jun 28, 14:14 UTCJun 29, 01:29 UTC11h 15m
2026-06-27 FDX6003 - Jun 27, 21:29 UTCJun 28, 01:25 UTC3h 55m
2026-06-27 FDX6003 - Jun 27, 19:09 UTCJun 27, 19:45 UTC35m
2026-06-26 FDX5231 - Jun 26, 14:05 UTCJun 26, 14:50 UTC45m
2026-06-26 FDX6127 - Jun 26, 05:10 UTCJun 26, 07:05 UTC1h 55m
2026-06-26 FDX6126 - Jun 26, 02:40 UTCJun 26, 03:00 UTC20m
2026-06-26 FDX6126 - Jun 26, 00:55 UTCJun 26, 01:24 UTC30m
2026-06-25 FDX6091 - Jun 25, 15:10 UTCJun 25, 23:09 UTC8h 0m
2026-06-24 FDX6159 - Jun 24, 20:24 UTCJun 24, 22:35 UTC2h 10m
2026-06-24 FDX6067 - Jun 24, 17:10 UTCJun 24, 17:40 UTC30m
2026-06-24 FDX6067 - Jun 24, 11:34 UTCJun 24, 12:09 UTC35m
2026-06-24 FDX6068 - Jun 24, 04:05 UTCJun 24, 05:15 UTC1h 10m
2026-06-24 FDX6068 - Jun 24, 01:24 UTCJun 24, 01:39 UTC15m
2026-06-23 FDX6068 - Jun 23, 21:39 UTCJun 23, 21:54 UTC15m
2026-06-23 FDX6067 - Jun 23, 17:09 UTCJun 23, 17:30 UTC20m
2026-06-23 FDX6067 - Jun 23, 10:59 UTCJun 23, 11:24 UTC25m
2026-06-23 FDX6068 - Jun 23, 04:14 UTCJun 23, 05:29 UTC1h 15m
2026-06-23 FDX6068 - Jun 23, 01:30 UTCJun 23, 01:40 UTC10m
2026-06-22 FDX6068 - Jun 22, 21:25 UTCJun 22, 22:10 UTC45m
2026-06-22 FDX6013 - Jun 22, 16:20 UTCJun 22, 16:40 UTC20m
2026-06-22 FDX9073 - Jun 22, 10:40 UTCJun 22, 14:24 UTC3h 45m
2026-06-21 FDX9073 - Jun 21, 23:59 UTCJun 22, 00:34 UTC35m
2026-06-21 FDX6073 - Jun 21, 14:24 UTCJun 21, 15:30 UTC1h 5m
2026-06-20 FDX6003 CAN → CDG Jun 20, 21:44 UTCJun 21, 01:55 UTC4h 10m
2026-06-20 FDX6003 CAN → CDG Jun 20, 18:24 UTCJun 20, 19:34 UTC1h 10m
2026-06-19 FDX6067 - Jun 19, 18:09 UTCJun 19, 18:30 UTC20m
2026-06-19 FDX6067 - Jun 19, 12:04 UTCJun 19, 12:29 UTC25m
2026-06-19 FDX6068 - Jun 19, 04:14 UTCJun 19, 05:24 UTC1h 10m
2026-06-19 FDX6068 - Jun 19, 01:50 UTCJun 19, 02:04 UTC15m
2026-06-18 FDX6068 - Jun 18, 22:20 UTCJun 18, 22:35 UTC15m
2026-06-18 FDX9158 - Jun 18, 13:50 UTCJun 18, 15:35 UTC1h 45m

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

Mode-S A0105B frequently asked

What is Mode-S code A0105B?
A0105B is an ICAO 24-bit transponder address. Allocated to United States. Assigned to N103FE.
Where is Mode-S A0105B registered?
Mode-S code A0105B 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 A0105B broadcasting right now?
No active broadcast right now. Last signal was 12h ago.
Hex, octal, and decimal Mode-S codes: what's the difference?
The same 24-bit identifier expressed in different bases: hex A0105B, octal 50010133, decimal 10,489,947.
What flights does A0105B operate?
Mode-S A0105B has broadcast 20 distinct callsigns, including FDX6068, FDX6067, FDX6126, FDX6091, FDX6127.