sensors Mode-S transponder

A0BD33

ICAO 24-bit transponder address · allocated to United States

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

Hex
A0BD33
Octal
50136463
Decimal
10,534,195
Country
US
Tail
N147FE
Type
B763
No current signal · last broadcast 1h ago
Flights observed
209
Distinct callsigns
20
Country
US
Last broadcast
1h ago

Last known position

Most recent position reported by Mode-S A0BD33.

Country allocation

The ICAO 24-bit address A0BD33 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
FDX67 - 11 2026-07-10
FDX68 - 4 2026-07-11
FDX54 - 4 2026-06-19
FDX53 - 4 2026-07-14
FDX3604 - 4 2026-07-07
FDX1708 FedEx Express 4 2026-05-13
FDX1292 - 4 2026-07-03
FDX434 - 3 2026-06-24
FDX404 FedEx Express 3 2026-05-20
FDX1804 FedEx Express 3 2026-06-02
FDX1711 FedEx Express 3 2026-05-20
FDX168 - 3 2026-07-04
FDX1631 FedEx Express 3 2026-06-11
FDX9121 - 2 2026-07-09
FDX9120 - 2 2026-07-08
FDX89 - 2 2026-07-17
FDX798 FedEx Express 2 2026-05-05
FDX66 - 2 2026-06-27
FDX644 - 2 2026-04-15
FDX505 FedEx Express 2 2026-04-30

Recent flights last 50

