Unstable approach — MXY1092

KHHR · 25

2026-06-03 17:08 UTC· KSDF → KHHR· BANK OF UTAH TRUSTEE· BCS3

MXY1092 (Bank of Utah) was operating from KSDF to KHHR on 2026-06-03. SkyMeter detected a low approach-stability score at Jack Northrop Field Hawthorne Municipal Airport (KHHR) on runway 25 at 17:08 UTC. Trace data at the event: 1179 ft AGL, 144 kt GS. Approach stability score: 42/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 4 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)
  • HAZARDS6/2366 2026-05-22 06:00Z – 2026-06-05 04:00Z SFC–10,000 ft

    12NM S PRESCOTT, AZ, Friday, May 22, 2026 through Friday, June 5, 2026 UTC

    View FAA NOTAM →
  • SECURITY6/3954 2026-06-01 00:00Z – 2026-07-20 23:59Z

    STILLWATER, OK, Monday, June 1, 2026 through Monday, July 20, 2026 UTC

    View FAA NOTAM →
  • SECURITY6/3996 2026-06-01 00:00Z – 2026-07-20 23:59Z

    OKLAHOMA CITY, OK, Monday, June 1, 2026 through Monday, July 20, 2026 UTC

    View FAA NOTAM →
  • 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/3952 2026-06-01 05:00Z – 2026-07-21 04:59Z SFC–400 ft

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

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

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

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

    OKLAHOMA CITY, OK, 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 →
  • 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 →
  • SECURITY6/4189 2026-06-01 07:00Z – 2026-07-21 06:59Z SFC–400 ft

    Los Angeles, CA, 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 25
  • 1179 ft AGL at event
  • 144 kt ground speed
  • 0 fpm vertical
  • Approach stability 42/100
  • 4 kt wind
  • 4 kt crosswind component
  • 16,093 m visibility
  • KHHR 151953Z 26008KT 10SM CLR 32/01 A2998 RMK AO2 SLP150 T03170006

Flight context

  • MXY1092
  • Bank of Utah
  • BCS3
  • KSDF → KHHR
  • 2026-06-03 17:08 UTC
  • KHHR runway 25

All events on this flight

Unstable approach 17:08:44 UTC · KHHR runway 25 · 1,179 ft AGL · 144 kt GS
Unstable approach 17:08:44 UTC · KHHR runway 25 · 1,179 ft AGL · 144 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· KHHR