Return to field — N967NA

KADW · 19R

2026-07-04 17:07 UTC· KADW → KADW· NATIONAL AERONAUTICS & SPACE ADMIN· T38

▶ Replay 📊 Analyse

N967NA (National Aeronautics & Space Admin) had departed KADW on 2026-07-04. SkyMeter detected a return to field at Joint Base Andrews (KADW) on runway 19R at 17:07 UTC. Peak altitude 7,483 ft, turnaround area near Brandywine, US. Approach stability score: 51/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)
  • AIR SHOWS/SPORTS6/0944 2026-07-03 14:00Z – 2026-07-05 03:30Z SFC–15,000 ft

    Washington, DC, Friday, July 3, 2026 through Sunday, July 5, 2026 UTC

    View FAA NOTAM →
  • AIR SHOWS/SPORTS6/1371 2026-07-03 14:00Z – 2026-07-05 03:30Z SFC–15,000 ft

    Washington, DC, Friday, July 3, 2026 through Sunday, July 5, 2026 UTC

    View FAA NOTAM →
  • VIP6/2673 2026-07-04 12:00Z – 2026-07-04 22:30Z SFC–9,999 ft

    Sterling, VA, Saturday, July 4, 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 19R
  • 7483 ft AGL at event
  • 425 kt ground speed
  • 0 fpm vertical
  • Approach stability 51/100
  • 0 kt wind
  • 0 kt crosswind component
  • 16,093 m visibility
  • KADW 162255Z AUTO 19005KT 10SM CLR 26/17 A3026 RMK AO2 SLP253 T02570173

Flight context

  • N967NA
  • National Aeronautics & Space Admin
  • T38
  • KADW → KADW
  • 2026-07-04 17:07 UTC
  • KADW runway 19R

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