EmergencyDescent — ATN3434
2026-09-01 14:03 UTC· PHLI → KSMF· CARGO AIRCRAFT MANAGEMENT INC· B763
ATN3434 (Cargo Aircraft Management) was operating from PHLI to KSMF on 2026-09-01. SkyMeter detected a emergencydescent at 14:03 UTC. Trace data at the event: 38288 ft AGL, 521 kt GS. METAR at the time reported 6 kt wind, 4 kt crosswind component. Detection algorithm and known limitations: see SkyMeter methodology.
Active FAA TFR during this flight
Source: FAA TFR archive (hourly snapshot)- SECURITY6/6491 2026-07-20 07:01Z – 2026-09-16 06:59Z SFC–1,499 ft
Concord, CA, Monday, July 20, 2026 through Tuesday, September 15, 2026 Local
View FAA NOTAM → - HAZARDS6/8070 2026-08-26 03:00Z – 2026-09-10 03:00Z SFC–8,500 ft
8NM SE BIG SUR, CA, Wednesday, August 26, 2026 through Thursday, September 10, 2026 UTC
View FAA NOTAM → - UAS PUBLIC GATHERING6/7555 2026-08-29 01:00Z – 2026-09-02 06:59Z SFC–400 ft
Santa Clara, CA, Saturday, August 29, 2026 through Wednesday, September 2, 2026 UTC
View FAA NOTAM → - UAS PUBLIC GATHERING6/7569 2026-08-29 01:00Z – 2026-09-02 06:59Z SFC–400 ft
Santa Clara, CA, Saturday, August 29, 2026 through Wednesday, September 2, 2026 UTC
View FAA NOTAM → - HAZARDS6/9187 2026-08-30 13:00Z – 2026-09-13 03:00Z SFC–8,500 ft
20NM SW KING CITY, CA, Sunday, August 30, 2026 through Sunday, September 13, 2026 UTC
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
- 38288 ft AGL at event
- 521 kt ground speed
- 0 fpm vertical
- 6 kt wind
- 4 kt crosswind component
Flight context
- ATN3434
- Cargo Aircraft Management
- B763
- PHLI → KSMF
- 2026-09-01 14:03 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