Return to field — N921NA

KEFD · 17R

2026-06-12 13:08 UTC· KEFD → KEFD· NATIONAL AERONAUTICS AND SPACE ADMINISTRATION, C/O RICHARD N CLA· T38

N921NA (National Aeronautics and Space Administration) had departed KEFD on 2026-06-12. SkyMeter detected a return to field at Ellington Airport (KEFD) on runway 17R at 13:08 UTC. Peak cruise altitude FL455, turnaround area near Hamilton, US. Approach stability score: 12/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/4240 2026-03-08 08:00Z – 2026-11-01 07:00Z SFC–180 ft

    SAN ANGELO, TX, Sunday, March 8, 2026 through Sunday, November 1, 2026 Local

    View FAA NOTAM →
  • SECURITY6/3999 2026-06-01 05:00Z – 2026-07-21 04:59Z SFC–400 ft

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

    View FAA NOTAM →
  • SECURITY6/4000 2026-06-01 05:00Z – 2026-07-21 04:59Z

    MANSFIELD, TX, Monday, June 1, 2026 through Tuesday, July 21, 2026 UTC

    View FAA NOTAM →
  • SECURITY6/4002 2026-06-01 05:00Z – 2026-07-21 04:59Z SFC–400 ft

    FORT WORTH, TX, Monday, June 1, 2026 through Monday, July 20, 2026 Local

    View FAA NOTAM →
  • SECURITY6/4008 2026-06-01 05:00Z – 2026-07-21 04:59Z SFC–400 ft

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

    View FAA NOTAM →
  • SECURITY6/4009 2026-06-01 05:00Z – 2026-07-21 04:59Z SFC–400 ft

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

    View FAA NOTAM →
  • SECURITY6/4019 2026-06-01 05:00Z – 2026-07-21 04:59Z SFC–400 ft

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

    View FAA NOTAM →
  • SECURITY6/4025 2026-06-01 05:00Z – 2026-07-21 04:59Z

    DENTON, TX, Monday, June 1, 2026 through Tuesday, July 21, 2026 UTC

    View FAA NOTAM →
  • SECURITY6/4030 2026-06-01 05:00Z – 2026-07-21 04:59Z SFC–400 ft

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

    View FAA NOTAM →
  • SECURITY6/4059 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/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/4097 2026-06-01 05:00Z – 2026-07-21 04:59Z

    SAN ANTONIO, TX, Monday, June 1, 2026 through Tuesday, July 21, 2026 UTC

    View FAA NOTAM →
  • SECURITY6/6447 2026-06-09 05:01Z – 2026-07-20 04:59Z SFC–1,000 ft

    Houston, TX, Tuesday, June 9, 2026 through Sunday, July 19, 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 17R
  • 45556 ft AGL at event
  • 546 kt ground speed
  • 0 fpm vertical
  • Approach stability 12/100
  • 0 kt wind
  • 0 kt crosswind component
  • 16,093 m visibility
  • KEFD 131854Z 14012G18KT 10SM BKN030 33/24 A2997

Flight context

  • N921NA
  • National Aeronautics and Space Administration
  • T38
  • KEFD → KEFD
  • 2026-06-12 13:08 UTC
  • KEFD runway 17R

All events on this flight

Return to field 13:08:08 UTC · KEFD runway 17R · 45,556 ft AGL · 546 kt GS
Unstable approach 16:54:08 UTC · KEFD runway 22 · 1,125 ft AGL · 189 kt GS
Unstable approach 16:54:08 UTC · KEFD runway 22 · 1,125 ft AGL · 189 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