DateFlightRouteTakeoffLandingDuration
2026-07-18 FDX1450 - Jul 18, 08:55 UTCJul 18, 09:45 UTC50m
2026-07-17 FDX89 - Jul 17, 09:20 UTCJul 18, 03:50 UTC18h 31m
2026-07-17 FDX2278 - Jul 17, 01:00 UTCJul 17, 02:30 UTC1h 30m
2026-07-17 FDX2278 MCO → MEM Jul 17, 00:57 UTCJul 17, 02:29 UTC1h 32m
2026-07-16 FDX1409 - Jul 16, 07:45 UTCJul 16, 09:10 UTC1h 25m
2026-07-16 FDX1387 - Jul 16, 02:15 UTCJul 16, 03:35 UTC1h 20m
2026-07-15 FDX1587 - Jul 15, 07:55 UTCJul 15, 09:20 UTC1h 25m
2026-07-15 FDX1220 - Jul 15, 03:10 UTCJul 15, 05:10 UTC2h 0m
2026-07-14 FDX529 - Jul 14, 21:25 UTCJul 14, 23:15 UTC1h 49m
2026-07-14 FDX254 - Jul 14, 14:30 UTCJul 14, 17:00 UTC2h 30m
2026-07-14 FDX53 - Jul 14, 10:05 UTCJul 14, 12:15 UTC2h 10m
2026-07-14 FDX2210 - Jul 14, 02:15 UTCJul 14, 03:40 UTC1h 25m
2026-07-11 FDX1410 - Jul 11, 08:55 UTCJul 11, 10:20 UTC1h 25m
2026-07-11 FDX68 - Jul 11, 03:05 UTCJul 11, 04:55 UTC1h 50m
2026-07-10 FDX67 - Jul 10, 22:40 UTCJul 11, 00:35 UTC1h 55m
2026-07-10 FDX67 MEM → MTY Jul 10, 22:36 UTCJul 11, 00:35 UTC1h 59m
2026-07-10 FDX1314 - Jul 10, 03:10 UTCJul 10, 05:25 UTC2h 15m
2026-07-09 FDX3709 - Jul 9, 21:05 UTCJul 9, 22:45 UTC1h 40m
2026-07-09 FDX3605 FLL → IND Jul 9, 11:30 UTCJul 9, 13:39 UTC2h 9m
2026-07-09 FDX3605 - Jul 9, 11:35 UTCJul 9, 13:45 UTC2h 10m
2026-07-09 FDX1444 - Jul 9, 08:00 UTCJul 9, 09:45 UTC1h 45m
2026-07-09 FDX9121 - Jul 9, 02:40 UTCJul 9, 04:25 UTC1h 45m
2026-07-09 FDX9121 YYZ → MEM Jul 9, 02:39 UTCJul 9, 04:26 UTC1h 47m
2026-07-08 FDX9120 - Jul 8, 23:35 UTCJul 9, 00:45 UTC1h 10m
2026-07-08 FDX9120 MEM → YYZ Jul 8, 23:30 UTCJul 9, 01:18 UTC1h 48m
2026-07-08 FDX452 - Jul 8, 13:00 UTCJul 8, 16:15 UTC3h 15m
2026-07-08 FDX1404 - Jul 8, 07:55 UTCJul 8, 11:00 UTC3h 5m
2026-07-08 FDX2283 - Jul 8, 03:55 UTCJul 8, 04:55 UTC1h 0m
2026-07-07 FDX3604 PDX → IND Jul 7, 13:45 UTCJul 7, 17:25 UTC3h 40m
2026-07-07 FDX1857 OAK → PDX Jul 7, 10:00 UTCJul 7, 11:05 UTC1h 5m
2026-07-07 FDX1835 - Jul 7, 05:15 UTCJul 7, 06:05 UTC50m
2026-07-07 FDX1835 LAX → OAK Jul 7, 05:13 UTCJul 7, 06:05 UTC52m
2026-07-05 FDX323 - Jul 5, 21:55 UTCJul 6, 01:15 UTC3h 20m
2026-07-04 FDX168 MTY → MEM Jul 4, 23:32 UTCJul 5, 01:21 UTC1h 49m
2026-07-04 FDX168 - Jul 4, 23:35 UTCJul 5, 01:20 UTC1h 45m
2026-07-04 FDX67 MTY → MTY Jul 4, 13:30 UTCJul 4, 21:55 UTC8h 25m
2026-07-04 FDX67 - Jul 4, 09:25 UTCJul 4, 11:20 UTC1h 55m
2026-07-04 FDX131 - Jul 4, 01:35 UTCJul 4, 04:00 UTC2h 25m
2026-07-03 FDX130 - Jul 3, 09:00 UTCJul 3, 11:15 UTC2h 15m
2026-07-03 FDX1292 JFK → MEM Jul 3, 03:20 UTCJul 3, 05:24 UTC2h 4m
2026-07-03 FDX1292 - Jul 3, 03:25 UTCJul 3, 05:25 UTC2h 0m
2026-07-02 FDX1483 - Jul 2, 08:40 UTCJul 2, 10:50 UTC2h 10m
2026-07-02 FDX1483 MEM → JFK Jul 2, 08:39 UTCJul 2, 10:48 UTC2h 9m
2026-07-02 FDX1203 - Jul 2, 01:35 UTCJul 2, 02:55 UTC1h 20m
2026-07-01 FDX1722 - Jul 1, 08:50 UTCJul 1, 09:35 UTC45m
2026-07-01 FDX1609 DFW → IND Jul 1, 03:50 UTCJul 1, 05:25 UTC1h 35m
2026-06-30 FDX1401 - Jun 30, 10:10 UTCJun 30, 11:10 UTC1h 0m
2026-06-30 FDX2364 BNA → MEM Jun 30, 04:40 UTCJun 30, 05:20 UTC40m
2026-06-30 FDX2364 BNA → MEM Jun 30, 04:40 UTCJun 30, 05:13 UTC33m
2026-06-27 FDX1498 - Jun 27, 09:29 UTCJun 27, 10:05 UTC35m

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

Mode-S A0BD33 frequently asked

What is Mode-S code A0BD33?
A0BD33 is an ICAO 24-bit transponder address. Allocated to United States. Assigned to N147FE.
Where is Mode-S A0BD33 registered?
Mode-S code A0BD33 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 A0BD33 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 A0BD33, octal 50136463, decimal 10,534,195.
What flights does A0BD33 operate?
Mode-S A0BD33 has broadcast 20 distinct callsigns, including FDX67, FDX68, FDX54, FDX53, FDX3604.