Unstable approach — N583TL
KMOD · 28R2026-06-20 23:41 UTC· KCYS → KMOD· 518MV AIR LLC· C560
N583TL (518mv AIR) was operating from KCYS to KMOD on 2026-06-20. SkyMeter detected a low approach-stability score at Modesto City Co-Harry Sham Field (KMOD) on runway 28R at 23:41 UTC. Trace data at the event: 1195 ft AGL, 141 kt GS. Approach stability score: 44/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 11 kt wind, 5 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/4164 2026-06-01 06:00Z – 2026-07-21 05:59Z SFC–400 ft
Sandy, UT, Monday, June 1, 2026 through Monday, July 20, 2026 Local
View FAA NOTAM → - SECURITY6/4167 2026-06-01 06:00Z – 2026-07-21 05:59Z SFC–400 ft
Salt Lake City, UT, Monday, June 1, 2026 through Monday, July 20, 2026 Local
View FAA NOTAM → - HAZARDS6/6225 2026-06-09 14:00Z – 2026-06-21 02:00Z SFC–10,500 ft
31NM SW NEPHI, UT, Tuesday, June 9, 2026 through Sunday, June 21, 2026 UTC
View FAA NOTAM → - HAZARDS6/6608 2026-06-09 15:00Z – 2026-06-22 04:00Z SFC–11,500 ft
13NM W NUCLA, CO, Tuesday, June 9, 2026 through Monday, June 22, 2026 UTC
View FAA NOTAM → - HAZARDS6/6827 2026-06-09 17:15Z – 2026-06-22 02:00Z SFC–10,000 ft
9NM SW TOOELE, UT, Tuesday, June 9, 2026 through Monday, June 22, 2026 UTC
View FAA NOTAM → - HAZARDS6/6965 2026-06-10 14:00Z – 2026-06-22 03:00Z SFC–10,000 ft
9NM SW TOOELE, UT, Wednesday, June 10, 2026 through Monday, June 22, 2026 UTC
View FAA NOTAM → - HAZARDS6/7478 2026-06-11 03:12Z – 2026-06-24 04:00Z SFC–11,500 ft
20NM N NUCLA, CO, Thursday, June 11, 2026 through Wednesday, June 24, 2026 UTC
View FAA NOTAM → - HAZARDS6/7479 2026-06-11 03:19Z – 2026-06-24 04:00Z SFC–11,500 ft
10NM NW NUCLA, CO, Thursday, June 11, 2026 through Wednesday, June 24, 2026 UTC
View FAA NOTAM → - HAZARDS6/7811 2026-06-12 03:18Z – 2026-06-25 04:00Z SFC–12,500 ft
29NM SE GLENWOOD SPRINGS, CO, Friday, June 12, 2026 through Thursday, June 25, 2026 UTC
View FAA NOTAM → - HAZARDS6/8549 2026-06-16 02:58Z – 2026-06-30 04:00Z SFC–12,000 ft
12NM NE GRAND JUNCTION, CO, Tuesday, June 16, 2026 through Tuesday, June 30, 2026 UTC
View FAA NOTAM → - AIR SHOWS/SPORTS6/7982 2026-06-19 18:00Z – 2026-06-20 22:30Z SFC–17,999 ft
Truckee, CA, Friday, June 19, 2026 through Saturday, June 20, 2026 UTC
View FAA NOTAM → - HAZARDS6/9412 2026-06-20 17:53Z – 2026-07-03 04:00Z SFC–11,000 ft
27NM SW PROVO, UT, Saturday, June 20, 2026 through Friday, July 3, 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 28R
- 1195 ft AGL at event
- 141 kt ground speed
- 0 fpm vertical
- Approach stability 44/100
- 11 kt wind
- 5 kt crosswind component
- 16,093 m visibility
- KMOD 100753Z AUTO 36003KT 10SM CLR 19/11 A2963 RMK AO2 SLP033 T01890111 403330161
Flight context
- N583TL
- 518mv AIR
- C560
- KCYS → KMOD
- 2026-06-20 23:41 UTC
- KMOD runway 28R
All events on this flight
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