Unstable approach — BGST02

KCEW · 35

2026-06-29 16:31 UTC· KBLV → KCEW· BE20

▶ Replay 📊 Analyse

BGST02 was operating from KBLV to KCEW on 2026-06-29. SkyMeter detected a low approach-stability score at Bob Sikes Airport (KCEW) on runway 35 at 16:31 UTC. Trace data at the event: 1304 ft AGL, 138 kt GS. Approach stability score: 30/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 3 kt wind, 3 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/4114 2026-06-01 04:00Z – 2026-07-21 03:59Z SFC–400 ft

    LOUISVILLE, KY, Monday, June 1, 2026 through Monday, July 20, 2026 Local

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

    LOUISVILLE, KY, Monday, June 1, 2026 through Monday, July 20, 2026 Local

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

    NASHVILLE, TN, Monday, June 1, 2026 through Monday, July 20, 2026 Local

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

    Nashville, TN, 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 35
  • 1304 ft AGL at event
  • 138 kt ground speed
  • 0 fpm vertical
  • Approach stability 30/100
  • 3 kt wind
  • 3 kt crosswind component
  • 16,093 m visibility
  • KCEW 142353Z AUTO 05004KT 10SM TS FEW046 BKN070 OVC100 25/22 A3012 RMK AO2 LTG DSNT ALQDS RAB40E53 TSB2259E14B27 SLP195 P0000 60000 T02500222 10367 20250 53006

Flight context

  • BGST02
  • BE20
  • KBLV → KCEW
  • 2026-06-29 16:31 UTC
  • KCEW runway 35

All events on this flight

Unstable approach 16:31:03 UTC · KCEW runway 35 · 1,304 ft AGL · 138 kt GS
Unstable approach 16:31:03 UTC · KCEW runway 35 · 1,304 ft AGL · 138 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· KCEW