sensors Mode-S transponder
A3E61A
ICAO 24-bit transponder address · allocated to United States
Currently assigned to N350PH · BOMBARDIER BD-100 Challenger 350 · operated by PAMPLEMOUSSE CORP
- Hex
- A3E61A
- Octal
- 50763032
- Decimal
- 10,741,274
- Country
- US
- Tail
- N350PH
- Type
- CL35
- Flights observed
- 63
- Distinct callsigns
- 1
- Country
- US
- Last broadcast
- Jul 26, 19:30 UTC
Last known position
Country allocation
The ICAO 24-bit address A3E61A 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 |
|---|---|---|---|
| N350PH | - | 63 | 2026-07-26 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-26 | N350PH | - | Jul 26, 16:10 UTC | Jul 26, 19:30 UTC | 3h 20m |
| 2026-07-25 | N350PH | - | Jul 25, 20:45 UTC | Jul 25, 23:05 UTC | 2h 20m |
| 2026-07-21 | N350PH | - | Jul 21, 19:55 UTC | Jul 21, 21:50 UTC | 1h 55m |
| 2026-07-20 | N350PH | - | Jul 20, 21:40 UTC | Jul 21, 00:30 UTC | 2h 49m |
| 2026-07-19 | N350PH | - | Jul 19, 00:00 UTC | Jul 19, 04:20 UTC | 4h 20m |
| 2026-07-18 | N350PH | - | Jul 18, 19:00 UTC | Jul 18, 21:40 UTC | 2h 40m |
| 2026-07-18 | N350PH | - | Jul 18, 14:05 UTC | Jul 18, 17:10 UTC | 3h 5m |
| 2026-07-17 | N350PH | - | Jul 17, 20:00 UTC | Jul 17, 22:00 UTC | 2h 0m |
| 2026-07-17 | N350PH | - | Jul 17, 16:04 UTC | Jul 17, 17:44 UTC | 1h 40m |
| 2026-07-17 | N350PH | - | Jul 17, 15:35 UTC | Jul 17, 16:00 UTC | 25m |
| 2026-07-15 | N350PH | - | Jul 15, 13:10 UTC | Jul 15, 15:15 UTC | 2h 5m |
| 2026-07-12 | N350PH | - | Jul 12, 19:50 UTC | Jul 12, 22:10 UTC | 2h 20m |
| 2026-07-11 | N350PH | - | Jul 11, 15:25 UTC | Jul 11, 18:35 UTC | 3h 10m |
| 2026-07-10 | N350PH | - | Jul 10, 17:35 UTC | Jul 10, 21:30 UTC | 3h 56m |
| 2026-07-09 | N350PH | TMB → HPN | Jul 9, 13:35 UTC | Jul 9, 16:10 UTC | 2h 35m |
| 2026-07-08 | N350PH | - | Jul 8, 21:05 UTC | Jul 8, 22:35 UTC | 1h 30m |
| 2026-07-08 | N350PH | - | Jul 8, 20:35 UTC | Jul 8, 21:00 UTC | 25m |
| 2026-07-05 | N350PH | - | Jul 5, 20:20 UTC | Jul 5, 22:15 UTC | 1h 55m |
| 2026-07-04 | N350PH | - | Jul 4, 19:05 UTC | Jul 4, 22:45 UTC | 3h 40m |
| 2026-07-03 | N350PH | - | Jul 3, 18:10 UTC | Jul 3, 21:55 UTC | 3h 45m |
| 2026-07-03 | N350PH | - | Jul 3, 14:30 UTC | Jul 3, 16:35 UTC | 2h 5m |
| 2026-07-02 | N350PH | - | Jul 2, 14:50 UTC | Jul 2, 18:35 UTC | 3h 45m |
| 2026-07-01 | N350PH | - | Jul 1, 20:40 UTC | Jul 2, 18:35 UTC | 21h 55m |
| 2026-07-01 | N350PH | - | Jul 1, 18:35 UTC | Jul 2, 18:30 UTC | 23h 55m |
| 2026-07-01 | N350PH | - | Jul 1, 17:35 UTC | Jul 2, 16:30 UTC | 22h 55m |
| 2026-06-29 | N350PH | TPA → TMB | Jun 29, 14:50 UTC | Jun 29, 15:30 UTC | 40m |
| 2026-06-28 | N350PH | TMB → TPA | Jun 28, 17:25 UTC | Jun 28, 18:05 UTC | 40m |
| 2026-06-27 | N350PH | - | Jun 27, 18:20 UTC | Jun 27, 20:24 UTC | 2h 5m |
| 2026-06-23 | N350PH | - | Jun 23, 19:59 UTC | Jun 23, 21:54 UTC | 1h 55m |
| 2026-06-10 | N350PH | - | Jun 10, 18:50 UTC | Jun 10, 21:05 UTC | 2h 15m |
| 2026-06-03 | N350PH | - | Jun 3, 13:10 UTC | Jun 3, 15:50 UTC | 2h 40m |
| 2026-06-02 | N350PH | - | Jun 2, 14:15 UTC | Jun 2, 17:10 UTC | 2h 55m |
| 2026-05-30 | N350PH | - | May 30, 19:45 UTC | May 30, 22:30 UTC | 2h 45m |
| 2026-05-30 | N350PH | - | May 30, 17:15 UTC | May 30, 18:15 UTC | 1h 0m |
| 2026-05-30 | N350PH | - | May 30, 15:20 UTC | May 30, 15:35 UTC | 15m |
| 2026-05-25 | N350PH | - | May 25, 20:30 UTC | May 25, 22:34 UTC | 2h 5m |
| 2026-05-25 | N350PH | - | May 25, 16:45 UTC | May 25, 19:25 UTC | 2h 40m |
| 2026-05-22 | N350PH | - | May 22, 13:10 UTC | May 22, 15:45 UTC | 2h 35m |
| 2026-05-21 | N350PH | - | May 21, 18:35 UTC | May 21, 20:35 UTC | 2h 0m |
| 2026-05-20 | N350PH | - | May 20, 18:15 UTC | May 20, 22:40 UTC | 4h 25m |
| 2026-05-19 | N350PH | - | May 19, 14:20 UTC | May 19, 21:25 UTC | 7h 5m |
| 2026-05-18 | N350PH | - | May 18, 16:40 UTC | May 18, 18:35 UTC | 1h 54m |
| 2026-05-18 | N350PH | - | May 18, 00:40 UTC | May 18, 03:20 UTC | 2h 40m |
| 2026-05-17 | N350PH | - | May 17, 21:05 UTC | May 17, 23:55 UTC | 2h 50m |
| 2026-05-17 | N350PH | - | May 17, 15:01 UTC | May 17, 17:10 UTC | 2h 10m |
| 2026-05-14 | N350PH | - | May 14, 00:35 UTC | May 14, 12:40 UTC | 12h 5m |
| 2026-05-13 | N350PH | - | May 13, 21:00 UTC | May 13, 23:10 UTC | 2h 10m |
| 2026-05-12 | N350PH | - | May 12, 18:25 UTC | May 12, 20:20 UTC | 1h 55m |
| 2026-05-12 | N350PH | - | May 12, 12:55 UTC | May 12, 15:01 UTC | 2h 5m |
| 2026-05-10 | N350PH | - | May 10, 17:15 UTC | May 10, 17:45 UTC | 30m |
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 N350PH page for operator, model, and routing details .