Long landing rollout — QXE2074

70S · 34

2026-06-18 22:26 UTC· KSEA → 70S· HORIZON AIR INDUSTRIES INC· E75L

▶ Replay 📊 Analyse

QXE2074 (Horizon AIR Industries) was operating from KSEA to 70S on 2026-06-18. SkyMeter detected a long landing rollout at Mead Flying Service Airport (70S) on runway 34 at 22:26 UTC. Trace data at the event: 2349 ft AGL, 0 kt GS. METAR at the time reported 6 kt wind, 5 kt crosswind component. A long landing rollout is detected when ground deceleration after touchdown is below the per-runway P10 envelope. It is an observational measure of rollout efficiency, not a runway-exit incident. Detection algorithm and known limitations: see SkyMeter methodology.

Active FAA TFR during this flight

Source: FAA TFR archive (hourly snapshot)
  • SECURITY6/4011 2026-06-01 07:00Z – 2026-07-21 06:59Z SFC–400 ft

    BELLEVUE, WA, Monday, June 1, 2026 through Monday, July 20, 2026 Local

    View FAA NOTAM →
  • SECURITY6/4033 2026-06-01 07:00Z – 2026-07-21 06:59Z SFC–400 ft

    RENTON, WA, Monday, June 1, 2026 through Monday, July 20, 2026 Local

    View FAA NOTAM →
  • SECURITY6/4034 2026-06-01 07:00Z – 2026-07-21 06:59Z SFC–400 ft

    Renton, WA, Monday, June 1, 2026 through Monday, July 20, 2026 Local

    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 34
  • 2349 ft AGL at event
  • 0 kt ground speed
  • 0 fpm vertical
  • 6 kt wind
  • 5 kt crosswind component

Flight context

  • QXE2074
  • Horizon AIR Industries
  • E75L
  • KSEA → 70S
  • 2026-06-18 22:26 UTC
  • 70S runway 34

All events on this flight

Long landing rollout 22:26:50 UTC · 70S runway 34 · 2,349 ft AGL · 0 kt GS
Long landing rollout 22:26:50 UTC · 70S runway 34 · 2,349 ft AGL · 0 kt GS

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

SkyMeter · trace data observed via ADS-B· 70S