Return to field — VADER20

KRIC · 16

2026-07-22 14:46 UTC· KRIC → KRIC· UNITED STATES GOVERNMENT, DEPARTMENT OF JUSTICE· B752

▶ Replay 📊 Analyse

VADER20 (United States Government) had departed KRIC on 2026-07-22. SkyMeter detected a return to field at Richmond International Airport (KRIC) on runway 16 at 14:46 UTC. Peak cruise altitude FL221, turnaround area near Tucker, US. Approach stability score: 49/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 0 kt wind, 16,093 m visibility. Detection algorithm and known limitations: see SkyMeter methodology.

Active FAA TFR during this flight

Source: FAA TFR archive (hourly snapshot)
  • HAZARDS6/5843 2026-07-14 23:37Z – 2026-07-22 23:45Z SFC–4,200 ft

    18NM SW WAYNESBORO, VA, Tuesday, July 14, 2026 through Wednesday, July 22, 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 16
  • 22109 ft AGL at event
  • 443 kt ground speed
  • 0 fpm vertical
  • Approach stability 49/100
  • 0 kt wind
  • 0 kt crosswind component
  • 16,093 m visibility
  • KRIC 162154Z 14006KT 10SM FEW300 27/17 A3031 RMK AO2 SLP266 T02720172

Flight context

  • VADER20
  • United States Government
  • B752
  • KRIC → KRIC
  • 2026-07-22 14:46 UTC
  • KRIC runway 16

All events on this flight

Return to field 14:46:02 UTC · KRIC runway 16 · 22,109 ft AGL · 443 kt GS
Unstable approach 16:36:02 UTC · KRIC runway 16 · 1,293 ft AGL · 124 kt GS

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· KRIC