Apparatus

Try JFK, AAL1290, BAW, or N225AN.

sensors Mode-S transponder

A2CF07

ICAO 24-bit transponder address · allocated to United States

Currently assigned to N280LT · GULFSTREAM G200 · operated by MCP INVESTMENTS LLC, WEAK D INVESTMENTS LLC, PIN OAK AVIONICS LLC

Hex
A2CF07
Octal
50547407
Decimal
10,669,831
Country
US
Tail
N280LT
Type
GALX
No current signal · last broadcast 3d ago
Flights observed
69
Distinct callsigns
1
Country
US
Last broadcast
3d ago

Last known position

Most recent position reported by Mode-S A2CF07.

Country allocation

The ICAO 24-bit address A2CF07 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 1 distinct

Callsign Airline Flights Last seen
JTL28 Jetall Holdings 69 2026-07-25

Recent flights last 50

DateFlightRouteTakeoffLandingDuration
2026-07-25 JTL28 RDU → APF Jul 25, 04:00 UTCJul 25, 04:40 UTC40m
2026-07-02 JTL28 - Jul 2, 17:15 UTCJul 2, 18:40 UTC1h 25m
2026-07-01 JTL28 - Jul 1, 23:05 UTCJul 2, 01:10 UTC2h 5m
2026-07-01 JTL28 - Jul 1, 20:40 UTCJul 1, 21:35 UTC55m
2026-07-01 JTL28 - Jul 1, 14:20 UTCJul 1, 16:30 UTC2h 10m
2026-06-29 JTL28 - Jun 29, 21:24 UTCJun 29, 22:19 UTC55m
2026-06-29 JTL28 - Jun 29, 19:15 UTCJun 29, 20:30 UTC1h 15m
2026-06-28 JTL28 - Jun 28, 19:55 UTCJun 28, 20:29 UTC35m
2026-06-28 JTL28 - Jun 28, 14:25 UTCJun 28, 17:55 UTC3h 30m
2026-06-27 JTL28 - Jun 27, 19:24 UTCJun 27, 20:24 UTC1h 0m
2026-06-27 JTL28 - Jun 27, 14:20 UTCJun 27, 18:04 UTC3h 45m
2026-06-26 JTL28 - Jun 26, 18:44 UTCJun 26, 19:30 UTC45m
2026-06-26 JTL28 - Jun 26, 17:15 UTCJun 26, 17:59 UTC45m
2026-06-26 JTL28 - Jun 26, 15:05 UTCJun 26, 16:09 UTC1h 5m
2026-06-20 JTL28 - Jun 20, 19:40 UTCJun 20, 21:19 UTC1h 40m
2026-06-19 JTL28 - Jun 19, 19:19 UTCJun 19, 19:59 UTC40m
2026-06-18 JTL28 - Jun 18, 20:05 UTCJun 18, 20:55 UTC50m
2026-06-18 JTL28 - Jun 18, 16:40 UTCJun 18, 17:25 UTC45m
2026-06-18 JTL28 - Jun 18, 13:50 UTCJun 18, 15:25 UTC1h 35m
2026-06-17 JTL28 - Jun 17, 20:25 UTCJun 17, 21:05 UTC40m
2026-06-17 JTL28 - Jun 17, 15:15 UTCJun 17, 16:10 UTC55m
2026-06-17 JTL28 - Jun 17, 12:05 UTCJun 17, 13:10 UTC1h 5m
2026-06-14 JTL28 RDU → APF Jun 14, 16:15 UTCJun 14, 17:55 UTC1h 40m
2026-06-14 JTL28 RDU → APF Jun 14, 14:00 UTCJun 14, 15:00 UTC1h 0m
2026-06-14 JTL28 RDU → APF Jun 14, 12:20 UTCJun 14, 12:35 UTC15m
2026-06-12 JTL28 RDU → APF Jun 12, 22:40 UTCJun 12, 23:10 UTC30m
2026-06-12 JTL28 RDU → APF Jun 12, 20:05 UTCJun 12, 21:50 UTC1h 45m
2026-06-12 JTL28 RDU → APF Jun 12, 15:35 UTCJun 12, 17:05 UTC1h 30m
2026-06-11 JTL28 RDU → APF Jun 11, 18:55 UTCJun 11, 19:30 UTC35m
2026-06-11 JTL28 RDU → APF Jun 11, 15:40 UTCJun 11, 18:05 UTC2h 25m
2026-06-11 JTL28 RDU → APF Jun 11, 12:35 UTCJun 11, 13:45 UTC1h 10m
2026-06-10 JTL28 RDU → APF Jun 10, 15:55 UTCJun 10, 19:10 UTC3h 15m
2026-06-09 JTL28 RDU → APF Jun 9, 22:55 UTCJun 10, 00:20 UTC1h 25m
2026-06-01 JTL28 RDU → APF Jun 1, 22:50 UTCJun 1, 23:30 UTC40m
2026-06-01 JTL28 RDU → APF Jun 1, 00:05 UTCJun 1, 02:45 UTC2h 40m
2026-05-30 JTL28 RDU → APF May 30, 21:15 UTCMay 30, 22:05 UTC50m
2026-05-30 JTL28 RDU → APF May 30, 17:50 UTCMay 30, 19:05 UTC1h 15m
2026-05-29 JTL28 RDU → APF May 29, 16:15 UTCMay 29, 17:50 UTC1h 35m
2026-05-28 JTL28 RDU → APF May 28, 14:50 UTCMay 28, 15:25 UTC35m
2026-05-24 JTL28 RDU → APF May 24, 17:00 UTCMay 24, 17:50 UTC50m
2026-05-22 JTL28 RDU → APF May 22, 16:05 UTCMay 22, 16:50 UTC45m
2026-05-21 JTL28 RDU → APF May 21, 19:40 UTCMay 21, 20:00 UTC20m
2026-05-17 JTL28 RDU → APF May 17, 20:30 UTCMay 17, 20:50 UTC20m
2026-05-17 JTL28 RDU → APF May 17, 17:35 UTCMay 17, 19:35 UTC2h 0m
2026-05-14 JTL28 RDU → APF May 14, 13:55 UTCMay 14, 15:50 UTC1h 55m
2026-05-13 JTL28 RDU → APF May 13, 20:40 UTCMay 13, 21:10 UTC30m
2026-05-07 JTL28 RDU → APF May 7, 21:35 UTCMay 7, 21:55 UTC20m
2026-05-07 JTL28 RDU → APF May 7, 17:00 UTCMay 7, 20:40 UTC3h 40m
2026-05-05 JTL28 RDU → APF May 5, 17:15 UTCMay 5, 20:05 UTC2h 50m
2026-05-05 JTL28 RDU → APF May 5, 14:30 UTCMay 5, 15:10 UTC40m

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

Mode-S A2CF07 frequently asked

What is Mode-S code A2CF07?
A2CF07 is an ICAO 24-bit transponder address. Allocated to United States. Assigned to N280LT.
Where is Mode-S A2CF07 registered?
Mode-S code A2CF07 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 A2CF07 broadcasting right now?
No active broadcast right now. Last signal was 3d ago.
Hex, octal, and decimal Mode-S codes: what's the difference?
The same 24-bit identifier expressed in different bases: hex A2CF07, octal 50547407, decimal 10,669,831.
What flights does A2CF07 operate?
Mode-S A2CF07 has broadcast 1 distinct callsign, including JTL28.