Unstable approach — N500RH

N500RH (HMS Holdings) was operating from KMRY to KJQF on 2026-07-25. SkyMeter detected a low approach-stability score at Concord-Padgett Regional Airport (KJQF) on runway 02 at 23:31 UTC. Trace data at the event: 1815 ft AGL, 122 kt GS. Approach stability score: 35/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, 2 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.

• HAZARDS6/5450 2026-07-14 04:00Z – 2026-07-29 04:00Z SFC–16,500 ft

  19NM NE OURAY, CO, Tuesday, July 14, 2026 through Wednesday, July 29, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/5451 2026-07-14 04:00Z – 2026-07-29 04:00Z SFC–16,500 ft

  1NM N OURAY, CO, Tuesday, July 14, 2026 through Wednesday, July 29, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/6360 2026-07-17 04:00Z – 2026-07-30 04:00Z SFC–15,000 ft

  9NM SW PUEBLO, CO, Friday, July 17, 2026 through Thursday, July 30, 2026 UTC

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

  14NM N CORTEZ, CO, Friday, July 17, 2026 through Thursday, July 30, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/6359 2026-07-17 14:00Z – 2026-07-31 03:00Z SFC–15,500 ft

  5NM E BEAVER, UT, Friday, July 17, 2026 through Friday, July 31, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/6567 2026-07-18 13:00Z – 2026-08-01 04:00Z SFC–16,000 ft

  16NM W MONTICELLO, UT, Saturday, July 18, 2026 through Saturday, August 1, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/6569 2026-07-18 14:00Z – 2026-07-31 03:00Z SFC–15,500 ft

  5NM E BEAVER, UT, Saturday, July 18, 2026 through Friday, July 31, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/6736 2026-07-19 12:00Z – 2026-08-01 03:00Z SFC–16,000 ft

  16NM W MONTICELLO, UT, Sunday, July 19, 2026 through Saturday, August 1, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/6876 2026-07-20 13:00Z – 2026-08-03 04:00Z SFC–16,000 ft

  7NM SW DEL NORTE, CO, Monday, July 20, 2026 through Monday, August 3, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/7246 2026-07-21 05:00Z – 2026-08-21 03:00Z SFC–10,500 ft

  20NM N INDEPENDENCE, CA, Tuesday, July 21, 2026 through Friday, August 21, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/7372 2026-07-21 13:38Z – 2026-08-22 03:00Z SFC–10,500 ft

  20NM N INDEPENDENCE, CA, Tuesday, July 21, 2026 through Saturday, August 22, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/7909 2026-07-22 18:11Z – 2026-08-08 04:00Z SFC–12,500 ft

  20NM N INDEPENDENCE, CA, Wednesday, July 22, 2026 through Saturday, August 8, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/8008 2026-07-23 12:00Z – 2026-08-01 03:00Z SFC–12,000 ft

  16NM W MONTICELLO, UT, Thursday, July 23, 2026 through Saturday, August 1, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/8010 2026-07-23 12:00Z – 2026-08-12 04:00Z SFC–16,500 ft

  19NM NE OURAY, CO, Thursday, July 23, 2026 through Wednesday, August 12, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/8012 2026-07-23 12:00Z – 2026-08-12 04:00Z SFC–16,500 ft

  1NM N OURAY, CO, Thursday, July 23, 2026 through Wednesday, August 12, 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