Unstable approach — N560PP

N560PP (Encore Aviation) was operating from KVQQ to KABQ on 2026-06-25. SkyMeter detected a low approach-stability score at Albuquerque International Sunport (KABQ) on runway 21 at 16:16 UTC. Trace data at the event: 6417 ft AGL, 127 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 3 kt wind, 3 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/4240 2026-03-08 08:00Z – 2026-11-01 07:00Z SFC–180 ft

  SAN ANGELO, TX, Sunday, March 8, 2026 through Sunday, November 1, 2026 Local

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

  ATLANTA, GA, Monday, June 1, 2026 through Tuesday, July 21, 2026 UTC

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

  CHATTANOOGA, TN, Monday, June 1, 2026 through Monday, July 20, 2026 Local

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

  MARIETTA, GA, Monday, June 1, 2026 through Monday, July 20, 2026 Local

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

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

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

  MANSFIELD, TX, Monday, June 1, 2026 through Tuesday, July 21, 2026 UTC

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

  FORT WORTH, TX, Monday, June 1, 2026 through Monday, July 20, 2026 Local

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

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

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

  DENTON, TX, Monday, June 1, 2026 through Tuesday, July 21, 2026 UTC

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

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

  View FAA NOTAM →
• SECURITY6/8212 2026-06-17 04:01Z – 2026-07-17 03:59Z SFC–400 ft

  Kennesaw, GA, Wednesday, June 17, 2026 through Thursday, July 16, 2026 Local

  View FAA NOTAM →
• HAZARDS6/9420 2026-06-20 21:25Z – 2026-07-04 04:00Z SFC–12,000 ft

  40NM SE ALBUQUERQUE, NM, Saturday, June 20, 2026 through Saturday, July 4, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/9456 2026-06-21 13:00Z – 2026-07-05 04:00Z SFC–12,000 ft

  40NM SE ALBUQUERQUE, NM, Sunday, June 21, 2026 through Sunday, July 5, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/0466 2026-06-24 16:30Z – 2026-06-30 03:00Z SFC–13,000 ft

  50NM E ALBUQUERQUE, NM, Wednesday, June 24, 2026 through Tuesday, June 30, 2026 UTC

  View FAA NOTAM →
• SECURITY6/9581 2026-06-25 04:01Z – 2026-06-26 03:59Z SFC–1,000 ft

  Atlanta, GA, Thursday, June 25, 2026 through Thursday, June 25, 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.

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