Not currently tracked · last seen 22h ago
- Flights observed
- 39
- Avg flight time
- 18m
- Typical route
- -
- Last seen
- 22h ago
Last known area
Recent flights last 39
| Date | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|
| 2026-06-03 | - | Jun 3, 20:20 UTC | Jun 3, 21:00 UTC | 40m |
| 2026-06-03 | - | Jun 3, 19:25 UTC | Jun 3, 19:35 UTC | 10m |
| 2026-06-03 | - | Jun 3, 18:20 UTC | Jun 3, 18:30 UTC | 10m |
| 2026-06-03 | - | Jun 3, 18:05 UTC | Jun 3, 18:10 UTC | 5m |
| 2026-06-03 | - | Jun 3, 17:50 UTC | Jun 3, 18:00 UTC | 10m |
| 2026-06-03 | - | Jun 3, 17:25 UTC | Jun 3, 17:40 UTC | 15m |
| 2026-06-03 | - | Jun 3, 17:05 UTC | Jun 3, 17:20 UTC | 15m |
| 2026-05-26 | - | May 26, 19:50 UTC | May 26, 20:24 UTC | 35m |
| 2026-05-26 | - | May 26, 19:10 UTC | May 26, 19:34 UTC | 25m |
| 2026-05-26 | - | May 26, 17:39 UTC | May 26, 17:50 UTC | 10m |
| 2026-05-26 | - | May 26, 17:04 UTC | May 26, 17:20 UTC | 15m |
| 2026-05-12 | - | May 12, 20:35 UTC | May 12, 21:30 UTC | 55m |
| 2026-05-12 | - | May 12, 18:35 UTC | May 12, 18:50 UTC | 15m |
| 2026-05-12 | - | May 12, 17:35 UTC | May 12, 18:20 UTC | 45m |
| 2026-05-12 | - | May 12, 17:20 UTC | May 12, 17:30 UTC | 10m |
| 2026-05-12 | - | May 12, 16:20 UTC | May 12, 16:35 UTC | 15m |
| 2026-05-12 | - | May 12, 16:05 UTC | May 12, 16:15 UTC | 10m |
| 2026-05-07 | - | May 7, 20:25 UTC | May 7, 20:40 UTC | 15m |
| 2026-05-07 | - | May 7, 19:30 UTC | May 7, 20:20 UTC | 50m |
| 2026-05-07 | - | May 7, 16:35 UTC | May 7, 17:00 UTC | 25m |
| 2026-05-07 | - | May 7, 16:25 UTC | May 7, 16:30 UTC | 5m |
| 2026-05-01 | - | May 1, 21:10 UTC | May 1, 21:20 UTC | 10m |
| 2026-05-01 | - | May 1, 20:45 UTC | May 1, 20:55 UTC | 10m |
| 2026-05-01 | - | May 1, 20:15 UTC | May 1, 20:30 UTC | 15m |
| 2026-05-01 | - | May 1, 19:00 UTC | May 1, 19:40 UTC | 40m |
| 2026-05-01 | - | May 1, 18:15 UTC | May 1, 18:45 UTC | 30m |
| 2026-05-01 | - | May 1, 18:00 UTC | May 1, 18:10 UTC | 10m |
| 2026-05-01 | - | May 1, 17:40 UTC | May 1, 17:45 UTC | 5m |
| 2026-05-01 | - | May 1, 16:30 UTC | May 1, 16:35 UTC | 5m |
| 2026-04-26 | - | Apr 26, 17:20 UTC | Apr 26, 17:25 UTC | 5m |
| 2026-04-26 | - | Apr 26, 17:10 UTC | Apr 26, 17:15 UTC | 5m |
| 2026-04-21 | - | Apr 21, 19:05 UTC | Apr 21, 19:45 UTC | 40m |
| 2026-04-21 | - | Apr 21, 18:40 UTC | Apr 21, 19:00 UTC | 20m |
| 2026-04-21 | - | Apr 21, 16:10 UTC | Apr 21, 16:15 UTC | 5m |
| 2026-04-14 | - | Apr 14, 18:55 UTC | Apr 14, 19:10 UTC | 15m |
| 2026-04-14 | - | Apr 14, 18:10 UTC | Apr 14, 18:15 UTC | 5m |
| 2026-04-14 | - | Apr 14, 17:45 UTC | Apr 14, 17:55 UTC | 10m |
| 2026-04-14 | - | Apr 14, 17:30 UTC | Apr 14, 17:40 UTC | 10m |
| 2026-04-14 | - | Apr 14, 17:10 UTC | Apr 14, 17:20 UTC | 10m |
Specifications
| Registration | N33YA |
| Operator | BLIEDEN IRA A |
| Mode-S code | A3959D · 50712635 (octal) |
Looking for transponder-level data? View the Mode-S A3959D page for country allocation, callsign history, and ADS-B signal details.
N33YA frequently asked
Who operates N33YA?
N33YA is operated by BLIEDEN IRA A.
What is the Mode-S transponder code for N33YA?
N33YA broadcasts on Mode-S (ICAO 24-bit) address A3959D (octal 50712635). View the transponder page.
Where is N33YA right now?
N33YA is not currently being tracked; last seen 22h ago.