Return to field — N907NA

KEFD · 17R

2026-07-20 18:50 UTC· KEFD KEFD· NATIONAL AERONAUTICS AND SPACE ADMINISTRATION· T38

N907NA (National Aeronautics and Space Administration) had departed KEFD on 2026-07-20. SkyMeter detected a return to field at Ellington Airport (KEFD) on runway 17R at 18:50 UTC. Peak cruise altitude FL484, turnaround area near Matagorda, US. Approach stability score: 19/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)
  • SECURITY6/4068 2026-06-01 05:00Z – 2026-07-21 04:59Z SFC–400 ft

    HOUSTON, TX, Monday, June 1, 2026 through Monday, July 20, 2026 Local

    View FAA NOTAM →
  • SECURITY6/6787 2026-07-03 15:07Z – 2026-07-21 04:59Z SFC–400 ft

    Houston, TX

    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 17R
  • 48476 ft AGL at event
  • 606 kt ground speed
  • 0 fpm vertical
  • Approach stability 19/100
  • 0 kt wind
  • 0 kt crosswind component
  • 16,093 m visibility
  • KEFD 170654Z 07003KT 10SM CLR 29/26 A3013

Flight context

  • N907NA
  • National Aeronautics and Space Administration
  • T38
  • KEFD → KEFD
  • 2026-07-20 18:50 UTC
  • KEFD runway 17R

All events on this flight

Return to field 18:50:10 UTC · KEFD runway 17R · 48,476 ft AGL · 606 kt GS
EmergencyDescent 19:13:25 UTC · · 41,520 ft AGL · 529 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· KEFD