sensors Mode-S transponder

A05BA2

ICAO 24-bit transponder address · allocated to United States

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

Hex
A05BA2
Octal
50055642
Decimal
10,509,218
Country
US
Tail
N122FE
Type
B763
No current signal · last broadcast 1d ago
Flights observed
212
Distinct callsigns
20
Country
US
Last broadcast
1d ago

Last known position

Most recent position reported by Mode-S A05BA2.

Country allocation

The ICAO 24-bit address A05BA2 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
FDX5607 - 17 2026-07-06
FDX6068 - 14 2026-06-25
FDX6179 - 11 2026-07-03
FDX6067 - 11 2026-06-25
FDX6001 - 11 2026-06-23
FDX6002 - 10 2026-06-24
FDX5158 - 10 2026-07-05
FDX6124 - 8 2026-07-03
FDX6020 - 8 2026-07-10
FDX6126 - 7 2026-07-09
FDX6127 - 6 2026-07-09
FDX6019 - 6 2026-07-09
FDX6091 - 5 2026-07-08
FDX5926 - 5 2026-07-08
FDX5775 - 5 2026-05-17
FDX5284 - 5 2026-04-24
FDX5146 - 5 2026-07-03
FDX5262 FedEx Express 4 2026-04-24
FDX5231 - 4 2026-06-29
FDX5199 - 4 2026-06-26

Recent flights last 50

