Unstable approach — N325TX
KSJT · 182026-07-19 02:54 UTC· KCRQ → KSJT· CONCHO FLIGHT SUPPORT LLC· E50P
N325TX (Concho Flight Support) was operating from KCRQ to KSJT on 2026-07-19. SkyMeter detected a low approach-stability score at San Angelo Regional Mathis Field (KSJT) on runway 18 at 02:54 UTC. Trace data at the event: 2998 ft AGL, 122 kt GS. Approach stability score: 42/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 5 kt wind, 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/4160 2026-02-14 08:00Z – 2026-08-15 06:59Z SFC–400 ft
Chula Vista, CA, Saturday, February 14, 2026 through Friday, August 14, 2026 Local
View FAA NOTAM → - SECURITY6/4183 2026-06-01 07:00Z – 2026-07-21 06:59Z SFC–400 ft
San Diego, CA, Monday, June 1, 2026 through Monday, July 20, 2026 Local
View FAA NOTAM → - SECURITY6/4202 2026-06-01 07:00Z – 2026-07-21 06:59Z SFC–400 ft
San Diego, CA, Monday, June 1, 2026 through Monday, July 20, 2026 Local
View FAA NOTAM → - SECURITY6/4203 2026-06-01 07:00Z – 2026-07-21 06:59Z SFC–400 ft
San Diego, CA, Monday, June 1, 2026 through Monday, July 20, 2026 Local
View FAA NOTAM → - SECURITY6/7820 2026-06-29 15:07Z – 2026-07-21 06:59Z SFC–400 ft
San Diego, CA
View FAA NOTAM → - SECURITY6/7821 2026-06-29 15:07Z – 2026-07-21 06:59Z SFC–400 ft
San Diego, CA
View FAA NOTAM → - SECURITY6/2652 2026-07-05 00:01Z – 2027-01-02 23:59Z SFC–500 ft
Coyote Wells, CA, Saturday, July 4, 2026 through Saturday, January 2, 2027 Local
View FAA NOTAM → - SECURITY6/2656 2026-07-05 00:01Z – 2027-01-02 23:59Z SFC–500 ft
Coyote Wells, CA, Saturday, July 4, 2026 through Saturday, January 2, 2027 Local
View FAA NOTAM → - SECURITY6/2657 2026-07-05 00:01Z – 2027-01-02 23:59Z SFC–500 ft
Calexico, CA, Saturday, July 4, 2026 through Saturday, January 2, 2027 Local
View FAA NOTAM → - SECURITY6/4812 2026-07-15 07:00Z – 2027-07-14 06:59Z SFC–17,999 ft
El Centro, CA, Wednesday, July 15, 2026 through Tuesday, July 13, 2027 Local
View FAA NOTAM → - HAZARDS6/6186 2026-07-17 13:00Z – 2026-07-30 03:00Z SFC–11,000 ft
21NM NE DOUGLAS, AZ, Friday, July 17, 2026 through Thursday, July 30, 2026 UTC
View FAA NOTAM → - SECURITY6/6542 2026-07-18 06:00Z – 2026-07-19 13:00Z SFC–17,999 ft
Libby AAF, AZ, Friday, July 17, 2026 through Sunday, July 19, 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.
Pilot review data
- Runway 18
- 2998 ft AGL at event
- 122 kt ground speed
- 0 fpm vertical
- Approach stability 42/100
- 5 kt wind
- 0 kt crosswind component
- 16,093 m visibility
- KSJT 161751Z 19011G19KT 10SM CLR 34/14 A3020 RMK AO2 SLP198 T03440139 10344 20217 58005
Flight context
- N325TX
- Concho Flight Support
- E50P
- KCRQ → KSJT
- 2026-07-19 02:54 UTC
- KSJT runway 18
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