Unstable approach — N780JH

N780JH (Jack Henry & Associates) was operating from KDTL to K94K on 2026-08-28. SkyMeter detected a low approach-stability score at Cassville Municipal Airport (K94K) on runway 09 at 21:23 UTC. Trace data at the event: 2568 ft AGL, 116 kt GS. Approach stability score: 37/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, 3 kt crosswind component. 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.

• HAZARDS6/1462 2026-08-04 13:00Z – 2026-09-01 04:00Z SFC–15,000 ft

  20NM SW PUEBLO, CO, Tuesday, August 4, 2026 through Tuesday, September 1, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/5463 2026-08-17 13:00Z – 2026-08-30 04:00Z SFC–13,000 ft

  20NM NE SALT LAKE CITY, UT, Monday, August 17, 2026 through Sunday, August 30, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/6723 2026-08-20 14:00Z – 2026-09-03 04:00Z SFC–9,000 ft

  16NM E BIG TIMBER, MT, Thursday, August 20, 2026 through Thursday, September 3, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/7092 2026-08-22 13:00Z – 2026-09-04 03:00Z SFC–14,000 ft

  26NM SW PRICE, UT, Saturday, August 22, 2026 through Friday, September 4, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/7115 2026-08-22 23:30Z – 2026-09-04 03:00Z SFC–13,000 ft

  41NM E PRICE, UT, Saturday, August 22, 2026 through Friday, September 4, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/7117 2026-08-23 11:00Z – 2026-08-29 01:00Z SFC–13,500 ft

  30NM SW PUEBLO, CO, Sunday, August 23, 2026 through Saturday, August 29, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/7530 2026-08-24 17:00Z – 2026-09-06 03:00Z SFC–10,000 ft

  35NM SW PROVO, UT, Monday, August 24, 2026 through Sunday, September 6, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/7463 2026-08-25 12:00Z – 2026-09-08 08:00Z SFC–16,500 ft

  1NM NE OURAY, CO, Tuesday, August 25, 2026 through Tuesday, September 8, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/7654 2026-08-25 13:00Z – 2026-09-07 04:00Z SFC–10,000 ft

  35NM SW PROVO, UT, Tuesday, August 25, 2026 through Monday, September 7, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/8109 2026-08-26 14:00Z – 2026-09-09 03:30Z SFC–11,000 ft

  32NM SE BILLINGS, MT, Wednesday, August 26, 2026 through Wednesday, September 9, 2026 UTC

  View FAA NOTAM →
• VIP6/7355 2026-08-26 16:45Z – 2026-08-28 18:00Z SFC–4,999 ft

  JACKSON HOLE, WY, Wednesday, August 26, 2026 through Friday, August 28, 2026 Local

  View FAA NOTAM →
• HAZARDS6/8310 2026-08-26 16:45Z – 2026-09-02 03:00Z SFC–14,000 ft

  23NM N PINEDALE, WY, Wednesday, August 26, 2026 through Wednesday, September 2, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/8502 2026-08-27 14:00Z – 2026-09-09 03:00Z SFC–15,000 ft

  48NM NW TAOS, NM, Thursday, August 27, 2026 through Wednesday, September 9, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/8524 2026-08-27 14:00Z – 2026-09-10 03:30Z SFC–12,500 ft

  18NM SE ENNIS, MT, Thursday, August 27, 2026 through Thursday, September 10, 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.

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