Unstable approach — N50NA

KUAO · 35

2026-06-28 19:36 UTC· KSZT → KUAO· BV TRANSPORTATION LLC· BE20

N50NA (BV Transportation) was operating from KSZT to KUAO on 2026-06-28. SkyMeter detected a low approach-stability score at Aurora State Airport (KUAO) on runway 35 at 19:36 UTC. Trace data at the event: 1273 ft AGL, 141 kt GS. Approach stability score: 40/100. Scores below 50 occur on under 10% of approaches at this runway and indicate the v2 scorer flagged the approach as highly anomalous (three or more gates exceeded the runway's P90 envelope simultaneously). METAR at the time reported 6 kt wind, 4 kt crosswind component, 16,093 m visibility. The approach-stability score rates the final approach against stabilized-approach gates (glideslope, lateral deviation, descent rate, and IAS) at defined altitudes. A low score means one or more of those were outside the normal envelope for how the approach was flown. The score is graded by guidance type, so instrument approaches (ILS or an aligned straight-in) are held to the full gate set, while visual and pattern arrivals are surfaced only when the score is clearly low. The score is advisory and observational, a deviation measure, not an assertion of an accident. 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/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/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 →
  • HAZARDS6/8253 2026-06-15 15:00Z – 2026-06-30 05:00Z SFC–6,000 ft

    3NM W BENTON CITY, WA, Monday, June 15, 2026 through Tuesday, June 30, 2026 UTC

    View FAA NOTAM →
  • HAZARDS6/8960 2026-06-17 15:23Z – 2026-07-01 06:00Z SFC–7,000 ft

    14NM SE OMAK, WA, Wednesday, June 17, 2026 through Wednesday, July 1, 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 →
  • HAZARDS6/9122 2026-06-18 14:00Z – 2026-07-01 06:00Z SFC–7,000 ft

    14NM SE OMAK, WA, Thursday, June 18, 2026 through Wednesday, July 1, 2026 UTC

    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 →

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
  • 1273 ft AGL at event
  • 141 kt ground speed
  • 0 fpm vertical
  • Approach stability 40/100
  • 6 kt wind
  • 4 kt crosswind component
  • 16,093 m visibility
  • KUAO 081625Z AUTO 00000KT 10SM CLR 13/11 A3007 RMK T01300110 MADISHF

Flight context

  • N50NA
  • BV Transportation
  • BE20
  • KSZT → KUAO
  • 2026-06-28 19:36 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

SkyMeter · trace data observed via ADS-B· KUAO