sensors Mode-S transponder
A44EE3
ICAO 24-bit transponder address · allocated to United States
Currently assigned to N377MD · BOMBARDIER BD-100 Challenger 300 · operated by CAMBRIA AVIATION LLC
- Hex
- A44EE3
- Octal
- 51047343
- Decimal
- 10,768,099
- Country
- US
- Tail
- N377MD
- Type
- CL30
- Flights observed
- 59
- Distinct callsigns
- 1
- Country
- US
- Last broadcast
- Jul 24, 01:50 UTC
Last known position
Country allocation
The ICAO 24-bit address A44EE3 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 |
|---|---|---|---|
| N377MD | - | 59 | 2026-07-24 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-24 | N377MD | - | Jul 24, 01:00 UTC | Jul 24, 01:50 UTC | 50m |
| 2026-07-23 | N377MD | - | Jul 23, 15:15 UTC | Jul 23, 16:15 UTC | 1h 0m |
| 2026-07-19 | N377MD | - | Jul 19, 03:40 UTC | Jul 19, 04:25 UTC | 45m |
| 2026-07-18 | N377MD | FCM → PIR | Jul 18, 22:55 UTC | Jul 18, 23:45 UTC | 50m |
| 2026-07-16 | N377MD | - | Jul 16, 16:40 UTC | Jul 16, 17:25 UTC | 45m |
| 2026-07-16 | N377MD | FCM → PIR | Jul 16, 15:00 UTC | Jul 16, 15:49 UTC | 50m |
| 2026-07-15 | N377MD | - | Jul 15, 17:50 UTC | Jul 15, 18:45 UTC | 55m |
| 2026-07-15 | N377MD | - | Jul 15, 14:35 UTC | Jul 15, 17:10 UTC | 2h 35m |
| 2026-07-13 | N377MD | - | Jul 13, 17:55 UTC | Jul 13, 20:20 UTC | 2h 25m |
| 2026-07-13 | N377MD | FCM → FSD | Jul 13, 17:15 UTC | Jul 13, 17:45 UTC | 30m |
| 2026-07-02 | N377MD | GRB → FCM | Jul 2, 23:50 UTC | Jul 3, 00:40 UTC | 50m |
| 2026-07-02 | N377MD | - | Jul 2, 12:15 UTC | Jul 2, 23:35 UTC | 11h 20m |
| 2026-06-29 | N377MD | - | Jun 29, 13:04 UTC | Jun 29, 15:19 UTC | 2h 15m |
| 2026-06-27 | N377MD | IAD → FCM | Jun 27, 01:15 UTC | Jun 27, 03:34 UTC | 2h 20m |
| 2026-06-25 | N377MD | - | Jun 25, 16:55 UTC | Jun 25, 18:39 UTC | 1h 45m |
| 2026-06-24 | N377MD | - | Jun 24, 21:04 UTC | Jun 24, 22:45 UTC | 1h 40m |
| 2026-06-24 | N377MD | - | Jun 24, 12:14 UTC | Jun 24, 13:40 UTC | 1h 25m |
| 2026-06-16 | N377MD | - | Jun 16, 22:40 UTC | Jun 16, 23:10 UTC | 30m |
| 2026-06-16 | N377MD | IAD → FSD | Jun 16, 19:25 UTC | Jun 16, 22:30 UTC | 3h 6m |
| 2026-06-16 | N377MD | - | Jun 16, 12:00 UTC | Jun 16, 12:39 UTC | 40m |
| 2026-06-16 | N377MD | - | Jun 16, 10:15 UTC | Jun 16, 11:45 UTC | 1h 30m |
| 2026-06-16 | N377MD | - | Jun 16, 09:34 UTC | Jun 16, 10:04 UTC | 30m |
| 2026-06-08 | N377MD | - | Jun 8, 19:10 UTC | Jun 8, 21:25 UTC | 2h 15m |
| 2026-06-08 | N377MD | - | Jun 8, 14:35 UTC | Jun 8, 15:55 UTC | 1h 20m |
| 2026-06-08 | N377MD | - | Jun 8, 12:50 UTC | Jun 8, 14:25 UTC | 1h 35m |
| 2026-06-07 | N377MD | - | Jun 7, 17:30 UTC | Jun 7, 18:30 UTC | 1h 0m |
| 2026-06-07 | N377MD | - | Jun 7, 14:25 UTC | Jun 7, 15:25 UTC | 1h 0m |
| 2026-06-05 | N377MD | - | Jun 5, 18:20 UTC | Jun 5, 19:20 UTC | 1h 0m |
| 2026-06-05 | N377MD | - | Jun 5, 16:10 UTC | Jun 5, 17:20 UTC | 1h 10m |
| 2026-05-28 | N377MD | - | May 28, 23:40 UTC | May 29, 00:10 UTC | 30m |
| 2026-05-28 | N377MD | - | May 28, 23:00 UTC | May 28, 23:35 UTC | 35m |
| 2026-05-28 | N377MD | - | May 28, 15:10 UTC | May 28, 15:40 UTC | 30m |
| 2026-05-28 | N377MD | - | May 28, 14:10 UTC | May 28, 14:45 UTC | 35m |
| 2026-05-21 | N377MD | - | May 21, 21:30 UTC | May 21, 22:15 UTC | 45m |
| 2026-05-21 | N377MD | - | May 21, 19:25 UTC | May 21, 21:15 UTC | 1h 50m |
| 2026-05-20 | N377MD | - | May 20, 18:15 UTC | May 20, 20:05 UTC | 1h 50m |
| 2026-05-07 | N377MD | - | May 7, 19:25 UTC | May 7, 21:05 UTC | 1h 40m |
| 2026-05-07 | N377MD | - | May 7, 18:10 UTC | May 7, 19:15 UTC | 1h 5m |
| 2026-05-06 | N377MD | IAD → PDK | May 6, 22:10 UTC | May 7, 00:05 UTC | 1h 55m |
| 2026-05-06 | N377MD | CAK → IAD | May 6, 13:50 UTC | May 6, 14:35 UTC | 45m |
| 2026-05-06 | N377MD | - | May 6, 12:10 UTC | May 6, 13:40 UTC | 1h 30m |
| 2026-05-06 | N377MD | - | May 6, 11:25 UTC | May 6, 12:01 UTC | 35m |
| 2026-04-29 | N377MD | - | Apr 29, 04:29 UTC | Apr 29, 05:05 UTC | 35m |
| 2026-04-29 | N377MD | - | Apr 29, 01:50 UTC | Apr 29, 04:20 UTC | 2h 30m |
| 2026-04-28 | N377MD | - | Apr 28, 10:10 UTC | Apr 28, 12:05 UTC | 1h 55m |
| 2026-04-28 | N377MD | FSD → FCM | Apr 28, 08:50 UTC | Apr 28, 09:20 UTC | 30m |
| 2026-04-28 | N377MD | - | Apr 28, 08:00 UTC | Apr 28, 08:30 UTC | 30m |
| 2026-04-26 | N377MD | - | Apr 26, 17:35 UTC | Apr 26, 20:10 UTC | 2h 35m |
| 2026-04-21 | N377MD | - | Apr 21, 16:25 UTC | Apr 21, 19:10 UTC | 2h 45m |
| 2026-04-16 | N377MD | - | Apr 16, 01:10 UTC | Apr 16, 01:40 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 N377MD page for operator, model, and routing details .