SHAGY3 was operating from KTUS to KLRF on 2026-08-27. SkyMeter detected a low approach-stability score at Little Rock Air Force Base (KLRF) on runway 25 at 23:14 UTC. Trace data at the event: 1414 ft AGL, 157 kt GS. Approach stability score: 57/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 4 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)- HAZARDS6/7128 2026-08-23 13:00Z – 2026-09-06 03:00Z SFC–14,500 ft
26NM NE RUIDOSO, NM, Sunday, August 23, 2026 through Sunday, September 6, 2026 UTC
View FAA NOTAM → - HAZARDS6/7422 2026-08-24 14:30Z – 2026-09-08 05:00Z SFC–12,500 ft
26NM NE RUIDOSO, NM, Monday, August 24, 2026 through Tuesday, September 8, 2026 UTC
View FAA NOTAM → - HAZARDS6/7589 2026-08-24 20:35Z – 2026-08-29 02:00Z SFC–5,500 ft
2NM W PALO PINTO, TX, Monday, August 24, 2026 through Saturday, August 29, 2026 UTC
View FAA NOTAM → - HAZARDS6/7630 2026-08-25 12:00Z – 2026-09-01 02:00Z SFC–5,500 ft
1NM W PALO PINTO, TX, Tuesday, August 25, 2026 through Tuesday, September 1, 2026 UTC
View FAA NOTAM → - HAZARDS6/7885 2026-08-25 19:02Z – 2026-09-02 23:45Z SFC–5,500 ft
PALO PINTO, TX, Tuesday, August 25, 2026 through Wednesday, September 2, 2026 UTC
View FAA NOTAM → - HAZARDS6/8102 2026-08-26 02:25Z – 2026-09-09 02:00Z SFC–5,500 ft
1NM NW PALO PINTO, TX, Wednesday, August 26, 2026 through Wednesday, September 9, 2026 UTC
View FAA NOTAM → - HAZARDS6/8103 2026-08-26 12:00Z – 2026-09-09 02:00Z SFC–4,000 ft
21NM NW BROKEN BOW, OK, Wednesday, August 26, 2026 through Wednesday, September 9, 2026 UTC
View FAA NOTAM → - HAZARDS6/8069 2026-08-26 14:00Z – 2026-09-09 04:00Z SFC–14,000 ft
26NM SE ALBUQUERQUE, NM, Wednesday, August 26, 2026 through Wednesday, September 9, 2026 UTC
View FAA NOTAM → - HAZARDS6/8445 2026-08-26 20:55Z – 2026-09-09 02:00Z SFC–5,500 ft
1NM NW PALO PINTO, TX, Wednesday, August 26, 2026 through Wednesday, September 9, 2026 UTC
View FAA NOTAM → - HAZARDS6/8586 2026-08-27 17:30Z – 2026-08-28 04:00Z SFC–14,000 ft
24NM SE ALBUQUERQUE, NM, Thursday, August 27, 2026 through Friday, August 28, 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 25
- 1414 ft AGL at event
- 157 kt ground speed
- 0 fpm vertical
- Approach stability 57/100
- 4 kt wind
- 4 kt crosswind component
- 16,093 m visibility
- KLRF 070455Z AUTO 36004KT 10SM CLR 27/22 A2990 RMK AO2 SLP123 T02730215 $
Flight context
- SHAGY3
- C30J
- KTUS → KLRF
- 2026-08-27 23:14 UTC
- KLRF runway 25
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