Unstable approach — N125DG

KPVU · 13

2026-07-22 22:08 UTC· KSNA → KPVU· FUGAL AVIATION LLC· C25B

N125DG (Fugal Aviation) was operating from KSNA to KPVU on 2026-07-22. SkyMeter detected a low approach-stability score at Provo Municipal Airport (KPVU) on runway 13 at 22:08 UTC. Trace data at the event: 5547 ft AGL, 150 kt GS. Approach stability score: 55/100. Scores in this band occur on roughly 10-15% of approaches at this runway, with multiple gates outside the per-runway envelope. METAR at the time reported 16 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.

Active FAA TFR during this flight

Source: FAA TFR archive (hourly snapshot)
  • HAZARDS6/4895 2026-07-10 23:19Z – 2026-07-24 23:00Z SFC–10,500 ft

    3NM W PIÑON HILLS, CA, Friday, July 10, 2026 through Friday, July 24, 2026 UTC

    View FAA NOTAM →
  • HAZARDS6/4907 2026-07-11 15:00Z – 2026-07-24 23:00Z SFC–10,500 ft

    3NM W PIÑON HILLS, CA, Saturday, July 11, 2026 through Friday, July 24, 2026 UTC

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

    9NM SE DUGWAY, UT, Sunday, July 12, 2026 through Sunday, July 26, 2026 UTC

    View FAA NOTAM →
  • HAZARDS6/5145 2026-07-13 00:57Z – 2026-07-26 07:45Z SFC–8,500 ft

    3NM W PIÑON HILLS, CA, Monday, July 13, 2026 through Sunday, July 26, 2026 UTC

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

    9NM SE DUGWAY, UT, Thursday, July 16, 2026 through Thursday, July 30, 2026 UTC

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

    9NM SE DUGWAY, UT, Friday, July 17, 2026 through Friday, July 31, 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/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/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 →

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 13
  • 5547 ft AGL at event
  • 150 kt ground speed
  • 0 fpm vertical
  • Approach stability 55/100
  • 16 kt wind
  • 2 kt crosswind component
  • 16,093 m visibility
  • METAR KPVU 241356Z 00000KT 10SM CLR 10/07 A3022 RMK AO2 SLP204 T01000067 PNO $

Flight context

  • N125DG
  • Fugal Aviation
  • C25B
  • KSNA → KPVU
  • 2026-07-22 22:08 UTC
  • KPVU runway 13

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· KPVU