EmergencyDescent — ATN3434
2026-07-11 14:10 UTC· PHLI → KSMF· AMAZON.COM SERVICES LLC· B763
ATN3434 (Amazon.Com Services) was operating from PHLI to KSMF on 2026-07-11. SkyMeter detected a emergencydescent at 14:10 UTC. Trace data at the event: 32436 ft AGL, 490 kt GS. METAR at the time reported 19 kt wind, 13 kt crosswind component. Detection algorithm and known limitations: see SkyMeter methodology.
Active FAA TFR during this flight
Source: FAA TFR archive (hourly snapshot)- SECURITY6/4052 2026-06-01 07:00Z – 2026-07-21 06:59Z SFC–400 ft
San Jose, CA, Monday, June 1, 2026 through Monday, July 20, 2026 Local
View FAA NOTAM → - SECURITY6/4054 2026-06-01 07:00Z – 2026-07-21 06:59Z SFC–400 ft
San Jose, CA, Monday, June 1, 2026 through Monday, July 20, 2026 Local
View FAA NOTAM → - SECURITY6/4060 2026-06-01 07:00Z – 2026-07-21 06:59Z SFC–400 ft
Oakland, CA, Monday, June 1, 2026 through Monday, July 20, 2026 Local
View FAA NOTAM → - SECURITY6/4061 2026-06-01 07:00Z – 2026-07-21 06:59Z SFC–400 ft
BERKLEY, CA, Monday, June 1, 2026 through Tuesday, July 21, 2026 Local
View FAA NOTAM → - SECURITY6/4204 2026-06-01 07:00Z – 2026-07-21 06:59Z SFC–400 ft
Santa Clara, CA, Monday, June 1, 2026 through Monday, July 20, 2026 Local
View FAA NOTAM → - SECURITY6/7983 2026-07-05 14:07Z – 2026-07-21 06:59Z SFC–400 ft
San Jose, CA
View FAA NOTAM → - SECURITY6/7984 2026-07-05 14:07Z – 2026-07-21 06:59Z SFC–400 ft
Oakland, CA
View FAA NOTAM → - SECURITY6/7985 2026-07-05 14:07Z – 2026-07-21 06:59Z SFC–400 ft
San Jose, CA
View FAA NOTAM →
SkyMeter cross-referenced this flight against FAA-published TFRs that were active during its window and within its geographic bounding box. Overlap doesn't necessarily mean violation — the aircraft may have been outside the TFR’s precise polygon or flying under air-traffic-control coordination.
Pilot review data
- 32436 ft AGL at event
- 490 kt ground speed
- 0 fpm vertical
- 19 kt wind
- 13 kt crosswind component
Flight context
- ATN3434
- Amazon.Com Services
- B763
- PHLI → KSMF
- 2026-07-11 14:10 UTC
Automated analysis. Events shown on this page (such as go-around, unstable approach, or runway events) are heuristic classifications produced by algorithms from publicly broadcast ADS-B data. They are intended to surface flights of interest for further review — they are not findings of fact, and they do not determine pilot fault, regulatory compliance, or the cause of any occurrence. Coverage gaps and sensor noise can affect accuracy. Only the relevant civil aviation authority or accident investigation body can make official determinations. How we detect events · Dispute or correct this data