BOE326 (Boeing) had departed KPAE on 2026-06-16. SkyMeter detected a return to field at Snohomish County (Paine Field) Airport (KPAE) on runway 34L at 18:01 UTC. Peak cruise altitude FL412, turnaround area near Wahkiakum, US. METAR at the time reported 0 kt wind, 16,093 m visibility. Detection algorithm and known limitations: see SkyMeter methodology.
Active FAA TFR during this flight
Source: FAA TFR archive (hourly snapshot)- SECURITY6/4013 2026-06-01 07:00Z – 2026-07-21 06:59Z SFC–400 ft
Seattle, WA, Monday, June 1, 2026 through Monday, July 20, 2026 Local
View FAA NOTAM → - SECURITY6/4040 2026-06-01 07:00Z – 2026-07-21 06:59Z SFC–400 ft
Portland, OR, Monday, June 1, 2026 through Monday, July 20, 2026 Local
View FAA NOTAM → - SECURITY6/4041 2026-06-01 07:00Z – 2026-07-21 06:59Z SFC–400 ft
PORTLAND, OR, Monday, June 1, 2026 through Monday, July 20, 2026 Local
View FAA NOTAM → - HAZARDS6/5042 2026-06-02 19:48Z – 2026-06-16 23:59Z SFC–1,000 ft
LONGVIEW, WA, Tuesday, June 2, 2026 through Tuesday, June 16, 2026 UTC
View FAA NOTAM → - HAZARDS6/5717 2026-06-04 19:29Z – 2026-06-16 23:59Z SFC–1,000 ft
LONGVIEW, WA, Thursday, June 4, 2026 through Tuesday, June 16, 2026 UTC
View FAA NOTAM → - HAZARDS6/7699 2026-06-11 20:16Z – 2026-06-16 23:59Z SFC–1,000 ft
LONGVIEW, WA, Thursday, June 11, 2026 through Tuesday, June 16, 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
- Runway 34L
- 41224 ft AGL at event
- 510 kt ground speed
- 0 fpm vertical
- 0 kt wind
- 0 kt crosswind component
- 16,093 m visibility
- KPAE 152153Z 24009KT 10SM CLR 22/13 A3013 RMK AO2 SLP202 T02170133
Flight context
- BOE326
- Boeing
- B763
- KPAE → KPAE
- 2026-06-16 18:01 UTC
- KPAE runway 34L
All events on this flight
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