Unstable approach — EJM21
KPVU · 312026-07-24 18:26 UTC· KSJC → KPVU· NJI SALES INC· GLF4
EJM21 (NJI Sales) was operating from KSJC to KPVU on 2026-07-24. SkyMeter detected a low approach-stability score at Provo Municipal Airport (KPVU) on runway 31 at 18:26 UTC. Trace data at the event: 5568 ft AGL, 152 kt GS. Approach stability score: 45/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, 4 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)- SECURITY6/3475 2026-03-08 09:00Z – 2026-11-01 09:59Z SFC–180 ft
BEALE AFB, CA, Sunday, March 8, 2026 through Sunday, November 1, 2026 Local
View FAA NOTAM → - SECURITY6/5797 2026-04-03 00:01Z – 2026-09-28 23:59Z SFC–400 ft
SACRAMENTO, CA, Thursday, April 2, 2026 through Monday, September 28, 2026 Local
View FAA NOTAM → - HAZARDS6/4964 2026-07-12 00:13Z – 2026-07-26 03:00Z SFC–10,500 ft
3NM N LOYALTON, CA, Sunday, July 12, 2026 through Sunday, July 26, 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/4978 2026-07-12 13:00Z – 2026-07-26 13:00Z SFC–10,500 ft
3NM N LOYALTON, CA, Sunday, July 12, 2026 through Sunday, July 26, 2026 UTC
View FAA NOTAM → - HAZARDS6/5054 2026-07-12 14:45Z – 2026-07-26 13:00Z SFC–12,500 ft
3NM N LOYALTON, CA, Sunday, July 12, 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/7245 2026-07-21 03:43Z – 2026-08-04 03:30Z SFC–7,000 ft
9NM NW GRASS VALLEY DISPATCH CENTER, CA, Tuesday, July 21, 2026 through Tuesday, August 4, 2026 UTC
View FAA NOTAM → - HAZARDS6/7854 2026-07-22 17:23Z – 2026-08-05 04:00Z SFC–7,000 ft
9NM NW GRASS VALLEY DISPATCH CENTER, CA, Wednesday, July 22, 2026 through Wednesday, August 5, 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 31
- 5568 ft AGL at event
- 152 kt ground speed
- 0 fpm vertical
- Approach stability 45/100
- 6 kt wind
- 4 kt crosswind component
- 16,093 m visibility
- KPVU 161156Z AUTO 16014KT 10SM BKN090 16/12 A3005 RMK AO2 LTG DSNT SE AND S SLP125 P0004 60011 70011 T01610122 10217 20156 55000
Flight context
- EJM21
- NJI Sales
- GLF4
- KSJC → KPVU
- 2026-07-24 18:26 UTC
- KPVU runway 31
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