Unstable approach — ROPER14

KBAB · 15

2026-07-23 21:56 UTC· KBAB KBAB· T38

ROPER14 was operating from KBAB to KBAB on 2026-07-23. SkyMeter detected a low approach-stability score at Beale Air Force Base (KBAB) on runway 15 at 21:56 UTC. Trace data at the event: 1273 ft AGL, 185 kt GS. Approach stability score: 50/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 5 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)
  • 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 →
  • HAZARDS6/7245 2026-07-21 03:43Z – 2026-08-04 03:30Z SFC–7,000 ft

    9NM NW GRASS VALLEY DISPATCH CENTER, CA, Tuesday, July 21, 2026 through Tuesday, August 4, 2026 UTC

    View FAA NOTAM →
  • HAZARDS6/7854 2026-07-22 17:23Z – 2026-08-05 04:00Z SFC–7,000 ft

    9NM NW GRASS VALLEY DISPATCH CENTER, CA, Wednesday, July 22, 2026 through Wednesday, August 5, 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 15
  • 1273 ft AGL at event
  • 185 kt ground speed
  • 0 fpm vertical
  • Approach stability 50/100
  • 5 kt wind
  • 4 kt crosswind component
  • 16,093 m visibility
  • KBAB 162255Z 18015KT 10SM CLR 27/11 A2986 RMK AO2A SLP114 T02730105 $

Flight context

  • ROPER14
  • T38
  • KBAB → KBAB
  • 2026-07-23 21:56 UTC
  • KBAB runway 15

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

SkyMeter · trace data observed via ADS-B· KBAB