Apparatus

Try JFK, AAL1290, BAW, or N225AN.

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 9h ago
Flights observed
132
Distinct callsigns
4
Country
US
Last broadcast
9h 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 4 distinct

Callsign Airline Flights Last seen
CFS7673 - 62 2026-07-17
CFS8673 - 55 2026-07-17
CFS4673 - 14 2026-07-13
CFS7373 - 1 2026-06-24

Recent flights last 50

DateFlightRouteTakeoffLandingDuration
2026-07-17 CFS7673 - Jul 17, 23:14 UTCJul 18, 00:04 UTC50m
2026-07-17 CFS8673 PDX → MFR Jul 17, 14:50 UTCJul 17, 15:49 UTC1h 0m
2026-07-16 CFS7673 MFR → PDX Jul 16, 23:15 UTCJul 17, 00:04 UTC50m
2026-07-16 CFS8673 - Jul 16, 15:05 UTCJul 16, 15:55 UTC50m
2026-07-15 CFS7673 MFR → PDX Jul 15, 23:15 UTCJul 16, 00:00 UTC45m
2026-07-15 CFS8673 - Jul 15, 15:20 UTCJul 15, 16:05 UTC45m
2026-07-14 CFS7673 MFR → PDX Jul 14, 23:20 UTCJul 15, 00:05 UTC45m
2026-07-14 CFS8673 PDX → MFR Jul 14, 15:35 UTCJul 14, 16:40 UTC1h 5m
2026-07-13 CFS7673 MFR → PDX Jul 13, 23:10 UTCJul 14, 00:05 UTC55m
2026-07-13 CFS4673 PDX → MFR Jul 13, 20:35 UTCJul 13, 21:30 UTC55m
2026-07-10 CFS7673 MFR → PDX Jul 10, 23:20 UTCJul 11, 00:10 UTC50m
2026-07-10 CFS8673 PDX → MFR Jul 10, 15:50 UTCJul 10, 16:45 UTC55m
2026-07-09 CFS7673 MFR → PDX Jul 9, 23:20 UTCJul 10, 00:15 UTC55m
2026-07-09 CFS8673 PDX → MFR Jul 9, 15:30 UTCJul 9, 16:25 UTC55m
2026-07-08 CFS7673 MFR → PDX Jul 8, 23:15 UTCJul 9, 00:05 UTC50m
2026-07-08 CFS8673 - Jul 8, 15:50 UTCJul 8, 16:45 UTC55m
2026-07-07 CFS7673 - Jul 7, 23:15 UTCJul 8, 00:05 UTC50m
2026-07-07 CFS8673 PDX → MFR Jul 7, 15:10 UTCJul 7, 16:05 UTC55m
2026-07-06 CFS7673 MFR → PDX Jul 6, 23:20 UTCJul 7, 00:10 UTC50m
2026-07-06 CFS4673 PDX → MFR Jul 6, 20:50 UTCJul 6, 21:40 UTC50m
2026-07-03 CFS7673 MFR → PDX Jul 3, 23:05 UTCJul 3, 23:55 UTC50m
2026-07-03 CFS8673 PDX → MFR Jul 3, 15:20 UTCJul 3, 16:10 UTC50m
2026-07-02 CFS7673 MFR → PDX Jul 2, 23:20 UTCJul 3, 00:10 UTC50m
2026-07-02 CFS8673 PDX → MFR Jul 2, 15:20 UTCJul 2, 16:10 UTC50m
2026-07-01 CFS7673 MFR → PDX Jul 1, 23:20 UTCJul 2, 00:15 UTC55m
2026-07-01 CFS8673 PDX → MFR Jul 1, 15:25 UTCJul 1, 16:20 UTC55m
2026-06-30 CFS7673 MFR → PDX Jun 30, 23:25 UTCJul 1, 00:20 UTC55m
2026-06-30 CFS8673 - Jun 30, 15:50 UTCJun 30, 16:40 UTC50m
2026-06-29 CFS7673 MFR → PDX Jun 29, 23:19 UTCJun 30, 00:14 UTC55m
2026-06-29 CFS4673 PDX → MFR Jun 29, 20:49 UTCJun 29, 21:39 UTC50m
2026-06-26 CFS7673 MFR → PDX Jun 26, 23:25 UTCJun 27, 00:20 UTC55m
2026-06-26 CFS8673 PDX → MFR Jun 26, 15:34 UTCJun 26, 16:30 UTC55m
2026-06-25 CFS7673 MFR → PDX Jun 25, 23:24 UTCJun 26, 00:20 UTC55m
2026-06-25 CFS8673 PDX → MFR Jun 25, 15:15 UTCJun 25, 16:09 UTC55m
2026-06-24 CFS7373 MFR → PDX Jun 24, 23:20 UTCJun 25, 00:09 UTC50m
2026-06-24 CFS8673 PDX → MFR Jun 24, 15:35 UTCJun 24, 16:29 UTC55m
2026-06-23 CFS7673 MFR → PDX Jun 23, 23:14 UTCJun 24, 00:05 UTC50m
2026-06-23 CFS8673 PDX → MFR Jun 23, 15:44 UTCJun 23, 16:35 UTC50m
2026-06-22 CFS7673 MFR → PDX Jun 22, 23:10 UTCJun 23, 00:00 UTC50m
2026-06-22 CFS4673 PDX → MFR Jun 22, 20:44 UTCJun 22, 21:40 UTC55m
2026-06-19 CFS7673 MFR → PDX Jun 19, 23:19 UTCJun 20, 00:09 UTC50m
2026-06-19 CFS8673 - Jun 19, 15:14 UTCJun 19, 16:04 UTC50m
2026-06-18 CFS7673 - Jun 18, 23:25 UTCJun 19, 00:20 UTC54m
2026-06-18 CFS8673 - Jun 18, 16:25 UTCJun 18, 17:21 UTC56m
2026-06-17 CFS7673 - Jun 17, 23:35 UTCJun 18, 00:30 UTC55m
2026-06-17 CFS8673 PDX → MFR Jun 17, 16:15 UTCJun 17, 17:05 UTC50m
2026-06-16 CFS7673 MFR → PDX Jun 16, 23:25 UTCJun 17, 00:15 UTC50m
2026-06-16 CFS8673 PDX → MFR Jun 16, 15:30 UTCJun 16, 16:25 UTC55m
2026-06-15 CFS7673 MFR → PDX Jun 15, 23:09 UTCJun 16, 00:05 UTC55m
2026-06-15 CFS4673 PDX → MFR Jun 15, 20:54 UTCJun 15, 21:45 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 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 9h 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 4 distinct callsigns, including CFS7673, CFS8673, CFS4673, CFS7373.