Return to field — N926NA
KEFD · 17R2026-06-25 15:40 UTC· KEFD → KEFD· NATIONAL AERONAUTICS AND SPACE ADMINISTRATION· WB57
N926NA (National Aeronautics and Space Administration) had departed KEFD on 2026-06-25. SkyMeter detected a return to field at Ellington Airport (KEFD) on runway 17R at 15:40 UTC. Peak cruise altitude FL478, turnaround area near Refugio, US. Approach stability score: 45/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/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 → - HAZARDS6/9459 2026-06-21 05:00Z – 2026-06-28 06:28Z SFC–5,000 ft
PORT ISABEL, TX, Sunday, June 21, 2026 through Sunday, June 28, 2026 UTC
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
- 47883 ft AGL at event
- 369 kt ground speed
- 0 fpm vertical
- Approach stability 45/100
- 0 kt wind
- 0 kt crosswind component
- 16,093 m visibility
- KEFD 090554Z 01003KT 10SM CLR 23/17 A2990
Flight context
- N926NA
- National Aeronautics and Space Administration
- WB57
- KEFD → KEFD
- 2026-06-25 15: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