Long landing rollout — N323NE
KUAO · 352026-07-05 19:41 UTC· KGEG → KUAO· NCW AIRCRAFT LLC, CWA AVIATION LLC· C560
N323NE (NCW Aircraft) was operating from KGEG to KUAO on 2026-07-05. SkyMeter detected a long landing rollout at Aurora State Airport (KUAO) on runway 35 at 19:41 UTC. Trace data at the event: 190 ft AGL, 6 kt GS, 0 fpm vertical. Approach stability score: 55/100. Scores in this band occur on roughly 10-15% of approaches at this runway, with multiple gates outside the per-runway envelope. METAR at the time reported 5 kt wind, 1 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/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 → - 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/9835 2026-06-22 19:50Z – 2026-07-06 04:00Z SFC–6,500 ft
30NM N MOSES LAKE, WA, Monday, June 22, 2026 through Monday, July 6, 2026 UTC
View FAA NOTAM → - HAZARDS6/9982 2026-06-23 02:31Z – 2026-07-07 04:00Z SFC–6,500 ft
30NM N MOSES LAKE, WA, Tuesday, June 23, 2026 through Tuesday, July 7, 2026 UTC
View FAA NOTAM → - HAZARDS6/0752 2026-06-26 14:00Z – 2026-07-07 02:00Z SFC–6,500 ft
30NM N MOSES LAKE, WA, Friday, June 26, 2026 through Tuesday, July 7, 2026 UTC
View FAA NOTAM → - HAZARDS6/1247 2026-06-28 22:17Z – 2026-07-10 16:00Z SFC–5,500 ft
7NM NW THE DALLES, OR, Sunday, June 28, 2026 through Friday, July 10, 2026 UTC
View FAA NOTAM → - HAZARDS6/1599 2026-06-29 19:20Z – 2026-07-06 01:00Z SFC–9,000 ft
26NM W YAKIMA, WA, Monday, June 29, 2026 through Monday, July 6, 2026 UTC
View FAA NOTAM → - HAZARDS6/1675 2026-06-29 21:09Z – 2026-07-13 04:00Z SFC–6,000 ft
75 ZSE AIRSPACE 13NM SE PASCO, WA, Monday, June 29, 2026 through Monday, July 13, 2026 UTC
View FAA NOTAM → - HAZARDS6/1598 2026-06-30 15:00Z – 2026-07-11 23:00Z SFC–5,500 ft
7NM NW THE DALLES, OR, Tuesday, June 30, 2026 through Saturday, July 11, 2026 UTC
View FAA NOTAM → - HAZARDS6/1787 2026-06-30 15:00Z – 2026-07-14 04:00Z SFC–6,000 ft
13NM SE PASCO, WA, Tuesday, June 30, 2026 through Tuesday, July 14, 2026 UTC
View FAA NOTAM → - HAZARDS6/2839 2026-07-03 22:52Z – 2026-07-11 03:00Z SFC–6,000 ft
5NM NE THE DALLES, OR, Friday, July 3, 2026 through Saturday, July 11, 2026 UTC
View FAA NOTAM → - HAZARDS6/2989 2026-07-05 17:35Z – 2026-07-20 05:00Z SFC–7,000 ft
15NM E PENDLETON, OR, Sunday, July 5, 2026 through Monday, July 20, 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 35
- 190 ft AGL at event
- 6 kt ground speed
- 0 fpm vertical
- Approach stability 55/100
- 5 kt wind
- 1 kt crosswind component
- 16,093 m visibility
- KUAO 162253Z 02009G19KT 10SM CLR 27/09 A3000 RMK AO2 SLP156 T02670094
Flight context
- N323NE
- NCW Aircraft
- C560
- KGEG → KUAO
- 2026-07-05 19:41 UTC
- KUAO runway 35
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