PEGGY41 was inbound to KSUU on 2026-08-06. SkyMeter detected a low approach-stability score at Travis Air Force Base (KSUU) on runway 21L at 21:53 UTC. Trace data at the event: 1169 ft AGL, 135 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 16 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/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 → - SECURITY6/6491 2026-07-20 07:01Z – 2026-09-16 06:59Z SFC–1,499 ft
Concord, CA, Monday, July 20, 2026 through Tuesday, September 15, 2026 Local
View FAA NOTAM → - HAZARDS6/8423 2026-07-24 16:00Z – 2026-08-07 04:00Z SFC–9,500 ft
35NM SE ROSEBURG, OR, Friday, July 24, 2026 through Friday, August 7, 2026 UTC
View FAA NOTAM → - HAZARDS6/9403 2026-07-28 13:00Z – 2026-08-10 03:00Z SFC–7,000 ft
20NM NW MEDFORD, OR, Tuesday, July 28, 2026 through Monday, August 10, 2026 UTC
View FAA NOTAM → - HAZARDS6/9888 2026-07-29 13:00Z – 2026-08-12 03:00Z SFC–6,000 ft
20NM NW MEDFORD, OR, Wednesday, July 29, 2026 through Wednesday, August 12, 2026 UTC
View FAA NOTAM → - HAZARDS6/0878 2026-08-02 01:15Z – 2026-08-15 05:00Z SFC–6,000 ft
2NM NE GRANTS PASS, OR, Sunday, August 2, 2026 through Saturday, August 15, 2026 UTC
View FAA NOTAM → - HAZARDS6/0889 2026-08-02 05:00Z – 2026-08-15 05:00Z SFC–6,000 ft
2NM NE GRANTS PASS, OR, Sunday, August 2, 2026 through Saturday, August 15, 2026 UTC
View FAA NOTAM → - HAZARDS6/0890 2026-08-02 13:00Z – 2026-08-15 03:00Z SFC–5,000 ft
20NM NW MEDFORD, OR, Sunday, August 2, 2026 through Saturday, August 15, 2026 UTC
View FAA NOTAM → - HAZARDS6/0938 2026-08-02 15:28Z – 2026-08-16 04:00Z SFC–6,000 ft
11NM SE UKIAH, CA, Sunday, August 2, 2026 through Sunday, August 16, 2026 UTC
View FAA NOTAM → - HAZARDS6/2436 2026-08-06 00:15Z – 2026-08-11 05:00Z SFC–11,000 ft
15NM N KLAMATH FALLS, OR, Thursday, August 6, 2026 through Tuesday, August 11, 2026 UTC
View FAA NOTAM → - HAZARDS6/2493 2026-08-06 05:00Z – 2026-08-16 05:00Z SFC–9,500 ft
35NM SE ROSEBURG, OR, Thursday, August 6, 2026 through Sunday, August 16, 2026 UTC
View FAA NOTAM → - HAZARDS6/2496 2026-08-06 05:00Z – 2026-08-19 05:00Z SFC–11,000 ft
15NM N KLAMATH FALLS, OR, Thursday, August 6, 2026 through Wednesday, August 19, 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 21L
- 1169 ft AGL at event
- 135 kt ground speed
- 0 fpm vertical
- Approach stability 45/100
- 16 kt wind
- 2 kt crosswind component
- 16,093 m visibility
- KSUU 161955Z AUTO 24017KT 10SM CLR 24/11 A2991 RMK AO2 SLP135 T02350109
Flight context
- PEGGY41
- B762
- 2026-08-06 21:53 UTC
- KSUU runway 21L
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