DateFlightRouteTakeoffLandingDuration
2026-07-13 FDX6013 - Jul 13, 16:50 UTCJul 13, 17:00 UTC10m
2026-07-13 FDX9073 - Jul 13, 14:05 UTCJul 13, 14:30 UTC25m
2026-07-13 FDX9073 - Jul 13, 10:40 UTCJul 13, 11:25 UTC45m
2026-07-12 FDX9078 KIX → ICN Jul 12, 13:55 UTCJul 13, 01:10 UTC11h 15m
2026-07-11 FDX9079 - Jul 11, 18:55 UTCJul 11, 22:15 UTC3h 20m
2026-07-10 FDX6020 - Jul 10, 14:00 UTCJul 10, 16:40 UTC2h 40m
2026-07-09 FDX6019 - Jul 9, 20:00 UTCJul 9, 23:40 UTC3h 40m
2026-07-09 FDX6231 - Jul 9, 13:55 UTCJul 9, 14:40 UTC45m
2026-07-09 FDX6127 TPE → ICN Jul 9, 05:40 UTCJul 9, 07:40 UTC2h 0m
2026-07-09 FDX6126 - Jul 9, 03:00 UTCJul 9, 03:35 UTC35m
2026-07-09 FDX6126 - Jul 9, 01:25 UTCJul 9, 02:10 UTC45m
2026-07-08 FDX5926 - Jul 8, 22:00 UTCJul 8, 22:50 UTC50m
2026-07-08 FDX6091 - Jul 8, 15:10 UTCJul 8, 16:40 UTC1h 30m
2026-07-07 FDX6053 - Jul 7, 13:30 UTCJul 7, 22:25 UTC8h 55m
2026-07-07 FDX6071 - Jul 7, 09:55 UTCJul 7, 10:50 UTC55m
2026-07-07 FDX5148 - Jul 7, 04:05 UTCJul 7, 06:00 UTC1h 55m
2026-07-07 FDX6091 - Jul 7, 01:15 UTCJul 7, 01:50 UTC35m
2026-07-06 FDX5607 - Jul 6, 16:10 UTCJul 6, 16:30 UTC20m
2026-07-06 FDX5607 - Jul 6, 14:55 UTCJul 6, 15:25 UTC30m
2026-07-05 FDX5158 - Jul 5, 19:30 UTCJul 5, 21:05 UTC1h 35m
2026-07-04 FDX5607 - Jul 4, 19:05 UTCJul 4, 19:30 UTC25m
2026-07-04 FDX5607 - Jul 4, 17:50 UTCJul 4, 18:20 UTC30m
2026-07-03 FDX5158 - Jul 3, 21:20 UTCJul 3, 23:00 UTC1h 40m
2026-07-03 FDX6124 - Jul 3, 17:35 UTCJul 3, 17:50 UTC15m
2026-07-03 FDX6124 - Jul 3, 13:55 UTCJul 3, 14:10 UTC15m
2026-07-03 FDX5146 - Jul 3, 06:30 UTCJul 3, 07:40 UTC1h 10m
2026-07-03 FDX6179 - Jul 3, 00:10 UTCJul 3, 00:30 UTC20m
2026-07-02 FDX6179 - Jul 2, 22:00 UTCJul 2, 23:35 UTC1h 35m
2026-07-02 FDX6024 - Jul 2, 13:50 UTCJul 2, 17:05 UTC3h 15m
2026-07-02 FDX5146 - Jul 2, 06:15 UTCJul 2, 07:25 UTC1h 10m
2026-07-02 FDX6179 - Jul 2, 00:10 UTCJul 2, 00:35 UTC25m
2026-07-01 FDX6179 - Jul 1, 21:35 UTCJul 1, 23:40 UTC2h 5m
2026-07-01 FDX5960 - Jul 1, 17:25 UTCJul 1, 18:05 UTC40m
2026-07-01 FDX5960 - Jul 1, 16:10 UTCJul 1, 16:35 UTC25m
2026-07-01 FDX5196 - Jul 1, 12:55 UTCJul 1, 14:25 UTC1h 30m
2026-06-30 FDX5142 - Jun 30, 22:50 UTCJul 1, 00:15 UTC1h 25m
2026-06-30 FDX5152 - Jun 30, 20:05 UTCJun 30, 21:40 UTC1h 35m
2026-06-30 FDX6231 - Jun 30, 13:40 UTCJun 30, 14:25 UTC45m
2026-06-30 FDX6127 TPE → ICN Jun 30, 04:55 UTCJun 30, 06:55 UTC2h 0m
2026-06-30 FDX6126 ICN → TPE Jun 30, 01:04 UTCJun 30, 03:10 UTC2h 6m
2026-06-29 FDX5926 - Jun 29, 22:10 UTCJun 29, 22:49 UTC40m
2026-06-29 FDX5231 - Jun 29, 16:25 UTCJun 29, 16:35 UTC10m
2026-06-29 FDX5231 - Jun 29, 13:44 UTCJun 29, 14:09 UTC25m
2026-06-29 FDX6127 TPE → ICN Jun 29, 04:45 UTCJun 29, 06:50 UTC2h 5m
2026-06-29 FDX6126 ICN → TPE Jun 29, 01:00 UTCJun 29, 03:10 UTC2h 10m
2026-06-27 FDX6127 - Jun 27, 05:49 UTCJun 27, 07:45 UTC1h 55m
2026-06-27 FDX6126 - Jun 27, 01:24 UTCJun 27, 03:34 UTC2h 10m
2026-06-26 FDX5926 - Jun 26, 22:44 UTCJun 26, 23:19 UTC35m
2026-06-26 FDX5199 - Jun 26, 13:45 UTCJun 26, 14:39 UTC55m
2026-06-26 FDX6003 - Jun 26, 01:20 UTCJun 26, 02:09 UTC50m

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

Mode-S A05BA2 frequently asked

What is Mode-S code A05BA2?
A05BA2 is an ICAO 24-bit transponder address. Allocated to United States. Assigned to N122FE.
Where is Mode-S A05BA2 registered?
Mode-S code A05BA2 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 A05BA2 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 A05BA2, octal 50055642, decimal 10,509,218.
What flights does A05BA2 operate?
Mode-S A05BA2 has broadcast 20 distinct callsigns, including FDX5607, FDX6068, FDX6179, FDX6067, FDX6001.