Return to field — JENA708

KRIC · 31

2026-04-16 16:45 UTC· KRIC → KRIC· UNITED STATES GOVERNMENT, DEPARTMENT OF JUSTICE· GLF5

▶ Replay 📊 Analyse

JENA708 (United States Government) had departed KRIC on 2026-04-16. SkyMeter detected a return to field at Richmond International Airport (KRIC) on runway 31 at 16:45 UTC. Peak cruise altitude FL303, turnaround area near Seabrook Farms, US. Approach stability score: 64/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 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)
  • SECURITY5/2811 2025-10-20 12:00Z – 2026-10-20 12:00Z SFC–1,000 ft

    NEW YORK, NY, Monday, October 20, 2025 through Tuesday, October 20, 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 31
  • 30365 ft AGL at event
  • 512 kt ground speed
  • 0 fpm vertical
  • Approach stability 64/100
  • 0 kt wind
  • 0 kt crosswind component
  • 16,093 m visibility
  • KRIC 210554Z 00000KT 10SM BKN060 BKN250 24/22 A2993 RMK AO2 LTG DSNT N SLP137 60000 T02390217 10267 20228 51001 $

Flight context

  • JENA708
  • United States Government
  • GLF5
  • KRIC → KRIC
  • 2026-04-16 16:45 UTC
  • KRIC runway 31

All events on this flight

Return to field 16:45:39 UTC · KRIC runway 31 · 30,365 ft AGL · 512 kt GS
Go-around 19:04:08 UTC · KMDT runway 31 · 427 ft AGL · 137 kt GS
Go-around 19:04:08 UTC · KMDT runway 31 · 427 ft AGL · 137 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