Apparatus

Try JFK, AAL1290, BAW, or N225AN.

sensors Mode-S transponder

A8FFA1

ICAO 24-bit transponder address · allocated to United States

Currently assigned to N67909 · CESSNA 402 Businessliner · operated by HYANNIS AIR SERVICE INC DBA, CAPE AIR

Hex
A8FFA1
Octal
52177641
Decimal
11,075,489
Country
US
Tail
N67909
Type
C402
No current signal · last broadcast 6h ago
Flights observed
194
Distinct callsigns
5
Country
US
Last broadcast
6h ago

Last known position

Most recent position reported by Mode-S A8FFA1.

Country allocation

The ICAO 24-bit address A8FFA1 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 5 distinct

Callsign Airline Flights Last seen
KAP22 Cape Air 113 2026-05-28
KAP615 Cape Air 71 2026-05-29
KAP394 Cape Air 8 2026-04-21
KAPT787 - 1 2026-05-25
KAP916 Cape Air 1 2026-04-23

Recent flights last 50

DateFlightRouteTakeoffLandingDuration
2026-05-29 KAP615 HYA → BOS May 29, 21:55 UTCMay 29, 22:10 UTC15m
2026-05-29 KAP615 HYA → BOS May 29, 20:35 UTCMay 29, 20:45 UTC10m
2026-05-29 KAP615 HYA → BOS May 29, 12:35 UTCMay 29, 13:10 UTC35m
2026-05-29 KAP615 HYA → BOS May 29, 10:30 UTCMay 29, 10:40 UTC10m
2026-05-28 KAP22 ACK → BOS May 28, 21:50 UTCMay 28, 22:00 UTC10m
2026-05-28 KAP22 ACK → BOS May 28, 20:40 UTCMay 28, 20:50 UTC10m
2026-05-28 KAP22 ACK → BOS May 28, 17:45 UTCMay 28, 18:00 UTC15m
2026-05-28 KAP22 ACK → BOS May 28, 16:40 UTCMay 28, 16:50 UTC10m
2026-05-28 KAP22 ACK → BOS May 28, 12:40 UTCMay 28, 13:30 UTC50m
2026-05-28 KAP22 ACK → BOS May 28, 11:10 UTCMay 28, 11:20 UTC10m
2026-05-28 KAP22 ACK → BOS May 28, 10:25 UTCMay 28, 10:40 UTC15m
2026-05-27 KAP615 HYA → BOS May 27, 10:25 UTCMay 27, 11:15 UTC50m
2026-05-26 KAP615 HYA → BOS May 26, 20:40 UTCMay 26, 20:50 UTC10m
2026-05-26 KAP615 HYA → BOS May 26, 12:40 UTCMay 26, 13:29 UTC50m
2026-05-26 KAP615 HYA → BOS May 26, 10:29 UTCMay 26, 10:39 UTC10m
2026-05-25 KAPT787 - May 25, 19:59 UTCMay 25, 22:40 UTC2h 40m
2026-05-23 KAP22 ACK → BOS May 23, 18:05 UTCMay 23, 18:15 UTC11m
2026-05-23 KAP22 ACK → BOS May 23, 16:35 UTCMay 23, 16:50 UTC15m
2026-05-23 KAP22 ACK → BOS May 23, 11:35 UTCMay 23, 13:25 UTC1h 50m
2026-05-22 KAP22 ACK → BOS May 22, 21:45 UTCMay 22, 21:55 UTC10m
2026-05-22 KAP22 ACK → BOS May 22, 20:35 UTCMay 22, 20:50 UTC15m
2026-05-22 KAP22 ACK → BOS May 22, 13:20 UTCMay 22, 13:30 UTC10m
2026-05-22 KAP22 ACK → BOS May 22, 12:40 UTCMay 22, 12:50 UTC10m
2026-05-22 KAP22 ACK → BOS May 22, 11:20 UTCMay 22, 11:35 UTC15m
2026-05-22 KAP22 ACK → BOS May 22, 10:35 UTCMay 22, 10:45 UTC10m
2026-05-21 KAP22 ACK → BOS May 21, 21:45 UTCMay 21, 21:55 UTC10m
2026-05-21 KAP22 ACK → BOS May 21, 20:40 UTCMay 21, 20:50 UTC10m
2026-05-21 KAP22 ACK → BOS May 21, 11:20 UTCMay 21, 11:30 UTC10m
2026-05-21 KAP22 ACK → BOS May 21, 10:30 UTCMay 21, 10:45 UTC15m
2026-05-20 KAP22 ACK → BOS May 20, 21:50 UTCMay 20, 22:00 UTC10m
2026-05-20 KAP22 ACK → BOS May 20, 20:45 UTCMay 20, 20:55 UTC10m
2026-05-20 KAP615 HYA → BOS May 20, 15:10 UTCMay 20, 15:20 UTC10m
2026-05-20 KAP615 HYA → BOS May 20, 11:05 UTCMay 20, 11:15 UTC10m
2026-05-20 KAP615 HYA → BOS May 20, 10:25 UTCMay 20, 10:35 UTC10m
2026-05-19 KAP615 HYA → BOS May 19, 21:55 UTCMay 19, 22:05 UTC10m
2026-05-19 KAP615 HYA → BOS May 19, 20:45 UTCMay 19, 21:00 UTC15m
2026-05-19 KAP615 HYA → BOS May 19, 12:45 UTCMay 19, 13:20 UTC35m
2026-05-19 KAP615 HYA → BOS May 19, 11:15 UTCMay 19, 11:25 UTC10m
2026-05-19 KAP615 HYA → BOS May 19, 10:35 UTCMay 19, 10:45 UTC10m
2026-05-18 KAP615 HYA → BOS May 18, 20:45 UTCMay 18, 20:55 UTC10m
2026-05-18 KAP615 HYA → BOS May 18, 12:40 UTCMay 18, 13:15 UTC35m
2026-05-18 KAP615 HYA → BOS May 18, 10:25 UTCMay 18, 10:35 UTC10m
2026-05-16 KAP22 ACK → BOS May 16, 18:05 UTCMay 16, 18:15 UTC10m
2026-05-16 KAP22 ACK → BOS May 16, 16:55 UTCMay 16, 17:05 UTC10m
2026-05-16 KAP22 ACK → BOS May 16, 13:25 UTCMay 16, 13:35 UTC10m
2026-05-16 KAP22 ACK → BOS May 16, 10:40 UTCMay 16, 11:35 UTC55m
2026-05-15 KAP22 ACK → BOS May 15, 21:45 UTCMay 15, 21:55 UTC10m
2026-05-15 KAP22 ACK → BOS May 15, 20:55 UTCMay 15, 21:10 UTC15m
2026-05-15 KAP22 ACK → BOS May 15, 19:30 UTCMay 15, 19:40 UTC10m
2026-05-15 KAP22 ACK → BOS May 15, 18:05 UTCMay 15, 18:35 UTC30m

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

Mode-S A8FFA1 frequently asked

What is Mode-S code A8FFA1?
A8FFA1 is an ICAO 24-bit transponder address. Allocated to United States. Assigned to N67909.
Where is Mode-S A8FFA1 registered?
Mode-S code A8FFA1 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 A8FFA1 broadcasting right now?
No active broadcast right now. Last signal was 6h ago.
Hex, octal, and decimal Mode-S codes: what's the difference?
The same 24-bit identifier expressed in different bases: hex A8FFA1, octal 52177641, decimal 11,075,489.
What flights does A8FFA1 operate?
Mode-S A8FFA1 has broadcast 5 distinct callsigns, including KAP22, KAP615, KAP394, KAPT787, KAP916.