Return to field — N921NA
KEFD · 17R2026-06-09 19:40 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-09. SkyMeter detected a return to field at Ellington Airport (KEFD) on runway 17R at 19:40 UTC. Peak altitude 10,618 ft, turnaround area near Wharton, US. 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/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/5855 2026-06-08 13:00Z – 2026-06-09 22:00Z SFC–1,000 ft
Houston, TX, Monday, June 8, 2026 through Tuesday, June 9, 2026 Local
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
- 10618 ft AGL at event
- 424 kt ground speed
- 0 fpm vertical
- 0 kt wind
- 0 kt crosswind component
- 16,093 m visibility
- KEFD 150654Z 11004KT 10SM SCT025 23/20 A3000
Flight context
- N921NA
- National Aeronautics and Space Administration
- T38
- KEFD → KEFD
- 2026-06-09 19:40 UTC
- KEFD runway 17R
All events on this flight
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