Long landing rollout — QXE2368
K6S8 · 142026-06-23 20:51 UTC· KPDX → K6S8· HORIZON AIR INDUSTRIES INC· E75L
QXE2368 (Horizon AIR Industries) was operating from KPDX to K6S8 on 2026-06-23. SkyMeter detected a long landing rollout at Laurel Municipal Airport (K6S8) on runway 14 at 20:51 UTC. Trace data at the event: 3553 ft AGL, 13 kt GS. METAR at the time reported 4 kt wind, 4 kt crosswind component, 16,093 m visibility. 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/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 → - HAZARDS6/8221 2026-06-14 20:07Z – 2026-06-28 03:00Z SFC–6,000 ft
22NM SE RICHLAND, WA, Sunday, June 14, 2026 through Sunday, June 28, 2026 UTC
View FAA NOTAM → - HAZARDS6/9121 2026-06-18 13:00Z – 2026-07-01 05:00Z SFC–7,000 ft
10NM SE PENDLETON, OR, Thursday, June 18, 2026 through Wednesday, July 1, 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 14
- 3553 ft AGL at event
- 13 kt ground speed
- 0 fpm vertical
- 4 kt wind
- 4 kt crosswind component
- 16,093 m visibility
- METAR K6S8 180555Z AUTO 10SM CLR 15/08 A3007 RMK A01
Flight context
- QXE2368
- Horizon AIR Industries
- E75L
- KPDX → K6S8
- 2026-06-23 20:51 UTC
- K6S8 runway 14
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