sensors Mode-S transponder
AD5A4F
ICAO 24-bit transponder address · allocated to United States
Currently assigned to N96FE · DASSAULT Falcon 900 · operated by ALLEGHENY ENERGY SERVICE CORP
- Hex
- AD5A4F
- Octal
- 53255117
- Decimal
- 11,360,847
- Country
- US
- Tail
- N96FE
- Type
- F900
- Flights observed
- 62
- Distinct callsigns
- 1
- Country
- US
- Last broadcast
- Jul 22, 21:50 UTC
Last known position
Country allocation
The ICAO 24-bit address AD5A4F 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 |
|---|---|---|---|
| N96FE | - | 62 | 2026-07-22 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-22 | N96FE | RDG → CAK | Jul 22, 21:00 UTC | Jul 22, 21:50 UTC | 50m |
| 2026-07-22 | N96FE | - | Jul 22, 12:00 UTC | Jul 22, 12:45 UTC | 45m |
| 2026-07-21 | N96FE | IAD → CAK | Jul 21, 15:25 UTC | Jul 21, 16:45 UTC | 1h 20m |
| 2026-07-20 | N96FE | - | Jul 20, 21:40 UTC | Jul 20, 22:25 UTC | 45m |
| 2026-07-14 | N96FE | - | Jul 14, 22:10 UTC | Jul 14, 22:45 UTC | 34m |
| 2026-07-14 | N96FE | - | Jul 14, 20:30 UTC | Jul 14, 21:30 UTC | 1h 0m |
| 2026-07-14 | N96FE | - | Jul 14, 15:35 UTC | Jul 14, 16:50 UTC | 1h 15m |
| 2026-07-14 | N96FE | - | Jul 14, 14:30 UTC | Jul 14, 15:00 UTC | 30m |
| 2026-07-12 | N96FE | - | Jul 12, 15:01 UTC | Jul 12, 15:50 UTC | 50m |
| 2026-07-08 | N96FE | - | Jul 8, 16:15 UTC | Jul 8, 16:55 UTC | 40m |
| 2026-06-30 | N96FE | - | Jun 30, 21:10 UTC | Jun 30, 21:55 UTC | 45m |
| 2026-06-30 | N96FE | - | Jun 30, 12:05 UTC | Jun 30, 12:45 UTC | 40m |
| 2026-06-30 | N96FE | - | Jun 30, 01:19 UTC | Jun 30, 02:20 UTC | 1h 1m |
| 2026-06-29 | N96FE | CAK → MMU | Jun 29, 20:35 UTC | Jun 29, 21:34 UTC | 1h 0m |
| 2026-06-23 | N96FE | TEB → CAK | Jun 23, 20:24 UTC | Jun 23, 21:34 UTC | 1h 10m |
| 2026-06-22 | N96FE | CAK → TEB | Jun 22, 15:59 UTC | Jun 22, 17:04 UTC | 1h 5m |
| 2026-06-18 | N96FE | - | Jun 18, 20:00 UTC | Jun 18, 20:35 UTC | 35m |
| 2026-06-18 | N96FE | - | Jun 18, 19:45 UTC | Jun 18, 19:55 UTC | 10m |
| 2026-06-18 | N96FE | CAK → RDG | Jun 18, 18:25 UTC | Jun 18, 19:05 UTC | 40m |
| 2026-06-17 | N96FE | RDG → CAK | Jun 17, 11:15 UTC | Jun 17, 12:00 UTC | 45m |
| 2026-06-17 | N96FE | CAK → RDG | Jun 17, 09:30 UTC | Jun 17, 10:10 UTC | 40m |
| 2026-06-15 | N96FE | - | Jun 15, 21:14 UTC | Jun 15, 22:00 UTC | 45m |
| 2026-06-15 | N96FE | CAK → IAD | Jun 15, 16:09 UTC | Jun 15, 16:55 UTC | 45m |
| 2026-06-12 | N96FE | FTY → CAK | Jun 12, 16:40 UTC | Jun 12, 17:55 UTC | 1h 15m |
| 2026-06-08 | N96FE | - | Jun 8, 19:15 UTC | Jun 8, 20:35 UTC | 1h 20m |
| 2026-06-04 | N96FE | EWR → CAK | Jun 4, 16:00 UTC | Jun 4, 16:55 UTC | 55m |
| 2026-06-03 | N96FE | - | Jun 3, 17:15 UTC | Jun 3, 18:20 UTC | 1h 5m |
| 2026-06-03 | N96FE | EWR → CAK | Jun 3, 14:15 UTC | Jun 3, 15:05 UTC | 50m |
| 2026-06-03 | N96FE | - | Jun 3, 12:20 UTC | Jun 3, 13:30 UTC | 1h 10m |
| 2026-06-02 | N96FE | - | Jun 2, 22:00 UTC | Jun 2, 22:40 UTC | 40m |
| 2026-06-02 | N96FE | CAK → RDG | Jun 2, 20:40 UTC | Jun 2, 21:30 UTC | 50m |
| 2026-06-02 | N96FE | - | Jun 2, 12:35 UTC | Jun 2, 13:20 UTC | 45m |
| 2026-06-02 | N96FE | CAK → RDG | Jun 2, 11:15 UTC | Jun 2, 12:00 UTC | 45m |
| 2026-06-02 | N96FE | LAS → CAK | Jun 2, 00:40 UTC | Jun 2, 04:15 UTC | 3h 35m |
| 2026-05-31 | N96FE | CAK → LAS | May 31, 19:00 UTC | May 31, 23:10 UTC | 4h 10m |
| 2026-05-28 | N96FE | - | May 28, 20:15 UTC | May 28, 21:00 UTC | 45m |
| 2026-05-28 | N96FE | CAK → MRB | May 28, 11:30 UTC | May 28, 12:05 UTC | 35m |
| 2026-05-21 | N96FE | FTY → CAK | May 21, 21:50 UTC | May 21, 23:00 UTC | 1h 10m |
| 2026-05-20 | N96FE | CAK → FTY | May 20, 18:40 UTC | May 20, 19:55 UTC | 1h 15m |
| 2026-05-18 | N96FE | - | May 18, 16:55 UTC | May 18, 20:30 UTC | 3h 34m |
| 2026-05-18 | N96FE | - | May 18, 15:35 UTC | May 18, 16:20 UTC | 45m |
| 2026-05-18 | N96FE | - | May 18, 11:25 UTC | May 18, 14:00 UTC | 2h 35m |
| 2026-05-14 | N96FE | TEB → CAK | May 14, 19:10 UTC | May 14, 20:55 UTC | 1h 45m |
| 2026-05-14 | N96FE | CAK → TEB | May 14, 12:15 UTC | May 14, 13:15 UTC | 1h 0m |
| 2026-05-11 | N96FE | CAK → CAK | May 11, 12:45 UTC | May 11, 13:30 UTC | 45m |
| 2026-05-07 | N96FE | - | May 7, 15:35 UTC | May 7, 16:30 UTC | 55m |
| 2026-05-07 | N96FE | - | May 7, 10:55 UTC | May 7, 12:10 UTC | 1h 15m |
| 2026-05-06 | N96FE | - | May 6, 21:45 UTC | May 6, 22:55 UTC | 1h 10m |
| 2026-05-06 | N96FE | - | May 6, 18:50 UTC | May 6, 19:25 UTC | 35m |
| 2026-05-05 | N96FE | - | May 5, 22:05 UTC | May 5, 22:50 UTC | 45m |
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 N96FE page for operator, model, and routing details .