Unstable approach — N907SF

N907SF (9twenty-Five98) was operating from KCRQ to KEKX on 2026-08-07. SkyMeter detected a low approach-stability score at Addington Field (KEKX) on runway 05 at 21:25 UTC. Trace data at the event: 1906 ft AGL, 142 kt GS. Approach stability score: 41/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 7 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.

• SECURITY6/4812 2026-07-15 07:00Z – 2027-07-14 06:59Z SFC–17,999 ft

  El Centro, CA, Wednesday, July 15, 2026 through Tuesday, July 13, 2027 Local

  View FAA NOTAM →
• HAZARDS6/8554 2026-07-26 12:00Z – 2026-08-10 03:00Z SFC–12,000 ft

  16NM W MONTICELLO, UT, Sunday, July 26, 2026 through Monday, August 10, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/9111 2026-07-28 14:00Z – 2026-08-10 03:00Z SFC–14,500 ft

  14NM N LOS ALAMOS, NM, Tuesday, July 28, 2026 through Monday, August 10, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/9885 2026-07-29 12:00Z – 2026-08-12 04:00Z SFC–15,000 ft

  8NM S PAGOSA SPRINGS, CO, Wednesday, July 29, 2026 through Wednesday, August 12, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/9841 2026-07-29 14:00Z – 2026-08-11 03:00Z SFC–11,500 ft

  11NM S CIMARRON, NM, Wednesday, July 29, 2026 through Tuesday, August 11, 2026 UTC

  View FAA NOTAM →
• SECURITY6/0708 2026-08-01 00:01Z – 2027-08-01 23:59Z SFC–400 ft

  Goodlettsville, TN, Saturday, August 1, 2026 through Sunday, August 1, 2027 UTC

  View FAA NOTAM →
• HAZARDS6/0715 2026-08-01 02:12Z – 2026-08-08 04:00Z SFC–7,000 ft

  YUCAIPA, CA, Saturday, August 1, 2026 through Saturday, August 8, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/0745 2026-08-01 14:00Z – 2026-08-14 04:00Z SFC–9,000 ft

  15NM N RAMONA, CA, Saturday, August 1, 2026 through Friday, August 14, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/0882 2026-08-02 04:00Z – 2026-08-15 04:00Z SFC–15,000 ft

  8NM S PAGOSA SPRINGS, CO, Sunday, August 2, 2026 through Saturday, August 15, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/0876 2026-08-02 14:00Z – 2026-08-09 02:00Z SFC–13,000 ft

  30NM NW ALBUQUERQUE, NM, Sunday, August 2, 2026 through Sunday, August 9, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/1949 2026-08-05 12:00Z – 2026-08-19 04:00Z SFC–13,000 ft

  13NM SW CORTEZ, CO, Wednesday, August 5, 2026 through Wednesday, August 19, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/2435 2026-08-06 13:00Z – 2026-08-20 04:00Z SFC–13,500 ft

  13NM N SANTA FE, NM, Thursday, August 6, 2026 through Thursday, August 20, 2026 UTC

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

  24NM SE ALBUQUERQUE, NM, Friday, August 7, 2026 through Friday, August 14, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/2842 2026-08-07 14:30Z – 2026-08-21 04:00Z SFC–13,500 ft

  13NM N SANTA FE, NM, Friday, August 7, 2026 through Friday, August 21, 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