Unstable approach — SCM81

KOMA · 14R

2026-06-20 15:24 UTC· KDAL → KOMA· N814TS LLC· LJ60

SCM81 (N814ts) was operating from KDAL to KOMA on 2026-06-20. SkyMeter detected a low approach-stability score at Eppley Airfield (KOMA) on runway 14R at 15:24 UTC. Trace data at the event: 2069 ft AGL, 166 kt GS. Approach stability score: 28/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 2 kt wind, 1 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/4008 2026-06-01 05:00Z – 2026-07-21 04:59Z SFC–400 ft

    FRISCO, TX, Monday, June 1, 2026 through Monday, July 20, 2026 Local

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

    FRISCO, TX, Monday, June 1, 2026 through Monday, July 20, 2026 Local

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

    Tulsa, OK, Monday, June 1, 2026 through Monday, July 20, 2026 Local

    View FAA NOTAM →
  • UAS PUBLIC GATHERING6/5706 2026-06-11 14:00Z – 2026-06-23 04:00Z SFC–400 ft

    Omaha, NE, Thursday, June 11, 2026 through Tuesday, June 23, 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 14R
  • 2069 ft AGL at event
  • 166 kt ground speed
  • 0 fpm vertical
  • Approach stability 28/100
  • 2 kt wind
  • 1 kt crosswind component
  • 16,093 m visibility
  • KOMA 100952Z 15010KT 10SM CLR 17/13 A2986 RMK AO2 SLP101 T01670133

Flight context

  • SCM81
  • N814ts
  • LJ60
  • KDAL → KOMA
  • 2026-06-20 15:24 UTC
  • KOMA runway 14R

All events on this flight

Unstable approach 15:24:26 UTC · KOMA runway 14R · 2,069 ft AGL · 166 kt GS
Unstable approach 15:24:26 UTC · KOMA runway 14R · 2,069 ft AGL · 166 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· KOMA