Unstable approach — TIV80
KSEZ · 032026-07-13 22:22 UTC· KSAT → KSEZ· SJ AVIATION PARTNERS II LLC· C25B
TIV80 (SJ Aviation Partners II) was operating from KSAT to KSEZ on 2026-07-13. SkyMeter detected a low approach-stability score at Sedona Airport (KSEZ) on runway 03 at 22:22 UTC. Trace data at the event: 5916 ft AGL, 122 kt GS. Approach stability score: 40/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, 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)- SECURITY6/4165 2026-02-14 07:00Z – 2026-08-15 06:59Z SFC–400 ft
Nogales, AZ, Saturday, February 14, 2026 through Friday, August 14, 2026 Local
View FAA NOTAM → - 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/4097 2026-06-01 05:00Z – 2026-07-21 04:59Z
SAN ANTONIO, TX, Monday, June 1, 2026 through Tuesday, July 21, 2026 UTC
View FAA NOTAM → - SECURITY6/3966 2026-06-01 07:00Z – 2026-07-21 06:59Z SFC–400 ft
Mesa, AZ, Monday, June 1, 2026 through Monday, July 20, 2026 Local
View FAA NOTAM → - SECURITY6/7079 2026-06-27 01:07Z – 2026-07-21 06:59Z SFC–400 ft
Mesa, AZ
View FAA NOTAM → - HAZARDS6/2561 2026-07-02 16:00Z – 2026-07-15 03:00Z SFC–12,000 ft
13NM SW FLAGSTAFF, AZ, Thursday, July 2, 2026 through Wednesday, July 15, 2026 UTC
View FAA NOTAM → - HAZARDS6/2884 2026-07-04 17:45Z – 2026-07-18 03:00Z SFC–13,800 ft
35NM NW SILVER CITY, NM, Saturday, July 4, 2026 through Saturday, July 18, 2026 UTC
View FAA NOTAM → - HAZARDS6/3016 2026-07-06 14:00Z – 2026-07-20 04:00Z SFC–11,000 ft
7NM SW FLAGSTAFF, AZ, Monday, July 6, 2026 through Monday, July 20, 2026 UTC
View FAA NOTAM → - HAZARDS6/3339 2026-07-07 14:00Z – 2026-07-21 04:00Z SFC–11,000 ft
7NM SW FLAGSTAFF, AZ, Tuesday, July 7, 2026 through Tuesday, July 21, 2026 UTC
View FAA NOTAM → - HAZARDS6/3341 2026-07-07 14:00Z – 2026-07-21 04:00Z SFC–8,500 ft
9NM S FLAGSTAFF, AZ, Tuesday, July 7, 2026 through Tuesday, July 21, 2026 UTC
View FAA NOTAM → - HAZARDS6/3393 2026-07-07 14:00Z – 2026-07-21 04:00Z SFC–11,000 ft
7NM SW FLAGSTAFF, AZ, Tuesday, July 7, 2026 through Tuesday, July 21, 2026 UTC
View FAA NOTAM → - SECURITY6/6820 2026-07-09 11:07Z – 2026-07-21 04:59Z SFC–400 ft
San Antonio, TX
View FAA NOTAM → - SECURITY6/6834 2026-07-09 11:07Z – 2026-07-21 04:59Z SFC–400 ft
San Antonio, TX
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 03
- 5916 ft AGL at event
- 122 kt ground speed
- 0 fpm vertical
- Approach stability 40/100
- 3 kt wind
- 2 kt crosswind component
- 16,093 m visibility
- METAR KSEZ 170415Z AUTO 30003KT 10SM -RA FEW030 BKN075 OVC090 16/16 A3028 RMK AO2
Flight context
- TIV80
- SJ Aviation Partners II
- C25B
- KSAT → KSEZ
- 2026-07-13 22:22 UTC
- KSEZ runway 03
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