Not currently tracked · last seen 2d ago
- Flights observed
- 36
- Avg flight time
- 1h 27m
- Typical route
- DVT → CGZ
- Last seen
- 2d ago
Last known area
Recent flights last 36
| Date | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|
| 2026-07-02 | - | Jul 2, 11:50 UTC | Jul 2, 12:55 UTC | 1h 5m |
| 2026-07-02 | - | Jul 2, 10:00 UTC | Jul 2, 11:10 UTC | 1h 10m |
| 2026-06-29 | DVT → DVT | Jun 29, 11:04 UTC | Jun 29, 13:00 UTC | 1h 55m |
| 2026-06-28 | - | Jun 28, 13:34 UTC | Jun 28, 14:34 UTC | 1h 0m |
| 2026-06-28 | DVT → CGZ | Jun 28, 10:39 UTC | Jun 28, 12:44 UTC | 2h 5m |
| 2026-06-23 | - | Jun 23, 15:40 UTC | Jun 23, 16:44 UTC | 1h 5m |
| 2026-06-23 | DVT → CGZ | Jun 23, 11:40 UTC | Jun 23, 14:49 UTC | 3h 10m |
| 2026-06-19 | - | Jun 19, 14:29 UTC | Jun 19, 15:39 UTC | 1h 10m |
| 2026-06-19 | - | Jun 19, 12:19 UTC | Jun 19, 13:59 UTC | 1h 40m |
| 2026-06-17 | - | Jun 17, 15:00 UTC | Jun 17, 16:05 UTC | 1h 5m |
| 2026-06-17 | - | Jun 17, 12:10 UTC | Jun 17, 14:20 UTC | 2h 10m |
| 2026-06-15 | - | Jun 15, 14:30 UTC | Jun 15, 15:50 UTC | 1h 20m |
| 2026-06-15 | - | Jun 15, 12:30 UTC | Jun 15, 13:54 UTC | 1h 25m |
| 2026-06-12 | - | Jun 12, 14:50 UTC | Jun 12, 16:15 UTC | 1h 25m |
| 2026-06-12 | - | Jun 12, 12:45 UTC | Jun 12, 14:10 UTC | 1h 25m |
| 2026-06-10 | - | Jun 10, 15:45 UTC | Jun 10, 16:40 UTC | 55m |
| 2026-06-10 | - | Jun 10, 13:05 UTC | Jun 10, 13:20 UTC | 15m |
| 2026-06-05 | - | Jun 5, 15:10 UTC | Jun 5, 16:15 UTC | 1h 5m |
| 2026-06-05 | - | Jun 5, 12:40 UTC | Jun 5, 14:20 UTC | 1h 40m |
| 2026-06-01 | - | Jun 1, 16:20 UTC | Jun 1, 17:35 UTC | 1h 15m |
| 2026-06-01 | - | Jun 1, 13:30 UTC | Jun 1, 15:30 UTC | 2h 0m |
| 2026-05-23 | - | May 23, 15:55 UTC | May 23, 17:00 UTC | 1h 5m |
| 2026-05-23 | - | May 23, 13:10 UTC | May 23, 14:50 UTC | 1h 40m |
| 2026-05-21 | - | May 21, 15:30 UTC | May 21, 16:30 UTC | 1h 0m |
| 2026-05-21 | - | May 21, 12:20 UTC | May 21, 14:10 UTC | 1h 50m |
| 2026-05-19 | - | May 19, 08:35 UTC | May 19, 09:50 UTC | 1h 15m |
| 2026-05-19 | - | May 19, 05:25 UTC | May 19, 07:50 UTC | 2h 25m |
| 2026-05-03 | - | May 3, 07:50 UTC | May 3, 08:40 UTC | 50m |
| 2026-05-03 | - | May 3, 04:50 UTC | May 3, 07:00 UTC | 2h 10m |
| 2026-04-29 | - | Apr 29, 08:20 UTC | Apr 29, 09:15 UTC | 56m |
| 2026-04-29 | - | Apr 29, 04:49 UTC | Apr 29, 07:35 UTC | 2h 45m |
| 2026-04-19 | - | Apr 19, 07:20 UTC | Apr 19, 08:05 UTC | 45m |
| 2026-04-19 | - | Apr 19, 04:55 UTC | Apr 19, 06:45 UTC | 1h 50m |
| 2026-04-16 | - | Apr 16, 07:29 UTC | Apr 16, 08:35 UTC | 1h 5m |
| 2026-04-16 | - | Apr 16, 05:09 UTC | Apr 16, 06:49 UTC | 1h 40m |
| 2026-04-16 | - | Apr 16, 04:14 UTC | Apr 16, 05:05 UTC | 50m |
Specifications
| Registration | N353EA |
| Operator | PENG JONATHAN |
| Mode-S code | A3F057 · 50770127 (octal) |
Looking for transponder-level data? View the Mode-S A3F057 page for country allocation, callsign history, and ADS-B signal details.
N353EA frequently asked
Who operates N353EA?
N353EA is operated by PENG JONATHAN.
What is the Mode-S transponder code for N353EA?
N353EA broadcasts on Mode-S (ICAO 24-bit) address A3F057 (octal 50770127). View the transponder page.
What route does N353EA typically fly?
N353EA most frequently flies between DVT and CGZ based on observed flights.
Where is N353EA right now?
N353EA is not currently being tracked; last seen 2d ago.