sensors Mode-S transponder

A987B4

ICAO 24-bit transponder address · allocated to United States

Currently assigned to N713FE · ATR-72-600 · operated by FEDERAL EXPRESS CORP

Hex
A987B4
Octal
52303664
Decimal
11,110,324
Country
US
Tail
N713FE
Type
AT76
No current signal · last broadcast 2h ago
Flights observed
66
Distinct callsigns
3
Country
US
Last broadcast
2h ago

Last known position

Most recent position reported by Mode-S A987B4.

Country allocation

The ICAO 24-bit address A987B4 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 3 distinct

Callsign Airline Flights Last seen
CFS7673 Empire Airlines 30 2026-06-02
CFS8673 Empire Airlines 28 2026-06-02
CFS4673 Empire Airlines 8 2026-06-01

Recent flights last 50

DateFlightRouteTakeoffLandingDuration
2026-06-02 CFS7673 MFR → PDX Jun 2, 23:15 UTCJun 3, 00:00 UTC45m
2026-06-02 CFS8673 PDX → MFR Jun 2, 16:00 UTCJun 2, 16:50 UTC50m
2026-06-01 CFS7673 MFR → PDX Jun 1, 23:15 UTCJun 2, 00:10 UTC55m
2026-06-01 CFS4673 PDX → MFR Jun 1, 21:05 UTCJun 1, 22:00 UTC55m
2026-05-29 CFS7673 MFR → PDX May 29, 23:25 UTCMay 30, 00:15 UTC50m
2026-05-29 CFS8673 PDX → MFR May 29, 15:30 UTCMay 29, 16:20 UTC50m
2026-05-28 CFS7673 MFR → PDX May 28, 23:25 UTCMay 29, 00:20 UTC55m
2026-05-28 CFS8673 PDX → MFR May 28, 17:00 UTCMay 28, 17:55 UTC55m
2026-05-27 CFS7673 MFR → PDX May 27, 23:15 UTCMay 28, 00:15 UTC1h 0m
2026-05-27 CFS8673 PDX → MFR May 27, 16:45 UTCMay 27, 17:35 UTC50m
2026-05-26 CFS4673 PDX → MFR May 26, 20:54 UTCMay 26, 21:44 UTC50m
2026-05-22 CFS7673 MFR → PDX May 22, 23:10 UTCMay 23, 00:05 UTC55m
2026-05-22 CFS8673 PDX → MFR May 22, 15:10 UTCMay 22, 16:05 UTC55m
2026-05-21 CFS7673 MFR → PDX May 21, 23:25 UTCMay 22, 00:25 UTC1h 0m
2026-05-21 CFS8673 PDX → MFR May 21, 15:30 UTCMay 21, 16:20 UTC50m
2026-05-20 CFS7673 MFR → PDX May 20, 23:15 UTCMay 21, 00:15 UTC1h 0m
2026-05-20 CFS8673 PDX → MFR May 20, 15:50 UTCMay 20, 16:45 UTC55m
2026-05-19 CFS7673 MFR → PDX May 19, 23:25 UTCMay 20, 00:20 UTC55m
2026-05-19 CFS8673 PDX → MFR May 19, 15:50 UTCMay 19, 16:40 UTC50m
2026-05-18 CFS4673 PDX → MFR May 18, 23:15 UTCMay 19, 00:10 UTC55m
2026-05-18 CFS4673 PDX → MFR May 18, 21:10 UTCMay 18, 22:00 UTC50m
2026-05-15 CFS7673 MFR → PDX May 15, 23:25 UTCMay 16, 00:15 UTC50m
2026-05-15 CFS8673 PDX → MFR May 15, 15:15 UTCMay 15, 16:10 UTC55m
2026-05-14 CFS7673 MFR → PDX May 14, 23:45 UTCMay 15, 00:40 UTC55m
2026-05-14 CFS8673 PDX → MFR May 14, 15:20 UTCMay 14, 16:15 UTC55m
2026-05-13 CFS7673 MFR → PDX May 13, 23:25 UTCMay 14, 00:15 UTC50m
2026-05-13 CFS8673 PDX → MFR May 13, 15:45 UTCMay 13, 16:35 UTC50m
2026-05-12 CFS7673 MFR → PDX May 12, 23:15 UTCMay 13, 00:00 UTC45m
2026-05-12 CFS8673 PDX → MFR May 12, 15:30 UTCMay 12, 16:30 UTC1h 0m
2026-05-11 CFS4673 PDX → MFR May 11, 20:45 UTCMay 11, 21:40 UTC55m
2026-05-08 CFS7673 MFR → PDX May 8, 23:30 UTCMay 9, 00:25 UTC55m
2026-05-08 CFS8673 PDX → MFR May 8, 15:40 UTCMay 8, 16:40 UTC1h 0m
2026-05-07 CFS7673 MFR → PDX May 7, 23:29 UTCMay 8, 00:25 UTC55m
2026-05-07 CFS8673 PDX → MFR May 7, 15:15 UTCMay 7, 16:10 UTC55m
2026-05-06 CFS7673 MFR → PDX May 6, 23:10 UTCMay 7, 00:05 UTC55m
2026-05-06 CFS8673 PDX → MFR May 6, 16:20 UTCMay 6, 17:15 UTC55m
2026-05-05 CFS7673 MFR → PDX May 5, 23:25 UTCMay 6, 00:15 UTC50m
2026-05-05 CFS8673 PDX → MFR May 5, 16:06 UTCMay 5, 16:55 UTC50m
2026-05-04 CFS7673 MFR → PDX May 4, 23:10 UTCMay 5, 00:05 UTC55m
2026-05-04 CFS4673 PDX → MFR May 4, 20:20 UTCMay 4, 21:10 UTC50m
2026-05-01 CFS7673 MFR → PDX May 1, 23:20 UTCMay 2, 00:05 UTC45m
2026-05-01 CFS8673 PDX → MFR May 1, 15:10 UTCMay 1, 16:10 UTC1h 0m
2026-04-30 CFS7673 MFR → PDX Apr 30, 23:20 UTCMay 1, 00:10 UTC50m
2026-04-30 CFS8673 PDX → MFR Apr 30, 15:30 UTCApr 30, 16:30 UTC1h 0m
2026-04-29 CFS7673 MFR → PDX Apr 29, 23:20 UTCApr 30, 00:15 UTC55m
2026-04-29 CFS8673 PDX → MFR Apr 29, 15:50 UTCApr 29, 16:40 UTC50m
2026-04-28 CFS8673 PDX → MFR Apr 28, 23:20 UTCApr 29, 00:10 UTC50m
2026-04-28 CFS8673 PDX → MFR Apr 28, 16:40 UTCApr 28, 17:35 UTC55m
2026-04-27 CFS7673 MFR → PDX Apr 27, 23:10 UTCApr 28, 00:05 UTC55m
2026-04-27 CFS4673 PDX → MFR Apr 27, 20:30 UTCApr 27, 21: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 N713FE page for operator, model, and routing details .

Mode-S A987B4 frequently asked

What is Mode-S code A987B4?
A987B4 is an ICAO 24-bit transponder address. Allocated to United States. Assigned to N713FE.
Where is Mode-S A987B4 registered?
Mode-S code A987B4 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 A987B4 broadcasting right now?
No active broadcast right now. Last signal was 2h ago.
Hex, octal, and decimal Mode-S codes: what's the difference?
The same 24-bit identifier expressed in different bases: hex A987B4, octal 52303664, decimal 11,110,324.
What flights does A987B4 operate?
Mode-S A987B4 has broadcast 3 distinct callsigns, including CFS7673, CFS8673, CFS4673.